From: Kristen Accardi <kristen.c.accardi@intel.com>
To: Pavel Machek <pavel@ucw.cz>
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: Thu, 25 May 2006 17:04:18 -0700 [thread overview]
Message-ID: <1148601858.3070.62.camel@whizzy> (raw)
In-Reply-To: <20060525221744.GA1671@elf.ucw.cz>
On Fri, 2006-05-26 at 00:17 +0200, Pavel Machek wrote:
> On Pá 26-05-06 00:12:22, Pavel Machek wrote:
> > Hi!
> >
> > > > Does the panic go away with CONFIG_ACPI_DOCK=n?
> >
> > > Can either Pavel or Andreas please try this little debugging patch and
> > > send me the dmesg output? Please enable the CONFIG_DEBUG_KERNEL option
> > > in your .config as well so that I can get additional info.
> >
> > Yep, you were right... this debugging patch helps.
>
> ...and docking +/- works, but it does not look like PCI in docking
> station is properly connected:
>
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.
Kristen
next prev parent reply other threads:[~2006-05-25 23:52 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 [this message]
2006-05-26 7:15 ` Pavel Machek
2006-05-26 18:29 ` Kristen Accardi
2006-05-30 10:25 ` Pavel Machek
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=1148601858.3070.62.camel@whizzy \
--to=kristen.c.accardi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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