On Thursday, 20 September 2007 16:12, Rafael J. Wysocki wrote:
quoted text
> On Thursday, 20 September 2007 15:43, Thomas Gleixner wrote:
> > On Thu, 2007-09-20 at 15:29 +0200, Rafael J. Wysocki wrote:
> > > > > I haven't had the time to check if any special command line arguments help.
> > > > > Will check tomorrow.
> > > > 
> > > > Can you please disable the patches, which I sent Linus wards:
> > > > 
> > > > timekeeping-access-rtc-outside-xtime-lock.patch
> > > > xtime-supsend-resume-fixup.patch
> > > > acpi-reevaluate-c-p-t-states.patch
> > > > clockevents-enforce-broadcast-on-resume.patch
> > > > clockevents-do-not-shutdown-broadcast-device-in-oneshot-mode.patch
> > > > clockevents-prevent-stale-tick-update-on-offline-cpu.patch
> > > 
> > > I have skipped all of them, but the resulting kernel behaves in the same
> > > way (ie. doesn't boot).
> > > 
> > > > Without those patches you get the state of rc4-mm1. It would be
> > > > interesting to know which one interferes with the acpi stuff.
> > > 
> > > It looks like something else went in between -rc4 and -rc6 that broke your
> > > patch.  I wonder what it might be ...
> > 
> > Hmm. Can you please go back in the -hrt project history:
> > http://tglx.de/projects/hrtimers/2.6.23-rc5/patch-2.6.23-rc5-hrt1.patches.tar.bz2
> > http://tglx.de/projects/hrtimers/2.6.23-rc4/patch-2.6.23-rc4-hrt1.patches.tar.bz2

Each of them on top of 2.6.23-rc6 gives the same symptoms as rc6-hrt2 (ie. the
box doesn't boot).

I'm going to check if -rc5 with patch-2.6.23-rc4-hrt1 on top of it works and
if not (I suspect so), I'll bisect the Linus' tree between -rc4 and -rc5 in
order to identify the responsible patch.

Greetings,
Rafael
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/