NetBSD Problem Report #32741

From www@netbsd.org  Sun Feb  5 05:42:37 2006
Return-Path: <www@netbsd.org>
Received: by narn.netbsd.org (Postfix, from userid 31301)
	id 1FF4C63B879; Sun,  5 Feb 2006 05:42:37 +0000 (UTC)
Message-Id: <20060205054237.1FF4C63B879@narn.netbsd.org>
Date: Sun,  5 Feb 2006 05:42:37 +0000 (UTC)
From: compoobah@valleyimplants.com
Reply-To: compoobah@valleyimplants.com
To: gnats-bugs@netbsd.org
Subject: VAXstation 3100/76 install crashes and/or panics
X-Send-Pr-Version: www-1.0

>Number:         32741
>Category:       port-vax
>Synopsis:       VAXstation 3100/76 install crashes and/or panics
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    port-vax-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 05 05:45:00 +0000 2006
>Closed-Date:    Thu Apr 12 19:06:00 +0000 2018
>Last-Modified:  Thu Apr 12 19:06:00 +0000 2018
>Originator:     Scott Quinn
>Release:        3.0
>Organization:
>Environment:
NetBSD on KA43 VAXstation 3176.
>Description:
Tried to install NetBSD 3.0 on a VAXstation 3100 model 76. Machine runs VMS V7.2-1 fine. Setup: 32 MB RAM, KA43-A DKA100=IBM 0664 2 GB narrow SCSI drive, DKA200=Toshiba XM4101.

Bootstrap works O.K.  At install: 1st attempt- failed at newfs, running newfs from shell nets error "/: write failed, filesystem full  
[1] illegal instruction: newfs /dev/rsd0d"

2nd attempt 
when install runs disklabel -w -r -f /tmp/disktab sd0 'cremevax'

"Panic: segv in kernel mode: PC 80065faa addr 0
  dumping" . . .
return to ">>>"

happened to two disks, was unable to verify my copy of NetBSD on VAX 4000/200 because NetBSD doesn't support KZQSA yet.
>How-To-Repeat:
Do not have another NetBSD supported VAX to test on, should be repeatable with process in "full description" pane.
>Fix:
unable to get around this one. Manual tweaking in the shell simply moves the error elsewhere (panic error happened once during extraction of tarballs when I managed to get disk labeled and formatted)

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->closed
State-Changed-By: ragge@NetBSD.org
State-Changed-When: Thu, 12 Apr 2018 19:06:00 +0000
State-Changed-Why:
A bug in the DMA driver on VS3100 caused data to/from userspace to 
be corrupted.  Fixed now.


>Unformatted:

Home	PR Database Search