--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: sis190: SiS 191 NIC fails when sending or recieving packets above 1496 bytes.
- From: AC <acooley82@yahoo.com>
- Date: Sat, 14 Apr 2012 11:07:42 +0200
- Message-id: <20120414090742.1975.45435.reportbug@Athena>
Package: sis190
Version: 1.4
Severity: important
SiS 191 NIC fails when sending or recieveing packets
above 1496 bytes. System is a Asus X59SR laptop.
Problem was first encountered when trying to install
from CD (debian-6.0.4-amd64-netinst). Install failed
to connect to mirrors.
Typing "wget http://www.google.com"; into console
downloaded index.html file so network appeared to
be working. Attempting to download larger files
failed.
Typing "ip link set eth0 mtu 1492" into console allowed
install to connect to mirrors and complete.
Problem persisted once system restarted, typing
"ifconfig eth0 mtu 1492" allowed system to run
"apt-get update" without failing. Further testing
showed MTU could be set up to 1496 before failing.
Experiments with the ping command resluted in the following:
$ping 192.168.0.1 -s 1468
PING 192.168.0.1 (192.168.0.1) 1468(1496) bytes of data.
1476 bytes from 192.168.0.1: icmp_req=1 ttl=64 time=2.77 ms
1476 bytes from 192.168.0.1: icmp_req=2 ttl=64 time=0.889 ms
^C
--- 192.168.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.889/1.832/2.776/0.944 ms
$ping 192.168.0.1 -s 1469
PING 192.168.0.1 (192.168.0.1) 1469(1497) bytes of data.
^C
--- 192.168.0.1 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms
Pinging various devices on the network from my main
Windows 7 machine resulted in correct behavior from
all machines (including a Windows 98 box) even when
"ping 192.168.0.1 -l 65500". The only system that
failed was the Laptop running Debian.
Tcpdump showed correct incoming when packet sizes
where small, but showed nothing at all when they where
larger. They simply didn't show up at all.
The only indication that anything was actually happening
was that "ifconfig eth0" showed increments in RX errors.
In a attempt to fix the problem, I downloaded the
latest kernel from kernel.org (3.3.1 at the time,
3.3.2 came out yesterday and I haven't tested it yet).
Regrettably the problem persists.
Although setting MTU is a workaround, the system is
not behaving as it should and can not be considered
reliable as things are.
-- System Information:
Debian Release: 6.0.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.3.1 (SMP w/2 CPU cores)
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---