From nobody  Sat Aug  9 20:51:49 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id UAA00415;
          Sat, 9 Aug 1997 20:51:49 -0700 (PDT)
Message-Id: <199708100351.UAA00415@hub.freebsd.org>
Date: Sat, 9 Aug 1997 20:51:49 -0700 (PDT)
From: itojun@itojun.org
To: freebsd-gnats-submit@freebsd.org
Subject: ahc driver: kernel goes to strange state if other device wakes up on the same scsi bus
X-Send-Pr-Version: www-1.0

>Number:         4256
>Category:       kern
>Synopsis:       ahc driver: kernel goes to strange state if other device wakes up on the same scsi bus
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gibbs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Aug  9 21:00:01 PDT 1997
>Closed-Date:    Tue Nov 3 11:09:02 PST 1998
>Last-Modified:  Tue Nov  3 11:09:40 PST 1998
>Originator:     Jun-ichiro Itoh
>Release:        FreeBSD 2.2.1-RELEASE
>Organization:
itojun.org
>Environment:
FreeBSD 2.2.1-RELEASE
FreeBSD 2.2.1-RELEASE + 2.2.2-RELEASE kernel has the same behavior.

>Description:
In an environment that two PC is sharing same scsi device,
FreeBSD box will go mad when power sw of Win95 turned on.
(FreeBSD box will answer to ping, however it looks that no user process
is running)
	printer (scsi port 1) ----- FreeBSD
		(scsi port 2) ----- Win95

On screen the following message will appear:
  Unexpected busfree.  LASTPHASE == 0x80
  SEQADDR == 0x42
  uk0(ahc0:1:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0
  SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa
  uk0(ahc0:1:0): SCB 0: Immediate reset.  Flags = 0x401
  ahc0: Issued Channel A Bus Reset. 1 SCBs aborted

>How-To-Repeat:
mmm, I'm not sure.
>Fix:
not yet. sorry.
tell me if there's anything i can do to track the reasons.
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->gibbs 
Responsible-Changed-By: itojun 
Responsible-Changed-When: Fri Oct 17 02:31:56 PDT 1997 
Responsible-Changed-Why:  
please help me Mr.ahc... 

State-Changed-From-To: open->feedback 
State-Changed-By: gibbs 
State-Changed-When: Mon Nov 2 11:45:53 PST 1998 
State-Changed-Why:  
Do you still see this behavior using the CAM SCSI aic7xxx drivers? 
State-Changed-From-To: feedback->closed 
State-Changed-By: gibbs 
State-Changed-When: Tue Nov 3 11:09:02 PST 1998 
State-Changed-Why:  
Originator no longer has hardware to test against and it is believed that this 
problem is fixed by CAM. 
>Unformatted:
