Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Jun 2010 22:29:02 +0200
From:      Andreas Tobler <andreast-list@fgznet.ch>
To:        Marius Strobl <marius@alchemy.franken.de>
Cc:        freebsd-sparc64@freebsd.org
Subject:   Re: U60 doesn't boot anymore with -CURRENT
Message-ID:  <4C153F8E.1010106@fgznet.ch>
In-Reply-To: <20100613201836.GC68288@alchemy.franken.de>
References:  <4C14ED7C.2030809@fgznet.ch> <20100613191518.GA95797@alchemy.franken.de> <4C1530F1.6070207@fgznet.ch> <20100613201836.GC68288@alchemy.franken.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On 13.06.10 22:18, Marius Strobl wrote:
> On Sun, Jun 13, 2010 at 09:26:41PM +0200, Andreas Tobler wrote:
>> On 13.06.10 21:15, Marius Strobl wrote:
>>> On Sun, Jun 13, 2010 at 04:38:52PM +0200, Andreas Tobler wrote:
>>>> Hi,
>>>>
>>>> my gecko testmachine refuses to boot with -CURRENT.
>>>>
>>>> Here the verbose part of the messages:
>>>>
>>>> ---
>>>> FreeBSD 9.0-CURRENT #0 r209123M: Sun Jun 13 14:07:28 CEST 2010
>>>>
>>>>      andreast@u60.andreas.nets:/usr/obj/export/devel/src/sys/GENERIC
>>>>      sparc64
>>>> Preloaded elf kernel "/boot/kernel/kernel" at 0xc0bbc000.
>>>> real memory  = 1610612736 (1536 MB)
>>>> avail memory = 1554571264 (1482 MB)
>>>> machine: SUNW,Ultra-60
>>>> cpu0: Sun Microsystems UltraSparc-II Processor (449.99 MHz CPU)
>>>>    mask=0xa0 maxtl=5 maxwin=7
>>>> initalizing intr_countp
>>>> ---
>>>>
>>>> And here it hangs.
>>>>
>>>> Any idea on hwat is going wrong?
>>>>
>>>
>>> Nothing obvious as no sparc64 specific changes went in lately.
>>> If you use a kernel built with options ALT_BREAK_TO_DEBUGGER,
>>> can you break into the debugger via the alternate break sequence
>>> on the serial console and get backtrace when it hangs? What is
>>> the last known working revision? Can you bisect which revsion
>>> triggers the problem?
>>
>> I tracked it down to r207537, especially mp_locore.S.
>> If I use r207536 from mp_locore.S then my machine boots again.
>>
>
> Ah, that revision fails to update one branch. Could you please
> give the attached patch a try with current sources?

Well, there is/was no patch attached. I hope it goes in the direction I 
discovered ?

I rebuild the kernel now with my observation. It will take a while. Half 
an hour or so.

Thanks,
Andreas



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C153F8E.1010106>