linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linuxppc-dev@ozlabs.org, David Woodhouse <dwmw2@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Milton Miller <miltonm@bga.com>
Subject: Re: Make sure we populate the initroot filesystem late enough
Date: Tue, 27 Feb 2007 07:46:39 +0100	[thread overview]
Message-ID: <1172558799.11949.41.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0702261315080.12485@woody.linux-foundation.org>


> USB controller issues? We used to have these really hard-to-debug problems 
> with the USB controller being active and having had the BIOS set up the 
> command queues etc. Really subtle. It's why we now have PCI quirks for 
> shutting up (most) USB controllers very early.

On powermacs or powerbooks, the USB controller is shut down by the
firmware when we call the "quiesce" OF call from prom_init.c, which
happens before the kernel relocates itself to 0 and takes over memory.
Unless we fucked up something in there, I wouldn't expect that to be the
cause.
 
> If there is some USB controller that we miss, or that sets up its command 
> chain to some unexpected area (so that USB is active and corrupting memory 
> even very early on), that could explain it.

Did we setup the OHCI controller when the crash happen ? Maybe we broke
something subtle in the USB stack ?

Ben.

  reply	other threads:[~2007-02-27  6:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200612112059.kBBKx1j7022473@hera.kernel.org>
2007-02-26  0:00 ` Make sure we populate the initroot filesystem late enough David Woodhouse
2007-02-26  0:24   ` Linus Torvalds
2007-02-26  0:45     ` David Woodhouse
2007-02-26  1:17     ` David Woodhouse
2007-02-26  3:45       ` Linus Torvalds
2007-02-26  4:01         ` David Woodhouse
2007-02-26  4:13           ` Linus Torvalds
2007-02-26 16:24             ` David Woodhouse
2007-02-26  6:59           ` William Lee Irwin III
2007-02-26 15:53           ` Benjamin Herrenschmidt
2007-02-26 16:00             ` Segher Boessenkool
2007-02-26 16:44           ` Milton Miller
2007-02-26 20:57             ` David Woodhouse
2007-02-26 21:17               ` Linus Torvalds
2007-02-27  6:46                 ` Benjamin Herrenschmidt [this message]
2007-02-26 15:51       ` Benjamin Herrenschmidt
2007-02-26 20:51         ` Kumar Gala
2007-02-26 19:27   ` john stultz
2007-02-26 22:27     ` Paul TBBle Hampson
2007-02-27  6:48       ` Benjamin Herrenschmidt
2007-02-27 11:58         ` Segher Boessenkool
2007-02-28  6:43           ` Benjamin Herrenschmidt
2007-02-28 10:13             ` David Woodhouse
2007-03-01  0:30               ` Michael Ellerman
2007-03-12 23:01                 ` Paul TBBle Hampson
2007-03-13  3:03                   ` Kumar Gala
2007-03-13  7:03                   ` Benjamin Herrenschmidt
2007-03-16  7:20                     ` Paul TBBle Hampson

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=1172558799.11949.41.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miltonm@bga.com \
    --cc=torvalds@linux-foundation.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).