From: Rich Coe <Richard.Coe@med.ge.com>
To: Tobias Karnat <tobias.karnat@googlemail.com>
Cc: Thomas Renninger <trenn@suse.de>,
richard.coe@med.ge.com, jslaby@novell.com,
linux-acpi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: acpi_button: random oops on boot
Date: Mon, 24 Jan 2011 12:48:13 -0600 [thread overview]
Message-ID: <20110124124813.bb03c6fe.Richard.Coe@med.ge.com> (raw)
In-Reply-To: <1295892786.3265.48.camel@Tobias-Karnat>
On Mon, 24 Jan 2011 19:13:06 +0100
Tobias Karnat <tobias.karnat@googlemail.com> wrote:
> Am Montag, den 24.01.2011, 14:03 +0100 schrieb Thomas Renninger:
> I hope Rich is still interested in a solution as I am. The bad thing is
> that the latest working version I had been running on that machine was
> ancient 2.6.23. So this problem is a regression, which I would have
> noticed earlier, if I had updated that machine more often.
>
> It is not an hardware problem [...]
I don't think it's a hardware problem either.
I reproduced this on later kernels, 2.6.36 (I think).
I've been working on a project that's almost finished, then I plan on going
back to tracking down this issue.
Rich
--
prev parent reply other threads:[~2011-01-24 18:46 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
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 [this message]
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=20110124124813.bb03c6fe.Richard.Coe@med.ge.com \
--to=richard.coe@med.ge.com \
--cc=jslaby@novell.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tobias.karnat@googlemail.com \
--cc=trenn@suse.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