sata-vsc broken on SGI Prism
I'm getting this panic when loading sata-vsc on a SGI Prism:
Loading sata_vsc
ACPI: Unable to derive IRQ for device 0001:00:03.0
ACPI: PCI Interrupt 0001:00:03.0[A]: no GSI FRZ XN request short error.
FRZ XN error detail 1A:
Command word: 0x11 Supplemental: 0xff Source node id: 0x0 Source chip id: 0x2 Destination chip id: 0x0 Data error: 0x0 Echo: 0x70 Valid: 0x0 Address: 0x1802000021 FRZ XN error detail 1B: Command word: 0x0 Supplemental: 0x0 Source node id: 0x0 Source chip id: 0x0 Destination chip id: 0x0 Echo: 0x0 Valid: 0x0 Address: 0x0 Fatal ICE HW error Kernel panic - not syncing: hub_eint_handler: Fatal TIO Error
Bisection has identified this patch (together with the follow-up patch to fix the compilation failure):
commit 7cbaa86b937b0b1fab95c159989f6a3c00bbcf78
Author: Dan Wolstenholme <[email protected]> Date: Tue Jan 9 05:59:21 2007 -0500
[libata] sata_vsc: support PCI MSI
Andreas.
Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Quoted 1 line · On Sat, 24 Mar 2007 10:17:24 +0100 Andreas Schwab <[email protected]> wrote:
I'm getting this panic when loading sata-vsc on a SGI Prism:
With what kernel?
Quoted 29 lines
Loading
sata_vsc
ACPI: Unable to derive IRQ for device 0001:00:03.0
ACPI: PCI Interrupt 0001:00:03.0[A]: no GSI FRZ XN request short error.
FRZ XN error detail 1A:Command word: 0x11 Supplemental: 0xff Source node id: 0x0 Source chip id: 0x2 Destination chip id: 0x0 Data error: 0x0 Echo: 0x70 Valid: 0x0 Address: 0x1802000021 FRZ XN error detail 1B: Command word: 0x0 Supplemental: 0x0 Source node id: 0x0 Source chip id: 0x0 Destination chip id: 0x0 Echo: 0x0 Valid: 0x0 Address: 0x0 Fatal ICE HW error Kernel panic - not syncing: hub_eint_handler: Fatal TIO ErrorBisection has identified this patch (together with the follow-up patch to fix the compilation failure):
Quoted 8 lines
commit
7cbaa86b937b0b1fab95c159989f6a3c00bbcf78Author: Dan Wolstenholme <[email protected]> Date: Tue Jan 9 05:59:21 2007 -0500[libata]
sata_vsc: support PCI MSISigned-off-by Jeff Garzik <[email protected]>
It seems that little of that patch remains present in current mainline.
Quoted 5 lines · Andrew Morton
Quoted 1 line · On Sat, 24 Mar 2007 10:17:24 +0100 Andreas Schwab <[email protected]> wrote:
I'm getting this panic when loading sata-vsc on a SGI Prism:
With what kernel?
Linus' latest at this point in time.
Andreas.
Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Quoted 5 lines · Andrew Morton
Quoted 1 line · On Sat, 24 Mar 2007 10:17:24 +0100 Andreas Schwab <[email protected]> wrote:
I'm getting this panic when loading sata-vsc on a SGI Prism:
With what kernel?
It's still the same with 2.6.21-rc5.
Quoted 7 lines
Quoted 7 lines
Bisection has identified this patch (together with the follow-up patch to fix the compilation failure):
commit
7cbaa86b937b0b1fab95c159989f6a3c00bbcf78Author: Dan Wolstenholme <[email protected]> Date: Tue Jan 9 05:59:21 2007 -0500
Quoted 6 lines
Quoted 4 lines
[libata]
sata_vsc: support PCI MSISigned-off-by Jeff Garzik <[email protected]>It seems that little of that patch remains present in current mainline.
I'd guess the real bug is in the SN code.
Andreas.
Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Quoted 11 lines · Andrew Morton
Quoted 8 lines · On Sat, 24 Mar 2007 10:17:24 +0100 Andreas Schwab <[email protected]> wrote:
commit
7cbaa86b937b0b1fab95c159989f6a3c00bbcf78Author: Dan Wolstenholme <[email protected]> Date: Tue Jan 9 05:59:21 2007 -0500[libata]
sata_vsc: support PCI MSISigned-off-by Jeff Garzik <[email protected]>It seems that little of that patch remains present in current mainline.
An unfortunately illusion of further changes. The "turn MSI on" stuff is still here, but Tejun's cleanups made some of that housekeeping code go away.
But, as Andreas was guessing, the problem here is the platform's MSI support, with this as an unfortunate symptom.
Jeff