kernel oops writing image to sd card

[James Hunt]

Writing a 3G image to an SD card led to an oops (on both occasions I tried it):

$ cat foo.img | sudo dd bs=16M of=/dev/mmcblk0

[36467.181234] Call Trace:
[36467.181245] [<ffffffff827596d9>] schedule_preempt_disabled+0x29/0x70
[36467.181251] [<ffffffff8275b525>] __mutex_lock_slowpath+0xd5/0x1d0
[36467.181278] [<ffffffff8275b63f>] mutex_lock+0x1f/0x2f
[36467.181283] [<ffffffff822066d3>] __blkdev_get+0x63/0x4c0
[36467.181287] [<ffffffff82206cf5>] blkdev_get+0x1c5/0x340
[36467.181291] [<ffffffff82206f1b>] blkdev_open+0x5b/0x80
[36467.181296] [<ffffffff821cd32f>] do_dentry_open+0x1ff/0x350
[36467.181300] [<ffffffff82206ec0>] ? blkdev_get_by_dev+0x50/0x50
[36467.181303] [<ffffffff821cd5c9>] vfs_open+0x49/0x50
[36467.181309] [<ffffffff821dca94>] do_last+0x554/0x1210
[36467.181317] [<ffffffff823226bb>] ? apparmor_file_alloc_security+0x5b/0x180
[36467.181322] [<ffffffff821dea1b>] path_openat+0xbb/0x620
[36467.181328] [<ffffffff82384d66>] ? sprintf+0x46/0x50
[36467.181333] [<ffffffff821e048a>] do_filp_open+0x3a/0x90
[36467.181340] [<ffffffff821ecff7>] ? __alloc_fd+0xa7/0x130
[36467.181345] [<ffffffff821ceea9>] do_sys_open+0x129/0x280
[36467.181349] [<ffffffff82021b55>] ? syscall_trace_enter+0x145/0x250
[36467.181353] [<ffffffff821cf01e>] SyS_open+0x1e/0x20
[36467.181359] [<ffffffff8275d43f>] tracesys+0xe1/0xe6

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-generic 3.16.0.5.6
ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
Uname: Linux 3.16.0-5-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: james 3817 F.... pulseaudio
 /dev/snd/controlC1: james 3817 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri Jul 25 17:23:47 2014
HibernationDevice: RESUME=UUID=db600bbe-faca-41f4-9338-c3e8e227599a
InstallationDate: Installed on 2014-04-11 (104 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)
MachineType: LENOVO 20AQCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-5-generic N/A
 linux-backports-modules-3.16.0-5-generic N/A
 linux-firmware 1.132
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-05-08 (78 days ago)
dmi.bios.date: 02/10/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET71WW (2.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98405 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQCTO1WW
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

I see you are hitting this bug with the latest upstream kernel. Was there an earlier kernel that did not exhibit this bug?

[James Hunt (jamesodhunt)]

@jsalisbury - I am only using ubuntu-packaged kernels. When I get a chance I'll try to identify the last working kernel. However, can you tell from the stacktrace if this is a generic kernel issue? If so, can the kernel team recreate?

@penalvch - my bios may not be at the latest version, but we cannot expect users to go through the hassle of flashing their bios just to write data to an SD card.

[penalvch (penalvch)]

James Hunt, a BIOS update is the first thing upstream asks about if you contact them about an SD Card problem. While it may be perceived as a hassle to some, it would be worth it if it did in fact address your issue (and one major objection dealt with beforehand in order to have upstream take your bug report seriously). :D