Bug#669335: linux-image-2.6.32-5-686-bigmem: 86-mm-Fix-pgd_lock-deadlock.patch
Package: linux-image-2.6.32-5-686-bigmem
Version: 2.6.32-41squeeze2
Severity: important
We received several problem reports from our customers and also
experienced the following bug when running said kernel with =2 CPUs in
a virtualization environbment (KVM and VMWare ESX). After some time the
VM just stops (no ping, no console, no activity).
Using gdb and KVMs gdbserver capability I was able to track it down to
the following symptom: One thread would be stuck in
flush_tlb_others_ipi() waiting for all other CPUs using a specifiy mm to
signal they have flushed there TLB, while all other CPU-threads would be
waiting for the pgd_lock to be freed.
I have no easy test to reproduce the bug, but it usually happens to me
when I run several pbuilder-builds in parallel. The more virtual CPUs
the VM has, the easier to trigger: With 2 VCPUs it's hours, with 6 VCPUs
it's usually less than 5 minutes.
This got more prominent with git-commit
831d52bc153971b70e64eccfbed2b232394f22f8: x86, mm: avoid possible bogus tlb
entries by clearing prev mm_cpumask after switching mm
(Linus tree), and even worse with
4981d01eada5354d81c8929d5b2836829ba3df7b: x86: Flush TLB if PGD entry is
changed in i386 PAE mode
I found the issue to be fixed by
a79e53d85683c6dd9f99c90511028adc2043031f: x86/mm: Fix pgd_lock deadlock
That patch is already in the Debian patch set, but only applied for the
xen flavour: features/all/xen/x86-mm-Fix-pgd_lock-deadlock.patch
I thinks this patch should be applied to all flavours. It doesn't apply
to the non-xen-flavour as is, because it depends on some other
xen-related patch.
The Patch was also back-ported to the OpenSUSE Kernel
http://kernel.opensuse.org/cgit/kernel-source/commit/?id=ac27c01aa880c65d17043ab87249c613ac4c3635,
but since the patch is trivial to backport, I'll attach my version as
well.
The patch should be forwarded to Upstream to be included into the
upstream 2.6.32 longterm stable kernel as well.
The full issue is tracked in our (German) Bugzilla:
https://forge.univention.org/bugzilla/show_bug.cgi?id=26661
Sincerely
Philipp
-- System Information:
Debian Release: 5.0.1
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.32-ucs57-686-bigmem
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Bug #26661: 686-bigmem VM deadlock
--- /dev/null
+++
linux-2.6.32-2.6.32/debian/patches/bugfix/x86/x86-mm-Fix-pgd_lock-deadlock.patch
@@ -0,0 +1,217 @@
+It's forbidden to take the page_table_lock with the irq disabled
+or if there's contention the IPIs (for tlb flushes) sent with
+the page_table_lock held will never run leading to a deadlock.
+
+Nobody takes the pgd_lock from irq context so the _irqsave can be
+removed.
+
+Signed-off-by: Andrea Arcangeli aarca...@redhat.com
+Acked-by: Rik van Riel r...@redhat.com
+Tested-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com
+Signed-off-by: Andrew Morton a...@linux-foundation.org
+Cc: Peter Zijlstra pet...@infradead.org
+Cc: Linus Torvalds torva...@linux-foundation.org
+Cc: sta...@kernel.org
+LKML-Reference: 201102162345.p1gnjmjm021...@imap1.linux-foundation.org
+Signed-off-by: Ingo Molnar mi...@elte.hu
+Git-commit: a79e53d85683c6dd9f99c90511028adc2043031f
+--- a/arch/x86/mm/fault.c
b/arch/x86/mm/fault.c
+@@ -223,15 +223,14 @@ void vmalloc_sync_all(void)
+address = TASK_SIZE address FIXADDR_TOP;
+address += PMD_SIZE) {
+
+- unsigned long flags;
+ struct page *page;
+
+- spin_lock_irqsave(pgd_lock, flags);
++ spin_lock(pgd_lock);
+ list_for_each_entry(page, pgd_list, lru) {
+ if (!vmalloc_sync_one(page_address(page), address))
+ break;
+ }
+- spin_unlock_irqrestore(pgd_lock, flags);
++ spin_unlock(pgd_lock);
+ }
+ }
+
+@@ -331,13 +330,12 @@ void vmalloc_sync_all(void)
+address += PGDIR_SIZE) {
+
+ const pgd_t *pgd_ref = pgd_offset_k(address);
+- unsigned long flags;
+ struct page *page;
+
+ if (pgd_none(*pgd_ref))
+ continue;
+
+- spin_lock_irqsave(pgd_lock, flags);
++ spin_lock(pgd_lock);
+ list_for_each_entry(page, pgd_list, lru) {
+ pgd_t *pgd;
+ pgd = (pgd_t *)page_address(page) + pgd_index(address);
+@@ -346,7 +344,7 @@ void vmalloc_sync_all(void)
+ else
+ BUG_ON(pgd_page_vaddr(*pgd) !=
pgd_page_vaddr(*pgd_ref));
+ }
+- spin_unlock_irqrestore(pgd_lock, flags);
++ spin_unlock(pgd_lock);
+ }
+ }
+
+--- a/arch/x86/mm/pageattr.c
b/arch/x86/mm/pageattr.c
+@@ -56,12 +56,10 @@ static unsigned long direct_pages_count[
+
+ void update_page_count(int level, unsigned long pages)
+ {
+- unsigned long flags;
+-
+ /* Protect against CPA */
Bug#669342: initramfs-tools should conflicts to dracut
Package: initramfs-tools Version: 0.101 Severity: minor Since dracut uses the same file name for the initrd and dracut is a replacement for initramfs-tools, it should conflict to dracut. The dracut package already conflicts to initramfs-tools. -- regards Thomas -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20367.54389.341847.644...@malzmuehle.informatik.uni-koeln.de
Bug#669345: /etc/kernel/postinst.d/initramfs-tools: update-initramfs: not found
Package: initramfs-tools
Version: 0.101
Severity: minor
Tags: patch
When I install dracut - which conflicts to initramfs-tools -
initramfs-tools will be removed. But when doing a dpkg-reconfigure the
script /etc/kernel/postinst.d/initramfs-tools is still executed, which
lead to following error:
/etc/kernel/postinst.d/initramfs-tools: 33:
/etc/kernel/postinst.d/initramfs-tools: update-initramfs: not found
Here's an easy patch for this:
--- /etc/kernel/postinst.d/initramfs-tools 2011-03-30 11:56:12.0
+0200
+++ initramfs-tools.new 2012-04-19 10:49:28.677972624 +0200
@@ -3,6 +3,8 @@
version=$1
bootopt=
+[ -x /usr/sbin/update-initramfs ] || exit 0
+
# passing the kernel version is required
if [ -z ${version} ]; then
echo 2 W: initramfs-tools: ${DPKG_MAINTSCRIPT_PACKAGE:-kernel
package} did not pass a version number
Log of the problem:
wheezy[~]# aptitude install dracut
The following NEW packages will be installed:
dracut{b}
0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/133 kB of archives. After unpacking 442 kB will be used.
The following packages have unmet dependencies:
dracut : Conflicts: initramfs-tools but 0.101 is installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) initramfs-tools
Accept this solution? [Y/n/q/?]
The following NEW packages will be installed:
dracut
The following packages will be REMOVED:
initramfs-tools{a}
0 packages upgraded, 1 newly installed, 1 to remove and 1 not upgraded.
Need to get 0 B/133 kB of archives. After unpacking 115 kB will be used.
Do you want to continue? [Y/n/?]
dpkg: initramfs-tools: dependency problems, but removing anyway as you
requested:
linux-image-3.2.0-2-amd64 depends on initramfs-tools (= 0.99~) |
linux-initramfs-tool; however:
Package initramfs-tools is to be removed.
Package linux-initramfs-tool is not installed.
Package dracut which provides linux-initramfs-tool is not installed.
Package initramfs-tools which provides linux-initramfs-tool is to be removed.
linux-image-3.2.0-2-amd64 depends on initramfs-tools (= 0.99~) |
linux-initramfs-tool; however:
Package initramfs-tools is to be removed.
Package linux-initramfs-tool is not installed.
Package dracut which provides linux-initramfs-tool is not installed.
Package initramfs-tools which provides linux-initramfs-tool is to be removed.
(Reading database ... 178235 files and directories currently installed.)
Removing initramfs-tools ...
Processing triggers for man-db ...
Processing triggers for doc-base ...
Processing 1 removed doc-base file...
Registering documents with dhelp...
Selecting previously unselected package dracut.
(Reading database ... 178182 files and directories currently installed.)
Unpacking dracut (from .../archives/dracut_018-2_all.deb) ...
Processing triggers for man-db ...
Setting up dracut (018-2) ...
dracut: Generating /boot/initrd.img-3.2.0-2-amd64
wheezy[~]# dpkg-reconfigure linux-image-3.2.0-2-amd64
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dracut 3.2.0-2-amd64
/boot/vmlinuz-3.2.0-2-amd64
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-2-amd64
/boot/vmlinuz-3.2.0-2-amd64
/etc/kernel/postinst.d/initramfs-tools: 33:
/etc/kernel/postinst.d/initramfs-tools: update-initramfs: not found
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
Failed to process /etc/kernel/postinst.d at
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 696, STDIN line 2.
-- Package-specific info:
-- initramfs sizes
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64
root=UUID=a1abfdce-78e6-4c16-a5d6-3eef6f04f9ee ro quiet
-- resume
RESUME=UUID=34690ec1-2b81-4b16-8105-ac3f759f309c
-- /proc/filesystems
ext4
-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages initramfs-tools depends on:
ii cpio 2.11-7
ii klibc-utils2.0~rc3-1
ii module-init-tools none
ii udev 175-3.1
Versions of packages initramfs-tools recommends:
ii busybox 1:1.19.3-5
Versions of packages initramfs-tools suggests:
pn bash-completion none
--
regards Thomas
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20367.54280.649032.516...@malzmuehle.informatik.uni-koeln.de
Bug#669342: initramfs-tools should conflicts to dracut
On Thu, 2012-04-19 at 11:01 +0200, Thomas Lange wrote: Package: initramfs-tools Version: 0.101 Severity: minor Since dracut uses the same file name for the initrd and dracut is a replacement for initramfs-tools, it should conflict to dracut. The dracut package already conflicts to initramfs-tools. They should both conflict with linux-initramfs-tool, to allow for, say, an updated yaird. Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't. signature.asc Description: This is a digitally signed message part
Processed: severity of 669345 is important
Processing commands for cont...@bugs.debian.org: severity 669345 important Bug #669345 [initramfs-tools] /etc/kernel/postinst.d/initramfs-tools: update-initramfs: not found Severity set to 'important' from 'minor' thanks Stopping processing here. Please contact me if you need assistance. -- 669345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13348408349323.transcr...@bugs.debian.org
Bug#660111: Bug#664653 pulseaudio: pa can't handle multiple HDMI devices -- chooses wrong default
tags 664653 fixed-upstream thanks Pulseaudio upstream version 1.99.1 (or master, specifically after commit e02cb7fb2e7865affed612693935c7fd698e3a6b) contains all the necessary bits to allow the user to select from several HDMI devices advertised by the kernel. Please consider packaging. Andres -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAH=dyrhswrdls65rdj1xt0q8vfeykvrasntoshu3yuo5kf1...@mail.gmail.com
Bug#669335: [PATCH 2.6.32.y] x86/mm: Fix pgd_lock deadlock
reassign 669335 src:linux-2.6 2.6.32-41squeeze2 tags 669335 + upstream patch quit Hi Philipp, Philipp Hahn wrote: We received several problem reports from our customers and also experienced the following bug when running said kernel with =2 CPUs in a virtualization environbment (KVM and VMWare ESX). After some time the VM just stops (no ping, no console, no activity). [...] I have no easy test to reproduce the bug, but it usually happens to me when I run several pbuilder-builds in parallel. The more virtual CPUs the VM has, the easier to trigger: With 2 VCPUs it's hours, with 6 VCPUs it's usually less than 5 minutes. [...] That patch is already in the Debian patch set, but only applied for the xen flavour: features/all/xen/x86-mm-Fix-pgd_lock-deadlock.patch I thinks this patch should be applied to all flavours. [...] The Patch was also back-ported to the OpenSUSE Kernel [...] The patch should be forwarded to Upstream to be included into the upstream 2.6.32 longterm stable kernel as well. Thanks! I have marked the bug so I can remember to investigate and forward it to Willy, but if you have time to send your backport before then to sta...@vger.kernel.org with [2.6.32.y] in the subject line, cc-ing Andrea Arcangeli aarca...@redhat.com, x...@kernel.org, xen-de...@lists.xensource.com, linux-ker...@vger.kernel.org, Jan Beulich jbeul...@suse.com, Thomas Gleixner t...@linutronix.de, Ingo Molnar mi...@elte.hu, Rik van Riel r...@redhat.com, Konrad Rzeszutek Wilk konrad.w...@oracle.com, Johannes Weiner jwei...@redhat.com, Jeremy Fitzhardinge jer...@goop.org, Larry Woodman lwood...@redhat.com Peter Zijlstra pet...@infradead.org, Linus Torvalds torva...@linux-foundation.org (or just replying-to-all to the original patch[1] and adding additional cc lines from the commit message), that would be helpful. Be sure to mention the upstream commit id, that it is part of 2.6.38 (hence in 3.0.y etc already), your symptoms, and what happened when you tested the patch. I imagine Willy will pick it up for the next point release unless someone objects. Thanks, Jonathan The full issue is tracked in our (German) Bugzilla: https://forge.univention.org/bugzilla/show_bug.cgi?id=26661 [1] http://thread.gmane.org/gmane.comp.emulators.xen.devel/91726/focus=1101391 mbox: http://download.gmane.org/gmane.linux.kernel/1101391/1101392 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120419155911.GB2775@burratino
Processed: Re: [PATCH 2.6.32.y] x86/mm: Fix pgd_lock deadlock
Processing commands for cont...@bugs.debian.org: reassign 669335 src:linux-2.6 2.6.32-41squeeze2 Bug #669335 [linux-image-2.6.32-5-686-bigmem] linux-image-2.6.32-5-686-bigmem: 86-mm-Fix-pgd_lock-deadlock.patch Bug reassigned from package 'linux-image-2.6.32-5-686-bigmem' to 'src:linux-2.6'. No longer marked as found in versions linux-2.6/2.6.32-41squeeze2. Ignoring request to alter fixed versions of bug #669335 to the same values previously set Bug #669335 [src:linux-2.6] linux-image-2.6.32-5-686-bigmem: 86-mm-Fix-pgd_lock-deadlock.patch Marked as found in versions linux-2.6/2.6.32-41squeeze2. tags 669335 + upstream patch Bug #669335 [src:linux-2.6] linux-image-2.6.32-5-686-bigmem: 86-mm-Fix-pgd_lock-deadlock.patch Added tag(s) upstream and patch. quit Stopping processing here. Please contact me if you need assistance. -- 669335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.133485116431273.transcr...@bugs.debian.org
Processed: Re: pa can't handle multiple HDMI devices -- chooses wrong default
Processing commands for cont...@bugs.debian.org: # Andres Cimmarusti wrote: # tags 664653 fixed-upstream # # Yep. tags 660111 - fixed-upstream Bug #660111 [linux-2.6] multiple, non-physically accesible, HDMI devices Removed tag(s) fixed-upstream. End of message, stopping processing here. Please contact me if you need assistance. -- 660111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.1334851500948.transcr...@bugs.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #616559 (http://bugs.debian.org/616559) # Bug title: BUG: soft lockup - CPU#1 stuck for 63s! [upowerd:7967] # * http://bugzilla.kernel.org/show_bug.cgi?id=43020 # * remote status changed: ASSIGNED - NEEDINFO usertags 616559 - status-ASSIGNED usertags 616559 + status-NEEDINFO # remote status report for #658662 (http://bugs.debian.org/658662) # Bug title: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 # * https://bugs.freedesktop.org/show_bug.cgi?id=45801 # * remote status changed: NEW - REOPENED usertags 658662 - status-NEW usertags 658662 + status-REOPENED thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120419163729.1440.15295.btsl...@busoni.debian.org
Bug#667446: closed by Ben Hutchings b...@decadent.org.uk (Bug#667446: fixed in linux-2.6 3.2.15-1)
On Sun, Apr 15, 2012 at 8:54 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: This is an automatic notification regarding your Bug report which was filed against the linux-2.6 package: #667446: linux-image-3.2.0-2-orion5x: leds-gpio fails on MV2120 It has been closed by Ben Hutchings b...@decadent.org.uk. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Ben Hutchings b...@decadent.org.uk by replying to this email. -- 667446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems Verified correct operation on device. Thank you for fixing this so fast. -- Henry von Tresckow (hvontres) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caea7u+kqutalrq22_dzscibwpyvxjpunycuqq7jupyhaam6...@mail.gmail.com
Bug#665881: [3.1 - 3.2.12 regression] module ath5k is blocking wlan-card
Hi Jonathan, today I tested with the old bpo-kernel, but sadly I could not manage to get this bug shown again, neither with pcie= nor without pcie= addition. But what i can say: This bug is gone! I have now rebooted almost 20 times and it never appeared a single time. IMO that bugreport can safely be closed (I think, it is already). It is a pity, I can give no other answer, but all my tests to reproduce the bug with the older kernel failed. However, I have already updated some software around it, for example some libs. My system (debian-amd/testing) is beeig updated nearly daily, so I can see bugs very fast. This is in one way good, on the other way it might be bad (like this time). Thank you for your help anyway. I hope, I can help next time better. Best regards Hans -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201204192122.21656.hans.ullr...@loop.de
Bug#665881: [3.1 - 3.2.12 regression] module ath5k is blocking wlan-card
unmerge 665881 notforwarded 665881 notfixed 665881 linux-2.6/3.2.14-1 , linux-2.6/3.3.2-1~experimental.1 tags 665881 = upstream unreproducible quit Hans-J. Ullrich wrote: Hi Jonathan, today I tested with the old bpo-kernel, but sadly I could not manage to get this bug shown again Thanks again. So we are back where we were. :) Sorry for my sloppiness. I'm keeping the bug closed and marked unreproducible, so we can pick up where we left off when it happens again. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120419195147.GA2429@burratino
Processed: Re: [3.1 - 3.2.12 regression] module ath5k is blocking wlan-card
Processing commands for cont...@bugs.debian.org:
unmerge 665881
Bug #665881 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.2.0-2-amd64: module ath5k is blocking wlan-card
Bug #665420 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.2.0-2-686-pae: pata_jmicron hdd/dvd/cdrom drives not detected,
gave up waiting for root device
Bug #666537 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.3.0-trunk-amd64: Kernel panic at beginning of boot
Bug #666873 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.2.0-2-amd64: kernel panics immediately on boot
Disconnected #665881 from all other report(s).
notforwarded 665881
Bug #665881 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.2.0-2-amd64: module ath5k is blocking wlan-card
Unset Bug forwarded-to-address
notfixed 665881 linux-2.6/3.2.14-1 , linux-2.6/3.3.2-1~experimental.1
Bug #665881 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.2.0-2-amd64: module ath5k is blocking wlan-card
No longer marked as fixed in versions linux-2.6/3.2.14-1 and
linux-2.6/3.3.2-1~experimental.1.
tags 665881 = upstream unreproducible
Bug #665881 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.2.0-2-amd64: module ath5k is blocking wlan-card
Added tag(s) unreproducible; removed tag(s) fixed-upstream and patch.
quit
Stopping processing here.
Please contact me if you need assistance.
--
665420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665420
665881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665881
666537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666537
666873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.133486512510953.transcr...@bugs.debian.org
Bug#666108: Dell PERC H710P is not supported by Squeeze Standard Kernel
Hi, Buford Peek wrote: So far everything is looking good..We do NOT run a stock config so I have recompiled the kernel with our specific config and will run LTP testing on the system to determine if their are any more issues. Thanks again. How did it go? (Ben, if it worked well for them then I think we should take these patches in s-p-u right after the next point release and see if anyone screams. Or sooner, if we can get someone at Dell or LSI to look over the list of patches or can get confidence some other way, like comparing to what Red Hat uses.) Curious, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120419223709.GA4904@burratino
RE: Basic question on debian kernel versions
On Thu, 2012-04-19 at 00:55 -0700, sarveshwar.ba...@emulex.com wrote: Ben, Thanks that clarifies a lot. I do intend to provide updates to driver. Some quick questions. I know need to figure this myself but am running round In circles. - Can you give me a pointer to latest debian kernel tree? I assume I will be able figure out the latest commit id that was taken for debian from that. Depending on which form you prefer to work with, you can use: 1. A git repository containing branches tracking each of the releases/suites. This is *not* the working repository (that's option 2) and is not always up-to-date, but may be preferable as a way to view and prepare patches: http://anonscm.debian.org/gitweb/?p=kernel/linux-2.6.git 2. The source package 'linux-2.6' contains upstream source and all the patches we apply to it. You can check out the development branch for each release/suite with Subversion: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official-vcs 3. The package 'linux-source-2.6.32' or 'linux-source-3.2' (depending on which release you are targetting) contains the source with all Debian patches applied: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-getting - Is it sufficient to give you commit id (from net-next) that need to be taken into debian or do I need to give patches Against the latest tree? If the driver source in net-next can just be dropped into the older kernel version and still work, then the commit ID is probably OK. But very often that isn't the case due to API changes (and I can't believe it's true for Debian 6.0, i.e. Linux 2.6.32). I personally prefer to see a patch series with upstream references (as you see in the kernel.org stable/longterm branches) and any necessary fix-ups for API differences made in those individual patches. As an example, see my own backport of tg3 at http://anonscm.debian.org/gitweb/?p=kernel/linux-2.6.git;a=shortlog;h=refs/heads/squeeze;pg=1. It's OK to backport the addition of new functions, e.g. the series of commits 'net: Add netdev_alloc_skb_ip_align() helper' up to 'err.h: add helper function to simplify pointer error checking' that you can see at http://anonscm.debian.org/gitweb/?p=kernel/linux-2.6.git;a=shortlog;h=refs/heads/squeeze;pg=7. But this has to be done with care to avoid affecting other drivers! - Whats the process, Do I just post these on this list or do I need to open bugs first? Or just point me to a faq. Do open a bug, requesting addition of new hardware support. Start with: Package: src:linux-2.6 Version: current version Severity: important If you want Debian 6.0 to be updated then specify the latest version there (2.6.32-43); if you only want this to go into Debian 7.0 then specify the latest version there (3.2.15-1). Patches should be sent to the bug address, which will forward to the debian-kernel mailing list. If you end up with a very long patch series it may be better to send it as a tarball. But if there's any thing that needs significant changes in the process of backporting, it might still be worth sending that individually so it's easier to review. Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't. signature.asc Description: This is a digitally signed message part
Bug#669335: linux-image-2.6.32-5-686-bigmem: 86-mm-Fix-pgd_lock-deadlock.patch
On Thu, 2012-04-19 at 08:48 +0200, Philipp Hahn wrote: [...] I thinks this patch should be applied to all flavours. It doesn't apply to the non-xen-flavour as is, because it depends on some other xen-related patch. Agreed. The Patch was also back-ported to the OpenSUSE Kernel http://kernel.opensuse.org/cgit/kernel-source/commit/?id=ac27c01aa880c65d17043ab87249c613ac4c3635, but since the patch is trivial to backport, I'll attach my version as well. [...] Well, it's not *that* trivial. As Jonathan said, please do send this to sta...@vger.kernel.org. Add the upstream commit ID, a note that you did the backport, and your Signed-off-by line (as you'll see in some other commits on the longterm branch). Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't. signature.asc Description: This is a digitally signed message part
