From: David Miller <davem@davemloft.net>
To: simoneau@ele.uri.edu
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: Re: [sparc64] 2.6.18 unaligned accesses in eth1394
Date: Thu, 12 Oct 2006 14:34:42 -0700 (PDT) [thread overview]
Message-ID: <20061012.143442.105431995.davem@davemloft.net> (raw)
In-Reply-To: <20061012143726.GD21243@ele.uri.edu>
From: Will Simoneau <simoneau@ele.uri.edu>
Date: Thu, 12 Oct 2006 10:37:26 -0400
> This will be difficult as the machine in question isn't one I want to
> reboot too often. The running kernel and modules are compiled with debug
> info, though; if I send you the relevant .o files will that help?
The reason I asked for it in the image is because I want to tell gdb
"x/10i 0xZZZZZ" using the exact program counters in the dumps and get
exactly the instruction that is faulting.
That is very difficult with modules since they can get loaded at any
address, and the gdb listings you provided with those symbol-relative
addresses were non-sensible, and that's why I can't match the true
cause up right now.
So whilst I can try with a module image, you'd have to do things like
tell me exactly what is the base address of the loaded kernel module
at the time of the message trigger and other non-trivial stuff like
that to get me the debugging info I want to fix this.
Thanks.
prev parent reply other threads:[~2006-10-12 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 21:15 [sparc64] 2.6.18 unaligned accesses in eth1394 Will Simoneau
2006-10-05 22:22 ` David Miller
2006-10-10 1:36 ` David Miller
2006-10-10 13:29 ` Will Simoneau
2006-10-10 22:17 ` David Miller
2006-10-11 12:33 ` Stefan Richter
2006-10-28 0:12 ` David Miller
2006-10-28 6:46 ` Stefan Richter
2006-10-12 14:37 ` Will Simoneau
2006-10-12 21:34 ` David Miller [this message]
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=20061012.143442.105431995.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=simoneau@ele.uri.edu \
--cc=sparclinux@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