linux-kernel - Re: [BUG] Suspend tries to suspend devices already in D3

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: <200902031034.12175.rjw@sisk.pl>
Date:	Tue, 3 Feb 2009 10:34:11 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Frans Pop <elendil@...net.nl>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] Suspend tries to suspend devices already in D3

On Tuesday 03 February 2009, Frans Pop wrote:
> This is the second time I've hit this warning on an STR. Most times
> I do *not* get the warning. The first line is an extra debug printk I added
> after the first occurrence to give me the driver causing the problem.
> 
> What is different is that before this suspend I had switched to my wired
> e1000e NIC and had done an ifdown on the wireless. I suspect that because
> of that the wireless already was at D3 _before_ the suspend was started.

If ifdown causes the device to go into D3, then this is possible.

> Could this be the same issue as reported by Ming Lei?

Yes, it could.

Thanks,
Rafael
--
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/