On Sun, 1 Jan 2012 01:42:36 -0600 Jonathan Nieder <firstname.lastname@example.org> wrote: > Passed upstream. But now I notice that there has been some upstream > work in this area recently (v3.2-rc7~23^2~1, rtc: m41t80: Workaround > broken alarm functionality, 2011-12-12). > > Please test v3.2-rc7 from experimental and let the upstream folks > know how it fares (by replying-to-all on the other side thread). Hello, Thank you for looking into this and for the information about the 3.2 possible fix. Unfortunately I can't try that kernel easily at the moment, as there doesn't seem to be an orion5x variant of the package in experimental. Some more info: - During my testing I have found that after booting with a 'bad' kernel, a full power-off of the device including disconnecting the power supply from the mains might be required, before a 'good' kernel will work properly. - This might have been mentioned, but the main reason this bug concerns me, is that the temperature sensor and the fan PWM control do not work on the 'bad' kernels (i.e. it's not just the periodic dmesg error). The fan does not turn on, which risks overheating the device and/or drives. -- With respect, Roman ~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Stallman had a printer, with code he could not see. So he began to tinker, and set the software free."
Description: PGP signature