Date: Thu, 18 Dec 2014 07:43:24 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 196084] New: UEFI boot panic: Unable to reserve vt_fb memory Message-ID: <bug-196084-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196084 Bug ID: 196084 Summary: UEFI boot panic: Unable to reserve vt_fb memory Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: editor@callfortesting.org Created attachment 150708 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=150708&action=edit Backtrace Hardware: Thinkpad T420 i5 with NVidia graphics BIOS: Fails with UEFI, Legacy or UEFI/Legacy BIOS: Fails with Discreet (NVidia) or Integrated Graphics 11.0-CURRENT from git://xenbits.xen.org/people/royger/freebsd.git | pvh_dom0_v9 >From December 15th, 2014 - Unable to determine equivalent upstream revision Checkout steps: http://wiki.xenproject.org/wiki/FreeBSD_Dom0 >From there, I built world, kernel and release For whatever reason, the copied /usr/src/release/amd64/make-uefi-memstick.sh to make-memstick.sh and it is built with the release. Upon boot to the resulting UEFI memstick image, the error appears after the vtfb0 driver probes: UEFI boot panic: Unable to reserve vt_fb memory This likely has nothing to do with the Xen DOM0 patches in their branch but I would not know as I am not a FreeBSD developer. See the attached photo of the backtrace. I will try to add the loader stage and panic but this seems to only allow for one photo. UEFI solves what problem exactly? -- 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-196084-8>