Date: Tue, 16 Aug 2005 17:21:41 +0300 From: Giorgos Keramidas <keramida@freebsd.org> To: Viren Shah <virenshah@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: if_dc panics with 3Com OfficeConnect 10/100B PCI Message-ID: <20050816142141.GK31411@flame.pc> In-Reply-To: <6f230735050816071119a68618@mail.gmail.com> References: <20050816124525.GA31411@flame.pc> <6f230735050816071119a68618@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-08-16 10:11, Viren Shah <virenshah@gmail.com> wrote: >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. Cool. Thanks for the reply. I'll try to obtain a kernel backtrace, since this seems to be broken on my setup in both in-kernel and module cases.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050816142141.GK31411>