From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gerhard Pircher <gerhard_pircher@gmx.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 2.6.23-rc8 dies somewhere during boot!?
Date: Fri, 28 Sep 2007 08:39:43 +1000 [thread overview]
Message-ID: <1190932783.6158.39.camel@pasglop> (raw)
In-Reply-To: <20070927222733.201970@gmx.net>
On Fri, 2007-09-28 at 00:27 +0200, Gerhard Pircher wrote:
> -------- Original-Nachricht --------
> > Datum: Thu, 27 Sep 2007 17:20:07 -0500
> > Von: linas@austin.ibm.com
> > An: Gerhard Pircher <gerhard_pircher@gmx.net>
> > CC: linuxppc-dev@ozlabs.org
> > Betreff: Re: 2.6.23-rc8 dies somewhere during boot!?
>
> > On Thu, Sep 27, 2007 at 11:57:35PM +0200, Gerhard Pircher wrote:
> >
> > The last identifiable message I was
> >
> > <7>PCI: Calling quirk...
> >
> > which is from drivers/pci/quirks.c
> >
> > ...CI: Found 0000:00:07.2 [1106/303...
> >
> > and this is from pci_setup_device() in drivers/pci/probe.c So I'd look
> > to see if pci_setup_device() ever returned, and then I'd look to see
> > what happened next.
> Ah, I thought probing is done in the architecture's PCI code. I'll take
> a look at pci_setup_device() function.
It's one of the quirks I suppose. Those are often full of x86 only
bogoziness that hurts everybody else if you happen to hit them.
The "late" quirks are called at pci_enable_device() time.
Ben
next prev parent reply other threads:[~2007-09-27 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 19:12 2.6.23-rc8 dies somewhere during boot!? Gerhard Pircher
2007-09-27 19:25 ` Linas Vepstas
2007-09-27 19:31 ` Gerhard Pircher
2007-09-27 20:50 ` Linas Vepstas
2007-09-27 21:17 ` Gerhard Pircher
2007-09-27 21:35 ` Linas Vepstas
2007-09-27 21:57 ` Gerhard Pircher
2007-09-27 22:20 ` Linas Vepstas
2007-09-27 22:27 ` Gerhard Pircher
2007-09-27 22:39 ` Benjamin Herrenschmidt [this message]
2007-09-27 23:31 ` Paul Mackerras
2007-09-28 9:53 ` Gerhard Pircher
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=1190932783.6158.39.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=gerhard_pircher@gmx.net \
--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).