From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Michael (rabenkind) Brandstetter" <listen@selfservix.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.24-rc1: OOPS at acpi_battery_update
Date: Mon, 5 Nov 2007 01:18:34 +0100 [thread overview]
Message-ID: <200711050118.34610.rjw@sisk.pl> (raw)
In-Reply-To: <200711050029.09768.listen@selfservix.org>
On Monday, 5 of November 2007, Michael (rabenkind) Brandstetter wrote:
> Am Sonntag, 4. November 2007 14:17:23 schrieben Sie:
> > On Sunday, 4 of November 2007, Romano Giannetti wrote:
> > > On Fri, 2007-11-02 at 17:08 +0100, Rafael J. Wysocki wrote:
> > > > On Friday, 2 November 2007 00:14, Andrew Morton wrote:
> > > > > On Mon, 29 Oct 2007 11:11:04 +0100
>
> Hello!
>
> > > [OOPS removed]
> > >
> > > > > Did any earlier kernels do this? In other words, do you believe that
> > > > > this is a bug which we added after 2.6.23 was released?
>
> Yes the kernels prior to 2.6.24-rc1 did not have this bug.
>
> The oops always appear when i plug in or remove the battery.
>
> > > Never noticed it before. But it's happening just sometime (I've had it
> > > just two times), so I cannot be sure.
> > >
> > > > This might be the same as
> > > > http://bugzilla.kernel.org/show_bug.cgi?id=9283
> > >
> > > Hmmm... there is too little info for my level in that bug report to
> > > understand if it's the same.
> >
> > Then, please apply the patch from
> >
> > http://bugzilla.kernel.org/attachment.cgi?id=13376&action=view
> >
> > and see if the problem goes away.
>
> The bug went away on my Dell Latitude C610. I applied the patch on two boxes
> (2.6.24-rc1-git12) and the haldaemon is not killed and no oops when i remove
> the battery or plug it in.
>
> But on the Portege 3110CT the bug remains.
Well, please create a bug report at http://bugzilla.kernel.org regarding this
bug and place all of the relevant information in there (including what boxes
are fixed by the above patch etc.) Also please add my address to the report's
CC list.
Thanks,
Rafael
next prev parent reply other threads:[~2007-11-05 0:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 10:11 2.6.24-rc1: OOPS at acpi_battery_update Romano Giannetti
2007-11-01 23:14 ` Andrew Morton
2007-11-02 16:08 ` Rafael J. Wysocki
2007-11-04 9:34 ` *SPAM* " Romano Giannetti
2007-11-04 13:17 ` Rafael J. Wysocki
2007-11-04 23:29 ` Michael (rabenkind) Brandstetter
2007-11-05 0:18 ` Rafael J. Wysocki [this message]
2007-11-08 15:53 ` Johannes Weiner
2007-11-08 16:16 ` Rafael J. Wysocki
2007-11-08 16:11 ` Alexey Starikovskiy
2007-11-08 16:46 ` Johannes Weiner
2007-11-08 16:35 ` Alexey Starikovskiy
2007-11-08 16:58 ` Johannes Weiner
2007-11-09 4:34 ` Andrew Morton
2007-11-09 9:36 ` Alexey Starikovskiy
2007-11-09 9:49 ` Andrew Morton
2007-11-13 8:35 ` Alexey Starikovskiy
2007-11-13 8:59 ` Andrew Morton
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=200711050118.34610.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=listen@selfservix.org \
/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