Hi, I am using FC5 with the latest kernel. FC5 comes with cryptsetup-luks 1.0.3rc2. My /home dir is in a separate partition, which I successfully encrypted. I am using a script I found at the wiki to open the encrypted device at boot. After entering the correct passowrd, however, I receive the following: Apr 22 00:22:21 WillamNB kernel: Pid: 1917, comm: mount Apr 22 00:22:21 WillamNB kernel: EIP: 0060:[<c013c5b3>] CPU: 0 Apr 22 00:22:21 WillamNB kernel: EIP is at find_get_pages+0x4c/0x53 Apr 22 00:22:21 WillamNB kernel: EFLAGS: 00000246 Tainted: P ( 2.6.16-1.2096_FC5 #1) Apr 22 00:22:21 WillamNB kernel: EAX: dcd68aa0 EBX: 00000001 ECX: 00000001 EDX: c11e5ce0 Apr 22 00:22:21 WillamNB kernel: ESI: 0000000e EDI: 004f2094 EBP: dcd68aa0 DS: 007b ES: 007b Apr 22 00:22:21 WillamNB kernel: CR0: 8005003b CR2: 00971510 CR3: 0f29c000 CR4: 000006d0 Apr 22 00:22:21 WillamNB kernel: [<c0140509>] pagevec_lookup+0x17/0x1d [<c0140850>] invalidate_mapping_pages+0x98/0xab Apr 22 00:22:21 WillamNB kernel: [<c0159a8f>] kill_bdev+0xd/0x20 [<c0159b0d>] set_blocksize+0x6b/0x77 Apr 22 00:22:21 WillamNB kernel: [<c0159b2a>] sb_set_blocksize+0x11/0x35 [<de895d30>] ext3_fill_super+0x3a5/0x12e6 [ext3] Apr 22 00:22:21 WillamNB kernel: [<c012d115>] __mutex_init+0x2d/0x3c [<c016a1a8>] get_filesystem+0xf/0x23 Apr 22 00:22:21 WillamNB kernel: [<c0158da5>] sget+0x457/0x463 [<c01584fc>] set_bdev_super+0x0/0xe Apr 22 00:22:21 WillamNB kernel: [<c015850a>] test_bdev_super+0x0/0xd [<c01c4b39>] snprintf+0x1c/0x1f Apr 22 00:22:21 WillamNB kernel: [<c0184b27>] disk_name+0x1f/0x60 [<c015925e>] get_sb_bdev+0xd5/0x11d Apr 22 00:22:21 WillamNB kernel: [<c016a521>] alloc_vfsmnt+0x97/0xbe [<de8943ba>] ext3_get_sb+0xe/0x11 [ext3] Apr 22 00:22:21 WillamNB kernel: [<de89598b>] ext3_fill_super+0x0/0x12e6 [ext3] [<c015905d>] do_kern_mount+0x86/0x12b Apr 22 00:22:21 WillamNB kernel: [<c016b946>] do_mount+0x6a5/0x6fd [<c013feaf>] pagevec_lookup_tag+0x1b/0x22 Apr 22 00:22:21 WillamNB kernel: [<c01c1672>] _atomic_dec_and_lock+0x22/0x2c [<c016ab62>] mntput_no_expire+0x11/0x6d Apr 22 00:22:21 WillamNB kernel: [<c0160a12>] link_path_walk+0xaf/0xb9 [<c0144e2a>] __handle_mm_fault+0x79b/0x7c3 Apr 22 00:22:21 WillamNB kernel: [<c013e2a8>] get_page_from_freelist+0x6f/0x2db [<c02de292>] do_page_fault+0x189/0x51d Apr 22 00:22:21 WillamNB kernel: [<c016a775>] copy_mount_options+0x26/0x109 [<c016ba02>] sys_mount+0x64/0x97 Apr 22 00:22:21 WillamNB kernel: [<c0102be9>] syscall_call+0x7/0xb <6>kjournald starting. Commit interval 5 seconds After a short while the boot process continues and I am allowed to login. The encrypted device appears to be working fine. Can anyone explain to what's causing the behavior I descibed above and what I need to do to get rid of it? Also tried using the latest version, but getting the same result. TIA, Gabor Walter Hungary
