Subject: kern/13202: uhci does not work on MIPS
To: None <>
From: None <>
List: netbsd-bugs
Date: 06/13/2001 20:14:12
>Number:         13202
>Category:       kern
>Synopsis:       uhci does not work on MIPS
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jun 13 20:13:01 PDT 2001
>Originator:     Jason R Thorpe
>Release:        NetBSD 1.5W, June 13, 2001
Zembu Labs, Inc.
System: NetBSD 1.5W NetBSD 1.5W (P5064) #82: Wed Jun 13 19:45:28 PDT 2001 algor
Architecture: mipsel
Machine: algor
	The `uhci' USB controller driver does not work on MIPS.  The
	error manifests itself on the Algorithmics P-5064 as a bus
	error, and the system hanging before asking the operator
	for the root device.

	The boot messages from a failed boot w/ uhci are:

 [ no symbols available ]

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 1.5W (P5064) #82: Wed Jun 13 19:45:28 PDT 2001
Algorithmics P-5064
total memory = 159 MB
avail memory = 144 MB
using 2073 buffers containing 8292 KB of memory
mainbus0 (root)
cpu0 at mainbus0: QED RM5200 CPU (0x2810) Rev. 1.0 with built-in FPU Rev. 1.0
cpu0: L1 cache: 16KB/32B instruction, 16KB/32B data, two way set associative
cpu0: No L2 cache
vtpbc0 at mainbus0 addr 0x1ef00000: V3 V962, revision C0
pci0 at vtpbc0 bus 0
pci0: i/o space, memory space enabled
tlp0 at pci0 dev 0 function 0: DECchip 21143 Ethernet, pass 4.1
tlp0: interrupting at Ethernet IRQ
tlp0: Ethernet address 00:40:bc:04:00:43
qsphy0 at tlp0 phy 13: QS6612 10/100 media interface, rev. 1
qsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
siop0 at pci0 dev 1 function 0: Symbios Logic 53c810a (fast scsi)
siop0: interrupting at SCSI IRQ
scsibus0 at siop0: 8 targets, 8 luns per target
pcib0 at pci0 dev 2 function 0: Intel 82371SB PCI-to-ISA Bridge (PIIX3) (rev. 0x01)
pciide0 at pci0 dev 2 function 1: Intel 82371SB IDE Interface (PIIX3) (rev. 0x00)
pciide0: bus-master DMA support present
pciide0: primary channel wired to compatibility mode
pciide0: primary channel ignored (disabled)
pciide0: secondary channel wired to compatibility mode
pciide0: secondary channel ignored (disabled)
uhci0 at pci0 dev 2 function 2: Intel 82371SB USB Host Controller (PIIX3) (rev. 0x01)
uhci0: interrupting at USB IRQ
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ATI Technologies Mach64 B (VGA display, revision 0x5c) at pci0 dev 3 function 0 not configured
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com0: console
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
mcclock0 at isa0 port 0x70-0x71: mc146818 or compatible
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
pcic0 at isa0 port 0x3e0-0x3e1 iomem 0xd0000-0xdffff
pcic0: controller 0 (Intel 82365SL Revision 1) has sockets A and B
pcic0: controller 1 (Intel 82365SL Revision 1) has no sockets
pcmcia0 at pcic0 controller 0 socket 0
pcmcia1 at pcic0 controller 0 socket 1
scsibus0: waiting 2 seconds for devices to settle...
WARNING: Bus error
uhci0: host system error
uhci0: host controller halted
pcic0: controller 0 detecting irqs with mask 0xdeb8: none
pcic0: no available irq; polling for socket events
IPsec: Initialized Security Association Processing.
pcic_chip_socket_enable: status 8c
pcic_wait_ready: ready never happened, status = 8c

	..the system then hangs.  A kernel without the uhci
	configured in proceeds with:

root device: tlp0
dump device: 
file system (default generic): 
root on tlp0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP next-server:
nfs_boot: my_addr=
nfs_boot: my_mask=
nfs_boot: gateway=
root on
WARNING: clock gained 6577 days -- CHECK AND RESET THE DATE!
root file system type: nfs

	The "WARNING: Bus error" message is printed by the
	P-5064 error interrupt handler.  It seems as if
	a bogus DMA address is being fed to the uhci controller.

	Note that DMA for SCSI and Ethernet work fine (while there
	are no devices currently plugged into the SCSI controller,
	it has generated several `command complete' interrupts).

	Try using uhci on a P-5064.

	Not known.