Bug 33232 - WARNING: at /build/buildd/linux-2.6.38/net/wireless/scan.c:591 cfg80211_inform_bss_frame 0x1da/0x1f0 [cfg80211]()
Summary: WARNING: at /build/buildd/linux-2.6.38/net/wireless/scan.c:591 cfg80211_infor...
Status: CLOSED CODE_FIX
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 low
Assignee: networking_wireless@kernel-bugs.osdl.org
URL: https://bugs.launchpad.net/ubuntu/+so...
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-13 18:48 UTC by njin
Modified: 2012-06-14 17:50 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.38-8.42
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
zd1211rw: fix invalid signal values from device (1.65 KB, patch)
2011-04-18 18:53 UTC, Jussi Kivilinna
Details | Diff

Description njin 2011-04-13 18:48:34 UTC
Hello
Reported just to keep track, system seems to work.

- latest updates installed
- window with stop sign displayed on desktop every time after full loading re kernel developed a serious problem ....
- os still functional in spite of above mssge (can perform updates, use mail, browse)

ProblemType: KernelOops
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42

[   52.942507] WARNING: at /build/buildd/linux-2.6.38/net/wireless/scan.c:591 cfg80211_inform_bss_frame+0x1da/0x1f0 [cfg80211]()
[   52.942509] Hardware name: GA-MA78GM-S2HP
[   52.942510] Modules linked in: binfmt_misc nls_iso8859_1 nls_cp437 vfat fat snd_hda_codec_hdmi arc4 snd_hda_codec_realtek snd_usb_audio snd_hda_intel snd_hda_codec zd1211rw ppdev mac80211 snd_pcm snd_hwdep snd_usbmidi_lib snd_seq_midi snd_rawmidi snd_seq_midi_event radeon snd_seq snd_timer psmouse snd_seq_device cfg80211 serio_raw uvcvideo videodev v4l2_compat_ioctl32 ttm snd k10temp edac_core drm_kms_helper edac_mce_amd parport_pc sp5100_tco i2c_piix4 drm xhci_hcd soundcore snd_page_alloc i2c_algo_bit lp parport usbhid hid usb_storage uas ahci floppy firewire_ohci firewire_core crc_itu_t r8169 pata_atiixp libahci
[   52.942537] Pid: 0, comm: kworker/0:1 Not tainted 2.6.38-8-generic #42-Ubuntu
[   52.942539] Call Trace:
[   52.942541]  <IRQ>  [<ffffffff81065cef>] ? warn_slowpath_common+0x7f/0xc0
[   52.942548]  [<ffffffff81065d4a>] ? warn_slowpath_null+0x1a/0x20
[   52.942553]  [<ffffffffa033403a>] ? cfg80211_inform_bss_frame+0x1da/0x1f0 [cfg80211]
[   52.942557]  [<ffffffff8144d2d6>] ? ehci_qtd_alloc.clone.58+0x16/0x60
[   52.942560]  [<ffffffff814377bc>] ? usb_hcd_link_urb_to_ep+0x8c/0xc0
[   52.942569]  [<ffffffffa038b875>] ? ieee80211_bss_info_update+0x55/0x220 [mac80211]
[   52.942574]  [<ffffffffa038bb58>] ? ieee80211_scan_rx+0x118/0x190 [mac80211]
[   52.942582]  [<ffffffffa03a0177>] ? ieee80211_prepare_and_rx_handle+0x217/0x260 [mac80211]
[   52.942589]  [<ffffffffa03a035f>] ? __ieee80211_rx_handle_packet+0x19f/0x300 [mac80211]
[   52.942596]  [<ffffffffa03a05da>] ? ieee80211_rx+0x11a/0x1d0 [mac80211]
[   52.942598]  [<ffffffff81450944>] ? ehci_irq+0x174/0x230
[   52.942603]  [<ffffffffa0386c11>] ? ieee80211_tasklet_handler+0xd1/0xe0 [mac80211]
[   52.942605]  [<ffffffff8106cc43>] ? tasklet_action+0x73/0x120
[   52.942607]  [<ffffffff8106d538>] ? __do_softirq+0xa8/0x1c0
[   52.942610]  [<ffffffff81030518>] ? ack_apic_level+0x78/0x1a0
[   52.942613]  [<ffffffff8100cf1c>] ? call_softirq+0x1c/0x30
[   52.942615]  [<ffffffff8100ea45>] ? do_softirq+0x65/0xa0
[   52.942617]  [<ffffffff8106d755>] ? irq_exit+0x85/0x90
[   52.942620]  [<ffffffff815caec6>] ? do_IRQ+0x66/0xe0
[   52.942622]  [<ffffffff815c3213>] ? ret_from_intr+0x0/0x15
[   52.942623]  <EOI>  [<ffffffff810d975b>] ? rcu_needs_cpu+0x6b/0x270
[   52.942628]  [<ffffffff81037f0b>] ? native_safe_halt+0xb/0x10
[   52.942631]  [<ffffffff81014801>] ? default_idle+0x41/0xe0
[   52.942634]  [<ffffffff8100a266>] ? cpu_idle+0xa6/0xf0
[   52.942636]  [<ffffffff815bc743>] ? start_secondary+0xbc/0xbe
[   52.942638] ---[ end trace 683bef0bfcfd6f92 ]---

Others log files in the linked Launchpad URL

Thanks
Fabio
Comment 1 Jussi Kivilinna 2011-04-18 18:53:18 UTC
Created attachment 54622 [details]
zd1211rw: fix invalid signal values from device

This patch to see if zd1211rw is source of the problem.
Comment 2 peter b 2011-04-20 18:35:49 UTC
hello Jussi,

I'm the natty user that filed the initial bug report; have been asked by Fabio to contact this site directly . here below the results of proposed patch apply procedure
----- 

hello Fabio,

I tried several ways ie the enclosed code stripped - just starting with diff -- etc, etc AND with all explanation ie zd1211rw: etc, etc.

results

root@GIGA-slow-1104:/home/peter# patch -p1 < zd1211rw-kpatch
patching file drivers/net/wireless/zd1211rw/zd_mac.c
Hunk #1 FAILED at 160.
Hunk #2 FAILED at 461.
Hunk #3 FAILED at 982.
3 out of 3 hunks FAILED -- saving rejects to file drivers/net/wireless/zd1211rw/zd_mac.c.rej
root@GIGA-slow-1104:/home/peter# patch -p1 -i zd1211rw-kpatch
patching file drivers/net/wireless/zd1211rw/zd_mac.c
Hunk #1 FAILED at 160.
Hunk #2 FAILED at 461.
Hunk #3 FAILED at 982.
3 out of 3 hunks FAILED -- saving rejects to file drivers/net/wireless/zd1211rw/zd_mac.c.rej
root@GIGA-slow-1104:/home/peter# exit

did I make any mistake by copy/paste the code to an empty file ? then apply the patch from that file ?
I tried to find the zd_mac.c.rej file in drivers/net/wireless/zd1211rw ; there is no such file BUT the ...ko .

regards.
-----

AND
-----

sorry, I forgot

when patch applied using the recovery/terminal option boot the results were same as above.

dmesgapr20 file attached.

-----

the above comments can be seen on

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759986

the file dmesgapr20 above can be seen/downloaded from there (I did not attach it here - should I have ?)
Comment 3 John W. Linville 2011-06-28 18:16:09 UTC
The patch in question is queued for 3.1.  You can test it by building the wireless-next-2.6 tree:

   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git

Please try that and give feedback here.  Alternatively, you will have to wait until the 3.1 kernel is released (in 4+ months).

Note You need to log in before you can comment on or make changes to this bug.