On Mon, 17 Jan 2000, Bruce Evans wrote:
> > Using the magic of :%s:p_stats->p_\([usi]\)\(u[^a-zA-Z_0-9]\):p_\1\2:g,
> > and just using vi to edit the headers too :), I submit the following to
> > you for review. I'll be testing it in its entirety tomorrow, but I'm
> > already reasonably confiden
> Using the magic of :%s:p_stats->p_\([usi]\)\(u[^a-zA-Z_0-9]\):p_\1\2:g,
> and just using vi to edit the headers too :), I submit the following to
> you for review. I'll be testing it in its entirety tomorrow, but I'm
> already reasonably confident this is correct. What do you think?
The subst
On Wed, 12 Jan 2000, Bruce Evans wrote:
>
> Please do the work, but send it to me for review.
>
> I didn't have a fix for this particular problem until after seeing
> your first mail about it. It didn't make sense for P_INMEM to be so
> apparently broken without it causing problems until recen
On Tue, 11 Jan 2000, Brian Fundakowski Feldman wrote:
> On Tue, 11 Jan 2000, Bruce Evans wrote:
> > ...
> > Fix: move the new monotonicity fields from struct pstats to struct
> > proc. I only put them in struct pstats because they logically go with
> > some fields in struct rusage.
> > ...
>
>
On Tue, 11 Jan 2000, Bruce Evans wrote:
> I broke calcru() with the monotonicity fixes (kern_resource.c rev.1.45
> (1999/03/13). Accessing p->p_stats at interrupt time is only valid if
> p == curproc.
>
> Fix: move the new monotonicity fields from struct pstats to struct
> proc. I only put the
On Tue, 11 Jan 2000, Brian Fundakowski Feldman wrote:
> On Mon, 10 Jan 2000, Stephen McKay wrote:
>
> > The problem is that calcru() thinks that P_INMEM means that the proc
> > structure is fully and accurately populated. But P_INMEM is one of the
> > first flags set.
> >
> > So, calcru() and p
>On Mon, 10 Jan 2000, Stephen McKay wrote:
>
>> The problem is that calcru() thinks that P_INMEM means that the proc
>> structure is fully and accurately populated. But P_INMEM is one of the
>> first flags set.
>>
>> So, calcru() and possibly some other places, are looking at a struct proc
>> bef
On Mon, 10 Jan 2000, Stephen McKay wrote:
> The problem is that calcru() thinks that P_INMEM means that the proc
> structure is fully and accurately populated. But P_INMEM is one of the
> first flags set.
>
> So, calcru() and possibly some other places, are looking at a struct proc
> before it's
I'm currently giving 4.0 a thrashing in the best way I know. I run way too
much stuff and let it page madly all day. Here's how I killed it:
1) pick a 32MB box
2) make -j20 buildworld
3) lean on ^T and let autorepeat go for it
Soon it dies in calcru() called from ttyinfo(). The stack trace sh
