linux-kernel - Re: [BISECTED] Suspend regression in v2.6.31 with Lenovo 3000 v200

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] [day] [month] [year] [list]

Message-ID: <4C237C70.70409@pardus.org.tr>
Date:	Thu, 24 Jun 2010 18:40:32 +0300
From:	Ozan Çağlayan <ozan@...dus.org.tr>
To:	Alan Stern <stern@...land.harvard.edu>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [BISECTED] Suspend regression in v2.6.31 with Lenovo 3000 v200

Alan Stern wrote:

> 
> The content of the power/wakeup file depends on two values: the 
> can_wakeup flag and the should_wakeup flag.  If can_wakeup is false 
> then the file will be empty; otherwise it will contain "disabled" or 
> "enabled" according to the value of should_wakeup.
> 
> Now, device_init_wakeup() sets both flags whereas 
> device_set_wakeup_capable() affects only the can_wakeup flag.  After 
> this change is made there should be nothing in the kernel that turns on 
> the should_wakeup flag, and consequently remote wakeup should remain 
> disabled.
> 
> You can check this by grepping for occurrences of "should_wakeup" or 
> "dev_set_wakeup_enable" (which affects the should_wakeup flag).
> 
> Alan Stern
> 

Okay the patch fixed the issue for the users. Thanks again for all your
helps, 

Regards,
Ozan Caglayan
--
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/