At 11 Oct 2000 18:43:14 GMT, John Baldwin <[EMAIL PROTECTED]> wrote: > I don't know. Can you try to narrow down the date by cvsupping or > cvs updating with date tags to see when it started slowing down? I've checked with -D '2000-10-03 00:00:00 GMT' and -D '2000-10-04 12:00:00 GMT'. With previous kernel, "time find /usr/obj" returns 65 seconds, but with later kernel, it returns 547 seconds (/usr/obj is NFS mounted from localhost). Top command shows many processes locked with MUTEX status. It seems this is caused by jasone's commit at 3rd Oct... -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. <[EMAIL PROTECTED]> // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- -current grinds exceeding slow Bob Bishop
- ed0: warning - receiver ring buffer overrun Bob Bishop
- Re: ed0: warning - receiver ring buffer over... Wilko Bulte
- Re: ed0: warning - receiver ring buffer ... Bob Bishop
- Re: ed0: warning - receiver ring buffer ... Bob Bishop
- Re: ed0: warning - receiver ring buf... Jun Kuriyama
- RE: -current grinds exceeding slow Daniel O'Connor
- RE: -current grinds exceeding slow John Baldwin
- Re: -current grinds exceeding slow Jun Kuriyama
- Re: -current grinds exceeding slow Jason Evans
- Re: -current grinds exceeding slow Jun Kuriyama
- RE: -current grinds exceeding slow Bob Bishop
- RE: -current grinds exceeding slow John Baldwin
- RE: -current grinds exceeding slow Bob Bishop
- RE: -current grinds exceeding s... Daniel O'Connor
- RE: -current grinds exceedi... Kenneth Wayne Culver