마지막 커널 업데이트 후 부팅할 수 없습니다(Fedora 23)

2024-5-23 • tag-icon

커널 4.2.8-300에서 제대로 실행되는 Fedora 23 시스템이 있습니다. 4.3.3-300 및 4.3.3-301로 업데이트했지만 둘 다 부팅되지 않습니다. 단일 사용자 모드에서도 마찬가지입니다.

화면에 보이는 것은 다음과 같습니다.

오류가 표시되지 않습니다. 문제가 무엇인지 아시나요?

편집하다

마지막 메시지 중 하나가 에 관한 것이었기 때문에 plymouth이전 커널로 부팅하고 완전히 제거했는지 확인하기 위한 것이었습니다. 변경 없음.

편집 2

grub.cfg항목은 동일한 것 같습니다(그러나 버전 번호는 다름).

직업 1:

menuentry 'Fedora (4.2.8-300.fc23.i686+PAE) 23 (Twenty Three)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-14f2ed60-6348-41b7-ade0-a4849a0d4d5a' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'  4001c5e3-fb16-4c71-9291-c48fd94ddc14
    else
      search --no-floppy --fs-uuid --set=root 4001c5e3-fb16-4c71-9291-c48fd94ddc14
    fi
    echo 'Loading Fedora (4.2.8-300.fc23.i686+PAE) 23 (Twenty Three)'
    linux   /vmlinuz-4.2.8-300.fc23.i686+PAE root=/dev/vg_matteo2/lv_root ro quiet rhgb LANG=en_US.UTF-8
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-4.2.8-300.fc23.i686+PAE.img
}

새로운 것:

menuentry 'Fedora (4.3.3-301.fc23.i686+PAE) 23 (Twenty Three)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-14f2ed60-6348-41b7-ade0-a4849a0d4d5a' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'  4001c5e3-fb16-4c71-9291-c48fd94ddc14
    else
      search --no-floppy --fs-uuid --set=root 4001c5e3-fb16-4c71-9291-c48fd94ddc14
    fi
    echo 'Loading Fedora (4.3.3-301.fc23.i686+PAE) 23 (Twenty Three)'
    linux   /vmlinuz-4.3.3-301.fc23.i686+PAE root=/dev/vg_matteo2/lv_root ro quiet rhgb LANG=en_US.UTF-8
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-4.3.3-301.fc23.i686+PAE.img
}

Citrix에서는 VMWare 클라이언트를 통해서만 콘솔에 접근할 수 있기 때문에 시리얼 콘솔에 접근하는 것이 그리 쉽지는 않을 것 같아요...

편집 3

커널 요약:

4.2.8-300 부츠(문제 없음)
실제로 4.3.3-300아니요시작하다
4.3.3-301 실제로아니요시작하다
실제로 4.3.3-303아니요시작하다
실제로 4.3.5-300아니요시작하다

편집 4

새로 출시된 커널로 테스트 4.3.4-300: 여전히 동일한 문제

마지막 메시지는 DRM에 관한 것이었기 때문에 DRM을 비활성화하려고 시도했지만 성공하지 못했습니다.

    linux   /vmlinuz-4.3.4-300.fc23.i686+PAE root=/dev/vg_matteo2/lv_root ro LANG=en_US.UTF-8 vga=normal nofb nomodeset video=vesafb:off i915.modeset=0 3

하지만 문제는 여전히 존재하며 최종 메시지는 여전히 동일합니다.

편집 5

제안한대로 시도했지만 i915.preliminary_hw_support=1얻었습니다.

vmwgfx 0000:00:0f.0: BAR 1: can't reserve [mem 0xf8000000-0xfbffffff]

편집 6

새 커널(4.4.2-301)을 사용하면 i915.preliminary_hw_support=1여전히 부팅할 수 없지만 최소한 콘솔의 출력은 읽을 수 있습니다.

일부 정보는 다음과 같이 작성됩니다 /var/log/messages/.

Feb 29 13:23:59 matteo kernel: [drm] Legacy Display Unit initialized
Feb 29 13:23:59 matteo kernel: [drm] width 1600
Feb 29 13:24:00 matteo kernel: [drm] height 1200
Feb 29 13:24:00 matteo kernel: [drm] bpp 32
Feb 29 13:24:00 matteo kernel: [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000007f
Feb 29 13:24:00 matteo kernel: [drm] DX: no.
Feb 29 13:24:00 matteo kernel: fb: switching to svgadrmfb from VESA VGA
Feb 29 13:24:00 matteo kernel: Console: switching to colour dummy device 80x25
Feb 29 13:24:00 matteo kernel: fbcon: svgadrmfb (fb0) is primary device
Feb 29 13:24:00 matteo kernel: fbcon_init: detected unhandled fb_set_par error, error code -22
Feb 29 13:24:00 matteo kernel: Console: switching to colour frame buffer device 200x75
Feb 29 13:24:00 matteo kernel: BUG: unable to handle kernel NULL pointer dereference at 00000068
Feb 29 13:24:00 matteo kernel: IP: [<f8a97c12>] vmw_fb_setcolreg+0x22/0xb0 [vmwgfx]
Feb 29 13:24:00 matteo kernel: *pdpt = 00000000369fc001 *pde = 0000000000000000 
Feb 29 13:24:00 matteo kernel: Oops: 0000 [#1] SMP 
Feb 29 13:24:00 matteo kernel: Modules linked in: crc32c_intel vmw_balloon joydev vmwgfx(+) ttm drm_kms_helper i2c_piix4 parport_pc vmw_vmci parport drm acpi_cpufreq tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd gr
ace sunrpc mptspi scsi_transport_spi mptscsih e1000 mptbase serio_raw ata_generic pata_acpi fjes
Feb 29 13:24:00 matteo kernel: CPU: 1 PID: 617 Comm: systemd-udevd Not tainted 4.4.2-301.fc23.i686+PAE #1
Feb 29 13:24:00 matteo kernel: Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/17/2015
Feb 29 13:24:00 matteo kernel: task: f6b21000 ti: f6b40000 task.ti: f6b40000
Feb 29 13:24:00 matteo kernel: EIP: 0060:[<f8a97c12>] EFLAGS: 00010293 CPU: 1
Feb 29 13:24:00 matteo kernel: EIP is at vmw_fb_setcolreg+0x22/0xb0 [vmwgfx]
Feb 29 13:24:00 matteo kernel: EAX: 00000000 EBX: f104235c ECX: 00000000 EDX: 00000000
Feb 29 13:24:00 matteo kernel: ESI: 00000000 EDI: 00000000 EBP: f6b418c4 ESP: f6b418a8
Feb 29 13:24:00 matteo kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Feb 29 13:24:00 matteo kernel: CR0: 80050033 CR2: 00000068 CR3: 327e8640 CR4: 000006f0
Feb 29 13:24:00 matteo kernel: Stack:
Feb 29 13:24:01 matteo kernel: f6b418c0 00000082 00000021 00000000 00000000 00000000 f8a97bf0 f6b41908
Feb 29 13:24:01 matteo kernel: c07b95bd 00000000 0000ffff f1042000 c102cc40 c102cc60 c102cc80 00000000
Feb 29 13:24:01 matteo kernel: c0e381dc 0000ffff 00000000 f1042000 f8a97bf0 f1042000 f703c204 f703c204
Feb 29 13:24:01 matteo kernel: Call Trace:
Feb 29 13:24:01 matteo kernel: [<f8a97bf0>] ? vmw_fb_fillrect+0x40/0x40 [vmwgfx]
Feb 29 13:24:01 matteo kernel: [<c07b95bd>] fb_set_cmap+0xed/0x130
Feb 29 13:24:01 matteo kernel: [<f8a97bf0>] ? vmw_fb_fillrect+0x40/0x40 [vmwgfx]
Feb 29 13:24:01 matteo kernel: [<c07a93d0>] fbcon_set_palette+0x130/0x160
Feb 29 13:24:01 matteo kernel: [<c07ac069>] fbcon_switch+0x3c9/0x630
Feb 29 13:24:01 matteo kernel: [<c082e0b3>] redraw_screen+0x163/0x250
Feb 29 13:24:01 matteo kernel: [<c082ecd9>] do_bind_con_driver+0x269/0x350
Feb 29 13:24:01 matteo kernel: [<c082f0ce>] do_take_over_console+0x13e/0x1b0
Feb 29 13:24:01 matteo kernel: [<c07aa0cf>] do_fbcon_takeover+0x5f/0xc0
Feb 29 13:24:01 matteo kernel: [<c07aebb7>] fbcon_event_notify+0x687/0x780
Feb 29 13:24:01 matteo kernel: [<c048ccce>] notifier_call_chain+0x4e/0x70
Feb 29 13:24:01 matteo kernel: [<c048d019>] __blocking_notifier_call_chain+0x39/0x60
Feb 29 13:24:01 matteo kernel: [<c048d05f>] blocking_notifier_call_chain+0x1f/0x30
Feb 29 13:24:01 matteo kernel: [<c07b3ec6>] fb_notifier_call_chain+0x16/0x20
Feb 29 13:24:01 matteo kernel: [<c07b5de1>] register_framebuffer+0x1f1/0x330
Feb 29 13:24:01 matteo kernel: [<f8a98b0b>] vmw_fb_init+0x39b/0x440 [vmwgfx]
Feb 29 13:24:01 matteo kernel: [<f8a97412>] vmw_driver_load+0xd72/0xfc0 [vmwgfx]
Feb 29 13:24:01 matteo kernel: [<f89bfb6e>] drm_dev_register+0x8e/0xa0 [drm]
Feb 29 13:24:01 matteo kernel: [<f89c1fd9>] drm_get_pci_dev+0x79/0x1c0 [drm]
Feb 29 13:24:01 matteo kernel: [<f8a95b22>] vmw_probe+0x12/0x20 [vmwgfx]
Feb 29 13:24:01 matteo kernel: [<c07888cb>] pci_device_probe+0x7b/0xf0
Feb 29 13:24:01 matteo kernel: [<c086c969>] ? devices_kset_move_last+0x49/0xa0
Feb 29 13:24:01 matteo kernel: [<c0870259>] driver_probe_device+0x1f9/0x490
Feb 29 13:24:01 matteo kernel: [<c063ed77>] ? sysfs_create_dir_ns+0x37/0x90
Feb 29 13:24:01 matteo kernel: [<c07885a1>] ? pci_match_device+0xc1/0xe0
Feb 29 13:24:01 matteo kernel: [<c0870569>] __driver_attach+0x79/0x80
Feb 29 13:24:01 matteo kernel: [<c08704f0>] ? driver_probe_device+0x490/0x490
Feb 29 13:24:01 matteo kernel: [<c086e0e7>] bus_for_each_dev+0x57/0xa0
Feb 29 13:24:01 matteo kernel: [<c086fa9e>] driver_attach+0x1e/0x20
Feb 29 13:24:01 matteo kernel: [<c08704f0>] ? driver_probe_device+0x490/0x490
Feb 29 13:24:01 matteo kernel: [<c086f63f>] bus_add_driver+0x1ef/0x290
Feb 29 13:24:01 matteo kernel: [<f899f000>] ? 0xf899f000
Feb 29 13:24:01 matteo kernel: [<f899f000>] ? 0xf899f000
Feb 29 13:24:01 matteo kernel: [<c0870d6d>] driver_register+0x5d/0xf0
Feb 29 13:24:02 matteo kernel: [<c07870b3>] __pci_register_driver+0x33/0x40
Feb 29 13:24:02 matteo kernel: [<f89c21fd>] drm_pci_init+0xdd/0x100 [drm]
Feb 29 13:24:02 matteo kernel: [<f899f000>] ? 0xf899f000
Feb 29 13:24:02 matteo kernel: [<f899f013>] vmwgfx_init+0x13/0x1000 [vmwgfx]
Feb 29 13:24:02 matteo kernel: [<c040211a>] do_one_initcall+0xaa/0x200
Feb 29 13:24:02 matteo kernel: [<f899f000>] ? 0xf899f000
Feb 29 13:24:02 matteo kernel: [<c05ba3e9>] ? kfree+0x119/0x130
Feb 29 13:24:02 matteo kernel: [<c05a4eb5>] ? __vunmap+0xa5/0xf0
Feb 29 13:24:02 matteo kernel: [<c05b9875>] ? kmem_cache_alloc_trace+0x165/0x1d0
Feb 29 13:24:02 matteo kernel: [<c0568ac7>] ? do_init_module+0x21/0x1b5
Feb 29 13:24:02 matteo kernel: [<c0568ac7>] ? do_init_module+0x21/0x1b5
Feb 29 13:24:02 matteo kernel: [<c0568af6>] do_init_module+0x50/0x1b5
Feb 29 13:24:02 matteo kernel: [<c04f5393>] load_module+0x1dd3/0x23d0
Feb 29 13:24:02 matteo kernel: [<c05a524e>] ? __vmalloc_node_range+0x14e/0x240
Feb 29 13:24:02 matteo kernel: [<c04f5abf>] SyS_init_module+0x12f/0x190
Feb 29 13:24:02 matteo kernel: [<c040382d>] do_fast_syscall_32+0x8d/0x150
Feb 29 13:24:02 matteo kernel: [<c0b12418>] sysenter_past_esp+0x3d/0x61
Feb 29 13:24:02 matteo kernel: Code: 5e 5d c3 8d b6 00 00 00 00 55 89 e5 57 56 53 83 ec 10 66 66 66 66 90 83 f8 0f 89 55 f0 77 72 8b 5d 10 8b 9b 4c 03 00 00 8b 7b 3c <8b> 77 68 83 fe 18 74 2e 83 fe 20 74 29 8b 47 6c 89 74 24 04 c7
Feb 29 13:24:02 matteo kernel: EIP: [<f8a97c12>] vmw_fb_setcolreg+0x22/0xb0 [vmwgfx] SS:ESP 0068:f6b418a8

답변1

F23 서버 버전을 실행하는 두 서버 모두에서 동일한 문제가 있습니다. 커널 4.3.4-300으로 업데이트하고 재부팅했는데 이로 인해 서버가 완전히 정지되었습니다. 이전 커널 4.2.6-301로 재부팅해야 했습니다.

ESC 버튼을 눌러도 시작 메시지가 표시되지 않습니다. 플리머스도 정체된 것 같습니다.

그런 다음 두 서버 모두에 커널 4.3.5-300(업데이트 테스트에서)을 설치했지만 단 하나만 새 커널을 성공적으로 부팅했습니다.

이해합니다:

# abrt-cli list
id 29e33b5c96e28619dca309942a505fc8e2ef19e2
reason:         BUG: unable to handle kernel NULL pointer dereference at 0000000000000060
time:           Fri 05 Feb 2016 03:35:14 PM CET
cmdline:        BOOT_IMAGE=/vmlinuz-4.3.4-300.fc23.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
count:          882
Directory:      /var/spool/abrt/oops-2016-02-05-15:35:10-1606-4
Reported:       cannot be reported

F23 워크스테이션 버전을 실행하는 데스크탑에 커널 4.3.4-301을 설치할 때 이러한 문제가 발생하지 않았습니다.

답변2

4.2.8 이상의 커널 버전에 지시어가 추가되었습니다 i915.preliminary_hw_support=1. grub-customize일반 설정에서 이 작업을 수행하거나 e부팅 시 커널 선택 메뉴를 누르고 새 줄을 추가한 다음 Ctrl + X부팅 계속을 눌러 수행할 수 있지만 이는 현재 부팅에만 작동합니다.

답변3

ESXi에서는 가상 머신 비디오 메모리를 5MB에서 8MB로 늘리면 문제가 해결되었습니다.

답변1

답변2

답변3

관련 정보