pluging usb devices while suspended causes crash

Bug #521156 reported by Paul Larson
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-fsl-imx51 (Ubuntu)
Invalid
High
Unassigned
Karmic
Won't Fix
Undecided
Unassigned
Lucid
Won't Fix
High
Unassigned

Bug Description

I'm able to suspend and resume on babbage 3 without any problems normally, but one of the tests I'm doing involves unplugging my usb keyboard and mouse, suspending the system, plugging the usb keyboard and mouse back in, and resuming. When I do this, I don't get an oops or anything, but the kernel does spew quite a few errors and fails to recover. I've been able to reproduce this very reliably.

Kernel version is 2.6.31.604.5

Here is the output I get from the serial console:
...
mxc_ipu mxc_ipu: Channel already disabled 9
mxc_ipu mxc_ipu: Channel already uninitialized 9
Aborting journal on device sdb1:8.
JBD2: I/O error detected when updating journal superblock for sdb1:8.
EXT4-fs error (device sdb1): ext4_journal_start_sb: Detected aborted journal
EXT4-fs (sdb1): Remounting filesystem read-only
journal commit I/O error
Read-error on swap-device (8:16:2584)
Read-error on swap-device (8:16:2600)
Read-error on swap-device (8:16:2608)
Read-error on swap-device (8:16:2616)
Read-error on swap-device (8:16:2624)
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #131074 offset 0
init: rsyslog main process (868) killed by BUS signal
init: rsyslog main process ended, respawning
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #131074 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #131074 offset 0
Read-error on swap-device (8:16:2376)
Read-error on swap-device (8:16:2384)
Read-error on swap-device (8:16:2392)
Read-error on swap-device (8:16:2400)
Read-error on swap-device (8:16:2408)
Read-error on swap-device (8:16:2416)
Read-error on swap-device (8:16:2424)
Read-error on swap-device (8:16:2432)
init: rsyslog-kmsg main process (864) killed by PIPE signal
init: rsyslog-kmsg main process ended, respawning
udevd-work[10015]: exec of program '/sbin/blkid' failed

EXT4-fs error (device sdb1): __ext4_get_inode_loc: unable to read inode block - inode=131739, block=524361
EXT4-fs error (device sdb1): __ext4_get_inode_loc: unable to read inode block - inode=3270, block=1261
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #16386 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #8193 offset 0
apmd[1084]: Proxy exited with stEXT4-fs error (device sdb1): ext4_find_entry: atus 1
reading directory #16386 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #65537 offset 0
udevd-work[10019]: exec of program '/lib/udev/devkit-disks-part-id' failed

udevd-work[10020]: exec of program '/sbin/blkid' failed

EXT4-fs error (device sdb1): ext4_find_entry: reading directory #155651 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #16386 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #16386 offset 0
udevd-work[10021]: exec of progrEXT4-fs error (device sdb1): ext4_find_entry: am '/sbin/blkid' failed

reading directory #24578 offset 0
init: rsyslog-kmsg post-stop process (10014) terminated with status 127
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #24578 offset 0
EXT4-fs error (device sdb1): ext4_read_block_bitmap: Cannot read block bitmap - block_group = 50, block_bitmap = 1572866
EXT4-fs error (device sdb1): ext4_discard_preallocations: Error in reading block bitmap for 50
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #385032 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #385032 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #1073192 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #385032 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #385032 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #385032 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #1073192 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106504 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106504 offset 0
usb 1-1: device descriptor read/64, error -71
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #98312 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #65537 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #98312 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #24578 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #65537 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #81922 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #24578 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106504 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #98312 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #65537 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #24578 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106504 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #98312 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #65537 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #24578 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #24577 offset 0
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/64, error -71
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #753737 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #278536 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106505 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #449230 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #753737 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #278536 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #753738 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106505 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106504 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #98312 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #65537 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106504 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #98312 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #65537 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #24578 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106504 offset 0
usb 1-1: device not accepting address 10, error -71
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #98312 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #65537 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #24578 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #458814 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #753737 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #16386 offset 0
usb 1-1: device not accepting address 11, error -71
hub 1-0:1.0: unable to enumerate USB device on port 1
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #455078 offset 0
Read-error on swap-device (8:16:2568)
init: cron main process (1069) killed by BUS signal
init: cron main process ended, respawning
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106504 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #98312 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #475165 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #1073192 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #106504 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #98312 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #65537 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #24578 offset 0
EXT4-fs error (device sdb1): ext4_find_entry: reading directory #81922 offset 0

Tags: armel imx51
Paul Larson (pwlars)
tags: added: armel
Changed in linux-fsl-imx51 (Ubuntu):
assignee: nobody → Bryan Wu (cooloney)
Revision history for this message
Tobin Davis (gruemaster) wrote :

I am seeing a problem with a laptop drive connected to the sata port not recovering from sleep. On resume, I get a text console full of read-error on swap-device and EXT4-fs errors on sda6 (multi-part disk with root on sda6 for this image).

Revision history for this message
Paul Larson (pwlars) wrote :

@Tobin - possible that you are seeing a different problem. Does the kernel output look like what you are seeing above? I am able to suspend/resume just fine with either sata, or with USB as my rootfs. The bug referenced here is a specific case of plugging usb (i.e. mouse/keyboard) while the system is suspended, then recovering.

Revision history for this message
Tobin Davis (gruemaster) wrote :

The kernel output is the same minus the usb messages (and the drive is sda6 instead of sdb1). I think the problem may be in the usb controller wakeup. That would affect sata as well, since it floats off the usb bus internally.

Paul Larson (pwlars)
Changed in linux-fsl-imx51 (Ubuntu):
importance: Undecided → High
tags: added: imx51
Steve Langasek (vorlon)
Changed in linux-fsl-imx51 (Ubuntu Lucid):
importance: Undecided → High
assignee: nobody → Bryan Wu (cooloney)
Changed in linux-fsl-imx51 (Ubuntu):
assignee: Bryan Wu (cooloney) → nobody
status: New → Invalid
Revision history for this message
Tobin Davis (gruemaster) wrote :

Marking as won't fix, as the only devices still supported by this release are the buildds, so very low chance of hitting this. Lucid Arm support ended once 11.10 was released (not an LTS release).

Changed in linux-fsl-imx51 (Ubuntu Karmic):
status: New → Won't Fix
Changed in linux-fsl-imx51 (Ubuntu Lucid):
status: New → Won't Fix
assignee: Bryan Wu (cooloney) → nobody
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.