Launchpad has imported 30 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=516909.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2009-08-11T20:52:01+00:00 Warren wrote: 1) Upgrade to grubby-7.0.2-1.fc12.x86_64 2) Install grubby-7.0.2-1.fc12.x86_64 title Fedora (2.6.31-0.145.rc5.git3.fc12.x86_64) root (hd0,0) kernel /vmlinuz-2.6.31-0.145.rc5.git3.fc12.x86_64 ro root=/dev/mapper/vg0-rootfs rhgb quiet usbcore.autosuspend=1 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us rd_plytheme=charge initrd /initrd-generic-2.6.31-0.145.rc5.git3.fc12.x86_64.img This stanza was written by new-kernel-pkg. Note that it is booting the initrd-generic shipped within the kernel RPM. 3) Attempt boot. My LVM vg is encrypted, with rootfs on a lv within that vg. I type my passphrase, it successfully unlocks it, but then sits there forever. key slot 0 unlocked. Command successful. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/0 ------------------------------------------------------------------------ On 2009-08-11T21:13:50+00:00 Warren wrote: oops, step #2 is install kernel-2.6.31-0.145.rc5.git3.fc12.x86_64 This is with dracut-0.8-1.fc12.noarch. I tried to create a new initrd image with dracut, but that image exhibits the same problem as initrd- generic. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/1 ------------------------------------------------------------------------ On 2009-08-11T22:07:15+00:00 Warren wrote: dracut on kernel-2.6.31-0.125.rc5.git2.fc12.x86_64 works. This seems to be a problem with kernel-2.6.31-0.145.rc5.git3.fc12.x86_64. Reassigning. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/2 ------------------------------------------------------------------------ On 2009-08-11T23:31:41+00:00 Warren wrote: kernel-2.6.31-0.145.2.1.rc5.git3.fc12.x86_64 is broken in the same manner. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/3 ------------------------------------------------------------------------ On 2009-08-12T10:58:46+00:00 Sven wrote: Same here. The last kernel that is working for me is kernel-2.6.31-0.139.rc5.git3.fc12.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/4 ------------------------------------------------------------------------ On 2009-08-12T16:42:59+00:00 Warren wrote: kernel-2.6.31-0.149.rc5.git3.fc12.x86_64 mkinitrd FAIL kernel-2.6.31-0.149.rc5.git3.fc12.x86_64 dracut FAIL Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/5 ------------------------------------------------------------------------ On 2009-08-12T22:31:46+00:00 Warren wrote: I built a LiveCD with kernel-2.6.31-0.149.rc5.git3.fc12.x86_6 + dracut. It gets stuck forever without any error messages and just fails to boot. It seems this has nothing to do with encrypted root. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/6 ------------------------------------------------------------------------ On 2009-08-12T22:58:06+00:00 Warren wrote: GOOD kernel-2.6.31-0.139.rc5.git3.fc12.x86_64 mkinitrd GOOD kernel-2.6.31-0.139.rc5.git3.fc12.x86_64 dracut FAIL kernel-2.6.31-0.142.rc5.git3.fc12.x86_64 mkinitrd FAIL kernel-2.6.31-0.142.rc5.git3.fc12.x86_64 dracut Confirmed, it broke somewhere between 139 and 142. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/7 ------------------------------------------------------------------------ On 2009-08-12T23:21:20+00:00 Dennis wrote: kernel-2.6.31-0.149.rc5.git3.fc12.sparc64 works just fine here. im using unencrypted lvm dracut-0.7-4.fc12 was used in the kernel build Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/8 ------------------------------------------------------------------------ On 2009-08-13T19:39:17+00:00 Warren wrote: I'm confused. The very same livecd of Comment #6 works today, but the kernel installed on my laptop silently gets stuck after unlocking the encrypted disk. Sven, are you using encryption? enrypted LVM vg specifically? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/9 ------------------------------------------------------------------------ On 2009-08-13T21:00:37+00:00 Warren wrote: http://people.redhat.com/wtogami/temp/post139loop.jpg SysRQ-p after it gets stuck. It appears to be stuck in a loop. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/10 ------------------------------------------------------------------------ On 2009-08-14T07:16:35+00:00 Sven wrote: I am using encryption. I can reproduce those hangs on two machines - both using full vg encryption. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/11 ------------------------------------------------------------------------ On 2009-08-15T20:44:33+00:00 Sven wrote: If I'm not mistaken F12Alpha is going to ship with a kernel >139 and that would mean full disk encrytion is broken for alpha. As this is a rather important feature I think blocking on F12Alpha is warranted. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/12 ------------------------------------------------------------------------ On 2009-08-15T20:45:51+00:00 Sven wrote: This seems to be the "non-boot-side" of the same bug: https://bugzilla.redhat.com/show_bug.cgi?id=517545 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/13 ------------------------------------------------------------------------ On 2009-08-15T21:10:03+00:00 Tom wrote: Yeah, believe I can reproduce a similar issue by plugging in a USB hard drive with a Luks encrypted file system: https://bugzilla.redhat.com/show_bug.cgi?id=517545 As reported there, works for 0.139, fails for later kernels up to and including kernel-2.6.31-0.156.rc6.fc12.x86_64. All these kernels boot fine on my unencrypted LVM, but exhibit "cryptsetup won't die and consumes available cpu cycles". I've posted SysRQ-p traces there.... Same issue? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/14 ------------------------------------------------------------------------ On 2009-08-15T23:40:32+00:00 Milan wrote: It works with Linus' kernel, patches which introduced problem in Fedora: Kernel Samepage Merging (KSM). linux-2.6-ksm.patch linux-2.6-ksm-updates.patch Quite serious bug, probably all encrypted system are not bootable now. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/15 ------------------------------------------------------------------------ On 2009-08-15T23:42:08+00:00 Milan wrote: *** Bug 517545 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/16 ------------------------------------------------------------------------ On 2009-08-16T11:17:59+00:00 Sven wrote: Both my rawhide machines are back to working state with kernel -157 (which disables the ksm-patches). Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/17 ------------------------------------------------------------------------ On 2009-08-16T13:19:36+00:00 Milan wrote: >From the included KSM series, probmlematic is this patch Subject: [PATCH 9/12] ksm: fix oom deadlock (fixes one deadlock...and introduces another one:-) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/18 ------------------------------------------------------------------------ On 2009-08-16T16:22:22+00:00 Tom wrote: -157 fixes my "plugging in a USB hard drive with encrypted FS" issue. FS now mounts and cryptsetup has properly exited. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/19 ------------------------------------------------------------------------ On 2009-08-17T15:11:29+00:00 Mark wrote: The F12 Alpha kernel is kernel-2.6.31-0.125.4.2.rc5.git2.fc12, so removing this from the alpha blocker Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/20 ------------------------------------------------------------------------ On 2009-08-18T10:36:00+00:00 Mark wrote: Summary: - '[PATCH 9/12] ksm: fix oom deadlock' appears to cause deadlock with an encrypted root volume - This was added in 2.6.31-0.141.rc5.git3 by the addition of this set of KSM patches: http://cvs.fedoraproject.org/viewvc/rpms/kernel/devel/linux-2.6-ksm- updates.patch?revision=1.1 - the KSM patches have since been disabled since 2.6.31-0.157.rc6 pending a fix for this Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/21 ------------------------------------------------------------------------ On 2009-08-18T10:44:49+00:00 Milan wrote: > - '[PATCH 9/12] ksm: fix oom deadlock' appears to cause deadlock with an > encrypted root volume FYI: no need to have encrypted root volume, any "cryptsetup luksOpen" on x86_64 will cause deadlock, for process backtrace see bug 517545. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/22 ------------------------------------------------------------------------ On 2009-08-18T16:03:17+00:00 Mark wrote: Andrea suggests checking whether these programs are calling madvise() with bogus flags Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/23 ------------------------------------------------------------------------ On 2009-08-18T16:44:27+00:00 Milan wrote: (In reply to comment #23) > Andrea suggests checking whether these programs are calling madvise() with > bogus flags Not explicitly, but probably forgot to unlock memory - try this code: #include <sys/mman.h> int main (int argc, char *argv[]) { mlockall(MCL_CURRENT | MCL_FUTURE); // munlockall(); return 0; } Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/24 ------------------------------------------------------------------------ On 2009-08-25T15:02:29+00:00 Andrea wrote: Investingating why those troublesome checks that deadlocks mlocked programs are added to page fault path... at first glance they look unnecessary, so asking just in case... Date: Tue, 25 Aug 2009 16:58:32 +0200 From: Andrea Arcangeli <[email protected]> To: Hugh Dickins <[email protected]> Cc: Izik Eidus <[email protected]>, Rik van Riel <[email protected]>, Chris Wright <[email protected]>, Nick Piggin <[email protected]>, Andrew Morton <[email protected]>, [email protected], [email protected] Subject: Re: [PATCH 9/12] ksm: fix oom deadlock On Mon, Aug 03, 2009 at 01:18:16PM +0100, Hugh Dickins wrote: > tables which have been freed for reuse; and even do_anonymous_page > and __do_fault need to check they're not being called by break_ksm > to reinstate a pte after zap_pte_range has zapped that page table. This deadlocks exit_mmap in an infinite loop when there's some region locked. mlock calls gup and pretends to page fault successfully if there's a vma existing on the region, but it doesn't page fault anymore because of the mm_count being 0 already, so follow_page fails and gup retries the page fault forever. And generally I don't like to add those checks to page fault fast path. Given we check mm_users == 0 (ksm_test_exit) after taking mmap_sem in unmerge_and_remove_all_rmap_items, why do we actually need to care that a page fault happens? We hold mmap_sem so we're guaranteed to see mm_users == 0 and we won't ever break COW on that mm with mm_users == 0 so I think those troublesome checks from page fault can be simply removed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/25 ------------------------------------------------------------------------ On 2009-08-25T15:27:22+00:00 Andrea wrote: Created attachment 358588 attempted fix (last one was wrong diff) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/26 ------------------------------------------------------------------------ On 2009-08-25T19:52:15+00:00 Andrea wrote: Created attachment 358624 new proposed patch this is actually making ksm_exit simpler and it already contains down_write(mmap_sem) (also this time I checked which workstation I'm running firefox on, before picking a random file from /tmp ;) discussion is going live on linux-mm with Hugh Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/31 ------------------------------------------------------------------------ On 2009-08-27T09:34:22+00:00 Andrea wrote: Hugh acked my attachment 358624 so please apply it and then we can close this bug. We've still some issue to discuss on oom handling with ksm on linux-mm but those aren't crtical issues and once we solve them, patches will flow in rawhide. thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/35 ------------------------------------------------------------------------ On 2009-08-27T13:24:48+00:00 Justin wrote: Already applied and should be in kernel-2.6.31-0.180.rc7.git4.fc12 today. KSM has been re-enabled. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418781/comments/36 ** Changed in: linux Importance: Unknown => High ** Bug watch added: Red Hat Bugzilla #517545 https://bugzilla.redhat.com/show_bug.cgi?id=517545 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/418781 Title: Karmic 2.6.31-7.27 KSM patchset breaks encrypted swap Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Karmic: Fix Released Bug description: Installed the latest Ubuntu kernel today, 2.6.31-7.27, but I can't boot into it, because it's missing padlock-sha.ko, which is required for encrypted swap. :-Dustin ProblemType: Bug Architecture: amd64 ArecordDevices: **** List of CAPTURE Hardware Devices **** card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: kirkland 4035 F.... pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 17' Mixer name : 'Conexant CX20561 (Hermosa)' Components : 'HDA:14f15051,17aa20ff,00100000' Controls : 15 Simple ctrls : 8 Date: Tue Aug 25 13:29:45 2009 DistroRelease: Ubuntu 9.10 MachineType: LENOVO 7454CTO Package: linux-image-2.6.31-6-generic 2.6.31-6.26 PccardctlIdent: PccardctlStatus: ProcCmdLine: root=UUID=d45ce184-de1d-48ac-a143-44ab4432a207 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-6.26-generic RelatedPackageVersions: linux-backports-modules-2.6.31-6-generic N/A linux-firmware 1.16 SourcePackage: linux Uname: Linux 2.6.31-6-generic x86_64 WpaSupplicantLog: dmi.bios.date: 04/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET44WW (2.08 ) dmi.board.name: 7454CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6DET44WW(2.08):bd04/22/2009:svnLENOVO:pn7454CTO:pvrThinkPadX200:rvnLENOVO:rn7454CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7454CTO dmi.product.version: ThinkPad X200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/418781/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
