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.
Cheers, -- Jacques A. Vidrine <[EMAIL PROTECTED]> http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] ----- Forwarded message from Alex <[EMAIL PROTECTED]> ----- Date: Mon, 01 Jul 2002 15:21:16 +0600 From: Alex <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Bug report From: [EMAIL PROTECTED], Alex S. Kabakaev, Tomsk Polytechnic University, Russia To: FreeBSD bug team I got the problem: FreeBSD computers freezes when i "ping -f -s 50000 any.freebsd.box" from linux box. And only reset can help to unfreeze them. There is no errors on screen or in logs. There is a number of tested configurations and realises: FreeBSD 4.4 on: 1. Duron 650, MB=epox(VIA KT133), Network Card=Matronix MX 3191(dc0 kernel module), 10 MBit per second Hub 2. K6-2 333, Mother Board = VIA MVP3, Network Card=Davicom Semiconductor DM9102AM(dc0 kernel module), 10 MBit per second Hub With FreeBSD 4.6 on K6-2 333, Mother Board = VIA MVP3, Network Card=Matronix MX 3191(dc0 kernel module), 10 MBit per second Hub And Any time i ping with flood and packet size >=30000 all this configurations get freeze. IMHO there is a bug with "dc0" kernel module. To make sure i prodused this test with FreeBSD 4.6 on MB=Lucky Star (VIA 8601T MVP3), integrated network card (Realtek RTL 8139) with another network kernel module. And there was no errors, freezes or bugs. That's why i think it's a bug with "dc" module. Thanks for attention. Mailto: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] ----- End forwarded message ----- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
