From: Steven Cole <elenstev@mesatop.com>
To: Robert Love <rml@tech9.net>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] BUG(): sched.c: Line 944
Date: 17 Sep 2002 14:32:28 -0600 [thread overview]
Message-ID: <1032294748.11913.59.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <1032293199.4588.235.camel@phantasy>
On Tue, 2002-09-17 at 14:06, Robert Love wrote:
> On Tue, 2002-09-17 at 15:54, Steven Cole wrote:
>
> Thank you for the testing, Steven.
>
> > Running dbench 3 resulted in the dbench clients hanging and being
> > unkillable with kill -9 in the D state.
>
> Hrm, I cannot reproduce this. I just successfully completed a `dbench
> 16'. Can you find where they are hanging? You can get a trace via
> sysrq. You can also see where they are in the kernel via the wchan
> field of ps: "ps -ewo user,pid,priority,%cpu,stat,command,wchan" is a
> favorite of mine.
I rebooted the box, but had to SYSRQ-S, SYSRQ-B, due to shutdown -r now
hanging up. On reboot, the init scripts froze after "starting atd", but
fortunately this was after sshd, so I ssh'd to the box several times,
and did your ps command before hanging it with dbench 3 (dbench 1 and 2
were successful again). I have that ps output if you want it. I could
NOT do that, or even ls, after the dbench 3 hang. When I shutdown,
SYSRQ-S only partially synced (just one partition).
>
> Sure it does not happen with a stock kernel (no preempt)?
I'll try 2.5.35-bk3 (no other patches) without preempt shortly.
I'll report any failures, but no news is good news.
>
> What if you replace the printk() and dump_stack() in schedule() with a
> no-op (but not something that will optimize away the conditional, i.e.
> try a cpu_relax()).
I'll try that if I get the time. But I wasn't getting any dump info in
dmesg for those boots.
>
> Oh, is the previous patch fully backed out? None of that do_exit muck
> anymore, right?
Yep, plain 2.5.35, then patched with 2.5.35-bk3, then with your patch
posted at 15:23. Nothing else.
>
> > Test box is 2-way pIII, kernel SMP.
>
> I too am SMP with kernel preemption, dual Athlon MP.
Steven
next prev parent reply other threads:[~2002-09-17 20:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 18:48 Robert Love
2002-09-16 19:01 ` Linus Torvalds
2002-09-16 21:14 ` Robert Love
2002-09-16 21:41 ` Linus Torvalds
2002-09-16 22:15 ` Robert Love
2002-09-16 22:26 ` Linus Torvalds
2002-09-16 23:15 ` Robert Love
2002-09-16 23:45 ` Linus Torvalds
2002-09-16 23:58 ` Robert Love
2002-09-17 5:56 ` Linus Torvalds
2002-09-17 8:12 ` Robert Love
2002-09-17 8:51 ` Robert Love
2002-09-17 8:59 ` Robert Love
2002-09-17 9:57 ` Ingo Molnar
2002-09-17 18:27 ` Robert Love
2002-09-17 18:46 ` Ingo Molnar
2002-09-17 14:10 ` Steven Cole
2002-09-17 18:29 ` Robert Love
2002-09-17 18:42 ` Steven Cole
2002-09-17 15:27 ` Linus Torvalds
2002-09-17 15:40 ` Linus Torvalds
2002-09-17 15:53 ` Ingo Molnar
2002-09-17 16:18 ` Linus Torvalds
2002-09-17 16:26 ` Ingo Molnar
2002-09-17 18:47 ` Robert Love
2002-09-17 18:57 ` Ingo Molnar
2002-09-17 19:23 ` Robert Love
2002-09-17 19:54 ` Steven Cole
2002-09-17 20:06 ` Robert Love
2002-09-17 20:32 ` Steven Cole [this message]
2002-09-17 20:58 ` Steven Cole
2002-09-18 4:44 ` Robert Love
2002-09-18 14:08 ` Steven Cole
2002-09-17 15:54 ` Ingo Molnar
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=1032294748.11913.59.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
--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®