netdev - Re: r8169 delay / segfault

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: <20121014213224.GA23396@electric-eye.fr.zoreil.com>
Date:	Sun, 14 Oct 2012 23:32:24 +0200
From:	Francois Romieu <romieu@...zoreil.com>
To:	Roland Stigge <stigge@...com.de>
Cc:	nic_swsd@...ltek.com, netdev@...r.kernel.org,
	hayeswang <hayeswang@...ltek.com>
Subject: Re: r8169 delay / segfault

Roland Stigge <stigge@...com.de> :
[...]
> What does the different device ID, XID and IRQ number mean ?

XID identifies the chipset. If the chipset stops responding - all 1 bits -
the device can not be identified.

> How can we force the device out of D3 power state?
> 
> I also compared with kernel 3.5, and it seems like a regression to me,
> With 3.5, it works and tells on resume:

Can you try both a 3.5 kernel with the 3.6 r8169 driver and a 3.6 kernel
with the 3.5 r8169 driver ?

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