From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: kernel oops on wireless-testing
Date: Tue, 10 Jul 2012 14:38:13 +0200 [thread overview]
Message-ID: <4FFC2235.5080801@broadcom.com> (raw)
In-Reply-To: <1341918560.4475.10.camel@jlt3.sipsolutions.net>
On 07/10/2012 01:09 PM, Johannes Berg wrote:
> On Tue, 2012-07-10 at 13:01 +0200, Arend van Spriel wrote:
>> Recently I get a kernel oops in nightly test on the wireless-testing
>> tree (see below). This is on 3.5-rc4 kernel based on following commit:
>>
>> commit a5b846deb890fbea72267e4e7d98f8f022959d14
>> Merge: 1532e30 bf52592
>> Author: John W. Linville <linville@tuxdriver.com>
>> Date: Wed Jun 27 16:15:29 2012 -0400
>>
>> Merge branch 'master' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/linvi
>>
>> Can this be expected (eg. recent change in struct wiphy) ? I will built
>> a new kernel from wireless-testing and see if that helps.
>
> Why would you expect this? Are you running new modules on an old kernel?
>
> johannes
>
>
Yes. I do not built the whole kernel upon wireless-testing update. So I
generally built cfg80211, mac80211, and our own drivers. That mostly
works except that (part of) wext can only be built in-kernel.
btw, moving to a newer kernel worked for me so it is a user issue. Sorry
for the noise.
Gr. AvS
prev parent reply other threads:[~2012-07-10 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 11:01 kernel oops on wireless-testing Arend van Spriel
2012-07-10 11:09 ` Johannes Berg
2012-07-10 12:38 ` Arend van Spriel [this message]
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=4FFC2235.5080801@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).