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: Sun, 23 Nov 2003 19:25:14 -0700 [thread overview]
Message-ID: <20031124022514.GA23224@colo.lackof.org> (raw)
In-Reply-To: <3FBFE71F.7060207@tiscali.be>
On Sat, Nov 22, 2003 at 10:45:51PM +0000, Joel Soete wrote:
> hmm b2k and c3k are very brother system in term of architecture and
> components?
yes - identical nearly. Share the same CPU, chipset, and firmware.
> May I ask you the amount of ram stand in your c3k? (on my
> b2k only 256k).
1GB.
> >If network, then I would guess your merge (or the 2.4.23-rc2 base) has a
> >bug.
>
> Certainly :( [but where, the rest ftp, rsync, nfs-client, gtk-app, ...
> work fine and no special messages neither into kernel, messages or
> syslog?]. Well don't care now, it is just a beat anoying to printout my
> scripts.
ok. TBH, I have no clue then. It might be possible to attach strace to
a running lp deamon, redirect strace output to /dev/console and then
compore what happens different on the b2k when a print job is started.
My hope is the syscall output will get printed before it totallte crashes.
grant
next prev parent reply other threads:[~2003-11-24 2:25 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
2003-11-22 22:45 ` Joel Soete
2003-11-24 2:25 ` Grant Grundler [this message]
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=20031124022514.GA23224@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.