Re: 2.6.23-rc6-mm1: failure to boot on HP nx6325, no sound when booted, USB-related WARNING

On Thursday, 20 September 2007 08:18, Thomas Gleixner wrote:
> On Thu, 2007-09-20 at 02:06 +0200, Rafael J. Wysocki wrote:
> > On Wednesday, 19 September 2007 21:21, Thomas Gleixner wrote:
> > > On Wed, 2007-09-19 at 19:44 +0200, Rafael J. Wysocki wrote:
> > > > > > It boots with nohpet alone and suspend/hibernation seem to work (still,
> > > > > > it didn't want to boot right after hibernation, but booted after I'd switched
> > > > > > it off/on manually).
> > > > > 
> > > > > Can you please check, whether
> > > > > 
> > > > > http://tglx.de/projects/hrtimers/2.6.23-rc6/patch-2.6.23-rc6-hrt2.patch
> > > > > 
> > > > > works for you ?
> > > > 
> > > > Nope.  It's a total disaster. :-(
> > > 
> > > True. I have instrumented it to the point where the broadcast device is
> > > programmed, but no interrupt comes in for totally unknown reasons.
> > > 
> > > > Doesn't boot at all, even with "noacpitimer nohpet", and that's with
> > > > NO_HZ and HIGH_RES_TIMERS unset.
> > > 
> > > > If you have a bisectable patch series, I can try to identify the responsible
> > > > patch.
> > > 
> > > http://tglx.de/projects/hrtimers/2.6.23-rc6/patch-2.6.23-rc6-hrt2.patches.tar.bz2
> > > 
> > > The first patches in the queue are the mainline fixups.
> > 
> > It's x86_64-convert-to-clockevents.patch (ie. after applying it the box stops
> > to boot).
> > 
> > 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 ...

Greetings,
Rafael