Bug 10131

Created attachment 15067 [details]
lspci

Created attachment 15068 [details]
cpuinfo

Created attachment 15069 [details]
dmesg after fresh boot

Created attachment 15070 [details]
acpidump-bin

Do you know if any earlier kernel versions worked OK?

No. This will be alot of work becouse i shortly upgrated my system from nonsmp with celeron d to smp with pentium d

I haw less problem with celeron d or with kernel option nosmp

kernel 2.6.23 olmost working... i mean, it can randomly wake up after short sleep ( like 1 min ) and newer after long one.
here is dmesg with 2.6.23 from Bug 9930
http://bugzilla.kernel.org/attachment.cgi?id=14838&action=view

(In reply to comment #0)
> PC can't wakeup if smp is enabled. Workaround is to boot with nosmp.
Please boot with nohz=off with/without highres=off and see if it can resume back.

Normally display will be disabled after resume, but with options nohz=off and/or highres=off and/orr hpet=disabled and kernel will oops alot. I can't get proper log of oops: 1. after resume ttyS0 do not send any thing ( or becouse i get on client notebook ...irq4 warning ). So i can't debug it with COM. 2. thirst opps is not on the screan, i can't get a picture.

How is about kdump, i newer did it before. Will it work with suspend/resume and should i configure kernel for it with hpet, nohz, loapic enabled like host kernel do?

I made some more tests. I have 2GB of RAM, if use only 1GB it working. There is 2 ram blocks each 1GB, they installed to use dualchannel mode but it don't make eny difference. I tested it with memtest and no errors found.

So now, known working konfigurations are: nosmp or mem=1G or unistall one memory block

I tryed agp=off but this oopsed kernel.

Latest "working" kernel is 2.6.21. This kernel can resume and go to xorg, but dmesg give:

[  140.432000] kernel BUG at mm/mmap.c:1999!
[  140.432000] invalid opcode: 0000 [#1]
[  140.432000] PREEMPT SMP 
.......

Created attachment 15140 [details]
dmesg-2.6.21 "working" with oops

Hi, Alexey 
    Will you please attach the output of lspci -vvxxx and acpidump?
    Thanks.

Created attachment 15196 [details]
lscpi -vvxxx

Created attachment 15197 [details]
acpidump

Hi, Alexey 
   Will you please set "CONFIG_PM, CONFIG_PM_TRACE, CONFIG_ACPI_DEBUG" in kernel configuration and do the following test? (Please use the latest kernel, 2.6.24.3)
    a. boot the system with the option of "acpi_sleep=s3_bios libata.noacpi=1 initcall_debug" 
    b. echo 1 > /sys/power/pm_trace 
    c. echo mem > /sys/power/state to enter suspend state
    d. press power button to confirm whether the system can be waked . 
    e. If the system can't be waked, please restart the system 
   
    After test is finished, please attach the output of dmesg.
    Thanks.
   

Created attachment 15200 [details]
dmesg 2.6.24.3 debug

Magic number: 0:340:984

kernel 2.6.24.4 will cleanly resume after of suspend 2-3 min. After 30 min of suspend it crash on resume.

Hi, Alexey
   Thanks for the test. 
   It seems that the system can be waked if only suspend 2-3 mins.
   Will you please do the test as required in comment #15 after the system is suspended for 30 mins?
   
   Thanks.
   

Sorry, it seems to be my mistake. I autmaticly used /etc/acpi/susped.sh instead of of echo mem > /sys/power/state. With last one it working perfektly.

some how this script /etc/acpi/susped.sh make kernel oops on SMP system. But, i think, this is other bug.

Now the laptop can be resumed from S3 state normally when "echo mem >/sys/power/state" is used.  

The bug will be rejected.