From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "William A.(Andy) Adamson" <andros@citi.umich.edu>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6.11-rc2 on powerbook g4 - lost interrupt
Date: Sat, 05 Feb 2005 10:37:49 +1100 [thread overview]
Message-ID: <1107560269.2188.103.camel@gaston> (raw)
In-Reply-To: <20050204135818.E67AC1BB0C@citi.umich.edu>
On Fri, 2005-02-04 at 08:58 -0500, William A.(Andy) Adamson wrote:
> hello
>
> thanks for the response.
>
> i disabled the cpufreq support. no change, config attached. the first 'lost
> interrupt' message appears after the 'hda: max request size: 1024KiB'. then
> lost interrupt messages are interleaved throughout the remaining boot, which
> eventually hangs.
>
> there is one 'lost interrupt, dma status: 8080' message
And going back to an earlier kernel fixes it ? Weird... I don't see
what's up there, I've tested this kernel on a bunch of powerbook's
without any such issue...
Ben.
prev parent reply other threads:[~2005-02-04 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 20:38 2.6.11-rc2 on powerbook g4 - lost interrupt William A.(Andy) Adamson
2005-02-03 23:07 ` Benjamin Herrenschmidt
2005-02-04 13:58 ` William A.(Andy) Adamson
2005-02-04 23:37 ` Benjamin Herrenschmidt [this message]
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=1107560269.2188.103.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=andros@citi.umich.edu \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).