Seems that this is not a kernel bug after all... Sorry for wasting your time!
While testing the new kernel I also decided to test with the older ones too to make sure that the problem was caused by a kernel upgrade in the first place.
I tried with mainline 3.2.9, since the problem first appeared after I upgraded from ubuntu kernel 3.2.0-18.29 (based on mainline 3.2.9) to newer one. And the bug existed there too. Then I thought that maybe I just did not notice the problem earlier and tried with mainline version 3.0.20 which was the kernel that ubuntu kernel 3.0.0-16.29 (in Oneiric) was based on. Same results: bug exists.
So I concluded that the problem is broken battery. It probably broke at the same time that I upgraded from 3.2.0-18.29 and therefore I made wrong conclusions then... sorry..
If Ashutosh has a similar problem, it's probably not related to my problem... What should be done with this bug?
Seems that this is not a kernel bug after all... Sorry for wasting your time!
While testing the new kernel I also decided to test with the older ones too to make sure that the problem was caused by a kernel upgrade in the first place.
I tried with mainline 3.2.9, since the problem first appeared after I upgraded from ubuntu kernel 3.2.0-18.29 (based on mainline 3.2.9) to newer one. And the bug existed there too. Then I thought that maybe I just did not notice the problem earlier and tried with mainline version 3.0.20 which was the kernel that ubuntu kernel 3.0.0-16.29 (in Oneiric) was based on. Same results: bug exists.
So I concluded that the problem is broken battery. It probably broke at the same time that I upgraded from 3.2.0-18.29 and therefore I made wrong conclusions then... sorry..
If Ashutosh has a similar problem, it's probably not related to my problem... What should be done with this bug?