Date: Sun, 26 Feb 2006 11:24:28 -0800 From: Kent Stewart <kstewart@owt.com> To: freebsd-questions@freebsd.org Cc: Garrett Cooper <youshi10@u.washington.edu>, Kris Kennaway <kris@obsecurity.org> Subject: Re: anyone recognize this panic? Message-ID: <200602261124.28829.kstewart@owt.com> In-Reply-To: <20060226061343.GA4483@xor.obsecurity.org> References: <17409.8562.677322.222883@jerusalem.litteratus.org> <440145EF.5000101@u.washington.edu> <20060226061343.GA4483@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 25 February 2006 22:13, Kris Kennaway wrote: > On Sat, Feb 25, 2006 at 10:08:47PM -0800, Garrett Cooper wrote: > > Kris Kennaway wrote: > > >On Sat, Feb 25, 2006 at 10:33:06PM -0500, Robert Huff wrote: > > >> I just had my -CURRENT* machine crash under moderate load. No > > >>dump is available because the machine locked hard, but I did copy > > >>this off the screen: > > >> > > >>re0: diagnostic failed to receive packet in loopback mode > > >>re0: attach aborted due to hardware diagnostic failure > > >>panic: mtx_lock() of spin mutex (null) @ > > >> /usr/src/sys/netinet/in_pcb,c:862 > > >> > > >> "re0" is a Linksys EG-1032, less than two months old. It was > > >>connected, but had zero traffic at the time of the crash. > > >> Before I take this to current@ - has anyone seen anything like > > >>this before? A quick check of the archives and the web in > > >> general didn't show anything. > > > > > >You need to at least get a traceback from the panic, and > > > preferably a crashdump. > > > > > >Kris > > > > Probably should pass this onto some devs. It seems like a null > > value was passed for locking a mutex in the OS, which is important. > > Having a traceback would be good though... but at least mentioning > > that the issue laid with the re (?) kernel driver would be a start. > > Unfortunately without a traceback the panic string is useless since > it gives you no clue about how the system got into that state. This > kind of panic is often a secondary effect of some other problem. > I can cause this to happen almost at will with a Netgear GA311. It only happens at boot. It will reboot after the panic just fine and, for me, it only happens repeatedly after I do a restart boot from XP. It has never happened if I shut the system down first. I have moved many GBs of distfiles and packages with out causing a panic. I haven't found a way to cause a dmp when it panics. At least, what I have read doesn't work. So, how can I get a dmp, which I can provide a traceback? Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602261124.28829.kstewart>