[HP Probook 6550b] Unable to enter suspend when SD card is plugged in

Bug #1065641 reported by Daniel Manrique
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Steps to reproduce:
- Insert SD card in slot
- Wait for a Nautilus window to open.
- run pm-suspend

Expected result:
- System enters sleep mode

Actual result:
- The screen turns black and keyboard stops responding; can't switch to a VT for instance. Backlight remains active.
- Sytem does NOT suspend.
- I am, however, still able to SSH into the system via the network interface. This may help collect diagnostics information.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-32-generic 3.2.0-32.51
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1758 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x94820000 irq 49'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:111d7603,103c1470,00100202 HDA:11c11040,103c3066,00100200 HDA:80862804,80860101,00100000'
   Controls : 36
   Simple ctrls : 12
Date: Thu Oct 11 14:48:39 2012
HibernationDevice: RESUME=UUID=cc495f50-c1d5-4d76-b33f-2a127e2fbc1e
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: Hewlett-Packard HP ProBook 6550b
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=fabf77e8-6e89-4b6b-aeba-a2a47d186f36 ro quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-32-generic N/A
 linux-backports-modules-3.2.0-32-generic N/A
 linux-firmware 1.79.1
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CDE Ver. F.00
dmi.board.name: 146D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 73.11
dmi.chassis.asset.tag: CNU0251DKY
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68CDEVer.F.00:bd04/21/2010:svnHewlett-Packard:pnHPProBook6550b:pvr:rvnHewlett-Packard:rn146D:rvrKBCVersion73.11:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 6550b
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Daniel Manrique (roadmr) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Daniel Manrique (roadmr) wrote :
Download full text (22.8 KiB)

Apologies for letting this one expire :(

I tested with a Precise kernel (3.2.0-29), following this procedure:
- Boot
- Insert SD card, ensure it gets mounted and a nautilus windows opens
- Open a terminal and run "sudo pm-suspend"

Result: The system doesn't enter suspend mode (no blinking power light), it just goes unresponsive with a black screen. I can SSH into it, and I was able to get this error trace from dmesg:
[ 129.989786] EXT2-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
[ 138.577570] PM: Syncing filesystems ... done.
[ 138.600440] PM: Preparing system for mem sleep
[ 139.095196] mmc0: card b368 removed
[ 360.692751] INFO: task mmcqd/0:2477 blocked for more than 120 seconds.
[ 360.692764] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 360.692774] mmcqd/0 D 0000000000000000 0 2477 2 0x00000000
[ 360.692784] ffff880041eabd90 0000000000000046 0000000000000082 ffff880070c3eafc
[ 360.692793] ffff880041eabfd8 ffff880041eabfd8 ffff880041eabfd8 00000000000137c0
[ 360.692802] ffff880041df4500 ffff8800385c1700 ffff880041eabd80 ffff88007006aaf4
[ 360.692811] Call Trace:
[ 360.692825] [<ffffffff8165b34f>] schedule+0x3f/0x60
[ 360.692834] [<ffffffff8150b1af>] __mmc_claim_host+0xaf/0x190
[ 360.692841] [<ffffffff810606a0>] ? try_to_wake_up+0x200/0x200
[ 360.692847] [<ffffffffa04431ba>] mmc_blk_issue_rq+0x21a/0x240 [mmc_block]
[ 360.692852] [<ffffffff812f4cd3>] ? blk_start_request+0x33/0x50
[ 360.692856] [<ffffffffa0443838>] mmc_queue_thread+0x68/0x160 [mmc_block]
[ 360.692860] [<ffffffffa04437d0>] ? mmc_alloc_sg+0x70/0x70 [mmc_block]
[ 360.692865] [<ffffffff8108b27c>] kthread+0x8c/0xa0
[ 360.692874] [<ffffffff816679b4>] kernel_thread_helper+0x4/0x10
[ 360.692877] [<ffffffff8108b1f0>] ? flush_kthread_worker+0xa0/0xa0
[ 360.692880] [<ffffffff816679b0>] ? gs_change+0x13/0x13
[ 360.692883] INFO: task pm-suspend:2503 blocked for more than 120 seconds.
[ 360.692886] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 360.692890] pm-suspend D 0000000000000000 0 2503 2502 0x00000000
[ 360.692894] ffff880059b238f8 0000000000000086 ffff880057373318 ffff8800365c4218
[ 360.692898] ffff880059b23fd8 ffff880059b23fd8 ffff880059b23fd8 00000000000137c0
[ 360.692902] ffff8800385c1700 ffff880038555c00 ffff880059b238d8 ffff880076c14080
[ 360.692906] Call Trace:
[ 360.692910] [<ffffffff811aa180>] ? __wait_on_buffer+0x30/0x30
[ 360.692913] [<ffffffff8165b34f>] schedule+0x3f/0x60
[ 360.692916] [<ffffffff8165b3ff>] io_schedule+0x8f/0xd0
[ 360.692918] [<ffffffff811aa18e>] sleep_on_buffer+0xe/0x20
[ 360.692922] [<ffffffff8165baca>] __wait_on_bit_lock+0x5a/0xc0
[ 360.692924] [<ffffffff811aa180>] ? __wait_on_buffer+0x30/0x30
[ 360.692927] [<ffffffff8165bbac>] out_of_line_wait_on_bit_lock+0x7c/0x90
[ 360.692930] [<ffffffff8108bd60>] ? autoremove_wake_function+0x40/0x40
[ 360.692933] [<ffffffff811aa1d6>] __lock_buffer+0x36/0x40
[ 360.692937] [<ffffffff811ab7c5>] __sync_dirty_buffer+0xc5/0xd0
[ 360.692940] [<ffffffff811ab7e3>] sync_dirty_buffer+0x13/0x20
[ 360.692945] [<ffffffffa0450bf4>] ext2_...

Revision history for this message
Daniel Manrique (roadmr) wrote :

Now, for the mainline kernel test. I did the same test as in the last comment, and system *was* able to suspend correctly and then resume without no problems. Kernel version is this:

Linux kernel x86 boot executable bzImage, version 3.8.0-030800rc5-generic (root@gomeisa) #201301251535 SMP Fri Ja, RO-rootFS, swap_dev 0x5, Normal VGA

I'll tag kernel-fixed-upstream.

Changed in linux (Ubuntu):
status: Expired → Confirmed
tags: added: kernel-fixed-upstream
removed: needs-upstream-testing
Revision history for this message
penalvch (penalvch) wrote :

Daniel Manrique, as per http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=4173772&prodTypeId=0&prodSeriesId=4173845&swLang=13&taskId=135&swEnvOID=4060#120 an update is available for your BIOS (F.23). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

tags: added: bios-outdated-f.23
tags: added: kernel-fixed-upstream-v3.6
removed: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

I can verify that this bug has been fixed.
For those who still affected by this, please feel free to open a new bug.

Changed in linux (Ubuntu):
status: Expired → Fix Released
tags: added: 201101-6954 taipei-lab
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.