acpi gets wrong interrupt for via sata in 2.6.16.17
Hello, this is my first time posting here.
The short: something that came in 2.6.16.17 has caused my sata to no longer work correctly (by work correctly, I mean actually be able to detect any drives). I'm no expert, but it seems that it is getting the wrong interrupt. In 2.6.16.16 it works fine with the exact same config.
It also works fine if I append 'pci=noacpi'. This has still happens in
2.6.17.
Here is the output of lspci:
scott@amdg:~$ /sbin/lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:07.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705 Gigabit Ethernet (rev 03) 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) 00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 01:00.0 VGA compatible controller: nVidia Corporation NV15DDR [GeForce2 Ti] (rev a4)
I can also attach my .config if needed.
Thanks,
Scott.
Signature · 2 lines
"Computer Science is no more about computers than astronomy is about telescopes." - Edsger Dijkstra
Quoted 6 lines · On Sat, 24 Jun 2006 20:28:26 -0500 Scott J. Harmon wrote:
The short: something that came in 2.6.16.17 has caused my sata to no longer work correctly (by work correctly, I mean actually be able to detect any drives). I'm no expert, but it seems that it is getting the wrong interrupt. In 2.6.16.16 it works fine with the exact same config.
It also works fine if I append 'pci=noacpi'. This has still happens in
2.6.17.
I assume that your root filesystem is on a SATA disk, and therefore you don't have an easy way to extract dmesg from a broken kernel?
Quoted 20 lines
Here is the output of lspci:
scott@amdg:~$ /sbin/lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:07.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705 Gigabit Ethernet (rev 03) 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) 00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Quoted 8 lines
Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 01:00.0 VGA compatible controller: nVidia Corporation NV15DDR [GeForce2 Ti] (rev a4)
Try to revert these patches:
(revert in the above order - these are two patches which depend on each other, you need to revert both). You can try it both with 2.6.16.17 and 2.6.17.
Chris: seems that the SATA subdevice (1106:3149) also needs the quirk, like EHCI, sound and builtin network.
Quoted 9 lines · Sergey Vlasov
Quoted 6 lines · On Sat, 24 Jun 2006 20:28:26 -0500 Scott J. Harmon wrote:
The short: something that came in 2.6.16.17 has caused my sata to no longer work correctly (by work correctly, I mean actually be able to detect any drives). I'm no expert, but it seems that it is getting the wrong interrupt. In 2.6.16.16 it works fine with the exact same config.
It also works fine if I append 'pci=noacpi'. This has still happens in
2.6.17.
Quoted 3 lines
I assume that your root filesystem is on a SATA disk, and therefore you don't have an easy way to extract dmesg from a broken kernel?
Exactly :)
Quoted 33 lines
Quoted 20 lines
Here is the output of lspci:
scott@amdg:~$ /sbin/lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:07.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705 Gigabit Ethernet (rev 03) 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) 00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Quoted 8 lines
Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 01:00.0 VGA compatible controller: nVidia Corporation NV15DDR [GeForce2 Ti] (rev a4)Try to revert these patches:
Quoted 8 lines
(revert in the above order - these are two patches which depend on each other, you need to revert both). You can try it both with 2.6.16.17 and 2.6.17.
Chris: seems that the SATA subdevice (1106:3149) also needs the quirk, like EHCI, sound and builtin network.
Will do, and will report back.
Thanks,
Scott.
Signature · 2 lines
"Computer Science is no more about computers than astronomy is about telescopes." - Edsger Dijkstra
Quoted 43 lines · Sergey Vlasov
Quoted 6 lines · On Sat, 24 Jun 2006 20:28:26 -0500 Scott J. Harmon wrote:
The short: something that came in 2.6.16.17 has caused my sata to no longer work correctly (by work correctly, I mean actually be able to detect any drives). I'm no expert, but it seems that it is getting the wrong interrupt. In 2.6.16.16 it works fine with the exact same config.
It also works fine if I append 'pci=noacpi'. This has still happens in
2.6.17.I assume that your root filesystem is on a SATA disk, and therefore you don't have an easy way to extract dmesg from a broken kernel?
Quoted 20 lines
Here is the output of lspci:
scott@amdg:~$ /sbin/lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:07.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705 Gigabit Ethernet (rev 03) 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) 00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Quoted 8 lines
Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 01:00.0 VGA compatible controller: nVidia Corporation NV15DDR [GeForce2 Ti] (rev a4)Try to revert these patches:
Quoted 7 lines
(revert in the above order - these are two patches which depend on each other, you need to revert both). You can try it both with 2.6.16.17 and 2.6.17.
Ok, reverting these two patches caused ACPI to function again here. Let me know if there is anything else you need from me to get this fixed in mainline.
Quoted 3 lines
Chris: seems that the SATA subdevice (1106:3149) also needs the quirk, like EHCI, sound and builtin network.
Thanks,
Scott.
Signature · 2 lines
"Computer Science is no more about computers than astronomy is about telescopes." - Edsger Dijkstra
Quoted 55 lines · Scott J. Harmon
Quoted 41 lines · Sergey Vlasov
Quoted 6 lines · On Sat, 24 Jun 2006 20:28:26 -0500 Scott J. Harmon wrote:
The short: something that came in 2.6.16.17 has caused my sata to no longer work correctly (by work correctly, I mean actually be able to detect any drives). I'm no expert, but it seems that it is getting the wrong interrupt. In 2.6.16.16 it works fine with the exact same config.
It also works fine if I append 'pci=noacpi'. This has still happens in
2.6.17.I assume that your root filesystem is on a SATA disk, and therefore you don't have an easy way to extract dmesg from a broken kernel?
Quoted 20 lines
Here is the output of lspci:
scott@amdg:~$ /sbin/lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:07.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705 Gigabit Ethernet (rev 03) 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) 00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Quoted 8 lines
Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 01:00.0 VGA compatible controller: nVidia Corporation NV15DDR [GeForce2 Ti] (rev a4)Try to revert these patches:
Quoted 7 lines
(revert in the above order - these are two patches which depend on each other, you need to revert both). You can try it both with 2.6.16.17 and 2.6.17.
Ok, reverting these two patches caused ACPI to function again here. Let me know if there is anything else you need from me to get this fixed in mainline.
Quoted 6 lines
Quoted 2 lines
Chris: seems that the SATA subdevice (1106:3149) also needs the quirk, like EHCI, sound and builtin network.
Thanks,
Scott.
Is this going to be merged into 2.6.16.x and 2.6.17.x?
Thanks,
Scott.
Signature · 2 lines
"Computer Science is no more about computers than astronomy is about telescopes." - Edsger Dijkstra
Quoted 56 lines · On Thu, 06 Jul 2006 19:30:23 -0500 "Scott J. Harmon" <[email protected]> wrote:
Quoted 55 lines · Scott J. Harmon
Quoted 41 lines · Sergey Vlasov
Quoted 6 lines · On Sat, 24 Jun 2006 20:28:26 -0500 Scott J. Harmon wrote:
The short: something that came in 2.6.16.17 has caused my sata to no longer work correctly (by work correctly, I mean actually be able to detect any drives). I'm no expert, but it seems that it is getting the wrong interrupt. In 2.6.16.16 it works fine with the exact same config.
It also works fine if I append 'pci=noacpi'. This has still happens in
2.6.17.I assume that your root filesystem is on a SATA disk, and therefore you don't have an easy way to extract dmesg from a broken kernel?
Quoted 20 lines
Here is the output of lspci:
scott@amdg:~$ /sbin/lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:07.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705 Gigabit Ethernet (rev 03) 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) 00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Quoted 8 lines
Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 01:00.0 VGA compatible controller: nVidia Corporation NV15DDR [GeForce2 Ti] (rev a4)Try to revert these patches:
Quoted 7 lines
(revert in the above order - these are two patches which depend on each other, you need to revert both). You can try it both with 2.6.16.17 and 2.6.17.
Ok, reverting these two patches caused ACPI to function again here. Let me know if there is anything else you need from me to get this fixed in mainline.
Quoted 9 lines
Quoted 6 lines
Quoted 2 lines
Chris: seems that the SATA subdevice (1106:3149) also needs the quirk, like EHCI, sound and builtin network.
Thanks,
Scott.
Is this going to be merged into 2.6.16.x and 2.6.17.x?
I have both reversion patches queued up but haven't heard from anyone about anything. I don't know if anyone's working on this bug.
Thursday is my subsystem-maintainer-spamming day, so the reverts will be heading Gregwards today.
Quoted 2 lines · Andrew Morton
I have both reversion patches queued up but haven't heard from anyone about anything.
i saw that --- i don't think it's right, but it's not more wrong than having that merged as-is in the first place which i'll argue is wrong by virtue of the fact we run the quirk everywhere and apparently break things
Quoted 1 line
I don't know if anyone's working on this bug.
it's not forgotten, i'm waiting to hear back from people still. enabling ACPI *should* suffice, but for some people clearly it doesn't (there are claims VIA got their ACPI wrong so this might explain why it works for some people and not others)
Quoted 2 lines
Thursday is my subsystem-maintainer-spamming day, so the reverts will be heading Gregwards today.
like i said, i really don't think reverting the patches is technically correct, but given that i don't have adequate hardware to test against it might be the least painful option right now
Quoted 17 lines · On Thu, 6 Jul 2006 20:47:35 -0700 Chris Wedgwood <[email protected]> wrote:
Quoted 2 lines · Andrew Morton
I have both reversion patches queued up but haven't heard from anyone about anything.
i saw that --- i don't think it's right, but it's not more wrong than having that merged as-is in the first place which i'll argue is wrong by virtue of the fact we run the quirk everywhere and apparently break things
Quoted 1 line
I don't know if anyone's working on this bug.
it's not forgotten, i'm waiting to hear back from people still. enabling ACPI *should* suffice, but for some people clearly it doesn't (there are claims VIA got their ACPI wrong so this might explain why it works for some people and not others)
Quoted 6 lines
Quoted 2 lines
Thursday is my subsystem-maintainer-spamming day, so the reverts will be heading Gregwards today.
like i said, i really don't think reverting the patches is technically correct, but given that i don't have adequate hardware to test against it might be the least painful option right now
Yes, it's a question of whose machines we choose to break.
It'd be great to get this thing nailed. Do the people who are out testing things need re-asking?
This is _still_ a problem with 2.6.17.11
Thanks,
Scott.
Quoted 33 lines · Andrew Morton
Quoted 15 lines · On Thu, 6 Jul 2006 20:47:35 -0700 Chris Wedgwood <[email protected]> wrote:
Quoted 2 lines · Andrew Morton
I have both reversion patches queued up but haven't heard from anyone about anything.
i saw that --- i don't think it's right, but it's not more wrong than having that merged as-is in the first place which i'll argue is wrong by virtue of the fact we run the quirk everywhere and apparently break things
Quoted 1 line
I don't know if anyone's working on this bug.
it's not forgotten, i'm waiting to hear back from people still. enabling ACPI *should* suffice, but for some people clearly it doesn't (there are claims VIA got their ACPI wrong so this might explain why it works for some people and not others)
Quoted 5 lines
Quoted 2 lines
Thursday is my subsystem-maintainer-spamming day, so the reverts will be heading Gregwards today.
like i said, i really don't think reverting the patches is technically correct, but given that i don't have adequate hardware to test against it might be the least painful option right now
Yes, it's a question of whose machines we choose to break.
It'd be great to get this thing nailed. Do the people who are out testing things need re-asking?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 2 lines
"Computer Science is no more about computers than astronomy is about telescopes." - Edsger Dijkstra
Quoted 2 lines · On Thu, 31 Aug 2006 22:07:48 -0500 "Scott J. Harmon" <[email protected]> wrote:
This is _still_ a problem with 2.6.17.11
We're all dazed and confused by now. It would help if you could re-describe the problem from scratch, thanks