Bug#514418: [FIX]: ultra45 boot failing...
On Sun, Feb 08, 2009 at 04:58:08PM -0800, David Miller wrote: So you're saying that X working is more important than machines actually booting at all? These priorities are wrong. When N (where N 0) users complain about dead X, and 0 users complain about not being able to boot, the priorities are fairly clear... -- 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
Bug#514418: [FIX]: ultra45 boot failing...
On Mon, Feb 09, 2009 at 12:28:18AM -0800, David Miller wrote: So you're saying that X working is more important than machines actually booting at all? These priorities are wrong. When N (where N 0) users complain about dead X, and 0 users complain about not being able to boot, the priorities are fairly clear... If their machine won't even boot into the installer they are unlikely to even make a report. Nobody (before you that is) reported an installer failure on these machines, so the situation is still clear from our point of view - it's certainly not perfect or even good, but the system as a whole depends on user input. Furthermore the point remains that you put a change into the kernel that I would never have advocated had you presented the bug to me. I would have suggested ways to fix the X server and even worked on the patch. But since nobody contacted me about this, a broken change went into the kernel instead. That is true, someone should have contacted you (sparclinux list at least) about that. But then, it would have been completely your prerogative to respond to that simply by saying - DTRT and go upgrade X, patching old X is a waste of my time, and I guess nobody wanted to risk hearing that answer? :) -- 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
Bug#514418: [FIX]: ultra45 boot failing...
From: Josip Rodin j...@debbugs.entuzijast.net Date: Mon, 9 Feb 2009 09:20:39 +0100 On Sun, Feb 08, 2009 at 04:58:08PM -0800, David Miller wrote: So you're saying that X working is more important than machines actually booting at all? These priorities are wrong. When N (where N 0) users complain about dead X, and 0 users complain about not being able to boot, the priorities are fairly clear... If their machine won't even boot into the installer they are unlikely to even make a report. You've really got it backwards. Users who hit this problem don't even have a chance to run your distribution at all. Furthermore the point remains that you put a change into the kernel that I would never have advocated had you presented the bug to me. I would have suggested ways to fix the X server and even worked on the patch. But since nobody contacted me about this, a broken change went into the kernel instead. And on top of it, you're going to sit here and argue with me about whether totally-unworking x-not-working. :-/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
Hi Otavio ;-) On Donnerstag, 5. Februar 2009, Otavio Salvador wrote: I won't be at FOSDEM :( You certainly missed a lot, but you didnt miss that meeting as it didnt take place. (TTBOMK) I planned to attend as I really really would like to see Debian Edu CDs build as part of the normal Debian CD sets for squeeze... (Currently we do this on our own machine using a patched version of debian-cd.) regards, Holger signature.asc Description: This is a digitally signed message part.
Bug#514418: [FIX]: ultra45 boot failing...
From: Josip Rodin j...@debbugs.entuzijast.net Date: Mon, 9 Feb 2009 09:45:27 +0100 But then, it would have been completely your prerogative to respond to that simply by saying - DTRT and go upgrade X, patching old X is a waste of my time, and I guess nobody wanted to risk hearing that answer? :) No, I would have said that if time is tight at least we can use fbdev as the Xorg driver for PCI devices on sparc until we have a better fix for Xorg. And meanwhile I would have done an: apt-get source xserver-xorg and worked on a patch for you guys. I'm running this on my workstation so I actually give a shit for crying out loud. Really, you're just being rediculious. There were a thousand better ways to have handled this. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Forthcoming changes in kernel-package
[...] c. his means there will be no need for /etc/kernel-img.conf file any more. [...] Isn't this file also read in the postinst of the official kernels? In FAI we had several issues when kernel-img.conf was missing or hadn't had the proper values in there. Best, Michael pgp2VegW6MbOX.pgp Description: PGP signature
Processed: Flood of warnings from hpet_legacy_next_event()
Processing commands for cont...@bugs.debian.org: tags 512617 + patch Bug#512617: kernel repeated warnings There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514592: linux-image-2.6.26-1-486: does not support ethernet adaptor Intel 0x10de
Package: linux-image-2.6.26-1-486 Version: 2.6.26+17 Severity: normal The iethernet adaptor 0x8086:0x10de does not work for me with this kernel. It is supposed to work with 2.6.28. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.28-macmini (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.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
Bug#512617: Flood of warnings from hpet_legacy_next_event()
tags 512617 + patch thanks I'm unfortunately able to reproduce this bug on an HP dc7900 with the latest available BIOS (V1.11). The patch in 2.6.28 looks trivial to backport to 2.6.26: it consists simply of replacing WARN_ON with WARN_ON_ONCE. See http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=commitdiff;h=1de5b0854623d30d01d72cd4ea323eb5f39d1f16 There may be other reasons to prefer 2.6.28 on a dc7900, but I'd still be grateful if this simple fix could make it into lenny. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: finalizing 2.6.28 config options
On Mon, Feb 09, 2009 at 12:59:41AM +, Ben Hutchings wrote: On Fri, 2009-02-06 at 14:42 +0100, maximilian attems wrote: [...] * FIRMWARE_IN_KERNEL default enabled we probably don't ship right yet relevant firmware separetly? FIRMWARE_IN_KERNEL enables inclusion of firmware along with drivers in the main kernel image, and has no effect on driver modules. Driver modules that use request_firmware() will always need separate firmware. right so do we disable support by not setting it? or do we get crucified for setting :) [...] * USB_SERIAL_KEYSPAN_MPR USB_SERIAL_KEYSPAN_USA28 USB_SERIAL_KEYSPAN_USA28X USB_SERIAL_KEYSPAN_USA28XA USB_SERIAL_KEYSPAN_USA28XB USB_SERIAL_KEYSPAN_USA19 USB_SERIAL_KEYSPAN_USA18X USB_SERIAL_KEYSPAN_USA19W USB_SERIAL_KEYSPAN_USA19QW USB_SERIAL_KEYSPAN_USA19QI USB_SERIAL_KEYSPAN_USA49W USB_SERIAL_KEYSPAN_USA49WLC bunch of new firmware for some option style serial dev not looked at their licences yet nor request_firmware() usage This driver uses request_firmware(). so aboves configs can be disabled, i'd guess? thanks for the input -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Forthcoming changes in kernel-package
Hi On Montag, 9. Februar 2009, Michael Tautschnig wrote: [...] c. his means there will be no need for /etc/kernel-img.conf file any more. [...] Isn't this file also read in the postinst of the official kernels? In FAI we had several issues when kernel-img.conf was missing or hadn't had the proper values in there. [...] As of yet kernel-package is still used in the official kernel builds[1], by using make-kpkg to build and create the linux-image packages (linux-headers is assembled manually). linux-2.6/debian/rules.real [...] kpkg_image := $(setup_env) ifdef DEBIAN_KERNEL_JOBS kpkg_image += CONCURRENCY_LEVEL=$(DEBIAN_KERNEL_JOBS) endif kpkg_image += make-kpkg --arch '$(firstword $(KPKG_ARCH) $(ARCH))' --cross-compile=- --stem linux --config silentoldconfig ifneq ($(INITRAMFS),False) kpkg_image += --initrd endif ifdef KPKG_SUBARCH kpkg_image += --subarch '$(KPKG_SUBARCH)' endif [...] Which is called from the following targets: $(STAMPS_DIR)/setup_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_kernel-package: [...]$(kpkg_image) configure [...] $(STAMPS_DIR)/build_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_kernel-package: [...]$(kpkg_image) build [...] install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_kernel-package: [...]$(kpkg_image) kernel-image [...] Due to this, the bootloader setup relies on postinst_hook/ postrm_hook and do_initrd in /etc/kernel-img.conf and honours the rest of the settings. Regards Stefan Lippers-Hollmann [1] http://svn.debian.org/viewsvn/kernel/dists/trunk/linux-2.6/debian/rules.real?view=markup signature.asc Description: This is a digitally signed message part.
Bug#514418: [FIX]: ultra45 boot failing...
On Mon, 2009-02-09 at 01:21 -0800, David Miller wrote: No, I would have said that if time is tight at least we can use fbdev as the Xorg driver for PCI devices on sparc until we have a better fix for Xorg. We can probably do that for r1. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514611: [linux-modules-extra-2.6] Please add batman-adv modules
Sven Eckelmann wrote: Please add batman-adv modules to autobuilt modules. The current version of the package is currently in the new queue due to a source package split. please ping again when lenny is released *and* your source package has made it into unstable, thanks. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514611: [linux-modules-extra-2.6] Please add batman-adv modules
Package: linux-modules-extra-2.6 Severity: wishlist Tags: patch Please add batman-adv modules to autobuilt modules. The current version of the package is currently in the new queue due to a source package split. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.28.1 Debian Release: 5.0 500 unstableftp.debian.org 500 unstabledebian.netcologne.de 1 experimentalftp.debian.org --- batman-adv/copyright | 19 +++ batman-adv/defines |5 + defines |1 + 3 files changed, 25 insertions(+), 0 deletions(-) create mode 100644 batman-adv/copyright create mode 100644 batman-adv/defines diff --git a/batman-adv/copyright b/batman-adv/copyright new file mode 100644 index 000..e2b36c6 --- /dev/null +++ b/batman-adv/copyright @@ -0,0 +1,19 @@ +Format-Specification: http://wiki.debian.org/Proposals/CopyrightFormat +Upstream-Name: B.A.T.M.A.N. Advanced +Upstream-Source: http://www.open-mesh.net/ +Upstream-Maintainer: Marek Lindner lindner_ma...@yahoo.de + Simon Wunderlich s...@hrz.tu-chemnitz.de + +Files: * +Copyright: Copyright 2006-2008, Marek Lindner lindner_ma...@yahoo.de +Copyright: Copyright 2006-2008, Simon Wunderlich s...@hrz.tu-chemnitz.de +License: GPL-2 + On Debian systems the full text of the GNU General Public License can be found + in the `/usr/share/common-licenses/GPL-2' file. + +Files: debian/* +Copyright: Copyright 2008-2009, Simon Wunderlich s...@hrz.tu-chemnitz.de +Copyright: Copyright 2008-2009, Sven Eckelmann sven.eckelm...@gmx.de +License: GPL-2 + On Debian systems the full text of the GNU General Public License can be found + in the `/usr/share/common-licenses/GPL-2' file. diff --git a/batman-adv/defines b/batman-adv/defines new file mode 100644 index 000..6b4c4f4 --- /dev/null +++ b/batman-adv/defines @@ -0,0 +1,5 @@ +[base] +desc: B.A.T.M.A.N. on Layer 2 +longdesc: + This package contains the set of loadable kernel modules for the + Layer 2 Mesh B.A.T.M.A.N. diff --git a/defines b/defines index 6433d18..d171e29 100644 --- a/defines +++ b/defines @@ -2,6 +2,7 @@ modules: atl2 aufs + batman-adv drbd8 et131x gspca
Bug#514624: linux-image for sparc64 sungem problems
Package: linux-image-2.6.24-etchnhalf.1-sparc64 Version: 2.6.24+13~etchnhalf.1 For some time, even since 2.6.18 we have had problems with the sungem NIC driver on our Sun Netra T1 AC200[1] where the machine is prone to locking up. Then recently this month on the LKML someone posted[2] that they too were having problems and submitted a fix. It would probably be worth backport this patch to the lenny 2.6.26 kernel before general release; the patch is trivial and David Miller seems happy with it too. It would save a lot of pain for some sparc64 users out there. Cheers [1] http://sunsolve.sun.com/handbook_pub/validateUser.do?target=Systems/Netra_T1_AC200/Netra_T1_AC200 [2] http://marc.info/?t=123393015500020r=1w=2 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513894: base: Internal error: Oops: f3 [#2]
Am Dienstag 03 Februar 2009 13:47:04 schrieben Sie: * root tom-k...@gmx.de [2009-02-02 08:33]: [42994982.81] Unable to handle kernel paging request at virtual address 692f7473 Can you please tell us more: when does this happen, how often, how reliably can you reproduce this problem, etc? Hello Martin, This happens several times a day. The system is a linksys nslu2. It looks like it has something to do with the i2c-tiny-usb driver. [43177942.75] i2c-adapter i2c-1: failure writing data [43177942.88] hub 1-1:1.0: port 1 disabled by hub (EMI?), re-enabling... [43177942.88] usb 1-1.1: USB disconnect, address 17 [43177942.97] usb 1-1.1: new low speed USB device using ehci_hcd and address 18 [43177943.09] usb 1-1.1: configuration #1 chosen from 1 choice [43177943.10] i2c-tiny-usb 1-1.1:1.0: version 2.05 found at bus 001 address 018 [43177943.13] i2c-adapter i2c-1: connected i2c-tiny-usb device [43177943.14] usb 1-1.1: New USB device found, idVendor=0403, idProduct=c631 [43177943.14] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [43177943.15] usb 1-1.1: Product: i2c-tiny-usb [43177943.16] usb 1-1.1: Manufacturer: Till Harbaum Most of the time I can see it after the device is registered again. Thanks, Thomas -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513894: Oops: f3 with i2c-tiny-usb
Hi Till and other I2C developers, Thomas Koch, a Debian user, reported the following backtrace with 2.6.26 related to i2c and possibly related to the i2c-tiny-usb driver. This is on an ARM device. Do you know if this is a known issue for which a patch is available in newer kernels, or is this a new bug? [42994982.81] Unable to handle kernel paging request at virtual address 692f7473 [42994982.81] pgd = c1da [42994982.81] [692f7473] *pgd= [42994982.81] Internal error: Oops: f3 [#2] [42994982.81] Modules linked in: ipv6 nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc nls_utf8 ntfs nls_base ext2 evdev ftdi_sio usbhid hid i2c_tiny_usb ff_memless usbserial ixp4xx_eth ixp4xx_npe firmware_class ixp4xx_qmgr ixp4xx_beeper ohci_hcd ext3 jbd mbcache sd_mod ehci_hcd usb_storage usbcorescsi_mod [42994982.81] CPU: 0Tainted: G D(2.6.26-1-ixp4xx #1) [42994982.81] PC is at module_put+0x20/0x48 [42994982.81] LR is at i2c_put_adapter+0x14/0x18 [42994982.81] pc : [c0060b00]lr : [c01940f4]psr: 2093 [42994982.81] sp : c0fc3c68 ip : c0fc3c78 fp : c0fc3c74 [42994982.81] r10: c18d3dd8 r9 : c1c0d120 r8 : [42994982.81] r7 : c1c1a208 r6 : 0008 r5 : c1daaac0 r4 : c13fe000 [42994982.81] r3 : 2093 r2 : 2013 r1 : c1daaac0 r0 : 692f7373 [42994982.81] Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user [42994982.81] Control: 397f Table: 01da DAC: 0015 [42994982.81] Process hcontrol (pid: 2671, stack limit = 0xc0fc2268) [42994982.81] Stack: (0xc0fc3c68 to 0xc0fc4000) [42994982.81] 3c60: c0fc3c84 c0fc3c78 c01940f4 c0060aec c0fc3c9c c0fc3c88 [42994982.81] 3c80: c0195d94 c01940ec c1daaac0 c0f0ea60 c0fc3cd4 c0fc3ca0 c009813c c0195d84 [42994982.81] 3ca0: c0ef9d30 c1daaac0 c1c1a200 c1c1a208 [42994982.81] 3cc0: 00f3 0001 c0fc3ce4 c0fc3cd8 c00984c4 c0098090 c0fc3d04 c0fc3ce8 [42994982.81] 3ce0: c0094dd0 c009849c c0f16e00 c1c1a200 0003 000c c0fc3d2c c0fc3d08 [42994982.81] 3d00: c0040980 c0094d64 c0f16e00 c0fc2000 c1e68060 000b c01941f8 0008 [42994982.81] 3d20: c0fc3d3c c0fc3d30 c0040a00 c0040904 c0fc3d54 c0fc3d40 c0041cf8 c00409e4 [42994982.81] 3d40: c003e550 c003e420 c0fc3d64 c0fc3d58 c0029de4 c0041aec c0fc3d84 c0fc3d68 [42994982.81] 3d60: c002c460 c0029b70 c0fc3ea0 00f3 692f7265 c0fc3ea0 c0fc3dac c0fc3d88 [42994982.81] 3d80: c002c718 c002c400 e5933000 c021db38 0013 e5933000 [42994982.81] 3da0: c0fc3dec c0fc3db0 c002e584 c002c6b4 c02c0a68 28841963 b229 [42994982.81] 3dc0: c0fc3df4 c02bc1bc 00f3 c0fc3ea0 692f7265 6013 [42994982.81] 3de0: c0fc3e9c c0fc3df0 c00251f0 c002e150 c005b76c c02bc4cc c0fc3e24 c0fc3e08 [42994982.81] 3e00: c003080c c00307a8 c02c1680 c02c1680 0005 c0fc3e3c c0fc3e28 [42994982.81] 3e20: c0043e2c c0037468 0005 0005 c0fc3e5c c0fc3e40 c002504c c0043dd4 [42994982.81] 3e40: c005b878 001f 0020 c0fc3eec c0fc3e60 c00256b0 c002500c [42994982.81] 3e60: 0001 c02c0a70 c0f374c0 0001 2883b65f b229 c0fc3f10 [42994982.81] 3e80: c0fc3ed4 be932b55 c051d360 c0025c48 c0fc3f04 c0fc3ea0 c002566c c00251c0 [42994982.81] 3ea0: c0fc2028 c0fc3f0c 0001 692f7265 c1c73a08 0001 be932b55 c051d360 [42994982.81] 3ec0: c0025c48 c0fc2000 c0fc3f04 c0fc3f08 c0fc3ee8 c0194cd4 c01941f8 [42994982.81] 3ee0: a013 0001 0001 be932b55 c051d360 c0fc3f2c c0fc3f08 [42994982.81] 3f00: c0194cd4 c01941ec c0fc3f4c 0001004b c13f0001 c051d360 be932b55 fff4 [42994982.81] 3f20: c0fc3f4c c0fc3f30 c01961ac c0194c98 c1daaac0 be932b55 c0fc3f78 0001 [42994982.81] 3f40: c0fc3f74 c0fc3f50 c0097778 c0196170 006d6561 0a6f c1daaac0 fff7 [42994982.81] 3f60: c0fc3fa4 c0fc3f78 c0097c44 c00976d0 [42994982.81] 3f80: d6fc 90a0 0003 c0fc3fa8 [42994982.81] 3fa0: c0025aa0 c0097c0c d6fc 0003 be932b55 0001 be932b55 [42994982.81] 3fc0: d6fc 90a0 0003 40025000 be932b6c [42994982.81] 3fe0: be932a40 b4ac 40209eac 4010 0003 0002003d [42994982.81] Backtrace: [42994982.81] [c0060ae0] (module_put+0x0/0x48) from [c01940f4] (i2c_put_adapter+0x14/0x18) [42994982.81] [c01940e0] (i2c_put_adapter+0x0/0x18) from [c0195d94] (i2cdev_release+0x1c/0x30) [42994982.81] [c0195d78] (i2cdev_release+0x0/0x30) from [c009813c] (__fput+0xb8/0x178) [42994982.81] r5:c0f0ea60 r4:c1daaac0 [42994982.81] [c0098084] (__fput+0x0/0x178) from [c00984c4] (fput+0x34/0x38) [42994982.81]
Re: Forthcoming changes in kernel-package
On Mon, Feb 09 2009, Michael Tautschnig wrote: [...] c. his means there will be no need for /etc/kernel-img.conf file any more. [...] Isn't this file also read in the postinst of the official kernels? In FAI we had several issues when kernel-img.conf was missing or hadn't had the proper values in there. I think that is a carry over from the days when the official kernels were based on kernel-package. I am given to understand that is not how things are supposed to work post lenny. In any case, I guess what I meant to say was that images created by kernel-package will stop paying attention to /etc/kernel-img.conf, and thus there will be no reason to keep that file for the sake of kernel-package images. kernel-package shall also stop creating the file if it does not exist. Another thing going away is the on-th-fly patching of the sources; the preferred way to patch the sources will be to do so outside of make-kpkg, before invoking the make-kpkg script to package the kernel images. All that convoluted code excised from kernel-package ought to improve robustness. manoj -- Love may laugh at locksmiths, but he has a profound respect for money bags. Sidney Paternoster, The Folly of the Wise Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
On Mon, Feb 09, 2009 at 10:35:40AM +0100, Holger Levsen wrote: Hi Otavio ;-) On Donnerstag, 5. Februar 2009, Otavio Salvador wrote: I won't be at FOSDEM :( You certainly missed a lot, but you didnt miss that meeting as it didnt take place. (TTBOMK) Sorry, it did. Unfortunately at a really bad time for you: just as the first talk was starting in the Debian devroom. We touched on quite a number of topics, and Mark Hymers was taking notes that I'm hoping he can post somewhere soon. The main focus of the meeting was how d-i builds and releases work, and I think we made quite some progress on that. There are a few changes that we think should be made that will help a great deal in building, publishing and releasing d-i. I'm not posting any of the details here just yet because my memory fails me... :-) I planned to attend as I really really would like to see Debian Edu CDs build as part of the normal Debian CD sets for squeeze... Sure, and I expect that should be easy. We've spoken about it in the past and things should be even simpler now. Ronny is already joining in on #debian-cd and talking about useful patches from debian-edu now. I don't expect any problems. -- Steve McIntyre, Cambridge, UK.st...@einval.com Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513894: Oops: f3 with i2c-tiny-usb
Hi Till and other I2C developers, Thomas Koch, a Debian user, reported the following backtrace with 2.6.26 related to i2c and possibly related to the i2c-tiny-usb driver. This is on an ARM device. Do you know if this is a known issue for which a patch is available in newer kernels, or is this a new bug? [42994982.81] Unable to handle kernel paging request at virtual address 692f7473 [42994982.81] pgd = c1da [42994982.81] [692f7473] *pgd= [42994982.81] Internal error: Oops: f3 [#2] [42994982.81] Modules linked in: ipv6 nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc nls_utf8 ntfs nls_base ext2 evdev ftdi_sio usbhid hid i2c_tiny_usb ff_memless usbserial ixp4xx_eth ixp4xx_npe firmware_class ixp4xx_qmgr ixp4xx_beeper ohci_hcd ext3 jbd mbcache sd_mod ehci_hcd usb_storage usbcorescsi_mod [42994982.81] CPU: 0Tainted: G D(2.6.26-1-ixp4xx #1) [42994982.81] PC is at module_put+0x20/0x48 [42994982.81] LR is at i2c_put_adapter+0x14/0x18 [42994982.81] pc : [c0060b00]lr : [c01940f4]psr: 2093 [42994982.81] sp : c0fc3c68 ip : c0fc3c78 fp : c0fc3c74 [42994982.81] r10: c18d3dd8 r9 : c1c0d120 r8 : [42994982.81] r7 : c1c1a208 r6 : 0008 r5 : c1daaac0 r4 : c13fe000 [42994982.81] r3 : 2093 r2 : 2013 r1 : c1daaac0 r0 : 692f7373 [42994982.81] Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user [42994982.81] Control: 397f Table: 01da DAC: 0015 [42994982.81] Process hcontrol (pid: 2671, stack limit = 0xc0fc2268) [42994982.81] Stack: (0xc0fc3c68 to 0xc0fc4000) [42994982.81] 3c60: c0fc3c84 c0fc3c78 c01940f4 c0060aec c0fc3c9c c0fc3c88 [42994982.81] 3c80: c0195d94 c01940ec c1daaac0 c0f0ea60 c0fc3cd4 c0fc3ca0 c009813c c0195d84 [42994982.81] 3ca0: c0ef9d30 c1daaac0 c1c1a200 c1c1a208 [42994982.81] 3cc0: 00f3 0001 c0fc3ce4 c0fc3cd8 c00984c4 c0098090 c0fc3d04 c0fc3ce8 [42994982.81] 3ce0: c0094dd0 c009849c c0f16e00 c1c1a200 0003 000c c0fc3d2c c0fc3d08 [42994982.81] 3d00: c0040980 c0094d64 c0f16e00 c0fc2000 c1e68060 000b c01941f8 0008 [42994982.81] 3d20: c0fc3d3c c0fc3d30 c0040a00 c0040904 c0fc3d54 c0fc3d40 c0041cf8 c00409e4 [42994982.81] 3d40: c003e550 c003e420 c0fc3d64 c0fc3d58 c0029de4 c0041aec c0fc3d84 c0fc3d68 [42994982.81] 3d60: c002c460 c0029b70 c0fc3ea0 00f3 692f7265 c0fc3ea0 c0fc3dac c0fc3d88 [42994982.81] 3d80: c002c718 c002c400 e5933000 c021db38 0013 e5933000 [42994982.81] 3da0: c0fc3dec c0fc3db0 c002e584 c002c6b4 c02c0a68 28841963 b229 [42994982.81] 3dc0: c0fc3df4 c02bc1bc 00f3 c0fc3ea0 692f7265 6013 [42994982.81] 3de0: c0fc3e9c c0fc3df0 c00251f0 c002e150 c005b76c c02bc4cc c0fc3e24 c0fc3e08 [42994982.81] 3e00: c003080c c00307a8 c02c1680 c02c1680 0005 c0fc3e3c c0fc3e28 [42994982.81] 3e20: c0043e2c c0037468 0005 0005 c0fc3e5c c0fc3e40 c002504c c0043dd4 [42994982.81] 3e40: c005b878 001f 0020 c0fc3eec c0fc3e60 c00256b0 c002500c [42994982.81] 3e60: 0001 c02c0a70 c0f374c0 0001 2883b65f b229 c0fc3f10 [42994982.81] 3e80: c0fc3ed4 be932b55 c051d360 c0025c48 c0fc3f04 c0fc3ea0 c002566c c00251c0 [42994982.81] 3ea0: c0fc2028 c0fc3f0c 0001 692f7265 c1c73a08 0001 be932b55 c051d360 [42994982.81] 3ec0: c0025c48 c0fc2000 c0fc3f04 c0fc3f08 c0fc3ee8 c0194cd4 c01941f8 [42994982.81] 3ee0: a013 0001 0001 be932b55 c051d360 c0fc3f2c c0fc3f08 [42994982.81] 3f00: c0194cd4 c01941ec c0fc3f4c 0001004b c13f0001 c051d360 be932b55 fff4 [42994982.81] 3f20: c0fc3f4c c0fc3f30 c01961ac c0194c98 c1daaac0 be932b55 c0fc3f78 0001 [42994982.81] 3f40: c0fc3f74 c0fc3f50 c0097778 c0196170 006d6561 0a6f c1daaac0 fff7 [42994982.81] 3f60: c0fc3fa4 c0fc3f78 c0097c44 c00976d0 [42994982.81] 3f80: d6fc 90a0 0003 c0fc3fa8 [42994982.81] 3fa0: c0025aa0 c0097c0c d6fc 0003 be932b55 0001 be932b55 [42994982.81] 3fc0: d6fc 90a0 0003 40025000 be932b6c [42994982.81] 3fe0: be932a40 b4ac 40209eac 4010 0003 0002003d [42994982.81] Backtrace: [42994982.81] [c0060ae0] (module_put+0x0/0x48) from [c01940f4] (i2c_put_adapter+0x14/0x18) [42994982.81] [c01940e0] (i2c_put_adapter+0x0/0x18) from [c0195d94] (i2cdev_release+0x1c/0x30) [42994982.81] [c0195d78] (i2cdev_release+0x0/0x30) from [c009813c] (__fput+0xb8/0x178) [42994982.81] r5:c0f0ea60 r4:c1daaac0 [42994982.81] [c0098084] (__fput+0x0/0x178) from [c00984c4] (fput+0x34/0x38) [42994982.81]
Processed: reassign 514624 to linux-image-2.6.26-1-sparc64, forcibly merging 508151 514624
Processing commands for cont...@bugs.debian.org: reassign 514624 linux-image-2.6.26-1-sparc64 Bug#514624: linux-image for sparc64 sungem problems Bug reassigned from package `linux-image-2.6.24-etchnhalf.1-sparc64' to `linux-image-2.6.26-1-sparc64'. forcemerge 508151 514624 Bug#508151: linux-image-2.6.26-1-sparc64: soft lockup when trying to bring up eth1 Bug#514624: linux-image for sparc64 sungem problems Forcibly Merged 508151 514624. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508151: AW: Bug#508151: Bug#514624: linux-image for sparc64 sungem problem s
Hi, sorry for topposting, the symbian mail client sucks ;) but yes, i would be able to test the fix on my netra. regards evgeni -- Ursprüngl. Mitteil. -- Betreff:Bug#508151: Bug#514624: linux-image for sparc64 sungem problems Von:dann frazier da...@debian.org Datum: 09/02/2009 18:50 forcemerge 508151 514624 thanks On Mon, Feb 09, 2009 at 03:37:09PM +, Alexander Clouter wrote: Package: linux-image-2.6.24-etchnhalf.1-sparc64 Version: 2.6.24+13~etchnhalf.1 For some time, even since 2.6.18 we have had problems with the sungem NIC driver on our Sun Netra T1 AC200[1] where the machine is prone to locking up. Then recently this month on the LKML someone posted[2] that they too were having problems and submitted a fix. It would probably be worth backport this patch to the lenny 2.6.26 kernel before general release; the patch is trivial and David Miller seems happy with it too. It would save a lot of pain for some sparc64 users out there. Thanks for the report; it is likely too late to get this fix included in the initial GR of lenny, but we can likely include it in the first update. Would you and/or Evgeni be able to test a 2.6.26 build to verify this fix if I provide one? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reassign 514624 to linux-image-2.6.26-1-sparc64, forcibly merging 508151 514624
reassign 514624 linux-image-2.6.26-1-sparc64 forcemerge 508151 514624 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#446323: marked as done (mdadm: recovery in infinite loop)
Your message dated Mon, 9 Feb 2009 20:22:19 +0100 with message-id 20090209192219.gb5...@piper.oerlikon.madduck.net and subject line Re: Bug#446323: mdadm: recovery in infinite loop has caused the Debian Bug report #446323, regarding mdadm: recovery in infinite loop to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 446323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mdadm Version: 2.5.6-9 Severity: normal Hello, I am trying to setup raid1 on my pc. I have 2 identical drives. 270+gb. each with 3 partitions. 30gb hdb1 - md0 250gb hdb2 -md2 4gb swap hdb5 -md4 Initially my raid had only one drive. I have added the second one with mdadm --add /dev/md2 /dev/hda1 then 2 then 4 It started doing recovery for drives. IT finished for md0,md4 but for md2 it is in infinite loop. IT goes to 15 % and starts again hplinux:/home/lucas# cat /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] [raid0] md4 : active raid1 hda5[0] hdb5[1] 1951744 blocks [2/2] [UU] md2 : active raid1 hdb2[1] hda2[2] 276438400 blocks [2/1] [_U] [] recovery = 2.8% (7898752/276438400) finish=2448.2min speed=1826K/sec md0 : active raid1 hda1[0] hdb1[1] 34178176 blocks [2/2] [UU] unused devices: none Oct 11 19:26:50 hplinux kernel: md: md2: sync done. Oct 11 19:26:51 hplinux kernel: md: syncing RAID array md2 Oct 11 19:26:51 hplinux kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. Oct 11 19:26:51 hplinux kernel: md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for reconstruction. Oct 11 19:26:51 hplinux kernel: md: using 128k window, over a total of 276438400 blocks. Oct 11 19:32:21 hplinux kernel: md: md2: sync done. Oct 11 19:32:21 hplinux mdadm: RebuildFinished event detected on md device /dev/md2 Oct 11 19:32:21 hplinux kernel: md: syncing RAID array md2 Oct 11 19:32:21 hplinux kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. Oct 11 19:32:21 hplinux kernel: md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for reconstruction. Oct 11 19:32:21 hplinux kernel: md: using 128k window, over a total of 276438400 blocks. Oct 11 19:32:21 hplinux mdadm: RebuildStarted event detected on md device /dev/md2 Oct 11 19:36:16 hplinux kernel: md: md2: sync done. Oct 11 19:36:17 hplinux kernel: md: syncing RAID array md2 why is this appening? I have checked both partitions for bad blocks with e2fsck. Is there something I am missing? The loops just goes on and on. ITs been 72h so I don't know how much longer with the drives survive this 20mb/s read and write. Thanks, lucas -- Package-specific info: --- mount output /dev/md0 on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) procbususb on /proc/bus/usb type usbfs (rw) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/md2 on /files type ext3 (rw) nfsd on /proc/fs/nfsd type nfsd (rw) rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) --- mdadm.conf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST system # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays # This file was auto-generated on Fri, 05 Oct 2007 21:54:54 -0500 # by mkconf $Id: mkconf 261 2006-11-09 13:32:35Z madduck $ ARRAY /dev/md0 level=raid1 num-devices=2 UUID=8f8b90a7:642e9c4d:b1274a75:6a339511 ARRAY /dev/md2 level=raid1 num-devices=2 UUID=6934dbf9:dfe9d7d1:b1274a75:6a339511 ARRAY /dev/md4 level=raid1 num-devices=2 UUID=967e922e:2688de6a:b1274a75:6a339511 --- /proc/mdstat: Personalities : [raid1] [raid6] [raid5] [raid4] [raid0] md4 : active raid1 hda5[0] hdb5[1] 1951744 blocks [2/2] [UU] md2 : active raid1 hdb2[1] hda2[2] 276438400 blocks [2/1] [_U] [] recovery =
Bug#513894: Oops: f3 with i2c-tiny-usb
Hi, this is an unknown problem. In fact it's the first time i ever got an error report for the device. And therefore there isn't any patch. There seems to be a usb write error. This is a diy hardware. There may be several reasons causing such problems: Hardware problems on the i2c-tiny-usb: - Have correct zener diodes (fast ones!) been used? - Is the PCB home made? If yes is it really reliable? - How long is the usb cable? General problems: - What is connected to the i2c-tiny-usb? - How much power does it draw? - Is the nslu really able to power everything via usb? (e.g. what happens if the i2c-tiny-usb is connected through a self powered hub?) Maybe the arm kernel barfs on i2c/usb transfer problems? Till Am Montag 09 Februar 2009 schrieb Martin Michlmayr: Hi Till and other I2C developers, Thomas Koch, a Debian user, reported the following backtrace with 2.6.26 related to i2c and possibly related to the i2c-tiny-usb driver. This is on an ARM device. Do you know if this is a known issue for which a patch is available in newer kernels, or is this a new bug? [42994982.81] Unable to handle kernel paging request at virtual address 692f7473 [42994982.81] pgd = c1da [42994982.81] [692f7473] *pgd= [42994982.81] Internal error: Oops: f3 [#2] [42994982.81] Modules linked in: ipv6 nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc nls_utf8 ntfs nls_base ext2 evdev ftdi_sio usbhid hid i2c_tiny_usb ff_memless usbserial ixp4xx_eth ixp4xx_npe firmware_class ixp4xx_qmgr ixp4xx_beeper ohci_hcd ext3 jbd mbcache sd_mod ehci_hcd usb_storage usbcorescsi_mod [42994982.81] CPU: 0Tainted: G D(2.6.26-1-ixp4xx #1) [42994982.81] PC is at module_put+0x20/0x48 [42994982.81] LR is at i2c_put_adapter+0x14/0x18 [42994982.81] pc : [c0060b00]lr : [c01940f4]psr: 2093 [42994982.81] sp : c0fc3c68 ip : c0fc3c78 fp : c0fc3c74 [42994982.81] r10: c18d3dd8 r9 : c1c0d120 r8 : [42994982.81] r7 : c1c1a208 r6 : 0008 r5 : c1daaac0 r4 : c13fe000 [42994982.81] r3 : 2093 r2 : 2013 r1 : c1daaac0 r0 : 692f7373 [42994982.81] Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user [42994982.81] Control: 397f Table: 01da DAC: 0015 [42994982.81] Process hcontrol (pid: 2671, stack limit = 0xc0fc2268) [42994982.81] Stack: (0xc0fc3c68 to 0xc0fc4000) [42994982.81] 3c60: c0fc3c84 c0fc3c78 c01940f4 c0060aec c0fc3c9c c0fc3c88 [42994982.81] 3c80: c0195d94 c01940ec c1daaac0 c0f0ea60 c0fc3cd4 c0fc3ca0 c009813c c0195d84 [42994982.81] 3ca0: c0ef9d30 c1daaac0 c1c1a200 c1c1a208 [42994982.81] 3cc0: 00f3 0001 c0fc3ce4 c0fc3cd8 c00984c4 c0098090 c0fc3d04 c0fc3ce8 [42994982.81] 3ce0: c0094dd0 c009849c c0f16e00 c1c1a200 0003 000c c0fc3d2c c0fc3d08 [42994982.81] 3d00: c0040980 c0094d64 c0f16e00 c0fc2000 c1e68060 000b c01941f8 0008 [42994982.81] 3d20: c0fc3d3c c0fc3d30 c0040a00 c0040904 c0fc3d54 c0fc3d40 c0041cf8 c00409e4 [42994982.81] 3d40: c003e550 c003e420 c0fc3d64 c0fc3d58 c0029de4 c0041aec c0fc3d84 c0fc3d68 [42994982.81] 3d60: c002c460 c0029b70 c0fc3ea0 00f3 692f7265 c0fc3ea0 c0fc3dac c0fc3d88 [42994982.81] 3d80: c002c718 c002c400 e5933000 c021db38 0013 e5933000 [42994982.81] 3da0: c0fc3dec c0fc3db0 c002e584 c002c6b4 c02c0a68 28841963 b229 [42994982.81] 3dc0: c0fc3df4 c02bc1bc 00f3 c0fc3ea0 692f7265 6013 [42994982.81] 3de0: c0fc3e9c c0fc3df0 c00251f0 c002e150 c005b76c c02bc4cc c0fc3e24 c0fc3e08 [42994982.81] 3e00: c003080c c00307a8 c02c1680 c02c1680 0005 c0fc3e3c c0fc3e28 [42994982.81] 3e20: c0043e2c c0037468 0005 0005 c0fc3e5c c0fc3e40 c002504c c0043dd4 [42994982.81] 3e40: c005b878 001f 0020 c0fc3eec c0fc3e60 c00256b0 c002500c [42994982.81] 3e60: 0001 c02c0a70 c0f374c0 0001 2883b65f b229 c0fc3f10 [42994982.81] 3e80: c0fc3ed4 be932b55 c051d360 c0025c48 c0fc3f04 c0fc3ea0 c002566c c00251c0 [42994982.81] 3ea0: c0fc2028 c0fc3f0c 0001 692f7265 c1c73a08 0001 be932b55 c051d360 [42994982.81] 3ec0: c0025c48 c0fc2000 c0fc3f04 c0fc3f08 c0fc3ee8 c0194cd4 c01941f8 [42994982.81] 3ee0: a013 0001 0001 be932b55 c051d360 c0fc3f2c c0fc3f08 [42994982.81] 3f00: c0194cd4 c01941ec c0fc3f4c 0001004b c13f0001 c051d360 be932b55 fff4 [42994982.81] 3f20: c0fc3f4c c0fc3f30 c01961ac c0194c98 c1daaac0 be932b55 c0fc3f78 0001 [42994982.81] 3f40: c0fc3f74 c0fc3f50 c0097778 c0196170 006d6561 0a6f c1daaac0 fff7 [42994982.81] 3f60: c0fc3fa4 c0fc3f78 c0097c44 c00976d0
Bug#514644: ipv6: net.ipv6.conf.*.temp_valid_lft counter seems to overflow
Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: normal #v+ # dev=wire # ip link set $dev down # sysctl -w net.ipv6.conf.$dev.use_tempaddr=2 net.ipv6.conf.wire.use_tempaddr = 2 # sysctl -w net.ipv6.conf.$dev.max_desync_factor=0 net.ipv6.conf.wire.max_desync_factor = 0 # sysctl -w net.ipv6.conf.$dev.temp_valid_lft=9 net.ipv6.conf.wire.temp_valid_lft = 9 # sysctl -w net.ipv6.conf.$dev.temp_prefered_lft=6 net.ipv6.conf.wire.temp_prefered_lft = 6 # ip address flush dev $dev 2/dev/null # ip link set $dev up # for x in `seq 1 25`; do sleep 1; ip -6 a sh dev $dev secondary | grep _lft; done valid_lft 9sec preferred_lft 604800sec valid_lft 8sec preferred_lft 604799sec valid_lft 6sec preferred_lft 604797sec valid_lft 5sec preferred_lft 604796sec valid_lft 4sec preferred_lft 604795sec valid_lft 3sec preferred_lft 604794sec valid_lft 2sec preferred_lft 604793sec valid_lft 1sec preferred_lft 604792sec valid_lft 0sec preferred_lft 604791sec valid_lft forever preferred_lft 604790sec valid_lft 4294967294sec preferred_lft 604789sec valid_lft 4294967293sec preferred_lft 604788sec valid_lft 4294967292sec preferred_lft 604787sec valid_lft 4294967291sec preferred_lft 604786sec valid_lft 4294967290sec preferred_lft 604785sec valid_lft 4294967289sec preferred_lft 604784sec valid_lft 4294967288sec preferred_lft 604783sec valid_lft 4294967287sec preferred_lft 604782sec valid_lft 4294967286sec preferred_lft 604781sec valid_lft 4294967285sec preferred_lft 604780sec valid_lft 4294967284sec preferred_lft 604779sec #v- It doesn't seems to be caused by relatively low value of temp_valid_lft, since I've succeed to reproduce this behaviour with temp_valid_lft = 200. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 18:29:31 UTC 2009 ** Not tainted -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.9-0exp2 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii lilo 1:22.8-7 LInux LOader - The Classic OS load pn linux-doc-2.6.26 none (no description available) -- debconf information excluded -- Piotr Lewandowski -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514646: ipv6: net.ipv6.conf.*.temp_prefered_lft value is ignored
Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: normal Documentation for temp_prefered_lft states that: #v+ temp_prefered_lft - INTEGER Preferred lifetime (in seconds) for temporary addresses. Default: 86400 (1 day) #v- But this setting seems to be ignored: #v+ # dev=wire # ip link set $dev down # sysctl -w net.ipv6.conf.$dev.use_tempaddr=2 net.ipv6.conf.wire.use_tempaddr = 2 # sysctl -w net.ipv6.conf.$dev.max_desync_factor=0 net.ipv6.conf.wire.max_desync_factor = 0 # sysctl -w net.ipv6.conf.$dev.temp_valid_lft=10 net.ipv6.conf.wire.temp_valid_lft = 10 # sysctl -w net.ipv6.conf.$dev.temp_prefered_lft=6 net.ipv6.conf.wire.temp_prefered_lft = 6 # ip address flush dev $dev # ip link set $dev up # sleep 5 # waiting for RA # ip -6 a sh dev $dev secondary 4: wire: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2001:6a0:12c:1100:1c54:33cb:4198:e058/64 scope global secondary tentative dynamic valid_lft 10sec preferred_lft 604800sec #v- Meanwhile, temp_valid_lft seems to be respected. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 18:29:31 UTC 2009 ** Not tainted -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.9-0exp2 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii lilo 1:22.8-7 LInux LOader - The Classic OS load pn linux-doc-2.6.26 none (no description available) -- debconf information excluded -- Piotr Lewandowski -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
It fails the same way with Lenny rc2 as previous versions did. Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#458467: linux-image-2.6.18-5-amd64 with 32bit userspace: xfs_fsr fails because ioctl32(xfs_fsr:15013): Unknown cmd
Moritz Muehlenhoff wrote: Does this error still occur with more recent kernel versions? If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html Miritz Muehlenhoff, Here are the results for this round. I tested with your linux-2.6.24 and testings version 2.6.26-1-amd64 (Debian 2.6.26-13) and Torvalds kernel linux-2.6.28 and I tried these with stable, testing and the current git version of the xfs_fsr tools from SGI (version 3.0.0). In each case I got the following new behavior. I no longer get any kernel messages to the system log. It fails, in a different way. Every ino that needs de-fragmenting get the following error: === ino=259367021 could not open tmp file: /.fsr/ag122/tmp3718: No such file or directory === Where 259367021, ag122 and tmp3718 change for each file that needs de-fragmenting. -- Jeffrey Hundstad -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508151: Bug#514624: linux-image for sparc64 sungem problems
On Mon, 9 Feb 2009 11:43:45 -0700 dann frazier wrote: Would you and/or Evgeni be able to test a 2.6.26 build to verify this fix if I provide one? I've just rebuilt 2.6.29-rc3 with the patch from http://marc.info/?l=linux-netdevm=123393014301523w=2 And it brought up the interface fine. There are some comments in http://marc.info/?l=linux-netdevm=123400984909800w=2 that the patch is good but prolly not enough. For me it is. Bringing the interface up and down works fine, traffic is too. So ACK from me to add this to Lenny r1. Regards Evgeni -- Bruce Schneier Fact Number 765: According to a recent survey, online buyers would trust ssl websites much more if their web browsers replaced the lock icon with a picture of Bruce Schneier. pgp7PuWHGSEk2.pgp Description: PGP signature
Re: Meeting(s) at FOSDEM
On Mon, Feb 09, 2009 at 06:30:00PM -0200, Otavio Salvador wrote: Steve McIntyre st...@einval.com writes: ... The main focus of the meeting was how d-i builds and releases work, and I think we made quite some progress on that. There are a few changes that we think should be made that will help a great deal in building, publishing and releasing d-i. I'm not posting any of the details here just yet because my memory fails me... :-) ... Please let me know those details as soon as possible :-) Oh, of course. :-) My beer-addled memory is not as reliable as it used to be, so I'm hoping that Mark's notes are more reliable. mhy: ping! -- Steve McIntyre, Cambridge, UK.st...@einval.com Welcome my son, welcome to the machine. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-2.6_2.6.18.dfsg.1-24_amd64.changes INSTALLED into stable
Installing: linux-2.6_2.6.18.dfsg.1-24.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24.diff.gz linux-2.6_2.6.18.dfsg.1-24.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24.dsc linux-doc-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-24_all.deb linux-headers-2.6.18-6-all-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-manual-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.18_2.6.18.dfsg.1-24_all.deb linux-modules-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb linux-modules-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-patch-debian-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.18_2.6.18.dfsg.1-24_all.deb linux-source-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-source-2.6.18_2.6.18.dfsg.1-24_all.deb linux-support-2.6.18-6_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-support-2.6.18-6_2.6.18.dfsg.1-24_all.deb linux-tree-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.18_2.6.18.dfsg.1-24_all.deb xen-linux-system-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/xen-linux-system-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb xen-linux-system-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/xen-linux-system-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb Override entries for your package: linux-2.6_2.6.18.dfsg.1-24.dsc - source devel linux-doc-2.6.18_2.6.18.dfsg.1-24_all.deb - optional doc linux-headers-2.6.18-6-all-amd64_2.6.18.dfsg.1-24_amd64.deb - optional devel linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24_amd64.deb - optional devel linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb - optional devel linux-headers-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb - optional devel linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24_amd64.deb - optional devel linux-headers-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb - optional devel linux-headers-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb - optional devel linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24_amd64.deb - optional devel linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24_amd64.deb - optional devel linux-headers-2.6.18-6_2.6.18.dfsg.1-24_amd64.deb - optional devel linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb - optional admin linux-image-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb - optional admin linux-image-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb - optional admin linux-image-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb - optional admin linux-manual-2.6.18_2.6.18.dfsg.1-24_all.deb - optional doc linux-modules-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb - optional admin linux-modules-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb -
linux-2.6.24_2.6.24-6~etchnhalf.8_hppa.changes INSTALLED into stable
Installing: linux-2.6.24_2.6.24-6~etchnhalf.8.diff.gz to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.8.diff.gz linux-2.6.24_2.6.24-6~etchnhalf.8.dsc to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.8.dsc linux-doc-2.6.24_2.6.24-6~etchnhalf.8_all.deb to pool/main/l/linux-2.6.24/linux-doc-2.6.24_2.6.24-6~etchnhalf.8_all.deb linux-headers-2.6.24-etchnhalf.1-all-hppa_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all-hppa_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-parisc-smp_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-parisc-smp_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-parisc64-smp_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-parisc64-smp_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-parisc64_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-parisc64_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-parisc_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-parisc_2.6.24-6~etchnhalf.8_hppa.deb linux-image-2.6.24-etchnhalf.1-parisc-smp_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-parisc-smp_2.6.24-6~etchnhalf.8_hppa.deb linux-image-2.6.24-etchnhalf.1-parisc64-smp_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-parisc64-smp_2.6.24-6~etchnhalf.8_hppa.deb linux-image-2.6.24-etchnhalf.1-parisc64_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-parisc64_2.6.24-6~etchnhalf.8_hppa.deb linux-image-2.6.24-etchnhalf.1-parisc_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-parisc_2.6.24-6~etchnhalf.8_hppa.deb linux-manual-2.6.24_2.6.24-6~etchnhalf.8_all.deb to pool/main/l/linux-2.6.24/linux-manual-2.6.24_2.6.24-6~etchnhalf.8_all.deb linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.8_all.deb to pool/main/l/linux-2.6.24/linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.8_all.deb linux-source-2.6.24_2.6.24-6~etchnhalf.8_all.deb to pool/main/l/linux-2.6.24/linux-source-2.6.24_2.6.24-6~etchnhalf.8_all.deb linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.8_all.deb to pool/main/l/linux-2.6.24/linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.8_all.deb linux-tree-2.6.24_2.6.24-6~etchnhalf.8_all.deb to pool/main/l/linux-2.6.24/linux-tree-2.6.24_2.6.24-6~etchnhalf.8_all.deb Override entries for your package: linux-2.6.24_2.6.24-6~etchnhalf.8.dsc - source devel linux-doc-2.6.24_2.6.24-6~etchnhalf.8_all.deb - optional doc linux-headers-2.6.24-etchnhalf.1-all-hppa_2.6.24-6~etchnhalf.8_hppa.deb - optional devel linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.8_hppa.deb - optional devel linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.8_hppa.deb - optional devel linux-headers-2.6.24-etchnhalf.1-parisc-smp_2.6.24-6~etchnhalf.8_hppa.deb - optional devel linux-headers-2.6.24-etchnhalf.1-parisc64-smp_2.6.24-6~etchnhalf.8_hppa.deb - optional devel linux-headers-2.6.24-etchnhalf.1-parisc64_2.6.24-6~etchnhalf.8_hppa.deb - optional devel linux-headers-2.6.24-etchnhalf.1-parisc_2.6.24-6~etchnhalf.8_hppa.deb - optional devel linux-image-2.6.24-etchnhalf.1-parisc-smp_2.6.24-6~etchnhalf.8_hppa.deb - optional admin linux-image-2.6.24-etchnhalf.1-parisc64-smp_2.6.24-6~etchnhalf.8_hppa.deb - optional admin linux-image-2.6.24-etchnhalf.1-parisc64_2.6.24-6~etchnhalf.8_hppa.deb - optional admin linux-image-2.6.24-etchnhalf.1-parisc_2.6.24-6~etchnhalf.8_hppa.deb - optional admin linux-manual-2.6.24_2.6.24-6~etchnhalf.8_all.deb - optional doc linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.8_all.deb - optional devel linux-source-2.6.24_2.6.24-6~etchnhalf.8_all.deb - optional devel linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.8_all.deb - optional devel linux-tree-2.6.24_2.6.24-6~etchnhalf.8_all.deb - optional devel Announcing to debian-chan...@lists.debian.org Closing bugs: 478717 502182 502553 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#502553: marked as done (support new smart array controllers)
Your message dated Mon, 09 Feb 2009 21:35:39 + with message-id e1lwdn1-0003cy...@ries.debian.org and subject line Bug#502553: fixed in linux-2.6 2.6.18.dfsg.1-24 has caused the Debian Bug report #502553, regarding support new smart array controllers to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 502553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.18.dfsg.1-23 Severity: important According to 24aac480e76c6f5d1391ac05c5e9c0eb9b0cd302, new smart array controllers will become available in late Fall 2008. This bug is to track the progress of adding support for these devices in etch. Patching in new Smart Array PCI IDs isn't strictly necessary, in general. There is a fallback mode in the cciss driver that recognizes Unknown Smart Array Controllers, and has some until recently sane defaults. The problem is that these defaults are no longer sane for newer hardware. The fallback 'max outstanding commands' setting is too high for the next generation controllers running in Zero Memory Raid mode. This means that the current etch kernels will happily detect and operate these newer controllers, but will be setting a queue depth too large for the controller's fifo. To resolve this, an additional patch is suggested that retrieves the queue depth setting from the card's config instead of hard coding each card's value in a table. 2.6.18 can also use 9cff3b383dad193b0762c27278a16237e10b53dc, adding pci ids for the previously released P700M controller, which is already supported in 2.6.24. -- dann frazier ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.18.dfsg.1-24 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.18.dfsg.1-24.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24.diff.gz linux-2.6_2.6.18.dfsg.1-24.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24.dsc linux-doc-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-24_all.deb linux-headers-2.6.18-6-all-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-manual-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.18_2.6.18.dfsg.1-24_all.deb linux-modules-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb linux-modules-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to
Bug#506420: marked as done (incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?)
Your message dated Mon, 09 Feb 2009 21:35:39 + with message-id e1lwdn1-0003cc...@ries.debian.org and subject line Bug#506420: fixed in linux-2.6 2.6.18.dfsg.1-24 has caused the Debian Bug report #506420, regarding incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 506420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libc6-xen Version: 2.7-16 As shipped, /etc/ld.so.conf.d/libc6-xen.conf read as follows: # This directive teaches ldconfig to search in nosegneg subdirectories # and cache the DSOs there with extra bit 1 set in their hwcap match # fields. In Xen guest kernels, the vDSO tells the dynamic linker to # search in nosegneg subdirectories and to match this extra hwcap bit # in the ld.so.cache file. hwcap 1 nosegneg However I still got thousands of 4gb seg fixup messages and ldd revealed that the runtime linker was not using the Xen-friendly Libc. Changing the 1 to 0, based on a mailing list posting I found, fixed the problem. Unfortunately I've not found where any of this is documented (the ldconfig man page does not contain any useful pointers) so this is slightly guesswork on my part. Perhaps the man page could be improved. (I'm using etch's Xen and running testing and unstable VMs; the kernel in all cases is 2.6.18-6-xen-686.) ttfn/rjk ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.18.dfsg.1-24 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.18.dfsg.1-24.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24.diff.gz linux-2.6_2.6.18.dfsg.1-24.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24.dsc linux-doc-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-24_all.deb linux-headers-2.6.18-6-all-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb linux-image-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-manual-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.18_2.6.18.dfsg.1-24_all.deb linux-modules-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb linux-modules-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-patch-debian-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.18_2.6.18.dfsg.1-24_all.deb
Bug#502553: marked as done (support new smart array controllers)
Your message dated Mon, 09 Feb 2009 21:35:30 + with message-id e1lwdms-0003bp...@ries.debian.org and subject line Bug#502553: fixed in fai-kernels 1.17+etch.24 has caused the Debian Bug report #502553, regarding support new smart array controllers to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 502553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.18.dfsg.1-23 Severity: important According to 24aac480e76c6f5d1391ac05c5e9c0eb9b0cd302, new smart array controllers will become available in late Fall 2008. This bug is to track the progress of adding support for these devices in etch. Patching in new Smart Array PCI IDs isn't strictly necessary, in general. There is a fallback mode in the cciss driver that recognizes Unknown Smart Array Controllers, and has some until recently sane defaults. The problem is that these defaults are no longer sane for newer hardware. The fallback 'max outstanding commands' setting is too high for the next generation controllers running in Zero Memory Raid mode. This means that the current etch kernels will happily detect and operate these newer controllers, but will be setting a queue depth too large for the controller's fifo. To resolve this, an additional patch is suggested that retrieves the queue depth setting from the card's config instead of hard coding each card's value in a table. 2.6.18 can also use 9cff3b383dad193b0762c27278a16237e10b53dc, adding pci ids for the previously released P700M controller, which is already supported in 2.6.24. -- dann frazier ---End Message--- ---BeginMessage--- Source: fai-kernels Source-Version: 1.17+etch.24 We believe that the bug you reported is fixed in the latest version of fai-kernels, which is due to be installed in the Debian FTP archive: fai-kernels_1.17+etch.24.dsc to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.dsc fai-kernels_1.17+etch.24.tar.gz to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.tar.gz fai-kernels_1.17+etch.24_i386.deb to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 502...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated fai-kernels package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 29 Dec 2008 11:36:34 -0700 Source: fai-kernels Binary: fai-kernels Architecture: source i386 Version: 1.17+etch.24 Distribution: stable Urgency: high Maintainer: Holger Levsen hol...@debian.org Changed-By: dann frazier da...@debian.org Description: fai-kernels - special kernels for FAI (Fully Automatic Installation) Closes: 391373 478717 502553 506418 506420 Changes: fai-kernels (1.17+etch.24) stable; urgency=high . * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-24: [ dann frazier ] * cciss: Add support for new hardware (closes: #502553) - Add PCI ids for P700m, P212, P410, P410i, P411, P812, P711m, p712m - Read the FIFO size from the controller config instead of hardcoding it into the driver * [hppa] disable UP-optimized flush_tlb_mm, fixing thread-related hangs. (closes: #478717) . [ Ian Campbell ] * xen: Add softlockup-no-idle-hz.patch to prevent softlockup in xen guest. (closes: #506418) . [ Bastian Blank ] * [xen] Remove 4gb segments warning completely. (closes: #391373) * [xen/i386] Fix pseudo hwcap value to match newer kernels. (closes: #506420) Files: f1dd70eeba3e86e5f3abbd51ffbe2189 725 admin extra fai-kernels_1.17+etch.24.dsc 70a28743493c996f9411c7b7a772f1ee 58059 admin extra fai-kernels_1.17+etch.24.tar.gz d1a10e3a5ab7a2f1d05bbe56e46f4f55 5509456 admin extra fai-kernels_1.17+etch.24_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJWTFRhuANDBmkLRkRAo3DAKCCzBUVZT6q5kNjP7lH4E9XwrTzbQCeKQwN YLiO7bRgFrEED4Iu2ZK+3kc= =QSXe -END PGP SIGNATURE- ---End Message---
Bug#506418: marked as done (linux-image-2.6.18-6-xen-amd64: domU soft lockup detected)
Your message dated Mon, 09 Feb 2009 21:35:39 + with message-id e1lwdn1-0003ca...@ries.debian.org and subject line Bug#506418: fixed in linux-2.6 2.6.18.dfsg.1-24 has caused the Debian Bug report #506418, regarding linux-image-2.6.18-6-xen-amd64: domU soft lockup detected to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 506418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-6-xen-amd64 Version: 2.6.18.dfsg.1-23 Severity: normal domU is getting these from time to time (no live migration is being done): BUG: soft lockup detected on CPU#1! Call Trace: IRQ [8029fb75] softlockup_tick+0xdb/0xed [80267dc0] timer_interrupt+0x38d/0x3db [80211162] handle_IRQ_event+0x2d/0x60 [8029feb4] __do_IRQ+0xa4/0x105 [8028366f] _local_bh_enable+0x59/0xb3 [802665ae] do_IRQ+0x65/0x73 [80361105] evtchn_do_upcall+0x86/0xe0 [8025c606] do_hypervisor_callback+0x1e/0x2c EOI [802063aa] hypercall_page+0x3aa/0x1000 [802063aa] hypercall_page+0x3aa/0x1000 [8026733c] raw_safe_halt+0x84/0xa8 [802645b1] xen_idle+0x38/0x4a [80248830] cpu_idle+0x97/0xba BUG: soft lockup detected on CPU#2! Call Trace: IRQ [8029fb75] softlockup_tick+0xdb/0xed [80267dc0] timer_interrupt+0x38d/0x3db [80211162] handle_IRQ_event+0x2d/0x60 [8029feb4] __do_IRQ+0xa4/0x105 [8028366f] _local_bh_enable+0x59/0xb3 [802665ae] do_IRQ+0x65/0x73 [80361105] evtchn_do_upcall+0x86/0xe0 [8025c606] do_hypervisor_callback+0x1e/0x2c EOI [802063aa] hypercall_page+0x3aa/0x1000 [802063aa] hypercall_page+0x3aa/0x1000 [8026733c] raw_safe_halt+0x84/0xa8 [802645b1] xen_idle+0x38/0x4a [80248830] cpu_idle+0x97/0xba There are other reports of this bug in Debian Etch kernel: http://lists.xensource.com/archives/html/xen-bugs/2008-10/msg3.html http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1261 And RedHat seems to have a patch you might be able to use: https://bugzilla.redhat.com/show_bug.cgi?id=250994 -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-xen-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-6-xen-amd64 depends on: ii e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 file system utilities and lib ii ini 0.85itools for generating an initramfs ii lin 2.6.18.dfsg.1-23 Linux 2.6.18 modules on AMD64 linux-image-2.6.18-6-xen-amd64 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.18.dfsg.1-24 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.18.dfsg.1-24.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24.diff.gz linux-2.6_2.6.18.dfsg.1-24.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24.dsc linux-doc-2.6.18_2.6.18.dfsg.1-24_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-24_all.deb linux-headers-2.6.18-6-all-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver-amd64_2.6.18.dfsg.1-24_amd64.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24_amd64.deb
Bug#506420: marked as done (incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?)
Your message dated Mon, 09 Feb 2009 21:35:30 + with message-id e1lwdms-0003bt...@ries.debian.org and subject line Bug#506420: fixed in fai-kernels 1.17+etch.24 has caused the Debian Bug report #506420, regarding incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 506420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libc6-xen Version: 2.7-16 As shipped, /etc/ld.so.conf.d/libc6-xen.conf read as follows: # This directive teaches ldconfig to search in nosegneg subdirectories # and cache the DSOs there with extra bit 1 set in their hwcap match # fields. In Xen guest kernels, the vDSO tells the dynamic linker to # search in nosegneg subdirectories and to match this extra hwcap bit # in the ld.so.cache file. hwcap 1 nosegneg However I still got thousands of 4gb seg fixup messages and ldd revealed that the runtime linker was not using the Xen-friendly Libc. Changing the 1 to 0, based on a mailing list posting I found, fixed the problem. Unfortunately I've not found where any of this is documented (the ldconfig man page does not contain any useful pointers) so this is slightly guesswork on my part. Perhaps the man page could be improved. (I'm using etch's Xen and running testing and unstable VMs; the kernel in all cases is 2.6.18-6-xen-686.) ttfn/rjk ---End Message--- ---BeginMessage--- Source: fai-kernels Source-Version: 1.17+etch.24 We believe that the bug you reported is fixed in the latest version of fai-kernels, which is due to be installed in the Debian FTP archive: fai-kernels_1.17+etch.24.dsc to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.dsc fai-kernels_1.17+etch.24.tar.gz to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.tar.gz fai-kernels_1.17+etch.24_i386.deb to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 506...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated fai-kernels package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 29 Dec 2008 11:36:34 -0700 Source: fai-kernels Binary: fai-kernels Architecture: source i386 Version: 1.17+etch.24 Distribution: stable Urgency: high Maintainer: Holger Levsen hol...@debian.org Changed-By: dann frazier da...@debian.org Description: fai-kernels - special kernels for FAI (Fully Automatic Installation) Closes: 391373 478717 502553 506418 506420 Changes: fai-kernels (1.17+etch.24) stable; urgency=high . * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-24: [ dann frazier ] * cciss: Add support for new hardware (closes: #502553) - Add PCI ids for P700m, P212, P410, P410i, P411, P812, P711m, p712m - Read the FIFO size from the controller config instead of hardcoding it into the driver * [hppa] disable UP-optimized flush_tlb_mm, fixing thread-related hangs. (closes: #478717) . [ Ian Campbell ] * xen: Add softlockup-no-idle-hz.patch to prevent softlockup in xen guest. (closes: #506418) . [ Bastian Blank ] * [xen] Remove 4gb segments warning completely. (closes: #391373) * [xen/i386] Fix pseudo hwcap value to match newer kernels. (closes: #506420) Files: f1dd70eeba3e86e5f3abbd51ffbe2189 725 admin extra fai-kernels_1.17+etch.24.dsc 70a28743493c996f9411c7b7a772f1ee 58059 admin extra fai-kernels_1.17+etch.24.tar.gz d1a10e3a5ab7a2f1d05bbe56e46f4f55 5509456 admin extra fai-kernels_1.17+etch.24_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJWTFRhuANDBmkLRkRAo3DAKCCzBUVZT6q5kNjP7lH4E9XwrTzbQCeKQwN YLiO7bRgFrEED4Iu2ZK+3kc= =QSXe -END PGP SIGNATURE- ---End Message---
Bug#506420: marked as done (incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?)
Your message dated Mon, 09 Feb 2009 21:35:53 + with message-id e1lwdnf-0003ew...@ries.debian.org and subject line Bug#506420: fixed in user-mode-linux 2.6.18-1um-2etch.24 has caused the Debian Bug report #506420, regarding incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 506420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libc6-xen Version: 2.7-16 As shipped, /etc/ld.so.conf.d/libc6-xen.conf read as follows: # This directive teaches ldconfig to search in nosegneg subdirectories # and cache the DSOs there with extra bit 1 set in their hwcap match # fields. In Xen guest kernels, the vDSO tells the dynamic linker to # search in nosegneg subdirectories and to match this extra hwcap bit # in the ld.so.cache file. hwcap 1 nosegneg However I still got thousands of 4gb seg fixup messages and ldd revealed that the runtime linker was not using the Xen-friendly Libc. Changing the 1 to 0, based on a mailing list posting I found, fixed the problem. Unfortunately I've not found where any of this is documented (the ldconfig man page does not contain any useful pointers) so this is slightly guesswork on my part. Perhaps the man page could be improved. (I'm using etch's Xen and running testing and unstable VMs; the kernel in all cases is 2.6.18-6-xen-686.) ttfn/rjk ---End Message--- ---BeginMessage--- Source: user-mode-linux Source-Version: 2.6.18-1um-2etch.24 We believe that the bug you reported is fixed in the latest version of user-mode-linux, which is due to be installed in the Debian FTP archive: user-mode-linux_2.6.18-1um-2etch.24.diff.gz to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.diff.gz user-mode-linux_2.6.18-1um-2etch.24.dsc to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.dsc user-mode-linux_2.6.18-1um-2etch.24_i386.deb to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 506...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated user-mode-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 29 Dec 2008 12:11:56 -0700 Source: user-mode-linux Binary: user-mode-linux Architecture: source i386 Version: 2.6.18-1um-2etch.24 Distribution: stable Urgency: high Maintainer: User Mode Linux Maintainers pkg-uml-p...@lists.alioth.debian.org Changed-By: dann frazier da...@debian.org Description: user-mode-linux - User-mode Linux (kernel) Closes: 391373 478717 502553 506418 506420 Changes: user-mode-linux (2.6.18-1um-2etch.24) stable; urgency=high . * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-24: [ dann frazier ] * cciss: Add support for new hardware (closes: #502553) - Add PCI ids for P700m, P212, P410, P410i, P411, P812, P711m, p712m - Read the FIFO size from the controller config instead of hardcoding it into the driver * [hppa] disable UP-optimized flush_tlb_mm, fixing thread-related hangs. (closes: #478717) . [ Ian Campbell ] * xen: Add softlockup-no-idle-hz.patch to prevent softlockup in xen guest. (closes: #506418) . [ Bastian Blank ] * [xen] Remove 4gb segments warning completely. (closes: #391373) * [xen/i386] Fix pseudo hwcap value to match newer kernels. (closes: #506420) Files: a1c5b965f88cba4b1b710130f20944a2 877 misc extra user-mode-linux_2.6.18-1um-2etch.24.dsc 6f58c7c625c76ff7fdeeb32c502b953f 19691 misc extra user-mode-linux_2.6.18-1um-2etch.24.diff.gz 692cf2f50488b66dc333b12eacafbd98 25602764 misc extra user-mode-linux_2.6.18-1um-2etch.24_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJWTFXhuANDBmkLRkRAhAvAJ4wkOuy4otOgudHnknNp7SCD3qHnQCdHHIB 6ZQfZgyGylRq309vJ4m6jvE= =hdlK -END PGP SIGNATURE- ---End Message---
Bug#506418: marked as done (linux-image-2.6.18-6-xen-amd64: domU soft lockup detected)
Your message dated Mon, 09 Feb 2009 21:35:30 + with message-id e1lwdms-0003br...@ries.debian.org and subject line Bug#506418: fixed in fai-kernels 1.17+etch.24 has caused the Debian Bug report #506418, regarding linux-image-2.6.18-6-xen-amd64: domU soft lockup detected to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 506418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-6-xen-amd64 Version: 2.6.18.dfsg.1-23 Severity: normal domU is getting these from time to time (no live migration is being done): BUG: soft lockup detected on CPU#1! Call Trace: IRQ [8029fb75] softlockup_tick+0xdb/0xed [80267dc0] timer_interrupt+0x38d/0x3db [80211162] handle_IRQ_event+0x2d/0x60 [8029feb4] __do_IRQ+0xa4/0x105 [8028366f] _local_bh_enable+0x59/0xb3 [802665ae] do_IRQ+0x65/0x73 [80361105] evtchn_do_upcall+0x86/0xe0 [8025c606] do_hypervisor_callback+0x1e/0x2c EOI [802063aa] hypercall_page+0x3aa/0x1000 [802063aa] hypercall_page+0x3aa/0x1000 [8026733c] raw_safe_halt+0x84/0xa8 [802645b1] xen_idle+0x38/0x4a [80248830] cpu_idle+0x97/0xba BUG: soft lockup detected on CPU#2! Call Trace: IRQ [8029fb75] softlockup_tick+0xdb/0xed [80267dc0] timer_interrupt+0x38d/0x3db [80211162] handle_IRQ_event+0x2d/0x60 [8029feb4] __do_IRQ+0xa4/0x105 [8028366f] _local_bh_enable+0x59/0xb3 [802665ae] do_IRQ+0x65/0x73 [80361105] evtchn_do_upcall+0x86/0xe0 [8025c606] do_hypervisor_callback+0x1e/0x2c EOI [802063aa] hypercall_page+0x3aa/0x1000 [802063aa] hypercall_page+0x3aa/0x1000 [8026733c] raw_safe_halt+0x84/0xa8 [802645b1] xen_idle+0x38/0x4a [80248830] cpu_idle+0x97/0xba There are other reports of this bug in Debian Etch kernel: http://lists.xensource.com/archives/html/xen-bugs/2008-10/msg3.html http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1261 And RedHat seems to have a patch you might be able to use: https://bugzilla.redhat.com/show_bug.cgi?id=250994 -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-xen-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-6-xen-amd64 depends on: ii e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 file system utilities and lib ii ini 0.85itools for generating an initramfs ii lin 2.6.18.dfsg.1-23 Linux 2.6.18 modules on AMD64 linux-image-2.6.18-6-xen-amd64 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: fai-kernels Source-Version: 1.17+etch.24 We believe that the bug you reported is fixed in the latest version of fai-kernels, which is due to be installed in the Debian FTP archive: fai-kernels_1.17+etch.24.dsc to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.dsc fai-kernels_1.17+etch.24.tar.gz to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.tar.gz fai-kernels_1.17+etch.24_i386.deb to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 506...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated fai-kernels package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 29 Dec 2008 11:36:34 -0700 Source: fai-kernels Binary: fai-kernels Architecture: source i386 Version: 1.17+etch.24 Distribution: stable Urgency: high Maintainer: Holger Levsen hol...@debian.org Changed-By: dann frazier da...@debian.org Description: fai-kernels - special kernels for FAI (Fully Automatic Installation) Closes: 391373 478717 502553 506418 506420 Changes: fai-kernels (1.17+etch.24) stable; urgency=high . * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-24: [ dann frazier ] * cciss: Add support for new hardware (closes: #502553) - Add
Bug#506418: marked as done (linux-image-2.6.18-6-xen-amd64: domU soft lockup detected)
Your message dated Mon, 09 Feb 2009 21:35:53 + with message-id e1lwdnf-0003eu...@ries.debian.org and subject line Bug#506418: fixed in user-mode-linux 2.6.18-1um-2etch.24 has caused the Debian Bug report #506418, regarding linux-image-2.6.18-6-xen-amd64: domU soft lockup detected to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 506418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-6-xen-amd64 Version: 2.6.18.dfsg.1-23 Severity: normal domU is getting these from time to time (no live migration is being done): BUG: soft lockup detected on CPU#1! Call Trace: IRQ [8029fb75] softlockup_tick+0xdb/0xed [80267dc0] timer_interrupt+0x38d/0x3db [80211162] handle_IRQ_event+0x2d/0x60 [8029feb4] __do_IRQ+0xa4/0x105 [8028366f] _local_bh_enable+0x59/0xb3 [802665ae] do_IRQ+0x65/0x73 [80361105] evtchn_do_upcall+0x86/0xe0 [8025c606] do_hypervisor_callback+0x1e/0x2c EOI [802063aa] hypercall_page+0x3aa/0x1000 [802063aa] hypercall_page+0x3aa/0x1000 [8026733c] raw_safe_halt+0x84/0xa8 [802645b1] xen_idle+0x38/0x4a [80248830] cpu_idle+0x97/0xba BUG: soft lockup detected on CPU#2! Call Trace: IRQ [8029fb75] softlockup_tick+0xdb/0xed [80267dc0] timer_interrupt+0x38d/0x3db [80211162] handle_IRQ_event+0x2d/0x60 [8029feb4] __do_IRQ+0xa4/0x105 [8028366f] _local_bh_enable+0x59/0xb3 [802665ae] do_IRQ+0x65/0x73 [80361105] evtchn_do_upcall+0x86/0xe0 [8025c606] do_hypervisor_callback+0x1e/0x2c EOI [802063aa] hypercall_page+0x3aa/0x1000 [802063aa] hypercall_page+0x3aa/0x1000 [8026733c] raw_safe_halt+0x84/0xa8 [802645b1] xen_idle+0x38/0x4a [80248830] cpu_idle+0x97/0xba There are other reports of this bug in Debian Etch kernel: http://lists.xensource.com/archives/html/xen-bugs/2008-10/msg3.html http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1261 And RedHat seems to have a patch you might be able to use: https://bugzilla.redhat.com/show_bug.cgi?id=250994 -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-xen-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-6-xen-amd64 depends on: ii e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 file system utilities and lib ii ini 0.85itools for generating an initramfs ii lin 2.6.18.dfsg.1-23 Linux 2.6.18 modules on AMD64 linux-image-2.6.18-6-xen-amd64 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: user-mode-linux Source-Version: 2.6.18-1um-2etch.24 We believe that the bug you reported is fixed in the latest version of user-mode-linux, which is due to be installed in the Debian FTP archive: user-mode-linux_2.6.18-1um-2etch.24.diff.gz to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.diff.gz user-mode-linux_2.6.18-1um-2etch.24.dsc to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.dsc user-mode-linux_2.6.18-1um-2etch.24_i386.deb to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 506...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated user-mode-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 29 Dec 2008 12:11:56 -0700 Source: user-mode-linux Binary: user-mode-linux Architecture: source i386 Version: 2.6.18-1um-2etch.24 Distribution: stable Urgency: high Maintainer: User Mode Linux Maintainers pkg-uml-p...@lists.alioth.debian.org Changed-By: dann frazier da...@debian.org Description: user-mode-linux - User-mode Linux (kernel) Closes: 391373 478717 502553 506418 506420 Changes: user-mode-linux (2.6.18-1um-2etch.24) stable; urgency=high . * Rebuild
Bug#502553: marked as done (support new smart array controllers)
Your message dated Mon, 09 Feb 2009 21:35:40 + with message-id e1lwdn2-0003cm...@ries.debian.org and subject line Bug#502553: fixed in linux-2.6.24 2.6.24-6~etchnhalf.8 has caused the Debian Bug report #502553, regarding support new smart array controllers to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 502553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.18.dfsg.1-23 Severity: important According to 24aac480e76c6f5d1391ac05c5e9c0eb9b0cd302, new smart array controllers will become available in late Fall 2008. This bug is to track the progress of adding support for these devices in etch. Patching in new Smart Array PCI IDs isn't strictly necessary, in general. There is a fallback mode in the cciss driver that recognizes Unknown Smart Array Controllers, and has some until recently sane defaults. The problem is that these defaults are no longer sane for newer hardware. The fallback 'max outstanding commands' setting is too high for the next generation controllers running in Zero Memory Raid mode. This means that the current etch kernels will happily detect and operate these newer controllers, but will be setting a queue depth too large for the controller's fifo. To resolve this, an additional patch is suggested that retrieves the queue depth setting from the card's config instead of hard coding each card's value in a table. 2.6.18 can also use 9cff3b383dad193b0762c27278a16237e10b53dc, adding pci ids for the previously released P700M controller, which is already supported in 2.6.24. -- dann frazier ---End Message--- ---BeginMessage--- Source: linux-2.6.24 Source-Version: 2.6.24-6~etchnhalf.8 We believe that the bug you reported is fixed in the latest version of linux-2.6.24, which is due to be installed in the Debian FTP archive: linux-2.6.24_2.6.24-6~etchnhalf.8.diff.gz to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.8.diff.gz linux-2.6.24_2.6.24-6~etchnhalf.8.dsc to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.8.dsc linux-doc-2.6.24_2.6.24-6~etchnhalf.8_all.deb to pool/main/l/linux-2.6.24/linux-doc-2.6.24_2.6.24-6~etchnhalf.8_all.deb linux-headers-2.6.24-etchnhalf.1-all-hppa_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all-hppa_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-parisc-smp_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-parisc-smp_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-parisc64-smp_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-parisc64-smp_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-parisc64_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-parisc64_2.6.24-6~etchnhalf.8_hppa.deb linux-headers-2.6.24-etchnhalf.1-parisc_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-parisc_2.6.24-6~etchnhalf.8_hppa.deb linux-image-2.6.24-etchnhalf.1-parisc-smp_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-parisc-smp_2.6.24-6~etchnhalf.8_hppa.deb linux-image-2.6.24-etchnhalf.1-parisc64-smp_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-parisc64-smp_2.6.24-6~etchnhalf.8_hppa.deb linux-image-2.6.24-etchnhalf.1-parisc64_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-parisc64_2.6.24-6~etchnhalf.8_hppa.deb linux-image-2.6.24-etchnhalf.1-parisc_2.6.24-6~etchnhalf.8_hppa.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-parisc_2.6.24-6~etchnhalf.8_hppa.deb linux-manual-2.6.24_2.6.24-6~etchnhalf.8_all.deb to pool/main/l/linux-2.6.24/linux-manual-2.6.24_2.6.24-6~etchnhalf.8_all.deb linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.8_all.deb to pool/main/l/linux-2.6.24/linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.8_all.deb linux-source-2.6.24_2.6.24-6~etchnhalf.8_all.deb to pool/main/l/linux-2.6.24/linux-source-2.6.24_2.6.24-6~etchnhalf.8_all.deb
Bug#502553: marked as done (support new smart array controllers)
Your message dated Mon, 09 Feb 2009 21:35:53 + with message-id e1lwdnf-0003es...@ries.debian.org and subject line Bug#502553: fixed in user-mode-linux 2.6.18-1um-2etch.24 has caused the Debian Bug report #502553, regarding support new smart array controllers to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 502553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.18.dfsg.1-23 Severity: important According to 24aac480e76c6f5d1391ac05c5e9c0eb9b0cd302, new smart array controllers will become available in late Fall 2008. This bug is to track the progress of adding support for these devices in etch. Patching in new Smart Array PCI IDs isn't strictly necessary, in general. There is a fallback mode in the cciss driver that recognizes Unknown Smart Array Controllers, and has some until recently sane defaults. The problem is that these defaults are no longer sane for newer hardware. The fallback 'max outstanding commands' setting is too high for the next generation controllers running in Zero Memory Raid mode. This means that the current etch kernels will happily detect and operate these newer controllers, but will be setting a queue depth too large for the controller's fifo. To resolve this, an additional patch is suggested that retrieves the queue depth setting from the card's config instead of hard coding each card's value in a table. 2.6.18 can also use 9cff3b383dad193b0762c27278a16237e10b53dc, adding pci ids for the previously released P700M controller, which is already supported in 2.6.24. -- dann frazier ---End Message--- ---BeginMessage--- Source: user-mode-linux Source-Version: 2.6.18-1um-2etch.24 We believe that the bug you reported is fixed in the latest version of user-mode-linux, which is due to be installed in the Debian FTP archive: user-mode-linux_2.6.18-1um-2etch.24.diff.gz to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.diff.gz user-mode-linux_2.6.18-1um-2etch.24.dsc to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.dsc user-mode-linux_2.6.18-1um-2etch.24_i386.deb to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 502...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated user-mode-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 29 Dec 2008 12:11:56 -0700 Source: user-mode-linux Binary: user-mode-linux Architecture: source i386 Version: 2.6.18-1um-2etch.24 Distribution: stable Urgency: high Maintainer: User Mode Linux Maintainers pkg-uml-p...@lists.alioth.debian.org Changed-By: dann frazier da...@debian.org Description: user-mode-linux - User-mode Linux (kernel) Closes: 391373 478717 502553 506418 506420 Changes: user-mode-linux (2.6.18-1um-2etch.24) stable; urgency=high . * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-24: [ dann frazier ] * cciss: Add support for new hardware (closes: #502553) - Add PCI ids for P700m, P212, P410, P410i, P411, P812, P711m, p712m - Read the FIFO size from the controller config instead of hardcoding it into the driver * [hppa] disable UP-optimized flush_tlb_mm, fixing thread-related hangs. (closes: #478717) . [ Ian Campbell ] * xen: Add softlockup-no-idle-hz.patch to prevent softlockup in xen guest. (closes: #506418) . [ Bastian Blank ] * [xen] Remove 4gb segments warning completely. (closes: #391373) * [xen/i386] Fix pseudo hwcap value to match newer kernels. (closes: #506420) Files: a1c5b965f88cba4b1b710130f20944a2 877 misc extra user-mode-linux_2.6.18-1um-2etch.24.dsc 6f58c7c625c76ff7fdeeb32c502b953f 19691 misc extra user-mode-linux_2.6.18-1um-2etch.24.diff.gz 692cf2f50488b66dc333b12eacafbd98 25602764 misc extra user-mode-linux_2.6.18-1um-2etch.24_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJWTFXhuANDBmkLRkRAhAvAJ4wkOuy4otOgudHnknNp7SCD3qHnQCdHHIB 6ZQfZgyGylRq309vJ4m6jvE= =hdlK -END PGP SIGNATURE-
Processed: tagging 502553
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.9.26etch1 tags 502553 + pending Bug#502553: support new smart array controllers There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 506420
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.9.26etch1 tags 506420 + pending Bug#506420: incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf? There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 506418
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.9.26etch1 tags 506418 + pending Bug#506418: linux-image-2.6.18-6-xen-amd64: domU soft lockup detected There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 502553
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.9.26etch1 tags 502553 + pending Bug#502553: support new smart array controllers Tags were: pending Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508151: Bug#514624: linux-image for sparc64 sungem problems
On Mon, Feb 09, 2009 at 07:54:24PM +, Alexander Clouter wrote: Would you and/or Evgeni be able to test a 2.6.26 build to verify this fix if I provide one? Guess I would be then committing myself to move to lenny sooner rather than later for my co-locatin box :) Sure, why not. On Mon, Feb 09, 2009 at 10:01:34PM +0100, Evgeni Golov wrote: On Mon, 9 Feb 2009 11:43:45 -0700 dann frazier wrote: Would you and/or Evgeni be able to test a 2.6.26 build to verify this fix if I provide one? I've just rebuilt 2.6.29-rc3 with the patch from http://marc.info/?l=linux-netdevm=123393014301523w=2 And it brought up the interface fine. There are some comments in http://marc.info/?l=linux-netdevm=123400984909800w=2 that the patch is good but prolly not enough. For me it is. Bringing the interface up and down works fine, traffic is too. So ACK from me to add this to Lenny r1. I'm transferring a build w/ the fix backported to the lenny kernel to here: http://people.debian.org/~dannf/bugs/514624/ If one or both of you could verify that it resolves the issue for you as well, it'd be appreciated. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 514624
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.9.26etch1 tags 514624 + pending Bug#514624: linux-image for sparc64 sungem problems There were no tags set. Bug#508151: linux-image-2.6.26-1-sparc64: soft lockup when trying to bring up eth1 Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#496850: linux-image-2.6.18-6-486: bogomips reduced from 100 to 20 after package upgrade
I believe this is resolved with version 2.6.18.dfsg.1-24 of linux-image-2.6.18-6.486: # cat /proc/cpuinfo processor : 0 vendor_id : unknown cpu family : 4 model : 0 model name : 486 stepping: unknown fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : no fpu_exception : no cpuid level : -1 wp : yes flags : bogomips: 97.79 Best regards, Kevin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
