On 12/08/15 12:22, Steven Chamberlain wrote:
David Gwynne wrote:
On 8 Dec 2015, at 10:17, Steven Chamberlain <[email protected]> wrote:
I'll try again with latest -CURRENT in light of these recent commits:
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/sparc64/dev/vnet.c.diff?r1=1.51&r2=1.52&f=h
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/sparc64/dev/vnet.c.diff?r1=1.52&r2=1.53&f=h

thats a network driver for "hardware" you dont have on an x1.

OK thanks.

I wonder, exactly which pools does dc(4) use?  As with previous crashes,
dma512 had Pgreq=1, Pgrel=1 meaning it was empty at the time, and had
already been freed.

dc uses the mbuf pools. the dma512 use comes from an ata driver from what i can 
tell.

I believe the problematic pool is in the range of 224<size<=512, so
I'll try to test with the in-page header threshold set to 256<size.
That could rule out pools of 256<size<=512 as being the cause of this.

maybe i should try and get an x1 to reproduce this with.

Last I checked, the Netra X1 is quite rare, the Fire V100 is easier to
find and has a CD-ROM drive making installation much simpler.  In mine,
I swapped the IDE disk for CompactFlash cards with an adapter.

A question for Fred perhaps -- does the Netra T1 105 also use dc(4)
ethernet?  Do you know if it's affected by this bug?

Thanks,
Regards,


Hi,

My V100 has two inbuilt dc's:

mainbus0 at root: Sun Fire V100 (UltraSPARC-IIe 500MHz)
dc0 at pci0 dev 12 function 0 "Davicom DM9102" rev 0x31: ivec 0x7c6, address 00:03:ba:13:a8:c7
amphy0 at dc0 phy 1: DM9102 10/100 PHY, rev. 0
dc1 at pci0 dev 5 function 0 "Davicom DM9102" rev 0x31: ivec 0x7dc, address 00:03:ba:13:a8:c8

Currently my Netra T1 105 is failing to boot - so it might finally be headed for the tip, not sure what the nic is though...

I've been trying to build a debug kernel on my V100 with David's patch as well but I've not managed that yet - but running with a kernel with David's patch has been stable - without the patch the kernel panics with the old: psycho0: uncorrectable DMA error AFAR 663f8250 (pa=0 tte=0/60a08012) AFSR 410000ff40800000

Cheers

Fred



Reply via email to