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: <4904469A.2090803@tuffmail.co.uk>
Date:	Sun, 26 Oct 2008 10:29:46 +0000
From:	Alan Jenkins <aj504@...dent.cs.york.ac.uk>
To:	Sanjoy Mahajan <sanjoy@...o.cam.ac.uk>
CC:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Francois Valenduc <francois.valenduc@...ablenet.be>,
	linux acpi <linux-acpi@...r.kernel.org>
Subject: Re: [Bug #11841] plenty of line "ACPI: EC: non-query interrupt received,
 switching to interrupt mode" in dmesg

Sanjoy Mahajan wrote:
>> The following bug entry is on the current list of known regressions
>> from 2.6.27.
> 
>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=11841
>> Subject : plenty of line "ACPI: EC: non-query interrupt received, switching to interrupt mode" in dmesg
> 
> I see these messages already with 2.6.27.3:
> 
>   # grep non-query /var/log/dmesg
>   [    0.205977] ACPI: EC: non-query interrupt received, switching to interrupt mode
> 
> There are 9 more occurrences in the current ring buffer:
>   # dmesg |grep non-query | wc -l
>   9
> 
> Each one happens right after waking from S3 sleep, for example:
> 
>   [70168.288590] CPU1 is up
>   [70168.288594] ACPI: Waking up from system sleep state S3
>   [70169.624254] ACPI: EC: non-query interrupt received, switching to interrupt mode
> 
> The setup is a TP T60 w/ Intel graphics, wireless (i.e. no taint),
> Debian unstable, but with vanilla kernel 2.6.27.3.
> 
> -Sanjoy

It's expected that you see that message on both boot and every wakeup from suspend.

If you look at the dmesg Francios' posted, his issue is that there are _floods_ of this message during boot.  That's not expected :).

Regards
Alan
--
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