From owner-freebsd-current Wed Nov 29 11: 2:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from acampi.inet.it (acampi.inet.it [213.92.4.194]) by hub.freebsd.org (Postfix) with SMTP id B9B6937B400 for ; Wed, 29 Nov 2000 11:02:34 -0800 (PST) Received: (qmail 364 invoked by uid 1002); 29 Nov 2000 20:00:42 -0000 Date: Wed, 29 Nov 2000 20:00:42 +0000 From: Andrea Campi To: John Baldwin Cc: freebsd-current@FreeBSD.org Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] Message-ID: <20001129200041.M92759@inet.it> References: <20001129142056.A97794@inet.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Wed, Nov 29, 2000 at 09:09:48AM -0800 Organization: I.NET S.p.A. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Then when it panics write down the values that get printed out. Next, > do 'nm /sys/compile/MYKERNEL/kernel.debug | sort' and look for the function > whose address matches the c_func address printed out, then send this info back > please. :) This time it took me 1 hour to get the panic, compared to a few minutes of earlier panics. So, I got: Bad callout handler: c_func = 0xc025ad3c, c_arg=0xc0338460, c_flags=7 First I tried a db> x/i,10 0xc025ad3c scrn_timer: pushl %ebp [...] nm just confirmed this, so it definitely looks like scrn_timer is to blame here. Any other instructions? ;-) For the time being, vidcontrol -t off (seems to) keep the machine up. Bye, Andrea -- Andrea Campi mailto:firewall@inet.it I.NET S.p.A. http://www.inet.it Direzione Tecnica - Gruppo Security Phone :+39.02.40906.1 v. Caldera, 21/d - I-20153 Milano, Italy Fax :+39.02.40906.303 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message