NetBSD Problem Report #10669

Received: (qmail 889 invoked from network); 24 Jul 2000 18:08:02 -0000
Message-Id: <200007241808.LAA26975@nbwww.isc.org>
Date: Mon, 24 Jul 2000 11:08:02 -0700 (PDT)
From: t1345@hopi.dtcc.edu
Reply-To: t1345@hopi.dtcc.edu
To: gnats-bugs@gnats.netbsd.org
Subject: continous repeat on LK-501AA
X-Send-Pr-Version: www-1.0

>Number:         10669
>Category:       port-pmax
>Synopsis:       continous repeat on LK-501AA
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-pmax-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 24 18:09:01 +0000 2000
>Closed-Date:    Tue Mar 23 07:23:30 +0000 2004
>Last-Modified:  Tue Mar 23 07:23:30 +0000 2004
>Originator:     Chris Tribo
>Release:        1.5 Alpha
>Organization:
>Environment:
NetBSD w-sysop-3.dtcc.edu 1.5_ALPHA NetBSD 1.5_ALPHA (Challenger) #2: Thu Jul  6
 17:11:52 EDT 2000     root@Challenger:/usr/src/sys/arch/pmax/compile/Challenger
 pmax

>Description:
upon starting xdm, if the dtop driver gets an overrun,
it doesn't appear to detect or correct it. So when the login window
appears, the cursor is just bouncing back and forth betweeen login and
password with login incorrect displayed below. Hitting control-C makes
the dialog reset, but when the login comes back it still occours. I can
log in if I hold down Enter and type at the same time (shouldn't be 
possible?) but I get nothing but carrige returns as soon as I get to an
xterm. I tried pushing all the buttons on the keyboard, and when I got 
to around the Do key, a white column came up on the left part of the
screen and the system appeared to freeze. Control-Alt-Enter did not work
so I had to reset the machine with Control-Alt-<X 


>How-To-Repeat:
Don't know how you could make an overrun occour while starting xdm

>Fix:
Fix the Access.Bus driver :)

>Release-Note:
>Audit-Trail:

From: Christopher Tribo <ctribo@hopi.dtcc.edu>
To: gnats-bugs@netbsd.org
Cc:  
Subject: Re: bin/10669
Date: Mon, 24 Jul 2000 14:11:51 -0400

 Sorry, I really screwed up, this PR should have gone to port-pmax as a
 SW-bug with low priority. Shall I re-file it?


 	Chris

From: t1345@hopi.dtcc.edu
To: gnats-bugs@gnats.netbsd.org
Cc:  
Subject: bin/10669: continous repeat on LK-501AA
Date: Mon, 24 Jul 2000 11:08:02 -0700 (PDT)

 >Number:         10669
 >Category:       bin
 >Synopsis:       continous repeat on LK-501AA
 >Confidential:   no
 >Severity:       non-critical
 >Priority:       low
 >Responsible:    bin-bug-people
 >State:          open
 >Class:          sw-bug
 >Submitter-Id:   net
 >Arrival-Date:   Mon Jul 24 11:09:01 PDT 2000
 >Closed-Date:
 >Last-Modified:
 >Originator:     Chris Tribo
 >Release:        1.5 Alpha
 >Organization:
 >Environment:
 NetBSD w-sysop-3.dtcc.edu 1.5_ALPHA NetBSD 1.5_ALPHA (Challenger) #2: Thu Jul  6
  17:11:52 EDT 2000     root@Challenger:/usr/src/sys/arch/pmax/compile/Challenger
  pmax

 >Description:
 upon starting xdm, if the dtop driver gets an overrun,
 it doesn't appear to detect or correct it. So when the login window
 appears, the cursor is just bouncing back and forth betweeen login and
 password with login incorrect displayed below. Hitting control-C makes
 the dialog reset, but when the login comes back it still occours. I can
 log in if I hold down Enter and type at the same time (shouldn't be 
 possible?) but I get nothing but carrige returns as soon as I get to an
 xterm. I tried pushing all the buttons on the keyboard, and when I got 
 to around the Do key, a white column came up on the left part of the
 screen and the system appeared to freeze. Control-Alt-Enter did not work
 so I had to reset the machine with Control-Alt-<X 


 >How-To-Repeat:
 Don't know how you could make an overrun occour while starting xdm

 >Fix:
 Fix the Access.Bus driver :)

 >Release-Note:
 >Audit-Trail:
 >Unformatted:


Responsible-Changed-From-To: bin-bug-people->port-pmax-maintainer 
Responsible-Changed-By: fair 
Responsible-Changed-When: Fri Jan 4 16:32:04 PST 2002 
Responsible-Changed-Why:  
misfiled PR reassigned. 

From: Chris Tribo <ctribo@college.dtcc.edu>
To: gnats-bugs@netbsd.org
Cc:  
Subject: Re: port-pmax/10669
Date: Tue, 23 Mar 2004 02:08:40 -0500 (EST)

 	This problem is now fixed with the wscons kernel in -current. You
 may close this pr.
State-Changed-From-To: open->closed 
State-Changed-By: simonb 
State-Changed-When: Tue Mar 23 07:22:53 UTC 2004 
State-Changed-Why:  
Problem noted as fixed by the PR originator. 
>Unformatted:

Home	PR Database Search