FS#6488 - System hangs when trying to access corrupted media
Attached to Project:
Arch Linux
Opened by Tal Levy (levytal) - Sunday, 25 February 2007, 21:42 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 10 June 2007, 09:50 GMT
Opened by Tal Levy (levytal) - Sunday, 25 February 2007, 21:42 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 10 June 2007, 09:50 GMT
|
Details
In the middle of burning a disc with k3b the system hangs
and takes a very long time to respond to input. The CD drive
is not ejectable and is constantly being read from. There is
no obvious process to kill to this condition and trying to
rmmod doesn't work either. dmesg gives this output:
hdc: status timeout: status=0xd8 { Busy } ide: failed opcode was: unknown hdc: drive not ready for command hdd: status timeout: status=0xd8 { Busy } ide: failed opcode was: unknown hdd: drive not ready for command BUG: soft lockup detected on CPU#0! [<c014d30b>] softlockup_tick+0xab/0x110 [<c0131131>] update_process_times+0x31/0x80 [<c01178a0>] smp_apic_timer_interrupt+0x90/0xb0 [<c0103d43>] apic_timer_interrupt+0x1f/0x24 [<e082cd73>] ide_inb+0x3/0x10 [ide_core] [<e082e1fc>] ide_wait_stat+0xec/0x120 [ide_core] [<e082bae5>] ide_do_request+0x335/0xa20 [ide_core] [<e082c95d>] ide_timer_expiry+0xcd/0x2e0 [ide_core] [<c01310cb>] run_timer_softirq+0x16b/0x1a0 [<e082c890>] ide_timer_expiry+0x0/0x2e0 [ide_core] [<c012c1b4>] __do_softirq+0x74/0xf0 [<c0405250>] unknown_bootoption+0x0/0x270 [<c012c26b>] do_softirq+0x3b/0x50 [<c012c4c5>] irq_exit+0x45/0x50 [<c01178a5>] smp_apic_timer_interrupt+0x95/0xb0 [<c0103d43>] apic_timer_interrupt+0x1f/0x24 [<c0405250>] unknown_bootoption+0x0/0x270 [<c0101b57>] default_idle+0x37/0x70 [<c0101c06>] cpu_idle+0x76/0xe0 [<c0405826>] start_kernel+0x366/0x430 [<c0405250>] unknown_bootoption+0x0/0x270 ======================= hdc: status timeout: status=0xd8 { Busy } ide: failed opcode was: unknown hdc: drive not ready for command hdd: status timeout: status=0xd8 { Busy } ide: failed opcode was: unknown hdd: drive not ready for command hdd: status timeout: status=0xd8 { Busy } ide: failed opcode was: unknown hdd: drive not ready for command hdd: status timeout: status=0xd8 { Busy } ide: failed opcode was: unknown hdd: drive not ready for command hdd: status timeout: status=0xd8 { Busy } ide: failed opcode was: unknown hdd: drive not ready for command A similar situation also occurs when trying to access bad blocks on a hard disk. |
This task depends upon
Comment by
Tobias Powalowski (tpowa) - Monday,
09 April 2007, 17:19 GMT
you could try to use the new pata subsystem for the burner,
perhaps it fixes your problem
Comment by
Tobias Powalowski (tpowa) - Sunday,
06 May 2007, 09:15 GMT
any response? else i close this tomorrow