From: Tom Sightler <ttsig@tuxyturvy.com>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1-mm5
Date: Tue, 20 Jan 2004 16:15:08 -0500 [thread overview]
Message-ID: <1074633308.14253.17.camel@localhost.localdomain> (raw)
I'm having a couple of minor issues with ACPI in the -mm series.
The battery status on my Dell Latitude D800 won't work at all without
the patch from http://bugzilla.kernel.org/show_bug.cgi?id=1766 however,
with vanilla 2.6.1 everything seems to work fine. Without this patch I
get tons of _ut_allocate: tried to allocate zero bytes (or something
close to this) and no battery status at all.
With the patch mentioned above everything seemed to work OK, however,
recently I enabled both 4GB highmem support (this seems to get me an
extra 128MB on my 1GB system) and preempt support and now, while it
initially works fine, the system eventually quits reporting battery
status and I get a lot of messages like the following every time I poll
for battery status (over and over if a battery status applet is loaded):
ACPI-0279: *** Error: Looking up [BST0] in namespace,
AE_ALREADY_EXISTS
ACPI-1120: *** Error: Method execution failed [\_SB_.BAT0._BST]
(Node f7feea60), AE_ALREADY_EXISTS
It seems that I can trigger this much quicker if a generate a lot of
traffic on my aironet wireless adapter, it will only take minutes to
occur. I'm going to try to back out preempt and 4GB support one at a
time and see what happens.
I haven't been able to reproduce any of these issues on 2.6.1 vanilla.
Later,
Tom
Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm5/
next reply other threads:[~2004-01-20 21:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 21:15 Tom Sightler [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-20 22:56 2.6.1-mm5 Thomas Molina
2004-01-20 23:09 ` 2.6.1-mm5 GCS
2004-01-20 23:47 ` 2.6.1-mm5 Thomas Molina
2004-01-21 0:27 ` 2.6.1-mm5 Greg KH
2004-01-21 1:33 ` 2.6.1-mm5 Thomas Molina
2004-01-21 0:34 ` 2.6.1-mm5 Andrew Morton
2004-01-21 1:36 ` 2.6.1-mm5 Thomas Molina
2004-01-21 1:41 ` 2.6.1-mm5 Andrew Morton
2004-01-21 2:27 ` 2.6.1-mm5 Thomas Molina
2004-01-21 9:14 ` 2.6.1-mm5 Marcos D. Marado Torres
[not found] <1fZhf-Xj-7@gated-at.bofh.it>
2004-01-20 15:35 ` 2.6.1-mm5 Matthew Kanar
2004-01-20 8:05 2.6.1-mm5 Andrew Morton
2004-01-20 11:14 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 16:37 ` 2.6.1-mm5 Andrew Morton
2004-01-20 11:35 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 18:30 ` 2.6.1-mm5 Mike Fedyk
2004-01-20 18:36 ` 2.6.1-mm5 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=1074633308.14253.17.camel@localhost.localdomain \
--to=ttsig@tuxyturvy.com \
--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