From: "David S. Miller" <davem@redhat.com>
To: mochel@osdl.org
Cc: anton@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [2.5.19] Oops during PCI scan on Alpha
Date: Tue, 04 Jun 2002 14:23:12 -0700 (PDT) [thread overview]
Message-ID: <20020604.142312.23013040.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0206041413530.654-100000@geena.pdx.osdl.net>
From: Patrick Mochel <mochel@osdl.org>
Date: Tue, 4 Jun 2002 14:14:26 -0700 (PDT)
On Tue, 4 Jun 2002, David S. Miller wrote:
> Does sys_bus_init require the generic bus layer to be initialized
> first?
Yes, and it is in drivers/base/bus.c just before sys_bus_init is called.
Linkers are allowed to reorder object files unless you tell them
explicitly not to.
This is why you need to put this stuff into a seperate initcall level.
This is precisely why I suggest postcore_initcall as the fix.
next prev parent reply other threads:[~2002-06-04 21:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 20:06 [2.5.19] Oops during PCI scan on Alpha Jan-Benedict Glaw
2002-06-03 4:27 ` Anton Blanchard
2002-06-03 3:39 ` David S. Miller
2002-06-04 15:50 ` Patrick Mochel
2002-06-04 17:07 ` Ivan Kokshaysky
2002-06-04 18:58 ` Patrick Mochel
2002-06-04 18:26 ` Benjamin Herrenschmidt
2002-06-05 14:20 ` Ivan Kokshaysky
2002-06-04 18:13 ` David S. Miller
2002-06-04 19:38 ` Patrick Mochel
2002-06-04 19:42 ` David S. Miller
2002-06-04 20:56 ` Tom Rini
2002-06-04 21:10 ` Patrick Mochel
2002-06-04 21:14 ` David S. Miller
2002-06-04 21:14 ` Patrick Mochel
2002-06-04 21:23 ` David S. Miller [this message]
2002-06-04 21:29 ` Patrick Mochel
2002-06-04 21:34 ` David S. Miller
2002-06-04 22:03 ` Patrick Mochel
2002-06-04 22:06 ` Patrick Mochel
2002-06-05 14:23 ` Ivan Kokshaysky
2002-06-05 22:29 ` David S. Miller
2002-06-06 0:01 ` Patrick Mochel
2002-06-06 13:22 ` Ivan Kokshaysky
2002-06-23 17:03 ` Jan-Benedict Glaw
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=20020604.142312.23013040.davem@redhat.com \
--to=davem@redhat.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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