Project

General

Profile

Actions
Copy link

Bug #6631

closed

vesa_configure error on boot

Added by Thijs Cramer almost 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
07/20/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

I have the same issue as this FreeBSD Mailing List thread: http://markmail.org/message/aoq6ub636ainxcxe#query:+page:1+mid:a2e5f6rwvz5ke6bb+state:results

From what i can understand, it's something in the kernel regarding <1MB Memory allocations. Fixed in FreeBSD Upstream kernel. (Verified with lateste FreeBSD11-CURRENT ISO)

Can we get this in pfSense?

Files

vesa_error.jpg (1.47 MB) vesa_error.jpg Thijs Cramer, 07/20/2016 01:02 PM
Actions
Copy link
 #1

Updated by Chris Buechler almost 9 years ago

  • Status changed from New to Closed
  • Priority changed from High to Normal

The change that's in reference to was only in 11, what you're seeing there isn't the same thing. Not a bug in our code, and not on hardware we sell and support, you'll need to replicate with stock FreeBSD and report upstream.

Actions
Copy link
 #2

Updated by Thijs Cramer almost 9 years ago

I've verified that it's already fixed. Not that the bug still persists. This means that the pfSense kernel should be patched with the upstream commit.

Actions
Copy link
 #3

Updated by Jim Pingle almost 9 years ago

In that case we'll get the change automatically when we switch to a FreeBSD 11 base for pfSense 2.4, which is only a few months out. Still not a bug in our code.

More trouble than it's worth to attempt to pull in extra upstream patches at this point since we're about to ship 2.3.2 and there won't be another full release in between (just security/errata patches)

Actions
Copy link

Also available in: Atom PDF