From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: will_schmidt@vnet.ibm.com
Cc: Steve Fox <drfickle@us.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: Linux v2.6.18-rc1
Date: Mon, 10 Jul 2006 15:40:13 +0100 [thread overview]
Message-ID: <1152542413.27368.131.camel@localhost.localdomain> (raw)
In-Reply-To: <1152537672.28828.4.camel@farscape.rchland.ibm.com>
Ar Llu, 2006-07-10 am 08:21 -0500, ysgrifennodd Will Schmidt:
> On Sun, 2006-09-07 at 20:34 +1000, Benjamin Herrenschmidt wrote:
> > On Fri, 2006-07-07 at 10:41 -0500, Steve Fox wrote:
> > > We've got a ppc64 machine that won't boot with this due to an IDE error.
> >
> > What machine precisely ?
>
> I see a slightly more verbose version on a JS20 blade.
>
> hda: dma_timer_expiry: dma status == 0x24
> hda: DMA interrupt recovery
> hda: lost interrupt
That in repeat generally means the IRQ logic on the platform has been
broken. If we don't get interrupts we don't work very well.
Also check if booting with "nodma" set on the relevant ide interface
makes a difference. Just to be sure. If it does then submit patches to
fix the bug.
Alan
next prev parent reply other threads:[~2006-07-10 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0607052115210.12404@g5.osdl.org>
2006-07-07 15:41 ` Linux v2.6.18-rc1 Steve Fox
2006-07-09 10:34 ` Benjamin Herrenschmidt
2006-07-10 13:21 ` Will Schmidt
2006-07-10 14:40 ` Alan Cox [this message]
2006-07-10 21:17 ` Benjamin Herrenschmidt
2006-07-11 17:00 ` Steve Fox
2006-07-10 21:16 ` Benjamin Herrenschmidt
2006-07-10 16:38 ` Steve Fox
2006-07-10 18:30 ` Steve Fox
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=1152542413.27368.131.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=drfickle@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=will_schmidt@vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).