From: Grant Grundler <grundler@parisc-linux.org>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] strace locks up 2.4.22-pa14
Date: Sat, 22 Nov 2003 15:09:19 -0700 [thread overview]
Message-ID: <20031122220919.GA6732@colo.lackof.org> (raw)
In-Reply-To: <3FBF4F65.70502@tiscali.be>
On Sat, Nov 22, 2003 at 11:58:29AM +0000, Joel Soete wrote:
> I don't know but seems to hang like boot hang when I include the pdc
> support into the kernel: green led stay lightning. (and toc seems to
> failed because of a time out IO; i don't remember but I think i do have
> to read it on lcd)
What do you mean by "PDC support"?
You mean CONFIG_PDC_CHASSIS?
AFAIK, this only enables chassis codes to be displayed on either
the "front panel" LCD or LEDs.
It looks like my box HPMCs after the TOC. The TOC performs
a reset and then seltests run. Then next thing on the LCD
display is "OS HPMC" even though the gfx card hasn't been
initialized yet.
> Well, I don't realy need that system hang to toc it?
Right. TOC is just convenient to use when the system is hung.
> So when I have some time, I will re-try a toc when system is running and
> see what hapen ;)
You'll get state info about cpu_idle() or whatever it happens to
be doing.
> >bummer. Makes me wonder if this is CPU cache related too.
> I am curious to see the result of your test ?)
2.4.22-pa17 on c3k, "strace -f -o /tmp/dcop.out dcopserver" hung at home.
GR02 0x10389567
20-23 0x32 0x0e 0x10 0x00
24-27 0x00 0x10 0xcc 0x102d2010
CR0-3 0x00 0x1822 0x00 0x1824
IOAQ 0x102a1188 number+170
CPU State 0x9e000001
Looks like the PIM dump is garbage. (gr02 is not a kernel address)
I've cleared the PIM and will retry later...gotta run.
> what I don't understand is that lpr works fine on my b180 runing a
> k-2.4.21 (for lvm2 support) otc the b2k is running a k-2.4.23-rc2-pa7 (a
> merge of mine); so my doubt is that I could break something :(.
Is this via parallel port or network printer?
If network, then I would guess your merge (or the 2.4.23-rc2 base) has a bug.
If parallel port, likely a bug in suckyio support for parallel port.
But it's not exactly "apples to apples" comparison since the IO subsystem
between B180 and B2k is completely different.
grant
next prev parent reply other threads:[~2003-11-22 22:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 0:50 [parisc-linux] strace locks up 2.4.22-pa14 Grant Grundler
2003-11-21 12:39 ` Joel Soete
2003-11-22 5:29 ` Grant Grundler
2003-11-22 11:58 ` Joel Soete
2003-11-22 22:09 ` Grant Grundler [this message]
2003-11-22 22:45 ` Joel Soete
2003-11-24 2:25 ` Grant Grundler
2003-11-24 7:21 ` Joel Soete
2003-11-24 7:33 ` Grant Grundler
2003-11-25 7:23 ` Joel Soete
2003-11-22 23:35 ` Joel Soete
[not found] ` <3FBFE7F0.2070204@tiscali.be>
2003-11-24 2:42 ` Grant Grundler
2003-11-24 7:49 ` Joel Soete
2003-11-24 16:26 ` Grant Grundler
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=20031122220919.GA6732@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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