Bug#688711: [3.4.4 - 3.5 regression] fails to find root device (Unable to find LVM volume data/root)

# 3.6-rc7 tags 688711 + fixed-upstream quit Jonathan Nieder wrote: Jonathan Nieder wrote: [ 1.949115] sda: sda1 sda2 sda3 sda5 [ 1.949751] sd 0:0:0:0: [sda] Attached SCSI disk Volume group data not found [...] Bisects to

Processed: Re: [3.4.4 - 3.5 regression] fails to find root device (Unable to find LVM volume data/root)

Processing commands for cont...@bugs.debian.org: # 3.6-rc7 tags 688711 + fixed-upstream Bug #688711 [src:linux] [3.4.4 - 3.5 regression] fails to find root device (Unable to find LVM volume data/root) Added tag(s) fixed-upstream. quit Stopping processing here. Please contact me if you need

Bug#688846: initramfs-tools: Upgrade Squeeze-Wheezy: crypto-LVM unaccessible

Package: initramfs-tools Version: 0.107 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, I upgrades my notebook from Squeeze to Wheezy (Stable - Testing). The laptop has an encrypted filesystem (encrypted LVM). The boot process failed because the kernel

Bug#678636: dm-crypt partitions not further working: possible workaround

Sorry for creating bug report #688846 without noticing #678636 is already there. Sounds to me that both addresses the same problem. Maybe merge them? I also found some kind of workaround that at least seems to work for me. Thanks, Sebastian -- To UNSUBSCRIBE, email to

Bug#503310: Any news ?

Hi, Is there any news on this old bug? Best 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/1348653324-0b04fff8f16de3410f97c62d6b41b...@quake.fr

Bug#619711: console-setup: breaks copying keymap to initramfs

On Fri, Sep 21, 2012 at 12:54:12PM +0200, Michael Prokop wrote: Anton, while working on this issue I noticed that setupcon doesn't always return an according error code. Example: http://michael-prokop.at/screeni/gkrellShoot_12-09-21_112226.png Could you please take care of that? Yes,

Bug#688880: linux: Please enable CONFIG_TCM_QLA2XXX=m

Source: linux Severity: wishlist Tags: patch Dear Maintainer, Please enable the CONFIG_TCM_QLA2XXX=m option for 3.5-trunk. This option enables the new target mode for qla2xxx HBAs (see http://www.linux-iscsi.org/wiki/Fibre_Channel). --- linux-3.5.2/debian/config/config2012-08-01

Bug#688882: linux-image-2.6.32-5-xen-amd64: Dom0 crashes when starting third DomU

Package: linux-2.6 Version: 2.6.32-45 Severity: important Whenever I start a third domU, my dom0 immediately crashes and reboots. Because it is in colo, I cannot pull a capture of why it's happening. If there is a way to do this without going onsite, I am willing to do that. All of the

Bug#688883: linux-image-2.6.32-5-xen-amd64: Dom0 crashes when starting third DomU

Package: linux-2.6 Version: 2.6.32-45 Severity: important Whenever I start a third domU, my dom0 immediately crashes and reboots. Because it is in colo, I cannot pull a capture of why it's happening. If there is a way to do this without going onsite, I am willing to do that. All of the

Bug#688884: linux-image-2.6.32-5-xen-amd64: Dom0 crashes when starting third DomU

Package: linux-2.6 Version: 2.6.32-45 Severity: important Whenever I start a third domU, my dom0 immediately crashes and reboots. Because it is in colo, I cannot pull a capture of why it's happening. If there is a way to do this without going onsite, I am willing to do that. All of the DomU's

Bug#687442: linux-image-3.2.0-3-686-pae: Add Intel Ivy Bridge support

Am Sonntag, 16. September 2012 schrieben Sie: The current Debian kernel 3.2.0 doesn't support the new Intel processors with built-in GPU. Sure it does. Certainly the driver has an entry for your GPU's device ID: INTEL_VGA_DEVICE(0x0162, intel_ivybridge_d_info), /* GT2 desktop */

Bug#688882: [squeeze] Dom0 crashes when starting third DomU

merge 62 63 64 quit Hi, Alan Laudicina wrote: Whenever I start a third domU, my dom0 immediately crashes and reboots. Looks like reportbug misfired and submitted this a couple of times too many. Merging. If you get a chance to also try with a 3.2.y kernel (from wheezy or

Processed: Re: [squeeze] Dom0 crashes when starting third DomU

Processing commands for cont...@bugs.debian.org: merge 62 63 64 Bug #62 [linux-2.6] linux-image-2.6.32-5-xen-amd64: Dom0 crashes when starting third DomU Bug #63 [linux-2.6] linux-image-2.6.32-5-xen-amd64: Dom0 crashes when starting third DomU Bug #64 [linux-2.6]

Bug#678636: dm-crypt partitions not further working: possible workaround

Am 26.09.2012 11:02, schrieb Sebastian Niehaus: Sorry for creating bug report #688846 without noticing #678636 is already there. Sounds to me that both addresses the same problem. I'm unsure. After an dist-upgrade (?) from squeeze to whezze the related package cryptsetup should been upgraded,

Re: trying to use virtio with the wheezy installer on arm versatile oops

Torben Hohn torb...@linutronix.de writes: Hi... Hi, i tried to use virtio inside qemu-system-arm emulating versatile. getting this kernel oops: [ 341.274760] pgd = cd818000 x [ 341.274940] [44000412]

Bug#688920: [linux-source] CONFIG_RT2500USB description confusing about target

Package: linux-source Version: 3.5.2-1~experimental.1 Severity: minor Tags: patch upstream Forwarded: https://bugzilla.kernel.org/show_bug.cgi?id=10440 The description of CONFIG_RT2500USB contains This adds support for rt2500 wireless chipset family. RT2500 specifically refers to

Processing of linux_3.2.30-1_multi.changes

linux_3.2.30-1_multi.changes uploaded successfully to localhost along with the files: linux_3.2.30-1.dsc linux_3.2.30.orig.tar.xz linux_3.2.30-1.debian.tar.xz linux-doc-3.2_3.2.30-1_all.deb linux-manual-3.2_3.2.30-1_all.deb linux-source-3.2_3.2.30-1_all.deb