Date: Sat, 31 Dec 2011 13:36:48 +0100 From: Stefan Bethke <stb@lassitu.de> To: freebsd-mips@freebsd.org Cc: Aleksandr Rybalko <ray@ddteam.net> Subject: Re: arge problem on MR3420 Message-ID: <2A05E0AA-5AA5-47FD-90EA-BD6B23A01EFE@lassitu.de> In-Reply-To: <98BA8EF5-E808-43F8-92A8-68B14CAF998F@lassitu.de> References: <B40E8E4D-115F-46EF-A51F-52E562EF166E@lassitu.de> <CAJ-VmokWLzfjd%2B=_=tSt7ukc=gK2kd9H5s7sH-7bbzSpzBFUcQ@mail.gmail.com> <20111231000638.d257448c.ray@ddteam.net> <98BA8EF5-E808-43F8-92A8-68B14CAF998F@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 30.12.2011 um 23:49 schrieb Stefan Bethke: > OK, trying to pull in everyone. There seems to be a problem with = if_arge on certain chips/platforms. I've encountered it on TL-MR3420 = and WRT-160NL. I'm currently working off Adrians gitorious repo. The problem is limited to BOOTP; if I mount a USB stick as root, I can = bring up arge1 without issue. On the AR7241, arge0 is connected to a phy and the blue WAN port, arge1 = is connected to the built-in switch. The port speeds are fixed (1000 = for the switch, 100 for the phy). With BOOTP enabled, I'm getting an interrupt storm on intr 3. I've = enabled debugging for arge, and it seems there is a TX underrun that is = not being cleared in that case. I'm not fully understanding the code, = so I'm not sure why the TX underrun is not being cleared, or keeps = reoccurring. Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2A05E0AA-5AA5-47FD-90EA-BD6B23A01EFE>