From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 23 02:20:23 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC8B5106564A for ; Mon, 23 Jan 2012 02:20:23 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id C16A88FC17 for ; Mon, 23 Jan 2012 02:20:23 +0000 (UTC) Received: by dadi14 with SMTP id i14so1944593dad.13 for ; Sun, 22 Jan 2012 18:20:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XOE2Tqlwkj2UbhgV79OKNkiReXaLxXWWmvXSXVAWhvc=; b=daZrlhIWxcJC33ivFlWi9ScaxhF0vRR9BSNn6mdevUzaNsyymDFpFI0vPJXTumhip9 wUNVe+QqJDgsMuqVAe+4Hw9w1m6BnrLUAPm8NgrMiUyIyy/dnmGpjHG2qhKSj01T3P4x G36ltA52yscdeadU0azCpDQV5y7iynxHSfl/I= MIME-Version: 1.0 Received: by 10.68.116.237 with SMTP id jz13mr18237854pbb.100.1327285223476; Sun, 22 Jan 2012 18:20:23 -0800 (PST) Received: by 10.68.136.106 with HTTP; Sun, 22 Jan 2012 18:20:23 -0800 (PST) In-Reply-To: <20120122210830.02d4bef6@atom.dino.sk> References: <20120117210108.28d007ec@atom.dino.sk> <20120119213116.579cac18@atom.dino.sk> <20120122210830.02d4bef6@atom.dino.sk> Date: Sun, 22 Jan 2012 21:20:23 -0500 Message-ID: From: Super Bisquit To: Milan Obuch Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-ppc@freebsd.org Subject: Re: Broken nullfs on powerpc X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2012 02:20:24 -0000 You need to report this to the FeeeBSD current mailing list. On 1/22/12, Milan Obuch wrote: > On Fri, 20 Jan 2012 11:04:51 -0500 > Super Bisquit wrote: > >> I have attached the MYKERNEL powerpc conf file. Look under debugging. >> I have nullfs built and running as a module. What test do you want me >> to run to see if it is working for me? >> > > So basically you have all debugging disabled... OK, I tested it this > way too and no go. Still almost instant trap/panic/reboot when trying > to write into null mounted directory, and, sometimes even just reading > it shows similar behavior. > > I am using freshly csup'ped sources for every build, 10-CURRENT. In my > case, nullfs is loaded as module, too, so if you could really use null > mounted directory to work with, there is some other difference between > us... > > In my case, command sequence > > mount_nullfs /data/src10 /usr/src > csup /usr/share/examples/cvsup/standard-supfile > > yields almost immediate panic, reproducible 100 %. > > Regards, > Milan >