Opened 5 years ago

Closed 2 years ago

#14804 closed bug (invalid)

PANIC: could not allocate block!

Reported by: mvfranz Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: - General Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

I am running haiku-r1beta1-x86_gcc2_hybrid-anyboot in VMWare 15 on Windows 10. After leaving the process running over night Haiku crashed with 'PANIC: could not allocate block!' and dropped in to the kernel debugger.

The stack trace indicates that it was in the 'screensaver controller'

The installation will no-longer start.

Attachments (1)

HaikuOS-VMWare15KernelCrash.PNG​ (63.6 KB ) - added by mvfranz 5 years ago.
Screen grab of the stack trace

Download all attachments as: .zip

Change History (3)

by mvfranz, 5 years ago

Attachment: HaikuOS-VMWare15KernelCrash.PNG​ added

Screen grab of the stack trace

comment:1 by waddlesplash, 5 years ago

Keywords: screensaver removed

"The installation will no-longer start" indicates that this is disk corruption, most likely. Please get a syslog from the failed boot, if you can.

comment:2 by waddlesplash, 2 years ago

Resolution: → invalid
Status: new → closed

No reply in 3 years.

Note: See TracTickets for help on using tickets.