Call Trace on boot

[Zach Wilkinson]

That's OK, it seems to work anyway.  No show stopper.
Besides, not being a engineer, I doubt I'm eligible to file a bug report.
Last thing I want is to get flamed about presuming to be able to file a bug
report.  Best to leave well enough alone; these lists can be rough
territory.

Thanks,

----- Original Message ----- 
From: "Dave Jones" <davej at redhat.com>
To: "For testers of Fedora Core development releases"
<fedora-test-list at redhat.com>
Sent: Thursday, April 01, 2004 5:38 AM
Subject: Re: Call Trace on boot


> On Wed, 2004-03-31 at 20:26, Zach Wilkinson wrote:
> > I started getting these errors after upgrading to 2.6.4 out of the
> > development tree.
> >
> > ip_tables: (C) 2000-2002 Netfilter core team
> > PCI: Enabling device 0000:00:09.0 (0014 -> 0017)
> > sk98lin: Network Device Driver v6.23
> > (C)Copyright 1999-2004 Marvell(R).
> > divert: allocating divert_blk for eth0
> > eth0: 3Com Gigabit LOM (3C940)
> >       PrefPort:A  RlmtMode:Check Link State
> > ip_tables: (C) 2000-2002 Netfilter core team
> > Debug: sleeping function called from invalid context at mm/slab.c:1943
> > in_atomic():0, irqs_disabled():1
> > Call Trace:
> >  [<02120144>] __might_sleep+0x80/0x8a
> >  [<02149cdf>] kmem_cache_alloc+0x1c/0x143
>
> Thou shalt not allocate memory with interrupts off.
>
> Please bugzilla this.
>
> Dave
>
>
> -- 
> fedora-test-list mailing list
> fedora-test-list at redhat.com
> To unsubscribe:
> http://www.redhat.com/mailman/listinfo/fedora-test-list
>