[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #5489: PANIC: vm_page_fault: unhandled page fault in
From:       "bonefish" <trac () haiku-os ! org>
Date:       2010-02-28 16:00:40
Message-ID: 050.f59d07d4cc6d4c8f0ce82578184c4ba2 () haiku-os ! org
[Download RAW message or body]

#5489: PANIC: vm_page_fault: unhandled page fault in kernel at 0x70616d6d, ip
0x800d2723
---------------------------+------------------------------------------------
 Reporter:  aldeck         |       Owner:  axeld         
     Type:  bug            |      Status:  new           
 Priority:  normal         |   Milestone:  R1            
Component:  System/Kernel  |     Version:  R1/Development
 Keywords:                 |   Blockedby:                
 Platform:  All            |    Blocking:                
---------------------------+------------------------------------------------

Comment(by bonefish):

 Regarding mutex_lock.cap: The bug in the "info" command is fixed in
 r35657. The double lock of the mutex is just a coincidence. The underlying
 problem is the page fault in object_cache_alloc(). If faults at
 0x70616000, which could also be a part of a string (or the end of one and
 start of another): "\0`ap". Grepping through our sources turned nothing up
 that would match, but it might come from somewhere else.

 I still think overwritten memory is the most likely cause. Axel's infinite
 loop problem might have the same cause, so I would first let him examine
 it, since he can easily reproduce it.

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/5489#comment:4>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.


[prev in list] [next in list] [prev in thread] [next in thread]