From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Tobias Karnat <tobias.karnat@googlemail.com>
Cc: linux-acpi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
richard.coe@med.ge.com, jslaby@novell.com
Subject: Re: acpi_button: random oops on boot
Date: Mon, 6 Dec 2010 09:28:11 -0700 [thread overview]
Message-ID: <201012060928.11307.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1291477752.5096.27.camel@Tobias-Karnat>
On Saturday, December 04, 2010 08:49:12 am Tobias Karnat wrote:
> I have a problem with random oopses on boot,
> every 1 out of 5 times I boot linux freezes.
>
> I was not able to obtain a call trace, however it happens around 10-15
> seconds after boot. I can hear that the tg3 driver is initialised.
>
> In this thread, they have the same problem:
> https://bugzilla.novell.com/show_bug.cgi?id=647029
Wow, that's a nasty problem.
> Applying the patch from the thread, makes the problem occurring less
> often and dmesg shows acpi-button loads for me on hid PNP0C0C and
> LNXPWRBN.
>
> Maybe commit e2fb9754d27513918a4936e8cbaad50ff56cfd3d
> ACPI: button: remove unnecessary null pointer checks
> has unmasked an underlying problem?
The oopses from the bugzilla are not the sort I would expect from
a null pointer dereference, but since it's fairly reproducible for
you, it might be worth reverting e2fb9754d27 to see whether it makes
any difference.
Does Rich's script from https://bugzilla.novell.com/show_bug.cgi?id=647029#c30
help you reproduce the problem?
Bjorn
next prev parent reply other threads:[~2010-12-06 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 15:49 acpi_button: random oops on boot Tobias Karnat
2010-12-06 16:28 ` Bjorn Helgaas [this message]
2010-12-06 23:01 ` Tobias Karnat
2010-12-06 23:26 ` Bjorn Helgaas
2010-12-06 23:54 ` Tobias Karnat
2010-12-07 0:22 ` Tobias Karnat
2010-12-07 5:15 ` Bjorn Helgaas
2010-12-07 14:44 ` Rich Coe
2010-12-07 15:02 ` Tobias Karnat
2010-12-07 15:35 ` Tobias Karnat
2010-12-07 15:52 ` Tobias Karnat
2011-01-24 13:03 ` Thomas Renninger
2011-01-24 18:13 ` Tobias Karnat
2011-01-24 18:48 ` Rich Coe
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=201012060928.11307.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=jslaby@novell.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.coe@med.ge.com \
--cc=tobias.karnat@googlemail.com \
/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