linux-kernel - Re: sata-vsc broken on SGI Prism

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 25 Mar 2007 01:20:44 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Andreas Schwab <schwab@...e.de>
Cc:	linux-ia64@...r.kernel.org, linux-kernel@...r.kernel.org,
	jeff@...zik.org
Subject: Re: sata-vsc broken on SGI Prism

On Sat, 24 Mar 2007 10:17:24 +0100 Andreas Schwab <schwab@...e.de> wrote:

> I'm getting this panic when loading sata-vsc on a SGI Prism:

With what kernel?

> 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 <daniel@...stenholme.net>
> Date:   Tue Jan 9 05:59:21 2007 -0500
> 
>     [libata] sata_vsc: support PCI MSI
>     
>     Signed-off-by: Jeff Garzik <jeff@...zik.org>
> 

It seems that little of that patch remains present in current mainline.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/