Ask Your Question
1

Emergency mode in Fedora 29

asked 2019-02-02 13:16:56 -0600

pueffl gravatar image

Hi there!

I run into emergency mode with the newest kernel (4.20.5-200.fc29.x86_64) and I don't know why. Can anyone please help? Running the previous kernel is ok.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2019-02-02 13:19:55 -0600

pueffl gravatar image

...would like to add output of journalctl -xb but have no idea how...

edit flag offensive delete link more
1

answered 2019-02-02 13:18:04 -0600

pueffl gravatar image

-- Logs begin at Tue 2019-01-08 21:43:19 CET, end at Sat 2019-02-02 19:59:11 CET. -- Feb 02 20:58:56 localhost.localdomain kernel: Linux version 4.20.5-200.fc29.x86_64 (mockbuild@bkernel04.phx2.fedoraprojec...) (gcc version 8.2.1 20181215 (Red Hat 8.2.1-6) (GCC)) #1 SMP Mon Jan 28 19:29:17 UTC 2019 Feb 02 20:58:56 localhost.localdomain kernel: Command line: BOOT_IMAGE=/vmlinuz-4.20.5-200.fc29.x86_64 root=/dev/mapper/fedora-root ro resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=de_AT.UTF-8 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 Feb 02 20:58:56 localhost.localdomain kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Feb 02 20:58:56 localhost.localdomain kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Feb 02 20:58:56 localhost.localdomain kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Feb 02 20:58:56 localhost.localdomain kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Feb 02 20:58:56 localhost.localdomain kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Feb 02 20:58:56 localhost.localdomain kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Feb 02 20:58:56 localhost.localdomain kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Feb 02 20:58:56 localhost.localdomain kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Feb 02 20:58:56 localhost.localdomain kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Feb 02 20:58:56 localhost.localdomain kernel: BIOS-provided physical RAM map: Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003ded2fff] usable Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x000000003ded3000-0x000000004ee5efff] reserved Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x000000004ee5f000-0x000000004fca0fff] ACPI NVS Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x000000004fca1000-0x000000004fd0efff] ACPI data Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x000000004fd0f000-0x000000004fd0ffff] usable Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x000000004fd10000-0x0000000057ffffff] reserved Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000058000000-0x00000000581fffff] usable Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000058200000-0x0000000059ffffff] reserved Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000fe010000-0x00000000fe010fff] reserved Feb 02 20:58:56 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008a3ffffff] usable Feb 02 20:58:56 localhost.localdomain kernel: NX (Execute Disable) protection: active Feb 02 20:58:56 localhost.localdomain kernel: e820: update [mem 0x32e06018-0x32e2f657] usable ==> usable Feb 02 20:58:56 localhost.localdomain kernel: e820: update [mem 0x32e06018-0x32e2f657] usable ==> usable Feb 02 20:58:56 localhost.localdomain kernel: extended physical RAM map: Feb 02 20:58:56 localhost.localdomain kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable Feb 02 20:58:56 localhost.localdomain kernel: reserve setup_data: [mem 0x000000000009f000-0x00000000000fffff] reserved ... (more)

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2019-02-02 13:16:56 -0600

Seen: 64 times

Last updated: Feb 02