WARNING: at /build/buildd/linux-2.6.38/net/wireless/scan.c:591 cfg80211_inform_bss_frame 0x1da/0x1f0 [cfg80211]()

Bug #759986 reported by peter b
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Low
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

- 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
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: peter 1704 F.... pulseaudio
 /dev/snd/controlC1: peter 1704 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a002,00100101'
   Controls : 38
   Simple ctrls : 21
Card1.Amixer.info:
 Card hw:1 'J'/'A4 TECH A4 TECH USB2.0 PC Camera J at usb-0000:00:12.2-3, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB0ac8:c40a'
   Controls : 3
   Simple ctrls : 2
Card2.Amixer.info:
 Card hw:2 'HDMI'/'HDA ATI HDMI at 0xfdefc000 irq 50'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100000'
   Controls : 4
   Simple ctrls : 1
Card2.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Wed Apr 13 11:32:40 2011
Failure: oops
Frequency: Once a day.
HibernationDevice: RESUME=UUID=95f2810f-2402-4cce-8570-0f501324f136
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1)
MachineType: Gigabyte Technology Co., Ltd. GA-MA78GM-S2HP
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=d1c63451-5f3a-4400-8502-608cf0346b46 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.50
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.38/net/wireless/scan.c:591 cfg80211_inform_bss_frame+0x1da/0x1f0 [cfg80211]()
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/21/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6b
dmi.board.name: GA-MA78GM-S2HP
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd01/21/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78GM-S2HP:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78GM-S2HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA78GM-S2HP
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
peter b (b1pete) wrote :
Revision history for this message
peter b (b1pete) wrote :

additional info

affects: ubuntu → linux (Ubuntu)
Changed in linux:
importance: Unknown → Low
status: Unknown → Confirmed
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello peter
can you please apply attached patch.
Instructions on:
http://www.kernel.org/doc/Documentation/applying-patches.txt

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux:
status: Confirmed → Incomplete
Revision history for this message
peter b (b1pete) wrote :

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.

Revision history for this message
peter b (b1pete) wrote :

sorry, I forgot

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

dmesgapr20 file attached.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello peter
can you please contact directly the developer repling on :
https://bugzilla.kernel.org/show_bug.cgi?id=33232
Thanks
Fabio

Revision history for this message
peter b (b1pete) wrote :

done Fabio - see comment 2 on #33232 above mentioned.

Revision history for this message
Jussi Kivilinna (jukivili) wrote :

Hello,

Ok, you don't know how to patch and build kernel. Let's try patched compat-wireless instead, to just update wifi-drivers.

Instructions:

1. Enter following commands.

2. > sudo apt-get install build-essential linux-headers-2.6.38-8-generic
3. > wget http://koti.mbnet.fi/axh/kernel/zd1211rw/compat-wireless-2011-05-28-zd1211rw_fix_signal_level.tar.bz2
4. > tar -jxf compat-wireless-2011-05-28-zd1211rw_fix_signal_level.tar.bz2
5. > cd compat-wireless-2011-05-28-zd1211rw_fix_signal_level
6. > make
7. > sudo make install

8. Then reboot and test to see if bug reappears or not.

Revision history for this message
peter b (b1pete) wrote :

thanks for post.

I have personally built kernels in the past just for the fun of it and they worked v well but never maintained/patched them afterwards because of the maintenance they require and I do not have material time for that; I'm not into that, I'm not a kernel developer/maintainer.

linux distributions that I'm using have already built and patched kernels and I prefer that for many reasons (chief being lack of time to dedicate maintaining kernels after I personally built/customized them ) - I use canonical's ubuntu releases.

however, after first post 2011-04-13 the ubuntu kernel updates (new builds) for sure took into account this issue because since the final natty narwhal release there is no sign of any problem with this issue.

............

this just for your info, there is as far as I could see (and experience) a v nagging and old very basic device problem in linux ubuntu releases (I'm just using ubuntu for quite some time ) related to floppy devices. I do not know if that is a linux generic problem or in linux ubuntu releases only. there are quite a few bugs posted on ubuntu launchpad related to floppy devices. one of them, if interested, is

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

I do know that that is a totally different topic but .... because you're a first/top line developer of linux generic I said to myself that maybe, just maybe, you'll be interested of looking into it and hopefully bring to a conclusion this issue if it is related to linux generic.

just let me know if I can do anything more on this floppy issue so that linux will NOT be looked upon by new users, after discovered, that they like linux BUT are happier with win because ALL basic devices on their pc function without flaw.

Revision history for this message
Seth Forshee (sforshee) wrote :

A build with the patch applied is available at:

http://people.canonical.com/~sforshee/lp759986/linux-2.6.38-8.42~lp769986v201106011610/

Please test and report back your results here. Thanks!

Revision history for this message
peter b (b1pete) wrote :

@Seth Forshee

thank you for post.

yes, I'd like v much to get this new build in place (on my pc); currently I have

uname -a
Linux unity1104-slowGIGA 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

or in summary

linux-image-2.6.38.8-generic 2.6.38.8.42
linux-headers-2.6.38.8-generic 2.6/38.8.42

linux-image-generic 2.6.38.8.22
linux-headers-generic 2.6.38.22

the conventional way of building new kernels, if I remember well, is something, + or -, along this

a kernel patch no doubt require a new kernel build that in turn requires, first, the current kernel source downloaded and second the patch file

I could see the patch on your post here

0001-zd1211rw-fix-invalid-signal-values-from-device.patch

however, where from can I get linux-image-2.6.38.8-generic 2.6.38.8.42 source pls ?

once I have the 2 packages (kernel source and patch) then

apply the patch to drivers/net/wireless/zd1211rw/zd_mac.c
cp -vi /boot/config-`uname -r` .config
make-menuconfig
fakeroot make-kpkg –append-to-version=patched kernel_image
dpkg -i (kernel image created)
mkinitrd ??? (not sure of entire cmd)

now, I could see in the post there are already .deb files for

linux-image-2.6.38-8-generic_2.6.38-8.42~lp769986v201106011610_amd64.deb
linux-headers-2.6.38-8-generic_2.6.38-8.42~lp769986v201106011610_amd64.deb

I never installed/upgraded kernels and headers by means of .deb files. I require some help pls ie

- do

linux-image-generic 2.6.38.8.22
linux-headers-generic 2.6.38.22

have to be upgraded too ? if yes should I apply Jussi's #8 procedure to linux-image-generic 2.6.38.8.22 ?
how about the linux-headers-generic 2.6.38.22 ?

- do cmds like

sudo dpkg -i linux-image-2.6.38-8-generic_2.6.38-8.42~lp769986v201106011610_amd64.deb
sudo dpkg -i linux-headers-2.6.38-8-generic_2.6.38-8.42~lp769986v201106011610_amd64.deb

suffice to get the job done ?

- what about linux-headers-2.6.38-8_2.6.38-8.42~lp769986v201106011610_all.deb ?
should it be installed too in the same way as the 2 above ?

sorry, I do not want to jump 'head first' so to speak and wreck my good installation BUT I'M v keen in learning howto install new kernel builds and headers .deb ON EXISTING ubuntu good installs. I do know that applying successfully patches to kernels in not an easy task - there are lots of things that have to be done/attended to in order to achieve success. your help is appreciated. tu.

Revision history for this message
Seth Forshee (sforshee) wrote : Re: [Bug 759986] Re: WARNING: at /build/buildd/linux-2.6.38/net/wireless/scan.c:591 cfg80211_inform_bss_frame 0x1da/0x1f0 [cfg80211]()

On Thu, Jun 02, 2011 at 04:20:00AM -0000, peter b wrote:
> - do cmds like
>
> sudo dpkg -i linux-image-2.6.38-8-generic_2.6.38-8.42~lp769986v201106011610_amd64.deb
> sudo dpkg -i linux-headers-2.6.38-8-generic_2.6.38-8.42~lp769986v201106011610_amd64.deb
>
> suffice to get the job done ?

Yes. All you need to do is download these two files and install them
like this. I've done all the patching and building so you don't have to
;)

> - what about linux-headers-2.6.38-8_2.6.38-8.42~lp769986v201106011610_all.deb ?
> should it be installed too in the same way as the 2 above ?

This shouldn't be needed in your case since the builds I posted are
exactly the same as what you're running now except for that single
patch. But you can install this package and it will not hurt anything.

Revision history for this message
peter b (b1pete) wrote :

@Seth Forshee

thank you for post.

yes, done just with the 2 packages listed above (...all.deb pkge NOT installed).

it all went fine (even grub-update was there) and the pc booted with NO flaw (like before new builds installed).

Seth, pls tell me is there a way to check drivers/net/wireless/zd1211rw/zd_mac.c source on my install and see whether it was indeed patched ? because even before this update there was no sign of problems since final natty release (see #9 above).

I would like this so I can report further to you and Jussi how it is working with the ubuntu patched kernel. tu

Revision history for this message
Seth Forshee (sforshee) wrote :

Unfortunately for that build you just have to take my word that the kernel is patched, as there's no way to extract the source from the files I posted. You can recreate the source by cloning the git repository for the natty kernel, checking out at the Ubuntu-2.6.38-8.42 tag, and applying the patch I posted alongside the builds. If you want information to help you get started building the kernel for Ubuntu, please see the following page.

https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

Revision history for this message
peter b (b1pete) wrote :

your word is taken. I won't go into that - time limitations.

Seth, it just occurred to me, for sure you'll see that ubuntu natty kernel future builds have this patch incorporated - it works - as far as I could see. however, linux 2.6.38.8.22 kernel I have NOT patched and build as #9 Jussi recommended.

I do not know what's the proper way to answer Jussi's and linux generic #9. is it going to be you that will tell linux generic that the patch is working in ubuntu natty linux release ? or should I post here, for Jussi's att'n that the patch is applied in ubuntu natty and holds fine ? do linux generic devs monitor ubuntu linux releases filed bugs ?

........

I use this opportunity to talk to an ubuntu dev team ;
Seth, I think you saw the second part of #9 above; a personal request if I may for the good of ubuntu future (I fully know that's a totally different topic BUT related to kernels the way I was let to believe, whether it is ubuntu kernels or linux generic I do not know) - PLEASE tell me what's your opinion re floppy devices issue in

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

is there, in your opinion, anything that can be done to advance and bring to a successful conclusion this issue ?. all potential future ubuntu users (and there is a whole lot of them out there) and it appears a good chunk of current ubuntu users are dissatisfied by the fact that CLI must be employed in order to get a basic pc device to work with various degree of success. for sure this issue reverberates into other packages (nautilus for sure is one and others).

can you pretty please look into it ? tu in advance.

Revision history for this message
Seth Forshee (sforshee) wrote :

peter, we won't incorporate the patch unless we can verify that it fixes a problem, and since you said in comment #13 that you haven't seen this problem since the final natty release I don't consider the patch to be verified. Ideally what should happen is that someone verifies that the problem exists with unpatched 2.6.38-8 and does not exist with the patched kernel, then this information should be posted on the upstream bugzilla so that the fix can be applied to the upstream kernel. But if the problem no longer exists in natty, there's no need to apply a fix.

Your other issue is off-topic for this bug.

Revision history for this message
Jussi Kivilinna (jukivili) wrote :

I searched for this exact same warning and found bug launchbad bug #766942 and appears to be zd1211rw related and.

So I think what happens is that firmware passing too high per packet signal-level values to zd1211rw-driver (and probably due to radio interface etc, hard to reproduce(?)). Zd1211rw then expects those values to be in specific range and passes them forward unchecked which leads to the warning in mac80211-layer.

So I'm going to make few changes to this patch (add logging for cases when there was out of range value from firmware) and submit patch to upstream.

Revision history for this message
peter b (b1pete) wrote :

following last post and past experience with 11.04 boot I decided to take another look at various logs because

- on 10/15 (+ or-) successful boots ONE is UNSUCCESSFUL (no mssgs whatsoever) AFTER prompted and entering the log in info. the info is accepted the screen turns to pink colour and the pc locks hard at this screen; there is no hd activity noticed; the pc must be powered down and up again and a successful boot can be obtained. there are no messages whatsoever after gdm successful boot.

looking at dmesg I noticed

[ 50.692374] hda-intel: IRQ timing workaround is activated for card #2. Suggest a bigger bdl_pos_adj.

also pls take a look at

[ 98.059446] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint

and following; quite a few iterations on this loop. basically sdf is an external hd device connected to an usb3 adapter card id as follows

02:00.0 USB Controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 03) (prog-if 30 [XHCI])
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at fddfe000 (64-bit, non-prefetchable) [size=8K]
 Capabilities: <access denied>
 Kernel driver in use: xhci_hcd
 Kernel modules: xhci-hcd

dmesg and kern.log attached. the kernel in use is the one with Seth's patch applied (see above) ; just an opinion - maybe this usb3 controller-hd combo authentication and config is the cause of the odd unsuccessful boots ?

Revision history for this message
peter b (b1pete) wrote :

this is kern.log attach post mentioned

Revision history for this message
Miguel Herrero (miguel-herrerobaena) wrote :

I was told that my wireless bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/766942) was a duplicate of this one. It is a problem with Sveon SNT1020.

Therefore I read all this conversation and installed (on Ubuntu 11.04) like:
sudo dpkg -i linux-headers-2.6.38-8-generic_2.6.38-8.42~lp769986v201106011610_i386.deb
and
sudo dpkg -i linux-image-2.6.38-8-generic_2.6.38-8.42~lp769986v201106011610_i386.deb

However, after rebooting, it doesn't recognize my wireless device. I don't know how to go on from this point. If someone has any idea or advice, please let me know.

Thank you.

Revision history for this message
Seth Forshee (sforshee) wrote :

@Miguel, does 'lsmod | grep zd1211rw' output anything? Please also attache the output of dmesg.

Revision history for this message
Seth Forshee (sforshee) wrote :

Closing as Invalid due to lack of response for several months.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in linux:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.