netdev - Re: [PATCH v2 fixed] e100: do not go D3 in shutdown unless system is powering off

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: <9929d2390904212246n4817b25r4db653cd7e6a24c1@mail.gmail.com>
Date:	Tue, 21 Apr 2009 22:46:19 -0700
From:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To:	Thadeu Lima de Souza Cascardo <cascardo@...oscopio.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, e1000-devel@...ts.sourceforge.net
Subject: Re: [PATCH v2 fixed] e100: do not go D3 in shutdown unless system is 
	powering off

On Tue, Apr 21, 2009 at 9:38 PM, Thadeu Lima de Souza Cascardo
<cascardo@...oscopio.com> wrote:
> After experimenting with kexec with the last merges after 2.6.29, I've
> had some problems when probing e100. It would not read the eeprom. After
> some bisects, I realized this has been like that since forever (at least
> 2.6.18). The problem is that shutdown is doing the same thing that
> suspend does and puts the device in D3 state. I couldn't find a way to
> get the device back to a sane state in the probe function. So, based on
> some similar patches from Rafael J. Wysocki for e1000, e1000e and ixgbe,
> I wrote this one for e100.
>
> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@...oscopio.com>
> ---

Thanks, I will add it to my queue of patches for e100.

Also, just FYI, Auke is no longer a maintainer for
e100/e1000/e1000e/igb/ixgb/ixgbe devices, so I have removed him from
the thread.

-- 
Cheers,
Jeff
--
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