From: Keith Owens <kaos@ocs.com.au>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: OOps - very obscure
Date: Thu, 25 Jan 2001 08:18:29 +1100 [thread overview]
Message-ID: <6789.980371109@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Wed, 24 Jan 2001 16:59:19 BST." <20010124165919.C15348@paradigm.rfc822.org>
On Wed, 24 Jan 2001 16:59:19 +0100,
Florian Lohoff <flo@rfc822.org> wrote:
>Code: (Bad address in epc)
>Warning (Oops_code): trailing garbage ignored on Code: line
> Text: 'Code: (Bad address in epc)'
> Garbage: 'ress in epc)'
>Warning (Oops_code_values): Code looks like message, not hex digits. No disassembly attempted.
>I guess the "Garbage" stuff has to be fixed in ksymoops
ksymoops understands "(Bad EIP value.*)", it does not know about "(Bad
address in epc)". I will add it to ksymoops 2.4.1.
next prev parent reply other threads:[~2001-01-24 21:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 15:30 OOps - very obscure Florian Lohoff
2001-01-24 15:59 ` Florian Lohoff
2001-01-24 16:22 ` Florian Lohoff
2001-01-24 21:18 ` Keith Owens [this message]
2001-01-25 12:43 ` Florian Lohoff
2001-01-25 18:59 ` Jun Sun
2001-01-25 19:22 ` Florian Lohoff
2001-01-25 15:55 ` [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call Florian Lohoff
2001-01-25 15:55 ` Florian Lohoff
2001-01-25 16:34 ` Origin 200 crash nick
2001-01-25 18:28 ` [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call Joe deBlaquiere
2001-01-25 19:35 ` Joe deBlaquiere
2001-01-25 22:19 ` Ralf Baechle
2001-01-26 0:53 ` Joe deBlaquiere
2001-01-26 10:21 ` Maciej W. Rozycki
2001-01-26 15:41 ` Joe deBlaquiere
2001-01-26 21:16 ` Ralf Baechle
2001-01-27 7:20 ` Maciej W. Rozycki
2001-01-26 21:15 ` Ralf Baechle
2001-01-27 7:28 ` Maciej W. Rozycki
2001-01-27 19:42 ` Ralf Baechle
2001-01-29 15:03 ` Maciej W. Rozycki
2001-01-26 20:01 ` Jun Sun
2001-01-26 20:38 ` Joe deBlaquiere
2001-01-26 21:02 ` Jun Sun
2001-04-04 22:13 ` Florian Lohoff
2001-02-19 13:11 ` strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call) Wichert Akkerman
2001-02-19 19:52 ` newbie question Can Altineller
2001-02-20 7:06 ` David Jez
2001-02-20 20:26 ` Mike McDonald
2001-02-20 20:30 ` nick
2001-02-20 20:53 ` Ralf Baechle
2001-02-20 20:41 ` strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call) Ralf Baechle
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=6789.980371109@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
/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