Ask Your Question

mjbright's profile - activity

2017-11-29 10:32:25 -0500 received badge  Popular Question (source)
2017-11-29 10:32:25 -0500 received badge  Notable Question (source)
2016-12-04 05:49:17 -0500 asked a question Fedora 24 - no longer able to suspend ("alsactl refusing to freeze")

Since a few days or a week ago I'm no longer to suspend my system, either by operating the power button or "systemctl suspend -i".

I've rebooted, performed dnf update, and running kernel 4.8.10-200.fc24.x86_64. After a reboot, still the same problem.

Looking at dmesg it seems that it's the alsactl process which is refusing to "freeze" - see below.

Any ideas how to fix this? Thx,

[Dec 4 12:05] Freezing of tasks failed after 20.009 seconds (1 tasks refusing to freeze, wq_busy=0): [ +0.000021] alsactl D ffff9f1d0ca5bb78 0 12178 1 0x00000004 [ +0.000003] ffff9f1d0ca5bb78 00ff9f1d2fb90100 ffff9f1d0c388000 ffff9f1d1db33d00 [ +0.000002] ffff9f1d0ca5bbc0 ffff9f1d0ca5c000 ffff9f1d0ca5bbc0 ffff9f1d2fb90100 [ +0.000001] 00000000ffffffff 0000000000000000 ffff9f1d0ca5bb90 ffffffffbc7fe1e5 [ +0.000001] Call Trace: [ +0.000005] [<ffffffffbc7fe1e5>] schedule+0x35/0x80 [ +0.000001] [<ffffffffbc80161b>] schedule_timeout+0x1db/0x3f0 [ +0.000002] [<ffffffffbc22642a>] ? kmem_cache_alloc_trace+0xea/0x1b0 [ +0.000005] [<ffffffffc070f595>] ? snd_ctl_open+0x85/0x190 [snd] [ +0.000003] [<ffffffffbc10f6d0>] ? del_timer_sync+0x50/0x50 [ +0.000002] [<ffffffffc070beed>] snd_power_wait+0xbd/0x110 [snd] [ +0.000003] [<ffffffffbc0cba90>] ? wake_up_q+0x80/0x80 [ +0.000002] [<ffffffffc070d99f>] snd_ctl_elem_info_user+0x5f/0xf0 [snd] [ +0.000002] [<ffffffffc0710544>] snd_ctl_ioctl+0x5e4/0x6c0 [snd] [ +0.000002] [<ffffffffbc264d73>] do_vfs_ioctl+0xa3/0x5f0 [ +0.000001] [<ffffffffbc265339>] SyS_ioctl+0x79/0x90 [ +0.000002] [<ffffffffbc802932>] entry_SYSCALL_64_fastpath+0x1a/0xa4

2016-11-05 12:33:07 -0500 asked a question Fedora 24 fails to boot (to 4.7.6-200) after 'dnf upgrade': mount: unknown filesystem type 'vfat'

This morning I performed a 'dnf update' (whilst booted on 4.7.6-200 kernel) to be able to pass from 4.7.6 to 4.8.4 to avoid the Dirty Cow vulnerability.

Since then I can boot neither the old 4.7.6 kernel, nor the new 4.8.4 kernel (separate problem asked here`).

I'm now "successfully" booted on 4.7.3 (!!) to enter this question.

4.7.6-200 boot problem:

So my system now fails to boot into 4.7.6 dropping into emergency mode.

Running 'journalctl -xb' shows a couple of 'Unknown filesystem type' errors.

Unit proc-fs-nfsd.mount fails: "unknown filesystem type 'nfsd'"

Nov 05 09:41:13 giraufab3.emea.hpqcorp.net mount[846]: mount: unknown filesystem type 'nfsd'
Nov 05 09:41:13 giraufab3.emea.hpqcorp.net systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited status=32
Nov 05 09:41:13 giraufab3.emea.hpqcorp.net systemd[1]: Failed to mount NFSD configuration filesystem.
-- Subject: Unit proc-fs-nfsd.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit proc-fs-nfsd.mount has failed.
--
-- The result is failed.

Unit boot-efi.mount fals, "unknown filesystem type 'vfat'"

Nov 05 09:41:22 giraufab3.emea.hpqcorp.net systemd[1]: Mounting /boot/efi...
-- Subject: Unit boot-efi.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit boot-efi.mount has begun starting up.
Nov 05 09:41:22 giraufab3.emea.hpqcorp.net mount[1369]: mount: unknown filesystem type 'vfat'
Nov 05 09:41:22 giraufab3.emea.hpqcorp.net systemd[1]: boot-efi.mount: Mount process exited, code=exited status=32
Nov 05 09:41:22 giraufab3.emea.hpqcorp.net systemd[1]: Failed to mount /boot/efi.
-- Subject: Unit boot-efi.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit boot-efi.mount has failed.
--
-- The result is failed.

So 'dnf upgrade' has broken my future (4.8.4) and current (4.7.6) kernel boot.

For info (probably not relevant, I guess vfat needs to be hardwired into the kernel):

find /lib/modules/4.* -iname 'vfat' /lib/modules/4.7.3-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz /lib/modules/4.7.6-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz /lib/modules/4.8.4-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz

> find /lib/modules/4.* -iname '*vfat*'
/lib/modules/4.7.3-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz
/lib/modules/4.7.6-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz
/lib/modules/4.8.4-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz

Any ideas?

2016-08-25 09:22:39 -0500 answered a question Emergency Mode when SELinux is enforcing since upgrade to F24

I have a similar problem (after a dnf upgrade, on a running F24 system).

Booting takes me to emergency_mode but I can't login as "/bin/bash: Permission Denied".

If I disable selinux I can boot OK.

So is there a way I can boot from live USB and apply restorecon to my root partition? Any other idea?