From owner-freebsd-current@FreeBSD.ORG Mon Feb 6 15:05:38 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E440106564A; Mon, 6 Feb 2012 15:05:38 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id 298938FC1B; Mon, 6 Feb 2012 15:05:37 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirj.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1RuQ8O-00051g-El; Mon, 06 Feb 2012 15:05:36 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1RuQ8O-0001oj-9W; Mon, 06 Feb 2012 15:05:36 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.5/8.14.5) with ESMTP id q16F5akH072024; Mon, 6 Feb 2012 15:05:36 GMT (envelope-from mexas@bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.5/8.14.5/Submit) id q16F5a7b072023; Mon, 6 Feb 2012 15:05:36 GMT (envelope-from mexas@bris.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bris.ac.uk using -f Date: Mon, 6 Feb 2012 15:05:35 +0000 From: Anton Shterenlikht To: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org Message-ID: <20120206150535.GA71948@mech-cluster241.men.bris.ac.uk> Mail-Followup-To: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org References: <20120206142239.GA71689@mech-cluster241.men.bris.ac.uk> <20120206144444.GA71830@mech-cluster241.men.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120206144444.GA71830@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.4.2.3i Cc: Subject: SOLVED: Re: ia64 fatal kernel trap [WAS: panic] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2012 15:05:38 -0000 On Mon, Feb 06, 2012 at 02:44:44PM +0000, Anton Shterenlikht wrote: > On Mon, Feb 06, 2012 at 02:22:39PM +0000, Anton Shterenlikht wrote: > > On ia64 I've built kernel and world with r230941. > > After installkernel, reboot, installworld, mergemaster, > > make remove-old, I reboot and get this panic at the very end: > > > > Recovering vi editor sessions:. > > /usr/local/etc/rc.d/svnserve: set_rcvar: not found > > Starting svnserve. > > su: unknown login: svn > > /etc/rc: WARNING: failed to start svnserve > > Updating motd:. > > Starting ntpd. > > /usr/local/etc/rc.d/rsyncd: set_rcvar: not found > > Starting rsyncd. > > /usr/local/etc/rc.d/gmond: set_rcvar: not found > > /etc/rc: WARNING: /usr/local/etc/rc.conf is not readable. > > /etc/rc: WARNING: failed precmd routine for rc > > /usr/local/etc/rc.d/bsdstats: set_rcvar: not found > > Starting bsdstats. > > > > fatal kernel trap (cpu 1): > > > > trap vector = 0x14 (Page Not Present) > > cr.iip = 0x9ffc0000008cb960 > > cr.ipsr = 0x1010080a6018 (ac,mfl,ic,i,dt,dfh,rt,cpl=0,it,ri=0,bn) > > cr.isr = 0x400000000 (code=0,vector=0,r,ei=0) > > cr.ifa = 0x168 > > curthread = 0xe000000011a9f9e0 > > pid = 760, comm = dig > > > > [ thread pid 760 tid 100073 ] > > Stopped at cpu_set_upcall+0x190: [M0] ld8 r14=[r14] ;; > > db> > > db> show proc 760 > > Process 760 (dig) at 0xe000000011a9a8e0: > > state: NORMAL > > uid: 0 gids: 0 > > parent: pid 759 at 0xe000000011b64000 > > ABI: FreeBSD ELF64 > > arguments: dig > > threads: 1 > > 100073 Run CPU 1 dig > > db> > > db> thread 100073 > > [ thread pid 760 tid 100073 ] > > cpu_set_upcall+0x190: [M0] ld8 r14=[r14] ;; > > db> > > db> bt > > Tracing pid 760 tid 100073 td 0xe000000011a9f9e0 > > cpu_set_upcall(0xe000000011a9e8a0, 0xe000000011a9f9e0, 0xa0000000f87ab780, 0xa0000000f87ab550) at cpu_set_upcall+0x190 > > create_thread(0xe000000011a9f9e0, 0x0, 0x1209a7090, 0x120c04800, 0x7fffffffff9fe000, 0x200000, 0x12039c200, 0x120c04800) at create_thread+0x1c0 > > kern_thr_new(0xe000000011a9f9e0, 0xa0000000f872b330, 0x9ffc000000436360) at kern_thr_new+0x100 > > sys_thr_new(0xe000000011a9f9e0, 0xa0000000f872b4e8, 0x9ffc0000008c6bf0, 0x48d) at sys_thr_new+0xa0 > > syscall(0xe000000011a9a8e0, 0xa0000000f872b3a8, 0x120c0442c, 0xe000000011a9f9e0, 0x0, 0x0, 0x9ffc0000008c2ec0, 0x8) at syscall+0x550 > > epc_syscall_return() at epc_syscall_return > > db> > > > > Please advise > > If I boot kernel.old, r224965, then the > network doesn't work: > > mech-as28# ifconfig -a > em0: flags=8843 metric 0 mtu 1500 > options=209b > ether 00:13:21:5b:05:1c > nd6 options=29 > media: Ethernet autoselect (1000baseT ) > status: active > em1: flags=8843 metric 0 mtu 1500 > options=209b > ether 00:13:21:5b:05:1d > nd6 options=29 > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 metric 0 mtu 16384 > options=3 > nd6 options=21 > mech-as28# ifconfig em0 inet 137.222.187.28 > ifconfig: ioctl (SIOCAIFADDR): Invalid argument > mech-as28# > > How can recover from this? I removed bsdstats, this was enough to stop the panic. I can now boot r230941. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423