From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jurij Smakov Date: Sat, 14 Oct 2006 18:49:08 +0000 Subject: Re: Problems booting 2.6.18 on SunBlade 100/150 Message-Id: <20061014184908.GA3487@droopy.oc.cox.net> List-Id: References: <200401070729.56891.pkarlsen@mandriva.com> In-Reply-To: <200401070729.56891.pkarlsen@mandriva.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: sparclinux@vger.kernel.org On Mon, Oct 09, 2006 at 01:21:56AM -0700, David Miller wrote: > From: Jurij Smakov > 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_regs0001ff011800000 while on 2.6.18 it's mstk48t59_regs0001fff1000000 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@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC