From: George France <france@handhelds.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jay Thorne <Yohimbe@userfriendly.org>
Subject: Re: PATCH - ksymoops on Alpha - 2.4.5-ac3
Date: Tue, 29 May 2001 01:00:56 -0400 [thread overview]
Message-ID: <01052901005607.17841@shadowfax.middleearth> (raw)
In-Reply-To: <4172.991093202@ocs3.ocs-net>
In-Reply-To: <4172.991093202@ocs3.ocs-net>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
> George France <france@handhelds.org> wrote:
> >Here is a trivial patch that will make ksymoops work again on Alpha.
Cleaner patch.
diff -urN linux-2.4.5-ac3-orig/arch/alpha/kernel/traps.c
linux-2.4.5/arch/alpha/kernel/traps.c
--- linux-2.4.5-ac3-orig/arch/alpha/kernel/traps.c Thu May 24 17:24:37 2001
+++ linux-2.4.5/arch/alpha/kernel/traps.c Tue May 29 00:42:40 2001
@@ -286,17 +286,11 @@
continue;
if (tmp >= (unsigned long) &_etext)
continue;
- /*
- * Assume that only the low 24-bits of a kernel text address
- * is interesting.
- */
- printk("%6x%c", (int)tmp & 0xffffff, (++i % 11) ? ' ' : '\n');
-#if 0
+ printk("%lx%c", tmp, ' ');
if (i > 40) {
printk(" ...");
break;
}
-#endif
}
printk("\n");
}
>
> Thanks for that. Now if you can just persuade the Alpha people to
> print the 'Code:' line in the same format as other architectures then
> ksymoops can decode the instructions as well. If Alpha wants to
> include its own instruction decoder as well then that is up to them but
> I would appreciate a standard 'Code:' line being printed first.
Could you send me an oops with the standard 'Code:' line?
Best Regards,
--George
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch-ksymoops --]
[-- Type: text/english; name="patch-ksymoops", Size: 613 bytes --]
diff -urN linux-2.4.5-ac3-orig/arch/alpha/kernel/traps.c linux-2.4.5/arch/alpha/kernel/traps.c
--- linux-2.4.5-ac3-orig/arch/alpha/kernel/traps.c Thu May 24 17:24:37 2001
+++ linux-2.4.5/arch/alpha/kernel/traps.c Tue May 29 00:42:40 2001
@@ -286,17 +286,11 @@
continue;
if (tmp >= (unsigned long) &_etext)
continue;
- /*
- * Assume that only the low 24-bits of a kernel text address
- * is interesting.
- */
- printk("%6x%c", (int)tmp & 0xffffff, (++i % 11) ? ' ' : '\n');
-#if 0
+ printk("%lx%c", tmp, ' ');
if (i > 40) {
printk(" ...");
break;
}
-#endif
}
printk("\n");
}
next prev parent reply other threads:[~2001-05-29 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 21:05 PATCH - ksymoops on Alpha - 2.4.5-ac3 George France
2001-05-28 23:40 ` Keith Owens
2001-05-29 5:00 ` George France [this message]
2001-05-29 6:26 ` Keith Owens
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=01052901005607.17841@shadowfax.middleearth \
--to=france@handhelds.org \
--cc=Yohimbe@userfriendly.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.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