how concerning should this be ?new strange boot and shut down messages showed up suddenly
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
how concerning should this be ?new strange boot and shut down messages showed up suddenly
recently my system (Fedora workstation 34) during boot , boot messages changed, also what appears to be the same code executes at shutdown as well. what specifically is the system doing here? how do I determine what the hex code is executing? or is this normal and I an idiot. output for dmesg:
Mon Nov 15 17:17:46 2021] proc: Bad value for 'hidepid'
[Mon Nov 15 17:17:46 2021] [drm] enabling PCIE gen 3 link speeds, disable with radeon.pcie_gen2=0
[Mon Nov 15 17:17:47 2021] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
[Mon Nov 15 17:17:47 2021] radeon 0000:01:00.0: WB enabled
[Mon Nov 15 17:17:47 2021] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x00000000e758f45e
[Mon Nov 15 17:17:47 2021] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0x00000000ce8bc762
[Mon Nov 15 17:17:47 2021] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0x000000008ec3fc35
[Mon Nov 15 17:17:47 2021] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x00000000a974746e
[Mon Nov 15 17:17:47 2021] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0x000000005d9a4105
[Mon Nov 15 17:17:47 2021] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0x000000004b47c483
[Mon Nov 15 17:17:47 2021] radeon 0000:01:00.0: failed VCE resume (-110).
[Mon Nov 15 17:17:48 2021] [drm] ring test on 0 succeeded in 1 usecs
[Mon Nov 15 17:17:48 2021] [drm] ring test on 1 succeeded in 1 usecs
[Mon Nov 15 17:17:48 2021] [drm] ring test on 2 succeeded in 1 usecs
[Mon Nov 15 17:17:48 2021] [drm] ring test on 3 succeeded in 3 usecs
[Mon Nov 15 17:17:48 2021] [drm] ring test on 4 succeeded in 3 usecs
[Mon Nov 15 17:17:48 2021] [drm] ring test on 5 succeeded in 2 usecs
[Mon Nov 15 17:17:48 2021] [drm] UVD initialized successfully.
[Mon Nov 15 17:17:48 2021] [drm] ib test on ring 0 succeeded in 0 usecs
[Mon Nov 15 17:17:48 2021] [drm] ib test on ring 1 succeeded in 0 usecs
[Mon Nov 15 17:17:48 2021] [drm] ib test on ring 2 succeeded in 0 usecs
[Mon Nov 15 17:17:48 2021] [drm] ib test on ring 3 succeeded in 0 usecs
[Mon Nov 15 17:17:48 2021] [drm] ib test on ring 4 succeeded in 0 usecs
[Mon Nov 15 17:17:48 2021] [drm] ib test on ring 5 succeeded
[Mon Nov 15 17:18:45 2021] proc: Bad value for 'hidepid'
[Mon Nov 15 17:21:02 2021] proc: Bad value for 'hidepid'
[Mon Nov 15 17:21:25 2021] proc: Bad value for 'hidepid'
[Mon Nov 15 17:25:52 2021] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[Mon Nov 15 17:25:52 2021] packagekitd[1485]: segfault at ffffffffffffff88 ip 00007f65fc0cbbd4 sp 00007ffc0493dba0 error 7 in libdnf.so.2[7f65fc08a000+ed000]
[Mon Nov 15 17:25:52 2021] Code: 8d 3d 50 b4 0a 00 53 89 d3 48 8d 15 43 d0 0a 00 48 83 ec 08 4c 63 2d 43 ef 0f 00 e8 16 8c fc ff f6 c3 01 75 21 83 e3 02 74 0c <42> c7 84 2d b8 00 00 00 00 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d
[Mon Nov 15 17:25:52 2021] proc: Bad value for 'hidepid'
[Mon Nov 15 17:34:23 2021] proc: Bad value for 'hidepid'
[Mon Nov 15 17:43:59 2021] SELinux: Converting 716 SID table entries...
[Mon Nov 15 17:43:59 2021] SELinux: policy capability network_peer_controls=1
[Mon Nov 15 17:43:59 2021] SELinux: policy capability open_perms=1
[Mon Nov 15 17:43:59 2021] SELinux: policy capability extended_socket_class=1
[Mon Nov 15 17:43:59 2021] SELinux: policy capability always_check_network=0
[Mon Nov 15 17:43:59 2021] SELinux: policy capability cgroup_seclabel=1
[Mon Nov 15 17:43:59 2021] SELinux: policy capability nnp_nosuid_transition=1
[Mon Nov 15 17:47:49 2021] systemd-sysv-generator[20943]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native sy>
[Mon Nov 15 17:47:49 2021] systemd-sysv-generator[20943]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd>
[Mon Nov 15 17:47:50 2021] systemd-sysv-generator[21926]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native sy>
[Mon Nov 15 17:47:50 2021] systemd-sysv-generator[21926]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd>
PackageKit provides a common interface to various update software, in your case dnf. The error suggests there is a bug in either packagekitd or libdnf.so. I suppose the code is what it was executing at the time, but it doesn't seem to be particularly helpful, does it? error 7 usually means "Argument list too long", which might be some kind of clue. Current on my Fedora 34 system is:
"radeon" has something to do with AMD graphics. "drm" too, indirectly.
"systemd-sysv-generator" clearly tells you what the matter is - it's more of a notice/warning anyhow.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.