arch/x86/include/asm/pvclock.h | 1 + arch/x86/kernel/pvclock.c | 5 +++++ arch/x86/xen/mmu.c | 13 +++++++------ arch/x86/xen/time.c | 2 ++ drivers/net/ixgbe/ixgbe_main.c | 4 ++++ drivers/net/r8169.c | 16 ++++++++++++---- 6 files changed, 31 insertions(+), 10 deletions(-)
New commits: commit 3c781f15d9cfec847beebfb588e7f403e7c15709 Author: Don Skidmore <[email protected]> Date: Tue Jan 18 22:53:47 2011 +0000 ixgbe: fix for 82599 erratum on Header Splitting commit a124339ad28389093ed15eca990d39c51c5736cc upstream. We have found a hardware erratum on 82599 hardware that can lead to unpredictable behavior when Header Splitting mode is enabled. So we are no longer enabling this feature on affected hardware. Please see the 82599 Specification Update for more information. Signed-off-by: Don Skidmore <[email protected]> Tested-by: Stephen Ko <[email protected]> Signed-off-by: Jeff Kirsher <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Andi Kleen <[email protected]> (cherry picked from commit 7978eb8d9cf53e9781bc9e143addeee8ee1ec4fe) commit 4937f421542d816cd3a0c09380ade377776b86af Author: Ivan Vecera <[email protected]> Date: Thu Jan 27 12:24:11 2011 +0100 r8169: use RxFIFO overflow workaround for 8168c chipset. commit b5ba6d12bdac21bc0620a5089e0f24e362645efd upstream. I found that one of the 8168c chipsets (concretely XID 1c4000c0) starts generating RxFIFO overflow errors. The result is an infinite loop in interrupt handler as the RxFIFOOver is handled only for ...MAC_VER_11. With the workaround everything goes fine. Signed-off-by: Ivan Vecera <[email protected]> Acked-by: Francois Romieu <[email protected]> Signed-off-by: Andi Kleen <[email protected]> Cc: Hayes <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> (cherry picked from commit 87f18d37dbbfeaf1cb3d8f7de81e38bc849f0536) commit fdd1430b8fd976cb714c95dc90d974d15fe99322 Author: Stanislaw Gruszka <[email protected]> Date: Tue Feb 22 02:00:11 2011 +0000 r8169: disable ASPM commit ba04c7c93bbcb48ce880cf75b6e9dffcd79d4c7b upstream. For some time is known that ASPM is causing troubles on r8169, i.e. make device randomly stop working without any errors in dmesg. Currently Tomi Leppikangas reports that system with r8169 device hangs with MCE errors when ASPM is enabled: https://bugzilla.redhat.com/show_bug.cgi?idd2861#c4 Lets disable ASPM for r8169 devices at all, to avoid problems with r8169 PCIe devices at least for some users. Reported-by: Tomi Leppikangas <[email protected]> Signed-off-by: Stanislaw Gruszka <[email protected]> Signed-off-by: David S. Miller <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Andi Kleen <[email protected]> (cherry picked from commit 91cda1a87e73670380948ad0954a2b544adf88fc) commit c9598123fb1474774b50d001c9a493f003d68d4c Author: françois romieu <[email protected]> Date: Mon Nov 8 13:23:58 2010 +0000 r8169: fix sleeping while holding spinlock. [ Upstream commit ea80907ff066edd1dd43c5fe90ae6677d15e6384 ] As device_set_wakeup_enable can now sleep, move the call to outside the critical section. Signed-off-by: Daniel J Blueman <[email protected]> Acked-by: Rafael J. Wysocki <[email protected]> Acked-by: Andrew Hendry <[email protected]> Signed-off-by: David S. Miller <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Andi Kleen <[email protected]> (cherry picked from commit b628317b1d1a58bc5722c982fce2729120438734) commit a1c00c554da8bc4ead379090f37514d53716c1fc Author: Stefano Stabellini <[email protected]> Date: Fri Feb 18 11:32:40 2011 +0000 xen: set max_pfn_mapped to the last pfn mapped commit 14988a4d350ce3b41ecad4f63c4f44c56f5ae34d upstream. Do not set max_pfn_mapped to the end of the initial memory mappings, that also contain pages that don't belong in pfn space (like the mfn list). Set max_pfn_mapped to the last real pfn mapped in the initial memory mappings that is the pfn backing _end. Signed-off-by: Stefano Stabellini <[email protected]> Acked-by: Konrad Rzeszutek Wilk <[email protected]> Signed-off-by: Andi Kleen <[email protected]> LKML-Reference: <alpine.DEB.2.00.1103171739050.3382@kaball-desktop> Signed-off-by: H. Peter Anvin <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> (cherry picked from commit c358c7982e8c4c5f1012a76fc3045eee29bb6824) commit 6ed3fd9cadf577284d48dfea8e0d3bec383bb5f0 Author: Jeremy Fitzhardinge <[email protected]> Date: Mon Oct 25 16:53:46 2010 -0700 x86/pvclock: Zero last_value on resume commit e7a3481c0246c8e45e79c629efd63b168e91fcda upstream. If the guest domain has been suspend/resumed or migrated, then the system clock backing the pvclock clocksource may revert to a smaller value (ie, can be non-monotonic across the migration/save-restore). Make sure we zero last_value in that case so that the domain continues to see clock updates. Signed-off-by: Jeremy Fitzhardinge <[email protected]> Signed-off-by: Ingo Molnar <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Andi Kleen <[email protected]> (cherry picked from commit ac9a0f1a28f560f2c65ee6e2ae5b750fac9f14cb) http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h<781f15d9cfec847beebfb588e7f403e7c15709 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;hI37f421542d816cd3a0c09380ade377776b86af http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;hýd1430b8fd976cb714c95dc90d974d15fe99322 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;hÉ598123fb1474774b50d001c9a493f003d68d4c http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h¡c00c554da8bc4ead379090f37514d53716c1fc http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;hnd3fd9cadf577284d48dfea8e0d3bec383bb5f0
_______________________________________________ svn mailing list [email protected] http://mailman.vyatta.com/mailman/listinfo/svn
