Date: Tue, 18 Nov 2014 15:03:13 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195148] New: vesa / vt(4) integration issues Message-ID: <bug-195148-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-195148-8>