mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "Con Kolivas" <kernel@kolivas.org>
Subject: Re: belkin bulldog ups monitor vs 2.6.21-rc2
Date: Fri, 02 Mar 2007 02:16:39 -0500	[thread overview]
Message-ID: <200703020216.40047.gene.heskett@gmail.com> (raw)
In-Reply-To: <8cd998d50703012259l274b2d13k6da5048706c4664a@mail.gmail.com>

On Friday 02 March 2007, Con Kolivas wrote:
>On 02/03/07, Gene Heskett <gene.heskett@gmail.com> wrote:
>> Greetings;
>>
>> I just rebooted to 2.6.21-rc2 and noted that getting x up and running
>> was about 15 seconds longer than usual.  When it got a bash shell
>> going I went to it and ran htop which showed that the bulldog monitor
>> was taking 90% of the cpu.  Killed it, then restarted it, but when I
>> ran the gui which ran fine and then stopped the gui, the daemon once
>> again went hog wild and had to be killed,  and I'm losing my kmail
>> composer focus for 30 seconds at a time now that amanda is making her
>> nightly run.
>>
>> There is nothing in the log about it other than from xinetd as it ran
>> the amanda server stuff.
>>
>> Not quite ready for prime time methinks.  Using the ck scheduler, this
>> is terrible performance, virtually no multitasking.  Back to
>> 2.6.20-ck1 in the morning if it lives the rest of the night.
>
>HI Gene.
>
>I'm not sure if you're saying here that the performance is terrible on
>2.6.21-rc2 only with the -ck scheduler, or only 2.6.21-rc2, or that
>2.6.20-ck1 is terrible or that it fixes the problem.  Can you please
>clarify this?

I miss-spoke above now that I read it again, sorry Con.  I think I thought 
my fingers had put 'Comparing' in front of the 'Using' above. This time 
of the night, my mind has been known to be running a chapter or more 
ahead of (or in some cases behind) my fingers.

2.6.20-ck1 runs great, 2.6.21-rc2 was not only a dog, it fed amanda a 
bunch of lsd via bad data from tar, so tar when told to do a level 1 
while 21-rc2 (without your patch) was running, it actually did a level 0, 
and predictably ran out of vtape.  /usr/pix didn't change over 7GB of its 
contents overnight, in fact nothing changed there yesterday, but tar sure 
went on a rampage.

Sorry about the confusion.  I'm back in 2.6.20-ck1 and everythings cool.

>Regards,
>-ck

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)

  reply	other threads:[~2007-03-02  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02  5:42 Gene Heskett
2007-03-02  6:59 ` Con Kolivas
2007-03-02  7:16   ` Gene Heskett [this message]
2007-03-02  7:06 ` Gene Heskett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200703020216.40047.gene.heskett@gmail.com \
    --to=gene.heskett@gmail.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®