lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20071208082815.GB30997@elte.hu> Date: Sat, 8 Dec 2007 09:28:15 +0100 From: Ingo Molnar <mingo@...e.hu> To: Fabio Comolli <fabio.comolli@...il.com> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, LKML <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Greg KH <gregkh@...e.de>, Len Brown <lenb@...nel.org> Subject: Re: 2.6.24-rc4-git5: Reported regressions from 2.6.23 * Fabio Comolli <fabio.comolli@...il.com> wrote: > <snip> > > > Subject : Battery shows up twice in kpowersave > > Submitter : Rolf Eike Beer <eike-kernel@...tec.de> > > References : http://bugzilla.kernel.org/show_bug.cgi?id=9494 > > Handled-By : Alexey Starikovskiy <astarikovskiy@...e.de> > > Patch : > > > > I don't think that this is a regression: I reported on RedHat bugzilla > when I switched from F7 to F8 and I was using 2.6.23.8 at that time. > It looks to me an HAL regression, but of course I may be wrong :-) as > the reported bisected to a bad commit. > > https://bugzilla.redhat.com/show_bug.cgi?id=373041 > > By the way, I now switched to Fedrora Rawhide with a 2.6.24-rc4-git5 > custom kernel and Gnome desktop and the problem is still present, even > with gnome-power-manager. to me this looks like an ABI regression - utilities should work without change. Something changed in /sys output that caused HAL to think that there are two batteries: | The output of lshal shows that there are two UDI's with | info.capabilities = { 'battery' }: | | udi = '/org/freedesktop/Hal/devices/acpi_BAT0' | udi = '/org/freedesktop/Hal/devices/computer_power_supply_0' whether it's a HAL bug or a kernel bug, the original state should be restored and it should be worked out without breaking users of older HAL versions. grumble: way too many times do various system utilities break when i upgrade the kernel on my laptop. Maybe a new debug mechanism: we should start fingerprinting the exact /sys and /proc output and enforce that it's immutable across kernel releases as long as the hardware is unmodified? Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists