linux-kernel - Re: [Bug #11841] plenty of line "ACPI: EC: non-query interrupt received, switching to interrupt mode" in dmesg

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	26 Oct 2008 03:16:25 +0000
From:	Sanjoy Mahajan <sanjoy@...o.cam.ac.uk>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Francois Valenduc <francois.valenduc@...ablenet.be>
Subject: Re: [Bug #11841] plenty of line "ACPI: EC: non-query interrupt received, switching to interrupt mode" in dmesg

> 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
--
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/