supercomputer7
commented
2 years ago I'll try to reproduce this on my local setup. It seems like it doesn't detect any harddrive, which is weird, but I guess it's something simple to debug :)
Open thankyouverycool opened 2 years ago
supercomputer7
commented
2 years ago I'll try to reproduce this on my local setup. It seems like it doesn't detect any harddrive, which is weird, but I guess it's something simple to debug :)
supercomputer7
commented
2 years ago I tried to run QEMU without KVM multiple times, both in i440FX and Q35 chipset modes, without any success to reproduce this.
supercomputer7
commented
2 years ago It'd be cool if you can give more details what you tried to do, and what is the QEMU version you run with.
thankyouverycool
commented
2 years ago Using qemu 5.2.0
I was able to panic 3 times out of the last 50 boots. I just realized my boot alias uses the old ninja install && ninja image && ninja run commands inside /Build/i686. Dunno if this is still acceptable since superbuild changes.
supercomputer7
commented
2 years ago I usually invoke build and running with:
sudo SERENITY_RUN=q35 SERENITY_KERNEL_CMDLINE= SERENITY_SCREENS= SERENITY_QEMU_DISPLAY_BACKEND=gtk SERENITY_RAM_SIZE=4096M ninja setup-and-runin the Build/i686 directory (I remove the q35 if needed to boot with i440fx PC chipset). It's definitely a race condition, I'm just unsure where it's actually the place of that race.
I also run with QEMU 6.0.0, so I suggest to check it to see if it helps :)
bgianfo
commented
2 years ago This is also impacting CI occasionally:
awesomekling
commented
2 years ago Dang, this happened again on CI. So not fixed by 05ed8d17385e6965fd66c42758d332bd7af741c0, reopening.
IzKuipers
commented
3 days ago Hi all, I know this issue doesn't appear to be active anymore, and I'm sorry if this is not the place to put it (though the discord invite is invalid?), but I thought I would document my findings regarding this specific issue. Over the course of today I've attempted to run Serenity OS (commit hash 1146284d86, built using the build guide on Linux Mint) on various devices, ranging from Pentium 4 to Core i5. Unfortunately, all devices panicked in the exact same way, no matter the configuration.
Tests were conducted using the GRUB image on both a 16GB USB 2.0 Silicon Power flash drive and a 32GB SanDisk USB 3.0 drive. The devices are listed in this neat table. Keep in mind that AHCI was disabled for all my tests:
| Device | CPU | CPU speed | Disk controller | Flash drive(s) |
|---|---|---|---|---|
| HP Compaq CQ2100NL | Intel Atom 230 | 1.6GHz | SATA | SanDisk & SP |
| HP Compaq 6200 Pro | Intel Core i5-2400 | 3.1GHz | SATA | SP |
| Custom build | AMD Athlon II X2-260 | 3.21GHz | SATA | SP |
| Custom build | Pentium 4 | 2.4GHz | IDE | SanDisk & SP |
| Dell Latitude E6500 | Core 2 Duo T9400 | 2.53GHz | SATA | SanDisk & SP |
| Lenovo ThinkPad T510 | Core i5-520m | 2.4GHz | SATA | SanDisk & SP |
The crash:
[init_stage2(1:1)]: ASSERTION FAILED: !m_controllers.is_empty()
[init_stage2(1:1)]: ./Kernel/Devices/Storage/StorageManagement.cpp:172 in void Kernel::StorageManagement::enumerate_storage_devices()
[init_stage2(1:1)]: KERNEL PANIC! :^(
[init_stage2(1:1)]: Aborted
[init_stage2(1:1)]: at ./Kernel/Arch/x86_64/CPU.cpp:36 in void abort()
[init_stage2(1:1)]: Kernel + 0x000000000067f97a Kernel::__panic(char const*, unsigned int, char const*) +0x9a
[init_stage2(1:1)]: Kernel + 0x0000000000ed9226 abort +0x22e
[init_stage2(1:1)]: Kernel + 0x0000000000ed8ff8 abort +0x0
[init_stage2(1:1)]: Kernel + 0x000000000112e58f Kernel::StorageManagement::enumerate_storage_devices() +0xbef
[init_stage2(1:1)]: Kernel + 0x0000000001131682 Kernel::StorageManagement::initialize(bool) +0x32
[init_stage2(1:1)]: Kernel + 0x0000000000003ef4 Kernel::init_stage2(void*) +0x1554I have no clue if any of this is useful to anyone, but what the hell.
spholz
commented
3 days ago Hi! Our custom discord invite doesn't appear to work anymore, so here is an old invite link which seems to still work: https://discord.com/invite/29gCcKsXkF. This issue is probably not the right place for this (this issue also probably can be closed).
Keep in mind that AHCI was disabled for all my tests
We don't support IDE anymore since 2cb86c13097c89194af51b185d1f7d3ee8be4882. AHCI and NVMe should work though. Also note that while we do support UHCI and USB mass storage devices (xHCI support isn't merged yet), nobody ever tested the mass storage driver on bare metal I think. So you probably would need to manually write the disk image from another OS onto one of your drives.
Run into this periodically booting i686 in ubuntu qemu without kvm