From owner-freebsd-bugs Thu Aug 31 0:40: 8 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8D2F337B423 for ; Thu, 31 Aug 2000 00:40:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id AAA23289; Thu, 31 Aug 2000 00:40:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 4F25737B423 for ; Thu, 31 Aug 2000 00:35:45 -0700 (PDT) Received: (qmail 10485 invoked from network); 31 Aug 2000 07:43:08 -0000 Received: from jhs.muc.de (HELO park.jhs.private) (193.149.49.84) by slarti.muc.de with SMTP; 31 Aug 2000 07:43:08 -0000 Received: (from jhs@localhost) by park.jhs.private (8.9.3/8.9.3) id BAA03102; Thu, 31 Aug 2000 01:29:44 GMT (envelope-from jhs) Message-Id: <200008310129.BAA03102@park.jhs.private> Date: Thu, 31 Aug 2000 01:29:44 GMT From: "Julian Stacey" Reply-To: jhs@freebsd.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/20958: ep0 lockup with ifconfig showing OACTIVE Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 20958 >Category: kern >Synopsis: ep0 lockup with ifconfig showing OACTIVE >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Aug 31 00:40:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Julian H. Stacey jhs@freebsd.org >Release: FreeBSD 4.1-RELEASE i386 >Organization: FreeBSD >Environment: >Description: With 4.1 I seem to be able to easily thrash FreeBSD into letting the ep driver interface lock up. Symptom seems to be seeing OACTIVE with ifconfig ep0 I suppose it's maybe swapping to hell, but I've not seen this poor behavious on previous FreeBSD releases with same hardware & similar loads ( It's a little 486 33M laptop with 12M, X11, ether, 1gig of IDE, & a few remote xterms moving trees, nfs heavy ide io etc. ) >How-To-Repeat: Get a slow disc, reduce ram, load & thrash. In case you can't do that, here's my log --- jhs@lapt.jhs.private 4.1-RELEASE csh ttyp2 2 % ping flip PING flip.jhs.private (192.168.91.24): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ^C --- flip.jhs.private ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss jhs@lapt.jhs.private 4.1-RELEASE csh ttyp2 4 % ifconfig -a ep0: flags=8c43 mtu 1500 inet 192.168.91.33 netmask 0xffffff00 broadcast 192.168.91.255 inet6 fe80::220:afff:fe0d:f426%ep0 prefixlen 64 scopeid 0xa ether 00:20:af:0d:f4:26 media: 10base2/BNC supported media: 10base2/BNC 10baseT/UTP 10base5/AUI jhs@lapt.jhs.private 4.1-RELEASE csh ttyp2 6 % su jhs@lapt.jhs.private 4.1-RELEASE csh ttyp2 101 % ifconfig ep0 down jhs@lapt.jhs.private 4.1-RELEASE csh ttyp2 102 % ifconfig ep0 up jhs@lapt.jhs.private 4.1-RELEASE csh ttyp2 103 % ping flip PING flip.jhs.private (192.168.91.24): 56 data bytes 64 bytes from 192.168.91.24: icmp_seq=0 ttl=255 time=0.981 ms 64 bytes from 192.168.91.24: icmp_seq=1 ttl=255 time=0.947 ms ^C --- flip.jhs.private ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.935/0.950/0.981/0.019 ms jhs@lapt.jhs.private 4.1-RELEASE csh ttyp2 104 % ifconfig -a ep0: flags=8843 mtu 1500 inet 192.168.91.33 netmask 0xffffff00 broadcast 192.168.91.255 inet6 fe80::220:afff:fe0d:f426%ep0 prefixlen 64 scopeid 0xa ether 00:20:af:0d:f4:26 media: 10base2/BNC supported media: 10base2/BNC 10baseT/UTP 10base5/AUI jhs@lapt.jhs.private 4.1-RELEASE csh ttyp2 105 % --- >Fix: No idea, but as those kernel developers who likely do have ideas, likely also have newer hardware which maybe wont see this, I jhs@freebsd.org will volunteer to be guinea pig for experiments / diffs to try, if someone suggests diffs or sysctls. I guess maybe some kernel assumptions/constants need to be changed/increased ? An ifconfig down, up resets it temporarily. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message