Opened 14 years ago

Last modified 6 years ago

#6010 closed bug

Kernel Panic after installation in VirtualBox — at Version 4

Reported by: awoe Owned by: marcusoverhagen
Priority: normal Milestone: R1
Component: Drivers/Disk Version: R1/alpha2
Keywords: scsi scsi_periph Cc:
Blocked By: Blocking:
Platform: x86

Description (last modified by bonefish)

​http://pl.tinypic.com/r/i56ct5/5 - scsi scheduler

After installation of Haiku R1/alpha2 in VirtualBox I see that console with kernel panic message.

Change History (6)

by awoe, 14 years ago

Attachment: haiku-error.png​ added

Prinscreen with error message

by awoe, 14 years ago

Attachment: HardDisks.tar.gz​ added

VirtualBox Config and Logs

comment:1 by richienyhus, 14 years ago

While in Kernel Debugging Land (KDL) can you try the command "BT" ?

comment:2 by luroh, 14 years ago

By the log, it looks like you're running a version of VirtualBox from October last year, try updating to the latest version (3.1.8 as of writing).

in reply to:  1 comment:3 by bonefish, 14 years ago

Replying to richienyhus:

While in Kernel Debugging Land (KDL) can you try the command "BT" ?

The screenshot already contains a stack trace.

comment:4 by bonefish, 14 years ago

Component: System/Kernel → Drivers/Disk
Description: modified (diff)
Keywords: scsi_periph added; scheduler kernel driver removed
Owner: changed from axeld to marcusoverhagen
Summary: Kernel-Panick after installation in VirtualBox → Kernel Panic after installation in VirtualBox

The division by zero happens ​here. Apparently scsi_periph_device_info::block_size is 0. No idea how that can happen or whether this is simply something that needs to be checked.

Note: See TracTickets for help on using tickets.