Date: 27 May 1998 08:31:54 +0200 From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) To: net@FreeBSD.ORG Subject: ep0 problems: shed some light? Message-ID: <xzpiumsgr6t.fsf@nastrond.ifi.uio.no>
next in thread | raw e-mail | index | archive | help
OK, I have begun to have problems with my ep0 getting stuck again, despite setting NMBCLUSTERS to 8192. I believe I have gotten a little bit closer to tracking down the bug. First, it is not mbuf-related. Although augmenting the number of mbufs seems to help, it can't be much more than an interesting side-effect. mbuf usage on my box never even reached 250 from my last reboot a couple of days ago till the interface got stuck last night. Second, it seems that 'ifconfig ep0 up' alone is enough to unstick the interface (which is good news, because 'ifconfig ep0 down' zaps my NFS connections). Third, 'ifconfig -au' before 'ifconfig ep0 up' reveals that ep0 is stuck with the OACTIVE bit on. Although 'ifconfig ep0 up' should theoretically be a no-op since ep0 is already up, it apparently clears the OACTIVE flag, which unsticks the interface. Fourth, the bug always manifests itself *between* two large NFS transfers. The only other machine on that physical network is a scratch box which does nothing but play MP3 files over NFS. The point at which the interface gets stuck (on the server, never on the client) is at the beginning of an MP3 file (16 frames into the file, to be precise). Does anyone feel like diving into the ep0 code to try to find out why the OACTIVE flag gets stuck? I would, but I have an exam in half an hour :) -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpiumsgr6t.fsf>