Upon resuming from suspend messages appear in tty

Bug #984088 reported by Brian Murray
198
This bug affects 51 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Low
linux (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

With every resume from suspend I briefly see the following in a tty before the display is switched to X and my screensaver:

Apr 17 08:33:45 localhost kernel: [ 256.610821] watchdog: only one watchdog can use /dev/watchdog.
Apr 17 08:33:45 localhost kernel: [ 256.610826] watchdog: error registering /dev/watchdog (err=-16).
Apr 17 08:33:45 localhost kernel: [ 256.610829] mei: unable to register watchdog device.

This accumulate so that on the 2nd resume from suspend I will see the previous messages and another one for a total of six lines. I believe this is a recent development and started happening with the 3.2.0-22 kernel.

== WORKAROUND ==

Blacklist the mei module

ProblemType: BugDistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-23-generic 3.2.0-23.36
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bdmurray 2144 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2520000 irq 45'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:14f15069,17aa2157,00100302 HDA:80862804,17aa21b5,00100000'
   Controls : 14
   Simple ctrls : 6
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6SHT30WW-1.11'
   Mixer name : 'ThinkPad EC 6SHT30WW-1.11'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
CheckboxSubmission: 2e6ecd139611830c78226ad04ff4c093
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Tue Apr 17 08:44:27 2012
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=34048ba2-2259-4391-aadc-102323dca898InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
MachineType: LENOVO 0831CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=58a88244-4d22-41f7-bd3a-aaa049c553a6 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic N/A
 linux-backports-modules-3.2.0-23-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: noSourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-01-04 (103 days ago)
dmi.bios.date: 09/15/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET53WW (1.23 )
dmi.board.name: 0831CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6QET53WW(1.23):bd09/15/2010:svnLENOVO:pn0831CTO:pvrThinkPadX201Tablet:rvnLENOVO:rn0831CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 0831CTO
dmi.product.version: ThinkPad X201 Tablet
dmi.sys.vendor: LENOVO

Revision history for this message
Brian Murray (brian-murray) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

Here's a little video of it.

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

Seeing this here as well; the messages also go to dmesg, and don't seem to affect anything, so it would be really nice to not have these marring the screen on resume.

Revision history for this message
Steve Langasek (vorlon) wrote :

And note, for reference, that they pop up another set as /part of/ the resume.

Revision history for this message
Elijah Lynn (elijah-lynn) wrote :

I have these same messages on a Thinkpad W510. Mine don't seem to accumulate. I used to see two, then I think they went away but after the kernel update yesterday I started seeing them again.

Revision history for this message
Brian Murray (brian-murray) wrote : Re: [Bug 984088] Re: Upon resuming from suspend messages appear in tty

On Fri, Apr 27, 2012 at 12:15:53PM -0000, Elijah Lynn wrote:
> I have these same messages on a Thinkpad W510. Mine don't seem to
> accumulate. I used to see two, then I think they went away but after the
> kernel update yesterday I started seeing them again.

If you updated the kernel you likely rebooted so the messages were
cleared. The messages accumulate for each suspend and resume between
reboots.

--
Brian Murray
Ubuntu Bug Master

Revision history for this message
CuteChaps (sh-senthilkumar) wrote :

I do see same set of error accumulating after every resume.

OS: Ubuntu 12.04 Final release
THINKPAD T410.

28 14:08:38 Senthil-IN kernel: [ 48.183715] firewire_core: rediscovered device fw0
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223888] PM: resume of drv:usb dev:1-1.4:1.1 complete after 593.496 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223896] PM: resume of drv: dev:ep_00 complete after 593.208 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223905] PM: resume of drv:usb dev:1-1.4:1.3 complete after 593.253 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223913] PM: resume of drv:usb dev:1-1.4:1.0 complete after 593.705 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223921] PM: resume of drv: dev:ep_83 complete after 593.504 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223926] PM: resume of drv:usb dev:1-1.4:1.2 complete after 593.409 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223938] PM: resume of drv: dev:ep_81 complete after 593.689 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223944] PM: resume of drv: dev:ep_82 complete after 593.674 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223953] PM: resume of drv: dev:ep_03 complete after 593.478 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223958] PM: resume of drv: dev:ep_84 complete after 593.428 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223968] PM: resume of drv: dev:ep_02 complete after 593.622 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.223979] PM: resume of drv: dev:ep_04 complete after 593.399 msecs
Apr 28 14:08:38 Senthil-IN kernel: [ 48.336057] watchdog: only one watchdog can use /dev/watchdog.
Apr 28 14:08:38 Senthil-IN kernel: [ 48.336062] watchdog: error registering /dev/watchdog (err=-16).
Apr 28 14:08:38 Senthil-IN kernel: [ 48.336065] mei: unable to register watchdog device.

Revision history for this message
roland (roland-micite) wrote :

This bug has been reported upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=42794

See also the ArchLinux discussion at:
https://bbs.archlinux.org/viewtopic.php?id=133083

Changed in linux (Ubuntu):
status: Confirmed → Triaged
description: updated
Revision history for this message
nikitakit (nikitakit) wrote :

I have the same messages since I upgraded to precise. My computer is a Fujitsu Lifebook T901. (I can post more info if needed)

Changed in linux:
importance: Unknown → Low
status: Unknown → Confirmed
Changed in linux:
status: Confirmed → Fix Released
Revision history for this message
Atheg (hoganaj) wrote :

I have this problem and it often seems related to instances when I am unable to resume at all.

Revision history for this message
Andre (ajx) wrote :

This problem still exists on Precise 12.04.2 64bit with Linux 3.2.0-38. Will the fix from upstream (August 2012) be applied to the Ubuntu kernel?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@Andre,

Can you test the latest 3.2 stable kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.39-precise/

That will confirm if this fix is in the upstream stable kernel. If it is, then the fix will make it's way into Precise through the normal stable update process.

Revision history for this message
Andre (ajx) wrote :

@Joseph, I tested the latest 3.2 stable kernel (3.2.39-030239). It did not fix the problem.

However, I discovered a workaround, which does (maybe it introduces another problem I am not aware of?): I blacklisted 'mei'. I added

blacklist mei

to

/etc/modprobe.d/blacklist.conf

Now I do not get these errors anymore, no matter if I use 3.2.38 or 3.2.39.

I found this workaround here:
http://ubuntuforums.org/showthread.php?t=1970325

Does this help to fix the problem for all users of Precise?

Revision history for this message
Oedipe (oedipe) wrote :

Same here with latest 3.2.0-40 on "Precise"

penalvch (penalvch)
tags: added: bios-outdated-1.40
penalvch (penalvch)
tags: added: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Brian Murray / Chris J Arges, 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? If so, since this was reported, there has been considerable work done in drivers/misc/mei/* addressing a plethora of watchdog issues. Would you mind testing for this with the latest development release of Ubuntu via http://cdimage.ubuntu.com/daily-live/current/ and advise on if this issue is reproducible?

Changed in linux (Ubuntu):
importance: Medium → Low
status: Triaged → Incomplete
Revision history for this message
Michael Doube (michael-doube) wrote :

This (or something very much like it) still occurs in relation to failing resume from suspend on my Dell T7600.

watchdog complaint is echoed to tty and resume fails.

This is on an up to date Ubuntu 12.04, and has affected the last few kernels (a few months I think, but haven't kept the old ones so can't easily test when it was introduced)

:~$ uname -a
Linux 3.2.0-65-generic #98-Ubuntu SMP Wed Jun 11 20:27:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

currently trying the mei blackist workaround, will feedback here.

Revision history for this message
Michael Doube (michael-doube) wrote :

blacklist mei workaround seems to help so far on this kernel. New kernel just released, will test that one too.

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.