Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Jan 2012 21:08:30 +0100
From:      Milan Obuch <freebsd-ppc@dino.sk>
To:        Super Bisquit <superbisquit@gmail.com>
Cc:        freebsd-ppc@freebsd.org
Subject:   Re: Broken nullfs on powerpc
Message-ID:  <20120122210830.02d4bef6@atom.dino.sk>
In-Reply-To: <CA%2BWntOurkEm3H%2B9SJM4U9zo40195ni%2B4_tmj3jqQHzV01h-cbw@mail.gmail.com>
References:  <20120117210108.28d007ec@atom.dino.sk> <CA%2BWntOvRaKkbvdaTWZmTnXzixm_Grjmg7p5mg5sq-ZZ3tn9AjQ@mail.gmail.com> <20120119213116.579cac18@atom.dino.sk> <CA%2BWntOurkEm3H%2B9SJM4U9zo40195ni%2B4_tmj3jqQHzV01h-cbw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 20 Jan 2012 11:04:51 -0500
Super Bisquit <superbisquit@gmail.com> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120122210830.02d4bef6>