Bug#666556: Please enable Intel Sandy-Bridge Integrated MC CONFIG_EDAC_SBRIDGE
On Sat, 2012-03-31 at 19:30 +0200, Carlos Alberto Lopez Perez wrote: Source: linux-2.6 Version: 3.2.12-1 Severity: normal Hello, Please enable the support for the Intel Sandy-Bridge memory controller for EDAC so we can take advantage of ECC ram modules on this platform. As you may know, EDAC is not required for ECC. It does improve error reporting and helps you to identify faulty modules. Just set CONFIG_EDAC_SBRIDGE=m in the .config The driver is marked as experimental and there are several important bug fixes post-3.2. If we enable it, we also need to apply those bug fixes and possibly others. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#666568: [acer_wmi] rfkill blocks WLAN on Sony VAIO VPCYA1V9E, regardless of hardware switch
Jonathan Nieder jrnie...@gmail.com writes: Please test the attached patch, following instructions from [1] or the following instructions: Thank you; I didn't realize this had already been fixed upstream. stable/linux-3.2.y was v3.2.13 = 02905906ddc049720ded93ded03bbc2652f4646a. That version has the bug; acer-wmi blocks WLAN on my VAIO as reported. Cherry-picking 5719b81988f3c24ff694dc3a37e35b35630a3966 fixes it. I deviated from your instructions by not using -s in git cherry-pick. pgpoIZIl4zFlf.pgp Description: PGP signature
Bug#666386: igb + bnx2 + ifenslave + brctl + vconfig = largely broken
On Sun, Apr 01, 2012 at 03:09:56AM +0100, Ben Hutchings wrote: I bet this is due to the combination of LRO plus bridging. We try to turn off LRO in devices under a bridge, but that won't work if there's an intermediate bonding device. If you run: # ethtool -K eth0 lro off # ethtool -K eth2 lro off does the bridge start working? Err... % sudo ethtool -K eth0 lro off Cannot set large receive offload settings: Operation not supported % sudo ethtool -K eth2 lro off Cannot set large receive offload settings: Operation not supported That's with eth0 removed from bonding, and eth2 inside. -- 2. That which causes joy or happiness. -- 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/20120401104044.ga28...@entuzijast.net
Bug#665881: [3.1 - 3.2.12 regression] module ath5k is blocking wlan-card
Made some new tests! When the wlan-hardware is set by the kernel, also Windows-XP will not see the card. So it is proven: The kernel is setting my wlancard into some mode, which can only be reset, when I take completely the power off the notebook. Reinitialisation through a reboot or by reloading the kernel-module does not work. Greets 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/201204011437.27078.hans.ullr...@loop.de
Can I 'fool' the uname command??
Okay - I am attempting to compile on a shared (virtual host) machine When I use the uname -a command, it displays the following: Linux ps91497 3.1.9-vs2.3.2.5 #1 SMP Thu Jan 26 02:37:05 UTC 2012 x86_64 GNU/Linux /usr/src/linux-source-3.2 is where I downloaded the sources: root@ps91497:/usr/src/linux-source-3.2# dpkg-query -l linux-source Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/ trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===- ===- == ii linux-source3.2+44~bpo60+1 Linux kernel source (meta-package) root@ps91497:/usr/src/linux-source-3.2# dpkg-query -s linux-source Package: linux-source Status: install ok installed Priority: optional Section: kernel Installed-Size: 32 Maintainer: Debian Kernel Team Architecture: all Source: linux-latest (44~bpo60+1) Version: 3.2+44~bpo60+1 Depends: linux-source-3.2 Description: Linux kernel source (meta-package) This package depends on packages containing the sources of the latest Linux kernel. So, to build this software package that I need - I need to convince the compiler that these are my kernel sources. Any simple way to do this? I don't want to mess with environment variables, I just want to get the software built. Any helpful hints would be much appreciated.
Re: Can I 'fool' the uname command??
In general, you can 'fool' the uname command (with LD_PRELOAD) but it probably won't solve the problem. On Sun, 2012-04-01 at 12:40 -0400, Glen Millard wrote: Okay - I am attempting to compile on a shared (virtual host) machine When I use the uname -a command, it displays the following: Linux ps91497 3.1.9-vs2.3.2.5 #1 SMP Thu Jan 26 02:37:05 UTC 2012 x86_64 GNU/Linux /usr/src/linux-source-3.2 is where I downloaded the sources: [...] So, to build this software package that I need - I need to convince the compiler that these are my kernel sources. [...] What does it need from the kernel source? You certainly can't build a useful kernel module this way (nor would you be permitted to load it anyway). Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#665420: [3.2.11 - 3.2.12 regression] pata_jmicron hdd/dvd/cdrom drives not detected, gave up waiting for root device
tags 665420 + fixed-upstream quit Fixed during the v3.4 merge window by commit c9651e70ad0a, and the patch is queued for 3.2.14 or 3.2.15. -- 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/20120401180444.GA20395@burratino
Processed: Re: [3.2.11 - 3.2.12 regression] pata_jmicron hdd/dvd/cdrom drives not detected, gave up waiting for root device
Processing commands for cont...@bugs.debian.org: tags 665420 + fixed-upstream Bug #665420 [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 Added tag(s) fixed-upstream. quit Stopping processing here. Please contact me if you need assistance. -- 665420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665420 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.10349726607.transcr...@bugs.debian.org
Processed: tagging 647750
Processing commands for cont...@bugs.debian.org: tags 647750 - moreinfo Bug #647750 [linux-source-2.6.32] linux-source-2.6.32: keyboard.c: 8 bits diacritics are displayed as a 7 bits representation after a space Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 647750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647750 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.1049572424.transcr...@bugs.debian.org
Bug#659363: Hibernate freezes on HP dc7900 with Linux 3.2 (regression)
It seems I am seeing the same bug too, on linux-image-3.2.0-0.bpo.1-686-pae, 3.2.4-1~bpo60+1. However, I'm on an nVidia nForce 570 chipset (AMD A64-x2), esp. using the sata_nv driver. About half of the hibernate-disk cycles do work, the other half starts writing the image to some point just normally, but after a few seconds the disk writer gets extremely slow (around 1% per minute), and after some more minutes, the kernel throws page allocation failures: [16095.943147] echo: page allocation failure: order:0, mode:0x20 [16095.945176] kthreadd: page allocation failure: order:0, mode:0x20 [16095.945180] Pid: 2, comm: kthreadd Not tainted 3.2.0-0.bpo.1-686-pae #1 [16095.945182] Call Trace: [16095.945189] [c10a1284] ? warn_alloc_failed+0xc0/0xd1 [16095.945192] [c10a236b] ? __alloc_pages_nodemask+0x55e/0x5cb [16095.945195] [c10a9959] ? shrink_zone+0x440/0x44c [16095.945199] [c10ca0aa] ? cache_alloc+0x25d/0x406 [16095.945201] [c10ca343] ? kmem_cache_alloc_trace+0x3c/0x7b [16095.945204] [c10f019d] ? __bdi_start_writeback+0x23/0x90 [16095.945206] [c10f0257] ? wakeup_flusher_threads+0x4d/0x64 [16095.945208] [c10a9f52] ? do_try_to_free_pages+0x2d4/0x403 [16095.945210] [c10aa28a] ? try_to_free_pages+0x9f/0xcd [16095.945213] [c10a21d0] ? __alloc_pages_nodemask+0x3c3/0x5cb [16095.945217] [c103a29b] ? copy_process+0xc5/0xdf1 [16095.945220] [c100baa9] ? __switch_to+0x6f/0xe2 [16095.945223] [c103b157] ? do_fork+0xbb/0x1d0 [16095.945226] [c10514fc] ? kthread_worker_fn+0x114/0x114 [16095.945229] [c101186f] ? kernel_thread+0x7b/0x83 [16095.945231] [c10514fc] ? kthread_worker_fn+0x114/0x114 [16095.945234] [c12d2c78] ? common_interrupt+0x38/0x38 [16095.945237] [c105160e] ? kthreadd+0xaa/0xdc [16095.945239] [c1051564] ? kthread+0x68/0x68 [16095.945241] [c12d2c7e] ? kernel_thread_helper+0x6/0x10 [16095.945242] Mem-Info: [16095.945243] DMA per-cpu: [16095.945245] CPU0: hi:0, btch: 1 usd: 0 [16095.945246] CPU1: hi:0, btch: 1 usd: 0 [16095.945247] Normal per-cpu: [16095.945249] CPU0: hi: 186, btch: 31 usd: 21 [16095.945250] CPU1: hi: 186, btch: 31 usd: 1 [16095.945251] HighMem per-cpu: [16095.945253] CPU0: hi: 186, btch: 31 usd: 0 [16095.945254] CPU1: hi: 186, btch: 31 usd: 0 [16095.945258] active_anon:30380 inactive_anon:864 isolated_anon:0 [16095.945259] active_file:112988 inactive_file:128220 isolated_file:0 [16095.945259] unevictable:0 dirty:0 writeback:0 unstable:0 [16095.945260] free:226695 slab_reclaimable:11024 slab_unreclaimable:15456 [16095.945261] mapped:13381 shmem:931 pagetables:959 bounce:0 [16095.945266] DMA free:16kB min:784kB low:980kB high:1176kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15792kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:4220kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [16095.945270] lowmem_reserve[]: 0 867 4039 4039 [16095.945275] Normal free:0kB min:44112kB low:55140kB high:66168kB active_anon:0kB inactive_anon:0kB active_file:1148kB inactive_file:1148kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:887976kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:44096kB slab_unreclaimable:57604kB kernel_stack:2000kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:220064075 all_unreclaimable? no [16095.945279] lowmem_reserve[]: 0 0 25378 25378 [16095.945285] HighMem free:906764kB min:512kB low:40856kB high:81204kB active_anon:121520kB inactive_anon:3456kB active_file:450804kB inactive_file:511732kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:3248468kB mlocked:0kB dirty:0kB writeback:0kB mapped:53520kB shmem:3724kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:3836kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [16095.945288] lowmem_reserve[]: 0 0 0 0 [16095.945290] DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 0kB [16095.945295] Normal: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 0kB [16095.945299] HighMem: 22355*4kB 16232*8kB 6812*16kB 2330*32kB 612*64kB 405*128kB 133*256kB 24*512kB 12*1024kB 7*2048kB 83*4096kB = 906764kB [16095.945305] 242139 total pagecache pages [16095.945306] 0 pages in swap cache [16095.945307] Swap cache stats: add 0, delete 0, find 0/0 [16095.945308] Free swap = 3715540kB [16095.945309] Total swap = 4194300kB [16095.948007] 1318896 pages RAM [16095.948007] 1091074 pages HighMem [16095.948007] 282321 pages reserved [16095.948007] 156789 pages shared [16095.948007] 702774 pages non-shared More netconsole output attached. The output matches the screenshot that was
Bug#666568: [acer_wmi] rfkill blocks WLAN on Sony VAIO VPCYA1V9E, regardless of hardware switch
tags 666568 - moreinfo quit Kalle Olavi Niemitalo wrote: stable/linux-3.2.y was v3.2.13 = 02905906ddc049720ded93ded03bbc2652f4646a. That version has the bug; acer-wmi blocks WLAN on my VAIO as reported. Cherry-picking 5719b81988f3c24ff694dc3a37e35b35630a3966 fixes it. Thanks for checking. Passed upstream so hopefully this fix will be part of gregkh's 3.2.y kernels soon. -- 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/20120401185517.GL2059@burratino
Processed: Re: [acer_wmi] rfkill blocks WLAN on Sony VAIO VPCYA1V9E, regardless of hardware switch
Processing commands for cont...@bugs.debian.org: tags 666568 - moreinfo Bug #666568 [linux-2.6] [acer_wmi] rfkill blocks WLAN on Sony VAIO VPCYA1V9E, regardless of hardware switch Removed tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 666568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666568 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.10652610132.transcr...@bugs.debian.org
Bug#666781: linux-image-2.6.32-5-amd64: can't mount cdrom (/dev/sr0)
Package: linux-2.6 Version: 2.6.32-41squeeze2 Severity: normal root@hsctb:/etc# mount /dev/sr0 /media/cdrom0 mount: /dev/sr0: unknown device that is what returns when manually mounting. I don't see anything if I just insert a cd... -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-41squeeze2) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Mar 22 17:26:33 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=5915530d-4e98-4979-86ae-72de126c51ab ro quiet ** Tainted: P (1) * Proprietary module has been loaded. ** Kernel log: [350012.453280] usb 1-3.2: usbfs: interface 1 claimed by usblp while 'usb' sets config #1 [350012.460801] usb 1-3.1.1: usbfs: interface 0 claimed by usblp while 'usb' sets config #1 [350094.146126] usb 1-3.2: USB disconnect, address 8 [350094.146596] usblp0: removed [350094.361323] usb 1-3.2: new high speed USB device using ehci_hcd and address 9 [350094.461551] usb 1-3.2: New USB device found, idVendor=03f0, idProduct=5c11 [350094.461556] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [350094.461560] usb 1-3.2: Product: Photosmart C4200 series [350094.461562] usb 1-3.2: Manufacturer: HP [350094.461565] usb 1-3.2: SerialNumber: CN78EJG16C04VP [350094.461695] usb 1-3.2: configuration #1 chosen from 1 choice [350094.462356] usblp0: USB Bidirectional printer dev 9 if 1 alt 0 proto 2 vid 0x03F0 pid 0x5C11 [350094.466260] scsi318 : SCSI emulation for USB Mass Storage devices [350094.466419] usb-storage: device found at 9 [350094.466423] usb-storage: waiting for device to settle before scanning [350095.882865] usb 1-3.2: usbfs: interface 1 claimed by usblp while 'usb' sets config #1 [350095.898726] usb 1-3.1.1: usbfs: interface 0 claimed by usblp while 'usb' sets config #1 [350099.265581] usb 1-3.2: USB disconnect, address 9 [350099.266052] usblp0: removed [350099.469041] usb 1-3.2: new high speed USB device using ehci_hcd and address 10 [350099.564881] usb 1-3.2: New USB device found, idVendor=03f0, idProduct=5c11 [350099.564892] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [350099.564901] usb 1-3.2: Product: Photosmart C4200 series [350099.564907] usb 1-3.2: Manufacturer: HP [350099.564912] usb 1-3.2: SerialNumber: CN78EJG16C04VP [350099.565165] usb 1-3.2: configuration #1 chosen from 1 choice [350099.566506] usblp0: USB Bidirectional printer dev 10 if 1 alt 0 proto 2 vid 0x03F0 pid 0x5C11 [350099.567081] scsi319 : SCSI emulation for USB Mass Storage devices [350099.567480] usb-storage: device found at 10 [350099.567485] usb-storage: waiting for device to settle before scanning [350104.565935] usb-storage: device scan complete [350104.567267] scsi 319:0:0:0: Direct-Access HP Photosmart C4250 1.00 PQ: 0 ANSI: 5 [350104.568648] sd 319:0:0:0: Attached scsi generic sg3 type 0 [350104.576664] sd 319:0:0:0: [sdc] Attached SCSI removable disk [350108.224737] usb 1-3.2: USB disconnect, address 10 [350108.225123] usblp0: removed [350108.385727] hub 1-3:1.0: unable to enumerate USB device on port 2 [350108.680938] usb 1-3.2: new high speed USB device using ehci_hcd and address 12 [350108.698840] hub 1-3:1.0: unable to enumerate USB device on port 2 [350108.937406] usb 1-3.2: new high speed USB device using ehci_hcd and address 13 [350109.032680] usb 1-3.2: New USB device found, idVendor=03f0, idProduct=5c11 [350109.032691] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [350109.032699] usb 1-3.2: Product: Photosmart C4200 series [350109.032705] usb 1-3.2: Manufacturer: HP [350109.032710] usb 1-3.2: SerialNumber: CN78EJG16C04VP [350109.032952] usb 1-3.2: configuration #1 chosen from 1 choice [350109.035621] usblp0: USB Bidirectional printer dev 13 if 1 alt 0 proto 2 vid 0x03F0 pid 0x5C11 [350109.036068] scsi320 : SCSI emulation for USB Mass Storage devices [350109.036370] usb-storage: device found at 13 [350109.036377] usb-storage: waiting for device to settle before scanning [350112.320966] usb 1-3.2: usbfs: interface 1 claimed by usblp while 'usb' sets config #1 [350112.332703] usb 1-3.1.1: usbfs: interface 0 claimed by usblp while 'usb' sets config #1 [350114.037612] usb-storage: device scan complete [350114.040371] scsi 320:0:0:0: Direct-Access HP Photosmart C4250 1.00 PQ: 0 ANSI: 5 [350114.043925] sd 320:0:0:0: Attached scsi generic sg3 type 0 [350114.052490] sd 320:0:0:0: [sdc] Attached SCSI removable disk [350468.121781] usb 1-3.2: USB disconnect, address 13 [350468.122264] usblp0: removed [350468.273867] hub 1-3:1.0: unable to enumerate USB device on port 2 [350468.589529] usb 1-3.2: new high speed USB device using ehci_hcd and address 15 [350468.606263] hub 1-3:1.0: unable to enumerate USB device on port 2 [350468.834206] usb 1-3.2: new high speed USB device using ehci_hcd and address 16 [350468.928413] usb 1-3.2: New USB device found, idVendor=03f0, idProduct=5c11 [350468.928424] usb 1-3.2: New USB device
Bug#659363: Hibernate freezes on HP dc7900 with Linux 3.2 (regression)
Hi Udo,
Udo Richter wrote:
It seems I am seeing the same bug too
Please test the attached patch[2], for example by following the following
instructions:
0. Prerequisites.
apt-get install git build-essential
1. Get a copy of the kernel history if you don't already have it.
git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
2. Fetch point releases.
cd linux
git remote add -f stable \
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
3. Configure, build, and test.
cp /boot/config-$(uname -r) .config; # current configuration
make localmodconfig; # optional: minimize configuration
make deb-pkg; # optionally with -jnum for parallel build
dpkg -i ../name of package; # as root
reboot
... test test test ...
4. Hopefully it reproduces the bug. Try the patch:
git am -3sc path to patch
make deb-pkg; # maybe with -j4
dpkg -i ../name of package; # as root
reboot
... test test test ...
An alternative method for testing patches is described at [1].
Hope that helps,
Jonathan
[1]
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
or the corresponding page from the debian-kernel-handbook package
[2] from http://thread.gmane.org/gmane.linux.kernel/1273425
From: Bojan Smojver bo...@rexursive.com
Date: Wed, 28 Mar 2012 10:41:12 +1100
Subject: Hibernation: lower/better control the amount of pages used for buffering
Hibernation/thaw improvements:
1. Set maximum number of pages for read buffering consistently, instead
of inadvertently depending on the size of the sector type.
2. Use at most one quarter of free pages for read buffering.
3. Require that number of free pages when writing the image never falls
below three quarters of total free pages available.
Signed-off-by: Bojan Smojver bo...@rexursive.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
kernel/power/swap.c | 35 ---
1 file changed, 24 insertions(+), 11 deletions(-)
diff --git a/kernel/power/swap.c b/kernel/power/swap.c
index 11a594c4ba25..c0ff52e0bb19 100644
--- a/kernel/power/swap.c
+++ b/kernel/power/swap.c
@@ -6,7 +6,7 @@
*
* Copyright (C) 1998,2001-2005 Pavel Machek pa...@ucw.cz
* Copyright (C) 2006 Rafael J. Wysocki r...@sisk.pl
- * Copyright (C) 2010 Bojan Smojver bo...@rexursive.com
+ * Copyright (C) 2010-2012 Bojan Smojver bo...@rexursive.com
*
* This file is released under the GPLv2.
*
@@ -52,6 +52,15 @@
#define MAP_PAGE_ENTRIES (PAGE_SIZE / sizeof(sector_t) - 1)
+/*
+ * Number of pages required to be kept free while writing the image. Always
+ * three quarters of all available pages before the writing starts.
+ */
+static inline unsigned long reqd_free_pages(void)
+{
+ return (nr_free_pages() / 4) * 3;
+}
+
struct swap_map_page {
sector_t entries[MAP_PAGE_ENTRIES];
sector_t next_swap;
@@ -73,7 +82,7 @@ struct swap_map_handle {
sector_t cur_swap;
sector_t first_sector;
unsigned int k;
- unsigned long nr_free_pages, written;
+ unsigned long reqd_free_pages;
u32 crc32;
};
@@ -317,8 +326,7 @@ static int get_swap_writer(struct swap_map_handle *handle)
goto err_rel;
}
handle-k = 0;
- handle-nr_free_pages = nr_free_pages() 1;
- handle-written = 0;
+ handle-reqd_free_pages = reqd_free_pages();
handle-first_sector = handle-cur_swap;
return 0;
err_rel:
@@ -353,11 +361,15 @@ static int swap_write_page(struct swap_map_handle *handle, void *buf,
handle-cur_swap = offset;
handle-k = 0;
}
- if (bio_chain ++handle-written handle-nr_free_pages) {
+ if (bio_chain nr_free_pages() handle-reqd_free_pages) {
error = hib_wait_on_bio_chain(bio_chain);
if (error)
goto out;
- handle-written = 0;
+ /*
+ * Recalculate the number of required free pages, to make sure
+ * we never take more than a quarter.
+ */
+ handle-reqd_free_pages = reqd_free_pages();
}
out:
return error;
@@ -405,7 +417,7 @@ static int swap_writer_finish(struct swap_map_handle *handle,
#define LZO_THREADS 3
/* Maximum number of pages for read buffering. */
-#define LZO_READ_PAGES (MAP_PAGE_ENTRIES * 8)
+#define LZO_READ_PAGES 8192
/**
@@ -616,10 +628,10 @@ static int save_image_lzo(struct swap_map_handle *handle,
}
/*
- * Adjust number of free pages after all allocations have been done.
- * We don't want to run out of pages when writing.
+ * Adjust the number of required free pages after all allocations have
+ * been done. We don't want to run out of pages when writing.
*/
- handle-nr_free_pages = nr_free_pages() 1;
+ handle-reqd_free_pages = reqd_free_pages();
/*
* Start the CRC32 thread.
@@ -1129,8 +1141,9 @@ static int load_image_lzo(struct swap_map_handle *handle,
/*
* Adjust number of pages for read buffering, in case we are short.
+ * Never take more than a quarter of all available pages.
*/
- read_pages =
Bug#584881: Lockups under heavy disk IO; md (RAID) resync/check implicated
There is a change in Linux 3.3, also intended to go into Linux 3.2.14,
which looks like a fix for bug #584881.
I'm attaching a backported version of this bug fix for Debian 6.0
'squeeze', which you may wish to test. You can build a kernel package
with this patch by following the instructions at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.
Note that no further bug fixes will be made in Debian 5.0 'lenny'.
Ben.
--
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett
From: NeilBrown ne...@suse.de
Date: Mon, 19 Mar 2012 12:46:38 +1100
Subject: [PATCH] md/raid1,raid10: avoid deadlock during resync/recovery.
commit d6b42dcb995e6acd7cc276774e751ffc9f0ef4bf upstream.
If RAID1 or RAID10 is used under LVM or some other stacking
block device, it is possible to enter a deadlock during
resync or recovery.
This can happen if the upper level block device creates
two requests to the RAID1 or RAID10. The first request gets
processed, blocks recovery and queue requests for underlying
requests in current-bio_list. A resync request then starts
which will wait for those requests and block new IO.
But then the second request to the RAID1/10 will be attempted
and it cannot progress until the resync request completes,
which cannot progress until the underlying device requests complete,
which are on a queue behind that second request.
So allow that second request to proceed even though there is
a resync request about to start.
This is suitable for any -stable kernel.
Cc: sta...@vger.kernel.org
Reported-by: Ray Morris supp...@bettercgi.com
Tested-by: Ray Morris supp...@bettercgi.com
Signed-off-by: NeilBrown ne...@suse.de
[bwh: Backport to 2.6.32:
- Test for non-empty BIO queue is current-bio_list current-bio_tail
- Adjust context]
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
--- a/drivers/md/raid1.c
+++ b/drivers/md/raid1.c
@@ -688,7 +688,20 @@ static void wait_barrier(struct r1conf *conf)
spin_lock_irq(conf-resync_lock);
if (conf-barrier) {
conf-nr_waiting++;
- wait_event_lock_irq(conf-wait_barrier, !conf-barrier,
+ /* Wait for the barrier to drop.
+ * However if there are already pending
+ * requests (preventing the barrier from
+ * rising completely), and the
+ * pre-process bio queue isn't empty,
+ * then don't wait, as we need to empty
+ * that queue to get the nr_pending
+ * count down.
+ */
+ wait_event_lock_irq(conf-wait_barrier,
+!conf-barrier ||
+(conf-nr_pending
+ current-bio_list
+ current-bio_tail),
conf-resync_lock,
raid1_unplug(conf-mddev-queue));
conf-nr_waiting--;
--- a/drivers/md/raid10.c
+++ b/drivers/md/raid10.c
@@ -734,7 +734,20 @@ static void wait_barrier(struct r10conf *conf)
spin_lock_irq(conf-resync_lock);
if (conf-barrier) {
conf-nr_waiting++;
- wait_event_lock_irq(conf-wait_barrier, !conf-barrier,
+ /* Wait for the barrier to drop.
+ * However if there are already pending
+ * requests (preventing the barrier from
+ * rising completely), and the
+ * pre-process bio queue isn't empty,
+ * then don't wait, as we need to empty
+ * that queue to get the nr_pending
+ * count down.
+ */
+ wait_event_lock_irq(conf-wait_barrier,
+!conf-barrier ||
+(conf-nr_pending
+ current-bio_list
+ current-bio_tail),
conf-resync_lock,
raid10_unplug(conf-mddev-queue));
conf-nr_waiting--;
signature.asc
Description: This is a digitally signed message part
Processed: tagging 584881
Processing commands for cont...@bugs.debian.org: tags 584881 + patch Bug #584881 [linux-2.6] Lockups under heavy disk IO; md (RAID) resync/check implicated Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 584881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584881 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.1112361188.transcr...@bugs.debian.org
Bug#665881: not Debian-specific
I have just compiled a custom 3.3.0 kernel for an Acer netbook, previously running 3.0.0, and see the same problem as reported by Hans. In my case, after 36 hours of uptime with the new kernel, the ath5k began to report constant gain calibration timeout errors and connectivity was lost. Rebooting with the previous kernel without powering off did not restore wireless connectivity. The old ath5k was reporting gain calibration timeout too. Powering off and on, and booting the old 3.0 kernel seems to have restored correct functionality. Just to be clear, both kernels are compiled from source from kernel.org, not Debian builds. Steve -- 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/4f78b5f4.5030...@annaghvarn.plus.com
Re: Can I 'fool' the uname command??
Reply to all (or to the list), not just to me. On Sun, 2012-04-01 at 14:24 -0400, Glen Millard wrote: Okay - any other suggestions? Well you could answer my question: I wrote: What does it need from the kernel source? You certainly can't build a useful kernel module this way (nor would you be permitted to load it anyway). Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#666781: linux-image-2.6.32-5-amd64: can't mount cdrom (/dev/sr0)
On Sun, 2012-04-01 at 14:32 -0500, Abel McClendon wrote: Package: linux-2.6 Version: 2.6.32-41squeeze2 Severity: normal Is this a regression from an earlier version? root@hsctb:/etc# mount /dev/sr0 /media/cdrom0 mount: /dev/sr0: unknown device that is what returns when manually mounting. I don't see anything if I just insert a cd... [...] Do you know what interface the CD/DVD drive is attached to (SATA or PATA)? Please send the contents of the files /var/log/dmesg and /proc/partitions. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Processed: tagging 666781
Processing commands for cont...@bugs.debian.org: tags 666781 + moreinfo Bug #666781 [linux-2.6] linux-image-2.6.32-5-amd64: can't mount cdrom (/dev/sr0) Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 666781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666781 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.1128248282.transcr...@bugs.debian.org
Bug#665881: ath5k reports gain calibration timeout errors and loses connectivity (Re: not Debian-specific)
Steve Graham wrote: [Subject: Bug#665881: not Debian-specific] Please keep in mind that these messages appear as emails in a crowded inbox, so the subject line can be a good place to put valuable context. I have just compiled a custom 3.3.0 kernel for an Acer netbook, previously running 3.0.0, and see the same problem as reported by Hans. In my case, after 36 hours of uptime with the new kernel, the ath5k began to report constant gain calibration timeout errors and connectivity was lost. Rebooting with the previous kernel without powering off did not restore wireless connectivity. The old ath5k was reporting gain calibration timeout too. Powering off and on, and booting the old 3.0 kernel seems to have restored correct functionality. Thanks! This agrees with Hans's observations, too. Please send a summary of your observations to linux-wirel...@vger.kernel.org, cc-ing Hans, ath5k-de...@lists.ath5k.org, and either me or this bug log so we can track it. Be sure to mention: - precise steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple in this case) - how reproducible and how quickly reproducible it is (e.g., within 5 hours 50% of the time?) - which kernel versions you have tested and what happened with each - full dmesg output from a working and a non-working boot, as attachments - a pointer to http://bugs.debian.org/665881 for the backstory - any workarounds or other weird observations Hopefully someone upstream may have ideas for commands or patches to try in order to narrow down the problem. Thanks and hope that helps, 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/20120401205238.GC20883@burratino
Processed: Re: ath5k reports gain calibration timeout errors and loses connectivity (Re: not Debian-specific)
Processing commands for cont...@bugs.debian.org: found 665881 linux-2.6/3.3-1~experimental.1 Bug #665881 [linux-2.6] linux-image-3.2.0-2-amd64: module ath5k is blocking wlan-card Marked as found in versions linux-2.6/3.3-1~experimental.1. tags 665881 + upstream Bug #665881 [linux-2.6] linux-image-3.2.0-2-amd64: module ath5k is blocking wlan-card Added tag(s) upstream. End of message, stopping processing here. Please contact me if you need assistance. -- 665881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665881 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.11364811309.transcr...@bugs.debian.org
Re: Can I 'fool' the uname command??
Sorry - my mistake. I need to build Vicidial installation on a Dreamhost server. root@ps91497:/usr/local/src/dahdi-linux-complete-2.3.0.1+2.3.0# make make -C linux all make[1]: Entering directory `/usr/local/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux' make -C drivers/dahdi/firmware firmware-loaders make[2]: Entering directory `/usr/local/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/firmware' make[2]: Leaving directory `/usr/local/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/firmware' You do not appear to have the sources for the 3.1.9-vs2.3.2.5 kernel installed. make[1]: *** [modules] Error 1 make[1]: Leaving directory `/usr/local/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux' make: *** [all] Error 2 root@ps91497:/usr/local/src/dahdi-linux-complete-2.3.0.1+2.3.0# So, the Makefile is looking for the kernel sources/headers and since it is a virtual host, I had to grab some headers/sources to build dependent software. This seems to be more trouble - I am going to dig and see if there are some binaries that I can download. If this doesn't work, I think I am going to build it all on a local VM and tweak it to run on my Dreamhost machine. That may be the route I need to take - would rather do it all in one place, but that may not happen. Glen On Sun, Apr 1, 2012 at 16:34, Ben Hutchings b...@decadent.org.uk wrote: Reply to all (or to the list), not just to me. On Sun, 2012-04-01 at 14:24 -0400, Glen Millard wrote: Okay - any other suggestions? Well you could answer my question: I wrote: What does it need from the kernel source? You certainly can't build a useful kernel module this way (nor would you be permitted to load it anyway). Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett
Uploading linux-2.6 (3.2.14-1)
Another week, another stable update. Linux 3.2.14 will have a large number of important bug fixes. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#661318: Possibility integrating newer Hyper-V paravirt drivers in squeeze?
Hi, Mathieu Simon wrote: But I'm not fully sure about your answer, if I understood you correctly this means cherry-picking every single related patch from 3.4-rcX to 3.2.(12) let's say from gregkh. - Right? I suppose my answer was less helpful than it could have been. :) Patches in the Debian kernel repository look like this: http://svn.debian.org/viewvc/kernel/dists/sid/linux-2.6/debian/patches/ The baseline for the current sid kernel is gregkh's 3.2.y kernel. When patches meet the criteria described in Documentation/stable_kernel_rules.txt, we can get them applied to 3.2.y and share their maintenance with others (no patch in the kernel repository needed in that case). For miscellaneous fixes not in the -stable tree, all that is needed is a list of commit ids corresponding to patches' appearance in linus's master or some tree that feeds into it. Driver backports are also often treated this way, and it's probably the right thing to do for your case. I do not think one big patch is ever acceptable for this, since it would make it way too hard to back out one patch while debugging. However, in theory it is even better (maybe the kernel team is happiest was a stretch) if a maintained version of the driver backport can be shared between distros and others using the same basic kernel/driver version combination. This is roughly speaking the way graphics drivers are maintained in squeeze: there is a linux-2.6.32.y-drm33.z tree that keeps track of fixes that were discovered to keep the graphics drivers from Linux 2.6.33.y working well against a 2.6.32.y kernel. That is fussy work and a long-term commitment, so it was probably not the best answer to what does Debian prefer. Upshot: if you send a list of relevant commit ids for commits that are not in 3.2.y, that's a good start, and we can try applying them and go from there. (If it's just the list output by git log --no-merges --oneline v3.2..origin/master \ -- drivers/hv drivers/staging/hv then the kernel team could just use that, but I think you mentioned needing a few more.) Thanks much and sorry for the lack of clarity. 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/20120402003644.GA29984@burratino
Bug#666781: linux-image-2.6.32-5-amd64: can't mount cdrom (/dev/sr0)
On Sun, 2012-04-01 at 18:20 -0500, hcm...@hosscomm.com wrote: The device in question is SATA - this is very similar to bug#583949 that's one of the reasons I went ahead and filed. Attached are the files you requested /var/log/dmesg and contents of /proc/partitions. From /var/log/dmesg I can see that the DVD writer was detected at boot time: [1.612267] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [1.624957] ata1.00: ATAPI: LITE-ON DVDRW LH-20A1L, BL05, max UDMA/100 [1.638229] ata1.00: configured for UDMA/100 [1.653753] scsi 0:0:0:0: CD-ROMLITE-ON DVDRW LH-20A1L BL05 PQ: 0 ANSI: 5 [...] [1.838813] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [1.838818] Uniform CD-ROM driver Revision: 3.20 [1.838947] sr 0:0:0:0: Attached scsi CD-ROM sr0 But the device is not available in the kernel now: major minor #blocks name 80 244198584 sda 811073152 sda1 82 1 sda2 85 18553856 sda5 86 11717632 sda6 877811072 sda7 88 205037568 sda8 8 16 244198584 sdb 8 17 14745600 sdb1 8 18 1 sdb2 8 21 73241600 sdb5 8 22 78124032 sdb6 8 23 78083072 sdb7 So there must have been some error that caused it to be disabled. I have the kernel log if you need it. Thanks for your assistance. Yes, please look for any messages about ata1, scsi0 or sr0. Regression? I am not sure. The device has proven it worked in the past I am not quite certain how long... IT worked great under lenny. I had to replace the motherboard a few months back and loaded squeeze from scratch. This is the first time I needed to burn something or use it since. [...] So this is a regression but not necessarily recent (in terms of kernel versions). Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Bug#666873: linux-image-3.2.0-2-amd64: kernel panics immediately on boot
Package: linux-2.6 Version: linux-image-3.2.0-2-amd64 Severity: critical Justification: breaks the whole system Dear Maintainer, I upgraded from 3.2.0-1 to 3.2.0-2 in unstable however the 3.2.0-2 kernel panics immediately after booting. 3.2.0-1 kernel still works. I also installed 3.3.0-rc6 from experimental and it boots (wireless doesn't connect but that's another bug...) Unfortunately, since it panics so early in the boot I don't know how to give you more information. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20120402005611.14274.84869.reportbug@debian
Bug#653669: Installation failed with BTRFS
On Sun, 2012-01-01 at 20:25 +0100, Bernhard wrote: Are you sure you made the partition big enough? btrfs at least used to not handle running out of disk space at all, and we can see it's trying to allocate a disk block, and this error occurs part of the way through debootstrap, when at least a few hundred megabytes will have been written to the disk. Alternatively, the 3.1.0-1 kernel could have a broken btrfs, if so reassign this bug to there. Hello Joey Yes, i'm sure the partition is big enough. The size of the root partition is about 10GB. [...] There were a large number of bug fixes to btrfs in Linux 3.2, including several relating to the sort of bug (failure to reserve space) that will trigger this warning. So I would suggest re-testing with the current daily installer. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Processed: severity of 666873 is serious
Processing commands for cont...@bugs.debian.org: severity 666873 serious Bug #666873 [linux-2.6] linux-image-3.2.0-2-amd64: kernel panics immediately on boot Severity set to 'serious' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 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.13026320007.transcr...@bugs.debian.org
Processed: notfound 666873 in linux-image-3.2.0-2-amd64, found 666873 in 3.2.12-1
Processing commands for cont...@bugs.debian.org: notfound 666873 linux-image-3.2.0-2-amd64 Bug #666873 [linux-2.6] linux-image-3.2.0-2-amd64: kernel panics immediately on boot There is no source info for the package 'linux-2.6' at version 'linux-image-3.2.0-2-amd64' with architecture '' Unable to make a source version for version 'linux-image-3.2.0-2-amd64' No longer marked as found in versions linux-image-3.2.0-2-amd64. # probably current testing version found 666873 3.2.12-1 Bug #666873 [linux-2.6] linux-image-3.2.0-2-amd64: kernel panics immediately on boot There is no source info for the package 'linux-2.6' at version '3.2.12-1' with architecture '' Unable to make a source version for version '3.2.12-1' Marked as found in versions 3.2.12-1. thanks Stopping processing here. Please contact me if you need assistance. -- 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.13030520103.transcr...@bugs.debian.org
Bug#666873: linux-image-3.2.0-2-amd64: kernel panics immediately on boot
On Sun, 2012-04-01 at 20:56 -0400, Kyle Girard wrote: Package: linux-2.6 Version: linux-image-3.2.0-2-amd64 Severity: critical Justification: breaks the whole system Dear Maintainer, I upgraded from 3.2.0-1 to 3.2.0-2 in unstable however the 3.2.0-2 kernel panics immediately after booting. 3.2.0-1 kernel still works. I also installed 3.3.0-rc6 from experimental and it boots (wireless doesn't connect but that's another bug...) Unfortunately, since it panics so early in the boot I don't know how to give you more information. Does the kernel parameter 'pcie_aspm=force' fix this? Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Processed: tagging 666873
Processing commands for cont...@bugs.debian.org: tags 666873 + moreinfo Bug #666873 [linux-2.6] linux-image-3.2.0-2-amd64: kernel panics immediately on boot Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 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.13039620391.transcr...@bugs.debian.org
Bug#666873: linux-image-3.2.0-2-amd64: kernel panics immediately on boot
On Sun, 2012-04-01 at 21:38 -0400, Kyle Girard wrote: On Apr 1, 2012 9:33 PM, Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2012-04-01 at 20:56 -0400, Kyle Girard wrote: Package: linux-2.6 Version: linux-image-3.2.0-2-amd64 Severity: critical Justification: breaks the whole system Dear Maintainer, I upgraded from 3.2.0-1 to 3.2.0-2 in unstable however the 3.2.0-2 kernel panics immediately after booting. 3.2.0-1 kernel still works. I also installed 3.3.0-rc6 from experimental and it boots (wireless doesn't connect but that's another bug...) Unfortunately, since it panics so early in the boot I don't know how to give you more information. Does the kernel parameter 'pcie_aspm=force' fix this? Yes, I am able to boot when I set that parameter. Thanks! Well that's just a workaround for the bug which I suspected. The real fix should be included in version 3.2.14-1 in a few days' time. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Processed: forcibly merging 665420 666873
Processing commands for cont...@bugs.debian.org: forcemerge 665420 666873 Bug #665420 [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 #666873 [linux-2.6] linux-image-3.2.0-2-amd64: kernel panics immediately on boot Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.kernel.pci/14503/focus=14514'. Severity set to 'important' from 'serious' There is no source info for the package 'linux-2.6' at version '3.2.12-1' with architecture '' Unable to make a source version for version '3.2.12-1' Marked as found in versions linux-2.6/3.3-1~experimental.1. Added tag(s) upstream, pending, fixed-upstream, and patch. Bug #665420 [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 Added tag(s) moreinfo. Merged 665420 666873 thanks Stopping processing here. Please contact me if you need assistance. -- 665420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665420 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.13372.transcr...@bugs.debian.org
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
On Tue, Mar 20, 2012 at 12:28:01AM +, Juha Jäykkä wrote: I am starting to believe I am in the clear here, but I am not yet convinced since the root cause is still unknown. In any case, thanks for all of you for helping hunt this down. Dafydd: I think you might want to try pcie_asmp=off next Cheers, Juha As I think I mentioned before, pice_aspm=off doesn't seem to help much for me. I still get wireless failure after a day or two, although they seem to be more often correlated with resuming from suspend. -- 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/20120402024231.GE31750@nia
Processed: Re: forcibly merging 665420 666873
Processing commands for cont...@bugs.debian.org: tags 665420 - moreinfo Bug #665420 [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 #666873 [linux-2.6] linux-image-3.2.0-2-amd64: kernel panics immediately on boot Removed tag(s) moreinfo. Removed tag(s) moreinfo. End of message, stopping processing here. Please contact me if you need assistance. -- 665420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665420 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.1355796663.transcr...@bugs.debian.org
Processed: tagging 666873
Processing commands for cont...@bugs.debian.org: tags 666873 - moreinfo Bug #666873 [linux-2.6] linux-image-3.2.0-2-amd64: kernel panics immediately on boot Bug #665420 [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 Ignoring request to alter tags of bug #666873 to the same tags previously set Ignoring request to alter tags of bug #665420 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 665420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665420 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.13691413512.transcr...@bugs.debian.org
Processed: tagging 666781
Processing commands for cont...@bugs.debian.org: tags 666781 - moreinfo Bug #666781 [linux-2.6] linux-image-2.6.32-5-amd64: can't mount cdrom (/dev/sr0) Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 666781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666781 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.14000727625.transcr...@bugs.debian.org
Re: Can I 'fool' the uname command??
On Sun, 2012-04-01 at 18:09 -0400, Glen Millard wrote: Sorry - my mistake. I need to build Vicidial installation on a Dreamhost server. root@ps91497:/usr/local/src/dahdi-linux-complete-2.3.0.1+2.3.0# make But here you're trying to build the DAHDI drivers, which I think must be optional (and certainly you're not going to be using them on a virtual server). So why don't you just skip that step? [...] If this doesn't work, I think I am going to build it all on a local VM and tweak it to run on my Dreamhost machine. That may be the route I need to take - would rather do it all in one place, but that may not happen. Really that is probably a more sensible thing to do. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Bug#666386: igb + bnx2 + ifenslave + brctl + vconfig = largely broken
On Sun, 2012-04-01 at 12:40 +0200, Josip Rodin wrote: On Sun, Apr 01, 2012 at 03:09:56AM +0100, Ben Hutchings wrote: I bet this is due to the combination of LRO plus bridging. We try to turn off LRO in devices under a bridge, but that won't work if there's an intermediate bonding device. If you run: # ethtool -K eth0 lro off # ethtool -K eth2 lro off does the bridge start working? Err... % sudo ethtool -K eth0 lro off Cannot set large receive offload settings: Operation not supported % sudo ethtool -K eth2 lro off Cannot set large receive offload settings: Operation not supported Hmm. Well it shouldn't be a problem but you could try also turning off GRO (similar commands). That's with eth0 removed from bonding, and eth2 inside. So the bonding device has only one slave now? What if you take the bonding device out completely and add eth2 directly to the bridge? Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Bug#661318: Possibility integrating newer Hyper-V paravirt drivers in squeeze?
G'day Am 02.04.2012 02:36, schrieb Jonathan Nieder: I suppose my answer was less helpful than it could have been. :) Thanks Jonathan for enlightening me, now I was able to understand :) [...] The baseline for the current sid kernel is gregkh's 3.2.y kernel. When patches meet the criteria described in Documentation/stable_kernel_rules.txt, Ok, they don't apply to these rules, otherwise they would have been applied upstream in Greg's tree. [...] For miscellaneous fixes not in the -stable tree, all that is needed is a list of commit ids corresponding to patches' appearance in linus's master or some tree that feeds into it. Driver backports are also often treated this way, and it's probably the right thing to do for your case. I'd say this criteria is matching. [...] Upshot: if you send a list of relevant commit ids for commits that are not in 3.2.y, that's a good start, and we can try applying them and go from there. (If it's just the list output by git log --no-merges --oneline v3.2..origin/master \ -- drivers/hv drivers/staging/hv then the kernel team could just use that, but I think you mentioned needing a few more.) Yeah a few more, but a helpful command to get started! Thanks much and sorry for the lack of clarity. I keep learning, thank you! Here it goes: To get a working set of Hyper-V drivers and utils to, present in 3.4 we need to observe: drivers/staging/hv drivers/hv drivers/scsi/storvsc* drivers/net/hyperv drivers/hid/hid-hyperv* tools/hv/ include/linux/hyperv.h The merge window is now closed by time of writing this message. In a follow-up I'll send a list of commit ids - and the order to get them applied in a way we don't run into merge conflicts :-) - Mathieu -- 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/4f793c44.4010...@gmail.com
