linux-kernel - Re: belkin bulldog ups monitor vs 2.6.21-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8cd998d50703012259l274b2d13k6da5048706c4664a@mail.gmail.com>
Date:	Fri, 2 Mar 2007 17:59:33 +1100
From:	"Con Kolivas" <kernel@...ivas.org>
To:	"Gene Heskett" <gene.heskett@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: belkin bulldog ups monitor vs 2.6.21-rc2

On 02/03/07, Gene Heskett <gene.heskett@...il.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?

Regards,
-ck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/