On Tue, 21 Jan 2003, Jacques A. Vidrine wrote:
> Looooong, loooong ago, someone reported a dc driver bug. However,
> a couple of us have tried and failed to reproduce the problem. I
> thought I'd bounce the issue here before completely forgetting about
> it.
I'm not seeing it on 4.5. MBUF exhaustion: yes, lockup: no.
( From a different machine)
[10:51pm] jeff@snip (~) # sudo ping -f -s 50000 snip
Password:
PING snip (snip): 50000 data bytes
....................................................
....................................................
....................................................
....................................................
....................................................
^C
(On the 4.5 machine)
[10:52pm] jeff@snip (~) # ifconfig dc0
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet snip netmask 0xfffff800 broadcast snip.255
ether 00:a0:cc:37:50:fa
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
[10:52pm] jeff@snip (~) # uname -a
FreeBSD snip 4.5-RELEASE-p1 FreeBSD 4.5-RELEASE-p1 #0: Fri Mar
1 15:09:01 GMT 2002
jeff@snip:/usr/src/sys/compile/snip_4_5 i386
[10:52pm] jeff@snip (~) dmesg -a | tail
m_clalloc failed, consider increase NMBCLUSTERS value
m_clalloc failed, consider increase NMBCLUSTERS value
m_clalloc failed, consider increase NMBCLUSTERS value
m_retry failed, consider increase mbuf value
m_clalloc failed, consider increase NMBCLUSTERS value
m_clalloc failed, consider increase NMBCLUSTERS value
m_clalloc failed, consider increase NMBCLUSTERS value
m_clalloc failed, consider increase NMBCLUSTERS value
m_retry failed, consider increase mbuf value
m_retryhdr failed, consider increase mbuf value
The system does drop icmp echo requests, if that matters.
- Jeff
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
