>Is it just me, or don't kernel Oopses usually contain symbol data?
not until the person with the oops uses the ksymoops util.
save what you sent below in a text file, and compile (g++ ksymoops.cc)
/usr/src/linux/scripts/ksymoops.cc
then cat that text file | ksymoops.cc /boot/System.map
then send us the output.
sorry, this connection sucks so im gonna sign off without saying anything else
>>EIP:0010:[<00125918>]
>>
>>EFLAGS:00060286
>>
>>eax:64ff5030 ebx:00000307 ecx:03823f94 edx:00000603
>>
>>ds:0018 es:0018 fs:002b gs:002b ss:0018
>>
>>process e2fsck (pid:148, process nr:14, stackpage=03823000
>>
>>stack: 00000002 00020307 03823e94 03823d30 00000c03 00126179 00000307
>> 00024f04 00000400 00000002 03823e94 00000000 00000001 00129c4f
>> 00000307 00024f04 00000400 03ec1880 00000400 03acbac00 000c5da0
>>
>>call trace:
>>[<00126179>][<00129c4f>][<00126179>][<0018a7eb>][<0011cdb2>][00112f54>]
>>[<0012f1c>][<00112f54>][<00118983>][<0010abab>][<0012990c>][<00123c02>]
>>[<0010ac25>]
>>
>>Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 db f9 ff
>>Segmentation fault
>>------------------------------------------------------------
>>[end black screen of death]
>---------------------------------------------------------------------------
>Send administrative requests to [EMAIL PROTECTED]
>
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
