linux-kernel - Re: Bringing up secondary rtl8169-based interface causes network hang/dma issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Sep 2009 02:08:57 +0800
From:	Shane Arnold <clontarf_x@...et.net.au>
To:	Francois Romieu <romieu@...zoreil.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Bringing up secondary rtl8169-based interface causes network
 hang/dma issues

Well it seems I have solved it by disabling APIC and MSI/MSI-X 
interrupts. Both NIC's up and playing nicely.

Now just to figure out why it's not communicating with anything...

Thanks Francois!

Francois Romieu wrote:
> Shane Arnold <clontarf_x@...et.net.au> :
> [...]
>> 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)
>                        ^^^^^^^
> Do you mean the in-kernel r8169 driver or Realtek's one ?
> 
>> 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 second (PCI only ?) network card is plugged and lspci does not display
> it, right ?
> 
>> The output from kern.log is as follows (right after bringing the link up)
> 
> Please send a complete dmesg from boot and the content of /proc/interrupts
> once the link is brought up.
> 
> [...]
>> 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.
> 
> It is suggested to send network related problems to netdev@...r.kernel.org
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/