From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mourad De Clerck Subject: r8169: freeze at high speeds Date: Fri, 09 Jun 2006 18:03:34 +0200 Message-ID: <44899BD6.20809@aquazul.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_hell-19534-1149869063-0001-2" Return-path: Received: from www.ypu.org ([80.242.208.21]:9186 "EHLO heaven.risen.be") by vger.kernel.org with ESMTP id S1030254AbWFIQDn (ORCPT ); Fri, 9 Jun 2006 12:03:43 -0400 To: netdev@vger.kernel.org Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. --=_hell-19534-1149869063-0001-2 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Hello, I have a problem where my machine freezes as soon as I send it data at high speeds. It works perfectly fine when transferring files slowly (over the internet for instance). But after sending some data for a few seconds at relatively high speed (let's say >10MB/sec), the whole machine just freezes. I've had it happen at relatively low speeds too (1MB/sec), but it's much less frequent. When I stick to really slow speeds, I can work without problems for days. I'm using the latest Debian kernel, which is based on 2.6.16.17 at the moment. btw: I tried using ethtool to force it on 100Mbit, but it seems to have little effect (it stays put on 1000Mbit). Autonegotiation stays "on" even after trying to switch it off manually. The machine is a nforce2-based k7 (no SMP). One possibly weird thing is that my SATA controller and my RT8169 are both on the same PCI card (behind a PCI bridge) - lspci is attached. I tried the patch that Francois Romieu posted on 2006-04-18, but it still locks up. I also tried the r1000 driver from Realtek themselves, but that one locks up too. btw2: I do often use nvidia's binary driver, but I made sure it had never been loaded when testing (fresh reboot, without nvidia.ko ever being loaded). Is this a known issue? Can I do anything to track down this bug? Thank you, -- Mourad DC --=_hell-19534-1149869063-0001-2 Content-Type: text/plain; name="lspci.txt"; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="lspci.txt" 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) (prog-if 8a [Master SecP PriP]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Unknown device f541 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- 01:06.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 15) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Bridge: PM- B3+ Capabilities: [90] #06 [0000] Capabilities: [a0] Vital Product Data 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) Subsystem: AFAVLAB Technology Inc Unknown device 8169 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR-