public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Chris Howie <cdhowie@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux PM List <linux-pm@lists.linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, "H. Anvin" <hpa@zytor.com>,
	Greg KH <gregkh@suse.de>
Subject: Re: Boot problems with 2.6.29.1 - cannot smoothly boot on battery
Date: Sun, 24 May 2009 22:36:21 +0200	[thread overview]
Message-ID: <200905242236.22715.rjw@sisk.pl> (raw)
In-Reply-To: <3d2f29dc0905180125x5e7ef51dqf10955a3d44336e2@mail.gmail.com>

On Monday 18 May 2009, Chris Howie wrote:
> Folks:
> 
> I've been running 2.6.29.1 for some time and reported an issue to this
> mailing list a while ago about the boot process.  I believe I have now
> nailed down the one factor that determines whether I see this issue.
> 
> The problem arises only when booting or halting my laptop when there
> is no power plugged in, e.g. the system is running on battery.
> Sometime after init begins starting services I must hold down a key on
> the keyboard to convince it to continue booting, otherwise it just
> hangs.  If the system is running on AC then it boots fine.  This same
> problem repeats itself during the halt process if running on battery.
> 
> This also happens when resuming a suspend-to-disk image, after loading
> the data from the hard drive, but before control is returned to
> userspace.  The keyboard has no effect on this hang, presumably
> because the kernel is not listening to the keyboard at this point.
> When this happens the only solution is to hold the power button and
> boot normally instead.
> 
> An issue like this is a serious usability problem for me.  I am
> neither a kernel developer nor hacker, my coding skills applying
> mostly to userspace applications.  If there is anything you need from
> me to help diagnose this problem please let me know.
> 
> I am not subscribed so please CC me on replies.

Let's try to make your report a bit more visible (some CCs added).

Best,
Rafael

       reply	other threads:[~2009-05-24 20:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3d2f29dc0905180125x5e7ef51dqf10955a3d44336e2@mail.gmail.com>
2009-05-24 20:36 ` Rafael J. Wysocki [this message]
2009-05-24 21:20   ` Boot problems with 2.6.29.1 - cannot smoothly boot on battery H. Peter Anvin
2009-05-25  0:49     ` yakui_zhao
2009-05-25  1:18     ` Shaohua Li
2009-05-25  1:53       ` Chris Howie
2009-05-26 19:51         ` Chris Howie

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=200905242236.22715.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=cdhowie@gmail.com \
    --cc=gregkh@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mingo@elte.hu \
    /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