linux-kernel - RE: [bug?] r8169: hangs under heavy load

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: <FCF60BC8872E4F1C9C72CE56F0E570C0@realtek.com.tw>
Date:	Fri, 2 Dec 2011 10:21:08 +0800
From:	hayeswang <hayeswang@...ltek.com>
To:	'Francois Romieu' <romieu@...zoreil.com>
CC:	<booster@...ke7.net>, 'Jonathan Nieder' <jrnieder@...il.com>,
	'Eric Dumazet' <eric.dumazet@...il.com>,
	<netdev@...r.kernel.org>, 'nic_swsd' <nic_swsd@...ltek.com>,
	<linux-kernel@...r.kernel.org>,
	'Armin Kazmi' <armin.kazmi@...dortmund.de>
Subject: RE: [bug?] r8169: hangs under heavy load

Francois Romieu [mailto:romieu@...zoreil.com] 
[...]
> > For the 8168c and the later chips, our hardware engineer 
> says that don't enable
> > the RxFIFOOver of IntrMask and don't clear the RxFIFOOver 
> of IntrStatus. The
> > hardware will automatically escape Rx fifo full situation. 
> Although you try to
> > clear the RxFIFOOver of IntrStatus, maybe the bit wouldn't 
> be cleared. Just
> > disregard it.
> 
> Should "later" be understood as gigabit PCI-E only or is 
> there a similar
> difference of behavior between older fast-ethernet PCI-E and 
> more recent
> ones ?
> 

For the fast controller, it should start from rtl8105e. 

Best Regards,
Hayes

--
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/