From: Keith Owens <kaos@ocs.com.au>
To: David Ford <david@blue-labs.org>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Alan Cox <laughing@shared-source.org>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.5-ac9
Date: Wed, 06 Jun 2001 15:25:51 +1000 [thread overview]
Message-ID: <28279.991805151@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 05 Jun 2001 21:55:39 MST." <3B1DB7CB.5090509@blue-labs.org>
On Tue, 05 Jun 2001 21:55:39 -0700,
David Ford <david@blue-labs.org> wrote:
>Quite positive it's the right map file. I used -m and specified the
>exact file.
>
>Jeff Garzik wrote:
>
>>David Ford wrote:
>>
>>> >>EIP; c01269f9 <proc_getdata+4d/154> <=====
>>>Trace; c01b1021 <read_eeprom+131/1a8>
>>
>>This trace looks corrupted to me... are you sure that System.map for the
>>crashed kernel matches -exactly- with the one ksymoops used to decode
>>this?
The trace definitely looks suspect, I cannot see any BUG() calls in
proc_getdata(), even looking at the object code.
Does
objdump --start-address=0xc01269f9 --stop-address=0xc0126a10 vmlinux
show the same code bytes, starting with ud2a? I will be surprised if
it does. If it does not then you definitely have the wrong System.map
for the oops.
next prev parent reply other threads:[~2001-06-06 5:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 22:49 Linux 2.4.5-ac9 Alan Cox
2001-06-06 2:03 ` Keith Owens
2001-06-06 4:32 ` David Ford
2001-06-06 4:39 ` Jeff Garzik
2001-06-06 4:55 ` David Ford
2001-06-06 5:25 ` Keith Owens [this message]
2001-06-06 6:08 ` SCSI is as SCSI don't Alan Olsen
2001-06-06 5:39 ` Greg KH
2001-06-06 8:04 ` Alan Olsen
2001-06-06 6:20 ` Alan Olsen
2001-06-06 7:49 ` Alan Cox
2001-06-07 0:00 ` Alan Olsen
2001-06-06 9:15 ` Linux 2.4.5-ac9 Thomas Sailer
2001-06-06 21:43 ` Alan Cox
2001-06-06 10:51 ` Christoph Hellwig
2001-06-06 11:41 ` Thomas Sailer
2001-06-06 13:40 ` Christoph Hellwig
2001-06-06 14:49 ` Chris Liebman
2001-06-06 17:20 ` Tom Sightler
2001-06-06 21:54 ` Ion Badulescu
2001-06-07 3:30 ` xircom_cb problems Tom Sightler
2001-06-07 8:31 ` Ion Badulescu
2001-06-07 18:40 ` Tom Sightler
2001-06-07 20:29 ` Ion Badulescu
2001-06-08 14:11 ` Tom Sightler
2001-06-08 20:34 ` Ion Badulescu
2001-06-09 1:36 ` Tom Sightler
2001-06-06 22:44 ` Linux 2.4.5-ac9 arjan
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=28279.991805151@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=david@blue-labs.org \
--cc=jgarzik@mandrakesoft.com \
--cc=laughing@shared-source.org \
--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 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.