date:20190107

[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

2019-01-07 Thread Łukasz Zemczak

** Also affects: alsa-lib (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in alsa-lib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1806532] Re: The line-out on the Dell Dock station can't work

2019-01-07 Thread Launchpad Bug Tracker

This bug was fixed in the package alsa-lib - 1.1.6-1ubuntu1.2

---
alsa-lib (1.1.6-1ubuntu1.2) cosmic; urgency=medium

  * d/p/0013-configure-Fix-forgotten-ucm-entry.patch
- enable line-out on the Dell WD Dock stations (LP: #1806532)

alsa-lib (1.1.6-1ubuntu1.1) cosmic; urgency=medium

  * d/p/0010-conf-ucm-Add-a-UCM-profile-for-Dell-WD15-Dock-USB-au.patch
  * d/p/0011-conf-ucm-Dell-WD15-Dock-Fix-incorrect-device-names.patch
  * d/p/0012-conf-USB-Audio-Add-Dell-WD19-Dock-in-the-IEC958-blac.patch
- enable line-out on the Dell WD Dock stations (LP: #1806532)

 -- Hui Wang   Wed, 19 Dec 2018 11:32:46 +0800

** Changed in: alsa-lib (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in alsa-lib source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1806532] Update Released

2019-01-07 Thread Łukasz Zemczak

The verification of the Stable Release Update for alsa-lib has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in alsa-lib source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1802168] Re: Unable to get right-click working on ThinkPad T480s

2019-01-07 Thread Pirouette Cacahuète

Can we get any news on that?

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

Title:
  Unable to get right-click working on ThinkPad T480s

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Updated to Ubuntu 18.10, I've been fighting some weird behavior of the
  touchpad. Now, right-click does not work, whatever solution I try
  within gnome-tweaks, whether relying on multi-finger tapping or not.

  Found a very very close report from RedHat, on the same model of laptop, 
around kernel 4.18, with a fix: 
https://bugzilla.redhat.com/show_bug.cgi?id=1628715
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2195 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1802168/+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 1810388] Re: syslog filled with drm messages 40 times per second

2019-01-07 Thread

You're right Timeo. Without debug, no log.
Now we know how to mask logs, but not the source of the problem.
If it ever was a bot, the impact may be more important than just filling logs.

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

Title:
  syslog filled with drm messages 40 times per second

Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Hi all,

  I don't really know when it exactly began.
  From /var/log/syslog :
  Jan  3 09:42:42 localhost kernel: [32659.271016] [drm:drm_mode_addfb2 [drm]] 
[FB:74]
  Jan  3 09:42:42 localhost kernel: [32659.300800] [drm:drm_mode_addfb2 [drm]] 
[FB:89]

  There are similar bugs that have been already noticed, but none of
  them helped me.

  Changing desktop environment to a non-gnome desktop stops messages.

  My environment (export cmd) :
  declare -x XDG_CONFIG_DIRS="/etc/xdg/xdg-ubuntu:/etc/xdg"
  declare -x XDG_CURRENT_DESKTOP="ubuntu:GNOME"
  declare -x 
XDG_DATA_DIRS="/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop"
  declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm-data/userprofile"
  declare -x XDG_MENU_PREFIX="gnome-"
  declare -x XDG_RUNTIME_DIR="/run/user/1000"
  declare -x XDG_SEAT="seat0"
  declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0"
  declare -x XDG_SESSION_DESKTOP="ubuntu"
  declare -x XDG_SESSION_ID="c2"
  declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session0"
  declare -x XDG_SESSION_TYPE="x11"
  declare -x XDG_VTNR="7"

  My kernel : 4.15.0-43-generic
  Ubuntu 18.04.01 LTS
  Graphic : Intel Haswell Mobile

  Any help is appreciated
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jan  3 09:38:35 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed
   virtualbox, 5.2.18, 4.19.0-041900-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
  InstallationDate: Installed on 2016-12-20 (743 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. XPS13 9333
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=19d7298f-74c8-4a78-9f17-88b9f04bbc3a ro net.ifnames=0 biosdevname=0 
acpi=force plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/31/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810388/+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 1806649] Re: Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter

2019-01-07 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE
  802.11ac PCIe Wireless Network Adapter

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

Bug description:
  Hello,

  Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE
  802.11ac PCIe Wireless Network Adapter.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2784 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 07:41:10 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806649/+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 1810392] [NEW] [Ubuntu 1810] Migrating Power9 guest back to source causes kernel Oops inside guest

2019-01-07 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

---Problem Description---
Migrating back Power9 to source cause Kernel Oops inside guest
 
Contact Information = Balamuruhan S / balamuruh...@in.ibm.com 
 
---uname output---
source and target host Kernel: 4.18.0-8-generic
Guest Kernel: 4.18.0-8-generic
 
Machine Type = Boston 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---

Due to Bug 172310, Turn off the firewalld in source and target host
machines.

1. Define a healthy guest and placed image in NFS share.

2. Mounted the image location in destination and start the guest to
perform migration.

3. Perform migration from source to target,
08:07:54 INFO | Migrating VM avocado-vt-vm1-migration from qemu:///system to 
qemu+ssh://9.40.194.13/system
08:07:54 DEBUG| Running virsh command: migrate --live --domain 
avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60
08:07:54 INFO | Running '/usr/bin/virsh -c 'qemu:///system' migrate --live 
--domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system 
--timeout 60'
08:08:21 DEBUG| [stdout]
08:08:21 INFO | Command '/usr/bin/virsh -c 'qemu:///system' migrate --live 
--domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system 
--timeout 60' finished with 0 after 26.9465551376s
08:08:21 DEBUG| status: 0
08:08:21 DEBUG| stdout:
08:08:21 DEBUG| stderr:
08:08:21 INFO | Migration exit status: 0

4. check VM uptime after successful migration,
08:07:44 INFO | Check VM uptime before migration: 57.66

5. Migration is successful from source to destination, now perform
migration back to source

08:08:49 INFO | Migrating VM avocado-vt-vm1-migration from 
qemu+ssh://9.40.194.13/system to qemu:///system
08:08:49 DEBUG| Running virsh command: migrate --live --domain 
avocado-vt-vm1-migration --desturi qemu:///system --timeout 60
08:08:49 INFO | Running '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' 
migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system 
--timeout 60'
08:09:22 DEBUG| [stdout]
08:09:22 INFO | Command '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' 
migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system 
--timeout 60' finished with 0 after 32.8640539646s
08:09:22 DEBUG| status: 0
08:09:22 DEBUG| stdout:
08:09:22 DEBUG| stderr:
08:09:22 INFO | Migration exit status: 0

6. check uptime of VM after migration and it is observed that VM have
gone for reboot

08:10:22 INFO | Check VM uptime after migrating back to source: 31.09

5. By checking the VM console Call Trace is observed as mentioned below

The time stamp during the call trace observed inside guest matches with the 
timestamp during which
migration is triggered.
 
Stack trace output:
 no

Attachment:
1. VM sosreport
2. source and target sosreport
3. VM console log with call trace
4. Guest xml
5. Test job log
 
Oops output:
 2018-10-26 08:08:26: root@ubuntu1810:~#
2018-10-26 08:09:11: [  144.512549] Unable to handle kernel paging request for 
data at address 0x71ff9672fa0e0989
2018-10-26 08:09:11: [  144.512655] Faulting instruction address: 
0xc03af7cc
2018-10-26 08:09:11: [  144.512741] Oops: Kernel access of bad area, sig: 11 
[#1]
2018-10-26 08:09:11: [  144.512789] LE SMP NR_CPUS=2048 NUMA pSeries
2018-10-26 08:09:11: [  144.512859] Modules linked in: iscsi_target_mod 
target_core_mod xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter bpfilter kvm dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel 
nfsd ib_iser auth_rpcgss rdma_cm nfs_acl iw_cm lockd ib_cm grace ib_core sunrpc 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
virtio_net net_failover crc32c_vpmsum virtio_blk virtio_scsi failover
2018-10-26 08:09:11: [  144.513801] CPU: 5 PID: 1072 Comm: systemd-network Not 
tainted 4.18.0-8-generic #9-Ubuntu
2018-10-26 08:09:11: [  144.513872] NIP:  c03af7cc LR: c03af7b8 
CTR: c0c9ea80
2018-10-26 08:09:11: [  144.513943] REGS: c000f19ab910 TRAP: 0380   Not 
tainted  (4.18.0-8-generic)
2018-10-26 08:09:11: [  144.514025] MSR:  80009033 
  CR: 24002824  XER: 
2018-10-26 08:09:11: [  144.514102] CFAR: c00174a0 IRQMASK: 0
2018-10-26 08:09:11: [  144.514102] GPR00: c03af670 c000f19abb90 
c178c800 
2018-10-26 08:09:11: [  144.514102] GPR04:  0007 
 0006
2018-10-26 08:09:11: [  144.514102] GPR08: b1ff967250115c09  
 c0d71000
2018-10-26 08:09:11: [  144.514102] GPR12: c0c9ea80 cfff8a00

[Kernel-packages] [Bug 1810392] Re: [Ubuntu 1810] Migrating Power9 guest back to source causes kernel Oops inside guest

2019-01-07 Thread Andrew Cloke

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  [Ubuntu 1810] Migrating Power9 guest back to source causes kernel Oops
  inside guest

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Migrating back Power9 to source cause Kernel Oops inside guest
   
  Contact Information = Balamuruhan S / balamuruh...@in.ibm.com 
   
  ---uname output---
  source and target host Kernel: 4.18.0-8-generic
  Guest Kernel: 4.18.0-8-generic
   
  Machine Type = Boston 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---

  Due to Bug 172310, Turn off the firewalld in source and target host
  machines.

  1. Define a healthy guest and placed image in NFS share.

  2. Mounted the image location in destination and start the guest to
  perform migration.

  3. Perform migration from source to target,
  08:07:54 INFO | Migrating VM avocado-vt-vm1-migration from qemu:///system to 
qemu+ssh://9.40.194.13/system
  08:07:54 DEBUG| Running virsh command: migrate --live --domain 
avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60
  08:07:54 INFO | Running '/usr/bin/virsh -c 'qemu:///system' migrate --live 
--domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system 
--timeout 60'
  08:08:21 DEBUG| [stdout]
  08:08:21 INFO | Command '/usr/bin/virsh -c 'qemu:///system' migrate --live 
--domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system 
--timeout 60' finished with 0 after 26.9465551376s
  08:08:21 DEBUG| status: 0
  08:08:21 DEBUG| stdout:
  08:08:21 DEBUG| stderr:
  08:08:21 INFO | Migration exit status: 0

  4. check VM uptime after successful migration,
  08:07:44 INFO | Check VM uptime before migration: 57.66

  5. Migration is successful from source to destination, now perform
  migration back to source

  08:08:49 INFO | Migrating VM avocado-vt-vm1-migration from 
qemu+ssh://9.40.194.13/system to qemu:///system
  08:08:49 DEBUG| Running virsh command: migrate --live --domain 
avocado-vt-vm1-migration --desturi qemu:///system --timeout 60
  08:08:49 INFO | Running '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' 
migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system 
--timeout 60'
  08:09:22 DEBUG| [stdout]
  08:09:22 INFO | Command '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' 
migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system 
--timeout 60' finished with 0 after 32.8640539646s
  08:09:22 DEBUG| status: 0
  08:09:22 DEBUG| stdout:
  08:09:22 DEBUG| stderr:
  08:09:22 INFO | Migration exit status: 0

  6. check uptime of VM after migration and it is observed that VM have
  gone for reboot

  08:10:22 INFO | Check VM uptime after migrating back to source: 31.09

  5. By checking the VM console Call Trace is observed as mentioned
  below

  The time stamp during the call trace observed inside guest matches with the 
timestamp during which
  migration is triggered.
   
  Stack trace output:
   no

  Attachment:
  1. VM sosreport
  2. source and target sosreport
  3. VM console log with call trace
  4. Guest xml
  5. Test job log
   
  Oops output:
   2018-10-26 08:08:26: root@ubuntu1810:~#
  2018-10-26 08:09:11: [  144.512549] Unable to handle kernel paging request 
for data at address 0x71ff9672fa0e0989
  2018-10-26 08:09:11: [  144.512655] Faulting instruction address: 
0xc03af7cc
  2018-10-26 08:09:11: [  144.512741] Oops: Kernel access of bad area, sig: 11 
[#1]
  2018-10-26 08:09:11: [  144.512789] LE SMP NR_CPUS=2048 NUMA pSeries
  2018-10-26 08:09:11: [  144.512859] Modules linked in: iscsi_target_mod 
target_core_mod xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter bpfilter kvm dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel 
nfsd ib_iser auth_rpcgss rdma_cm nfs_acl iw_cm lockd ib_cm grace ib_core sunrpc 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
virtio_net net_failover crc32c_vpmsum virtio_blk virtio_scsi failover
  2018-10-26 08:09:11: [  144.513801] CPU: 5 PID: 1072 Comm: systemd-network 
Not tainted 4.18.0-8-gener

[Kernel-packages] [Bug 1810636] Re: QCA6174 doesn't utilise btcoex - Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570

2019-01-07 Thread Berg Lloyd-Haig

Ok, I managed to get the latest firmware working. It still exhibits the
same issue. I think I must of only rebooted last time instead of
shutting down completely.

I've tried the speaker sitting on top of the track-pad, about 50 cm away
from the laptop - all to the same effect - the it's like it misses an
audio packet, and rather than dropping the packet, it re-transmits
again, buffering all subsequent packets for the stream. I would rather
lose the packets completely in this case.

The speaker is a Sony SRS-HG1. I can pair the speaker to my Xiaomi Mi8
phone and it negotiates LDAC codec for the Bluetooth audio sink. I can
then run high load on the Mi8 WiFi and play a movie in FullHD over DLNA
and it never skips a beat, there is a small delay as you'd expect with
Bluetooth, but it's less than 100 ms and seems normal after a short
while.

I experienced this problem also in another location when I was house
sitting recently - so different environment/access points etc. I think
demonstrating the problem with the speaker and my phone without any
problems puts me back on the firmware/driver troubleshooting path.

Do you have any other ideas @kaihengfeng? Would you like me to do
Bluetooth packet capture?

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

Title:
QCA6174 doesn't utilise btcoex - Ubuntu 18 Bluetooth Audio
Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570

Status in linux package in Ubuntu:
Confirmed

Bug description:
I'm running Linux 4.20.0-042000-generic #201812232030 x64 on a Dell XPS 9570
with QCA6174 chipset, and have had the problem with Bluetooth audio choppiness
ever since I have owned this laptop. This problem has persisted for me with
previous kernels. If I disable wifi and use media on machine
locally, the problem doesn't occur.

Note: I've reverted back v4.18.0-13-generic and reproduced the problem for
the apport-collect report.

It started with Ubuntu 18.04 and continues with 18.10. It's
particularly noticeable when the when saturating the WLAN connection
with throughput, i.e. copying a large file sequentially across from a
samba share, but also streaming video online results in the audio
progressively delaying over-time. Re-establishing the Bluetooth audio
sync restores the sync, but slowly creeps out again.

I've upgraded my linux-firmware package to disco 176 to match v4.20
kernel drivers ref: https://launchpad.net/ubuntu/+source/linux-
firmware/1.176

The ath10k_core driver that supports this device has a reference for
btcoex: ref

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c?h=v4.20#n2598

It's possible that the Bluetooth component firmware is not supporting
or communicating btcoex compatibility, but this is starting to reach
the edge of my ability to diagnose the problem.

This btcoex support in ath9k has resolved/improved the Bluetooth
bandwidth problem for older Qualcomm chipsets as shown in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164

As a troubleshooting step, I've also tried the very latest firmware-6 file
from, but I'm continuing to experience the problem ref:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: berg 2871 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-07-02 (187 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. XPS 15 9570
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=UUID=c825a7b0-a5ac-41de-bd57-7663fef8a1f1 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
RelatedPackageVersions:
linux-restricted-modules-4.18.0-13-generic N/A
linux-backports-modules-4.18.0-13-generic N/A
linux-firmware 1.176
Tags: cosmic
Uname: Linux 4.18.0-13-generic x86_64
UpgradeStatus: Upgraded to cosmic on 2018-10-18 (79 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/02/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.0
dmi.board.name: 07GHH0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.produ

1 2 >

1 - 100 of 172 matches

Mail list logo