NetBSD Problem Report #447

From gnats  Tue Aug 30 22:56:29 1994
Received: from MindBender.HeadCandy.com (root@stingray.cc.iastate.edu [129.186.140.33]) by sun-lamp.cs.berkeley.edu (8.6.9/8.6.9) with ESMTP id WAA06749 for <gnats-bugs@sun-lamp.cs.berkeley.edu>; Tue, 30 Aug 1994 22:56:27 -0700
Message-Id: <199408310557.AAA00490@MindBender.HeadCandy.com>
Date: Wed, 31 Aug 1994 00:57:12 -0500
From: "Michael L. VanLoon" <michaelv@HeadCandy.com>
Reply-To: michaelv@HeadCandy.com
To: gnats-bugs@sun-lamp.cs.berkeley.edu
Subject: bt driver bug in current
X-Send-Pr-Version: 3.2

>Number:         447
>Category:       kern
>Synopsis:       bt driver problem
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 30 23:05:02 +0000 1994
>Closed-Date:    Wed Dec 07 17:24:25 +0000 1994
>Last-Modified:  
>Originator:     Michael L. VanLoon
>Release:        NetBSD/i386-1.0_Beta, 8/30/94 sup
>Organization:
HeadCandy Associates... Playing with your mind
>Environment:
ALR 486DLC EISA, 17MB, build from 8/30/94 current sup

System: NetBSD MindBender.HeadCandy.com 1.0_BETA NetBSD 1.0_BETA (MINDBENDER) #158: Sat Aug 13 22:33:31 CDT 1994 michaelv@MindBender.HeadCandy.com:/usr/src/sys/arch/i386/compile/MINDBENDER i386


>Description:
The last build I did was from a sup around the 12th or
13th.  That kernel has been running just great -- no problems.  I
built a kernel from the 8/20 sup, and again from the 8/30 sup,
remaking config each time, and both of them give me timeouts and
resyncs on the SCSI drive.  They generally look like this:

Aug 31 00:00:45 MindBender /netbsd: bt0: mbi at 0xf87039cc should be found, stat=81..resync
Aug 31 00:00:45 MindBender /netbsd: bt0: mbi at 0xf87039e4 should be found, stat=81..resync
Aug 31 00:00:45 MindBender /netbsd: bt0: mbi at 0xf87039fc should be found, stat=81..resync
Aug 31 00:00:45 MindBender /netbsd: sd0(bt0:0:0): timed out 

The system doesn't crash -- it generally continues to run for the
short amount of time I keep it up, but the resyncs and timeouts make
for very frequent and long pauses.  The 8/13 kernel doesn't exhibit
this behaviour.

(Charles, I'm not using your modifications that you suggested yet.)

>How-To-Repeat:
It happens every time I boot one of the new kernels
I've build.  I've built four different kernels that do this.

>Fix:
Heckifiknow.  It must be some modification made to something to
do with the SCSI subsystem or bt driver between now (or the 20th), and
the 12th or 13th, when it worked last.


	The submitter reports that this turned out to be a problem with
	Cyrix 486DLC handling, which has since been fixed.  - mycroft

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: mycroft 
State-Changed-When: Wed Dec 7 09:24:25 PST 1994 
State-Changed-Why:  
Submitter says this was a different bug, which has been fixed. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.