From: Ralf Baechle <ralf@oss.sgi.com>
To: K.H.C.vanHouten@kpn.com
Cc: linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: process lockups
Date: Tue, 24 Oct 2000 17:09:39 +0200 [thread overview]
Message-ID: <20001024170939.C7342@bacchus.dhis.org> (raw)
In-Reply-To: <200010240551.HAA02069@sparta.research.kpn.com>; from K.H.C.vanHouten@research.kpn.com on Tue, Oct 24, 2000 at 07:51:42AM +0200
On Tue, Oct 24, 2000 at 07:51:42AM +0200, Houten K.H.C. van (Karel) wrote:
> Aside from this I stil get 'bug in get_wchan' messages, but everything
> seems to run fine. I hope to test my current kernels on a 5000/150 and
> a 3100.
Try this untested fix for get_wchan. The values in the ps axl column should
now be numbers that make sense as addresses. Unless the `n' option is
also used ps will try to translate the address back into a symbol. Cite
from ps(1):
[...]
To produce the WCHAN field, ps needs to read the Sys
tem.map file created when the kernel is compiled. The
search path is:
$PS_SYSTEM_MAP
/boot/System.map-`uname -r`
/boot/System.map
/lib/modules/`uname -r`/System.map
/usr/src/linux/System.map
/System.map
[...]
If that's working as planned please send me the WCHAN of any stuck process.
I need to know where they're stuck.
Ralf
--- arch/mips/kernel/process.c 2000/10/05 01:18:43 1.21
+++ arch/mips/kernel/process.c 2000/10/24 14:54:29
@@ -203,18 +203,9 @@
return 0;
pc = thread_saved_pc(&p->thread);
- if (pc == (unsigned long) interruptible_sleep_on
- || pc == (unsigned long) sleep_on) {
- schedule_frame = ((unsigned long *)p->thread.reg30)[9];
- return ((unsigned long *)schedule_frame)[15];
- }
- if (pc == (unsigned long) interruptible_sleep_on_timeout
- || pc == (unsigned long) sleep_on_timeout) {
- schedule_frame = ((unsigned long *)p->thread.reg30)[9];
- return ((unsigned long *)schedule_frame)[16];
- }
if (pc >= first_sched && pc < last_sched) {
- printk(KERN_DEBUG "Bug in %s\n", __FUNCTION__);
+ schedule_frame = ((unsigned long *)p->thread.reg30)[9];
+ return ((unsigned long *)schedule_frame)[11];
}
return pc;
next prev parent reply other threads:[~2000-10-24 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 1:22 process lockups Karsten Merker
2000-10-24 2:47 ` Ralf Baechle
2000-10-24 5:51 ` Houten K.H.C. van (Karel)
2000-10-24 11:15 ` Karsten Merker
2000-10-24 14:38 ` Ralf Baechle
2000-10-24 17:55 ` Karsten Merker
2000-10-25 1:29 ` Ralf Baechle
2000-10-24 15:09 ` Ralf Baechle [this message]
2000-10-24 12:25 ` Florian Lohoff
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=20001024170939.C7342@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=K.H.C.vanHouten@kpn.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.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