From: pacman@kosh.dhis.org
To: benh@kernel.crashing.org (Benjamin Herrenschmidt)
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: memory corrupting bug, bisected to 6dda9d55
Date: Wed, 20 Oct 2010 13:33:36 -0500 (GMT+5) [thread overview]
Message-ID: <20101020183336.1714.qmail@kosh.dhis.org> (raw)
In-Reply-To: <1287570736.2198.19.camel@pasglop>
Benjamin Herrenschmidt writes:
>
> On Tue, 2010-10-19 at 22:23 -0500, pacman@kosh.dhis.org wrote:
> > The diff fragment above applied inside prom_close_stdin, but there are
> > some
> > prom_printf calls after prom_close_stdin. Calling prom_printf after
> > closing
> > stdout sounds like it could be bad. If I moved it down below all the
> > prom_printf's, it would be after the "quiesce" call. Would that be
> > acceptable
> > (or even interesting as an experiment)? Does a close need a quiesce
> > after it?
>
> Just try :-) "quiesce" is something that afaik only apple ever
> implemented anyways. It uses hooks inside their OF to shut down all
> drivers that do bus master (among other HW sanitization tasks).
I booted a version with a prom_close_stdout after the last prom_debug. It
didn't have any effect. That 1000Hz clock was still ticking.
--
Alan Curry
WARNING: multiple messages have this Message-ID (diff)
From: pacman@kosh.dhis.org
To: benh@kernel.crashing.org (Benjamin Herrenschmidt)
Cc: segher@kernel.crashing.org (Segher Boessenkool),
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: memory corrupting bug, bisected to 6dda9d55
Date: Wed, 20 Oct 2010 13:33:36 -0500 (GMT+5) [thread overview]
Message-ID: <20101020183336.1714.qmail@kosh.dhis.org> (raw)
In-Reply-To: <1287570736.2198.19.camel@pasglop>
Benjamin Herrenschmidt writes:
>
> On Tue, 2010-10-19 at 22:23 -0500, pacman@kosh.dhis.org wrote:
> > The diff fragment above applied inside prom_close_stdin, but there are
> > some
> > prom_printf calls after prom_close_stdin. Calling prom_printf after
> > closing
> > stdout sounds like it could be bad. If I moved it down below all the
> > prom_printf's, it would be after the "quiesce" call. Would that be
> > acceptable
> > (or even interesting as an experiment)? Does a close need a quiesce
> > after it?
>
> Just try :-) "quiesce" is something that afaik only apple ever
> implemented anyways. It uses hooks inside their OF to shut down all
> drivers that do bus master (among other HW sanitization tasks).
I booted a version with a prom_close_stdout after the last prom_debug. It
didn't have any effect. That 1000Hz clock was still ticking.
--
Alan Curry
next prev parent reply other threads:[~2010-10-20 18:33 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 9:57 PROBLEM: memory corrupting bug, bisected to 6dda9d55 pacman
2010-10-09 9:57 ` pacman
2010-10-11 12:52 ` Christoph Lameter
2010-10-11 12:52 ` Christoph Lameter
2010-10-11 14:30 ` Mel Gorman
2010-10-11 14:30 ` Mel Gorman
2010-10-11 20:35 ` pacman
2010-10-11 20:35 ` pacman
2010-10-11 21:00 ` Andrew Morton
2010-10-11 21:00 ` Andrew Morton
2010-10-11 21:00 ` Andrew Morton
2010-10-13 14:40 ` Mel Gorman
2010-10-13 14:40 ` Mel Gorman
2010-10-13 14:40 ` Mel Gorman
2010-10-13 17:52 ` pacman
2010-10-13 17:52 ` pacman
2010-10-13 17:52 ` pacman
2010-10-18 11:33 ` Mel Gorman
2010-10-18 11:33 ` Mel Gorman
2010-10-18 11:33 ` Mel Gorman
2010-10-18 19:10 ` pacman
2010-10-18 19:10 ` pacman
2010-10-18 19:10 ` pacman
2010-10-18 21:10 ` Benjamin Herrenschmidt
2010-10-18 21:10 ` Benjamin Herrenschmidt
2010-10-18 21:33 ` pacman
2010-10-18 21:33 ` pacman
2010-10-18 21:33 ` pacman
2010-10-19 10:16 ` Benjamin Herrenschmidt
2010-10-19 10:16 ` Benjamin Herrenschmidt
2010-10-19 18:10 ` pacman
2010-10-19 18:10 ` pacman
2010-10-19 18:10 ` pacman
2010-10-19 20:47 ` Segher Boessenkool
2010-10-19 20:47 ` Segher Boessenkool
2010-10-19 20:47 ` Segher Boessenkool
2010-10-19 21:02 ` Benjamin Herrenschmidt
2010-10-19 21:02 ` Benjamin Herrenschmidt
2010-10-19 21:02 ` Benjamin Herrenschmidt
2010-10-20 3:23 ` pacman
2010-10-20 3:23 ` pacman
2010-10-20 3:23 ` pacman
2010-10-20 10:32 ` Benjamin Herrenschmidt
2010-10-20 10:32 ` Benjamin Herrenschmidt
2010-10-20 10:32 ` Benjamin Herrenschmidt
2010-10-20 18:33 ` pacman [this message]
2010-10-20 18:33 ` pacman
2010-10-20 20:56 ` Benjamin Herrenschmidt
2010-10-20 20:56 ` Benjamin Herrenschmidt
2010-10-22 9:15 ` pacman
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 8:57 ` pacman
2010-10-27 10:13 ` Olaf Hering
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 22:58 ` pacman
2010-10-27 23:33 ` Segher Boessenkool
2010-10-27 23:33 ` Segher Boessenkool
2010-10-28 1:11 ` pacman
2010-10-28 19:50 ` Segher Boessenkool
2010-10-28 19:50 ` Segher Boessenkool
2010-10-28 21:07 ` pacman
2010-10-29 0:16 ` Segher Boessenkool
2010-10-29 0:16 ` Segher Boessenkool
2010-11-05 6:43 ` pacman
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-27 13:27 ` Benjamin Herrenschmidt
2010-10-19 20:58 ` PROBLEM: memory corrupting bug, bisected to 6dda9d55 Benjamin Herrenschmidt
2010-10-19 20:58 ` Benjamin Herrenschmidt
2010-10-18 19:37 ` Andrew Morton
2010-10-18 19:37 ` Andrew Morton
2010-10-18 19:37 ` Andrew Morton
2010-10-18 21:02 ` Benjamin Herrenschmidt
2010-10-18 21:02 ` Benjamin Herrenschmidt
2010-10-18 21:55 ` Thomas Gleixner
2010-10-18 21:55 ` Thomas Gleixner
2010-10-18 21:55 ` Thomas Gleixner
2010-10-19 16:24 ` Helmut Grohne
2010-10-19 16:24 ` Helmut Grohne
2010-10-19 16:24 ` Helmut Grohne
2010-10-19 16:42 ` Thomas Gleixner
2010-10-19 16:42 ` Thomas Gleixner
2010-10-19 16:42 ` Thomas Gleixner
2010-10-18 20:59 ` Benjamin Herrenschmidt
2010-10-18 20:59 ` Benjamin Herrenschmidt
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=20101020183336.1714.qmail@kosh.dhis.org \
--to=pacman@kosh.dhis.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.