WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x7c/0x80() with kern.log mesages ata2: softreset failed (device not ready), ata2.00: qc timeout (cmd 0xec), ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Bug #350609 reported by sam tygier
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Some systems are having this issue related to certain combinations of Disk Controllers and Disks. Bug #286672 identifies a problematic combination. This one could be the same or related.

== Original Report ==
got this on resume from suspend.

seems like Bug #329254 so i guess it is just a warning that resume was too slow.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
DistroRelease: Ubuntu 9.04
Failure: oops
MachineType:

NonfreeKernelModules: openafs
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcCmdLine: root=UUID=b47b2a54-a928-47f0-905a-f0adca106bc6 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x7c/0x80()

Revision history for this message
sam tygier (samtygier) wrote :
Revision history for this message
Johan Ehnberg (johan-ehnberg) wrote :

I'm getting the same error. I wonder why they produce it as an oops, as it causes a lot of "false" bugs. Essentially, there is a bug either in the kernel (for false oopses which cause serious kernel warnings) or in kerneloops and other helper apps for not understanding them.

Revision history for this message
Mozg (andrei-arhont) wrote :

I get this on Jaunty Beta pretty much every time I suspend/resume the laptop.

Revision history for this message
Matt Zimmerman (mdz) wrote :

<apw> mdz thats another which really should not be a warning at all

Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Andres Mujica (andres.mujica) wrote :

actually this is not a false positive

according to TJ's data analysis when the resume takes more than 12seconds is symptom of something else.

In this case tha SATA devices seem to have triggering the problem.

4.582566] serial 00:02: activated
[ 9104.583847] parport_pc 00:03: activated
[ 9104.583975] sd 0:0:0:0: [sda] Starting disk
[ 9113.752007] ata2: softreset failed (device not ready)
[ 9113.752013] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9113.752021] ata1: softreset failed (device not ready)
[ 9113.752026] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9118.748009] ata2.00: qc timeout (cmd 0xec)
[ 9118.748014] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 9118.748015] ata2.00: revalidation failed (errno=-5)
[ 9118.748023] ata1.00: qc timeout (cmd 0xec)
[ 9118.748027] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 9118.748028] ata1.00: revalidation failed (errno=-5)
[ 9119.232011] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9119.232021] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9119.237000] ata1.00: configured for UDMA/133
[ 9119.240820] ata2.00: configured for UDMA/133
[ 9119.252058] sd 0:0:0:0: [sda] 293046768 512-byte hardware sectors: (150 GB/139 GiB)
[ 9119.252077] sd 0:0:0:0: [sda] Write Protect is off
[ 9119.252079] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 9119.252102] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9119.256033] sd 1:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
[ 9119.256046] sd 1:0:0:0: [sdb] Write Protect is off
[ 9119.256048] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 9119.256070] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9119.265230] sd 1:0:0:0: [sdb] Starting disk
[ 9119.856015] usb 2-2: reset low speed USB device using uhci_hcd and address 2
[ 9120.166352] PM: resume devices took 16.888 seconds
[ 9120.166359] ------------[ cut here ]------------
[ 9120.166361] WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x7c/0x80()
[ 9120.166362] Component: resume devices
[ 9120.166363] Modules linked in: openafs(P) binfmt_misc radeon drm bridge stp bnep video output input_polldev lp snd_pcm_oss snd_hda_intel snd_mixer_oss arc4 ecb snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi ath5k snd_seq_midi_event snd_seq mac80211 snd_timer snd_seq_device psmouse iTCO_wdt iTCO_vendor_support snd tpm_infineon led_class ppdev parport_pc i5000_edac tpm soundcore serio_raw pcspkr edac_core tpm_bios snd_page_alloc cfg80211 shpchp parport usbhid ohci1394 ieee1394 e1000e raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear fbcon tileblit font bitblit softcursor
[ 9120.166398] Pid: 28270, comm: pm-suspend Tainted: P W 2.6.28-11-generic #38-Ubuntu
[ 9120.166399] Call Trace:
[ 9120.166405] [<ffffffff80250927>] warn_slowpath+0xb7/0xf0

description: updated
tags: added: test-suspend-seconds
summary: WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177
- suspend_test_finish+0x7c/0x80()
+ suspend_test_finish+0x7c/0x80() with kern.log mesages ata2: softreset
+ failed (device not ready), ata2.00: qc timeout (cmd 0xec), ata2.00:
+ failed to IDENTIFY (I/O error, err_mask=0x4)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, 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-triage
Changed in linux (Ubuntu):
status: Triaged → Incomplete
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 release http://www.ubuntu.com/getubuntu/download . 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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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