From owner-freebsd-bugs@FreeBSD.ORG  Tue Jul 29 19:01:43 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 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 25F0EF1C
 for <freebsd-bugs@FreeBSD.org>; Tue, 29 Jul 2014 19:01:43 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 06AE5267E
 for <freebsd-bugs@FreeBSD.org>; Tue, 29 Jul 2014 19:01:43 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6TJ1gcb071945
 for <freebsd-bugs@FreeBSD.org>; Tue, 29 Jul 2014 19:01:42 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 192248] New: [vt] panic in vtbuf_fill_locked from vt_upgrade
 with no vt(4) drivers attached
Date: Tue, 29 Jul 2014 19:01:43 +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 Only Me
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-192248-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
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, 29 Jul 2014 19:01:43 -0000

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

            Bug ID: 192248
           Summary: [vt] panic in vtbuf_fill_locked from vt_upgrade with
                    no vt(4) drivers attached
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: emaste@freebsd.org

** I have no early vt(4) driver:
VT: init without driver.

** My WIP vt(4) fb driver fails to attach:
terasic_mtl0: Failed to attach fbd device

** Later vt_upgrade gets called and panics:
panic: vtbuf_fill_locked begin.tp_row 0 must be < screen height 0
cpuid = 0
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at      kdb_enter+0x8c: lui     at,0x0
db> bt
Tracing pid 0 tid 100000 td 0xffffffff80729c20
db_trace_thread+40 (?,?,?,?) ra ffffffff80117514 sp 98000000007c5ca0 sz 32
ffffffff80117388+18c (ff0000,?,ffffffff,?) ra ffffffff801165f0 sp
98000000007c5cc0 sz 64
ffffffff80116168+488 (?,?,?,?) ra ffffffff801168bc sp 98000000007c5d00 sz 224
db_command_loop+f4 (?,?,?,?) ra ffffffff8011a2c8 sp 98000000007c5de0 sz 32
ffffffff8011a120+1a8 (?,?,?,?) ra ffffffff802e3e10 sp 98000000007c5e00 sz 832
kdb_trap+1f0 (?,?,?,?) ra ffffffff80515bb0 sp 98000000007c6140 sz 64
trap+10d8 (?,?,?,?) ra ffffffff804ff34c sp 98000000007c6180 sz 320
MipsKernGenException+168 (0,0,80582490,aa) ra ffffffff802e3944 sp
98000000007c62c0 sz 448
kdb_enter+8c (?,?,?,?) ra ffffffff80293800 sp 98000000007c6480 sz 32
ffffffff80293550+2b0 (?,?,?,?) ra ffffffff80293930 sp 98000000007c64a0 sz 32
kassert_panic+c8 (?,0,0,107b3ac) ra ffffffff80186fd4 sp 98000000007c64c0 sz 128
vtbuf_fill_locked+54 (?,?,?,?) ra ffffffff80188ddc sp 98000000007c6540 sz 64
ffffffff80188dc8+14 (?,?,?,?) ra ffffffff802fc28c sp 98000000007c6580 sz 32
terminal_set_winsize_blank+1bc (?,?,?,?) ra ffffffff802fc2e0 sp
98000000007c65a0 sz 96
terminal_set_winsize+28 (?,?,?,?) ra ffffffff80189654 sp 98000000007c6600 sz 32
vt_upgrade+194 (?,?,?,?) ra ffffffff802231dc sp 98000000007c6620 sz 160
mi_startup+20c (?,?,?,?) ra ffffffff8010026c sp 98000000007c66c0 sz 32
_start+dc (?,?,?,?) ra 0 sp 98000000007c66e0 sz 0
pid 0
db>

presumably vt_upgrade needs to detect the case that only the dummy driver
exists, and do nothing

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