Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Apr 2010 16:05:31 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        Mike Tancsa <mike@sentex.net>
Cc:        pyunyh@gmail.com, freebsd-current@freebsd.org, Jack Vogel <jfvogel@gmail.com>
Subject:   Re: LOR on em in HEAD ( was Re: em driver regression
Message-ID:  <20100410160008.Q40281@maildrop.int.zabbadoz.net>
In-Reply-To: <201004101446.o3AEkQ0O058513@lava.sentex.ca>
References:  <201004081831.o38IVR3s043434@lava.sentex.ca> <n2q2a41acea1004081406o969e7acbla0cef35f65f14f0a@mail.gmail.com> <20100408230750.GR5734@michelle.cdnetworks.com> <201004091317.o39DHFEl049965@lava.sentex.ca> <20100409164115.GB1085@michelle.cdnetworks.com> <g2u2a41acea1004090945p6f77ee30yeb9fbab9a8e43863@mail.gmail.com> <201004091900.o39J0b0k051687@lava.sentex.ca> <z2r2a41acea1004091209maca81e47td7f03d7c343b3ec9@mail.gmail.com> <20100409201307.GF1085@michelle.cdnetworks.com> <201004092105.o39L5SSh052323@lava.sentex.ca> <q2x2a41acea1004091411gfb99e085ka841661a66216d40@mail.gmail.com> <201004101446.o3AEkQ0O058513@lava.sentex.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 10 Apr 2010, Mike Tancsa wrote:

Hi Mike,

> At 05:11 PM 4/9/2010, Jack Vogel wrote:
>> Don't know, but I would just ignore it, I think its a false warning anyway.
>
> OK.  I updated to HEAD as of this AM, but now I get a panic at bootup
>
...
> Trying to mount root from nfs:
> NFS ROOT: 10.255.255.1:/usr/home/pxe9/
> panic: mutex em0:rx(0) not owned at 
> /usr/HEAD/src/sys/modules/em/../../dev/e1000/if_em.c:4093
> cpuid = 3
> KDB: enter: panic
> [ thread pid 0 tid 100032 ]
> Stopped at      kdb_enter+0x3a: movl    $0,kdb_why
> db> bt
> Tracing pid 0 tid 100032 td 0xc5f5bb40
> kdb_enter(c0cb0e9d,c0cb0e9d,c0caf56e,c5b2ac28,3,...) at kdb_enter+0x3a
> panic(c0caf56e,c6002024,c11a0357,ffd,c5b2ac7c,...) at panic+0x136
> _mtx_assert(c6002010,4,c11a0357,ffd,64,...) at _mtx_assert+0x87
> em_rxeof(246,c5ff7d98,c5b2aca8,c088e194,c5ff7d98,...) at em_rxeof+0x3b
> em_handle_que(c6006000,1,c0cb5c9c,4f,c5ff7d98,...) at em_handle_que+0x38
> taskqueue_run(c5ff7d80,c5ff7d98,c0ca6410,0,c0caf5f6,...) at 
> taskqueue_run+0x103
> taskqueue_thread_loop(c600a520,c5b2ad38,c0cac192,343,c0e0ce20,...) at 
> taskqueue_thread_loop+0x68
> fork_exit(c08dcde0,c600a520,c5b2ad38) at fork_exit+0xb8
> fork_trampoline() at fork_trampoline+0x8
> --- trap 0, eip = 0, esp = 0xc5b2ad70, ebp = 0 ---
> db>


This is a bug that seems to only happen in the Kitchener area as I hit
it with a machine there just a few minutes ago as well.

This one has fixed it for me:
http://lists.freebsd.org/pipermail/svn-src-head/2010-April/016249.html

/bz

-- 
Bjoern A. Zeeb         It will not break if you know what you are doing.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100410160008.Q40281>