mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@freenet.de>
To: Stephen R Smoot <smoot@alum.mit.edu>
Cc: Kernel-Mailingliste <linux-kernel@vger.kernel.org>
Subject: Re: Ongoing problems with sis900.c in 2.4.20pre11
Date: Tue, 28 Jan 2003 18:41:38 +0100	[thread overview]
Message-ID: <3E36C0D2.1080302@athlon.maya.org> (raw)
In-Reply-To: <1157976531.20030127174314@alum.mit.edu>

Hi Stephen,

Stephen R Smoot wrote:
> Hi,
>   You posted a message about a SiS900 problem (see below if you don't
>   recall).  I think I may be seeing the same thing in 2.4.19.  Do you
>   know in what kernel it works?

I don't know any kernel which resolved this problem. Since I posted this 
message in the lkml, I got about 4 questions like yours - and I have to 
tell always the same.
I think there is no interest to fix this problem :-( - or I didn't see the 
fix.


Regards,
Andreas Hartmann



> Ongoing problems with sis900.c in 2.4.20pre11
> From: Andreas Hartmann (andihartmann@freenet.de)
> Date: Thu Oct 24 2002 - 12:53:06 EST 
> 
> Hello all, 
> 
> 
> though the new bug fix for Tx timeout from Mufasa Yang in Rev 1.08.06, the 
> problem is not fixed at all. The problem appeares now not quite often as 
> before. 
> 
> 
> 
> I can find the following logentries in /var/log/messages: 
> 
> 
> Oct 24 19:40:25 susi kernel: eth0: Media Link Off 
> Oct 24 19:40:35 susi kernel: eth0: Media Link On 100mbps full-duplex 
> Oct 24 19:40:36 susi kernel: eth0: Media Link Off 
> Oct 24 19:40:46 susi kernel: eth0: Media Link On 100mbps full-duplex 
> Oct 24 19:40:47 susi kernel: eth0: Media Link Off 
> Oct 24 19:40:57 susi kernel: eth0: Media Link On 100mbps full-duplex 
> Oct 24 19:40:58 susi kernel: eth0: Media Link Off 
> Oct 24 19:41:07 susi kernel: NETDEV WATCHDOG: eth0: transmit timed out 
> Oct 24 19:41:07 susi kernel: eth0: Transmit timeout, status 00000004 
> 00000000 
> Oct 24 19:41:08 susi kernel: eth0: Media Link On 100mbps full-duplex 
> Oct 24 19:41:09 susi kernel: eth0: Media Link Off 
> Oct 24 19:41:18 susi kernel: NETDEV WATCHDOG: eth0: transmit timed out 
> Oct 24 19:41:18 susi kernel: eth0: Transmit timeout, status 00000004 
> 00000040 
> Oct 24 19:41:19 susi kernel: eth0: Media Link On 100mbps full-duplex 
> Oct 24 19:41:20 susi kernel: eth0: Media Link Off 
> Oct 24 19:41:30 susi kernel: eth0: Media Link On 100mbps full-duplex 
> 
> 
> 
> The problem occures between two sis900-cards (see lspci). You can fix it by 
> restarting the network on one of the two machines (including rmmod sis900). 
> 
> 
> 
> 00:00.0 Host bridge: Acer Laboratories Inc. [ALi] M1541 (rev 04) 
>         Subsystem: Acer Laboratories Inc. [ALi] ALI M1541 Aladdin V/V+ AGP 
> System Controller 
>         Flags: bus master, slow devsel, latency 64 
>         Memory at e6000000 (32-bit, non-prefetchable) [size=16M] 
>         Capabilities: [b0] AGP version 1.0 
> 
> 
> 00:01.0 PCI bridge: Acer Laboratories Inc. [ALi] M5243 (rev 04) (prog-if 00 
> [Normal decode]) 
>         Flags: bus master, slow devsel, latency 64 
>         Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 
>         I/O behind bridge: 0000d000-0000dfff 
>         Memory behind bridge: e4800000-e5ffffff 
>         Prefetchable memory behind bridge: e7f00000-e7ffffff 
> 
> 
> 00:03.0 Bridge: Acer Laboratories Inc. [ALi] M7101 PMU 
>         Subsystem: Acer Laboratories Inc. [ALi] ALI M7101 Power Management 
> Controller 
>         Flags: medium devsel 
> 
> 
> 00:07.0 ISA bridge: Acer Laboratories Inc. [ALi] M1533 PCI to ISA Bridge 
> [Aladdin IV] (rev c3) 
>         Flags: bus master, medium devsel, latency 0 
> 
> 
> 00:0a.0 Multimedia audio controller: Xilinx, Inc. RME Digi96 
>         Flags: slow devsel, IRQ 12 
>         Memory at e3000000 (32-bit, non-prefetchable) [size=16M] 
> 
> 
> 00:0b.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 
> Ethernet (rev 02) 
>         Subsystem: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet 
> Adapter 
>         Flags: bus master, medium devsel, latency 32, IRQ 10 
>         I/O ports at b800 [size=256] 
>         Memory at e2800000 (32-bit, non-prefetchable) [size=4K] 
>         Expansion ROM at <unassigned> [disabled] [size=128K] 
>         Capabilities: [40] Power Management version 1 
> 
> 
> 00:0f.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev c1) 
> (prog-if 8a [Master SecP PriP]) 
>         Flags: bus master, medium devsel, latency 32 
>         I/O ports at b400 [size=16] 
> 
> 
> 01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP 
> 1X/2X (rev 5c) (prog-if 00 [VGA]) 
>         Subsystem: ATI Technologies Inc: Unknown device 0084 
>         Flags: bus master, stepping, medium devsel, latency 64, IRQ 11 
>         Memory at e5000000 (32-bit, non-prefetchable) [size=16M] 
>         I/O ports at d800 [size=256] 
>         Memory at e4800000 (32-bit, non-prefetchable) [size=4K] 
>         Expansion ROM at e7fe0000 [disabled] [size=128K] 
>         Capabilities: [50] AGP version 1.0 
> 
> 
> 
> I would be very happy if this very old problem could be really fixed. 


      parent reply	other threads:[~2003-01-28 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24 17:53 Andreas Hartmann
     [not found] ` <1157976531.20030127174314@alum.mit.edu>
2003-01-28 17:41   ` Andreas Hartmann [this message]

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=3E36C0D2.1080302@athlon.maya.org \
    --to=andihartmann@freenet.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smoot@alum.mit.edu \
    /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

Powered by JetHome