On 1/8/16 3:45 PM, Kurt Lidl wrote:
On 1/8/16 1:58 PM, Marius Strobl wrote:
On Fri, Jan 08, 2016 at 10:42:33AM -0500, Kurt Lidl wrote:
I recently updated a sparc64 V120 from r291993
to r293243, and it now traps during the
autoconfiguration phase of the kernel boot:
<...>
-- data access
On Fri, Jan 08, 2016 at 10:42:33AM -0500, Kurt Lidl wrote:
> I recently updated a sparc64 V120 from r291993
> to r293243, and it now traps during the
> autoconfiguration phase of the kernel boot:
>
<...>
> -- data access exception sfar=0xfcf821ca0218 sfsr=0x41029
> %o7=0xc06165e8 --
What
On 08/01/16 15:42, Kurt Lidl wrote:
> I recently updated a sparc64 V120 from r291993
> to r293243, and it now traps during the
> autoconfiguration phase of the kernel boot:
>
> Hit [Enter] to boot immediately, or any other key for command prompt.
> Booting [/boot/kernel/kernel]...
> jumping to
On 1/8/16 1:58 PM, Marius Strobl wrote:
On Fri, Jan 08, 2016 at 10:42:33AM -0500, Kurt Lidl wrote:
I recently updated a sparc64 V120 from r291993
to r293243, and it now traps during the
autoconfiguration phase of the kernel boot:
<...>
-- data access exception sfar=0xfcf821ca0218
On 1/8/16 11:57 AM, Mark Cave-Ayland wrote:
On 08/01/16 15:42, Kurt Lidl wrote:
I recently updated a sparc64 V120 from r291993
to r293243, and it now traps during the
autoconfiguration phase of the kernel boot:
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting
On Fri, Jan 08, 2016 at 04:57:58PM +, Mark Cave-Ayland wrote:
> On 08/01/16 15:42, Kurt Lidl wrote:
>
> This looks amazingly similar to what I get trying to boot FreeBSD under
> QEMU, i.e. pointing at sched_clock():
>
<...>
> -- kernel stack fault %o7=0xc011a050 --
> panic: longjmp botch
>
I recently updated a sparc64 V120 from r291993
to r293243, and it now traps during the
autoconfiguration phase of the kernel boot:
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
jumping to kernel entry at 0xc00b.
GDB: no debug ports
