Bug#565494: linux-image-2.6.26-2-amd64: does not include CONFIG_INFINIBAND_IPOIB_CM infiniband connected mode
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-19lenny2 Severity: wishlist Hi, On infiniband kernel 2.6.32-trunk-686 from debian, /sys/class/net/ib0/mode is missing to toggle infiniband connected mode it is usefull to size up MTU to boost IPoIB network traffic performance, Can you please add CONFIG_INFINIBAND_IPOIB_CM=y to default kernel ? http://www.mail-archive.com/linux-r...@vger.kernel.org/msg02127.html Regards. Nicolas -- Package-specific info: -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (999, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-amd64 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-2-amd64 recommends no packages. Versions of packages linux-image-2.6.26-2-amd64 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none(no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526983: r8169
linux-image-2.6.26-2-amd64-2.6.26-21 fixes this r8169 issue for me. No more problems. Thanks! Marcel. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [Users] New Kernel Patch
On Sat, Jan 16, 2010 at 12:17:19PM +0100, Suno Ano wrote: currently (January 2010) mainline is in development for the .33 release, .32 is stable and used by most Linux Distributions like for example Debian, Ubuntu, Suse, etc. From what it looks now Debian and Ubuntu are going into freeze for their next stable release in March 2010. Will there be an up-to-date OpenVZ kernel patch available by then? Debian is targeting to ship .32 with their next stable release called squeeze. In case OpenVZ will not be available on at least one of the major Linux distributions and its offsprings, no need to mention how horrid that would be ... http://lists.debian.org/debian-devel-announce/2009/10/msg3.html said OpenVZ will remain supported, but and http://lists.debian.org/debian-release/2009/08/msg00233.html had previously went unanswered and I don't see anything new at http://packages.debian.org/linux-image-2.6-openvz-686 I'm thinking the most usable compromise would be if someone volunteered to maintain the Debian packages of the actual kernel stable release 2.6.27 - where the meaning of stable more closely corresponds to the Debian stable release concept. For off-the-shelf usage, mainline releases can satisfy the same definition, but for corner cases it's doubtful because they tend to move too fast for people to track them reliably. I have to mention that Xen has a similar problem - there are XCI 2.6.27 patches which seem to be maintained, whereas it's doubtful anyone really wants to continue forward-porting the old branch to .32. Xen upstream do have an advanced paravirt_ops dom0 branch (it's much further along than LXC vs. OpenVZ, judging by the LXC description in this thread), but it would still be a regression compared to the old branch for some people who use some of those still-unimplemented features, so it's not a drop-in replacement yet. I'm Cc:ing Adrian Bunk - given that you initated the marking of .27 as the real stable, and Greg KH is still maintaining .27 upstream, I can't help but wonder if you might be willing to maintain those packages? :) Also Cc:'ing the debian-kernel mailing list. -- 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#534880: Same problem here
Hi Everybody, I confirm this bug on three different servers, with amd64 architecture. I've updated all dom0 and domU with linux-image-2.6.26-2-xen-amd64 2.6.26-20 and reboot the servers at 2009-12-20. Since this upgrade, we already have two domU in unresponsive state, with the same behaviour in this bug report (ssh, ping, xm console, etc...) Each time I've added a domU with vcpu 1 on a physical server, the time between each unresponsive state is reduced. I've posted a bug report on the Xen's bugzilla: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1564 We don't have Xen development skills, but we can recompile our kernels with some options to generate a backtrace. Yours. -- Ludovic Gasc - DMoon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-image-2.6.30-2-amd64 - config
Hello, to recompile my kernel for Lenny i downloaded source, then, to do first, i downloaded the following pkg to retrieve the. config http://ftp.it.debian.org/debian/pool/main/l/linux-2.6/linux-image-2.6.30-2-amd64_2.6.30-8_amd64.deb http://www.backports.org/debian/pool/main/l/linux-2.6/linux-image-2.6.30-bpo.2-amd64_2.6.30-8~bpo50+2_amd64.deb Surprise, the CPU is not selected. # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set Regards, Ferdinando -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#565511: ext4.ko module missing from initramfs
Processing commands for cont...@bugs.debian.org: reassign 565511 initramfs-tools 0.93.4 Bug #565511 [installation-reports] installation-reports: Failure with ext4 on Acer Aspire One Bug reassigned from package 'installation-reports' to 'initramfs-tools'. Bug #565511 [initramfs-tools] installation-reports: Failure with ext4 on Acer Aspire One Bug Marked as found in versions initramfs-tools/0.93.4. retitle 565511 ext4.ko module missing from dep initramfs Bug #565511 [initramfs-tools] installation-reports: Failure with ext4 on Acer Aspire One Changed Bug title to 'ext4.ko module missing from dep initramfs' from 'installation-reports: Failure with ext4 on Acer Aspire One' 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
Re: Bug#565511: ext4.ko module missing from initramfs
reassign 565511 initramfs-tools 0.93.4 retitle 565511 ext4.ko module missing from dep initramfs thanks On Saturday 16 January 2010, ael wrote: On further investigation, I find that /lib/modules/2.6.30-2-686/kernel/fs/ext4/ext4.ko is missing from the initramfs. I assume that this explains the failure. I do now seem to remember choosing a slim initrd during installation. That's the problem. The ext4 module *would* have been included if you'd selected the standard initrd. Going into rescue mode, I could not find any way to revert to a full initrd. Just edit the initramfs-tools configuration file in /etc for the installed system to use 'MODULES=most' and then regenerate the initrd (see 'man update-initramfs'). I could not see any bug about this against linux-image-2.6.30-2-686. I assume it generates initrd? No, the package is initramfs-tools. Not sure that it is a bug though. I'm reassigning your report because maybe initramfs-tools should be detecting that ext4 is needed in this case. We'll let its maintainer decide. So it seems that while the installer supports ext4, the installed target system initrd does not. Only because you used an expert option without knowing the consequences or knowing how to fix it. You really should have stuck to the default! So I guess that I will have to compile my own kernel on the target and then change to ext4 via the rescue mode (it's the root partition) later. That's absolutely not necessary. You only need to get ext4 included in the initrd. Cheers, FJP -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565511: ext4.ko module missing from initramfs
On Sunday 17 January 2010, Frans Pop wrote: On Saturday 16 January 2010, ael wrote: On further investigation, I find that /lib/modules/2.6.30-2-686/kernel/fs/ext4/ext4.ko is missing from the initramfs. I assume that this explains the failure. I do now seem to remember choosing a slim initrd during installation. That's the problem. The ext4 module *would* have been included if you'd selected the standard initrd. I cannot reproduce the problem though. If I install a system with an ext4 root file system and MODULES=dep for initramfs-tools, the ext4 module gets correctly included in the initrd and the installed system boots fine. I wonder if the issue isn't caused by the initial problems you had with your SSD. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565511: ext4.ko module missing from initramfs
* Frans Pop elen...@planet.nl [2010-01-17 01:13]: I cannot reproduce the problem though. If I install a system with an ext4 root file system and MODULES=dep for initramfs-tools, the ext4 module gets correctly included in the initrd and the installed system boots fine. Didn't he say that he installed Debian and *then* converted the disk to ext4. This would explain why the ext4 module is not included - the disk wasn't ext4 when the ramdisk was generated. Can you confirm that this the case? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
