linux-kernel - Re: [PATCH] x86, olpc: Wait for last byte of EC command to be accepted

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: <CAMLZHHQCcWwG6mg1LNHrZ5E4q0M=OHjhsQgPWgPqzC63u57yEw@mail.gmail.com>
Date:	Fri, 5 Aug 2011 11:55:29 +0100
From:	Daniel Drake <dsd@...top.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	mingo@...hat.com, tglx@...utronix.de, hpa@...or.com,
	x86@...nel.org, dilinger@...ued.net, pgf@...top.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86, olpc: Wait for last byte of EC command to be accepted

On Fri, Aug 5, 2011 at 11:43 AM, Ingo Molnar <mingo@...e.hu> wrote:
> What did that result in - a resume hang? (i.e. how urgent is this fix
> - v3.1 material or v3.2 material?)

Sorry - the explanation is indeed lacking in that area!

It means that sometimes, on XO-1.5 (but not XO-1), the devices that
were marked as wakeup sources can't wake up the system. e.g. you ask
for wifi wakeups, suspend, but then incoming wifi frames don't wake up
the system as they should.

In my opinion, as a simple bugfix (verified by 2 of our EC firmware
developers) it is 3.1 material.

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