[Kernel-packages] [Bug 1853197] Re: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection

2019-12-08 Thread Bernd Schütte 
it is running for five days and memory consumption looks normal (not
leaking)

** Changed in: linux (Ubuntu Bionic)
   Status: Fix Committed => 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/1853197

Title:
  Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [SRU Justification]

  == Impact ==

  An upstream change in v4.11 made xfrm loose memory (8 pages per ipsec 
connection). This was fixed in v5.4 by:
commit 86c6739eda7d "xfrm: Fix memleak on xfrm state destroy"

  == Fix ==

  Pick the upstream fix into all affected series.

  == Testcase ==

  see below

  == Risk of Regression ==

  Low, the change adds a single memory release case in one driver. The
  effect can be verified.

  ---

  Ubuntu linux distro, 4.15.0-62 kernel, server platform.
  This OS is used as an IPSec VPN gateway.  It serves up to several hundred 
concurrent connections

  In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed
  that VPN gateway VMs were running out of physical memory after 12-48
  hours, depending on load.

  Attachments from a server machine in this state in attached leakinfo.txt
  output of free -t
  output of /proc/meminfo in out of memory condition
  output of /slabtop -o -sc
  /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 
hrs and ran out of memory
  Patches for 4.15 and 5.4

  Highlight from page_owner, we can see the leak is a buffer associated
  with the ipsec impelementation.  Each connection leaks 32k of memory
  via alloc_page with order=3

  100960 times:
  Page allocated via order 3, mask 
0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP)
   get_page_from_freelist+0xd64/0x1250
   __alloc_pages_nodemask+0x11c/0x2e0
   alloc_pages_current+0x6a/0xe0
   skb_page_frag_refill+0x71/0x100
   esp_output_head+0x265/0x3e0 [esp4]
   esp_output+0xbc/0x180 [esp4]
   xfrm_output_resume+0x179/0x530
   xfrm_output+0x8e/0x230
   xfrm4_output_finish+0x2b/0x30
   __xfrm4_output+0x3a/0x50
   xfrm4_output+0x43/0xc0
   ip_forward_finish+0x51/0x80
   ip_forward+0x38a/0x480
   ip_rcv_finish+0x122/0x410
   ip_rcv+0x292/0x360
   __netif_receive_skb_core+0x815/0xbd0

  Patch to fix this issue in 4.15 (tested and verified on same server 
exhibiting above leak):
  diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
  index 728272f..7842f83 100644
  --- a/net/xfrm/xfrm_state.c
  +++ b/net/xfrm/xfrm_state.c
  @@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x)
  }
  xfrm_dev_state_free(x);
  security_xfrm_state_free(x);
  +
  +   if(x->xfrag.page)
  +   put_page(x->xfrag.page);
  +
  kfree(x);
  }

  Patch for master branch (5.4 I believe) from Paul Wouters
  (p...@nohats.ca)

  diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
  index c6f3c4a1bd99..f3423562d933 100644
  --- a/net/xfrm/xfrm_state.c
  +++ b/net/xfrm/xfrm_state.c
  @@ -495,6 +495,8 @@ static void ___xfrm_state_destroy(struct xfrm_state *x)
  x->type->destructor(x);
  xfrm_put_type(x->type);
  }
  + if (x->xfrag.page)
  + put_page(x->xfrag.page);
  xfrm_dev_state_free(x);
  security_xfrm_state_free(x);
  xfrm_state_free(x);

  Severity:  Critical - we are unable to use any kernel later than 4.11,
  and are sticking with 4.4 in production.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853197/+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 1855645] Status changed to Confirmed

2019-12-08 Thread Ubuntu Kernel Bot 
This change was made by a bot.

** 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/1855645

Title:
  Touchpad not working completely.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad stopped working suddenly. At night of yesterday, it was
  working, but in the morning it was not worked. Before its stop working
  there were some packages showing there update and asking for the
  restart of the system. And did not restart that time. After some time
  I shutdown my system. But after starting the system the came in the
  touchpad. My system working in dual boot mode with windows 10 also.
  Touchpad working in the windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   ghanshyam   1675 F...m pulseaudio
   /dev/snd/controlC1:  ghanshyam   1675 F pulseaudio
   /dev/snd/controlC0:  ghanshyam   1675 F pulseaudio
  CRDA:
   global
   country IN: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5150 - 5350 @ 160), (N/A, 23), (N/A)
(5725 - 5875 @ 80), (N/A, 23), (N/A)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 09:57:19 2019
  InstallationDate: Installed on 2019-01-28 (314 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Vostro 3558
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=c754d81b-93d5-449d-aa12-40e76d829be9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PPH4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/01/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0PPH4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 3558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855645/+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 1855645] Re: Touchpad not working completely.

2019-12-08 Thread Chris Guiver 
Thank you for taking the time to report this issue and helping to make
Ubuntu better.

Probable duplicate of 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798
"Synaptics, product: TM3108-002"  (that report impacts Synaptics s3203 and 
TM2714-002)

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

Title:
  Touchpad not working completely.

Status in linux package in Ubuntu:
  New

Bug description:
  The touchpad stopped working suddenly. At night of yesterday, it was
  working, but in the morning it was not worked. Before its stop working
  there were some packages showing there update and asking for the
  restart of the system. And did not restart that time. After some time
  I shutdown my system. But after starting the system the came in the
  touchpad. My system working in dual boot mode with windows 10 also.
  Touchpad working in the windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   ghanshyam   1675 F...m pulseaudio
   /dev/snd/controlC1:  ghanshyam   1675 F pulseaudio
   /dev/snd/controlC0:  ghanshyam   1675 F pulseaudio
  CRDA:
   global
   country IN: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5150 - 5350 @ 160), (N/A, 23), (N/A)
(5725 - 5875 @ 80), (N/A, 23), (N/A)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 09:57:19 2019
  InstallationDate: Installed on 2019-01-28 (314 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Vostro 3558
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=c754d81b-93d5-449d-aa12-40e76d829be9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PPH4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/01/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0PPH4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 3558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855645/+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 1855645] [NEW] Touchpad not working completely.

2019-12-08 Thread Ghanshyam Bairwa 
Public bug reported:

The touchpad stopped working suddenly. At night of yesterday, it was
working, but in the morning it was not worked. Before its stop working
there were some packages showing there update and asking for the restart
of the system. And did not restart that time. After some time I shutdown
my system. But after starting the system the came in the touchpad. My
system working in dual boot mode with windows 10 also. Touchpad working
in the windows 10.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-72-generic 4.15.0-72.81
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   ghanshyam   1675 F...m pulseaudio
 /dev/snd/controlC1:  ghanshyam   1675 F pulseaudio
 /dev/snd/controlC0:  ghanshyam   1675 F pulseaudio
CRDA:
 global
 country IN: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5150 - 5350 @ 160), (N/A, 23), (N/A)
(5725 - 5875 @ 80), (N/A, 23), (N/A)
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  9 09:57:19 2019
InstallationDate: Installed on 2019-01-28 (314 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Vostro 3558
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=c754d81b-93d5-449d-aa12-40e76d829be9 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-72-generic N/A
 linux-backports-modules-4.15.0-72-generic  N/A
 linux-firmware 1.173.12
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0PPH4M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/01/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0PPH4M:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Vostro 3558
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  Touchpad not working completely.

Status in linux package in Ubuntu:
  New

Bug description:
  The touchpad stopped working suddenly. At night of yesterday, it was
  working, but in the morning it was not worked. Before its stop working
  there were some packages showing there update and asking for the
  restart of the system. And did not restart that time. After some time
  I shutdown my system. But after starting the system the came in the
  touchpad. My system working in dual boot mode with windows 10 also.
  Touchpad working in the windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   ghanshyam   1675 F...m pulseaudio
   /dev/snd/controlC1:  ghanshyam   1675 F pulseaudio
   /dev/snd/controlC0:  ghanshyam   1675 F pulseaudio
  CRDA:
   global
   country IN: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5150 - 5350 @ 160), (N/A, 23), (N/A)
(5725 - 5875 @ 80), (N/A, 23), (N/A)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 09:57:19 2019
  InstallationDate: Installed on 2019-01-28 (314 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Vostro 3558
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=c754d81b-93d5-449d-aa12-40e76d829be9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PPH4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/01/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0PPH4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 3558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1826461] Re: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection.

2019-12-08 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Suspend fails on Ubuntu 18.04 when mobile network connected and no
  WiFi connection.

Status in linux package in Ubuntu:
  Expired
Status in modem-manager-gui package in Ubuntu:
  Expired

Bug description:
  Suspend fails on Ubuntu 18.04 when mobile network connected and no
  WiFi connection.

  Ubuntu 18.04, Thinkpad X240, Sierra modem
  Reproduced on 4.15 and 4.18 kernel. 
  The bug is triggered only when there is no WiFi connection. After waking 
laptop from suspend ModemManager stops working and after that I cannot suspend 
anymore. When it happens mmcli -L gives:

  Found 1 modems:
  /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001]

  And mmcli -m 9:

Status   |   lock: 'none'
 | unlock retries: 'sim-pin (3)'
 |  state: 'registered'
 |power state: 'on'
 |access tech: 'gprs, lte'
 | signal quality: '0' (cached)

  After a few attempts to restart ModemManager and suspend it starts
  working. But only for one suspend. After one suspend I need to do the
  whole procedure again.

  Similar to:
  
https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743

  On Ubuntu 16.04 suspend and ModemManager used to work flawlessly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan2384 F pulseaudio
   /dev/snd/controlC1:  jan2384 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998
  InstallationDate: Installed on 2016-10-22 (915 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20ALA0ARHH
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-generic N/A
   linux-backports-modules-4.18.0-18-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.18.0-18-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago)
  UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET94WW (2.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALA0ARHH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X240
  dmi.product.name: 20ALA0ARHH
  dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+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 1826461] Re: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection.

2019-12-08 Thread Launchpad Bug Tracker 
[Expired for modem-manager-gui (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: modem-manager-gui (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Suspend fails on Ubuntu 18.04 when mobile network connected and no
  WiFi connection.

Status in linux package in Ubuntu:
  Expired
Status in modem-manager-gui package in Ubuntu:
  Expired

Bug description:
  Suspend fails on Ubuntu 18.04 when mobile network connected and no
  WiFi connection.

  Ubuntu 18.04, Thinkpad X240, Sierra modem
  Reproduced on 4.15 and 4.18 kernel. 
  The bug is triggered only when there is no WiFi connection. After waking 
laptop from suspend ModemManager stops working and after that I cannot suspend 
anymore. When it happens mmcli -L gives:

  Found 1 modems:
  /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001]

  And mmcli -m 9:

Status   |   lock: 'none'
 | unlock retries: 'sim-pin (3)'
 |  state: 'registered'
 |power state: 'on'
 |access tech: 'gprs, lte'
 | signal quality: '0' (cached)

  After a few attempts to restart ModemManager and suspend it starts
  working. But only for one suspend. After one suspend I need to do the
  whole procedure again.

  Similar to:
  
https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743

  On Ubuntu 16.04 suspend and ModemManager used to work flawlessly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan2384 F pulseaudio
   /dev/snd/controlC1:  jan2384 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998
  InstallationDate: Installed on 2016-10-22 (915 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20ALA0ARHH
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-generic N/A
   linux-backports-modules-4.18.0-18-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.18.0-18-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago)
  UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET94WW (2.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALA0ARHH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X240
  dmi.product.name: 20ALA0ARHH
  dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+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 1843790] Re: [Thunderbolt][CML-U/S] After freeze sleep finished more than 30s, lspci trigger tbt in D0, "TX ring 0 is already enabled" Call Trace generated and then failed to se

2019-12-08 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [Thunderbolt][CML-U/S] After freeze sleep finished more than 30s,
  lspci trigger tbt in D0, "TX ring 0 is already enabled" Call Trace
  generated and then failed to send driver ready to ICM

Status in intel:
  Won't Fix
Status in linux package in Ubuntu:
  Expired

Bug description:
  Description
  Platform: CML-U (CML-S no need TR AIC)

  TR AIC: rev41

  Linux kernel: 5.3.0-rc1

  No TBT device connected.

  Executed freeze sleep successfully, after freeze exit more than 30s,

  cat /sys/bus/thunderbolt/devices/domain0/boot_acl  and lspci to
  trigger TBT root port in D0.

  Then "TX ring 0 is already enabled" Call Trace generated, then failed
  to send driver ready to  ICM.

  Thunderbolt driver was down.
   

  [ 263.903342] LTP: starting TBT_XS_FUNC_RTD3_freeze_test (tbt_rtd3.sh -c 0 -s 
rtd3_host_freeze)
  [ 264.010613] PM: suspend entry (s2idle)
  [ 286.868539] PM: suspend exit
  [ 313.202856] thunderbolt :03:00.0: stopping RX ring 0
  [ 313.204135] thunderbolt :03:00.0: disabling interrupt at register 
0x38200 bit 12 (0x1001 -> 0x1)
  [ 313.205565] thunderbolt :03:00.0: stopping TX ring 0
  [ 313.206842] thunderbolt :03:00.0: disabling interrupt at register 
0x38200 bit 0 (0x1 -> 0x0)
  [ 313.208018] thunderbolt :03:00.0: control channel stopped
  [ 321.432230] pcieport :02:01.0: pciehp: Slot(1): Link Up
  [ 321.433559] pcieport :02:04.0: pciehp: Slot(4-1): Link Up
  [ 322.550092] xhci_hcd :39:00.0: Refused to change power state, currently 
in D3
  [ 322.671084] thunderbolt :03:00.0: control channel starting...
  [ 322.672343] thunderbolt :03:00.0: starting TX ring 0
  [ 322.673601] thunderbolt :03:00.0: enabling interrupt at register 
0x38200 bit 0 (0x -> 0x)
  [ 322.674912] ---[ cut here ]---
  [ 322.676173] thunderbolt :03:00.0: interrupt for TX ring 0 is already 
enabled
  [ 322.706970] Call Trace:
  [ 322.708542] tb_ring_start+0x110/0x1a0 [thunderbolt]
  [ 322.710166] tb_ctl_start+0x36/0xc0 [thunderbolt]
  [ 322.711762] ? pci_restore_standard_config+0x50/0x50
  [ 322.71] ? pci_restore_standard_config+0x50/0x50
  [ 322.748162] thunderbolt :03:00.0: interrupt for RX ring 0 is already 
enabled
  [ 322.788047] ? pci_restore_standard_config+0x50/0x50
  [ 322.789901] ? pci_restore_standard_config+0x50/0x50
  [ 404.405929] thunderbolt :03:00.0: failed to send driver ready to ICM
  [ 405.596681] LTP: starting TBT_XS_FUNC_RTD3_S3_test (tbt_rtd3.sh -c 0 -s 
rtd3_host_s3)

  
  Target Release: 20.04
  Target Kernel: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1843790/+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 1426216] Re: pci driver messages - BAR 13: no space for

2019-12-08 Thread gst 
Hi,

I am also impacted. 18.04 with 5.0 and 4.15 kernels.

My system also freezes from time to time.


```
[  171.384150] pci_bus :03: Allocating resources
[  171.384173] pcieport :03:01.0: bridge window [io  0x1000-0x0fff] to [bus 
05-39] add_size 1000
[  171.384181] pcieport :03:02.0: bridge window [io  0x1000-0x0fff] to [bus 
3a] add_size 1000
[  171.384182] pcieport :03:02.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 3a] add_size 20 add_align 10
[  171.384190] pcieport :02:00.0: bridge window [io  0x1000-0x0fff] to [bus 
03-3a] add_size 3000
[  171.384192] pcieport :02:00.0: BAR 13: no space for [io  size 0x3000]
[  171.384193] pcieport :02:00.0: BAR 13: failed to assign [io  size 0x3000]
[  171.384194] pcieport :02:00.0: BAR 13: no space for [io  size 0x3000]
[  171.384194] pcieport :02:00.0: BAR 13: failed to assign [io  size 0x3000]
[  171.384196] pcieport :03:02.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
[  171.384197] pcieport :03:02.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
[  171.384198] pcieport :03:01.0: BAR 13: no space for [io  size 0x1000]
[  171.384198] pcieport :03:01.0: BAR 13: failed to assign [io  size 0x1000]
[  171.384199] pcieport :03:02.0: BAR 13: no space for [io  size 0x1000]
[  171.384200] pcieport :03:02.0: BAR 13: failed to assign [io  size 0x1000]
[  171.384201] pcieport :03:02.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
[  171.384201] pcieport :03:02.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
[  171.384202] pcieport :03:02.0: BAR 13: no space for [io  size 0x1000]
[  171.384203] pcieport :03:02.0: BAR 13: failed to assign [io  size 0x1000]
[  171.384203] pcieport :03:01.0: BAR 13: no space for [io  size 0x1000]
[  171.384204] pcieport :03:01.0: BAR 13: failed to assign [io  size 0x1000]
[  176.033220] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure 
on pipe A (start=12148 end=12149) time 3562 us, min 1073, max 1079, scanline 
start 1071, end 192
[  176.486807] pcieport :03:00.0: Refused to change power state, currently 
in D3
[  176.556903] pci_bus :04: busn_res: [bus 04] is released
[  176.556962] pci_bus :05: busn_res: [bus 05-39] is released
[  176.557053] pci_bus :3a: busn_res: [bus 3a] is released
[  176.557161] pci_bus :03: busn_res: [bus 03-3a] is released
```

I have also quite lot of :

[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe
A (start=12148 end=12149) time 3562 us, min 1073, max 1079, scanline
start 1071, end 192

Not sure if related. I can give more details if requested.

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

Title:
  pci driver messages - BAR 13: no space for

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  pci driver messages - BAR 13: no space for 

  ---uname output---
  3.18.0-12-generic
   
  Machine Type = POWER8 

  ---Steps to Reproduce---
  Install Ubuntu 15.04 daily build running bare-metal
  After the installation following messages are seen in dmesg. 
  Not sure if these indicate a problem. Can some one look at these and confirm 
if this is problem or can be ignored ?

  Messages from dmesg log

  [0.714476] pci_bus 0001:00: max bus depth: 3 pci_try_num: 4
  [0.714519] pci 0001:04:00.0: reg 0x16c: [mem 0x-0x 64bit]
  [0.714541] pci 0001:04:00.0: reg 0x174: [mem 0x-0x 64bit]
  [0.714577] pci 0001:00:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714579] pci 0001:00:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe081ff]
  [0.714581] pci 0001:00:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714583] pci 0001:00:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714586] pci 0001:01:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714588] pci 0001:01:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0817f]
  [0.714590] pci 0001:01:00.0: BAR 0: assigned [mem 
0x3fe08180-0x3fe08183]
  [0.714595] pci 0001:01:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714597] pci 0001:01:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714600] pci 0001:02:01.0: BAR 15: assigned [mem 
0x3b101000-0x3b101fff 64bit pref]
  [0.714602] pci 0001:02:08.0: BAR 15: assigned [mem 
0x3b102000-0x3b102fff 64bit pref]
  [0.714604] pci 0001:02:09.0: BAR 15: assigned [mem 
0x3b103000-0x3b103fff 64bit pref]
  [0.714606] pci 0001:02:01.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0807f]
  [0.714608] pci 0001:02:08.0: BAR 14: assigned [mem 
0x3fe08080-0x3fe080ff]
  [0.714609] pci 0001:02:09.0: BAR 14: assigned [mem 
0x3fe08100-0x3fe0817f]

[Kernel-packages] [Bug 1855584] Re: [Hasee NH50_70_55_58_ED, EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS

2019-12-08 Thread sgqy 
> #19

I tried the two kernel. For now. And have another problem, maybe not
important. 樂

5.3.0-24-ubuntu (current)
5.4.2-mainline

On the beginning, speaker never works. Headphone have only two volume: 0
and 100 (unable to change volume).

I removed '/var/lib/alsa/*' and '~/.config/pulse/*'.

1st reboot: pulseaudio not work.
2nd/3rd reboot: pulseaudio started. The volume is init value.

1st VLC play: speaker and headphone works. When changing volume, the music lags 
and lags and repeats.
2nd/3rd VLC play: volume changing becomes smooth. Everything just works.

(The two kernels have the same behavior above.)


But... The noise problem is random, keep watching. 

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable

[Kernel-packages] [Bug 1846335] Re: [CML] New device id's for CMP-H

2019-12-08 Thread You-Sheng Yang 
Verified 5.3.0-25.27/eoan-proposed, 5.0.0-38.41/disco-proposed.

** Description changed:

+ [Impact]
+ On new CML PCH-H platforms, many devices are not correctly probed,
+ inclusive of touchpad.
+ 
+ [Fix]
+ New device IDs for CML PCH-H are landed in v5.4-rc1 and linux-next. So
+ far the known list are:
+ * 8f05eee67c14: "mmc: sdhci-pci: Add another Id for Intel CML"
+ * 07f047e3fe33: "i2c: i801: Add support for Intel Comet Lake PCH-H"
+ * 5a0feb6287e3: "mtd: spi-nor: intel-spi: Add support for Intel Comet
+   Lake-H SPI serial flash"
+ * dd047dce3a6f: "mfd: intel-lpss: Add Intel Comet Lake PCH-H PCI IDs"
+ 
+ The first one has been included in v5.4-rc1, while the rest are
+ currently in linux-next.
+ 
+ [Test Case]
+ Verify built kernel on platforms with CML PCH-H. Check if intel-lpss
+ module is loaded, i2c-hid is probed, and so on.
+ 
+ [Regression Potential]
+ Low. These patches add only new device IDs of previously not probed
+ devices.
+ 
+ [Other Info]
+ There 4 patches for OEM-OSP1-B/D/E and only 3 for U because 8f05eee67c14
+ is already included in U.
+ 
+ == original bug description ==
+ 
  split from bug 1843774
  
  Description
  This task is to identify what new device IDs are required for CML PCH-H.
  
  Controller Kernel Version Commit Approved to be published Comments
  USB device/xDCI 0x02ee v5.2 7ae622c978db6b2
  I²C (CMP-H)|0x06c5 0x06c6 0x06e8 0x06e9 0x06ea 0x06eb
  
https://lore.kernel.org/lkml/20191029094409.43741-1-andriy.shevche...@linux.intel.com/
  
  HS-UART (CMP-H) 0x06a8 0x06a9 0x06c7
  
https://lore.kernel.org/lkml/20191029094409.43741-1-andriy.shevche...@linux.intel.com/
  
  SPI (CMP-H) 0x06aa 0x06ab 0x06fb f0cf17ed76cf from spi.git
  
https://lore.kernel.org/lkml/20191029094409.43741-1-andriy.shevche...@linux.intel.com/
  
  SPI Flash Controller (CMP-H) 0x06a4 https://lore.kernel.org/linux-
  mtd/20191023145140.51427-1-mika.westerb...@linux.intel.com/
  
  GPIO(CMP-H) INT3450 "It seems the same as for CNL, nothing needs to be done 
here.
  SD Card (CMP-H) 0x06f5 v5.4-rc1 8f05eee67c1404a
  SMBus (CMP-H) 0x06a3 v5.5 07f047e3fe33
  
  Target Release: 19.10

** Tags removed: verification-needed-disco verification-needed-eoan
** Tags added: verification-done-disco verification-done-eoan

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

Title:
  [CML] New device id's for CMP-H

Status in HWE Next:
  New
Status in intel:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem-osp1 source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  New

Bug description:
  [Impact]
  On new CML PCH-H platforms, many devices are not correctly probed,
  inclusive of touchpad.

  [Fix]
  New device IDs for CML PCH-H are landed in v5.4-rc1 and linux-next. So
  far the known list are:
  * 8f05eee67c14: "mmc: sdhci-pci: Add another Id for Intel CML"
  * 07f047e3fe33: "i2c: i801: Add support for Intel Comet Lake PCH-H"
  * 5a0feb6287e3: "mtd: spi-nor: intel-spi: Add support for Intel Comet
Lake-H SPI serial flash"
  * dd047dce3a6f: "mfd: intel-lpss: Add Intel Comet Lake PCH-H PCI IDs"

  The first one has been included in v5.4-rc1, while the rest are
  currently in linux-next.

  [Test Case]
  Verify built kernel on platforms with CML PCH-H. Check if intel-lpss
  module is loaded, i2c-hid is probed, and so on.

  [Regression Potential]
  Low. These patches add only new device IDs of previously not probed
  devices.

  [Other Info]
  There 4 patches for OEM-OSP1-B/D/E and only 3 for U because 8f05eee67c14
  is already included in U.

  == original bug description ==

  split from bug 1843774

  Description
  This task is to identify what new device IDs are required for CML PCH-H.

  Controller Kernel Version Commit Approved to be published Comments
  USB device/xDCI 0x02ee v5.2 7ae622c978db6b2
  I²C (CMP-H)|0x06c5 0x06c6 0x06e8 0x06e9 0x06ea 0x06eb
  
https://lore.kernel.org/lkml/20191029094409.43741-1-andriy.shevche...@linux.intel.com/

  HS-UART (CMP-H) 0x06a8 0x06a9 0x06c7
  
https://lore.kernel.org/lkml/20191029094409.43741-1-andriy.shevche...@linux.intel.com/

  SPI (CMP-H) 0x06aa 0x06ab 0x06fb f0cf17ed76cf from spi.git
  
https://lore.kernel.org/lkml/20191029094409.43741-1-andriy.shevche...@linux.intel.com/

  SPI Flash Controller (CMP-H) 0x06a4 https://lore.kernel.org/linux-
  mtd/20191023145140.51427-1-mika.westerb...@linux.intel.com/

  GPIO(CMP-H)

[Kernel-packages] [Bug 1847451] Re: [CML-S62] Need enable turbostat patch support for Comet lake- S 6+2

2019-12-08 Thread You-Sheng Yang 
Verified 5.3.0-25.27/eoan-proposed, 5.0.0-1032.36/bionic-proposed.

** Tags removed: verification-needed-bionic verification-needed-eoan
** Tags added: verification-done-bionic verification-done-eoan

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

Title:
  [CML-S62] Need enable turbostat patch support for Comet lake- S 6+2

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem-osp1 source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Confirmed
Status in linux source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  New

Bug description:
  [SRU Justification]

  [Impact]
  Cometlake -S 6+2 is using a different CPU Model number: DEC 165, HEX
  A5, and turbostat doesn't currently have them, therefore it gives
  incomplete info on Comet Lake platforms.

  [Fix]
  commit 68973b44c860 "tools/power turbostat: Add Cometlake support" to
  be backported to all series as it's currently not yet available in
  mainline.

  [Test Case]
  Run `sudo /usr/lib//turbostat` and check if extra fields,
  e.g. TSC, MSR_PKG_POWER_INFO, MSR_PKGC{3,6,7,8,9,10}_IRTL, are listed.

  [Regression Potential]
  Low. This adds new CPU model support.

  == original bug description ==

  Description
  Cometlake -S 6+2 is using a different CPU Model number: DEC 165, HEX: A5

  We need the turbostat patch to support CML-S 6+2

  Target Kernel: 5.6
  Target Release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1847451/+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 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

2019-12-08 Thread Jorgehn 
I have tried what described by AaronMa (apengyu) and now the touchpad of
my Dell Inspiron works perfectly. Thank you so much.

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

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  SRU justification
  =
  [Impact]
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

  [Fix]
  After applied commit "Input: synaptics-rmi4 - avoid processing unknown
  IRQs",
  no irq response from touchpad.
  This commit is depended on commit:
  "Input: synaptics-rmi4 - convert irq distribution to irq_domain"

  [Test]
  Verified on hardware, tests results are good.

  [Regression Potential]
  Low.
  Fix bug that introduced by stable release update.

  2nd and 3rd patches are fixes for the 1st patch.
  These commits are already included by eoan kernel, so bionic 4.15 only.

  Original reports
  ===

  environment:
  Dell Laptop XPS-9333
  Device:
  # xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  id=9[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Ultrathin Touch Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]

  # xinput --list-props 12
  Device 'Synaptics s3203':
   Device Enabled (142):1
   Coordinate Transformation Matrix (144):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (270):  1
   Device Accel Constant Deceleration (271):2.50
   Device Accel Adaptive Deceleration (272):1.00
   Device Accel Velocity Scaling (273): 9.712231
   Synaptics Edges (304):   162, 3908, 133, 2339
   Synaptics Finger (305):  25, 30, 0
   Synaptics Tap Time (306):180
   Synaptics Tap Move (307):209
   Synaptics Tap Durations (308):   180, 180, 100
   Synaptics ClickPad (309):1
   Synaptics Middle Button Timeout (310):   0
   Synaptics Two-Finger Pressure (311): 282
   Synaptics Two-Finger Width (312):7
   Synaptics Scrolling Distance (313):  -95, 95
   Synaptics Edge Scrolling (314):  0, 0, 0
   Synaptics Two-Finger Scrolling (315):1, 1
   Synaptics Move Speed (316):  1.00, 1.75, 0.042008, 0.00
   Synaptics Off (317): 0
   Synaptics Locked Drags (318):0
   Synaptics Locked Drags Timeout (319):5000
   Synaptics Tap Action (320):  0, 0, 0, 0, 1, 3, 2
   Synaptics Click Action (321):1, 3, 2
   Synaptics Circular Scrolling (322):  0
   Synaptics Circular Scrolling Distance (323): 0.10
   Synaptics Circular Scrolling Trigger (324):  0
   Synaptics Circular Pad (325):0
   Synaptics Palm Detection (326):  1
   Synaptics Palm Dimensions (327): 10, 200
   Synaptics Coasting Speed (328):  20.00, 50.00
   Synaptics Pressure Motion (329): 30, 160
   Synaptics Pressure Motion Factor (330):  1.00, 1.00
   Synaptics Resolution Detect (331):   1
   Synaptics Grab Event Device (332):   0
   Synaptics Gestures (333):1
   Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0
   Synaptics Pad Resolution (335):  42, 42
   Synaptics Area (336):0, 0, 0, 0
   Synaptics Soft Button Areas (337):   0, 0, 0, 0, 0, 0, 0, 0
   Synaptics Noise Cancellation (338):  23, 23
   Device Product ID (262): 1739, 10036
   Device Node (263):   "/dev/input/event5"

  # lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
09)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI

[Kernel-packages] [Bug 1847450] Re: [CML-S62] Need enable intel_pmc_core driver patch for Comet lake- S 6+2

2019-12-08 Thread You-Sheng Yang 
Verified 5.3.0-25.27/eoan-proposed, 5.0.0-1032.36/bionic-proposed.

** Tags removed: verification-needed-bionic verification-needed-eoan
** Tags added: verification-done-bionic verification-done-eoan

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

Title:
  [CML-S62] Need enable intel_pmc_core driver patch for Comet lake- S
  6+2

Status in intel:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  New
Status in linux source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  There is no way to access information under /sys/kernel/debug/pmc_core
  on Comet Lake platforms.

  [Fix]
  * https://lkml.org/lkml/2019/11/18/713 ("platform/x86: intel_pmc_core: Add 
Comet
Lake (CML) platform support to intel_pmc_core driver")

  [Test Case]
  1. install prebuilt kernels from ppa:vicamo/ppa-1847450
  2. boot with installed kernel and check if /sys/kernel/debug/pmc_core is
 then available.

  [Regression Potential]
  Low. This only adds two new IDs to a model white list and doesn't change
  behavior of existing systems.

  == original bug description ==

  Description
  Cometlake -S 6+2 is using a different CPU Model number: DEC 165, HEX: A5

  We need the intel_pmc_core driver patch to support CML-S6+2

  Target Kernel: 5.5
  Target Release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1847450/+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 1854842] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs

2019-12-08 Thread Matthew Ruffell 
Hi Mohammad,

I have completed backporting both commits and I have built test kernels
for each.

Can you install the test kernels and run the reproducer with Mellanox hardware?
My lab doesn't have any Mellanox NICs, so I can't test myself.

Please note these test kernels are NOT SUPPORTED by Canonical, and are
for TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment.

The first test kernel is for:

Subject: net/mlx5e: Rx, Fixup skb checksum for packets with tail padding
Commit: 0aa1d18615c163f92935b806dcaff9157645233a
Backport: https://paste.ubuntu.com/p/Svfp8DQGRP/

Instructions to install (On a bionic system)
1) sudo add-apt-repository ppa:mruffell/lp1854842-test
2) sudo apt-get update
3) sudo apt install linux-image-unsigned-4.15.0-72-generic 
linux-modules-4.15.0-72-generic linux-modules-extra-4.15.0-72-generic 
linux-headers-4.15.0-72 linux-headers-4.15.0-72-generic
4) sudo reboot
5) uname -rv
4.15.0-72-generic #81+hf1854842v20191207b2-Ubuntu SMP Sat Dec 7 09:51:02 UTC 
2019

Run the reproducer and see if the problem is fixed or not.

The second test kernel is for:

Subject: net/mlx5e: Rx, Fix checksum calculation for new hardware
Commit: db849faa9bef993a1379dc510623f750a72fa7ce
Backport: https://paste.ubuntu.com/p/QNPPSDf5Tm/

Instructions to install (On a bionic system)
1) sudo add-apt-repository ppa:mruffell/lp1854842-test-2
2) sudo apt-get update
3) sudo apt install linux-image-unsigned-4.15.0-72-generic 
linux-modules-4.15.0-72-generic linux-modules-extra-4.15.0-72-generic 
linux-headers-4.15.0-72 linux-headers-4.15.0-72-generic
4) sudo reboot
5) uname -rv
4.15.0-72-generic #81+hf1854842v20191209b1-Ubuntu SMP Sun Dec 8 23:37:16 UTC 
2019

Run the reproducer and see if the problem is fixed or not.

Hopefully one of these kernels / commits fixes the problem. If it does,
I will submit the commit to the Ubuntu kernel mailing list for SRU.

If neither of the kernels fix the problem, we will have to continue
debugging.

Can you please test the kernels for me and let me know how they go?

Thanks,
Matthew

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

Title:
  mlx5_core reports hardware checksum error for padded packets on
  Mellanox NICs

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
  Hi,
  we have the following issue which affects a lot of our customers this issue 
fixes upstream and need to add the fixes to ubuntu 18.04.

  Mlx5 driver: Tail padding HW Checksum crash in Ubuntu 18.04 kernel
  Ubuntu-4.15.0-72

  Crach log:

  [  785.337368] Call Trace:

  [  785.337372]   

  [  785.337388]  dump_stack+0x63/0x8e  

  [  785.337397]  netdev_rx_csum_fault+0x38/0x40

  [  785.337403]  __skb_checksum_complete+0xbc/0xd0 

  [  785.337408]  nf_ip_checksum+0xc3/0xf0  

  [  785.337417]  icmp_error+0x27d/0x310 [nf_conntrack_ipv4]

  [  785.337431]  nf_conntrack_in+0x15a/0x510 [nf_conntrack]

  [  785.337437]  ? __skb_checksum+0x68/0x330   

  [  785.337441]  ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]   

  [  785.337449]  nf_hook_slow+0x48/0xc0

  [  785.337452]  ? skb_send_sock+0x50/0x50
  [  785.337460]  ip_rcv+0x301/0x360
  [  785.337463]  ? inet_del_offload+0x40/0x40
  [  785.337468]  __netif_receive_skb_core+0x432/0xb80
  [  785.337473]  __netif_receive_skb+0x18/0x60
  [  785.337477]  ? __netif_receive_skb+0x18/0x60
  [  785.337481]  netif_receive_skb_internal+0x45/0xe0
  [  785.337483]  napi_gro_receive+0xc5/0xf0
  [  785.337517]  mlx5e_handle_rx_cqe+0x48d/0x5e0 [mlx5_core]
  [  785.337524]  ? enqueue_task_rt+0x1b4/0x2e0
  [  785.337546]  mlx5e_poll_rx_cq+0xd1/0x8c0 [mlx5_core]
  [  785.337566]  mlx5e_napi_poll+0x9d/0x290 [mlx5_core]
  [  785.337569]  net_rx_action+0x140/0x3a0
  [  785.337574]  __do_softirq+0xe4/0x2d4
  [  785.337580]  irq_exit+0xc5/0xd0
  [  785.337583]  do_IRQ+0x86/0xe0
  [  785.337588]  common_interrupt+0x8c/0x8c
  [  785.337590]  
  [  785.337598] RIP: 0010:cpuidle_enter_state+0xa4/0x2f0
  [  785.337600] RSP: 0018:ad8d8329fe68 EFLAGS: 0246 ORIG_RAX: 
ffd9
  [  785.337604] RAX: 8a6c7f7e1840 RBX: 00b6d9bf6a06 RCX: 
001f
  [  785.337605] RDX: 00b6d9bf6a06 RSI: ffd4a4b4c86359ce RDI: 

  [  785.337607] RBP: ad8d8329fea8 R08: 0004 R09: 
00021080
  [  785.337609] R10: ad8d8329fe38 R11: 0056b80166a42400 R12: 
8a6c7f7ece18
  [  785.337610] R13: 0005 R14: aff73438

[Kernel-packages] [Bug 1848978] Re: CML: perf enabling for core

2019-12-08 Thread You-Sheng Yang 
Verified 5.3.0-25.27/eoan-proposed

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ There is no complete perf support for Comet Lake CPU. For Ice Lake, some
+ changes has been included in v5.3, but still misses CPU IDs.
+ 
+ [Fix]
+ perf support for Comet Lake is based on previous works for Ice Lake, so
+ changes for both have to be backported.
+ 
+ [Test Case]
+ On platforms with Comet Lake/Ice Lake CPUs, one should find new
+ cstate_pkg events c{8,9,10}-residency appear in output of `perf list`
+ for use.
+ 
+ [Regression Potential]
+ Low. This backports perf support for previously incompletedly supported
+ cpu models.
+ 
+ == original bug description ==
+ 
  Description:
  
  CML perf enabling for core
  
  v5.4-rc3
  1ffa6c04dae39776a3c222bdf88051e394386c01 
9066288b2aab1804dc1eebec6ff88474363b89cb 
9674b1cc0f94c34f76e58c102623a866836f269e
  
- 
  Target Kernel: 5.4
  Target Release: 20.04

** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  CML: perf enabling for core

Status in intel:
  Fix Committed
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-osp1 source package in Focal:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]
  There is no complete perf support for Comet Lake CPU. For Ice Lake, some
  changes has been included in v5.3, but still misses CPU IDs.

  [Fix]
  perf support for Comet Lake is based on previous works for Ice Lake, so
  changes for both have to be backported.

  [Test Case]
  On platforms with Comet Lake/Ice Lake CPUs, one should find new
  cstate_pkg events c{8,9,10}-residency appear in output of `perf list`
  for use.

  [Regression Potential]
  Low. This backports perf support for previously incompletedly supported
  cpu models.

  == original bug description ==

  Description:

  CML perf enabling for core

  v5.4-rc3
  1ffa6c04dae39776a3c222bdf88051e394386c01 
9066288b2aab1804dc1eebec6ff88474363b89cb 
9674b1cc0f94c34f76e58c102623a866836f269e

  Target Kernel: 5.4
  Target Release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1848978/+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 1847454] Re: [CML-S62] Need enable intel_rapl patch support for Comet lake- S 6+2

2019-12-08 Thread You-Sheng Yang 
Verified 5.3.0-25.27/eoan-proposed.

** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  [CML-S62] Need enable intel_rapl patch support for Comet lake- S 6+2

Status in intel:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem-osp1 source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Confirmed
Status in linux source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]
  Intel RAPL (running average power limit) driver doesn't support Comet
  Lake platforms.

  [Fix]
  Two commits from linux-next tree to be SRU-ed:
  * commit cae478114fbe ("powercap/intel_rapl: add support for CometLake 
Mobile")
  * commit f84fdcbc8ec0 ("powercap/intel_rapl: add support for Cometlake
desktop")

  [Test Case]
  1. Boot prebuilt kernel from ppa:vicamo/ppa-1847454
  2. Check if /sys/devices/virtual/powercap/intel-rapl is created and
 populated.

  [Regression Potential]
  Low. This affects only platforms with specific CPU models, which have no
  intel_rapl support currently.

  == original bug description ==

  Description
  Cometlake -S 6+2 is using a different CPU Model number: DEC 165, HEX: A5

  We need the intel_rapl patch to support CML-S 6+2

  Target Kernel: 5.6
  Target Release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1847454/+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 1855460] Re: Touchpad Not Working After Update

2019-12-08 Thread Po-Hsu Lin 
*** This bug is a duplicate of bug 1854798 ***
https://bugs.launchpad.net/bugs/1854798

Hello,
this looks like a duplicate of bug 1854798
please feel free to change the status if you think it's different.

Thank you.

** This bug has been marked a duplicate of bug 1854798
   Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-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/1855460

Title:
  Touchpad Not Working After Update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently did the automated software update on my computer. It
  required that I restart my computer. Upon restarting, the touchpad was
  no longer responsive. Left and Right clicking doesn't work either.
  This is a Dell laptop.

  This information is from the sticker on the bottom of the laptop. 
  Windows
  Vostro 15
  45173/SDPPI/2016 Made in China DPC
  SERVICE TAG(S\N): FWKQXN2 
  MFG YR: 2018 

  34621501646
  EXPRESS SERVICE CODE

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-lowlatency 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-lowlatency 4.15.18
  Uname: Linux 4.15.0-72-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  breakthrough   1159 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Dec  6 10:01:51 2019
  InstallationDate: Installed on 2019-04-01 (248 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 15-3568
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-lowlatency 
root=UUID=ed003051-5bde-4bcf-af52-88a32c940792 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-lowlatency N/A
   linux-backports-modules-4.15.0-72-lowlatency  N/A
   linux-firmware1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.0
  dmi.board.name: 09PD65
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.0:bd05/15/2018:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn09PD65:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855460/+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 1853440] Re: Volume either 0 or 100% on Lenovo X1 Carbon G7

2019-12-08 Thread AaronMa 
Could you try linux-oem-osp1 kernel?

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

Title:
  Volume either 0 or 100% on Lenovo X1 Carbon G7

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Volume increasing or decreasing doesn't work. 
  I can only toggle sound on (= 100%) and off (= 0%).

  What I found out is that the Master channel seems to have no effect
  for volume adjustments, but the PCM channel does. If the sound is
  muted, PCM is set to 0 and therefore the sound is toggled off, but
  when I increase the sound a bit, PCM jumps straight to 100, causing
  the speakers to be very load.

  I have attached alsa-info output.

  System environment:
  Pop!_OS 19.10
  Release: 19.10

  Alsa-Version:
  alsa-base: 1.0.25

  Sound Card:
  HDA-Intel
  Codec: Realtek ALC285
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: pop:GNOME
  DisplayManager: gdm3
  DistroRelease: Pop!_OS 19.10
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 
5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7
  RelatedPackageVersions: mutter-common 
3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a
  Tags: third-party-packages eoan
  Uname: Linux 5.3.0-22-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1855584] Re: [Hasee NH50_70_55_58_ED, EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS

2019-12-08 Thread sgqy 
> #2

It is not a typo. The problem goes half a year.
I remember it was fine in 18.04 and 18.10.

Also, before headphone becomes white noise, the speaker does a very very
short time of "PA!" sound, like a bomb.


I will try the new kernel for days and reply. :)

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+subscriptions

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

[Kernel-packages] [Bug 1855487] Re: Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of 4.15.0-72-generic

2019-12-08 Thread Po-Hsu Lin 
Hello,
can you test the kernel here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798/comments/11

Thanks

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

** Changed in: linux-hwe (Ubuntu)
   Status: New => Incomplete

** No longer affects: linux-hwe (Ubuntu)

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

Title:
  Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When upgrading from kernel 4.15.0-70-generic to 4.15.0-72-generic, the
  touchpad and track point on the ThinkPad X1 Carbon 5th Gen stops
  working. There are no errors in the logs, the mouse cursor just does
  not move at all & clicks are not registered.

  From dmesg the touchpad is identified as:
  psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 
0xf002a3/0x940300/0x12e800/0x40, board id: 3289, fw id: 2492434
  rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: 
TM3289-002, fw id: 2492434

  The trackpoint:
  psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x04, buttons: 3/3

  Found on Linux Mint 18.2 - which uses the Ubuntu 16.04 repo for this
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855487/+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 1855584] UdevDb.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] ProcModules.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] WifiSyslog.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] ProcEnviron.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855542] Re: Touchpad not working

2019-12-08 Thread AaronMa 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798/comments/11

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

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installation "zsh-autosuggestions", following instructions on:
  https://github.com/zsh-users/zsh-
  autosuggestions/blob/master/INSTALL.md , my note touchpad stopped
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leandro2537 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 11:07:08 2019
  InstallationDate: Installed on 2018-12-06 (366 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80YH
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=d1ee713a-114d-4799-9071-37939c97549c ro i8042.reset quiet splash 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN29WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN29WW:bd09/30/2017:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80YH
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855542/+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 1855584] ProcInterrupts.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] RfKill.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] ProcCpuinfoMinimal.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Lspci.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Lsusb.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Dependencies.txt

2019-12-08 Thread sgqy 
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1855584/+attachment/5310919/+files/Dependencies.txt

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] IwConfig.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Re: [Hasee NH50_70_55_58_ED, EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS

2019-12-08 Thread sgqy 
apport information

** Tags added: apport-collected

** Description changed:

  This problem seems begin from ubuntu 19.04.
  
  Sometimes after login, headphone outputs white noise only, speaker does
  not work.
  
  Nothing can play music with the noise.
  
  The noise is impossible to stop except POWEROFF the PC.
  
  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.
  
  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)
  
  It seems pulseaudio killed the sound card...
  
  The problem appears randomly, I do not know how to reproduce. sorry...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu13
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aya1796 F pulseaudio
+  /dev/snd/controlC1:  aya1796 F pulseaudio
+ DistroRelease: Ubuntu 20.04
+ MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: pulseaudio 1:13.0-1ubuntu1
+ PackageArchitecture: amd64
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
+ ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
+ 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.3.0-24-generic N/A
+  linux-backports-modules-5.3.0-24-generic  N/A
+  linux-firmware1.184
+ Tags:  focal
+ Uname: Linux 5.3.0-24-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 11/16/2018
+ dmi.bios.vendor: INSYDE Corp.
+ dmi.bios.version: 1.07.05RHZX1
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: NH50_70_55_58_ED,EDQ
+ dmi.board.vendor: Notebook
+ dmi.board.version: Not Applicable
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Notebook
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
+ dmi.product.family: Not Applicable
+ dmi.product.name: NH50_70_55_58_ED,EDQ
+ dmi.product.sku: Not Applicable
+ dmi.product.version: Not Applicable
+ dmi.sys.vendor: HASEE Computer

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1855584/+attachment/5310916/+files/AlsaInfo.txt

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS,

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

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] CurrentDmesg.txt

2019-12-08 Thread sgqy 
apport information

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aya1796 F pulseaudio
   /dev/snd/controlC1:  aya1796 F pulseaudio
  DistroRelease: Ubuntu 20.04
  MachineType: HASEE Computer NH50_70_55_58_ED,EDQ
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855608] Status changed to Confirmed

2019-12-08 Thread Ubuntu Kernel Bot 
This change was made by a bot.

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

** Tags added: bionic

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

Title:
  Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on
  Intel Comet Lake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just received a new Dell XPS 13 7390 laptop. With factory
  preinstalled Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics
  was severely distorted. The display would constantly flicker with
  areas of the display staying black or showing patterns of square color
  blocks.

  Booting in recovery mode worked, though and I was able to install all
  updates for preinstalled 18.04 LTS with the OEM kernel. Problems in
  non-recovery mode persisted after installing all updates. I then
  updated to Ubuntu 19.04 and changed to "generic" linux kernel image
  without success: Problem persisted, only recovery mode was usable. I
  updated once more to 19.10 again without any success.

  From the perhaps related bug #1849947 I tried latest drm-tip kernel
  from

  https://kernel.ubuntu.com/~kernel-ppa/mainline/

  drm-tip kernel solves the issue for first boot, but after resuming
  from suspend, the same issues display issues occur.

  Kernel images I tried:
  - linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics 
output without "nomodeset"
  - linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output 
without "nomodeset"
  - linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output 
without "nomodeset"
  - linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted 
graphics output after resuming from suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.4.0-994-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 18:51:15 2019
  DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2019-11-25 (13 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic 
root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+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 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

2019-12-08 Thread AaronMa 
Could you test the following kernel ppa please:

sudo add-apt-repository ppa:mapengyu/bionic-oem
sudo apt-get update

sudo apt install linux-image-unsigned-4.15.0-73-generic linux-
modules-4.15.0-73-generic linux-modules-extra-4.15.0-73-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/1854798

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  SRU justification
  =
  [Impact]
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

  [Fix]
  After applied commit "Input: synaptics-rmi4 - avoid processing unknown
  IRQs",
  no irq response from touchpad.
  This commit is depended on commit:
  "Input: synaptics-rmi4 - convert irq distribution to irq_domain"

  [Test]
  Verified on hardware, tests results are good.

  [Regression Potential]
  Low.
  Fix bug that introduced by stable release update.

  2nd and 3rd patches are fixes for the 1st patch.
  These commits are already included by eoan kernel, so bionic 4.15 only.

  Original reports
  ===

  environment:
  Dell Laptop XPS-9333
  Device:
  # xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  id=9[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Ultrathin Touch Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]

  # xinput --list-props 12
  Device 'Synaptics s3203':
   Device Enabled (142):1
   Coordinate Transformation Matrix (144):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (270):  1
   Device Accel Constant Deceleration (271):2.50
   Device Accel Adaptive Deceleration (272):1.00
   Device Accel Velocity Scaling (273): 9.712231
   Synaptics Edges (304):   162, 3908, 133, 2339
   Synaptics Finger (305):  25, 30, 0
   Synaptics Tap Time (306):180
   Synaptics Tap Move (307):209
   Synaptics Tap Durations (308):   180, 180, 100
   Synaptics ClickPad (309):1
   Synaptics Middle Button Timeout (310):   0
   Synaptics Two-Finger Pressure (311): 282
   Synaptics Two-Finger Width (312):7
   Synaptics Scrolling Distance (313):  -95, 95
   Synaptics Edge Scrolling (314):  0, 0, 0
   Synaptics Two-Finger Scrolling (315):1, 1
   Synaptics Move Speed (316):  1.00, 1.75, 0.042008, 0.00
   Synaptics Off (317): 0
   Synaptics Locked Drags (318):0
   Synaptics Locked Drags Timeout (319):5000
   Synaptics Tap Action (320):  0, 0, 0, 0, 1, 3, 2
   Synaptics Click Action (321):1, 3, 2
   Synaptics Circular Scrolling (322):  0
   Synaptics Circular Scrolling Distance (323): 0.10
   Synaptics Circular Scrolling Trigger (324):  0
   Synaptics Circular Pad (325):0
   Synaptics Palm Detection (326):  1
   Synaptics Palm Dimensions (327): 10, 200
   Synaptics Coasting Speed (328):  20.00, 50.00
   Synaptics Pressure Motion (329): 30, 160
   Synaptics Pressure Motion Factor (330):  1.00, 1.00
   Synaptics Resolution Detect (331):   1
   Synaptics Grab Event Device (332):   0
   Synaptics Gestures (333):1
   Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0
   Synaptics Pad Resolution (335):  42, 42
   Synaptics Area (336):0, 0, 0, 0
   Synaptics Soft Button Areas (337):   0, 0, 0, 0, 0, 0, 0, 0
   Synaptics Noise Cancellation (338):  23, 23
   Device Product ID (262): 1739, 10036
   Device Node (263):   "/dev/input/event5"

  # lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
  00:03.0 Audio device:

[Kernel-packages] [Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake

2019-12-08 Thread Daniel van Vugt 
** Summary changed:

- Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10
+ Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel 
Comet Lake

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on
  Intel Comet Lake

Status in linux package in Ubuntu:
  New

Bug description:
  I just received a new Dell XPS 13 7390 laptop. With factory
  preinstalled Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics
  was severely distorted. The display would constantly flicker with
  areas of the display staying black or showing patterns of square color
  blocks.

  Booting in recovery mode worked, though and I was able to install all
  updates for preinstalled 18.04 LTS with the OEM kernel. Problems in
  non-recovery mode persisted after installing all updates. I then
  updated to Ubuntu 19.04 and changed to "generic" linux kernel image
  without success: Problem persisted, only recovery mode was usable. I
  updated once more to 19.10 again without any success.

  From the perhaps related bug #1849947 I tried latest drm-tip kernel
  from

  https://kernel.ubuntu.com/~kernel-ppa/mainline/

  drm-tip kernel solves the issue for first boot, but after resuming
  from suspend, the same issues display issues occur.

  Kernel images I tried:
  - linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics 
output without "nomodeset"
  - linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output 
without "nomodeset"
  - linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output 
without "nomodeset"
  - linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted 
graphics output after resuming from suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.4.0-994-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 18:51:15 2019
  DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2019-11-25 (13 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic 
root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+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 1855584] Missing required logs.

2019-12-08 Thread Ubuntu Kernel Bot 
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1855584

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855521] Missing required logs.

2019-12-08 Thread Ubuntu Kernel Bot 
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1855521

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855584] Re: [Hasee NH50_70_55_58_ED, EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS

2019-12-08 Thread Daniel van Vugt 
Also, please try a newer kernel like:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.2/

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Re: [Hasee NH50_70_55_58_ED, EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS

2019-12-08 Thread Daniel van Vugt 
You say the problem began around 19.04 and you are now running 20.04. Is
that correct or a typo?

** Summary changed:

- pulseaudio: sometimes generate eternal white noise even reboot to Windows OS
+ [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white 
noise even reboot to Windows OS

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

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

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

Title:
  [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal
  white noise even reboot to Windows OS

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This problem seems begin from ubuntu 19.04.

  Sometimes after login, headphone outputs white noise only, speaker
  does not work.

  Nothing can play music with the noise.

  The noise is impossible to stop except POWEROFF the PC.

  Rebooting cannot stop it, the noise keeps even reboot into Windows OS.
  In Windows OS, headphone still white noise, after unplugging headphone, the 
speaker does not work, too.

  
  It works fine in Windows OS.
  If I remove pulseaudio, only use ALSA. It also works stable.
  (But now... firefox do not support ALSA, chromium-snap do not support ALSA 
too...)

  It seems pulseaudio killed the sound card...

  The problem appears randomly, I do not know how to reproduce. sorry...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aya5434 F pulseaudio
   /dev/snd/controlC0:  aya5434 F pulseaudio
  Date: Sun Dec  8 19:51:02 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RHZX1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH50_70_55_58_ED,EDQ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NH50_70_55_58_ED,EDQ
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855608] [NEW] Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake

2019-12-08 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

I just received a new Dell XPS 13 7390 laptop. With factory preinstalled
Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics was severely
distorted. The display would constantly flicker with areas of the
display staying black or showing patterns of square color blocks.

Booting in recovery mode worked, though and I was able to install all
updates for preinstalled 18.04 LTS with the OEM kernel. Problems in non-
recovery mode persisted after installing all updates. I then updated to
Ubuntu 19.04 and changed to "generic" linux kernel image without
success: Problem persisted, only recovery mode was usable. I updated
once more to 19.10 again without any success.

>From the perhaps related bug #1849947 I tried latest drm-tip kernel from

https://kernel.ubuntu.com/~kernel-ppa/mainline/

drm-tip kernel solves the issue for first boot, but after resuming from
suspend, the same issues display issues occur.

Kernel images I tried:
- linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics output 
without "nomodeset"
- linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output 
without "nomodeset"
- linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output 
without "nomodeset"
- linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted graphics 
output after resuming from suspend

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
Uname: Linux 5.4.0-994-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec  8 18:51:15 2019
DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0962]
InstallationDate: Installed on 2019-11-25 (13 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
MachineType: Dell Inc. XPS 13 7390
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic 
root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago)
dmi.bios.date: 11/08/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.1
dmi.board.name: 0G2D0W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption eoan third-party-packages ubuntu
-- 
Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet 
Lake
https://bugs.launchpad.net/bugs/1855608
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1855521] Re: [Dell Inspiron 5490] Internal microphone not detected

2019-12-08 Thread Daniel van Vugt 
** Summary changed:

- Internal microphone not detected
+ [Dell Inspiron 5490] Internal microphone not detected

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

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1852001] Status changed to Confirmed

2019-12-08 Thread Ubuntu Kernel Bot 
This change was made by a bot.

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

** Tags added: bionic

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

Title:
  KDE GUI freeze on high disk IO, but disabling swap fixes it

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've got massive problems with GUI on my PC.

  The attached logs are from the following setting: 
  - high disk load (f3write)
  - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan)
  - no swap available

  These are the parameters (disk load, kernel, swap) I am fiddling with
  to find out the cause, see below.

  In general 
  - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo
  - more likely to happen with high disk or CPU load, but not necessarily.
  - less likely with the 4.x kernel mentioned above. 

  I just installed the following kernels from kernel-ppa:
  5.3.10-050310-generic 
  5.4.0-050400rc6-generic
  5.4.0-997-generic (drm-intel-next)
  Now I am waiting for the freeze to occur again. 

  The problem started about half a year ago. 
  There have been three changes that happened at the time and could be the cause
  - switch to kernel 5.x
  - update to Ubuntu 19.4
  - swapped motherboard, CPU and RAM. 

  The hassle started with the following scenario, repeated often: 
  - high disk load
  - PC becomes laggy
  - soon dies/freezes

  The longer I waited, the deeper the lockdown went. but I don't know the exact 
details. 
  The first cause I found was kswapd running amok and take the system with it. 
Workaround: add swap space. 

  Now the problem shifted: Whenever I got high disk load (eg dd 100 GB
  of data) the kernel swaps likle crazy and makes the GUI first lag soon
  freeze. but no excessive CPU load any more, as kswapd does not go
  crazy.

  Again I found a workaround: 
  the above mentioned 4.x kernel. In this case the GUI lags as expected from a 
heavily swapping system. nothing more. 
  but still sometimes the GUI simply freezes (the error reported at the top)

  Another workaround is to completely remove swap. Let's see what
  happens, if kswapd goes amok again.

  I am not sure as how these problems are related.

  I did extensive hardware check like
  - memtest86 newest version, no "may be vulnerable to high frequency row 
hammering"
  - smart

  do you suggest any burn in test suites?

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18
  Uname: Linux 4.15.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Nov 10 15:55:14 2019
  DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb 
http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled 
on upgrade to eoan' was disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 
(Desktop 9 Series) [1462:7b16]
  InstallationDate: Installed on 2017-12-16 (693 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B16
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem 
root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago)
  dmi.bios.date: 08/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: Default string
  dmi.board.name: B360 GAMING PRO CARBON (MS-7B16)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B16
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core:

[Kernel-packages] [Bug 1854531] Re: [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf

2019-12-08 Thread Daniel van Vugt 
I feel this is going to be closely related to bug 1775881. Maybe if it's
a kernel bug then it can affect both Wayland and Xorg. Just one more
often than the other.

** Summary changed:

- [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled 
to false in gdm3's custom.conf
+ [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled 
to false in gdm3's custom.conf (AMD Caicos)

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

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

Title:
  [radeon] Ubuntu fails to run Xorg the first reboot after I set
  WaylandEnabled to false in gdm3's custom.conf (AMD Caicos)

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Whenever I set Wayland to false in Gnome Display Manager's custom.conf
  file and then reboot, I still see the same scrambled graphics on the
  machine as if it were using Wayland. Rebooting the machine a SECOND
  time resolves the issue. However, I should not have to reboot twice
  for the new setting to take effect.

  Steps to Reproduce:
  1. When the machine boots up with scrambled graphics, press Control+Alt+F3
  2. Log into the machine using the tty session and run "sudo editor 
/etc/gdm3/custom.conf
  3. Set Wayland to false and reboot
  4. Notice after reboot the same scrambled graphics appear until the user 
reboots again

  Expected Results:
  Gnome Display Manager runs xorg and xorg shows the correct graphics for the 
machine.

  Actual Results:
  Graphics are scrambled and settings do not appear to take effect until next 
reboot.

  This issue occurred right before 12:45 PM, EDT, on November 29, 2019.

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  gdm3:
Installed: 3.28.3-0ubuntu18.04.4
Candidate: 3.28.3-0ubuntu18.04.4
Version table:
   *** 3.28.3-0ubuntu18.04.4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 29 12:39:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease:

[Kernel-packages] [Bug 1854531] Re: [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf (AMD Caicos)

2019-12-08 Thread Daniel van Vugt 
Please try installing a newer kernel like
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.2/


** Changed in: gdm3 (Ubuntu)
   Status: New => Incomplete

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  [radeon] Ubuntu fails to run Xorg the first reboot after I set
  WaylandEnabled to false in gdm3's custom.conf (AMD Caicos)

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Whenever I set Wayland to false in Gnome Display Manager's custom.conf
  file and then reboot, I still see the same scrambled graphics on the
  machine as if it were using Wayland. Rebooting the machine a SECOND
  time resolves the issue. However, I should not have to reboot twice
  for the new setting to take effect.

  Steps to Reproduce:
  1. When the machine boots up with scrambled graphics, press Control+Alt+F3
  2. Log into the machine using the tty session and run "sudo editor 
/etc/gdm3/custom.conf
  3. Set Wayland to false and reboot
  4. Notice after reboot the same scrambled graphics appear until the user 
reboots again

  Expected Results:
  Gnome Display Manager runs xorg and xorg shows the correct graphics for the 
machine.

  Actual Results:
  Graphics are scrambled and settings do not appear to take effect until next 
reboot.

  This issue occurred right before 12:45 PM, EDT, on November 29, 2019.

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  gdm3:
Installed: 3.28.3-0ubuntu18.04.4
Candidate: 3.28.3-0ubuntu18.04.4
Version table:
   *** 3.28.3-0ubuntu18.04.4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 29 12:39:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Package: xorg-server
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature:

[Kernel-packages] [Bug 1176977] Re: XFS instability on armhf under load

2019-12-08 Thread Henrik Nordvik 
I'm getting a very similar error on 18.04.3 arm, except I didn't use
swift, I used GlusterFS and copied files to it.

Linux odroid 4.14.150-170 #1 SMP PREEMPT Tue Oct 22 12:31:29 -03 2019
armv7l armv7l armv7l GNU/Linux

[Sun Dec  8 04:21:13 2019] vmap allocation for size 1048576 failed: use 
vmalloc= to increase size
[Sun Dec  8 04:21:13 2019] vmap allocation for size 1048576 failed: use 
vmalloc= to increase size
[Sun Dec  8 04:21:13 2019] vmap allocation for size 1048576 failed: use 
vmalloc= to increase size
[Sun Dec  8 04:21:13 2019] XFS (dm-4): xfs_buf_get_map: failed to map pagesn
[Sun Dec  8 04:21:13 2019] XFS (dm-4): Internal error xfs_trans_cancel at line 
1005 of file fs/xfs/xfs_trans.c.  Caller xfs_link+0x1a8/0x328 [xfs]
[Sun Dec  8 04:21:13 2019] CPU: 5 PID: 23936 Comm: glfs_iotwr008 Not tainted 
4.14.150-170 #1
[Sun Dec  8 04:21:13 2019] Hardware name: ODROID-XU4
[Sun Dec  8 04:21:13 2019] [] (unwind_backtrace) from [] 
(show_stack+0x10/0x14)
[Sun Dec  8 04:21:13 2019] [] (show_stack) from [] 
(dump_stack+0x88/0x9c)
[Sun Dec  8 04:21:13 2019] [] (dump_stack) from [] 
(xfs_trans_cancel+0xd8/0xf4 [xfs])
[Sun Dec  8 04:21:13 2019] [] (xfs_trans_cancel [xfs]) from 
[] (xfs_link+0x1a8/0x328 [xfs])
[Sun Dec  8 04:21:13 2019] [] (xfs_link [xfs]) from [] 
(xfs_vn_link+0x44/0x7c [xfs])
[Sun Dec  8 04:21:13 2019] [] (xfs_vn_link [xfs]) from [] 
(vfs_link+0x218/0x340)
[Sun Dec  8 04:21:13 2019] [] (vfs_link) from [] 
(SyS_linkat+0x1d0/0x2b8)
[Sun Dec  8 04:21:13 2019] [] (SyS_linkat) from [] 
(ret_fast_syscall+0x0/0x54)
[Sun Dec  8 04:21:13 2019] XFS (dm-4): xfs_do_force_shutdown(0x8) called from 
line 1006 of file fs/xfs/xfs_trans.c.  Return address = 0xbf33cff4
[Sun Dec  8 04:21:13 2019] XFS (dm-4): Corruption of in-memory data detected.  
Shutting down filesystem
[Sun Dec  8 04:21:13 2019] XFS (dm-4): Please umount the filesystem and rectify 
the problem(s)

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

Title:
  XFS instability on armhf under load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've observed issues with XFS on ARM hardware on both 12.04 and
  12.10. Details from ubuntu-bug are attached from a 12.10 installation.
  The specific load in this case is setting up and running a single node
  install of Swift and then exercising it with swift-bench for a
  prolonged period. After a few hours you get the following:

  [361819.562519] SGI XFS with ACLs, security attributes, large block/inode 
numbers, no debug enabled
  [361819.566196] XFS (loop0): Mounting Filesystem
  [361819.617186] XFS (loop0): Ending clean mount
  [372224.630644] alloc_vmap_area: 18 callbacks suppressed
  [372224.630656] vmap allocation for size 2097152 failed: use vmalloc= 
to increase size.
  [372224.630687] vmap allocation for size 2097152 failed: use vmalloc= 
to increase size.
  [372224.630716] vmap allocation for size 2097152 failed: use vmalloc= 
to increase size.
  [372224.630730] XFS (loop0): xfs_buf_get: failed to map pages
  [372224.630730]
  [372224.630745] XFS (loop0): Internal error xfs_trans_cancel at line 1466 of 
file /build/buildd/linux-3.5.0/fs/xfs/xfs_trans.c.  Caller 0xbf0465e0
  [372224.630745]
  [372224.645280] [] (unwind_backtrace+0x0/0x104) from [] 
(dump_stack+0x20/0x24)
  [372224.645475] [] (dump_stack+0x20/0x24) from [] 
(xfs_error_report+0x60/0x6c [xfs])
  [372224.645800] [] (xfs_error_report+0x60/0x6c [xfs]) from 
[] (xfs_trans_cancel+0xfc/0x11c [xfs])
  [372224.646117] [] (xfs_trans_cancel+0xfc/0x11c [xfs]) from 
[] (xfs_create+0x228/0x558 [xfs])
  [372224.646387] [] (xfs_create+0x228/0x558 [xfs]) from [] 
(xfs_vn_mknod+0x9c/0x180 [xfs])
  [372224.646648] [] (xfs_vn_mknod+0x9c/0x180 [xfs]) from 
[] (xfs_vn_create+0x1c/0x20 [xfs])
  [372224.646791] [] (xfs_vn_create+0x1c/0x20 [xfs]) from 
[] (vfs_create+0xb4/0x120)
  [372224.646805] [] (vfs_create+0xb4/0x120) from [] 
(do_last+0x860/0x9bc)
  [372224.646818] [] (do_last+0x860/0x9bc) from [] 
(path_openat+0xcc/0x428)
  [372224.646829] [] (path_openat+0xcc/0x428) from [] 
(do_filp_open+0x3c/0x90)
  [372224.646844] [] (do_filp_open+0x3c/0x90) from [] 
(do_sys_open+0xfc/0x1d0)
  [372224.646855] [] (do_sys_open+0xfc/0x1d0) from [] 
(sys_open+0x2c/0x30)
  [372224.646868] [] (sys_open+0x2c/0x30) from [] 
(ret_fast_syscall+0x0/0x30)
  [372224.646881] XFS (loop0): xfs_do_force_shutdown(0x8) called from line 1467 
of file /build/buildd/linux-3.5.0/fs/xfs/xfs_trans.c.  Return address = 
0xbf08640c
  [372224.647010] XFS (loop0): Corruption of in-memory data detected.  Shutting 
down filesystem
  [372224.655289] XFS (loop0): Please umount the filesystem and rectify the 
problem(s)
  [372227.273367] XFS (loop0): xfs_log_force: error 5 returned.

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

-- 
Mailing list:

[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO, but disabling swap fixes it

2019-12-08 Thread Daniel van Vugt 
Thanks. This looks like the cause of high disk IO at least:

jan   3400  0.0  0.0   2600   676 pts/8SDez07   0:00 /bin/sh 
/usr/bin/bcompare RAID/Incoming/NAS-DATEN/ jan/NAS-DATEN/
jan   3412 70.7 11.3 2759972 1851804 pts/8 Sl   Dez07 900:13 
/usr/bin/bcompare RAID/Incoming/NAS-DATEN/ jan/NAS-DATEN/

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

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

Title:
  KDE GUI freeze on high disk IO, but disabling swap fixes it

Status in linux package in Ubuntu:
  New

Bug description:
  I've got massive problems with GUI on my PC.

  The attached logs are from the following setting: 
  - high disk load (f3write)
  - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan)
  - no swap available

  These are the parameters (disk load, kernel, swap) I am fiddling with
  to find out the cause, see below.

  In general 
  - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo
  - more likely to happen with high disk or CPU load, but not necessarily.
  - less likely with the 4.x kernel mentioned above. 

  I just installed the following kernels from kernel-ppa:
  5.3.10-050310-generic 
  5.4.0-050400rc6-generic
  5.4.0-997-generic (drm-intel-next)
  Now I am waiting for the freeze to occur again. 

  The problem started about half a year ago. 
  There have been three changes that happened at the time and could be the cause
  - switch to kernel 5.x
  - update to Ubuntu 19.4
  - swapped motherboard, CPU and RAM. 

  The hassle started with the following scenario, repeated often: 
  - high disk load
  - PC becomes laggy
  - soon dies/freezes

  The longer I waited, the deeper the lockdown went. but I don't know the exact 
details. 
  The first cause I found was kswapd running amok and take the system with it. 
Workaround: add swap space. 

  Now the problem shifted: Whenever I got high disk load (eg dd 100 GB
  of data) the kernel swaps likle crazy and makes the GUI first lag soon
  freeze. but no excessive CPU load any more, as kswapd does not go
  crazy.

  Again I found a workaround: 
  the above mentioned 4.x kernel. In this case the GUI lags as expected from a 
heavily swapping system. nothing more. 
  but still sometimes the GUI simply freezes (the error reported at the top)

  Another workaround is to completely remove swap. Let's see what
  happens, if kswapd goes amok again.

  I am not sure as how these problems are related.

  I did extensive hardware check like
  - memtest86 newest version, no "may be vulnerable to high frequency row 
hammering"
  - smart

  do you suggest any burn in test suites?

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18
  Uname: Linux 4.15.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Nov 10 15:55:14 2019
  DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb 
http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled 
on upgrade to eoan' was disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 
(Desktop 9 Series) [1462:7b16]
  InstallationDate: Installed on 2017-12-16 (693 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B16
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem 
root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago)
  dmi.bios.date: 08/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: Default string
  dmi.board.name: B360 GAMING PRO CARBON (MS-7B16)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B16
  dmi.product.version: 1.0
  dmi.sys.vendor:

[Kernel-packages] [Bug 1775881] Status changed to Confirmed

2019-12-08 Thread Ubuntu Kernel Bot 
This change was made by a bot.

** 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/1775881

Title:
  [radeon] Wayland sessions including the login screen are just static
  noise on AMD Caicos

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  Ubuntu Version 18.04 LTS

  gdm3:
  Installed: 3.28.0-0ubuntu1 500

  Package name: /etc/gdm3

  Whenever I boot Ubuntu following installation from the official
  install ISO, the boot screen appears, but the login manager appears as
  static, scrambled graphics, making me unable to login without opening
  the VT and installing lightdm and switching to that login manager.

  Expected Results:
  Login manager appears with login field, background, and menu while I am able 
to find, click, and enter information into the login text fields.

  Actual Results:
  Scrambled noise appeared on my screen and I am unable to leave without 
force-shutting down my Gateway PC, or opening a VT and installing lightdm, 
rebooting afterwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Jun  8 11:41:23 2018
  InstallationDate: Installed on 2018-06-07 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Tags:  bionic
  Uname: Linux 5.0.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-12-08T13:34:15.689391

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+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 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos

2019-12-08 Thread Daniel van Vugt 
** Summary changed:

- [radeon] Wayland sessions including the login screen are just static noise
+ [radeon] Wayland sessions including the login screen are just static noise on 
AMD Caicos

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

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

Title:
  [radeon] Wayland sessions including the login screen are just static
  noise on AMD Caicos

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  Ubuntu Version 18.04 LTS

  gdm3:
  Installed: 3.28.0-0ubuntu1 500

  Package name: /etc/gdm3

  Whenever I boot Ubuntu following installation from the official
  install ISO, the boot screen appears, but the login manager appears as
  static, scrambled graphics, making me unable to login without opening
  the VT and installing lightdm and switching to that login manager.

  Expected Results:
  Login manager appears with login field, background, and menu while I am able 
to find, click, and enter information into the login text fields.

  Actual Results:
  Scrambled noise appeared on my screen and I am unable to leave without 
force-shutting down my Gateway PC, or opening a VT and installing lightdm, 
rebooting afterwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Jun  8 11:41:23 2018
  InstallationDate: Installed on 2018-06-07 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Tags:  bionic
  Uname: Linux 5.0.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2019-12-08T13:34:15.689391

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+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 1854114] Re: My 4K display goes black screen when I updated my NVIDIA driver from 340 to 435

2019-12-08 Thread Amin Sadeghi 
In case it helps debugging, I found a workaround: I enabled legacy mode
in motherboard bios, and it got fixed.

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

Title:
  My 4K display goes black screen when I updated my NVIDIA driver from
  340 to 435

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

Bug description:
  Here's what happened: I have Ubuntu 19.10 installed + NVIDIA driver
  340 + 4K screen. Everything works file. I upgraded my NVIDIA driver to
  435 and then everything is still fine until the login screen. When I
  enter my password, the screen goes black. So, I connected my old HD
  monitor, rebooted, and it worked! Funny thing is that, when I'm logged
  in the OS, if I reconnect my 4K monitor, it works! But if I restart my
  system, the problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 26 19:21:07 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-23-generic, x86_64: installed
   openrazer-driver, 2.6.0, 5.3.0-22-generic, x86_64: installed
   openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097]
  InstallationDate: Installed on 2019-10-18 (39 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Precision Tower 5810
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=ab778d32-5ce1-4c38-a14e-2024d96eb5d3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A32
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA32:bd09/24/2019:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.product.sku: 0617
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1854114/+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 1855619] Status changed to Confirmed

2019-12-08 Thread Ubuntu Kernel Bot 
This change was made by a bot.

** 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/1855619

Title:
  Touchpad not working Eoan

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop is an Acer Aspire F5-571. It doesn't detect my touchpad when
  I decided to install Ubuntu 19.10. I have disabled advanced functions
  of the touchpad (because I think it had issues with I2C).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barrosorbf   1326 F pulseaudio
   /dev/snd/controlC0:  barrosorbf   1326 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 11:10:38 2019
  InstallationDate: Installed on 2019-12-08 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire F5-571
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=53242bb9-2591-4fba-b598-04911527760d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireF5-571:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire F5-571
  dmi.product.sku: Aspire F5-571_098A_1_37
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855619/+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 1855619] [NEW] Touchpad not working Eoan

2019-12-08 Thread Roberto Barroso Fernández 
Public bug reported:

My laptop is an Acer Aspire F5-571. It doesn't detect my touchpad when I
decided to install Ubuntu 19.10. I have disabled advanced functions of
the touchpad (because I think it had issues with I2C).

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-24-generic 5.3.0-24.26
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  barrosorbf   1326 F pulseaudio
 /dev/snd/controlC0:  barrosorbf   1326 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec  8 11:10:38 2019
InstallationDate: Installed on 2019-12-08 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Acer Aspire F5-571
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=53242bb9-2591-4fba-b598-04911527760d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-24-generic N/A
 linux-backports-modules-5.3.0-24-generic  N/A
 linux-firmware1.183
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/16/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.37
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: ZORO_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireF5-571:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: BDW
dmi.product.name: Aspire F5-571
dmi.product.sku: Aspire F5-571_098A_1_37
dmi.product.version: V3.72
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug eoan

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1855619/+attachment/5310862/+files/devices

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

Title:
  Touchpad not working Eoan

Status in linux package in Ubuntu:
  New

Bug description:
  My laptop is an Acer Aspire F5-571. It doesn't detect my touchpad when
  I decided to install Ubuntu 19.10. I have disabled advanced functions
  of the touchpad (because I think it had issues with I2C).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barrosorbf   1326 F pulseaudio
   /dev/snd/controlC0:  barrosorbf   1326 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 11:10:38 2019
  InstallationDate: Installed on 2019-12-08 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire F5-571
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=53242bb9-2591-4fba-b598-04911527760d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireF5-571:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire F5-571
  dmi.product.sku: Aspire F5-571_098A_1_37
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855619/+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 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

2019-12-08 Thread Erik Davidson 
I'm also seeing this issue on a fresh install of Ubuntu 19.10 with a
Razer Core X Chroma and a Lenovo X1 Extreme Gen2. I was seeing it on a
fully updated Arch Linux install and installed Ubuntu in hopes it would
fix the issue. Here's some info from my current install. Let me know if
you need anything else!

uname:
Linux fate 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

I've attached all the same info you were asking for earlier.

** Attachment added: "egpu_debug.txt"
   
https://bugs.launchpad.net/ubuntu/artful/+source/linux/+bug/1749961/+attachment/5310852/+files/egpu_debug.txt

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+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 1814481] Re: bluetooth keyboard not working

2019-12-08 Thread Yaroslav Kolodiy 
Same problem with Keychrom K2 ubuntu 19.10
but when I'm in the loggin screen it works fine...

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

Title:
  bluetooth keyboard not working

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Incomplete

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency 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
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

[Kernel-packages] [Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

2019-12-08 Thread xoristzatziki 
same problem here (full updates)
uname -a 
Linux  4.15.0-72-generic #81~16.04.1-Ubuntu SMP Tue Nov 26 16:34:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

same problem here (full updates)

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

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

Status in xen:
  Unknown
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency

  [...]

  update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.159
  Uname: Linux 4.8.0-040800rc1-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  Date: Mon Aug  8 17:50:38 2016
  Dependencies:
   
  InstallationDate: Installed on 2015-07-26 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xen/+bug/1611124/+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 1855264] Re: Kernel upgrade 5.3.0-23 to -24 results in panic

2019-12-08 Thread Rob Peters 
A clean install fixed the problem.

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

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

Title:
  Kernel upgrade 5.3.0-23 to -24 results in panic

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Dell XPS 15 7590 2019 version.
  Apt linux kernel update from 5.3.0-23 to 5.3-0-24 and boot failed, kernel 
panic.
  Attached file with booting with 5.3.0-24 debug display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855264/+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 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

2019-12-08 Thread Philip Parry 
I have the same problem; Lenovo Yoga 3 11, Synaptics TM2714-002,
touchpad not working after update to kernel 4.15.0-72-generic, reboot
with 4.15.0-70 and it works fine.

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

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  SRU justification
  =
  [Impact]
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

  [Fix]
  After applied commit "Input: synaptics-rmi4 - avoid processing unknown
  IRQs",
  no irq response from touchpad.
  This commit is depended on commit:
  "Input: synaptics-rmi4 - convert irq distribution to irq_domain"

  [Test]
  Verified on hardware, tests results are good.

  [Regression Potential]
  Low.
  Fix bug that introduced by stable release update.

  2nd and 3rd patches are fixes for the 1st patch.
  These commits are already included by eoan kernel, so bionic 4.15 only.

  Original reports
  ===

  environment:
  Dell Laptop XPS-9333
  Device:
  # xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  id=9[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Ultrathin Touch Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]

  # xinput --list-props 12
  Device 'Synaptics s3203':
   Device Enabled (142):1
   Coordinate Transformation Matrix (144):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (270):  1
   Device Accel Constant Deceleration (271):2.50
   Device Accel Adaptive Deceleration (272):1.00
   Device Accel Velocity Scaling (273): 9.712231
   Synaptics Edges (304):   162, 3908, 133, 2339
   Synaptics Finger (305):  25, 30, 0
   Synaptics Tap Time (306):180
   Synaptics Tap Move (307):209
   Synaptics Tap Durations (308):   180, 180, 100
   Synaptics ClickPad (309):1
   Synaptics Middle Button Timeout (310):   0
   Synaptics Two-Finger Pressure (311): 282
   Synaptics Two-Finger Width (312):7
   Synaptics Scrolling Distance (313):  -95, 95
   Synaptics Edge Scrolling (314):  0, 0, 0
   Synaptics Two-Finger Scrolling (315):1, 1
   Synaptics Move Speed (316):  1.00, 1.75, 0.042008, 0.00
   Synaptics Off (317): 0
   Synaptics Locked Drags (318):0
   Synaptics Locked Drags Timeout (319):5000
   Synaptics Tap Action (320):  0, 0, 0, 0, 1, 3, 2
   Synaptics Click Action (321):1, 3, 2
   Synaptics Circular Scrolling (322):  0
   Synaptics Circular Scrolling Distance (323): 0.10
   Synaptics Circular Scrolling Trigger (324):  0
   Synaptics Circular Pad (325):0
   Synaptics Palm Detection (326):  1
   Synaptics Palm Dimensions (327): 10, 200
   Synaptics Coasting Speed (328):  20.00, 50.00
   Synaptics Pressure Motion (329): 30, 160
   Synaptics Pressure Motion Factor (330):  1.00, 1.00
   Synaptics Resolution Detect (331):   1
   Synaptics Grab Event Device (332):   0
   Synaptics Gestures (333):1
   Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0
   Synaptics Pad Resolution (335):  42, 42
   Synaptics Area (336):0, 0, 0, 0
   Synaptics Soft Button Areas (337):   0, 0, 0, 0, 0, 0, 0, 0
   Synaptics Noise Cancellation (338):  23, 23
   Device Product ID (262): 1739, 10036
   Device Node (263):   "/dev/input/event5"

  # lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
09)
  00:14.0 USB

[Kernel-packages] [Bug 1855487] Re: Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of 4.15.0-72-generic

2019-12-08 Thread Albert Pool 
** Attachment added: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1855487/+attachment/5310755/+files/Lspci.txt

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

Title:
  Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  When upgrading from kernel 4.15.0-70-generic to 4.15.0-72-generic, the
  touchpad and track point on the ThinkPad X1 Carbon 5th Gen stops
  working. There are no errors in the logs, the mouse cursor just does
  not move at all & clicks are not registered.

  From dmesg the touchpad is identified as:
  psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 
0xf002a3/0x940300/0x12e800/0x40, board id: 3289, fw id: 2492434
  rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: 
TM3289-002, fw id: 2492434

  The trackpoint:
  psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x04, buttons: 3/3

  Found on Linux Mint 18.2 - which uses the Ubuntu 16.04 repo for this
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855487/+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 1855487] Re: Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of 4.15.0-72-generic

2019-12-08 Thread Albert Pool 
** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1855487/+attachment/5310754/+files/CurrentDmesg.txt

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

Title:
  Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  When upgrading from kernel 4.15.0-70-generic to 4.15.0-72-generic, the
  touchpad and track point on the ThinkPad X1 Carbon 5th Gen stops
  working. There are no errors in the logs, the mouse cursor just does
  not move at all & clicks are not registered.

  From dmesg the touchpad is identified as:
  psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 
0xf002a3/0x940300/0x12e800/0x40, board id: 3289, fw id: 2492434
  rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: 
TM3289-002, fw id: 2492434

  The trackpoint:
  psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x04, buttons: 3/3

  Found on Linux Mint 18.2 - which uses the Ubuntu 16.04 repo for this
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855487/+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 1855487] Re: Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of 4.15.0-72-generic

2019-12-08 Thread Albert Pool 
** Attachment added: "Syslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1855487/+attachment/5310760/+files/Syslog.txt

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

Title:
  Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  When upgrading from kernel 4.15.0-70-generic to 4.15.0-72-generic, the
  touchpad and track point on the ThinkPad X1 Carbon 5th Gen stops
  working. There are no errors in the logs, the mouse cursor just does
  not move at all & clicks are not registered.

  From dmesg the touchpad is identified as:
  psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 
0xf002a3/0x940300/0x12e800/0x40, board id: 3289, fw id: 2492434
  rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: 
TM3289-002, fw id: 2492434

  The trackpoint:
  psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x04, buttons: 3/3

  Found on Linux Mint 18.2 - which uses the Ubuntu 16.04 repo for this
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855487/+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 1855487] Re: Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of 4.15.0-72-generic

2019-12-08 Thread Albert Pool 
** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1855487/+attachment/5310758/+files/ProcModules.txt

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

Title:
  Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  When upgrading from kernel 4.15.0-70-generic to 4.15.0-72-generic, the
  touchpad and track point on the ThinkPad X1 Carbon 5th Gen stops
  working. There are no errors in the logs, the mouse cursor just does
  not move at all & clicks are not registered.

  From dmesg the touchpad is identified as:
  psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 
0xf002a3/0x940300/0x12e800/0x40, board id: 3289, fw id: 2492434
  rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: 
TM3289-002, fw id: 2492434

  The trackpoint:
  psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x04, buttons: 3/3

  Found on Linux Mint 18.2 - which uses the Ubuntu 16.04 repo for this
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855487/+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 1855487] Re: Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of 4.15.0-72-generic

2019-12-08 Thread Albert Pool 
** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1855487/+attachment/5310756/+files/ProcCpuinfo.txt

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

Title:
  Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  When upgrading from kernel 4.15.0-70-generic to 4.15.0-72-generic, the
  touchpad and track point on the ThinkPad X1 Carbon 5th Gen stops
  working. There are no errors in the logs, the mouse cursor just does
  not move at all & clicks are not registered.

  From dmesg the touchpad is identified as:
  psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 
0xf002a3/0x940300/0x12e800/0x40, board id: 3289, fw id: 2492434
  rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: 
TM3289-002, fw id: 2492434

  The trackpoint:
  psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x04, buttons: 3/3

  Found on Linux Mint 18.2 - which uses the Ubuntu 16.04 repo for this
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855487/+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 1855487] Re: Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of 4.15.0-72-generic

2019-12-08 Thread Albert Pool 
I hope I've now attached all necessary log files, in the absence of a
working apport-collect.

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

Title:
  Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  When upgrading from kernel 4.15.0-70-generic to 4.15.0-72-generic, the
  touchpad and track point on the ThinkPad X1 Carbon 5th Gen stops
  working. There are no errors in the logs, the mouse cursor just does
  not move at all & clicks are not registered.

  From dmesg the touchpad is identified as:
  psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 
0xf002a3/0x940300/0x12e800/0x40, board id: 3289, fw id: 2492434
  rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: 
TM3289-002, fw id: 2492434

  The trackpoint:
  psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x04, buttons: 3/3

  Found on Linux Mint 18.2 - which uses the Ubuntu 16.04 repo for this
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855487/+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 1855487] Re: Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of 4.15.0-72-generic

2019-12-08 Thread Albert Pool 
** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1855487/+attachment/5310757/+files/ProcInterrupts.txt

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

Title:
  Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  When upgrading from kernel 4.15.0-70-generic to 4.15.0-72-generic, the
  touchpad and track point on the ThinkPad X1 Carbon 5th Gen stops
  working. There are no errors in the logs, the mouse cursor just does
  not move at all & clicks are not registered.

  From dmesg the touchpad is identified as:
  psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 
0xf002a3/0x940300/0x12e800/0x40, board id: 3289, fw id: 2492434
  rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: 
TM3289-002, fw id: 2492434

  The trackpoint:
  psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x04, buttons: 3/3

  Found on Linux Mint 18.2 - which uses the Ubuntu 16.04 repo for this
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855487/+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 1855487] Re: Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of 4.15.0-72-generic

2019-12-08 Thread Albert Pool 
** Attachment added: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1855487/+attachment/5310759/+files/UdevDb.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1855487

Title:
  Touchpad & trackpoint on Thinkpad X1 Carbon 5th gen broken as of
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  When upgrading from kernel 4.15.0-70-generic to 4.15.0-72-generic, the
  touchpad and track point on the ThinkPad X1 Carbon 5th Gen stops
  working. There are no errors in the logs, the mouse cursor just does
  not move at all & clicks are not registered.

  From dmesg the touchpad is identified as:
  psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 
0xf002a3/0x940300/0x12e800/0x40, board id: 3289, fw id: 2492434
  rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: 
TM3289-002, fw id: 2492434

  The trackpoint:
  psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x04, buttons: 3/3

  Found on Linux Mint 18.2 - which uses the Ubuntu 16.04 repo for this
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855487/+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 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files

2019-12-08 Thread Colin Ian King 
Tested with 5.3.0-25-generic #27-Ubuntu with the regression test and it
now works fine. Marking bug as verification-done for eoan

** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  remount of multilower moved pivoted-root overlayfs root, results in
  I/O errors on some modified files

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Bionic:
  In Progress
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  In Progress

Bug description:
  == SRU Justification Disco, Eoan, Focal ==

  Multiple squashfs filesystems with overlayfs cause file corruption issues
  when modifying zero sized files

  == Fix ==

  The current fix is pending in
  
https://github.com/amir73il/linux/commit/b2d4f0ea5af42e16e154254de99da064f3ac551a

  == Test case ==

  With an Ubuntu ISO on the cdrom drive, use:

  #!/bin/bash -x
  mkdir -p /cdrom
  mount -t iso9660 -o ro,noatime /dev/sr0 /cdrom
  sleep 1
  mkdir -p /cow
  mount -t tmpfs -o 'rw,noatime,mode=755' tmpfs /cow
  sleep 1
  mkdir -p /cow/upper
  mkdir -p /cow/work
  modprobe -q -b overlay
  sleep 1
  modprobe -q -b loop
  sleep 1
  dev=$(losetup -f)
  mkdir -p /filesystem.squashfs
  losetup $dev /cdrom/casper/filesystem.squashfs
  mount -t squashfs -o ro,noatime $dev /filesystem.squashfs
  sleep 1

  dev=$(losetup -f)
  mkdir -p /installer.squashfs
  losetup $dev /cdrom/casper/installer.squashfs
  mount -t squashfs -o ro,noatime $dev /installer.squashfs
  sleep 1

  mkdir -p /root-tmp
  mount -t overlay -o 
'upperdir=/cow/upper,lowerdir=/installer.squashfs:/filesystem.squashfs,workdir=/cow/work'
 /cow /root-tmp

  FILE=/root-tmp/etc/.pwd.lock

  echo foo > $FILE
  cat $FILE
  sync
  #
  # dropping caches or remounting causes the bug
  #
  echo 3 > /proc/sys/vm/drop_caches
  cat $FILE

  Without the fix the cat of the file will produce an error. With the
  the cat will work correctly.

  == Regression Potential ==

  There is an unhandled corner case:
  - two filesystems, A and B, both have null uuid
  - upper layer is on A
  - lower layer 1 is also on A
  - lower layer 2 is on B

  However, since this is an issue without the fix and will be addressed
  later with subsequent fixes once they are OK with upstream I think the
  risk is minimal considering nobody is complaining about these corner
  cases with the current broken overlayfs squashfs layering.

  ---

  1) Download focal subiquity pending image, or eoan release image
  2) boot, and press ESC and edit boot command line (F6 in bios, e in UEFI)
  3) After --- insert the following options

     break=top debug init=/bin/bash

  4) Continue boot (Enter in BIOS, ctrl+x in UEFI)
  5) in the initramfs execute:

  rm /scripts/casper-bottom/25adduser
  exit

  6) you will be dropped into pivoted root filesystem, before systemd is execed 
as pid one
  7) /run/initramfs/ will contain a debug log, showing how everything was 
mounted. Ie. cdrom mounted, squashfs losetup from there, then multilower 
overlay setup from them, moved to /root, and then pivot-root to /root done to 
finally end up as /. Underlying layers are moved into /cow for your convenience.

  8) At this point modifying zero-byte length files, that exist in the
  lowest layer, but not the middle one, in certain ways, will results in
  them to be corrupted, after / is remounted.

  9) Corruption examples

  (On both focal & eoan)

  cat /etc/.pwd.lock
  systemd-sysusers
  cat /etc/.pwd.lock
  mount -o remount /
  cat /etc/.pwd.lock
  overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000)
  cat: /etc/.pwd.lock: Input/output error

  (Only on eoan)

  cat /etc/machine-id
  systemd-machine-id-setup
  cat /etc/machine-id
  mount -o remount /
  cat /etc/machine-id
  overlayfs: invalid origin (etc/machine-id, ftype=8000, origin ftype=4000)
  cat: /etc/machine-id: Input/output error

  Lots of things break once machine-id and .pwd.lock are corrupted. I.e.
  unable to dhcp, connect to dbus, add/remove/change users or groups,
  etc.

  We were unable to recreate the issue outside of booting things with
  casper. Ie. statically on a regular host machine without pivot-root.
  But hopefully booting to a quite state with nothing running is
  sufficient to reproduce this.

  Instead of booting with `bebroken init=/bin/bash` you can boot with
  `bebroken systemd.mask=systemd-remount-fs.service` this will complete
  the boot, with /etc/machine-id & .pwd.lock modified, meaning that
  remount of / will cause IO errors on those files.

  Currently, we are shipping two hacks in casper's 25adduser script to
  "rm" the offending files, and

[Kernel-packages] [Bug 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)

2019-12-08 Thread Tad Marko 
Confirming that comment #23 also solved my problem on a B450 I Aorus Pro
Wifi ITX motherboard with Ryzen 5 3400G.

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

Title:
  [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen
  2500u (Raven Ridge)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  I have graphics artefacts: screan tearing, pieces of the previous window 
appear in the newly opened window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-08 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+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 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

2019-12-08 Thread Alberto Pianon 
It affects also my Lenovo Yoga 3 11 with touchpad Synaptics TM2714-002

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

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  SRU justification
  =
  [Impact]
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

  [Fix]
  After applied commit "Input: synaptics-rmi4 - avoid processing unknown
  IRQs",
  no irq response from touchpad.
  This commit is depended on commit:
  "Input: synaptics-rmi4 - convert irq distribution to irq_domain"

  [Test]
  Verified on hardware, tests results are good.

  [Regression Potential]
  Low.
  Fix bug that introduced by stable release update.

  2nd and 3rd patches are fixes for the 1st patch.
  These commits are already included by eoan kernel, so bionic 4.15 only.

  Original reports
  ===

  environment:
  Dell Laptop XPS-9333
  Device:
  # xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  id=9[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Ultrathin Touch Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]

  # xinput --list-props 12
  Device 'Synaptics s3203':
   Device Enabled (142):1
   Coordinate Transformation Matrix (144):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (270):  1
   Device Accel Constant Deceleration (271):2.50
   Device Accel Adaptive Deceleration (272):1.00
   Device Accel Velocity Scaling (273): 9.712231
   Synaptics Edges (304):   162, 3908, 133, 2339
   Synaptics Finger (305):  25, 30, 0
   Synaptics Tap Time (306):180
   Synaptics Tap Move (307):209
   Synaptics Tap Durations (308):   180, 180, 100
   Synaptics ClickPad (309):1
   Synaptics Middle Button Timeout (310):   0
   Synaptics Two-Finger Pressure (311): 282
   Synaptics Two-Finger Width (312):7
   Synaptics Scrolling Distance (313):  -95, 95
   Synaptics Edge Scrolling (314):  0, 0, 0
   Synaptics Two-Finger Scrolling (315):1, 1
   Synaptics Move Speed (316):  1.00, 1.75, 0.042008, 0.00
   Synaptics Off (317): 0
   Synaptics Locked Drags (318):0
   Synaptics Locked Drags Timeout (319):5000
   Synaptics Tap Action (320):  0, 0, 0, 0, 1, 3, 2
   Synaptics Click Action (321):1, 3, 2
   Synaptics Circular Scrolling (322):  0
   Synaptics Circular Scrolling Distance (323): 0.10
   Synaptics Circular Scrolling Trigger (324):  0
   Synaptics Circular Pad (325):0
   Synaptics Palm Detection (326):  1
   Synaptics Palm Dimensions (327): 10, 200
   Synaptics Coasting Speed (328):  20.00, 50.00
   Synaptics Pressure Motion (329): 30, 160
   Synaptics Pressure Motion Factor (330):  1.00, 1.00
   Synaptics Resolution Detect (331):   1
   Synaptics Grab Event Device (332):   0
   Synaptics Gestures (333):1
   Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0
   Synaptics Pad Resolution (335):  42, 42
   Synaptics Area (336):0, 0, 0, 0
   Synaptics Soft Button Areas (337):   0, 0, 0, 0, 0, 0, 0, 0
   Synaptics Noise Cancellation (338):  23, 23
   Device Product ID (262): 1739, 10036
   Device Node (263):   "/dev/input/event5"

  # lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
09)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel

[Kernel-packages] [Bug 1855264] Re: Kernel upgrade 5.3.0-23 to -24 results in panic

2019-12-08 Thread Rob Peters 
For what its worth, this system originally had a wifi problem and is
running a backport-iwlwifi-dkms package.  Could that be the problem?

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

Title:
  Kernel upgrade 5.3.0-23 to -24 results in panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 7590 2019 version.
  Apt linux kernel update from 5.3.0-23 to 5.3-0-24 and boot failed, kernel 
panic.
  Attached file with booting with 5.3.0-24 debug display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855264/+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 1788928] Re: psmouse: after sleep/suspend thinkpad touchpad not functional

2019-12-08 Thread Youssoufou YABRE 
*** This bug is a duplicate of bug 1786574 ***
https://bugs.launchpad.net/bugs/1786574

I had the same problem with ubuntu 20.04 daily build on
Thinkpad T440s .

adding "psmouse.synaptics_intertouch=0" to GRUB_CMDLINE_LINUX in
/etc/default/grub solved the problem.

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

Title:
  psmouse: after sleep/suspend thinkpad touchpad not functional

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Summary:
  The touchpad after sleep/suspend of my ThinkPad X1 will not function 
correctly.

  Expected Behavior:
  After sleep/suspend scroll works correctly.

  Actual Behavior:
  Unable to scroll or correctly click on a window and move it without reloading 
the driver

  Steps to reproduce:
  1. Install Bionic on Thinkpad X1 (4.15.0-32-generic)
  2. Open something to scroll (e.g. browser, terminal, etc.)
  3. Close lid
  4. Re-open lid once sleeping/suspended
  5. Try to scroll and note that it does not work

  Workaround:
  Run the following after re-opening the lid
  $ sudo modprobe psmouse -r; sudo modprobe psmouse

  dmesg on reload:
  [12753.847050] psmouse serio1: synaptics: queried max coordinates: x 
[..5676], y [..4758]
  [12753.879362] psmouse serio1: synaptics: queried min coordinates: x 
[1266..], y [1096..]
  [12753.879375] psmouse serio1: synaptics: Trying to set up SMBus access
  [12753.882246] psmouse serio1: synaptics: SMbus companion is not ready yet
  [12753.944774] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 
0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x1, board id: 3072, fw id: 
1795685
  [12753.944791] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
  [12753.985102] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input24
  [12754.619594] psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [12754.823238] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio5/input/input25
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj2506 F pulseaudio
   /dev/snd/controlC0:  powersj2506 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on 2018-02-19 (185 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  Lsusb:
   Bus 001 Device 002: ID 8087:8001 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20BSCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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=/vmlinuz-4.15.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET42W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788928/+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 1849141] Re: (Lenovo S130-11IGM) No touchpad after update to 18.04 4.15.0-65

2019-12-08 Thread Arthur Lutz 
For me the trackpad works on 4.15.0-70-generic but breaks on
4.15.0-72-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/1849141

Title:
  (Lenovo S130-11IGM) No touchpad after update to 18.04 4.15.0-65

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop works fine out of the box with 18.04  4.15.0-20. After the software 
update to 4.15.0-65, the touchpad is no longer detected. Cannot use 19.04 as 
seems to be a problem with emmc support 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883).
  Currently dropped back to 4.15.0-20.

  Followed the advice of installing synaptics, then evdev drivers but
  still same issue. Touchpad works fine in 4.15.0-20 using libinput.

  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-65-generic.
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1276 F lxpanel
    james  1336 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xa131 irq 132'
     Mixer name : 'Realtek ALC269VC'
     Components : 'HDA:10ec0269,17aa380f,00100203 
HDA:8086280d,80860101,0010'
     Controls  : 58
     Simple ctrls  : 16
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-16 (4 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5627 Realtek Semiconductor Corp.
   Bus 001 Device 003: ID 0bda:c024 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81J1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=253cd622-8008-48b8-84eb-ce104896999e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-65-generic N/A
   linux-backports-modules-4.15.0-65-generic  N/A
   linux-firmware 1.173.9
  Tags:  bionic
  Uname: Linux 4.15.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HCN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32802WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad S130-11IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM:
  dmi.product.family: ideapad S130-11IGM
  dmi.product.name: 81J1
  dmi.product.version: Lenovo ideapad S130-11IGM
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849141/+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 1853440] ShellJournal.txt

2019-12-08 Thread Jan 
apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1853440/+attachment/5310725/+files/ShellJournal.txt

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

Title:
  Volume either 0 or 100% on Lenovo X1 Carbon G7

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Volume increasing or decreasing doesn't work. 
  I can only toggle sound on (= 100%) and off (= 0%).

  What I found out is that the Master channel seems to have no effect
  for volume adjustments, but the PCM channel does. If the sound is
  muted, PCM is set to 0 and therefore the sound is toggled off, but
  when I increase the sound a bit, PCM jumps straight to 100, causing
  the speakers to be very load.

  I have attached alsa-info output.

  System environment:
  Pop!_OS 19.10
  Release: 19.10

  Alsa-Version:
  alsa-base: 1.0.25

  Sound Card:
  HDA-Intel
  Codec: Realtek ALC285
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: pop:GNOME
  DisplayManager: gdm3
  DistroRelease: Pop!_OS 19.10
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 
5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7
  RelatedPackageVersions: mutter-common 
3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a
  Tags: third-party-packages eoan
  Uname: Linux 5.3.0-22-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1853440] ProcCpuinfoMinimal.txt

2019-12-08 Thread Jan 
apport information

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

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

Title:
  Volume either 0 or 100% on Lenovo X1 Carbon G7

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Volume increasing or decreasing doesn't work. 
  I can only toggle sound on (= 100%) and off (= 0%).

  What I found out is that the Master channel seems to have no effect
  for volume adjustments, but the PCM channel does. If the sound is
  muted, PCM is set to 0 and therefore the sound is toggled off, but
  when I increase the sound a bit, PCM jumps straight to 100, causing
  the speakers to be very load.

  I have attached alsa-info output.

  System environment:
  Pop!_OS 19.10
  Release: 19.10

  Alsa-Version:
  alsa-base: 1.0.25

  Sound Card:
  HDA-Intel
  Codec: Realtek ALC285
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: pop:GNOME
  DisplayManager: gdm3
  DistroRelease: Pop!_OS 19.10
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 
5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7
  RelatedPackageVersions: mutter-common 
3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a
  Tags: third-party-packages eoan
  Uname: Linux 5.3.0-22-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1853440] ProcEnviron.txt

2019-12-08 Thread Jan 
apport information

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

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

Title:
  Volume either 0 or 100% on Lenovo X1 Carbon G7

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Volume increasing or decreasing doesn't work. 
  I can only toggle sound on (= 100%) and off (= 0%).

  What I found out is that the Master channel seems to have no effect
  for volume adjustments, but the PCM channel does. If the sound is
  muted, PCM is set to 0 and therefore the sound is toggled off, but
  when I increase the sound a bit, PCM jumps straight to 100, causing
  the speakers to be very load.

  I have attached alsa-info output.

  System environment:
  Pop!_OS 19.10
  Release: 19.10

  Alsa-Version:
  alsa-base: 1.0.25

  Sound Card:
  HDA-Intel
  Codec: Realtek ALC285
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: pop:GNOME
  DisplayManager: gdm3
  DistroRelease: Pop!_OS 19.10
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 
5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7
  RelatedPackageVersions: mutter-common 
3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a
  Tags: third-party-packages eoan
  Uname: Linux 5.3.0-22-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1853440] Re: Volume either 0 or 100% on Lenovo X1 Carbon G7

2019-12-08 Thread Jan 
apport information

** Tags added: apport-collected third-party-packages

** Description changed:

  Volume increasing or decreasing doesn't work. 
  I can only toggle sound on (= 100%) and off (= 0%).
  
  What I found out is that the Master channel seems to have no effect for
  volume adjustments, but the PCM channel does. If the sound is muted, PCM
  is set to 0 and therefore the sound is toggled off, but when I increase
  the sound a bit, PCM jumps straight to 100, causing the speakers to be
  very load.
  
  I have attached alsa-info output.
  
  System environment:
  Pop!_OS 19.10
  Release: 19.10
  
  Alsa-Version:
  alsa-base: 1.0.25
  
  Sound Card:
  HDA-Intel
  Codec: Realtek ALC285
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ CurrentDesktop: pop:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Pop!_OS 19.10
+ Package: linux
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 
5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7
+ RelatedPackageVersions: mutter-common 
3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a
+ Tags: third-party-packages eoan
+ Uname: Linux 5.3.0-22-generic x86_64
+ UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1853440/+attachment/5310721/+files/Dependencies.txt

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

Title:
  Volume either 0 or 100% on Lenovo X1 Carbon G7

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Volume increasing or decreasing doesn't work. 
  I can only toggle sound on (= 100%) and off (= 0%).

  What I found out is that the Master channel seems to have no effect
  for volume adjustments, but the PCM channel does. If the sound is
  muted, PCM is set to 0 and therefore the sound is toggled off, but
  when I increase the sound a bit, PCM jumps straight to 100, causing
  the speakers to be very load.

  I have attached alsa-info output.

  System environment:
  Pop!_OS 19.10
  Release: 19.10

  Alsa-Version:
  alsa-base: 1.0.25

  Sound Card:
  HDA-Intel
  Codec: Realtek ALC285
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: pop:GNOME
  DisplayManager: gdm3
  DistroRelease: Pop!_OS 19.10
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 
5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7
  RelatedPackageVersions: mutter-common 
3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a
  Tags: third-party-packages eoan
  Uname: Linux 5.3.0-22-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1853440] GsettingsChanges.txt

2019-12-08 Thread Jan 
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1853440/+attachment/5310722/+files/GsettingsChanges.txt

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

Title:
  Volume either 0 or 100% on Lenovo X1 Carbon G7

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Volume increasing or decreasing doesn't work. 
  I can only toggle sound on (= 100%) and off (= 0%).

  What I found out is that the Master channel seems to have no effect
  for volume adjustments, but the PCM channel does. If the sound is
  muted, PCM is set to 0 and therefore the sound is toggled off, but
  when I increase the sound a bit, PCM jumps straight to 100, causing
  the speakers to be very load.

  I have attached alsa-info output.

  System environment:
  Pop!_OS 19.10
  Release: 19.10

  Alsa-Version:
  alsa-base: 1.0.25

  Sound Card:
  HDA-Intel
  Codec: Realtek ALC285
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: pop:GNOME
  DisplayManager: gdm3
  DistroRelease: Pop!_OS 19.10
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 
5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7
  RelatedPackageVersions: mutter-common 
3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a
  Tags: third-party-packages eoan
  Uname: Linux 5.3.0-22-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1855588] Re: Touchpad stopped working after upgrade to 4.15.0-72-generic

2019-12-08 Thread Chris Guiver 
*** This bug is a duplicate of bug 1854798 ***
https://bugs.launchpad.net/bugs/1854798

** This bug has been marked a duplicate of bug 1854798
   Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-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/1855588

Title:
  Touchpad stopped working after upgrade to 4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 18.04.3 on a Dell XSP12 laptop.  After an
  automatic kernel update from 4.15.0-70-generic to 4.15.0-72-generic,
  my touchpad stopped working. (The mouse pointer is not moving, and I
  cannot click.)  The touchpad is still working when I start up with the
  older kernel.

  I think it's a Synaptics touchpad.  The output of 'xinput list' when
  running either kernel is as follows:

  
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ATML1000:00 03EB:842F   id=11   [slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Generic Mouse  id=16   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Webcam: Integrated W id=9[slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=10   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcus 1546 F pulseaudio
   /dev/snd/controlC1:  marcus 1546 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 13:55:23 2019
  HibernationDevice: RESUME=UUID=07196a12-9711-4352-816d-530ed0fe9c00
  InstallationDate: Installed on 2019-04-29 (222 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. XPS 12-9Q33
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=fa2cb087-82ac-4ae2-94ca-9cdc35006815 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855588/+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 1855588] [NEW] Touchpad stopped working after upgrade to 4.15.0-72-generic

2019-12-08 Thread cohomology84 
Public bug reported:

I am running Ubuntu 18.04.3 on a Dell XSP12 laptop.  After an automatic
kernel update from 4.15.0-70-generic to 4.15.0-72-generic, my touchpad
stopped working. (The mouse pointer is not moving, and I cannot click.)
The touchpad is still working when I start up with the older kernel.

I think it's a Synaptics touchpad.  The output of 'xinput list' when
running either kernel is as follows:


⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ ATML1000:00 03EB:842F id=11   [slave  pointer  (2)]
⎜   ↳ Synaptics s3203   id=12   [slave  pointer  (2)]
⎜   ↳ PS/2 Generic Mouseid=16   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Integrated Webcam: Integrated W   id=9[slave  keyboard (3)]
↳ Intel Virtual Button driver   id=10   [slave  keyboard (3)]
↳ Dell WMI hotkeys  id=13   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=14   [slave  keyboard (3)]
↳ DELL Wireless hotkeys id=15   [slave  keyboard (3)]

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-72-generic 4.15.0-72.81
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  marcus 1546 F pulseaudio
 /dev/snd/controlC1:  marcus 1546 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec  8 13:55:23 2019
HibernationDevice: RESUME=UUID=07196a12-9711-4352-816d-530ed0fe9c00
InstallationDate: Installed on 2019-04-29 (222 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. XPS 12-9Q33
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=fa2cb087-82ac-4ae2-94ca-9cdc35006815 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-72-generic N/A
 linux-backports-modules-4.15.0-72-generic  N/A
 linux-firmware 1.173.12
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: XPS 12-9Q33
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 12-9Q33
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

** Summary changed:

- Touchpad stopped working after upgrade to 4.15.0-70-generic
+ Touchpad stopped working after upgrade to 4.15.0-72-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/1855588

Title:
  Touchpad stopped working after upgrade to 4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 18.04.3 on a Dell XSP12 laptop.  After an
  automatic kernel update from 4.15.0-70-generic to 4.15.0-72-generic,
  my touchpad stopped working. (The mouse pointer is not moving, and I
  cannot click.)  The touchpad is still working when I start up with the
  older kernel.

  I think it's a Synaptics touchpad.  The output of 'xinput list' when
  running either kernel is as follows:

  
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ATML1000:00 03EB:842F   id=11   [slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Generic Mouse  id=16   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard

[Kernel-packages] [Bug 1855588] Status changed to Confirmed

2019-12-08 Thread Ubuntu Kernel Bot 
This change was made by a bot.

** 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/1855588

Title:
  Touchpad stopped working after upgrade to 4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 18.04.3 on a Dell XSP12 laptop.  After an
  automatic kernel update from 4.15.0-70-generic to 4.15.0-72-generic,
  my touchpad stopped working. (The mouse pointer is not moving, and I
  cannot click.)  The touchpad is still working when I start up with the
  older kernel.

  I think it's a Synaptics touchpad.  The output of 'xinput list' when
  running either kernel is as follows:

  
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ATML1000:00 03EB:842F   id=11   [slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Generic Mouse  id=16   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Webcam: Integrated W id=9[slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=10   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcus 1546 F pulseaudio
   /dev/snd/controlC1:  marcus 1546 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 13:55:23 2019
  HibernationDevice: RESUME=UUID=07196a12-9711-4352-816d-530ed0fe9c00
  InstallationDate: Installed on 2019-04-29 (222 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. XPS 12-9Q33
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=fa2cb087-82ac-4ae2-94ca-9cdc35006815 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855588/+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 1847937] Re: 'gpu has fallen off the bus' after return from suspend

2019-12-08 Thread Jonathon Padfield 
I'm seeing the same problem; after waking from suspend it wakes to a
black console with the message "GPU has fallen off the bus".

This is with a Dell Precision 5540, NVIDIA Corporation TU117GLM [Quadro
T1000 Mobile]

Kubuntu, Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

The failures happens with both nvidia-driver-435 and nvidia-driver-440
driver packages.

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

Title:
  'gpu has fallen off the bus' after return from suspend

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With this message the only way to resume work is to reboot the system
  using power button.

  With kernel linux-image-5.3.0-13-generic everything is OK.
  Problem appeared afer upgrade to linux-image-5.3.0-17-generic and still 
happens in linux-image-5.3.0-18-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  player 4451 F pulseaudio
   /dev/snd/controlC1:  player 4451 F pulseaudio
   /dev/snd/controlC0:  player 4451 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Oct 14 01:27:04 2019
  HibernationDevice: RESUME=UUID=a58bb700-5818-4ca6-8351-fd4e5e28ea9e
  MachineType: LENOVO 20BG0016US
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=d0c33b75-6f04-4d53-bc3b-91924e3bcf91 ro quiet splash vga=current 
loglevel=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-08 (5 days ago)
  WifiSyslog:
   
  dmi.bios.date: 05/30/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET88WW (2.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BG0016US
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BG0016US
  dmi.product.sku: LENOVO_MT_20BG
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+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 1852001] Re: KDE GUI freeze on high disk IO, but disabling swap fixes it

2019-12-08 Thread JPT 
attached "ps auxw" while GUI was freezed. 
kernel 5.4.1-050401-generic
no swap
I restarted GUI using /etc/init.d/sddm restart
right now only the KDE taskbar and menu are locked, Alt-Tab and programs still 
work. (this is a rather new phenomena)
I already experienced this once, where some programs were freezed too (eg 
libreoffice) and others weren't. I only got a message like "program does not 
answer, force close it"?
maybe this is a second hand problem as some inter-process communication locks 
apps when KDE is locked?

after about 5 minutes KDE bar crashed and restarted. now works.

from syslog while KDE bar locked:
pulseaudio[30539]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
...
PackageKit: daemon quit
systemd[1]: packagekit.service: Main process exited, code=killed, status=15/TERM
systemd[1]: packagekit.service: Succeeded.
...
dbus-daemon[1772]: [system] Activating via systemd: service 
name='org.freedesktop.PackageKit' unit='packagekit.service' requested by 
':1.679' (uid=1000 pid=32050 comm="/usr/bin/plasmashell ")
systemd[1]: Starting PackageKit Daemon...
PackageKit: daemon start
dbus-daemon[1772]: [system] Successfully activated service 
'org.freedesktop.PackageKit'
systemd[1]: Started PackageKit Daemon.


** Attachment added: "processes.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852001/+attachment/5310701/+files/processes.txt

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

Title:
  KDE GUI freeze on high disk IO, but disabling swap fixes it

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've got massive problems with GUI on my PC.

  The attached logs are from the following setting: 
  - high disk load (f3write)
  - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan)
  - no swap available

  These are the parameters (disk load, kernel, swap) I am fiddling with
  to find out the cause, see below.

  In general 
  - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo
  - more likely to happen with high disk or CPU load, but not necessarily.
  - less likely with the 4.x kernel mentioned above. 

  I just installed the following kernels from kernel-ppa:
  5.3.10-050310-generic 
  5.4.0-050400rc6-generic
  5.4.0-997-generic (drm-intel-next)
  Now I am waiting for the freeze to occur again. 

  The problem started about half a year ago. 
  There have been three changes that happened at the time and could be the cause
  - switch to kernel 5.x
  - update to Ubuntu 19.4
  - swapped motherboard, CPU and RAM. 

  The hassle started with the following scenario, repeated often: 
  - high disk load
  - PC becomes laggy
  - soon dies/freezes

  The longer I waited, the deeper the lockdown went. but I don't know the exact 
details. 
  The first cause I found was kswapd running amok and take the system with it. 
Workaround: add swap space. 

  Now the problem shifted: Whenever I got high disk load (eg dd 100 GB
  of data) the kernel swaps likle crazy and makes the GUI first lag soon
  freeze. but no excessive CPU load any more, as kswapd does not go
  crazy.

  Again I found a workaround: 
  the above mentioned 4.x kernel. In this case the GUI lags as expected from a 
heavily swapping system. nothing more. 
  but still sometimes the GUI simply freezes (the error reported at the top)

  Another workaround is to completely remove swap. Let's see what
  happens, if kswapd goes amok again.

  I am not sure as how these problems are related.

  I did extensive hardware check like
  - memtest86 newest version, no "may be vulnerable to high frequency row 
hammering"
  - smart

  do you suggest any burn in test suites?

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18
  Uname: Linux 4.15.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Nov 10 15:55:14 2019
  DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb 
http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled 
on upgrade to eoan' was disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 
(Desktop 9 Series) [1462:7b16]
  InstallationDate: Installed on 2017-12-16 (693 days ago)

[Kernel-packages] [Bug 1852432] Re: i40e: Setting VF MAC address causes General Protection Fault

2019-12-08 Thread Nobuto Murata 
The general protection fault was reproducible with the current 5.3 kernel as 
follows by creating 10 SR-IOV sequentially. After updating it to the -proposed 
one as
 linux-image-5.3.0-25-generic 5.3.0-25.27, there is no such general protection 
fault happened with the same operations. So we can consider the fix is verified 
with the eoan-proposed kernel.

** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  i40e: Setting VF MAC address causes General Protection Fault

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [Impact]
   * Creating SR-IOV enabled VMs in Openstack can sometimes trigger the GPF and 
leave system unusable

  [Test Case]
   * Continuously spin up VFs and set MAC address with e.g. ifconfig

  [Fix]
   * The fix updates the VSI pointer passed down to i40e_set_vf_mac function() 
if the adapter is still in reset, preventing the GPF.

  [Regression Potential]
   * Regression potential should be low, as we're now updating the VSI using 
the ID stored in the VF pointer
   * Regressions could arise from issues in VF creation or reset, as that would 
corrupt the new VSI pointer
   * Patch was validated and tested in a production environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852432/+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 1852663] Re: i40e: general protection fault in i40e_config_vf_promiscuous_mode

2019-12-08 Thread Nobuto Murata 
The general protection fault is reproducible with the current 5.3 kernel as 
follows by creating 10 SR-IOV enabled VMs with OpenStack and deleting 5 VMs 
sequentially. After updating it to the -proposed one as
 linux-image-5.3.0-25-generic 5.3.0-25.27, there is no such general protection 
fault happened with the same operations. So we can consider the fix is verified.

===

Dec 08 08:39:07 hostname kernel: i40e :af:00.1: Bring down and up the VF 
interface to make this change effective.
Dec 08 08:39:07 hostname kernel: general protection fault:  [#1] SMP PTI
Dec 08 08:39:07 hostname kernel: CPU: 36 PID: 3225 Comm: libvirtd Not tainted 
5.3.0-24-generic #26~18.04.2-Ubuntu

Dec 08 08:39:07 hostname kernel: Hardware name: HPE ProLiant DL380 
Gen10/ProLiant DL380 Gen10, BIOS U30 05/21/2019
Dec 08 08:39:07 hostname kernel: RIP: 
0010:i40e_config_vf_promiscuous_mode+0x172/0x330 [i40e]
Dec 08 08:39:07 hostname kernel: Code: 48 8b 00 83 d1 00 48 85 c0 75 ef 49 83 
c4 08 4c 39 e6 75 dd 85 c9 74 73 0f b6 45 c0 45 31 d2 89 45 d0 4d 8b 3e 4d 85 
ff 74 53 <41> 0f b7 4f 16
Dec 08 08:39:07 hostname kernel: RSP: 0018:a7045d32b760 EFLAGS: 00010202
Dec 08 08:39:07 hostname kernel: RAX:  RBX: 94e379bdb000 
RCX: 
Dec 08 08:39:07 hostname kernel: RDX:  RSI: 0600 
RDI: 9583a4424350
Dec 08 08:39:07 hostname kernel: RBP: a7045d32b7b0 R08:  
R09: 9583a54d95e0
Dec 08 08:39:07 hostname kernel: R10:  R11: 0100 
R12: 94e379bdba28
Dec 08 08:39:07 hostname kernel: R13: 9583a4424008 R14: 94e379bdb338 
R15: 010eb7eb8c61c8cb
Dec 08 08:39:07 hostname kernel: FS:  7f495b017700() 
GS:9533bfa8() knlGS:
Dec 08 08:39:07 hostname kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Dec 08 08:39:07 hostname kernel: CR2: 7f4967d89360 CR3: 004d839c0004 
CR4: 007626e0
Dec 08 08:39:07 hostname kernel: DR0:  DR1:  
DR2: 
Dec 08 08:39:07 hostname kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
Dec 08 08:39:07 hostname kernel: PKRU: 5554
Dec 08 08:39:07 hostname kernel: Call Trace:
Dec 08 08:39:07 hostname kernel:  i40e_ndo_set_vf_port_vlan+0x1a2/0x440 [i40e]
Dec 08 08:39:07 hostname kernel:  do_setlink+0x53f/0xee0
Dec 08 08:39:07 hostname kernel:  ? update_load_avg+0x596/0x620
Dec 08 08:39:07 hostname kernel:  ? update_curr+0x7a/0x1d0
Dec 08 08:39:07 hostname kernel:  ? __switch_to_asm+0x40/0x70
Dec 08 08:39:07 hostname kernel:  ? __switch_to_asm+0x34/0x70


** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  i40e: general protection fault in i40e_config_vf_promiscuous_mode

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  [Impact] 
  Assign some VFs to VMs, when deleting VMs, a general protection fault occurs 
in i40e_config_vf_promiscuous_mode

  general protection fault:  [#1] SMP PTI
  CPU: 54 PID: 6200 Comm: libvirtd Not tainted 5.3.0-21-generic 
#22~18.04.1-UbuntuHardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, 
BIOS U30 05/21/2019
  RIP: 0010:i40e_config_vf_promiscuous_mode+0x172/0x330 [i40e]
  Code: 48 8b 00 83 d1 00 48 85 c0 75 ef 49 83 c4 08 4c 39 e6 75 dd 85 c9 74 73 
0f b6 45 c0 45 31 d2 89 45 d0 4d 8b 3e 4d 85 ff 74 53 <41> 0f b7 4f 16 66 81 f9 
ff 0f 77 3f 0f b7 b3 ea 0c 00 00 8b 55 d0
  RSP: 0018:b987b5c77760 EFLAGS: 00010202
  RAX:  RBX: 9bb5df5a9000 RCX: 
  RDX:  RSI: 0600 RDI: 9bace4bce350
  RBP: b987b5c777b0 R08:  R09: 9bace56a9da0
  R10:  R11: 0100 R12: 9bb5df5a9a28
  R13: 9bace4bce008 R14: 9bb5df5a9338 R15: 26c2b975d54f5980
  FS:  7f9f07fff700() GS:9bfcff48() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7fa73c9c0e10 CR3: 00f6ab37a002 CR4: 007626e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  PKRU: 5554
  Call Trace:
  i40e_ndo_set_vf_port_vlan+0x1a2/0x440[i40e]
  do_setlink+0x53f/0xee0
  ?update_load_avg+0x596/0x620
  ?update_curr+0x7a/0x1d0
  ?__switch_to_asm+0x40/0x70
  ?__switch_to_asm+0x34/0x70
  ?__switch_to_asm+0x40/0x70
  ?__switch_to_asm+0x34/0x70
  rtnl_setlink+0x113/0x150
  rtnetlink_rcv_msg+0x296/0x340
  ?aa_label_sk_perm.part.4+0x10f/0x160
  ?_cond_resched+0x19/0x40
  ?rtnl_calcit.isra.30+0x120/0x120
  netlink_rcv_skb+0x51/0x120
  rtnetlink_rcv+0x15/0x20
  netlink_unicast+0x1a4/0x250
  netlink_sendmsg+0x2d7/0x3d0

[Kernel-packages] [Bug 1852663] Re: i40e: general protection fault in i40e_config_vf_promiscuous_mode

2019-12-08 Thread Nobuto Murata 
The general protection fault is reproducible with the current 5.3 kernel as 
follows by creating 10 SR-IOV enabled VMs with OpenStack and deleting 5 VMs 
sequentially. After updating it to the -proposed one as
 linux-image-5.3.0-25-generic 5.3.0-25.27, there is no such general protection 
fault happened with the same operations. So we can consider the fix is verified.

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

Title:
  i40e: general protection fault in i40e_config_vf_promiscuous_mode

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  [Impact] 
  Assign some VFs to VMs, when deleting VMs, a general protection fault occurs 
in i40e_config_vf_promiscuous_mode

  general protection fault:  [#1] SMP PTI
  CPU: 54 PID: 6200 Comm: libvirtd Not tainted 5.3.0-21-generic 
#22~18.04.1-UbuntuHardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, 
BIOS U30 05/21/2019
  RIP: 0010:i40e_config_vf_promiscuous_mode+0x172/0x330 [i40e]
  Code: 48 8b 00 83 d1 00 48 85 c0 75 ef 49 83 c4 08 4c 39 e6 75 dd 85 c9 74 73 
0f b6 45 c0 45 31 d2 89 45 d0 4d 8b 3e 4d 85 ff 74 53 <41> 0f b7 4f 16 66 81 f9 
ff 0f 77 3f 0f b7 b3 ea 0c 00 00 8b 55 d0
  RSP: 0018:b987b5c77760 EFLAGS: 00010202
  RAX:  RBX: 9bb5df5a9000 RCX: 
  RDX:  RSI: 0600 RDI: 9bace4bce350
  RBP: b987b5c777b0 R08:  R09: 9bace56a9da0
  R10:  R11: 0100 R12: 9bb5df5a9a28
  R13: 9bace4bce008 R14: 9bb5df5a9338 R15: 26c2b975d54f5980
  FS:  7f9f07fff700() GS:9bfcff48() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7fa73c9c0e10 CR3: 00f6ab37a002 CR4: 007626e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  PKRU: 5554
  Call Trace:
  i40e_ndo_set_vf_port_vlan+0x1a2/0x440[i40e]
  do_setlink+0x53f/0xee0
  ?update_load_avg+0x596/0x620
  ?update_curr+0x7a/0x1d0
  ?__switch_to_asm+0x40/0x70
  ?__switch_to_asm+0x34/0x70
  ?__switch_to_asm+0x40/0x70
  ?__switch_to_asm+0x34/0x70
  rtnl_setlink+0x113/0x150
  rtnetlink_rcv_msg+0x296/0x340
  ?aa_label_sk_perm.part.4+0x10f/0x160
  ?_cond_resched+0x19/0x40
  ?rtnl_calcit.isra.30+0x120/0x120
  netlink_rcv_skb+0x51/0x120
  rtnetlink_rcv+0x15/0x20
  netlink_unicast+0x1a4/0x250
  netlink_sendmsg+0x2d7/0x3d0
  sock_sendmsg+0x63/0x70
  ___sys_sendmsg+0x2a9/0x320
  ?aa_label_sk_perm.part.4+0x10f/0x160
  ?_raw_spin_unlock_bh+0x1e/0x20
  ?release_sock+0x8f/0xa0
  __sys_sendmsg+0x63/0xa0
  ?__sys_sendmsg+0x63/0xa0
  __x64_sys_sendmsg+0x1f/0x30
  do_syscall_64+0x5a/0x130
  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  This issue also happens when deleting k8s pod if VF is used by k8s pod, there 
was a bug reported in the e1000-devel mailing list
  https://sourceforge.net/p/e1000/mailman/message/36766306/ 

  The fix is suggested by Billy McFall, to add protection when accessing
  the hash list(vsi->mac_filter_hash), but it's not upstream yet

  [Test Case]
  Spin up some VMs with VFs, then delete all VMs

  
  [Regression Potential]
  Low, the fix is to add a protection for a hash list, shouldn't have potential 
regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852663/+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/speaker default to low quality headset mode and fails to switch to A2DP when selected

2019-12-08 Thread Balazs Gyurak 
I have the same problem with Sony wh-1000xm3 and Ubuntu 19.10.

-- 
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/speaker default to low quality headset mode and
  fails to switch to A2DP when selected

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  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.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

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