lkml.org 
[lkml]   [2011]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: PROBLEM: 3.0-rc kernels unbootable since -rc3
From
>Very good.  I have created a new jms.2011.07.07a branch in the -rcu
>git tree at:

I get my own branch! :-) (thanks for all your trouble with this.)

>Hello, Julie,

>Any news?

Sorry for the delay (again), I have to work very late Fridays and Saturdays.
Anyway, I have tested the six commits on my v3.0-rc4 branch (with
f8b7fc6b514f34a5 and a46e0899eec7a3069bc reverted) and can confirm
that they _all_ produce a bootable kernel at my end.

Btw, you may have noticed that my config has RCU_BOOST=n?
If I build a simple v3.0-rc4 kernel (ie one which includes the four
original commits (f8b7fc6b514, a46e0899eec, 09223371dea and
9a432736904)) but with RCU_BOOST=y it _will_ boot. I didn't know if
this was helpful or not.

If it is helpful, you probably know this, but in order to get
RCU_BOOST=y I have to change a couple of other configs - PREEMPT_RCU=y
(previously n) and to get PREEMPT_RCU=y, my preemption model has to be
'Preemptible Kernel (Low-Latency Desktop)' - PREEMPT=y (instead of
'Voluntary Kernel Preemption (Desktop)' - PREEMPT=n which it was
originally).

It's my day off tomorrow so I'll do some more testing (on -rc5 and
-rc6) (past 1.30am here in the UK now).

HTH,
Julie


\
 
 \ /
  Last update: 2011-07-10 02:49    [W:0.081 / U:0.316 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site