[haiku-bugs] Re: [Haiku] #6324: Haiku boot image fails on HP Vectra pentium 3 computer

  • From: "bonefish" <trac@xxxxxxxxxxxx>
  • Date: Wed, 21 Jul 2010 15:04:03 -0000

#6324: Haiku boot image fails on HP Vectra pentium 3 computer
---------------------------------+------------------------------------------
  Reporter:  Karvjorm            |         Owner:  axeld    
      Type:  bug                 |        Status:  new      
  Priority:  normal              |     Milestone:  R1       
 Component:  Servers/app_server  |       Version:  R1/alpha2
Resolution:                      |      Keywords:           
Blocked By:                      |   Has a Patch:  0        
  Platform:  All                 |      Blocking:           
---------------------------------+------------------------------------------
Changes (by bonefish):

  * keywords:  Boot image 512 MB RAM =>
  * component:  System/Boot Loader => Servers/app_server


Comment:

 Apparently the app server crashes:
 {{{
 1267    vm_soft_fault: va 0x8db000 not covered by area in address space
 1268    vm_page_fault: vm_soft_fault returned error 'Bad address' on fault
 at 0x8dbd1c, ip 0x8dbd1c, write 0, user 1, thread 0x34
 1269    vm_page_fault: thread "app_server" (52) in team "app_server" (52)
 tried to read address 0x8dbd1c, ip 0x8dbd1c ("???" +0x8dbd1c)
 1270    debug_server: Thread 52 entered the debugger: Segment violation
 1272    stack trace, current PC 0x8dbd1c  :
 1273      (0x7ffeedbc)  0x2779a5  Shutdown__6Screen + 0x31
 1274      (0x7ffeedec)  0x2778d5  _._6Screen + 0x29
 1276      (0x7ffeee1c)  0x2793a8
 _AddHWInterface__13ScreenManagerP11HWInterface + 0x130
 1277      (0x7ffeee5c)  0x279233  _ScanDrivers__13ScreenManager + 0x63
 1278      (0x7ffeee8c)  0x278c57  __13ScreenManager + 0x5f
 1279      (0x7ffeeefc)  0x24ad65  __9AppServer + 0x1c5
 1280      (0x7ffeef4c)  0x24b639  main + 0x65
 1281      (0x7ffeef7c)  0x24a0bf  _start + 0x5b
 1282      (0x7ffeefac)  0x105d62  runtime_loader + 0x14a
 }}}
 Since the fault address is at the instruction pointer, that's likely when
 calling a virtual method or some function via function pointer. My guess
 would be the latter, in `AccelerantHWInterface::Shutdown()` (the function
 would be missing in the stack trace in such a situation).

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

Other related posts: