From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
To: Alan Jenkins <alan-jenkins-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
Cc: Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux acpi <linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Regression: BUG when battery is removed before resuming from hibernation
Date: Tue, 8 Jun 2010 22:52:49 +0200 [thread overview]
Message-ID: <201006082252.49452.rjw@sisk.pl> (raw)
In-Reply-To: <4C0E40E1.2080108-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
On Tuesday 08 June 2010, Alan Jenkins wrote:
> I found this bug 2.6.34 on my Asus EeePC 701 (x86_32 arch). It didn't
> happen to me before, when I was running nearly-2.6.33 or 2.6.32-release.
>
> I used git-bisect, but unfortunately the result isn't very helpful. My
> next step will be to try to narrowing down the culprits by disabling
> individual CONFIG options. Here are my results so far, in case anyone
> is interested.
>
>
> == Steps to reproduce ==
>
> I) Boot off mains power, with battery removed. Login to KDE4 session,
> with Konsole as the only running application.
> II) Run "sudo pm-hibernate"
>
> 1. When the system switches to text mode (a.k.a the console),
> immediately insert the battery.
> 2. Once the system has fully hibernated, remove the battery.
> 3. Press the power button to resume. The backtrace below is generated
> during resume.
You're not supposed to be doing that.
Rafael
next prev parent reply other threads:[~2010-06-08 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 13:08 Regression: BUG when battery is removed before resuming from hibernation Alan Jenkins
[not found] ` <4C0E40E1.2080108-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2010-06-08 15:27 ` Alan Jenkins
2010-06-08 20:52 ` Rafael J. Wysocki [this message]
[not found] ` <201006082252.49452.rjw-KKrjLPT3xs0@public.gmane.org>
2010-06-09 9:07 ` Regression: " Alan Jenkins
[not found] ` <4C0F59C8.8020704-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2010-06-09 9:14 ` Rafael J. Wysocki
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=201006082252.49452.rjw@sisk.pl \
--to=rjw-kkrjlpt3xs0@public.gmane.org \
--cc=alan-jenkins-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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