Opened 12 months ago
Closed 12 months ago
#18701 closed bug (fixed)
Regression, Boot failure with ACPI enabled
Reported by: | bbjimmy | Owned by: | korli |
---|---|---|---|
Priority: | high | Milestone: | R1/beta5 |
Component: | Drivers/ACPI | Version: | R1/beta4 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Attachments (2)
Change History (11)
by , 12 months ago
Attachment: | Bitmap.png added |
---|
comment:1 by , 12 months ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
by , 12 months ago
Attachment: | DSC_0078.JPG added |
---|
comment:2 by , 12 months ago
Milestone: | Unscheduled → R1/beta5 |
---|
comment:3 by , 12 months ago
comment:4 by , 12 months ago
Sorry, I cannot help at the moment. Might always revert the relevant here.
comment:5 by , 12 months ago
If the only intended changes of https://git.haiku-os.org/haiku/commit/?id=f2acc47f4363f14c20f645e48aac98f48259de26 were the volatile whatever and the loop exit condition, the return from AcpiOsAcquireGlobalLock should also test ACPI_GLOCK_OWNED to be like the previous version; that is, something like: return (newValue & (ACPI_GLOCK_PENDING | ACPI_GLOCK_OWNED)) != 0;
comment:6 by , 12 months ago
Ah, I see the mistake now in comparison with FreeBSD's methods: https://xref.landonf.org/source/xref/freebsd-current/sys/dev/acpica/Osd/OsdSynch.c#607
comment:9 by , 12 months ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Same problem on my machine. Attached a picture of the on-screen debug, in case it provides some hints.