NetBSD Problem Report #20128

Received: (qmail 1865 invoked by uid 605); 30 Jan 2003 21:49:14 -0000
Message-Id: <200301302149.h0ULnAK09317@zentrum2.radiologie.rad.klinikum.rwth-aachen.de>
Date: Thu, 30 Jan 2003 22:49:10 +0100 (MET)
From: kilbi@rad.rwth-aachen.de
Sender: gnats-bugs-owner@netbsd.org
Reply-To: kilbi@rad.rwth-aachen.de
To: gnats-bugs@gnats.netbsd.org
Subject: sys/dev/tc/if_le_tc.c 1.15-1.16 changes break scsi detection of rx23 device
X-Send-Pr-Version: 3.95

>Number:         20128
>Category:       port-alpha
>Synopsis:       With the above change the rx23 scsi dev (floppy) is no longer detected
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-alpha-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 30 21:50:00 +0000 2003
>Closed-Date:    
>Last-Modified:  Tue Aug 19 00:50:02 +0000 2008
>Originator:     
>Release:        NetBSD 1.6_STABLE / 1.6_RC1 (and -current I guess)
>Organization:
>Environment:
System: NetBSD zentrum2 1.6_STABLE NetBSD 1.6_STABLE (ZENTRUM2) #28: Sun Jan 12 04:25:40 MET 2003 kilbi@dfgaxp:/amd/basis.lke/usr/src/sys/arch/alpha/compile/ZENTRUM2 alpha
Architecture: alpha
Machine: alpha
>Description:
With the above mentioned changes to sys/dev/tc/if_le_tc.c (recent in
the 1.6 branch) my (additional) le1 device is initialized and works
correctly:

  NetBSD 1.6_RC1 (ZENTRUM2) #0: Tue Jan 28 22:25:40 MET 2003
  DEC 3000 - M300X, 175MHz, s/n
  8192 byte page size, 1 processor.
  total memory = 256 MB
  (2048 KB reserved for PROM, 254 MB used by NetBSD)
  avail memory = 232 MB
  using 1638 buffers containing 13104 KB of memory
  mainbus0 (root)
  cpu0 at mainbus0: ID 0 (primary), 21064-1
  cpu0: Architecture extensions: 2<FIX>
  [...]
  le1 at tc0 slot 1 offset 0x0: address 08:00:2b:93:4d:29
  le1: 32 receive buffers, 8 transmit buffers

but the formerly detected scsi device (a scsi floppy drive):

  tcds0 at tc0 slot 4 offset 0x0: TurboChannel Dual SCSI (baseboard)
  tcds0: fast mode set for chip 0
  asc0 at tcds0 chip 0: NCR53C94, 25MHz, SCSI ID 7
  scsibus0 at asc0: 8 targets, 8 luns per target
  [...]
  sd1 at scsibus0 target 1 lun 0: <DEC, RX23     (C) DEC, 0070> SCSI1 0/direct removable
  sd1: drive offline
  sd1: async, 8-bit transfers

is no longer detected (which changes the numbering of all following
scsi disks :-/).
>How-To-Repeat:
Just compile a kernel with sys/dev/tc/if_le_tc.c v1.15 or v1.16: With
v1.15 le1 doesn't work, but the rx23 is detected. With v1.16 le1
works, but the rx23 is not detected.
>Fix:
No idea.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: mycroft 
State-Changed-When: Thu Jul 8 20:08:57 UTC 2004 
State-Changed-Why:  
I think this was related to a one-byte array overrun that I fixed on  
2003/09/26.  Have you tested it again since then? 


Responsible-Changed-From-To: port-alpha-maintainer->mycroft 
Responsible-Changed-By: mycroft 
Responsible-Changed-When: Thu Jul 8 20:08:57 UTC 2004 
Responsible-Changed-Why:  
. 

From: Markus W Kilbinger <kilbi@rad.rwth-aachen.de>
To: gnats-bugs@gnats.netbsd.org
Cc: mycroft@netbsd.org, port-alpha-maintainer@netbsd.org
Subject: Re: port-alpha/20128
Date: Fri, 9 Jul 2004 00:16:48 +0200

 >>>>> "mycroft" == mycroft  <mycroft@netbsd.org> writes:

     mycroft> Synopsis: With the above change the rx23 scsi dev (floppy) is no longer detected
     mycroft> State-Changed-From-To: open->feedback
     mycroft> State-Changed-By: mycroft
     mycroft> State-Changed-When: Thu Jul 8 20:08:57 UTC 2004
     mycroft> State-Changed-Why: 
     mycroft> I think this was related to a one-byte array overrun that I fixed on 
     mycroft> 2003/09/26.  Have you tested it again since then?

 The machine is running now an actual netbsd-2-0 kernel (and userland)
 (which should contain your fix from 2003/09/26?) and still does not
 find the rx23 device.

 Should I try a current kernel?

 Markus.
Responsible-Changed-From-To: mycroft->port-alpha-maintainer
Responsible-Changed-By: wiz@netbsd.org
Responsible-Changed-When: Sun, 03 Sep 2006 01:18:17 +0000
Responsible-Changed-Why:
Back to role account, mycroft doesn't have commit access any longer.


State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 04 May 2008 02:42:22 +0000
State-Changed-Why:
Feedback received, in 2004.
Trying a -current kernel now might be helpful, but probably nothing's
changed.


From: Markus W Kilbinger <kilbi@rad.rwth-aachen.de>
To: gnats-bugs@NetBSD.org
Cc: port-alpha-maintainer@netbsd.org, netbsd-bugs@netbsd.org,
	gnats-admin@netbsd.org, dholland@NetBSD.org
Subject: Re: port-alpha/20128 (With the above change the rx23 scsi dev (floppy)
 is no longer detected)
Date: Mon, 18 Aug 2008 15:51:41 +0200

 >>>>> "dholland" == dholland  <dholland@NetBSD.org> writes:

     dholland> Synopsis: With the above change the rx23 scsi dev (floppy) is no longer detected
     dholland> State-Changed-From-To: feedback->open
     dholland> State-Changed-By: dholland@NetBSD.org
     dholland> State-Changed-When: Sun, 04 May 2008 02:42:22 +0000
     dholland> State-Changed-Why:
     dholland> Feedback received, in 2004.
     dholland> Trying a -current kernel now might be helpful, but probably nothing's
     dholland> changed.

 Hmm, the machine has retired 2 yrs ago. Just to resurrect it for
 re-testing is quite a huge effort for me to do... esp. if it's not
 very promising.

 So, for me the problem was 'gone' by retiring the machine. If I'm the
 only one (left) with this problem, you can close the PR.

 Markus.

From: David Holland <dholland-bugs@netbsd.org>
To: Markus W Kilbinger <kilbi@rad.rwth-aachen.de>
Cc: gnats-bugs@NetBSD.org, port-alpha-maintainer@netbsd.org,
	netbsd-bugs@netbsd.org, gnats-admin@netbsd.org, dholland@NetBSD.org
Subject: Re: port-alpha/20128 (With the above change the rx23 scsi dev
	(floppy) is no longer detected)
Date: Tue, 19 Aug 2008 00:45:40 +0000

 On Mon, Aug 18, 2008 at 03:51:41PM +0200, Markus W Kilbinger wrote:
  >     dholland> State-Changed-Why:
  >     dholland> Feedback received, in 2004.
  >     dholland> Trying a -current kernel now might be helpful, but 
  >     dholland> probably nothing's changed.
  > 
  > Hmm, the machine has retired 2 yrs ago. Just to resurrect it for
  > re-testing is quite a huge effort for me to do... esp. if it's not
  > very promising.

 Ok. Don't bother unless you feel the urge sometime.

  > So, for me the problem was 'gone' by retiring the machine. If I'm the
  > only one (left) with this problem, you can close the PR.

 Well, we don't know if you are or not, that's the thing, and with
 problems like this (that are reasonably serious and that someone else
 might be able to test) it's better to keep the report open. I'll add
 it to my list of stuck but valid PRs nobody can do anything with.
 Sometime we might manage to teach gnats about this list...

 -- 
 David A. Holland
 dholland@netbsd.org

>Unformatted:

Home	PR Database Search