NetBSD Problem Report #16379
Received: (qmail 18873 invoked from network); 16 Apr 2002 23:40:32 -0000
Message-Id: <200204162340.g3GNeH326317@starbuck.kasbah>
Date: Wed, 17 Apr 2002 01:40:17 +0200 (CEST)
From: reinoud@netbsd.org
Reply-To: reinoud@netbsd.org
To: gnats-bugs@gnats.netbsd.org
Subject: Serious problems with the ohci driver on a DEC PWS 500au (Alpha)
X-Send-Pr-Version: 3.95
>Number: 16379
>Category: port-alpha
>Synopsis: Serious problems with the ohci driver on a DEC PWS 500au (Alpha)
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Apr 16 23:41:00 +0000 2002
>Closed-Date: Mon Mar 25 07:54:53 +0000 2013
>Last-Modified: Mon Mar 25 07:54:53 +0000 2013
>Originator: Reinoud Zandijk
>Release: NetBSD 1.5ZC
>Organization:
>Environment:
System: NetBSD starbuck.kasbah 1.5ZC NetBSD 1.5ZC (config.starbuck) #8: Mon Apr 15 01:00:44 CEST 2002 root@starbuck.13thmonkey.org:/usr/sources/cvs.netbsd.org/src/sys/arch/alpha/compile/config.starbuck alpha
Architecture: alpha
Machine: DEC PersonalWorkStation 500au Alpha machine with PCI devices.
The build in USB device :
vendor 0x1080 product 0xc693 (USB serial bus, interface 0x10) at pci0 dev 7 function 3 not configured
>Description:
When i reinstalled my Alpha i came to this same problem again : the GENERIC kernel
does boot but panics the machine later on IDE disk activity... resulting in interrupt
lossage and propable data corruption. The USB is an integrated device so i can't just
rip it out ... i've build a custum kernel without the USB drivers and all works fine
but offcource no USB.
In backtalk with Jason Thorpe its propably a busspace barrier problem that the driver
seems to lack resulting in this mayhem.
>How-To-Repeat:
Boot a GENERIC kernel on a DEC PWS 500au and you are in trouble.
>Fix:
Create a kernel without the USB drivers uhci and ohci (probed)
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: kern-bug-people->mycroft
Responsible-Changed-By: mycroft
Responsible-Changed-When: Tue Jun 29 02:54:23 UTC 2004
Responsible-Changed-Why:
.
From: Reinoud Zandijk <reinoud@netbsd.org>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/16379
Date: Thu, 5 Aug 2004 16:22:15 +0200
Update on PR# : In -current sources (05 aug 2004) the USB works!!! I tested
the USB mouse and allthough it has some weird plug-in behaviour, it seems
to work OK (no data read out though... no testing program and X isnt
working without INSECURE). Still IRQ problems with the harddisc in
-current so i haven't tested it thouroughly.
Small `dmesg' piece from booting: (IRQ14 is IDE); note the sheduling
overrun while no USB devices connected (!)
-----
stray isa irq 14
stray isa irq 14; stopped logging
root file system type: ffs
ohci0: 1 scheduling overruns
nfs_send: proc botch: rep 0x0 arg 0x0 curproc 0xfffffc0001c28280
------
Connect USB mouse:
---------
uhidev0 at uhub0 port 1 configuration 1 interface 0
uhidev0: Logitech USB Mouse, rev 1.10/6.20, addr 2, iclass 3/1
ums0 at uhidev0: 3 buttons and Z dir.
ohci0: 1 scheduling overruns
wsmouse1 at ums0 (mux ignored)
uhidev0: at uhub0 port 1 (addr 2) disconnected
wsmouse1 detached
ums0 detached
uhidev0 detached
uhidev0 at uhub0 port 1 configuration 1 interface 0
uhidev0: Logitech USB Mouse, rev 1.10/6.20, addr 2, iclass 3/1
ums0 at uhidev0: 3 buttons and Z dir.
wsmouse1 at ums0 (mux ignored)
------
Disconnect mouse:
------
uhidev0: at uhub0 port 1 (addr 2) disconnected
wsmouse1 detached
ums0 detached
uhidev0 detached
------
Connect again:
------
uhidev0 at uhub0 port 2 configuration 1 interface 0
uhidev0: Logitech USB Mouse, rev 1.10/6.20, addr 2, iclass 3/1
ums0 at uhidev0: 3 buttons and Z dir.
wsmouse1 at ums0 (mux ignored)
uhidev0: at uhub0 port 2 (addr 2) disconnected
wsmouse1 detached
ums0 detached
uhidev0 detached
uhidev0 at uhub0 port 2 configuration 1 interface 0
uhidev0: Logitech USB Mouse, rev 1.10/6.20, addr 2, iclass 3/1
ums0 at uhidev0: 3 buttons and Z dir.
wsmouse1 at ums0 (mux ignored)
ohci0: 1 scheduling overruns
syncing disks... 6 6 done
rebooting...
....
Question: why the connect, disconnect, connect sequence as shown above when
plugging in a device ?
Responsible-Changed-From-To: mycroft->kern-bug-people
Responsible-Changed-By: wiz@netbsd.org
Responsible-Changed-When: Sun, 03 Sep 2006 01:13:42 +0000
Responsible-Changed-Why:
Back to role account, mycroft doesn't have commit access any longer.
State-Changed-From-To: open->closed
State-Changed-By: skrll@NetBSD.org
State-Changed-When: Mon, 25 Mar 2013 07:54:53 +0000
State-Changed-Why:
Reinoud is happy to close as he doesn't have the hardware anymore. The problem also
seems to be mostly fixed.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.