NetBSD Problem Report #1726

From gnats  Fri Nov  3 21:49:05 1995
Received: from Collatz.McRCIM.McGill.EDU by pain.lcs.mit.edu (8.6.9/8.6.9) with ESMTP id VAA03162 for <gnats-bugs@gnats.netbsd.org>; Fri, 3 Nov 1995 21:30:26 -0500
Message-Id: <199511040229.VAA08411@Collatz.McRCIM.McGill.EDU>
Date: Fri, 3 Nov 1995 21:29:42 -0500
From: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
Reply-To: mouse@Collatz.McRCIM.McGill.EDU
To: gnats-bugs@gnats.netbsd.org
Subject: [dM] (sun3) ufsboot gives no second chances
X-Send-Pr-Version: 3.2

>Number:         1726
>Category:       port-sun3
>Synopsis:       [dM] (sun3) ufsboot gives no second chances
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 03 21:50:02 +0000 1995
>Closed-Date:    Wed Apr 10 18:30:05 +0000 1996
>Last-Modified:  Wed Apr 10 18:33:23 +0000 1996
>Originator:     der Mouse
>Release:        1.1_ALPHA, sup of Nov 2 AM
>Organization:
	Dis-
>Environment:
	Machine is Sun-3/150, disk is:
	  vmes0 at mainbus0
	  si0 at vmes0 addr 0xff200000 level 2 vector 0x40
	  scsibus0 at si0
	  si0 targ 0 lun 0: <SEAGATE, ST15230N, 0498> SCSI2 0/direct fixed
	  sd0 at scsibus0: 4095MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sec
	though I suspect it has nothing to do with the details of the
	disk, and possibly isn't even sun3-specific.
>Description:
	If you once give a nonexistent filename to ufsboot, all further
	attempts produce a confusing and unhelpful failure, a failure
	that shouldn't be happening at all.
>How-To-Repeat:
	>b nebtsd -s
	Boot: sd(0,0,0)nebtsd -s
	>> NetBSD ufsboot [$Revision: 1.2 $]
	boot: nebtsd: No such file or directory
	boot: netbsd
	boot: netbsd: Unknown error: code 24
	boot: 

	All further attempts produce the same "Unknown error: code 24",
	regardless of whether they exist or not, as far as I can tell.

	Upon resetting at this point with the back panel switch,
	though, booting with
	>b netbsd -s
	works fine; it's not anything wrong with /netbsd itself.
>Fix:
	Unknown.  I browsed through ufsboot source and didn't see
	anything obvious, but I must admit a certain lack of
	understanding of what's going on there.

					der Mouse

			    mouse@collatz.mcrcim.mcgill.edu
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: gwr 
State-Changed-When: Mon Jan 29 18:46:55 EST 1996 
State-Changed-Why:  
Corrected the open/close logic in sys/arch/sun3/stand/netboot/dev_net.c 
State-Changed-From-To: closed->open 
State-Changed-By: gwr 
State-Changed-When: Tue Jan 30 14:40:11 EST 1996 
State-Changed-Why:  
I closed this by mistake. (wishful thinking) 
State-Changed-From-To: open->closed 
State-Changed-By: gwr 
State-Changed-When: Wed Apr 10 14:30:05 EDT 1996 
State-Changed-Why:  
Changed sys/arch/sun3/stand/libsa/dev_disk.c to 
call prom_iopen only on the first disk_open. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.