lkml.org 
[lkml]   [2003]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectproblems while burning
Hi,

I'm new to this list and already searched the archive, but didn't find
anything that helped.

My Problem is the following:

I've got a LiteOn Lt12101B IDE CD Burner here and it causes Kernel
Panics once in a while. I cannot reproduce this safely, but it comes up
when the PC not only does the burning, but a make or a galeon session
also.

The first mysterious thing is that as far as I've tested until now, it
only comes up with cdrecord, cdrdao burns images without kernel panic.

For the hardware and that stuff:

I've got a PIII 500 MHz on a Tyan Tsunami AT (PIIX4 Chip). The primary
master is a SAMSUNG SV4002H with the following from
/proc/ide/hda/settings:
name value min max mode
---- ----- --- --- ----
current_speed 66 0 69 rw
init_speed 66 0 69 rw
io_32bit 1 0 3 rw
multcount 16 0 16 rw
pio_mode write-only 0 255 w
using_dma 1 0 1 rw

primary slave is a Mistumi FX4820T with settings:
name value min max mode
---- ----- --- --- ----
current_speed 66 0 69 rw
init_speed 66 0 69 rw
io_32bit 1 0 3 rw
pio_mode write-only 0 255 w
using_dma 1 0 1 rw

secondary master is the LITE-ON LTR-12101B
with setting:
name value min max mode
---- ----- --- --- ----
current_speed 34 0 69 rw
init_speed 34 0 69 rw
io_32bit 0 0 3 rw
pio_mode write-only 0 255 w
using_dma 1 0 1 rw

and the secondary Slave is a Maxtor 91360U4 with settings:
name value min max mode
---- ----- --- --- ----
current_speed 66 0 69 rw
init_speed 66 0 69 rw
io_32bit 1 0 3 rw
multcount 16 0 16 rw
pio_mode write-only 0 255 w
using_dma 1 0 1 rw

The Image lies on the primary HDD and the cdrecord call is:

| cdrecord -VVVV debug=7 -kd=7 -vvvv -fs=16m dev=0,1,0 \
| timeout=60 driveropts=burnfree -xa2 iso.bin

The Bin-Iso-image was made with cdrdao, but it also happens with
mkisofs-created ones. I can also remove all switches and it still
hapens.

Sometimes there is somethins in /var/log/messages:

In some cases I get:
| Dec 19 18:06:38 debian kernel: scsi : aborting command due to timeout :
| pid 4561
| , scsi0, channel 0, id 1, lun 0 0x2a 00 00 01 f0 ba 00 00 1f 00
| Dec 19 18:06:38 debian kernel: hdc: timeout waiting for DMA
| Dec 19 18:06:38 debian kernel: ide_dmaproc: chipset supported
| ide_dma_timeout fu
| nc only: 14
| Dec 19 18:06:38 debian kernel: hdc: status timeout: status=0xd8 { Busy }
| Dec 19 18:06:38 debian kernel: hdc: drive not ready for command
| Dec 19 18:07:08 debian kernel: hdc: ATAPI reset timed-out, status=0x88
| Dec 19 18:07:08 debian kernel: hdd: DMA disabled
| Dec 19 18:07:13 debian kernel: scsi : aborting command due to timeout :
| pid 4561
| , scsi0, channel 0, id 1, lun 0 0x2a 00 00 01 f0 ba 00 00 1f 00
| Dec 19 18:07:13 debian kernel: SCSI host 0 abort (pid 4561) timed out -
| resetting

And so on, until I reset the system.

And 2 times in the last 4 I got:
| Jan 7 20:40:17 debian kernel: scsi : aborting command due to timeout :
| pid 1356
| 4, scsi0, channel 0, id 1, lun 0 0x2a 00 00 00 4c 69 00 00 1f 00
| Jan 7 20:40:17 debian kernel: hdc: timeout waiting for DMA
| Jan 7 20:40:17 debian kernel: ide_dmaproc: chipset supported
| ide_dma_timeout fu
| nc only: 14
| Jan 7 20:40:17 debian kernel: hdd: status timeout: status=0xd8 { Busy }
| Jan 7 20:40:17 debian kernel: hdd: DMA disabled
| Jan 7 20:40:17 debian kernel: hdd: drive not ready for command
| Jan 7 20:40:17 debian kernel: ide1: reset: master: error (0x00?)

I havn't got the time to try to disable dma with hdparm -d0 or to reduce
the speed of the cdburner to something below 34 (which is mdma? right).

Is there something else that can be done about this?

Ooops I forgot: Kernel is 2.4.20 from debian packages, I can send the
config if it is needed.

Andreas

--
Gut ist auch das Emporkommen von Linux als Herausforderer von Microsoft.
-- CDU-Vorsitzende Angela Merkel
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2005-03-22 13:32    [W:0.046 / U:2.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site