Suspend only works once, dmesg shows errors about sata disk

Bug #510246 reported by seku
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I have a problem with suspend only working once. On second try my hard disks and displays go off but come back again after some minutes. After that my sata disk does not work anymore.

I installed karmic on ide hard disk and tried suspend again and got many errors of sata disk in dmesg.

sd 0:0:0:0: [sda] START_STOP FAILED
...
PM: Device 0:0:0:0 failed to suspend: error 134217730

If I take my sata disk off my computer suspend works without problem.

My motherboard is Asus K8V deluxe and sata controller
00:08.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02)
and sata hard disk is Samsung 640GB

ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jettis 1710 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'V8237'/'VIA 8237 with AD1980 at 0xc800, irq 22'
   Mixer name : 'Analog Devices AD1980'
   Components : 'AC97a:41445370'
   Controls : 53
   Simple ctrls : 35
Date: Wed Jan 20 18:39:02 2010
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=e1a2bbac-0d56-41d7-800a-7ed41eb80533
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux-image-2.6.31-18-generic 2.6.31-18.55
ProcCmdLine: root=UUID=a702ebf6-f4d5-42f2-a63b-3e903770235a ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=fi_FI.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-18-generic N/A
 linux-firmware 1.26
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-18-generic i686
XsessionErrors:
 (gnome-settings-daemon:1726): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1837): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1826): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:1825): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -4 and height 24
 (firefox:1975): GLib-WARNING **: g_set_prgname() called multiple times
dmi.bios.date: 09/02/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1012.001
dmi.board.name: K8V
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1012.001:bd09/02/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnK8V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
seku (jettis) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi seku,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 510246

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kernel-suspend
tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
seku (jettis) wrote :

Suspend doesn't work in lucid. Crashes also when trying to suspend second time.

Revision history for this message
seku (jettis) wrote :
Revision history for this message
Robert Moerland (veel-mail) wrote : apport-collect data

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
Uname: Linux 2.6.28-18-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Robert Moerland (veel-mail) wrote :

I have the exact same issue with ubuntu jaunty, with (slightly?) different hardware: a Promise PDC20375 (SATA150 TX2plus) controller. I've attached the dmesg output after the first and second (attempt at a ) suspend. The second time, the graphics are turned off and a single blinking cursor is visible. After a while, text that also appears in dmesg is shown on-screen (still console) and I can switch to a graphical desktop by pressing Alt+F7. I ran apport-collect but apparently it didn't really add anything useful, or so it seems.

My jaunty machine has performed excellently at suspend/resume, until I added this promise controller with a sata disk. I have tried to test this with the live image of Ubuntu 10.04, but I ran into other suspend/resume issues (like a black screen on wakeup), which made testing difficult with the live cd. Therefore, I upgraded my jaunty machine (via karmic) to 10.04 but still I had additional suspend/resume issues that could be caused by other things. I am now back to jaunty again, but I hope that my input is useful nevetheless.

Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty

Linux tvgebakje 2.6.28-18-generic #60-Ubuntu SMP Fri Mar 12 04:40:52 UTC 2010 i686 GNU/Linux

Revision history for this message
Robert Moerland (veel-mail) wrote :
Revision history for this message
Robert Moerland (veel-mail) wrote :
seku (jettis)
tags: removed: needs-upstream-testing
Revision history for this message
kundor (kundor) wrote :

I have the same symptoms on Kubuntu Lucid, amd64, kernel "2.6.32-22-generic #33-Ubuntu SMP". I also have an Asus K8V Deluxe motherboard, with a Promise "PDC20378 (FastTrak 378/SATA 378) (rev 02)" (according to lspci) SATA controller.

Suspending once works. After resume, everything seems fine. The following message appears in "kern.log" at resume (identical timestamps snipped):
May 16 08:57:37 chade kernel: [23999.040031] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May 16 08:57:39 chade kernel: [23999.040038] ata6.00: failed command: READ DMA EXT
[23999.040045] ata6.00: cmd 25/00:08:c0:ee:dc/00:00:39:00:00/e0 tag 0 dma 4096 in
[23999.040047] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[23999.040050] ata6.00: status: { DRDY }
[23999.040057] ata6: hard resetting link
[23999.550041] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[23999.621420] ata6.00: configured for UDMA/133
[23999.621425] ata6.00: device reported invalid CHS sector 0
[23999.621430] ata6: EH complete

If I, later, try to suspend again, the screen goes black, but the computer does not turn off; after several minutes the screen comes back on at the console, where this message is displayed:

PM: some devices failed to suspend: error 13421773034217730
ata6.00: status { DRDY }
ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata6.00: failed command: STANDBY IMMEDIATE
ata6.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
 res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

(copied by hand, typos possible).
It sat there for at least 20 minutes. The machine was not responsive to any key combos or the soft-off button, so eventually I had to "hard-off."

Revision history for this message
kundor (kundor) wrote : apport information

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: kundor 1579 F.... kmix
 /dev/snd/controlC0: kundor 1579 F.... kmix
 /dev/snd/pcmC0D0p: kundor 1531 F...m knotify4
 /dev/snd/timer: kundor 1531 f.... knotify4
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'CS46xx'/'Sound Fusion CS46xx at 0xfda00000/0xfd900000, irq 18'
   Mixer name : 'Cirrus Logic CS4297A rev 4,Cirrus Logic CS4294 rev 5'
   Components : 'AC97a:43525914 AC97a:4352592d'
   Controls : 71
   Simple ctrls : 45
Card1.Amixer.info:
 Card hw:1 'V8237'/'VIA 8237 with AD1980 at 0x1000, irq 22'
   Mixer name : 'Analog Devices AD1980'
   Components : 'AC97a:41445370'
   Controls : 53
   Simple ctrls : 35
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=e89f615c-92bc-49c8-96ae-9bb5bebafdb9
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: root=UUID=521392e1-f5af-4194-9ea3-8ca2476ab07a ro splash quiet
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Regression: No
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:

Tags: lucid graphics needs-upstream-testing
Uname: Linux 2.6.32-22-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WifiSyslog:

dmi.bios.date: 06/16/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1011.002
dmi.board.name: K8V
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1011.002:bd06/16/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnK8V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

tags: added: apport-collected
Revision history for this message
kundor (kundor) wrote : AlsaDevices.txt

apport information

Revision history for this message
kundor (kundor) wrote : AplayDevices.txt

apport information

Revision history for this message
kundor (kundor) wrote : ArecordDevices.txt

apport information

Revision history for this message
kundor (kundor) wrote : BootDmesg.txt

apport information

Revision history for this message
kundor (kundor) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
kundor (kundor) wrote : Card0.Codecs.codec97.0.ac97.0.0.txt

apport information

Revision history for this message
kundor (kundor) wrote : Card0.Codecs.codec97.0.ac97.0.0.regs.txt

apport information

Revision history for this message
kundor (kundor) wrote : Card0.Codecs.codec97.0.ac97.1.1.txt

apport information

Revision history for this message
kundor (kundor) wrote : Card0.Codecs.codec97.0.ac97.1.1.regs.txt

apport information

Revision history for this message
kundor (kundor) wrote : Card1.Amixer.values.txt

apport information

Revision history for this message
kundor (kundor) wrote : Card1.Codecs.codec97.0.ac97.0.0.txt

apport information

Revision history for this message
kundor (kundor) wrote : Card1.Codecs.codec97.0.ac97.0.0.regs.txt

apport information

Revision history for this message
kundor (kundor) wrote : CurrentDmesg.txt

apport information

Revision history for this message
kundor (kundor) wrote : Lspci.txt

apport information

Revision history for this message
kundor (kundor) wrote : Lsusb.txt

apport information

Revision history for this message
kundor (kundor) wrote : PciMultimedia.txt

apport information

Revision history for this message
kundor (kundor) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
kundor (kundor) wrote : ProcInterrupts.txt

apport information

Revision history for this message
kundor (kundor) wrote : ProcModules.txt

apport information

Revision history for this message
kundor (kundor) wrote : UdevDb.txt

apport information

Revision history for this message
kundor (kundor) wrote : UdevLog.txt

apport information

Revision history for this message
kundor (kundor) wrote :

The preceding apport-collect information was after one suspend/resume cycle.
The Promise SATA TX2plus controller (Promise BIOS version 1.00.0.33) has two disks on it:
A Western Digital 500 GB on which Kubuntu is installed, WD5000AAKS, known to the logs as ata6.00 or ATA-7;
A Seagate 1.5 TB, ST31500341AS, known to the logs as ata5.00 or ATA-8.
The error messages about g15daemon are unrelated.
Sound also fails after resume, but I believe that is an unrelated issue. (There are known issues and kernel patches for my sound card, cs46xx.)
For what it's worth, I had the same symptoms (suspend only works once, dmesg shows errors about SATA disks on the promise controller) in another distribution, with kernel versions from (at least) 2.6.24 to 2.6.28.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Fisslefink (erin-simonds) wrote :

Same exact behavior with the Asus P4P800-E Deluxe motherboard: First suspend and first resume work as expected. Second suspend causes hard disks to spin down and display to go blank, but does not shut down fans or CPU ... computer non-responsive except for hard reboot (even Alt+SysRq+REISUB does nothing).

This is with Maverick (Ubuntu 10.10) and kernel 2.6.35-22-generic #35-Ubuntu SMP.

I also tried today's mainline kernel 2.6.37-020637rc2-generic #201011160905 SMP but got the same result.

Unmounting the drive on the RAID controller in linux (umount /dev/sdc1) has no effect.

This bug occurs whether the Promise RAID controller is set to IDE or RAID mode.

The only way I was able to get multiple suspend/resume cycles to work was by disabling the Promise RAID controller in "Onboard Devices" menu. On my motherboard, there are two RAID SATA ports driven by the Promise FastTrak controller, and two SATA ports driven by the Intel ICH5R bridge. Since I only need two hard drives, and I don't mind running them in IDE (i.e. not RAID) mode, I connected both to the Intel ICH5R ports, and disabled the RAID controller in BIOS. Under this configuration, suspend to ram (S3) and resume work through many cycles.

IMHO: This bug should not be expired -- there is plenty of logs and I've now tested it against the mainline kernel. Maybe the devs have no idea how to fix it, but that's no excuse!

Revision history for this message
seku (jettis) wrote :

Just tried new Natty alpha 2. Still crashes when trying to suspend. I tried 2.6.38-1-generic and mainline 2.6.38-999-generic #201102040905 kernels. Only thing that has changed is kernel doesn't come back from crash so I couldn't get any logs about it. Tried also serial console but it didn't show anything about crash.

Changed in linux (Ubuntu):
status: Expired → New
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: b73a1py79
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
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.