Date: Thu, 27 Jul 2006 21:08:07 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Jeremie Le Hen <jeremie@le-hen.org> Cc: freebsd-current@freebsd.org, Jack Vogel <jfvogel@gmail.com> Subject: Re: [fbsd] Re: em(4) watchdog timeout Message-ID: <20060727120807.GB19286@cdnetworks.co.kr> In-Reply-To: <20060727115727.GD1458@obiwan.tataz.chchile.org> References: <20060721123448.GV6253@obiwan.tataz.chchile.org> <2a41acea0607210927s108d1326qdad02b7d29376a09@mail.gmail.com> <20060725123603.GH6253@obiwan.tataz.chchile.org> <20060727005326.GA19286@cdnetworks.co.kr> <20060727115727.GD1458@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 27, 2006 at 01:57:27PM +0200, Jeremie Le Hen wrote: > Hi Pyun, > > On Thu, Jul 27, 2006 at 09:53:27AM +0900, Pyun YongHyeon wrote: > > I think the debug_info is useless as it's the output after > > hardware reset. Would you try latest em(4) in CURRENT? > > I've fixed a DMA related bug. Not sure it helps. > > I am now running with a very recent -CURRENT from 2006.07.22.08.00.00, > is it enough ? From CVSweb, it seems the lastest change dates from > 2006.07.20, if_em.h rev 1.45. > You need if_em.c rev 1.120 or higher to verify it. > My box has been running for nearly two days, and I saw no em(4) watchdog > timeout so far. I am going to run some heavy computanional workload > this afternoon, trying to trigger it. Note that I have switched to > davidxu's SCHED_CORE during my latest upgrade, it may hide the bug. > If I can't trigger any watchdog timeout with it, I will back to > SCHED_4BSD. -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060727120807.GB19286>