Jerone Young | 1 Feb 07:47 2010

[SRU] [Karmic] fix volume hotkeys for Dell Studio 1557

Impact:
	On the Dell Studio 1557 if you press any of the volume keys they will
not give a release and press infinitely.
https://bugs.launchpad.net/bugs/465250

Fix:
	Patch attached adds quirk to fix hotkeys for 2.6.31. 

	Though for 2.6.32 & upstream this fix is expected to go into udev.
Though Lucid has not pulled in a recent version supporting this
functionality.

Testcase:
	Pressing volume keys will not infinitely generate key presses.

Fix volume hotkeys for Dell Studio 1157 generating infinite key presses.

Signed-off-by: Jerone Young <jerone.young <at> canonical.com>

diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
index 950673f..af1744d 100644
--- a/drivers/input/keyboard/atkbd.c
+++ b/drivers/input/keyboard/atkbd.c
 <at>  <at>  -857,6 +857,14  <at>  <at>  static unsigned int atkbd_dell_laptop_forced_release_keys[] = {
 };

 /*
+ * Dell Studio 1557 does not generate release keys for
+ * mute, volume up, & volume down
+ */
(Continue reading)

Colin Ian King | 1 Feb 12:56 2010

Re: Likely Duplicate Bugs

Hi Brian,

This kernel message are dups of the same BIOS corruption message, but
occurs on a wide range of machines. I had a look at the first 15 or so
of the dups and saw that there was a wide spread of Aspire, HP Compaqs
and Pavilions and quite a number of unknown systems too.

Specifically, the kernel fills known regions of the low 64K of memory
with a known pattern and periodically monitors them.  Any buggy BIOS
that writes to these regions gets detected and the warning is issued.

BIOS corruption of these regions can occur when doing suspend/resume or
HDMI cable unplugging.

The error message is a warning - the system's stability is not
compromised as the pages being monitored are already reserved for the
purpose of being monitored for corruption in the first place.

This check can be disabled by setting the kernel boot parameter
memory_corruption_check=0

Since this is intended as a BIOS corruption detection tool perhaps it
should be disabled as a compile time option to stop getting these
messages. However, it does have some value in showing that the BIOS may
be dodgy. 

Colin

On Fri, 2010-01-29 at 20:36 -0800, Brian Murray wrote:
> I was perusing some kernel bugs and ran across some likely duplicates
(Continue reading)

Bryan Wu | 1 Feb 19:07 2010

[PATCH 0/2] UBUNTU: [Config] Enable CONFIG_DEBUG_KERNEL for ARM branch and CONFIG_TIMER_STATS for fsl-imx51 branch

In bug #513241, CONFIG_TIMER_STATS needs to be turned on for supporting
powertop application on ARM hardware. Since CONFIG_TIMER_STATS depends on
CONFIG_DEBUG_KERNEL, we need to enable CONFIG_DEBUG_KERNEL firstly.

The first patch can be shared with all ARM branches, the second patch is
simply enabling it on fsl-imx51 kernel. Please git pull from:
 git://kernel.ubuntu.com/roc/ubuntu-lucid lp513241_config_timer_stats

Bryan Wu (2):
  UBUNTU: [Config] Enable CONFIG_DEBUG_KERNEL for ARM branch
  UBUNTU: [Config] Enable CONFIG_TIMER_STATS for fsl-imx51 kernel

 debian.fsl-imx51/config/config.common.ubuntu |   47 +++++++++++++++++++++++++-
 1 files changed, 46 insertions(+), 1 deletions(-)

Bryan Wu | 1 Feb 19:07 2010

[PATCH 1/2] UBUNTU: [Config] Enable CONFIG_DEBUG_KERNEL for ARM branch

BugLink: http://bugs.launchpad.net/bugs/513241

We need to enable CONFIG_TIMER_STATS to use powertop properly on ARM hardware.
But CONFIG_TIMER_STATS depends on CONFIG_DEBUG_KERNEL. So we turn on this
option here as well as x86 branches.

This patch can share with all ARM branches

Signed-off-by: Bryan Wu <bryan.wu <at> canonical.com>
---
 debian.fsl-imx51/config/config.common.ubuntu |   47 +++++++++++++++++++++++++-
 1 files changed, 46 insertions(+), 1 deletions(-)

diff --git a/debian.fsl-imx51/config/config.common.ubuntu b/debian.fsl-imx51/config/config.common.ubuntu
index b3b6ccc..e9f5b8d 100644
--- a/debian.fsl-imx51/config/config.common.ubuntu
+++ b/debian.fsl-imx51/config/config.common.ubuntu
 <at>  <at>  -177,6 +177,7  <at>  <at>  CONFIG_BACKLIGHT_MXC=y
 CONFIG_BACKLIGHT_MXC_MC13892=y
 CONFIG_BACKLIGHT_PWM=m
 CONFIG_BACKLIGHT_WM8350=m
+# CONFIG_BACKTRACE_SELF_TEST is not set
 CONFIG_BASE_FULL=y
 CONFIG_BASE_SMALL=0
 CONFIG_BATTERY_BQ27x00=m
 <at>  <at>  -222,6 +223,7  <at>  <at>  CONFIG_BLK_DEV_SR=y
 # CONFIG_BLK_DEV_XIP is not set
 CONFIG_BLOCK=y
 CONFIG_BONDING=m
+# CONFIG_BOOT_PRINTK_DELAY is not set
(Continue reading)

Bryan Wu | 1 Feb 19:07 2010

[PATCH 2/2] UBUNTU: [Config] Enable CONFIG_TIMER_STATS for fsl-imx51 kernel

BugLink: http://bugs.launchpad.net/bugs/513241

For using powertop on armel hardware (at least for the bits and pieces where
it can gather data on non x86 HW), it needs to enable CONFIG_TIMER_STATS.

Signed-off-by: Bryan Wu <bryan.wu <at> canonical.com>
---
 debian.fsl-imx51/config/config.common.ubuntu |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/debian.fsl-imx51/config/config.common.ubuntu b/debian.fsl-imx51/config/config.common.ubuntu
index e9f5b8d..4b57037 100644
--- a/debian.fsl-imx51/config/config.common.ubuntu
+++ b/debian.fsl-imx51/config/config.common.ubuntu
 <at>  <at>  -2422,7 +2422,7  <at>  <at>  CONFIG_THERMAL_HWMON=y
 CONFIG_THRUSTMASTER_FF=y
 CONFIG_TICK_ONESHOT=y
 CONFIG_TIMERFD=y
-# CONFIG_TIMER_STATS is not set
+CONFIG_TIMER_STATS=y
 CONFIG_TIPC=m
 # CONFIG_TIPC_ADVANCED is not set
 # CONFIG_TIPC_DEBUG is not set
--

-- 
1.6.3.3

John Johansen | 1 Feb 19:29 2010

[Lucid] EC2 kernel request pull

The following changes since commit 72d1181fd70be26436c0a41ff1b5e6820bc5c689:
  Eric Miao (1):
        UBUNTU: SAUCE: Make CONFIG_{OMNIBOOK, AVERATEC_5100P, PACKARDBELL_E5} depend on X86

are available in the git repository at:

  git://kernel.ubuntu.com/jj/uec-karmic.git ec2

Alok Kataria (1):
      From 851b164231d1117673aa44c00c7622e48b7dfcf4 Mon Sep 17 00:00:00 2001 Date: Tue, 13 Oct 2009 14:51:05 -0700 Subject: [SCSI] vmw_pvscsi: SCSI driver for VMware's virtual HBA. Patch-mainline: 2.6.33 commit 851b164231d1117673aa44c00c7622e48b7dfcf4 upstream.

Andrea Arcangeli (1):
      Subject: [PATCH seccomp: make tsc disabling optional Patch-mainline: unknown References: 191123 Make the TSC disable purely paranoid feature optional, so by default seccomp returns absolutely zerocost.

Borislav Petkov (2):
      Subject: x86, cpu: mv display_cacheinfo -> cpu_detect_cache_sizes Patch-mainline: 2.6.33-rc1 References: bnc#564618, FATE#306952 Git-commit: 27c13ecec4d8856687b50b959e1146845b478f95 display_cacheinfo() doesn't display anything anymore and it is used to detect CPU cache sizes. Rename it accordingly.
      Subject: x86, cpu: mv display_cacheinfo -> cpu_detect_cache_sizes Patch-mainline: 2.6.33-rc1 References: bnc#564618, FATE#306952 Git-commit: 27c13ecec4d8856687b50b959e1146845b478f95 display_cacheinfo() doesn't display anything anymore and it is used to detect CPU cache sizes. Rename it accordingly.

Gerd Hoffmann (1):
      backward compatibility Patch-mainline: obsolete

Greg Kroah-Hartman (3):
      Subject: Linux 2.6.32.2 Signed-off-by: Greg Kroah-Hartman <gregkh <at> suse.de>
      Subject: Linux 2.6.32.3 Signed-off-by: Greg Kroah-Hartman <gregkh <at> suse.de>
      Subject: Linux 2.6.32.4 Patch-mainline: 2.6.32.4 Signed-off-by: Greg Kroah-Hartman <gregkh <at> suse.de>

Jack Steiner (2):
      Subject: x86: UV SGI: Don't track GRU space in PAT References: bnc#561933, fate#306952 Patch-mainline: 2.6.33-rc1 Git-commit: fd12a0d69aee6d90fa9b9890db24368a897f8423 GRU space is always mapped as WB in the page table. There is no need to track the mappings in the PAT. This also eliminates the "freeing invalid memtype" messages when the GRU space is unmapped.
      Subject: x86: UV SGI: Don't track GRU space in PAT References: bnc#561933, fate#306952 Patch-mainline: 2.6.33-rc1 Git-commit: fd12a0d69aee6d90fa9b9890db24368a897f8423 Commit fd12a0d69aee6d90fa9b9890db24368a897f8423 upstream.

(Continue reading)

Leann Ogasawara | 1 Feb 19:52 2010

Re: [Karmic] SRU: enabled ext4 and block loop for EC2

On Fri, 2010-01-29 at 12:49 -0800, John Johansen wrote:
> The following changes since commit 475a6aad6a68257e80c60fa8bbc0b47f02184c77:
>   Stefan Bader (1):
>         UBUNTU: Ubuntu-2.6.31-303.9
> 
> are available in the git repository at:
> 
>   git://kernel.ubuntu.com/jj/uec-karmic.git ec2
> 
> John Johansen (1):
>       UBUNTU: [Config] enable ext4 and block loop
> 
>  debian.ec2/config/amd64/config.flavour.ec2 |    4 ++++
>  debian.ec2/config/config.common.ubuntu     |    8 ++++----
>  debian.ec2/config/i386/config.common.i386  |    4 ++++
>  3 files changed, 12 insertions(+), 4 deletions(-)

Looks to only affect ec2.

Signed-off-by: Leann Ogasawara <leann.ogasawara <at> canonical.com>

Stefan Bader | 1 Feb 19:54 2010

Re: [Karmic] SRU: enabled ext4 and block loop for EC2

Ok, won't have impact on the main tree and looks sane.

Acked-by: Stefan Bader <stefan.bader <at> canonical.com>

John Johansen wrote:
> The following changes since commit 475a6aad6a68257e80c60fa8bbc0b47f02184c77:
>   Stefan Bader (1):
>         UBUNTU: Ubuntu-2.6.31-303.9
> 
> are available in the git repository at:
> 
>   git://kernel.ubuntu.com/jj/uec-karmic.git ec2
> 
> John Johansen (1):
>       UBUNTU: [Config] enable ext4 and block loop
> 
>  debian.ec2/config/amd64/config.flavour.ec2 |    4 ++++
>  debian.ec2/config/config.common.ubuntu     |    8 ++++----
>  debian.ec2/config/i386/config.common.i386  |    4 ++++
>  3 files changed, 12 insertions(+), 4 deletions(-)
> 

John Johansen | 1 Feb 20:18 2010

Re: [Lucid] EC2 kernel request pull

last request pull was from the wrong repo,

The following changes since commit 72d1181fd70be26436c0a41ff1b5e6820bc5c689:
  Eric Miao (1):
        UBUNTU: SAUCE: Make CONFIG_{OMNIBOOK, AVERATEC_5100P, PACKARDBELL_E5} depend on X86

are available in the git repository at:

  git://kernel.ubuntu.com/jj/ubuntu-lucid.git ec2

Alok Kataria (1):
      From 851b164231d1117673aa44c00c7622e48b7dfcf4 Mon Sep 17 00:00:00 2001 Date: Tue, 13 Oct 2009 14:51:05 -0700 Subject: [SCSI] vmw_pvscsi: SCSI driver for VMware's virtual HBA. Patch-mainline: 2.6.33 commit 851b164231d1117673aa44c00c7622e48b7dfcf4 upstream.

Andrea Arcangeli (1):
      Subject: [PATCH seccomp: make tsc disabling optional Patch-mainline: unknown References: 191123 Make the TSC disable purely paranoid feature optional, so by default seccomp returns absolutely zerocost.

Borislav Petkov (2):
      Subject: x86, cpu: mv display_cacheinfo -> cpu_detect_cache_sizes Patch-mainline: 2.6.33-rc1 References: bnc#564618, FATE#306952 Git-commit: 27c13ecec4d8856687b50b959e1146845b478f95 display_cacheinfo() doesn't display anything anymore and it is used to detect CPU cache sizes. Rename it accordingly.
      Subject: x86, cpu: mv display_cacheinfo -> cpu_detect_cache_sizes Patch-mainline: 2.6.33-rc1 References: bnc#564618, FATE#306952 Git-commit: 27c13ecec4d8856687b50b959e1146845b478f95 display_cacheinfo() doesn't display anything anymore and it is used to detect CPU cache sizes. Rename it accordingly.

Gerd Hoffmann (1):
      backward compatibility Patch-mainline: obsolete

Greg Kroah-Hartman (3):
      Subject: Linux 2.6.32.2 Signed-off-by: Greg Kroah-Hartman <gregkh <at> suse.de>
      Subject: Linux 2.6.32.3 Signed-off-by: Greg Kroah-Hartman <gregkh <at> suse.de>
      Subject: Linux 2.6.32.4 Patch-mainline: 2.6.32.4 Signed-off-by: Greg Kroah-Hartman <gregkh <at> suse.de>

Jack Steiner (2):
      Subject: x86: UV SGI: Don't track GRU space in PAT References: bnc#561933, fate#306952 Patch-mainline: 2.6.33-rc1 Git-commit: fd12a0d69aee6d90fa9b9890db24368a897f8423 GRU space is always mapped as WB in the page table. There is no need to track the mappings in the PAT. This also eliminates the "freeing invalid memtype" messages when the GRU space is unmapped.
(Continue reading)

Alessio Igor Bogani | 1 Feb 21:15 2010

[PATCH] Added new -lowlatency kernel flavour

Signed-off-by: Alessio Igor Bogani <abogani <at> ubuntu.com>
---
 debian.master/config/amd64/config.common.amd64     |    4 --
 debian.master/config/amd64/config.flavour.generic  |   13 +++++++
 .../config/amd64/config.flavour.lowlatency         |   29 +++++++++++++++++
 debian.master/config/amd64/config.flavour.server   |   13 +++++++
 debian.master/config/armel/config.common.armel     |    7 ++++
 debian.master/config/config.common.ubuntu          |   11 +-----
 debian.master/config/i386/config.common.i386       |    6 +---
 debian.master/config/i386/config.flavour.386       |   13 +++++++
 debian.master/config/i386/config.flavour.generic   |   13 +++++++
 .../config/i386/config.flavour.generic-pae         |   13 +++++++
 .../config/i386/config.flavour.lowlatency          |   34 ++++++++++++++++++++
 debian.master/config/lpia/config.common.lpia       |    9 +++++
 debian.master/control.d/vars.lowlatency            |    6 +++
 debian.master/rules.d/amd64.mk                     |    2 +-
 debian.master/rules.d/i386.mk                      |    2 +-
 debian.master/scripts/misc/getabis                 |    4 +-
 16 files changed, 157 insertions(+), 22 deletions(-)
 create mode 100644 debian.master/config/amd64/config.flavour.lowlatency
 create mode 100644 debian.master/config/i386/config.flavour.lowlatency
 create mode 100644 debian.master/control.d/vars.lowlatency

diff --git a/debian.master/config/amd64/config.common.amd64 b/debian.master/config/amd64/config.common.amd64
index 4b8a800..7eae719 100644
--- a/debian.master/config/amd64/config.common.amd64
+++ b/debian.master/config/amd64/config.common.amd64
 <at>  <at>  -60,8 +60,6  <at>  <at>  CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
 # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
 CONFIG_HUGETLB_PAGE=y
(Continue reading)


Gmane