* IDE kernel traces in 2.6.9 - Bad IRQ ?
@ 2004-10-30 23:21 Phil Dibowitz
2004-10-31 11:01 ` Phil Dibowitz
0 siblings, 1 reply; 6+ messages in thread
From: Phil Dibowitz @ 2004-10-30 23:21 UTC (permalink / raw)
To: linux-ide
[-- Attachment #1: Type: text/plain, Size: 15659 bytes --]
I just upgraded my computer, compiled a new kernel appropriately, and
I'm getting a ton of kernel issues surrounding the IDE driver. I tried a
generic debian kernel as well, but same issue. Here are the tracebacks I
get during boot:
Oct 30 15:56:19 rider kernel: ide0 at 0xefe0-0xefe7,0xefae on irq 5
Oct 30 15:56:19 rider kernel: hda: max request size: 128KiB
Oct 30 15:56:19 rider kernel: [__report_bad_irq+42/139]
__report_bad_irq+0x2a/0x8b
Oct 30 15:56:19 rider kernel: [note_interrupt+111/159]
note_interrupt+0x6f/0x9f
Oct 30 15:56:19 rider kernel: [do_IRQ+295/310] do_IRQ+0x127/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [__do_softirq+47/135] __do_softirq+0x2f/0x87
Oct 30 15:56:19 rider kernel: [do_softirq+38/40] do_softirq+0x26/0x28
Oct 30 15:56:19 rider kernel: [do_IRQ+259/310] do_IRQ+0x103/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [mwait_idle+48/70] mwait_idle+0x30/0x46
Oct 30 15:56:19 rider kernel: [cpu_idle+55/80] cpu_idle+0x37/0x50
Oct 30 15:56:19 rider kernel: [start_kernel+343/368]
start_kernel+0x157/0x170
Oct 30 15:56:19 rider kernel: [unknown_bootoption+0/348]
unknown_bootoption+0x0/0x15c
Oct 30 15:56:19 rider kernel: hda: 30015216 sectors (15367 MB) w/2048KiB
Cache, CHS=29777/16/63, UDMA(100)
Oct 30 15:56:19 rider kernel: hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
Oct 30 15:56:19 rider kernel: hdb: max request size: 128KiB
Oct 30 15:56:19 rider kernel: [__report_bad_irq+42/139]
__report_bad_irq+0x2a/0x8b
Oct 30 15:56:19 rider kernel: [note_interrupt+111/159]
note_interrupt+0x6f/0x9f
Oct 30 15:56:19 rider kernel: [do_IRQ+295/310] do_IRQ+0x127/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [__do_softirq+47/135] __do_softirq+0x2f/0x87
Oct 30 15:56:19 rider kernel: [do_softirq+38/40] do_softirq+0x26/0x28
Oct 30 15:56:19 rider kernel: [do_IRQ+259/310] do_IRQ+0x103/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [mwait_idle+48/70] mwait_idle+0x30/0x46
Oct 30 15:56:19 rider kernel: [cpu_idle+55/80] cpu_idle+0x37/0x50
Oct 30 15:56:19 rider kernel: [start_kernel+343/368]
start_kernel+0x157/0x170
Oct 30 15:56:19 rider kernel: [unknown_bootoption+0/348]
unknown_bootoption+0x0/0x15c
Oct 30 15:56:19 rider kernel: hdb: 240121728 sectors (122942 MB)
w/7936KiB Cache, CHS=65535/16/63, UDMA(100)
Oct 30 15:56:19 rider kernel: [__report_bad_irq+42/139]
__report_bad_irq+0x2a/0x8b
Oct 30 15:56:19 rider kernel: [note_interrupt+111/159]
note_interrupt+0x6f/0x9f
Oct 30 15:56:19 rider kernel: [do_IRQ+295/310] do_IRQ+0x127/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [__do_softirq+47/135] __do_softirq+0x2f/0x87
Oct 30 15:56:19 rider kernel: [do_softirq+38/40] do_softirq+0x26/0x28
Oct 30 15:56:19 rider kernel: [do_IRQ+259/310] do_IRQ+0x103/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [ide_do_drive_cmd+213/312]
ide_do_drive_cmd+0xd5/0x138
Oct 30 15:56:19 rider kernel: [ide_diag_taskfile+161/228]
ide_diag_taskfile+0xa1/0xe4
Oct 30 15:56:19 rider kernel: [ide_raw_taskfile+39/43]
ide_raw_taskfile+0x27/0x2b
Oct 30 15:56:19 rider kernel: [write_cache+113/146] write_cache+0x71/0x92
Oct 30 15:56:19 rider kernel: [task_no_data_intr+0/149]
task_no_data_intr+0x0/0x95
Oct 30 15:56:19 rider kernel: [idedisk_setup+907/1270]
idedisk_setup+0x38b/0x4f6
Oct 30 15:56:19 rider kernel: [idedisk_attach+152/342]
idedisk_attach+0x98/0x156
Oct 30 15:56:19 rider kernel: [ata_attach+219/418] ata_attach+0xdb/0x1a2
Oct 30 15:56:19 rider kernel: [ide_register_driver+261/280]
ide_register_driver+0x105/0x118
Oct 30 15:56:19 rider kernel: [idedisk_init+15/22] idedisk_init+0xf/0x16
Oct 30 15:56:19 rider kernel: [do_initcalls+39/179] do_initcalls+0x27/0xb3
Oct 30 15:56:19 rider kernel: [sock_init+63/72] sock_init+0x3f/0x48
Oct 30 15:56:19 rider kernel: [init+0/341] init+0x0/0x155
Oct 30 15:56:19 rider kernel: [init+61/341] init+0x3d/0x155
Oct 30 15:56:19 rider kernel: [kernel_thread_helper+0/11]
kernel_thread_helper+0x0/0xb
Oct 30 15:56:19 rider kernel: [kernel_thread_helper+5/11]
kernel_thread_helper+0x5/0xb
Oct 30 15:56:19 rider kernel: hdb: hdb1
Oct 30 15:56:19 rider kernel: [__report_bad_irq+42/139]
__report_bad_irq+0x2a/0x8b
Oct 30 15:56:19 rider kernel: [note_interrupt+111/159]
note_interrupt+0x6f/0x9f
Oct 30 15:56:19 rider kernel: [do_IRQ+295/310] do_IRQ+0x127/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [__do_softirq+47/135] __do_softirq+0x2f/0x87
Oct 30 15:56:19 rider kernel: [do_softirq+38/40] do_softirq+0x26/0x28
Oct 30 15:56:19 rider kernel: [do_IRQ+259/310] do_IRQ+0x103/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [mwait_idle+48/70] mwait_idle+0x30/0x46
Oct 30 15:56:19 rider kernel: [cpu_idle+55/80] cpu_idle+0x37/0x50
Oct 30 15:56:19 rider kernel: [start_kernel+343/368]
start_kernel+0x157/0x170
Oct 30 15:56:19 rider kernel: [unknown_bootoption+0/348]
unknown_bootoption+0x0/0x15c
....(other non-related boot messages, then)....
Oct 30 15:56:19 rider kernel: Freeing unused kernel memory: 116k freed
Oct 30 15:56:19 rider kernel: [__report_bad_irq+42/139]
__report_bad_irq+0x2a/0x8b
Oct 30 15:56:19 rider kernel: [note_interrupt+111/159]
note_interrupt+0x6f/0x9f
Oct 30 15:56:19 rider kernel: [do_IRQ+295/310] do_IRQ+0x127/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [__do_softirq+47/135] __do_softirq+0x2f/0x87
Oct 30 15:56:19 rider kernel: [do_softirq+38/40] do_softirq+0x26/0x28
Oct 30 15:56:19 rider kernel: [do_IRQ+259/310] do_IRQ+0x103/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [mwait_idle+48/70] mwait_idle+0x30/0x46
Oct 30 15:56:19 rider kernel: [cpu_idle+55/80] cpu_idle+0x37/0x50
Oct 30 15:56:19 rider kernel: [start_kernel+343/368]
start_kernel+0x157/0x170
Oct 30 15:56:19 rider kernel: [unknown_bootoption+0/348]
unknown_bootoption+0x0/0x15
c
Oct 30 15:56:19 rider kernel: [__report_bad_irq+42/139]
__report_bad_irq+0x2a/0x8b
Oct 30 15:56:19 rider kernel: [note_interrupt+111/159]
note_interrupt+0x6f/0x9f
Oct 30 15:56:19 rider kernel: [do_IRQ+295/310] do_IRQ+0x127/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [__do_softirq+47/135] __do_softirq+0x2f/0x87
Oct 30 15:56:19 rider kernel: [do_softirq+38/40] do_softirq+0x26/0x28
Oct 30 15:56:19 rider kernel: [do_IRQ+259/310] do_IRQ+0x103/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [enable_irq+64/197] enable_irq+0x40/0xc5
Oct 30 15:56:19 rider kernel: [SELECT_DRIVE+47/69] SELECT_DRIVE+0x2f/0x45
Oct 30 15:56:19 rider kernel: [ide_config_drive_speed+331/857]
ide_config_drive_spee
d+0x14b/0x359
Oct 30 15:56:19 rider kernel: [piix_tune_chipset+559/961]
piix_tune_chipset+0x22f/0x
3c1
Oct 30 15:56:19 rider kernel: [piix_config_drive_for_dma+120/159]
piix_config_drive_
for_dma+0x78/0x9f
Oct 30 15:56:19 rider kernel: [piix_config_drive_xfer_rate+157/172]
piix_config_driv
e_xfer_rate+0x9d/0xac
Oct 30 15:56:19 rider kernel: [set_using_dma+54/113]
set_using_dma+0x36/0x71
Oct 30 15:56:19 rider kernel: [ide_write_setting+110/241]
ide_write_setting+0x6e/0xf
1
Oct 30 15:56:19 rider kernel: [generic_ide_ioctl+194/1734]
generic_ide_ioctl+0xc2/0x
6c6
Oct 30 15:56:19 rider kernel: [do_page_fault+923/1437]
do_page_fault+0x39b/0x59d
Oct 30 15:56:19 rider kernel: [dentry_open+265/546] dentry_open+0x109/0x222
Oct 30 15:56:19 rider kernel: [filp_open+98/100] filp_open+0x62/0x64
Oct 30 15:56:19 rider kernel: [idedisk_ioctl+0/27] idedisk_ioctl+0x0/0x1b
Oct 30 15:56:19 rider kernel: [blkdev_ioctl+134/1051]
blkdev_ioctl+0x86/0x41b
Oct 30 15:56:19 rider kernel: [block_ioctl+0/21] block_ioctl+0x0/0x15
Oct 30 15:56:19 rider kernel: [sys_ioctl+247/588] sys_ioctl+0xf7/0x24c
Oct 30 15:56:19 rider kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Oct 30 15:56:19 rider kernel: [__report_bad_irq+42/139]
__report_bad_irq+0x2a/0x8b
Oct 30 15:56:19 rider kernel: [note_interrupt+111/159]
note_interrupt+0x6f/0x9f
Oct 30 15:56:19 rider kernel: [do_IRQ+295/310] do_IRQ+0x127/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [__do_softirq+47/135] __do_softirq+0x2f/0x87
Oct 30 15:56:19 rider kernel: [do_softirq+38/40] do_softirq+0x26/0x28
Oct 30 15:56:19 rider kernel: [do_IRQ+259/310] do_IRQ+0x103/0x136
Oct 30 15:56:19 rider kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct 30 15:56:19 rider kernel: [mwait_idle+48/70] mwait_idle+0x30/0x46
Oct 30 15:56:19 rider kernel: [cpu_idle+55/80] cpu_idle+0x37/0x50
Oct 30 15:56:19 rider kernel: [start_kernel+343/368]
start_kernel+0x157/0x170
Oct 30 15:56:19 rider kernel: [unknown_bootoption+0/348]
unknown_bootoption+0x0/0x15c
Here's an lspci -v:
[phil@rider ~]$ sudo lspci -v
0000:00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM
Controller/Host-Hub Interface (rev 02)
Subsystem: Asustek Computer, Inc. P4P800 Mainboard
Flags: bus master, fast devsel, latency 0
Memory at e0000000 (32-bit, prefetchable) [size=256M]
Capabilities: [e4] #09 [2106]
Capabilities: [a0] AGP version 3.0
0000:00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller
(rev 02) (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, fast devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
Memory behind bridge: fc900000-fe9fffff
Prefetchable memory behind bridge: bff00000-dfefffff
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
UHCI #1 (rev 02) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc. P4P800 Mainboard
Flags: bus master, medium devsel, latency 0, IRQ 10
I/O ports at ef00 [size=32]
0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
UHCI #2 (rev 02) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc. P4P800 Mainboard
Flags: bus master, medium devsel, latency 0, IRQ 5
I/O ports at ef20 [size=32]
0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
UHCI #3 (rev 02) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc. P4P800 Mainboard
Flags: bus master, medium devsel, latency 0, IRQ 5
I/O ports at ef40 [size=32]
0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
UHCI #4 (rev 02) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc. P4P800 Mainboard
Flags: bus master, medium devsel, latency 0, IRQ 10
I/O ports at ef80 [size=32]
0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2
EHCI Controller (rev 02) (prog-if 20 [EHCI])
Subsystem: Asustek Computer, Inc. P4P800 Mainboard
Flags: bus master, medium devsel, latency 0, IRQ 11
Memory at febffc00 (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 c2) (prog-if
00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fea00000-feafffff
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge
(rev 02)
Flags: bus master, medium devsel, latency 0
0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra
ATA 100 Storage Controller (rev 02) (prog-if 8f [Master SecP SecO PriP
PriO])
Subsystem: Asustek Computer, Inc. P4P800 Mainboard
Flags: bus master, medium devsel, latency 0, IRQ 5
I/O ports at efe0 [size=8]
I/O ports at efac [size=4]
I/O ports at efa0 [size=8]
I/O ports at efa8 [size=4]
I/O ports at ef60 [size=16]
Memory at 40000000 (32-bit, non-prefetchable) [size=1K]
0000:00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller
(rev 02)
Subsystem: Asustek Computer, Inc. P4P800 Mainboard
Flags: medium devsel, IRQ 5
I/O ports at 0400 [size=32]
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER
(ICH5/ICH5R) AC'97 Audio Controller (rev 02)
Subsystem: Asustek Computer, Inc.: Unknown device 812a
Flags: bus master, medium devsel, latency 0, IRQ 5
I/O ports at e800 [size=256]
I/O ports at ee80 [size=64]
Memory at febff800 (32-bit, non-prefetchable) [size=512]
Memory at febff400 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
0000:01:00.0 VGA compatible controller: nVidia Corporation NV 36
[GeForce 5700] (rev a1) (prog-if 00 [VGA])
Subsystem: Asustek Computer, Inc.: Unknown device 814f
Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 10
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (32-bit, prefetchable) [size=256M]
Expansion ROM at fe9e0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 3.0
0000:02:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 80) (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 808a
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at feaff800 (32-bit, non-prefetchable) [size=2K]
I/O ports at dc00 [size=128]
Capabilities: [50] Power Management version 2
0000:02:05.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 11
Memory at feaf8000 (32-bit, non-prefetchable) [size=16K]
I/O ports at d800 [size=256]
Expansion ROM at feaa0000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
[phil@rider ~]$
uname:
[phil@rider ~]$ uname -a
Linux rider 2.6.9rider #1 Sun Oct 31 04:10:25 PST 2004 i686 GNU/Linux
[phil@rider ~]$
I have an Asus P4P800-E Delux motherboard, with a Pentium 4 3.0G E, I
have two PATA hard drives connected to hda and hdb -- if I connect my
CDROMs on hdc and hdd I get so many of the above errors I can't even
boot -- but with just the two harddrives I get the errors exactly as above.
If there's any additional information I can provide, please let me know.
Also, I'm not on the linux-ide list, so please CC me on replies.
Thanks.
--
Phil Dibowitz phil@ipom.com
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: IDE kernel traces in 2.6.9 - Bad IRQ ?
2004-10-30 23:21 IDE kernel traces in 2.6.9 - Bad IRQ ? Phil Dibowitz
@ 2004-10-31 11:01 ` Phil Dibowitz
2004-10-31 11:13 ` Jeff Garzik
0 siblings, 1 reply; 6+ messages in thread
From: Phil Dibowitz @ 2004-10-31 11:01 UTC (permalink / raw)
To: linux-ide
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Phil Dibowitz wrote:
> I just upgraded my computer, compiled a new kernel appropriately, and
> I'm getting a ton of kernel issues surrounding the IDE driver. I tried a
> generic debian kernel as well, but same issue. Here are the tracebacks I
> get during boot:
>
> Oct 30 15:56:19 rider kernel: ide0 at 0xefe0-0xefe7,0xefae on irq 5
> Oct 30 15:56:19 rider kernel: hda: max request size: 128KiB
So, it turns out if I change the IDE Configuration in my BIOS to be
"Compatible mode" instead of "Enhanced Mode", this is fixed completely.
All my drives work flawelessly.
Any idea what, if any, features I'm missing, or how to make linux work
with "enhanced mode" ?
--
Phil Dibowitz phil@ipom.com
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: IDE kernel traces in 2.6.9 - Bad IRQ ?
2004-10-31 11:01 ` Phil Dibowitz
@ 2004-10-31 11:13 ` Jeff Garzik
2004-10-31 19:14 ` Phil Dibowitz
0 siblings, 1 reply; 6+ messages in thread
From: Jeff Garzik @ 2004-10-31 11:13 UTC (permalink / raw)
To: Phil Dibowitz; +Cc: linux-ide
Phil Dibowitz wrote:
> Phil Dibowitz wrote:
>
>> I just upgraded my computer, compiled a new kernel appropriately, and
>> I'm getting a ton of kernel issues surrounding the IDE driver. I tried
>> a generic debian kernel as well, but same issue. Here are the
>> tracebacks I get during boot:
>>
>> Oct 30 15:56:19 rider kernel: ide0 at 0xefe0-0xefe7,0xefae on irq 5
>> Oct 30 15:56:19 rider kernel: hda: max request size: 128KiB
>
>
> So, it turns out if I change the IDE Configuration in my BIOS to be
> "Compatible mode" instead of "Enhanced Mode", this is fixed completely.
> All my drives work flawelessly.
>
> Any idea what, if any, features I'm missing, or how to make linux work
> with "enhanced mode" ?
Sounds like you're not using CONFIG_SCSI_SATA for your SATA?
Jeff
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: IDE kernel traces in 2.6.9 - Bad IRQ ?
2004-10-31 11:13 ` Jeff Garzik
@ 2004-10-31 19:14 ` Phil Dibowitz
2004-11-01 14:28 ` Ericisko
0 siblings, 1 reply; 6+ messages in thread
From: Phil Dibowitz @ 2004-10-31 19:14 UTC (permalink / raw)
To: Jeff Garzik; +Cc: linux-ide
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
Jeff Garzik wrote:
> Phil Dibowitz wrote:
>
>> Phil Dibowitz wrote:
>>
>>> I just upgraded my computer, compiled a new kernel appropriately, and
>>> I'm getting a ton of kernel issues surrounding the IDE driver. I
>>> tried a generic debian kernel as well, but same issue. Here are the
>>> tracebacks I get during boot:
>>>
>>> Oct 30 15:56:19 rider kernel: ide0 at 0xefe0-0xefe7,0xefae on irq 5
>>> Oct 30 15:56:19 rider kernel: hda: max request size: 128KiB
>>
>>
>>
>> So, it turns out if I change the IDE Configuration in my BIOS to be
>> "Compatible mode" instead of "Enhanced Mode", this is fixed
>> completely. All my drives work flawelessly.
>>
>> Any idea what, if any, features I'm missing, or how to make linux work
>> with "enhanced mode" ?
>
>
>
> Sounds like you're not using CONFIG_SCSI_SATA for your SATA?
Erm. That's possible -- I have an SATA controller on the new board, but
I don't have any SATA drives, so I didn't compile the promise driver or
anything else for SATA...
Thanks, I'll look into that.
--
Phil Dibowitz phil@ipom.com
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: IDE kernel traces in 2.6.9 - Bad IRQ ?
2004-10-31 19:14 ` Phil Dibowitz
@ 2004-11-01 14:28 ` Ericisko
2004-11-01 17:46 ` Phil Dibowitz
0 siblings, 1 reply; 6+ messages in thread
From: Ericisko @ 2004-11-01 14:28 UTC (permalink / raw)
To: Phil Dibowitz, Jeff Garzik; +Cc: linux-ide
Hi,
I have similar problem. I have MSI Neo2-FIS2R board
with 865PE chipset. I have 1 PATA hard drive connected
to ICH5, IDE channel 1 and DVD and CD-RW connected to
IDE channel 2. I use IDE driver piix, not libata. When
IDE is in legacy mode (BIOS setup), everything works
fine - each channel has its own IRQ. When I change
mode to native, I get the message "Disabling IRQ" with
trace stack showing 2 ide_intr handlers for IRQ (1 for
each channel?) and both channels share the same IRQ.
It looks like interrupt is not handled and it's level
triggered so /proc/interrupts shows huge number of
interrupts and soon IRQ is disabled.
If ide-cd is compiled as module, everything works fine
unless I load ide-cd module. Than I get the same
errors.
As that particular interrupt was shared also by USB
and eth0, I built the minimal kernel so ide0 and ide1
were the only devices using the interrupt - the same
problem.
I'm not at my computer right now so I can't send any
additional info at the moment.
Erik
--- Phil Dibowitz <phil@ipom.com> wrote:
> Jeff Garzik wrote:
> > Phil Dibowitz wrote:
> >
> >> Phil Dibowitz wrote:
> >>
> >>> I just upgraded my computer, compiled a new
> kernel appropriately, and
> >>> I'm getting a ton of kernel issues surrounding
> the IDE driver. I
> >>> tried a generic debian kernel as well, but same
> issue. Here are the
> >>> tracebacks I get during boot:
> >>>
> >>> Oct 30 15:56:19 rider kernel: ide0 at
> 0xefe0-0xefe7,0xefae on irq 5
> >>> Oct 30 15:56:19 rider kernel: hda: max request
> size: 128KiB
> >>
> >>
> >>
> >> So, it turns out if I change the IDE
> Configuration in my BIOS to be
> >> "Compatible mode" instead of "Enhanced Mode",
> this is fixed
> >> completely. All my drives work flawelessly.
> >>
> >> Any idea what, if any, features I'm missing, or
> how to make linux work
> >> with "enhanced mode" ?
> >
> >
> >
> > Sounds like you're not using CONFIG_SCSI_SATA for
> your SATA?
>
> Erm. That's possible -- I have an SATA controller on
> the new board, but
> I don't have any SATA drives, so I didn't compile
> the promise driver or
> anything else for SATA...
>
> Thanks, I'll look into that.
>
>
> --
> Phil Dibowitz
> phil@ipom.com
> Freeware and Technical Pages Insanity
> Palace of Metallica
> http://www.phildev.net/
> http://www.ipom.com/
>
> "They that can give up essential liberty to obtain a
> little temporary
> safety deserve neither liberty nor safety."
> - Benjamin Franklin, 1759
>
>
> ATTACHMENT part 2 application/pgp-signature
name=signature.asc
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: IDE kernel traces in 2.6.9 - Bad IRQ ?
2004-11-01 14:28 ` Ericisko
@ 2004-11-01 17:46 ` Phil Dibowitz
0 siblings, 0 replies; 6+ messages in thread
From: Phil Dibowitz @ 2004-11-01 17:46 UTC (permalink / raw)
To: Ericisko; +Cc: Jeff Garzik, linux-ide
[-- Attachment #1: Type: text/plain, Size: 3060 bytes --]
Ericisko wrote:
> Hi,
>
> I have similar problem. I have MSI Neo2-FIS2R board
> with 865PE chipset. I have 1 PATA hard drive connected
> to ICH5, IDE channel 1 and DVD and CD-RW connected to
> IDE channel 2. I use IDE driver piix, not libata. When
> IDE is in legacy mode (BIOS setup), everything works
> fine - each channel has its own IRQ. When I change
> mode to native, I get the message "Disabling IRQ" with
> trace stack showing 2 ide_intr handlers for IRQ (1 for
> each channel?) and both channels share the same IRQ.
> It looks like interrupt is not handled and it's level
> triggered so /proc/interrupts shows huge number of
> interrupts and soon IRQ is disabled.
> If ide-cd is compiled as module, everything works fine
> unless I load ide-cd module. Than I get the same
> errors.
> As that particular interrupt was shared also by USB
> and eth0, I built the minimal kernel so ide0 and ide1
> were the only devices using the interrupt - the same
> problem.
> I'm not at my computer right now so I can't send any
> additional info at the moment.
So I played with this a little more. And I think I understand better.
With this BIOS there's a few possible combinations:
Enhanced: S-ATA
P-ATA+S-ATA
P-ATA
or
Compatability: Primary P-ATA+S-ATA
Secondary P-ATA+S-ATA
P-ATA Only
Basically, there are way more ATA chains on this mobo than others. Yuo
have your SATA controller (1 chain, 2 drives), your PATA controller (2
chains, 4 drives), and your RAID PATA controller (1 chain, 2 drives).
So here's what happens:
- I chose Enhanced P-ATA+S-ATA which meant that SATA drives came first,
then PATA. This caused the kernel some confusion... not exactly sure
why, but something to the effect of /dev/hda was first, but wasn't first
(that chainw as listed as the 2nd chain in bios with nothing on the
first). This causes traces
- I was able to fix it with Compatibilty P-ATA only which puts things in
the right order
- I was *also* able to fix it, it turns out, with Enhanced S-ATA. Now
that seems counter intuitive until you break down and read the manual
that comes with the board. This basically says "if you have SATA, we
ignore all PATA and just use SATA. If you don't have SATA, we ignore all
SATA and just use PATA" -- that thus puts things in the right order
since I don't have any SATA at this time.
Ther other compatiblity modes mix which Primaries you want to use and
which you want to throw away and replace with SATA. The other enhances
modes are exactly what they say.
So that's some more information based on expiramentation, reading the
fine manual, and a bit of speculating... doesn't solve everything, but I
hope it helps.
--
Phil Dibowitz phil@ipom.com
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-11-01 17:46 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-30 23:21 IDE kernel traces in 2.6.9 - Bad IRQ ? Phil Dibowitz
2004-10-31 11:01 ` Phil Dibowitz
2004-10-31 11:13 ` Jeff Garzik
2004-10-31 19:14 ` Phil Dibowitz
2004-11-01 14:28 ` Ericisko
2004-11-01 17:46 ` Phil Dibowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).