Bug 926986 - Kernel 3.9.0-0.rc3.git1.4.fc19.x86_64 don't boot
Summary: Kernel 3.9.0-0.rc3.git1.4.fc19.x86_64 don't boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-24 16:23 UTC by dominique
Modified: 2013-09-04 14:17 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-04 14:17:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
/var/log/messages (90.81 KB, text/plain)
2013-03-24 16:23 UTC, dominique
no flags Details
journalctl.txt (69.43 KB, text/plain)
2013-03-28 06:28 UTC, dominique
no flags Details

Description dominique 2013-03-24 16:23:43 UTC
Created attachment 715585 [details]
/var/log/messages

Description of problem:

I installed the last kernel fot F19 from update (3.9.0-0.rc3.git1.4.fc19.x86_64) but that don't boot.

That entering in emergency boot, but i can't type journalctl for seeing this journal.

I attach the /var/log/messages

Comment 1 dominique 2013-03-27 12:55:45 UTC
Sorry, the log is for a boot with a good kernel.

With kernel 3.9.0-0.rc3.git1.4.fc19.x86_64 I have no log, but I can see that I can copy journalctl.txt on USB stick or on /boot.

But I don't know how.

Can you help me ?

Comment 2 dominique 2013-03-28 06:27:42 UTC
I was able to recover journalctl.txt, but in the manipulation my F19 was broken...

I attach this file, but I do other test when I should install the F19 alpha tc3 (the tc2 don't work for me, problem with anaconda, see Bug 926926 )

Comment 3 dominique 2013-03-28 06:28:40 UTC
Created attachment 717455 [details]
journalctl.txt

Comment 4 Thomas Schweikle 2013-04-26 11:16:11 UTC
Same here. Fedora kernels 3.9.0-0.rc6.git2.3.fc19.x86_64 will not boot at all. Grub loads kernel, initrd, than transfers control. The kernel than hangs without doing anything.

The last kernel that boots is 3.8.0-2.fc19.x86_64 all newer ones do the same: grub loads them, then initrd, then transfers control. These newer ones hang then without doing anything.

The HD light is of. No further access to disk. CPU load seems high (its getting really warm after some time, power consumption is high). Since the hardware I am testing on does not have a serial port I can't test if debugging output is produced.

Compiling the kernel from plain vanilla sources (taking kernel build options from one of the fedora 3.9.0-0-rc-Kernels), then installing it makes it boot. Looks like it is something with the modules defined and the patches applied by fedora.

Comment 5 Thomas Schweikle 2013-05-02 07:49:13 UTC
Same for kernel 3.9.0-301.fc19.x86_64:
Hangs after/while loading initrd. It works with a plain vanilla kernel compiled from scratch using a .config from debian. Using the .config supplied by fedora doesn't work. I'll attach both later today.

Comment 6 Thomas Schweikle 2013-05-02 08:01:02 UTC
Same for kernel 3.10.0-0.rc0.git7.1.fc20.x86_64:
Hangs after/while loading initrd. Did not test a plain vanilla version.

Comment 7 Thomas Schweikle 2013-05-02 11:16:07 UTC
Ubuntu 1310 with kernel 3.9.0-generic does have the very same problem:
Hangs after/while loading initrd. I've tested a new initrd, but without success. After grub transfers control the kernel hangs.
Tried to debug the situation, but no connection to the system was possible. Looks a lot like the 3.9-kernels do have some real problem an a variety of hardware, stopping the show.

Comment 8 Marius Hoch 2013-08-23 22:07:56 UTC
I had the very same problem on one of my machines and kernel 3.10.7-100.fc18.x86_64 seems to work again.

Comment 9 Michele Baldessari 2013-09-03 23:15:33 UTC
Thomas, Dominique,

can you test if 3.10.10 is working for you?
If it is not working for you try booting with:
systemd.log_level=debug systemd.log_target=console log_buf_len=1M rdinitdebug 

make sure to remove "quiet rhgb" from the boot command line.

If you could take a photo of the screen once it is stuck with 3.10.x when using the above boot parameters, we might get a better idea of what is going on.

Thanks,
Michele

Comment 10 dominique 2013-09-04 05:13:48 UTC
kernel 3.10.10-200.fc19 work fine on my laptop.
No problems ans no bugs.

Comment 11 Josh Boyer 2013-09-04 14:17:38 UTC
Thanks for letting us know.


Note You need to log in before you can comment on or make changes to this bug.