Re: Can not allocate memory for KERN_MSGBUF

[Mark Kettenis]

This happens if kernel and the dmesg(8) userland program are out of
sync.  And yes, that can even happen for snapshots.  Next snapshot
should be ok again.

Re: Can not allocate memory for KERN_MSGBUF

[Andreas Kusalananda Kähäri]

On Fri, Jun 24, 2016 at 01:19:32PM +0200, Alexander Bluhm wrote:
> On Fri, Jun 24, 2016 at 10:30:04AM +0200, Andreas Kusalananda K?h?ri wrote:
> > I'm following -current on amd64, running in VirtualBox.  I recompiled
> > the kernel today with fresh sources, like I do a few times a week on
> > slow days.
> 
> Have you also installed /usr/include/sys/msgbuf.h from
> /usr/src/sys/sys/msgbuf.h and recomiled /usr/src/sbin/dmesg ?
> A make build should do that.
> 
> bluhm
> 

I believe I have fallen into the trap of not recompiling the userland
binaries before reacting te seeing the dmesg command misbehave.

I was doing a regular update of the system so I recompiled the kernel
and rebooted.  I have a piece of shell code in my login scripts that
compares the dmsg output from the current boot with that of the previous
boot, and when I saw that there was no output from the current boot I
reacted before thinking.


I am sincerely sorry for the noise.

Regards,


signature.asc
Description: PGP signature

Re: Can not allocate memory for KERN_MSGBUF

[Alexander Bluhm]

On Fri, Jun 24, 2016 at 10:30:04AM +0200, Andreas Kusalananda K?h?ri wrote:
> I'm following -current on amd64, running in VirtualBox.  I recompiled
> the kernel today with fresh sources, like I do a few times a week on
> slow days.

Have you also installed /usr/include/sys/msgbuf.h from
/usr/src/sys/sys/msgbuf.h and recomiled /usr/src/sbin/dmesg ?
A make build should do that.

bluhm