Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #175615 > unrolled thread

Where to report wl bad behavior ?

Back to article view | Back to linux.debian.user

Contents

  Where to report wl bad behavior ? Laurent Debian <laurent.debian@gmail.com> - 2016-12-11 12:40 +0100
    Re: Where to report wl bad behavior ? kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2016-12-11 21:00 +0100
      Re: Where to report wl bad behavior ? kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2016-12-13 05:30 +0100
        Re: Where to report wl bad behavior ? Laurent Debian <laurent.debian@gmail.com> - 2016-12-13 10:30 +0100

#175615 — Where to report wl bad behavior ?

[Multipart message — attachments visible in raw view] — view raw

Hi all,
I experienced a lot of pb recently with wl driver of my brodcoam 4360 ....
I have wl loaded, and get continuously this type of message below
On my kde desktop when resuming from suspend the pass-key of my network is
asked again (but typing it do nothing I just need to restart X server)
Since my all notebook is getting weird recently I would like to try fix
this pb to see if the others are linked to that (desktop instability)

So should i fill a bug against something ? since wl is proprietary I don't
know what to do
Cheers,
Laurent D










Dec 11 12:22:44 debian kernel: [ 4762.794051] WARNING: CPU: 2 PID: 315 at
> /build/linux-lIgGMF/linux-4.8.11/net/wireless/sme.c:876
> *wl_notify_roaming_status*+0xb6/0x130 [wl]
> Dec 11 12:22:45 debian kernel: [ 4762.802903] Modules linked in: fuse
> rfcomm cmac bnep binfmt_misc nls_utf8 isofs udf crc_itu_t loop efi_pstore
> snd_hda_codec_hdmi joydev btusb btrtl btbcm btintel bluetooth hid_generic
> hid_apple iTCO_wdt iTCO_vendor_support evdev intel_rapl applesmc
> input_polldev x86_pkg_temp_thermal i915 coretemp bcm5974 kvm_intel kvm
> snd_hda_codec_cirrus snd_hda_codec_generic wl(POE) irqbypass drm_kms_helper
> snd_hda_intel snd_hda_codec crct10dif_pclmul crc32_pclmul snd_hda_core
> usbhid snd_hwdep hid cfg80211 snd_pcm lpc_ich ghash_clmulni_intel mfd_core
> sg thunderbolt pcspkr efivars i2c_i801 snd_timer i2c_smbus mei_me snd
> acpi_als soundcore drm mei sbs kfifo_buf rfkill battery sbshc shpchp
> i2c_algo_bit industrialio video apple_bl ac button tpm_tis tpm_tis_core tpm
> parport_pc ppdev lp parport sunrpc efivarfs ip_tables x_tables autofs4 ext4
> crc16 jbd2 crc32c_generic fscrypto ecb mbcache sd_mod uas usb_storage
> crc32c_intel ahci libahci xhci_pci xhci_hcd aesni_intel libata aes_x86_64
> glue_helper lrw scsi_mod gf128mul ablk_helper cryptd usbcore usb_common fjes
> Dec 11 12:22:45 debian kernel: [ 4762.832815] CPU: 2 PID: 315 Comm:
> wl_event_handle Tainted: P        W  OE   4.8.0-2-amd64 #1 Debian 4.8.11-1
> Dec 11 12:22:45 debian kernel: [ 4762.839274] Hardware name: Apple Inc.
> MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS MBP111.88Z.0138.B14.1501071216
> 01/07/2015
> Dec 11 12:22:45 debian kernel: [ 4762.845773]  0000000000000286
> 00000000332fa14f ffffffffba7269f5 0000000000000000
> Dec 11 12:22:45 debian kernel: [ 4762.852261]  0000000000000000
> ffffffffba47c16e ffff90262330a700 ffff90255f2c5594
> Dec 11 12:22:45 debian kernel: [ 4762.858713]  ffff90262330af1a
> ffff902621262000 ffff90262330aaf8 ffff90262f298180
> Dec 11 12:22:45 debian kernel: [ 4762.865031] Call Trace:
> Dec 11 12:22:45 debian kernel: [ 4762.871176]  [<ffffffffba7269f5>] ?
> dump_stack+0x5c/0x77
> Dec 11 12:22:45 debian kernel: [ 4762.877205]  [<ffffffffba47c16e>] ?
> __warn+0xbe/0xe0
> Dec 11 12:22:45 debian kernel: [ 4762.883117]  [<ffffffffc0acda76>] ?
> wl_notify_roaming_status+0xb6/0x130 [wl]
> Dec 11 12:22:45 debian kernel: [ 4762.889022]  [<ffffffffc0acd148>] ?
> wl_event_handler+0x58/0x1a0 [wl]
> Dec 11 12:22:45 debian kernel: [ 4762.894878]  [<ffffffffc0acd0f0>] ?
> wl_notify_scan_status+0x320/0x320 [wl]
> Dec 11 12:22:45 debian kernel: [ 4762.900660]  [<ffffffffba49aecd>] ?
> kthread+0xcd/0xf0
> Dec 11 12:22:45 debian kernel: [ 4762.906438]  [<ffffffffba9efcaf>] ?
> ret_from_fork+0x1f/0x40
> Dec 11 12:22:45 debian kernel: [ 4762.912198]  [<ffffffffba49ae00>] ?
> kthread_create_on_node+0x190/0x190
> Dec 11 12:22:45 debian kernel: [ 4762.918045] ---[ end trace
> 33d09e85602c83e7 ]---
>
>

[toc] | [next] | [standalone]

#175632

On Sun, Dec 11, 2016 at 6:32 AM, Laurent Debian
<laurent.debian@gmail.com> wrote:
> Hi all,
> I experienced a lot of pb recently with wl driver of my brodcoam 4360 ....
> I have wl loaded, and get continuously this type of message below
> On my kde desktop when resuming from suspend the pass-key of my network is
> asked again (but typing it do nothing I just need to restart X server)
> Since my all notebook is getting weird recently I would like to try fix this
> pb to see if the others are linked to that (desktop instability)
>
> So should i fill a bug against something ? since wl is proprietary I don't
> know what to do

How and where did you get the wireless driver? If the driver is not
part of the official Debian software repository, I do not see how
filing a bug report would help. Your best shot is to complain to the
upstream yourself or use a different hardware.

raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

[toc] | [prev] | [next] | [standalone]

#175652

> 2016-12-11 20:59 GMT+01:00 kamaraju kusumanchi
> <raju.mailinglists@gmail.com>:
>>
>> How and where did you get the wireless driver? If the driver is not
>> part of the official Debian software repository, I do not see how
>> filing a bug report would help. Your best shot is to complain to the
>> upstream yourself or use a different hardware.
>>
>> raju
>> --
>> Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
>
>
On Mon, Dec 12, 2016 at 12:46 AM, Laurent Debian
<laurent.debian@gmail.com> wrote:
> Hi
> it is. It's in the non-free depot.
>  And AFAIK, it is the only one making works "properly" this kind of chipset
> (broadcom 4360...)
> And I don't like the idea to open up a mac book pro find the wifi chip and
> change it?

Hi Laurent,

It is better to reply to the list instead of writing to me personally.
That way others will also be able to help you and the conversations
will be part of the archive.

Coming back to your question... Yes, you can file a bug report on a
package that is in the non-free component of Debian.

hth
raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

[toc] | [prev] | [next] | [standalone]

#175657

[Multipart message — attachments visible in raw view] — view raw

Hi kamaraju,
Thanks for your feedback.
I will file a bug report against wl then.

Cheers (the reply only to you was a mistake)


2016-12-13 5:23 GMT+01:00 kamaraju kusumanchi <raju.mailinglists@gmail.com>:

> > 2016-12-11 20:59 GMT+01:00 kamaraju kusumanchi
> > <raju.mailinglists@gmail.com>:
> >>
> >> How and where did you get the wireless driver? If the driver is not
> >> part of the official Debian software repository, I do not see how
> >> filing a bug report would help. Your best shot is to complain to the
> >> upstream yourself or use a different hardware.
> >>
> >> raju
> >> --
> >> Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
> >
> >
> On Mon, Dec 12, 2016 at 12:46 AM, Laurent Debian
> <laurent.debian@gmail.com> wrote:
> > Hi
> > it is. It's in the non-free depot.
> >  And AFAIK, it is the only one making works "properly" this kind of
> chipset
> > (broadcom 4360...)
> > And I don't like the idea to open up a mac book pro find the wifi chip
> and
> > change it?
>
> Hi Laurent,
>
> It is better to reply to the list instead of writing to me personally.
> That way others will also be able to help you and the conversations
> will be part of the archive.
>
> Coming back to your question... Yes, you can file a bug report on a
> package that is in the non-free component of Debian.
>
> hth
> raju
> --
> Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web