From: Will Simoneau <simoneau@ele.uri.edu>
To: sparclinux@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [sparc64] 2.6.18 unaligned acccess in ehci_hub_control
Date: Wed, 20 Sep 2006 13:21:23 -0400 [thread overview]
Message-ID: <20060920172123.GA9334@ele.uri.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
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.
According to gdb (my first time using it...),
drivers/usb/host/ehci-hub.c:280 is to blame:
(gdb) list *ehci_hub_control+0x350
0x8d0 is in ehci_hub_control (drivers/usb/host/ehci-hub.c:280).
275 struct usb_hub_descriptor *desc
276 ) {
277 int ports = HCS_N_PORTS (ehci->hcs_params);
278 u16 temp;
279
280 desc->bDescriptorType = 0x29;
281 desc->bPwrOn2PwrGood = 10; /* ehci 1.0, 2.3.9 says 20ms max */
282 desc->bHubContrCurrent = 0;
283
284 desc->bNbrPorts = ports;
System is a Sun U80 4x450 with 2.5G and a USB2 PCI card. GCC for the
kernel is 4.1.1 (with gentoo patchset). The only USB2 device is an
external Sony dual layer DVD writer.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-09-20 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 17:21 Will Simoneau [this message]
2006-09-20 17:56 ` [sparc64] 2.6.18 unaligned acccess in ehci_hub_control David Miller
2006-09-21 10:37 ` Mikael Pettersson
2006-09-21 20:51 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
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=20060920172123.GA9334@ele.uri.edu \
--to=simoneau@ele.uri.edu \
--cc=linux-kernel@vger.kernel.org \
--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