From: Andrew Morton <akpm@osdl.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: miles.lane@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: OOPS running "ls -l /sys/class/i2c-adapter/*"-- 2.6.12-rc1-mm2
Date: Thu, 24 Mar 2005 23:45:44 -0800 [thread overview]
Message-ID: <20050324234544.135a1eb2.akpm@osdl.org> (raw)
In-Reply-To: <20050325073846.A18596@flint.arm.linux.org.uk>
Russell King <rmk+lkml@arm.linux.org.uk> wrote:
>
> On Thu, Mar 24, 2005 at 08:22:15PM -0800, Andrew Morton wrote:
> > Miles Lane <miles.lane@gmail.com> wrote:
> > > Unable to handle kernel paging request at virtual address 24fc1024
> > > c0198448
> > > *pde = 00000000
> > > Oops: 0000 [#1]
> > > CPU: 0
> > > EIP: 0060:[<c0198448>] Not tainted VLI
> >
> > I wonder why the EIP sometimes doesn't get decoded.
> >
> > > Using defaults from ksymoops -t elf32-i386 -a i386
> > > EFLAGS: 00210206 (2.6.12-rc1-mm2)
>
> ksymoops seems to remove lines from the kernel output that it doesn't
> like.
but. but. There used to be a symbol+0xN/0xM in the EIP: line. Are you
saying that ksymoops rubbed that out and stuck a hex number in there?
> I've seen this many times on ARM, and each time I see an oops
> from a 2.6 kernel which has been ksymoopsed, I always ask the submitter
> to send the original non-ksymoopsed version.
>
> Users need to be re-educated _not_ to use ksymoops.
I wonder if there's something clever we could do to the kallsymsised oops
output so that ksymoops would simply cease to recognise it.
next prev parent reply other threads:[~2005-03-25 7:46 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 12:41 2.6.12-rc1-mm2 Andrew Morton
2005-03-24 14:40 ` 2.6.12-rc1-mm2 Stefano Rivoir
2005-03-24 15:13 ` 2.6.12-rc1-mm2 Manuel Lauss
2005-03-24 15:18 ` 2.6.12-rc1-mm2 Brice Goglin
2005-03-24 15:31 ` 2.6.12-rc1-mm2 Stefano Rivoir
2005-03-24 20:05 ` 2.6.12-rc1-mm2 Andrew Morton
2005-03-24 20:21 ` 2.6.12-rc1-mm2 Brice Goglin
2005-03-25 1:19 ` 2.6.12-rc1-mm2 Alexey Dobriyan
2005-03-24 15:09 ` 2.6.12-rc1-mm2 (build error In function `zft_init') Steven Cole
2005-03-24 15:55 ` 2.6.12-rc1-mm2 (patch to fix build " Steven Cole
2005-03-24 21:49 ` Greg KH
2005-03-24 21:53 ` Andrew Morton
2005-03-24 16:46 ` 2.6.12-rc1-mm2 Lee Revell
2005-03-24 20:17 ` 2.6.12-rc1-mm2 Andrew Morton
2005-03-24 22:31 ` 2.6.12-rc1-mm2 Rafael J. Wysocki
2005-03-24 22:37 ` 2.6.12-rc1-mm2 Rafael J. Wysocki
2005-03-24 23:33 ` 2.6.12-rc1-mm2 Laurent Riffard
2005-03-24 23:49 ` 2.6.12-rc1-mm2 Andrew Morton
2005-03-25 1:00 ` 2.6.12-rc1-mm2 Patrick Mochel
2005-03-25 6:05 ` 2.6.12-rc1-mm2 Greg KH
2005-03-25 18:01 ` 2.6.12-rc1-mm2 Laurent Riffard
2005-05-26 0:29 ` 2.6.12-rc1-mm2 Andrew Morton
2005-05-26 13:58 ` 2.6.12-rc1-mm2 Rafael J. Wysocki
2005-03-25 0:38 ` [2.6 patch] remove exports for oem modules Adrian Bunk
2005-03-25 4:12 ` OOPS running "ls -l /sys/class/i2c-adapter/*"-- 2.6.12-rc1-mm2 Miles Lane
2005-03-25 4:22 ` Andrew Morton
2005-03-25 7:38 ` Russell King
2005-03-25 7:45 ` Andrew Morton [this message]
2005-03-25 7:50 ` Russell King
2005-03-25 8:13 ` Russell King
2005-03-25 12:52 ` Miles Lane
2005-03-25 18:40 ` Andrew Morton
2005-03-25 19:50 ` Jean Delvare
2005-03-26 4:44 ` Miles Lane
2005-03-25 20:53 ` Lee Revell
2005-03-25 21:07 ` Russell King
2005-03-25 21:45 ` [PATCH] make Documentation/oops-tracing.txt relevant to 2.6 [was Re: OOPS running "ls -l /sys/class/i2c-adapter/*"-- 2.6.12-rc1-mm2] Lee Revell
2005-03-25 21:52 ` Russell King
2005-03-25 21:54 ` Lee Revell
2005-03-25 19:26 ` x86-64 preemption fix from IRQ and BKL in 2.6.12-rc1-mm2 Christophe Saout
2005-03-27 0:19 ` [PATCH] Fix preemption off of irq context on x86-64 with PREEMPT_BKL Christophe Saout
2005-03-27 17:28 ` Andi Kleen
2005-03-27 17:26 ` x86-64 preemption fix from IRQ and BKL in 2.6.12-rc1-mm2 Andi Kleen
2005-03-27 18:05 ` Christophe Saout
2005-03-28 15:26 ` Andi Kleen
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=20050324234544.135a1eb2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=rmk+lkml@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).