[haiku-bugs] Re: [Haiku] #5206: NMI Interrupt introduced between r34760 and r34915

#5206: NMI Interrupt introduced between r34760 and r34915
---------------------------+------------------------------------------------
 Reporter:  adamk          |       Owner:  bonefish      
     Type:  bug            |      Status:  assigned      
 Priority:  high           |   Milestone:  R1            
Component:  System/Kernel  |     Version:  R1/Development
 Keywords:                 |   Blockedby:                
 Platform:  x86            |    Blocking:                
---------------------------+------------------------------------------------
Changes (by anevilyak):

  * owner:  nobody => bonefish
  * status:  new => assigned
  * version:  R1/alpha1 => R1/Development
  * component:  - General => System/Kernel


Old description:

> This afternoon I updated my local svn repo to r34915 and installed an
> updated build to a spare partition I use for testing.
>
> Upon booting up, I'm greeted with a KDL: 'PANIC: Fatal exception "NMI
> Interrupt" occurred! Error code: 0x0" .  I've noticed other reports on
> here, and someone on #haiku mentioned the same problem, but it seems that
> others are able to 'cont' and the boot up proceeds as normal.
> Unfortunately, continuing is not an option for me as I end up with a
> vm_page_fault.
>
> I can still boot up my r34760 installation on another partition on the
> same drive.
>
> I have a logging via a serial cable, and grabbed a backtrace which I am
> attaching to this ticket.
>
> While it is certainly possible for me to start reverting to previous
> commits, this will undoubtedly take a while, so I'm hoping someone can
> read something in my backtrace that indicates the source of the problem
> and figure out which commit broke Haiku for me :-)

New description:

 This afternoon I updated my local svn repo to r34915 and installed an
 updated build to a spare partition I use for testing.

 Upon booting up, I'm greeted with a KDL: 'PANIC: Fatal exception "NMI
 Interrupt" occurred! Error code: 0x0" .  I've noticed other reports on
 here, and someone on #haiku mentioned the same problem, but it seems that
 others are able to 'cont' and the boot up proceeds as normal.
 Unfortunately, continuing is not an option for me as I end up with a
 vm_page_fault.

 I can still boot up my r34760 installation on another partition on the
 same drive.

 I have a logging via a serial cable, and grabbed a backtrace which I am
 attaching to this ticket.

 While it is certainly possible for me to start reverting to previous
 commits, this will undoubtedly take a while, so I'm hoping someone can
 read something in my backtrace that indicates the source of the problem
 and figure out which commit broke Haiku for me :-)

--

Comment:

 From the backtrace, looks possibly related to some of Ingo's recent area
 management changes...if that backtrace is consistent, the output of "call
 15 -3" after the NMI itself would be interesting (i.e. without trying to
 continue).

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

Other related posts: