sd-card reader does not resume from suspend, module error?

Brian Deery

unread,

Apr 21, 2018, 5:44:44 PM4/21/18

to qubes...@googlegroups.com

Greetings mailing list:

I am very happy that 4.0 has been released and am using it for my main system.

One quirk that might have an easy fix is my SD card.

My Dell Precision 7520 has an internal sd card reader.

I am running the latest (non-experimental) updates for dom0. I am using the latest BIOS as well.

according to the logs, it looks like mmc_block, as well as several other modules have trouble with suspending. Is there a module to blacklist or some other easy fix for this?

could it be related to this recent suspend issue? https://github.com/QubesOS/qubes-issues/issues/3738

Should I be worried about the other modules with errors too?

insert before suspend

Apr 21 15:18:05 dom0 kernel: mmc0: cannot verify signal voltage switch
Apr 21 15:18:05 dom0 kernel: mmc0: new ultra high speed SDR50 SDHC card at address aaaa
Apr 21 15:18:05 dom0 kernel: mmcblk0: mmc0:aaaa SL08G 7.40 GiB
Apr 21 15:18:05 dom0 kernel: mmcblk0: p1
Apr 21 15:18:05 dom0 dbus-daemon[12182]: [session uid=1000 pid=12182] Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service' requested by ':1.47'
Apr 21 15:18:05 dom0 systemd[12165]: Starting XFCE notifications service...
Apr 21 15:18:05 dom0 dbus-daemon[12182]: [session uid=1000 pid=12182] Successfully activated service 'org.freedesktop.Notifications'
Apr 21 15:18:05 dom0 systemd[12165]: Started XFCE notifications service.

remove card

Apr 21 15:21:29 dom0 kernel: mmc0: card aaaa removed

insert again:

Apr 21 15:23:09 dom0 kernel: mmc0: cannot verify signal voltage switch
Apr 21 15:23:09 dom0 kernel: mmc0: new ultra high speed SDR50 SDHC card at address aaaa
Apr 21 15:23:09 dom0 kernel: mmcblk0: mmc0:aaaa SL08G 7.40 GiB
Apr 21 15:23:09 dom0 kernel: mmcblk0: p1

remove:

Apr 21 15:24:08 dom0 kernel: mmc0: card aaaa removed

With journalctl I see this when I suspend the computer.

Apr 21 15:26:47 dom0 kernel: ------------[ cut here ]------------
Apr 21 15:26:47 dom0 kernel: WARNING: CPU: 0 PID: 13288 at /home/user/rpmbuild/BUILD/kernel-4.14.18/linux-4.14.18/kernel/power/suspend_test.c:55 suspend_test_finish+0x6b/0x70
Apr 21 15:26:47 dom0 kernel: Modules linked in: mmc_block loop ebtable_filter ebtables ip6table_filter ip6_tables snd_hda_codec_hdmi joydev uvcvideo videobuf2_vmalloc videobuf2_memops vide
Apr 21 15:26:47 dom0 kernel: int3400_thermal int340x_thermal_zone intel_hid acpi_thermal_rel sparse_keymap xenfs dm_thin_pool dm_persistent_data libcrc32c dm_bio_prison dm_crypt rtsx_pci_
Apr 21 15:26:47 dom0 kernel: CPU: 0 PID: 13288 Comm: systemd-sleep Tainted: G     U W       4.14.18-1.pvops.qubes.x86_64 #1
Apr 21 15:26:47 dom0 kernel: Hardware name: Dell Inc. Precision 7520/      , BIOS 1.10.2 03/09/2018
Apr 21 15:26:47 dom0 kernel: task: ffff88015443db80 task.stack: ffffc90005100000
Apr 21 15:26:47 dom0 kernel: RIP: e030:suspend_test_finish+0x6b/0x70
Apr 21 15:26:47 dom0 kernel: RSP: e02b:ffffc90005103d28 EFLAGS: 00010282
Apr 21 15:26:47 dom0 kernel: RAX: 0000000000000026 RBX: ffffffff8208fb53 RCX: ffffffff82251e68
Apr 21 15:26:47 dom0 kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000201
Apr 21 15:26:47 dom0 kernel: RBP: 0000000000005a63 R08: 00000006ce1cf04f R09: 0000000000000026
Apr 21 15:26:47 dom0 kernel: R10: 0000000000000040 R11: 0000000000028970 R12: 0000000000000000
Apr 21 15:26:47 dom0 kernel: R13: ffffffff82251b90 R14: 00000000fffffff0 R15: 0000000000000004
Apr 21 15:26:47 dom0 kernel: FS: 000071ad037c8180(0000) GS:ffff880198800000(0000) knlGS:0000000000000000
Apr 21 15:26:47 dom0 kernel: CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 21 15:26:47 dom0 kernel: CR2: ffff80000050c2b0 CR3: 0000000160084000 CR4: 0000000000042660
Apr 21 15:26:47 dom0 kernel: Call Trace:
Apr 21 15:26:47 dom0 kernel: suspend_devices_and_enter+0x185/0x7b0
Apr 21 15:26:47 dom0 kernel: pm_suspend+0x335/0x3a0
Apr 21 15:26:47 dom0 kernel: state_store+0x72/0xe0
Apr 21 15:26:47 dom0 kernel: kernfs_fop_write+0x109/0x1a0
Apr 21 15:26:47 dom0 kernel: __vfs_write+0x33/0x170
Apr 21 15:26:47 dom0 kernel: ? __audit_syscall_entry+0xae/0x100
Apr 21 15:26:47 dom0 kernel: vfs_write+0xb0/0x190
Apr 21 15:26:47 dom0 kernel: SyS_write+0x52/0xc0
Apr 21 15:26:47 dom0 kernel: do_syscall_64+0x6f/0x180
Apr 21 15:26:47 dom0 kernel: entry_SYSCALL_64_after_hwframe+0x21/0x86
Apr 21 15:26:47 dom0 kernel: RIP: 0033:0x71ad02c98b50
Apr 21 15:26:47 dom0 kernel: RSP: 002b:00007ffd961c8df8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
Apr 21 15:26:47 dom0 kernel: RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 000071ad02c98b50
Apr 21 15:26:47 dom0 kernel: RDX: 0000000000000004 RSI: 00005989d5601390 RDI: 0000000000000004
Apr 21 15:26:47 dom0 kernel: RBP: 00005989d5601390 R08: 00005989d5601240 R09: 000071ad037c8180
Apr 21 15:26:47 dom0 kernel: R10: 00005989d5601390 R11: 0000000000000246 R12: 0000000000000004
Apr 21 15:26:47 dom0 kernel: R13: 0000000000000001 R14: 00005989d5601160 R15: 000071ad02f5e3c0
Apr 21 15:26:47 dom0 kernel: Code: ea 06 69 c2 e8 03 00 00 29 c1 e8 3c 38 00 00 81 fd 10 27 00 00 77 03 5b 5d c3 89 ea 48 89 de 48 c7 c7 c9 fd 08 82 e8 20 38 00 00 <0f> ff 5b 5d c3 0f 1f 4
Apr 21 15:26:47 dom0 kernel: ---[ end trace 2efc73b32d68f1f3 ]---

Apr 21 15:26:47 dom0 kernel: ------------[ cut here ]------------
Apr 21 15:26:47 dom0 kernel: WARNING: CPU: 0 PID: 13288 at /home/user/rpmbuild/BUILD/kernel-4.14.18/linux-4.14.18/kernel/power/suspend_test.c:55 suspend_test_finish+0x6b/0x70
Apr 21 15:26:47 dom0 kernel: Modules linked in: mmc_block loop ebtable_filter ebtables ip6table_filter ip6_tables snd_hda_codec_hdmi joydev uvcvideo videobuf2_vmalloc videobuf2_memops vide
Apr 21 15:26:47 dom0 kernel: int3400_thermal int340x_thermal_zone intel_hid acpi_thermal_rel sparse_keymap xenfs dm_thin_pool dm_persistent_data libcrc32c dm_bio_prison dm_crypt rtsx_pci_
Apr 21 15:26:47 dom0 kernel: CPU: 0 PID: 13288 Comm: systemd-sleep Tainted: G     U W       4.14.18-1.pvops.qubes.x86_64 #1
Apr 21 15:26:47 dom0 kernel: Hardware name: Dell Inc. Precision 7520/      , BIOS 1.10.2 03/09/2018
Apr 21 15:26:47 dom0 kernel: task: ffff88015443db80 task.stack: ffffc90005100000
Apr 21 15:26:47 dom0 kernel: RIP: e030:suspend_test_finish+0x6b/0x70
Apr 21 15:26:47 dom0 kernel: RSP: e02b:ffffc90005103d28 EFLAGS: 00010282
Apr 21 15:26:47 dom0 kernel: RAX: 0000000000000026 RBX: ffffffff8208fb53 RCX: ffffffff82251e68
Apr 21 15:26:47 dom0 kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000201
Apr 21 15:26:47 dom0 kernel: RBP: 0000000000005a63 R08: 00000006ce1cf04f R09: 0000000000000026
Apr 21 15:26:47 dom0 kernel: R10: 0000000000000040 R11: 0000000000028970 R12: 0000000000000000
Apr 21 15:26:47 dom0 kernel: R13: ffffffff82251b90 R14: 00000000fffffff0 R15: 0000000000000004
Apr 21 15:26:47 dom0 kernel: FS: 000071ad037c8180(0000) GS:ffff880198800000(0000) knlGS:0000000000000000
Apr 21 15:26:47 dom0 kernel: CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 21 15:26:47 dom0 kernel: CR2: ffff80000050c2b0 CR3: 0000000160084000 CR4: 0000000000042660
Apr 21 15:26:47 dom0 kernel: Call Trace:
Apr 21 15:26:47 dom0 kernel: suspend_devices_and_enter+0x185/0x7b0
Apr 21 15:26:47 dom0 kernel: pm_suspend+0x335/0x3a0
Apr 21 15:26:47 dom0 kernel: state_store+0x72/0xe0
Apr 21 15:26:47 dom0 kernel: kernfs_fop_write+0x109/0x1a0
Apr 21 15:26:47 dom0 kernel: __vfs_write+0x33/0x170
Apr 21 15:26:47 dom0 kernel: ? __audit_syscall_entry+0xae/0x100
Apr 21 15:26:47 dom0 kernel: vfs_write+0xb0/0x190
Apr 21 15:26:47 dom0 kernel: SyS_write+0x52/0xc0
Apr 21 15:26:47 dom0 kernel: do_syscall_64+0x6f/0x180
Apr 21 15:26:47 dom0 kernel: entry_SYSCALL_64_after_hwframe+0x21/0x86
Apr 21 15:26:47 dom0 kernel: RIP: 0033:0x71ad02c98b50
Apr 21 15:26:47 dom0 kernel: RSP: 002b:00007ffd961c8df8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
Apr 21 15:26:47 dom0 kernel: RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 000071ad02c98b50
Apr 21 15:26:47 dom0 kernel: RDX: 0000000000000004 RSI: 00005989d5601390 RDI: 0000000000000004
Apr 21 15:26:47 dom0 kernel: RBP: 00005989d5601390 R08: 00005989d5601240 R09: 000071ad037c8180
Apr 21 15:26:47 dom0 kernel: R10: 00005989d5601390 R11: 0000000000000246 R12: 0000000000000004
Apr 21 15:26:47 dom0 kernel: R13: 0000000000000001 R14: 00005989d5601160 R15: 000071ad02f5e3c0
Apr 21 15:26:47 dom0 kernel: Code: ea 06 69 c2 e8 03 00 00 29 c1 e8 3c 38 00 00 81 fd 10 27 00 00 77 03 5b 5d c3 89 ea 48 89 de 48 c7 c7 c9 fd 08 82 e8 20 38 00 00 <0f> ff 5b 5d c3 0f 1f 4
Apr 21 15:26:47 dom0 kernel: ---[ end trace 2efc73b32d68f1f3 ]---

awokd

unread,

Apr 22, 2018, 9:50:10 AM4/22/18

to Brian Deery, qubes...@googlegroups.com

On Sat, April 21, 2018 9:44 pm, Brian Deery wrote:

> One quirk that might have an easy fix is my SD card.

>

> according to the logs, it looks like mmc_block, as well as several other
> modules have trouble with suspending. Is there a module to blacklist or
> some other easy fix for this?

Check out https://www.qubes-os.org/doc/wireless-troubleshooting/. It might
apply to your SD card too. I looked at your logs but couldn't really tell
which module you'd want to try to blacklist- it would be the equivalent of
iwlwifi for SD cards. Maybe "mmc0"?

Brian Deery

unread,

Apr 22, 2018, 3:25:43 PM4/22/18

to aw...@danwin1210.me, qubes...@googlegroups.com

ok, I added

blacklist=mmc_block

to the end of my /etc/default/grub file then ran "sudo grub2-mkconfig -o /boot/grub2/grub.cfg"

on rebooting I examined the grub commands and it showed the kernel was being booted with the blacklist option. This blacklist did not fix the problem. The card still is unrecognized after suspend. I removed the kernel option.

I also tried adding "blacklist=mmc_block blacklist=mmc_core blacklist=rtsx_pci_sdmmc" to grub when booting with no effect. modinfo shows mmc_block and rtsx_pci_sdmmc both depend on mmc_core

before suspend, as root, these commands attach and detach the SD card successfully:

echo -n mmc0:aaaa > /sys/bus/mmc/drivers/mmcblk/bind
echo -n mmc0:aaaa > /sys/bus/mmc/drivers/mmcblk/unbind

After suspend, the above commands give the error "bash: echo: write error: No such device"

before the first suspend:
"sudo modprobe -r mmc_block" doesn't have much effect when the SD card is removed.
This command resets the machine if the SD card is inserted and attached.

after the first suspend:
sudo modprobe -r mmc_block

and
sudo modprobe mmc_block

don't seem to have any effect.

awokd

unread,

Apr 22, 2018, 4:07:52 PM4/22/18

to Brian Deery, aw...@danwin1210.me, qubes...@googlegroups.com

I used the word "blacklist" but meant it only in context of suspends. Did
you see the link? Check the bottom of that page. Instead of blacklisting
the modules outright, try to rmmod then modprobe them (also per that page)
and see if any get your SD working again. If so, add them to
suspend-module-blacklist. Try these one at a time: mmc_block mmc_core
rtsx_pci_sdmmc".

Reply all

Reply to author

Forward