Bug 5838
| Summary: | logfile flooded with ACPI error messages on FuSi Amilo M1439G | ||
|---|---|---|---|
| Product: | ACPI | Reporter: | Marcus Fischer (linux) |
| Component: | Power-Battery | Assignee: | Vladimir Lebedev (vladimir.p.lebedev) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.15 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
|
Description
Marcus Fischer
2006-01-05 14:23:36 UTC
First of all please try 2.6.16-rc1-mm3. Ok, I wasn't able to get the necessary sources and patches together and applied, I'm a typical end user only and don't really understand what's going on on your side of the curtain :-) But for luck, there is a new "feature" for the Mandriva Cooker repository: They offer "kernel-linus..." RPMs for a couple of weeks now, which are plain vanilla ones and not totally patched distro kernels. The latest I got was "kernel-linus-2.6.16.rc1". I know this is not Andrews -mm series release, but the ACPI error messages are still available *puh* Is this enough information? - Or are there important ACPI fixes which went into -mm for testing only? I'll try get to a rc1-mm3 kernel today, but I cannot promise to be successful right now. Marcus > Is this enough information? - Or are there important ACPI fixes which went
> into -mm for testing only?
Yes, there are some fixes which are available in 'mm' only now.
So, there are two ways:
a) wait for the next kernel version ...
b) try to build the latest kernel version manully.
I can help you here. Are you ready?
I'm ready for a linux lesson, yes ;-) Ok, first of, I'll explain how I tried to get to 2.6.16-rc1-mm3, and you can correct me if something is wrong. 1.) I downloaded the full sources for 2.6.15.1 from kernel.org 2.) I downloaded the 2.6.16-rc1 patch 3.) I downloaded the three patches 2.6.16-rc1-mm1 .. -mm3 4.) I extracted the sources and tried to apply the -rc1 patch via "patch -p1 <patchfile.name" (found that command in a forum somewhere...) I think I got initial error messages here, but few only. 5.) I tried to apply the MM series patches in the same way, and -mm1 run half the way down, besides some error messages. (There was a prompt which asks for a "-R" option. I answered everything by Return to get the default settings running. The patches -mm2 and -mm3 didn't work anymore, I had to press Return for every single line which can obviously not be the expected behaviour. Questions: - Against which full source do I have to apply the -mm series patches? - If I didn't got it totally wrong, ..16-rc1-mm1 is a diff against ..15-mm4 or something. Do Linus' and Andrews kernel series never ever meet at a stable point? (If that's true, how can I apply --mm patches against a full source?) Fine, that's you turn now. Keep in mind that I'm a end user only! Also keep in mind that this was your idea about this lesson ;-) First of all you should download linux-2.6.15.tar.bz2 (not 2.6.15.1) from http://www.kernel.org/pub/linux/kernel/v2.6/, patch-2.6.16-rc1.bz2 and 2.6.16-rc1-mm2.bz2 patches (you have them now) Apply patch-2.6.16-rc1.bz2 and 2.6.16-rc1-mm2 patches: cd linux-2.6.15 bzcat .../patch-2.6.16-rc1.bz2 | patch -p1 bzcat .../2.6.16-rc1-mm2.bz2 | patch -p1 Rename linux-2.6.15 to linux 2.6.16-rc1-mm2 for convenience Copy .config file from linux-2.6.12 kernel tree to linux-2.6.16-rc1-mm2 Also .config could be available in /boot directory, name is config-... or in /proc/config.gz file. Perform: make menuconfig (escape and yes (save) only) make as user root: make modules_install make install No error should be during all these actions. Reboot the system and choose linux-2.6.16-rc1-mm2 in startup menu ... Regards. Vladimir. Vladimir, thanks for your patience. Ok, here we go. I learn a lot with your instroctions yesterday. But most important, it worked! :-) I spend a big while in menuconfig to go through all these options and throw out all modules I identified to be be definitly unnecessary. Afterwards, I compiled and installed, also without problems. I restarted, and only my Sound was not working anymore. I guess there was an major ALSA update which makes my userspace alsatools incompatible perhaps, because I definitly built the proper modules. For now, I'll not update the userspace tools 'cause I tried to avoid issues with my former kernels... There was one big mistake, I have to correct during the next days. I thought it would help to enable ACPI_DEBUG, but /var/log/messages is flooded with debug messages now! Good news: I grep'ed for the ACPI error messages and couldn't find a new one. But I'll verify that this is correct because I was running on power line with the battery plugged into the laptop. I should get a clear statement by mid/end of this week. Thanks, Marcus Damn, a critical error in my statement above: The battery was of course _not_ plugged in! Regards, Marcus Fine, I am glad that everything is allright. So I am waiting for your final results to close the bug. Regards Vladimir. Ok, you can close that report! I compiled again, without ACPI_DEBUG this time. Definitly easier to look for ACPI messages now ;-). I inserted the battery with a running 2.6.12 Mandriva kernel. The message appear immediatly (in tail -f /var/log/messages!). I restarted the box with a plain 2.6.16-rc1-mm2 kernel and cannot reproduce the messages now. The issue seems to be fixed. Thanks for your support, Marcus |