Bug#360478: linux-image-2.6.16-1-k7: mount encrypted ide crash
tags 360478 moreinfo
On Sun, 02 Apr 2006, franck wrote:
> Since 2.6.16 I experience some crashes when mounting an encrypted ide
> partition. Crashes does not always happen but let's say 50% time. If it
> shall crash it always happen just when mounting the partition.
> Effects are : X or console freeze. Under console, SysRq Sync +
> remount may allow to recover the console after some 'sleeping time'
> (however no 'DONE' appearing). Later '/sbin/reboot' sometimes hangs and
> SysRq reboot is the only way.
can we have an update on that based on current testing and linux image
> In case the console comes back one can save from dmesg:
> BUG: soft lockup detected on CPU#0!
> Pid: 4199, comm: mount
> EIP: 0060:[<b0130097>] CPU: 0
> EIP is at find_get_pages+0x41/0x45
> EFLAGS: 00000246 Not tainted (2.6.16-1-k7 #1)
> EAX: 80000821 EBX: eb11fc80 ECX: eb11fc8c EDX: b17625e0
> ESI: 00000001 EDI: 00000001 EBP: 00000001 DS: 007b ES: 007b
> CR0: 8005003b CR2: af8d95e4 CR3: 3b954000 CR4: 000006d0
> [<b01357a4>] pagevec_lookup+0x1a/0x21
> [<b013613e>] invalidate_mapping_pages+0x92/0xa7
> [<b0136160>] invalidate_inode_pages+0xd/0x11
> [<b014c707>] kill_bdev+0xb/0x22
> [<b014cdfb>] set_blocksize+0x6f/0x7b
> [<b014ce1d>] sb_set_blocksize+0x16/0x3c
> [<f08d1089>] ext3_fill_super+0x3bd/0x1368 [ext3]
> [<b01a3a36>] snprintf+0x1a/0x1e
> [<b014c495>] get_sb_bdev+0xc5/0x10f
> [<f08cf49f>] ext3_get_sb+0x1a/0x1e [ext3]
> [<f08d0ccc>] ext3_fill_super+0x0/0x1368 [ext3]
> [<b014bca2>] do_kern_mount+0x88/0x12d
> [<b015d428>] do_mount+0x629/0x684
> [<b0152be8>] link_path_walk+0xb0/0xbb
> [<b013a193>] __handle_mm_fault+0x348/0x650
> [<b0152fb3>] do_path_lookup+0x17f/0x19a
> [<b0133b8f>] get_page_from_freelist+0x7e/0x294
> [<b0133df3>] __alloc_pages+0x4e/0x261
> [<b01341c2>] __get_free_pages+0x2f/0x34
> [<b015c27e>] copy_mount_options+0x28/0x10e
> [<b015d4f5>] sys_mount+0x72/0xad
> [<b01028ff>] sysenter_past_esp+0x54/0x75
> SysRq : Emergency Sync
> SysRq : Emergency Remount R/O
> I never experienced such problem with 2.6.15. I booted with 2.6.12 and did
> not see the same problem -> seems to come from 2.6.16.
> I tried to reproduce it on an encrypted USB stick (to avoid any risk of
> hdd corruption resulting from trials), but I couldn't -> seems linked to
> I can reproduce it on several different hdd.
> FYI encryption comes from: dpkg -l cryptsetup dmsetup
> ii cryptsetup 1.0.2+1.0.3-rc3-1 configures encrypted block devices
> ii dmsetup 1.02.03-1 The Linux Kernel Device Mapper userspace library
> Kind regards,
> Franck R.
happy new year