From: Shane Arnold <clontarf_x@iinet.net.au>
To: linux-kernel@vger.kernel.org
Subject: Bringing up secondary rtl8169-based interface causes network hang/dma issues
Date: Tue, 08 Sep 2009 20:39:06 +0800 [thread overview]
Message-ID: <4AA6506A.7040900@iinet.net.au> (raw)
Also posted at:
http://www.linuxquestions.org/questions/linux-networking-3/rtl8169-hanging-networkdma-issues-on-secondary-interface-ifup-753532/
Hi All,
The issue I am having is when bringing up a second Ethernet interface
that uses the rtl8169 driver, it seems to cause network issues. I lose
all network connectivity to the machine, and I simultaneously see a DMA
error occur for my primary IDE drive.
Two interfaces:
Quote:
eth0 (rtl8168 (using rtl8169 driver) - Onboard PCI-E Gigabit Ethernet)
eth1 (rtl8169 (using rtl8169 driver) - RTL8169 PCI Gigabit Ethernet)
The chipset running the IDE drive that experiences the DMA crash is:
Quote:
ATI Technologies Inc SB700/SB800 IDE Controller (atiixp)
Vitals:
Debian 5.0.1 @ Kernel 2.6.30
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:01.0 PCI bridge: ASUSTeK Computer Inc. Device 9602
00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge
(PCIE port 2)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA
Controller [IDE mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0
Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0
Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2
Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3200
Graphics
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
03:07.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
03:07.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04)
03:07.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
The output from kern.log is as follows (right after bringing the link up)
Sep 8 19:36:42 wdhq kernel: r8169: eth1: link up
Sep 8 19:36:45 wdhq kernel: hda: ide_dma_intr: bad DMA status (0x76)
Sep 8 19:36:45 wdhq kernel: hda: dma_intr: status=0x50 { DriveReady
SeekComplete }
Sep 8 19:36:45 wdhq kernel: hda: possibly failed opcode: 0x35
Sep 8 19:36:45 wdhq kernel: hda: ide_dma_intr: bad DMA status (0x76)
Sep 8 19:36:45 wdhq kernel: hda: dma_intr: status=0x50 { DriveReady
SeekComplete }
Sep 8 19:36:45 wdhq kernel: hda: possibly failed opcode: 0x35
Sep 8 19:36:45 wdhq kernel: hda: ide_dma_intr: bad DMA status (0x76)
Sep 8 19:36:45 wdhq kernel: hda: dma_intr: status=0x50 { DriveReady
SeekComplete }
Sep 8 19:36:45 wdhq kernel: hda: possibly failed opcode: 0x35
Sep 8 19:36:45 wdhq kernel: hda: ide_dma_intr: bad DMA status (0x76)
Sep 8 19:36:45 wdhq kernel: hda: dma_intr: status=0x50 { DriveReady
SeekComplete }
Sep 8 19:36:45 wdhq kernel: hda: possibly failed opcode: 0x35
Sep 8 19:36:46 wdhq kernel: hda: ide_dma_intr: bad DMA status (0x76)
Sep 8 19:36:46 wdhq kernel: hda: dma_intr: status=0x50 { DriveReady
SeekComplete }
Sep 8 19:36:46 wdhq kernel: hda: possibly failed opcode: 0x35
Sep 8 19:36:46 wdhq kernel: hda: DMA disabled
Sep 8 19:36:46 wdhq kernel: hdb: DMA disabled
Sep 8 19:36:46 wdhq kernel: ide0: reset: success
If you guys need any package versions just ask. Also feel free to point
me in the direction of a better place to post this issue.
HELP! I want to be able to multihome but this is stopping me :(
next reply other threads:[~2009-09-08 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 12:39 Shane Arnold [this message]
2009-09-08 17:55 ` Bringing up secondary rtl8169-based interface causes network hang/dma issues Francois Romieu
2009-09-09 18:08 ` Shane Arnold
2009-09-09 19:43 ` Francois Romieu
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=4AA6506A.7040900@iinet.net.au \
--to=clontarf_x@iinet.net.au \
--cc=linux-kernel@vger.kernel.org \
/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