Date: Tue, 19 Jun 2018 21:49:59 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured Message-ID: <bug-229167-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229167 Bug ID: 229167 Summary: [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: decui@microsoft.com People are seeing some different call-traces with FreeBSD 11.2 and/or the latest CURRENT code recently and some call-traces are mentioned here : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220453 #1: panic in namei(): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220453#c5 #2: panic in vmbus_msghc_exec(): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220453#c7 It's reported FreeBSD-12.0-CURRENT-amd64-20180618-r335317-disc1.iso also reproduces this call-panic. #3: No detailed call-trace. It looks the panic happens just after root is mounted.: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220453#c14 But it looks I can't reproduce the issue any more, after I fresh-build a ke= rnel with the same version. Not sure if this is some kind of weird memory corrup= tion issue. --=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-229167-227>