NetBSD Problem Report #12521

Received: (qmail 25045 invoked from network); 1 Apr 2001 13:32:48 -0000
Message-Id: <Pine.SOL.4.33.0104011428110.2715-100000@draco.cus.cam.ac.uk>
Date: Sun, 1 Apr 2001 14:32:36 +0100 (BST)
From: Ben Harris <bjh21@netbsd.org>
Sender: Ben Harris <bjh21@cus.cam.ac.uk>
To: <gnats-bugs@gnats.netbsd.org>
Subject: aborts using ei(4) and asc(4)

>Number:         12521
>Category:       port-acorn32
>Synopsis:       aborts using ei(4) and asc(4)
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-acorn32-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 01 13:33:00 +0000 2001
>Closed-Date:    
>Last-Modified:  Mon Feb 28 14:57:27 +0000 2011
>Originator:     Ben Harris
>Release:        2001-03-31
>Organization:
>Environment:
>Description:
[ Reported on port-arm32 by Richard Earnshaw.  I don't want to lose it. ]

rearnsha@arm.com said:
> Unfortunately, adding this driver seems to be causing my RPC to abort
> in  irq_enter when (checking the SPL masks, I think).  One possibility
> is that  this is related to the fact that I have both an Ether1 and an
> Acorn SCSI  card on the same podule bus (and that both have to share
> the same irq  entry).  Didn't have time to look further last night, or
> try backing off  to the old driver to see if it might be something
> unrelated.

>How-To-Repeat:
>Fix:



>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: port-arm32-maintainer->bjh21 
Responsible-Changed-By: bjh21 
Responsible-Changed-When: Sun Apr 1 06:37:58 PDT 2001 
Responsible-Changed-Why:  
I'm responsible for the ei(4) driver and for the new podulebus code. 
I expect one or the other of those is at fault. 

Message-Id: <Pine.SOL.4.33.0104071454570.863-100000@libra.cus.cam.ac.uk>
Date: Sat, 7 Apr 2001 15:03:03 +0100 (BST)
From: Ben Harris <bjh21@netbsd.org>
Sender: Ben Harris <bjh21@cus.cam.ac.uk>
To: <rearnsha@arm.com>
Cc: <gnats-bugs@gnats.netbsd.org>
Subject: parm-arm32/12521: aborts using ei(4) and asc(4)

 I've been trying to reproduce the aborts you were getting using my new
 Ether1 driver in the same system as an Acorn SCSI controller, and I
 haven't had much success (e.g. flood pinging the Ether1 while dding from a
 convenient SCSI CD-ROM drive).  Could you give me some more details about
 your configuration, and what you did to trigger the problem?

 Thanks in advance.

 -- 
 Ben Harris                                                   <bjh21@netbsd.org>
 Portmaster, NetBSD/arm26               <URL:http://www.netbsd.org/Ports/arm26/>

Message-Id: <200104071449.PAA07729@cam-mail2.cambridge.arm.com>
Date: Sat, 07 Apr 2001 15:49:15 +0100
From: Richard Earnshaw <rearnsha@arm.com>
Reply-To: Richard.Earnshaw@arm.com
To: Ben Harris <bjh21@netbsd.org>
Cc: rearnsha@arm.com, gnats-bugs@gnats.netbsd.org
In-Reply-To: Your message of "Sat, 07 Apr 2001 15:03:03 BST."
             <Pine.SOL.4.33.0104071454570.863-100000@libra.cus.cam.ac.uk> 
Subject: Re: parm-arm32/12521: aborts using ei(4) and asc(4) 


 IIRC ftp of large amounts of data to the RISCPC should trigger it.

 I'll try it again at some point to see if it's still there...

 R.


Responsible-Changed-From-To: bjh21->port-acorn32-maintainer
Responsible-Changed-By: wiz@NetBSD.org
Responsible-Changed-When: Mon, 28 Feb 2011 14:57:27 +0000
Responsible-Changed-Why:
Reset responsible field for retired developer.


>Unformatted:

Home	PR Database Search