* Help needed to interpret kernel warning and call trace
@ 2014-09-01 18:28 Amitav Mohanty
2014-09-01 18:41 ` Larry Finger
0 siblings, 1 reply; 5+ messages in thread
From: Amitav Mohanty @ 2014-09-01 18:28 UTC (permalink / raw)
To: linux-wireless
Hey
How do I interpret the following kernel warning?
Sep 01 17:13:30 TSS-ARCH kernel: ------------[ cut here ]------------
Sep 01 17:13:30 TSS-ARCH kernel: WARNING: CPU: 0 PID: 4 at
net/wireless/reg.c:1806 reg_process_hint+0x2d1/0x460 [cfg80211]()
Sep 01 17:13:30 TSS-ARCH kernel: Modules linked in: ctr ccm fuse arc4
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common
videodev iwldvm dell_wmi nvidia
Sep 01 17:13:30 TSS-ARCH kernel: mei_me mei tpm_tis tpm battery video
ac button processor cpufreq_userspace cpufreq_powersave ext4 crc16
mbcache jbd2 sd_mod sr_mod cdrom c
Sep 01 17:13:30 TSS-ARCH kernel: CPU: 0 PID: 4 Comm: kworker/0:0
Tainted: P O 3.16.1-1-ARCH #1
Sep 01 17:13:30 TSS-ARCH kernel: Hardware name: Dell Inc. Latitude
E6520/0J4TFW, BIOS A06 07/11/2011
Sep 01 17:13:30 TSS-ARCH kernel: Workqueue: events reg_todo [cfg80211]
Sep 01 17:13:30 TSS-ARCH kernel: 0000000000000000 00000000a89ed9aa
ffff88022216fd50 ffffffff8152ae6c
Sep 01 17:13:30 TSS-ARCH kernel: 0000000000000000 ffff88022216fd88
ffffffff8106e45d ffff8800c547a300
Sep 01 17:13:30 TSS-ARCH kernel: ffff8800c7e18260 ffff8800c547a31c
ffff88022dc18000 0ffff88022dc1800
Sep 01 17:13:30 TSS-ARCH kernel: Call Trace:
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8152ae6c>] dump_stack+0x4d/0x6f
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8106e45d>]
warn_slowpath_common+0x7d/0xa0
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8106e58a>]
warn_slowpath_null+0x1a/0x20
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffffa048e3c1>]
reg_process_hint+0x2d1/0x460 [cfg80211]
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffffa048e5c9>]
reg_todo+0x79/0x1a0 [cfg80211]
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8108afa8>]
process_one_work+0x168/0x450
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8108b5db>] worker_thread+0x6b/0x550
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8108b570>] ?
init_pwq.part.22+0x10/0x10
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff81091cea>] kthread+0xea/0x100
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff81091c00>] ?
kthread_create_on_node+0x1b0/0x1b0
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff81530b3c>] ret_from_fork+0x7c/0xb0
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff81091c00>] ?
kthread_create_on_node+0x1b0/0x1b0
Sep 01 17:13:30 TSS-ARCH kernel: ---[ end trace ffb56350dc197a6a ]---
Sep 01 17:13:30 TSS-ARCH kernel: cfg80211: Calling CRDA for country: US
Sep 01 17:13:30 TSS-ARCH kernel: ------------[ cut here ]------------
Sep 01 17:13:30 TSS-ARCH kernel: WARNING: CPU: 0 PID: 4 at
net/wireless/reg.c:1806 reg_process_hint+0x2d1/0x460 [cfg80211]()
Sep 01 17:13:30 TSS-ARCH kernel: Modules linked in: ctr ccm fuse arc4
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common
videodev iwldvm dell_wmi nvidia
Sep 01 17:13:30 TSS-ARCH kernel: mei_me mei tpm_tis tpm battery video
ac button processor cpufreq_userspace cpufreq_powersave ext4 crc16
mbcache jbd2 sd_mod sr_mod cdrom c
Sep 01 17:13:30 TSS-ARCH kernel: CPU: 0 PID: 4 Comm: kworker/0:0
Tainted: P W O 3.16.1-1-ARCH #1
Sep 01 17:13:30 TSS-ARCH kernel: Hardware name: Dell Inc. Latitude
E6520/0J4TFW, BIOS A06 07/11/2011
Sep 01 17:13:30 TSS-ARCH kernel: Workqueue: events reg_todo [cfg80211]
Sep 01 17:13:30 TSS-ARCH kernel: 0000000000000000 00000000a89ed9aa
ffff88022216fd50 ffffffff8152ae6c
Sep 01 17:13:30 TSS-ARCH kernel: 0000000000000000 ffff88022216fd88
ffffffff8106e45d ffff8800c547a300
Sep 01 17:13:30 TSS-ARCH kernel: ffff8800c7e18260 ffff8800c547a31c
ffff88022dc18000 0ffff88022dc1800
Sep 01 17:13:30 TSS-ARCH kernel: Call Trace:
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8152ae6c>] dump_stack+0x4d/0x6f
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8106e45d>]
warn_slowpath_common+0x7d/0xa0
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8106e58a>]
warn_slowpath_null+0x1a/0x20
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffffa048e3c1>]
reg_process_hint+0x2d1/0x460 [cfg80211]
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffffa048e5c9>]
reg_todo+0x79/0x1a0 [cfg80211]
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8108afa8>]
process_one_work+0x168/0x450
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8108b5db>] worker_thread+0x6b/0x550
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff8108b570>] ?
init_pwq.part.22+0x10/0x10
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff81091cea>] kthread+0xea/0x100
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff81091c00>] ?
kthread_create_on_node+0x1b0/0x1b0
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff81530b3c>] ret_from_fork+0x7c/0xb0
Sep 01 17:13:30 TSS-ARCH kernel: [<ffffffff81091c00>] ?
kthread_create_on_node+0x1b0/0x1b0
Sep 01 17:13:30 TSS-ARCH kernel: ---[ end trace ffb56350dc197a6b ]---
Sep 01 17:13:30 TSS-ARCH kernel: cfg80211: Calling CRDA for country: US
Please suggest.
Thanks and regards,
Amitav
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Help needed to interpret kernel warning and call trace
2014-09-01 18:28 Help needed to interpret kernel warning and call trace Amitav Mohanty
@ 2014-09-01 18:41 ` Larry Finger
2014-09-01 18:55 ` Amitav Mohanty
0 siblings, 1 reply; 5+ messages in thread
From: Larry Finger @ 2014-09-01 18:41 UTC (permalink / raw)
To: Amitav Mohanty, linux-wireless
On 09/01/2014 01:28 PM, Amitav Mohanty wrote:
> Hey
>
> How do I interpret the following kernel warning?
>
> Sep 01 17:13:30 TSS-ARCH kernel: ------------[ cut here ]------------
> Sep 01 17:13:30 TSS-ARCH kernel: WARNING: CPU: 0 PID: 4 at
> net/wireless/reg.c:1806 reg_process_hint+0x2d1/0x460 [cfg80211]()
That warning comes from
/*
* Two consecutive Country IE hints on the same wiphy.
* This should be picked up early by the driver/stack
*/
if (WARN_ON(regdom_changes(country_ie_request->alpha2)))
return REG_REQ_OK;
return REG_REQ_ALREADY_SET;
The problem appears to arise in iwldvm, but before anyone devotes very much
effort to finding the cause, you will need to reproduce it without that "P"
taint. From the module list, the offending module appears to be unloaded, but
the taint remains.
Larry
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: Help needed to interpret kernel warning and call trace
2014-09-01 18:41 ` Larry Finger
@ 2014-09-01 18:55 ` Amitav Mohanty
2014-09-01 19:10 ` Larry Finger
0 siblings, 1 reply; 5+ messages in thread
From: Amitav Mohanty @ 2014-09-01 18:55 UTC (permalink / raw)
To: Larry Finger; +Cc: linux-wireless
Hey Larry
Thank you for the prompt reply. I am not a kernel dev. My intension
was to seek help and understand how this impacts my system. I looked
for removing the taint. However, it seems Nvidia driver is the one
that is tainting the kernel. Since this is the laptop I use for work,
I don't think I can remove NVidia driver. If I understand correctly,
using the Nouveau driver instead the proprietary one should remove the
taint. Is there any other way I can help ?
Regards,
Amitav
On Tue, Sep 2, 2014 at 12:11 AM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> On 09/01/2014 01:28 PM, Amitav Mohanty wrote:
>> Hey
>>
>> How do I interpret the following kernel warning?
>>
>> Sep 01 17:13:30 TSS-ARCH kernel: ------------[ cut here ]------------
>> Sep 01 17:13:30 TSS-ARCH kernel: WARNING: CPU: 0 PID: 4 at
>> net/wireless/reg.c:1806 reg_process_hint+0x2d1/0x460 [cfg80211]()
>
> That warning comes from
>
> /*
> * Two consecutive Country IE hints on the same wiphy.
> * This should be picked up early by the driver/stack
> */
> if (WARN_ON(regdom_changes(country_ie_request->alpha2)))
> return REG_REQ_OK;
> return REG_REQ_ALREADY_SET;
>
> The problem appears to arise in iwldvm, but before anyone devotes very much
> effort to finding the cause, you will need to reproduce it without that "P"
> taint. From the module list, the offending module appears to be unloaded, but
> the taint remains.
>
> Larry
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Help needed to interpret kernel warning and call trace
2014-09-01 18:55 ` Amitav Mohanty
@ 2014-09-01 19:10 ` Larry Finger
2014-09-01 19:47 ` Amitav Mohanty
0 siblings, 1 reply; 5+ messages in thread
From: Larry Finger @ 2014-09-01 19:10 UTC (permalink / raw)
To: Amitav Mohanty; +Cc: linux-wireless
On 09/01/2014 01:55 PM, Amitav Mohanty wrote:
> Hey Larry
>
> Thank you for the prompt reply. I am not a kernel dev. My intension
> was to seek help and understand how this impacts my system. I looked
> for removing the taint. However, it seems Nvidia driver is the one
> that is tainting the kernel. Since this is the laptop I use for work,
> I don't think I can remove NVidia driver. If I understand correctly,
> using the Nouveau driver instead the proprietary one should remove the
> taint. Is there any other way I can help ?
Yes, nvidia does taint the kernel. If nouveau works, that would remove the taint.
The warning will have exactly zero impact on your system, other than to pollute
your logs.
Larry
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Help needed to interpret kernel warning and call trace
2014-09-01 19:10 ` Larry Finger
@ 2014-09-01 19:47 ` Amitav Mohanty
0 siblings, 0 replies; 5+ messages in thread
From: Amitav Mohanty @ 2014-09-01 19:47 UTC (permalink / raw)
To: Larry Finger; +Cc: linux-wireless
Thank you for clarifying. Appreciate your help.
Regards,
Amitav
On Tue, Sep 2, 2014 at 12:40 AM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> On 09/01/2014 01:55 PM, Amitav Mohanty wrote:
>> Hey Larry
>>
>> Thank you for the prompt reply. I am not a kernel dev. My intension
>> was to seek help and understand how this impacts my system. I looked
>> for removing the taint. However, it seems Nvidia driver is the one
>> that is tainting the kernel. Since this is the laptop I use for work,
>> I don't think I can remove NVidia driver. If I understand correctly,
>> using the Nouveau driver instead the proprietary one should remove the
>> taint. Is there any other way I can help ?
>
> Yes, nvidia does taint the kernel. If nouveau works, that would remove the taint.
>
> The warning will have exactly zero impact on your system, other than to pollute
> your logs.
>
> Larry
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-09-01 19:47 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-09-01 18:28 Help needed to interpret kernel warning and call trace Amitav Mohanty
2014-09-01 18:41 ` Larry Finger
2014-09-01 18:55 ` Amitav Mohanty
2014-09-01 19:10 ` Larry Finger
2014-09-01 19:47 ` Amitav Mohanty
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).