On Thu, Dec 10, 2009 at 6:08 PM, Kyle McMartin <kyle@xxxxxxxxxxx> wrote: > On Thu, Dec 10, 2009 at 12:50:38AM +0100, Domenico Andreoli wrote: >> On Tue, Dec 08, 2009 at 12:44:04AM +0100, Domenico Andreoli wrote: >> > On Sat, Dec 05, 2009 at 09:35:11AM +0100, Domenico Andreoli wrote: >> > > On Fri, Dec 04, 2009 at 07:50:10PM +0100, Helge Deller wrote: >> > > >> > > > I just want to make sure, that you have more or less a correct kernel >> > > > configuration setup (.config).... >> > > >> > > there is at least a configuration glitch which makes my kernel hang >> > > and the debian one continue in degraded mode. i attached also the >> > > configuration, just in case i forgot something important. >> > >> > i found the configuration glitch, it is CONFIG_DEBUG_MUTEXES. if it is >> > set, 64bit hangs right after "Releasing cpu 1 now, hpa=...", otherwise >> > the 64bit boot continues with a "SMP: CPU:1 is stuck." >> >> i was wrong, it's again CONFIG_DEBUG_SPINLOCK. if it is set, the >> boot hangs. >> >> i passed the last few days building kernels... >> > > So CONFIG_DEBUG_SPINLOCK causes hangs, with it unset, everything is > fine? Interesting. Sounds like initialization issues. I'll take a look soon. no exactly, with CONFIG_DEBUG_SPINLOCK unset kernel boots but still with 1 CPU and the "SMP: CPU:1 is stuck." message, this at 64bit. at 32bit and CONFIG_DEBUG_SPINLOCK unset (both gcc 4.3 & 4.4) i get the build error i reported in another thread. with CONFIG_DEBUG_SPINLOCK set kernel builds and runs nicely. regards, Domenico -----[ Domenico Andreoli, aka cavok --[ http://www.dandreoli.com/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
