From owner-freebsd-current  Fri Apr 25 05:41:09 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id FAA12383
          for current-outgoing; Fri, 25 Apr 1997 05:41:09 -0700 (PDT)
Received: from chess.inetspace.com ([206.50.163.14])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA12378
          for <freebsd-current@freebsd.org>; Fri, 25 Apr 1997 05:41:06 -0700 (PDT)
Received: (from kgor@localhost) by chess.inetspace.com (8.8.5/8.7.3) id HAA01650; Fri, 25 Apr 1997 07:38:34 -0500 (CDT)
Date: Fri, 25 Apr 1997 07:38:34 -0500 (CDT)
Message-Id: <199704251238.HAA01650@chess.inetspace.com>
From: "Kent S. Gordon" <kgor@inetspace.com>
To: obiwan@zeppelin.net
CC: freebsd-current@freebsd.org, davidn@unique.usn.blaze.net.au
In-reply-to: <XFMail.970424154557.obiwan@zeppelin.net> (message from Josh
	Howard on Thu, 24 Apr 1997 15:43:16 -0700 (PDT))
Subject: Re: Upgrading from 3.0-19970209-SNAP to -current
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>>>> "obiwan" == Josh Howard <obiwan@zeppelin.net> writes:

    > On 24-Apr-97 Kent S. Gordon wrote:
    >>>>>>> "davidn" == David Nugent <davidn@unique.usn.blaze.net.au>
    >>>>>>> writes:
    >> I have Cyrix 596-100, 16MB, bustek 445 and New kernel's do not
    >> successfully boot (die in detection of boot device.  Message
    >> vary with -current date and kernel options.  Normally just a
    >> hang, but I have seen disk detected as unknown device.  I tried
    >> tracing it using DDB but was unsuccesfully in finding anything
    >> useful).

    > Well, these problems we're suffering from seem to leave no
    > message, no kernel problems that are obvious, etc. Not sure
    > where your problem lies..

    >>  scsi detection.  My guess is that we are triggering a VM bug.
    >> 
    >> > It might even be a bug that's been there all along, but the >
    >> lite2 merges have brought it to light.
    >> 
    >> > Come to think of it, all of the other -current machines I run
    >> > and work fine are scsi, or in one case, mostly scsi - aha and
    >> > aic types. Hmm.  I have a PP-180, 64MB, mainly ide system
    >> that works great.
    >> 

    > Well, the newest theory might be pointing towards pppd (or even
    > ijppp), do you run either of those on that machine?
No ppp or ijppp.  My problem looks like somehow the scsi adapter has
been wedged and the code just loops looking for a valid scsi command
returning.

Kent S. Gordon
Senior Software Engineer
iNetSpace Co.
voice: (972)851-3494 fax:(972)702-0384 e-mail:kgor@inetspace.com