linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kilobug@freesurf.fr (Gaël Le Mignot)
To: linux-kernel@vger.kernel.org
Cc: ollie@sis.com.tw
Subject: [BUG] 2.6.0-t1 sis900 timeout
Date: Sun, 03 Aug 2003 12:21:35 +0200	[thread overview]
Message-ID: <plopm3smoj11ow.fsf@drizzt.kilobug.org> (raw)


Hello,

I'm  running 2.6.0-test1-ac3  on my  sis-based laptop,  and  I've some
problems with  the sis  900 networking card:  in a  low-bandwith usage
(like a ssh to another computer,  or a copy from another computer with
a 10Mbps card), I get some network freezes, and after a few seconds it
starts again (with the following messages in the syslog):

Aug  3 11:55:13 kesto kernel: eth0: Media Link Off
Aug  3 11:55:22 kesto kernel: NETDEV WATCHDOG: eth0: transmit timed out
Aug  3 11:55:22 kesto kernel: eth0: Transmit timeout, status 00000004 00000000 
Aug  3 11:55:23 kesto kernel: eth0: Media Link On 100mbps full-duplex 

When I  copy files  to another 100  Mbps laptop (with  a cross-cable),
after a short while the network  stops completly to work, and I cannot
even rmmod sis900 (device or ressource busy).

If you want the /proc/pci entry for the network card:

  Bus  0, device   1, function  1:
    Ethernet controller: Silicon Integrated S SiS900 10/100 Ethern (rev 130).
      IRQ 10.
      Master Capable.  Latency=128.  Min Gnt=52.Max Lat=11.
      I/O at 0x3200 [0x32ff].
      Non-prefetchable 32 bit memory at 0x44000000 [0x44000fff].

I've enabled preempt and local  APIC in my kernel configuration, but I
used to patch my 2.4 kernels  with preempt before switching to 2.6 and
I never had any network-related problem.

As a side-node,  I can tell you  that when we (a friend  and I) ported
the sis900  driver to GNU Mach,  we had to  add a delay loop  (I know,
it's ugly, but it's just a quick-and-dirty patch while waiting for the
OSKit-based GNU Mach) in the sis900_start_xmit function. With no delay
at  all  the  driver  stopped  to  work  after  one  packet  has  been
transmitted, with  a small delay  it worked for  low-bandwidth program
(say, a "ping 192.168.1.1") but not for a file transfert, I had to add
a bigger one to make it work fine.

I'm available if you need additional informations.

-- 
Gael Le Mignot "Kilobug" - kilobug@nerim.net - http://kilobug.free.fr
GSM         : 06.71.47.18.22 (in France)   ICQ UIN   : 7299959
Fingerprint : 1F2C 9804 7505 79DF 95E6 7323 B66B F67B 7103 C5DA

Member of HurdFr: http://hurdfr.org - The GNU Hurd: http://hurd.gnu.org

             reply	other threads:[~2003-08-03 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03 10:21 Gaël Le Mignot [this message]
2003-08-04  8:10 [BUG] 2.6.0-t1 sis900 timeout Daniel Blueman
2003-08-04 10:06 ` K.M. Liu
2003-08-09 11:47 ` Gaël Le Mignot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=plopm3smoj11ow.fsf@drizzt.kilobug.org \
    --to=kilobug@freesurf.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ollie@sis.com.tw \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).