Skip to content
Commits on Dec 19, 2009
  1. @NigelCunningham

    Bump version to 3.0.99.44.

    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    NigelCunningham committed Dec 19, 2009
  2. @NigelCunningham

    Fix two bio allocation issues.

    First, fix an issue with the last patch to this routine, wherein we
    need to call devices_of_same_priority() once, in order to avoid
    invoking it on a NULL chain in the routine's main loop.
    
    Second, we shouldn't assume that allocators will actually find some
    storage to register. Prio_chain_head might still be NULL after
    invoking toi_bio_register_storage, so check for that.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    NigelCunningham committed Dec 19, 2009
Commits on Dec 18, 2009
  1. @NigelCunningham
  2. @gregkh

    Linux 2.6.32.2

    gregkh committed Dec 18, 2009
  3. @gregkh

    implement early_io{re,un}map for ia64

    commit cd7bcf3 upstream.
    
    Needed for commit 2c99220 ("intel-iommu: Detect DMAR in hyperspace at
    probe time.) to build on IA64.
    
    Signed-off-by: Tony Luck <tony.luck@intel.com>
    Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Luck, Tony committed with gregkh Dec 14, 2009
  4. @paulusmack @gregkh

    perf_event: Fix incorrect range check on cpu number

    commit 0f624e7 upstream.
    
    It is quite legitimate for CPUs to be numbered sparsely, meaning
    that it possible for an online CPU to have a number which is
    greater than the total count of possible CPUs.
    
    Currently find_get_context() has a sanity check on the cpu
    number where it checks it against num_possible_cpus().  This
    test can fail for a legitimate cpu number if the
    cpu_possible_mask is sparsely populated.
    
    This fixes the problem by checking the CPU number against
    nr_cpumask_bits instead, since that is the appropriate check to
    ensure that the cpu number is same to pass to cpu_isset()
    subsequently.
    
    Reported-by: Michael Neuling <mikey@neuling.org>
    Signed-off-by: Paul Mackerras <paulus@samba.org>
    Tested-by: Michael Neuling <mikey@neuling.org>
    Acked-by: Peter Zijlstra <peterz@infradead.org>
    LKML-Reference: <20091215084032.GA18661@brick.ozlabs.ibm.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    paulusmack committed with gregkh Dec 15, 2009
  5. @gregkh

    netfilter: xtables: document minimal required version

    commit 7a92263 upstream.
    
    For both .33 and .32-stable.
    
    Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
    Signed-off-by: Patrick McHardy <kaber@trash.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Jan Engelhardt committed with gregkh Dec 14, 2009
  6. @chriswright @gregkh

    intel-iommu: ignore page table validation in pass through mode

    commit 1672af1 upstream.
    
    We are seeing a bug when booting w/ iommu=pt with current upstream
    (bisect blames 19943b0 "intel-iommu:
    Unify hardware and software passthrough support).
    
    The issue is specific to this loop during identity map initialization
    of each device:
    
    domain_context_mapping_one(si_domain, ..., CONTEXT_TT_PASS_THROUGH)
    ...
    		/* Skip top levels of page tables for
    		* iommu which has less agaw than default.
    		*/
    		for (agaw = domain->agaw; agaw != iommu->agaw; agaw--) {
    			pgd = phys_to_virt(dma_pte_addr(pgd));
    			if (!dma_pte_present(pgd)) {      <------ failing here
    				spin_unlock_irqrestore(&iommu->lock, flags);
    			return -ENOMEM;
    		}
    
    This box has 2 iommu's in it.  The catchall iommu has MGAW == 48, and
    SAGAW == 4.  The other iommu has MGAW == 39, SAGAW == 2.
    
    The device that's failing the above pgd test is the only device connected
    to the non-catchall iommu, which has a smaller address width than the
    domain default.  This test is not necessary since the context is in PT
    mode and the ASR is ignored.
    
    Thanks to Don Dutile for discovering and debugging this one.
    
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
    Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    chriswright committed with gregkh Dec 2, 2009
  7. @dwmw2 @gregkh

    intel-iommu: Fix oops with intel_iommu=igfx_off

    commit 44cd613 upstream.
    
    The hotplug notifier will call find_domain() to see if the device in
    question has been assigned an IOMMU domain. However, this should never
    be called for devices with a "dummy" domain, such as graphics devices
    when intel_iommu=igfx_off is set and the corresponding IOMMU isn't even
    initialised. If you do that, it'll oops as it dereferences the (-1)
    pointer.
    
    The notifier function should check iommu_no_mapping() for the
    device before doing anything else.
    
    Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    dwmw2 committed with gregkh Dec 2, 2009
  8. @dwmw2 @gregkh

    intel-iommu: Check for an RMRR which ends before it starts.

    commit 5595b52 upstream.
    
    Some HP BIOSes report an RMRR region (a region which needs a 1:1 mapping
    in the IOMMU for a given device) which has an end address lower than its
    start address. Detect that and warn, rather than triggering the
    BUG() in dma_pte_clear_range().
    
    Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    dwmw2 committed with gregkh Dec 2, 2009
  9. @dwmw2 @gregkh

    intel-iommu: Apply BIOS sanity checks for interrupt remapping too.

    commit 6ecbf01 upstream.
    
    The BIOS errors where an IOMMU is reported either at zero or a bogus
    address are causing problems even when the IOMMU is disabled -- because
    interrupt remapping uses the same hardware. Ensure that the checks get
    applied for the interrupt remapping initialisation too.
    
    Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    dwmw2 committed with gregkh Dec 2, 2009
  10. @chriswright @gregkh

    intel-iommu: Detect DMAR in hyperspace at probe time.

    commit 2c99220 upstream.
    
    Many BIOSes will lie to us about the existence of an IOMMU, and claim
    that there is one at an address which actually returns all 0xFF.
    
    We need to detect this early, so that we know we don't have a viable
    IOMMU and can set up swiotlb before it's too late.
    
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
    Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    chriswright committed with gregkh Dec 2, 2009
  11. @dwmw2 @gregkh

    jffs2: Fix long-standing bug with symlink garbage collection.

    commit 2e16cfc upstream.
    
    Ever since jffs2_garbage_collect_metadata() was first half-written in
    February 2001, it's been broken on architectures where 'char' is signed.
    When garbage collecting a symlink with target length above 127, the payload
    length would end up negative, causing interesting and bad things to happen.
    
    Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    dwmw2 committed with gregkh Dec 16, 2009
  12. @horms @gregkh

    ipvs: zero usvc and udest

    commit 258c889 upstream.
    
    Make sure that any otherwise uninitialised fields of usvc are zero.
    
    This has been obvserved to cause a problem whereby the port of
    fwmark services may end up as a non-zero value which causes
    scheduling of a destination server to fail for persisitent services.
    
    As observed by Deon van der Merwe <dvdm@truteq.co.za>.
    This fix suggested by Julian Anastasov <ja@ssi.bg>.
    
    For good measure also zero udest.
    
    Cc: Deon van der Merwe <dvdm@truteq.co.za>
    Acked-by: Julian Anastasov <ja@ssi.bg>
    Signed-off-by: Simon Horman <horms@verge.net.au>
    Signed-off-by: Patrick McHardy <kaber@trash.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    horms committed with gregkh Dec 15, 2009
  13. @gregkh

    mm: sigbus instead of abusing oom

    commit d99be1a upstream.
    
    When do_nonlinear_fault() realizes that the page table must have been
    corrupted for it to have been called, it does print_bad_pte() and returns
    ...  VM_FAULT_OOM, which is hard to understand.
    
    It made some sense when I did it for 2.6.15, when do_page_fault() just
    killed the current process; but nowadays it lets the OOM killer decide who
    to kill - so page table corruption in one process would be liable to kill
    another.
    
    Change it to return VM_FAULT_SIGBUS instead: that doesn't guarantee that
    the process will be killed, but is good enough for such a rare
    abnormality, accompanied as it is by the "BUG: Bad page map" message.
    
    And recent HWPOISON work has copied that code into do_swap_page(), when it
    finds an impossible swap entry: fix that to VM_FAULT_SIGBUS too.
    
    Signed-off-by: Hugh Dickins <hugh.dickins@tiscali.co.uk>
    Cc: Izik Eidus <ieidus@redhat.com>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Nick Piggin <npiggin@suse.de>
    Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
    Cc: Rik van Riel <riel@redhat.com>
    Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
    Cc: Andi Kleen <andi@firstfloor.org>
    Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
    Reviewed-by: Wu Fengguang <fengguang.wu@intel.com>
    Reviewed-by: Minchan Kim <minchan.kim@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Hugh Dickins committed with gregkh Dec 14, 2009
  14. @gregkh

    drm/i915: Fix LVDS stability issue on Ironlake

    commit 1b3c7a4 upstream.
    
    In disable sequence, all output ports on PCH have to be disabled
    before PCH transcoder, but LVDS port was left always enabled. This
    one fixes that by disable LVDS port properly during pipe disable
    process, and resolved stability issue seen on Ironlake. Also move
    panel fitting disable time just after pipe disable to align with
    the spec.
    
    Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Zhenyu Wang committed with gregkh Nov 25, 2009
  15. @gregkh

    drm/i915: PineView only has LVDS and CRT ports

    commit 103a196 upstream.
    
    PineView only has 2 ports for LVDS and CRT. Don't enable other
    ports for it.
    
    Cc: Shaohua Li <shaohua.li@intel.com>
    Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Zhenyu Wang committed with gregkh Nov 27, 2009
  16. @ickle @gregkh

    drm/i915: Avoid NULL dereference with component_only tv_modes

    commit d271817 upstream.
    
    In commit d2d9f23, the guard for a valid video mode was removed. This
    caused the regression:
    
      kernel crash during kms graphic boot on Intel GM4500 platform
      https://bugzilla.redhat.com/show_bug.cgi?id=540218
    
    This patches changes the logic slightly not to rely on a coupled
    variable, but to just check whether the video_modes is valid before
    dereferencing.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: David Woodhouse <dwmw2@infradead.org>
    Cc: Zhenyu Wang <zhenyu.z.wang@intel.com>
    [ickle: Actually reference the correct bug report]
    Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    ickle committed with gregkh Nov 27, 2009
  17. @gregkh

    x86: Under BIOS control, restore AP's APIC_LVTTHMR to the BSP value

    Upstream commit a2202aa.
    
    On platforms where bios handles the thermal monitor interrupt,
    APIC_LVTTHMR on each logical CPU is programmed to generate a SMI and OS
    can't touch it.
    
    Unfortunately AP bringup sequence using INIT-SIPI-SIPI clear all
    the LVT entries except the mask bit. Essentially this results in
    all LVT entries including the thermal monitoring interrupt set to masked
    (clearing the bios programmed value for APIC_LVTTHMR).
    
    And this leads to kernel take over the thermal monitoring interrupt
    on AP's but not on BSP (leaving the bios programmed value only on BSP).
    
    As a result of this, we have seen system hangs when the thermal
    monitoring interrupt is generated.
    
    Fix this by reading the initial value of thermal LVT entry on BSP
    and if bios has taken over the control, then program the same value
    on all AP's and leave the thermal monitoring interrupt control
    on all the logical cpu's to the bios.
    
    Signed-off-by: Yong Wang <yong.y.wang@intel.com>
    Reviewed-by: Suresh Siddha <suresh.b.siddha@intel.com>
    Cc: Borislav Petkov <borislav.petkov@amd.com>
    Cc: Arjan van de Ven <arjan@infradead.org>
    LKML-Reference: <20091110013824.GA24940@ywang-moblin2.bj.intel.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Yong Wang committed with gregkh Dec 16, 2009
  18. @ffainelli @gregkh

    bcm63xx_enet: fix compilation failure after get_stats_count removal

    commit a3f92ee upstream.
    
    This patch converts bcm63xx_enet to uset get_sset_count
    like the other drivers do.
    
    Signed-off-by: Florian Fainelli <ffainelli@freebox.fr>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    ffainelli committed with gregkh Dec 15, 2009
  19. @rmilecki @gregkh

    V4L/DVB (13116): gspca - ov519: Webcam 041e:4067 added.

    commit 518c8df upstream.
    
    Signed-off-by: Rafal Milecki <zajec5@gmail.com>
    Signed-off-by: Jean-Francois Moine <moinejf@free.fr>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
    Cc: Surbhi Palande <surbhi.palande@canonical.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    rmilecki committed with gregkh Oct 2, 2009
  20. @jankara @gregkh

    ext3: Fix data / filesystem corruption when write fails to copy data

    commit 68eb3db upstream.
    
    When ext3_write_begin fails after allocating some blocks or
    generic_perform_write fails to copy data to write, we truncate blocks already
    instantiated beyond i_size. Although these blocks were never inside i_size, we
    have to truncate pagecache of these blocks so that corresponding buffers get
    unmapped. Otherwise subsequent __block_prepare_write (called because we are
    retrying the write) will find the buffers mapped, not call ->get_block, and
    thus the page will be backed by already freed blocks leading to filesystem and
    data corruption.
    
    Reported-by: James Y Knight <foom@fuhm.net>
    Signed-off-by: Jan Kara <jack@suse.cz>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    jankara committed with gregkh Dec 1, 2009
  21. @ebiederm @gregkh

    net: Fix userspace RTM_NEWLINK notifications.

    commit d90a909 upstream.
    
    I received some bug reports about userspace programs having problems
    because after RTM_NEWLINK was received they could not immeidate
    access files under /proc/sys/net/ because they had not been
    registered yet.
    
    The problem was trivailly fixed by moving the userspace
    notification from rtnetlink_event to the end of register_netdevice.
    
    Signed-off-by: Eric W. Biederman <ebiederm@aristanetworks.com>
    Cc: David Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    ebiederm committed with gregkh Dec 13, 2009
  22. @yakuizhao @gregkh

    ACPI: Use the ARB_DISABLE for the CPU which model id is less than 0x0f.

    commit 03a05ed upstream.
    
    Currently, ARB_DISABLE is a NOP on all of the recent Intel platforms.
    For such platforms, reduce contention on c3_lock by skipping the fake
    ARB_DISABLE.
    
    The cpu model id on one laptop is 14. If we disable ARB_DISABLE on this box,
    the box can't be booted correctly. But if we still enable ARB_DISABLE on this
    box, the box can be booted correctly.
    
    So we still use the ARB_DISABLE for the cpu which mode id is less than 0x0f.
    
    http://bugzilla.kernel.org/show_bug.cgi?id=14700
    
    Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
    Acked-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
    Signed-off-by: Len Brown <len.brown@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    yakuizhao committed with gregkh Dec 11, 2009
  23. @gregkh

    vmalloc: conditionalize build of pcpu_get_vm_areas()

    No matching upstream commit as it was resolved differently there.
    
    
    pcpu_get_vm_areas() is used only when dynamic percpu allocator is used
    by the architecture.  In 2.6.32, ia64 doesn't use dynamic percpu
    allocator and has a macro which makes pcpu_get_vm_areas() buggy via
    local/global variable aliasing and triggers compile warning.
    
    The problem is fixed in upstream and ia64 uses dynamic percpu
    allocators, so the only left issue is inclusion of unnecessary code
    and compile warning on ia64 on 2.6.32.
    
    Don't build pcpu_get_vm_areas() if legacy percpu allocator is in use.
    
    Signed-off-by: Tejun Heo <tj@kernel.org>
    Reported-by: Jan Beulich <JBeulich@novell.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Tejun Heo committed with gregkh Dec 10, 2009
  24. @iksaif @gregkh

    asus-laptop: change light sens default values.

    commit d951d4c upstream.
    
    The light sensor disable brightness key and
    /sys/class/backlight/ control. There was a lot of report
    from users who didn't understand why they couldn't change their
    brightness, including:
    
    https://bugs.launchpad.net/bugs/222171
    https://bugzilla.novell.com/show_bug.cgi?id=514747
    http://bugzilla.kernel.org/show_bug.cgi?id=13671
    http://bugzilla.kernel.org/show_bug.cgi?id=14432
    
    Now the light sensor is disabled, and if the user want to enable
    it, the level should be ok.
    
    The funny thing is that comments where ok, not code.
    
    Cc: stable@kernel.org
    Cc: Thomas Renninger <trenn@suse.de>
    Cc: Peter Küppers <peter-mailbox@web.de>
    Cc: Michael Franzl <michaelfranzl@gmx.at>
    Cc: Ian Turner <vectro@vectro.org>
    Signed-off-by: Corentin Chary <corentincj@iksaif.net>
    Signed-off-by: Len Brown <len.brown@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    iksaif committed with gregkh Dec 7, 2009
  25. @xypiie @gregkh

    acerhdf: add new BIOS versions

    commit 3606574 upstream.
    
    Added new BIOS versions for following netbooks: Acer 1410, Gateway LT31,
    Packard Bell DOA150.  As the Gateway LT31 machines have different register
    values for setting and checking the off-state, the "cmd_off" variable has
    been splitted up to "cmd_off" and "chk_off".
    
    Signed-off-by: Peter Feuerer <peter@piie.net>
    Cc: Borislav Petkov <petkovbb@gmail.com>
    Cc: Andreas Mohr <andi@lisas.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Len Brown <len.brown@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    xypiie committed with gregkh Nov 17, 2009
  26. @gregkh

    matroxfb: fix problems with display stability

    commit 8c65131 upstream.
    
    Regression caused in 2.6.23 and then despite repeated requests never fixed
    or dealt with (Petr promised to sort it in 2008 but seems to have
    forgotten).
    
    Enough is enough - remove the problem line that was added.  If it upsets
    someone they've had two years to deal with it and at the very least it'll
    rattle their cage and wake them up.
    
    Addresses http://bugzilla.kernel.org/show_bug.cgi?id=9709
    
    Signed-off-by: Alan Cox <alan@linux.intel.com>
    Reported-by: Damon <account@bugzilla.kernel.org.juxtaposition.net>
    Tested-by: Ruud van Melick <rvm1974@raketnet.nl>
    Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>
    Cc: Pekka Enberg <penberg@cs.helsinki.fi>
    Cc: Paul A. Clarke <pc@us.ibm.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Alan Cox committed with gregkh Dec 15, 2009
  27. @gregkh

    ipw2100: fix rebooting hang with driver loaded

    commit 52ce3e9 upstream.
    
    Add PCI .shutdown method so that we can disable the device during
    shutdown or reboot. Without this, the reboot doesn't work well on
    some platforms.
    
    This fixes http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2124
    
    Tested-by: pablo <pablolm2005@gmail.com>
    Signed-off-by: Zhu Yi <yi.zhu@intel.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Zhu Yi committed with gregkh Dec 2, 2009
  28. @hmh @gregkh

    thinkpad-acpi: preserve rfkill state across suspend/resume

    commit 208b996 upstream.
    
    Since the rfkill rework in 2.6.31, the driver is always resuming with
    the radios disabled.
    
    Change thinkpad-acpi to ask the firmware to resume with the radios in
    the last state.  This fixes the Bluetooth and WWAN rfkill switches.
    
    Note that it means we respect the firmware's oddities.  Should the
    user toggle the hardware rfkill switch on and off, it might cause the
    radios to resume enabled.
    
    UWB is an unknown quantity since it has nowhere the same level of
    firmware support (no control over state storage in NVRAM, for
    example), and might need further fixing.  Testers welcome.
    
    This change fixes a regression from 2.6.30.
    
    Reported-by: Jerone Young <jerone.young@canonical.com>
    Reported-by: Ian Molton <ian.molton@collabora.co.uk>
    Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
    Tested-by: Ian Molton <ian.molton@collabora.co.uk>
    Signed-off-by: Len Brown <len.brown@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    hmh committed with gregkh Dec 9, 2009
  29. @hmh @gregkh

    thinkpad-acpi: fix default brightness_mode for R50e/R51

    commit a9f8eac upstream.
    
    According to a report, the R50e wants EC-based brightness control,
    even if it uses an Intel GPU.  The current driver default was reported
    to not work at all.
    
    This bug can be worked around by the "brightness_mode=3" module
    parameter.
    
    Change the default of the R50e and R51 2xxx models (which use the same
    EC firmware, 1V) to TPACPI_BRGHT_Q_EC, but keep TPACPI_BRGHT_Q_ASK set
    for now, as I'd like to get more reports.
    
    This fixes a regression caused by commit
    59fe4fe,
    "thinkpad-acpi: fix incorrect use of TPACPI_BRGHT_MODE_ECNVRAM"
    
    Kernel 2.6.31 also needs this fix.
    
    Reported-by: Ferenc Wagner <wferi@niif.hu>
    Tested-by: Ferenc Wagner <wferi@niif.hu>
    Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
    Cc: stable@kernel.org
    Signed-off-by: Len Brown <len.brown@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    hmh committed with gregkh Dec 9, 2009
  30. @kiryl @gregkh

    memcg: fix memory.memsw.usage_in_bytes for root cgroup

    commit cd9b45b upstream.
    
    A memory cgroup has a memory.memsw.usage_in_bytes file.  It shows the sum
    of the usage of pages and swapents in the cgroup.  Presently the root
    cgroup's memsw.usage_in_bytes shows the wrong value - the number of
    swapents are not added.
    
    So take MEM_CGROUP_STAT_SWAPOUT into account.
    
    Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name>
    Reviewed-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
    Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    kiryl committed with gregkh Dec 15, 2009
  31. @gregkh

    drm/i915: Fix sync to vblank when VGA output is turned off

    commit 778c902 upstream
    
    In current vblank-wait implementation, if we turn off VGA output,
    drm_wait_vblank will still wait on the disabled pipe until timeout,
    because vblank on the pipe is assumed be enabled. This would cause
    slow system response on some system such as moblin.
    
    This patch resolve the issue by adding a drm helper function
    drm_vblank_off which explicitly clear vblank_enabled[crtc], wake up
    any waiting queue and save last vblank counter before turning off
    crtc. It also slightly change drm_vblank_get to ensure that we will
    will return immediately if trying to wait on a disabled pipe.
    
    Signed-off-by: Li Peng <peng.li@intel.com>
    Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
    [anholt: hand-applied for conflicts with overlay changes]
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Cc: Stefan Bader <stefan.bader@canonical.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Li Peng committed with gregkh Dec 16, 2009
  32. @gregkh

    mac80211: Fix dynamic power save for scanning.

    Upstream commit: 7c3f4bb
    
    Not only ps_sdata but also IEEE80211_CONF_PS is to be considered
    before restoring PS in scan_ps_disable(). For instance, when ps_sdata
    is set but CONF_PS is not set just because the dynamic timer is still
    running, a sw scan leads to setting of CONF_PS in scan_ps_disable
    instead of restarting the dynamic PS timer.
    Also for the above case, a null data frame is to be sent after
    returning to operating channel which was not happening with the
    current implementation. This patch fixes this too.
    
    
    Signed-off-by: Vivek Natarajan <vnatarajan@atheros.com>
    Reviewed-by: Kalle Valo <kalle.valo@nokia.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Vivek Natarajan committed with gregkh Dec 16, 2009
  33. @gregkh

    ath9k: fix tx status reporting

    This is a backport of upstream commit: e8c6342d989e241513baeba4b05a04b6b1f3bc8b
    
    This patch fixes a bug in ath9k's tx status check, which
    caused mac80211 to consider regularly transmitted unicast frames
    as un-acked.
    
    When checking the ts_status field for errors, it needs to be masked
    with ATH9K_TXERR_FILT, because this field also contains other fields
    like ATH9K_TX_ACKED.
    
    Without this patch, AP mode is pretty much unusable, as hostapd
    checks the ACK status for the frames that it injects.
    
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Dec 16, 2009
Something went wrong with that request. Please try again.