From: Yu Luming <luming.yu@intel.com>
To: Narayan Desai <desai@mcs.anl.gov>
Cc: Alexander Wagner <a.wagner@physik.uni-wuerzburg.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.1[4,5]: battery info lost
Date: Fri, 13 Jan 2006 13:55:36 +0800 [thread overview]
Message-ID: <200601131355.36958.luming.yu@intel.com> (raw)
In-Reply-To: <87mzi1ay5f.fsf@topaz.mcs.anl.gov>
On Friday 13 January 2006 06:18, Narayan Desai wrote:
> I found that disabling CONFIG_PREEMPT fixed the problems for me. A
> co-worker reported (today, coincidentally) that using the
> acpi_serialize kernel option seems to have fixed the problem for him.
> -nld
Please try patch http://bugzilla.kernel.org/show_bug.cgi?id=4588#c31
when PREEMPT enabled.
--
Thanks,
Luming
next prev parent reply other threads:[~2006-01-13 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 17:37 2.6.1[4,5]: battery info lost Alexander Wagner
2006-01-12 19:17 ` Jiri Slaby
2006-01-12 19:48 ` Gene Heskett
2006-01-12 22:18 ` Narayan Desai
2006-01-13 5:55 ` Yu Luming [this message]
2006-01-13 5:52 ` Yu Luming
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=200601131355.36958.luming.yu@intel.com \
--to=luming.yu@intel.com \
--cc=a.wagner@physik.uni-wuerzburg.de \
--cc=desai@mcs.anl.gov \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).