#15749 closed bug (fixed)
[atheroswifi] PANIC: mutex_destroy(): the lock (0xffffffff85461828) is held by 0, not by the caller
| Reported by: | sunnysideup | Owned by: | waddlesplash |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | Drivers/Network/atheroswifi | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | #15822 | |
| Platform: | All |
Description (last modified by )
After being advised on the IRC chats to raise a ticket for my problem, here's my attempt to describe the issue in a clear and concise manner.
I had built haiku from source to get the anyboot-nightly iso file, which I'd tested on qemu-kvm.
I wanted to try this on my real machine, which, although a little old, shouldn't show any errors (I was told RAM might be an issue - It has a 2GB DDR2).
This is what happens when I boot into it.
I also tried downloading prebuilt nightlies and booting into those. Same result.
I was advised to post the logs from /system/var/log.
So I tried to get the syslog after the first boot attempt. (Prebuilt nightly) (PS. I've tried to disable ACPI and also tried to enable failsafe graphics. This just has me stuck on a blue screen)
I don't get a syslog :(
I try failsafe graphics and disabling ACPI. I still don't get a syslog.
PS. I'm using a bootable USB to boot the anyboot-iso
Attachments (5)
Change History (19)
comment:1 by , 5 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 5 years ago
| Component: | - General → Drivers/Network |
|---|
comment:3 by , 5 years ago
How long did you wait at the blue screen? I don't think the nightly isos come up quickly even on my gaming computer.
comment:5 by , 5 years ago
| Component: | Drivers/Network → Drivers/Network/atheroswifi |
|---|---|
| Owner: | changed from to |
You can blacklist atheroswifi driver in the bootloader and see if it gets any futher.
comment:6 by , 5 years ago
Update: Enabling safe mode (Enable safe mode, continue booting) gets me into Haiku! I'll upload the syslog now
by , 5 years ago
/system/var/syslog - The systemlog after boot into Haiku (safemode + failsafe graphics)
comment:7 by , 5 years ago
Seems like the driver failed to fully initialize, and in a way that it tried to deinitialize but then crashed. Try blacklisting it.
comment:8 by , 5 years ago
| Blocking: | 15822 added |
|---|
comment:9 by , 5 years ago
| Summary: | Problems booting into Haiku → [atheroswifi] PANIC: mutex_destroy(): the lock (0xffffffff85461828) is held by 0, not by the caller |
|---|
comment:12 by , 5 years ago
Sure, but it'll take some time to test because of the quarantine :(. I don't have the machine with me right now
comment:13 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Confirmed that the panic is gone by reporter of #15822.
comment:14 by , 5 years ago
| Milestone: | Unscheduled → R1/beta2 |
|---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
This looks like a combination of 2 problems happening at the same time:
Corrupted graphics - never seen this before in any other ticket.
Network driver crash, unfortunately, the name of the driver is cut off.
What you can do is to enable both fail-safe graphics driver and safe mode. If that won't help see this article https://dev.haiku-os.org/wiki/ReportingBugs#OnScreenDebugOutput
Taking another picture might also help.