From owner-freebsd-stable@FreeBSD.ORG Tue Nov 29 06:50:38 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 482FF106567D for ; Tue, 29 Nov 2011 06:50:38 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id 2EE438FC1B for ; Tue, 29 Nov 2011 06:50:37 +0000 (UTC) Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta12.emeryville.ca.mail.comcast.net with comcast id 2ufE1i0020EPchoACuqXgd; Tue, 29 Nov 2011 06:50:31 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta01.emeryville.ca.mail.comcast.net with comcast id 2ucr1i00t1t3BNj8MucsLs; Tue, 29 Nov 2011 06:36:52 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id BF003102C1D; Mon, 28 Nov 2011 22:50:36 -0800 (PST) Date: Mon, 28 Nov 2011 22:50:36 -0800 From: Jeremy Chadwick To: Mike Andrews Message-ID: <20111129065036.GA21518@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, Jack Vogel Subject: Re: Sporadic 9.0-RC2 boot-time panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2011 06:50:38 -0000 On Mon, Nov 28, 2011 at 05:37:27PM -0500, Mike Andrews wrote: > *Sometimes* when booting 9.0-RC2 on *some* of my machines, I'll get > one of the following two panics during multiuser startup, usually > while running the /usr/local/etc/rc.d scripts. (The instruction > pointer is always exactly one of these two, and they look fairly > related.) If after two or three reboots it manages to not panic, > the system will run perfectly stable. > > For some probably-unrelated reason, the dump never finishes in either case. > > First panic (note em0 warning before it): > ----- > em0: discard frame w/o packet header > > > Fatal trap 9: general protection fault while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xffffffff805e4fc5 > stack pointer = 0x28:0xffffff80003299e0 > frame pointer = 0x28:0xffffff8000329a00 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 12 (irq256: em0:rx 0) > trap number = 9 > panic: general protection fault > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > kdb_backtrace() at kdb_backtrace+0x37 > panic() at panic+0x187 > trap_fatal() at trap_fatal+0x290 > trap() at trap+0x10a > calltrap() at calltrap+0x8 > --- trap 0x9, rip = 0xffffffff805e4fc5, rsp = 0xffffff80003299e0, rbp = 0xffffff8000329a00 --- > m_freem() at m_freem+0x25 > ether_nh_input() at ether_nh_input+0x82 > netisr_dispatch_src() at netisr_dispatch_src+0x20b > em_rxeof() at em_rxeof+0x1ca > em_msix_rx() at em_msix_rx+0x24 > intr_event_execute_handlers() at intr_event_execute_handlers+0x104 > ithread_loop() at ithread_loop+0xa4 > fork_exit() at fork_exit+0x11f > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff8000329d00, rbp = 0 --- > Uptime: 49s > Dumping 679 out of 12263 MB: > > ----- > > Second panic (no em0 discard warning this time): > > ----- > > Fatal trap 9: general protection fault while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xffffffff8063c0e4 > stack pointer = 0x28:0xffffff8000329a00 > frame pointer = 0x28:0xffffff8000329a40 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 12 (irq256: em0:rx 0) > trap number = 9 > panic: general protection fault > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > kdb_backtrace() at kdb_backtrace+0x37 > panic() at panic+0x187 > trap_fatal() at trap_fatal+0x290 > trap() at trap+0x10a > calltrap() at calltrap+0x8 > --- trap 0x9, rip = 0xffffffff8063c0e4, rsp = 0xffffff8000329a00, rbp = 0xffffff8000329a40 --- > ether_nh_input() at ether_nh_input+0x94 > netisr_dispatch_src() at netisr_dispatch_src+0x20b > em_rxeof() at em_rxeof+0x1ca > em_msix_rx() at em_msix_rx+0x24 > intr_event_execute_handlers() at intr_event_execute_handlers+0x104 > ithread_loop() at ithread_loop+0xa4 > fork_exit() at fork_exit+0x11f > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff8000329d00, rbp = 0 --- > Uptime: 46s > Dumping 657 out of 12263 MB:..3% We need the following things: * uname -a output * dmesg output (only details specific to emX NICs please) * pciconf -lvcb output (only details specific to emX NICs please) CC'ing Jack Vogel (driver author) who can hopefully shed some light on this. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |