From: Bob Copeland <me@bobcopeland.com>
To: Dan McGee <dpmcgee@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless@vger.kernel.org, Michael Buesch <mb@bu3sch.de>
Subject: Re: Kernel oops when loading ath5k from compat-wireless in 2.6.27
Date: Sun, 16 Nov 2008 11:52:13 -0500 [thread overview]
Message-ID: <20081116165213.GC14126@hash.localnet> (raw)
In-Reply-To: <449c10960811160838h70fd1852g66d8a51c7551530b@mail.gmail.com>
On Sun, Nov 16, 2008 at 10:38:39AM -0600, Dan McGee wrote:
> On Sun, Nov 16, 2008 at 10:20 AM, Bob Copeland <me@bobcopeland.com> wrote:
> > As you can see, the modules think "phy0" should be at offset 164, but
> > it's really at 160.
>
> > Also I noticed the original config had CONFIG_DYNAMIC_FTRACE=y, unfortunately
> > turning that off didn't seem to change anything (hmm, I didn't get a build
> > bug, was the breakage fixed in 2.6.27.y?)
>
> Note that HAVE is set if the architecture supports it; CONFIG_FTRACE
> itself was turned off (and CONFIG_DYNAMIC_FTRACE is not even present):
> $ grep FTRACE .config
> CONFIG_HAVE_FTRACE=y
> CONFIG_HAVE_DYNAMIC_FTRACE=y
> # CONFIG_FTRACE is not set
Oh, you are right. Thanks. I probably won't be able to do any more
testing today but I would suggest trying to turn off wireless-related
options in the main kernel config and see if you can get it working
(start with cfg80211 and its dependencies...)
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2008-11-16 16:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 5:46 Kernel oops when loading ath5k from compat-wireless in 2.6.27 Dan McGee
2008-11-14 6:17 ` Luis R. Rodriguez
2008-11-14 17:02 ` Bob Copeland
2008-11-14 17:37 ` Luis R. Rodriguez
2008-11-14 17:49 ` Bob Copeland
2008-11-14 18:06 ` Luis R. Rodriguez
2008-11-14 18:13 ` Sujith
2008-11-14 18:29 ` Luis R. Rodriguez
2008-11-14 18:33 ` Sujith
2008-11-14 18:37 ` Luis R. Rodriguez
2008-11-14 19:33 ` Dan McGee
2008-11-14 20:33 ` Bob Copeland
2008-11-14 20:41 ` Luis R. Rodriguez
2008-11-14 21:13 ` Luis R. Rodriguez
2008-11-15 0:25 ` Dan McGee
2008-11-15 0:36 ` Luis R. Rodriguez
2008-11-15 2:05 ` Dan McGee
2008-11-15 2:29 ` Bob Copeland
2008-11-15 2:57 ` Dan McGee
2008-11-15 6:30 ` Dan McGee
[not found] ` <449c10960811142229v77ea85f4nf898d447c7e63422@mail.gmail.com>
2008-11-15 18:19 ` Bob Copeland
2008-11-16 0:12 ` Dan McGee
2008-11-15 0:38 ` Bob Copeland
2008-11-14 18:34 ` Bob Copeland
2008-11-16 2:11 ` Dan McGee
2008-11-16 2:38 ` Dan McGee
2008-11-16 5:48 ` Luis R. Rodriguez
2008-11-16 5:53 ` Bob Copeland
2008-11-16 6:05 ` Luis R. Rodriguez
2008-11-16 6:06 ` Luis R. Rodriguez
2008-11-16 6:15 ` Luis R. Rodriguez
2008-11-16 16:20 ` Bob Copeland
2008-11-16 16:38 ` Dan McGee
2008-11-16 16:52 ` Bob Copeland [this message]
2008-11-16 18:01 ` Dan McGee
2008-11-16 18:05 ` Johannes Berg
2008-11-16 18:20 ` Luis R. Rodriguez
2008-11-16 5:55 ` Bob Copeland
2008-11-14 13:18 ` Bob Copeland
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=20081116165213.GC14126@hash.localnet \
--to=me@bobcopeland.com \
--cc=dpmcgee@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=mcgrof@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).