1 |
Hi Alexander, |
2 |
|
3 |
On Sun, 23 Aug 2015, Alexander Kapshuk wrote: |
4 |
|
5 |
> On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher <newsspam@××××××××××.org> wrote: |
6 |
> > |
7 |
> > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I |
8 |
> > upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of |
9 |
> > them. On the screen I see |
10 |
> > |
11 |
> > Decompressing Linux... Parsing ELF... done. |
12 |
> > Booting the kernel. |
13 |
> > |
14 |
> > as the last thing, then it just sits there. |
15 |
> |
16 |
> I am running vanilla-sources 4.1.6, and so far I have not had any |
17 |
> trouble booting it. |
18 |
> |
19 |
> Are you able to boot some of your previous kernels? If so, what does |
20 |
> your '/boot/grub/grub.cfg' look like? |
21 |
> What is the output of 'cat /etc/fstab' and 'ls -1 /boot'? |
22 |
|
23 |
I can still boot 4.0.5 fine, with the same setup. I use lilo, and I |
24 |
checked that I changed the two/four digits correctly in /etc/lilo.conf. |
25 |
|
26 |
By chance I left the boot sit there for more than the typical minute, |
27 |
and got multiple messages like |
28 |
|
29 |
INFO: rcu_sched self-detected stall on CPU { 3} (t=60000 jiffies g=-256 c=-257 q=193) |
30 |
rcu_sched kthread starved for 50027 jiffies! |
31 |
|
32 |
right after the above "Booting the kernel." line. |
33 |
|
34 |
Do I need to activate a different kind of clocking or a CPU feature in |
35 |
4.1.x? |
36 |
|
37 |
Peter. |