Problem 1:
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 sometimes I get the same message and
linux hangs.
Problem 2:
syslog message "irq 18: nobody cared!" followed by a call trace repeats
while booting and while running linux.
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) and nvidia 6600GT PCIe graphic card.
I'm running a self compiled kernel 2.6.12rc4 but I've had these bugs in
self compiled kernel 2.6.11.8 and default debian kernel
2.6.11-9-em64t-p4-smp too.
The default debian kernel 2.6.8-11-em64t-p4-smp seems to be the only one
where problem 1 does not occur but problem 2 does.
/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
...
I would like to add more informations for you if you say me how I can
help. The problem is not solved in kernel 2.6.12rc5.
Here is my lspci output. Perhaps it is helpfull for you.
# lspci -v
0000:00:00.0 Host bridge: Intel Corp. 915G/P/GV Processor to I/O
Controller (rev 04)
Subsystem: Intel Corp. 915G/P/GV Processor to I/O Controller
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] #09 [2109]
0000:00:01.0 PCI bridge: Intel Corp. 915G/P/GV PCI Express Root Port
(rev 04) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: d0000000-d6ffffff
Prefetchable memory behind bridge: d8000000-dfffffff
Capabilities: [88] #0d [0000]
Capabilities: [80] Power Management version 2
Capabilities: [90] Message Signalled Interrupts: 64bit-
Queue=0/0 Enable+
Capabilities: [a0] #10 [0141]
0000:00:1b.0 0403: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High
Definition Audio Controller (rev 03)
Subsystem: Asustek Computer, Inc.: Unknown device 813d
Flags: bus master, fast devsel, latency 0, IRQ 169
Memory at cfdf4000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
Capabilities: [70] #10 [0091]
0000:00:1c.0 PCI bridge: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family)
PCI Express Port 1 (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Capabilities: [40] #10 [0141]
Capabilities: [80] Message Signalled Interrupts: 64bit-
Queue=0/0 Enable+
Capabilities: [90] #0d [0000]
Capabilities: [a0] Power Management version 2
0000:00:1c.1 PCI bridge: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family)
PCI Express Port 2 (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: cff00000-cfffffff
Capabilities: [40] #10 [0141]
Capabilities: [80] Message Signalled Interrupts: 64bit-
Queue=0/0 Enable+
Capabilities: [90] #0d [0000]
Capabilities: [a0] Power Management version 2
0000:00:1d.0 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #1 (rev 03) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 80a6
Flags: bus master, medium devsel, latency 0, IRQ 50
I/O ports at 4400 [size=32]
0000:00:1d.1 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #2 (rev 03) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 80a6
Flags: bus master, medium devsel, latency 0, IRQ 225
I/O ports at 4800 [size=32]
0000:00:1d.2 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #3 (rev 03) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 80a6
Flags: bus master, medium devsel, latency 0, IRQ 217
I/O ports at 5000 [size=32]
0000:00:1d.3 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #4 (rev 03) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 80a6
Flags: bus master, medium devsel, latency 0, IRQ 169
I/O ports at 5400 [size=32]
0000:00:1d.7 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB2 EHCI Controller (rev 03) (prog-if 20 [EHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 80a6
Flags: bus master, medium devsel, latency 0, IRQ 50
Memory at cfdff800 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] #0a [20a0]
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev d3) (prog-if
01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 00009000-0000bfff
Memory behind bridge: cfe00000-cfefffff
Prefetchable memory behind bridge: 00000000d7f00000-00000000d7f00000
Capabilities: [50] #0d [0000]
0000:00:1f.0 ISA bridge: Intel Corp. 82801FB/FR (ICH6/ICH6R) LPC
Interface Bridge (rev 03)
Flags: bus master, medium devsel, latency 0
0000:00:1f.1 IDE interface: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) IDE Controller (rev 03) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Asustek Computer, Inc.: Unknown device 80a6
Flags: bus master, medium devsel, latency 0, IRQ 217
I/O ports at 7000 [size=8]
I/O ports at 6800 [size=4]
I/O ports at 6400 [size=8]
I/O ports at 6000 [size=4]
I/O ports at 5800 [size=16]
0000:00:1f.2 IDE interface: Intel Corp. 82801FR/FRW (ICH6R/ICH6RW) SATA
Controller (rev 03) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Asustek Computer, Inc.: Unknown device 2601
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 225
I/O ports at 8800 [size=8]
I/O ports at 8400 [size=4]
I/O ports at 8000 [size=8]
I/O ports at 7800 [size=4]
I/O ports at 7400 [size=16]
Memory at cfdffc00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [70] Power Management version 2
0000:00:1f.3 SMBus: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family)
SMBus Controller (rev 03)
Subsystem: Asustek Computer, Inc.: Unknown device 80a6
Flags: medium devsel
I/O ports at 0400 [size=32]
0000:01:03.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b
Link Layer Controller (rev 01) (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 813c
Flags: bus master, medium devsel, latency 64, IRQ 233
Memory at cfefb800 (32-bit, non-prefetchable) [size=2K]
Memory at cfef4000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
0000:01:04.0 Unknown mass storage controller: Integrated Technology
Express, Inc. IT/ITE8212 Dual channel ATA RAID controller (PCI version
seems to be IT8212, embedded seems (rev 13)
Subsystem: Asustek Computer, Inc.: Unknown device 813a
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 5
I/O ports at b000 [size=8]
I/O ports at a800 [size=4]
I/O ports at a400 [size=8]
I/O ports at a000 [size=4]
I/O ports at 9800 [size=16]
Expansion ROM at cfea0000 [disabled] [size=128K]
Capabilities: [80] Power Management version 2
0000:01:06.0 Ethernet controller: Marvell Technology Group Ltd. Yukon
Gigabit Ethernet 10/100/1000Base-T Adapter (rev 13)
Subsystem: Asustek Computer, Inc.: Unknown device 811a
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 169
Memory at cfefc000 (32-bit, non-prefetchable) [size=16K]
I/O ports at b400 [size=256]
Expansion ROM at cfec0000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
0000:01:09.0 Multimedia video controller: Brooktree Corporation Bt878
Video Capture (rev 02)
Subsystem: Hauppauge computer works Inc. WinTV Series
Flags: bus master, medium devsel, latency 64, IRQ 201
Memory at d7ffe000 (32-bit, prefetchable) [size=4K]
0000:01:09.1 Multimedia controller: Brooktree Corporation Bt878 Audio
Capture (rev 02)
Subsystem: Hauppauge computer works Inc. WinTV Series
Flags: bus master, medium devsel, latency 64, IRQ 201
Memory at d7fff000 (32-bit, prefetchable) [size=4K]
0000:01:0a.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 01)
Subsystem: Unknown device 4942:4c4c
Flags: bus master, slow devsel, latency 64, IRQ 233
I/O ports at b800 [size=64]
0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd.: Unknown
device 4362 (rev 15)
Subsystem: Asustek Computer, Inc.: Unknown device 8142
Flags: bus master, fast devsel, latency 0, IRQ 5
Memory at cfffc000 (64-bit, non-prefetchable) [size=16K]
I/O ports at c800 [size=256]
Expansion ROM at cffc0000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [5c] Message Signalled Interrupts: 64bit+
Queue=0/1 Enable-
Capabilities: [e0] #10 [0011]
0000:04:00.0 VGA compatible controller: nVidia Corporation: Unknown
device 0140 (rev a2) (prog-if 00 [VGA])
Flags: bus master, fast devsel, latency 0, IRQ 169
Memory at d0000000 (32-bit, non-prefetchable) [size=64M]
Memory at d8000000 (64-bit, prefetchable) [size=128M]
Memory at d6000000 (64-bit, non-prefetchable) [size=16M]
Expansion ROM at d5fe0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [68] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
Capabilities: [78] #10 [0001]
Alexander Fieroch <[email protected]> wrote:
>
> Problem 1:
> 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 sometimes I get the same message and
> linux hangs.
>
> Problem 2:
> syslog message "irq 18: nobody cared!" followed by a call trace repeats
> while booting and while running linux.
>
> 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) and nvidia 6600GT PCIe graphic card.
> I'm running a self compiled kernel 2.6.12rc4 but I've had these bugs in
> self compiled kernel 2.6.11.8 and default debian kernel
> 2.6.11-9-em64t-p4-smp too.
> The default debian kernel 2.6.8-11-em64t-p4-smp seems to be the only one
> where problem 1 does not occur but problem 2 does.
Does the thing work correctly under any versions of Linux? If so, which?
It appears that you entered cdrom_pc_intr() with IDE_IREASON_REG = 0x01.
* ATAPI Interrupt Reason Register.
*
* cod : Information transferred is command (1) or data (0)
* io : The device requests us to read (1) or write (0)
io = 0
cod = 1
I'm not sure what this means. It generated an interrupt, expecting the
kernel to send a write command? That sounds odd.
If the answer to my first queston is "no" then perhaps the hardware is
busted. Try swapping out cables, check power supplies, try a different
drive, etc.
If none of that helps then perhaps there's something we can do in
cdrom_pc_intr() to work around this?
(Should cdrom_pc_intr() be using atapi_ireason_t?)
Andrew Morton wrote:
> Does the thing work correctly under any versions of Linux? If so, which?
Ok, I have gathered much informations as possible that could help you.
I've tested different versions of linux as follows. None works fine but
all have different error messages:
With kernel 2.6.8.1 and kernel 2.6.9 I get continually apic error
messages that makes the kernel unusable for me:
May 28 13:12:53 orclex kernel: APIC error on CPU0: 60(60)
May 28 13:13:05 orclex last message repeated 44 times
This is repeating every few seconds.
Kernel 2.6.10
-------------
I did not recognize the error message above with apic error but I get
every 2 seconds the following message on my terminal which makes the
kernel unusable for me too.
Call Trace:<IRQ> <ffffffff801505fc>{__report_bad_irq+48}
<ffffffff801506c0>{note_interr
upt+91}
<ffffffff80150080>{__do_IRQ+257} <ffffffff8010ffb8>{do_IRQ+58}
<ffffffff8010d7c9>{ret_from_intr+0} <EOI>
<ffffffff8010b573>{mwait_idle+94}
<ffffffff8010b4ca>{cpu_idle+45} <ffffffff80645882>{start_kernel+415}
<ffffffff80645259>{x86_64_start_kernel+365}
handlers:
[<ffffffff802f33b2>] (ide_intr+0x0/0x17e)
[<ffffffff8033f5e9>] (usb_hcd_irq+0x0/0x68)
Disabling IRQ #185
irq 185: nobody cared!
Kernel 2.6.11.11
----------------
Kernel 2.6.11.xx is the first kernel where the message "drive appears
confused" is thrown.
I also recognize the following lines in syslog where the kernel hangs
for some seconds (nearly a minute) while booting:
May 28 13:47:10 orclex kernel: ACPI: PCI interrupt 0000:01:0a.0[A] ->
GSI 21 (level, lo
w) -> IRQ 21
May 28 13:47:10 orclex kernel: hda: dma_timer_expiry: dma status == 0x64
May 28 13:47:10 orclex kernel: hda: DMA interrupt recovery
May 28 13:47:10 orclex kernel: hda: lost interrupt
I have enabled "ACPI APIC" in my bios. Disabling this causes the kernel
to hang on the last message above and repeating "hda: lost interrupt"
continually.
The "nobody cared" message is still here.
...
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
irq 18: nobody cared!
Call Trace:<IRQ> <ffffffff80150064>{__report_bad_irq+48}
<ffffffff80150128>{note_interrupt+91}
<ffffffff8014fae3>{__do_IRQ+257} <ffffffff80110105>{do_IRQ+71}
<ffffffff8010d83d>{ret_from_intr+0} <EOI>
<ffffffff8015e0a1>{clear_page_range+845}
<ffffffff8015e10a>{clear_page_range+950}
<ffffffff801641bb>{exit_mmap+222}
<ffffffff8012faa8>{mmput+50} <ffffffff80134adc>{do_exit+306}
<ffffffff80134e78>{sys_exit_group+0}
<ffffffff8010d296>{system_call+126}
handlers:
[<ffffffff803021af>] (ide_intr+0x0/0x17a)
[<ffffffff8034e53a>] (usb_hcd_irq+0x0/0x68)
Disabling IRQ #18
hdb: lost interrupt
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
...
After booting this is repeating continually and I get every minute a
message on the console:
Message from syslogd@orclex at Sat May 28 13:33:02 2005 ...
orclex kernel: Disabling IRQ #18
syslog contains following message every minute:
May 28 13:33:01 orclex kernel: hdb: lost interrupt
May 28 13:33:01 orclex kernel: hdb: cdrom_pc_intr: The drive appears
confused (ireason
= 0x01)
May 28 13:33:01 orclex last message repeated 18 times
May 28 13:33:02 orclex kernel: irq 18: nobody cared!
May 28 13:33:02 orclex kernel:
May 28 13:33:02 orclex kernel: Call Trace:<IRQ>
<ffffffff80150064>{__report_bad_irq+48}
<ffffffff80150128>{note_interrupt+91}
May 28 13:33:02 orclex kernel: <ffffffff8014fae3>{__do_IRQ+257}
<ffffffff8011010
5>{do_IRQ+71}
May 28 13:33:02 orclex kernel:
<ffffffff8010d83d>{ret_from_intr+0} <EOI> <fffff
fff8010b588>{mwait_idle+94}
May 28 13:33:02 orclex kernel: <ffffffff8010b50c>{cpu_idle+57}
<ffffffff8065686d
>{start_kernel+425}
May 28 13:33:02 orclex kernel:
<ffffffff80656258>{x86_64_start_kernel+364}
May 28 13:33:02 orclex kernel: handlers:
May 28 13:33:02 orclex kernel: [<ffffffff803021af>] (ide_intr+0x0/0x17a)
May 28 13:33:02 orclex kernel: [<ffffffff8034e53a>] (usb_hcd_irq+0x0/0x68)
May 28 13:33:02 orclex kernel: Disabling IRQ #18
May 28 13:34:03 orclex kernel: hdb: lost interrupt
May 28 13:34:03 orclex kernel: hdb: cdrom_pc_intr: The drive appears
confused (ireason
= 0x01)
May 28 13:34:03 orclex last message repeated 21 times
May 28 13:34:04 orclex kernel: irq 18: nobody cared!
May 28 13:34:04 orclex kernel:
May 28 13:34:04 orclex kernel: Call Trace:<IRQ>
<ffffffff80150064>{__report_bad_irq+48}
<ffffffff80150128>{note_interrupt+91}
May 28 13:34:04 orclex kernel: <ffffffff8014fae3>{__do_IRQ+257}
<ffffffff8011010
5>{do_IRQ+71}
May 28 13:34:04 orclex kernel:
<ffffffff8010d83d>{ret_from_intr+0} <EOI> <fffff
fff8010b588>{mwait_idle+94}
May 28 13:34:04 orclex kernel: <ffffffff8010b50c>{cpu_idle+57}
<ffffffff8065686d
>{start_kernel+425}
May 28 13:34:04 orclex kernel:
<ffffffff80656258>{x86_64_start_kernel+364}
May 28 13:34:04 orclex kernel: handlers:
May 28 13:34:04 orclex kernel: [<ffffffff803021af>] (ide_intr+0x0/0x17a)
May 28 13:34:04 orclex kernel: [<ffffffff8034e53a>] (usb_hcd_irq+0x0/0x68)
May 28 13:34:04 orclex kernel: Disabling IRQ #18
Kernel 2.6.12rc5
----------------
Some more informations like "packet command error: status=0xd0" but
still the same errors like kernel 2.6.11.xx.
May 28 14:04:04 orclex kernel: hda: lost interrupt
May 28 14:04:04 orclex kernel: hdb: cdrom_pc_intr: The drive appears
confused (ireason
= 0x01)
May 28 14:04:04 orclex last message repeated 38 times
May 28 14:04:04 orclex kernel: hdb: packet command error: status=0xd0 {
Busy }
May 28 14:04:04 orclex kernel: ide: failed opcode was: unknown
May 28 14:04:04 orclex kernel: hdb: cdrom_pc_intr: The drive appears
confused (ireason
= 0x01)
May 28 14:04:04 orclex last message repeated 17 times
May 28 14:04:04 orclex kernel: scsi: unknown opcode 0x85
May 28 14:04:05 orclex lpd[4400]: restarted
May 28 14:04:05 orclex hddtemp[4391]: /dev/hda: IC35L060AVV207-0: 38 C
May 28 14:04:05 orclex kernel: irq 217: nobody cared!
May 28 14:04:05 orclex kernel:
May 28 14:04:05 orclex kernel: Call Trace: <IRQ>
<ffffffff80154078>{__report_bad_irq+48
} <ffffffff8015413c>{note_interrupt+91}
May 28 14:04:05 orclex kernel: <ffffffff80153af7>{__do_IRQ+257}
<ffffffff8011049
d>{do_IRQ+67}
May 28 14:04:05 orclex kernel:
<ffffffff8010dded>{ret_from_intr+0} <EOI>
May 28 14:04:05 orclex kernel: handlers:
May 28 14:04:05 orclex kernel: [<ffffffff8030a879>] (ide_intr+0x0/0x17a)
May 28 14:04:05 orclex kernel: [<ffffffff80357a5d>] (usb_hcd_irq+0x0/0x68)
May 28 14:04:05 orclex kernel: Disabling IRQ #217
> If the answer to my first queston is "no" then perhaps the hardware is
> busted. Try swapping out cables, check power supplies, try a different
> drive, etc.
To test the hardware if it is busted I've have installed an ugly redmont
os and I could not recognize any problems. I also have burned a cdrom
with my burner that is hdb on linux and makes the problems. So I think
the hardware can't be busted and there has to be a problem with the
module for the Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE
Controller?
> If none of that helps then perhaps there's something we can do in
> cdrom_pc_intr() to work around this?
That would be very great. I would like to give you any more information
that is needed.
Thanks and regards,
Alexander