Ok. Thanks!
Bowen
On Tue, Aug 15, 2017 at 11:21:31PM -0700, Adam Williamson wrote:
> On Tue, 2017-08-15 at 22:21 -0500, Bowen Wang wrote:
> > Hi Everyone,
> > After I upgraded my rawhide to 0811(I am not very sure about the date, but it
> > should be around this date), the system cannot be boot up even after I did the
> > upgrade on 0815.
> >
> > Here are the output from dmesg(I get this information using ssh):
> > [ 18.986579] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
> > [ 18.988601] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
> > [ 21.619237] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
> > [ 21.619654] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
> > [ 23.969115] systemd-udevd[1126]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
> > [ 23.969292] systemd-udevd[1126]: Could not generate persistent MAC address for virbr0: No such file or directory
> > [ 23.989317] tun: Universal TUN/TAP device driver, 1.6
> > [ 23.989688] systemd-journald[1130]: Failed to map sequential number file, ignoring: Permission denied
> > [ 23.991398] virbr0: port 1(virbr0-nic) entered blocking state
> > [ 23.991403] virbr0: port 1(virbr0-nic) entered disabled state
> > [ 23.991453] systemd-journald[1130]: Failed to open runtime journal: Permission denied
> > [ 23.991484] device virbr0-nic entered promiscuous mode
> > [ 23.993860] systemd-udevd[1133]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
> > [ 24.005632] systemd-journald[1135]: Failed to map sequential number file, ignoring: Permission denied
> > [ 24.005941] systemd-journald[1135]: Failed to open runtime journal: Permission denied
> > [ 24.018793] systemd-journald[1138]: Failed to map sequential number file, ignoring: Permission denied
> > [ 24.019090] systemd-journald[1138]: Failed to open runtime journal: Permission denied
> > [ 24.031254] systemd-journald[1141]: Failed to map sequential number file, ignoring: Permission denied
> > [ 24.031572] systemd-journald[1141]: Failed to open runtime journal: Permission denied
> > [ 24.043386] systemd-journald[1144]: Failed to map sequential number file, ignoring: Permission denied
> > [ 24.043691] systemd-journald[1144]: Failed to open runtime journal: Permission denied
> > [ 24.181318] virbr0: port 1(virbr0-nic) entered blocking state
> > [ 24.181330] virbr0: port 1(virbr0-nic) entered listening state
> > [ 24.299972] virbr0: port 1(virbr0-nic) entered disabled state
> > [ 24.648320] systemd-logind[871]: Removed session c1.
> > [ 24.705753] systemd-logind[871]: New session c2 of user gdm.
> > [ 25.212613] systemd-logind[871]: Removed session c2.
> > [ 25.256314] systemd-logind[871]: Failed to remove runtime directory /run/user/42: Permission denied
> > [ 25.285529] systemd-logind[871]: New session c3 of user gdm.
> >
> > [ 27.249568] ======================================================
> > [ 27.249569] WARNING: possible circular locking dependency detected
> > [ 27.249570] 4.13.0-0.rc4.git4.1.fc27.x86_64 #1 Not tainted
> > [ 27.249571] ------------------------------------------------------
> > [ 27.249572] Xorg/1344 is trying to acquire lock:
> > [ 27.249572] (reservation_ww_class_mutex){+.+.+.}, at: [<ffffffffc04c68b8>] i915_gem_object_set_tiling+0x118/0x330 [i915]
> > [ 27.249618]
> > but task is already holding lock:
> > [ 27.249619] (&dev->struct_mutex){+.+.+.}, at: [<ffffffffc04c6c6b>] i915_gem_set_tiling_ioctl+0x19b/0x350 [i915]
> > [ 27.249639]
> > which lock already depends on the new lock.
> >
> > [ 27.249640]
> > the existing dependency chain (in reverse order) is:
> > [ 27.249641]
> > -> #1 (&dev->struct_mutex){+.+.+.}:
> > [ 27.249647] lock_acquire+0xa3/0x1f0
> > [ 27.249658] drm_gem_object_put_unlocked+0x3d/0xb0 [drm]
> > [ 27.249690] validate_fini_no_ticket+0xf5/0x130 [nouveau]
> > [ 27.249708] nouveau_gem_ioctl_pushbuf+0x65f/0x10f0 [nouveau]
> > [ 27.249716] drm_ioctl_kernel+0x5d/0xb0 [drm]
> > [ 27.249721] drm_ioctl+0x31b/0x3d0 [drm]
> > [ 27.249736] nouveau_drm_ioctl+0x72/0xc0 [nouveau]
> > [ 27.249738] do_vfs_ioctl+0xa6/0x6c0
> > [ 27.249739] SyS_ioctl+0x79/0x90
> > [ 27.249741] entry_SYSCALL_64_fastpath+0x1f/0xbe
> > [ 27.249742]
> > -> #0 (reservation_ww_class_mutex){+.+.+.}:
> > [ 27.249745] __lock_acquire+0x1367/0x13b0
> > [ 27.249747] lock_acquire+0xa3/0x1f0
> > [ 27.249748] __ww_mutex_lock.constprop.9+0xa1/0x10c0
> > [ 27.249749] ww_mutex_lock+0x5e/0x70
> > [ 27.249769] i915_gem_object_set_tiling+0x118/0x330 [i915]
> > [ 27.249782] i915_gem_set_tiling_ioctl+0x1b4/0x350 [i915]
> > [ 27.249788] drm_ioctl_kernel+0x5d/0xb0 [drm]
> > [ 27.249792] drm_ioctl+0x31b/0x3d0 [drm]
> > [ 27.249793] do_vfs_ioctl+0xa6/0x6c0
> > [ 27.249794] SyS_ioctl+0x79/0x90
> > [ 27.249796] entry_SYSCALL_64_fastpath+0x1f/0xbe
> > [ 27.249797]
> > other info that might help us debug this:
> >
> > [ 27.249798] Possible unsafe locking scenario:
> >
> > [ 27.249799] CPU0 CPU1
> > [ 27.249799] ---- ----
> > [ 27.249800] lock(&dev->struct_mutex);
> > [ 27.249801] lock(reservation_ww_class_mutex);
> > [ 27.249802] lock(&dev->struct_mutex);
> > [ 27.249803] lock(reservation_ww_class_mutex);
> > [ 27.249804]
> > *** DEADLOCK ***
> >
> > [ 27.249806] 1 lock held by Xorg/1344:
> > [ 27.249806] #0: (&dev->struct_mutex){+.+.+.}, at: [<ffffffffc04c6c6b>] i915_gem_set_tiling_ioctl+0x19b/0x350 [i915]
> > [ 27.249820]
> > stack backtrace:
> > [ 27.249822] CPU: 0 PID: 1344 Comm: Xorg Not tainted 4.13.0-0.rc4.git4.1.fc27.x86_64 #1
> > [ 27.249823] Hardware name: Gigabyte Technology Co., Ltd. Z97X-UD5H/Z97X-UD5H, BIOS F8 06/17/2014
> > [ 27.249824] Call Trace:
> > [ 27.249827] dump_stack+0x8e/0xd6
> > [ 27.249828] print_circular_bug+0x1b6/0x210
> > [ 27.249830] __lock_acquire+0x1367/0x13b0
> > [ 27.249832] lock_acquire+0xa3/0x1f0
> > [ 27.249834] ? lock_acquire+0xa3/0x1f0
> > [ 27.249846] ? i915_gem_object_set_tiling+0x118/0x330 [i915]
> > [ 27.249858] ? i915_gem_object_set_tiling+0x118/0x330 [i915]
> > [ 27.249860] __ww_mutex_lock.constprop.9+0xa1/0x10c0
> > [ 27.249871] ? i915_gem_object_set_tiling+0x118/0x330 [i915]
> > [ 27.249873] ? debug_lockdep_rcu_enabled+0x1d/0x30
> > [ 27.249875] ? __lock_is_held+0x65/0xb0
> > [ 27.249877] ww_mutex_lock+0x5e/0x70
> > [ 27.249878] ? ww_mutex_lock+0x5e/0x70
> > [ 27.249889] i915_gem_object_set_tiling+0x118/0x330 [i915]
> > [ 27.249901] i915_gem_set_tiling_ioctl+0x1b4/0x350 [i915]
> > [ 27.249912] ? i915_gem_object_set_tiling+0x330/0x330 [i915]
> > [ 27.249917] drm_ioctl_kernel+0x5d/0xb0 [drm]
> > [ 27.249922] drm_ioctl+0x31b/0x3d0 [drm]
> > [ 27.249933] ? i915_gem_object_set_tiling+0x330/0x330 [i915]
> > [ 27.249935] ? __might_sleep+0x4a/0x80
> > [ 27.249937] do_vfs_ioctl+0xa6/0x6c0
> > [ 27.249939] SyS_ioctl+0x79/0x90
> > [ 27.249941] entry_SYSCALL_64_fastpath+0x1f/0xbe
> > [ 27.249942] RIP: 0033:0x7fa9f27a0277
> > [ 27.249943] RSP: 002b:00007ffe2177ef28 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
> > [ 27.249944] RAX: ffffffffffffffda RBX: 00007fa9e37c78a8 RCX: 00007fa9f27a0277
> > [ 27.249945] RDX: 00007ffe2177ef30 RSI: 00000000c0106461 RDI: 000000000000000d
> > [ 27.249945] RBP: 00007fa9e32ac180 R08: 00000000017cd900 R09: 00000000017cd900
> > [ 27.249946] R10: 0000000000000001 R11: 0000000000000246 R12: 00007ffe2177eff0
> > [ 27.249947] R13: 00000000017a7020 R14: 00000000017a6fb8 R15: 0000000000000000
> > [ 29.049706] systemd-logind[871]: Removed session c3.
> > [ 29.081546] systemd-logind[871]: Failed to remove runtime directory /run/user/42: Permission denied
> > [ 29.160756] systemd-logind[871]: New session c4 of user gdm.
> > [ 29.334968] systemd-logind[871]: Removed session c4.
> > [ 29.360063] systemd-logind[871]: Failed to remove runtime directory /run/user/42: Permission denied
> > [ 30.953645] systemd-logind[871]: Removed session c5.
> > [ 30.984611] systemd-logind[871]: Failed to remove runtime directory /run/user/42: Permission denied
> > [ 31.001911] systemd-logind[871]: New session c6 of user gdm.
> > [ 32.579152] systemd-logind[871]: Removed session c6.
> > [ 32.609583] systemd-logind[871]: Failed to remove runtime directory /run/user/42: Permission denied
> > [ 32.627687] systemd-logind[871]: New session c7 of user gdm.
> > [ 34.018140] systemd-journald[1970]: Failed to map sequential number file, ignoring: Permission denied
> > [ 34.018522] systemd-journald[1970]: Failed to open runtime journal: Permission denied
> > [ 34.027269] systemd-journald[1972]: Failed to map sequential number file, ignoring: Permission denied
> > [ 34.027502] systemd-journald[1972]: Failed to open runtime journal: Permission denied
> > [ 34.036590] systemd-journald[1973]: Failed to map sequential number file, ignoring: Permission denied
> > [ 34.036800] systemd-journald[1973]: Failed to open runtime journal: Permission denied
> > [ 34.045227] systemd-journald[1975]: Failed to map sequential number file, ignoring: Permission denied
> > [ 34.045477] systemd-journald[1975]: Failed to open runtime journal: Permission denied
> > [ 34.054090] systemd-journald[1977]: Failed to map sequential number file, ignoring: Permission denied
> > [ 34.054306] systemd-journald[1977]: Failed to open runtime journal: Permission denied
> > [ 34.325938] systemd-logind[871]: Removed session c7.
> > [ 34.362383] systemd-logind[871]: Failed to remove runtime directory /run/user/42: Permission denied
> > [ 34.377764] systemd-logind[871]: New session c8 of user gdm.
> > [ 36.152022] systemd-logind[871]: Removed session c8.
> > [ 36.181666] systemd-logind[871]: Failed to remove runtime directory /run/user/42: Permission denied
> > [ 36.197316] systemd-logind[871]: New session c9 of user gdm.
> > [ 37.983927] systemd-logind[871]: Removed session c9.
> > [ 38.014761] systemd-logind[871]: Failed to remove runtime directory /run/user/42: Permission denied
> > [ 53.316947] systemd-logind[871]: New session 10 of user bwang.
> >
> >
> > It seems there is something wrong with the systemd and the file system journal
> > part.
> >
> > Anyone knows what the problem is?
>
> I sent a mail out just the other day about this and other issues caused
> by a new SELinux permission being introduced. Try booting with
> enforcing=0 . A new selinux-policy-targeted build should show up for
> you soon which is expected to fix most of the problems.
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> http://www.happyassassin.net
> _______________________________________________
> test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
