From owner-freebsd-current@FreeBSD.ORG Tue Jul 13 05:52:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EFD316A4CE for ; Tue, 13 Jul 2004 05:52:57 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A476A43D1D for ; Tue, 13 Jul 2004 05:52:56 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i6D5qqhd024970; Tue, 13 Jul 2004 01:52:52 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i6D5qq6G024967; Tue, 13 Jul 2004 01:52:52 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Tue, 13 Jul 2004 01:52:52 -0400 (EDT) From: Andre Guibert de Bruet To: Mike Schreckengost In-Reply-To: Message-ID: <20040713011400.S24726@alpha.siliconlandmark.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Hard lockups on CURRENT w/backtrace (Was: -current panic:kse/thread mismatch?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 13 Jul 2004 05:52:57 -0000 On Mon, 12 Jul 2004, Mike Schreckengost wrote: > Within the past week or so, I have been experiencing severe stability > problems (i.e., hard lockups) with FreeBSD-current. I am using a stock > GENERIC kernel (with the exception of 'device atapicam'). Usually these > lockups occur while I am using Mozilla, XMMS or other X-based applications, > and until tonight I have been unable to get a kernel panic or other useful > information to help in diagnosing the problem. This evening, I logged into > X-Windows and started to play a music file in XMMS. I switched back to the > text console and captured (by hand) the following panic about 1m30s later: > > panic: kse/thread mismatch > cpuid = 1; > boot() called on cpu#1 > > syncing disks, buffers remaining... panic: pmap_invalidate_range: interrupts > disabled > cpuid=1; > boot() called on cpu#1 > Uptime: 6m6s > > The system locked up without dropping me to the debugger, so I am unable to "Me too". I managed to get a backtrace on this badboy through a serial console. Sources are from shortly before the following: FreeBSD 5.2-CURRENT #1: Mon Jul 12 22:58:33 EDT 2004 root@bling.home:/usr/CURRENT/sys/i386/compile/BLING panic: kse/thread mismatch cpuid = 0; KDB: stack backtrace: kdb_backtrace(60736ebe,0,607373c7,b018eb90,100) at 0x60577d2e panic(607373c7,65dbc540,0,b018ebc0,6056f97a) at 0x6055d4e3 choosethread(6580bb40,1,607381c4,288,659db1bc) at 0x605639d0 sched_switch(65dbc540,0,60737644,129,10f212e6) at 0x6056f97a mi_switch(1,0,60739605,198,0) at 0x605653b3 sleepq_switch(6580c4dc,607b5100,1,6073619e,0) at 0x6057e3a6 sleepq_timedwait_sig(6580c4dc,0,60737644,e7,0) at 0x6057e6c7 msleep(6580c4dc,659db228,168,60734bf4,5) at 0x60564f9f kse_release(65dbc540,b018ed14,4,431,1) at 0x605493fc syscall(2f,2f,2f,8136100,0) at 0x606efab2 Xint0x80_syscall() at 0x606dbb3f --- syscall (383, FreeBSD ELF32, kse_release), eip = 0x48174e7b, esp = 0x8141f98, ebp = 0x8141fd4 --- KDB: enter: panic Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >