Bug 7290 - Fails to resume from S3
Summary: Fails to resume from S3
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: acpi_power-sleep-wake
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-09 02:43 UTC by mugilan
Modified: 2007-10-06 14:23 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.15
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description mugilan 2006-10-09 02:43:17 UTC 
Most recent kernel where this bug did not occur:
Distribution:
Hardware Environment:
Software Environment:
Problem Description:

Steps to reproduce:


Unable to resume from S3 in Fedora linux 2.6.15.  while going to sleep(s3)  
the firmware wake vector should be filled by OS (linux). but in our case it is 
not filled (value 0)
Comment 1 Diego Calleja 2006-10-09 10:41:13 UTC 
Can you tell if this problem is still in 2.6.18? 2.6.15 is kinda old with the
current development speed
Comment 2 mugilan 2006-10-10 07:55:34 UTC 
ya, i am facing the problem in 2.6.18 kernel version also
Comment 3 mugilan 2006-11-02 00:00:22 UTC 

When i debugged the kernel using kdb, i stopped inside the 
function "acpi_set_firmware_waking_vector" in "\linux-2.6.16.13
\drivers\acpi\hardware". i can able the assembly code, i have an istruction.
mov ecx,dword ptr [0xc1312800]. i am using only 256 ram.
 
this is virtual addrss. can anyone tell me how should i calculate the 
physcial  address of that corresponding virt address.

Actually the Waking_vector_address is filled in this function by OS. 
Its getting filled in Virtual address. But when i saw the physical address 
corresponding to that virtual address, its not get filled. Could any one 
suggest how to proceed next..
Comment 4 Len Brown 2007-09-06 15:27:33 UTC 
Is this still a problem in linux-2.6.22.stable or later?
Comment 5 Adrian Bunk 2007-10-06 14:23:22 UTC 
Please reopen this bug if it's still present with kernel 2.6.22.
Note You need to log in before you can comment on or make changes to this bug.