I have a fairly recent CURRENT:
FreeBSD kapran.bitmcnit.bryansk.su 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Dec 30
12:41:53 MSK 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/KAPRAN i386
And what I noticed is a massive slowdown when running make(1). It seems
that I am going to finish a new `bu
In message <[EMAIL PROTECTED]> Sean Kelly writes:
: I did not have this behavior in -STABLE, but now I do since I upgraded
: to -CURRENT.
-current's interrupt latency is horrible these days, which seems to
manifest itself in problem with the sound driver. I have a -current
laptop and get all kin
What is the current status of the pcm driver? I ask this because I
am able to hear sticking and slowdowns in sound when I move my PS/2
mouse.
pcm0: at io 0xe800 irq 11 (4p/3r channels duplex)
I did not have this behavior in -STABLE, but now I do since I upgraded
to -CURRENT.
FreeB
On Sat, 20 Jan 2001, Boris Popov wrote:
> On Fri, 19 Jan 2001, Rogier Mulhuijzen wrote:
>
> > During normal operation on my NTFS partition I got no messages, so I took a
> > bold step and added 'ip->i_devvp = ntmp->ntm_devvp;' just before the VREF call.
>
> You're absolutely right here.
On Fri, 19 Jan 2001, Rogier Mulhuijzen wrote:
> During normal operation on my NTFS partition I got no messages, so I took a
> bold step and added 'ip->i_devvp = ntmp->ntm_devvp;' just before the VREF call.
You're absolutely right here. This line definitely should be
presented in the cod
lopanic: mutex_enter(sio:1, MTX_SPIN) out of order @ ../../isa/sio.c:2585 already
holding sched lock:2
cpuid = 0; lapic.id =
Debugger("panic")
d
CPU0 stopping CPUs: 0x0002... stopped.
Stopped at Debugger+0x45: pushl %ebx
db> trace
Debugger(c0231e61) at Debugger+0x45
panic(c0
[ Followups to -arch only please ]
I've got some changes to libc and libc_r that I'd like reviewed.
These changes eliminate the _THREAD_SAFE macro and allow a libc
and libc_r that can be linked together via -lc_r. This also means
that -pthread and -D_THREAD_SAFE can be deprecated. Note that
lib
"Crist J. Clark" <[EMAIL PROTECTED]> writes:
> On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote:
> > It should also log a message if the hostname changes.
> Should that be a responsibility of syslogd(8) or hostname(1)?
I meant syslogd(8), but putting it in hostname(1) might mak
If I remove the old /usr/libexec/cpp with a newer cpp0 installed,
'make world' fails with the following:
--
>>> stage 4: populating /usr/obj/usr/src/i386/usr/include
--
cd /usr/
On 19-Jan-01 Bruce Evans wrote:
> On Fri, 19 Jan 2001, John Baldwin wrote:
>
>> rummage together a vinum stripe to build on or some such. However, after
>> thinking some more, even in a preemptive kernel, Giant will protect against
>> the
>> *strategy() race you brought up, because we won't get
On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote:
> [EMAIL PROTECTED] writes:
> > I propose that syslogd(8) should reload the hostname with a
> > SIGHUP. I cannot think of any reason that one should not update the
> > hostname, but as I pointed out, there are reasons why one
On Fri, 19 Jan 2001, John Baldwin wrote:
> rummage together a vinum stripe to build on or some such. However, after
> thinking some more, even in a preemptive kernel, Giant will protect against the
> *strategy() race you brought up, because we won't get a context switch in
> kernel mode that rel
Just out of curiousity, has anyone documented how much of a performance
hit there is with the i386 code enabled in the kernel?
Regards,
Glen Gross
On Thu, 18 Jan 2001, Mike Smith wrote:
> > > That's one of the big reasons that we're 4.x based right now rather
> > > than 3.x based, despite 4
a quick look at kldstat output pinpointed the ??'s in my stacktrace(see
previous posts) to ntfs.ko. Compiled NTFS into my kernel and reproduced the
crash.
Taking a look at the trace now:
#11 0xc01c0c97 in vref (vp=0x0) at machine/atomic.h:332
#12 0xc0239592 in ntfs_vgetex (mp=0xc0f7dc00, ino=4
Hello,
The current default /etc/auth.conf is as follows:
--
#
# $FreeBSD: src/etc/auth.conf,v 1.5 2000/12/28 10:32:00 peter Exp $
#
# This file contains information on what types of authentication to use.
# It is just the beginnings of a greater scheme.
# crypt_default = md5 des
#
It seems John Baldwin wrote:
>
> Can you post a dmesg of your box?
Sure, attached the dmesg from the system that is worst affected:
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of Cal
[EMAIL PROTECTED] writes:
> I propose that syslogd(8) should reload the hostname with a
> SIGHUP. I cannot think of any reason that one should not update the
> hostname, but as I pointed out, there are reasons why one would want
> that behavior.
It should also log a message if the hostname
On 19-Jan-01 Maxim Sobolev wrote:
> John Baldwin wrote:
>
>> On 19-Jan-01 Chris Knight wrote:
>> > Howdy,
>> >
>> > Since the sysinstall move, make release on FreeBSD-stable (as of 3 hrs
>> > ago)
>> > breaks when building sysinstall. The output is:
>>
>> rtermcap needs to be a build-tool in wor
It seems Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, John Baldwin writes:
> >
> >This is _not_ true. My quad xeon test box runs a pure source tree, and has not
> >had a single problem building many worlds and releases since the fix to
> >atomic_store_rel_ptr().
>
> How many disks
John Baldwin wrote:
> On 19-Jan-01 Chris Knight wrote:
> > Howdy,
> >
> > Since the sysinstall move, make release on FreeBSD-stable (as of 3 hrs ago)
> > breaks when building sysinstall. The output is:
>
> rtermcap needs to be a build-tool in world. The 4.x upgrade path is b0rked
> too. I think
In message <[EMAIL PROTECTED]>, John Baldwin writes:
>>
>> How many disks are active when you build world on that box ?
>
>Just one. [...]
>Details like this would be helpful though.
They have never been secret, and I voiced this issue early on.
> However, after
>thinking some more, even in a pr
On 19-Jan-01 Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, John Baldwin writes:
>>
>>This is _not_ true. My quad xeon test box runs a pure source tree, and has
>>not
>>had a single problem building many worlds and releases since the fix to
>>atomic_store_rel_ptr().
>
> How many di
In message <[EMAIL PROTECTED]>, John Baldwin writes:
>
>This is _not_ true. My quad xeon test box runs a pure source tree, and has not
>had a single problem building many worlds and releases since the fix to
>atomic_store_rel_ptr().
How many disks are active when you build world on that box ?
On 19-Jan-01 Soren Schmidt wrote:
> It seems Peter Wemm wrote:
>> Soren Schmidt wrote:
>> > It seems Peter Wemm wrote:
>> > >
>> > > Soren, can you retest a buildworld with the currently committed kernel
>> > > with no other changes? Let us see if the forward_signal() stuff is the
>> > > culpri
On 19-Jan-01 Chris Knight wrote:
> Howdy,
>
> Since the sysinstall move, make release on FreeBSD-stable (as of 3 hrs ago)
> breaks when building sysinstall. The output is:
rtermcap needs to be a build-tool in world. The 4.x upgrade path is b0rked
too. I think that file2c also needs to become
Soren Schmidt wrote:
> It seems Peter Wemm wrote:
> > This is bad news.. This means we have races somewhere, or some other badne
ss.
>
> That is what I've been harping about for months...
>
> What strikes me here as a very serious problem is that the SMPng developers
> has told me over and
26 matches
Mail list logo
