[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#309964: marked as done ("drive appears confused (ireason = 0x01)" and linux hangs)

Your message dated Thu, 8 May 2008 23:07:29 +0200
with message-id <20080508210729.GI13915@stro.at>
and subject line Re: "drive appears confused (ireason = 0x01)" and linux hangs
has caused the Debian Bug report #309964,
regarding "drive appears confused (ireason = 0x01)" and linux hangs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
309964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309964
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: kernel-image-2.6.11-9-em64t-p4-smp
Version: 2.6.11-2
Severity: grave

while booting the message "hdb: cdrom_pc_intr: The drive appears
confused (ireason = 0x01)" repeats several times and the system hangs
for some seconds. After booting and running some applications the same
message repeats and linux hangs. It makes all newer kernels unusable
with my hardware.

On the bottom of this mail you'll find an extract of /var/log/syslog
showing this error.


My system is a P4 630 with em64t, ASUS P5GD2 Premium board (ICH6
chipset), 250GB Seagate SATA harddisk and nvidia 6600GT PCIe graphic card.
I'm running debian SID for amd64.

I've had these bugs in self compiled linux kernels 2.6.11.8, 2.6.12rc4
and the default debian kernel 2.6.11-9-em64t-p4-smp.
The default debian kernel 2.6.8-11-em64t-p4-smp on debian for amd64
seems to be the only one that I can use. There the error does not occur
and so the system does not hang. So it has to be a broken module in a
newer kernel than 2.6.8 that is responsible for this error.


Here are some bootmessages from /var/log/syslog:

...
ICH6: chipset revision 3
ICH6: 100%% native mode on irq 18
    ide0: BM-DMA at 0x5800-0x5807, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0x5808-0x580f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: IC35L060AVV207-0, ATA DISK drive
hdb: SONY CD-RW CRX210E1, ATAPI CD/DVD-ROM drive
ide0 at 0x7000-0x7007,0x6802 on irq 18
Probing IDE interface ide1...
Probing IDE interface ide1...
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
hda: max request size: 1024KiB
hda: 120103200 sectors (61492 MB) w/1821KiB Cache, CHS=16383/255/63,
UDMA(100)
hda: cache flushes supported
 hda: hda1
hdb: packet command error: status=0xd0 { Busy }
ide: failed opcode was: unknown
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Losing some ticks... checking if CPU frequency changed.
ide: failed opcode was: unknown
hdb: drive not ready for command
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
last message repeated 37 times
irq 18: nobody cared!

Call Trace: <IRQ> <ffffffff80151c54>{__report_bad_irq+48}
<ffffffff80151d18>{note_interrupt+91}
       <ffffffff801516d3>{__do_IRQ+257} <ffffffff80110469>{do_IRQ+67}
       <ffffffff8010ddc1>{ret_from_intr+0}  <EOI>
<ffffffff8010dee9>{retint_kernel+38}
       <ffffffff8010bb2c>{mwait_idle+94} <ffffffff8010bab0>{cpu_idle+71}
       <ffffffff80670876>{start_kernel+445}
<ffffffff8067022c>{x86_64_start_kernel+320}

handlers:
[<ffffffff80308031>] (ide_intr+0x0/0x17a)
Disabling IRQ #18
ide-cd: cmd 0x5a timed out
hdb: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hdb: DMA disabled
hdb: ATAPI reset complete
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
last message repeated 52 times
Uniform CD-ROM driver Revision: 3.20
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
last message repeated 3 times
...


Regards,
Alexander







-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCjjs5lLqZutoTiOMRAhKQAJ0ZtqYkY5wv3z7oz6E6KVUTlU7wrgCaA3HF
OX2mQjUjqlwBVjS1ROLfxw4=
=5HiC
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Version: 2.6.23-1

fixed upstream, thus closing, thanks.

-- 
maks

--- End Message ---
Reply to: