From: Joel Soete <soete.joel@tiscali.be>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Carlos O'Donell <carlos@systemhalted.org>,
Matthew Wilcox <matthew@wil.cx>,
parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Latest palinux crash
Date: Thu, 21 Jul 2005 19:48:23 +0000 [thread overview]
Message-ID: <42DFFC07.5080607@tiscali.be> (raw)
In-Reply-To: <20050721124713.GB27330@colo.lackof.org>
Grant Grundler wrote:
> On Thu, Jul 21, 2005 at 11:34:22AM +0000, Joel Soete wrote:
>
>>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).
>
>
> Joel,
> This is good news. Thanks for trying this out.
>
>
>>...
>>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>)
>
>
> In 026855.html you wrote you didn't save the System.map.
>
Yes my script analysis is based on the famous dump_analyser.sh so still grab the label into System.map
but insn match well the address ;-) (today I learn more about addr2line and thought that it would help to get rid of this pb :-)
>
>>So am I also looking for way to help: lkcd? instrumenting the kernel like
>>kprobes/dprobes? (but not yet hppa support)
>
>
> kprobes will need more support for runtime patching of the code.
> It's not trivial to do that given the VIVT caches on parisc.
(Sorry: VIVT?)
> It's certainly possible though since I know HPUX does that.
> But it also means changing the kernel text to RW or using
> absolute stores/icache flushing to modified the kernel instructions.
>
well so not sure that kprobe was already for p-l but I find this paper
<http://www-128.ibm.com/developerworks/linux/library/l-graphvis/> on gcc fnct instrumentation very attractive
and looking for something like this for the kernel: in paper the link to kprobes is dead but resent me to dprobes on sf.net?
>
>
>>Unfortunately, I definetily don't have deep enough knowledge of linux
>>kernel to help more, sorry.
>
>
> I only know enough to be dangerous to be people who know less. :^)
>
> grant
>
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 19:48 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
2005-07-21 12:47 ` Grant Grundler
2005-07-21 19:48 ` Joel Soete [this message]
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=42DFFC07.5080607@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=carlos@systemhalted.org \
--cc=grundler@parisc-linux.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.