System halt during resume from S4 on Santa Rosa with Crestline

Bug #119977 reported by Kevin Wang
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

This bug occured during testing Feisty update (i386 and x86_64 Desktop)
on Santa Rosa platform with the following specs:

Santa Rosa CRB
Crestline(B0) ICH8M(B0)
Merom(B1) 2.0GHz
EM64T 4M 667MHz
2048M DDR2 667
80G Sata

Steps:
 1. Run glxgears
 2. echo ‘disk’ > /sys/power/state
 3. After system suspended, press power button

Expected result:
 1. System suspends after the command,
 2. System resumes after power button pressed, display and keyboard/mouse works well

Actual result:
 1. System halt after the command, after press the power button, the system can not start; currently I start the system by re-install the GRUB.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hi Kevin,

Please consult https://wiki.ubuntu.com/DebuggingKernelSuspend on getting debugging information. Thanks.

Changed in linux-source-2.6.20:
status: Unconfirmed → Needs Info
Revision history for this message
Kevin Wang (kevin-xuepu-wang) wrote :

Hi,

I did the test again today with the following method:

     sync
     echo 1 > /sys/power/pm_trace
     echo disk > /sys/power/state

    result: the system will be suspend after this, then push the power button, the system will be reboot, and the boot failed for the first time with the following prompt:
               booting from local disk...
               isolinux: Disk error 02, AX = 0201, drive 80

               Boot failed: press a key to retry
      then press a key, the system will be start up.

      I did two times, the same result, please find the dmesg info in the attachment

thanks
Kevin

Revision history for this message
Kevin Wang (kevin-xuepu-wang) wrote :

Hi,

I did the test again today with the following method:

     sync
     echo 1 > /sys/power/pm_trace
     echo disk > /sys/power/state

    result: the system will be suspend after this, then push the power button, the system will be reboot, and the boot failed for the first time with the following prompt:
               booting from local disk...
               isolinux: Disk error 02, AX = 0201, drive 80

               Boot failed: press a key to retry
      then press a key, the system will be start up.

      I did two times, the same result, please find the dmesg info in the attachment

thanks
Kevin

Revision history for this message
Kevin Wang (kevin-xuepu-wang) wrote :

Hi,

I did the test again today with the following method:

     sync
     echo 1 > /sys/power/pm_trace
     echo disk > /sys/power/state

    result: the system will be suspend after this, then push the power button, the system will be reboot, and the boot failed for the first time with the following prompt:
               booting from local disk...
               isolinux: Disk error 02, AX = 0201, drive 80

               Boot failed: press a key to retry

      then press a key, the system will be start up.

      I did two times, the same result, please find the dmesg info in the attachment

thanks
Kevin

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Thanks for the logs. (FYI, we seemed to have gotten 3 copies of that message -- not a problem in it self)

Changed in linux-source-2.6.20:
status: Incomplete → Confirmed
Revision history for this message
Rolla Selbak (rolla-n-selbak) wrote :

Kevin, is this fixed in Gutsy Tribe 3?

Revision history for this message
Kevin Wang (kevin-xuepu-wang) wrote :

It is OK in Tribe 3

thanks
Kevin

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

This bug is filed against 2.6.20 (which is Feisty) and the issues has been reported fixed in Gutsy (tribe 3). Are we seeking a backport to Feisty or shall we close it as fixed?

Changed in linux-source-2.6.20:
status: Confirmed → Fix Released
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Ooops, it seems I did set it to fixed there. Please reopen if that was wrong.

Revision history for this message
Rolla Selbak (rolla-n-selbak) wrote :

I think we're OK since this is fixed in Gutsy. Backport isn't needed imo. Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.