[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2016-09-16 Thread Alexandre
** Also affects: linux-lts-xenial (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2016-09-16 Thread Alexandre
This kernel bug, is affecting all the container solutions also on Xenial
/ 16.04.1 up to 4.4.0-38.

Lots of people are hitting this on many distributions / container solutions:
https://github.com/docker/docker/issues/5618 (mentions Docker, LXC, kubernetes, 
etc.)
https://github.com/coreos/bugs/issues/254
...

Apparently this was fixed in 12.04 and now reintroduced in 16.04.

Once you get the following dmesg message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
... The only fix is to reboot the host.

What I gathered from the docker issue tracking this, it seems a fix was merged 
in net-next very recently:
http://www.spinics.net/lists/netdev/msg393688.html

... and is in mainline now:
https://github.com/torvalds/linux/blob/master/net/ipv6/addrconf.c

As I wasn't sure this thread was tracking Xenial (I just added it to the
list), I'm trying to figure out if Ubuntu is tracking this issue
upstream and can backport it into 16.04's 4.4.0-? branch, as a lot of
container use case start to break down because of this bug for the past
weeks?

Thanks!

** Bug watch added: github.com/docker/docker/issues #5618
   https://github.com/docker/docker/issues/5618

** Bug watch added: github.com/coreos/bugs/issues #254
   https://github.com/coreos/bugs/issues/254

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2016-09-16 Thread Alexandre
Bug was reintroduced in Ubuntu Xenial's kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1627670] Re: 4.4.0-40.60 fails to boot

2016-09-28 Thread Alexandre
I also have a boot issue with full root encryption never prompting for
the password, also on a Dell, see:

https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1628546

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1627670

Title:
  4.4.0-40.60 fails to boot

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  I've just tried both -39 and -40 in xenial-proposed, and both fail to
  boot on my laptop (dropping to busybox - see the attached screenshot).

  This is a regression over -38, which works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chr1s  2537 F pulseaudio
   /dev/snd/controlC1:  chr1s  2537 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 26 10:42:45 2016
  HibernationDevice: RESUME=UUID=934c1be9-b0ee-4b9d-9508-7bfb0af474c9
  InstallationDate: Installed on 2016-03-09 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Dell Inc. Precision 7510
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=aa26703d-fe98-42ad-927a-31369b873d93 ro noprompt persistent quiet 
splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.05.04
  dmi.board.name: 0692Y5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.05.04:bd05/27/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0692Y5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627670/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1628546] Re: 4.4.0-40-generic no prompts for disk encryption + loops on dots load screen

2016-09-28 Thread Alexandre
Just tested v4.4.20 and v4.4.21 and both worked by showing the luks password 
prompted and then booted.
As a result I didn't test .19, should I ?

The luks password prompt might be a different issue than the kernel
stack trace one?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1628546

Title:
  4.4.0-40-generic no prompts for disk encryption + loops on dots load
  screen

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Since the upgrade to Ubuntu's 16.04.1 Linux kernel 4.4.0-40.60, it is 
impossible to boot my machine with full root encryption. 
  It will keep loading the purple Ubuntu "dots" loading screen for ages and 
stay there.

  There is no issue rebooting back with kernel 4.4.0-38.57.

  I tried recreating the initramfs to no avail:
  update-initramfs -d -u -k 4.4.0-40-generic

  Hardware is a Dell Laptop: XPS13 9350 16GB/i7/512GB SSD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628546/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1628546] Re: 4.4.0-40-generic no prompts for disk encryption + loops on dots load screen

2016-09-28 Thread Alexandre
-41 is booting just fine, seems like only -40 is broken.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1628546

Title:
  4.4.0-40-generic no prompts for disk encryption + loops on dots load
  screen

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Since the upgrade to Ubuntu's 16.04.1 Linux kernel 4.4.0-40.60, it is 
impossible to boot my machine with full root encryption. 
  It will keep loading the purple Ubuntu "dots" loading screen for ages and 
stay there.

  There is no issue rebooting back with kernel 4.4.0-38.57.

  I tried recreating the initramfs to no avail:
  update-initramfs -d -u -k 4.4.0-40-generic

  Hardware is a Dell Laptop: XPS13 9350 16GB/i7/512GB SSD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628546/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1628546] Re: 4.4.0-40-generic no prompts for disk encryption + loops on dots load screen

2016-09-29 Thread Alexandre
Ah, that makes sense, NVMe is pretty common on newer (Dell among others)
laptops.

Thanks! :)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1628546

Title:
  4.4.0-40-generic no prompts for disk encryption + loops on dots load
  screen

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Since the upgrade to Ubuntu's 16.04.1 Linux kernel 4.4.0-40.60, it is 
impossible to boot my machine with full root encryption. 
  It will keep loading the purple Ubuntu "dots" loading screen for ages and 
stay there.

  There is no issue rebooting back with kernel 4.4.0-38.57.

  I tried recreating the initramfs to no avail:
  update-initramfs -d -u -k 4.4.0-40-generic

  Hardware is a Dell Laptop: XPS13 9350 16GB/i7/512GB SSD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628546/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2016-10-11 Thread Alexandre
Apparently the fix is in:

https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.22

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1628546] Re: 4.4.0-40-generic no prompts for disk encryption + loops on dots load screen

2016-10-12 Thread Alexandre
As a reference, 4.4.0-42.62 works fine with LUKS on the XPS13 9350 512GB SSD.
Maybe something else than NVMe this time... :/

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1628546

Title:
  4.4.0-40-generic no prompts for disk encryption + loops on dots load
  screen

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Since the upgrade to Ubuntu's 16.04.1 Linux kernel 4.4.0-40.60, it is 
impossible to boot my machine with full root encryption. 
  It will keep loading the purple Ubuntu "dots" loading screen for ages and 
stay there.

  There is no issue rebooting back with kernel 4.4.0-38.57.

  I tried recreating the initramfs to no avail:
  update-initramfs -d -u -k 4.4.0-40-generic

  Hardware is a Dell Laptop: XPS13 9350 16GB/i7/512GB SSD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628546/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2016-10-13 Thread Alexandre
Oh oops, didn't realize this was the patch with the
751eb6b6042a596b0080967c1a529a9fe98dac1d commit Paul mentionned.

Well, if that made it into Ubuntu's kernel before and including
4.4.0-42, it didn't fix it (I still get the bug on many machines & VMs).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2016-11-24 Thread Alexandre
Update:
I've hit the issue with 4.4.0-47... now testing 4.4.0-49 for the next weeks.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2016-11-28 Thread Alexandre
Seems like the fix isn't in or isn't working for this problem as I've just hit 
this issue again on 4.4.0-49, at least twice:
[434074.636075] unregister_netdevice: waiting for lo to become free. Usage 
count = 1


Since, I see a lot of people talking about 4.8+ kernels fixing this issue, is 
there a generic package (or future plans for one, say when 4.9 LTS comes out in 
a week or two) that will allow anyone to upgrade, but also keep up with updates 
without following versions by hand? (Like the linux-image-generic package)

cheers!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2016-11-08 Thread Alexandre
I was running 4.4.0-46 (not sure if different than the latest .67?) on
October 27th and yesterday had to reboot for the "... count = 1"
problem.

Was there previous 4.4.0-46 releases? If not, the bug is still
present...

Otherwise, I'll confirm if it happens again, or if it doesn't within a
few weeks.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1416998] [NEW] package linux-image-3.16.0-30-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2015-02-02 Thread Alexandre
Public bug reported:

netflix not working
same slow system

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-30-generic (not installed)
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic i686
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  asus   1743 F pulseaudio
Date: Sun Feb  1 20:43:31 2015
DuplicateSignature: package:linux-image-3.16.0-30-generic:(not 
installed):subprocess new pre-installation script returned error exit status 128
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=1cf4ae38-201a-4024-9374-13acc44a4bd1
InstallationDate: Installed on 2015-01-22 (10 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
MachineType: ASUSTeK Computer INC. 1005HA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic 
root=UUID=07ab74ff-7448-4f59-8509-ed1cc815d589 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-15
SourcePackage: linux
Title: package linux-image-3.16.0-30-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1601
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1601:bd04/18/2011:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 utopic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1416998

Title:
  package linux-image-3.16.0-30-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  netflix not working
  same slow system

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-30-generic (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic i686
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asus   1743 F pulseaudio
  Date: Sun Feb  1 20:43:31 2015
  DuplicateSignature: package:linux-image-3.16.0-30-generic:(not 
installed):subprocess new pre-installation script returned error exit status 128
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=1cf4ae38-201a-4024-9374-13acc44a4bd1
  InstallationDate: Installed on 2015-01-22 (10 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  MachineType: ASUSTeK Computer INC. 1005HA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic 
root=UUID=07ab74ff-7448-4f59-8509-ed1cc815d589 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-15
  SourcePackage: linux
  Title: package linux-image-3.16.0-30-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1601
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1005HA
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1601:bd04/18/2011:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1005HA
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416998/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to 

[Kernel-packages] [Bug 1847643] [NEW] iwlwifi during heavy transfers on XPS15 7590

2019-10-10 Thread Alexandre
Public bug reported:

This wifi card is identified in `lspci` as:

3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)
>From my googling the Dell 7590 seems to have a Killer AX1650 (in collaboration 
>with Intel?)

And when uploading a massive image to say S3, for example through CLI or
browser, I get the following messages in `dmesg` after a few dozens of
MB, at which point the net is killed and I need to turn the wifi off and
on again to get online:

[234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
[234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
[234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
[234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
[234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT  
[234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
[234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
[234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
[234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
[234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
[234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
[234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
[234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
[234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
[234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
[234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
[234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
[234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
[234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
[234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
[234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
[234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
[234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
[234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
[234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
[234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
[234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
[234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
[234483.616572] iwlwifi :3b:00.0: 0x | isr4
[234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
[234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
[234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
[234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
[234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
[234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
[234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
[234483.616577] iwlwifi :3b:00.0: 0x | timestamp
[234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
[234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
[234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
[234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
[234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
[234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
[234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
[234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
[234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
[234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
[234483.616657] iwlwifi :3b:00.0: 0x | umac data3
[234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
[234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
[234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
[234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
[234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
[234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
[234483.616688] iwlwifi :3b:00.0: Fseq Registers:
[234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
[234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
[234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
[234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VERSION
[234483.616759] iwlwifi :3b:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[234483.616771] iwlwifi :3b:00.0: 0x00100530 | FSEQ_CNVI_ID
[234483.616783] iwlwifi :3b:00.0: 0x0532 | FSEQ_CNVR_ID
[234483.616790] iwlwifi :3b:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[234483.616819] iwlwifi :3b:00.0: 0x0532 | CNVR_AUX_MISC_CHIP
[234483.616860] iwlwifi :3b:00.0: 0x05B0905B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[234483.616903] iwlwifi :3b:00.0: 0x025B | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[234483.617148] iwlwifi :3b:00.0: Collecting data: trigger 2 fired.
[234483.617150] ieee80211 phy0: Hardware restart

[Kernel-packages] [Bug 1847643] Re: iwlwifi during heavy transfers on XPS15 7590

2019-10-10 Thread Alexandre
** Description changed:

  This wifi card is identified in `lspci` as:
  
  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)
- From my googling the Dell 7590 seems to have a Killer AX1650 (in 
collaboration with Intel?)
+ 
+ From my googling the Dell 7590 seems to have a Killer AX1650 (in
+ collaboration with Intel?)
  
  And when uploading a massive image to say S3, for example through CLI or
  browser, I get the following messages in `dmesg` after a few dozens of
  MB, at which point the net is killed and I need to turn the wifi off and
  on again to get online:
  
  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
- [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT 
 
+ [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VERSION
  [234483.616759] iwlwifi :3b:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
  [234483.616771] iwlwifi :3b:00.0: 0x00100530 | FSEQ_CNVI_ID
  [234483.616783] iwlwifi :3b:00.0: 0x0532 | FSEQ_CNVR_ID
  [234483.616790] iwlwifi :3b:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
  [234483.616819] iwlwifi :3b:00.0: 0x0532 | CN

[Kernel-packages] [Bug 1847643] Re: iwlwifi during heavy transfers on XPS15 7590 (19.10)

2019-10-11 Thread Alexandre
apport information

** Tags added: apport-collected

** Description changed:

  I'm running 19.10 (beta).
  
  The Dell's 7590 wifi card is identified in `lspci` as:
  
  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)
  
  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)
  
  And when uploading a massive image to say S3, for example through CLI or
  browser, I get the following messages in `dmesg` after a few dozens of
  MB, at which point the net is killed and I need to turn the wifi off and
  on again to get online:
  
  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VERSION
  [234483.616759] iwlwifi :3b:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
  [234483.616771] iwlwifi :3b:00.0: 0x00100530 | FSEQ_CNVI_ID
  [234483.616783] iwlwifi :3b:00.0: 0x0532 | FSEQ_CNVR_ID
  [234483.616790] iwlwifi :3b:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
  [234483.616819] iwlwifi :3b:00.0: 0x0532 | CNVR_AUX_MISC_CHIP
  [234483.616860] iwlwifi :3b:00.0: 0x05B0905B | 
CNVR_SCU_SD_

[Kernel-packages] [Bug 1847643] Lsusb.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1847643/+attachment/5296597/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VERSION
  [2344

[Kernel-packages] [Bug 1847643] Lspci.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1847643/+attachment/5296596/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VERSION
  [2344

[Kernel-packages] [Bug 1847643] IwConfig.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1847643/+attachment/5296595/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VERSION

[Kernel-packages] [Bug 1847643] CurrentDmesg.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1847643/+attachment/5296594/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_

[Kernel-packages] [Bug 1847643] ProcCpuinfoMinimal.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1847643/+attachment/5296598/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_

[Kernel-packages] [Bug 1847643] CRDA.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1847643/+attachment/5296593/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VERSION
  [234483

[Kernel-packages] [Bug 1847643] UdevDb.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1847643/+attachment/5296604/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VERSION
  [23

[Kernel-packages] [Bug 1847643] ProcInterrupts.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1847643/+attachment/5296600/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONT

[Kernel-packages] [Bug 1847643] PulseList.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1847643/+attachment/5296602/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VERSIO

[Kernel-packages] [Bug 1847643] ProcModules.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1847643/+attachment/5296601/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VE

[Kernel-packages] [Bug 1847643] WifiSyslog.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1847643/+attachment/5296605/+files/WifiSyslog.txt

** Changed in: linux-firmware (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  

[Kernel-packages] [Bug 1847643] RfKill.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1847643/+attachment/5296603/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VERSION
  [23

[Kernel-packages] [Bug 1847643] ProcEnviron.txt

2019-10-11 Thread Alexandre
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1847643/+attachment/5296599/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847643

Title:
  iwlwifi during heavy transfers on XPS15 7590 (19.10)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I'm running 19.10 (beta).

  The Dell's 7590 wifi card is identified in `lspci` as:

  3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)

  From my googling the Dell 7590 seems to have a Killer AX1650 (in
  collaboration with Intel?)

  And when uploading a massive image to say S3, for example through CLI
  or browser, I get the following messages in `dmesg` after a few dozens
  of MB, at which point the net is killed and I need to turn the wifi
  off and on again to get online:

  [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.
  [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6
  [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0
  [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT
  [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0
  [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1
  [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2
  [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1
  [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2
  [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1
  [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2
  [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3
  [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time
  [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low
  [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi
  [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1
  [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2
  [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type
  [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major
  [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor
  [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version
  [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version
  [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd
  [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0
  [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1
  [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2
  [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3
  [234483.616572] iwlwifi :3b:00.0: 0x | isr4
  [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id
  [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event
  [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control
  [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration
  [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid
  [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match
  [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel
  [234483.616577] iwlwifi :3b:00.0: 0x | timestamp
  [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler
  [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump:
  [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7
  [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1
  [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2
  [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1
  [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2
  [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1
  [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2
  [234483.616657] iwlwifi :3b:00.0: 0x | umac data3
  [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major
  [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor
  [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer
  [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer
  [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd
  [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg
  [234483.616688] iwlwifi :3b:00.0: Fseq Registers:
  [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE
  [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
  [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
  [234483.616735] iwlwifi :3b:00.0: 0xA503 | FSEQ_OTP_VERSION
  [234483.616747] iwlwifi :3b:00.0: 0x8003 | FSEQ_TOP_CONTENT_VE

[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-09-05 Thread Alexandre Magno
Unfortunately I can not help you. I have no time to investigate the
problems with the wifi. I did not do patches. Only organized tips on how
to compile and install a code found on the Internet. Study from wiki.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-09-19 Thread Alexandre Magno
My brother is using the kernel 4.04; touchpad, bluetooth and wifi works
fine after of rebuild with checkinstall.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-09-19 Thread Alexandre Magno
Hi, Adnam,

He told me that uses mouse and keyboard simultaneously.

1) Install and use (boot) the kernel 4.04.
2) Do: https://github.com/alexandre-mbm/rt3290/wiki/Checkinstall
3) After: https://github.com/alexandre-mbm/rt3290/releases/tag/3.9.3-patched


Alexandre

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-08-23 Thread Alexandre Magno
Yes, my brother got, the mouse.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-08-25 Thread Alexandre Magno
Before: https://github.com/alexandre-mbm/rt3290/wiki/Checkinstall
After: https://github.com/alexandre-mbm/rt3290/releases/tag/3.9.3-patched

No try to use DEB file downloaded from last link.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-08-25 Thread Alexandre Magno
Alex10336, no try to use DEB file downloaded from last link. Follow the
two tutorials. Generate your DEB by using checkinstall.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-09-02 Thread Alexandre Magno
@corradoventu, which the install method you have tried?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-09-03 Thread Alexandre Magno
@corradoventu, I ask if you followed my comment #155.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-07-11 Thread Alexandre Magno
The solution at Helvete's Mediafire works on Ubuntu 15.04.

http://wirama.web.id/rt3290-bluetooth-rtbth-driver-with-kernel-3-13/
http://wirama.web.id/rt3290-bluetooth-rtbth-driver-with-kernel-3-13/#comment-15

http://www.mediafire.com/download/2t59ayhx9fxxfoh/rtbth-3.9.3-patched.7z

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1049466] Re: Need support of Ralink RT3290 wifi support

2015-07-11 Thread Alexandre Magno
The solution at Helvete's Mediafire works on Ubuntu 15.04.

http://wirama.web.id/rt3290-bluetooth-rtbth-driver-with-kernel-3-13/
http://wirama.web.id/rt3290-bluetooth-rtbth-driver-with-kernel-3-13/#comment-15

http://www.mediafire.com/download/2t59ayhx9fxxfoh/rtbth-3.9.3-patched.7z

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1049466

Title:
  Need support of Ralink RT3290 wifi support

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-firmware source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Invalid
Status in linux-firmware source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Fix Released
Status in linux-firmware source package in Raring:
  Fix Released
Status in linux package in Baltix:
  Opinion
Status in linux package in Gentoo Linux:
  New

Bug description:
  RT3290 wifi chip is becoming common on consumer notebooks. Its support
  starts from 3.6 so support on 12.10 may need lbm-cw.

  commit a89534edaaa7008992b878680490e9b02a665563
  Author: Woody Hung 
  Date:   Wed Jun 13 15:01:16 2012 +0800

  rt2x00 : RT3290 chip support v4
  
  This patch support the new chipset rt3290 wifi implementation in rt2x00.
  It initailize the related mac, bbp and rf register in startup phase.
  And this patch modify the efuse read/write method for the different efuse 
data offset of rt3290.
  
  Signed-off-by: Woody Hung 
  Signed-off-by: John W. Linville 

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1049466/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1049466] Re: Need support of Ralink RT3290 wifi support

2015-07-11 Thread Alexandre Magno
See algo the bug #1189721

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1049466

Title:
  Need support of Ralink RT3290 wifi support

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-firmware source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Invalid
Status in linux-firmware source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Fix Released
Status in linux-firmware source package in Raring:
  Fix Released
Status in linux package in Baltix:
  Opinion
Status in linux package in Gentoo Linux:
  New

Bug description:
  RT3290 wifi chip is becoming common on consumer notebooks. Its support
  starts from 3.6 so support on 12.10 may need lbm-cw.

  commit a89534edaaa7008992b878680490e9b02a665563
  Author: Woody Hung 
  Date:   Wed Jun 13 15:01:16 2012 +0800

  rt2x00 : RT3290 chip support v4
  
  This patch support the new chipset rt3290 wifi implementation in rt2x00.
  It initailize the related mac, bbp and rf register in startup phase.
  And this patch modify the efuse read/write method for the different efuse 
data offset of rt3290.
  
  Signed-off-by: Woody Hung 
  Signed-off-by: John W. Linville 

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1049466/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1049466] Re: Need support of Ralink RT3290 wifi support

2015-07-11 Thread Alexandre Magno
In really I don't know if this bug affects me. The wifi signal looks
very poor... is this a symptom?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1049466

Title:
  Need support of Ralink RT3290 wifi support

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-firmware source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Invalid
Status in linux-firmware source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Fix Released
Status in linux-firmware source package in Raring:
  Fix Released
Status in linux package in Baltix:
  Opinion
Status in linux package in Gentoo Linux:
  New

Bug description:
  RT3290 wifi chip is becoming common on consumer notebooks. Its support
  starts from 3.6 so support on 12.10 may need lbm-cw.

  commit a89534edaaa7008992b878680490e9b02a665563
  Author: Woody Hung 
  Date:   Wed Jun 13 15:01:16 2012 +0800

  rt2x00 : RT3290 chip support v4
  
  This patch support the new chipset rt3290 wifi implementation in rt2x00.
  It initailize the related mac, bbp and rf register in startup phase.
  And this patch modify the efuse read/write method for the different efuse 
data offset of rt3290.
  
  Signed-off-by: Woody Hung 
  Signed-off-by: John W. Linville 

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1049466/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1355096] Re: Ralink RT3290 [1814:3298] missing bluetooth support with 12.04.5(kernel 3.13)

2015-07-11 Thread Alexandre Magno
RT3290 Bluetooth (rtbth) driver with Kernel >= 3.13 + PATCH!
http://wirama.web.id/rt3290-bluetooth-rtbth-driver-with-kernel-3-13/
http://wirama.web.id/rt3290-bluetooth-rtbth-driver-with-kernel-3-13/#comment-15

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1355096

Title:
  Ralink RT3290 [1814:3298] missing bluetooth support with
  12.04.5(kernel 3.13)

Status in HWE Next:
  Won't Fix
Status in linux-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Look into the spec, the ralink rt3290 should have bluetooth supported,
  https://wikidevi.com/files/Ralink/RT3290%20product%20brief.pdf

  System with fresh 12.04.5 installed does not detect the bluetooth
  correctly.

  rfkill failed to show the bluetooth device:
  ubuntu@201209-11786:~/$ rfkill list all
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  
  However lspci does listed bluetooth device:
  ubuntu@201209-11786:~/$ lspci -v|grep -i RT3290
  02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
  02:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 05:37:32 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355096/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1355096] Re: Ralink RT3290 [1814:3298] missing bluetooth support with 12.04.5(kernel 3.13)

2015-07-11 Thread Alexandre Magno
RT3290 Bluetooth for Ubuntu 15.04 vivid
http://alexandre-mbm.github.io/rt3290

(created with checkinstall)

sudo dpkg -i rtbth_3.9.3-patched-1_amd64.deb

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1355096

Title:
  Ralink RT3290 [1814:3298] missing bluetooth support with
  12.04.5(kernel 3.13)

Status in HWE Next:
  Won't Fix
Status in linux-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Look into the spec, the ralink rt3290 should have bluetooth supported,
  https://wikidevi.com/files/Ralink/RT3290%20product%20brief.pdf

  System with fresh 12.04.5 installed does not detect the bluetooth
  correctly.

  rfkill failed to show the bluetooth device:
  ubuntu@201209-11786:~/$ rfkill list all
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  
  However lspci does listed bluetooth device:
  ubuntu@201209-11786:~/$ lspci -v|grep -i RT3290
  02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
  02:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 05:37:32 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355096/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-07-11 Thread Alexandre Magno
RT3290 Bluetooth for Ubuntu 15.04 vivid
http://alexandre-mbm.github.io/rt3290

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-07-12 Thread Alexandre Magno
I have not had chance to test pairing.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-07-18 Thread Alexandre Magno
Sorry.

$ sudo modprobe -r rtbth
$ sudo modprobe rtbth

That package is a workaround that I am doing to my brother. It has bugs.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1216734] Re: btrfs continuously crash

2014-07-16 Thread Alexandre Magno
linux-kernel-bugs #60793 have patch.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1216734

Title:
  btrfs continuously crash

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  btrfs continuously crash. If user trying to work with filesystem (save
  file, move file, etc.) when that happen, application that interact
  with filesystem (Dolphin or LibreOffice for example) hang for several
  tens of seconds.

  Please look into dmesg for additional information.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-3-generic 3.11.0-3.8
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1216734/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1292642] Re: [PACKARD BELL BV EasyNote MV85] suspend/resume failure

2014-04-22 Thread Alexandre Fidalgo
Hi have a Acer Aspire One Aod260 Intel Atom N455, with the same problem. I 
close the netbook and he goes perfectly to Standbye, but whem I try to resume 
he freezes in black screen.
Im shutdown, restart/power on, the netbook works well!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1292642

Title:
  [PACKARD BELL BV EasyNote MV85] suspend/resume failure

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Still unable to enter suspend mode - computer freezes.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-17-generic 3.13.0-17.37
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Mar 14 11:29:24 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=2a568898-d25b-42e4-aa67-17cc2a0af7d2
  InstallationDate: Installed on 2014-03-08 (6 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225)
  InterpreterPath: /usr/bin/python3.4
  MachineType: PACKARD BELL BV EasyNote MV85
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-17-generic 
root=UUID=d8659da2-dabe-4a49-8f24-ba09f9fccc7e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [PACKARD BELL BV EasyNote MV85] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/11/2006
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R1.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: EasyNote MV85
  dmi.board.vendor: PACKARD BELL BV
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Packard Bell BV
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrR1.15:bd09/11/2006:svnPACKARDBELLBV:pnEasyNoteMV85:pvrPB49201906:rvnPACKARDBELLBV:rnEasyNoteMV85:rvrBaseBoardVersion:cvnPackardBellBV:ct1:cvrChassisVersion:
  dmi.product.name: EasyNote MV85
  dmi.product.version: PB49201906
  dmi.sys.vendor: PACKARD BELL BV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292642/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1349108] Re: Disconnections problems each day after upgrade linux-firmware:amd64 (1.127.4, 1.127.5)

2014-07-27 Thread Alexandre Neveux
Actually, I'm using the previous version for this package : 
linux-firmware:amd64 (1.127.4).
Everything works !

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux-firmware” package in Ubuntu:
  New

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:

[Kernel-packages] [Bug 1349108] Re: Disconnections problems each day after upgrade linux-firmware:amd64 (1.127.4, 1.127.5)

2014-07-27 Thread Alexandre Neveux
Much details about my problems :

My wireless works well before upgrading my system with synaptic.
Here is the list of upgraded packages :

oxideqt-codecs-extra:amd64 (1.0.0~bzr501-0ubuntu2, 1.0.4-0ubuntu0.14.04.1),
firefox-locale-en:amd64 (30.0+build1-0ubuntu0.14.04.3, 
31.0+build1-0ubuntu0.14.04.1),
firefox-locale-fr:amd64 (30.0+build1-0ubuntu0.14.04.3, 
31.0+build1-0ubuntu0.14.04.1),
thunderbird-locale-en-us:amd64 (24.6.0+build1-0ubuntu0.14.04.1, 
31.0+build1-0ubuntu0.14.04.1),
thunderbird:amd64 (24.6.0+build1-0ubuntu0.14.04.1, 
31.0+build1-0ubuntu0.14.04.1),
firefox:amd64 (30.0+build1-0ubuntu0.14.04.3, 31.0+build1-0ubuntu0.14.04.1),
grub-common:amd64 (2.02~beta2-9, 2.02~beta2-9ubuntu1),
nfs-common:amd64 (1.2.8-6ubuntu1, 1.2.8-6ubuntu1.1),
grub2-common:amd64 (2.02~beta2-9, 2.02~beta2-9ubuntu1),
thunderbird-locale-en:amd64 (24.6.0+build1-0ubuntu0.14.04.1, 
31.0+build1-0ubuntu0.14.04.1),
libupstart1:amd64 (1.12.1-0ubuntu4, 1.12.1-0ubuntu4.2),
thunderbird-locale-fr:amd64 (24.6.0+build1-0ubuntu0.14.04.1, 
31.0+build1-0ubuntu0.14.04.1),
liboxideqtcore0:amd64 (1.0.0~bzr501-0ubuntu2, 1.0.4-0ubuntu0.14.04.1),
thunderbird-gnome-support:amd64 (24.6.0+build1-0ubuntu0.14.04.1, 
31.0+build1-0ubuntu0.14.04.1),
grub-pc-bin:amd64 (2.02~beta2-9, 2.02~beta2-9ubuntu1),
upstart:amd64 (1.12.1-0ubuntu4, 1.12.1-0ubuntu4.2),
grub-pc:amd64 (2.02~beta2-9, 2.02~beta2-9ubuntu1),
liboxideqt-qmlplugin:amd64 (1.0.0~bzr501-0ubuntu2, 1.0.4-0ubuntu0.14.04.1),
libtasn1-6:amd64 (3.4-3, 3.4-3ubuntu0.1)
language-selector-common:amd64 (0.129.1, 0.129.2),
libdecoration0:amd64 (0.9.11.1+14.04.20140701-0ubuntu1, 
0.9.11.2+14.04.20140714-0ubuntu1),
libnautilus-extension1a:amd64 (3.10.1-0ubuntu9.2, 3.10.1-0ubuntu9.3),
compiz-gnome:amd64 (0.9.11.1+14.04.20140701-0ubuntu1, 
0.9.11.2+14.04.20140714-0ubuntu1),
unity:amd64 (7.2.1+14.04.20140513-0ubuntu2, 7.2.2+14.04.20140714-0ubuntu1),
libunity-core-6.0-9:amd64 (7.2.1+14.04.20140513-0ubuntu2, 
7.2.2+14.04.20140714-0ubuntu1),
compiz-core:amd64 (0.9.11.1+14.04.20140701-0ubuntu1, 
0.9.11.2+14.04.20140714-0ubuntu1),
compiz:amd64 (0.9.11.1+14.04.20140701-0ubuntu1, 
0.9.11.2+14.04.20140714-0ubuntu1),
libcompizconfig0:amd64 (0.9.11.1+14.04.20140701-0ubuntu1, 
0.9.11.2+14.04.20140714-0ubuntu1),
unity-services:amd64 (7.2.1+14.04.20140513-0ubuntu2, 
7.2.2+14.04.20140714-0ubuntu1),
base-files:amd64 (7.2ubuntu5, 7.2ubuntu5.1),
language-selector-gnome:amd64 (0.129.1, 0.129.2),
liblzo2-2:amd64 (2.06-1.2ubuntu1, 2.06-1.2ubuntu1.1),
nautilus:amd64 (3.10.1-0ubuntu9.2, 3.10.1-0ubuntu9.3),
nautilus-data:amd64 (3.10.1-0ubuntu9.2, 3.10.1-0ubuntu9.3),
compiz-plugins-default:amd64 (0.9.11.1+14.04.20140701-0ubuntu1, 
0.9.11.2+14.04.20140714-0ubuntu1),
linux-firmware:amd64 (1.127.4, 1.127.5),
pm-utils:amd64 (1.4.1-13, 1.4.1-13ubuntu0.1),
file-roller:amd64 (3.10.2.1-0ubuntu4, 3.10.2.1-0ubuntu4.1)

Previously, I said everything's working ... ... ... but not !

As explain above, I just downgraded linux-firmware from 1.127.5 to
1.127.4 but a new problem appears during a synchronization : network was
completely blocked.

Finally, I reinstall Ubuntu 14.04 LTS because the downgrade of language-
selector-common wanted remove unity-desktop !

After the reinstall, the current package in use is linux-firmware
1.127.5.

At this time, the wireless works ... (...for how long ?)

I'm a little disappointed because I try to look after the operating system 
avoiding to install or compile any external program.
For more, my hardware is certified for the current Ubuntu version (see: 
http://www.clevo.fr/ ).

Have I to reinstall Ubuntu each month to avoid upgrade bugs ?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux-firmware” package in Ubuntu:
  New

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474

[Kernel-packages] [Bug 1349108] Re: Disconnections problems each day after upgrade linux-firmware:amd64 (1.127.4, 1.127.5)

2014-07-27 Thread Alexandre Neveux
Hi,

So, the reinstall don't solve the problem : 5 hours running and once
again disconnect.

The NetworkManager ask me for the SSID password ...
I have to switch off/on the wifi to be able to reconnect.

Can someone help me please ?

Has NetworkManager a problem ?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux-firmware” package in Ubuntu:
  New

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:1

[Kernel-packages] [Bug 1349108] Re: Disconnections problems each day after upgrade linux-firmware:amd64 (1.127.4, 1.127.5)

2014-07-29 Thread Alexandre Neveux
Hi,

Thanks for your reply.

I'm sorry Seth but before reading your message, I proceeded to a new fresh 
install of Ubuntu 14.04 without installing updates during installation. After 
installation, I configured 'synaptic' to receive only updates from 
'trusty-security' to avoid updating 'linux-firmware' from 1.127.4 to 1.127.5 or 
any other recent packages.
-> My computer was online all the night and no wireless disconnection occurs.

Today, once again, I proceeded to a new fresh install. I installed Ubuntu by 
checking to install updates during installation.
After installation, I installed all available updates for normal use. I didn't 
install additionnal packages.
-> After 2 hours, any disconnection appears. The wireless keeps ready after 
sleep/wake.

Now, as you ask me in your message, I'm waiting for a wireless
disconnection to send you information with 'apport-collect'

Whatever happens or not, I come back to you as soon as possible.

Regards.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq

[Kernel-packages] [Bug 1349108] Re: Disconnections problems each day after upgrade linux-firmware:amd64 (1.127.4, 1.127.5)

2014-07-29 Thread Alexandre Neveux
Hi,

Good news !

No wireless disconnection occurs this night.

I will install additionnal packages this afternoon (gimp, vlc, etc...).

Regards.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNA

[Kernel-packages] [Bug 1349108] BootDmesg.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1349108/+attachment/4165920/+files/BootDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME N

[Kernel-packages] [Bug 1349108] CurrentDmesg.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1349108/+attachment/4165922/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOST

[Kernel-packages] [Bug 1349108] Lspci.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1349108/+attachment/4165924/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME NetworkMan

[Kernel-packages] [Bug 1349108] ProcCpuinfo.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1349108/+attachment/4165926/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNA

[Kernel-packages] [Bug 1349108] Lsusb.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1349108/+attachment/4165925/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME NetworkMan

[Kernel-packages] [Bug 1349108] ProcEnviron.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1349108/+attachment/4165927/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNA

[Kernel-packages] [Bug 1349108] IwConfig.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1349108/+attachment/4165923/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME Net

[Kernel-packages] [Bug 1349108] ProcModules.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1349108/+attachment/4165929/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNA

[Kernel-packages] [Bug 1349108] Re: Disconnections problems each day after upgrade linux-firmware:amd64 (1.127.4, 1.127.5)

2014-07-30 Thread Alexandre Neveux
apport information

** Tags added: apport-collected

** Description changed:

  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Activation 
(wlan0/wireless): disconnected during association, asking for new key.
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): device state 
change: activated -> need-auth (reason 'supplicant-disconnect') [100 60 8]
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  NetworkManager state is 
now CONNECTING
  Jul 27 11:08:35 HOSTNAME whoopsie[1194]: online
  Jul 2

[Kernel-packages] [Bug 1349108] ProcInterrupts.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1349108/+attachment/4165928/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 

[Kernel-packages] [Bug 1349108] CRDA.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1349108/+attachment/4165921/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME NetworkManag

[Kernel-packages] [Bug 1349108] WifiSyslog.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1349108/+attachment/4165934/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME

[Kernel-packages] [Bug 1349108] UdevLog.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1349108/+attachment/4165933/+files/UdevLog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME Netwo

[Kernel-packages] [Bug 1349108] RfKill.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1349108/+attachment/4165931/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME NetworkM

[Kernel-packages] [Bug 1349108] UdevDb.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1349108/+attachment/4165932/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME NetworkM

[Kernel-packages] [Bug 1349108] PulseList.txt

2014-07-30 Thread Alexandre Neveux
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1349108/+attachment/4165930/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME N

[Kernel-packages] [Bug 1349108] Re: Disconnections problems each day after upgrade linux-firmware:amd64 (1.127.4, 1.127.5)

2014-07-30 Thread Alexandre Neveux
Hi,

Once again a new disconnection !

...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Activation 
(wlan0/wireless): disconnected during association, asking for new 

[Kernel-packages] [Bug 1349108] Re: Disconnections problems each day after upgrade linux-firmware:amd64 (1.127.4, 1.127.5)

2014-07-30 Thread Alexandre Neveux
Hi,

Here we are !
A wireless disconnection occurs after 30 minutes of use.

As you ask me, I ran 'apport-collect 1349108'.

So, I installed 30 minutes ago these additionnal packages and rebooted my 
computer before the issue occurs :
unrar:amd64 (5.0.10-1),
ttf-mscorefonts-installer:amd64 (3.4+nmu1ubuntu1),
libmjpegutils-2.1-0:amd64 (2.1.0+debian-2.1, automatic),
cabextract:amd64 (1.4-4, automatic),
gstreamer0.10-plugins-bad-multiverse:amd64 (0.10.21-1ubuntu3),
libfaac0:amd64 (1.28-6, automatic),
libmplex2-2.1-0:amd64 (2.1.0+debian-2.1, automatic),
libmpeg2encpp-2.1-0:amd64 (2.1.0+debian-2.1, automatic),
ubuntu-restricted-extras:amd64

Regards.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 2

[Kernel-packages] [Bug 1349108] Re: Disconnections problems each day after upgrade linux-firmware:amd64 (1.127.4, 1.127.5)

2014-07-30 Thread Alexandre Neveux
Hi,

I found this log for each disconnection (/var/log/syslog) :

wpa_supplicant[875]: wlan0: WPA: 4-Way Handshake failed - pre-shared key
may be incorrect

...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616530] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
  Jul 27 

[Kernel-packages] [Bug 1349108] Re: Disconnections problems each day after upgrade linux-firmware:amd64 (1.127.4, 1.127.5)

2014-08-08 Thread Alexandre Neveux
Hi Seth,

Since last week, I try to solve this issue.

After reading the description to bug #1293569, I renamed the
iwlwifi-7260-8.ucode to iwlwifi-7260-8.backup in /lib/firmware.

The wireless works fine since last saturday (2014/08/02) : no issue
occurs at startup, at wake up or after several hours in use.


So, it's OK for me. This issue is resolved.


Thanks for the previous information.

Regards.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349108

Title:
  Disconnections problems each day after upgrade linux-firmware:amd64
  (1.127.4, 1.127.5)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Jul 27 13:15:28 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.675959] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: completed -> disconnected
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682734] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682741] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682746] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682750] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682753] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682756] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME kernel: [61424.682760] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:38 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-SCAN-STARTED 
  Jul 27 13:15:38 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: disconnected -> scanning
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: SME: Trying to 
authenticate with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.528312] wlan0: authenticate with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.530148] wlan0: send auth to 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: scanning -> authenticating
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Trying to associate 
with a0:b1:c2:d3:e4:f5 (SSID='SSIDNAME' freq=2437 MHz)
  Jul 27 13:15:39 HOSTNAME kernel: [61425.538366] wlan0: authenticated
  Jul 27 13:15:39 HOSTNAME kernel: [61425.540490] wlan0: associate with 
a0:b1:c2:d3:e4:f5 (try 1/3)
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: authenticating -> associating
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): roamed from 
BSSID a0:b1:c2:d3:e4:f5 (SSIDNAME) to (none) ((none))
  Jul 27 13:15:39 HOSTNAME kernel: [61425.568127] wlan0: RX AssocResp from 
a0:b1:c2:d3:e4:f5 (capab=0x431 status=0 aid=2)
  Jul 27 13:15:39 HOSTNAME wpa_supplicant[1020]: wlan0: Associated with 
a0:b1:c2:d3:e4:f5
  Jul 27 13:15:39 HOSTNAME kernel: [61425.576541] wlan0: associated
  Jul 27 13:15:39 HOSTNAME NetworkManager[955]:  (wlan0): supplicant 
interface state: associating -> 4-way handshake
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a0:b1:c2:d3:e4:f5 reason=4 locally_generated=1
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
  Jul 27 13:15:40 HOSTNAME wpa_supplicant[1020]: wlan0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSIDNAME" auth_failures=1 duration=10
  Jul 27 13:15:40 HOSTNAME NetworkManager[955]:  Connection disconnected 
(reason -4)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.610886] cfg80211: Calling CRDA to 
update world regulatory domain
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616505] cfg80211: World regulatory 
domain updated:
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616512] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616517] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616520] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616524] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Jul 27 13:15:40 HOSTNAME kernel: [61426.616527] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Jul 27

[Kernel-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

2016-06-14 Thread Alexandre Payet
** Changed in: turbo
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1590844

Title:
  Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1593919] Re: Bluetooth not working with Meizu Pro 5

2016-07-30 Thread Alexandre Payet
** Tags added: turbo

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1593919

Title:
  Bluetooth not working with Meizu Pro 5

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I have problems with bluetooth. When I connect my Jabra Supreme
  headset, or connect with my car (Ford Fiesta), I only hear a lot of
  noise. This is both when I make a call, or receive an incoming call. I
  can hear music via bluetooth without problems on both headset, and in
  the car.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1593919/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1593919] Re: Bluetooth not working with Meizu Pro 5

2016-07-30 Thread Alexandre Payet
** Also affects: turbo
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1593919

Title:
  Bluetooth not working with Meizu Pro 5

Status in turbo:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I have problems with bluetooth. When I connect my Jabra Supreme
  headset, or connect with my car (Ford Fiesta), I only hear a lot of
  noise. This is both when I make a call, or receive an incoming call. I
  can hear music via bluetooth without problems on both headset, and in
  the car.

To manage notifications about this bug go to:
https://bugs.launchpad.net/turbo/+bug/1593919/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

2016-08-01 Thread Alexandre Payet
These ares different log I get after following the Debugging Bluetooth
documentation.

With the headset I used (a old one), I didn't get any sound or noise when doing 
a call with bluetooth
I've tested the sound from music app and it worked well with no noise

I will try to upload some others logs soon with an other headset or car
bluetooth (with the noise)

@ Konrad : I hope that I've following well the procedure. I've tried the
headset one time without verbose logging (around 18.35 I think) and a
second time after enable verbose logging (around 18.45 I think). I've
got one error : impossible to edit /etc/init/ofono.override --> Read
only file system (even if I used the sudo mount -o remount,rw /)

See the attaches files

Alexandre,

** Attachment added: "log-bug-1590844.tar"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4711722/+files/log-bug-1590844.tar

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1590844

Title:
  Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1537737] Re: Since Bluez5, headsets don't reconnect audio when reconnecting

2016-08-01 Thread Alexandre Payet
I can reproduce this bug on Meizu pro 5 rc-proposed and Nexus 4 rc-
proposed (both last revision)

In my case if you disconnect manually from the bluetooth device and
reconnect to it (in settings>Bluetooth>device name), then the sound is
routed well to bluetooth device

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1537737

Title:
  Since Bluez5, headsets don't reconnect audio when reconnecting

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Pairing a Bluetooth headset (A2DP) seems to work fine. After pairing,
  the phone successfully switches to transmit audio over Bluetooth. When
  disconnecting the Headset again, the phone successfully switches audio
  back to the integrated speaker. However, on a reconnect without
  pairing, the headset seems to connect properly, but it doesn't route
  audio any more to the headset. Despite the headset being connected,
  audio is still routed to the integrated speaker. A reboot does not
  seem to help. The only way to get back to Bluetooth audio streaming is
  to delete the device from the settings, and pair it again, which makes
  it work once again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

2016-08-02 Thread Alexandre Payet
Here is the logs with an other headset
Doing a call --> lot of noise / saturated sound in headset
Playing music --> sound is good in headset

At the beginning of the log, I had to disconnect manually from the
headset and reconnect because the sound was not redirected to headset (I
think this is an other bug like here --> #1537737 [1])


[1] : https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737


Alexandre,

** Attachment added: "log-bug-1590844.zip"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4712228/+files/log-bug-1590844.zip

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1590844

Title:
  Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1537737] Re: Since Bluez5, headsets don't reconnect audio when reconnecting

2016-08-02 Thread Alexandre Payet
Here some logs in attachment (I think in the first 10 minutes)

Explanation :

How it works : 
1. Turn on the headset --> bluetooth connects automatically the headset 
(already paired in the past)
2. Make a call --> dialer-app  show the bluetooth icon by default
3. No sound for the call (even in internal phone speaker), if you switch back 
to phone speaker option the sound is back in internal phone speaker
4. Switch back to bluetooth --> still no sound
5. Disconnect manually from headset and reconnect (in settings>Bluetooth>device 
name)
6. Make a call --> The sound is now routed to headset 

How it should work : 
1. Turn on the headset --> bluetooth connects automatically the headset 
(already paired in the past)
2. Make a call --> dialer-app  shows the bluetooth icon by default
3. The sound is routed to the bluetooth headset

Alexandre,

** Attachment added: "log-bug-1537737 .zip"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737/+attachment/4712251/+files/log-bug-1537737%20.zip

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1537737

Title:
  Since Bluez5, headsets don't reconnect audio when reconnecting

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Pairing a Bluetooth headset (A2DP) seems to work fine. After pairing,
  the phone successfully switches to transmit audio over Bluetooth. When
  disconnecting the Headset again, the phone successfully switches audio
  back to the integrated speaker. However, on a reconnect without
  pairing, the headset seems to connect properly, but it doesn't route
  audio any more to the headset. Despite the headset being connected,
  audio is still routed to the integrated speaker. A reboot does not
  seem to help. The only way to get back to Bluetooth audio streaming is
  to delete the device from the settings, and pair it again, which makes
  it work once again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1593919] Re: Bluetooth not working with Meizu Pro 5

2016-08-17 Thread Alexandre Payet
*** This bug is a duplicate of bug 1590844 ***
https://bugs.launchpad.net/bugs/1590844

** This bug has been marked a duplicate of bug 1590844
   Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1593919

Title:
  Bluetooth not working with Meizu Pro 5

Status in turbo:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I have problems with bluetooth. When I connect my Jabra Supreme
  headset, or connect with my car (Ford Fiesta), I only hear a lot of
  noise. This is both when I make a call, or receive an incoming call. I
  can hear music via bluetooth without problems on both headset, and in
  the car.

To manage notifications about this bug go to:
https://bugs.launchpad.net/turbo/+bug/1593919/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1049466] Re: Need support of Ralink RT3290 wifi support

2016-05-14 Thread Alexandre Magno
Høst, maybe the manufacturer needs to talk with the Ubuntu team, give
them sufficient information about their hardware! Note that Dell
notebooks are very much compatibles.

corrado venturini, try rebuild it.

My last message about it:
https://bugs.launchpad.net/bluetooth/+bug/1189721/comments/191

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1049466

Title:
  Need support of Ralink RT3290 wifi support

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-firmware source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Invalid
Status in linux-firmware source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Fix Released
Status in linux-firmware source package in Raring:
  Fix Released
Status in linux package in Baltix:
  Opinion
Status in linux package in Gentoo Linux:
  New

Bug description:
  RT3290 wifi chip is becoming common on consumer notebooks. Its support
  starts from 3.6 so support on 12.10 may need lbm-cw.

  commit a89534edaaa7008992b878680490e9b02a665563
  Author: Woody Hung 
  Date:   Wed Jun 13 15:01:16 2012 +0800

  rt2x00 : RT3290 chip support v4
  
  This patch support the new chipset rt3290 wifi implementation in rt2x00.
  It initailize the related mac, bbp and rf register in startup phase.
  And this patch modify the efuse read/write method for the different efuse 
data offset of rt3290.
  
  Signed-off-by: Woody Hung 
  Signed-off-by: John W. Linville 

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1049466/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1524939] [NEW] Using telephony with bluetooth not possible after second connection

2015-12-10 Thread Alexandre Payet
Public bug reported:

I've a problem using telephony with bluetooth in my car

I explain : 
I can connect in bluetooth with my car
At the first connection everything works fine (I can do a call, play music 
normally in car speakers)
At the second automatic connection (ie. I leave the car and go away, lost the 
bluetooth connection, and come back in the car --> the phone reconnect 
automatically to the car bluetooth)

At this second connection, I loose the possibility to do a call with
audio in car speakers. Telephony app detect the bluetooth well
(bluetooth icon in app), but this doesn’t cut the sound already playing
in car speaker and phone call is not redirected to car speakers. When I
hangout the sound playing in car speaker is cut (for 2sec) but if do an
other call this still not working.


So to solve the problem, I have to manually disconnect from car bluetooth and 
reconnect again (in settings). If I just turn off bluetooth then turn it back 
on, the problem is not solved.

Does someone have the same issue or am I not clear ? 
I could try to add a syslog if it could help.

Device : mako rc-proposed; Bluetooth car module :  XCARLink Smart BT in
207 Peugeot

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1524939

Title:
  Using telephony with bluetooth not possible after second connection

Status in bluez package in Ubuntu:
  New

Bug description:
  I've a problem using telephony with bluetooth in my car

  I explain : 
  I can connect in bluetooth with my car
  At the first connection everything works fine (I can do a call, play music 
normally in car speakers)
  At the second automatic connection (ie. I leave the car and go away, lost the 
bluetooth connection, and come back in the car --> the phone reconnect 
automatically to the car bluetooth)

  At this second connection, I loose the possibility to do a call with
  audio in car speakers. Telephony app detect the bluetooth well
  (bluetooth icon in app), but this doesn’t cut the sound already
  playing in car speaker and phone call is not redirected to car
  speakers. When I hangout the sound playing in car speaker is cut (for
  2sec) but if do an other call this still not working.

  
  So to solve the problem, I have to manually disconnect from car bluetooth and 
reconnect again (in settings). If I just turn off bluetooth then turn it back 
on, the problem is not solved.

  Does someone have the same issue or am I not clear ? 
  I could try to add a syslog if it could help.

  Device : mako rc-proposed; Bluetooth car module :  XCARLink Smart BT
  in 207 Peugeot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1524939/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1524939] Re: Using telephony in car with bluetooth not possible after second connection

2015-12-11 Thread Alexandre Payet
** Summary changed:

- Using telephony with bluetooth not possible after second connection
+ Using telephony in car with bluetooth not possible after second connection

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1524939

Title:
  Using telephony in car with bluetooth not possible after second
  connection

Status in bluez package in Ubuntu:
  New

Bug description:
  I've a problem using telephony with bluetooth in my car

  I explain : 
  I can connect in bluetooth with my car
  At the first connection everything works fine (I can do a call, play music 
normally in car speakers)
  At the second automatic connection (ie. I leave the car and go away, lost the 
bluetooth connection, and come back in the car --> the phone reconnect 
automatically to the car bluetooth)

  At this second connection, I loose the possibility to do a call with
  audio in car speakers. Telephony app detect the bluetooth well
  (bluetooth icon in app), but this doesn’t cut the sound already
  playing in car speaker and phone call is not redirected to car
  speakers. When I hangout the sound playing in car speaker is cut (for
  2sec) but if do an other call this still not working.

  
  So to solve the problem, I have to manually disconnect from car bluetooth and 
reconnect again (in settings). If I just turn off bluetooth then turn it back 
on, the problem is not solved.

  Does someone have the same issue or am I not clear ? 
  I could try to add a syslog if it could help.

  Device : mako rc-proposed; Bluetooth car module :  XCARLink Smart BT
  in 207 Peugeot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1524939/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1524939] Re: Using telephony in car with bluetooth not possible after second connection

2015-12-12 Thread Alexandre Payet
** Also affects: ofono (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1524939

Title:
  Using telephony in car with bluetooth not possible after second
  connection

Status in bluez package in Ubuntu:
  New
Status in ofono package in Ubuntu:
  New

Bug description:
  I've a problem using telephony with bluetooth in my car

  I explain : 
  I can connect in bluetooth with my car
  At the first connection everything works fine (I can do a call, play music 
normally in car speakers)
  At the second automatic connection (ie. I leave the car and go away, lost the 
bluetooth connection, and come back in the car --> the phone reconnect 
automatically to the car bluetooth)

  At this second connection, I loose the possibility to do a call with
  audio in car speakers. Telephony app detect the bluetooth well
  (bluetooth icon in app), but this doesn’t cut the sound already
  playing in car speaker and phone call is not redirected to car
  speakers. When I hangout the sound playing in car speaker is cut (for
  2sec) but if do an other call this still not working.

  
  So to solve the problem, I have to manually disconnect from car bluetooth and 
reconnect again (in settings). If I just turn off bluetooth then turn it back 
on, the problem is not solved.

  Does someone have the same issue or am I not clear ? 
  I could try to add a syslog if it could help.

  Device : mako rc-proposed; Bluetooth car module :  XCARLink Smart BT
  in 207 Peugeot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1524939/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-10-16 Thread Alexandre Magno
Yes,  Shankey.  If I'm not mistaken and if I remember correctly, this is
the code that I have used in that project at GitHub.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1566229] [NEW] XPS 13 9350 Unity freeze

2016-04-05 Thread Alexandre Strzelewicz
Public bug reported:

Sometime there is a freeze during 1 to 10 seconds when I use my new
XPS13 with Ubuntu 16.04. It happens that Unity get restarted totally
(all window disappear and appear again)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-16-generic 4.4.0-16.32 [modified: 
boot/vmlinuz-4.4.0-16-generic]
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  shant  1623 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr  5 11:59:49 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=745a5726-fc6f-4fce-b2c4-009359f51d32
InstallationDate: Installed on 2016-04-05 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
 Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=e735b0f3-ce4f-4486-82ed-ddb5b4c59d26 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-16-generic N/A
 linux-backports-modules-4.4.0-16-generic  N/A
 linux-firmware1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 09JHRY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566229

Title:
  XPS 13 9350 Unity freeze

Status in linux package in Ubuntu:
  New

Bug description:
  Sometime there is a freeze during 1 to 10 seconds when I use my new
  XPS13 with Ubuntu 16.04. It happens that Unity get restarted totally
  (all window disappear and appear again)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32 [modified: 
boot/vmlinuz-4.4.0-16-generic]
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shant  1623 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr  5 11:59:49 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=745a5726-fc6f-4fce-b2c4-009359f51d32
  InstallationDate: Installed on 2016-04-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=e735b0f3-ce4f-4486-82ed-ddb5b4c59d26 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566229/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1566229] Re: XPS 13 9350 Unity freeze

2016-04-05 Thread Alexandre Strzelewicz
Hello Joseph,

I received my XPS 2 days ago, there was already Windows 10 installed. I
downloaded Ubuntu 16.04, created an ubuntu usb key (with unetbootin) and
installed the system as is.

I have not made any kernel upgrade.

How to test the latest upstream kernel? If you have any link describing
how to do this, its welcome.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566229

Title:
  XPS 13 9350 Unity freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime there is a freeze during 1 to 10 seconds when I use my new
  XPS13 with Ubuntu 16.04. It happens that Unity get restarted totally
  (all window disappear and appear again)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32 [modified: 
boot/vmlinuz-4.4.0-16-generic]
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shant  1623 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr  5 11:59:49 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=745a5726-fc6f-4fce-b2c4-009359f51d32
  InstallationDate: Installed on 2016-04-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=e735b0f3-ce4f-4486-82ed-ddb5b4c59d26 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566229/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1566229] Re: XPS 13 9350 Unity freeze

2016-04-05 Thread Alexandre Strzelewicz
Alright I found the link, I will try to upgrade and will keep you
informed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566229

Title:
  XPS 13 9350 Unity freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime there is a freeze during 1 to 10 seconds when I use my new
  XPS13 with Ubuntu 16.04. It happens that Unity get restarted totally
  (all window disappear and appear again)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32 [modified: 
boot/vmlinuz-4.4.0-16-generic]
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shant  1623 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr  5 11:59:49 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=745a5726-fc6f-4fce-b2c4-009359f51d32
  InstallationDate: Installed on 2016-04-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=e735b0f3-ce4f-4486-82ed-ddb5b4c59d26 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566229/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1566229] Re: XPS 13 9350 Unity freeze

2016-04-05 Thread Alexandre Strzelewicz
Ok I just tried it:

shant@onyx:~$ uname -a
Linux onyx 4.6.0-040600rc2-generic #201604031130 SMP Sun Apr 3 15:32:46 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

And the bug still exists (happened 2 times during 5/10 secs)

If I can be of any help to diagnose this bug, please let me know,

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566229

Title:
  XPS 13 9350 Unity freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime there is a freeze during 1 to 10 seconds when I use my new
  XPS13 with Ubuntu 16.04. It happens that Unity get restarted totally
  (all window disappear and appear again)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32 [modified: 
boot/vmlinuz-4.4.0-16-generic]
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shant  1623 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr  5 11:59:49 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=745a5726-fc6f-4fce-b2c4-009359f51d32
  InstallationDate: Installed on 2016-04-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=e735b0f3-ce4f-4486-82ed-ddb5b4c59d26 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566229/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1566229] Re: XPS 13 9350 Unity freeze

2016-04-12 Thread Alexandre Strzelewicz
4.6 rc3 installed, been one hour playing around, no freeze at all!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566229

Title:
  XPS 13 9350 Unity freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime there is a freeze during 1 to 10 seconds when I use my new
  XPS13 with Ubuntu 16.04. It happens that Unity get restarted totally
  (all window disappear and appear again)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32 [modified: 
boot/vmlinuz-4.4.0-16-generic]
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shant  1623 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr  5 11:59:49 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=745a5726-fc6f-4fce-b2c4-009359f51d32
  InstallationDate: Installed on 2016-04-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=e735b0f3-ce4f-4486-82ed-ddb5b4c59d26 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566229/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1566229] Re: XPS 13 9350 Unity freeze

2016-04-12 Thread Alexandre Strzelewicz
Sometimes the lag is there, but it's much more usable than before

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566229

Title:
  XPS 13 9350 Unity freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime there is a freeze during 1 to 10 seconds when I use my new
  XPS13 with Ubuntu 16.04. It happens that Unity get restarted totally
  (all window disappear and appear again)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32 [modified: 
boot/vmlinuz-4.4.0-16-generic]
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shant  1623 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr  5 11:59:49 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=745a5726-fc6f-4fce-b2c4-009359f51d32
  InstallationDate: Installed on 2016-04-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=e735b0f3-ce4f-4486-82ed-ddb5b4c59d26 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566229/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1566229] Re: XPS 13 9350 Unity freeze

2016-04-12 Thread Alexandre Strzelewicz
It stopped working (total freeze), if I can be of any help please let me
know

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566229

Title:
  XPS 13 9350 Unity freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime there is a freeze during 1 to 10 seconds when I use my new
  XPS13 with Ubuntu 16.04. It happens that Unity get restarted totally
  (all window disappear and appear again)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32 [modified: 
boot/vmlinuz-4.4.0-16-generic]
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shant  1623 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr  5 11:59:49 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=745a5726-fc6f-4fce-b2c4-009359f51d32
  InstallationDate: Installed on 2016-04-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=e735b0f3-ce4f-4486-82ed-ddb5b4c59d26 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566229/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-10-26 Thread Alexandre Magno
The "success" that I got was with wifi's bad sensibility and bluetooth
without communication with smartphone.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-11-03 Thread Alexandre Magno
I want notify that I have no more access to a test machine. The project
at GitHub is stopped but still accepts pull requests. Sorry.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

2015-11-03 Thread Alexandre Magno
My brother donated the machine to my brother in law and he does not use
GNU/Linux.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1189721

Title:
  Ralink RT3290 doesn't have a bluetooth driver

Status in Linux:
  Unknown
Status in Linux Mint:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Raring Ubuntu has a wifi driver for the RT3290 that works out of
  the box.

  It still does not have bluetooth support.

  This thread in the Ubuntu forums links to a driver that is claimed to
  work:

  http://ubuntuforums.org/showthread.php?t=2115570
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graeme 2412 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70
  InstallationDate: Installed on 2013-05-17 (144 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.32
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1529049] [NEW] Switch bluetooth keyboard from qwerty to azerty

2015-12-24 Thread Alexandre Payet
Public bug reported:

Trying convergence, I've noticed that :

When a bluetooth keyboard is paired, the keyboard is by default in
Qwerty (even if it's an Azerty keyboard and the settings of UT are on
French Azerty keyboard layout)

We should have an option to set the Azerty / Qwerty option in bluetooth 
settings.
Or a better solution could be that the bluetooth keyboard layout is set to the 
default keyboard layout we have put in Language settings.

Does someone know a way to set correctly the layout of the bluetooth
keyboard ? (I've tried : 'loadkeys fr' in terminal but this didn't work,
I suspect that the default layout was already on fr but the bluetooth
keyboard doesn't detect it)

Device : mako rc-proposed last revision of 24 dec 2015

** Affects: ubuntu-keyboard
 Importance: Undecided
 Status: New

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bluetooth convergence keyboard

** Also affects: ubuntu-keyboard
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-keyboard (Ubuntu)

** Tags added: keyboard

** Also affects: bluez (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: bluetooth convergence

** Description changed:

  Trying convergence, I've noticed that :
  
  When a bluetooth keyboard is paired, the keyboard is by default in
  Qwerty (even if it's an Azerty keyboard and the settings of UT are on
  French Azerty keyboard layout)
  
  We should have an option to set the Azerty / Qwerty option in bluetooth 
settings.
  Or a better solution could be that the bluetooth keyboard layout is set to 
the default keyboard layout we have put in Language settings.
  
  Does someone know a way to set correctly the layout of the bluetooth
  keyboard ? (I've tried : 'loadkeys fr' in terminal but this didn't work,
  I suspect that the default layout was already on fr but the bluetooth
  keyboard doesn't detect it)
+ 
+ Device : mako rc-proposed last revision of 24 dec 2015

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1529049

Title:
  Switch bluetooth keyboard from qwerty to azerty

Status in ubuntu-keyboard:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Trying convergence, I've noticed that :

  When a bluetooth keyboard is paired, the keyboard is by default in
  Qwerty (even if it's an Azerty keyboard and the settings of UT are on
  French Azerty keyboard layout)

  We should have an option to set the Azerty / Qwerty option in bluetooth 
settings.
  Or a better solution could be that the bluetooth keyboard layout is set to 
the default keyboard layout we have put in Language settings.

  Does someone know a way to set correctly the layout of the bluetooth
  keyboard ? (I've tried : 'loadkeys fr' in terminal but this didn't
  work, I suspect that the default layout was already on fr but the
  bluetooth keyboard doesn't detect it)

  Device : mako rc-proposed last revision of 24 dec 2015

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1529049/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1528856] Re: bluetooth & car handsfree issue

2015-12-24 Thread Alexandre Payet
I've noticed similar problem on nexus 4 rc-proposed.

I've tried to describe it in this bug report #1524939

This could come from ofono package too (sometime it show x icons
speaker, sometimes the bluetooth speaker icon). Even with the bluetooth
speaker icon, it's doesn't work sometimes. For me I've to manually
disconnect and reconnect or more "forget" the bluetooth car system and
do a new connection to it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1528856

Title:
  bluetooth & car handsfree issue

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  When playing music through headphone output connected to aux car radio
  input and going to call someone while driving, i only hear some
  "beeps" and apparently the call was succesfull but i can't hear
  anything and no sound is transmitted . In the phone screen appears the
  speaker icon with an x (like there is no speaker connected) but phone
  and car are paired correctly.

  In addition to, when to SIM cards are inserted y only receive call
  through bluetooth for the one i have selected as default, for the
  other SIM, ring tones sounds in phone speaker and no through bluetooth
  device.

  Device: BQ Aquaris E4.5 Ubuntu Edition
  Channel: RC-proposed
  Version: r604

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1528856/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1724232] Re: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256'

2017-12-07 Thread Alexandre Bourget
Hitting this with 4.13.0-17-generic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1724232

Title:
  sysfs: cannot create duplicate filename
  '/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256'

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  bluetooth can not be used. 
  Steps to reproduce:

  - Connect bluetooth headset
  - Wait a few minutes, switch profile

  Result:

  - The bluetooth device is disconnected and the following traces are
  printed in dmesg

  [  104.514539] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [  104.514544] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [  104.524525] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [  104.524530] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [  104.524531] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [  106.587815] Bluetooth: hci0 SCO packet for unknown connection handle 258
  [  133.101575] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256'
  [  133.101593] [ cut here ]
  [  133.101603] WARNING: CPU: 1 PID: 382 at 
/build/linux-XO_uEE/linux-4.13.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x56/0x70
  [  133.101605] Modules linked in: cmac rfcomm ccm xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter bnep arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_alps 
iwlmvm mac80211 snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc 
snd_hda_codec_generic snd_soc_sst_ipc iwlwifi snd_soc_sst_dsp snd_hda_ext_core 
snd_soc_sst_match cfg80211 snd_soc_core rtsx_pci_ms snd_compress memstick 
ac97_bus snd_pcm_dmaengine dell_rbtn dell_laptop dell_smm_hwmon intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel
  [  133.101672]  aes_x86_64 crypto_simd glue_helper cryptd intel_cstate 
intel_rapl_perf serio_raw dell_wmi dell_smbios wmi_bmof dcdbas snd_hda_intel 
snd_usb_audio snd_hda_codec snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm 
joydev shpchp snd_seq_midi idma64 snd_seq_midi_event virt_dma snd_rawmidi 
snd_seq cdc_mbim cdc_wdm qcserial mei_me mei cdc_ncm usb_wwan usbnet 
snd_seq_device usbserial mii snd_timer intel_lpss_pci snd uvcvideo 
videobuf2_vmalloc videobuf2_memops soundcore videobuf2_v4l2 videobuf2_core 
input_leds videodev media btusb processor_thermal_device btrtl 
intel_pch_thermal intel_soc_dts_iosf hci_uart btbcm serdev btqca btintel 
bluetooth ecdh_generic intel_lpss_acpi intel_lpss int3403_thermal 
int340x_thermal_zone intel_hid int3400_thermal tpm_crb sparse_keymap 
acpi_thermal_rel acpi_als acpi_pad
  [  133.101743]  kfifo_buf mac_hid industrialio parport_pc ppdev lp parport 
ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 i2c_algo_bit 
drm_kms_helper rtsx_pci_sdmmc e1000e syscopyarea sysfillrect sysimgblt 
fb_sys_fops ptp nvme pps_core nvme_core drm rtsx_pci wmi i2c_hid hid video 
pinctrl_sunrisepoint pinctrl_intel
  [  133.101783] CPU: 1 PID: 382 Comm: kworker/u9:1 Not tainted 
4.13.0-16-generic #19-Ubuntu
  [  133.101785] Hardware name: Dell Inc. Latitude 7380/0KK5D1, BIOS 1.6.4 
08/29/2017
  [  133.101815] Workqueue: hci0 hci_rx_work [bluetooth]
  [  133.101818] task: 990d1105 task.stack: ba328203c000
  [  133.101824] RIP: 0010:sysfs_warn_dup+0x56/0x70
  [  133.101827] RSP: 0018:ba328203fb80 EFLAGS: 00010282
  [  133.101829] RAX: 0073 RBX: 990d0dbc8000 RCX: 

  [  133.101831] RDX:  RSI: 990d2e48dc78 RDI: 
990d2e48dc78
  [  133.101833] RBP: ba328203fb98 R08: 0001 R09: 
03ef
  [  133.101834] R10: 0001 R11:  R12: 
990cbafc8060
  [  133.101836] R13: 990d19e8bbb8 R14: 990cbad4aa88 R15: 
990c944c2c50
  [  133.101839] FS:  () GS:990d2e48() 
knlGS:
  [  133.101841] CS:  0010 DS:  ES:  CR0: 80050033
  [  133.101843] CR2: 7f536eb7000c CR3: 0002ec209000 CR4: 
003406e0
  [  133.101845] DR0:  DR1:  DR2: 

  [  133.101846] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  133.101848] Call Trace:
  [  133.101855]  sysfs_create_dir_ns+0x77/0x90
  [  133.101861]  kobject_add_internal+0xac/0x2b0
  [  133.101864]  kobject_add+0x71/0xd0
  [  133.101871]  ? kfree_const+0x20/0x30
  [  133.101878]  device_add+0x12c/0x680
  [  133.101907]  hci_conn_add_sysfs+0x49/0xc0 [bluetooth]
  [  133.101932]  hci_conn_complete_evt.is

  1   2   >