anyone recognize this panic?
youshi10 at u.washington.edu
Sat Feb 25 22:08:49 PST 2006
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
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.
More information about the freebsd-questions