Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Aug 2005 10:40:03 -0400
From:      John Baldwin <jhb@FreeBSD.org>
To:        freebsd-alpha@freebsd.org
Cc:        alpha@freebsd.org, current@freebsd.org, "Simon L. Nielsen" <simon@freebsd.org>
Subject:   Re: Locking fixes for dc(4): please test!
Message-ID:  <200508051040.05333.jhb@FreeBSD.org>
In-Reply-To: <20050804212718.GD852@zaphod.nitro.dk>
References:  <200508041255.05839.jhb@FreeBSD.org> <20050804212718.GD852@zaphod.nitro.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 04 August 2005 05:27 pm, Simon L. Nielsen wrote:
> On 2005.08.04 12:55:05 -0400, John Baldwin wrote:
> > I have some fixes for the locking in the dc(4) driver, please test them
> > if you have some dc(4) hardware, thanks!
> >
> > http://www.FreeBSD.org/~jhb/patches/dc_locking.patch
>
> It hasn't blown up yet with:
>
> dc0: <Intel 21143 10/100BaseTX> port 0xec00-0xec7f mem
> 0xeb104000-0xeb1043ff irq 15 at device 20.0 on pci0 dc0: Ethernet address:
> 00:40:f4:36:4e:e7
> dc0: if_start running deferred for Giant
> dc0: [GIANT-LOCKED]

Ok.  Try changing the IS_MPSAFE at around line 348 flag from 0 to 1 and see if 
it blows up then. :)  Thanks for testing.

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



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