Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Sep 2008 20:19:47 -0400
From:      Sean Thomas Caron <scaron@umich.edu>
To:        freebsd-sparc64@freebsd.org
Subject:   Kernel panic in 7.0-RELEASE with fatm driver
Message-ID:  <20080929201947.86701vp3bs8vcatc@web.mail.umich.edu>

next in thread | raw e-mail | index | archive | help
Hi folks,

I've been running FreeBSD 6.x on a number of Ultrasparc based systems =20
using the Cranor NATM driver with a bunch of Fore PCA-200E cards. It =20
generally worked but as the machines got hit with higher and higher =20
network load I would get kernel panics at fairly random intervals on =20
"sbdrop" and "sbflush". Sometimes I would get two per day, sometimes I =20
wouldn't get any for two weeks.

So after a while at this I decided to try 7.0-RELEASE out hoping =20
whatever bug was causing these random kernel panics might have gotten =20
fixed.

Test system is Sun Fire v120, 550 MHz, 1 GB RAM, PCA-200e installed in =20
PCI slot.

I pruned a bunch of stuff from GENERIC and added the usual Cranor NATM =20
stuff that I was using in 6.x. In particular -

# ATM

options         NATM
device          atm
device          fatm
device          utopia

Kernel does have multiprocessing enabled (as GENERIC did) even though =20
it's a uniprocessor machine.

I built the new kernel then reboot and it panics immediately after =20
touching the ATM card -

fatm0: <FORE PCA200E> mem 0x200000-0x3fffff at device 5.0 on pci2
panic: bus_dma_tag_create: parent DMA tag NULL
cpuid =3D 0
Uptime: 1s
Automatic reboot in 15 seconds - press a key on the console to abort
--> Press a key on the console to reboot,
--> or switch off the system now.

I'm hoping maybe someone has seen this before and has a patch laying =20
around somewhere, or if nothing else, it might get passed along to the =20
fatm maintainer eventually?

If anyone wants to see any further information e.g. full kernel =20
configuration file, I will be happy to pass along. I can also procure =20
a backtrace if someone can tell me how to hardcode a dump path into =20
the kernel; I can't find a procedure documented anywhere.

Thanks!

-Sean



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080929201947.86701vp3bs8vcatc>