Opened 4 years ago

Last modified 3 weeks ago

#11683 assigned bug

Boot failure: PANIC: acquire_spinlock(): failed to acquire spinlock for a long time

Reported by: cdesai Owned by: nobody
Priority: normal Milestone: R1/beta2
Component: Drivers/Graphics/intel_extreme Version: R1/Development
Keywords: boot-failure Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description (last modified by diver)

I 'dd'ed the image from haiku-nightly-hrev48579-x86_gcc2_hybrid-anyboot.zip to a flash drive

Had to select Graphics mode VGA from the bootloader as any other option didn't work with my monitor (1600x900@60)

This is after I enabled the 'show debug text on display' option, it crashed right after and dropped me in a KDL prompt, where I typed 'co' to get this.

Hardware: i7-2600 (onboard graphics, HD 3000), 12G RAM, Dell 1600x900 monitor.

stacktrace

Attachments (2)

IMG_20141231_181233.jpg (170.9 KB) - added by cdesai 4 years ago.
stacktrace
lspci (1.4 KB) - added by cdesai 4 years ago.
lspci output from Linux

Download all attachments as: .zip

Change History (17)

Changed 4 years ago by cdesai

Attachment: IMG_20141231_181233.jpg added

stacktrace

comment:1 Changed 4 years ago by waddlesplash

Blocking: 7665 added
Component: - GeneralSystem/Kernel
Milestone: R1R1/beta1
Owner: changed from nobody to axeld
Summary: Haiku won't bootBoot failure: PANIC: acquire_spinlock(): failed to acquire spinlock for a long time

comment:2 Changed 4 years ago by anevilyak

Component: System/Kernel- General
Milestone: R1/beta1Unscheduled
Owner: changed from axeld to nobody

waddlesplash: for the thousandth time, stop recategorizing tickets if you don't actually know where they belong to. There isn't enough information here to implicate any component whatsoever.

@cdesai: a list of hardware (I.e. lspci output from Linux) would be helpful.

Last edited 4 years ago by anevilyak (previous) (diff)

comment:3 Changed 4 years ago by cdesai

comment:4 Changed 4 years ago by waddlesplash

@cdesai: please attach that as a text file to the ticket

@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).

Last edited 4 years ago by waddlesplash (previous) (diff)

Changed 4 years ago by cdesai

Attachment: lspci added

lspci output from Linux

comment:5 in reply to:  4 Changed 4 years ago by anevilyak

Replying to 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.

comment:6 Changed 4 years ago by cdesai

Okay so I was able to get it booting finally, but the resolution wasn't right.

Some more details: Still the same image/hrev/hardware. Booting directly via the flash drive results in a black screen after the Haiku loading screen finishes because it picks and invalid resolution and the monitor doesn't like that. I then tried a bunch of options from the bootloader menu, some of which resulted in the above.

It only allows me to select 4:3 resolutions.

So then I started from square one again, and was able to get it to boot by selecting the 'VGA Mode' in the failsafe video option, enabling it and booting into safe mode.

I did check the syslog from a working build and the video BIOS did report the correct values, unfortunately I didn't have any FAT partition devices around so I couldn't save the full log, I'll get it next time from a non-working boot via the way you suggested.

comment:7 Changed 4 years ago by diver

Description: modified (diff)
Milestone: UnscheduledR1

comment:8 Changed 4 years ago by diver

Component: - GeneralDrivers/Graphics/intel_extreme
Owner: changed from nobody to axeld

comment:9 Changed 4 years ago by pulkomandy

Now this bugreport is confusing, I can't understand what your problems are. Is the following correct?

  • First boot without any special settings: results in black screen
  • Black screen is caused by wrong video mode choice (have you checked this, which mode is chosen?)
  • Checking "use failsafe video mode" gets system to work (no need to force a video mode?)
  • Forcing a 4:3 video mode + "use failsafe video mode" works?
  • Once booted this way, setting a video mode in preferences > screen and rebooting normally (with the intel driver), does that work?
  • After having set a video mode this way and rebooting, can you go to screen preferences again and set the native resolution? Does it work then?
  • Does the panic happen only in 'show debug on screen' mode?

It would be better to have two separate issues for video mode setting, and the crash. Maybe there are existing tickets for those, so check that first.

comment:10 Changed 4 years ago by cdesai

  • First boot without any special settings: results in black screen

Yes.

  • Black screen is caused by wrong video mode choice (have you checked this, which mode is chosen?)

I couldn't find the mode from a quick look in the bootloader, and couldn't save it as I didn't have a FAT partition / another drive at that time, sory.

  • Checking "use failsafe video mode" gets system to work (no need to force a video mode?)

I had to force Standard VG

  • Forcing a 4:3 video mode + "use failsafe video mode" works?

I tried a few and they didn't work.

  • Once booted this way, setting a video mode in preferences > screen and rebooting normally (with the intel driver), does that work?

There were no 16:9 options there.

  • After having set a video mode this way and rebooting, can you go to screen preferences again and set the native resolution? Does it work then?

Like above, no 16:9 options.

  • Does the panic happen only in 'show debug on screen' mode?

Yes.

I have had a hardware configuration, got a new graphics card (AMD R9 270), and that worked well - same build, booted off live usb, it picked 1600x900@60 and worked just fine. Unfortunately, this also means I won't be able to test the older configuration now.

comment:11 Changed 2 years ago by axeld

Owner: changed from axeld to nobody
Status: newassigned

comment:12 Changed 10 months ago by waddlesplash

Keywords: boot-failure added

comment:13 Changed 10 months ago by waddlesplash

Blocking: 7665 removed

comment:14 Changed 6 months ago by pulkomandy

Milestone: R1R1/beta2

comment:15 Changed 3 weeks ago by waddlesplash

Please retest after hrev53040.

Note: See TracTickets for help on using tickets.