From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Olaf Hering <olaf@aepfle.de>,
linuxppc-dev@ozlabs.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.26-rc5 (G5 SATA broken)
Date: Fri, 06 Jun 2008 14:36:46 +1000 [thread overview]
Message-ID: <1212727006.12464.25.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0806051255340.28792@blonde.site>
> I've been bisecting that on Quad G5 (sata_svw): irq 18: nobody cared ...,
> then later endless ata1.00: exception..., blah blah, ata1: EH complete.
> It comes down to:
Thanks for finding that !
/me likes when he wakes up in the morning to find a G5 bug ... and the
fix in the same thread :-)
Cheers,
Ben.
next prev parent reply other threads:[~2008-06-06 4:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 3:36 Linux 2.6.26-rc5 Linus Torvalds
2008-06-05 11:24 ` Olaf Hering
2008-06-05 12:09 ` Linux 2.6.26-rc5 (G5 SATA broken) Hugh Dickins
2008-06-05 12:54 ` Alan Cox
2008-06-05 13:44 ` [PATCH] libata: fix G5 SATA broken on -rc5 Hugh Dickins
2008-06-05 14:45 ` Olaf Hering
2008-06-06 4:36 ` Benjamin Herrenschmidt [this message]
2008-06-05 12:42 ` Linux 2.6.26-rc5 Alan Cox
2008-06-05 13:03 ` Alejandro Riveira Fernández
2008-06-05 14:54 ` Linus Torvalds
2008-06-05 15:12 ` Bjorn Helgaas
2008-06-05 16:12 ` Bjorn Helgaas
2008-06-05 16:19 ` Linus Torvalds
2008-06-05 16:32 ` Bjorn Helgaas
2008-06-05 14:43 ` Ben Dooks
2008-06-06 18:35 ` Linus Torvalds
2008-06-10 12:57 ` ACPI pull for 2.6.26? Adrian Bunk
2008-06-10 15:23 ` Len Brown
2008-06-10 15:39 ` Adrian Bunk
2008-06-05 14:47 ` Linux 2.6.26-rc5 Alex Romosan
2008-06-07 19:44 ` Jesper Krogh
2008-06-07 21:50 ` Frans Pop
2008-06-09 3:39 ` Bjorn Helgaas
2008-06-09 10:01 ` Frans Pop
2008-06-07 19:52 ` Jesper Krogh
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=1212727006.12464.25.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hugh@veritas.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olaf@aepfle.de \
--cc=torvalds@linux-foundation.org \
/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