From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Mel Gorman <mel@csn.ul.ie>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
pacman@kosh.dhis.org, Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: PROBLEM: memory corrupting bug, bisected to 6dda9d55
Date: Wed, 20 Oct 2010 08:02:48 +1100 [thread overview]
Message-ID: <1287522168.2198.5.camel@pasglop> (raw)
In-Reply-To: <56111.84.105.60.153.1287521237.squirrel@gate.crashing.org>
On Tue, 2010-10-19 at 22:47 +0200, Segher Boessenkool wrote:
>
> It looks like it is the frame counter in an USB OHCI HCCA.
> 16-bit, 1kHz update, offset x'80 in a page.
>
> So either the kernel forgot to call quiesce on it, or the firmware
> doesn't implement that, or the firmware messed up some other way.
I vote for the FW being on crack. Wouldn't be the first time with
Pegasos.
It's an OHCI or an UHCI in there ?
Can you try in prom_init.c changing the prom_close_stdin() function to
also close "stdout" ?
if (prom_getprop(_prom->chosen, "stdin", &val, sizeof(val)) > 0)
call_prom("close", 1, 0, val);
+ if (prom_getprop(_prom->chosen, "stdout", &val, sizeof(val)) > 0)
+ call_prom("close", 1, 0, val);
See if that makes a difference ?
Last option would be to manually turn the thing off with MMIO in yet-another
pegasos workaround in prom_init.c.
Cheers,
Ben.
next prev parent reply other threads:[~2010-10-19 21:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101009095718.1775.qmail@kosh.dhis.org>
[not found] ` <20101011143022.GD30667@csn.ul.ie>
2010-10-11 21:00 ` PROBLEM: memory corrupting bug, bisected to 6dda9d55 Andrew Morton
2010-10-13 14:40 ` Mel Gorman
2010-10-13 17:52 ` pacman
2010-10-18 11:33 ` Mel Gorman
2010-10-18 19:10 ` pacman
2010-10-18 21:10 ` Benjamin Herrenschmidt
2010-10-18 21:33 ` pacman
2010-10-19 10:16 ` Benjamin Herrenschmidt
2010-10-19 18:10 ` pacman
2010-10-19 20:47 ` Segher Boessenkool
2010-10-19 21:02 ` Benjamin Herrenschmidt [this message]
2010-10-20 3:23 ` pacman
2010-10-20 10:32 ` Benjamin Herrenschmidt
2010-10-20 18:33 ` pacman
2010-10-20 20:56 ` Benjamin Herrenschmidt
2010-10-22 9:15 ` pacman
2010-10-27 8:57 ` Pegasos OHCI bug (was Re: PROBLEM: memory corrupting bug, bisected to 6dda9d55) pacman
2010-10-27 10:13 ` Olaf Hering
2010-10-27 21:04 ` Pegasos OHCI bug (was Re: PROBLEM: memory corrupting bug, pacman
2010-10-27 22:05 ` Segher Boessenkool
2010-10-27 22:58 ` pacman
2010-10-27 23:33 ` Segher Boessenkool
2010-10-28 1:11 ` pacman
2010-10-28 19:50 ` Segher Boessenkool
2010-10-28 21:07 ` pacman
2010-10-29 0:16 ` Segher Boessenkool
2010-11-05 6:43 ` pacman
2010-11-29 5:44 ` Benjamin Herrenschmidt
2010-10-27 13:27 ` Pegasos OHCI bug (was Re: PROBLEM: memory corrupting bug, bisected to 6dda9d55) Benjamin Herrenschmidt
2010-10-19 20:58 ` PROBLEM: memory corrupting bug, bisected to 6dda9d55 Benjamin Herrenschmidt
2010-10-18 19:37 ` Andrew Morton
2010-10-18 21:02 ` Benjamin Herrenschmidt
2010-10-18 21:55 ` Thomas Gleixner
2010-10-19 16:24 ` Helmut Grohne
2010-10-19 16:42 ` Thomas Gleixner
2010-10-18 20:59 ` Benjamin Herrenschmidt
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=1287522168.2198.5.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mel@csn.ul.ie \
--cc=pacman@kosh.dhis.org \
--cc=segher@kernel.crashing.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).