You are not logged in.
Pages: 1
Hi all,
I'm seeing these error messages during boot:
Failed to start Rebuild Hardware Database.
Failed to mount FUSE Control File System.
Failed to start First Boot Wizard.
and with:
$ journalctl -p 3 -xb
-- Logs begin at Sat 2019-01-26 17:41:23 CET, end at Sat 2019-06-29 18:22:41 CEST. --
Jun 29 18:07:37 hostname kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190215/psargs-330)
Jun 29 18:07:37 hostname kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190215/psparse-529)
Jun 29 18:07:37 hostname kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190215/psargs-330)
Jun 29 18:07:37 hostname kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190215/psparse-529)
Jun 29 18:07:37 hostname kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190215/psargs-330)
Jun 29 18:07:37 hostname kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190215/psparse-529)
Jun 29 18:07:37 hostname kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190215/psargs-330)
Jun 29 18:07:37 hostname kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190215/psparse-529)
Jun 29 18:07:37 hostname kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190215/psargs-330)
Jun 29 18:07:37 hostname kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190215/psparse-529)
Jun 29 18:07:37 hostname kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190215/psargs-330)
Jun 29 18:07:37 hostname kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190215/psparse-529)
Jun 29 18:07:37 hostname kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20190215/psargs-330)
Jun 29 18:07:37 hostname kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20190215/psparse-529)
Jun 29 18:07:37 hostname kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20190215/psargs-330)
Jun 29 18:07:37 hostname kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20190215/psparse-529)
Jun 29 18:07:37 hostname kernel: sd 11:0:0:0: [sdf] No Caching mode page found
Jun 29 18:07:37 hostname kernel: sd 11:0:0:0: [sdf] Assuming drive cache: write through
Jun 29 18:07:37 hostname kernel: usb 3-1.7: device descriptor read/64, error -32
Jun 29 18:07:37 hostname systemd-udevd[410]: Specified group 'plugdev' unknown
Jun 29 18:07:38 hostname systemd[1]: Failed to start Rebuild Hardware Database.
-- Subject: A start job for unit systemd-hwdb-update.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit systemd-hwdb-update.service has finished with a failure.
--
-- The job identifier is 612 and the job result is failed.
Jun 29 18:07:38 hostname systemd[1]: Failed to mount FUSE Control File System.
-- Subject: A start job for unit sys-fs-fuse-connections.mount has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit sys-fs-fuse-connections.mount has finished with a failure.
--
-- The job identifier is 611 and the job result is failed.
Jun 29 18:07:38 hostname systemd[1]: Failed to start First Boot Wizard.
-- Subject: A start job for unit systemd-firstboot.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit systemd-firstboot.service has finished with a failure.and more with:
$ journalctl --since "30 minutes ago"
Jun 29 18:07:38 hostname systemd[1]: Failed to parse swap priority "defaults,pri=-2", ignoring: Numerical result out of range
Jun 29 18:07:38 hostname systemd[1]: Activating swap /dev/disk/by-uuid/...
Jun 29 18:07:38 hostname kernel: Adding 62914556k swap on /dev/sdb2. Priority:-2 extents:1 across:62914556k FS
Jun 29 18:07:38 hostname systemd[1]: Activated swap /dev/disk/by-uuid/e18a88d8-bb3b-40e7-9b98-fd19ddd61ef9.
Jun 29 18:07:38 hostname kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card2/input15
Jun 29 18:07:38 hostname kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card2/input16
Jun 29 18:07:38 hostname kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card2/input17
Jun 29 18:07:38 hostname systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Jun 29 18:07:38 hostname systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Jun 29 18:07:38 hostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Jun 29 18:07:38 hostname systemd[1]: Reached target Swap.
Jun 29 18:07:38 hostname systemd-udevd[463]: Process '/usr/bin/alsactl restore 2' failed with exit code 99.
Jun 29 18:07:38 hostname systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
Jun 29 18:07:38 hostname systemd[1]: Failed to start Rebuild Hardware Database.
Jun 29 18:07:38 hostname systemd[1]: sys-fs-fuse-connections.mount: Start request repeated too quickly.
Jun 29 18:07:38 hostname systemd[1]: Failed to mount FUSE Control File System.
Jun 29 18:07:38 hostname systemd[1]: systemd-firstboot.service: Start request repeated too quickly.
Jun 29 18:07:38 hostname systemd[1]: Failed to start First Boot Wizard.
Jun 29 18:07:38 hostname systemd-udevd[414]: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
Jun 29 18:07:38 hostname kernel: nvidia: module license 'NVIDIA' taints kernel.
Jun 29 18:07:38 hostname kernel: Disabling lock debugging due to kernel taint
Jun 29 18:07:38 hostname kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 236
Jun 29 18:07:38 hostname kernel: nvidia 0000:02:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Jun 29 18:07:38 hostname kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 430.26 Tue Jun 4 17:40:52 CDT 2019
Jun 29 18:07:38 hostname kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 430.26 Tue Jun 4 17:45:09 CDT 2019
Jun 29 18:07:38 hostname kernel: [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver
Jun 29 18:07:38 hostname kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:02:00.0 on minor 0
Jun 29 18:07:40 hostname kernel: snd_hda_intel 0000:00:1b.0: azx_get_response timeout, switching to polling mode: last cmd=0x300f0000
Jun 29 18:07:41 hostname kernel: snd_hda_intel 0000:00:1b.0: No response from codec, disabling MSI: last cmd=0x300f0000
Jun 29 18:07:42 hostname kernel: snd_hda_intel 0000:00:1b.0: Codec #3 probe error; disabling it...
Jun 29 18:07:42 hostname kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC892: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Jun 29 18:07:42 hostname kernel: snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)It seems to be related with the package nvidia-dkms 430.26 since it appeared after upgrading it from nvidia-dkms 430.18. But even with nvidia-dkms 430.18 at some point, booting with linux froze at the line "loading graphical user interface", that's why I tried to upgrade.
Has anyone else the same issue?
Any ideas how to resolve it?
Offline
Pages: 1