linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: David Ford <david@blue-labs.org>
Cc: Alan Cox <laughing@shared-source.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.5-ac9
Date: Wed, 06 Jun 2001 00:39:08 -0400	[thread overview]
Message-ID: <3B1DB3EC.AF7034@mandrakesoft.com> (raw)
In-Reply-To: <20010605234928.A28971@lightning.swansea.linux.org.uk> <3B1DB270.6070603@blue-labs.org>

David Ford wrote:
>  >>EIP; c01269f9 <proc_getdata+4d/154>   <=====
> Trace; c01b1021 <read_eeprom+131/1a8>
> Trace; c01b1c43 <rtl8139_tx_timeout+143/148>
> Trace; c01b2643 <rtl8139_interrupt+5f/170>
> Trace; c0137fc0 <__emul_lookup_dentry+a4/fc>
> Trace; c0138871 <open_namei+4d1/560>
> Trace; c0167ccb <leaf_define_dest_src_infos+1a7/1ac>
> Trace; c012e389 <do_readv_writev+15d/228>
> Trace; c012e2c2 <do_readv_writev+96/228>

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?  It uses /proc/ksyms by default, which is incorrect for most
postmortem ksymoops runs...

rtl8139_interrupt doesn't call tx_timeout, which doesn't call
read_eeprom, which doesn't call proc_getdata.

-- 
Jeff Garzik      | An expert is one who knows more and more about
Building 1024    | less and less until he knows absolutely everything
MandrakeSoft     | about nothing.

  reply	other threads:[~2001-06-06  4:39 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 [this message]
2001-06-06  4:55     ` David Ford
2001-06-06  5:25       ` Keith Owens
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=3B1DB3EC.AF7034@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=david@blue-labs.org \
    --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 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).