Bug#601997: [Bug 538648] Re: [Intel GM45] Irregular sync flashes on 8086:2a42 (Needs i915.powersave quirk)
Alexis, On Mon, 2010-11-01 at 21:55 +, Alexis de Lattre wrote: @Russel, You will find an up-to-date summary of the situation at the very beginning of the bug report (your bug report ! :-), in the 3 first paragraphs of the bug description. I think the problem is that when Julien looked at this bug report, it wasn't clear which kernel version is the one that provides the fix so that the Debian folk can investigate whether they can issue that kernel for Squeeze. ** Description changed: [Status] Fixed in maverick Not fixed in lucid (bug still seen on 2010-09-22 with kernel 2.6.32-25) Debian Squeeze is still running the 2.6.32-5-amd64 kernel, Maverick is running 2.6.35-22. Does anyone know which changeset to which kernel series actually cures the problem? Do we even know whether this is a 2.6.32, 2.6.33, 2.6.34 or 2.6.35 issue? [Workaround] As workaround add the option i915.powersave=0 to the kernel command line in the grub config (for GRUB 2: edit /etc/default/grub and add i915.powersave=0 to GRUB_CMDLINE_LINUX, then run sudo update-grub; for GRUB 1: edit /boot/grub/menu.lst and add i915.powersave=0 to the end of the line beginning with # kopt=, then run sudo update-grub). [Alternative workaround for experts] - Compile your kernel with Andy Whitcroft's patch from http://people.canonical.com/~apw/lp538648-lucid/ (see comment #88). + Compile your kernel with Andy Whitcroft's patch from http://people.canonical.com/~apw/lp538648-lucid/ (see comment #92). I am not sure this is an option for the Debian folk, they need to run a kernel from the official series. Thanks. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@russel.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Processed: bug 602009 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=31311
Processing commands for cont...@bugs.debian.org: forwarded 602009 https://bugs.freedesktop.org/show_bug.cgi?id=31311 Bug #602009 [linux-2.6] linux-image-2.6.36-trunk-amd64: i915.powersave option is not respected in 2.6.36 Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=31311'. thanks Stopping processing here. Please contact me if you need assistance. -- 602009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12886901254183.transcr...@bugs.debian.org
Re: Xen dom0 (core) merged to upstream Linux 2.6.37 and other new features
On Tue, Nov 02, 2010 at 12:26:42AM +0800, Liang Suilong wrote: NVIDIA and ATi proprietary drivers do not support xen kernel. If a trunk or generic kernel is built in xen pv_ops support, when users switch from normal mode to booting xen kernel, X server will not boot. Though we know a user who sets up a xen server is not a Linux newbies, the result makes user uncomfortable. It looks an uneasy problem. you are on you own once you load those. Linus has released kernel-2.6.37-rc1. I read the changelog. Some Xen pvops patch has merged into upstream kernel. Waiting Debian to push 2.6.37-rc1 to experimental and test it for Xen. experimental is currently on .36 and will stay on such until later 2.6.37-rcX (probably rc5 or such). anyway the currently merged patches are bare dom0 support without any backend, see http://wiki.xensource.com/xenwiki/XenParavirtOps P.S. please do not top post. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101102103317.gg15...@vostochny.stro.at
Bug#481684: marked as done (Please enable CONFIG_LATENCYTOP so we can use the latencytop tool)
Your message dated Tue, 2 Nov 2010 20:18:30 +0800 with message-id aanlktin+e9bfwujfhrzi_-giqwugqmly2yab5xhlj...@mail.gmail.com and subject line Re: Bug#600935: [linux-2.6] Please consider to enable CONFIG_LATENCYTOP has caused the Debian Bug report #600935, regarding Please enable CONFIG_LATENCYTOP so we can use the latencytop tool 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.) -- 600935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.25-2-686 Version: 2.6.25-3 Severity: normal Hi, please consider enabling CONFIG_LATENCYTOP in the kernel, as it's needed for the 'latencytop' utility to work. latencytop itself is already in unstable. See also http://latencytop.org/. The current kernels have CONFIG_HAVE_LATENCYTOP_SUPPORT=y # CONFIG_LATENCYTOP is not set but both options are needed. I must admit I do _not_ know if there are any negative effects when enabling that setting. However, I have rebuilt my kernel (Debian 2.6.25-3 version) with CONFIG_LATENCYTOP and it _did_ make latencytop work fine for me. Thanks, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ---End Message--- ---BeginMessage--- On Tue, Oct 26, 2010 at 4:55 AM, Ben Hutchings b...@decadent.org.uk wrote: You misunderstand. We do not enable debugging options that will hurt performance for most users. This has nothing to do with providing debug information, which is provided in separate packages and has a minimal effect on the kernel image packages. Thanks, close this bug. -- Liang Guo http://bluestone.cublog.cn ---End Message---
Bug#600935: marked as done ([linux-2.6] Please consider to enable CONFIG_LATENCYTOP)
Your message dated Tue, 2 Nov 2010 20:18:30 +0800 with message-id aanlktin+e9bfwujfhrzi_-giqwugqmly2yab5xhlj...@mail.gmail.com and subject line Re: Bug#600935: [linux-2.6] Please consider to enable CONFIG_LATENCYTOP has caused the Debian Bug report #600935, regarding [linux-2.6] Please consider to enable CONFIG_LATENCYTOP 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.) -- 600935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.36~rc5-1~experimental.1 Severity: wishlist Hi, Latencytop is a excelient utility to latency problem in desktop environment, it can only work with CONFIG_LATENCYTOP enabled kernel, so I advice to consider enable CONFIG_LATENCYTOP in future linux-image. Compired with /boot/config-2.6.36-rc6-amd64, when CONFIG_LATENCYTOP is enabled, following options will be enabled too. CONFIG_KALLSYMS_ALL CONFIG_SCHEDSTATS CONFIG_FRAME_POINTER Bug 481684 was submitted to ask to enable CONFIG_LATENCY on May 18 2008, but debian provide kernel debug now, is it the time to consider to enable CONFIG_LATENCYTOP ? Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On Tue, Oct 26, 2010 at 4:55 AM, Ben Hutchings b...@decadent.org.uk wrote: You misunderstand. We do not enable debugging options that will hurt performance for most users. This has nothing to do with providing debug information, which is provided in separate packages and has a minimal effect on the kernel image packages. Thanks, close this bug. -- Liang Guo http://bluestone.cublog.cn ---End Message---
Bug#600846: The problem also exists in 2.6.32-27 version of linux-image-2.6.32-5-amd64 package.
The problem also exists in 2.6.32-27 version of linux-image-2.6.32-5-amd64 package. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd01f8a.7040...@online.de
Bug#600846: The problem also exists in 2.6.32-27 version of linux-image-2.6.32-5-amd64 package.
On Tue, Nov 02, 2010 at 03:26:18PM +0100, hu...@online.de wrote: The problem also exists in 2.6.32-27 version of linux-image-2.6.32-5-amd64 package. please name the latest good 2.6.32-XX linux-image, which didn't show the error, so that the regression can be bisected. all images should be available on snapshot.debian.org. thank you. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101102143202.gh15...@vostochny.stro.at
Bug#600846: Strange background behind login window.
I remember another item: At the time when the Suspend-To-RAM worked fine the login window always occurred in front of an empty clean black background. But now the background behind the login window has a strange colored look and seems to be a shattered and unrecognizable picture - maybe taken from an Xserver screen saver or a KDE desktop style or something like that. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd021e4.7070...@online.de
Re: item for kernel meeting -- NX emulation
hello Kees, On Fri, 29 Oct 2010, Kees Cook wrote: Thanks for adding this to the agenda! I've added details about both AppArmor and the nx-emulation bits to the wiki page. Let me know if you've got any questions. Do you know if newly split out 32bit-mmap-exec-randomization has a chance in going upstream or has already been submitted? thanks -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101102150413.ga...@stro.at
Bug#587917: linux-image-2.6.36-rc6-amd64: GoogleEarth freezes my PC
Package: linux-2.6 Version: 2.6.36~rc6-1~experimental.1 Followup-For: Bug #587917 My laptop consistently hangs when I try to run GoogleEarth 5.1.3533.1731+0.5.4-1. I see the splash screen and then that's all she wrote. This only happens with the rc6 kernel - GoogleEarth runs fine in Lenny. -- Package-specific info: ** Version: Linux version 2.6.36-rc6-amd64 (Debian 2.6.36~rc6-1~experimental.1) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.4-17) ) #1 SMP Mon Oct 4 09:56:45 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.36-rc6-amd64 root=/dev/mapper/VgCompaq-debian resume=/dev/VgCompaq/swap ro quiet splash vga=0x317 ** Not tainted ** Kernel log: [8.706374] PM: Marking nosave pages: bf5bb000 - bf5bf000 [8.706376] PM: Basic memory bitmaps created [8.720747] PM: Basic memory bitmaps freed [9.775980] EXT3-fs: barriers not enabled [9.790202] kjournald starting. Commit interval 5 seconds [9.790225] EXT3-fs (dm-4): mounted filesystem with ordered data mode [ 13.324159] udevd version 125 started [ 14.103548] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 14.138087] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 14.414134] i801_smbus :00:1f.3: PCI INT D - GSI 19 (level, low) - IRQ 19 [ 14.458146] input: PC Speaker as /devices/platform/pcspkr/input/input1 [ 14.573718] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 [ 14.573780] ACPI: Power Button [PWRB] [ 14.573843] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3 [ 14.573920] ACPI: Lid Switch [LID0] [ 14.573981] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4 [ 14.574017] ACPI: Sleep Button [SLPB] [ 14.574097] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 [ 14.574129] ACPI: Power Button [PWRF] [ 14.622287] ACPI: acpi_idle registered with cpuidle [ 14.628743] Linux video capture interface: v2.00 [ 14.663517] Monitor-Mwait will be used to enter C-1 state [ 14.702725] uvcvideo: Found UVC 1.00 device CNF7041 (04f2:b057) [ 14.702770] Monitor-Mwait will be used to enter C-2 state [ 14.706449] input: CNF7041 as /devices/pci:00/:00:1d.7/usb1/1-6/1-6:1.0/input/input6 [ 14.706508] usbcore: registered new interface driver uvcvideo [ 14.706510] USB Video Class driver (v0.1.0) [ 14.720025] Monitor-Mwait will be used to enter C-3 state [ 14.720040] Marking TSC unstable due to TSC halts in idle [ 14.748027] Switching to clocksource hpet [ 15.165089] cfg80211: Calling CRDA to update world regulatory domain [ 15.508141] ACPI: AC Adapter [AC] (on-line) [ 15.614607] ACPI: Battery Slot [BAT0] (battery present) [ 15.614867] ACPI: WMI: Mapper loaded [ 15.750544] ath5k :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 15.750561] ath5k :01:00.0: setting latency timer to 64 [ 15.750648] ath5k :01:00.0: registered as 'phy0' [ 16.522056] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input7 [ 16.607520] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input8 [ 16.958287] alloc irq_desc for 22 on node -1 [ 16.958290] alloc kstat_irqs on node -1 [ 16.958302] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 16.958401] alloc irq_desc for 41 on node -1 [ 16.958403] alloc kstat_irqs on node -1 [ 16.958417] HDA Intel :00:1b.0: irq 41 for MSI/MSI-X [ 16.958453] HDA Intel :00:1b.0: setting latency timer to 64 [ 16.997162] input: HP WMI hotkeys as /devices/virtual/input/input9 [ 17.157439] ath: EEPROM regdomain: 0x67 [ 17.157442] ath: EEPROM indicates we should expect a direct regpair map [ 17.157447] ath: Country alpha2 being used: 00 [ 17.157449] ath: Regpair used: 0x67 [ 17.263307] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input10 [ 17.265407] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input11 [ 17.265882] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input12 [ 17.266337] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input13 [ 17.505020] phy0: Selected rate control algorithm 'minstrel_ht' [ 17.505704] Registered led device: ath5k-phy0::rx [ 17.505725] Registered led device: ath5k-phy0::tx [ 17.505734] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) [ 18.742234] EXT3-fs (dm-4): using internal journal [ 19.271233] loop: module loaded [ 21.547868] fuse init (API version 7.15) [ 21.891473] EXT3-fs: barriers not enabled [ 21.901481] kjournald starting. Commit interval 5 seconds [ 21.901648] EXT3-fs (sda1): using internal journal [ 21.901653] EXT3-fs (sda1): mounted filesystem with ordered data mode [ 21.956752] EXT3-fs: barriers not enabled [ 21.973101] kjournald starting. Commit interval 5 seconds [ 21.973380] EXT3-fs (dm-3): using internal journal [ 21.973385]
Bug#600846: The problem also exists in 2.6.32-27 version of linux-image-2.6.32-5-amd64 package.
On Tue, Nov 02, 2010 at 04:29:10PM +0100, hu...@online.de wrote: As far as I remember there was no good 2.6.32-XX linux-image which didn't show the error - all of them did. If my memory serves me well the last good kernel that didn't show the error was 2.6.30-1 , and the error came up in 2.6.30-2 . (If you want I could test this kernel version again on my system - just tell me how to add a valid public key so that synaptic accepts the snapshot repository). oh well you probably mean abi number above and not version number, so the regression is really old and most probably either due to switch to libata or to KMS intel drivers. in that case it be more useful to know if newer linux-2.6 is fixed, by any chance tried anything newer from experimental? current 2.6.36 linux-image installs just fine in testing. can you reproduce it there? The problem is that I did not make any notes about this - I didn't intend to write a bug report at this time but expected the problem to vanish anyway with the update next week or so (but it didn't - for a lot of weeks now). So I am not sure about all of this - not even if the problem is caused by the kernel or by another component like Xserver or KDE - I must leave it to you linux professionals to make this decision. The only thing I am sure about is that every second or third Suspend-To-RAM hangs. I see, thanks a lot for the quick responsiveness. P.S.: please keep bug report on cc, to keep record of it, thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101102154807.gi15...@vostochny.stro.at
updated text
Maks I discussed this on IRC and drafted the following text which we believe is ready for inclusion: Debian 6.0 will be the final Debian release to include Linux kernel virtualization featuresets outside of mainline. This means that the OpenVZ and Linux-Vserver featuresets should be considered deprecated, and users should migrate to linux-2.6 upstream merged virtualization solutions like KVM, Linux Containers or Xen. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101102154313.ga24...@dannf.org
Re: item for kernel meeting -- NX emulation
On Tue, Nov 02, 2010 at 04:04:13PM +0100, maximilian attems wrote: hello Kees, On Fri, 29 Oct 2010, Kees Cook wrote: Thanks for adding this to the agenda! I've added details about both AppArmor and the nx-emulation bits to the wiki page. Let me know if you've got any questions. Do you know if newly split out 32bit-mmap-exec-randomization has a chance in going upstream or has already been submitted? I would fight it going upstream as it has terrible entropy. I feel it only has value when combined with the nx-emu patch, which would have 0 entropy for the relocated executable regions if left as-is. The goal discussed on the Fedora kernel list was to somehow get rewrites of the existing upstream ASLR so that it could be used with the nx-emu patch and then the 32bit-mmap-exec-randomization could be eliminated. The feature 32bit-mmap-exec-randomization is trying to implement is ASCII armor (leading 0 byte on addresses), but it's greedy-fit method creates a nearly deterministic layout for each given ELF. So if a way to do ASCII armor with the upstream ASLR can be created, it can be dropped. There has been no progress on this, though. -Kees -- Kees Cook@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101102154757.gj5...@outflux.net
Bug#602009: linux-image-2.6.36-trunk-amd64: i915.powersave option is not respected in 2.6.36
Hello, On Tue, Nov 2, 2010 at 1:10 AM, Fernando Lemos fernando...@gmail.com wrote: Thanks for your prompt response. Done, it's bug #31311: https://bugs.freedesktop.org/show_bug.cgi?id=31311 Chris Wilson's reply shed some light on this and I now understand what's going on. I commented up i915.powersave=0 to test if #580601 was gone in 2.6.36, and that made into the initrd, as I found out after examining it. Running update-initramfs -k all -u solved the issue. In 2.6.36, as Chris Wilson stated, /sys/modules/i915/parameters/powersave is 0400. I'm led to believe that at some point in initialization, after the root filesystem is mounted, modprobe goes over /etc/modprobe.d again to reset the options. This might be why leaving i915.powersave=0 commented out in the initrd worked before 2.6.36. If this is the case, then it might be nice to have the commit mentioned in the f.d.o bug report backported, perhaps. It could also be that my other initrds simply didn't have that option commented out. Anyways, the issue is now solved for me: ferna...@vostro:~$ sudo cat /sys/module/i915/parameters/powersave 0 ferna...@vostro:~$ uname -a Linux vostro 2.6.36-trunk-amd64 #1 SMP Wed Oct 27 14:28:29 UTC 2010 x86_64 GNU/Linux ferna...@vostro:~$ Please feel free to close/archive/invalidate this bug report. Sorry for any inconvenience and thanks for your time. Regards, -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimade9h92bp=_4ansmdhz2ljg6figa2kf5xe...@mail.gmail.com
Re: updated text
Hello Dann, I've got your message from the list and would like to ask you what this mean? We are massively using OpenVZ for our containers and this is the base of our weberver farm. The lxc Linux Containers project ( http://lxc.sourceforge.net) sounds similar as OpenVZ. Are the kernel patches based upon the work of OpenVZ from Kir Kolyshkin? My colleague and I know Kir Kolyshkin (OpenVZ) since some years and we are in contact from time to time with him. I gather that it isn't currently a problem for us because squeeze will have an OpenVZ kernel image but its good to know whats coming next because we then have to productive migrate a lot of instances. Does anyone know whats the currently status of OpenVZ integration in Debian 6.0 and later is? Whats the plan or vision? The lxc homepage and the lxc article on wiki.debian.org or are quite straight forward. We aren't developers but we could do some testing if help is needed. Mario On Tue, Nov 2, 2010 at 4:43 PM, dann frazier da...@debian.org wrote: Maks I discussed this on IRC and drafted the following text which we believe is ready for inclusion: Debian 6.0 will be the final Debian release to include Linux kernel virtualization featuresets outside of mainline. This means that the OpenVZ and Linux-Vserver featuresets should be considered deprecated, and users should migrate to linux-2.6 upstream merged virtualization solutions like KVM, Linux Containers or Xen. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101102154313.ga24...@dannf.org -- http://www.n0r1sk.com
Bug#602254: initramfs-tools: [lib]crc32c* modules handling
Package: initramfs-tools Version: 0.98.5 Severity: normal libcrc32c requires one crc32c provider (currently crc32c or crc32c-intel) to work properly. libcrc32c does not have any hard dependencies: % modinfo libcrc32c | grep depends depends: Some drivers like the bnx2x network module: % modinfo bnx2x | grep depends depends:mdio,libcrc32c ... as well as the btrfs filesystem module: % modinfo btrfs | grep libcrc depends:libcrc32c require libcrc32c and therefore depend on a crc32c provider to work properly on the other hand. I've bugreports that servers using bnx2x based NICs (like HP Proliant BL460cG6, Dell R210,...) don't work out-of-the-box because of unresolved symbols during boot - affecting both Debian and Ubuntu. I can't trigger this bug on a booted system with loading btrfs - *crc32* is loaded as intended. Instead there seems to be a race condition when multiple modprobes are asking for the same driver (like what happens with multiple similar NICs asking for bnx2x). Manually adding crc32c, libcrc32c and mdio to conf/modules is known to solve the problem. AFAICS this works because the modules in conf/modules are loaded through load_modules() *before* relying on automatisms which seem to fail. I found the following discussions with upstream: http://article.gmane.org/gmane.linux.kernel.cryptoapi/4132 http://lkml.org/lkml/2010/5/26/63 In linux-2.6.git I noticed commit 9bea7f23952d5948f8e5dfdff4de09bb9981fb5f - though the issue is known to be still present with kernel 2.6.35 and current userspace from Debian/unstable, so whether it's a bug in i-t, kernel or module-init-tools - we should investigate on that. This issue might qualify for a RC bug, though needs deeper investigation. I'm currently short of time and don't have a decent solution besides the workaround available, tough I'd like to see this issue at least documented in Debian's BTS for now and welcome any suggestions how we we could solve this problem. PS: I don't own the according hardware to trigger the bug on my own, but if we need any testing/feedback I think the bugreporters might help us out - so please ping me then. regards, -mika- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2010-10-29t12-48...@devnull.michael-prokop.at
Bug#602256: linux-image-2.6.32-5-amd64: Squeeze kernel (amd64/i386) won't boot on Lenny KVM/amd64 with vcpu 1
Package: linux-2.6 Version: 2.6.32-27 Severity: important Aftering install via beta 1 d-i on Lenny KVM/amd64 host, neither Squeeze amd64 or i386 will boot with vcpu more than 1. Booting in rescue mode shows it hanging after initializing USB. Both OSes boot correctly with vcpu = 1. Additionally, the beta 1 i386 installer will run with vcpu = 2, but the amd64 beta 1 installer will not. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-27) (m...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat Oct 30 14:18:21 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=UUID=9d0f2b04-6c07-44f4-a25b-10ccaf426bd3 ro quiet ** Not tainted ** Kernel log: [0.323138] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [0.323277] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16450 [0.323560] 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16450 [0.323649] input: Macintosh mouse button emulation as /devices/virtual/input/input0 [0.323694] PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 [0.324331] serio: i8042 KBD port at 0x60,0x64 irq 1 [0.324335] serio: i8042 AUX port at 0x60,0x64 irq 12 [0.324410] mice: PS/2 mouse device common for all mice [0.324696] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 [0.324930] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0 [0.324999] rtc0: alarms up to one day, 114 bytes nvram [0.325006] cpuidle: using governor ladder [0.325008] cpuidle: using governor menu [0.325011] No iBFT detected. [0.325306] TCP cubic registered [0.325397] NET: Registered protocol family 10 [0.326068] lo: Disabled Privacy Extensions [0.326251] Mobile IPv6 [0.326256] NET: Registered protocol family 17 [0.326335] PM: Resume from disk failed. [0.326340] registered taskstats version 1 [0.326588] rtc_cmos 00:01: setting system clock to 2010-11-02 23:09:51 UTC (1288739391) [0.326610] Initalizing network drop monitor service [0.326628] Freeing unused kernel memory: 584k freed [0.326798] Write protecting the kernel read-only data: 4232k [0.388473] udev[46]: starting version 163 [0.700181] SCSI subsystem initialized [0.724436] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [0.724467] virtio-pci :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 [0.724993] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10 [0.725010] virtio-pci :00:04.0: PCI INT A - Link[LNKD] - GSI 10 (level, high) - IRQ 10 [0.726483] usbcore: registered new interface driver usbfs [0.726592] usbcore: registered new interface driver hub [0.729847] usbcore: registered new device driver usb [0.738071] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [0.739523] uhci_hcd: USB Universal Host Controller Interface driver [0.739563] uhci_hcd :00:01.2: PCI INT D - Link[LNKD] - GSI 10 (level, high) - IRQ 10 [0.739594] uhci_hcd :00:01.2: setting latency timer to 64 [0.739606] uhci_hcd :00:01.2: UHCI Host Controller [0.739636] uhci_hcd :00:01.2: new USB bus registered, assigned bus number 1 [0.739729] uhci_hcd :00:01.2: irq 10, io base 0xc020 [0.739806] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [0.739810] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.739812] usb usb1: Product: UHCI Host Controller [0.739813] usb usb1: Manufacturer: Linux 2.6.32-5-amd64 uhci_hcd [0.739814] usb usb1: SerialNumber: :00:01.2 [0.739866] usb usb1: configuration #1 chosen from 1 choice [0.739889] hub 1-0:1.0: USB hub found [0.739896] hub 1-0:1.0: 2 ports detected [0.740750] vda: [0.741251] FDC 0 is a S82078B [0.743046] vda1 vda2 vda3 [0.750192] libata version 3.00 loaded. [0.752079] ata_piix :00:01.1: version 2.13 [0.752162] ata_piix :00:01.1: setting latency timer to 64 [0.752378] scsi0 : ata_piix [0.754440] scsi1 : ata_piix [0.754518] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14 [0.754520] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15 [0.912395] ata2.00: ATAPI: QEMU DVD-ROM, 0.9.1, max UDMA/100 [0.912805] ata2.00: configured for MWDMA2 [0.913218] scsi 1:0:0:0: CD-ROMQEMU QEMU DVD-ROM 0.9. PQ: 0 ANSI: 5 [0.922922] sr0: scsi3-mmc drive: 4x/4x xa/form2 tray [0.922928] Uniform CD-ROM driver Revision: 3.20 [0.923136] sr 1:0:0:0: Attached scsi CD-ROM sr0 [0.935845] sr 1:0:0:0: Attached scsi generic sg0 type 5 [1.000886] PM: Starting manual resume from disk [1.000888] PM: Resume from partition 254:2 [1.000889] PM: Checking hibernation image. [1.000971] PM: Error -22 checking image file [1.000972] PM: Resume from disk failed. [1.041735] EXT4-fs (vda3): mounted filesystem with ordered data mode [1.644699]
Processed: tagging 602152
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 602152 + pending Bug #602152 [linux-2.6] [INTL:ja] Japanease translation of the debconf templates linux-2.6 Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 602152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128874240620788.transcr...@bugs.debian.org
Re: updated text
On Tue, 2010-11-02 at 21:35 +0100, Mario Kleinsasser wrote: Hello Dann, I've got your message from the list and would like to ask you what this mean? We are massively using OpenVZ for our containers and this is the base of our weberver farm. The lxc Linux Containers project (http://lxc.sourceforge.net) sounds similar as OpenVZ. Are the kernel patches based upon the work of OpenVZ from Kir Kolyshkin? My colleague and I know Kir Kolyshkin (OpenVZ) since some years and we are in contact from time to time with him. I believe that many of the OpenVZ developers have also been working on Linux Containers. I gather that it isn't currently a problem for us because squeeze will have an OpenVZ kernel image but its good to know whats coming next because we then have to productive migrate a lot of instances. Does anyone know whats the currently status of OpenVZ integration in Debian 6.0 and later is? Whats the plan or vision? [...] It is still supported in Debian 6.0, and the OpenVZ developers are actively maintaining a branch based on Linux 2.6.32 which we are taking fixes from. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 602009
Processing commands for cont...@bugs.debian.org: tags 602009 - moreinfo Bug #602009 [linux-2.6] linux-image-2.6.36-trunk-amd64: i915.powersave option is not respected in 2.6.36 Ignoring request to alter tags of bug #602009 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 602009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128874512631780.transcr...@bugs.debian.org
Processed: bug 602009 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=31311
Processing commands for cont...@bugs.debian.org: forwarded 602009 https://bugs.freedesktop.org/show_bug.cgi?id=31311 Bug #602009 [linux-2.6] linux-image-2.6.36-trunk-amd64: i915.powersave option is not respected in 2.6.36 Ignoring request to change the forwarded-to-address of bug#602009 to the same value thanks Stopping processing here. Please contact me if you need assistance. -- 602009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128875052119975.transcr...@bugs.debian.org
