From owner-freebsd-current Thu Nov 2 13:19:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 5635537B4D7; Thu, 2 Nov 2000 13:19:47 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id eA2LFjh00473; Thu, 2 Nov 2000 22:15:45 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Akinori MUSHA" Cc: Marcel Moolenaar , Andrew Gallatin , Marcel Moolenaar , current@FreeBSD.ORG, morganw@chemicals.tacorp.com Subject: Re: cvs commit: src/sys/compat/linux linux_stats.c In-Reply-To: Your message of "Fri, 03 Nov 2000 05:52:42 +0900." <86g0lap04l.wl@archon.local.idaemons.org> Date: Thu, 02 Nov 2000 22:15:45 +0100 Message-ID: <471.973199745@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <86g0lap04l.wl@archon.local.idaemons.org>, "Akinori MUSHA" writes: >At Thu, 02 Nov 2000 15:26:29 -0500, >Marcel Moolenaar wrote: >> >> Akinori MUSHA wrote: >> > >> > At Thu, 2 Nov 2000 14:11:44 -0500 (EST), >> > Andrew Gallatin wrote: >> > > To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls? >> > >> > Yes. >> >> How is linux_ustat involved if the panic is caused by a native binary? > >Not at all. Sorry, that was my mistaken assumption, after all. :( > >I confirmed linux ls didn't cause panic, so the culprit should belong >somewhere else. Hopefully phk will catch it for us. :) I hope I just did. Please report back if this has or hasn't solve the problem. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message