From owner-freebsd-emulation Sat Jun 24 17:50:50 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from io.dreamscape.com (io.dreamscape.com [206.64.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 02EA537B520; Sat, 24 Jun 2000 17:50:39 -0700 (PDT) (envelope-from krentel@dreamscape.com) Received: from dreamscape.com (sa7-p42.dreamscape.com [209.4.228.170]) by io.dreamscape.com (8.9.3/8.8.4) with ESMTP id UAA25575; Sat, 24 Jun 2000 20:48:59 -0400 (EDT) X-Dreamscape-Track-A: sa7-p42.dreamscape.com [209.4.228.170] X-Dreamscape-Track-B: Sat, 24 Jun 2000 20:48:59 -0400 (EDT) Received: (from krentel@localhost) by dreamscape.com (8.9.3/8.9.3) id UAA14215; Sat, 24 Jun 2000 20:49:51 -0400 (EDT) (envelope-from krentel) Date: Sat, 24 Jun 2000 20:49:51 -0400 (EDT) From: "Mark W. Krentel" Message-Id: <200006250049.UAA14215@dreamscape.com> To: freebsd-emulation@freebsd.org, freebsd-fs@freebsd.org Subject: panic running linux binaries from ext2fs Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I get a panic when running linux binaries directly from an ext2fs partition. They run fine on UFS, but on ext2fs they panic. I'm currently using linux_base-6.1 and 4.0-stable (as of May 20), but the problem goes back to at least 3.2. See PR kern/19407. I don't know whether the real problem is with Linux emulation or ext2fs or some weird combination of the two. Or maybe it's something with kernel locking, some of the panics say "lockmgr: not exclusive lock holder". I've asked about this before and the answer was "works fine for me." But it happens so easily and reliably for me that I'm just baffled about what I'm doing differently. I'd like to track this down, but I don't know enough about the internals of the Linuxulator or ext2fs. But I can apply patches and send back stack traces, if someone who knows more about the internals can help me out. --Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message