They added this debug in the code recently.  I’m not sure if it is upstreamed 
into illumos proper, but the idea is that you should never explicitly call this 
function with a zero size.  (It used to be OK, but now is undesired.)

Something in syslog is doing so.  Tracking it down will require looking at the 
code.  This message was supposed to help find things that do this.  Apart from 
the messages themselves, it’s harmless for now.

        - Garrett


> On May 27, 2015, at 12:19 PM, Jason Lawrence <[email protected]> wrote:
> 
> Ever since upgrading to joyent_20150514T133314Z, my dmesg logs have been
> flooded with messages like this:
> 
> 2015-05-27T18:49:41.314478+00:00 hostname genunix: [ID 801535 kern.warning] 
> WARNING: kmem_alloc(): sleeping allocation with size of 0
> 2015-05-27T18:50:41.473881+00:00 hostname genunix: [ID 801535 kern.warning] 
> WARNING: kmem_alloc(): sleeping allocation with size of 0
> 2015-05-27T18:51:41.633887+00:00 hostname genunix: [ID 801535 kern.warning] 
> WARNING: kmem_alloc(): sleeping allocation with size of 0
> 2015-05-27T18:52:41.793817+00:00 hostname genunix: [ID 801535 kern.warning] 
> WARNING: kmem_alloc(): sleeping allocation with size of 0
> 
> I can't find any other context in related logs. I have a mix of native, KVM, 
> and LX zones running. Anyone have suggestions to what is causing this?
> 
> --jason
> 
> 
> -------------------------------------------
> smartos-discuss
> Archives: https://www.listbox.com/member/archive/184463/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/184463/22103350-51080293
> Modify Your Subscription: https://www.listbox.com/member/?&;
> Powered by Listbox: http://www.listbox.com



-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to