lkml.org 
[lkml]   [1999]   [Jun]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.2.9-ac2 locks solid
On Mon, 7 Jun 1999, Alan Cox wrote:

>> It survived up to filling all of swap this time. When it came time for the
>> kernel to kill things, it printed a few oopses though. Not sure if IKD or
>> the real kernel made them:
>
>Those look like real oopses, but they aren't from the signal stuff, ok thats
>one bug nailed. Now someone can dig into the memory full bug you found

The oopses from out of memory (replicated below) seems to have be caused by
IKD. I had CONFIG_DEBUG_SOFTLOCKUP, CONFIG_NMI_WATCHDOG, and
CONFIG_SEMAPHORE_DEADLOCK set at the time. (2.2.7 + ikd from Andrea) In my
non-kernel-trained eye, it appears to just be due to being out of memory
taking too long:

+Semapahore deadlock detector
+CONFIG_SEMAPHORE_DEADLOCK
+ With this option enabled the first down() that will block for more than
+ 20 sec will generate an Oops that will allow you to know the code path
+ that deadlocked.

So if one process is stuck for 20 sec due to the system being otherwise
detained trying to kill something, these would result.

Unable to handle kernel NULL pointer dereference at virtual address 00000000
current->tss.cr3 = 0708c000, %cr3 = 0708c000
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c0117552>]
EFLAGS: 00010246
eax: 00002694 ebx: c00807f8 ecx: 00000000 edx: c00807e0
esi: c1964000 edi: c1965f68 ebp: c1965f84 esp: c1965f58
ds: 0018 es: 0018 ss: 0018
Process gimp (pid: 112, process nr: 63, stackpage=c1965000)
Stack: bf7ffc98 c1964000 c1965f68 c1965f70 c1964000 c00807fc 00000000 00000000
00007e7c c00807f8 c011746c c1965fb4 c0194258 c00807f8 00000000 00000000
c0114b78 c1964000 bf7ffec0 bf7ffc98 c1965fc4 c00807f8 080e3c74 bf7ffbdc
Call Trace: [<c011746c>] [<c0194258>] [<c0114b78>] [<c0108b8d>]
Code: c7 05 00 00 00 00 00 00 00 00 8b 75 d8 c7 06 02 00 00 00 31

>>EIP: c0117552 <__down+be/16c>
Trace: c011746c <generate_oops+0/28>
Trace: c0194258 <__down_failed+8/10>
Trace: c0114b78 <do_page_fault+60/334>
Trace: c0108b8d <error_code+2d/40>
Code: c0117552 <__down+be/16c> 00000000 <_EIP>: <===
Code: c0117552 <__down+be/16c> 0: c7 05 00 00 00 movl $0x0,0x0 <===
Code: c0117557 <__down+c3/16c> 5: 00 00 00 00 00
Code: c011755c <__down+c8/16c> a: 8b 75 d8 movl 0xffffffd8(%ebp),%esi
Code: c011755f <__down+cb/16c> d: c7 06 02 00 00 movl $0x2,(%esi)
Code: c0117564 <__down+d0/16c> 12: 00
Code: c0117565 <__down+d1/16c> 13: 31 00 xorl %eax,(%eax)

In other words, not an issue I hope.

-George Greer


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:52    [W:0.962 / U:1.568 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site