[lug] Mystery Kernel Panic on cdrecord

Steve T. maxl at squeep.com
Sun Mar 3 22:24:44 MST 2002


Greetings.

  I have been getting bizarre mystery kernel panics that appear to be refering
to either the interrupt handler or potentially a kernel paging mechanism -
alas, I have never encountered the Kernel Panic beast before.

The Panic occurs when trying to use cdrecord to write to a Memorex CD-RW
that lurks on device number 0,0,0; cdrecord starts up right proper fine,
and when it goes into writing the CD, quite suddenly the charming kernel
panic is produced.  I typed it by hand due to a lack of it appearing in any
sort of logging facility; I'm assuming this means it totally thrashes the
system in the most horrendous way possible.

For the record, the kernel running on the machine is a stock 2.4.18.

I know that the drive has been used before to write CDs under Linux, and was
used to write a CD back in mid-Septemberish; could it be possible that the
drive has simply given out, and rather than just refuse to work, has decided
to explode?  I know it works perfectly fine for reading from CDs.

Further information available upon request if it is necessary to help debug
and understand my problem.  Enjoy the kernel panic message.

-- 
Stephen Tramer:	    | "From a certain point onward there
Math, programming,  |   is no longer any turning back.
 typesetting, linux |   That is the point that must be reached."
maxl at squeep.com     | -- F. Kafka

-------------- next part --------------

Unable to handle kernel paging request at virtual address 88b09814
*pde = 00000000
Oops: 0000
CPU: 1
EIP: 0010:[<88b09814>]	Not tainted
EFLAGS: 00010046
eax: 88b09814	ebx: 00000046	ecx: 00000000	edx: d7d414a0
esi: 00000000	edi: 00000000	ebp: d5278000	esp: c1c1be94
ds: 0018	es: 0018	ss: 0018
Process swapper (pid: 0, stackpage=c1c1b000)
Stack: f088b41d d5381732 d7d414a0 c030c490 000000d0 c030c450 00000000 d7d414a0
       c1c0e4a0 c030c490 c01c1d22 00000000 efeede60 c030c490 efeede60 f088b470
       000000d0 c01c291a c030c490 c024ba02 000000d0 efeede60 c01c2770 00000000
Call Trace: [<f088b41d>] [<c01c1d22>] [<f088b470>] [<c01c291a>] [<c01c2770>]
  [<c011eb96>] [<c011b170>] [<c011b04d>] [<c011adef>] [<c010874d>] [<c01051c0>]

  [<c01051c0>] [<c010a888>] [<c01051c0>] [<c01051c0>] [<c01051ec>] [<c0105252>]

  [<c0116f1e>] [<c0116e2f>]

Code: Bad EIP value.
 <0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing


More information about the LUG mailing list