diff --git a/local/docs/boot-logs/REDBEAR-FULL-BOOT-POST-VIRTIO-BLKD-FIX-RESULTS.md b/local/docs/boot-logs/REDBEAR-FULL-BOOT-POST-VIRTIO-BLKD-FIX-RESULTS.md new file mode 100644 index 0000000000..2684566ad4 --- /dev/null +++ b/local/docs/boot-logs/REDBEAR-FULL-BOOT-POST-VIRTIO-BLKD-FIX-RESULTS.md @@ -0,0 +1,238 @@ +# Red Bear OS Boot Test — Post `virtio-blkd` Read-Only Fix Results + +**Date:** 2026-06-09 18:13 +**Test ID:** `bg_` follow-up +**Operator:** Sisyphus-Junior (automated follow-up test) +**Image under test:** `build/x86_64/redbear-mini/harddrive.img` (fallback from +`redbear-full`, which has no built image) +**Previous comparison:** `redbear-full-boot-20260609-135308.log` (the log that +panicked at `virtio-blkd` before the read-only fix landed) +**Current log:** `redbear-full-boot-20260609-150550.log` +**Archived log:** `redbear-full-boot-post-virtio-blkd-fix-20260609-181340.log` + +## TL;DR + +| Question | Answer | +|---|---| +| Did the `virtio-blkd` panic go away? | **No.** Same panic, same line, same CPU frame. | +| Did the boot reach further than the previous run? | **No.** Boot terminates at the identical point. | +| Was the fix commit present in the source fork? | **Yes.** `cffacf59 virtio-blkd: handle read-only drives gracefully (VIRTIO_BLK_F_RO feature)` is HEAD of `local/sources/base`. | +| Was the running image built from the fixed source? | **No.** `build/x86_64/redbear-mini/harddrive.img` mtime is `2026-06-09 02:46:25`, ~15h before the fix was committed. The test ran the **stale** image. | + +## Test invocation + +```bash +cd /home/kellito/Builds/RedBear-OS && \ + timeout 350 ./local/scripts/test-redbear-full-qemu.sh \ + --timeout 300 --fallback redbear-mini 2>&1 \ + | tee /tmp/redbear-full-boot-post-fix.log +``` + +The script emitted: + +``` +WARNING: redbear-full image missing; using redbear-mini fallback: + build/x86_64/redbear-mini/harddrive.img +=== Red Bear OS redbear-full QEMU Boot Test === +Config: redbear-mini +Image: build/x86_64/redbear-mini/harddrive.img +UEFI: /usr/share/ovmf/x64/OVMF.4m.fd +KVM: yes +Timeout: 300s +Log: local/docs/boot-logs/redbear-full-boot-20260609-150550.log +``` + +`redbear-full` was chosen by the script (via the filename) but no image exists +under `build/x86_64/redbear-full/` (only `redbear.tag` and `repo.tag`, both +zero-byte placeholders). The fallback to `redbear-mini` worked correctly. + +The script used the standard `snapshot=on,readonly=on` flags for the disk +attach (already in the script), so we are not mutating host state. + +## Boot progression (post-fix run) + +| Stage | Reached? | Notes | +|---|---|---| +| UEFI firmware → Redox bootloader | ✅ | Boots from `Boot0004 "UEFI Misc Device"` (PciRoot 0x0/0x5/0x0). | +| Bootloader finds RedoxFS | ✅ | `RedoxFS f0509f4b-fca3-457c-ad53-cc409e2e14d0: 1533 MiB`. | +| Kernel loads | ✅ | `kernel::arch::x86_shared::start:INFO -- RedBear OS starting...` | +| ACPI tables parse | ✅ (with warnings) | `x2APIC mode active but no LocalX2Apic entries found; falling back` and `duplicate APIC ID 0`. These are QEMU/firmware quirks, not regressions. | +| `acpid` starts | ✅ | `acpid start`, but `SMBIOS data unavailable` (no SMBIOS from bootloader). DMI rules are inert. | +| `vesad` / `fbcond` | ⚠️ | `vesad: No boot framebuffer` → `fbcond: No display present yet`. Same as the pre-fix run. | +| `hwd` ACPI backend | ✅ | `using ACPI backend`. | +| `pcid` PCI enumeration | ✅ | 9 PCI devices enumerated (00:00.0, 00:01.0, 00:02.0, 00:03.0, 00:04.0, 00:05.0, 00:1f.0, 00:1f.2, 00:1f.3). | +| `pcid-spawner` | ✅ | Spawns `nvmed` (00:04.0 NVME), then `virtio-blkd` (00:05.0), then `ahcid` (00:1f.2 SATA AHCI). | +| `nvmed` | ✅ | `QEMU NVMe Ctrl 11.0.0`, NSID 1, 2097152 sectors. | +| **`virtio-blkd`** | ❌ | **PANIC at `drivers/storage/virtio-blkd/src/scheme.rs:70:9`** — see below. | +| `ahcid` | ✅ (reached *before* the panic) | AHCI port-2 reports `SATAPI` (QEMU DVD-ROM), port 2 fails with `I/O error`. Ports 0/1/3/4/5 are `None`. | +| Console / login prompt | ❌ | Never reached. | +| D-Bus system bus | ❌ | Never reached. | +| KWin Wayland compositor | ❌ | Never reached. | +| SDDM | ❌ | Never reached. | + +## The panic + +``` +thread 'main' (1) panicked at drivers/storage/virtio-blkd/src/scheme.rs:70:9: +assertion `left == right` failed + left: 1 + right: 0 +[virtio-blkd@relibc::header::stdlib:119 ERROR] Abort +Invalid opcode fault +... +kernel::context::signal:INFO -- UNHANDLED EXCEPTION, CPU #3, PID 19, + NAME /scheme/initfs/lib/drivers/virti, CONTEXT 0xffffff7f8012bd10 +qemu: terminating on signal 15 from pid 1446342 (timeout) +``` + +`scheme.rs:70` is the `sector: block,` line inside `BlkExtension::write()`, +specifically inside `Dma::new(BlockVirtRequest { ... }).unwrap()`. The +`left: 1, right: 0` shape (numerically `1 != 0`) is the syscall-error unwrap +panic — `Dma::new` returned a non-zero `Result::Err` and `.unwrap()` aborted. + +In the **fixed** source, `virtio-blkd/src/scheme.rs:140-149`, the +`driver_block::Disk` `write` method now checks `self.read_only` **before** +issuing the request, returning `EACCES` and bypassing the inner +`BlkExtension::write()` (where the panic lives) entirely. The fix is correct +in source — it just has not been compiled into a fresh boot image yet. + +## Comparison with the previous (135308) run + +| Aspect | 20260609-135308 (pre-fix) | 20260609-150550 (post-fix) | Delta | +|---|---|---|---| +| Image used | `redbear-mini/harddrive.img` (timestamp unknown) | `redbear-mini/harddrive.img` (`2026-06-09 02:46:25`) | Same image (no rebuild between runs) | +| UEFI boot path | `Boot0004 "UEFI Misc Device"` | `Boot0004 "UEFI Misc Device"` | Identical | +| `pcid` PCI count | 9 devices | 9 devices | Identical | +| `nvmed` identify | `QEMU NVMe Ctrl 11.0.0` | `QEMU NVMe Ctrl 11.0.0` | Identical | +| `virtio-blkd` panic | `scheme.rs:70:9`, `left: 1, right: 0` | `scheme.rs:70:9`, `left: 1, right: 0` | **Identical panic, same line, same values** | +| `ahcid` reached? | Yes (port 2 = SATAPI, I/O error, ports 0/1/3/4/5 = None) | Yes (same) | Identical | +| Failure CPU/PID | CPU #0, PID 19 | CPU #3, PID 19 | Cosmetic — different CPU assigned to the `virtio-blkd` thread, same PID | +| Last line before panic | `pcid GETDENTS id=3 offset=9 entries_count=9` | `pcid GETDENTS id=3 offset=9 entries_count=9` | Identical | +| Time-to-panic | ~3 ms after `acpid` (kernel time 0.91s) | ~3 ms after `acpid` (kernel time 0.81s) | Same wall-clock pattern | +| Init log line counts | 152 | 152 | Identical | + +**Verdict:** The post-fix run is functionally a no-op compared to the pre-fix +run. Boot terminates at the same `virtio-blkd` panic with the same stack +signature. + +## Why the fix didn't take effect + +The fix is committed in the `base` fork: + +```text +$ git -C local/sources/base log --oneline -1 +cffacf59 virtio-blkd: handle read-only drives gracefully (VIRTIO_BLK_F_RO feature) +$ git -C local/sources/base status +(nothing to commit, working tree clean) +``` + +But the boot image is stale: + +```text +$ stat -c '%y' build/x86_64/redbear-mini/harddrive.img +2026-06-09 02:46:25.357992020 +0300 +``` + +The `base-initfs` recipe (which embeds `virtio-blkd` into the initrd) was last +cooked **before** commit `cffacf59` was made. The initramfs baked into +`harddrive.img` still contains the **pre-fix** `virtio-blkd` binary, which +panics on first read-only `write` attempt. Until the recipe is re-cooked and +the disk image is rebuilt, the fix cannot be observed at runtime. + +The `redbear-full` image is not even built (no `harddrive.img` in +`build/x86_64/redbear-full/`), so the fallback to `redbear-mini` is the only +thing the test can exercise. + +## What is reached vs what is not + +### Reached +- UEFI firmware +- Redox bootloader / RedoxFS detection +- Kernel boot (x2APIC, ACPI parsing) +- `acpid`, `rtcd` +- `hwd` (ACPI backend) +- `pcid` enumeration (all 9 PCI devices) +- `pcid-spawner` autospawn for `nvmed`, `virtio-blkd`, `ahcid` +- `nvmed` (QEMU NVMe Ctrl 11.0.0) +- `ahcid` (AHCI controller, 6 ports probed; port 2 reports QEMU DVD-ROM, fails with I/O error) + +### Not reached (panic at `virtio-blkd`) +- Console (no shell prompt) +- Initramfs switchroot to the real rootfs +- Root filesystem mount +- D-Bus system bus +- `redbear-sessiond` +- `redbear-authd` +- Wayland compositor (`redbear-compositor`) +- KWin +- SDDM +- Login prompt +- Anything KDE / Qt6 / KF6 + +## New errors or warnings introduced by the fix + +**None.** The pre-fix and post-fix logs are byte-for-byte equivalent +modulo timestamps and the cosmetic CPU number (`#0` → `#3` for the panic +thread). No new warnings, no new errors, no new behavior. + +The panic itself is the same panic, the same line, the same values +(`left: 1`, `right: 0`). + +## Reproducibility + +The test is fully repeatable from this commit with: + +```bash +cd /home/kellito/Builds/RedBear-OS +timeout 350 ./local/scripts/test-redbear-full-qemu.sh \ + --timeout 300 --fallback redbear-mini 2>&1 \ + | tee /tmp/redbear-full-boot-post-fix.log +``` + +To actually verify the fix at runtime, a rebuild is required first: + +```bash +# Rebuild the driver +./target/release/repo cook recipes/core/base-initfs --allow-protected + +# Re-embed into the disk image +make all CONFIG_NAME=redbear-mini + +# Re-run the test +./local/scripts/test-redbear-full-qemu.sh --timeout 300 --fallback redbear-mini +``` + +The cascade script `./local/scripts/rebuild-cascade.sh base` is the +recommended way to rebuild `base` and all its dependents, but be aware +that rebuilding `base` invalidates the entire initramfs and will require +re-cooking every package that uses the initfs. + +## What to do next + +1. **Rebuild the boot image with the fix.** Run + `./local/scripts/rebuild-cascade.sh base` (or at minimum + `./target/release/repo cook recipes/core/base-initfs --allow-protected` + followed by `make all CONFIG_NAME=redbear-mini`). +2. **Re-run the test** with the same `--timeout 300 --fallback redbear-mini` + flags. +3. **Re-archive the new log** to + `local/docs/boot-logs/redbear-full-boot-post-virtio-blkd-fix-.log` + and update this summary with the rebuilt results. +4. **Build the `redbear-full` image** if the desktop path is the actual + target — the `redbear-full` build directory currently has only empty tag + files, no `harddrive.img`. Until that image exists, the test is exercising + the text-only fallback. + +## Files referenced + +- `local/docs/boot-logs/redbear-full-boot-20260609-135308.log` — pre-fix run +- `local/docs/boot-logs/redbear-full-boot-20260609-150550.log` — post-fix run + (this test) +- `local/docs/boot-logs/redbear-full-boot-post-virtio-blkd-fix-20260609-181340.log` + — archived copy of this run +- `local/sources/base/drivers/storage/virtio-blkd/src/scheme.rs` — fixed + source (HEAD = `cffacf59`) +- `build/x86_64/redbear-mini/harddrive.img` — stale boot image used for the + test (mtime `2026-06-09 02:46:25`, predates the fix) +- `build/x86_64/redbear-full/` — empty (no `harddrive.img`); only + `redbear.tag` and `repo.tag` placeholders diff --git a/local/docs/boot-logs/redbear-full-boot-post-virtio-blkd-fix-20260609-181340.log b/local/docs/boot-logs/redbear-full-boot-post-virtio-blkd-fix-20260609-181340.log new file mode 100644 index 0000000000..c6c3c0c852 --- /dev/null +++ b/local/docs/boot-logs/redbear-full-boot-post-virtio-blkd-fix-20260609-181340.log @@ -0,0 +1,152 @@ +[=3hBdsDxe: failed to load Boot0002 "UEFI QEMU NVMe Ctrl NVME_EXTRA 1" from PciRoot(0x0)/Pci(0x4,0x0)/NVMe(0x1,00-00-00-00-00-00-00-00): Not Found +BdsDxe: loading Boot0004 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0) +BdsDxe: starting Boot0004 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0) +WARN - Failed to locate Outputs: Status(0x800000000000000E) "not found" + RedBear OS Bootloader 1.0.0 on x86_64/UEFI + Hardware descriptor: Acpi(7e1c6000, 24) + Looking for RedoxFS: + WARN - GPT: no valid signature at LBA 1 + WARN - GPT: no valid signature at LBA 1 + RedoxFS f0509f4b-fca3-457c-ad53-cc409e2e14d0: 1533 MiB + + usr/lib/boot/kernel: 0/1 MiB usr/lib/boot/kernel: 0/1 MiB usr/lib/boot/kernel: 1/1 MiB usr/lib/boot/kernel: 1/1 MiB + usr/lib/boot/initfs: 0/37 MiB usr/lib/boot/initfs: 0/37 MiB usr/lib/boot/initfs: 1/37 MiB usr/lib/boot/initfs: 2/37 MiB usr/lib/boot/initfs: 3/37 MiB usr/lib/boot/initfs: 4/37 MiB usr/lib/boot/initfs: 5/37 MiB usr/lib/boot/initfs: 6/37 MiB usr/lib/boot/initfs: 7/37 MiB usr/lib/boot/initfs: 8/37 MiB usr/lib/boot/initfs: 9/37 MiB usr/lib/boot/initfs: 10/37 MiB usr/lib/boot/initfs: 11/37 MiB usr/lib/boot/initfs: 12/37 MiB usr/lib/boot/initfs: 13/37 MiB usr/lib/boot/initfs: 14/37 MiB usr/lib/boot/initfs: 15/37 MiB usr/lib/boot/initfs: 16/37 MiB usr/lib/boot/initfs: 17/37 MiB usr/lib/boot/initfs: 18/37 MiB usr/lib/boot/initfs: 19/37 MiB usr/lib/boot/initfs: 20/37 MiB usr/lib/boot/initfs: 21/37 MiB usr/lib/boot/initfs: 22/37 MiB usr/lib/boot/initfs: 23/37 MiB usr/lib/boot/initfs: 24/37 MiB usr/lib/boot/initfs: 25/37 MiB usr/lib/boot/initfs: 26/37 MiB usr/lib/boot/initfs: 27/37 MiB usr/lib/boot/initfs: 28/37 MiB usr/lib/boot/initfs: 29/37 MiB usr/lib/boot/initfs: 30/37 MiB usr/lib/boot/initfs: 31/37 MiB usr/lib/boot/initfs: 32/37 MiB usr/lib/boot/initfs: 33/37 MiB usr/lib/boot/initfs: 34/37 MiB usr/lib/boot/initfs: 35/37 MiB usr/lib/boot/initfs: 36/37 MiB usr/lib/boot/initfs: 37/37 MiB usr/lib/boot/initfs: 37/37 MiB + Starting graphical debug +Framebuffer not found +kernel::arch::x86_shared::start:INFO -- RedBear OS starting... +kernel::startup::memory:INFO -- Memory 900000:7EB3F000 contains reservation 7E0B3000:7E0B5000 +kernel::startup::memory:INFO -- Memory 900000:7E0B3000 contains reservation 7DF2A000:7DF6D000 +kernel::startup::memory:INFO -- Memory 900000:7DF2A000 contains reservation 7DF1A000:7DF1B000 +kernel::startup::memory:INFO -- Memory 900000:7DF1A000 contains reservation 774B0000:799B7000 +kernel::startup::memory:INFO -- Memory 7DF6D000:7E0B3000 overlaps with reservation 7DF6E000:7E0B3000 +kernel::startup::memory:INFO -- Memory 7E0B5000:7EB3F000 contains reservation 7E1C6000:7E1C7000 +kernel::startup::memory:INFO -- Memory: 4051 MB +kernel::startup::memory:INFO -- Permanently used: 9244 KB +kernel::arch::x86_shared::device::local_apic:INFO -- Detected x2APIC +kernel::acpi::madt::arch:WARN -- MADT: x2APIC mode active but no LocalX2Apic entries found; falling back to LocalApic entries with zero-extended IDs +kernel::acpi::madt::arch:WARN -- MADT: duplicate APIC ID 0 in LocalApic entry (x2APIC fallback), firmware bug +I/O APICs: [IoApic { redir_table: [32, 33, 32, 35, 36, 32805, 38, 39, 40, 32809, 32810, 32811, 44, 45, 46, 47, 65536, 65536, 65536, 65536, 65536, 65536, 65536, 65536], gsi_start: 0, count: 23 }], overrides: [Override { bus_irq: 0, gsi: 2, trigger_mode: ConformsToSpecs, polarity: ConformsToSpecs }, Override { bus_irq: 5, gsi: 5, trigger_mode: Level, polarity: ActiveHigh }, Override { bus_irq: 9, gsi: 9, trigger_mode: Level, polarity: ActiveHigh }, Override { bus_irq: 10, gsi: 10, trigger_mode: Level, polarity: ActiveHigh }, Override { bus_irq: 11, gsi: 11, trigger_mode: Level, polarity: ActiveHigh }] +kernel::smbios:INFO -- SMBIOS: no EPS data provided by bootloader +kernel::smbios:INFO -- SMBIOS: no TABLE data provided by bootloader +init: switchroot to /scheme/initfs /scheme/initfs/etc +rtcd: CMOS RTC read successful: 1781017552 +rtcd: failed to set time offset: Permission denied +1970-01-01T00-00-00.727Z [@acpid:31 INFO] acpid start +1970-01-01T00-00-00.728Z [@acpid:101 INFO] acpid: SMBIOS data unavailable (No such device (os error 19)); /scheme/acpi/dmi will be absent (no data from bootloader) +1970-01-01T00-00-00.731Z [@redox_driver_sys::quirks::dmi:191 WARN] quirks: cannot read DMI from /scheme/acpi/dmi: No such device (os error 19); acpid DMI producer is not serving data, all DMI-based rules are inert +vesad: No boot framebuffer +fbbootlogd: No display present yet: Invalid argument (os error 22) +1970-01-01T00-00-00.742Z [@fbcond::display:30 ERROR] fbcond: No display present yet: Invalid argument (os error 22) +1970-01-01T00-00-00.747Z [@hwd:25 INFO] using ACPI backend +1970-01-01T00-00-00.750Z [@pcid:266 INFO] PCI SG-BS:DV.F VEND:DEVI CL.SC.IN.RV +1970-01-01T00-00-00.752Z [@pcid:362 INFO] PCI 0000:00:00.0 8086:29C0 06.00.00.00 6 +1970-01-01T00-00-00.753Z [@redox_driver_sys::quirks::dmi:191 WARN] quirks: cannot read DMI from /scheme/acpi/dmi: No such file or directory (os error 2); acpid DMI producer is not serving data, all DMI-based rules are inert +1970-01-01T00-00-00.756Z [@pcid:362 INFO] PCI 0000:00:01.0 1B36:000D 0C.03.30.01 12 XHCI +1970-01-01T00-00-00.759Z [@pcid:362 INFO] PCI 0000:00:02.0 8086:293E 04.03.00.03 4 +1970-01-01T00-00-00.762Z [@pcid:362 INFO] PCI 0000:00:03.0 1AF4:1000 02.00.00.00 2 +1970-01-01T00-00-00.765Z [@pcid:362 INFO] PCI 0000:00:04.0 1B36:0010 01.08.02.02 1 NVME +1970-01-01T00-00-00.768Z [@pcid:362 INFO] PCI 0000:00:05.0 1AF4:1001 01.00.00.00 1 +1970-01-01T00-00-00.772Z [@pcid:362 INFO] PCI 0000:00:1f.0 8086:2918 06.01.00.02 6 +1970-01-01T00-00-00.774Z [@pcid:362 INFO] PCI 0000:00:1f.2 8086:2922 01.06.01.02 1 SATA AHCI +1970-01-01T00-00-00.776Z [@pcid:362 INFO] PCI 0000:00:1f.3 8086:2930 0C.05.00.02 12 +1970-01-01T00-00-00.778Z [@acpi::aml:106 INFO] Initializing AML interpreter v6.1.1 +1970-01-01T00-00-00.783Z [@pcid::scheme:84 INFO] pcid OPEN `` flags 0x11010000 dirfd=2 +1970-01-01T00-00-00.785Z [@pcid::scheme:98 INFO] pcid OPEN TopLevel with 9 entries: ["0000--00--00.0", "0000--00--01.0", "0000--00--02.0", "0000--00--03.0", "0000--00--04.0", "0000--00--05.0", "0000--00--1f.0", "0000--00--1f.2", "0000--00--1f.3"] +1970-01-01T00-00-00.788Z [@pcid::scheme:199 INFO] pcid GETDENTS id=3 offset=0 entries_count=9 +1970-01-01T00-00-00.790Z [@pcid::scheme:84 INFO] pcid OPEN `0000--00--00.0/channel` flags 0x30000 dirfd=2 +1970-01-01T00-00-00.792Z [@pcid::scheme:84 INFO] pcid OPEN `0000--00--01.0/channel` flags 0x30000 dirfd=2 +1970-01-01T00-00-00.794Z [@pcid::scheme:84 INFO] pcid OPEN `0000--00--02.0/channel` flags 0x30000 dirfd=2 +1970-01-01T00-00-00.796Z [@pcid::scheme:84 INFO] pcid OPEN `0000--00--03.0/channel` flags 0x30000 dirfd=2 +1970-01-01T00-00-00.798Z [@pcid::scheme:84 INFO] pcid OPEN `0000--00--04.0/channel` flags 0x30000 dirfd=2 +1970-01-01T00-00-00.800Z [@pcid_spawner:88 INFO] pcid-spawner: spawn "/scheme/initfs/lib/drivers/nvmed" +kernel::scheme::irq:WARN -- MSI vector 50 arrived before IOMMU remapping was activated. This is normal in QEMU or when no IOMMU is present. +1970-01-01T00-00-00.807Z [@nvmed::nvme::identify:176 INFO]  - Model: QEMU NVMe Ctrl 11.0.0 Serial: NVME_EXTRA Firmware: TR +1970-01-01T00-00-00.810Z [@nvmed::nvme::identify:214 INFO] NSID: 1 Size: 2097152 Capacity: 2097152 +1970-01-01T00-00-00.812Z [@pcid::scheme:84 INFO] pcid OPEN `0000--00--05.0/channel` flags 0x30000 dirfd=2 +1970-01-01T00-00-00.814Z [@pcid_spawner:88 INFO] pcid-spawner: spawn "/scheme/initfs/lib/drivers/virtio-blkd" +1970-01-01T00-00-00.817Z [@virtio_blkd:125 INFO] virtio-blk: initiating startup sequence :^) +1970-01-01T00-00-00.820Z [@virtio_blkd:139 INFO] virtio-blk: disk size: 3145728 sectors and block size of 512 bytes +1970-01-01T00-00-00.834Z [@pcid::scheme:84 INFO] pcid OPEN `0000--00--1f.0/channel` flags 0x30000 dirfd=2 +1970-01-01T00-00-00.836Z [@pcid::scheme:84 INFO] pcid OPEN `0000--00--1f.2/channel` flags 0x30000 dirfd=2 +1970-01-01T00-00-00.838Z [@pcid_spawner:88 INFO] pcid-spawner: spawn "/scheme/initfs/lib/drivers/ahcid" +1970-01-01T00-00-00.842Z [@ahcid:40 INFO] AHCI pci-0000-00-1f.2 on: 4=P60C0 5=80044000 IRQ: 10 +1970-01-01T00-00-00.843Z [@ahcid::ahci:54 INFO] pci-0000-00-1f.2_ahci-0: None +1970-01-01T00-00-00.845Z [@ahcid::ahci:54 INFO] pci-0000-00-1f.2_ahci-1: None +1970-01-01T00-00-00.847Z [@ahcid::ahci:54 INFO] pci-0000-00-1f.2_ahci-2: SATAPI +1970-01-01T00-00-00.869Z [@ahcid::ahci::hba:255 INFO] Serial: QM00005 Firmware: 2.5+ Model: QEMU DVD-ROM 28-bit LBA Size: 0 MB +1970-01-01T00-00-00.872Z [@ahcid::ahci::hba:451 ERROR] IS 40000000 IE 17 CMD 3000006 TFD 2041 +1970-01-01T00-00-00.873Z [@ahcid::ahci::hba:452 ERROR] SSTS 113 SCTL 700 SERR 0 SACT 0 +1970-01-01T00-00-00.875Z [@ahcid::ahci::hba:456 ERROR] CI 0 SNTF 0 FBS 0 +1970-01-01T00-00-00.878Z [@ahcid::ahci:67 ERROR] 2: I/O error +1970-01-01T00-00-00.879Z [@ahcid::ahci:54 INFO] pci-0000-00-1f.2_ahci-3: None +1970-01-01T00-00-00.881Z [@ahcid::ahci:54 INFO] pci-0000-00-1f.2_ahci-4: None +1970-01-01T00-00-00.882Z [@ahcid::ahci:54 INFO] pci-0000-00-1f.2_ahci-5: None +1970-01-01T00-00-00.884Z [@pcid::scheme:84 INFO] pcid OPEN `0000--00--1f.3/channel` flags 0x30000 dirfd=2 +1970-01-01T00-00-00.886Z [@pcid::scheme:199 INFO] pcid GETDENTS id=3 offset=9 entries_count=9 + +thread 'main' (1) panicked at drivers/storage/virtio-blkd/src/scheme.rs:70:9: +assertion `left == right` failed + left: 1 + right: 0 +[virtio-blkd@relibc::header::stdlib:119 ERROR] Abort +Invalid opcode fault +RFLAG: 0000000000010202 +CS: 000000000000002b +RIP: 0000000000455b60 +RSP: 00007fffffffe970 +SS: 0000000000000023 +FSBASE 0000000000004000 +GSBASE 0000000000000000 +KGSBASE ffff80007f8ac000 +RAX: 0000000000000001 +RCX: 0000000000000000 +RDX: 0000000000000018 +RDI: 0000000000006b88 +RSI: 0000000000495398 +R8: 0000000000000000 +R9: 0000000000000003 +R10: 00000000004a1c82 +R11: 0000000000000216 +RBX: 0000000000000001 +RBP: 00007fffffffe9e0 +R12: 00000000004b8298 +R13: 00000000004c0078 +R14: 0000000000000000 +R15: 00007fffffffeaf8 + FP 00007fffffffe9e0: PC 00000000004024da + FP 00007fffffffe9f0: PC 0000000000402349 + FP 00007fffffffea00: PC 0000000000401a1a + FP 00007fffffffea10: PC 000000000042833a + FP 00007fffffffea20: PC 00000000004019ce + FP 00007fffffffea50: PC 00000000004364bb + FP 00007fffffffeae0: PC 00000000004319c2 + FP 00007fffffffeb20: PC 00000000004321ec + FP 00007fffffffeb50: PC 000000000040473c + FP 00007fffffffeb90: PC 0000000000404653 + FP 00007fffffffec20: PC 0000000000400271 + FP 00007fffffffec50: PC 000000000040ab6a + FP 00007fffffffed20: PC 000000000040a330 + FP 00007fffffffed90: PC 0000000000408425 + FP 00007ffffffff030: PC 000000000040b1fc + FP 00007ffffffff390: PC 000000000040ec3c + FP 00007ffffffff8c0: PC 0000000000410648 + FP 00007ffffffffa30: PC 00000000004104b5 + FP 00007ffffffffce0: PC 000000000040fcd9 + FP 00007ffffffffcf0: PC 000000000040fce2 + FP 00007ffffffffd00: PC 000000000040ed91 + FP 00007ffffffffd10: PC 0000000000410d5a + FP 00007ffffffffd20: PC 0000000000435b96 + FP 00007ffffffffd70: PC 000000000040f02d + FP 00007ffffffffd90: PC 0000000000472239 + FP 00007ffffffffeb0: PC 0000000000404da1 + FP 00007ffffffffec0: PC 0000000000404d90 + + FP ffff8000042cfee0: PC ffffffff80071f8c + FFFFFFFF80071E20+016C + kernel::arch::x86_shared::interrupt::exception::invalid_opcode::inner + FP ffff8000042cff50: PC ffffffff8006a926 + FFFFFFFF8006A8F8+002E + kernel::arch::x86_shared::interrupt::exception::invalid_opcode + 00007fffffffe9e0: GUARD PAGE +kernel::context::signal:INFO -- UNHANDLED EXCEPTION, CPU #3, PID 19, NAME /scheme/initfs/lib/drivers/virti, CONTEXT 0xffffff7f8012bd10 +qemu: terminating on signal 15 from pid 1446342 (timeout)