[Kernel-packages] [Bug 2038960] Re: X11 session crash when resuming from sleed mode

[Alexandre AM MOYRAND]

any help please?

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

Title:
  X11 session crash when resuming from sleed mode

Status in linux-signed-hwe-6.2 package in Ubuntu:
  New

Bug description:
  after my laptop has been in sleep mode I try to login.
  After 1 enter my password, it asks me a second time my password and the 
system start a brand new session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 21:22:07 2023
  InstallationDate: Installed on 2023-09-22 (18 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038960/+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 2038960] [NEW] X11 session crash when resuming from sleed mode

[Alexandre AM MOYRAND]

Public bug reported:

after my laptop has been in sleep mode I try to login.
After 1 enter my password, it asks me a second time my password and the system 
start a brand new session.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 10 21:22:07 2023
InstallationDate: Installed on 2023-09-22 (18 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-6.2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  X11 session crash when resuming from sleed mode

Status in linux-signed-hwe-6.2 package in Ubuntu:
  New

Bug description:
  after my laptop has been in sleep mode I try to login.
  After 1 enter my password, it asks me a second time my password and the 
system start a brand new session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 21:22:07 2023
  InstallationDate: Installed on 2023-09-22 (18 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038960/+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 2033295] Re: AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen

[Alexandre Hen]

Same problem here on Ubuntu 22.04.3 with latest and updated 6.2 kernel.
On a Thinkpad P14s gen1 20Y with a Ryzen 4750u pro.

It is not possible to use this laptop with Ubuntu 23.04 (I tried, same
problem because same kernel I guess) nor 22.04.3.

-- 
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/2033295

Title:
  AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary.
  AMD Ryzen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Frequently, when I just use the computer, the mouse cursor freezes,
  the screen starts to flicker and freezes (screen flickers between
  entirely black and desktop visible). No interaction possible. In most
  cases Ctrl-Alt-Prnt-REISUB works to hard reboot the system.

  Frequency: Freezes happen several times a day. Unsaved work is lost.

  I noticed that:
  * The freezes usually happen when an external display is connected (it does 
not matter whether USB-C or HDMI). The freezes rarely happen when no external 
display is connected.
  * The freezes happen with Wayland and X11, with Ubuntu UI and Gnome Shell.
  * The freezes happen randomly, but I have the feeling that they happen more 
often when "something graphical" happens, e.g. when I go to the Gnome Shell 
overview, desktop switching, or when I switch to/from full screen mode, click 
on an image to scale it, or when I use map services in the web browser like 
Google Maps or radio.garden.
  * The freezes even more often happened when WebGL is active in Firefox or 
Chomium.
  * I encounter these annoying freezes already for several weeks.

  Having looked at the log files, I assume that AMDGPU is at the core of
  the problem.

  System:
  Ubuntu 23.04 (up to date), Wayland (freezes also happen with X11), Gnome 
44.3. 
  Linux 6.2.0-31-generic
  Lenovo ThinkPad T14s Gen 1 (with most recent BIOS/UEFI 1.44), AMD Ryzen™ 7 
PRO 4750U with Radeon™ Graphics × 16.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-06-06 (813 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20UJS00K00
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=9eae73b3-aab9-4f80-9203-01ac00f03c33 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-31-generic N/A
   linux-backports-modules-6.2.0-31-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6
  Tags:  lunar wayland-session
  Uname: Linux 6.2.0-31-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-11 (110 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UJS00K00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UJS00K00:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJS00K00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UJ_BU_Think_FM_ThinkPadT14sGen1:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UJS00K00
  dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033295/+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 2025530] Re: package linux-image-6.2.0-1005-oracle 6.2.0-1005.5 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

[Alexandre Klostermann]

Same Here, impossible to update using APt or ubuntu update:

 sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libnvidia-cfg1-515 libnvidia-common-515 libnvidia-compute-515 
libnvidia-compute-515:i386 libnvidia-decode-515
  libnvidia-decode-515:i386 libnvidia-encode-515 libnvidia-encode-515:i386 
libnvidia-extra-515 libnvidia-fbc1-515
  libnvidia-fbc1-515:i386 libnvidia-gl-515 libnvidia-gl-515:i386 
linux-signatures-nvidia-6.2.0-1005-oracle
  nvidia-compute-utils-515 nvidia-kernel-source-515 nvidia-utils-515 
xserver-xorg-video-nvidia-515
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  linux-modules-nvidia-515-generic-hwe-22.04 
linux-signatures-nvidia-6.2.0-24-generic
The following packages will be upgraded:
  linux-firmware
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
2 not fully installed or removed.
Need to get 281 MB of archives.
After this operation, 3.072 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://br.archive.ubuntu.com/ubuntu lunar-updates/main amd64 
linux-firmware all 20230323.gitbcdcfbcf-0ubuntu1.2 [281 MB]
Fetched 281 MB in 20s (14,3 MB/s)   

  
(Reading database ... 280370 files and directories currently installed.)
Preparing to unpack .../linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2_all.deb 
...
Unpacking linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) over 
(20230323.gitbcdcfbcf-0ubuntu1.1) ...
Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ...
update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic
Setting up linux-image-6.2.0-1007-lowlatency (6.2.0-1007.7) ...
I: /boot/initrd.img is now a symlink to initrd.img-6.2.0-1007-lowlatency
Setting up linux-image-6.2.0-1005-oracle (6.2.0-1005.5) ...
I: /boot/initrd.img.old is now a symlink to initrd.img-6.2.0-1005-oracle
Processing triggers for linux-image-6.2.0-1007-lowlatency (6.2.0-1007.7) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-1007-lowlatency
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Error! Your kernel headers for kernel 6.2.0-1007-lowlatency cannot be found at 
/lib/modules/6.2.0-1007-lowlatency/build or 
/lib/modules/6.2.0-1007-lowlatency/source.
Please install the linux-headers-6.2.0-1007-lowlatency package or use the 
--kernelsourcedir option to tell DKMS where it's located.
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Error! Your kernel headers for kernel 6.2.0-1007-lowlatency cannot be found at 
/lib/modules/6.2.0-1007-lowlatency/build or 
/lib/modules/6.2.0-1007-lowlatency/source.
Please install the linux-headers-6.2.0-1007-lowlatency package or use the 
--kernelsourcedir option to tell DKMS where it's located.
dkms autoinstall on 6.2.0-1007-lowlatency/x86_64 failed for evdi(1) nvidia(1)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.2.0-1007-lowlatency (--configure):
 installed linux-image-6.2.0-1007-lowlatency package post-installation script 
subprocess returned error exit status 1
Processing triggers for linux-image-6.2.0-1005-oracle (6.2.0-1005.5) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-1005-oracle
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Error! Your kernel headers for kernel 6.2.0-1005-oracle cannot be found at 
/lib/modules/6.2.0-1005-oracle/build or /lib/modules/6.2.0-1005-oracle/source.
Please install the linux-headers-6.2.0-1005-oracle package or use the 
--kernelsourcedir option to tell DKMS where it's located.
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Error! Your kernel headers for kernel 6.2.0-1005-oracle cannot be found at 
/lib/modules/6.2.0-1005-oracle/build or /lib/modules/6.2.0-1005-oracle/source.
Please install the linux-headers-6.2.0-1005-oracle package or use the 
--kernelsourcedir option to tell DKMS where it's located.
dkms autoinstall on 6.2.0-1005-oracle/x86_64 failed for evdi(1) nvidia(1)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package 

[Kernel-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

[Alexandre Paulo]

Observed today on chrome. Using "--no-sandbox" as temporary fix while
waiting for permanent solution.

Kubuntu 22.04
Kernel 5.19.0-1010-nvidia-lowlatency (64-bit)

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

Title:
  Chrome crashes with FATAL:credentials.cc(127)] Check failed: . :
  Permission denied (13)

Status in linux-meta-nvidia-5.19 package in Ubuntu:
  Confirmed

Bug description:
  With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I 
experience that google-chrome crashes.
  It shows

  ```shell
  [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap (core dumped)".
  ```

  To be honest I don't think it has anything to do with google-chrome at all.
  When google-chrome starts it (normally) request the system key-manager 
(KWallet in my case) for access to the users keys before it actually shows 
anything from chrome. Not even that part (the KWallet password box) shows up.

  I can only reproduce this problem with this specific kernel. It should
  be possible to take google-chrome out of the equation by using another
  application that starts by request the desktop key manager for access.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-nvidia-5.19 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92
  Uname: Linux 5.15.0-1023-nvidia x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Apr 28 11:23:23 2023
  InstallationDate: Installed on 2016-01-08 (2666 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: linux-meta-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen

[Alexandre Ghiti]

> Without linux-image-5.19.0-21-generic i915-fix the USB Live will never
boot in an intel Tiger Lake/Alder Lake IGPU

Indeed the live desktop installer fails to boot on a 12th intel cpu: I
have lots of kernel backtraces in dmesg caused by nouveau driver. The
kernel from the installer is 5.19.0-21.

-- 
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/1991704

Title:
  Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After today's Kinetic update my Framework laptop won't boot.

  The boot hangs after this output:

  [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci 
:00:07.1: DPC: RP PIO log size 8 is invalid
  [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci 
:00:07.3: DPC: RP PIO log size 0 is invalid
  [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst
  ead

  Falling back to 5.19.0-15-generic works.

  My Thinkpad X1 Carbon 6th gen does not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik4014 F wireplumber
   /dev/snd/seq:jik4009 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 13:55:09 2022
  InstallationDate: Installed on 2022-09-17 (16 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Framework Laptop (12th Gen Intel Core)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 3.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.04
  dmi.board.asset.tag: *
  dmi.board.name: FRANMACP04
  dmi.board.vendor: Framework
  dmi.board.version: A4
  dmi.chassis.asset.tag: FRANDACPA423350021
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04:
  dmi.product.family: 13in Laptop
  dmi.product.name: Laptop (12th Gen Intel Core)
  dmi.product.sku: FRANDACP04
  dmi.product.version: A4
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1990964] Re: FTBFS on kinetic

[Alexandre Ghiti]

> In general, does strace get a release for each kernel release? Should
it be updated in parallel?

I tried to find an answer to this question and I would say yes. As is
stated in [1], strace follows the same release cycle as the kernel. In
addition, every strace release at least comes with a non-backward
compatible change, which is the update of the ioctl commands list (for
an example see [2]).

So instead of cherry-picking the 2 commits mwhudson mentions, I'd rather
update to 5.19 since the default kernel for kinetic is 5.19 (both
commits belong to this version).

[1] https://lists.strace.io/pipermail/strace-devel/2022-August/011094.html
[2] 
https://github.com/strace/strace/commit/22f61979141fa5c9732d01ea69c23f46a3e2868a

-- 
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/1990964

Title:
  FTBFS on kinetic

Status in linux package in Ubuntu:
  Fix Released
Status in strace package in Ubuntu:
  Triaged

Bug description:
  As can be seen in [1], strace FTBFS in kinetic: this is caused by the
  kernel headers (linux-libc-dev) which do not define F_GETLK64 and
  other on 64b builds because the kernel contains a bogus commit
  (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in
  fcntl.h"). This commit actually did the opposite of what it was
  supposed to do, namely defining those macros even on 64b builds. There
  is an attempt here to fix this which was not merged yet:
  
https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/

  [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic-
  amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+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 1979633] Re: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated"

[Alexandre Ghiti]

Hi Alberto,

Sorry I did not get notified of your answers...Thanks for your
investigation: did you file a bug against the kernel then?

Thanks,

Alex

-- 
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/1979633

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

Status in linux package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1992458] [NEW] Disable VMAP_STACK as it causes crash in EFI

[Alexandre Ghiti]

*** This bug is a duplicate of bug 1967130 ***
https://bugs.launchpad.net/bugs/1967130

Public bug reported:

[ Impact ]

The kernel crashes when trying to access the EFI runtime
services/variables if the kernel is configured with CONFIG_VMAP_STACK.
Indeed, to access EFI variables/services, the kernel switches to the EFI
page table which is created during the boot process *but* is never
updated during the life of the kernel: as CONFIG_VMAP_STACK allocates
the kernel stack in the vmalloc region and maps it in the *kernel page
table*, the EFI page table never has this new mapping and then segfaults
when trying to access the kernel stack of the current process.

This is easier to reproduce on the Unmatched than on QEMU (never
reproduced on this platform):

ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/*

Which gives rise to a kernel crash, gdb traces below:

(gdb) bt
#0  handle_exception () at /home/alex/work/linux/arch/riscv/kernel/entry.S:27
#1  0x8080741a in efi_virtmap_load () at 
/home/alex/work/linux/arch/riscv/include/asm/current.h:31
#2  0x in ?? ()
(gdb) p/x $stval
$1 = 0xffc8946cbc38
(gdb) display /i $sepc
1: x/i $sepc
   0x8000392c :sd  ra,8(sp)
(gdb) p/x $sp
$6 = 0xffc8946cbc30

A workaround can be to disable CONFIG_VMAP_STACK but actually any
mapping in the kernel page table that is not also added to the EFI page
table can cause such crash: but I'm not sure this can happen and this
workaround was enough in the previous release to fix this bug and to be
able to live install a system.

I advise to implement this workaround for now as I'm implementing the
proper patch which consists in updating the EFI page table before
switching to it, just like x86 does.

[ Test Plan ]

Use a kernel with CONFIG_VMAP_STACK disabled and simply enter the
following command, preferably on the Unmatched:

ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/*

This should not trigger a crash.

[ Where problems could occur ]

As said above, just disabling CONFIG_VMAP_STACK may not be enough.

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

** This bug has been marked a duplicate of bug 1967130
   rcu_sched detected stalls on CPUs/tasks

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

Title:
  Disable VMAP_STACK as it causes crash in EFI

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  [ Impact ]

  The kernel crashes when trying to access the EFI runtime
  services/variables if the kernel is configured with CONFIG_VMAP_STACK.
  Indeed, to access EFI variables/services, the kernel switches to the
  EFI page table which is created during the boot process *but* is never
  updated during the life of the kernel: as CONFIG_VMAP_STACK allocates
  the kernel stack in the vmalloc region and maps it in the *kernel page
  table*, the EFI page table never has this new mapping and then
  segfaults when trying to access the kernel stack of the current
  process.

  This is easier to reproduce on the Unmatched than on QEMU (never
  reproduced on this platform):

  ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/*

  Which gives rise to a kernel crash, gdb traces below:

  (gdb) bt
  #0  handle_exception () at /home/alex/work/linux/arch/riscv/kernel/entry.S:27
  #1  0x8080741a in efi_virtmap_load () at 
/home/alex/work/linux/arch/riscv/include/asm/current.h:31
  #2  0x in ?? ()
  (gdb) p/x $stval
  $1 = 0xffc8946cbc38
  (gdb) display /i $sepc
  1: x/i $sepc
 0x8000392c :  sd  ra,8(sp)
  (gdb) p/x $sp
  $6 = 0xffc8946cbc30

  A workaround can be to disable CONFIG_VMAP_STACK but actually any
  mapping in the kernel page table that is not also added to the EFI
  page table can cause such crash: but I'm not sure this can happen and
  this workaround was enough in the previous release to fix this bug and
  to be able to live install a system.

  I advise to implement this workaround for now as I'm implementing the
  proper patch which consists in updating the EFI page table before
  switching to it, just like x86 does.

  [ Test Plan ]

  Use a kernel with CONFIG_VMAP_STACK disabled and simply enter the
  following command, preferably on the Unmatched:

  ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/*

  This should not trigger a crash.

  [ Where problems could occur ]

  As said above, just disabling CONFIG_VMAP_STACK may not be enough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1992458/+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 1991790] [NEW] Disable sv57 as the userspace is not ready

[Alexandre Ghiti]

Public bug reported:

[ Impact ]

sv57 breaks Go since Go uses the upper bits of a pointer to store data,
and it is not ready for sv57 yet. It probably breaks other type of
software using this "pointer tagging" technic. The following patch fixes
this: at the moment, there is no way to indicate to the kernel to
downgrade to sv48, so we must patch the kernel.

diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
index 2c4a64e97aec..18a0c70ed313 100644
--- a/arch/riscv/mm/init.c
+++ b/arch/riscv/mm/init.c
@@ -775,6 +775,10 @@ static __init void set_satp_mode(void)
disable_pgtable_l4();
}
 
+   /* UBUNTU: Force disable sv57 and fallback to sv48 */
+   if (pgtable_l5_enabled)
+   disable_pgtable_l5();
+
memset(early_pg_dir, 0, PAGE_SIZE);
memset(early_p4d, 0, PAGE_SIZE);
memset(early_pud, 0, PAGE_SIZE);

[ Test Plan ]

Build an image with the new kernel and make sure snapd started
correctly, or that you can compile a simple helloworld written in Go.

[ Where problems could occur ]

The patch could be wrong, but I already built a kernel with it and it
worked fine.

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

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

Title:
  Disable sv57 as the userspace is not ready

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  [ Impact ]

  sv57 breaks Go since Go uses the upper bits of a pointer to store
  data, and it is not ready for sv57 yet. It probably breaks other type
  of software using this "pointer tagging" technic. The following patch
  fixes this: at the moment, there is no way to indicate to the kernel
  to downgrade to sv48, so we must patch the kernel.

  diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
  index 2c4a64e97aec..18a0c70ed313 100644
  --- a/arch/riscv/mm/init.c
  +++ b/arch/riscv/mm/init.c
  @@ -775,6 +775,10 @@ static __init void set_satp_mode(void)
  disable_pgtable_l4();
  }
   
  +   /* UBUNTU: Force disable sv57 and fallback to sv48 */
  +   if (pgtable_l5_enabled)
  +   disable_pgtable_l5();
  +
  memset(early_pg_dir, 0, PAGE_SIZE);
  memset(early_p4d, 0, PAGE_SIZE);
  memset(early_pud, 0, PAGE_SIZE);

  [ Test Plan ]

  Build an image with the new kernel and make sure snapd started
  correctly, or that you can compile a simple helloworld written in Go.

  [ Where problems could occur ]

  The patch could be wrong, but I already built a kernel with it and it
  worked fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1991790/+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 1931432] Re: crash FTBFS on riscv64

[Alexandre Ghiti]

Progress is being made and crash could be available for 5.20:
https://lore.kernel.org/all/20220813031753.3097720-1-xianting.t...@linux.alibaba.com/

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

Title:
  crash FTBFS on riscv64

Status in crash package in Ubuntu:
  Confirmed
Status in crash source package in Focal:
  Confirmed
Status in crash source package in Groovy:
  Confirmed

Bug description:
  Crash fails to build from source on riscv at least for Focal and
  Groovy, later releases may also be affected but I haven't confirm it.

  Examples of failed builds :

  Groovy : 
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864
  Focal : 
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432/+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 1982559] [NEW] gpio-poweroff probe failed

[Alexandre Ghiti]

Public bug reported:

I observe the following message in 5.15.0-1015-generic:

[0.656680] poweroff-gpio gpio-poweroff: gpio_poweroff_probe: pm_power_off 
function already registered
[0.665278] poweroff-gpio: probe of gpio-poweroff failed with error -16

It happens because we enabled SBI SRST extension which now handles the
poweroff/reset, we could either do nothing or remove the gpio-poweroff
node from the device tree (introduce a delta with upstream).

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

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

Title:
  gpio-poweroff probe failed

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I observe the following message in 5.15.0-1015-generic:

  [0.656680] poweroff-gpio gpio-poweroff: gpio_poweroff_probe: pm_power_off 
function already registered
  [0.665278] poweroff-gpio: probe of gpio-poweroff failed with error -16

  It happens because we enabled SBI SRST extension which now handles the
  poweroff/reset, we could either do nothing or remove the gpio-poweroff
  node from the device tree (introduce a delta with upstream).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1982559/+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 1973168] [NEW] Package still suggests to install crda whereas it was removed

[Alexandre Ghiti]

Public bug reported:

This package still suggests crda to be installed whereas it was removed
from jammy already: simply remove this from debian/control as done in
[1].

[1]
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13612257/+listing-
archive-extra

** Affects: wireless-regdb (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Package still suggests to install crda whereas it was removed

Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  This package still suggests crda to be installed whereas it was
  removed from jammy already: simply remove this from debian/control as
  done in [1].

  [1]
  
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13612257/+listing-
  archive-extra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1973168/+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 1955042] Re: SBI SRST extension is missing

[Alexandre Ghiti]

This fix was merged in 5.15.0-1005.5.

** Changed in: linux-riscv (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  SBI SRST extension is missing

Status in linux-riscv package in Ubuntu:
  Fix Released

Bug description:
  SBI SRST extension is needed for handling sifive unmatched reboot and
  with the reset now merged into openSBI package, enabling SRST
  extension finally gives us the possibility to reset the board.

  The patch to enable SRST extension can be found here:
  https://lore.kernel.org/all/20210609121322.3058-2-anup.pa...@wdc.com/
  or use the attached patch.

  I tested it on top of 5.13.0-1006.6+22.04.1 on the unmatched board and
  it allows to successfully reboots the board.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1955042/+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 1967130] Re: rcu_sched detected stalls on CPUs/tasks

[Alexandre Ghiti]

The workaround built successfully in my PPA:
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13413205/+listing-
archive-extra

I tested it successfully with the RISC-V live installer (where this
problem was seen).

I did not have time yet to work on the proper fix so I think we should
go for this workaround: @xnox what do you think?

Thanks

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

Title:
  rcu_sched detected stalls on CPUs/tasks

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  When running the riscv64 live installer
  (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-
  live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly
  see rcu_sched stalls related to accessing the UEFI runtime:

  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched 
detected stalls on CPUs/tasks:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu:   3-...0: (3 
GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, 
t=15002 jiffies, g=155853, q=1286)
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1
state:R  running task stack:0 pid: 3715 ppid: 2 flags:0x0008
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq 
efi_call_rts
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] 
__schedule+0x226/0x644

  uname -a:
  Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 
2022 riscv64 riscv64 riscv64 GNU/Linux
  --- 
  ProblemType: Bug
  Architecture: riscv64
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.1004.4
  PackageArchitecture: riscv64
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
  Uname: Linux 5.15.0-1004-generic riscv64
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+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 1967130] Re: rcu_sched detected stalls on CPUs/tasks

[Alexandre Ghiti]

I have a workaround for this:

UBUNTU: SAUCE: riscv: Disable VMAP_STACK since it fails with efi

When VMAP_STACK is enabled, kernel threads have their stacks in the vmalloc
region.

So when The kworker responsible for handling efi work queue (efi_call_rts) 
calls
efi_virtmap_load and then switch_mm, if the stack of the worker is in a 
vmalloc
area not yet synchronized with efi_mm (since RISC-V lazily populates vmalloc
area), an attempt to access this stack will trigger a fault which can't be
resolved since when trying to save the context, a new trap will be 
triggered and
so on.

So disable VMAP_STACK for now until we figure out the correct fix.

And I'm working on the proper fix which consists in synchronizing the
efi page table with the page table of the calling thread before
switching to efi mm.

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

Title:
  rcu_sched detected stalls on CPUs/tasks

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  When running the riscv64 live installer
  (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-
  live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly
  see rcu_sched stalls related to accessing the UEFI runtime:

  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched 
detected stalls on CPUs/tasks:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu:   3-...0: (3 
GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, 
t=15002 jiffies, g=155853, q=1286)
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1
state:R  running task stack:0 pid: 3715 ppid: 2 flags:0x0008
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq 
efi_call_rts
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] 
__schedule+0x226/0x644

  uname -a:
  Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 
2022 riscv64 riscv64 riscv64 GNU/Linux
  --- 
  ProblemType: Bug
  Architecture: riscv64
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.1004.4
  PackageArchitecture: riscv64
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
  Uname: Linux 5.15.0-1004-generic riscv64
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+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 1964796] Re: Fix unmatched ASMedia ASM2824 PCIe link training

[Alexandre Ghiti]

A similar patch that solves the same issue was actually merged for 5.18
[1].

I encountered this bug with our current u-boot (2022.01+dfsg-2ubuntu1)
and linux kernel (5.15.0-1004.4): I applied the patch in [1] on top of
5.15.0-1004.4 successfully and it solved the problem. So as you already
tagged it, this should be cherry-picked for 22.04. A similar patch for
u-boot exists, I'll report a new bug there.

Thanks

[1] https://patchwork.kernel.org/project/linux-
riscv/patch/20220318152430.526320-1-ben.do...@codethink.co.uk/

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

Title:
  Fix unmatched ASMedia ASM2824 PCIe link training

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  
https://lore.kernel.org/all/alpine.deb.2.21.2202010240190.58...@angie.orcam.me.uk/raw

  It has been discovered that Unmatched board ships ASMedia ASM2824 PCIe
  which frequently fails to complete link training and negotiate stable
  and fast speeds.

  To ensure PCIe devices on Unmatched board can operate with stable and
  predictable link speeds cherry-pick upstream submitted patch that
  resolves the issue.

  It is currently applied as a SAUCE patch, whilst the upstream
  inclusion review is ongoing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964796/+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 1961789] [NEW] "ponteiro e tela travaram, não consegui ter acesso a nada do notebook" nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build

[Alexandre Pereira de Souza]

Public bug reported:

Estava acessando o meu endereço de e-mail e havia deixado o visual
studio code e libreOffice Writer em aberto. Quando tentei abrir um
e-mail, travou o ponteiro do mouse e a tela travou juntamente. Não
consegui ter acesso a anda do notebook, não consegui nem desligar ele.
Ficou ligado a noite toda, pela manhã eu vi que ele tinha descarregado e
coloquei na carga e consegui ligar ele, e aparentemente voltou ao
normal.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83
Uname: Linux 5.10.0-1057-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.14.0-1024-oem
Date: Tue Feb 22 09:47:57 2022
Dependencies:
 
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
DuplicateSignature: 
dkms:nvidia-kernel-source-440:440.100-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/440.100/build/common/inc/nv-mm.h:149:45:
 error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer 
type [-Werror=incompatible-pointer-types]
InstallationDate: Installed on 2022-02-03 (19 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
PackageVersion: 440.100-0ubuntu0.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.2
SourcePackage: nvidia-graphics-drivers-440
Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-440 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  "ponteiro e tela travaram, não consegui ter acesso a nada do notebook"
  nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel
  module failed to build

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  Estava acessando o meu endereço de e-mail e havia deixado o visual
  studio code e libreOffice Writer em aberto. Quando tentei abrir um
  e-mail, travou o ponteiro do mouse e a tela travou juntamente. Não
  consegui ter acesso a anda do notebook, não consegui nem desligar ele.
  Ficou ligado a noite toda, pela manhã eu vi que ele tinha descarregado
  e coloquei na carga e consegui ligar ele, e aparentemente voltou ao
  normal.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83
  Uname: Linux 5.10.0-1057-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.14.0-1024-oem
  Date: Tue Feb 22 09:47:57 2022
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DuplicateSignature: 
dkms:nvidia-kernel-source-440:440.100-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/440.100/build/common/inc/nv-mm.h:149:45:
 error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer 
type [-Werror=incompatible-pointer-types]
  InstallationDate: Installed on 2022-02-03 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  PackageVersion: 440.100-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: nvidia-graphics-drivers-440
  Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1961789/+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 1955042] [NEW] SBI SRST extension is missing

[Alexandre Ghiti]

Public bug reported:

SBI SRST extension is needed for handling sifive unmatched reboot and
with the reset now merged into openSBI package, enabling SRST extension
finally gives us the possibility to reset the board.

The patch to enable SRST extension can be found here:
https://lore.kernel.org/all/20210609121322.3058-2-anup.pa...@wdc.com/ or
use the attached patch.

I tested it on top of 5.13.0-1006.6+22.04.1 on the unmatched board and
it allows to successfully reboots the board.

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

** Attachment added: "0001-RISC-V-Use-SBI-SRST-extension-when-available.patch"
   
https://bugs.launchpad.net/bugs/1955042/+attachment/5548032/+files/0001-RISC-V-Use-SBI-SRST-extension-when-available.patch

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

Title:
  SBI SRST extension is missing

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  SBI SRST extension is needed for handling sifive unmatched reboot and
  with the reset now merged into openSBI package, enabling SRST
  extension finally gives us the possibility to reset the board.

  The patch to enable SRST extension can be found here:
  https://lore.kernel.org/all/20210609121322.3058-2-anup.pa...@wdc.com/
  or use the attached patch.

  I tested it on top of 5.13.0-1006.6+22.04.1 on the unmatched board and
  it allows to successfully reboots the board.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1955042/+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 1943030] Re: Enable riscv64 build of nvidia-settings

[Alexandre Ghiti]

I may be wrong here but I'd see things differently: when the binaries
get available, we won't be notified and people will start trying to
install it and it will fail since we decided not to make it available. A
few people will take the time to file a bug report, others will get
disappointed: this seems like a bad user experience to me whereas it
does not cost that much to enable.

But I'm quite new to this, so feel free to explain where I'm wrong :)

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

Title:
  Enable riscv64 build of nvidia-settings

Status in nvidia-settings package in Ubuntu:
  Incomplete

Bug description:
  Please enable the build on riscv64 architecture of nvidia-settings
  since it works fine using the attached debdiff:
  https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+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 1943030] Re: Enable riscv64 build of nvidia-settings

[Alexandre Ghiti]

** Tags added: fr-1689

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

Title:
  Enable riscv64 build of nvidia-settings

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  Please enable the build on riscv64 architecture of nvidia-settings
  since it works fine using the attached debdiff:
  https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+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 1943030] [NEW] Enable riscv64 build of nvidia-settings

[Alexandre Ghiti]

Public bug reported:

Please enable the build on riscv64 architecture of nvidia-settings since
it works fine using the attached debdiff:
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "nvidia_settings_debdiff.patch"
   
https://bugs.launchpad.net/bugs/1943030/+attachment/5523773/+files/nvidia_settings_debdiff.patch

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

Title:
  Enable riscv64 build of nvidia-settings

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  Please enable the build on riscv64 architecture of nvidia-settings
  since it works fine using the attached debdiff:
  https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+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 1914052] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build

[Alexandre de Barros Cabral]

*** This bug is a duplicate of bug 1872908 ***
https://bugs.launchpad.net/bugs/1872908

I have this error to install the wi-fi drive. is blocking me.
help me please

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-41-generic
  Date: Mon Feb  1 10:09:25 2021
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
 error: implicit declaration of function ‘ioremap_nocache’; did you mean 
‘ioremap_cache’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2021-02-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu5
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1914052/+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 1882968] Re: ath10k_pci failed to wake target for write32

[Alexandre Anoutchine]

@thedoctar Thank you for the suggestion!
I don't really want install the newest kernel, do you think it can work without 
(5.4.0-42-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/1882968

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32

[Alexandre Anoutchine]

It looks like I'm affected by this issue too. I loose connection and have to 
restart my machine all the time. Is there a way just to reset the module?
@thedoctar how did you solve it? Did you manually I install the latest 
firmware? My system is fully updated but nothing helps.

-- 
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/1882968

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode

[C-alexandre-pires]

I've installed https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/
and the problem seems to have been solved. My laptop is a HP-Pavilion-
Laptop-15-cw1xxx, CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx.

-- 
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/1870971

Title:
  [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad
  L340-17API when in battery mode

Status in linux package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  Freshly installed Xubuntu 20.04 shows black screen instead of login
  screen upon boot on Lenovo Ideapad L340-17API. It is not possible to
  chvt to text terminal when boot is stuck on black screen.

  Booting with 'nomodeset' kernel option works properly but is not an
  option (e.g. screen brightness is not adjustable in this case).

  Another workaround is to ssh to laptop and run systemctl restart
  display-manager.service. After 5-10 seconds upon executing this
  command perfectly working login screen appears.

  Check dmesg. There is apparently related messages from amdgpu driver:

  ...
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start
  апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done
  апр 05 20:46:45 kernel: [drm] Skip scheduling IBs!
  апр 05 20:46:45 kernel: [ cut here ]
  апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at 
include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched]
  апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher 
af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec >
  апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G  
 OE 5.4.0-21-generic #25-Ubuntu
  апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 
07/11/2019
  апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched]
  апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 
[gpu_sched]
  апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 
48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf 
<0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c
  апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246
  апр 05 20:46:45 kernel: RAX:  RBX: 0001 RCX: 

  апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: 

  апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 
0004
  апр 05 20:46:45 kernel: R10:  R11: 0001 R12: 
8cc9ac463c00
  апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 
8cc9a6fc9140
  апр 05 20:46:45 kernel: FS:  () GS:8cc9b88c() 
knlGS:
  апр 05 20:46:45 kernel: CS:  0010 DS:  ES:  CR0: 80050033
  апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 
003406e0
  апр 05 20:46:45 kernel: Call Trace:
  апр 05 20:46:45 kernel:  amdgpu_device_gpu_recover+0x6cd/0x95a [amdgpu]
  апр 05 20:46:45 kernel:  amdgpu_job_timedout+0x103/0x130 

[Kernel-packages] [Bug 1883105] [NEW] TouchPad Lenovo ThinkPad T470s not detected

[Alexandre Bouschbacher]

Public bug reported:

I: Bus=0019 Vendor= Product=0003 Version=
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
U: Uniq=
H: Handlers=event1 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=046d Product=c534 Version=0111
N: Name="Logitech USB Receiver"
P: Phys=usb-:00:14.0-2/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:046D:C534.0001/input/input6
U: Uniq=
H: Handlers=sysrq kbd event4 leds 
B: PROP=0
B: EV=120013
B: KEY=10007 ff8007ff febeffdfffef fffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=046d Product=c534 Version=0111
N: Name="Logitech USB Receiver"
P: Phys=usb-:00:14.0-2/input1
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/0003:046D:C534.0002/input/input7
U: Uniq=
H: Handlers=kbd mouse0 event5 
B: PROP=0
B: EV=1f
B: KEY=300ff 0 0 48317aff32d bf56 0001 130ff38b17c000 
677bfad941dfed 9ed6804400 1002
B: REL=1c3
B: ABS=1
B: MSC=10

I: Bus=0019 Vendor=17aa Product=5054 Version=4101
N: Name="ThinkPad Extra Buttons"
P: Phys=thinkpad_acpi/input0
S: Sysfs=/devices/platform/thinkpad_acpi/input/input8
U: Uniq=
H: Handlers=rfkill kbd event6 
B: PROP=0
B: EV=33
B: KEY=10040 0 1804 0 501000 0 1701b02102004 c000280041114000 
10e 0
B: MSC=10
B: SW=8

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus=0003 Vendor=04f2 Product=b5ab Version=0010
N: Name="Integrated Camera: Integrated C"
P: Phys=usb-:00:14.0-8/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input10
U: Uniq=
H: Handlers=kbd event8 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Dock Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
U: Uniq=
H: Handlers=event10 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Dock Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
U: Uniq=
H: Handlers=event11 
B: PROP=0
B: EV=21
B: SW=4

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14
U: Uniq=
H: Handlers=event12 
B: PROP=0
B: EV=21
B: SW=4

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15
U: Uniq=
H: Handlers=event13 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16
U: Uniq=
H: Handlers=event14 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input17
U: Uniq=
H: Handlers=event15 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input18
U: Uniq=
H: Handlers=event16 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=10"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input19
U: Uniq=
H: Handlers=event17 
B: PROP=0
B: EV=21
B: SW=140

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-99-generic 4.15.0-99.100
ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
Uname: Linux 4.15.0-99-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 

[Kernel-packages] [Bug 1881433] [NEW] 5.3.0-1022-azure syslog flood: kernel: [ 897.770784] testing the buffer

[Alexandre M.]

Public bug reported:

Updating azure VM kernel from 5.3.0-1020 to linux-image-azure
5.3.0.1022.22 results in syslog being flooded with

May 30 18:56:58  kernel: [  882.730807] testing the buffer
May 30 18:56:58  kernel: [  882.730831] testing the buffer
May 30 18:56:58  kernel: [  882.730842] testing the buffer
May 30 18:56:58  kernel: [  882.730921] testing the buffer
May 30 18:56:58  kernel: [  882.730934] testing the buffer
May 30 18:57:03  kernel: [  887.743339] testing the buffer
May 30 18:57:03  kernel: [  887.743364] testing the buffer
May 30 18:57:03  kernel: [  887.743375] testing the buffer
May 30 18:57:03  kernel: [  887.743453] testing the buffer
May 30 18:57:03  kernel: [  887.743465] testing the buffer
May 30 18:57:08  kernel: [  892.756017] testing the buffer
May 30 18:57:08  kernel: [  892.756043] testing the buffer
May 30 18:57:08  kernel: [  892.756055] testing the buffer
May 30 18:57:08  kernel: [  892.756149] testing the buffer
May 30 18:57:08  kernel: [  892.756162] testing the buffer
May 30 18:57:13  kernel: [  897.770663] testing the buffer
May 30 18:57:13  kernel: [  897.770687] testing the buffer
May 30 18:57:13  kernel: [  897.770697] testing the buffer
May 30 18:57:13  kernel: [  897.770773] testing the buffer
May 30 18:57:13  kernel: [  897.770784] testing the buffer

type messages

Ref: https://github.com/clearlinux/distribution/issues/1878

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


** Tags: linux-image-azure

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

Title:
  5.3.0-1022-azure syslog flood:  kernel: [  897.770784] testing the
  buffer

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Updating azure VM kernel from 5.3.0-1020 to linux-image-azure
  5.3.0.1022.22 results in syslog being flooded with

  May 30 18:56:58  kernel: [  882.730807] testing the buffer
  May 30 18:56:58  kernel: [  882.730831] testing the buffer
  May 30 18:56:58  kernel: [  882.730842] testing the buffer
  May 30 18:56:58  kernel: [  882.730921] testing the buffer
  May 30 18:56:58  kernel: [  882.730934] testing the buffer
  May 30 18:57:03  kernel: [  887.743339] testing the buffer
  May 30 18:57:03  kernel: [  887.743364] testing the buffer
  May 30 18:57:03  kernel: [  887.743375] testing the buffer
  May 30 18:57:03  kernel: [  887.743453] testing the buffer
  May 30 18:57:03  kernel: [  887.743465] testing the buffer
  May 30 18:57:08  kernel: [  892.756017] testing the buffer
  May 30 18:57:08  kernel: [  892.756043] testing the buffer
  May 30 18:57:08  kernel: [  892.756055] testing the buffer
  May 30 18:57:08  kernel: [  892.756149] testing the buffer
  May 30 18:57:08  kernel: [  892.756162] testing the buffer
  May 30 18:57:13  kernel: [  897.770663] testing the buffer
  May 30 18:57:13  kernel: [  897.770687] testing the buffer
  May 30 18:57:13  kernel: [  897.770697] testing the buffer
  May 30 18:57:13  kernel: [  897.770773] testing the buffer
  May 30 18:57:13  kernel: [  897.770784] testing the buffer

  type messages

  Ref: https://github.com/clearlinux/distribution/issues/1878

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881433/+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 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected

[Alexandre Anoutchine]

This issue is real pain and persists even with Ubuntu 20.04 and my Bose 
QuietComfort 35.
Selecting High Fidelity Playback (A2DP Sink) does nothing. I managed to do it 
once but it seems it stuck with low quality now :(

-- 
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/1845046

Title:
  Bluetooth headphones default to low quality headset mode and fail to
  switch to A2DP when selected

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Released
Status in bluez source package in Eoan:
  Fix Released
Status in bluez source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Whenever I turn on my headphones they'll connect to my computer but
  I'm able to hear the input audio from my microphone and low quality
  output audio. I have to disconnect the headphones in the bluetooth
  devices and reconnect for it to fix the problem.

  [Test Case]

  0. Set up your Bluetooth headphones with Ubuntu.
  1. Turn off the headphones.
  2. Turn on the headphones.
  3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high 
quality, no microphone support).

  [Regression Potential]

  Low. Only the headset code path is affected and the fix has already
  been released for some time in BlueZ 5.51 onward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 847001] Re: Adjusting display brightness is very slow on several Dell laptops

[Alexandre Rufato]

Bug happens on ubuntu 19.10 on a dell 7520. Here's what the command
lspci -k | grep -iA2 VGA returns:


00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
Subsystem: Dell 3rd Gen Core processor Graphics Controller
Kernel driver in use: i915
--
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Chelsea LP [Radeon HD 7730M]
Subsystem: Dell Chelsea LP [Radeon HD 7730M]
Kernel driver in use: radeon

-- 
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/847001

Title:
  Adjusting display brightness is very slow on several Dell laptops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Changing the brightness via FN key combination or via the brightness applet 
is very slow.
  the CPUs don't seem to go to 100%, but the adjustment process seems 
relatively slow.
  The mouse cursor is also sluggish.
  Reinstalled the OS twice, but not because of this issue and the problem seems 
to persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-power-manager 2.32.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  Architecture: amd64
  Date: Sun Sep 11 15:29:02 2011
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  MachineType: Dell Inc. Latitude E5410
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05C67D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/847001/+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 1776967] Re: glibc pkeys test fail on powerpc

[Lucas Alexandre Mello Magalhaes]

I think this patch solves the problem
https://sourceware.org/ml/libc-alpha/2020-01/msg00327.html
It's already in master at glibc-2.30.9000-492-g70ba28f7ab

-- 
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/1776967

Title:
  glibc pkeys test fail on powerpc

Status in glibc package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in glibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in glibc source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  powerpc introduced protection keys support, now present on 4.17
  kernel.

  glibc has a tst-pkey that fails on powerpc, and that needs further
  investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1776967/+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 1763594] Re: xhci hangs; reset results in NULL pointer dereference

[Alexandre ACEBEDO]

Got the same issue on 5.2 5.3 and 5.4 rc kernels.
The BT part of my Intel 8265 wifi/BT card of my matebook D14 laptop is kicked 
out after a few minutes of use with a logitech anywhere mx 2s mouse.

Only a hard power off resolve the issue. reboot does not revive the
adapter.

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

Title:
  xhci hangs; reset results in NULL pointer dereference

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux package in Arch Linux:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  xHC stops to work after some time. This happens when the xHC gets
  runtime resumed/suspended constantly.

  [Test]
  User reports this backport fixes the issue.

  [Fix]
  In addition to check EINT, also check ports' status.

  [Regression Potential]
  Low. It fixes a known bug and it's in -stable.

  ===Original Bug Report===

  Now and then, my xhci bus will hang, resulting in these kinds of
  messages in dmesg:

  [252220.002102] xhci_hcd :00:14.0: xHC is not running.
  [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up
  [252220.133794] usb 1-2: USB disconnect, device number 2
  [252220.135042] usb 1-7: USB disconnect, device number 3
  [252220.137455] usb 1-8: USB disconnect, device number 4
  [252220.243317] usb 1-9: USB disconnect, device number 5

  Usually, I can fix this bij resetting the bus by calling a script
  reset-xhci:

  for xhci in /sys/bus/pci/drivers/?hci_hcd ; do
    cd $xhci
    echo Resetting devices from $xhci...
    for i in :??:??.? ; do
  echo -n "$i" > unbind
  echo -n "$i" > bind
    done
  done

  But doing this today resulted in a kernel bug:

  [252243.401814] xhci_hcd :00:14.0: remove, state 4
  [252243.401887] usb usb2: USB disconnect, device number 1
  [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered
  [252243.470378] xhci_hcd :00:14.0: remove, state 4
  [252243.470383] usb usb1: USB disconnect, device number 1
  [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19
  [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed.
  [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered
  [252243.475938] [ cut here ]
  [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device
  [252243.475951] WARNING: CPU: 2 PID: 1787 at 
/build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 
pci_disable_device+0x9c/0xc0
  [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage 
hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 
ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 
nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark 
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log 
nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink 
nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip 
nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE 
nf_nat_masquerade_ipv4
  [252243.475984]  xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack 
br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep 
binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl 
snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas 
snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl 
snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq 
btrtl
  [252243.476023]  iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev 
input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw 
snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios 
videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof 
dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick 
shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf 
int3400_thermal acpi_thermal_rel dell_rbtn mac_hid 

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

[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 | 

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

[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 | 

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

[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

[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
  

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

[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 | 

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

[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 | 

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

[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
  

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

[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 | 

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

[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 | 

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

[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
  

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

[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] Lspci.txt

[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
  

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

[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
  

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

[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 | 

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

[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 | 

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

[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 

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

[Alexandre Forte]

This issue also affects Asus Vivobook 15 X510UR.

-- 
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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1780560] [NEW] package libnvidia-compute-390 390.48-0ubuntu3 failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/libnvidia-ml.so », qui appartien

[Alexandre Engelhardt]

Public bug reported:

Bug happened during installation with the apt install command

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libnvidia-compute-390 390.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 libcuda1-340:amd64: Remove
 nvidia-opencl-icd-340:amd64: Remove
 libnvidia-compute-390:amd64: Install
 nvidia-utils-390:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Jul  7 18:34:22 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
ErrorMessage: tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/libnvidia-ml.so », qui appartient aussi au paquet 
nvidia-340 340.106-0ubuntu3
InstallationDate: Installed on 2018-07-07 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.2
SourcePackage: nvidia-graphics-drivers-390
Title: package libnvidia-compute-390 390.48-0ubuntu3 failed to install/upgrade: 
tentative de remplacement de « /usr/lib/x86_64-linux-gnu/libnvidia-ml.so », qui 
appartient aussi au paquet nvidia-340 340.106-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package libnvidia-compute-390 390.48-0ubuntu3 failed to
  install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-
  gnu/libnvidia-ml.so », qui appartient aussi au paquet nvidia-340
  340.106-0ubuntu3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Bug happened during installation with the apt install command

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libnvidia-compute-390 390.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libcuda1-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   libnvidia-compute-390:amd64: Install
   nvidia-utils-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jul  7 18:34:22 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ErrorMessage: tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/libnvidia-ml.so », qui appartient aussi au paquet 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-07-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-compute-390 390.48-0ubuntu3 failed to 
install/upgrade: tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/libnvidia-ml.so », qui appartient aussi au paquet 
nvidia-340 340.106-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1780560/+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 1780561] [NEW] package nvidia-utils-390 390.48-0ubuntu3 failed to install/upgrade: tentative de remplacement de « /usr/bin/nvidia-bug-report.sh », qui appartient aussi au paquet

[Alexandre Engelhardt]

Public bug reported:

Bug happened during installation with the apt install command

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-utils-390 390.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 libcuda1-340:amd64: Remove
 nvidia-opencl-icd-340:amd64: Remove
 libnvidia-compute-390:amd64: Install
 nvidia-utils-390:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Jul  7 18:34:22 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
 libnvidia-compute-390 390.48-0ubuntu3
ErrorMessage: tentative de remplacement de « /usr/bin/nvidia-bug-report.sh », 
qui appartient aussi au paquet nvidia-340 340.106-0ubuntu3
InstallationDate: Installed on 2018-07-07 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.2
SourcePackage: nvidia-graphics-drivers-390
Title: package nvidia-utils-390 390.48-0ubuntu3 failed to install/upgrade: 
tentative de remplacement de « /usr/bin/nvidia-bug-report.sh », qui appartient 
aussi au paquet nvidia-340 340.106-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package nvidia-utils-390 390.48-0ubuntu3 failed to install/upgrade:
  tentative de remplacement de « /usr/bin/nvidia-bug-report.sh », qui
  appartient aussi au paquet nvidia-340 340.106-0ubuntu3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Bug happened during installation with the apt install command

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-utils-390 390.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libcuda1-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   libnvidia-compute-390:amd64: Install
   nvidia-utils-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jul  7 18:34:22 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libnvidia-compute-390 390.48-0ubuntu3
  ErrorMessage: tentative de remplacement de « /usr/bin/nvidia-bug-report.sh », 
qui appartient aussi au paquet nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-07-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-utils-390 390.48-0ubuntu3 failed to install/upgrade: 
tentative de remplacement de « /usr/bin/nvidia-bug-report.sh », qui appartient 
aussi au paquet nvidia-340 340.106-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1780561/+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 1768050] Re: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status

[Alexandre Lima]

I had the same problem and I solved with this solution:

As rootm run:

# for FILE in $(dpkg-divert --list | grep nvidia-340 | awk '{print
$3}'); do dpkg-divert --remove $FILE; done

Then:

# apt --fix-broken install


Font: https://askubuntu.com/questions/1035409/installing-nvidia-drivers-on-18-04


Best Regards!

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

Title:
  package libnvidia-gl-390 (not installed) failed to install/upgrade:
  new libnvidia-gl-390:amd64 package pre-installation script subprocess
  returned error exit status 2 (NOT FIXED)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  There is a previous report, but I don't think this bug has been fixed,
  it is still there.

  When I execute "sudo ubuntu-drivers autoinstall"

  the driver does not installed. then I was told:

  "diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340
  dpkg-divert: error: mismatch on package"

  then I trace the bug and found it may be comes from libnvidia-gl-390
  package and libnvidia-ifr1-390.

  and When I try to install only the libnvidia-gl-390 package, I've got:

  package libnvidia-gl-390 (not installed) failed to install/upgrade:
  new libnvidia-gl-390:amd64 package pre-installation script subprocess
  returned error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1768050/+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 1756315] Re: fstrim and discard operations take too long to complete - Ubuntu 16.04

[Alexandre Makoto Tanno]

Hello David!

I launched an instance and tried to create a RAID0 array using the chunk
size of 4096 bytes. The result was the same, mkfs.xfs took around 2
hours and the same for fstrim -v on the mount point where /dev/md0 was
mounted.

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

Title:
  fstrim and discard operations take too long to complete - Ubuntu 16.04

Status in linux-aws package in Ubuntu:
  New

Bug description:
  1-) Ubuntu Release : Ubuntu 16.04 LTS

  2-) linux-image-4.4.0.1052.54-aws

  3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should
  not take more than some seconds to complete.

  4-) Formating the raid0 array with xfs took around 2 hours. Running
  fstrim -v on the mount point mounted on top of the raid array took
  around 2 hours.

  How to reproduce the issue:

  - Launch an i3.4xlarge instance on Amazon AWS using an Ubuntu 16.04 AMI ( 
ami-78d2be01 on EU-WEST-1 ), this will generate an instance with one 8Gb EBS 
root volume and two 1.9T SSD drives that are presented to the instance using 
the nvme driver.
  - Compose a raid0 array with the following command :

   # mdadm --create --verbose --level=0 /dev/md0 --raid-devices=2
  /dev/nvme0n1 /dev/nvme1n1

  - When trying to format the raid0 array ( /dev/md0 ) using xfs it
  takes around 2 hours to complete. I tried other AMIs like RHEL7,
  CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds.

  root@ip-172-31-30-133:~# time mkfs.xfs /dev/md0

  real120m45.725s
  user0m0.000s
  sys 0m18.248s

  - Running fstrim -v on a filesystem mounted on top of /dev/md0 can
  take around 2 hours to complete. With other AMIs like RHEL7, CentOS7
  and Ubuntu 18.04 and the time needed was around 2 seconds.

  - When I try the same with any of the nvme SSD devices alone, let's
  say /dev/nvme0n1, the issue doesn't happen.

  - I tried to replicate this issue using LVM and striping, fstrim and
  mkfs.xfs, the tasks complete without taking hours :

  root@ip-172-31-27-69:~# pvcreate /dev/nvme0n1
Physical volume "/dev/nvme0n1" successfully created

  root@ip-172-31-27-69:~# pvcreate /dev/nvme1n1
Physical volume "/dev/nvme1n1" successfully created

  root@ip-172-31-27-69:~# vgcreate raid0 /dev/nvme0n1 /dev/nvme1n1
Volume group "raid0" successfully created

  root@ip-172-31-27-69:~# lvcreate --type striped --stripes 2 --extents 
100%FREE raid0 /dev/nvme0n1 /dev/nvme1n1
Using default stripesize 64.00 KiB.
Logical volume "lvol0" created.

  root@ip-172-31-27-69:~# vgchange -ay
1 logical volume(s) in volume group "raid0" now active

  root@ip-172-31-27-69:~# lvchange -ay /dev/raid0/lvol0

  root@ip-172-31-27-69:~# lvs -a /dev/raid0/lvol0
LVVGAttr   LSize Pool Origin Data%  Meta%  Move Log Cpy%Sync 
Convert
lvol0 raid0 -wi-a- 3.46t
  htop
  root@ip-172-31-27-69:~# time mkfs.xfs /dev/raid0/lvol0
  meta-data=/dev/raid0/lvol0   isize=512agcount=32, agsize=28991664 blks
   =   sectsz=512   attr=2, projid32bit=1
   =   crc=1finobt=1, sparse=0
  data =   bsize=4096   blocks=927733248, imaxpct=5
   =   sunit=16 swidth=32 blks
  naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
  log  =internal log   bsize=4096   blocks=453008, version=2
   =   sectsz=512   sunit=16 blks, lazy-count=1
  realtime =none   extsz=4096   blocks=0, rtextents=0

  real0m2.926s
  user0m0.180s
  sys 0m0.000s

  
  root@ip-172-31-27-69:~# mount /dev/raid0/lvol0 /mnt

  root@ip-172-31-27-69:~# time fstrim -v /mnt
  /mnt: 3.5 TiB (3798138650624 bytes) trimmed

  real0m1.794s
  user0m0.000s
  sys 0m0.000s

  So the issue only happens when using nvme and md to compose the raid0
  array.

  Bellow follows some information that may be useful:

  started formating the md array with mkfs.xfs. Process looks hanged.

  root@ip-172-31-24-66:~# ps aux | grep -i mkfs.xfs
  root   1693 12.0  0.0  12728   968 pts/1D+   07:54   0:03 mkfs.xfs 
/dev/md0

  PID 1693 is in uninterruptible sleep ( D )

  Looking at /proc/7965/stack

  root@ip-172-31-24-66:~# cat /proc/1693/stack
  [] blkdev_issue_discard+0x232/0x2a0
  [] blkdev_ioctl+0x61d/0x7d0
  [] block_ioctl+0x41/0x50
  [] do_vfs_ioctl+0x2e3/0x4d0
  [] SyS_ioctl+0x81/0xa0
  [] system_call_fastpath+0x1a/0x1f
  [] 0x

  
  Looking at the stack, looks like it's hanged on a discard operation

  root@ip-172-31-24-66:~# ps -flp 1693
  F S UID PID   PPID  C PRI  NI ADDR SZ WCHAN  STIME TTY  TIME 
CMD
  4 D root   1693   1682  2  80   0 -  3182 blkdev 07:54 pts/100:00:03 
mkfs.xfs /dev/md0

  
  root@ip-172-31-24-66:~# cat /proc/1693/wchan
  blkdev_issue_discard

  Process stuck with function 

[Kernel-packages] [Bug 1756315] [NEW] fstrim and discard operations take too long to complete - Ubuntu 16.04

[Alexandre Makoto Tanno]

Public bug reported:

1-) Ubuntu Release : Ubuntu 16.04 LTS

2-) linux-image-4.4.0.1052.54-aws

3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not
take more than some seconds to complete.

4-) Formating the raid0 array with xfs took around 2 hours. Running
fstrim -v on the mount point mounted on top of the raid array took
around 2 hours.

How to reproduce the issue:

- Launch an i3.4xlarge instance on Amazon AWS using an Ubuntu 16.04 AMI ( 
ami-78d2be01 on EU-WEST-1 ), this will generate an instance with one 8Gb EBS 
root volume and two 1.9T SSD drives that are presented to the instance using 
the nvme driver.
- Compose a raid0 array with the following command :

 # mdadm --create --verbose --level=0 /dev/md0 --raid-devices=2
/dev/nvme0n1 /dev/nvme1n1

- When trying to format the raid0 array ( /dev/md0 ) using xfs it takes
around 2 hours to complete. I tried other AMIs like RHEL7, CentOS7 and
Ubuntu 18.04 and the time needed was around 2 seconds.

root@ip-172-31-30-133:~# time mkfs.xfs /dev/md0

real120m45.725s
user0m0.000s
sys 0m18.248s

- Running fstrim -v on a filesystem mounted on top of /dev/md0 can take
around 2 hours to complete. With other AMIs like RHEL7, CentOS7 and
Ubuntu 18.04 and the time needed was around 2 seconds.

- When I try the same with any of the nvme SSD devices alone, let's say
/dev/nvme0n1, the issue doesn't happen.

- I tried to replicate this issue using LVM and striping, fstrim and
mkfs.xfs, the tasks complete without taking hours :

root@ip-172-31-27-69:~# pvcreate /dev/nvme0n1
  Physical volume "/dev/nvme0n1" successfully created

root@ip-172-31-27-69:~# pvcreate /dev/nvme1n1
  Physical volume "/dev/nvme1n1" successfully created

root@ip-172-31-27-69:~# vgcreate raid0 /dev/nvme0n1 /dev/nvme1n1
  Volume group "raid0" successfully created

root@ip-172-31-27-69:~# lvcreate --type striped --stripes 2 --extents 100%FREE 
raid0 /dev/nvme0n1 /dev/nvme1n1
  Using default stripesize 64.00 KiB.
  Logical volume "lvol0" created.

root@ip-172-31-27-69:~# vgchange -ay
  1 logical volume(s) in volume group "raid0" now active

root@ip-172-31-27-69:~# lvchange -ay /dev/raid0/lvol0

root@ip-172-31-27-69:~# lvs -a /dev/raid0/lvol0
  LVVGAttr   LSize Pool Origin Data%  Meta%  Move Log Cpy%Sync 
Convert
  lvol0 raid0 -wi-a- 3.46t
htop
root@ip-172-31-27-69:~# time mkfs.xfs /dev/raid0/lvol0
meta-data=/dev/raid0/lvol0   isize=512agcount=32, agsize=28991664 blks
 =   sectsz=512   attr=2, projid32bit=1
 =   crc=1finobt=1, sparse=0
data =   bsize=4096   blocks=927733248, imaxpct=5
 =   sunit=16 swidth=32 blks
naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
log  =internal log   bsize=4096   blocks=453008, version=2
 =   sectsz=512   sunit=16 blks, lazy-count=1
realtime =none   extsz=4096   blocks=0, rtextents=0

real0m2.926s
user0m0.180s
sys 0m0.000s


root@ip-172-31-27-69:~# mount /dev/raid0/lvol0 /mnt

root@ip-172-31-27-69:~# time fstrim -v /mnt
/mnt: 3.5 TiB (3798138650624 bytes) trimmed

real0m1.794s
user0m0.000s
sys 0m0.000s

So the issue only happens when using nvme and md to compose the raid0
array.

Bellow follows some information that may be useful:

started formating the md array with mkfs.xfs. Process looks hanged.

root@ip-172-31-24-66:~# ps aux | grep -i mkfs.xfs
root   1693 12.0  0.0  12728   968 pts/1D+   07:54   0:03 mkfs.xfs 
/dev/md0

PID 1693 is in uninterruptible sleep ( D )

Looking at /proc/7965/stack

root@ip-172-31-24-66:~# cat /proc/1693/stack
[] blkdev_issue_discard+0x232/0x2a0
[] blkdev_ioctl+0x61d/0x7d0
[] block_ioctl+0x41/0x50
[] do_vfs_ioctl+0x2e3/0x4d0
[] SyS_ioctl+0x81/0xa0
[] system_call_fastpath+0x1a/0x1f
[] 0x


Looking at the stack, looks like it's hanged on a discard operation

root@ip-172-31-24-66:~# ps -flp 1693
F S UID PID   PPID  C PRI  NI ADDR SZ WCHAN  STIME TTY  TIME CMD
4 D root   1693   1682  2  80   0 -  3182 blkdev 07:54 pts/100:00:03 
mkfs.xfs /dev/md0


root@ip-172-31-24-66:~# cat /proc/1693/wchan
blkdev_issue_discard

Process stuck with function --> blkdev_issue_discard

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


** Tags: aws discard fstrim mkfs.xfs trim

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

Title:
  fstrim and discard operations take too long to complete - Ubuntu 16.04

Status in linux-aws package in Ubuntu:
  New

Bug description:
  1-) Ubuntu Release : Ubuntu 16.04 LTS

  2-) linux-image-4.4.0.1052.54-aws

  3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should
  not take more than some seconds to complete.

  4-) Formating the raid0 array with xfs 

[Kernel-packages] [Bug 1756311] [NEW] fstrim and discard operations take too long to complete

[Alexandre Makoto Tanno]

Public bug reported:

1-) Ubuntu Release : Ubuntu 14.04.5 LTS

2-) linux-image-3.13.0-143-generic and linux-image-4.4.0-1014-aws

3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not
take more than some seconds to complete.

4-) Formating the raid0 array with xfs took around 2 hours. Running
fstrim -v on the mount point mounted on top of the raid array took
around 2 hours.

How to reproduce the issue:

- Launch an i3.4xlarge instance on Amazon AWS using an Ubuntu 14.04.5 AMI ( 
ami-78d2be01 on EU-WEST-1 ), this will generate an instance with one 8Gb EBS 
root volume and two 1.9T SSD drives that are presented to the instance using 
the nvme driver.
- Compose a raid0 array with the following command :

 # mdadm --create --verbose --level=0 /dev/md0 --raid-devices=2
/dev/nvme0n1 /dev/nvme1n1

- When trying to format the raid0 array ( /dev/md0 ) using xfs it takes
around 2 hours to complete. I tried other AMIs like RHEL7, CentOS7 and
Ubuntu 18.04 and the time needed was around 2 seconds.

root@ip-172-31-30-133:~# time mkfs.xfs /dev/md0

real120m45.725s
user0m0.000s
sys 0m18.248s

- Running fstrim -v on a filesystem mounted on top of /dev/md0 can take
around 2 hours to complete. With other AMIs like RHEL7, CentOS7 and
Ubuntu 18.04 and the time needed was around 2 seconds.

- When I try the same with any of the nvme SSD devices alone, let's say
/dev/nvme0n1, the issue doesn't happen.

- I tried to replicate this issue using LVM and striping, fstrim and
mkfs.xfs, the tasks complete without taking hours :

root@ip-172-31-27-69:~# pvcreate /dev/nvme0n1
  Physical volume "/dev/nvme0n1" successfully created

root@ip-172-31-27-69:~# pvcreate /dev/nvme1n1
  Physical volume "/dev/nvme1n1" successfully created

root@ip-172-31-27-69:~# vgcreate raid0 /dev/nvme0n1 /dev/nvme1n1
  Volume group "raid0" successfully created

root@ip-172-31-27-69:~# lvcreate --type striped --stripes 2 --extents 100%FREE 
raid0 /dev/nvme0n1 /dev/nvme1n1
  Using default stripesize 64.00 KiB.
  Logical volume "lvol0" created.

root@ip-172-31-27-69:~# vgchange -ay
  1 logical volume(s) in volume group "raid0" now active

root@ip-172-31-27-69:~# lvchange -ay /dev/raid0/lvol0

root@ip-172-31-27-69:~# lvs -a /dev/raid0/lvol0
  LVVGAttr   LSize Pool Origin Data%  Meta%  Move Log Cpy%Sync 
Convert
  lvol0 raid0 -wi-a- 3.46t
htop
root@ip-172-31-27-69:~# time mkfs.xfs /dev/raid0/lvol0
meta-data=/dev/raid0/lvol0   isize=512agcount=32, agsize=28991664 blks
 =   sectsz=512   attr=2, projid32bit=1
 =   crc=1finobt=1, sparse=0
data =   bsize=4096   blocks=927733248, imaxpct=5
 =   sunit=16 swidth=32 blks
naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
log  =internal log   bsize=4096   blocks=453008, version=2
 =   sectsz=512   sunit=16 blks, lazy-count=1
realtime =none   extsz=4096   blocks=0, rtextents=0

real0m2.926s
user0m0.180s
sys 0m0.000s


root@ip-172-31-27-69:~# mount /dev/raid0/lvol0 /mnt

root@ip-172-31-27-69:~# time fstrim -v /mnt
/mnt: 3.5 TiB (3798138650624 bytes) trimmed

real0m1.794s
user0m0.000s
sys 0m0.000s

So the issue only happens when using nvme and md to compose the raid0
array.

Bellow follows some information that may be useful:

started formating the md array with mkfs.xfs. Process looks hanged.

root@ip-172-31-24-66:~# ps aux | grep -i mkfs.xfs
root   1693 12.0  0.0  12728   968 pts/1D+   07:54   0:03 mkfs.xfs 
/dev/md0

PID 1693 is in uninterruptible sleep ( D )

Looking at /proc/7965/stack

root@ip-172-31-24-66:~# cat /proc/1693/stack
[] blkdev_issue_discard+0x232/0x2a0
[] blkdev_ioctl+0x61d/0x7d0
[] block_ioctl+0x41/0x50
[] do_vfs_ioctl+0x2e3/0x4d0
[] SyS_ioctl+0x81/0xa0
[] system_call_fastpath+0x1a/0x1f
[] 0x


Looking at the stack, looks like it's hanged on a discard operation

root@ip-172-31-24-66:~# ps -flp 1693
F S UID PID   PPID  C PRI  NI ADDR SZ WCHAN  STIME TTY  TIME CMD
4 D root   1693   1682  2  80   0 -  3182 blkdev 07:54 pts/100:00:03 
mkfs.xfs /dev/md0


root@ip-172-31-24-66:~# cat /proc/1693/wchan
blkdev_issue_discard

Process stuck with function --> blkdev_issue_discard

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

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

Title:
  fstrim and discard operations take too long to complete

Status in linux-aws package in Ubuntu:
  New

Bug description:
  1-) Ubuntu Release : Ubuntu 14.04.5 LTS

  2-) linux-image-3.13.0-143-generic and linux-image-4.4.0-1014-aws

  3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should
  not take more than some seconds to complete.

  4-) Formating the raid0 array 

[Kernel-packages] [Bug 1743027] Re: error loading realtime clock since upgrading to 17.10

[Alexandre BELLONI]

The issue is caused by CONFIG_WDAT_WDT which driver is stealing the RTC
resources before the RTC driver is probed. Disabling CONFIG_WDAT_WDT
will solve that issue.

-- 
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/1743027

Title:
  error loading realtime clock since upgrading to 17.10

Status in linux package in Ubuntu:
  Triaged

Bug description:
  (originally asked over at askubuntu.com, but is still unresolved:
  https://askubuntu.com/questions/971349/problem-with-real-time-clock-
  since-upgrading-to-ubuntu-17-10)

  I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the
  software update process. The update completed without any errors, and
  Ubuntu 17.10 is now running without any major issues.

  However, I was running a script previously that uses rtcwake which has
  since stopped working. The script automatically hibernates my laptop
  after a set period of time in sleep mode, and was working perfectly in
  Ubuntu 17.04.

  In the process of troubleshooting, I discovered that the problem was
  with rtcwake which is complaining about /dev/rtc0 missing.

  Here is output from a sample rtcwake command:

  peter@haven:~$ rtcwake -m no -s 1300
  rtcwake: assuming RTC uses UTC ...
  rtcwake: /dev/rtc0: unable to find device: No such file or directory

  I verified that in fact, that directory is missing. Since this was
  working prior to the upgrade, I have to assume that it was there
  previously, but I don't know for sure.

  In researching the error, I found some suggestions to get further
  information with timedatectl and hwclock, so here are the results from
  those commands as well.

  Output of timedatectl:

  peter@haven:~$ timedatectl
Local time: Fri 2017-10-27 19:06:26 EDT
Universal time: Fri 2017-10-27 23:06:26 UTC
  RTC time: n/a
 Time zone: America/New_York (EDT, -0400)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  Output of hwclock --debug:

  peter@haven:~$ sudo hwclock --debug
  [sudo] password for peter: 
  hwclock from util-linux 2.30.1
  Trying to open: /dev/rtc0
  Trying to open: /dev/rtc
  Trying to open: /dev/misc/rtc
  No usable clock interface found.
  hwclock: Cannot access the Hardware Clock via any known method.

  UPDATE

  When I boot with my old kernel, 4.10.0-37-generic the real-time clock
  works fine.

  I get the following RTC messages in dmesg when I boot the
  4.13.0-16-generic kernel:

  peter@haven:~$ dmesg | grep -i rtc
  [0.089393] RTC time: 17:03:55, date: 11/01/17
  [1.238784] rtc_cmos 00:01: RTC can wake from S4
  [1.238794] rtc_cmos: probe of 00:01 failed with error -16
  [1.295459] hctosys: unable to open rtc device (rtc0)

  UPDATE #2

  Well, I was starting to believe that I had a hardware issue, since
  discovering I was unable to save changes to my BIOS and could not boot
  from USB. As it turns out, my laptop was bitten by this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing
  my BIOS to be locked in a read-only state.

  Once I resolved the BIOS issue, and fixed the USB boot problem, I did
  a live boot of Ubuntu 17.10. The issue with my real time clock still
  exists under this clean boot scenario, yet when I boot other distros,
  like Linux Mint 18.3 and the real time clock works fine. I feel this
  definitely has something to do with the Ubuntu install, perhaps even a
  kernel bug.

  UPDATE #3

  More evidence to suggest this is a kernel bug: I live-booted a copy of
  Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it
  exhibited the same problem with the real time clock as Ubuntu 17.10.
  In addition, I confirmed that the Linux Mint version I booted earlier
  (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic.

  So, I suspect that sometime between kernels 4.10 and 4.13 this bug was 
introduced.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1832 F pulseaudio
   /dev/snd/controlC1:  peter  1832 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad
  InstallationDate: Installed on 2017-04-05 (292 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20354
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=fa5454aa-9072-475d-b515-acd51a6166cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   

[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'

[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]  

[Kernel-packages] [Bug 1732686] Re: Asus Fx553VD - Keyboard LED backlight controls are not working # kernel-bug-reported-upstream

[Alexandre Pereira Nunes]

Glad it worked for you. For anyone who has linux-stable on git (like
me), if your kernel version lacks this, it's a matter of git cherry-pick
339ee3fcbdab736adbc30b7a3d675005c61a2a40 and there you go.

Btw this should work on any "gamer" laptop who have this USB keyboard:
Bus 001 Device 006: ID 0b05:1854 ASUSTek Computer, Inc.

-- 
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/1732686

Title:
  Asus Fx553VD - Keyboard LED backlight controls are not working #
  kernel-bug-reported-upstream

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi , i'm using this laptop with it's latest bios (V303 -
  https://www.asus.com/Laptops/ASUS-FX553VD/HelpDesk_BIOS/ )

  Kernel : 4.14.0-041400-generic x86_64

  I can't control keyboard LED backlight level with it's dedicated FN
  keys or anything else. FN keys are recognized by Linux Mint 18.2 and
  Ubuntu 16.04 but pressing them have no effect.

  Kernels from 4.10 to 4.14 are the same on that regard.

  And also i have these errors on "inxi -F && dmesg | grep -i error"

  [0.031175] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20170728/dswload-378)
  [0.040665] ACPI Error: 1 table load failures, 10 successful 
(20170728/tbxfload-246)
  [0.506425] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
  [1.694527] RAS: Correctable Errors collector initialized.
  [9.833145] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

  I'm not a developer but only a user. So if i opened that issue to the
  wrong place can you point me the correct place to open it?

  Thanks.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-10-22 (24 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  Tags:  sonya
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732686/+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 1732686] Re: Asus Fx553VD - Keyboard LED backlight controls are not working # kernel-bug-reported-upstream

[Alexandre Pereira Nunes]

I'm not sure this is entirely related, but someone should try
https://github.com/archerhush/linux-fx553vd/blob/master/kbd-
backlight.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/1732686

Title:
  Asus Fx553VD - Keyboard LED backlight controls are not working #
  kernel-bug-reported-upstream

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi , i'm using this laptop with it's latest bios (V303 -
  https://www.asus.com/Laptops/ASUS-FX553VD/HelpDesk_BIOS/ )

  Kernel : 4.14.0-041400-generic x86_64

  I can't control keyboard LED backlight level with it's dedicated FN
  keys or anything else. FN keys are recognized by Linux Mint 18.2 and
  Ubuntu 16.04 but pressing them have no effect.

  Kernels from 4.10 to 4.14 are the same on that regard.

  And also i have these errors on "inxi -F && dmesg | grep -i error"

  [0.031175] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20170728/dswload-378)
  [0.040665] ACPI Error: 1 table load failures, 10 successful 
(20170728/tbxfload-246)
  [0.506425] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
  [1.694527] RAS: Correctable Errors collector initialized.
  [9.833145] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

  I'm not a developer but only a user. So if i opened that issue to the
  wrong place can you point me the correct place to open it?

  Thanks.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-10-22 (24 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  Tags:  sonya
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732686/+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 1701509] [NEW] package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Alexandre F]

*** This bug is a duplicate of bug 1701085 ***
https://bugs.launchpad.net/bugs/1701085

Public bug reported:

During a update ...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-83-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
Uname: Linux 4.4.0-81-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alexandre   1747 F pulseaudio
Date: Fri Jun 30 11:03:40 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=83f08c75-1464-43f7-b943-b9f5864b86b3
InstallationDate: Installed on 2017-02-22 (127 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b571 Chicony Electronics Co., Ltd 
 Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
 Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575G
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic.efi.signed 
root=UUID=0297345b-5224-4981-a870-7ea0d48b5823 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 N/A
SourcePackage: linux
Title: package linux-image-4.4.0-83-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: 12/13/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.20
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.20:bd12/13/2016:svnAcer:pnAspireE5-575G:pvrV1.20:rvnAcer:rnIronman_SK:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-575G
dmi.product.version: V1.20
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-package 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/1701509

Title:
  package linux-image-4.4.0-83-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:
  During a update ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexandre   1747 F pulseaudio
  Date: Fri Jun 30 11:03:40 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=83f08c75-1464-43f7-b943-b9f5864b86b3
  InstallationDate: Installed on 2017-02-22 (127 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b571 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic.efi.signed 
root=UUID=0297345b-5224-4981-a870-7ea0d48b5823 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 N/A
  SourcePackage: linux
  Title: package linux-image-4.4.0-83-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: 12/13/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.20
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.20:bd12/13/2016:svnAcer:pnAspireE5-575G:pvrV1.20:rvnAcer:rnIronman_SK:rvrV1.20:cvnChassisManufacturer:ct

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

[Alexandre Payet]

Hello Stephan,

Is there a simple / not risky way to update the kernel on ubuntu ? 
Alexandre,

-- 
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:
  Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in telephony-service 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 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

[Alexandre Payet]

** Summary changed:

- Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
+ Call with Bluetooth headset not working [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/1590844

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

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New

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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

[Alexandre Payet]

@Seth, 
I don't know at all. I also tied to modify some pulseaudio conf without success.
1. It's working on android --> so the problem come from ubuntu ? 
2. Bluez / Bluetooth seems to have same behaviour than the other ubuntu phone 
(nexus 4 , ...)
3. Pulseaudio / audio is working well with the other sounds (music player, ...) 
even with Bluetooth 
4. Only a call sound with bluetooth is noising. Problem seems to be sound's 
configuration between telephony service / bluez / pulseaudio

If we don't know the service(s) that impact this bug, could it be
possible to have a discussion between people working on theses different
services in order to understand the link between
telephony/bluez/pulseaudio ?

These are only assumptions.

** Also affects: telephony-service (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/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
Status in pulseaudio package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New

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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

[Alexandre Payet]

** Also affects: pulseaudio (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/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
Status in pulseaudio package in Ubuntu:
  New

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 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

[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

[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

[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 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

[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 1628546] Re: 4.4.0-40-generic no prompts for disk encryption + loops on dots load screen

[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

[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

[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 1628546] Re: 4.4.0-40-generic no prompts for disk encryption + loops on dots load screen

[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

[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 1627670] Re: 4.4.0-40.60 fails to boot

[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 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

[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 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

[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

[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 1593919] Re: Bluetooth not working with Meizu Pro 5

[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 1537737] Re: Since Bluez5, headsets don't reconnect audio when reconnecting

[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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

[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

[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

[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 1593919] Re: Bluetooth not working with Meizu Pro 5

[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 1593919] Re: Bluetooth not working with Meizu Pro 5

[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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

[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 1049466] Re: Need support of Ralink RT3290 wifi support

[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 1566229] Re: XPS 13 9350 Unity freeze

[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 1566229] Re: XPS 13 9350 Unity freeze

[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

[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

[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

[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

[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] [NEW] XPS 13 9350 Unity freeze

[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 1524939] Re: Using telephony in car with bluetooth not possible after second connection

[Alexandre Payet]

would like to comment again on this bug to confirm it.
Big progress was made recently in rc-proposed about calls with bluetooth audio 
car. It works again now (since rc-proposed 03-10-2016). 

But the bug described above is still effective. At a second automatic
reconnection, it's no more possible to use handsfree car system to do a
call. You have to disconnect and reconnect manually the bluetooth device
to solve the problem

Does someone know the commands lines to do this (ie. disconnect and
reconnect to a bluetooth device) ? Will try to put a shorcut in terminal
to do this because it's a bit tricky to do this with the UI while
driving.

-- 
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:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed

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 1528856] Re: bluetooth & car handsfree issue

[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 1529049] [NEW] Switch bluetooth keyboard from qwerty to azerty

[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 1524939] Re: Using telephony in car with bluetooth not possible after second connection

[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 1524939] Re: Using telephony in car with bluetooth not possible after second connection

[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] [NEW] Using telephony with bluetooth not possible after second connection

[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 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver

[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