I just got this on one of the alpha package build machines
Kris
panic: mutex Giant not owned at /local0/src-client/sys/vm/vm_kern.c:312
db_print_backtrace() at db_print_backtrace+0x18
panic() at panic+0x104
_mtx_assert() at _mtx_assert+0xb4
kmem_malloc() at kmem_malloc+0x50
page_alloc() at page_a
On Fri, 6 Dec 2002, Julian Elischer wrote:
> As part of shuting down a thread and discarding it, we want to
> throw away any floating point context there may be.
> Currently this saves out the floating point state to make the fpu
> be declared 'unused'. However we dont't need any fpu state saved.
On Fri, Dec 06, 2002 at 07:18:03PM -0800, Lars Eggert wrote:
> >I'm getting this too:
After discussing this with various people on IRC, it was determined
that this is not the place where the reversal is occurring, but since
witness doesn't have the lock order defined it has to guess, and in
this
On Thu, Dec 05, 2002 at 07:36:18PM -0600, Scot W. Hetzel wrote:
> > >>You could try the patch I've attached:
> > >>
> > >>cd /usr/src
> > >>zcat c++-wchar.diff.gz | patch
> > >>cd gnu/lib/libstdc++
> > >>make
> > >>make install
...
> Attached is the patch
This would pull files off the vendor branc
On Fri, Dec 06, 2002 at 01:29:19AM +0100, Marcin Dalecki wrote:
> Hmm... at some point in time it may perhaps just make perfect sense to
> replace
> the libstdc++ by the STLport library as the standard C++ library?
> The gnu libstdc++ is really somehoe hopeless.
No thanks. Please lobby the GCC g
On Fri, 6 Dec 2002, Kris Kennaway wrote:
> I'm getting this too:
>
> Local package initialization:lock order reversal
> 1st 0xc449ad34 filedesc structure (filedesc structure) @
>/local0/src-client/sys/kern/sys_generic.c:901
> 2nd 0xc4146780 pipe mutex (pipe mutex) @ /local0/src-client/sys/ker
On Fri, Dec 06, 2002 at 07:18:03PM -0800, Lars Eggert wrote:
> >I'm getting this too:
> >
>
> Have you gotten this before today? I haven't, and I'm wondering if I see
> it because I'm running with jhb@'s witness patch for the other LOR. Does
> your kernel have that patch, too?
>
> (Excuse me i
On Fri, 6 Dec 2002 23:26:52 +0200
Vallo Kallaste <[EMAIL PROTECTED]> wrote:
> I've built it yesterday together with a lots of other stuff. Using
> other -march values than i686 is unofficially claimed to be
> unsupported (kan@freebsd). As others I'll bet the -march=p4 is
> causing problems, i686 w
On 12/6/2002 6:22 PM, Kris Kennaway wrote:
On Fri, Dec 06, 2002 at 02:36:49PM -0800, Lars Eggert wrote:
On today's -current:
lock order reversal
1st 0xc6948234 filedesc structure (filedesc structure) @
/usr/src/sys/kern/sys_generic.c:901
2nd 0xc691f380 pipe mutex (pipe mutex) @ /usr/src/sys/ke
On Fri, Dec 06, 2002 at 02:36:49PM -0800, Lars Eggert wrote:
> On today's -current:
>
> lock order reversal
> 1st 0xc6948234 filedesc structure (filedesc structure) @
> /usr/src/sys/kern/sys_generic.c:901
> 2nd 0xc691f380 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:1239
>
> Debugger
Kirk McKusick wrote:
> I suggest that we drag Thomas-Henning von Kamptz into this
> discussion as he was one of the main authors of growfs. He
> is copied on my reply.
Thanks.
FYI, I finally fixed things by doing what Julian suggested, which
is to copy / to /usr, reboot with /usr mounted as /, ne
Adding a two minute delay before starting background fsck
sounds like a very good idea to me. Please send me your
suggested change.
Kirk McKusick
=-=-=-=-=
Date: Fri, 6 Dec 2002 10:44:45 -0800
From: Brooks Davis <[EMAIL PROTECTED]>
To: Nate Lawson <[EMAIL PROTECTED]>
Cc: Kirk McKusick <[
From: Archie Cobbs <[EMAIL PROTECTED]>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-To: <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>
Date: Fri, 6 Dec 2002 15:23:36 -0800 (PST)
CC: Archie Cobbs <[EMAIL PROTECTED]>, Nate Lawson <[EMAIL PRO
I suggest that we drag Thomas-Henning von Kamptz into this
discussion as he was one of the main authors of growfs. He
is copied on my reply.
Kirk McKusick
=-=-=-=-=-=
From: Archie Cobbs <[EMAIL PROTECTED]>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-To: <[EMAIL
As part of shuting down a thread and discarding it, we want to
throw away any floating point context there may be.
Currently this saves out the floating point state to make the fpu
be declared 'unused'. However we dont't need any fpu state saved.
Is there any way to just mark it as 'unused' witho
On Fri, 6 Dec 2002, Archie Cobbs wrote:
> David Rhodus wrote:
> > > Softupdates is enabled on /usr and /var but not /.
> >
> > Why does softupdates not get enabled on / , by default on the install?
>
> I disabled softupdates on / back when having it enabled caused disk
> full problems during 'make
Kirk McKusick wrote:
> OK, it looks like my hypothesis on having a small number of buffers
> and running out of them is the problem. I enclose below a patch which
> should check for the problem arising and help to mitigate it. I
> would appreciate you dropping it into your kernel and seeing if
> i
Julian Elischer wrote:
> I put a copy of / in /usr
> then from the fixit, I mounted /usr as / and ran growfs from there..
> the trick is to not do it while / is mounted.
/ wasn't mounted yet when I ran growfs:
> > I ran growfs after booting single user mode but before mounting
> > any disks.. per
On Fri, Dec 06, 2002 at 05:10:11PM -0500, Paul Murphy wrote:
> On Fri, 6 Dec 2002 14:29:37 -0700
> "Cliff L. Biffle" <[EMAIL PROTECTED]> wrote:
>
>
> > group know that the world and kernel seem quite stable using the athlon-tbird
> > optimizations. Not to mention smokingly fast.
>
> Is that j
There is no default CPUTYPE. If there is no CPUTYPE, and you are on
i386, -mcpu=pentiumpro gets added (top of bsd.cpu.mk).
Oops! Yes, you're right. I think I got confused by the #CPUTYPE?=i686 in
the example make.conf.
Marc
"Premature optimization is the root of all evil." -- Donald E. Knuth
T
The CPUTYPE is not i686 by default.
Stupid me... Of course, you're right.
Marc
"Premature optimization is the root of all evil." -- Donald E. Knuth
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I put a copy of / in /usr
then from the fixit, I mounted /usr as / and ran growfs from there..
the trick is to not do it while / is mounted.
On Fri, 6 Dec 2002, Archie Cobbs wrote:
> Julian Elischer wrote:
> > most systems follow / with their swap region..
> >
> > you can boot from fixit, or pi
Marc Recht wrote:
> -march=pentiumpro is not the default, -mcpu=pentiumpro is. Anyway, I
Nope, -march=pentiumpro is added, if the CPUTYPE is i686 (the default).
At least if I had read examples/etc/make.conf and bsd.cpu.mk correctly.
> doubt this is the cause of the problem. It's more likely t
On Sat, Dec 07, 2002 at 12:09:04AM +0100, Marc Recht wrote:
> >-march=pentiumpro is not the default, -mcpu=pentiumpro is. Anyway, I
> Nope, -march=pentiumpro is added, if the CPUTYPE is i686 (the default).
> At least if I had read examples/etc/make.conf and bsd.cpu.mk correctly.
The CPUTYPE is no
In the last episode (Dec 07), Marc Recht said:
> >-march=pentiumpro is not the default, -mcpu=pentiumpro is. Anyway, I
> Nope, -march=pentiumpro is added, if the CPUTYPE is i686 (the default).
> At least if I had read examples/etc/make.conf and bsd.cpu.mk correctly.
There is no default CPUTYPE.
Joe Marcus Clarke wrote:
>
> Sorry, just got power back after the ice storm. What modules do you
> have loaded. I had the following, and the nv driver started right up:
>
> Section "Module"
> Load"dbe"
> Load"dri"
> Load"extmod"
> Load"glx"
>
-march=pentiumpro is not the default, -mcpu=pentiumpro is. Anyway, I
Nope, -march=pentiumpro is added, if the CPUTYPE is i686 (the default).
At least if I had read examples/etc/make.conf and bsd.cpu.mk correctly.
doubt this is the cause of the problem. It's more likely to be a
stale dependency
Julian Elischer wrote:
> most systems follow / with their swap region..
>
> you can boot from fixit, or picoBSD floppy
> and use disklabel -e to exend the root partition
> then you can use growfs to add the new space to your root fs.
Hmm.. I tried that and it didn't seem to work.
The disklabel
On Fri, Dec 06, 2002 at 07:29:55PM +0100, Marc Recht wrote:
>
> >mozilla-devel port fails to build on current. I would imagine this is
> >already known, but I haven't seen any posts on the mailing list.
> >ign -Wno-long-long -O -pipe -march=pentium4 -pipe -DNDEBUG -DTRIMMED
> I'd bet that -march=
I got this overnight on the gohan cluster. Machine is still in DDB if
further debugging is necessary.
Kris
login: lock order reversal
1st 0xc577212c vnode interlock (vnode interlock) @
/local0/src-client/sys/kern/vfs_subr.c:939
2nd 0xc046a560 vm page queue mutex (vm page queue mutex) @
/loca
On today's -current:
lock order reversal
1st 0xc6948234 filedesc structure (filedesc structure) @
/usr/src/sys/kern/sys_generic.c:901
2nd 0xc691f380 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:1239
Debugger("witness_lock")
Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0
On Fri, Dec 06, 2002 at 11:01:00AM -0500, Anthony Volodkin wrote:
> Hey,
>
> I tried the following. Anyone know what these errors mean?
>
> divine# rpc.statd
> rpc.statd: svc_tp_create: Could not register prog 100024
> vers 1 on udp6
> rpc.statd: svc_tp_create: Could not register prog 100024
>
On Fri, 6 Dec 2002 14:29:37 -0700
"Cliff L. Biffle" <[EMAIL PROTECTED]> wrote:
> group know that the world and kernel seem quite stable using the athlon-tbird
> optimizations. Not to mention smokingly fast.
Is that just a -CURRENT thing, I can't see anything like that in -STABLE's LINT.
--
From: Archie Cobbs <[EMAIL PROTECTED]>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-To: <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>
Date: Fri, 6 Dec 2002 13:01:20 -0800 (PST)
CC: Archie Cobbs <[EMAIL PROTECTED]>, Nate Lawson <[EMAIL PRO
On Fri, 6 Dec 2002, Maxime Henrion wrote:
> Doug Barton wrote:
> > The native nvidia drivers work great in RELENG_4 with my geforce 4 mmx,
> > but in -current they hate me. I just upgraded to the latest -current and
> > I'm using XFree compiled on -current, no joy. It's always the same error:
> >
On Fri, 06 Dec 2002, Cliff L. Biffle wrote:
> On Friday 06 December 2002 01:11 pm, leafy wrote:
> > CPUTYPE=pentium4 is know to be broken. What is the known working highest
> > CPUTYPE then? pentium3 or pentium2?
>
> Well, I know this isn't quite what you were asking, but I wanted to let the
> g
It seems Cliff L. Biffle wrote:
> I mentioned earlier on the list that the ATA issues I'd been having with 4.7
> had disappeared since installing 5.0. They're still much less frequent --
> i.e. I can burn CDs now -- but I just got one of the old messages and wanted
> to submit it for your perus
I mentioned earlier on the list that the ATA issues I'd been having with 4.7
had disappeared since installing 5.0. They're still much less frequent --
i.e. I can burn CDs now -- but I just got one of the old messages and wanted
to submit it for your perusal.
cliff50 kernel: acd0: READ_BIG - ME
On Friday 06 December 2002 01:11 pm, leafy wrote:
> CPUTYPE=pentium4 is know to be broken. What is the known working highest
> CPUTYPE then? pentium3 or pentium2?
Well, I know this isn't quite what you were asking, but I wanted to let the
group know that the world and kernel seem quite stable usi
I haven't seen this one reported yet.
FreeBSD dan.emsphone.com 5.0-RC FreeBSD 5.0-RC #228: Thu Dec 5 17:28:33 CST 2002
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/DANSMP i386
lock order reversal
1st 0xc2d454b0 vnode interlock (vnode interlock) @ ../../../ufs/ffs/ffs_snapshot.c:1876
2nd
On Fri, Dec 06, 2002 at 10:19:23AM -0800, James Satterfield
<[EMAIL PROTECTED]> wrote:
> mozilla-devel port fails to build on current. I would imagine this is
> already known, but I haven't seen any posts on the mailing list.
I've built it yesterday together with a lots of other stuff. Using
othe
5.0-RC of 2002.12.05.12.00.00-UTC
Lock order reversal without panic:
lock order reversal
1st 0xc2e30708 vnode interlock (vnode interlock) @
/var/HEAD/src/sys/kern/vfs_subr.c:939
2nd 0xc033c3c0 vm page queue mutex (vm page queue mutex) @
/var/HEAD/src/sys/vm/vm_kern.c:424
Bigger problem that
Fri, Dec 06, 2002 at 13:11:51, osa (Sergey A. Osokin) wrote about "Re: cvsup weird
problem":
SAO> Any other idea? :-)
Remove src/contrib/gcc/INSTALL/ and sup checkouts directory simultaneously,
this usually fixes such errors ;)
> > > >> Delete src/contrib/gcc/INSTALL
> > > >> Cannot delete "
In the last episode (Dec 07), leafy said:
> Hi,
>
> CPUTYPE=pentium4 is know to be broken. What is the known working highest
> CPUTYPE then? pentium3 or pentium2?
p3 has been working for me for quite a while.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL P
Kirk McKusick wrote:
> by the syncer who is also blocked. Could you please run the following
> command on your system and send me the results:
>
> sysctl vfs.lodirtybuffers
> sysctl vfs.hidirtybuffers
> sysctl vfs.numdirtybuffers
>
> both before and after the lockup. If you cann
In the last episode (Dec 06), Kirk McKusick said:
> The main reason for not using soft updates on the root filesystem was
> because of the delay between removing files and having the space show
> up. The result was that world installs on the root filesystem often
> failed if the root was nearly ful
Hi,
CPUTYPE=pentium4 is know to be broken. What is the known working highest
CPUTYPE then? pentium3 or pentium2?
JY
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
The loss of files under soft updates is possible if your editor
fails to fsync the new file before unlinking the old file. The
`vi' editor always does an `fsync' after writing the new copy and
before removing the old copy. I have not checked with other editors
such as emacs to see if they properly
> Finally, one more bit of info: I have WITNESS enabled in this kernel> and
get this message during boot:
>
> /usr/src/sys/vm/uma_core.c:1330: could sleep with "dc0" locked from
/usr/src/sys/pci/if_dc.c:691
>
if_attach does a malloc with M_WAITOK. If the attach happens inside a lock
in the dr
On Fri, Dec 06, 2002 at 10:59:16AM -0800, James Satterfield wrote:
> lcms still fails build tests when compiled with CPUTYPE?=i686 and no CFLAGS
> set.
>
> James.
Worked just fine yesterday on PII-233, albeit with the previous (prerelease)
3.2.1 system compiler. (20021009) I use -march=pentium2.
Date: Fri, 6 Dec 2002 18:06:03 +0200
From: Ruslan Ermilov <[EMAIL PROTECTED]>
To: Petr Holub <[EMAIL PROTECTED]>, Matt Dillon <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: UFS1 created by 5.0 is incompatible with 4.0's?
X-ASK-Info: Whitelist match
On Fri, 2002-12-06 at 13:59, James Satterfield wrote:
> lcms still fails build tests when compiled with CPUTYPE?=i686 and no CFLAGS
> set.
It builds just fine on my P4 at work. I have nothing CFLAGS or CPUTYPE
related in /etc/make.conf. It builds with -O -pipe and
-march=pentiumpro.
Joe
--
PG
On Sat, Dec 07, 2002 at 01:00:44AM +0800, Clive Lin wrote:
> Hi,
>
> Since rescent -CURRENT is stable enough, I have the chance to find
> out remaining pcm problem. My MP box no more has double fatal fault
> and turns into random sleep. The random sleep happens after pcm having
> its own probl
From: Archie Cobbs <[EMAIL PROTECTED]>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-To: <[EMAIL PROTECTED]>
To: Nate Lawson <[EMAIL PROTECTED]>
Date: Fri, 6 Dec 2002 10:57:13 -0800 (PST)
CC: Kirk McKusick <[EMAIL PROTECTED]>,
On Fri, 6 Dec 2002, Archie Cobbs wrote:
> To copy the 'ps' debugger output, I'd have to manually copy it all,
> so here are just a few highlights:
>
> Proc State
> -
> fsck_ufs 0004000 norm[SLPQ nbufbs c036e5b0][SLP]
> fsck 0004002 norm[SLPQ wait c124dce8
On 2002-12-06 10:05, Sean LeBlanc <[EMAIL PROTECTED]> wrote:
> In any case, my installworld doesn't work, and I wonder if that's why.
> I did the following:
>
> make buildworld
> make buildkernel
> make installkernel
> rebooted,
> and did mergemaster -p
> and make installworld
>
> as defined in han
On Fri, 6 Dec 2002, Archie Cobbs wrote:
> David Rhodus wrote:
> > > Softupdates is enabled on /usr and /var but not /.
> >
> > Why does softupdates not get enabled on / , by default on the install?
>
> I disabled softupdates on / back when having it enabled caused disk
> full problems during '
On Fri, 6 Dec 2002, Archie Cobbs wrote:
> Reproduced it again just now. After pulling the plug and rebooting
> I didn't touch the box. It booted normally, started background
> fsck, and the HDD light was blinking as expected. After about 10
> seconds, rather suddenly the HDD light stopped blink
Dan Nelson wrote:
> > Why does softupdates not get enabled on / , by default on the
> > install?
>
> Softupdates updates on-disk structures in the background, and
> background fsck cannot relink unreferenced files into lost+found, so
> you run the risk of losing both the original and backup copies
It seems Andrew Gallatin wrote:
>
> Kris Kennaway writes:
> > I got this on one of the gohan machines overnight. These machines
> > have failing disks -- I get a lot of hard read errors, but the
> > INVARIANTS panic could better be replaced by something else.
> >
> > I reported another inst
Nate Lawson wrote:
> > Does the background fsck process continue to run, or does the whole
> > system come to a halt? If the fsck process continues to run, what
> > happens when it eventually finishes? Is the system still dead, or
> > does it come back to life? If the system does not come back to
David Rhodus wrote:
> > Softupdates is enabled on /usr and /var but not /.
>
> Why does softupdates not get enabled on / , by default on the install?
I disabled softupdates on / back when having it enabled caused disk
full problems during 'make installworld,' and never re-enabled it.
FYI at this
In the last episode (Dec 06), David Rhodus said:
> Why does softupdates not get enabled on / , by default on the
> install?
Softupdates updates on-disk structures in the background, and
background fsck cannot relink unreferenced files into lost+found, so
you run the risk of losing both the origina
In message <[EMAIL PROTECTED]>, Nate Lawson wri
tes:
>On Fri, 6 Dec 2002 [EMAIL PROTECTED] wrote:
>> >> [...]
>> >> I've discussed this issue with Poul-Henning Kamp. You need fsck
>> >> from at least 4.7.
>> >>
>> >Is this handled by fsck/setup.c,v 1.17.2.4 commit?
>>
>> Yes, this looks like the
lcms still fails build tests when compiled with CPUTYPE?=i686 and no CFLAGS
set.
James.
- Original Message -
From: "Joe Marcus Clarke" <[EMAIL PROTECTED]>
To: "James Satterfield" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, December 06, 2002 10:47 AM
Subject: Re: /usr/ports/gr
On Fri, Dec 06, 2002 at 01:52:11PM -0500, David Rhodus wrote:
>
> On Friday, December 6, 2002, at 01:39 PM, Archie Cobbs wrote:
>
> >Kirk McKusick wrote:
> >>Does the background fsck process continue to run, or does the whole
> >>system come to a halt? If the fsck process continues to run, what
>
On Friday, December 6, 2002, at 01:39 PM, Archie Cobbs wrote:
Kirk McKusick wrote:
Does the background fsck process continue to run, or does the whole
system come to a halt? If the fsck process continues to run, what
happens when it eventually finishes? Is the system still dead, or
does it come
On Fri, 2002-12-06 at 13:41, James Satterfield wrote:
> The lcms port fails it's build time tests on current with a P4. I believe
> this builds on non-P4 systems running current.
Same thing as your mozilla-devel issue. Like Marc mentioned, don't use
-march=pentium4. I think I recall hearing it's
+---[ James Satterfield ]--
| The lcms port fails it's build time tests on current with a P4. I believe
| this builds on non-P4 systems running current.
Builds fine on my athlon under current.
--
Totally Holistic Enterprises Internet| | Andrew Milton
Kirk McKusick wrote:
> Does the background fsck process continue to run, or does the whole
> system come to a halt? If the fsck process continues to run, what
> happens when it eventually finishes? Is the system still dead, or
> does it come back to life? If the system does not come back to life
On Fri, Dec 06, 2002 at 10:27:10AM -0800, Nate Lawson wrote:
> On Thu, 5 Dec 2002, Kirk McKusick wrote:
> > Does the background fsck process continue to run, or does the whole
> > system come to a halt? If the fsck process continues to run, what
> > happens when it eventually finishes? Is the syst
The lcms port fails it's build time tests on current with a P4. I believe
this builds on non-P4 systems running current.
building static lcms library
building shared library liblcms.so.1
ranlib liblcms.a
cd /usr/ports/graphics/lcms/work/lcms-1.09/src/../testbed && /usr/bin/env
CFLAGS="-O -pip
:..
:>=20
:> I've discussed this issue with Poul-Henning Kamp. You need fsck
:> from at least 4.7.
:>=20
:...
(Ruslan Ermilov writes):
:Is this handled by fsck/setup.c,v 1.17.2.4 commit?
Yes, I believe so.
-Matt
Matthew Dillon
On Fri, 6 Dec 2002 [EMAIL PROTECTED] wrote:
> >> [...]
> >> I've discussed this issue with Poul-Henning Kamp. You need fsck
> >> from at least 4.7.
> >>
> >Is this handled by fsck/setup.c,v 1.17.2.4 commit?
>
> Yes, this looks like the correct commit.
>
> --
> Poul-Henning Kamp | UNIX sin
On Fri, 6 Dec 2002, Marc Recht wrote:
> > mozilla-devel port fails to build on current. I would imagine this is
> > already known, but I haven't seen any posts on the mailing list.
> > ign -Wno-long-long -O -pipe -march=pentium4 -pipe -DNDEBUG -DTRIMMED
> I'd bet that -march=pentium4 is your probl
mozilla-devel port fails to build on current. I would imagine this is
already known, but I haven't seen any posts on the mailing list.
ign -Wno-long-long -O -pipe -march=pentium4 -pipe -DNDEBUG -DTRIMMED
I'd bet that -march=pentium4 is your problem. Try with -march=pentiumpro
(the default).
M
On Thu, 5 Dec 2002, Kirk McKusick wrote:
> Does the background fsck process continue to run, or does the whole
> system come to a halt? If the fsck process continues to run, what
> happens when it eventually finishes? Is the system still dead, or
> does it come back to life? If the system does no
Kris Kennaway writes:
> I got this on one of the gohan machines overnight. These machines
> have failing disks -- I get a lot of hard read errors, but the
> INVARIANTS panic could better be replaced by something else.
>
> I reported another instance of this to sos a few weeks ago but didn't
mozilla-devel port fails to build on current. I would imagine this is
already known, but I haven't seen any posts on the mailing list.
jsdtoa.c
cc -o
jsdtoa.o -c -DOSTYPE=\"FreeBSD5\" -DOSARCH=\"FreeBSD\" -DOJI -DEXPORT_JS_A
PI -DJS_USE_SAFE_ARENA -I../../dist/include/js -I../../dist/include -
I got this on one of the gohan machines overnight. These machines
have failing disks -- I get a lot of hard read errors, but the
INVARIANTS panic could better be replaced by something else.
I reported another instance of this to sos a few weeks ago but didn't
hear a reply.
Kris
ad0: hard error
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 5 Dec 2002, Josef Karthauser wrote:
>
> If you're an ohci user can you please test this patch out for inclusion
> in 5.0. I need to know that it doesn't break anything - the reports are
> that it fixes broken ohci :).
I've been running it since you posted the patch a couple of days ago.
Hi,
Since rescent -CURRENT is stable enough, I have the chance to find
out remaining pcm problem. My MP box no more has double fatal fault
and turns into random sleep. The random sleep happens after pcm having
its own problem.
uname -av is
FreeBSD cartier.home 5.0-CURRENT FreeBSD 5.0-CURR
Hi all,
If you're an ohci user can you please test this patch out for inclusion
in 5.0. I need to know that it doesn't break anything - the reports are
that it fixes broken ohci :).
Joe
--
Josef Karthauser ([EMAIL PROTECTED]) http://www.josef-k.net/
FreeBSD (cvs meister, admin and
In message <006501c29d44$33a8e980$2603fb93@kloboucek>, "Petr Holub" writes:
>Hi Poul,
>
>there's discussion in the -current list which we
>had before a while. I think answer to this is
>'yes' but I'm not 100% sure so I wanted to check
>it with you.
>
>Thanks very much,
>Petr
>
>> [...]
>> I've dis
On Fri, Dec 06, 2002 at 01:59:11PM +0100, Petr Holub wrote:
> Hi,
>
> > While testing the 4.0 -> 5.0 upgrade path, I've created (under
> > 5.0) a UFS1 partition and installed 4.0 onto it. After booting
> > the 4.0 from it, kernel complained about ``numdirs is zero, try
> > using an alternate supe
FWIW.
i have a similar setup except that the fxp is replaced by rl. All i did was
to change ifconfig_ed1 to ifconfig_ed0 in rc.conf.
for some strange reason, when i installed(sysinstall), the ed card was
detected as ed1 and not as ed0 but on subsequent boots (after i changed
rc.co
Hey,
I tried the following. Anyone know what these errors mean?
divine# rpc.statd
rpc.statd: svc_tp_create: Could not register prog 100024
vers 1 on udp6
rpc.statd: svc_tp_create: Could not register prog 100024
vers 1 on udpr
rpc.statd: cannot create udp service
divine# rpc.lockd
rpc.lockd: u
Out of da blue Kris Kennaway aka ([EMAIL PROTECTED]) said:
> Kernels with the following configuration do not link:
>
> # ATA and ATAPI devices
> device ata
> device atapicd # ATAPI CDROM drives
>
> linking kernel.debug
> ata-all.o: In function `ata_boot_attach':
> ata-al
Hi
Is it possible to build OOo on -current?
gcc core dumps periodically when i compile big things ...
Hardware is ok ... (on 4.7 stable no problems).
P.S. please CC me, i'm not subscribed
P.P.S. sorry my bad english
To Unsubscribe: send m
On Wed, 2002-12-04 at 23:25, Rob wrote:
> Joe Marcus Clarke wrote:
> >
> > On Wed, 2002-12-04 at 22:46, Rob wrote:
> > > Rob wrote:
> > > >
> > > > Joe Marcus Clarke wrote:
> > > > >
> > > > > On Wed, 2002-12-04 at 17:04, Rob wrote:
> > > > > > Is there any solution to the above combo other than j
Maxime Henrion wrote:
>
> Doug Barton wrote:
> > The native nvidia drivers work great in RELENG_4 with my geforce 4 mmx,
> > but in -current they hate me. I just upgraded to the latest -current and
> > I'm using XFree compiled on -current, no joy. It's always the same error:
> >
> > panic: bremfre
Doug Barton wrote:
> The native nvidia drivers work great in RELENG_4 with my geforce 4 mmx,
> but in -current they hate me. I just upgraded to the latest -current and
> I'm using XFree compiled on -current, no joy. It's always the same error:
>
> panic: bremfree: bp 0xc7751bb8 not locked
This is
Hi,
> While testing the 4.0 -> 5.0 upgrade path, I've created (under
> 5.0) a UFS1 partition and installed 4.0 onto it. After booting
> the 4.0 from it, kernel complained about ``numdirs is zero, try
> using an alternate superblock'' for / partition -- I've tried
> what it suggests (by fsck -b 32
On Fri, 6 Dec 2002, Doug Barton wrote:
> The native nvidia drivers work great in RELENG_4 with my geforce 4 mmx,
> but in -current they hate me. I just upgraded to the latest -current and
> I'm using XFree compiled on -current, no joy. It's always the same error:
>
> panic: bremfree: bp 0xc7751bb8
The native nvidia drivers work great in RELENG_4 with my geforce 4 mmx,
but in -current they hate me. I just upgraded to the latest -current and
I'm using XFree compiled on -current, no joy. It's always the same error:
panic: bremfree: bp 0xc7751bb8 not locked
I've tried both with and without agp
On Thu, Dec 05, 2002 at 05:22:50PM +0200, Giorgos Keramidas wrote:
> On 2002-12-05 21:33, leafy <[EMAIL PROTECTED]> wrote:
> > On Thu, Dec 05, 2002 at 04:32:01PM +0300, Sergey A. Osokin wrote:
> > > > Delete src/contrib/gcc/INSTALL
> > > > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory no
Hi
The new binutils and gcc3.2.1 release hit the tree recently, nice to
see everything is moving forward. I would like to tell the importers
that XFree86-4, KDE3 and GNOME2 built without a hitch for me. Here's
my list without GNOME2, latter was built only for testing purposes
and deleted promptly
It seems Kris Kennaway wrote:
> ata-all.o: In function `ata_boot_attach':
> ata-all.o(.text+0x1590): undefined reference to `ata_raid_attach'
> ata-all.o(.text+0x1594): undefined reference to `ata_raid_attach'
Yes, I've seen it there is two other issues I'd like to fix also,
I'll ask re@ for appr
$FreeBSD: src/UPDATING,v 1.228 2002/10/30 20:11:07 imp Exp $
"To upgrade from 4.x-stable to current" suggests:
cd src/sys/boot ; make install [6]
This does not work. You need to:
cd src/sys/boot ; make all install [6]
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
1 - 100 of 103 matches
Mail list logo
