Date: Thu, 15 Oct 2009 21:24:52 -0400 From: Glen Barber <glen.j.barber@gmail.com> To: Weongyo Jeong <weongyo@freebsd.org>, freebsd-current@freebsd.org Subject: Re: if_rum dies on transmit... Message-ID: <4ad871310910151824q13842e1en53a3a682f85c1dd8@mail.gmail.com> In-Reply-To: <20091015172914.GF67082@weongyo> References: <86051.1254232666@critter.freebsd.dk> <20091013174201.GC67082@weongyo> <86iqei7tgq.fsf@jodie.vectavision.com> <20091014201059.GE67082@weongyo> <20091014230715.E96894@ury.york.ac.uk> <20091015172914.GF67082@weongyo>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On Thu, Oct 15, 2009 at 1:29 PM, Weongyo Jeong <weongyo.jeong@gmail.com> wr= ote: [snip] >> Do you know if this patch is likely to fix the panics seen with rum(4) o= r >> is this likely to only fix the TX hangs? > > AFAIK this patch only fixes TX hangs. =A0I didn't see PRs yet related wit= h > the panics but I think it could affect user's panic a little bit. > I applied this patch to -STABLE and it seems to have fixed my panic problems with rum(4). So far, 1+ hour uptime on AC power and 20+ minutes on battery, which is unusual. rum(4) was one of the potential culprits I was trying to isolate. Thank you! FreeBSD pegasus 8.0-RC1 FreeBSD 8.0-RC1 #8 r198161M: Thu Oct 15 20:09:20 EDT 2009 root@pegasus:/usr/obj/usr/src/sys/PEGASUS i386 --=20 Glen Barber
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ad871310910151824q13842e1en53a3a682f85c1dd8>