Date: Wed, 26 Mar 2025 21:51:40 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 285681] [Hyper-V] i386 panic during storvsc_xferbuf_prepare() Message-ID: <bug-285681-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285681 Bug ID: 285681 Summary: [Hyper-V] i386 panic during storvsc_xferbuf_prepare() Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: dim@FreeBSD.org Follow-up from bug 285415, where a panic occurred under Hyper-V, in storvsc_xferbuf_prepare(). Applying the patch from bug 285415 comment 17, t= his shows: cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: <Msft Virtual CD/ROM 1.0> Removable CD-ROM SPC-3 SCSI device cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: 349MB (178896 2048 byte sectors) da0 at blkvsc0 bus 0 scbus2 target 0 lun 0 da0: <Msft Virtual Disk 1.0> Fixed Direct Access SPC-3 SCSI device da0: 300.000MB/s transfers da0: Command Queueing enabled da0: 102400MB (209715200 512 byte sectors) da1 at blkvsc1 bus 0 scbus3 target 1 lun 0 da1: <Msft Virtual Disk 1.0> Fixed Direct Access SPC-3 SCSI device da1: 300.000MB/s transfers da1: Command Queueing enabled da1: 8192MB (16777216 512 byte sectors) segs[0]: ofs 0xf7f45000, len 4096 segs[1]: ofs 0xf7f46000, len 4096 segs[2]: ofs 0xf7f47000, len 4096 segs[3]: ofs 0xf7f48000, len 4096 panic: invalid 1st page, ofs 0xdeadc0de, len 3735929054 cpuid =3D 3 time =3D 1743025553 KDB: stack backtrace: db_trace_self_wrapper(f7,1521eb40,4,4,2a9a8c00,...) at db_trace_self_wrapper+0x28/frame 0x150db174 vpanic(141534a,150db1b0,150db1b0,150db1d0,132bb8c,...) at vpanic+0xf4/frame 0x150db190 panic(141534a,deadc0de,0,deadc0de,356ea000,...) at panic+0x14/frame 0x150db= 1a4 storvsc_xferbuf_prepare(2b136200,2a9a8c00,4,0) at storvsc_xferbuf_prepare+0x14c/frame 0x150db1d0 bus_dmamap_load_mem(26c30f40,2b132e80,150db224,132ba40,2b136200,1) at bus_dmamap_load_mem+0x2f2/frame 0x150db204 bus_dmamap_load_ccb(26c30f40,2b132e80,356ea000,132ba40,2b136200,1) at bus_dmamap_load_ccb+0x4a/frame 0x150db244 storvsc_action(2b0d5140,356ea000) at storvsc_action+0x3a7/frame 0x150db290 xpt_run_devq(2b0d1040,35676000,128b1890,2b0d1050,356ea000,...) at xpt_run_devq+0x287/frame 0x150db2cc xpt_action_default(356ea000) at xpt_action_default+0x3c6/frame 0x150db2f0 scsi_action(356ea000) at scsi_action+0x19/frame 0x150db308 dastart(2b1cd900,356ea000) at dastart+0x30d/frame 0x150db344 xpt_run_allocq(2b1cd900,480) at xpt_run_allocq+0x8b/frame 0x150db36c cam_iosched_schedule(2fd33c80,2b1cd900) at cam_iosched_schedule+0x21/frame 0x150db380 dastrategy(356e3d9c) at dastrategy+0x64/frame 0x150db39c g_disk_start(356e4a78,150db420,2fd33980,4000,0,...) at g_disk_start+0x469/f= rame 0x150db3fc g_io_request(356e4a78,356bc000) at g_io_request+0x26b/frame 0x150db424 g_read_data(356bc000,400,0,4000,0,150db464) at g_read_data+0x99/frame 0x150db444 gpt_read_tbl(1,356da200,0,0,ffffff,...) at gpt_read_tbl+0x10e/frame 0x150db= 490 g_part_gpt_read(35704c00,356bc000) at g_part_gpt_read+0x96/frame 0x150db4c8 G_PART_READ(3568af00,356f5150,3568af00,2fd33980,18186d8,...) at G_PART_READ+0x39/frame 0x150db4e0 g_part_taste(18186d8,2fd33980,0) at g_part_taste+0x14f/frame 0x150db500 g_new_provider_event(2fd33980,0) at g_new_provider_event+0x96/frame 0x150db= 51c g_run_events(0,150db568) at g_run_events+0x10c/frame 0x150db538 fork_exit(ebde80,0,150db568,0,0,...) at fork_exit+0x6b/frame 0x150db554 fork_trampoline() at 0xffc0348e/frame 0x150db554 So "ofs 0xdeadc0de" is pretty bad, and len 3735929054 is also 0xdeadc0de. This is different from the original panic, which said: panic: invalid 1st page, ofs 0x3985000, len 2048 But that might also have been some sort of garbage value? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-285681-227>