Date: Fri, 5 Aug 2005 19:27:32 +0200 From: "Simon L. Nielsen" <simon@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-current@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: Locking fixes for dc(4): please test! Message-ID: <20050805172732.GD857@zaphod.nitro.dk> In-Reply-To: <200508051040.05333.jhb@FreeBSD.org> References: <200508041255.05839.jhb@FreeBSD.org> <20050804212718.GD852@zaphod.nitro.dk> <200508051040.05333.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--aVD9QWMuhilNxW9f Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2005.08.05 10:40:03 -0400, John Baldwin wrote: > 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 th= em > > > 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 addre= ss: > > 00:40:f4:36:4e:e7 > > dc0: if_start running deferred for Giant > > dc0: [GIANT-LOCKED] >=20 > Ok. Try changing the IS_MPSAFE at around line 348 flag from 0 to 1 and s= ee if=20 > it blows up then. :) Thanks for testing. Also works fine, and the two last lines are gone from dmesg. BTW. this is on i386 UP. --=20 Simon L. Nielsen --aVD9QWMuhilNxW9f Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC86GEh9pcDSc1mlERAt7oAKCnFnaUAMPwGDgNkbBFfDDNtwLYVwCcDWRb HX1pWSGY8055zwkBVzlA+kM= =hajY -----END PGP SIGNATURE----- --aVD9QWMuhilNxW9f--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050805172732.GD857>