ROSA Linux Bugzilla – Bug 2728
3.10 Kernel loading problem
Last modified: 2013-10-07 12:06:23 MSD
Description of problem:
3.10.9 kernel doesn't work. After suspend I can't boot my system. At the same time 3.8 works fine. I'll investigate problem and provide more info later.
$ uname -a
Linux work 3.8.12-nrj-desktop-2rosa #1 SMP PREEMPT Thu May 16 21:53:13 MSK 2013 x86_64 x86_64 x86_64 GNU/Linux
Created attachment 1941 [details]
Created attachment 1942 [details]
mei_me problem kernel at startup
For 3.10 kernel there is mei_me problem at startup. It delays loading of systemd, but maybe it freezes loading during systemd stage. For 3.8 kernel there is no such mei_me problem.
This problem is known and fixed in all kernels, starting from 3.10.10.
We expect 3.10.14 to be pushed to official repo as soon as it is released.
To fix this issue immediately you can install any kernel >= 3.10.10 from this repo
Created attachment 1943 [details]
I've updates kernel. mei_me has disappeared, but the problem not. With 3.10.12 kernel my computer freezes during systemd loading. Last systemd messages may be different from one boot to another (because systemd may have time to load some services). I don't know how collect more information because logs are empty (like I don't ever started 3.10 kernel (: )
This problem appears only when you try to resume from sleep/hybernate ?
No, then I try to start 3.10 kernel.
(In reply to comment #5)
> I don't know how collect more information
> because logs are empty (like I don't ever started 3.10 kernel (: )
First of all, let us make the logs persistent. By default, journald stores them in memory, so they disappear each time the system restarts.
Your system can boot with lernel 3.8.12, right? If so, boot the system with it and then check if /var/log/journal/ directory exists. If it does not, create it than reboot the system using kernel 3.10.
When the system hangs again, wait a little, just in case (1-2 minutes would be OK).
To make sure the next boot does not overwrite the logs, you can boot from a USB stick or DVD in Live mode, mount the HDD partition contaning /var somewhere, say, to /mnt/root_part/
Then get the logs in the readable format with
journalctl -a -D /mnt/root_part/var/log/journal/
Let's see if this gives us anything.
First of all, journald isn't started so I've created required folder /var/log/journal but it was empty after fail of 3.10 (:.
Hmmmmm... interesting, after boot to 3.8 I checked folder and it was non-empty. Then I tried to reboot to 3.10 and ........ and ....... and ......... it started!!! I don't understand what it was!
I'll try to reboot several times later and then remove /var/log/journal and try to boot to 3.10.
It doesn't matter a folder '/var/log/journal' does exist or not, my computer doesn't want to boot with 3.10 kernel again.
(In reply to comment #10)
> It doesn't matter a folder '/var/log/journal' does exist or not, my computer
> doesn't want to boot with 3.10 kernel again.
Which kernel version have you tried now? 3.10.13-nrj-desktop?
Certainly, '/var/log/journal' should not affect if the system is bootable or not.
But now, you might have the logs there that could help identify the problem. Please collect them as I described in the comment #8 and post the relevant part here.
If you used 3.10.9 or an earlier kernel, please try newer versions first as Alexander suggested.
First of all, I have next kernels' versions:
$ ls /boot | grep vml
And 3.10.9, 3.10.12 don't want to work (:
I've tried several times to do steps described in comment #8 but every time I saw empty /var/log/journal.