From owner-freebsd-bugs@FreeBSD.ORG  Tue Nov 18 15:03:13 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 909DA69E
 for <freebsd-bugs@FreeBSD.org>; Tue, 18 Nov 2014 15:03:13 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 792F416F
 for <freebsd-bugs@FreeBSD.org>; Tue, 18 Nov 2014 15:03:13 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAIF3DA9072209
 for <freebsd-bugs@FreeBSD.org>; Tue, 18 Nov 2014 15:03:13 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195148] New: vesa / vt(4) integration issues
Date: Tue, 18 Nov 2014 15:03:13 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: emaste@freebsd.org
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-195148-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2014 15:03:13 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195148

            Bug ID: 195148
           Summary: vesa / vt(4) integration issues
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: emaste@freebsd.org

FreeBSD-current, GENERIC kernel using vt(4) reports on boot:

> module_register_init: MOD_LOAD (vesa, 0xffffffff80dc3400, 0) error 1

And a panic if vesa is loaded from the loader:

> OK load vesa
> /boot/kernel/vesa.ko size 0xb2a8 at 0x1bf2000

...

panic: module_register_init: module named vesa not found

cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff81c04ad0
kdb_backtrace() at kdb_backtrace+0x39/frame 0xffffffff81c04b80
vpanic() at vpanic+0x189/frame 0xffffffff81c04c00
panic() at panic+0x43/frame 0xffffffff81c04c60
module_register_init() at module_register_init+0x22d/frame 0xffffffff81c04c90
mi_startup() at mi_startup+0x108/frame 0xffffffff81c04cb0
btext() at btext+0x2c
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at      kdb_enter+0x3e: movq    $0,kdb_why

-- 
You are receiving this mail because:
You are the assignee for the bug.