suspend to ram problem

Hi,

I am trying to make work suspend to ram on a MSI MS-6380E with a 2.6.23 kernel.

Standby mode works.
S2ram suspend seems to work : the computer turn off and I can wake up it with the keyboard.

But when the computer wakeup, I see the video card POST on the screen, but after that the computer hangs : black screen, no working numlock.

I tried to compile PM_TRACE, but it give no result. So this means the resume hang very early.

What can I do to debug this ?

Quoted 15 lines · matthieu castet

Hi,

I am trying to make work suspend to ram on a MSI MS-6380E with a 2.6.23 kernel.

Standby mode works.
S2ram suspend seems to work : the computer turn off and I can wake up it with the keyboard.

But when the computer wakeup, I see the video card POST on the screen, but after that the computer hangs : black screen, no working numlock.

I tried to compile PM_TRACE, but it give no result. So this means the resume hang very early.

Quoted 2 lines

What can I do to debug this ?

I play with the s2_beep feature and :
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer beep
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer not beep
- adding a beep in bogus_real_magic, make the computer not beep

So the hang seems located in wakeup_start.

Quoted 15 lines · matthieu castet

Hi,

I am trying to make work suspend to ram on a MSI MS-6380E with a 2.6.23 kernel.

Standby mode works.
S2ram suspend seems to work : the computer turn off and I can wake up it with the keyboard.

But when the computer wakeup, I see the video card POST on the screen, but after that the computer hangs : black screen, no working numlock.

I tried to compile PM_TRACE, but it give no result. So this means the resume hang very early.

Quoted 2 lines

What can I do to debug this ?

I play with the s2_beep feature and :
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer beep
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer not beep
- adding a beep in bogus_real_magic, make the computer not beep

So the hang seems located in wakeup_start.

Quoted 23 lines · matthieu castet

Quoted 9 lines · matthieu castet

Hi,

I am trying to make work suspend to ram on a MSI MS-6380E with a 2.6.23 kernel.

Standby mode works.
S2ram suspend seems to work : the computer turn off and I can wake up it with the keyboard.

Quoted 8 lines

But when the computer wakeup, I see the video card POST on the screen, but after that the computer hangs : black screen, no working numlock.

I tried to compile PM_TRACE, but it give no result. So this means the resume hang very early.

What can I do to debug this ?

I play with the s2_beep feature and :
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer beep
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer not beep
- adding a beep in bogus_real_magic, make the computer not beep

Quoted 1 line

So the hang seems located in wakeup_start.

Hm. Can you add unconditional BEEP after "jne bogus_real_magic" in arch/x86/kernel/acpi/wakeup.S and see if it beeps?

Quoted 24 lines · Rafael J. Wysocki

Quoted 23 lines · matthieu castet

Quoted 9 lines · matthieu castet

Hi,

I am trying to make work suspend to ram on a MSI MS-6380E with a 2.6.23 kernel.

Standby mode works.
S2ram suspend seems to work : the computer turn off and I can wake up it with the keyboard.

Quoted 8 lines

But when the computer wakeup, I see the video card POST on the screen, but after that the computer hangs : black screen, no working numlock.

I tried to compile PM_TRACE, but it give no result. So this means the resume hang very early.

What can I do to debug this ?

I play with the s2_beep feature and :
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer beep
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer not beep
- adding a beep in bogus_real_magic, make the computer not beep

Quoted 4 lines

Quoted 1 line

So the hang seems located in wakeup_start.

Hm. Can you add unconditional BEEP after "jne bogus_real_magic" in arch/x86/kernel/acpi/wakeup.S and see if it beeps?

Hmm, maybe I know where problem could be. Try

        movl     $(wakeup_stack - wakeup_code), %esp              # Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes -- I uncovered that during rewrite.

Quoted 24 lines · Rafael J. Wysocki

Quoted 23 lines · matthieu castet

Quoted 9 lines · matthieu castet

Hi,

I am trying to make work suspend to ram on a MSI MS-6380E with a 2.6.23 kernel.

Standby mode works.
S2ram suspend seems to work : the computer turn off and I can wake up it with the keyboard.

Quoted 8 lines

But when the computer wakeup, I see the video card POST on the screen, but after that the computer hangs : black screen, no working numlock.

I tried to compile PM_TRACE, but it give no result. So this means the resume hang very early.

What can I do to debug this ?

I play with the s2_beep feature and :
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer beep
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer not beep
- adding a beep in bogus_real_magic, make the computer not beep

Quoted 4 lines

Quoted 1 line

So the hang seems located in wakeup_start.

Hm. Can you add unconditional BEEP after "jne bogus_real_magic" in arch/x86/kernel/acpi/wakeup.S and see if it beeps?

Hmm, maybe I know where problem could be. Try

        movl     $(wakeup_stack - wakeup_code), %esp              # Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes -- I uncovered that during rewrite.

Quoted 3 lines · Rafael J. Wysocki

Quoted 1 line

So the hang seems located in wakeup_start.

Hm. Can you add unconditional BEEP after "jne bogus_real_magic" in arch/x86/kernel/acpi/wakeup.S and see if it beeps?

Hmm, maybe I know where problem could be. Try

        movl     $(wakeup_stack - wakeup_code), %esp              # Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Quoted 3 lines · Rafael J. Wysocki

Quoted 1 line

So the hang seems located in wakeup_start.

Hm. Can you add unconditional BEEP after "jne bogus_real_magic" in arch/x86/kernel/acpi/wakeup.S and see if it beeps?

Hmm, maybe I know where problem could be. Try

        movl     $(wakeup_stack - wakeup_code), %esp              # Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Quoted 6 lines · Pavel Machek

Hmm, maybe I know where problem could be. Try

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

Quoted 6 lines · Pavel Machek

Hmm, maybe I know where problem could be. Try

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

Quoted 4 lines · matthieu castet

Quoted 2 lines · Pavel Machek

Hmm, maybe I know where problem could be. Try

Quoted 6 lines

Quoted 4 lines

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

Quoted 4 lines · matthieu castet

Quoted 2 lines · Pavel Machek

Hmm, maybe I know where problem could be. Try

Quoted 6 lines

Quoted 4 lines

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

Hi,

Quoted 5 lines · matthieu castet

Quoted 4 lines · matthieu castet

Quoted 2 lines · Pavel Machek

Hmm, maybe I know where problem could be. Try

Quoted 9 lines

Quoted 7 lines

Quoted 4 lines

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hi,

Quoted 5 lines · matthieu castet

Quoted 4 lines · matthieu castet

Quoted 2 lines · Pavel Machek

Hmm, maybe I know where problem could be. Try

Quoted 9 lines

Quoted 7 lines

Quoted 4 lines

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Quoted 20 lines · matthieu castet

Hi,

Quoted 4 lines · matthieu castet

Quoted 3 lines · matthieu castet

Quoted 2 lines · Pavel Machek

Hmm, maybe I know where problem could be. Try

Quoted 8 lines

Quoted 6 lines

Quoted 4 lines

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

Quoted 1 line

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Quoted 20 lines · matthieu castet

Hi,

Quoted 4 lines · matthieu castet

Quoted 3 lines · matthieu castet

Quoted 2 lines · Pavel Machek

Hmm, maybe I know where problem could be. Try

Quoted 8 lines

Quoted 6 lines

Quoted 4 lines

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

Quoted 1 line

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Quoted 13 lines

Quoted 13 lines

Quoted 6 lines

Quoted 4 lines

Quoted 1 line

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

Quoted 5 lines

Quoted 2 lines

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Yes that also break.

Hi!

Quoted 19 lines

Quoted 13 lines

Quoted 13 lines

Quoted 6 lines

Quoted 4 lines

Quoted 1 line

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

Quoted 5 lines

Quoted 2 lines

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Yes that also break.

Not sure what is going on...

Hi!

Quoted 19 lines

Quoted 13 lines

Quoted 13 lines

Quoted 6 lines

Quoted 4 lines

Quoted 1 line

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

Quoted 5 lines

Quoted 2 lines

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Yes that also break.

Not sure what is going on...

Quoted 13 lines

Quoted 13 lines

Quoted 6 lines

Quoted 4 lines

Quoted 1 line

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

Quoted 5 lines

Quoted 2 lines

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Yes that also break.

Quoted 24 lines · Rafael J. Wysocki

Quoted 23 lines · matthieu castet

Hi,

Quoted 4 lines · matthieu castet

Quoted 3 lines · matthieu castet

Quoted 2 lines · Pavel Machek

Hmm, maybe I know where problem could be. Try

Quoted 9 lines

Quoted 7 lines

Quoted 4 lines

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

Quoted 5 lines

Quoted 2 lines

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Yes that also break.

Quoted 4 lines · matthieu castet

Quoted 3 lines

Quoted 1 line

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Yes that also break.

Hmm, and what kind of machine is that?

Quoted 4 lines · matthieu castet

Quoted 3 lines

Quoted 1 line

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Yes that also break.

Hmm, and what kind of machine is that?

Quoted 7 lines

Quoted 5 lines

Quoted 4 lines

Quoted 2 lines

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Yes that also break.

Hmm, and what kind of machine is that?

processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 6
model name : AMD Athlon(tm) XP 1800+
stepping : 2
cpu MHz : 1533.490
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no

fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow ts
bogomips : 3070.84
clflush size : 32

Quoted 7 lines

Quoted 5 lines

Quoted 4 lines

Quoted 2 lines

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Yes that also break.

Hmm, and what kind of machine is that?

processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 6
model name : AMD Athlon(tm) XP 1800+
stepping : 2
cpu MHz : 1533.490
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no

fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow ts
bogomips : 3070.84
clflush size : 32

Hi!
So I assume it is some kind of desktop?

Quoted 3 lines

...if someone calls start as 0x1234:0, we are okay. But if some broken bios calls us as 0x1:0x234, we've got a problem.

Well, in that case the signature/end_signature tests below would trigger, no?

Not sure what is going on... but if you remove all the stack references, does it go up to 32-bit mode?

Looks like ss goes bonkers or the 32-bit opcodes are invalid in real mode. Matthieu, can you try "pushw %ax; popw %ax;", please?

Hi!
So I assume it is some kind of desktop?

Quoted 3 lines

...if someone calls start as 0x1234:0, we are okay. But if some broken bios calls us as 0x1:0x234, we've got a problem.

Well, in that case the signature/end_signature tests below would trigger, no?

Not sure what is going on... but if you remove all the stack references, does it go up to 32-bit mode?

Looks like ss goes bonkers or the 32-bit opcodes are invalid in real mode. Matthieu, can you try "pushw %ax; popw %ax;", please?

Hi,

Quoted 2 lines · Pavel Machek

Hi!
So I assume it is some kind of desktop?

Yes.

Quoted 6 lines

Quoted 3 lines

...if someone calls start as 0x1234:0, we are okay. But if some broken bios calls us as 0x1:0x234, we've got a problem.

Well, in that case the signature/end_signature tests below would trigger, no?

Yes, and for example the beep flag won't work.

Quoted 3 lines

Not sure what is going on... but if you remove all the stack references, does it go up to 32-bit mode?

Yes, but I end up with a kernel panic after console resume and some resume stuff.

Quoted 1 line

Looks like ss goes bonkers or the 32-bit opcodes are invalid in real

mode.

Quoted 1 line

Matthieu, can you try "pushw %ax; popw %ax;", please?

I still crash.
I also try to set ss to 0, and hardcode the stack (knowing we are loaded at 0x1000). And it crash.

I wonder if there a way to check that we are realy in real mode ?

Hi,

Quoted 2 lines · Pavel Machek

Hi!
So I assume it is some kind of desktop?

Yes.

Quoted 6 lines

Quoted 3 lines

...if someone calls start as 0x1234:0, we are okay. But if some broken bios calls us as 0x1:0x234, we've got a problem.

Well, in that case the signature/end_signature tests below would trigger, no?

Yes, and for example the beep flag won't work.

Quoted 3 lines

Not sure what is going on... but if you remove all the stack references, does it go up to 32-bit mode?

Yes, but I end up with a kernel panic after console resume and some resume stuff.

Quoted 1 line

Looks like ss goes bonkers or the 32-bit opcodes are invalid in real

mode.

Quoted 1 line

Matthieu, can you try "pushw %ax; popw %ax;", please?

I still crash.
I also try to set ss to 0, and hardcode the stack (knowing we are loaded at 0x1000). And it crash.

I wonder if there a way to check that we are realy in real mode ?

Quoted 1 line

I wonder if there a way to check that we are realy in real mode ?

Yes. In real mode bit 0 of the cr0 register should be 0.

Quoted 1 line

I wonder if there a way to check that we are realy in real mode ?

Yes. In real mode bit 0 of the cr0 register should be 0.

Quoted 24 lines · Rafael J. Wysocki

Quoted 23 lines · matthieu castet

Hi,

Quoted 4 lines · matthieu castet

Quoted 3 lines · matthieu castet

Quoted 2 lines · Pavel Machek

Hmm, maybe I know where problem could be. Try

Quoted 9 lines

Quoted 7 lines

Quoted 4 lines

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

Quoted 5 lines

Quoted 2 lines

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hm, can you place a "pushl %eax; popl %eax;" in place of the removed code and see if that breaks?

Yes that also break.

Quoted 9 lines

Quoted 9 lines

Quoted 6 lines

Hmm, maybe I know where problem could be. Try

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

Quoted 2 lines

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Quoted 9 lines

Quoted 9 lines

Quoted 6 lines

Hmm, maybe I know where problem could be. Try

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

Quoted 2 lines

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Hi!

Quoted 9 lines

Quoted 9 lines

Quoted 9 lines

Quoted 6 lines

Hmm, maybe I know where problem could be. Try

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

Quoted 8 lines

Quoted 2 lines

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

Could you try the .c wakeup? I changed it a bit, perhaps that's enough.

Quoted 2 lines

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Actually, I see a possible problem:

_start:

        cli
        cld

        /* Set up segments */
        movw    %cs,%ax
        movw    %ax,%ds
        movw    %ax,%es
        movw    %ax,%ss

        movl    $wakeup_stack_end, %esp

        /* Clear the EFLAGS */
        pushl   $0
        popfl

...if someone calls start as 0x1234:0, we are okay. But if some broken bios calls us as 0x1:0x234, we've got a problem.

Hi!

Quoted 9 lines

Quoted 9 lines

Quoted 9 lines

Quoted 6 lines

Hmm, maybe I know where problem could be. Try

        movl     $(wakeup_stack - wakeup_code), %esp              # 

Private stack is needed for ASUS bo\

instead of existing stack setup. That helped on one of my test-boxes

Thanks, I will try that.
Because clearing the flags imply pop/push in the stack it could be the problem

Quoted 8 lines

Quoted 2 lines

That doesn't help : it still crash in pushl $0.

All stack stuff in wakeup_code crash for me.
I tried to change the stack position, make sure upper bit of %esp are clear, ... nothing work.
What's are strange is that according to my x86 manual, in real mode the failure can only happen if the stack wrap which is not the case here. Any x86 guru advice ?

Could you try the .c wakeup? I changed it a bit, perhaps that's enough.

Quoted 2 lines

If I remove stack access (remove clearing flag stuff, not call to video stuff) the resume works.

Actually, I see a possible problem:

_start:

        cli
        cld

        /* Set up segments */
        movw    %cs,%ax
        movw    %ax,%ds
        movw    %ax,%es
        movw    %ax,%ss

        movl    $wakeup_stack_end, %esp

        /* Clear the EFLAGS */
        pushl   $0
        popfl

...if someone calls start as 0x1234:0, we are okay. But if some broken bios calls us as 0x1:0x234, we've got a problem.

Quoted 23 lines · matthieu castet

Quoted 9 lines · matthieu castet

Hi,

I am trying to make work suspend to ram on a MSI MS-6380E with a 2.6.23 kernel.

Standby mode works.
S2ram suspend seems to work : the computer turn off and I can wake up it with the keyboard.

Quoted 8 lines

But when the computer wakeup, I see the video card POST on the screen, but after that the computer hangs : black screen, no working numlock.

I tried to compile PM_TRACE, but it give no result. So this means the resume hang very early.

What can I do to debug this ?

I play with the s2_beep feature and :
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer beep
- echo 4 > /proc/sys/kernel/acpi_video_flags make the computer not beep
- adding a beep in bogus_real_magic, make the computer not beep

Quoted 1 line

So the hang seems located in wakeup_start.

Hm. Can you add unconditional BEEP after "jne bogus_real_magic" in arch/x86/kernel/acpi/wakeup.S and see if it beeps?