Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Joel Soete" <soete.joel@tiscali.be>
To: "Steve Bromwich" <lists@fop.ns.ca>, parisc-linux@parisc-linux.org
Subject: RE: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17
Date: Tue, 18 Nov 2003 18:28:27 +0000	[thread overview]
Message-ID: <3FB265EC0000392B@ocpmta3.freegates.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0311181014220.5439@brain.fop.ns.ca>

Hi Steve,

The toc 'process' don't display anything (excepted may be on lcd). To see
'piminfo', you should interupt the boot and collect the 'piminfo' (iirc >
ser pim).

hth,
    Joel

PS: btw which glibc is installed on your system?

>-- Original Message --
>From: Steve Bromwich <lists@fop.ns.ca>
>To: parisc-linux@parisc-linux.org
>Date: Tue, 18 Nov 2003 10:24:56 -0400 (AST)
>Subject: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17
>
>
>Hi,

I installed 2.4.22-pa17 on my machine over the weekend, and I'm getting
processes stuck in D state. The machine usually runs for several hours
without any problem, but then processes start dying, apparently fairly
randomly, the load goes up, 
>nd vmstat shows CPU as near 100% idle. I
*think* it's something to do with writing to the drive, since one of the
first things to die is syslogging. Anything that doesn't touch the drive
(eg, IRC clients) seem to run forever. One thing that really k
>lls it
seems to be daily maintenance around 6am; I can see mail being delivered
until then, and after that it queues on my backup MX. The only way to get
the machine back is to pull the power - shutdown -r now hangs, presing the
power button gets s
>utdown started but still hangs, and the TOC doesn't
seem to produce any output on my serial console. I've only seen a process
die in ffront of me once, when I was exiting from a bash session; the
machine just sat there with no i/o, ps aux showed the
>bash session stuck
in D state, and I couldn't ctrl-c or ctrl-z out of it at all.

Prior to this I was running 2.4.18 with no problem with the machine
running for months at a time. Has anyone seen this problem and/or got any
tips on how to figure o
>t what's going wrong? I can't find any error
output anywhere that's hinting what could be wrong, so I'm really stuck on
this one.

I've attached my .config, dmesg and cpuinfo in case anyone can see
anything obvious. Thanks for any help!

Cheers,
>Steve
>
>Attachment: config_2422pa17
>
>
>Attachment: dmesg
>
>
>Attachment: cpuinfo
>


-------------------------------------------------------------------------
Tiscali ADSL: 3 mois GRATUITS! L'Internet rapide, c'est pour tout le monde.

http://reg.tiscali.be/default.asp?lg=fr

  reply	other threads:[~2003-11-18 18:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-18 14:24 [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17 Steve Bromwich
2003-11-18 18:28 ` Joel Soete [this message]
2003-11-18 18:34   ` Steve Bromwich
2003-11-19  8:21     ` Joel Soete
2003-11-19 13:03       ` Matthew Wilcox
2003-11-19 13:21       ` Steve Bromwich
2003-11-21 20:58         ` Joel Soete
2003-11-22  1:55           ` Steve Bromwich
2003-12-08  7:29             ` Michael Wood

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=3FB265EC0000392B@ocpmta3.freegates.net \
    --to=soete.joel@tiscali.be \
    --cc=lists@fop.ns.ca \
    --cc=parisc-linux@parisc-linux.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