From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 17 Mar 2003 19:03:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 17 Mar 2003 19:03:36 -0500 Received: from holomorphy.com ([66.224.33.161]:28892 "EHLO holomorphy") by vger.kernel.org with ESMTP id ; Mon, 17 Mar 2003 19:03:35 -0500 Date: Mon, 17 Mar 2003 16:14:05 -0800 From: William Lee Irwin III To: Manfred Spraul Cc: Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: [RFC] O(1) proc_pid_readdir Message-ID: <20030318001405.GS20188@holomorphy.com> Mail-Followup-To: William Lee Irwin III , Manfred Spraul , Ingo Molnar , linux-kernel@vger.kernel.org References: <20030316213516.GM20188@holomorphy.com> <20030317070334.GO20188@holomorphy.com> <3E761124.8060402@colorfullife.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E761124.8060402@colorfullife.com> User-Agent: Mutt/1.3.28i Organization: The Domain of Holomorphy Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org William Lee Irwin III wrote: >> The NMI oopses are mostly decoded by hand b/c in-kernel (and other) >> backtrace decoders can't do it automatically. I might have to generate >> some fresh data, with some kind of hack (e.g. hand-coded NMI-based kind >> of smp_call_function) to trace the culprit and not just the victim. >> The victims were usually stuck in fork() or exit(). On Mon, Mar 17, 2003 at 07:17:08PM +0100, Manfred Spraul wrote: > Could you check if the attached test app triggers the NMI oopser? Sure, no problem. -- wli