Date: Tue, 16 Aug 2005 09:22:35 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: keramida@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: if_dc panics with 3Com OfficeConnect 10/100B PCI Message-ID: <20050816.092235.16452975.imp@bsdimp.com> In-Reply-To: <20050816124525.GA31411@flame.pc> References: <20050816124525.GA31411@flame.pc>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20050816124525.GA31411@flame.pc>
Giorgos Keramidas <keramida@freebsd.org> writes:
: I've recently acquired a 3Com 3CSOHO100B-TX NIC, which seems to be supported
: by the ``dc'' driver. The output of pciconf is:
:
: % none0@pci0:10:0: class=0x020000 card=0x930010b7 chip=0x930010b7 rev=0x31 hdr=0x00
: % vendor = '3COM Corp, Networking Division'
: % device = '3C910 Integrated Fast Ethernet Controller (3CSOHO100B-TX Compatible)'
: % class = network
: % subclass = ethernet
:
: When I compile the ``dc'' driver into my kernel or load it as a module
: though, a relatively recent CURRENT (updated yesterday, 14 Aug 2005)
: panics after a port mapping failure.
:
: The same panic happens when the device is configured into the kernel or
: when I kldload if_dc. Is anyone else using ``dc'' interfaces on CURRENT
: and seeing similar problems?
Trace?
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050816.092235.16452975.imp>