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]
Date:	Tue, 10 Jun 2008 18:37:35 +0000
From:	"Justin Mattock" <justinmattock@...il.com>
To:	"Len Brown" <lenb@...nel.org>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	linux-acpi@...r.kernel.org,
	"Alexey Starikovskiy" <astarikovskiy@...e.de>
Subject: Re: ACPI: EC: GPE storm detected, disabling EC GPE

On Tue, Jun 10, 2008 at 3:30 PM, Len Brown <lenb@...nel.org> wrote:
>
>
>> Could someone from acpi land please help here?
>
> Alexey maintains the EC, and he's supplied 3 patches to test
> in the bug report.  The 3rd is awaiting word from Justin.
>
> cheers,
> -Len
>
>> Justin, has this machine always had this problem or is it something
>> which earlier kernels handled correctly?
>
> note that the EC storm detection is new -- so the failure may
> have simply been different in older kernels -- such as a huge
> number of ACPI interrupts.
>
> cheers,
> -len
>
>

Hello; O.K. I applied the patch. after rebooting I was still seeing
this message, also I noticed HAL daemon was taking longer
to start. when unplugging the A/C adapter with pommed the screen
wouldn't dim, and under dmesg nothing about the battery.
when unplugging and plugging in. also with suspend the screen took
longer than normal to recover. So feeling uncomfortable
with how this patch was causing the system to react, I reverted back
just to be safe. After reverting it took a few reboots to bring the
battery
back to a good state. I'm not sure if this was because of ec.c or not.
Now before this patch The only chage that I had done was change 5 to
20,
after a few day's I did notice this message to dissipate. Maybe this
is just something with a macbook pro, and not other computers, with
this patch.
regards;

-- 
Justin P. Mattock
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ