From: David Ford <david@blue-labs.org>
To: Josh Logan <josh@wcug.wwu.edu>
Cc: Andrea Arcangeli <andrea@suse.de>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Andrew Morton <andrewm@uow.edu.au>,
Klaus Dittrich <kladit@t-online.de>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.7p6 hang
Date: Wed, 11 Jul 2001 15:27:28 -0400 [thread overview]
Message-ID: <3B4CA8A0.507@blue-labs.org> (raw)
In-Reply-To: <Pine.BSO.4.21.0107111129150.26715-100000@sloth.wcug.wwu.edu>
This patch fixes the hang for me.
Thank you,
David
Josh Logan wrote:
>I'm having a hang right after the floppy is initialised with pre5 and pre6
>(2.4.3 works fine) I tried this patch, but it did not make any
>improvments. The machine still has SysRq commands available. Please let
>me know what other information you would like to debug this problem.
>
>BTW, I also tried to disable the floppy in the BIOS and got:
>...
>Floppy OK
>task queue still active
><HANG>
>
> Later, JOSH
>
>
>On Wed, 11 Jul 2001, Andrea Arcangeli wrote:
>
>>On Wed, Jul 11, 2001 at 04:22:04PM +0200, Trond Myklebust wrote:
>>
>>>>>>>>" " == Andrew Morton <andrewm@uow.edu.au> writes:
>>>>>>>>
>>> > Trond Myklebust wrote:
>>> >>
>>> >> ... I have the same problem on my setup. To me, it looks like
>>> >> the loop in spawn_ksoftirqd() is suffering from some sort of
>>> >> atomicity problem.
>>>
>>> > Does a `set_current_state(TASK_RUNNING);' in spawn_ksoftirqd()
>>> > fix it? If so we have a rogue initcall...
>>>
>>>Nope. The same thing happens as before.
>>>
>>>A couple of debugging statements show that ksoftirqd_CPU0 gets created
>>>fine, and that ksoftirqd_task(0) is indeed getting set correctly
>>>before we loop in spawn_ksoftirqd().
>>>After this the second call to kernel_thread() succeeds, but
>>>ksoftirqd() itself never gets called before the hang occurs.
>>>
>>ksoftirqd is quite scheduler intensive, and while its startup is
>>correct (no need of any change there), it tends to trigger scheduler
>>bugs (one of those bugs was just fixed in pre5). The reason I never seen
>>the deadlock I also fixed this other scheduler bug in my tree:
>>
>> ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.7pre5aa1/00_sched-yield-1
>>
>>this one I forgot to sumbit but here it is now for easy merging:
>>
>>--- 2.4.4aa3/kernel/sched.c.~1~ Sun Apr 29 17:37:05 2001
>>+++ 2.4.4aa3/kernel/sched.c Tue May 1 16:39:42 2001
>>@@ -674,8 +674,10 @@
>> #endif
>> spin_unlock_irq(&runqueue_lock);
>>
>>- if (prev == next)
>>+ if (prev == next) {
>>+ current->policy &= ~SCHED_YIELD;
>> goto same_process;
>>+ }
>>
>> #ifdef CONFIG_SMP
>> /*
>>
next prev parent reply other threads:[~2001-07-11 19:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 8:49 2.4.7p6 hang Klaus Dittrich
2001-07-11 12:56 ` Trond Myklebust
2001-07-11 13:38 ` Andrew Morton
2001-07-11 14:22 ` Trond Myklebust
2001-07-11 15:58 ` Andrea Arcangeli
2001-07-11 16:30 ` Trond Myklebust
2001-07-11 16:53 ` Andrea Arcangeli
2001-07-11 17:19 ` Mike Kravetz
2001-07-11 18:33 ` Josh Logan
2001-07-11 19:05 ` Andrea Arcangeli
2001-07-11 19:28 ` Josh Logan
2001-07-16 19:16 ` Josh Logan
2001-07-16 19:34 ` David Ford
2001-07-16 21:07 ` Josh Logan
2001-07-11 19:27 ` David Ford [this message]
2001-07-12 0:17 ` Johan Kullstam
2001-07-11 15:49 ` Andrea Arcangeli
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=3B4CA8A0.507@blue-labs.org \
--to=david@blue-labs.org \
--cc=andrea@suse.de \
--cc=andrewm@uow.edu.au \
--cc=josh@wcug.wwu.edu \
--cc=kladit@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.