Kernel from elrepo hangs on boot

General support questions
Post Reply
jhylkema
Posts: 3
Joined: 2018/02/23 06:26:45

Kernel from elrepo hangs on boot

Post by jhylkema » 2018/02/23 07:36:35

Hello all.

I am running CentOS 7 on a MacBook Pro unibody. When I installed the elrepo kernel-ml and tried to boot it, the boot process stops at virbr0. After that, all I get are some fsck errors. Even so, I can get to a shell by hitting CTRL-ALT-F2 and login. Here's what the dmesg says:

Code: Select all

[   17.800870] Netfilter messages via NETLINK v0.30.
[   17.808553] ip_set: protocol 6
[   24.192042] nvidia 0000:03:00.0: irq 30 for MSI/MSI-X
[   24.201971] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.203181] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.203656] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.203678] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.203697] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.203715] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.203733] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.203750] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.536637] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.555328] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.573469] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.594684] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   24.774858] nvidia 0000:02:00.0: irq 31 for MSI/MSI-X
[   24.930466] ACPI Warning: \_SB_.PCI0.RP01.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[   26.137381] tun: Universal TUN/TAP device driver, 1.6
[   26.137388] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   26.140216] virbr0: port 1(virbr0-nic) entered blocking state
[   26.140222] virbr0: port 1(virbr0-nic) entered disabled state
[   26.140278] device virbr0-nic entered promiscuous mode
[   26.450591] virbr0: port 1(virbr0-nic) entered blocking state
[   26.450598] virbr0: port 1(virbr0-nic) entered listening state
[   26.450662] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready
[   26.621594] virbr0: port 1(virbr0-nic) entered disabled state
[   26.639591] virbr1: port 1(virbr1-nic) entered blocking state
[   26.639598] virbr1: port 1(virbr1-nic) entered disabled state
[   26.639715] device virbr1-nic entered promiscuous mode
[   27.029519] virbr1: port 1(virbr1-nic) entered blocking state
[   27.029526] virbr1: port 1(virbr1-nic) entered listening state
[   27.029588] IPv6: ADDRCONF(NETDEV_UP): virbr1: link is not ready
[   27.203502] virbr1: port 1(virbr1-nic) entered disabled state
[   38.685546] fuse init (API version 7.22)
[   91.659026] ERROR @wl_notify_scan_status : wls3 Scan_results error (-22)
[  106.894847] EXT4-fs error (device sda4): ext4_mb_generate_buddy:757: group 995, block bitmap and bg descriptor inconsistent: 30197 vs 30198 free clusters
[  106.895343] JBD2: Spotted dirty metadata buffer (dev = sda4, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
[  175.023650] perf: interrupt took too long (2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
[  237.477086] ERROR @wl_notify_scan_status : wls3 Scan_results error (-22)
[  305.560335] perf: interrupt took too long (3157 > 3140), lowering kernel.perf_event_max_sample_rate to 63000
[  314.336162] EXT4-fs (sda4): error count since last fsck: 131159
[  314.336178] EXT4-fs (sda4): initial error at time 1519181131: ext4_free_inode:340
[  314.336183] EXT4-fs (sda4): last error at time 1519370865: ext4_mb_generate_buddy:757
[  337.113650] ERROR @wl_notify_scan_status : wls3 Scan_results error (-22)
I am using the NVIDIA 340.11 driver and Nouveau is blacklisted (natch).

What gives?

Any help would be appreciated.

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Kernel from elrepo hangs on boot

Post by TrevorH » 2018/02/23 09:34:22

The ELRepo kmod-nvidia series only works with the distro 3.10.0 kernel series. If you use kernel-ml then you must install the nvidia proprietary drivers using their .run file.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

jhylkema
Posts: 3
Joined: 2018/02/23 06:26:45

Re: Kernel from elrepo hangs on boot

Post by jhylkema » 2018/02/24 05:59:44

That worked. You the man.

Thanks for your help

Post Reply