From: linas@austin.ibm.com
To: maurie <maurie@risc.sps.mot.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Linuxppc 8245 lost interrupt
Date: Thu, 10 Jul 2003 12:17:33 -0500 [thread overview]
Message-ID: <20030710121733.B41788@forte.austin.ibm.com> (raw)
In-Reply-To: <000101c346ee$46545ac0$9b7c520a@sps.mot.com>; from maurie@risc.sps.mot.com on Thu, Jul 10, 2003 at 09:19:28AM -0500
On Thu, Jul 10, 2003 at 09:19:28AM -0500, maurie wrote:
>
> I am using kernel 2.4.21-rc1.
Please try another one of the kernels. There were several ide-related
ppc64 bugs; I am currently confused about which ones got fixed when
(or if they are fixed yet). I breifly saw the lost-irq bug, but it
went away for me, not sure why.
--linas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-10 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 14:19 Linuxppc 8245 lost interrupt maurie
2003-07-10 17:17 ` linas [this message]
2003-07-14 15:07 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2003-07-10 14:17 Linuxppc 8245 Lost interrupt maurie
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=20030710121733.B41788@forte.austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=maurie@risc.sps.mot.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).