On Mon, Oct 09, 2006 at 01:21:56AM -0700, David Miller wrote: > From: Jurij Smakov <jurij@xxxxxxxxx> > Date: Sun, 8 Oct 2006 19:29:54 -0700 > > > We have two reports now of boot failures of 2.6.18 on SunBlade 100 and > > 150. According to the reporters (who are CC'd), they see the following > > during boot: > > > > Booting Linux... > > NVRAM: Low Battery Voltage! > > CLOCK: Clock was stopped. Kick start > > > > Then machine hangs. Any ideas on how to fix it will be appreciated. > > It's probably a device probing regression caused by the > new in-kernel device tree code I added to 2.6.18 Thanks to the debugging performed by Jim Watson, we have now confirmed that the addresses of the clock registers calculated in clock_probe() (arch/sparc64/sparc/time.c) differ in 2.6.16 and 2.6.18. On 2.6.16 it gets mstk48t59_regs=000001ff011800000 while on 2.6.18 it's mstk48t59_regs=000001fff1000000 More information, including prtconf output from 3 affected machines is available in the bug trail at http://bugs.debian.org/392078 Best regards, -- Jurij Smakov jurij@xxxxxxxxx Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC - To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
