I posted about this in 2.1.38, in which case it locks the system rock solid
for approximately 5 minutes, at which point I get the segfault and
everything contiunues normally. I can confirm that it still happens in
2.1.41, and in addition, a very interesting property: the lock is VERY
hard, ie my clock is now 10 minutes slow (I just did it twice...) I have no
idea if this is normal or not, but I thought it was interesting.
here is my output...
May 29 19:22:31 eliot213 kernel: general protection: 0000
May 29 19:22:31 eliot213 kernel: CPU: 0
May 29 19:22:31 eliot213 kernel: EIP: 0010:[<c01095f6>]
May 29 19:22:31 eliot213 kernel: EFLAGS: 00010282
May 29 19:22:31 eliot213 kernel: eax: 00000000 ebx: 0805ba78 ecx:
0805baa8 edx: 00000000
May 29 19:22:31 eliot213 kernel: esi: 0805baa8 edi: bffffd3a ebp:
bffffc28 esp: c0329fec
May 29 19:22:31 eliot213 kernel: ds: 002b es: 002b ss: 0018
May 29 19:22:31 eliot213 kernel: Process vmlinux (pid: 429, process nr: 41,
stackpage=c0329000)
May 29 19:22:31 eliot213 kernel: Stack: c0100000 00000023 00000282 bffffbb4
0000002b
May 29 19:22:31 eliot213 kernel: Call Trace: [<c0100000>]
May 29 19:22:31 eliot213 kernel: Code: cf 89 f6 8d bc 27 00 00 00 00 f7 44
24 30 00 00 02 00 54 75
>>EIP: c01095f6 <ret_with_reschedule+25/2f>
Trace: c0100000 <startup_32>
===
Evan Jeffrey
erjeffre@artsci.wustl.edu
Let us go. Let us leave this festering hell hole. Let us think the
unthinkable, let us do the undoable. Let us prepare to grapple with the
ineffable itself, and see if we may not eff it after all.
--Dirk Gently