From: Mikael Pettersson <mikpe@it.uu.se>
To: David Miller <davem@davemloft.net>
Cc: simoneau@ele.uri.edu, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [sparc64] 2.6.18 unaligned acccess in ehci_hub_control
Date: Thu, 21 Sep 2006 12:37:09 +0200 [thread overview]
Message-ID: <17682.27477.995475.57130@alkaid.it.uu.se> (raw)
In-Reply-To: <20060920.105659.128612840.davem@davemloft.net>
David Miller writes:
> From: Will Simoneau <simoneau@ele.uri.edu>
> Date: Wed, 20 Sep 2006 13:21:23 -0400
>
> > I upgraded from 2.6.17.7 to 2.6.18 today, and in dmesg I have 5 of these
> > messages in a row:
> >
> > Kernel unaligned access at TPC[100be8c8] ehci_hub_control+0x350/0x680 [ehci_hcd]
> >
> > This message wasn't there before... I suppose it is pretty harmless as
> > the kernel is supposed to handle unaligned accesses (right?) but this is
> > the first time it's happened.
>
> Yes, I've been meaning to send Greg KH patches to fix these
> cases, thanks for reminding me about it.
I don't think it's harmless. My Ultra5 has an add-on PCI USB controller
card (Belkin). A 2.6.18-rc kernel compiled with gcc-4.1.1 will throw a few
unaligned accesses when I initialise USB by inserting a USB memory stick.
Removing the memory stick then results in PCI errors and other breakage.
The same kernel compiled with gcc-3.4.6 has no problems at all, so I've
been assuming it's a gcc-4 issue and not a kernel issue.
/Mikael
next prev parent reply other threads:[~2006-09-21 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 17:21 Will Simoneau
2006-09-20 17:56 ` David Miller
2006-09-21 10:37 ` Mikael Pettersson [this message]
2006-09-21 20:51 ` David Miller
2006-09-22 22:15 Mikael Pettersson
2006-09-22 22:22 ` David Miller
2006-09-24 0:05 ` David Miller
2006-09-24 13:58 Mikael Pettersson
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=17682.27477.995475.57130@alkaid.it.uu.se \
--to=mikpe@it.uu.se \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®