ext4 on mmcblk card causes major kernel problems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Debian |
Fix Released
|
Unknown
|
|||
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Release: Precise
Architecture: i386
Testcase:
- Have a ext4 formatted partition on a mmcblk device mounted
- Start a shell and change into a directory on that sd card
- Suspend and Resume
Result: Kernel fails to forcefully unmount the partition and produces a lot of errors because re-discovery of the filesystem runs into duplicate proc and sysfs files. fs is unmountable until the shell leaves the directory.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.2.0-8-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.90-0ubuntu1
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x78540000 irq 45'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,
Controls : 13
Simple ctrls : 8
Date: Mon Jan 9 17:02:53 2012
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110819)
MachineType: Acer AOA110
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.67
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/06/2008
dmi.bios.vendor: Acer
dmi.bios.version: v0.3310
dmi.board.
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: AOA110
dmi.product.
dmi.sys.vendor: Acer
Changed in linux (Ubuntu): | |
assignee: | nobody → Stefan Bader (stefan-bader-canonical) |
importance: | Undecided → Medium |
Changed in linux (Ubuntu): | |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | In Progress → Won't Fix |
assignee: | Stefan Bader (stefan-bader-canonical) → nobody |
Changed in debian: | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in debian: | |
status: | Unknown → New |
Changed in debian: | |
status: | New → Fix Released |
So getting back to this issue. It still happens with a relatively upstream kernel version 3.4-rc3. When experimenting a bit more it seems that there are various cases:
1. automatically mounted by udisk under /media and not having a shell changed into that mount dir.
-> this seems to work, after resuming a new nautilus window appears as with a freshly inserted card
2. automatically mounted by udisk but having a shell changed into the mount dir.
-> Shows the mount error, the mountpoint does _not_ show up in df or /proc/mounts and typing ls
in the shell results in an IO error.
3. manually mounted (to /mnt) without shell changed into the mount dir.
-> Shows the mount error, df and /proc/mounts do contain the mount point, typing ls results
in the IO error.
4. manually mounted and changing into the mount dir seems the same as 3.