Re: port-alpha/22160 (panic using SCSI TK50 in NetBSD 1.6.1)

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR port-alpha/22160; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: "John A. Dundas III" <dundas%caltech.edu@localhost>
Cc: port-alpha-maintainer%netbsd.org@localhost, 
gnats-admin%netbsd.org@localhost,
        netbsd-bugs%netbsd.org@localhost, gnats-bugs%netbsd.org@localhost
Subject: Re: port-alpha/22160 (panic using SCSI TK50 in NetBSD 1.6.1)
Date: Tue, 2 Dec 2008 16:38:02 +0000

 On Mon, Dec 01, 2008 at 05:10:05PM +0000, John A. Dundas III wrote:
  >  >Synopsis: panic using SCSI TK50 in NetBSD 1.6.1
  >  >
  >  >State-Changed-From-To: open->feedback
  >  >State-Changed-By: dholland%NetBSD.org@localhost
  >  >State-Changed-When: Sun, 30 Nov 2008 07:04:44 +0000
  >  >State-Changed-Why:
  >  >Have you seen this problem on a recent kernel?
  >  
  >  Gee, I filed that ticket several years ago :-)
 
 And it's sat there ever since :(  I've been trying to get ones like
 that some attention.
 
  >  I haven't tried recently.  Is there any reason to expect a change in 
  >  behavior with a more recent kernel than the one it was filed under?
 
 There have been a number of changes to physio (and st) since 1.6,
 so... maybe. I think in -current or 5.0 beta it probably at least
 won't crash the system any more just because you get an I/O error from
 the system. (Although on the other hand, beware of PR 38643.)
 
 I don't have any idea if anything's been done with the vax-specific
 patches, but if you can find them it should be possible to figure out.
 
 The urls in the original report are all stale, I'm afraid.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost