SD-Card produces kernel Oops
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Medium
|
Brian Murray |
Bug Description
Binary package hint: linux
Inserting a Kingston Mini-SD-Card produces in syslog:
---snipp---
Apr 24 12:35:07 red kernel: [ 105.331950] tifm_7xx1: sd card detected in socket 1
Apr 24 12:35:07 red NetworkManager: <debug info>^I[
org/freedesktop
Apr 24 12:35:07 red kernel: [ 105.599458] mmcblk0: mmc0:a9c1 SD02G 2011136KiB
Apr 24 12:35:07 red kernel: [ 105.599489] mmcblk0: p1
Apr 24 12:35:07 red NetworkManager: <debug info>^I[
org/freedesktop
Apr 24 12:35:08 red kernel: [ 106.011306] tifm_sd: card failed to respond for a long period of time<6>tifm_7xx1: demand remo
ving card from socket 1
Apr 24 12:35:08 red kernel: [ 106.011577] mmcblk0: error 1 sending read/write command
Apr 24 12:35:08 red kernel: [ 106.011582] end_request: I/O error, dev mmcblk0, sector 4022208
Apr 24 12:35:08 red kernel: [ 106.011585] printk: 4 messages suppressed.
Apr 24 12:35:08 red kernel: [ 106.011587] Buffer I/O error on device mmcblk0, logical block 502776
##
## followed by a LOT of:
##
Apr 24 12:35:08 red kernel: [ 106.013120] mmcblk0: error 1 sending read/write command
Apr 24 12:35:08 red kernel: [ 106.013122] end_request: I/O error, dev mmcblk0, sector 0
[...]
---snapp---
and leaves this in dmesg:
---snipp---
[ 136.789664] Unable to handle kernel NULL pointer dereference at 0000000000000040 RIP:
[ 136.789667] [<ffffffff88606
[ 136.789676] PGD 57dc1067 PUD 591ad067 PMD 0
[ 136.789680] Oops: 0000 [1] SMP
[ 136.789682] CPU 0
[ 136.789684] Modules linked in: mmc_block tifm_sd mmc_core fglrx(P) binfmt_misc rfcomm l2cap ipv6 ppdev powernow_k8 cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table cpufreq_
[ 136.789741] Pid: 6615, comm: mmcqd Tainted: P 2.6.20-15-generic #2
[ 136.789744] RIP: 0010:[<
[ 136.789751] RSP: 0018:ffff81004c
[ 136.789754] RAX: 0000000000000000 RBX: ffff81006dda1b58 RCX: 0000000000000000
[ 136.789757] RDX: 0000000000000000 RSI: ffff81006dda1b58 RDI: 0000000000000000
[ 136.789760] RBP: ffff81006dda1b58 R08: ffff81006dda11f8 R09: 0000000000000000
[ 136.789763] R10: 0000000000000001 R11: 0000000000000000 R12: ffff810061ae49a0
[ 136.789767] R13: ffffffff88606e50 R14: ffffffff802a3170 R15: ffff810001336800
[ 136.789771] FS: 00002b0bef0d6f0
[ 136.789774] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[ 136.789777] CR2: 0000000000000040 CR3: 0000000059cfc000 CR4: 00000000000006e0
[ 136.789781] Process mmcqd (pid: 6615, threadinfo ffff81004ce00000, task ffff81004e28b820)
[ 136.789783] Stack: ffff81006c0d8cd8 ffffffff80333338 ffff810061ae49a0 ffff81006dda1b58
[ 136.789790] ffff810061ae4990 ffff81006c0d8cd8 ffff810061ae49a0 ffffffff88606eb4
[ 136.789795] 00000000fffffffc ffff810061ae4990 ffff81005a417ac0 ffffffff80233f59
[ 136.789800] Call Trace:
[ 136.789808] [<ffffffff80333
[ 136.789816] [<ffffffff88606
[ 136.789824] [<ffffffff80233
[ 136.789834] [<ffffffff80261
[ 136.789840] [<ffffffff802a3
[ 136.789847] [<ffffffff80231
[ 136.789856] [<ffffffff80233
[ 136.789861] [<ffffffff80261
[ 136.789865]
[ 136.789866]
[ 136.789867] Code: ff 52 40 85 c0 74 18 eb 1d 48 c7 c6 22 71 60 88 48 89 df e8
[ 136.789877] RIP [<ffffffff88606
[ 136.789882] RSP <ffff81004ce01eb0>
[ 136.789884] CR2: 0000000000000040
[ 136.789886]
---snapp---
Version hint:
Ubuntu 7.04; 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug does not meet the criteria for a stable release update and is being marked as Won't Fix for this particular version of the kernel. You can learn more about the stable release update process at https:/ /wiki.ubuntu. com/StableRelea seUpdates . www.ubuntu. com/testing/ . wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks again and we appreciate your help.
However, the issue that you reported is one that should be possible to test with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://
If you do decide to test with the development release of Ubuntu please comment on this bug report and include at least the minimal information requested at http://