Comment 21 for bug 1228406

On Sun, Oct 27, 2013 at 01:25:26AM -0000, Furkan Alaca wrote:
> It's been another 10 days since I last posted, and I still haven't
> encountered this bug again. I have no idea if it was the new kernel
> version or the BIOS that "fixed" it - I updated them both within a
> couple of days of eachother, so I am running the latest BIOS that
> Christopher linked to. Of course it could also be that I'm on a lucky
> streak, since I've never been able to consistently replicate the bug -
> but before I updated the BIOS + kernel it was happening on approximately
> a weekly basis.

> I sort of doubt that the BIOS would be the issue though (but you never
> know), since I've had this laptop since April 2010 and I've never faced
> the issue while running Windows 7 (I just switched over to Ubuntu in
> May).

Well, I've had this one since October 2010, always running Ubuntu, and it
didn't start having problems until September.

Maybe there's code in the BIOS that starts misbehaving only after a certain
date. I could try setting the clock back to test.

> Steve, I tried to replicate your results by running echo mem >
> /sys/power/state and pm-suspend on AC power while docked, and then pm-
> suspend again while undocked, and it seems to work fine. Do you have any
> further detailed suggestions on how I could try to replicate the issue?

No, if the problem isn't reproducible for you that way, then you seem to be
unaffected. It's quite possible that the problem is caused by a hardware
failure on my machine.