On Thu, 8 Jul 1999 11:00:24 +0100 (BST),
Doug Rabson <[EMAIL PROTECTED]> said:
>> There is one problem in this method. acquire_timer0() is only implemented
>> for i386. We would need to write something equivalent for alpha...
dfr> The timer hardware on the alpha is essentially the same but the
> todays current breaks in build of libgcc
Since libgcc/Makefile hasn't been touched since April, me thinks
something else is going on in your environment.
> ===> gnu/lib/libgcc
> c++ -O2 -mpentium -fpcc-struct-return -ffast-math -fno-strength-reduce
...
What does adding "-v" to your CLFAGS in
>upon booting -current (from 7/6/99) i noticed that the kernel didn't report
>that the work around was enabled... so i began searching through the code
>looking for where the workaround actually was... i found it in
>src/sys/i386/isa/wd.c (line 282), but the wdc_pci() function only sets
>static in
>From the keyboard of Boris Staeblow:
> >> Why is rc.conf readable by world?!
> >
> >Why not?
>
> What about that:
>
> spppconfig_isp0="authproto=chap myauthname=foo myauthsecret='top secret'
> hisauthname=some-gw hisauthsecret='another secret'"
I'm not quite satisfied with the way the passwor
On Thu, Jul 08, 1999 at 10:18:35AM -0300, The Hermit Hacker wrote:
> The newest INN does not have this option, MMAP() is a requirement for
> it...
Sorry, I didn't know that. Too bad, then.
> ah, okay, so you are saying that FreeBSD shouldn't be demonstrated using
> software that taxes/tweaks bug
:At that time, Matt pop'd up and stated that he knew of *at least* 6 MMAP()
:related race conditions that he was hoping to be able to get fixed "within
:a week"...that would have been two weeks ago.
I think I was talking about mmap w/ NFS.
Under FreeBSD-current I know of two problems ( t
>dfr> If I understand this correctly, you are suggesting that we program timer0
>dfr> so that we only take interrupts when a finetimer is due to fire? If so,
>dfr> then it sounds very good. The idea of taking 6000+ interrupts/sec made me
>dfr> uneasy, even though most would return without doing an
Somebody should study the abilities of the on-cpu APIC for this
for pentium ff. machines.
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>>dfr> If I understand this correctly, you are suggesting that we program timer0
>>dfr> so that we only take interrupts when a finetimer is due to fire?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Just to head off complaints - we accidently made an incomplete commit
last night updating some vfs/bio stuff. I have an email in to Kirk
with the pieces that we forgot. CURRENT will not build (or if it does,
it will crunch) at the moment.
Ok, I've traced the code down and I think that there is a good chance
that the OBJ_DEAD fix that Alan described may solve the problem.
What I think is happening is that a process context is holding a PIP
count on the object, then deallocating the object and creating an
interlo
On Thu, 8 Jul 1999, The Hermit Hacker wrote:
> right now, at work, I'm enjoying a 4 way battle. Me, fighting to bring in
> FreeBSD to replace some of our Solaris boxes. A friend of mine, fighting
> to bring in Linux to replace some of our Solaris boxes. My boss fighting
> against both of us to
:> it will crunch) at the moment.
:>
:> -Matt
:
:Is there anything I can do?
:
:Cheers,
:-Peter
(CC'ing to current)
Kirk committed the fix -- The sense of a KASSERT() had gotten reversed
accidently.
Everything is hunky dory - except for
On Thu, 8 Jul 1999, Bruce Evans wrote:
> Rev.1.31 of ide_pci.c put the call in a dubious place (after some early
> return statements) in ide_pci_attach(). Try putting it at the beginning
> of the function (after `type' is initialized).
hmmm if i had looked the code above that switch()... i
I wish to make one thing perfectly clear here, or, rather, a couple of
things. None of this thread was started as a 'slam session' against
*anyone* out there...
To those that have responded privately that "they are experiencing the
problem too", without a better way of saying it...that helps ab
For some video cards (to wit, the voodoo stuff), the MTRRs should be set up as
follows
write-combining
+--+
+---+
uncacheable
i.e. the two regions have the same starting area, but the small chunk for the
registers should be un
On Thu, 8 Jul 1999, David O'Brien wrote:
> > todays current breaks in build of libgcc
>
> Since libgcc/Makefile hasn't been touched since April, me thinks
> something else is going on in your environment.
>
> > ===> gnu/lib/libgcc
> > c++ -O2 -mpentium -fpcc-struct-return -ffast-math -fno-stre
I've been seeing an interesting problem when doing a make installworld on a
486 with 16MB of memory. Immediately after installing libc.so.3, it will hang.
DDB gives a backtrace to a mmap related call (sorry, the box is at home at the
memoment and this email was prompted by something on freebsd-
Stephen Hocking-Senior Programmer PGS Tensor Perth once wrote:
> I've been seeing an interesting problem when doing a make installworld
> on a 486 with 16MB of memory. Immediately after installing libc.so.3,
> it will hang.
Happened to me here today on Pentium 90 with 64Mb of RAM. It wa
19 matches
Mail list logo
