From owner-freebsd-current Thu Aug 9 7:38:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id F04D037B40D; Thu, 9 Aug 2001 07:38:50 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f79EcoR15538; Thu, 9 Aug 2001 10:38:50 -0400 (EDT) (envelope-from wollman) Date: Thu, 9 Aug 2001 10:38:50 -0400 (EDT) From: Garrett Wollman Message-Id: <200108091438.f79EcoR15538@khavrinen.lcs.mit.edu> To: John Baldwin Cc: Sean Kelly , current@FreeBSD.ORG Subject: RE: Random Lockups In-Reply-To: References: <20010807234645.A573@edgemaster.zombie.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 < said: > 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? I have a July 26th kernel which every week or so deadlocks on an inode while I'm sending mail. The resulting race-to-the-root soon locks everything up solid. I haven't yet been able to document the precise circumstances which lead to the problem. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message