[haiku-bugs] Re: [Haiku] #11683: Boot failure: PANIC: acquire_spinlock(): failed to acquire spinlock for a long time

  • From: "anevilyak" <trac@xxxxxxxxxxxx>
  • Date: Thu, 01 Jan 2015 17:50:00 -0000

#11683: Boot failure: PANIC: acquire_spinlock(): failed to acquire spinlock for 
a
long time
-------------------------+----------------------------
   Reporter:  cdesai     |      Owner:  nobody
       Type:  bug        |     Status:  new
   Priority:  normal     |  Milestone:  Unscheduled
  Component:  - General  |    Version:  R1/Development
 Resolution:             |   Keywords:
 Blocked By:             |   Blocking:  7665
Has a Patch:  0          |   Platform:  All
-------------------------+----------------------------

Comment (by anevilyak):

 Replying to [comment:4 waddlesplash]:
 > @anevilyak: I was pretty sure, from talking to cdesai on IRC, and from
 looking at the stacktrace, that this is the kernel's fault. After all,
 it's just after the entry point (_start) no? (And there were some very
 similar bugs surrounding acquire_spinlock before, but they occurred after
 boot had finished).

 Except those are also frequently provoked by using the on-screen debug
 output option, that one can mess with timing in a number of ways and
 really shouldn't generally be used. It's really only meant for debugging
 very early boot issues. More useful would be the syslog output from a
 perfectly normal boot attempt, i.e. by attempting to boot normally, then a
 soft reset, then accessing the previous boot's in-memory syslog via the
 boot loader. Most likely this one's a device driver issue.

--
Ticket URL: <https://dev.haiku-os.org/ticket/11683#comment:5>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: