From: Nick Piggin <piggin@cyberone.com.au>
To: "Markus Hästbacka" <midian@ihme.org>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Nick's scheduler v19a
Date: Fri, 21 Nov 2003 20:14:56 +1100 [thread overview]
Message-ID: <3FBDD790.5060401@cyberone.com.au> (raw)
In-Reply-To: <1069405566.18362.5.camel@midux>
Markus Hästbacka wrote:
>Hi again.
>I'm not sure if this is because of the patch or what, but my X crashes
>normally in ~2 days, and the framebuffer gets all messy (green lines,
>can't see what I'm typing, etc.), this doesn't happen with your patch at
>all, only with vanilla kernel(s). Maybe my hardware likes your patch or
>something. My X have been running for four days now without any kind of
>problem on the patched kernel. (I'm not sure if it's the kernel or what,
>but reported it anyway). That's the only problem I've been getting more
>than often.
>
>There's no other problems, only that the kernel standard scheduler is a
>bit slower than yours.
>
>
Well yes its possible that my scheduler is better at hiding some bug. It
wouldn't be fixing anything, of course. It definitely was better at
exposing a kernel or postgresql bug when running OSDL's PostgreSQL tests -
I saw the crash 3 times I think, though never with standard kernel.
I don't know how you should be reporting X crashes. I guess you could report
the bug to the XFree86 guys as per their guidelines if you can reproduce the
crashes with an up to date 2.4 kernel.
Nick
>Regards,
>Markus
>
>On Fri, 2003-11-21 at 08:20, Nick Piggin wrote:
>
>
>>Well that's very good to hear :) err, just remember if you have
>>any specific problems with unpatched 2.6 to make a report. We
>>want the standard scheduler to run well too.
>>
>>Thanks,
>>Nick
>>
>>
next prev parent reply other threads:[~2003-11-21 9:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 13:11 Nick's scheduler v19a Nick Piggin
2003-11-20 20:45 ` Markus Hästbacka
2003-11-20 23:34 ` Nick Piggin
2003-11-21 6:11 ` Markus Hästbacka
2003-11-21 6:20 ` Nick Piggin
2003-11-21 9:06 ` Markus Hästbacka
2003-11-21 9:14 ` Nick Piggin [this message]
2003-11-21 9:32 ` Markus Hästbacka
2003-11-21 9:54 ` Måns Rullgård
2003-11-21 10:21 ` Markus Hästbacka
2003-11-21 16:19 ` Timothy Miller
2003-11-21 17:00 ` Markus Hästbacka
2003-11-24 7:45 ` Peter C. Ndikuwera
2004-01-12 19:40 ` Bug found (Was: Re: Nick's scheduler v19a) Markus Hästbacka
2003-12-03 16:14 ` Nick's scheduler v19a Markus Hästbacka
2003-12-03 22:15 ` Nick Piggin
2003-12-07 21:52 ` Markus Hästbacka
2003-12-07 23:05 ` Nick Piggin
[not found] <3FF79C54.4070200@cyberone.com.au>
2004-02-02 11:21 ` Markus Hästbacka
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=3FBDD790.5060401@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=midian@ihme.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