From: Joel Soete <soete.joel@tiscali.be>
To: "Carlos O'Donell" <carlos@systemhalted.org>
Cc: parisc-linux@parisc-linux.org, Matthew Wilcox <matthew@wil.cx>
Subject: Re: [parisc-linux] Latest palinux crash
Date: Thu, 21 Jul 2005 11:34:22 +0000 [thread overview]
Message-ID: <42DF883E.1020607@tiscali.be> (raw)
In-Reply-To: <20050721043626.GY30182@systemhalted.org>
Carlos O'Donell wrote:
> On Wed, Jul 20, 2005 at 01:22:27PM +0100, Matthew Wilcox wrote:
>
[...]
>
> We need better tools for this... I wonder if we still have lkcd support
> for hppa.
>
> If we had lkcd support would you be willing to run a modified kernel on
> parisc-linux?
>
Afaik unfortunately there wasn't any more support of lkcd on hppa since 2 or 3 years :-(
(iirc Bruno Vidal made this effort in 2.4 but never ported in 2.6 :_( ?
But I totaly agree with you, we would need better tool, specialy when the situation is not clear:
some weeks ago, with jda's help I manage to compile p-l kernel with gcc-4.0 and some fpr constraint.
This kernel seems to be very more stable (passed with success some stress test of mine during severall days when it would crash in
few ours or less when compile with gcc-3.3).
But I also tried to rebuild gcc-4.1 to just reproduce the pb encountered by jda in a c++ test:
efectively, the kernel 'hang' or 'freeze' during this test and it's hard to guess what's hapening;
no more network responds (no ping, no ssh, ...), no more console responds, ...
but pressing TOC button launched well a panic, and unfortunately pim analisys didn't help at all :-?
(fyi: <http://lists.parisc-linux.org/pipermail/parisc-linux/2005-July/026855.html>)
So am I also looking for way to help: lkcd? instrumenting the kernel like kprobes/dprobes? (but not yet hppa support)
Unfortunately, I definetily don't have deep enough knowledge of linux kernel to help more, sorry.
Thanks,
Joel
_______________________________________________
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-07-21 11:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 12:22 [parisc-linux] Latest palinux crash Matthew Wilcox
2005-07-21 4:36 ` Carlos O'Donell
2005-07-21 11:34 ` Joel Soete [this message]
2005-07-21 12:47 ` Grant Grundler
2005-07-21 19:48 ` Joel Soete
2005-07-22 3:14 ` Grant Grundler
2005-07-21 12:30 ` Grant Grundler
2005-07-21 12:48 ` Michael S. Zick
2005-07-21 19:58 ` Joel Soete
2005-07-21 22:43 ` John David Anglin
2005-07-22 13:35 ` Joel Soete
2005-07-26 16:37 ` John David Anglin
2005-08-08 19:29 ` Joel Soete
2005-08-15 14:40 ` Joel Soete
2005-08-15 19:37 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2005-08-16 9:30 Joel Soete
2005-07-25 15:04 Joel Soete
2005-06-25 15:09 [parisc-linux] latest " Matthew Wilcox
2005-06-27 17:29 ` 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=42DF883E.1020607@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=carlos@systemhalted.org \
--cc=matthew@wil.cx \
--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 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.