Comment 51 for bug 160763

Hi again,

I'm using I've tried several things since last time. I'm using ubuntu 9.04 64 bits...

- Tried using quirks, but didn't try all of them.
- Tried using some grub kernel options (taken from http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-advanced.html):
    * maxcpus=1
    * noapic
    * nolapic
    * noapic nolapic
    * nolapic_timer
    * nohz=off
    * ec_burst=1
- Tried debugging the suspend proccess, but all I got was:

mrrusof@mrrusof-laptop:~$ cat dmesg.txt | grep "hash matches"
[ 3.995026] hash matches /build/buildd/linux-2.6.28/drivers/base/power/main.c:390

and

mrrusof@mrrusof-laptop:~$ cat dmesg.txt | grep "resume"
[ 5.203097] PM: Starting manual resume from disk
[ 14.361930] synaptics was reset on resume, see synaptics_resume_reset if you have trouble on resume

I cannot find any clue about a driver interfering with the resume proccess.

- I can hibernate. Suspension works once, but not twice in a row. However, if I alternate hibernations with suspensions, the system resumes after both hibernation and suspension.

- I see that Maxim Letvisky got some hint about modifying kernel itself. I wonder if he tried (and in that case, succeeded). See http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-09/msg06756.html .

I just need to be pointed in the right direction to bring this bug down, come on guys!