Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

F21 fails to boot reliably with kernels >= 3.18

Hi! I have a problem with my system and hope that you guys could help me.

The Problem

With recent kernel versions, sometimes the boot gets "stuck". This is occurs randomly (estimated 50% of the time). Booting without "rhgb quiet" produces the following screen: Boot screen when stuck

I assume that there isn't anything special about "Started Set Up Additional Binary Formats", because with different kernel versions/drivers the last line was something different.

The Workarounds

The strange thing is, I still have an old 3.17.4 Kernel image installed. This one boots perfectly well, 100% of time. Also, if I add "3" to the command line, boot (with >= 3.18) into text mode, log in as root and do telinit 5, the machine comes up completely fine.

Here is the journalctl -b of a randomly successful boot: http://pastebin.com/HRt2cFkg

The System

  • Fedora 21, with the following packages installed: http://pastebin.com/dBHkk6VR
  • Booting uses UEFI
  • Hardware:
    • CPU: Intel i5 4690k
    • Graphics: NVIDIA GTX 960
    • SSD: 256GB 2,5" CRUCIAL MX100 SATA III rt (Root partition drive)
    • HDD: WD 2TB WD20EZRX GP SA3 ("data" drive)
    • HDD: 250 gbSAMSUNG SP2504C
    • Mainboard: MSI Z97 PC-Mate

What I tried so far

  • Adding nomodeset as Kernel parameter: no difference
  • Adding nox2acpi as Kernel parameter: no difference
  • Changing NVIDIA drivers: This whole problem started out when I had a default install and only had "nouveau" drivers. I thought installing proprietary NVIDIA drivers (from RPMFusion) would fix the problem. I switched back and forth, and they seem to have no effect on the boot behaviour.
  • Installing different kernel versions I tried several 3.18 versions, one 3.19 from rawhide-kernel-nodebug, and one 4.0.0rc1 from rawhide-kernel-nodebug. They all behave the same (apart from 4.0.0rc1 breaking my dkms modules).

F21 fails to boot reliably with kernels >= 3.18

Hi! I have a problem with my system and hope that you guys could help me.

The Problem

With recent kernel versions, sometimes the boot gets "stuck". This is occurs randomly (estimated 50% of the time). Booting without "rhgb quiet" produces the following screen: Boot screen when stuck

I assume that there isn't anything special about "Started Set Up Additional Binary Formats", because with different kernel versions/drivers the last line was something different.

The Workarounds

The strange thing is, I still have an old 3.17.4 Kernel image installed. This one boots perfectly well, 100% of time. Also, if I add "3" to the command line, boot (with >= 3.18) into text mode, log in as root and do telinit 5, the machine comes up completely fine.

Here is the journalctl -b of a randomly successful boot: http://pastebin.com/HRt2cFkghttp://pastebin.com/HRt2cFkg There is no journal for a failed boot, I checked with journalctl --list-boots.

The System

  • Fedora 21, with the following packages installed: http://pastebin.com/dBHkk6VR
  • Booting uses UEFI
  • Hardware:
    • CPU: Intel i5 4690k
    • Graphics: NVIDIA GTX 960
    • SSD: 256GB 2,5" CRUCIAL MX100 SATA III rt (Root partition drive)
    • HDD: WD 2TB WD20EZRX GP SA3 ("data" drive)
    • HDD: 250 gbSAMSUNG SP2504C
    • Mainboard: MSI Z97 PC-Mate

What I tried so far

  • Adding nomodeset as Kernel parameter: no difference
  • Adding nox2acpi as Kernel parameter: no difference
  • Changing NVIDIA drivers: This whole problem started out when I had a default install and only had "nouveau" drivers. I thought installing proprietary NVIDIA drivers (from RPMFusion) would fix the problem. I switched back and forth, and they seem to have no effect on the boot behaviour.
  • Installing different kernel versions I tried several 3.18 versions, one 3.19 from rawhide-kernel-nodebug, and one 4.0.0rc1 from rawhide-kernel-nodebug. They all behave the same (apart from 4.0.0rc1 breaking my dkms modules).

F21 fails to boot reliably with kernels >= 3.18

Hi! I have a problem with my system and hope that you guys could help me.

The Problem

With recent kernel versions, sometimes the boot gets "stuck". This is occurs randomly (estimated 50% of the time). Booting without "rhgb quiet" produces the following screen: Boot screen when stuck

I assume that there isn't anything special about "Started Set Up Additional Binary Formats", because with different kernel versions/drivers the last line was something different.

The Workarounds

The strange thing is, I still have an old 3.17.4 Kernel image installed. This one boots perfectly well, 100% of time. Also, if I add "3" to the command line, boot (with >= 3.18) into text mode, log in as root and do telinit 5, the machine comes up completely fine.

Here is the journalctl -b of a randomly successful boot: http://pastebin.com/HRt2cFkg There is no journal for a failed boot, I checked with journalctl --list-boots.

The System

  • Fedora 21, with the following packages installed: http://pastebin.com/dBHkk6VR
  • Booting uses UEFI
  • Hardware:
    • CPU: Intel i5 4690k
    • Graphics: NVIDIA GTX 960
    • SSD: 256GB 2,5" CRUCIAL MX100 SATA III rt (Root partition drive)
    • HDD: WD 2TB WD20EZRX GP SA3 ("data" drive)
    • HDD: 250 gbSAMSUNG SP2504C
    • Mainboard: MSI Z97 PC-Mate

What I tried so far

  • Adding nomodeset as Kernel parameter: no difference
  • Adding nox2acpi as Kernel parameter: no difference
  • Changing NVIDIA drivers: This whole problem started out when I had a default install and only had "nouveau" drivers. I thought installing proprietary NVIDIA drivers (from RPMFusion) would fix the problem. I switched back and forth, and they seem to have no effect on the boot behaviour.
  • Installing different kernel versions I tried several 3.18 versions, one 3.19 from rawhide-kernel-nodebug, and one 4.0.0rc1 from rawhide-kernel-nodebug. They all behave the same (apart from 4.0.0rc1 breaking my dkms modules).
  • Updating Motherboard BIOS from 4.0 -> 4.7
  • Turning off Turbo Boost Mode of the CPU

F21 fails to boot reliably with kernels >= 3.18

Hi! I have a problem with my system and hope that you guys could help me.

The Problem

With recent kernel versions, sometimes the boot gets "stuck". This is occurs randomly (estimated 50% of the time). Booting without "rhgb quiet" produces the following screen: Boot screen when stuck

I assume that there isn't anything special about "Started Set Up Additional Binary Formats", because with different kernel versions/drivers the last line was something different.

The Workarounds

The strange thing is, I still have an old 3.17.4 Kernel image installed. This one boots perfectly well, 100% of time. Also, if I add "3" to the command line, boot (with >= 3.18) into text mode, log in as root and do telinit 5, the machine comes up completely fine.

Here is the journalctl -b of a randomly successful boot: http://pastebin.com/HRt2cFkg There is no journal for a failed boot, I checked with journalctl --list-boots.

The System

  • Fedora 21, with the following packages installed: http://pastebin.com/dBHkk6VR
  • Booting uses UEFI
  • Hardware:
    • CPU: Intel i5 4690k
    • Graphics: NVIDIA GTX 960
    • SSD: 256GB 2,5" CRUCIAL MX100 SATA III rt (Root partition drive)
    • HDD: WD 2TB WD20EZRX GP SA3 ("data" drive)
    • HDD: 250 gbSAMSUNG SP2504C
    • Mainboard: MSI Z97 PC-Mate

What I tried so far

  • Adding nomodeset as Kernel parameter: no difference
  • Adding nox2acpi as Kernel parameter: no difference
  • Changing NVIDIA drivers: This whole problem started out when I had a default install and only had "nouveau" drivers. I thought installing proprietary NVIDIA drivers (from RPMFusion) would fix the problem. I switched back and forth, and they seem to have no effect on the boot behaviour.
  • Installing different kernel versions I tried several 3.18 versions, one 3.19 from rawhide-kernel-nodebug, and one 4.0.0rc1 from rawhide-kernel-nodebug. They all behave the same (apart from 4.0.0rc1 breaking my dkms modules).
  • Installing self-compiled kernels with default-configs: 4.0.0rc5 fails, 3.17.8 works.
  • Updating Motherboard BIOS from 4.0 -> 4.7
  • Turning off Turbo Boost Mode of the CPU

Update: Seeing that even self-compiled kernels behave the same way (4.0.0rc5 fails, 3.17.8 works), I would infer that: - Fedora Kernel Patches are not the problem - Fedora Kernel Config are not the problem

Also, I installed a different 3.17-version (3.17.8) from Koji, it works just as well as 3.17.4. Which leads me to believe that - it's not a ramdisk-issue

F21 fails to boot reliably with kernels >= 3.18

Hi! I have a problem with my system and hope that you guys could help me.

The Problem

With recent kernel versions, sometimes the boot gets "stuck". This is occurs randomly (estimated 50% of the time). Booting without "rhgb quiet" produces the following screen: Boot screen when stuck

I assume that there isn't anything special about "Started Set Up Additional Binary Formats", because with different kernel versions/drivers the last line was something different.

The Workarounds

The strange thing is, I still have an old 3.17.4 Kernel image installed. This one boots perfectly well, 100% of time. Also, if I add "3" to the command line, boot (with >= 3.18) into text mode, log in as root and do telinit 5, the machine comes up completely fine.

Here is the journalctl -b of a randomly successful boot: http://pastebin.com/HRt2cFkg There is no journal for a failed boot, I checked with journalctl --list-boots.

The System

  • Fedora 21, with the following packages installed: http://pastebin.com/dBHkk6VR
  • Booting uses UEFI
  • Hardware:
    • CPU: Intel i5 4690k
    • Graphics: NVIDIA GTX 960
    • SSD: 256GB 2,5" CRUCIAL MX100 SATA III rt (Root partition drive)
    • HDD: WD 2TB WD20EZRX GP SA3 ("data" drive)
    • HDD: 250 gbSAMSUNG SP2504C
    • Mainboard: MSI Z97 PC-Mate

What I tried so far

  • Adding nomodeset as Kernel parameter: no difference
  • Adding nox2acpi as Kernel parameter: no difference
  • Changing NVIDIA drivers: This whole problem started out when I had a default install and only had "nouveau" drivers. I thought installing proprietary NVIDIA drivers (from RPMFusion) would fix the problem. I switched back and forth, and they seem to have no effect on the boot behaviour.
  • Installing different kernel versions versions: I tried several 3.18 versions, one 3.19 from rawhide-kernel-nodebug, and one 4.0.0rc1 from rawhide-kernel-nodebug. They all behave the same (apart from 4.0.0rc1 breaking my dkms modules).
  • same.
    • Installing self-compiled kernels with default-configs: 4.0.0rc5 fails, 3.17.8 works.works
    • Updating Motherboard BIOS from 4.0 -> 4.7
    • Turning off Turbo Boost Mode of the CPU

Update: Seeing that even self-compiled kernels behave the same way (4.0.0rc5 fails, 3.17.8 works), I would infer that: - that:

  • Fedora Kernel Patches are not the problem - problem
  • Fedora Kernel Config are not the problem

Also, I installed a different 3.17-version (3.17.8) from Koji, it works just as well as 3.17.4. Which leads me to believe that - that

  • it's not a ramdisk-issue

F21 fails to boot reliably with kernels >= 3.18

Hi! I have a problem with my system and hope that you guys could help me.

The Problem

With recent kernel versions, sometimes the boot gets "stuck". This is occurs randomly (estimated 50% of the time). Booting without "rhgb quiet" produces the following screen: Boot screen when stuck

I assume that there isn't anything special about "Started Set Up Additional Binary Formats", because with different kernel versions/drivers the last line was something different.

The Workarounds

The strange thing is, I still have an old 3.17.4 Kernel image installed. This one boots perfectly well, 100% of time. Also, if I add "3" to the command line, boot (with >= 3.18) into text mode, log in as root and do telinit 5, the machine comes up completely fine.

Here is the journalctl -b of a randomly successful boot: http://pastebin.com/HRt2cFkg There is no journal for a failed boot, I checked with journalctl --list-boots.

The System

  • Fedora 21, with the following packages installed: http://pastebin.com/dBHkk6VR
  • Booting uses UEFI
  • Hardware:
    • CPU: Intel i5 4690k
    • Graphics: NVIDIA GTX 960
    • SSD: 256GB 2,5" CRUCIAL MX100 SATA III rt (Root partition drive)
    • HDD: WD 2TB WD20EZRX GP SA3 ("data" drive)
    • HDD: 250 gbSAMSUNG SP2504C
    • Mainboard: MSI Z97 PC-Mate

What I tried so far

  • Adding nomodeset as Kernel parameter: no difference
  • Adding nox2acpi as Kernel parameter: no difference
  • Changing NVIDIA drivers: This whole problem started out when I had a default install and only had "nouveau" drivers. I thought installing proprietary NVIDIA drivers (from RPMFusion) would fix the problem. I switched back and forth, and they seem to have no effect on the boot behaviour.
  • Installing different kernel versions: I tried several 3.18 versions, one 3.19 from rawhide-kernel-nodebug, and one 4.0.0rc1 from rawhide-kernel-nodebug. They all behave the same.
    • Installing self-compiled kernels with default-configs: 4.0.0rc5 fails, 3.17.8 works
    • Updating Motherboard BIOS from 4.0 -> 4.7
    • Turning off Turbo Boost Mode of the CPU
    • Running btrfs-zero-log on the root partition
    • running btrfs check --repair on the root partition
    • patching the kernel with commit 9c4f61

Update: Seeing that even self-compiled kernels behave the same way (4.0.0rc5 fails, 3.17.8 works), I would infer that:

  • Fedora Kernel Patches are not the problem
  • Fedora Kernel Config are not the problem

Also, I installed a different 3.17-version (3.17.8) from Koji, it works just as well as 3.17.4. Which leads me to believe that

  • it's not a ramdisk-issue

F21 fails to boot reliably with kernels >= 3.18

Hi! I have a problem with my system and hope that you guys could help me.

The Problem

With recent kernel versions, sometimes the boot gets "stuck". This is occurs randomly (estimated 50% of the time). Booting without "rhgb quiet" produces the following screen: Boot screen when stuck

I assume that there isn't anything special about "Started Set Up Additional Binary Formats", because with different kernel versions/drivers the last line was something different.

The Workarounds

The strange thing is, I still have an old 3.17.4 Kernel image installed. This one boots perfectly well, 100% of time. Also, if I add "3" to the command line, boot (with >= 3.18) into text mode, log in as root and do telinit 5, the machine comes up completely fine.

Here is the journalctl -b of a randomly successful boot: http://pastebin.com/HRt2cFkg There is no journal for a failed boot, I checked with journalctl --list-boots.

The System

  • Fedora 21, with the following packages installed: http://pastebin.com/dBHkk6VR
  • Booting uses UEFI
  • Hardware:
    • CPU: Intel i5 4690k
    • Graphics: NVIDIA GTX 960
    • SSD: 256GB 2,5" CRUCIAL MX100 SATA III rt (Root partition drive)
    • HDD: WD 2TB WD20EZRX GP SA3 ("data" drive)
    • HDD: 250 gbSAMSUNG SP2504C
    • Mainboard: MSI Z97 PC-Mate

What I tried so far

  • Adding nomodeset as Kernel parameter: no difference
  • Adding nox2acpi as Kernel parameter: no difference
  • Changing NVIDIA drivers: This whole problem started out when I had a default install and only had "nouveau" drivers. I thought installing proprietary NVIDIA drivers (from RPMFusion) would fix the problem. I switched back and forth, and they seem to have no effect on the boot behaviour.
  • Installing different kernel versions: I tried several 3.18 versions, one 3.19 from rawhide-kernel-nodebug, and one 4.0.0rc1 from rawhide-kernel-nodebug. They all behave the same.
    • Installing self-compiled kernels with default-configs: 4.0.0rc5 fails, 3.17.8 works
  • Updating Motherboard BIOS from 4.0 -> 4.7
  • Turning off Turbo Boost Mode of the CPU
  • Running btrfs-zero-log on the root partition
  • running btrfs check --repair on the root partition
  • patching the kernel with commit 9c4f61

Update: Seeing that even self-compiled kernels behave the same way (4.0.0rc5 fails, 3.17.8 works), I would infer that:

  • Fedora Kernel Patches are not the problem
  • Fedora Kernel Config are not the problem

Also, I installed a different 3.17-version (3.17.8) from Koji, it works just as well as 3.17.4. Which leads me to believe that

  • it's not a ramdisk-issue

F21 fails to boot reliably with kernels >= 3.18

Solved: upgrade to Fedora 22 with fedup.


Hi! I have a problem with my system and hope that you guys could help me.

The Problem

With recent kernel versions, sometimes the boot gets "stuck". This is occurs randomly (estimated 50% of the time). Booting without "rhgb quiet" produces the following screen: Boot screen when stuck

I assume that there isn't anything special about "Started Set Up Additional Binary Formats", because with different kernel versions/drivers the last line was something different.

The Workarounds

The strange thing is, I still have an old 3.17.4 Kernel image installed. This one boots perfectly well, 100% of time. Also, if I add "3" to the command line, boot (with >= 3.18) into text mode, log in as root and do telinit 5, the machine comes up completely fine.

Here is the journalctl -b of a randomly successful boot: http://pastebin.com/HRt2cFkg There is no journal for a failed boot, I checked with journalctl --list-boots.

The System

  • Fedora 21, with the following packages installed: http://pastebin.com/dBHkk6VR
  • Booting uses UEFI
  • Hardware:
    • CPU: Intel i5 4690k
    • Graphics: NVIDIA GTX 960
    • SSD: 256GB 2,5" CRUCIAL MX100 SATA III rt (Root partition drive)
    • HDD: WD 2TB WD20EZRX GP SA3 ("data" drive)
    • HDD: 250 gbSAMSUNG SP2504C
    • Mainboard: MSI Z97 PC-Mate

What I tried so far

  • Adding nomodeset as Kernel parameter: no difference
  • Adding nox2acpi as Kernel parameter: no difference
  • Changing NVIDIA drivers: This whole problem started out when I had a default install and only had "nouveau" drivers. I thought installing proprietary NVIDIA drivers (from RPMFusion) would fix the problem. I switched back and forth, and they seem to have no effect on the boot behaviour.
  • Installing different kernel versions: I tried several 3.18 versions, one 3.19 from rawhide-kernel-nodebug, and one 4.0.0rc1 from rawhide-kernel-nodebug. They all behave the same.
    • Installing self-compiled kernels with default-configs: 4.0.0rc5 fails, 3.17.8 works
  • Updating Motherboard BIOS from 4.0 -> 4.7
  • Turning off Turbo Boost Mode of the CPU
  • Running btrfs-zero-log on the root partition
  • running btrfs check --repair on the root partition
  • patching the kernel with commit 9c4f61

Update: Seeing that even self-compiled kernels behave the same way (4.0.0rc5 fails, 3.17.8 works), I would infer that:

  • Fedora Kernel Patches are not the problem
  • Fedora Kernel Config are not the problem

Also, I installed a different 3.17-version (3.17.8) from Koji, it works just as well as 3.17.4. Which leads me to believe that

  • it's not a ramdisk-issue

F21 fails to boot reliably with kernels >= 3.18

Solved: upgrade to Fedora 22 with fedup.


Hi! I have a problem with my system and hope that you guys could help me.

The Problem

With recent kernel versions, sometimes the boot gets "stuck". This is occurs randomly (estimated 50% of the time). Booting without "rhgb quiet" produces the following screen: Boot screen when stuck

I assume that there isn't anything special about "Started Set Up Additional Binary Formats", because with different kernel versions/drivers the last line was something different.

The Workarounds

The strange thing is, I still have an old 3.17.4 Kernel image installed. This one boots perfectly well, 100% of time. Also, if I add "3" to the command line, boot (with >= 3.18) into text mode, log in as root and do telinit 5, the machine comes up completely fine.

Here is the journalctl -b of a randomly successful boot: http://pastebin.com/HRt2cFkg There is no journal for a failed boot, I checked with journalctl --list-boots.

The System

  • Fedora 21, with the following packages installed: http://pastebin.com/dBHkk6VR
  • Booting uses UEFI
  • Hardware:
    • CPU: Intel i5 4690k
    • Graphics: NVIDIA GTX 960
    • SSD: 256GB 2,5" CRUCIAL MX100 SATA III rt (Root partition drive)
    • HDD: WD 2TB WD20EZRX GP SA3 ("data" drive)
    • HDD: 250 gbSAMSUNG SP2504C
    • Mainboard: MSI Z97 PC-Mate

What I tried so far

  • Adding nomodeset as Kernel parameter: no difference
  • Adding nox2acpi as Kernel parameter: no difference
  • Changing NVIDIA drivers: This whole problem started out when I had a default install and only had "nouveau" drivers. I thought installing proprietary NVIDIA drivers (from RPMFusion) would fix the problem. I switched back and forth, and they seem to have no effect on the boot behaviour.
  • Installing different kernel versions: I tried several 3.18 versions, one 3.19 from rawhide-kernel-nodebug, and one 4.0.0rc1 from rawhide-kernel-nodebug. They all behave the same.
    • Installing self-compiled kernels with default-configs: 4.0.0rc5 fails, 3.17.8 works
  • Updating Motherboard BIOS from 4.0 -> 4.7
  • Turning off Turbo Boost Mode of the CPU
  • Running btrfs-zero-log on the root partition
  • running btrfs check --repair on the root partition
  • patching the kernel with commit 9c4f61

Update: Seeing that even self-compiled kernels behave the same way (4.0.0rc5 fails, 3.17.8 works), I would infer that:

  • Fedora Kernel Patches are not the problem
  • Fedora Kernel Config are not the problem

Also, I installed a different 3.17-version (3.17.8) from Koji, it works just as well as 3.17.4. Which leads me to believe that

  • it's not a ramdisk-issue