netdev - Re: r8169 won't transmit with 3.12

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]

Message-ID: <20140124002525.GA29384@electric-eye.fr.zoreil.com>
Date:	Fri, 24 Jan 2014 01:25:25 +0100
From:	Francois Romieu <romieu@...zoreil.com>
To:	Craig Small <csmall@....com.au>
Cc:	Realtek linux nic maintainers <nic_swsd@...ltek.com>,
	netdev@...r.kernel.org
Subject: Re: r8169 won't transmit with 3.12

Craig Small <csmall@....com.au> :
[...]
> That's fine. I was doing it to see if it would work. I'll stay with the r8169
> for now.

Thanks.

> I got a watchdog notice now, not sure if that is better or worse.

It's the usual Tx failure symptom.

[dmesg]
> [    0.000000] DMI: Gigabyte Technology Co., Ltd. To be filled by O.E.M./970A-D3P, BIOS F3 05/24/2013

(8168evl on a fairly recent motherboard, bios could be upgraded)

Did you enable the iommu in the setup ? If not, please give it a try.

-- 
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html