Subject: port-shark/18433: current shark kernel does not boot
To: None <gnats-bugs@gnats.netbsd.org>
From: Martin Husemann <martin@duskware.de>
List: netbsd-bugs
Date: 09/27/2002 07:37:26
>Number: 18433
>Category: port-shark
>Synopsis: current shark kernel does not boot
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: port-shark-maintainer
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Sep 26 22:40:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Martin Husemann
>Release: NetBSD 1.6I
>Organization:
>Environment:
System: NetBSD night-porter.duskware.de 1.6G NetBSD 1.6G (PORTER) #0: Sun Sep 1 22:14:34 MEST 2002 martin@night-porter.duskware.de:/usr/src/sys/arch/i386/compile/PORTER i386
Architecture: i386
Machine: i386
>Description:
A -current shark kernel, cross-compiled from i386, dies early:
cpu0: 16KB/32B 32-way write-back Data cache
[u]vm_fault(0xf01466a0, aad5a000, 1, 0) -> e
Unhandled trap (frame = 0xf07cfe3c)
Data abort: 'Translation fault (section)' status=005 address=aad5a5a5 PC=f00824ec
Stopped in pid 0 (swapper) at 0xf00824ec: ldrb r3, [r1, #0x0000]
If someone tells me the magic to get ddb symbols into shark kernels, I could
provide more usefull details.
This seems to happen (not too surprising) somewhere in configure...
f008236c T configure
f0082568 T config_search
>How-To-Repeat:
s/a
>Fix:
n/a
>Release-Note:
>Audit-Trail:
>Unformatted:
current (1.6I), cvs updated Sep 26, 2002