RE: -current grinds exceeding slow
I use 0.85, I had some wierd problems with it in -CURRENT. I've moved down to 4.1.1-STABLE till some of this stuff in -CURRENT cools down. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Fri, 13 Oct 2000, Daniel O'Connor wrote: > > On 12-Oct-00 Bob Bishop wrote: > > >It's not. My current box that is having problems has an fxp0 card. > > >BTW, what speed is your processor? I'm curious because the PPro 200 > > >I have here is having problems, but the PIII-700 isn't very affected. > > Try removing SMP_DEBUG from your config (see > > Message-ID: <[EMAIL PROTECTED]> > > from Jason Evans on this thread). > > That worked for me... > > Does anyone here run the really new version of Licq? > > I know it sounds dumb, but it seems that if I run it and do some reasonably > heavy disk, processes start getting stuck in things like vnlock, inode and > ffsvgt... > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -current grinds exceeding slow
On 12-Oct-00 Bob Bishop wrote: > >It's not. My current box that is having problems has an fxp0 card. > >BTW, what speed is your processor? I'm curious because the PPro 200 > >I have here is having problems, but the PIII-700 isn't very affected. > Try removing SMP_DEBUG from your config (see > Message-ID: <[EMAIL PROTECTED]> > from Jason Evans on this thread). That worked for me... Does anyone here run the really new version of Licq? I know it sounds dumb, but it seems that if I run it and do some reasonably heavy disk, processes start getting stuck in things like vnlock, inode and ffsvgt... --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -current grinds exceeding slow
Hi, At 10:17 -0700 12/10/00, John Baldwin wrote: [...] >It's not. My current box that is having problems has an fxp0 card. >BTW, what speed is your processor? I'm curious because the PPro 200 >I have here is having problems, but the PIII-700 isn't very affected. Try removing SMP_DEBUG from your config (see Message-ID: <[EMAIL PROTECTED]> from Jason Evans on this thread). -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -current grinds exceeding slow
On 12-Oct-00 Bob Bishop wrote: > Hi, > > At 11:42 -0700 11/10/00, John Baldwin wrote: >>On 10-Oct-00 Bob Bishop wrote: >>> Hi, >>> >>> What's happened recently to make -current so slow? >>> [etc] >> >>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? > > More data: it's networking that's doing it, not NFS per se. I'm doing a > build with local sources on one of the affected boxes, on first impression > looks like that is up to speed. > > Both my affected boxes have ed NICs, I'll see if I can scare up a different > card to try in case it's the ed driver. Watch this space... It's not. My current box that is having problems has an fxp0 card. BTW, what speed is your processor? I'm curious because the PPro 200 I have here is having problems, but the PIII-700 isn't very affected. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -current grinds exceeding slow
Hi, At 11:42 -0700 11/10/00, John Baldwin wrote: >On 10-Oct-00 Bob Bishop wrote: >> Hi, >> >> What's happened recently to make -current so slow? >> [etc] > >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? More data: it's networking that's doing it, not NFS per se. I'm doing a build with local sources on one of the affected boxes, on first impression looks like that is up to speed. Both my affected boxes have ed NICs, I'll see if I can scare up a different card to try in case it's the ed driver. Watch this space... -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current grinds exceeding slow
At 12 Oct 2000 04:08:04 GMT, Jason Evans <[EMAIL PROTECTED]> wrote: > Do you have the SMP_DEBUG kernel option enabled? Yes, I had SMP_DEBUG in my kernel configuration. > My changes added lots of mutexes to the kernel, and mtx_validate() iterates > through all mutexes for mtx_init() and mtx_destroy() calls if SMP_DEBUG is > enabled. I'm working on a change that will use a pool of mutexes that are > allocated at boot time, which will make this slow down go away, but it may > be a while before it gets checked in. Thank you for your information. I've disabled SMP_DEBUG and it works with usual speed! I'll keep disabled until your modification will come. -- 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
Re: -current grinds exceeding slow
On Thu, Oct 12, 2000 at 12:41:29PM +0900, Jun Kuriyama wrote: > 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... Do you have the SMP_DEBUG kernel option enabled? My changes added lots of mutexes to the kernel, and mtx_validate() iterates through all mutexes for mtx_init() and mtx_destroy() calls if SMP_DEBUG is enabled. I'm working on a change that will use a pool of mutexes that are allocated at boot time, which will make this slow down go away, but it may be a while before it gets checked in. Jason To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -current grinds exceeding slow
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
RE: -current grinds exceeding slow
On 10-Oct-00 Bob Bishop wrote: > Hi, > > What's happened recently to make -current so slow? > > make world kernel FreeBSD 5.0-CURRENT #11: Sat Sep 30 15:07:06 BST 2000 elf make world started on Fri Oct 6 08:33:20 BST 2000 elf make world completed on Fri Oct 6 13:30:13 BST 2000 > > ...just under 5hrs > > > make world kernel FreeBSD 5.0-CURRENT #0: Sun Oct 8 13:37:48 BST 2000 elf make world started on Sun Oct 8 15:09:39 BST 2000 elf make world completed on Mon Oct 9 16:35:00 BST 2000 > > ...over 25hrs > > The machine feels very sluggish too, and the snake sometimes wiggles to a > standstill. 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? > This is a UP box, I've got an SMP box with the same symptoms. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -current grinds exceeding slow
On 10-Oct-00 Bob Bishop wrote: > make world kernel FreeBSD 5.0-CURRENT #11: Sat Sep 30 15:07:06 BST 2000 > >>> elf make world started on Fri Oct 6 08:33:20 BST 2000 > >>> elf make world completed on Fri Oct 6 13:30:13 BST 2000 > > ...just under 5hrs > > > make world kernel FreeBSD 5.0-CURRENT #0: Sun Oct 8 13:37:48 BST 2000 > >>> elf make world started on Sun Oct 8 15:09:39 BST 2000 > >>> elf make world completed on Mon Oct 9 16:35:00 BST 2000 > > ...over 25hrs > > The machine feels very sluggish too, and the snake sometimes wiggles to a > standstill. > > This is a UP box, I've got an SMP box with the same symptoms. 'Me too'. I notice it gets MUCH worse when using NFS, and just bad when using UFS (don't know if it is FS specific or just the fact that NFS is networked though). --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
