spurious kernel oops on luksOpen

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi (please CC: me in replies),

time and again I'm getting a kernel oops when luksOpen'ing
my crypt containers. The system is still usable afterwards,
only the cryptsetup and any other process accessing the
crpyt devices later on gets locked in the kernel.

This is my oops message:

] BUG: unable to handle kernel paging request at virtual address 01600013
]  printing eip:
] c01428a3
] *pde = 00000000
] Oops: 0000 [#1]
] PREEMPT 
] Modules linked in: xt_NFQUEUE xt_tcpudp xt_state xt_limit xt_CONNMARK xt_connmark ipt_ROUTE xt_multiport ipt_REDIRECT ipt_MASQUERADE ipt_LOG nfnetlink_queue nfnetlink iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack ipv6 iptable_filter ip_tables x_tables ntfs sha256 aes_i586 cbc dm_crypt dm_mod nvidia(P) agpgart snd_virmidi snd_seq_virmidi snd_ca0106 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm ac97_bus snd_page_alloc snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore usb_storage sd_mod scsi_mod nls_utf8 nls_cp850 nls_iso8859_1 hisax_fcpcipnp hisax_isac hisax via686a w83781d hwmon_vid hwmon i2c_isa i2c_viapro i2c_core msr isdn_bsdcomp isdn cpuid rtc
] CPU:    0
] EIP:    0060:[<c01428a3>]    Tainted: P      VLI
] EFLAGS: 00010286   (2.6.20-rc6 #3)
] EIP is at mempool_free+0x13/0xb0
] eax: caaf0614   ebx: caaf0614   ecx: dff8c480   edx: 01600013
] esi: 01600013   edi: caaf0614   ebp: dff0bec8   esp: dff0beb8
] ds: 007b   es: 007b   ss: 0068
] Process kcryptd/0 (pid: 829, ti=dff0a000 task=dff49070 task.ti=dff0a000)
] Stack: 00000200 caaf0614 d97e3180 c1734da0 dff0bed8 e0934776 dff0bf20 d97e3180 
]        dff0bf4c e0934bfb c16fec60 0000007c 00000000 00000000 c16fec60 caaf0614 
]        c16fece0 c011fa63 00000046 0000000b dff49220 dff0bf24 c0101e80 c038d550 
] Call Trace:
]  [<c0103f2a>] show_trace_log_lvl+0x1a/0x30
]  [<c0103fe9>] show_stack_log_lvl+0xa9/0xd0
]  [<c01041c9>] show_registers+0x1b9/0x2f0
]  [<c010440e>] die+0x10e/0x230
]  [<c0115950>] do_page_fault+0x2b0/0x5d0
]  [<c030aa34>] error_code+0x74/0x7c
]  [<e0934776>] dec_pending+0x46/0x60 [dm_crypt]
]  [<e0934bfb>] kcryptd_do_work+0x2fb/0x3b0 [dm_crypt]
]  [<c012ad34>] run_workqueue+0xa4/0x180
]  [<c012b437>] worker_thread+0x137/0x160
]  [<c012e2c3>] kthread+0xa3/0xd0
]  [<c0103b5b>] kernel_thread_helper+0x7/0x1c
]  =======================
] Code: f4 60 1c 00 8d 74 26 00 eb d3 31 db e9 37 ff ff ff 8d b4 26 00 00 00 00 55 89 e5 83 ec 10 89 75 f8 89 7d fc 89 d6 89 5d f4 89 c7 <8b> 02 39 42 04 7d 27 9c 5b fa 89 e0 25 00 e0 ff ff ff 40 14 8b 
] EIP: [<c01428a3>] mempool_free+0x13/0xb0 SS:ESP 0068:dff0beb8

Observations:
* I keep getting those segfaults since about 2.6.12, I don't remember
  exactly when they began.
* They tend to occur more often if I mount the crypt devices after the
  system has accumulated some uptime - mounting them directly at boot
  time has never triggered the bug so far.
* dec_pending() seems to request a page being faulted in that doesn't
  exist or is invalid... but I'm unable to gather more.

What can I do to futher debug this?


Regards,

Jan

---------------------------------------------------------------------
dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx


[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux