From: Con Kolivas <kernel@kolivas.org>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7-ck1
Date: Sun, 20 Jun 2004 02:38:05 +1000 [thread overview]
Message-ID: <40D46BED.2010901@kolivas.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0406191824030.4764@alpha.polcom.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Grzegorz Kulewski wrote:
|
| On Sat, 19 Jun 2004, Con Kolivas wrote:
|
|
|>Con Kolivas wrote:
|>
|>>On Sat, 19 Jun 2004 04:35, Grzegorz Kulewski wrote:
|>>
|>>
|>>>Hi Con,
|>>>
|>>>I have two problems with 2.6.7-ck1. My distribution is Gentoo Linux
|>>>unstable with all latest updates. Oh, yes, both 2.6.7-ck1 and 2.6.7-rc3
|>>>I tested have vesafb-tng applied from http://dev.gentoo.org/~spock/, but
|>>>it should not cause any problems because it is very non-intrusive
patch I
|>>>think. Maybe you should include this in your patchset?
|>>>
|>>>1. When booting init script freezes after starting input hotplugging (it
|>>>is udev system). The only way to make it run is to press Ctrl-Alt-SysRQ
|>>>and various keys to display kernel state several times. After that
system
|>>>starts normally. I do not know if it is only -ck problem because I had
|>>>no time to test 2.6.7 vanilla, but 2.6.7-rc3 worked fine. (Log
included.)
|>>
|>>
|>>Yes I have a sneaking suspicion it's related to the fact kernel
threads are
|>>fixed priority at the moment in staircase (they dont descend priority
like
|>>normal tasks so act like relatively low priority real time tasks). I'm
|>>addressing that for the next version so hopefully that will fix it.
|>
|>Here's a diff for -ck1 which brings you up to staircase7.1
|>Can you try that?
|
|
| It does not solve the problem for me, sorry...
Ok I'll keep looking. That change was necessary anyway.
Thanks,
Con
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA1GvtZUg7+tp6mRURAk4MAJ9xJ49Mwyv/Qlb5M4Dm8acsto5kRgCdEtIp
WE4lkMOxIh3HB+IET/oEs9c=
=4ayV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-19 16:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 11:22 2.6.7-ck1 Con Kolivas
2004-06-18 16:28 ` 2.6.7-ck1 Felipe Alfaro Solana
2004-06-19 3:48 ` 2.6.7-ck1 Con Kolivas
2004-06-19 5:20 ` 2.6.7-ck1 Con Kolivas
2004-06-19 8:39 ` 2.6.7-ck1 Felipe Alfaro Solana
[not found] ` <Pine.LNX.4.58.0406182004370.32121@alpha.polcom.net>
2004-06-19 4:06 ` 2.6.7-ck1 Con Kolivas
2004-06-19 5:26 ` 2.6.7-ck1 Con Kolivas
2004-06-19 16:25 ` 2.6.7-ck1 Grzegorz Kulewski
2004-06-19 16:38 ` Con Kolivas [this message]
2004-06-28 22:46 ` 2.6.7-ck1 Pavel Machek
2004-06-28 20:52 ` 2.6.7-ck1 kernel
2004-06-29 8:19 ` 2.6.7-ck1 Felipe Alfaro Solana
2004-06-19 21:00 ` 2.6.7-ck1, cfq ionice? Prakash K. Cheemplavam
2004-06-19 21:05 ` Prakash K. Cheemplavam
2004-06-19 23:18 ` Con Kolivas
2004-06-20 7:40 ` Prakash K. Cheemplavam
2004-06-21 16:02 ` 2.6.7-ck1 Brian S. Stephan
-- strict thread matches above, loose matches on Subject: below --
2004-06-19 20:50 2.6.7-ck1 AshMilsted
2004-06-19 23:10 ` 2.6.7-ck1 Con Kolivas
2004-06-25 13:48 2.6.7-ck1 Con Kolivas
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=40D46BED.2010901@kolivas.org \
--to=kernel@kolivas.org \
--cc=kangur@polcom.net \
--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