From: Will Simoneau <simoneau@ele.uri.edu>
To: David Miller <davem@davemloft.net>
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 10:37:26 -0400 [thread overview]
Message-ID: <20061012143726.GD21243@ele.uri.edu> (raw)
In-Reply-To: <20061010.151751.90998930.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On 15:17 Tue 10 Oct , David Miller wrote:
> From: Will Simoneau <simoneau@ele.uri.edu>
> Date: Tue, 10 Oct 2006 09:29:43 -0400
>
> > I still get:
> >
> > Kernel unaligned access at TPC[10162164] ether1394_reset_priv+0x2c/0xe0 [eth1394]
> > Kernel unaligned access at TPC[10163148] ether1394_data_handler+0xdd0/0x1060 [eth1394]
> >
> > The second one triggers on every packet received, the first only triggers once in a while.
> >
> > If you want more gdb info or a disassembly just ask.
>
> Hmmm, can you do me a favor? Build ieee1394 and eth1394 statically
> into your kernel, reproduce, and post the kernel log messages
> and the vmlinux image somewhere where I can fetch them.
>
> I should be able to fix this once I have that.
>
> Thanks a lot.
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?
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-12 14:37 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 [this message]
2006-10-12 21:34 ` David Miller
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=20061012143726.GD21243@ele.uri.edu \
--to=simoneau@ele.uri.edu \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--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