Matthias Biel wrote:

please pipe your oops log through ksymoops so that the symbols get resolved. Otherwise it has no meaning to us.

How can i do that?



Look at


/usr/src/linux/Documentation/oops-tracing.txt

Am i right if i think i should send the according
*.ksyms and *.modules files from /var/log/ksymoops?



When the kernel detect a problem, a dump of the current state (register values, stack, ...) is generated and (with luck) written to a log file (depending on your distribution). Sometimes its only printed on the console..too bad if the screen safer was active by that time.
There is a patch available that write the state information to a floppy, but I haven't tried it.


In any case, you have to pipe the state information into ksymoops and send the output to the list.

use


$ dmesg | ksymoops

in order to resolve the symbol names in the kernel log ringbuffer. You can use dmesg also to adjust the size of the logging buffer and to enable/disable kernel logs on the current console.

Holger



--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as 
subject.



Reply via email to