From owner-freebsd-current Wed Aug 8 7:54:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id B064037B40B for ; Wed, 8 Aug 2001 07:54:02 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id HAA17973; Wed, 8 Aug 2001 07:53:55 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010807234645.A573@edgemaster.zombie.org> Date: Wed, 08 Aug 2001 07:53:57 -0700 (PDT) From: John Baldwin To: Sean Kelly Subject: RE: Random Lockups Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 08-Aug-01 Sean Kelly wrote: > I'm surry I don't have much data to provide, but... > > I've been experiencing random lockups on a -CURRENT kernel from the August > 5th source. I've gotten it a lot when running screen and ssh on two > different terminals at the same time, but that is not the only time it > happens. > > Hardware is a 1.2ghz Thunderbird on an ABIT KT7-RAID > > I'd attach dmesg output or tracebacks, but there are none. It's just a > solid lockup. I'm getting no lockups with a kernel built on July 16th... > > Anybody else seeing this or have ideas how I can debug it further? I'm not > sure how to debug a full lockup. Usually it involves an NMI switch. :( Can you cvs (or cvsup) by dates on the kernel sources to narrow down exactly what day (and possibly what commit) causes these lockups? I.e., does it work fine on August 4th, but break on August 5th? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message