From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: 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 16:22:04 +0200 [thread overview]
Message-ID: <15180.24844.687421.239488@charged.uio.no> (raw)
In-Reply-To: <3B4C56F1.3085D698@uow.edu.au>
In-Reply-To: <200107110849.f6B8nlm00414@df1tlpc.local.here> <shslmlv62us.fsf@charged.uio.no> <3B4C56F1.3085D698@uow.edu.au>
>>>>> " " == 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.
Cheers,
Trond
next prev parent reply other threads:[~2001-07-11 14:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 8:49 Klaus Dittrich
2001-07-11 12:56 ` Trond Myklebust
2001-07-11 13:38 ` Andrew Morton
2001-07-11 14:22 ` Trond Myklebust [this message]
2001-07-11 15:58 ` 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
2001-07-12 0:17 ` Johan Kullstam
2001-07-11 16:30 ` Trond Myklebust
2001-07-11 16:53 ` Andrea Arcangeli
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=15180.24844.687421.239488@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=andrewm@uow.edu.au \
--cc=kladit@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®