From owner-freebsd-current Wed Feb 7 1:37:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp6.port.ru (mx6.port.ru [194.67.23.42]) by hub.freebsd.org (Postfix) with ESMTP id 0348C37B699; Wed, 7 Feb 2001 01:36:55 -0800 (PST) Received: from adsl-141-154-118-213.bostma.adsl.bellatlantic.net ([141.154.118.213] helo=kan.dnsalias.net) by smtp6.port.ru with esmtp (Exim 3.14 #87) id 14QR1w-000Lyk-00; Wed, 07 Feb 2001 12:36:53 +0300 Received: (from kan@localhost) by kan.dnsalias.net (8.11.2/8.11.2) id f175woN00732; Wed, 7 Feb 2001 00:58:50 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.6 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 07 Feb 2001 00:58:49 -0500 (EST) From: "Alexander N. Kabaev" To: freebsd-current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup Cc: John Baldwin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can easily reproduce the panic on my -CURRENT Athlon box by just starting any print job. Other that that, the system seems to be running OK, i.e. no panics occur unless some lpr activity is involved. Here is the stack dump: #9 0xc02a9fbc in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = -857849588, tf_esi = 32, tf_ebp = -696148124, tf_isp = -696148164, tf_ebx = -1069967232, tf_edx = -857849856, tf_ecx = -868400672, tf_eax = -1070952435, tf_trapno = 9, tf_err = 32, tf_eip = -1070952316, tf_cs = 8, tf_eflags = 65670, tf_esp = -1071733991, tf_ss = 0}) at ../../i386/i386/trap.c:656 #10 0xc02a9084 in sw1b () #11 0xc02b075b in ithd_loop (dummy=0x0) at ../../i386/isa/ithread.c:216 #12 0xc01dc48d in fork_exit (callout=0xc02b0664 , arg=0x0, frame=0xd6819fa8) at ../../kern/kern_fork.c:669 and disassembled code at the point of the trap looks like 0xc02a9076 : mov %eax,0x0(%ebx) 0xc02a9079 : mov 0x4(%edi),%eax 0xc02a907c : mov %eax,0x4(%ebx) 0xc02a907f : mov $0x20,%esi 0xc02a9084 : ltr %si ...... ^^^^^^^^^^^^^^ Also, a pretty unpleasant crash occurs on the latest current boxes everytime vidcontrol is used to change console resolution to the VESA_800x600 mode. I was able to get the crash dump, but unfortunately it seems like the stack is becoming corrupt and so there is no useful information to report. ---------------------------------- E-Mail: Alexander N. Kabaev Date: 07-Feb-2001 Time: 00:35:38 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message