[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#422675: marked as done (sis900: tons of corrupted packets are reported)

Your message dated Sun, 26 Jul 2009 11:48:50 +0200
with message-id <20090726094850.GA2922@galadriel.inutil.org>
and subject line Re: Bug still occurs in 2.6.26
has caused the Debian Bug report #422675,
regarding sis900: tons of corrupted packets are reported
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
422675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422675
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-4-k7
Version: 2.6.18.dfsg.1-12etch1
Severity: normal


While tracking down some rsync trouble I found this error/waring
message appears 4-5 times every second:

May  6 06:28:28 vargas kernel: eth0: Corrupted packet received, buffer status = 0x908401b8/440.
May  6 06:28:28 vargas kernel: eth0: Corrupted packet received, buffer status = 0x90880187/391.
May  6 06:28:28 vargas kernel: eth0: Corrupted packet received, buffer status = 0x90840143/323.
May  6 06:28:28 vargas kernel: eth0: Corrupted packet received, buffer status = 0x90880134/308.
May  6 06:28:28 vargas kernel: eth0: Corrupted packet received, buffer status = 0x9084019e/414.

As you see the numbers at the end vary, but I see no close relation to
the amount of traffic trough the interface. If it is related to my
network problem isn't sure yet, but it creates 18MB of logfile a day.

I had no such messages with it previous kernel version (before the
latest security update).

The NIC is reported to be a 
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
the mii module is loaded aswell.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)

Versions of packages linux-image-2.6.18-4-k7 depends on:
ii  coreutils                     5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0]         1.5.11     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85g      tools for generating an initramfs
ii  module-init-tools             3.3-pre4-2 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-4-k7 recommends:
ii  libc6-i686                  2.3.6.ds1-13 GNU C Library: Shared libraries [i

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
On Sun, Dec 07, 2008 at 05:28:52PM +0100, Moritz Muehlenhoff wrote:
> On Sun, Nov 30, 2008 at 05:51:09PM +0000, Chris Carr wrote:
> > I have recently found this problem on an old socket 7 machine with an  
> > SiS900 network card. The lspci output for the card is
> >
> > 00:0b.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI  
> > Fast Ethernet (rev 02)
> >
> > The motherboard is a PC Chips (Hsin Tech) M537DMA33:
> >
> > http://www.users.zetnet.co.uk/thorfin/motherboards/mb01/motherboard_1.htm
> >
> > Kernel is 2.6.26 from the Lenny RC1 installer.
> >
> > I'm afraid I don't know how to troubleshoot this bug. For example,  
> > earlier messages mention setting the card to half-duplex mode - should I  
> > try that, and if so how is it done?
> 
> You can use "mii-tools -F" from net-tools for that.
> 
> Could you try to reproduce this with a current 2.6.28-rcX kernel (you can use the Debian
> config from /boot/config* ) and file a bug at bugzilla.kernel.org if the problem
> persists?

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz

--- End Message ---
Reply to: