Prev: Slackware 13 aren't booting on VMWare
Next: Slack13, src2pkg, FATAL! Home directory...
From: Grant on 30 Apr 2010 01:50
On Fri, 30 Apr 2010 02:55:28 +0000 (UTC), Sylvain Robitaille <syl(a)alcor.concordia.ca> wrote:

>Grant wrote:
>
>> ... The complex schedulers may fail (to perform) in corner cases.
>
>Reference?

lkml, if you can find vger.kernel.org, I can't reach it today :(

Why I put 'to perform' in parens, didn't mean it fails, meant it fails to
do better than nothing on some loads.

Grant.
>
>: charlotte[syl] ~; uptime
> 22:54:39 up 134 days, 4:11, 46 users, load average: 0.22, 0.16, 0.10
>: charlotte[syl] ~; cat /etc/slackware-version
>Slackware 13.0.0.0.0
>: charlotte[syl] ~; uname -a
>Linux charlotte 2.6.29.6-smp #2 SMP Mon Aug 17 00:52:54 CDT 2009 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
>: charlotte[syl] ~; zgrep IOSCHED /proc/config.gz
>CONFIG_IOSCHED_NOOP=y
>CONFIG_IOSCHED_AS=y
>CONFIG_IOSCHED_DEADLINE=y
>CONFIG_IOSCHED_CFQ=y
>CONFIG_DEFAULT_IOSCHED="cfq"
--
http://bugs.id.au/
From: Chick Tower on 30 Apr 2010 12:33
On 2010-04-29, Grant <omg(a)grrr.id.au> wrote:
> The complex schedulers may fail (to perform) in corner cases.

Just disable them in the kernel config:

ALLOW_CORNER_CASES=n
--
Chick Tower

For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
From: Grant on 30 Apr 2010 17:22
On Fri, 30 Apr 2010 16:33:39 +0000 (UTC), Chick Tower <c.tower(a)deadspam.com> wrote:

>On 2010-04-29, Grant <omg(a)grrr.id.au> wrote:
>> The complex schedulers may fail (to perform) in corner cases.
>
>Just disable them in the kernel config:
>
>ALLOW_CORNER_CASES=n

Very funny, which released kernel has that one?

Grant.
--
http://bugs.id.au/
From: Michael Black on 2 May 2010 10:33
On Wed, 28 Apr 2010, Douglas Mayne wrote:

> This kernel reportedly fixes some XFS filesystem deadlock bugs. I
> personally ran into deadlocks on 2.6.33.2, which made that version
> unreliable for me. BTW, I was testing with XFS on a loopback file when I
> ran into this bug. Anyway, my advice is to skip over 2.6.33.2 now that a
> new patch is available. YMMV.
>
And a few days later, 2.6.33.3 is at Slackware.

It's no wonder it take so long between releases, they just did 2.6.33.2
on April 20th and 2.6.33.1 on March 30th. If the kernel wasn't constantly
being upgraded, they'd have more time to deal with the other things.

Michael

From: Grant on 2 May 2010 18:42
On Sun, 2 May 2010 10:33:30 -0400, Michael Black <et472(a)ncf.ca> wrote:

>On Wed, 28 Apr 2010, Douglas Mayne wrote:
>
>> This kernel reportedly fixes some XFS filesystem deadlock bugs. I
>> personally ran into deadlocks on 2.6.33.2, which made that version
>> unreliable for me. BTW, I was testing with XFS on a loopback file when I
>> ran into this bug. Anyway, my advice is to skip over 2.6.33.2 now that a
>> new patch is available. YMMV.
>>
>And a few days later, 2.6.33.3 is at Slackware.
>
>It's no wonder it take so long between releases, they just did 2.6.33.2
>on April 20th and 2.6.33.1 on March 30th. If the kernel wasn't constantly
>being upgraded, they'd have more time to deal with the other things.

Minor kernel updates would surely be scripted? Usually there's no change
to the .config involved.

Grant.
--
http://bugs.id.au/
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Slackware 13 aren't booting on VMWare
Next: Slack13, src2pkg, FATAL! Home directory...