From: Greg KH <greg@kroah.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Battery-related regression between 2.6.17-git3 and 2.6.17-git6
Date: Mon, 3 Jul 2006 11:00:53 -0700 [thread overview]
Message-ID: <20060703180053.GA16787@kroah.com> (raw)
In-Reply-To: <200607031316.46034.rjw@sisk.pl>
On Mon, Jul 03, 2006 at 01:16:45PM +0200, Rafael J. Wysocki wrote:
> Hi,
>
> On Sunday 02 July 2006 11:15, Rafael J. Wysocki wrote:
> > On Sunday 02 July 2006 00:21, Rafael J. Wysocki wrote:
> > > With the recent -git on my box (Asus L5D, x86_64 SUSE 10) the powersave
> > > demon is apparently unable to get the battery status, although the data in
> > > /proc/acpi/battery/BAT0 seem to be correct. As a result, battery status
> > > notification via kpowersave doesn't work and it's hard to notice when the
> > > battery is low/critical.
> > >
> > > So far I have verified that this feature works fine with 2.6.17-git3 and
> > > doesn't work with 2.6.17-git6 (-git5 doesn't compile here).
> > >
> > > I'll try to get more information tomorrow (unless someone in the know has
> > > an idea of what's up ;-) ).
> >
> > I've verified that the problem first appeared in 2.6.17-git4.
>
> Apparently this happens because powersaved takes the battery status
> information from hald and the following kernel changes make hald crash on
> my system:
>
> http://kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=43104f1da88f5335e9a45695df92a735ad550dda
> http://kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=bd00949647ddcea47ce4ea8bb2cfcfc98ebf9f2a
> http://kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c182274ffe1277f4e7c564719a696a37cacf74ea
> http://kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9bde7497e0b54178c317fac47a18be7f948dd471
> http://kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=36679ea59846d8f34a48f71ca1a37671ca0ad3c5
>
> (ie. after reverting them hald works again).
Ick, that should not cause any problems, as sysfs should look identical
to how it was before those patches. Except that the /sys/class/usb/
stuff is now symlinks instead of real directories, but HAL has had to
handle that for a long time now (and it's even documented in
Documentation/ABI/testing/sysfs-class)
Can you tell me exactly which of the above patches breaks HAL?
Which version of HAL are you using? I have 0.5.7 here and it works just
fine.
And why would they even matter? The battery is not a USB device...
confused,
greg k-h
next prev parent reply other threads:[~2006-07-03 18:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 22:21 Battery-related regression between 2.6.17-git3 and 2.6.17-git6 Rafael J. Wysocki
2006-07-02 9:15 ` Rafael J. Wysocki
2006-07-03 11:16 ` Rafael J. Wysocki
2006-07-03 18:00 ` Greg KH [this message]
2006-07-03 19:39 ` Rafael J. Wysocki
2006-07-03 19:44 ` Greg KH
2006-07-03 20:26 ` Rafael J. Wysocki
2006-07-03 20:45 ` Greg KH
2006-07-04 11:55 ` Rafael J. Wysocki
2006-07-04 21:48 ` Greg KH
2006-07-04 22:14 ` Kay Sievers
2006-07-05 2:51 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2006-07-05 21:17 Larry Finger
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=20060703180053.GA16787@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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