Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12956 - [kernel26] msi_laptop corrupts acpi information on MSI S271 Notebook
Attached to Project:
Arch Linux
Opened by Filipp Andjelo (scorp) - Sunday, 25 January 2009, 09:07 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 04 October 2009, 23:02 GMT
Opened by Filipp Andjelo (scorp) - Sunday, 25 January 2009, 09:07 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 04 October 2009, 23:02 GMT
|
DetailsDescription:
Battery status (and maybe other ACPI info) on the MSI S271 is wrong once the module 'msi_laptop' is loaded. The module is coming from the Kernel, so I think it's really a Kernel bug. Workaround: Blacklist 'msi_laptop' in '/etc/rc.conf' and reboot. It's not enough just to unload the module. No side effects known yet. Additional info: Tested on Kernel 2.6.28 (kernel26 2.6.28.1-1) |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Sunday, 04 October 2009, 23:02 GMT
Reason for closing: Upstream
Additional comments about closing: we can't do much here
Sunday, 04 October 2009, 23:02 GMT
Reason for closing: Upstream
Additional comments about closing: we can't do much here

- Field changed: Category (Packages: Core → Upstream Bugs)
If you really think it's a kernel bug, why didn't you submit it upstream?

- Field changed: Status (Unconfirmed → Assigned)
- Task assigned to Tobias Powalowski (tpowa)
Assigning, but it's probably upstream so we'll just have to wait for a fix

I submit this bug here, 'cause I think it's helpful for s.o. who's using the same hardware and can find the workaround. For me (and I think for many Arch users) it's one of the first places I'm looking for help. You know, may be it's a bug which all distributions are suffering from, but on Arch you can find a workaround :) If you think I shouldn't do it in the future, I'll not do.

status on .29 series?

Same thing...

status with 2.6.30 ? This is reported to upstream?

Nothing changed. It's a reported Kernel Bug... since a long time

Could you post a link to the upstream report for the devs to track the issue?