Hi Juha, Juha Jäykkä wrote:
> What is the status of the fix from Intel? I have the same problem since > upgrading to 3.x series and it is VERY annoying - only way I can fix it is > rebooting the kernel, so it really seems a kernel bug. Hibernating the system > and doing a full power-off (unplug AC, remove battery, wait 60 seconds – this > should do it) the laptop does NOT fix it, so I concur: the kernel must retain > some bogus information somewhere since the hw has definitely lost its status > info. Please provide: - steps to reproduce, assuming I had the same hardware - expected result, actual result, and how the difference indicates a bug (should be simple enough in this case) - how reproducible it is (100% of the time? 50%?) - which kernel versions you have tested, and results with each - full "dmesg" output from booting and reproducing the bug, as an attachment - any other weird observations or workarounds I believe the best way to move forward would be to take this report upstream to a public mailing list. So the purpose of these questions is to collect data on what's known so far as a starting point. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120211193827.GE6944@burratino
