All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jet Chen <jet.chen@intel.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	devel@driverdev.osuosl.org, Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [staging: r8192ee] WARNING: CPU: 0 PID: 1 at net/mac80211/rate.c:43 ieee80211_rate_control_register()
Date: Tue, 27 May 2014 02:07:54 +0800	[thread overview]
Message-ID: <538382FA.8070601@intel.com> (raw)
In-Reply-To: <538374E4.7010401@lwfinger.net>

On 05/27/2014 01:07 AM, Larry Finger wrote:
> On 05/26/2014 09:55 AM, Jet Chen wrote:
> 
> Jet,
> 
>> 0day kernel testing robot got the below dmesg and the first bad commit is
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-next
>> commit 0629f3b8c33899140b48d5897259eab8ebae78ca
>> Author:     Larry Finger <Larry.Finger@lwfinger.net>
>> AuthorDate: Wed May 21 16:25:36 2014 -0500
>> Commit:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> CommitDate: Fri May 23 11:33:56 2014 +0900
>>
>>      staging: r8192ee: Turn on build of the new driver
>>          In addition, this commit contains a TODO file for this driver
>>          Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>>      Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> The splat comes from the driver trying to register a rate-control algorithm that 
> is already registered. That could happen because a driver is calling the 
> registration routine twice, or because more than one driver is using the same 
> routine name. As I think there is code to prevent the former, and I have never 
> seen that splat here, I suspect that more than one driver has used the name. On 
> my real hardware, I can only have one of these devices in the machine at a time.
> 
> Is if possible to test the attached patch to see if it fixes the problem? If 
> not, could you get a listing of the loaded modules at the time of the splat? If 
> this is not the fix, I will try to duplicate it here.
> 
> Thanks,
> 
> Larry
> 

That patch fixes the problem.

Tested-by: Jet Chen <jet.chen@intel.com>

Thanks,
Jet

      reply	other threads:[~2014-05-26 18:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 14:55 [staging: r8192ee] WARNING: CPU: 0 PID: 1 at net/mac80211/rate.c:43 ieee80211_rate_control_register() Jet Chen
2014-05-26 17:07 ` Larry Finger
2014-05-26 18:07   ` Jet Chen [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=538382FA.8070601@intel.com \
    --to=jet.chen@intel.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=fengguang.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.