Messages in this thread | | | Date | Fri, 21 Mar 2008 19:11:27 +0100 | From | Gabriel C <> | Subject | Re: 2.6.25-rc5-git6: Reported regressions from 2.6.24 |
| |
Gabriel C wrote: > Thomas Gleixner wrote: >> On Fri, 21 Mar 2008, Gabriel C wrote: >> >>>> still hangs when I boot with clocksource=acpi_pm so that seems to >>>> be introduced in a different commit. >>>> >>>> I will try to bisect this hang also , most probably on weekend. >>>> >>> Correction on this one. >>> >>> Current git head boots just fine with clocksource=acpi_pm here , I >>> just don't know which commit fixed it. >> Hmm. Very dubious. I'm a bit afraid of self healing problems. It would >> be interesting to find the commit which fixed the acpi_pm timer >> problem unvoluntary. > > I can try to find it. > >> Also, can you please reapply the reverted clocksource patch ? I have >> the feeling that the acpi_pm one was the real problem which was >> triggered the modfied watchdog. > > Sure I can , will do so in some minutes and let you know.
It took a bit longer sorry but I have more infos now.
The acpi_pm was not related to that I still get the problem.
Of course I still can try to find the commit which magically fixed acpi_pm if you really want.
It seems like it breaks only when you enable HT and only on 2 socket motherboards. ( at least the ones I own , I know is old hardware but worked fine for me )
Also disabling the second CPU and enabling HT works , enabling both CPUs and disabling HT works , booting with enabled HT and both CPUs but maxcpus=2 also works , booting with 2 CPUs and HT on breaks , booting with both CPUs HT on but maxcpus=3 breaks also.
Also I have another dual motherboard here 604 socket with 2 2,4 GHz Xeon's. The motherboard has the storage controller somewhat broken but for a quick test it is still good :) and I see the same thing.
Does that make any sense ?
Also all that tested on 2.6.25-rc6-00224-gae51801-dirty ( dirty while I reverted the revert =) )
Gabriel
| |