Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] strace locks up 2.4.22-pa14
Date: Sat, 22 Nov 2003 11:58:29 +0000	[thread overview]
Message-ID: <3FBF4F65.70502@tiscali.be> (raw)
In-Reply-To: <20031122052915.GB29917@colo.lackof.org>


Grant Grundler wrote:
> On Fri, Nov 21, 2003 at 01:39:49PM +0100, Joel Soete wrote:
> 
>>Hi Grant,
>>
>>I am tring to track a lpr pb on my b2k and so try:
>># strace -f /usr/bin/lpr foo.doc
>>
>>that works;
> 
> 
> ok
> 
> 
>>I read your post and try so now:
>># strace -f -o /var/tmp/Strace.doc /usr/bin/lpr foo.doc
>>
>>and system also hang (same behaviour as)
>>and so I toc it (which seems to failled ; apparently because of ide-cdrom???)
> 
> 
> hrm. I doubt the ide-cdrom is causing the TOC to fail. 

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)

> It's likely the CD-ROM drive is getting reset when TOC occurs
> and that's the noise you hear.
> Something else might be causing problems.
> 
Well, I don't realy need that system hang to toc it? (just think right now)
So when I have some time, I will re-try a toc when system is running and 
see what hapen ;)
> 
>>I took the opportunity to unplug ide-cable's cdrom (to test various).
>>
>>Then to try to obtain a relevant toc, I re-launch:
>># strace -f -o /var/tmp/Strace.doc /usr/bin/lpr foo.doc
>>
>>This time it works??
>>Is it the same for you after the reboot?
> 
> 
> I haven't retried because I need that to actaully work on that system.
> I'm building a new kernel and will try at home tonight.
> 
Ok
> 
> 
>>(sorry, I tried severall time strace but no more means to reproduce)
> 
> 
> bummer. Makes me wonder if this is CPU cache related too. 
> 
I am curious to see the result of your test ?)
> 
>>PS: btw the end of my strace is:
>>[...]
>>24801 write(3, "\1lp\n", 4)             = 4
>>24801 read(3, "\0", 1)                  = 1
>>24801 close(3)                          = 0
>>24801 SYS_222(0, 0, 0x1, 0x2f, 0)       = -1 ENOSYS (Function not implemented)
>>24801 exit(0)                           = ?
>>
>>And at the same time, at the serial console I got:
>>+ set -v
>>+ exec
>>
>>Have you any advise about what I miss?
> 
> 
> include/asm/unistd.h says:
> #define __NR_exit_group         (__NR_Linux + 222)
> 
> No architecture implements that syscall.
> ("find -name '*.[S]' | xargs fgrep exit_group")
> I have no clue what it's supposed to do and looks like
> I don't need to care either.
> 
> Perhaps just recompiling the application or linked lib that uses
> that syscall might get rid of it.
> 
Good idea, I will try.

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 :(.

Thanks for advise,
	Joel


> grant
> 

  reply	other threads:[~2003-11-22 11:58 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 [this message]
2003-11-22 22:09       ` Grant Grundler
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=3FBF4F65.70502@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.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