From: Johannes Berg <johannes@sipsolutions.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Alignment issue with 4965 and 2.6.28-rc3
Date: Mon, 03 Nov 2008 08:25:00 +0100 [thread overview]
Message-ID: <1225697100.3619.21.camel@johannes.berg> (raw)
In-Reply-To: <DFAA4A8C-F8D5-4D08-9C6E-8BB65E3BCFC2@holtmann.org> (sfid-20081103_011401_708646_769D4445)
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Mon, 2008-11-03 at 01:13 +0100, Marcel Holtmann wrote:
> Hi guys,
>
> so I switched to a 2.6.28-rc3 kernel and after less then 10 minutes
> uptime my dmesg is full of warnings. I enabled a bunch of debugging
> options and the first warning that I see is the alignment warning from
> mac80211. I have kerneloops enabled and all warnings are posted there.
> For reference I attach my full dmesg and config.
You can ignore the alignment warning, it's been decided that Intel
driver/firmware/hw will not work properly on platforms that cannot do
unaligned loads efficiently. I've tried sending a patch to add
CONFIG_HAVE_EFFICIENT_ALIGNED_ACCESS or something like that so that we
can fix it up if that is unset or make the driver depend on it, but it
hasn't stuck so far, so for now, ignore the warning and don't try to use
Intel wireless hw on platforms that don't like unaligned loads.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-11-03 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 0:13 Alignment issue with 4965 and 2.6.28-rc3 Marcel Holtmann
2008-11-03 7:25 ` Johannes Berg [this message]
2008-11-03 7:35 ` David Miller
2008-11-03 7:39 ` Johannes Berg
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=1225697100.3619.21.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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