Date: Tue, 16 Aug 2005 10:11:49 -0400 From: Viren Shah <virenshah@gmail.com> To: Giorgos Keramidas <keramida@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: if_dc panics with 3Com OfficeConnect 10/100B PCI Message-ID: <6f230735050816071119a68618@mail.gmail.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
On 8/16/05, Giorgos Keramidas <keramida@freebsd.org> wrote:
<snip>
> 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?
I'm running a -current kernel from today morning just fine.
bandersnatch# ifconfig dc0
dc0: flags=108843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
options=8<VLAN_MTU>
inet6 fe80::210:a4ff:fe7b:e2f4%dc0 prefixlen 64 scopeid 0x3
inet 192.168.2.127 netmask 0xffffff00 broadcast 192.168.2.255
ether 00:10:a4:7b:e2:f4
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
FreeBSD bandersnatch.virtc.com 7.0-CURRENT FreeBSD 7.0-CURRENT #6: Tue
Aug 16 06:23:46 EDT 2005
root@bandersnatch.virtc.com:/usr/obj/usr/src/sys/BANDERSNATCH i386
The dc driver is compiled into the kernel
Viren
> - Giorgos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6f230735050816071119a68618>