Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Steve Bromwich <lists@fop.ns.ca>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17
Date: Fri, 21 Nov 2003 20:58:18 +0000	[thread overview]
Message-ID: <3FBE7C6A.3010104@tiscali.be> (raw)
In-Reply-To: <Pine.LNX.4.58.0311190913310.1125@brain.fop.ns.ca>

Hi Steve,

Steve Bromwich wrote:
>>>Just to clarify, this is happening during operation, not bootup. Next time
>>>it happens (probably tomorrow morning) I'll break on serial and try
>>>piminfo
> 
> 
> So much for that idea - I forgot I had magic sysrq on, so break just gave
> me the usual sysrq options. I'll recompile without sysrq over the weekend
> and see what happens, but in the meantime I've reverted to 2.4.18 to see
> if I get the same problem, just to make sure it's not faulty hardware. I
> checked ps, and all the processes in D state were ones that touch the
> drive (eg, find, exim, apache).
> 
> I've got a J class at work that's not in production, so if I get time I'll
> try it out with the same config (or at least, the closest I can get) just
> to make sure it's not something obviously wonky in my config.
> 
well, but those system are widly different (cpu, architecture, ...).
> 
>>May be if you can, run hp diag tools?
> 
> 
> I don't have a CD in that machine - do you know if there's any netbootable
> images I can use? I have an HPUX 11.0 CD set, so if there's something I
> can pull off there I'll be good to go.
> 
Good question? never have to test it but it is a bootable cd (I don't 
remember if it is available via internet?) so if you copy it's image 
(with dd) on a system, i think that following the faq how-to netboot 
<http://parisc-linux.org/faq/index.html#netboot> , it would works?
> 
>>(I have no clue about 715 model but well running 2.4.22 (and above) on various
>>b180, b2k, c110, N4000 and i have never encounter such pb?)
> 
> 
> Well, the frustrating thing is is that there's no debug output anywhere
> that I can find that's showing anything obviously wrong.
Don't feel alone, during severall month (2, 3, 4, ... I don't want to 
remember) I try to get just a panic message from a smp kernel on a N4k 
: no success :_(
...

> I had a skim
> through lasi700.c/.h and couldn't see anything that'd help, do you know if
> there's any debug/printks I can scatter anywhere to give me some pointers?
>
Sorry, I couldn't help here.

hmm, what kind of disk have you on your D: hot-swapable or fixed?
(with fixed disk, I already encounter a pb of flat cable and with 
hot-swap disk a pb with dust on disks' support)

Cheers,
	Joel

  reply	other threads:[~2003-11-21 20:58 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
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 [this message]
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=3FBE7C6A.3010104@tiscali.be \
    --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