Subject: Re:Re:Reboot NetBSD on Falcon
To: None <port-atari@netbsd.org>
From: JL Meyrial <JLMEYRIAL@CIMEGroup.com>
List: port-atari
Date: 02/28/2000 15:48:56
This is a multi-part message in MIME format.
------=_NextPart_000_001C_01BF8203.51F09FA0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I wrote:
> I use NetBSD 1.4 (BOOTX) on Atari Falcon 030: 14 Mb RAM, 520 Mb SCSI =
disk IBM-DSAS3540 (targ 0),
> SCSI2 CDROM TOSHIBA (targ 5) with a RGB atari monitor (resolution =
768x480 256 colors)
> and I often have to reboot 2 or 3 times before having NetBSD running =
correctly.
>
> When it crashes at reboot, I have:
> vm_fault, trap type 8
> kernel: MMU fault trap
> dump registers and panic:MMU fault
>
> traces on debugger are:
> _Debugger (8,2104,8,1ec64,2315bf4) +6
> _panic (9b4ff,2315c50,0,cf7a0,1ec64) +52
> _panictrap (8,402a64d,2,2315c50) +a8
> _trap (8,402a64d,2) +43c
> _run_main (317e80,2315d30,9d13c,0,2000) +d4
> _cdmaint (0,2000,0,11,11) +3e
> _intr_dispatch (20,0,cbf30,e16cb,20000000) +ac
> _intr_glue (?)
> _mi_switch (2004,e000,0,0,100000) +4
>
> Sometimes, I have the message "spurious interrupt" but NetBSD is =
running with no crash.
The crash happens generally at booting when it checks the ffs format on =
the SCSI2 disk (2 ffs partitions), sometimes it happens at logins (after =
the user input loggin)=20
------=_NextPart_000_001C_01BF8203.51F09FA0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#c0c0c0>
<DIV><FONT size=3D2>
<DIV><FONT size=3D2>I wrote:</FONT></DIV>
<DIV><FONT size=3D2>> I use NetBSD 1.4 (BOOTX) on Atari Falcon 030: =
14 Mb RAM,=20
520 Mb SCSI disk IBM-DSAS3540 (targ 0),<BR>> SCSI2 CDROM TOSHIBA =
(targ 5)=20
with a RGB atari monitor (resolution 768x480 256 colors)<BR>> and I =
often=20
have to reboot 2 or 3 times before having NetBSD running =
correctly.</FONT></DIV>
<DIV><FONT size=3D2>></FONT></DIV>
<DIV><FONT size=3D2>> When it crashes at reboot, I have:<BR>> =
vm_fault, trap=20
type 8<BR>> kernel: MMU fault trap<BR>> dump registers and =
panic:MMU=20
fault</FONT></DIV>
<DIV><FONT size=3D2>></FONT></DIV>
<DIV><FONT size=3D2>> traces on debugger are:<BR>> _Debugger=20
(8,2104,8,1ec64,2315bf4) +6<BR>> _panic (9b4ff,2315c50,0,cf7a0,1ec64) =
+52<BR>> _panictrap (8,402a64d,2,2315c50) +a8<BR>> _trap =
(8,402a64d,2)=20
+43c<BR>> _run_main (317e80,2315d30,9d13c,0,2000) +d4<BR>> =
_cdmaint=20
(0,2000,0,11,11) +3e<BR>> _intr_dispatch (20,0,cbf30,e16cb,20000000)=20
+ac<BR>> _intr_glue (?)<BR>> _mi_switch (2004,e000,0,0,100000)=20
+4</FONT></DIV>
<DIV><FONT size=3D2>></FONT></DIV>
<DIV><FONT size=3D2>> Sometimes, I have the message "spurious =
interrupt" but=20
NetBSD is running with no crash.</FONT></DIV>
<DIV><FONT size=3D2><BR> </DIV></FONT>
<DIV><FONT size=3D2>The crash happens generally at booting when =
it checks the=20
ffs format on the SCSI2 disk (2 ffs partitions), sometimes it happens at =
logins=20
(after the user input loggin) </FONT></DIV></FONT></DIV></BODY></HTML>
------=_NextPart_000_001C_01BF8203.51F09FA0--