Bug 469580 - Tyan Tomcat K8E reboots after resume from suspend
Summary: Tyan Tomcat K8E reboots after resume from suspend
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 10
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: John Feeney
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-02 21:00 UTC by Joachim Frieben
Modified: 2013-01-10 07:08 UTC (History)
2 users (show)

Fixed In Version: kernel-2.6.27.12-170.2.5.fc10.x86_64
Clone Of:
Environment:
Last Closed: 2009-01-25 18:27:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg with kernel 2.6.27.4-69.fc10.x86_64 (33.38 KB, text/plain)
2008-11-02 21:00 UTC, Joachim Frieben
no flags Details
Trailing entries in /var/log/messages after failed resume from suspend (1.54 KB, text/plain)
2008-11-07 09:15 UTC, Joachim Frieben
no flags Details
pm-suspend.log (4.11 KB, text/plain)
2008-11-07 09:16 UTC, Joachim Frieben
no flags Details
dmesg with kernel 2.6.28-0.113.rc7.git5.fc11.x86_64 (35.63 KB, text/plain)
2008-12-07 14:02 UTC, Joachim Frieben
no flags Details

Description Joachim Frieben 2008-11-02 21:00:03 UTC
Created attachment 322237 [details]
dmesg with kernel 2.6.27.4-69.fc10.x86_64

Description of problem:
After suspending (apparently) successfully, a Tyan Tomcat K8E does not resume properly. Instead, the system reboots.

Version-Release number of selected component (if applicable):
kernel-2.6.27.4-69.fc10.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Suspend from GDM or from within a GNOME session.
2. Press power button to resume operation.
  
Actual results:
The system reboots.

Expected results:
The system resumes.

Additional info:
- Resume used to work for x86_64 F9 w/o updates, and it still does so
  when suspend/resume are executed running the original F9 i386 live
  CD [I have not tested the x86_64 version though].
- Suspend stopped to work in F9 x86_64 about 3 months ago.
- After installing F10 Beta x86_64 and subsequent snapshots, the system
  also reboots upon resume both for installed system and live media
  [both i386 and x86_64]. I thus suspect the update to some recent 2.6.x
  kernel to be the culprit.
- Executing pm-suspend with all available quirks still leads to a reboot.
- The video device is an ATI X800 [R430] PCIe card using the "nomodeset"
  option.

Comment 1 Joachim Frieben 2008-11-07 09:15:28 UTC
Created attachment 322833 [details]
Trailing entries in /var/log/messages after failed resume from suspend

As of current kernel-2.6.27.4-79.fc10.x86_64, there is some progress: instead of a plain reboot after triggering the resume process, one know hears a dozen of times the GNOME sound "Window minimised" before starting over. I have enabled sound effects to be played when buttons are clicked.
Moreover, there is an additional entry in /valog/messages now stemming from the resume process, "Freezing user space processes ... (elapsed 0.00 seconds) done."

Comment 2 Joachim Frieben 2008-11-07 09:16:28 UTC
Created attachment 322834 [details]
pm-suspend.log

Comment 3 Bug Zapper 2008-11-26 04:39:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Joachim Frieben 2008-12-06 21:47:38 UTC
Current status of this issue:

  kernel-2.6.27.7-135.fc10.x86_64              failure
  kernel-2.6.28-0.113.rc7.git5.fc11.x86_64   **success**

F10 update kernels lead to emission of some distorted (system (?)) sound while executing the suspend command. Execution of suspend by the "rawhide" kernel, however, is not accompanied by such. Relevant modules are:

  snd_intel8x0           98736  3 
  snd_ac97_codec        180968  1 snd_intel8x0
  ac97_bus               67456  1 snd_ac97_codec
  snd_seq_dummy          68740  0 
  snd_seq_oss            96976  0 
  snd_seq_midi_event     72328  1 snd_seq_oss
  snd_seq               120008  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
  snd_seq_device         72988  3 snd_seq_dummy,snd_seq_oss,snd_seq
  snd_pcm_oss           108304  0 
  snd_mixer_oss          80520  1 snd_pcm_oss
  snd_pcm               142000  3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
  snd_timer              87328  2 snd_seq,snd_pcm
  snd                   127016  16 snd_intel8x0,snd_ac97_codec,snd_seq_dummy,
                                snd_seq_oss,snd_seq,snd_seq_device,
                                snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
  soundcore              72336  1 snd
  snd_page_alloc         74768  2 snd_intel8x0,snd_pcm

The sound system is included into the nForce pro chipset:

  00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio
  Controller (rev a2)

The issue is probably solved once kernel 2.6.28 final hits F10 updates.

Comment 5 Joachim Frieben 2008-12-07 14:02:36 UTC
Created attachment 326040 [details]
dmesg with kernel 2.6.28-0.113.rc7.git5.fc11.x86_64

New entry in dmesg file:

 "Phoenix BIOS detected: BIOS may corrupt low RAM, working it around."

Comment 6 Joachim Frieben 2008-12-14 19:05:50 UTC
F10-updates kernel-2.6.27.9-155.fc10.x86_64 fails like earlier ones.

Comment 7 Joachim Frieben 2008-12-18 14:05:29 UTC
After reverting the system to current F10 w/updates, also 2.6.28 prerelease kernels fail to resume:

  xorg-x11-server-1.5.3-6.fc10.x86_64,
  xorg-x11-drv-ati-6.9.0-62.fc10.x86_64 plus

  kernel-2.6.28-0.129.rc8.git2.fc11.x86_64: ##failure##
  kernel-2.6.27.9-163.fc10.x86_64:          ##failure##

Comment 8 Joachim Frieben 2009-01-14 08:14:08 UTC
Resume from suspend still fails for F10 w/updates plus kernel-2.6.28-4.fc10.x86_64 whereas it used to work when "rawhide" and kernel-2.6.28-0.113.rc7.git5.fc11.x86_64 were installed on the same system about one month ago.

Comment 9 Joachim Frieben 2009-01-25 18:27:49 UTC
Tried for current F10 w/updates including kernel-2.6.27.12-170.2.5.fc10.x86_64, and the system does resume successfully from suspend.


Note You need to log in before you can comment on or make changes to this bug.