>[/usr/src/usr.bin/top/machine.c:char *format_next_process(handle, get_userid)]
>
> if (smpmode && PP(pp, p_oncpu) == 0xff)
> ^^
> this should be '!='.
Oops. Thanks for the fix.
Bruce
To Unsubscribe:
Hi!
I cvsuped, made and installed the world at 04:00 7th May 1999 (JST) on
my SMP box to find that the STATE in top(1) displayed "CPU255" for some
processes. I have only 2 CPUs...
[/usr/src/usr.bin/top/machine.c:char *format_next_process(handle, get_userid)]
if (smpmode && PP(pp, p
In article <4.1.19990304100812.00cb0...@aire.open.ac.uk>,
Mike Zanker wrote:
> At 10:03 04/03/99 , Sheldon Hearn wrote:
>
> >I'm living in the past again. Fixed in rev1.225 of files.i386 . Update
> >your src/sys/i386/conf, since LINT has been updated as well.
>
> Hmm, I just did but via cvsup.u
In article <199903051706.taa00...@hangdog.is.co.za>,
Geoff Rehmet wrote:
>
> I've just decided to keep my list of bonnie tests running. I haven't
> pulled the latest changes yet, as CVSUP is basically a day behind
> from cvsup.za.freebsd.org.
Are you sure? The CVSup server logs on freefall sh
Ah,
bzero(c, sizeof *c);
I suppose.
Brian Feldman wrote:
>
> I make a habit of checking out any interesting kernel changes in full, and one
> thing I found in the recent diff by Mr. Wollman for kern_timeout.c is:
>
> +void
> +callout_init(c)
> + struct callout *c;
> +{
> +
I just got a new set of PARSE patches from Frank Kardel, and I'm waiting
for Dave Mills to give me the go-ahead to commit them. Dave is chasing
some possible bugs and wanted a stable codebase for a while.
H
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current"
< said:
> Understood, but the point being that Garrett is an experienced
> programmer, and made this mistake. The latter version avoids any
> possibilities of said mistake.
...and instead opens up the possibility of the same bug if the type of
the structure is ever changed.
I will fix this (cur
auth 99e0b1d8 unsubscribe freebsd-current hellr...@usa.net
This looks like a reception problem. You must be pretty far out in
the reception area of DCF77 (just like me), and will probably find
that whenever a sunrise or sunset is in the area reception sux.
Try to see if it does better in daylight...
I don't know the state of the DCF77/parse stuff in v4
According to Poul-Henning Kamp:
> It looks synchronized to me, it just looks like it hasn't swung in yet ?
The two outputs I sent were with 4.0.90f. When I run 4.0.92c, ntpd is not
able to get any accurate data from the device whereas 4.0.90f does.
I get lots of these in /var/log/messages and it
I have the same problem on 4.0-current SMP of Mon Feb 15 03:34:29 PST
1999.
tomdean
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Fri, 5 Mar 1999, Brian Feldman wrote:
> It seems that actually, not through my own fault, the fd driver is broken. I
> noticed this weeks ago but thought it a fluke since I only had the problem on
> one computer. However, on the school FreeBSD box, I also notice the same
> problem!
The point
I just built a new 4.0-CURRENT kernel yesterday and noticed that there
seem to be more warnings generated than used to be. I rebuilt it today
with the latest sources as of 3am March 6, built a new kernel from
scratch (after deleting the entire old build dir), removed the "cc"
lines, and got t
On Sat, 6 Mar 1999, Nate Williams wrote:
> > > > > I make a habit of checking out any interesting kernel changes in
> > > > > full, and one
> > > > > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is:
> > > > >
> > > > > +void
> > > > > +callout_init(c)
> > > > > + stru
Nate Williams wrote:
>> > +void
>> > +callout_init(c)
>> > + struct callout *c;
>> > +{
>> > + bzero(c, sizeof c);
>> > }
>> >
>> > That doesn't look correct, does it?
>>
>> Agreed. I think it should be "sizeof *c".
>
> Ahh, I see. I think it should say
>
>bzero(c, sizeo
> > > > I make a habit of checking out any interesting kernel changes in full,
> > > > and one
> > > > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is:
> > > >
> > > > +void
> > > > +callout_init(c)
> > > > + struct callout *c;
> > > > +{
> > > > + bzero(c, size
On Sat, 6 Mar 1999, Nate Williams wrote:
> > > I make a habit of checking out any interesting kernel changes in full,
> > > and one
> > > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is:
> > >
> > > +void
> > > +callout_init(c)
> > > + struct callout *c;
> > > +{
> >
In message <19990306164238.a29...@keltia.freenix.fr>, Ollivier Robert writes:
>According to Poul-Henning Kamp:
>> Please send comments and observations, both positive AND negative.
>
>I can't get my DCF77 device to synchronize with both the kernel diff
>applied and 4.0.92c. With the older 4.0.90f I
According to Poul-Henning Kamp:
> Please send comments and observations, both positive AND negative.
I can't get my DCF77 device to synchronize with both the kernel diff
applied and 4.0.92c. With the older 4.0.90f I'm able to sync.
remote refid st t when poll reach delay o
> > I make a habit of checking out any interesting kernel changes in full, and
> > one
> > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is:
> >
> > +void
> > +callout_init(c)
> > + struct callout *c;
> > +{
> > + bzero(c, sizeof c);
> > }
> >
> > That doesn't
> I make a habit of checking out any interesting kernel changes in full, and one
> thing I found in the recent diff by Mr. Wollman for kern_timeout.c is:
>
> +void
> +callout_init(c)
> + struct callout *c;
> +{
> + bzero(c, sizeof c);
> }
>
> That doesn't look correct, does it?
Car
I installed 4.0-19990304-SNAP/src/sys and cvsup-ed to current . I
found that the last changes of current are not included into
snap/src/src (till 03/04/99). Is that o.k.?
Val
_
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.
In article ,
Brian Feldman wrote:
> I make a habit of checking out any interesting kernel changes in full, and one
> thing I found in the recent diff by Mr. Wollman for kern_timeout.c is:
>
> +void
> +callout_init(c)
> + struct callout *c;
> +{
> + bzero(c, sizeof c);
> }
>
> That
At 10:59 AM 3/6/99 -0500, Brian Feldman wrote:
>I make a habit of checking out any interesting kernel changes in full, and
one
>thing I found in the recent diff by Mr. Wollman for kern_timeout.c is:
>
>+void
>+callout_init(c)
>+ struct callout *c;
>+{
>+ bzero(c, sizeof c);
> }
>
>That
I make a habit of checking out any interesting kernel changes in full, and one
thing I found in the recent diff by Mr. Wollman for kern_timeout.c is:
+void
+callout_init(c)
+ struct callout *c;
+{
+ bzero(c, sizeof c);
}
That doesn't look correct, does it?
Brian Feldman
It seems Steve Price wrote:
[debug output omitted]
I think I know what is failing now, I just have to find a fix for it..
-Søren
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
> For quite some time now Netscape 4.5 has been very unstable on my
> -current system. I've cvsup'ed and made world many times in the hope the
> problem would go away.
>
> Today I decided to ktrace it, and see where it would stop.
>
> Of course it now refuses to crash. Even on java stuff that wou
Hi,
For quite some time now Netscape 4.5 has been very unstable on my
-current system. I've cvsup'ed and made world many times in the hope the
problem would go away.
Today I decided to ktrace it, and see where it would stop.
Of course it now refuses to crash. Even on java stuff that would crash
On Fri, Mar 05, 1999 at 04:40:33AM -0800, David O'Brien wrote:
> > === make depend error ===
> > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
> > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -
29 matches
Mail list logo
