From: Andrew Morton <akpm@linux-foundation.org>
To: Andreas Schwab <schwab@suse.de>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
jeff@garzik.org
Subject: Re: sata-vsc broken on SGI Prism
Date: Sun, 25 Mar 2007 01:20:44 -0800 [thread overview]
Message-ID: <20070325012044.97dc14fc.akpm@linux-foundation.org> (raw)
In-Reply-To: <je8xdnova3.fsf@sykes.suse.de>
On Sat, 24 Mar 2007 10:17:24 +0100 Andreas Schwab <schwab@suse.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@wolstenholme.net>
> Date: Tue Jan 9 05:59:21 2007 -0500
>
> [libata] sata_vsc: support PCI MSI
>
> Signed-off-by: Jeff Garzik <jeff@garzik.org>
>
It seems that little of that patch remains present in current mainline.
next prev parent reply other threads:[~2007-03-25 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-24 9:17 sata-vsc broken on SGI Prism Andreas Schwab
2007-03-25 9:20 ` Andrew Morton [this message]
2007-03-25 9:47 ` Andreas Schwab
2007-03-26 10:01 ` Andreas Schwab
2007-03-27 5:15 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070325012044.97dc14fc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox