From: Tobias Karnat <tobias.karnat@googlemail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.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: Tue, 07 Dec 2010 00:54:59 +0100 [thread overview]
Message-ID: <1291679699.6246.11.camel@Tobias-Karnat> (raw)
In-Reply-To: <201012061626.45962.bjorn.helgaas@hp.com>
Am Montag, den 06.12.2010, 16:26 -0700 schrieb Bjorn Helgaas:
> On Monday, December 06, 2010 04:01:43 pm Tobias Karnat wrote:
> > No, it only crashes on boot (without the printk patch).
> > If it happens the machine is completely dead, SysRq does not work.
> >
> > However it is definitely the acpi_button module, because removing it
> > also fixes this.
>
> If it crashes on boot (not when loading an acpi_button module),
> you must be building acpi_button into the static kernel.
It does crash on boot either if built-in to the kernel or as a module,
However it does not crash if the module is loaded/unloaded after the
machine has booted.
> The acpi_button driver has a fairly complicated add() method.
> In the absence of a better idea, I might just comment out blocks
> of it and try to isolate the problem. For example, take out
> all the input stuff, take out the wakeup GPE stuff, take out
> the type/name setup, etc.
Couldn't this be a compiler issue?
Adding some printk's to fix it seems to be insane.
-Tobias
next prev parent reply other threads:[~2010-12-06 23:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 15:49 Tobias Karnat
2010-12-06 16:28 ` Bjorn Helgaas
2010-12-06 23:01 ` Tobias Karnat
2010-12-06 23:26 ` Bjorn Helgaas
2010-12-06 23:54 ` Tobias Karnat [this message]
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=1291679699.6246.11.camel@Tobias-Karnat \
--to=tobias.karnat@googlemail.com \
--cc=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 \
/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
all inboxes | Powered by JetHome®