>
> Does:
>
> cat /dev/null > bad.file
>
> Cause a kernel panic?
>
>
>
ah, sadly that does cause a kernel panic. I hadn't tried it though, thanks
for the suggestion.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
from Mark Linimon :
> In an ideal world, the bits that will almost certainly become FreeBSD 9.1
> would not appear on the masters, or any of the mirrors, until the same
> instant that the release announcement is set to freebsd-annou...@freebsd.org.
> In practice this doesn't happen. If there is
Hello everyone,
I'm running FreeBSD 9.1-PRERELEASE and today I synchronised my /usr/src
directory with the svn_stable_9 branch on gitorious [1]. I am using ccache.
My /etc/make.conf contains the following:
-8<-
CPUTYPE?=native
CFLAGS=-O3 -pipe
COPT
On Sat, Dec 29, 2012 at 1:46 PM, Thomas Mueller wrote:
> from Mark Linimon :
>
>> In an ideal world, the bits that will almost certainly become FreeBSD 9.1
>> would not appear on the masters, or any of the mirrors, until the same
>> instant that the release announcement is set to freebsd-annou...@
On Sat, Dec 29, 2012 at 1:59 PM, Kimmo Paasiala wrote:
> On Sat, Dec 29, 2012 at 1:46 PM, Thomas Mueller
> wrote:
>> from Mark Linimon :
>>
>>> In an ideal world, the bits that will almost certainly become FreeBSD 9.1
>>> would not appear on the masters, or any of the mirrors, until the same
>>>
On 29-12-12 12:53, Mark van Dijk wrote:
> (...)
> I'll admit that I did modify my make.conf right before building. It
> already *did* contain the CC/CXX/CPP lines for clang but the ccache
> portion was slightly different. It used to contain the literal contents
> of ccache-howto-freebsd.txt:
>
> C
On Fri, Dec 28, 2012 at 01:27:24PM +0200, Konstantin Belousov wrote:
> Please try the following patch. It is against HEAD, might need some
> adjustments for 8. I do the resume and write accounting atomically,
> not allowing other suspension to intervent between.
So is this only limited to snapshot
On 29-12-12 12:53, Mark van Dijk wrote:
> I suspect that the error is caused by -march=native, my CPU is an Intel
> Core i5.
Looks like I was correct. CPUTYPE?=core2 will build world fine so
perhaps 'native' does not know about my processor yet. Apparently it
falls back to assuming it's a i686.
M
On Sat, Dec 29, 2012 at 8:34 AM, Mark van Dijk wrote:
> On 29-12-12 12:53, Mark van Dijk wrote:
>> I suspect that the error is caused by -march=native, my CPU is an Intel
>> Core i5.
>
> Looks like I was correct. CPUTYPE?=core2 will build world fine so
> perhaps 'native' does not know about my pro
On 2012-12-29 20:02, Scot Hetzel wrote:> On Sat, Dec 29, 2012 at 8:34 AM, Mark van
Dijk wrote:
On 29-12-12 12:53, Mark van Dijk wrote:
I suspect that the error is caused by -march=native, my CPU is an Intel
Core i5.
Looks like I was correct. CPUTYPE?=core2 will build world fine so
perhaps 'n
Humph, so it's not supported, then it's working then it's not supported
again.
How come it's working for most (I'm not being sarcastic, genuinely
concerned, as setting to native is handy)?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/FreeBSD-9-amd64-buildworld-stage-4-
e.g. Penryn CPU:
$ cc -march=native -E -v - &1 | grep cc1
"/usr/bin/cc" -cc1 -triple x86_64-unknown-freebsd9.0 -E -disable-free
-main-file-name - -mrelocation-model static -mdisable-fp-elim -masm-verbose
-mconstructor-aliases -munwind-tables -target-cpu penryn
-momit-leaf-frame-pointer -v -resour
On Sat, Dec 29, 2012 at 12:35 AM, Greg Bonett wrote:
>
> >
> > Does:
> >
> > cat /dev/null > bad.file
> >
> > Cause a kernel panic?
> >
> >
> >
> ah, sadly that does cause a kernel panic. I hadn't tried it though, thanks
> for the suggestion.
It's probably a long shot, but you may try removing ba
> It's probably a long shot, but you may try removing bad file using
> illumos (ex opensolaris) system (or liveCD). In the past it used to be
> a little bit more robust than FreeBSD when it came to dealing with
> filesystem corruption. In one case I had illumos printed out a message
> about corrupt
14 matches
Mail list logo
