From: Pavel Machek <pavel@ucw.cz>
To: Kristen Accardi <kristen.c.accardi@intel.com>
Cc: "Brown, Len" <len.brown@intel.com>,
Andreas Saur <saur@acmelabs.de>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc4-mm3 - kernel panic
Date: Tue, 30 May 2006 12:25:39 +0200 [thread overview]
Message-ID: <20060530102538.GA1662@elf.ucw.cz> (raw)
In-Reply-To: <1148668175.7600.11.camel@whizzy>
Hi!
> > > No, I would not expect PCI to work properly with the debug patch -
> > > basically all I did was prevent the oops and confirm that this is the
> > > issue, I did not actually solve the problem.
> > >
> > > I need some way to prevent acpiphp from loading before dock is completed
> > > it's init.
> > >
> > > I guess I will think about this some more.
> >
> > Using different _init levels? Like putting dock at subsys_initcall()
> > while acpiphp at late_initcall()?
> > Pavel
>
> Can you see if this works for you? Revert the first debug patch I sent
> and apply this one instead (against -mm).
Tried it in
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 17
EXTRAVERSION =-rc4-mm3
...and now kernel hangs, last messages being:
pci_hotplug: ... core version: 0.5
ibmphpd: ... 0.6
acpiphp: ... 0.5
acpiphp: Slot [1] registered
I tried hitting magic sysrq, but it did not seem to respond.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-05-30 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CFF307C98FEABE47A452B27C06B85BB68AD7E1@hdsmsx411.amr.corp.intel.com>
2006-05-25 19:01 ` 2.6.17-rc4-mm3 - kernel panic Kristen Accardi
2006-05-25 22:12 ` Pavel Machek
2006-05-25 22:17 ` Pavel Machek
2006-05-26 0:04 ` Kristen Accardi
2006-05-26 7:15 ` Pavel Machek
2006-05-26 18:29 ` Kristen Accardi
2006-05-30 10:25 ` Pavel Machek [this message]
2006-05-25 18:55 Brown, Len
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=20060530102538.GA1662@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=kristen.c.accardi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saur@acmelabs.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