if_dc panics with 3Com OfficeConnect 10/100B PCI

[John Baldwin]

On Tuesday 16 August 2005 11:47 am, Giorgos Keramidas wrote:
> On 2005-08-16 09:22, "M. Warner Losh" <imp at bsdimp.com> wrote:
> > In message: <20050816124525.GA31411 at flame.pc>
> >             Giorgos Keramidas <keramida at 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 at 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?
> 
> It's a bit tricky, since I have to either copy it manually from the
> console or find out how I can boot the machine with the NIC in serial
> console mode.
> 
> Booting with 'dc' compiled into the kernel doens't quite work, since the
> panic happens too early for dumpdev to be set.  If there a way to set
> dumpdev earlier than /etc/rc.conf (i.e. from the boot loader)?
> 
> Using a module doesn't really help with obtaining a trace, because the
> symbols of the module are printed as ??? in kgdb.
> 
> I'll try to obtain a trace later tonight though.  Thanks for the reply :)

Compile in DDB and get a stack trace over the serial console using 't' in DDB 
instead of worrying about getting a dump.

-- 
John Baldwin <jhb at FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org