Date: Fri, 28 Mar 2025 08:50:14 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 285681] [Hyper-V] i386 panic during storvsc_xferbuf_prepare() Message-ID: <bug-285681-27103-exwak3z49q@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-285681-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-285681-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285681 Mark Johnston <markj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open CC| |whu@FreeBSD.org --- Comment #5 from Mark Johnston <markj@FreeBSD.org> --- (In reply to Dimitry Andric from comment #4) I'm wondering if the panic is reproducible with less than 4GB of RAM. In particular, I guess we're bouncing the I/O pages, and since the driver does= n't keep track of the 1st page offset, this flag fixes the problem. Could you please try, say, 3GB of RAM, and without the patch? In particular I note t= hat the page address passed by storvsc_xferbuf_prepare() is a uint64_t, so mayb= e we can avoid bouncing entirely on i386. If that works, it still doesn't explain why we need to disable the assertio= n on arm64. Can we try the same test from comment 2 on arm64? --=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-27103-exwak3z49q>