Messages in this thread | | | Date | Sat, 25 Dec 1999 16:58:51 +0100 | From | Manfred Spraul <> | Subject | Re: Bug at spinlock.h line 92 |
| |
Sergey Kubushin wrote: > > I attach the ksymoops output on the oops sequence and the oopses itself. I > do really hope that someone will fix this bug. > > Call Trace: [eepro100:eepro100_init+-643084/10933] [eepro100:eepro100_init+-535563/10933] ^^^^^^^^^^^^ The offset is larger then the length of the function. This often means that the module which caused the oops was not loaded/loaded to a different address when ksymoops tried to decode the oops.
It's virtually impossible to analyze such an oops report, could you crash your server once more?
* disable the EIP translation of klogd [klogd -x] * insmod the scsi module. * save your /proc/ksyms and /proc/modules file. * crash the server * <restart?> * run 'ksymoops -k /tmp/ksyms -l /tmp/modules' and post the result.
How much memory do you have installed? 256 MB?
-- Manfred
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |