Resume from mem state == Reboot (Averatec)

DISCUSSION Jason Dagit 2 participants 4 messages Mar 14, 2005 – Mar 22, 2005 2 messages not in the archive ACPI

Share & tools

Jason Dagit

author

2005-03-14 20:28 UTC #0 lore raw

My laptop is an Averatec AV3250HX-01. I'm currently using kernel version 2.6.10 (I tried 2.6.11.3 a little as well). If I do:

echo -n "mem" >/sys/power/state

The laptop appears to suspend to ram correctly. But the laptop will not respond to any input (except the powerbutton) after it has suspended. When I hit the power button the laptop acts as though it has been off and restarts, the bios posts and I endup at the lilo prompt. If I do the same sort of thing in windows instead of linux, then any button will wake the laptop including the powerbutton. So I know the laptop is fine.

I would like to debug/fix this problem. After a fair bit of googling it would appear than everyone with this model of laptop has the some problem. I'm not very experienced with debugging the kernel, and I'm even less experienced with acpi. What should I do to find out more about this? Are there commands I can run and information to provide the list with to get to the next step in finding the problem? If I include my dsdt or other information what is the best way to send that info to the list? Should I use an email attachment?

Thanks,
Jason

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

A message that is not in the archive (sent off-list or not yet received): 87k6oaug4a.fsf-mMfbam+mt929kzlf/[email protected]

Matthew Garrett

2005-03-14 22:45 UTC #2 lore raw

Quoted 8 lines · Jason Dagit

I would like to debug/fix this problem. After a fair bit of googling it would appear than everyone with this model of laptop has the some problem. I'm not very experienced with debugging the kernel, and I'm even less experienced with acpi. What should I do to find out more about this? Are there commands I can run and information to provide the list with to get to the next step in finding the problem? If I include my dsdt or other information what is the best way to send that info to the list? Should I use an email attachment?

This is likely to be the same problem as
http://bugzilla.kernel.org/show_bug.cgi?id=3691

Signature · 9 lines

Matthew Garrett | [email protected]



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Jason Dagit

author

2005-03-21 06:45 UTC #3 lore raw

Quoted 2 lines · Matthew Garrett

This is likely to be the same problem as
http://bugzilla.kernel.org/show_bug.cgi?id=3691

Has anyone made progress on this bug? I've been trying various things on my system to get an understanding of the problem. But I don't really know what I'm doing and I could really use some guidance.

What sort of information would be useful in troubleshooting this? I've attached all the diagnostic output I know how to generate to the bug listed above, but there must be something else I can do or try.

Today when I was poking around I did discover in tbconvert.c inside the function acpi_tb_build_common_facs that acpi_gbl_common_fACS.firmware_waking_vector is 0x0de8000c. But in acpi_pm_prepare the function acpi_set_firmware_waking_vector is given a physical address of 0x00001000, which comes from a virtual address of 0xc0001000. Is there something I can inspect or disassemble to find out what the firmware_waking_vector should be?

Thanks,
Jason

A message that is not in the archive (sent off-list or not yet received): 87eke94hul.fsf-mMfbam+mt929kzlf/[email protected]

Jason Dagit

author

2005-03-22 08:12 UTC #5 lore raw

Quoted 4 lines · Jason Dagit

Quoted 2 lines · Matthew Garrett
This is likely to be the same problem as
http://bugzilla.kernel.org/show_bug.cgi?id=3691

I made a discovery today. This bug says the following:
http://bugme.osdl.org/show_bug.cgi?id=3586

---- Begin Paste ----
Code from arch/i386/kernel/acpi/wakeup.S:
[...]
mov $(wakeup_stack - wakeup_code), %sp # Private stack is needed for ASUS board
movw $0x0e00 + 'S', %fs:(0x12)

pushl $0 ###THIS LINE CAUSES REBOOT! # Kill any dangerous flags
popfl

movl real_magic - wakeup_code, %eax
[...]

Commenting out pushl $0 and popfl wakeup code goes on until another issue blocks it later (more on this to be added as soon as we point something out on the acpi-devel mailing list)
---- End Paste ----

I tried commenting out those lines (both the pushl and popfl) and my laptop suspends and resumes! The screen is blank when the machine resumes, but I can toggle capslock and if I type "find /" the hard drive light comes on. So it would appear that the machine is setting the firmware_wake_vector correctly, but something about that push and pop is not good for this machine. Now I'm off to debug the video resume problems, which appears to be a pretty common problem with suspend/resume.

I hope this is helpful to others. Matthew can you try this on your laptop?

Thanks,
Jason