amd64/62753: txp(4) panics on amd4

[Mikhail Teterin]

>Number:         62753
>Category:       amd64
>Synopsis:       txp(4) panics on amd4
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 12 13:40:17 PST 2004
>Closed-Date:
>Last-Modified:
>Originator:     Mikhail Teterin
>Release:        FreeBSD 5.2.1-RC amd64
>Organization:
Virtual Estates, Inc.
>Environment:
System: FreeBSD pollux 5.2.1-RC FreeBSD 5.2.1-RC #0: Sat Jan 31 12:38:34 GMT 2004 root at ngoc.NUXI.com:/usr/obj/usr/src/sys/GENERIC amd64

>Description:
	Although the txp0 is found and reported at boot time, an attempt
	to ifconfig it causes kernel page fault with txp0 being the "current
	process".

	Manual ifconfig or through dhclient -- does not matter.

	I first observed it while installing the RC and then (after
	installing over a different NIC) confirmed on a functional system.

	Here it is:

	dmesg:

	txp0: <3Com 3cR990-TX-95 Etherlink with 3XP Processor> port 0x8080-0x80ff mem 0xff380000-0xff3bffff irq 16 at device 10.0 on pci3
	txp0: Ethernet address 00:01:02:68:53:e7

	ifconfig:

	txp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
		options=13<RXCSUM,TXCSUM,VLAN_HWTAGGING>
		ether 00:01:02:68:53:e7
		media: Ethernet autoselect (100baseTX <full-duplex>)
		status: active

	The card, of course, worked perfectly in a i386 box for years.

>How-To-Repeat:

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