Date: Sun, 17 Feb 2008 15:31:19 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Milan Obuch <freebsd-current@dino.sk> Cc: freebsd-current@freebsd.org Subject: Re: CFT: vr(4) Message-ID: <20080217063119.GA10866@cdnetworks.co.kr> In-Reply-To: <200802161949.02217.freebsd-current@dino.sk> References: <20080204022334.GC27999@cdnetworks.co.kr> <200802051540.01916.freebsd-current@dino.sk> <20080211060915.GI2317@cdnetworks.co.kr> <200802161949.02217.freebsd-current@dino.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 16, 2008 at 07:49:01PM +0100, Milan Obuch wrote: > On Monday 11 February 2008, Pyun YongHyeon wrote: > > On Tue, Feb 05, 2008 at 03:40:01PM +0100, Milan Obuch wrote: > > > On Monday 04 February 2008, Pyun YongHyeon wrote: > > [snip] > > > > > > > Hi, > > > > > > did anybody test Routerboard 44? It is quad network card, uses VT6105M > > > chips as network controller (Via) and PCI6152 as PCI-PCI bridge (PLX > > > Technology). With both stock if_vr and modified from site given above it > > > partially works - interfaces are created, ifconfig works, but even > > > pinging some host in local network (I achieve the effect with ping -f in > > > a minue or so) hangs system. Nothing on my console, nothing in system > > > log. Only hard powerdown restores system in functioning state. > > > > > > I tested it with stock vr driver in both 6 and 7 stable on both i386 and > > > amd64, and now with overhauled vr in 8 freshly cvsupped and two files > > > replaced on i386. > > > > > > If anybody has any idea or some patches I could test, I will. > > > > I have tested 4-port Rhine III(6105LOM) and I never seen this hangs. > > Does this also happen on other network interface too? > > When the system hangs, would you break into DDB and show me > > the output of 'show alllocks' and 'ps'? > > > > I need some tests with another box. I was not able to break into DDB. > Ctrl-Alt-Esc worked until hang. Hang was really hard, Ctrl-Alt-Esc did not > invoke DDB. I do not feel if_vr is culprit here, more probably PCI bus got > somehow locked, but I have no idea how could I test it currently. > Serial console may work better for this situation. In order to rule out vr(4) you may have to try another network card on your box. -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080217063119.GA10866>