From: Randolph Chung <randolph@tausq.org>
To: Joel Soete <soete.joel@tiscali.be>
Cc: "James.Bottomley" <James.Bottomley@SteelEye.com>,
dave <dave@hiauly1.hia.nrc.ca>,
parisc-linux <parisc-linux@lists.parisc-linux.org>,
tsg45800 <tsg45800@scarlet.be>
Subject: Re: [parisc-linux] Re: gsyprf11 and 2.6.13-rc3-pa1
Date: Tue, 16 Aug 2005 18:10:24 +0800 [thread overview]
Message-ID: <4301BB90.5060907@tausq.org> (raw)
In-Reply-To: <ILB5TV$CA7EA436EF33A0C6E0748DAEC30B9B9F@scarlet.be>
> on a b180 model runing the latest cvs 2.6.13-rc6-pa1 (compiled with debian
> stock gcc-4.0, as it's an unstable install but downgraded libc6 2.3.2), foo
> runs untils:
> ...
> Estimating stack consumed 0x7fee40
> Estimating stack consumed 0x7fef80
> Estimating stack consumed 0x7ff0c0
> ====<hang>===
>
> The ping still responding but not anymore the console (nor other process
> apparently)... no more heartbit/disk leds flashing; pressing TOC buton launch
> the reboot but what is bad: nothing was saved in piminfo (all 0 and No valid
> timestamp) :-(
Yup, this is the same as what others are seeing. It's definitely a
problem with infinitely looping signal handlers.
I'm not sure what's the "correct" behavior in this case. I recall now
that we saw a similar problem with expect where the signal handler was
recursing.
Is the kernel responsible for blocking SIGSEGV handlers that generate
SIGSEGV?
randolph
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-08-16 10:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 9:17 [parisc-linux] Re: gsyprf11 and 2.6.13-rc3-pa1 Joel Soete
2005-08-16 10:10 ` Randolph Chung [this message]
2005-08-16 13:39 ` John David Anglin
2005-08-16 14:34 ` Randolph Chung
2005-08-16 15:06 ` Michael S. Zick
2005-08-16 23:57 ` Randolph Chung
2005-08-17 0:08 ` John David Anglin
2005-08-17 0:50 ` John David Anglin
[not found] <no.id>
2005-08-16 3:32 ` John David Anglin
[not found] <20050812180551.GA32609@colo.lackof.org>
2005-08-13 0:00 ` John David Anglin
2005-08-13 5:02 ` Grant Grundler
2005-08-13 5:11 ` John David Anglin
2005-08-13 5:14 ` John David Anglin
2005-08-13 13:40 ` James Bottomley
2005-08-13 17:46 ` John David Anglin
2005-08-13 19:30 ` John David Anglin
2005-08-16 3:02 ` Randolph Chung
2005-08-16 3:18 ` John David Anglin
2005-08-14 1:32 ` John David Anglin
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=4301BB90.5060907@tausq.org \
--to=randolph@tausq.org \
--cc=James.Bottomley@SteelEye.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=soete.joel@tiscali.be \
--cc=tsg45800@scarlet.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