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

Bug#433501: marked as done (Oops in kcryptd)



Your message dated Wed, 5 Dec 2007 02:22:07 -0500
with message-id <200712050222.07925.chealer@gmail.com>
and subject line Fixed
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message --- Package: linux-2.6
Version: 2.6.18.dfsg.1-12etch2
Severity: critical

This is also on the kernel's bugzilla (http://bugzilla.kernel.org/show_bug.cgi?id=7388 )

It happens at random interval (1 out of 20 times), when doing a "cryptsetup luksOpen".  After that, as soon as the file (/dev/mapper/xxx) is accessed, the oops appears.  I'm able to reproduce it easily.

Here's the message from the kernel :

BUG: unable to handle kernel paging request at virtual address 0000000c
 printing eip:
c013d598
*pde = 023db001
Oops: 0000 [#1]
PREEMPT SMP
CPU:    0
EIP:    0060:[<c013d598>] Not tainted VLI
EFLAGS: 00010286 (2.6.18 #2)
EIP is at mempool_free+0x18/0x90
eax: f793975c  ebx: 00000000  ecx: dffe3e40  edx: 00000000
esi: dfd9ff2c  edi: f793975c  ebp: f793975c  esp: dfd9ff0c
ds: 007b es: 007b ss:0068
Process kcryptd/0 (pid: 906, ti=dfd9e000 task=c232f030 task.ti=dfd9e000)
Stack: dff52c40 f793975c dfd9ff2c dff52c40 c031584a c21b7c00 0000007c
00000000
       c21b7c00 c21b7c00 00000000 00000000 00000001 00000001 0000007d
00000000
       f7939768 f793976c c22bdb40 c012ca8b c048b700 c048b700 dfd9ff8c
c22bdb68
Call trace:
 [<c031584a>] kcryptd_do_work+0x4a/0x60
 [<c012ca8b>] run_workqueue+0x7b/0xf0
 [<c0315800>] kcryptd_do_work+0x0/0x60
 [<c012d2e7>] worker_thread+0x117/0x140
 [<c0116770>] default_wake_function+0x0/0x10
 [<c012d1d0>] worker_thread+0x0/0x140
 [<c012fc97>] kthread+0xf7/0x100
 [<c012fba0>] kthread+0x0/0x100
 [<c0100e25>] kernel_thread_helper+0x5/0x10
 =========================
Code: 74 26 00 89 d1 89 c2 89 c8 c9 95 8e 01 00 90 8d 74 26 00 83 ec 10
89 5c 24 04 89 d3 89 7c 24 0c 89 c7 89 74 24 08 0f
ae f0 89 f6 <8b> 42 0c 3b 42 08 7d 1a 89 d0 e8 f9 4a 28 00 89 c6 8b 43
0c 3b
EIP: [<c013d598>] mempool_free+0x18/0x90 SS:ESP 0068:dfd9ff0c



--- End Message ---
--- Begin Message ---
Version: 2.6.22-4

This was fixed in 2.6.22.2 by Milan Broz <mbroz@redhat.com>


--- End Message ---

Reply to: