All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife-l3A5Bk7waGM@public.gmane.org>
To: Jan Niehusmann <jan-7BUxKyILgIXQT0dZR+AlfA@public.gmane.org>
Cc: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	kernel list
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ACPI mailing list
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: bouncing keys and skipping sound with 2.6.11
Date: Mon, 07 Mar 2005 08:26:32 +0100	[thread overview]
Message-ID: <422C0228.1000709@suse.de> (raw)
In-Reply-To: <20050306185539.GA2149-7BUxKyILgIXQT0dZR+AlfA@public.gmane.org>

Jan Niehusmann wrote:

> By trying different kernel versions, I traced down the problem to the
> changes introduced between linux-2.6.11-rc2-bk9 and
> linux-2.6.11-rc2-bk10, and, more specifically, to the ACPI changes
> within that patch. (Therefore the Cc: to Len Brown, who wrote or
> submitted most of these changes, as far as I can tell from the
> changelog)

I bet you have CONFIG_ACPI_DEBUG enabled. Disable it or try to put
#define ACPI_ENABLE_OBJECT_CACHE 1
at the end of include/acpi/acpi.h (before the last #endif)
This fixed it for me (and some others).
There is also a patch for a "CONFIG_ACPI_DEBUG_LITE" from Thomas
Renninger on the acpi-devel list, which leaves some of the debugging in,
but disables the worst offenders IIUC.

Hope that helps,

     Stefan



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

WARNING: multiple messages have this Message-ID (diff)
From: Stefan Seyfried <seife@suse.de>
To: Jan Niehusmann <jan@gondor.com>
Cc: len.brown@intel.com, kernel list <linux-kernel@vger.kernel.org>,
	ACPI mailing list <acpi-devel@lists.sourceforge.net>
Subject: Re: bouncing keys and skipping sound with 2.6.11
Date: Mon, 07 Mar 2005 08:26:32 +0100	[thread overview]
Message-ID: <422C0228.1000709@suse.de> (raw)
In-Reply-To: <20050306185539.GA2149@gondor.com>

Jan Niehusmann wrote:

> By trying different kernel versions, I traced down the problem to the
> changes introduced between linux-2.6.11-rc2-bk9 and
> linux-2.6.11-rc2-bk10, and, more specifically, to the ACPI changes
> within that patch. (Therefore the Cc: to Len Brown, who wrote or
> submitted most of these changes, as far as I can tell from the
> changelog)

I bet you have CONFIG_ACPI_DEBUG enabled. Disable it or try to put
#define ACPI_ENABLE_OBJECT_CACHE 1
at the end of include/acpi/acpi.h (before the last #endif)
This fixed it for me (and some others).
There is also a patch for a "CONFIG_ACPI_DEBUG_LITE" from Thomas
Renninger on the acpi-devel list, which leaves some of the debugging in,
but disables the worst offenders IIUC.

Hope that helps,

     Stefan


  parent reply	other threads:[~2005-03-07  7:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02  8:02 Linux 2.6.11 Linus Torvalds
2005-02-28 18:44 ` key bounce problem with 2.6.11-rc5 Jan Niehusmann
2005-03-02 20:06   ` bouncing keys and skipping sound with 2.6.11 Jan Niehusmann
2005-03-06 18:55     ` Jan Niehusmann
     [not found]       ` <20050306185539.GA2149-7BUxKyILgIXQT0dZR+AlfA@public.gmane.org>
2005-03-07  7:26         ` Stefan Seyfried [this message]
2005-03-07  7:26           ` Stefan Seyfried
2005-03-12 11:13           ` Jan Niehusmann
2005-03-02 10:31 ` Linux 2.6.11 Matthias Andree
2005-03-02 11:01   ` Jesper Juhl
2005-03-02 15:46   ` Linus Torvalds
2005-03-02 16:47     ` Matthias Andree
2005-03-02 17:35       ` Linus Torvalds
2005-03-03  5:20     ` Ryan Anderson
2005-03-03 12:21       ` Matthias Andree
2005-03-02 12:47 ` Herbert Poetzl
2005-03-02 14:06   ` Michael Tokarev
2005-03-03  0:54     ` Herbert Poetzl
2005-03-02 16:18 ` John Cherry
2005-03-02 23:24 ` Jan Dittmer
2005-03-06  0:19 ` J.A. Magallon
2005-03-06  5:48   ` Trond Myklebust
2005-03-06  6:03     ` Neil Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=422C0228.1000709@suse.de \
    --to=seife-l3a5bk7wagm@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=jan-7BUxKyILgIXQT0dZR+AlfA@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.