Subject: kern/31279: esiop driver trouble
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <e.e.dehling@student.utwente.nl>
List: netbsd-bugs
Date: 09/09/2005 19:38:00
>Number:         31279
>Category:       kern
>Synopsis:       esiop driver trouble
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Sep 09 19:38:00 +0000 2005
>Originator:     Eike Dehling
>Release:        2.0
>Organization:
>Environment:
NetBSD hostname 2.0 NetBSD 2.0 (GENERIC) #0: Tue Nov 30 21:04:03 UTC 2004  builds@build:/big/builds/ab/netbsd-2-0-RELEASE/alpha/200411300000Z-obj/big/builds/ab/netbsd-2-0-RELEASE/src/sys/arch/alpha/compile/GENERIC alpha
>Description:
When using the generic kernel, my lsi 53c896 based scsi adapter is recognised by the esiop driver. This driver quite regularly panics my system: sometimes it will panic during shutdown, preventing the kernel from syncing discs, sometimes it will panic during CVS checkouts, etc. Generally at inconvenient moments while there is (heavy) filesystem activity. I haven't experienced this with the siop driver. 
>How-To-Repeat:
Get a system with an LSI 53c896 card, and generate some heavy filesystem activity. With some "luck" it will panic.
>Fix: