#14913 closed bug (fixed)
Haiku-64 crash after update (hrev52902)
Reported by: | tatoomi | Owned by: | waddlesplash |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | - General | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86-64 |
Description
After update (hrev52902) and reboot , haiku crash after rocket. Console return :
PANIC : attemting to block thread 555 wich is pinned.
Thread 555 'lauch demon' running on cpu1 stack trace for thread 555 'lauch demon'
Is it related to that (source activity)?
kernel/x86: Pin the current thread before calling interrupt handlers.
I just noted the beginning of the console message, if you need more, tell me.
Change History (6)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Enter the boot options by holding SHIFT while booting (or hitting the spacebar, if that shouldn't work for you). There you can select an older state to boot. See the last bullet at the User Guide's troubleshooting section.
I see the same thing, BTW.
comment:3 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Problematic commits reverted in hrev52903. You can safely upgrade using the steps humdinger notes, indeed.
comment:4 by , 6 years ago
Thank you all
After booting in safe mode , i need to restart network for update system. Can you give me the right command ? One more time , thanks
comment:5 by , 6 years ago
You don't need safe mode, just an earlier state. That won't disable the network.
comment:6 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
can you tell me how to fix the problem without reinstalling everything. Thank you