From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, Olaf Hering <olaf@aepfle.de>
Subject: Re: crash in init_ipic_sysfs on efika
Date: Fri, 21 Mar 2008 22:18:35 +1100 [thread overview]
Message-ID: <1206098315.8420.69.camel@pasglop> (raw)
In-Reply-To: <47E24B69.2080607@genesi-usa.com>
On Thu, 2008-03-20 at 11:32 +0000, Matt Sealey wrote:
> subsys_initcall(init_ipic_sysfs); <-- this, in my eyes, is the culprit. If
> init_ipic() runs, init_ipic_sysfs should be called from that, not left for
> some further subsystem to blindly try and register sysfs nodes for devices
> which may not even be present..
>
> I'd love someone to explain to me how this works and why, and why it isn't
> braindead? :D
init_ipic() is called way too early to be able to manpipulate sysfs.
Ben.
next prev parent reply other threads:[~2008-03-21 11:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 19:53 crash in init_ipic_sysfs on efika Olaf Hering
2008-03-19 5:26 ` Paul Mackerras
2008-03-20 6:45 ` Olaf Hering
2008-03-19 15:27 ` Olaf Hering
2008-03-20 11:32 ` Matt Sealey
2008-03-21 11:18 ` Benjamin Herrenschmidt [this message]
2008-03-20 15:15 ` Kumar Gala
2008-03-21 1:38 ` Paul Mackerras
2008-03-21 5:14 ` Grant Likely
2008-03-21 9:03 ` Paul Mackerras
2008-03-21 9:18 ` Kumar Gala
2008-03-24 8:02 ` Paul Mackerras
2008-03-24 22:59 ` Kumar Gala
2008-03-21 13:14 ` Matt Sealey
2008-03-21 18:51 ` Grant Likely
2008-03-22 15:25 ` Sven Luther
2008-03-23 9:00 ` David Woodhouse
2008-03-23 10:12 ` Sven Luther
2008-03-23 10:13 ` David Woodhouse
2008-03-23 10:24 ` Sven Luther
2008-03-24 23:01 ` Matt Sealey
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=1206098315.8420.69.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.com \
--cc=olaf@aepfle.de \
/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).