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
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
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
Comment by Glenn Matthys (RedShift) - Sunday, 25 January 2009, 11:57 GMT
  • Field changed: Category (Packages: Core → Upstream Bugs)
If you really think it's a kernel bug, why didn't you submit it upstream?
Comment by Aaron Griffin (phrakture) - Monday, 26 January 2009, 18:51 GMT
Assigning, but it's probably upstream so we'll just have to wait for a fix
Comment by Filipp Andjelo (scorp) - Friday, 30 January 2009, 11:48 GMT
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.
Comment by Tobias Powalowski (tpowa) - Thursday, 14 May 2009, 05:22 GMT
status on .29 series?
Comment by Filipp Andjelo (scorp) - Thursday, 14 May 2009, 07:01 GMT
Same thing...
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 15 June 2009, 22:54 GMT
status with 2.6.30 ? This is reported to upstream?
Comment by Filipp Andjelo (scorp) - Tuesday, 16 June 2009, 09:05 GMT
Nothing changed. It's a reported Kernel Bug... since a long time
Comment by Greg (dolby) - Tuesday, 16 June 2009, 12:20 GMT
Could you post a link to the upstream report for the devs to track the issue?

Loading...