Opened 18 months ago

Last modified 8 months ago

#18444 new bug

PANIC: acquire_spinlock(): Failed to acquire spinlock ... for a long time (in the vein of #17865)

Reported by: WildKeccak Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: x86-64

Description

I know that I'm being sparse here. There are people I don't want to disturb at this late hour. My system is like a smaller version of his:

hrev 57078

AMD Ryzen 5 3400G (instead of 5700G) 8GB Ram (instead of 16GB) A Ryzen 5700 XT (instead of 6700 XT, although it may be a 6700 XT) Same Motherboard, I believe

I can deliver lsusb and lspci tomorrow. Serial logs, if necessary, can take a little longer.

Attachments (2)

IMG_0213.png (1.5 MB ) - added by WildKeccak 18 months ago.
A picture of the crash
syslog - with CSM (61.8 KB ) - added by WildKeccak 18 months ago.
syslog with CSM enabled? Obtained by letting it crash, and then booting off of a live Haiku to retrieve the file

Download all attachments as: .zip

Change History (17)

by WildKeccak, 18 months ago

Attachment: IMG_0213.png added

A picture of the crash

comment:1 by pulkomandy, 18 months ago

A look at the syslog would be interesting (mostly the end of it) since it's the syslog_sender that crashed. You can access it by typing the "syslog" command in KDL.

Anything special you're doing to make this happen?

comment:2 by pulkomandy, 18 months ago

Component: - GeneralSystem/Kernel
Version: R1/Development

comment:3 by WildKeccak, 18 months ago

I am starting my machine off of USB. I am booting using UEFI. Legacy boot (CSM) is enabled, if I remember correctly.

by WildKeccak, 18 months ago

Attachment: syslog - with CSM added

syslog with CSM enabled? Obtained by letting it crash, and then booting off of a live Haiku to retrieve the file

comment:4 by WildKeccak, 17 months ago

I'm not able to reproduce this. In fact, I'm using the nightly image right now. However, booting takes just shy of three minutes. Most of which is spent looking at a progress bar that doesn't change.

comment:5 by WildKeccak, 17 months ago

Boots quickly on Beta 4

comment:6 by WildKeccak, 17 months ago

R1/beta4 (Revision hrev56578+59) works. Haven't succeeded in getting hrev56578 or any other recent nightly to work as far as I know. That's what I meant in comment 5.

comment:7 by pulkomandy, 17 months ago

Milestone: UnscheduledR1/beta5

Moving to beta5 milestone since it's a regression, then?

Your comments are a bit unclear, do I undertand correctly the current situation:

  • beta 4 works fine
  • nightlies work but you have to wait 3 minutes to boot
  • the initial problem with the spinlock is not reproducible anymore?

comment:8 by WildKeccak, 15 months ago

beta 4 works fine

nightlies don't reliably work and if they do, it takes 3 minutes.

Last edited 15 months ago by WildKeccak (previous) (diff)

comment:9 by WildKeccak, 15 months ago

This was supposed to be the CSM enabled version of the bug, but things got worse

These statements are not true.

Now, no icons light.

I have no EFI shell that I'm aware of to see how similar this bug is to #18557

comment:10 by WildKeccak, 15 months ago

The HDMI port I use / adapter I use matters. The integrated HDMI is what I'm using right now.

comment:11 by WildKeccak, 13 months ago

I am not currently experiencing this problem.

comment:12 by WildKeccak, 13 months ago

The integrated HDMI works, the Radeon, not so much.

comment:13 by waddlesplash, 10 months ago

I am not currently experiencing this problem.

So, is there anything left to do here?

comment:14 by waddlesplash, 10 months ago

Milestone: R1/beta5Unscheduled

Bumping out of milestone.

comment:15 by WildKeccak, 8 months ago

I imagine the primary problem is that I have a "custom" gaming rig, to speak charitably of the beast. The secondary problem is that it is generally unstable, especially with regard to the Radeon 5700XT. The bug report is wrongly specific. I'll take a look at it again, but I spoke wrongly when I said it worked.

Note: See TracTickets for help on using tickets.