[Kernel-packages] [Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-19 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in GNOME Shell:
  Fix Released
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.

  * Add a line to /usr/lib/udev/rules.d/61-gdm.rules:
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1705369/+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 1832782] Re: Backport VMW_PVRDMA PPN64 patch

2019-06-14 Thread Bug Watch Updater
** Changed in: linux (Debian)
   Status: Unknown => 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/1832782

Title:
  Backport VMW_PVRDMA PPN64 patch

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  New

Bug description:
  Hi,

  Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and
  later?

  Here is the commit log:

  commit 8aa04ad3b39396e315b23448c56d5465200fa777
  Author: Adit Ranadive 
  Date:   Sat Jan 26 05:09:36 2019 +

  RDMA/vmw_pvrdma: Support upto 64-bit PFNs

  Update the driver to use the new device capability to report 64-bit UAR
  PFNs.

  Thanks,
  Adit

  [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2010 F pulseaudio
adit   3290 F pulseaudio
   /dev/snd/controlC0:  gdm2010 F pulseaudio
adit   3290 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723
  InstallationDate: Installed on 2018-11-06 (219 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T3600
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-51-generic N/A
   linux-backports-modules-4.15.0-51-generic  N/A
   linux-firmware 1.173.6
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/09/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 08HPGT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3600
  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/1832782/+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 1832776] Re: Backport VMCI PPN64 patch

2019-06-13 Thread Bug Watch Updater
** Changed in: linux (Debian)
   Status: Unknown => 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/1832776

Title:
  Backport VMCI PPN64 patch

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  New

Bug description:
  Hi,

  Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I
  have already filed a bug with Debian[2].

  Here is the commit log:

  commit f2db7361cb19bf3a6f7fd367f21d8eb325397946
  Author: Vishnu DASA 
  Commit: Greg Kroah-Hartman 

  VMCI: Support upto 64-bit PPNs

  Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI
  device exposes the capability for 64-bit PPNs.

  Thanks,
  Adit

  [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946
  [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  adit   3290 F pulseaudio
   /dev/snd/controlC0:  adit   3290 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723
  InstallationDate: Installed on 2018-11-06 (219 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T3600
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-51-generic N/A
   linux-backports-modules-4.15.0-51-generic  N/A
   linux-firmware 1.173.6
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 08HPGT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3600
  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/1832776/+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 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-13 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in GNOME Shell:
  New
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1705369/+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 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

2019-06-12 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => Fix Released

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

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

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1791312/+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 190587] Re: Local root exploit in kernel 2.6.17 - 2.6.24 (vmsplice)

2019-06-11 Thread Bug Watch Updater
Launchpad has imported 35 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=432251.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-02-10T13:37:47+00:00 mjc wrote:

A new system call named vmsplice() was introduced in the 2.6.17
release of the Linux kernel. 

COSEINC reported two issues affecting vmsplice, CVE-2008-0009 and
CVE-2008-0010.

On Saturday 20080210 a public exploit was released that utilised a similar flaw
in vmsplice (vmsplice_to_pipe function) to allow a local user to gain privileges
on some architectures.  

See also
http://marc.info/?t=12026365533=1=2

This issue will affect kernels 2.6.17+ and therefore affected Red Hat Enterprise
Linux 5, but not Red Hat Enterprise Linux 4, 3, or 2.1.

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/8


On 2008-02-10T16:39:00+00:00 mjc wrote:

Note that there may be a  little confusion as there are actually three vmsplice
issues:

CVE-2008-0009 is already fixed upstream, does not affect any RHEL,  has no
public exploit.  Upstream patch is the second hunk of:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8811930dc74a503415b35c4a79d14fb0b408a361

CVE-2008-0010 is already fixed upstream, does not affect any RHEL, but has
a public exploit. ( http://www.milw0rm.com/exploits/5093 )
Upstream patch is the first hunk of:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8811930dc74a503415b35c4a79d14fb0b408a361

CVE-2008-0600 is not yet fixed upstream, affects RHEL5,
and has a public exploit ( http://www.milw0rm.com/exploits/5092 )


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/190587/comments/12


On 2008-02-10T18:11:58+00:00 mjc wrote:

Proposed patch for RHEL5 from Al Viro

diff -urN linux-2.6.18.x86_64/fs/splice.c linux-2.6.18.x86_64-fix/fs/splice.c
--- linux-2.6.18.x86_64/fs/splice.c 2008-02-10 11:08:19.0 -0500
+++ linux-2.6.18.x86_64-fix/fs/splice.c 2008-02-10 11:31:06.0 -0500
@@ -1154,6 +1154,9 @@
if (unlikely(!base))
break;
 
+   if (unlikely(!access_ok(VERIFY_READ, base, len)))
+   break;
+
/*
 * Get this base offset and number of pages, then map
 * in the user pages.




Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/14


On 2008-02-10T20:42:39+00:00 mjc wrote:

Confirmed the patch blocks this issue for Red Hat Enterprise Linux 5; this
specific exploit prints "[-] vmsplice: Bad address" and fails.

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/20


On 2008-02-10T21:17:01+00:00 mjc wrote:

Upstream fix:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=712a30e63c8066ed84385b12edbfb804f49cbc44


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/190587/comments/22


On 2008-02-10T22:05:50+00:00 mjc wrote:

For Red Hat Enterprise Linux 5:
CVSS v2 Base score: 7.2 (High) (AV:L/AC:L/Au:N/C:C/I:C/A:C)

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/24


On 2008-02-10T23:16:13+00:00 redhat wrote:

We added a quick and dirty patch for the problem here:
http://home.powertech.no/oystein/ptpatch2008/

It is a kernel module that disables vmsplice, and logs any attempts to exploit
the bug.
As it it a loadable module it can easily be deployed on systems that can not be
updated with a new kernel for various reasons.

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/29


On 2008-02-10T23:38:28+00:00 seva wrote:

Ola,

I tried that module on a test system and got:
   kernel: general protection fault:  [1] SMP 

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/31


On 2008-02-11T03:29:52+00:00 ryan wrote:

The make file required some modification for PAE kernels due to path issues;
once compiled module fails to load with:
insmod: error inserting 'ptpatch2008.ko': -1 

[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

2019-06-09 Thread Bug Watch Updater
** Changed in: linux
   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/1826125

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  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+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

2019-05-31 Thread Bug Watch Updater
** Changed in: systemd (Debian)
   Status: Unknown => 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/1814373

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in udisks2 source package in Eoan:
  Invalid
Status in systemd package in Debian:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1615405] Re: zfs share doesn't work

2019-05-31 Thread Bug Watch Updater
** Changed in: zfs
   Status: Unknown => New

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

Title:
  zfs share doesn't work

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  I'm testing on Ubuntu 16.04 with the included zol 0.6.5.

  I have also reported this bug here:
  https://github.com/zfsonlinux/zfs/issues/4999

  zfs share and zfs share -a just don't work. zfs set sharesmb=on
  pool/dataset works fine. I discovered that the shares are listed in
  /etc/dfs/sharetab but don't work. If I reboot or anything and try to
  share them again with zfs share, it will not work. net usershare list
  displays nothing. And of course because of this all shares are lost on
  every reboot.

  Despite a dataset having the sharesmb=on value set, it will not share
  with zfs share -a and if I use zfs share pool/dataset it says: cannot
  share 'pool/dataset': filesystem already shared, when net usershare
  list shows nothing**. Samba is running and the shares appear in
  /etc/dfs/sharetab, not that that is helping me.

  I've detailed a bunch of stuff at serverfault... if that's not good
  enough, I can bring some of it over here:

  http://serverfault.com/questions/797938/ubuntu-xenial-16-04-zfs-share-
  command-doesnt-work-for-smb-shares

  System/package informatiom

  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu12
Candidate: 0.6.5.6-0ubuntu12
Version table:
   *** 0.6.5.6-0ubuntu12 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu12
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 12:11:47 2016
  InstallationDate: Installed on 2016-05-26 (87 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.zfs: [modified]
  mtime.conffile..etc.default.zfs: 2016-07-12T22:45:19.830513

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1615405/+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 1754584] Re: zfs system process hung on container stop/delete

2019-05-31 Thread Bug Watch Updater
** Changed in: zfs
   Status: New => Fix Released

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

Title:
  zfs system process hung on container stop/delete

Status in Native ZFS for Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in zfs-linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request [Xenial][Artful] ==

  == Justification ==

  It is possible to hang zfs asynchronous reads if a read to a page that
  is mmap'd onto the the file being read is the same offset in the
  mapping as in the file. This is caused by two lock operations on the
  page.

  == Fix ==

  Upstream ZFS fix to ensure the page is not double-locked during async
  I/O of one or more pages.

  == Testing ==

  Create a zfs pool + zfs file system, run the reproducer program in
  comment #28 on the zfs filesystem.  Without the fix this can lock up,
  with the fix this runs to completion.

  == Regression Potential ==

  Minimal, the locking fix addresses a fundamental bug in the locking
  and this should not affect ZFS read/write I/O with this fix.

  --

  Summary:
  On a Bionic system running 4.15.0-10-generic, after attempting to build 
libaio in a Bionic daily container I cannot stop or delete the container. dmesg 
shows a variety of hung tasks

  Steps to Reproduce:
  Use the following script and watch for the the hang. At that point attempt to 
stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/

  Originally filed against LXD: https://github.com/lxc/lxd/issues/4314

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj2414 F pulseaudio
   /dev/snd/controlC0:  powersj2414 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 09:19:11 2018
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on 2018-02-19 (17 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
  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-10-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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
  ---
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj1878 F pulseaudio
   /dev/snd/controlC0:  powersj1878 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on 2018-02-19 (17 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 

[Kernel-packages] [Bug 1699804] Re: zfs fails on remount when using bind mounts

2019-05-31 Thread Bug Watch Updater
** Changed in: linux
   Status: New => Fix Released

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

Title:
  zfs fails on remount when using bind mounts

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

Bug description:
  When using a ZFS filesystem, if it is mounted and the bind-mounted,
  and then the original mount is unmounted, the bind mount will still be
  able to access the zfs filesystem contents, and zfs refuses to mount
  the original mount point.

  This is upstream zfs bug 5796:
  https://github.com/zfsonlinux/zfs/issues/5796

  Example repro steps (from upstream bug):

  zfs create tank/test
  zfs set mountpoint=/tank-test tank/test
  touch /tank-test/tank-test-file
  mount -B /tank-test /mnt
  zfs umount tank/test
  ls -al /tank-test/ (filesystem unmounted, file not found)
  ls -al /mnt (filesystem still referenced and file still found)
  zfs mount tank/test (will complain about dataset being mounted)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1699804/+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 1628553] Re: Ubuntu 16.04.1 Install zfsutils-linux Panic Error, endless loop

2019-05-31 Thread Bug Watch Updater
** Changed in: zfs
   Status: Unknown => Fix Released

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

Title:
  Ubuntu 16.04.1 Install zfsutils-linux Panic Error, endless loop

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  Fresh install of Ubuntu 16.04.1, installed all updates / upgrades for
  system before installing zfsutils-linux. The install processes all the
  way to Reached target Swap then has a PANIC error and loops endlessly.

  There is a zpool there already (was) with 3TB of data on it. This only
  happened after the system upgrade, so I reinstalled the boot drive /
  OS to see if it was just a issue with that, clearly it's an issue with
  the zfsutils-linux package for 16.04.1

  Package version installed zfsutils-linux 0.6.5.6-0ubuntu12

  Screenshot attached as I can't actually do anything once the boot gets
  to this stage:

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1628553/+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 1785912] Re: Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV

2019-05-30 Thread Bug Watch Updater
** Changed in: linux
   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/1785912

Title:
  Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo
  Ideapad 720s 13IKB 81BV

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

Bug description:
  Horrible screen flicker from login screen and after login.  18.04.1 LTS.
  I have two similar laptops, both Lenovo Ideapad 720s 13IKB,
  model 81A8 - Core i5 7200U - Intel HD Graphics 620 Rev 02 - works fine.
  model 81BV - Core i5 8250U - Intel UHD Graphics 620 Rev 07 - awful screen 
flashing.

  Neither have the problem in Windows (ie hardware fine)

  I installed the standard Ubuntu 18.04 on each of them (same USB Key,
  few weeks apart) but only the 81BV / 8th gen / UHD 620 Rev 07 has the
  problem.

  Flickering visible on video here:
  https://photos.app.goo.gl/HCN73q1nQfgstgVBA

  I've used ubuntu-bug so I believe you have all the details of the
  machine.  The install came straight from your standard 18.04 download.
  Any changes are due to me trying to fix this (not much prev exp of
  kernel params etc)

  Things tried but which didn't work were:
  - enable huc/guc (got it to load - it's now visible in the attached dmesg - 
but didn't help.)
  - enable_rc6=0 (just stopped sleep / resume working)
  - edp_vswing=2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Aug  7 23:09:14 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:39af]
  InstallationDate: Installed on 2018-08-06 (1 days ago)
  InstallationMedia: Ubuntu 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 0cf3:e500 Atheros Communications, Inc.
   Bus 001 Device 003: ID 5986:210d Acer, Inc
   Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81BV
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=10eb4e00-26e4-4f42-b983-9a603a658f89 ro i915.enable_guc=3 
i915.enable_guc_loading=1
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MCN27WW:bd05/02/2018:svnLENOVO:pn81BV:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB:
  dmi.product.family: ideapad 720S-13IKB
  dmi.product.name: 81BV
  dmi.product.version: Lenovo ideapad 720S-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1785912/+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 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

2019-05-29 Thread Bug Watch Updater
** Changed in: linux
   Status: In Progress => 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/1826125

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  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+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+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 1791405] Re: bluetooth always in discoverable mode (security issue)

2019-05-28 Thread Bug Watch Updater
** Changed in: gnome-bluetooth (Fedora)
   Status: Confirmed => Won't Fix

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

Title:
  bluetooth always in discoverable mode (security issue)

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  New
Status in gnome-bluetooth source package in Bionic:
  Fix Released
Status in bluez source package in Cosmic:
  New
Status in gnome-bluetooth source package in Cosmic:
  Fix Released
Status in bluez source package in Disco:
  New
Status in gnome-bluetooth source package in Disco:
  Fix Released
Status in bluez source package in Eoan:
  Fix Committed
Status in gnome-bluetooth package in Fedora:
  Won't Fix

Bug description:
  Excerpt from a similar report
  (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) :

  Opening the Bluetooth settings will make the device discoverable
  again, but does not make the device undiscoverable after the settings
  are closed (this is not intended behavior; devices should only be
  discoverable when the bluetooth settings UI is open).

  There seem to be a merge request :

  https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1

  Could you please merge it asap, it should be treated as a security
  issue IMHO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+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 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

2019-05-26 Thread Bug Watch Updater
** Changed in: linux
   Status: Incomplete => In Progress

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  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+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+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 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot

2019-05-22 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=101951.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-07-25T23:17:23+00:00 fraph24 wrote:

Created attachment 183641
kernel oops log

How to reproduce:
$ mkdir {lower,upper,work,overlay}
$ uname > lower/uname
# mount overlay -t overlay -o lowerdir=lower,upperdir=upper,workdir=work overlay
$ # edit overlay/uname

Results:
Kernel oops, screen freezes.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532145/comments/0


On 2015-09-17T15:22:21+00:00 rauter.gabriel wrote:

I have the same problem although i am using overlay while being in a docker 
container. Host fs is btrfs on arch linux kernel 4.2.0, guest docker image 
ubuntu:wily.
kernel oops log can be found here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496438/comments/2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532145/comments/1


On 2016-02-10T16:51:25+00:00 colin.king wrote:

I've debugged this a bit, the failure occurs on an atomic_inc on root,
when root is NULL, cf:

atomic_inc(>log_batch);

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532145/comments/11


On 2016-02-16T11:01:18+00:00 colin.king wrote:

bisected: 4bacc9c9234c7c8eec44f5ed4e960d9f96fa0f01 is the first bad
commit

commit 4bacc9c9234c7c8eec44f5ed4e960d9f96fa0f01
Author: David Howells 
Date: Thu Jun 18 14:32:31 2015 +0100

overlayfs: Make f_path always point to the overlay and f_inode to
the underlay

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532145/comments/15


On 2016-02-16T15:24:24+00:00 colin.king wrote:

The following stops the issue. I'm not sure if it is the correct fix
though.

diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
index 098bb8f..5e5df8b 100644
--- a/fs/btrfs/file.c
+++ b/fs/btrfs/file.c
@@ -1884,7 +1884,7 @@ static int start_ordered_ops(struct inode *inode, loff_t 
start, loff_t end)
 int btrfs_sync_file(struct file *file, loff_t start, loff_t end, int datasync)
 {
struct dentry *dentry = file->f_path.dentry;
-   struct inode *inode = d_inode(dentry);
+   struct inode *inode = file_inode(file);
struct btrfs_root *root = BTRFS_I(inode)->root;
struct btrfs_trans_handle *trans;
struct btrfs_log_ctx ctx;

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532145/comments/17


On 2016-02-16T15:41:10+00:00 colin.king wrote:


Commit 4bacc9c9234c7c8eec44f5ed4e960d9f96fa0f01 ("overlayfs: Make f_path
always point to the overlay and f_inode to the underlay") resulted in an
issue when using a combination of btrfs and overlayfs.  This is
noticeable when doing a fsync() on a file in a chroot with overlayfs on
top of btrfs; we hit a kernel oops in btrfs_sync_file() on
atomic_inc(>log_batch) because root is NULL.

I've debugged this further and found that in btrfs_sync_file():

struct inode *inode = d_inode(dentry);

does not return the inode I expected when using the stacked overlay fs,
where as:

struct inode *inode = file_inode(file);

does.

However, I'm not well at all well versed in btrfs, so I am not confident
this is a actually correct.  Any comments?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532145/comments/18


On 2019-05-21T12:33:42+00:00 dsterba wrote:

Fixed by de17e793b104d690e1d "btrfs: fix crash/invalid memory access on
fsync when using overlayfs", in 4.6.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532145/comments/23


** Changed in: linux
   Status: Unknown => Fix Released

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  Kernel Panic wrt btrfs while sbuild/schroot

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm running ubuntu Wily amd64 on a MSI Ghost Pro laptop.

  I'm running btrfs on top of a bcached dmraid setup(intel software
  raid0).

  I can't use sbuild, cause it crashes.

  I tried to use  a schroot env, and when updating it I got it to crash
  also.

  All the keyboard/mouse/X11 are stalled, but I could ssh to it.
  Trying to restart 

[Kernel-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

2019-05-21 Thread Bug Watch Updater
** Changed in: dri
   Status: Confirmed => Fix Released

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Fix Released
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1714178/+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 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

2019-05-19 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => Incomplete

** Changed in: linux
   Importance: Medium => Critical

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  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+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+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 1771431] Re: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer)

2019-05-18 Thread Bug Watch Updater
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1625415.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-09-04T21:44:00+00:00 hostacny.peter wrote:

+++ This bug was initially created as a clone of Bug #1521100 +++

Description of problem:

I bought new wireless keyboard for my Lenovo laptop (T470s) with mouse.
The mouse works, but the keyboard doesn't. Only keys "super" and "alt"
react on the keyboard. It is really pity, because i would like to use
it.

Strange is that the keyboard works in bios and in grub. Same problem I
have with Fedora 26.


>> dmesg
[  100.790513] usb 1-1: USB disconnect, device number 5
[  104.577088] usb 1-1: new full-speed USB device number 6 using xhci_hcd
[  104.749378] usb 1-1: New USB device found, idVendor=17ef, idProduct=60a9
[  104.749381] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[  104.749383] usb 1-1: Product: Lenovo Essential Wireless Keyboard and Mouse 
Combo
[  104.752210] input: Lenovo Essential Wireless Keyboard and Mouse Combo as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:17EF:60A9.0009/input/input23
[  104.804226] hid-generic 0003:17EF:60A9.0009: input,hidraw0: USB HID v1.11 
Keyboard [Lenovo Essential Wireless Keyboard and Mouse Combo] on 
usb-:00:14.0-1/input0
[  104.805579] input: Lenovo Essential Wireless Keyboard and Mouse Combo as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:17EF:60A9.000A/input/input24
[  104.805739] hid-generic 0003:17EF:60A9.000A: input,hidraw1: USB HID v1.11 
Mouse [Lenovo Essential Wireless Keyboard and Mouse Combo] on 
usb-:00:14.0-1/input1
[  104.806528] input: Lenovo Essential Wireless Keyboard and Mouse Combo as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.2/0003:17EF:60A9.000B/input/input25
[  104.858215] hid-generic 0003:17EF:60A9.000B: input,hidraw2: USB HID v1.11 
Device [Lenovo Essential Wireless Keyboard and Mouse Combo] on 
usb-:00:14.0-1/input2
[  104.859445] hid-generic 0003:17EF:60A9.000C: hiddev96,hidraw3: USB HID v1.11 
Device [Lenovo Essential Wireless Keyboard and Mouse Combo] on 
usb-:00:14.0-1/input3
[  114.566488] input input23: event field not found
[  114.630487] input input23: event field not found
[  114.854488] input input23: event field not found


>> lsusb 
Bus 001 Device 006: ID 17ef:60a9 Lenovo 


Version-Release number of selected component (if applicable):
kernel 4.13.16-202.fc26.x86_64

How reproducible:
always, except bios and grub

Steps to Reproduce:
1. use  Lenovo Essential Wireless Keyboard and Mouse Combo 

Actual results:
not work

Expected results:
keyboard and mouse work correctly in gnome-shell

--- Additional comment from Kari Hautio on 2018-01-08 03:51:47 EST ---

Same problem with
Lenovo keyboard and mouse combo (4X30H567)

lsusb:
  Bus 002 Device 004: ID 17ef:609b Lenovo 

The mouse works without issues but pressing any keys on keyboard will result in 
just
[ 1378.864283] input input12: event field not found
[ 1378.896265] input input12: event field not found
[ 1378.896270] input input12: event field not found
[ 1378.944333] input input12: event field not found

--- Additional comment from Pavel Studeník on 2018-01-10 10:02:39 EST
---

Maybe I found solution, but it didn't test.

https://github.com/y-trudeau/linux_lenovo_ultraslim_plus

--- Additional comment from Laura Abbott on 2018-02-20 15:00:09 EST ---

We apologize for the inconvenience.  There is a large number of bugs to go 
through and several of them have gone stale.  As kernel maintainers, we try to 
keep up with bugzilla but due the rate at which the upstream kernel project 
moves, bugs may be fixed without any indication to us. Due to this, we are 
doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  Please test this kernel 
update (or newer) and let us know if you issue has been resolved or if it is 
still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

--- Additional comment from Franz Brauneder on 2018-02-22 14:48:46 EST
---

Same problem with Lenovo keyboard and mouse combos (4X30M39472 and
4X30H56809).

The issue is still present in kernel version 4.15.3-300.fc27.

Maybe the information on this page can help.
https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/377873#377873

I also found a bugzilla entry on kernel.org that seems to handle the
same problem (https://bugzilla.kernel.org/show_bug.cgi?id=197787).

--- Additional comment from Pavel Studeník on 2018-05-06 10:06:17 EDT
---

I upgraded system to Fedora 28 and Kernel 4.16.6-302.fc28.x86_64 and the
issue is still not 

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

2019-05-16 Thread Bug Watch Updater
Launchpad has imported 36 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=108514.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-10-22T16:07:16+00:00 Werner-lueckel-m wrote:

my laptop: HP Compaq nx9420
my grafic card:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])
screen resolution: 1680x1050@60.1

when booting UBUNTU "14.04.5 LTS, Trusty Tahr" kernel 3.13.0-160-generic
-> the screen is fine in text-mode and in grafic-mode; NO flickering.
boot-messages say:
[drm] Initialized radeon 2.36.0 ...

BUT,
when booting UBUNTU "18.04.1 LTS (Bionic Beaver)" kernel 4.15.0-36-generic
-> the screen starts heavy flickering as soon as the kernel-module "radeon.ko"
is loaded. The flickering continues in grafic-mode.
here the boot-messages say:
[drm] Initialized radeon 2.50.0 ...
so: this seems to be a new version of radeon.ko.

My question:
- is there a method or a 'hidden flag' to switch radeon.ko-2.50 back to the
  good behaviour of radeon.ko-2.16?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/comments/8


On 2018-10-22T18:14:39+00:00 Alexdeucher wrote:

Any chance you can narrow down when the regression occurred and bisect
it using git?  Please attach your dmesg output and xorg log (if using
X).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/comments/9


On 2018-10-23T16:31:25+00:00 Werner-lueckel-m wrote:

Created attachment 142154
dmesg Ubuntu14.04, Kernel3.13.0-160, radeon 2.36.0, screen O.K.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/comments/10


On 2018-10-23T16:34:59+00:00 Werner-lueckel-m wrote:

Created attachment 142155
dmesg Ubuntu18.04, Kernel4.15.0-36, radeon 2.50.0, screen flickering

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/comments/11


On 2018-10-23T16:45:12+00:00 Werner-lueckel-m wrote:

- I attached 2 dmesg-listings;
  booting Ubuntu14.04, Kernel3.13 -> screen is o.k.; no flickering
  booting Ubuntu18.04, Kernel4.15 -> screen flickers.
- no Xorg log since the flickering happens already in text-mode
- I did the following test (on Ubuntu18.04):
  . boot with radeon.modeset=0 (thus: disable radeon driver)
-> screen o.k.; NO flickering
  . then sudo modprobe -v radeon modeset=1
-> and the flickering starts ...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/comments/12


On 2018-10-23T17:07:33+00:00 Werner-lueckel-m wrote:

Created attachment 142156
dmesg Ubuntu14.04, Kernel4.4.0-133, radeon 2.43.0, screen flickering

... and I found out that the screen-flickering already starts with
VERSION="14.04.5 LTS, Trusty Tahr"
kernel: 4.4.0-133-generic
radeon 2.43.0

see the attached dmesg14.04_4.4.0-133.txt

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/comments/13


On 2018-10-24T13:29:58+00:00 Werner-lueckel-m wrote:

Additional Information:

- I have the same flickering screen with

  Debian Life CD: UBCD-life
Linux version 3.16.0-4-586
[drm] Initialized radeon 2.39.0 20080528

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/comments/14


On 2018-10-30T15:54:54+00:00 Werner-lueckel-m wrote:

some more tests with different systems give the following table:

sorted by radeon-version
systemkernelradeon  result
- ---   
UBUNTU 14.04.5 LTS, Trusty Tahr   3.13.0-1612.36.0  O.K.
puppy_tahr 6.0.5  3.14.56   2.37.0  O.K.
puppy_slacko 6.3.23.14.55   2.37.0  O.K
UBCD  3.16.02.39.0  FLICKER
puppy_xenialpup 7.5   4.4.952.43.0  FLICKER
UBUNTU 14.04.5 LTS, Trusty Tahr   4.4.0-133 2.43.0  FLICKER
UBUNTU 18.04.1 LTS (Bionic Beaver)4.15.0-36 2.50.0  FLICKER

so the problem seems to start with a radeon.ko driver > 2.37.0;
I wonder how the radeon-version 2.38.0 would work, but, so far, I havn't 
found a system including it.


[Kernel-packages] [Bug 1816947] Re: [Dell XPS L321X] The touchpad doesn't work unless the cursor is moved slowly.

2019-05-03 Thread Bug Watch Updater
** Changed in: libinput
   Status: Unknown => 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/1816947

Title:
  [Dell XPS L321X] The touchpad doesn't work unless the cursor is moved
  slowly.

Status in libinput:
  New
Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touchpad doesn't work unless the cursor is moved slowly.

  WORKAROUND: Execute at a terminal:
  sudo modprobe -r psmouse
  sudo modprobe psmouse proto=imps

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.402
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 02:56:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  MachineType: Dell Inc. Dell System XPS L321X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.394
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  MachineType: Dell Inc. Dell System XPS L321X
  Package: libinput (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Tags:  bionic ubuntu
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  

[Kernel-packages] [Bug 1826645] Re: no sound in laptop ASUS UX362FA - sending repair

2019-04-27 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=203443.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-04-27T12:26:28+00:00 petr.nosek wrote:

Hi,

  I bought laptop ASUS UX362FA: https://www.asus.com/2-in-1-PCs/ASUS-
ZenBook-Flip-13-UX362FA/

  The sound didn't work. I was looking for solution and I found this
article: https://forum.manjaro.org/t/alc294-analog-audio-card-detected-
but-no-sound-internaly-or-headphones/54089/29

  
  So I added this line into 
(https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek.c):

  SND_PCI_QUIRK(0x1043, 0x13e1, "ASUS UX362FA", ALC294_FIXUP_ASUS_SPK),

  behind this line: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA",
ALC294_FIXUP_ASUS_SPK)


   And recompile kernel and it works. I'm sending this report for others, who 
have the same problem with this laptop version. Please add this repair to 
kernel for the others. 

  Thank you.


   

   my hwinfo:

root@zenbook:~$ hwinfo --sound
15: PCI 1f.3: 0403 Audio device 
  [Created at pci.378]
  Unique ID: nS1_.jsQALdVXpeB
  SysFS ID: /devices/pci:00/:00:1f.3
  SysFS BusID: :00:1f.3
  Hardware Class: sound
  Model: "Intel Audio device"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x9dc8 
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x13e1 
  Revision: 0x30
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xb1218000-0xb121bfff (rw,non-prefetchable)
  Memory Range: 0xb100-0xb10f (rw,non-prefetchable)
  IRQ: 127 (100 events)
  Module Alias: "pci:v8086d9DC8sv1043sd13E1bc04sc03i80"
  Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
  Driver Info #1:
Driver Status: snd_soc_skl is active
Driver Activation Cmd: "modprobe snd_soc_skl"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645/comments/0


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  no sound in laptop ASUS UX362FA - sending repair

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

Bug description:
  Hi,

I bought laptop ASUS UX362FA: https://www.asus.com/2-in-1-PCs/ASUS-
  ZenBook-Flip-13-UX362FA/

The sound didn't work. I was looking for solution and I found this
  article: https://forum.manjaro.org/t/alc294-analog-audio-card-
  detected-but-no-sound-internaly-or-headphones/54089/29


So I added this line into 
(https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek.c):

SND_PCI_QUIRK(0x1043, 0x13e1, "ASUS UX362FA",
  ALC294_FIXUP_ASUS_SPK),

behind this line: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA",
  ALC294_FIXUP_ASUS_SPK)

  
 And recompile kernel and it works. I'm sending this report for others, who 
have the same problem with this laptop version. Please add this repair to 
kernel for the others. 

Thank you.

  
 

 my hwinfo:

  root@zenbook:~$ hwinfo --sound
  15: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.jsQALdVXpeB
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x9dc8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x13e1 
Revision: 0x30
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xb1218000-0xb121bfff (rw,non-prefetchable)
Memory Range: 0xb100-0xb10f (rw,non-prefetchable)
IRQ: 127 (100 events)
Module Alias: "pci:v8086d9DC8sv1043sd13E1bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826645/+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 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

2019-04-25 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=110511.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-04-25T10:24:02+00:00 Paulo Matos wrote:

Created attachment 144092
dmesg from boot

This was previously reported here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826125

Brand new XPS 13 9380 arrived a couple of days ago from Dell with Ubuntu
18.04 preinstalled.

Flickering started immediatelly post boot and it was constant.
I updated BIOS from 1.1.1 to 1.2.1, tried i915.fastboot and i915.enable_rc6 
combinations to no avail. 

Updated to Ubuntu 19.04 and kernel-5 to no avail. However flickering
changed from constant to only if there's a screen refresh.

Videos pre kernel 5:
https://photos.app.goo.gl/1PkL2HrjMBP41aML9
https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6

Videos post kernel 5:
https://photos.app.goo.gl/tpmTGWVJXpChoERz6

I attach dmesg from boot.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826125/comments/33


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  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+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+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 1730069] Re: kernel 4.10 fails to boot on AMD E-350D APU

2019-04-23 Thread Bug Watch Updater
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=197895.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-11-16T15:00:18+00:00 kernel.9566d wrote:

I have a GA-E350N-WIN8 gigabyte motherboard, after kernel commit
9479c7cebfb568f8b8b424be7f1cac120e9eea95 the amd64 kernel no longer
boots (commit ab72a27da4c6c19b0e3d6d7556fdd4afb581c8ac) works.

This bug was found with ubuntu and reported at:
https://bugs.launchpad.net/bugs/1730069

Wit the broken kernel, ubuntu wont book, the screen just stays blank.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730069/comments/28


On 2019-04-23T00:57:03+00:00 mail+kernel-bugzilla wrote:

I can confirm this bug on different hardware (a Chromebook Samsung
500C).

It, too, gets a black screen on boot.

My kernel bisection has also identified this as the first bad commit:

9479c7cebfb568f8b8b424be7f1cac120e9eea95 is the first bad commit
commit 9479c7cebfb568f8b8b424be7f1cac120e9eea95
Author: Matt Fleming 
Date:   Fri Feb 26 21:22:05 2016 +

efi: Refactor efi_memmap_init_early() into arch-neutral code

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730069/comments/30


On 2019-04-23T01:03:59+00:00 mail+kernel-bugzilla wrote:

I can also add that when the kernel is started via kexec instead of via
normal hardware boot, the problem does not occur.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730069/comments/32


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  kernel 4.10 fails to boot on AMD E-350D APU

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

Bug description:
  I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8
  motherboard). This has always worked fine until the kernel was
  upgraded to 4.10 as part of the regular system upgrades. Since then
  the machine wont boot, there are no errors, the screen just stays
  blank. If I boot using a previous kernel (such as 4.8.0-58-generic)
  then it all works fine.

  As of the 7th of Nov 2017, all the linux kernels above 4.8 that I have
  tried have failed, currently this includes:

  linux-image-4.10.0-30-generic
  linux-image-4.10.0-32-generic
  linux-image-4.10.0-33-generic
  linux-image-4.10.0-38-generic
  linux-image-4.13.0-16-generic

  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pim1369 F pulseaudio
   /dev/snd/controlC0:  pim1369 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=46570214-98e0-4bad-9e3c-51fd31c04b18
  InstallationDate: Installed on 2017-03-11 (238 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=screen
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed 
root=UUID=25808329-ef64-4a67-960f-6140c5610dd4 ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-58-generic N/A
   linux-backports-modules-4.8.0-58-generic  N/A
   linux-firmware1.157.13
  RfKill:

  Tags:  xenial
  Uname: Linux 4.8.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: E350N WIN8
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Kernel-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend

2019-04-18 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 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))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  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.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1809407/+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 1651199] Re: 16.04 - Kernel panic on docker server

2019-04-18 Thread Bug Watch Updater
** Changed in: linux
   Status: New => Fix Released

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

Title:
  16.04 - Kernel panic on docker server

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  [31016.057405] BUG: unable to handle kernel paging request at 82c4801e6bda
  [31016.061249] IP: [] __xen_evtchn_do_upcall+0x43/0x80
  [31016.061380] PGD 0 
  [31016.061380] Oops: 0010 [#1] SMP 
  [31016.061380] Modules linked in: binfmt_misc xt_REDIRECT nf_nat_redirect 
veth xt_comment xt_mark ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user 
xfrm_algo xt_addrtype iptable_filter xt_conntrack br_netfilter bridge stp llc 
overlay xt_nat xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables isofs ppdev serio_raw 
parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd ixgbevf psmouse floppy
  [31016.061380] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.0-53-generic 
#74-Ubuntu
  [31016.061380] Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016
  [31016.061380] task: 880406496040 ti: 8804064e task.ti: 
8804064e
  [31016.061380] RIP: 0010:[]  [] 
__xen_evtchn_do_upcall+0x43/0x80
  [31016.061380] RSP: 0018:88040fc43f78  EFLAGS: 00010082
  [31016.061380] RAX:  RBX: 88040fc4b840 RCX: 
0001
  [31016.061380] RDX: fffe RSI: 000123a0 RDI: 
88040fc43f30
  [31016.061380] RBP: 88040fc43f90 R08: f24a R09: 
0001
  [31016.061380] R10: 0001 R11:  R12: 
0001
  [31016.061380] R13: 0003 R14:  R15: 
8804064e
  [31016.178419] FS:  () GS:88040fc4() 
knlGS:
  [31016.178419] CS:  0010 DS:  ES:  CR0: 80050033
  [31016.178419] CR2: 82c4801e6bda CR3: 000204f2f000 CR4: 
001406e0
  [31016.178419] DR0:  DR1:  DR2: 

  [31016.178419] DR3:  DR6: fffe0ff0 DR7: 
0400
  [31016.178419] Stack:
  [31016.178419]   0003  
88040fc43fa8
  [31016.178419]  814d6bc0 81f36a00 8804064e3e90 
81837f32
  [31016.178419]  8804064e3de8   8804064e  

  [31016.178419] Call Trace:
  [31016.178419]   
  [31016.178419]  [] xen_evtchn_do_upcall+0x30/0x40
  [31016.178419]  [] xen_hvm_callback_vector+0x82/0x90
  [31016.178419]   
  [31016.178419]  [] ? native_safe_halt+0x6/0x10
  [31016.178419]  [] default_idle+0x1e/0xe0
  [31016.239315]  [] arch_cpu_idle+0xf/0x20
  [31016.239899]  [] default_idle_call+0x2a/0x40
  [31016.239899]  [] cpu_startup_entry+0x2f1/0x350
  [31016.239899]  [] start_secondary+0x154/0x190
  [31016.239899] Code: 01 00 00 00 65 44 8b 2d dc 56 b3 7e c6 03 00 44 89 e0 65 
0f c1 05 2e d8 b3 7e 85 c0 75 35 48 8b 05 63 ce d0 00 44 89 ef ff 50 50 <9c> 58 
0f 1f 44 00 00 f6 c4 02 75 23 65 8b 05 0a d8 b3 7e 65 c7 
  [31016.239899] RIP  [] __xen_evtchn_do_upcall+0x43/0x80
  [31016.239899]  RSP 
  [31016.239899] CR2: 82c4801e6bda
  [31016.239899] ---[ end trace 5b3e8ea32013e327 ]---
  [31016.239899] Kernel panic - not syncing: Fatal exception in interrupt
  [31016.239899] Kernel Offset: disabled

  
  We believe this appeared in the last 1-2mo of releases, since this started 
happening after we did a `apt-get upgrade` on our machines after a bit of a 
pause. These are EC2 m4.xlarge servers running Ubuntu 16.04.1. They are 
Kubernetes minions, so I assume docker is likely the trigger.

  Unfortunately there aren't really any interesting logs in journalctl
  from the previous boot prior to the panic.

  Let me know what I can do to debug further.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 19 15:56 seq
   crw-rw 1 root audio 116, 33 Dec 19 15:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: 

[Kernel-packages] [Bug 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but

2019-04-16 Thread Bug Watch Updater
** Changed in: linux
   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/1822441

Title:
  [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports
  "(EE) modeset(0): failed to set mode: Invalid argument" when using
  kernel 4.19.26 and later (but 4.19.25 and earlier works)

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Updated from kubuntu 18.10 to 19.04 beta without problems. After first
  reboot, first the kubuntu logo, then just a blank screen, no login
  screen. Switching to console and log in there possible. All seems
  fine, including wlan etc.

  systemd status sddm says sddm is running, any attempt to start KDE
  (including startkde) however fails with "could not connect to any x
  display".

  This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the
  login screen comes up and all is fine.

  Anything I can contribute?

  Description:Ubuntu Disco Dingo (development branch)
  Release:19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Mar 30 21:51:04 2019
  DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed
   tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
  InstallationDate: Installed on 2017-07-07 (631 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 78545HG
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L420
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/linux/+bug/1822441/+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 1790181] Re: /proc/diskstats shows weird values

2019-04-15 Thread Bug Watch Updater
** Changed in: debian
   Status: Unknown => 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/1790181

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed
Status in Debian:
  New

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

2019-04-10 Thread Bug Watch Updater
** Bug watch added: freedesktop.org Bugzilla #110360
   https://bugs.freedesktop.org/show_bug.cgi?id=110360

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

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

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1747463/+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 1729051] Re: dkms mkdeb fails: Can't find package

2019-04-10 Thread Bug Watch Updater
** Changed in: dkms (Debian)
   Status: New => Fix Released

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

Title:
  dkms mkdeb fails: Can't find package

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Artful:
  New
Status in dkms package in Debian:
  Fix Released

Bug description:
  For some reason, the Debian version of dkms mkdeb tries to generate a
  .deb package with the current arch as a suffix in its name, instead of
  'all'. However, since the control file wasn't properly set up, the
  .deb file will have the 'all' suffix and dkms mkdeb will fail.

  This bug is also present in Ubuntu. I added a patch to the original
  Debian bug report, here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558

  but since the original bug report was made about a year ago and nobody
  cared, I'm hoping that someone will at least fix this for Ubuntu.

  The patch looks like this:

  --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:40:41.690069116 -0300
  +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:41:12.137973994 -0300
  @@ -6,6 +6,6 @@
   Standards-Version: 3.8.1

   Package: DEBIAN_PACKAGE-dkms
  -Architecture: all
  +Architecture: DEBIAN_BUILD_ARCH
   Depends: dkms (>= 1.95), ${misc:Depends}
   Description: DEBIAN_PACKAGE driver in DKMS format.

  I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1729051/+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 1423672] Re: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y

2019-04-09 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=104571.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-09-15T08:10:58+00:00 linux-ext4 wrote:

This bug report is about ext4 metadata corruption on large (>=10TB) ext4 
volumes.
This was also reported in 2014 [ 
http://marc.info/?l=linux-ext4=139878494527370=2 ]

I'm getting sporadic FS errors like this one:
(More of these i've pasted at https://8n1.org/10745/cc34)

|  EXT4-fs error (device vdb): ext4_mb_generate_buddy:757:
|   group 79842, block bitmap and bg descriptor inconsistent: 10073 vs 10071
|   free clusters
| Aborting journal on device vdb-8.

An e2fsck run then shows:
| Pass 5: Checking group summary information
| Block bitmap differences:  +(2616281446--2616281447)
| Free blocks count wrong (170942497, counted=129906218).
| Free inodes count wrong (670863012, counted=670860975).

I've patched my kernel with WARN_ON(1); inserted in tactical places and caught
one such situation:

| EXT4-fs (vdb): pa 880016544888: logic 982168, phys. 2469410748, len 104
| EXT4-fs error (device vdb): ext4_mb_release_inode_pa:3773: group 75360, free 
38, pa_free 36
| Aborting journal on device vdb-8.
| EXT4-fs (vdb): Remounting filesystem read-only
| [ cut here ]
| WARNING: CPU: 1 PID: 1706 at fs/ext4/mballoc.c:3774 
ext4_mb_release_inode_pa.isra.27+0x1cb/0x2c0()
| Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter xt_tcpudp 
ip6_tables
| nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter 
ip_tables
| x_tables cirrus ttm drm_kms_helper drm kvm_intel kvm ppdev syscopyarea 
sysfillrect
| 8250_fintek serio_raw i2c_piix4 sysimgblt pvpanic parport_pc mac_hid nfsd 
auth_rpcgss nfs_acl
| lockd grace sunrpc lp parport autofs4 psmouse floppy pata_acpi
| CPU: 1 PID: 1706 Comm: deluged Not tainted 3.19.8-ckt4 #1
| Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
|  81ab4fef 8800da1bb978 817c3760 0007
|   8800da1bb9b8 8107696a 8800da1bb9a8
|  0026 3825 3824 880016544888
| Call Trace:
|  [] dump_stack+0x45/0x57
|  [] warn_slowpath_common+0x8a/0xc0
|  [] warn_slowpath_null+0x1a/0x20
|  [] ext4_mb_release_inode_pa.isra.27+0x1cb/0x2c0
|  [] ? ext4_read_block_bitmap_nowait+0x26f/0x5f0
|  [] ext4_discard_preallocations+0x30a/0x490
|  [] ext4_da_update_reserve_space+0x178/0x1b0
|  [] ext4_ext_map_blocks+0xcd9/0xe50
|  [] ext4_map_blocks+0x129/0x570
|  [] ? ext4_writepages+0x35d/0xca0
|  [] ? __ext4_journal_start_sb+0x69/0xe0
|  [] ext4_writepages+0x582/0xca0
|  [] do_writepages+0x1e/0x30
|  [] __filemap_fdatawrite_range+0x59/0x60
|  [] filemap_write_and_wait+0x2c/0x60
|  [] do_vfs_ioctl+0x3fd/0x4e0
|  [] SyS_ioctl+0x81/0xa0
|  [] system_call_fastpath+0x16/0x1b
| ---[ end trace c7de4d0d78cb95b6 ]---
| EXT4-fs error (device vdb) in ext4_writepages:2412: IO failure
| EXT4-fs (vdb): ext4_writepages: jbd2_start: 9223372036854775751 pages, ino 
84149503; err -30

After this, the system started logging a lot of this same message:
| EXT4-fs error (device vdb): ext4_find_extent:900: inode #84149503: comm 
deluged: 
|pblk 225181822 bad header/extent: invalid magic - magic 53fd, entries 
37907,
|max 27407(0), depth 50401(0)

Ran e2fsck and got:
| Pass 5: Checking group summary information
| Block bitmap differences:   +(1431556444--1431556445) +(2469410748-2469410749)
| Free blocks count wrong (134030133, counted=57970467).
| Free inodes count wrong (670746893, counted=670746452).

Which is usually the same output for fsck in these situations.

This server is a QEMU KVM virtual machine running on Intel x64 hardware.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672/comments/34


On 2015-09-28T08:04:48+00:00 linux-ext4 wrote:

Hit by this bug again:

| EXT4-fs error (device vdb): ext4_mb_generate_buddy:757: group 76916,
|block bitmap and bg descriptor inconsistent: 959 vs 957 free
|clusters
| Aborting journal on device vdb-8.
| EXT4-fs (vdb): Remounting filesystem read-only
| [ cut here ]
| WARNING: CPU: 0 PID: 5000 at fs/ext4/mballoc.c:758
|ext4_mb_generate_buddy+0x1fa/0x340()
| Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs
|msdos jfs xfs libcrc32c xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6
|ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack
|nf_conntrack iptable_filter ip_tables x_tables cirrus ttm drm_kms_helper
|drm kvm_intel kvm ppdev syscopyarea sysfillrect serio_raw pvpanic
|sysimgblt 8250_fintek 

[Kernel-packages] [Bug 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but

2019-04-09 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=110359.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-04-08T18:31:21+00:00 Torsten Römer wrote:

Created attachment 143902
Xorg Log containing the error

Since kernel 4.19.26 and later (4.19.25 and earlier works), with Intel
integrated graphics i915 (Intel® HD Graphics 3000), Xorg fails to start
with: "(EE) modeset(0): failed to set mode: Invalid argument".

After reverting https://patchwork.freedesktop.org/series/58893/ (commit
d179b88deb3bf6fed4991a31fd6f0f2cad21fab5 upstream kernel drm/i915/fbdev)
and rebuilding default disco kernel 5.0.0-8-generic everything works as
expected.

This bug was initially reported as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441

Possible duplicate: https://bugs.freedesktop.org/show_bug.cgi?id=109174

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/comments/10


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => High

** Bug watch added: freedesktop.org Bugzilla #109174
   https://bugs.freedesktop.org/show_bug.cgi?id=109174

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

Title:
  [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports
  "(EE) modeset(0): failed to set mode: Invalid argument" when using
  kernel 4.19.26 and later (but 4.19.25 and earlier works)

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

Bug description:
  Updated from kubuntu 18.10 to 19.04 beta without problems. After first
  reboot, first the kubuntu logo, then just a blank screen, no login
  screen. Switching to console and log in there possible. All seems
  fine, including wlan etc.

  systemd status sddm says sddm is running, any attempt to start KDE
  (including startkde) however fails with "could not connect to any x
  display".

  This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the
  login screen comes up and all is fine.

  Anything I can contribute?

  Description:Ubuntu Disco Dingo (development branch)
  Release:19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Mar 30 21:51:04 2019
  DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed
   tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
  InstallationDate: Installed on 2017-07-07 (631 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 78545HG
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L420
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1804028] Re: Surface Go - QCA6174 wifi card not correctly recognized and therefore not working

2019-04-09 Thread Bug Watch Updater
** Changed in: linux-firmware (Fedora)
   Status: Fix Committed => Fix Released

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

Title:
  Surface Go - QCA6174 wifi card not correctly recognized and therefore
  not working

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware package in Fedora:
  Fix Released

Bug description:
  Output of dmesg on Surface Go fresh installed Ubuntu 18.10.

  "[ 4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 168c:3370
  [ 4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
  [ 4.243006] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 4.308059] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 
from ath10k/QCA6174/hw3.0/board-2.bin
  [ 4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a"

  There is a board.bin available directly from the vendor
  http://www.killernetworking.com/support/K1535_Debian/board.bin

  The only thing which is missing is getting this added to
  https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles so
  the official board-2.bin. My problem is that I dont know how to read
  the board files and modify them because I do not know the encoding
  they use.

  Also there have been some updates in the upstream linux-firmware repo.
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336 and
  https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0 but
  they also do not help to get the wifi card working/recognized.

  Any ideas how to get this solved?

  Also there is a guide how to port it to Linux
  https://developer.qualcomm.com/download/qca9377/wlan-bluetooth-linux-
  porting-guide.pdf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1804028/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

2019-04-04 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=110187.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-03-19T06:49:42+00:00 Timo Aaltonen wrote:

This bug is filed to monitor the progress on getting this patchset
upstream:

https://patchwork.freedesktop.org/series/55415/

one use case for it is to be able to set up a 3x4k horizontal monitor
configuration for X.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1714178/comments/61


** Changed in: dri
   Status: Unknown => Confirmed

** Changed in: dri
   Importance: Unknown => Medium

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Confirmed
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Kernel-packages] [Bug 1328727] Re: [Asus 1000HE] s2disk/hibernate hangs during saving of image data

2019-04-03 Thread Bug Watch Updater
Launchpad has imported 29 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=75101.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-04-29T20:13:44+00:00 oliverml1 wrote:

Created attachment 134271
Full console trace with various SysRq outputs

Since v3.14 under normal desktop usage my s2disk/hibernate often blocks
on the saving of the image data ("Saving 506031 image data pages ()
...").

With following test I can reproduce the problem reliably:
---
0) Boot

1) Fill ram with 2GiB (+50% in my case)

mount -t tmpfs tmpfs /media/test/
dd if=/dev/zero of=/media/test/test0.bin bs=1k count=$[1024*1024]
dd if=/dev/zero of=/media/test/test1.bin bs=1k count=$[1024*1024]

2) Do s2disk

s2disk

---
s2disk: Unable to switch virtual terminals, using the current console.
s2disk: Snapshotting system
s2disk: System snapshot ready. Preparing to write
s2disk: Image size: 2024124 kilobytes
s2disk: Free swap: 3791208 kilobytes
s2disk: Saving 506031 image data pages (press backspace to abort) ...   0%

#Problem>: ... there is stays and blocks. SysRq still responds, so that I could 
trigger various debug outputs.
---

I've bisected this to following commit:
---
commit a1c3bfb2f67ef766de03f1f56bdfff9c8595ab14 (HEAD, refs/bisect/bad)
Author: Johannes Weiner 
Date:   Wed Jan 29 14:05:41 2014 -0800

mm/page-writeback.c: do not count anon pages as dirtyable memory

[...]
---

Reverting a1c3bfb2 fixes s2disk for me again - so basically I'm ok ;).
But maybe there is still another better solution.

Attached is a full console trace with various SysRq outputs, possibly
useful for analyzing.

BR, Oliver

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/comments/0


On 2014-04-29T20:20:21+00:00 oliverml1 wrote:

Arch: x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/comments/1


On 2014-04-29T22:24:41+00:00 akpm wrote:

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Tue, 29 Apr 2014 20:13:44 + bugzilla-dae...@bugzilla.kernel.org
wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=75101
> 
> Bug ID: 75101
>Summary: [bisected] s2disk / hibernate blocks on "Saving 506031
> image data pages () ..."
>Product: Memory Management
>Version: 2.5
> Kernel Version: v3.14
>   Hardware: All
> OS: Linux
>   Tree: Mainline
> Status: NEW
>   Severity: normal
>   Priority: P1
>  Component: Other
>   Assignee: a...@linux-foundation.org
>   Reporter: oliver...@oli1170.net
> Regression: No
> 
> Created attachment 134271
>   --> https://bugzilla.kernel.org/attachment.cgi?id=134271=edit
> Full console trace with various SysRq outputs
> 
> Since v3.14 under normal desktop usage my s2disk/hibernate often blocks on
> the
> saving of the image data ("Saving 506031 image data pages () ...").

A means to reproduce as well as a bisection result.  Nice!  Thanks.

Johannes, could you please take a look?

> With following test I can reproduce the problem reliably:
> ---
> 0) Boot
> 
> 1) Fill ram with 2GiB (+50% in my case)
> 
> mount -t tmpfs tmpfs /media/test/
> dd if=/dev/zero of=/media/test/test0.bin bs=1k count=$[1024*1024]
> dd if=/dev/zero of=/media/test/test1.bin bs=1k count=$[1024*1024]
> 
> 2) Do s2disk 
> 
> s2disk
> 
> ---
> s2disk: Unable to switch virtual terminals, using the current console.
> s2disk: Snapshotting system
> s2disk: System snapshot ready. Preparing to write
> s2disk: Image size: 2024124 kilobytes
> s2disk: Free swap: 3791208 kilobytes
> s2disk: Saving 506031 image data pages (press backspace to abort) ...   0%
> 
> #Problem>: ... there is stays and blocks. SysRq still responds, so that I
> could
> trigger various debug outputs.
> ---
> 
> I've bisected this to following commit:
> ---
> commit a1c3bfb2f67ef766de03f1f56bdfff9c8595ab14 (HEAD, refs/bisect/bad)
> Author: Johannes Weiner 
> Date:   Wed Jan 29 14:05:41 2014 -0800
> 
> mm/page-writeback.c: do not count anon pages as dirtyable memory
> 
> [...]
> ---
> 
> Reverting a1c3bfb2 fixes s2disk for me again - so basically I'm ok ;). But
> maybe there is still another better solution.
> 
> Attached is a full console trace with various SysRq outputs, possibly useful
> for analyzing.
> 
> BR, Oliver
>

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/comments/2


On 2014-05-05T15:35:51+00:00 

[Kernel-packages] [Bug 1626731] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!

2019-03-30 Thread Bug Watch Updater
Launchpad has imported 20 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=111291.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-01-25T19:46:19+00:00 caravena wrote:

Created attachment 201651
dmesg_4.5.0-040500rc1-generic.txt

[6.362067] uvcvideo: Found UVC 1.00 device WebCam SC-13HDL12131N (2232:1035)
[6.388720] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not 
initialized!
[6.388729] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not 
initialized!
[6.388734] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not 
initialized!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731/comments/0


On 2016-01-25T19:46:49+00:00 caravena wrote:

Created attachment 201671
lspci_-vvnn.txt

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731/comments/1


On 2016-01-29T18:47:26+00:00 jani.nikula wrote:

This is about USB Video Class, not Intel graphics. Not sure where to
reassign really, setting Video(Other) and adding some Cc's.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731/comments/2


On 2016-02-01T18:01:19+00:00 caravena wrote:

Created attachment 202651
dmesg_4.5.0-040500rc2-generic.txt

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731/comments/3


On 2016-04-15T06:01:12+00:00 arthurborsboom wrote:

After upgrading from kernel 4.4.5 to 4.5.0 the following kernel messages
appeared on my system too.

[2.517311] usbcore: registered new interface driver snd-usb-audio
[2.517340] uvcvideo: Found UVC 1.00 device  (046d:0807)
[2.532997] uvcvideo 3-10:1.0: Entity type for entity Extension 4 was not 
initialized!
[2.532999] uvcvideo 3-10:1.0: Entity type for entity Extension 8 was not 
initialized!
[2.533000] uvcvideo 3-10:1.0: Entity type for entity Extension 10 was not 
initialized!
[2.533002] uvcvideo 3-10:1.0: Entity type for entity Extension 12 was not 
initialized!
[2.533003] uvcvideo 3-10:1.0: Entity type for entity Extension 11 was not 
initialized!
[2.533004] uvcvideo 3-10:1.0: Entity type for entity Processing 2 was not 
initialized!
[2.533005] uvcvideo 3-10:1.0: Entity type for entity Extension 13 was not 
initialized!
[2.533006] uvcvideo 3-10:1.0: Entity type for entity Camera 1 was not 
initialized!
[2.533007] uvcvideo 3-10:1.0: Entity type for entity Extension 14 was not 
initialized!
[2.533088] input: UVC Camera (046d:0807) as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/input/input20
[2.533156] usbcore: registered new interface driver uvcvideo

The webcam does work in an application i have tested.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731/comments/4


On 2016-04-15T06:09:27+00:00 arthurborsboom wrote:

Created attachment 212791
Complete kernel log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731/comments/5


On 2016-04-15T06:10:30+00:00 arthurborsboom wrote:

Created attachment 212801
Information about the USB webcam causing the warning

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731/comments/6


On 2016-09-11T09:47:45+00:00 mattia.b89 wrote:

I have this issue too! The webcam affected is the integrated one in my laptop, 
a Dell XPS 13 (9343).
If you need any other information, just ask

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731/comments/7


On 2016-09-22T20:41:15+00:00 caravena wrote:

4.8.0-14-generic:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731/comments/11


On 2016-09-30T10:45:38+00:00 laurent.pinchart+bugzilla-kernel wrote:

This is a known issue, caused by

commit b50bde4e476dede4a28e9c8fdcd134da2f34ef2e
Author: Mauro Carvalho Chehab 
Date:   Thu May 7 22:12:38 2015 -0300

[media] v4l2-subdev: use MEDIA_ENT_T_UNKNOWN for new subdevs

Instead of abusing MEDIA_ENT_T_V4L2_SUBDEV, initialize
new subdev entities as MEDIA_ENT_T_UNKNOWN.

Acked-by: Hans Verkuil 
Signed-off-by: 

[Kernel-packages] [Bug 1628238] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!

2019-03-30 Thread Bug Watch Updater
Launchpad has imported 20 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=111291.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-01-25T19:46:19+00:00 caravena wrote:

Created attachment 201651
dmesg_4.5.0-040500rc1-generic.txt

[6.362067] uvcvideo: Found UVC 1.00 device WebCam SC-13HDL12131N (2232:1035)
[6.388720] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not 
initialized!
[6.388729] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not 
initialized!
[6.388734] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not 
initialized!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628238/comments/0


On 2016-01-25T19:46:49+00:00 caravena wrote:

Created attachment 201671
lspci_-vvnn.txt

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628238/comments/1


On 2016-01-29T18:47:26+00:00 jani.nikula wrote:

This is about USB Video Class, not Intel graphics. Not sure where to
reassign really, setting Video(Other) and adding some Cc's.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628238/comments/2


On 2016-02-01T18:01:19+00:00 caravena wrote:

Created attachment 202651
dmesg_4.5.0-040500rc2-generic.txt

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628238/comments/3


On 2016-04-15T06:01:12+00:00 arthurborsboom wrote:

After upgrading from kernel 4.4.5 to 4.5.0 the following kernel messages
appeared on my system too.

[2.517311] usbcore: registered new interface driver snd-usb-audio
[2.517340] uvcvideo: Found UVC 1.00 device  (046d:0807)
[2.532997] uvcvideo 3-10:1.0: Entity type for entity Extension 4 was not 
initialized!
[2.532999] uvcvideo 3-10:1.0: Entity type for entity Extension 8 was not 
initialized!
[2.533000] uvcvideo 3-10:1.0: Entity type for entity Extension 10 was not 
initialized!
[2.533002] uvcvideo 3-10:1.0: Entity type for entity Extension 12 was not 
initialized!
[2.533003] uvcvideo 3-10:1.0: Entity type for entity Extension 11 was not 
initialized!
[2.533004] uvcvideo 3-10:1.0: Entity type for entity Processing 2 was not 
initialized!
[2.533005] uvcvideo 3-10:1.0: Entity type for entity Extension 13 was not 
initialized!
[2.533006] uvcvideo 3-10:1.0: Entity type for entity Camera 1 was not 
initialized!
[2.533007] uvcvideo 3-10:1.0: Entity type for entity Extension 14 was not 
initialized!
[2.533088] input: UVC Camera (046d:0807) as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/input/input20
[2.533156] usbcore: registered new interface driver uvcvideo

The webcam does work in an application i have tested.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628238/comments/4


On 2016-04-15T06:09:27+00:00 arthurborsboom wrote:

Created attachment 212791
Complete kernel log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628238/comments/5


On 2016-04-15T06:10:30+00:00 arthurborsboom wrote:

Created attachment 212801
Information about the USB webcam causing the warning

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628238/comments/6


On 2016-09-11T09:47:45+00:00 mattia.b89 wrote:

I have this issue too! The webcam affected is the integrated one in my laptop, 
a Dell XPS 13 (9343).
If you need any other information, just ask

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628238/comments/7


On 2016-09-22T20:41:15+00:00 caravena wrote:

4.8.0-14-generic:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626731

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628238/comments/8


On 2016-09-30T10:45:38+00:00 laurent.pinchart+bugzilla-kernel wrote:

This is a known issue, caused by

commit b50bde4e476dede4a28e9c8fdcd134da2f34ef2e
Author: Mauro Carvalho Chehab 
Date:   Thu May 7 22:12:38 2015 -0300

[media] v4l2-subdev: use MEDIA_ENT_T_UNKNOWN for new subdevs

Instead of abusing MEDIA_ENT_T_V4L2_SUBDEV, initialize
new subdev entities as MEDIA_ENT_T_UNKNOWN.

Acked-by: Hans Verkuil 
Signed-off-by: 

[Kernel-packages] [Bug 1686048] Re: Touchpad not detected on Lenovo S21e-20

2019-03-29 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => Fix Released

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

Title:
  Touchpad not detected on Lenovo S21e-20

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

Bug description:
  xinput list
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳  USB OPTICAL MOUSEid=9[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)]
  ↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)]
  ↳ Lenovo EasyCamera

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

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

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

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

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

  I: Bus=0003 Vendor=15d9 Product=0a4c Version=0111
  N: Name=" USB OPTICAL MOUSE"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:15D9:0A4C.0001/input/input5
  U: Uniq=
  H: Handlers=mouse0 event5 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=103
  B: MSC=10

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

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

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

  I: Bus=0003 Vendor=5986 Product=0674 Version=4207
  N: Name="Lenovo EasyCamera"
  P: Phys=usb-:00:14.0-3/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/input/input9
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1146 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Apr 25 11:15:33 2017
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 105b:e065 Foxconn 

[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2019-03-27 Thread Bug Watch Updater
** Changed in: linux
   Importance: High => Medium

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

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  Updated docking station firmware to latest 2.33.00.

  PC temperatures are normal as per lm-sensors.

  20171109 - Not reproducible testing drm-tip for 1.5 days.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1727662/+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 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2019-03-23 Thread Bug Watch Updater
** Changed in: linux
   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/1727662

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  Updated docking station firmware to latest 2.33.00.

  PC temperatures are normal as per lm-sensors.

  20171109 - Not reproducible testing drm-tip for 1.5 days.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1727662/+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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2019-03-21 Thread Bug Watch Updater
** Bug watch added: freedesktop.org Bugzilla #109206
   https://bugs.freedesktop.org/show_bug.cgi?id=109206

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

2019-03-21 Thread Bug Watch Updater
Launchpad has imported 21 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=194521.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-02-08T20:32:58+00:00 vaclav.ovsik wrote:

Created attachment 254611
crash logged using netconsole

I bought my daughter a notebook HP 15-ba062nc
(http://support.hp.com/us-en/product/HP-15-ba000-Notebook-PC-series/10862317/model/11792430).
Installed is Debian Stretch/Sid with kernel 4.9.6.

Successful boot without crash is possible with
- disabled amdgpu (e.g. old nomodeset)
- or disabled iommu (iommu=off)
otherwise the kernel crashes and the file-system is corrupted.

iommu=off is much better way now, because the notebook runs in energy
efficient manner - the fan is quiet or stopped.

Attached are kernel messages using netconsle.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/comments/0


On 2017-02-08T20:35:58+00:00 vaclav.ovsik wrote:

Created attachment 254621
nomodeset - no crash

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/comments/1


On 2017-02-08T20:37:02+00:00 vaclav.ovsik wrote:

Created attachment 254631
iommu=off - no crash

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/comments/2


On 2017-02-08T20:48:42+00:00 vaclav.ovsik wrote:

Created attachment 254641
lspci -vvv

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/comments/3


On 2017-02-08T20:52:17+00:00 vaclav.ovsik wrote:

Created attachment 254651
/proc/cpuinfo

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/comments/4


On 2017-02-08T21:09:53+00:00 vaclav.ovsik wrote:

Created attachment 254661
crash logged using netconsole

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/comments/5


On 2017-02-09T12:07:28+00:00 fin4478 wrote:

Do you have the amdgpu firmware installed?

When you create bugs against amdgpu driver, use the latest kernel and mesa code:
https://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-4.11-wip
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

Problems might be fixed in the latest code.

Latest polaris firmware:
https://people.freedesktop.org/~agd5f/radeon_ucode/polaris/


How to create a custom kernel, see:
https://bugzilla.kernel.org/show_bug.cgi?id=193651

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/comments/6


On 2017-02-09T23:34:15+00:00 vaclav.ovsik wrote:

Doubt the problem is in the amdgpu driver. What about bug in the amd_iommu?
I think this because I tried to switch off external GPU using acpi_call module.
The following command was successful:

echo '\_SB_.PCI0.VGA.PX02' > /proc/acpi/call

while running kernel with no KMS (no amdgpu). Fan really went silent
after this, but kernel crashed in several seconds in similar way like
with amdgpu and active iommu.

The filesystem is after every crash corrupted. I'm afraid that storage
controller goes through iommu too and crash causes some random writes to
disk :(. But may be I am wrong and this ACPI call is illegal in reality
and amdgpu does something wrong regarding iommu to. Nevertheless amdgpu works
with iommu=off fine. Maybe the problem is with some buggy BIOS/firmware
from vendor.

I will try a newer kernel.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/comments/7


On 2017-02-10T18:36:11+00:00 vaclav.ovsik wrote:

I tried kernel 4.10.0-rc6-amd64 from Debian experimental archive and the
result is very similar. To minimize harm on filesystem I booted into
emergency mode with read-only file-system and tried to switch off GPU
using ACPI call. There is some warning during call, but something
happened :)

ACPI Warning: \_SB.PCI0.VGA.PX02: Insufficient arguments - Caller passed
0, method requires 1 (20160930/nsarguments-256)

I did this twice - one time with and one time without iommu=off.

I'm attaching netconsole logs...

Is this a proof the problem is in the amd_iommu.c?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/comments/8


On 2017-02-10T18:37:59+00:00 vaclav.ovsik 

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2019-03-19 Thread Bug Watch Updater
** Bug watch added: Linux Kernel Bug Tracker #202971
   https://bugzilla.kernel.org/show_bug.cgi?id=202971

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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


[Kernel-packages] [Bug 1802168] Re: Unable to get right-click working on ThinkPad T480s

2019-03-19 Thread Bug Watch Updater
** Changed in: libinput
   Status: Unknown => Fix Released

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

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

Status in libinput:
  Fix Released
Status in Linux:
  Unknown
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged

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

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

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

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


[Kernel-packages] [Bug 1817097] Re: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices

2019-03-11 Thread Bug Watch Updater
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1669751.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-01-26T17:38:46+00:00 nkshirsa wrote:

Description of problem:

lvm should not allow extending an LV with a PV of different sector size
than existing PVs making up the LV, since the FS on the LV does not
mount once LVM adds in the new PV and extends the LV.


How reproducible:
Steps to Reproduce:

** Device: sdc (using the device with default sector size of 512)

# blockdev --report /dev/sdc
RORA   SSZ   BSZ   StartSecSize   Device
rw  8192   512  4096  0  1073741824   /dev/sdc

** LVM is created with the default sector size of 512.

# blockdev --report /dev/mapper/testvg-testlv 
RORA   SSZ   BSZ   StartSecSize   Device
rw  8192   512  4096  0  1069547520   /dev/mapper/testvg-testlv

** The filesystem will also pick up 512 sector size.

# mkfs.xfs /dev/mapper/testvg-testlv 
meta-data=/dev/mapper/testvg-testlv isize=512agcount=4, agsize=65280 blks
 =   sectsz=512   attr=2, projid32bit=1
 =   crc=1finobt=0, sparse=0
data =   bsize=4096   blocks=261120, imaxpct=25
 =   sunit=0  swidth=0 blks
naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
log  =internal log   bsize=4096   blocks=855, version=2
 =   sectsz=512   sunit=0 blks, lazy-count=1
realtime =none   extsz=4096   blocks=0, rtextents=0

** Now we will mount it

# xfs_info /test
meta-data=/dev/mapper/testvg-testlv isize=512agcount=4, agsize=65280 blks
 =   sectsz=512   attr=2, projid32bit=1
 =   crc=1finobt=0 spinodes=0
data =   bsize=4096   blocks=261120, imaxpct=25
 =   sunit=0  swidth=0 blks
naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
log  =internal   bsize=4096   blocks=855, version=2
 =   sectsz=512   sunit=0 blks, lazy-count=1
realtime =none   extsz=4096   blocks=0, rtextents=0

** Let's extend it with a PV with a sector size of 4096:

#modprobe scsi_debug sector_size=4096 dev_size_mb=512

# fdisk -l /dev/sdd
 
Disk /dev/sdd: 536 MB, 536870912 bytes, 131072 sectors
Units = sectors of 1 * 4096 = 4096 bytes <==
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 262144 bytes
 
# blockdev --report /dev/sdd
RORA   SSZ   BSZ   StartSecSize   Device
rw  8192  4096  4096  0   536870912   /dev/sdd

# vgextend testvg /dev/sdd
  Physical volume "/dev/sdd" successfully created
  Volume group "testvg" successfully extended

# lvextend -l +100%FREE /dev/mapper/testvg-testlv
  Size of logical volume testvg/testlv changed from 1020.00 MiB (255 extents) 
to 1.49 GiB (382 extents).
  Logical volume testlv successfully resized.

# umount /test

# mount /dev/mapper/testvg-testlv /test
mount: mount /dev/mapper/testvg-testlv on /test failed: Function not 
implemented <===

# dmesg | grep -i dm-2

[  477.517515] XFS (dm-2): Unmounting Filesystem
[  486.905933] XFS (dm-2): device supports 4096 byte sectors (not 512) 
<

The sector size of the lv is now 4096.
# blockdev --report /dev/mapper/testvg-testlv 
RORA   SSZ   BSZ   StartSecSize   Device
rw  8192  4096  4096  0  1602224128   /dev/mapper/testvg-testlv


Expected results:
LVM should fail the lvextend if sector size is different to existing PV's


Additional info:
Discussed with Zdenek during LVM meeting in Brno

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1817097/comments/0


On 2019-01-28T15:53:23+00:00 teigland wrote:

Should we just require all PVs in the VG to have the same sector size?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1817097/comments/1


On 2019-01-28T16:46:28+00:00 zkabelac wrote:

Basically that's what we have agreed in meeting - since we don't know
yet how to handle different sector-sized PVs.

And a short fix could be to not allow that to happen on creating time.

But still there are already users having that  VGs already created - so lvm2 
can't just say such VG is invalid
and disable access to it...

So I'd probably see something similar we did for 'mirrorlog' -
add lvm.conf option to disable creation - that is respected on vgcreate 

[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2019-03-09 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => 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/1727662

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  Updated docking station firmware to latest 2.33.00.

  PC temperatures are normal as per lm-sensors.

  20171109 - Not reproducible testing drm-tip for 1.5 days.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1727662/+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 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2019-03-04 Thread Bug Watch Updater
Launchpad has imported 20 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=103643.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-11-09T11:54:00+00:00 Alexander Kops wrote:

I reported this issue in the Ubuntu bug tracker:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662
I was advised to cross post it here. 

It can be reproduced in the latest Mainline kernel 4.14-rc8
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8/
but doesn't seem to appear (after 1.5 days of testing) with the current drm-tip 
build
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

Copying original bug description here:
"What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
* Most of the time the computer is found shut down.
* Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
* The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

I have two external monitors attached to the docking station.

When I dock my laptop, the battery indicator does recognize its
charging.

I've not seen this issue when:
1) With the laptop in the dock, while actively using the laptop.
2) With the laptop out of the dock and no external monitors present.

This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

Using or not using the following kernel parameter didn't change anything:
i915.enable_rc6=0

PC temperatures are normal as per lm-sensors."

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/35


On 2017-11-09T21:02:25+00:00 Elizabethx-de-la-torre-mena wrote:

Hello Alexander, 
Could you share a dmesg or/and kern.log with debug information from boot til 
problem: drm.debug=0x1e log_bug_len=2M on grub.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/40


On 2017-11-09T21:18:32+00:00 Alexander Kops wrote:

I'm currently running my computer with the current Mainline kernel
(4.14-rc8) and these settings and will post the dmesg as soon as I'm
able to reproduce it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/41


On 2017-11-10T12:57:04+00:00 Alexander Kops wrote:

Created attachment 135371
kern.log - Crash seemed to happen at 13:31:38

I added a compressed kern.log (the computer shut down at Nov 10 13:31:38
I reproduced the bug running the current Mainline kernel 
4.14.0-041400rc8-generic

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/42


On 2017-11-13T14:34:17+00:00 Alexander Kops wrote:

Created attachment 135436
kern.log with running drm-tip kernel from today - Computer shut down at 15:20:39

Today I was able to reproduce it with the drm-tip kernel found here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

I attach the kern.log, the computer shut itself down at 15:20:39
This time no messages about a fifo underrun are in the log.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/44


On 2017-11-13T16:13:20+00:00 Elizabethx-de-la-torre-mena wrote:

(In reply to Alexander Kops from comment #4)
> Created attachment 135436 [details]
> kern.log with running drm-tip kernel from today - Computer shut down at
> 15:20:39
> 
> Today I was able to reproduce it with the drm-tip kernel found here:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
> 
> I attach the kern.log, the computer shut itself down at 15:20:39
> This time no messages about a fifo underrun are in the log.
Hello Alexander, it seems that the log is keeping all the information that you 
already shared in the first attachment. Could you reproduce with a clean 
kern.log, since it shuts I guess a dmesg can't be obtained. 

To clean kern.log:
# rm /var/logs/kern.log
# reboot
The kern.log will regenerate after boot.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/45


On 2017-11-13T16:16:35+00:00 Elizabethx-de-la-torre-mena wrote:

Also I noticed you marked this bug as a regression, could you please
share latest good know kernel commit and bad know commit.


[Kernel-packages] [Bug 1788018] Re: udevd keeps binding and unbinding some usb device und uses all cpu

2019-03-01 Thread Bug Watch Updater
Launchpad has imported 13 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=199035.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-03-06T21:09:45+00:00 mathieutournier wrote:

Created attachment 274593
dmesg

Hi,
I'm currently running ubuntu 18.04 with a 4.15 kernel and i can observe very 
high cpu usage to the  systemd-udevd deamon.

removing the rule :
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
  ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
  RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"

Solved the high CPU usage eventhough my bluetooth card is not available
anymore (as not in hci mode)

It seems that the command hid2hci creates a bind/unbind loop in udev
that is looping trying to set the device in hci mode. (that what udevadm
monitor seems to show, looping from bind to unbind for the device)

I suspect a0085f2510e8976614ad8f766b209448b385492f introduced a
regression (i have not tried to revert it yet).

Please not that there also seem to be a bug in hid2hci.c from bluez l148 :
if (err == 0) {
err = -1;
errno = EALREADY;
}
Correcting this and recompile bluez desn't solve the issue as cpu usage remains 
very high.

Using a 4.13 kernel result in a normal CPU usage, this seems a
regression in 4.14.

Other people seems to have the same issue, here is a bug report related to this 
:
https://dev.solus-project.com/T5224

Thanks a lot for your support,

Mathieu Tournier

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/0


On 2018-05-04T05:57:10+00:00 boro wrote:

I have the very same problem using the same distro (Ubuntu 18.04,
64-bit) on Dell Latitude E5400 laptop. Disabling BT from BIOS or
removing the aforementioned rule solves the problem but leaves BT
unusable.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/1


On 2018-05-09T23:02:06+00:00 lucent wrote:

Bus 001 Device 009: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
Bus 001 Device 004: ID 0a5c: Broadcom Corp. 

Linux zontar 4.16.0-1-amd64 #1 SMP Debian 4.16.5-1 (2018-04-29) x86_64
GNU/Linux

May 09 15:59:00 hostname upowerd[14610]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
...repeating...

15632 root  20   0  233136 186656   2664 R  94.1%   4.7%  62:14.67 
systemd-udevd   
  
16222 root  20   0   88252   2432   1888 R  35.3%   0.1%  25:21.87 
systemd-udevd   
  

Looks like same problem affects this Dell Precision M6500 laptop.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/2


On 2018-05-20T07:57:41+00:00 f.dittmer wrote:

I observed the high cpu usage after upgrading from udev-233 to 
udev-236/udev-238 on Gentoo Linux. Downgrading back to udev-233 lets me use 
newer kernels (currently running 4.15.18) without any problems.
Using DELL Latitude E6400 from 2009, with same Broadcom Bluetooth module as 
mentioned above.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/3


On 2018-06-13T16:50:40+00:00 rickfharris wrote:

As per https://patchwork.kernel.org/patch/10384111/ editing
97-hid2hci.rules as follows works around the new uevents added to the
kernel in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65

-ACTION=="remove", GOTO="hid2hci_end"
+ACTION!="add", GOTO="hid2hci_end"

Bluetooth now works with kernels above and below 4.14.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/4


On 2018-06-14T00:32:13+00:00 

[Kernel-packages] [Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore

2019-02-28 Thread Bug Watch Updater
** Changed in: linux
   Status: Incomplete => Fix Released

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

Title:
  [Samsung NP530U3C-A01] LID close, AC, and battery status events not
  produced anymore

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

Bug description:
  On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery
  status events not produced anymore. The situation is the same (tested
  with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where
  I can put all the information related to this bug here:
  http://zenstep.com.ar/samsung-linux/

  In summary, after a suspend sleep with many events (8 plug/unplug, or
  battery dropping or increasing about 16%, maybe less), the Embedded
  Controller accumulates those events and stops producing GPE 0x17.
  Neither Windows nor Linux query those accumulated events, because the
  EC doesn't produce GPE 0x17 anymore. The issue persists between
  restarts and shutdowns, and even after re-suspending/re-resuming.
  Hitting the reset button through the hole in the back fixes the
  problem temporarily. That is, until the next unlucky suspend.

  IMPORTANT: if the laptop is never ever suspended, the issue never
  comes back.

  To force the issue to happen, you can either:
  1) Sleep the computer in linux (by closing the lid or any other means).
  2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 
actions or more).
  3) Resume from sleep. You'll note that the battery icon is fixed, and 
unplugging or plugging doesn't update battery status anymore. Also note that 
the ability to suspend by closing the LID is lost.

  OR:
  1) echo disable > /sys/firmware/acpi/interrupts/gpe17
  2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions)
  3) echo enable > /sys/firmware/acpi/interrupts/gpe17

  WORKAROUND: Turn off the computer, unplug it, hit the reset button in
  the back of the laptop, and then plug it again.

  WORKAROUND (kernel patch 1):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133

  BETTER WORKAROUND (kernel patch 2):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-11-generic 3.13.0-11.31
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2546 F pulseaudio
  CasperVersion: 1.337
  Date: Sat Feb 22 22:57:34 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-11-generic N/A
   linux-backports-modules-3.13.0-11-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1283589/+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 929244] Re: Cannot connect to wireless network in 12.04

2019-02-27 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=42843.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-03-01T16:36:57+00:00 aquaglow wrote:

Created attachment 72509
Apport generated log of information.

My wireless network is listed in Network Manager, but upon entering the
password it tries to connect and then re-prompts for a password. I could
previously connect fine in Ubuntu 10.10/Fedora 16.

This issue occured in the stock Ubuntu 3.2.0 kernel (issue raised here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/929244), and also
in the mainline 3.3.0 kernel when I tried that instead.

Steps to reproduce:
1. Select wireless network in Network Manager (802.11g with WPA2 in my case)
2. Watch the network icon animate while it tries to connect
3. Dialog box re-prompts for password

My wireless card details:

01:08.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI
 Subsystem: Linksys WMP54G v4.1
 Flags: bus master, slow devsel, latency 32, IRQ 18
 Memory at dbff8000 (32-bit, non-prefetchable) [size=32K]
 Capabilities: 
 Kernel driver in use: rt61pci
 Kernel modules: rt61pci

dmesg output immediately after connection failed:

[ 422.332069] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
[ 422.334473] wlan0: authenticated
[ 422.348049] wlan0: associate with 00:26:f2:05:ad:dc (try 1)
[ 422.350844] wlan0: deauthenticated from 00:26:f2:05:ad:dc (Reason: 6)
[ 507.012093] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
[ 507.015078] wlan0: authenticated
[ 507.017076] wlan0: failed to insert Dummy STA entry for the AP (error -17)

Attached is the apport generated log.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/929244/comments/11


On 2017-03-06T19:59:08+00:00 szg wrote:

Please try this bug with latest kernel image.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/929244/comments/26

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

Title:
  Cannot connect to wireless network in 12.04

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

Bug description:
  My wireless network is listed in Network Manager, but upon entering
  the password it tries to connect and then re-prompts for a password. I
  can connect fine in Ubuntu 10.10/Fedora 16.

  Steps to reproduce:
  1. Select wireless network in Network Manager (802.11g with WPA2 in my case)
  2. Watch the network icon animate while it tries to connect
  3. Dialog box re-prompts for password

  My wireless card details:

  01:08.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI
Subsystem: Linksys WMP54G v4.1
Flags: bus master, slow devsel, latency 32, IRQ 18
Memory at dbff8000 (32-bit, non-prefetchable) [size=32K]
Capabilities: 
Kernel driver in use: rt61pci
Kernel modules: rt61pci

  dmesg output immediately after connection failed:

  [  422.332069] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
  [  422.334473] wlan0: authenticated
  [  422.348049] wlan0: associate with 00:26:f2:05:ad:dc (try 1)
  [  422.350844] wlan0: deauthenticated from 00:26:f2:05:ad:dc (Reason: 6)
  [  507.012093] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
  [  507.015078] wlan0: authenticated
  [  507.017076] wlan0: failed to insert Dummy STA entry for the AP (error -17)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/929244/+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 1043403] Re: Wireless not active during installation or after boot

2019-02-27 Thread Bug Watch Updater
Launchpad has imported 4 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=46721.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-08-30T16:45:07+00:00 lars.nooden+kernel wrote:

Created attachment 78811
dmesg

The i386 has a Ralink corp. RT2561/RT61 802.11g PCI wireless card.
However, the installation process seems unable to use it to find any
wireless networks, not even open networks. Same goes after booting and
trying manually.  This is true even with the new kernel:

# uname -a
Linux easynote 3.6.0-030600rc3-generic #201208221735 SMP Wed Aug 22 21:45:31 
UTC 2012 i686 i686 i686 GNU/Linux

# rfkill list all
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: yes

What information is needed to make a proper bug report?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043403/comments/22


On 2012-08-30T19:59:46+00:00 alan wrote:

[   15.649864] rt61pci :00:06.0: enabling device ( -> 0002)
[   15.649882] rt61pci :00:06.0: can't find IRQ for PCI INT A; please try 
using pci=biosirq
[   15.649900] rt61pci :00:06.0: setting latency timer to 64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043403/comments/24


On 2012-08-31T07:32:38+00:00 lars.nooden+kernel wrote:

Created attachment 78861
dmesg after pci=biosirq

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043403/comments/25


On 2012-08-31T07:34:19+00:00 lars.nooden+kernel wrote:

I tried setting pci=biosirq in the grub menu and the only difference I
see is that the consoles vanish.  I can still log in via ssh though.

# rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043403/comments/26

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

Title:
  Wireless not active during installation or after boot

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

Bug description:
  The i386 has a  Ralink corp. RT2561/RT61 802.11g PCI wireless card.
  However, the installation process seems unable to use it to find any
  wireless networks, not even open networks.  Same goes after booting
  and trying manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  Date: Wed Aug 29 18:50:47 2012
  InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash --
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120828)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AcpiTables:

  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   27.408464] init: lightdm main process (943) terminated with 
status 1
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=2a0d5ff8-7854-49fd-91e2-be4326cfc418
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120828)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Packard Bell Computers International Packard Bell EasyNote
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic 
root=UUID=1e64a51f-2f5b-4d0f-bb43-88c03014c8b4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-13-generic N/A
   linux-backports-modules-3.5.0-13-generic  N/A
   linux-firmware1.90
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: yes
  Tags:  quantal
  Uname: Linux 3.5.0-13-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: /08/0520
  

[Kernel-packages] [Bug 1686048] Re: Touchpad not detected on Lenovo S21e-20

2019-02-26 Thread Bug Watch Updater
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=195669.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-05-05T09:04:20+00:00 rghvdberg wrote:

Created attachment 256219
lshw

OS Kubuntu 17.04
Kernel 4.11.0-041100-generic (mainline)
The touchpad isn

I've tried several kernel paramaters

i8042.nomux=1
i8042.reset=1
i8042.noloop=1
i8042.kbdreset=1
i8042.nopnp=1
i8042.debug=1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686048/comments/9


On 2017-05-05T09:05:12+00:00 rghvdberg wrote:

Created attachment 256221
dmesg

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686048/comments/10


On 2017-05-05T09:07:17+00:00 rghvdberg wrote:

Created attachment 256223
devices

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686048/comments/11


On 2017-09-19T13:37:32+00:00 nikolas wrote:

Can you attach the output of `udevadm info -e` run as root?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686048/comments/13


On 2017-09-20T13:45:40+00:00 rghvdberg wrote:

NOTE : Currently on 4.9.48-1-MANJARO
output was too long so I pastebinned it

https://pastebin.com/HV6CRvFJ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686048/comments/14


On 2019-02-25T14:50:08+00:00 vbatts wrote:

This is still not working on 4.16.3 and 4.20.8 on Fedora
reading on https://alpha-labs.net/2015/08/lenovo-s21e-linux-and-the-touchpad/
it looks like there had been a fix floated for the hid-rmi module.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686048/comments/15


On 2019-02-25T15:26:19+00:00 vbatts wrote:

ah, sorry. This looks like an i2c elan touchpad issue. My apologies.
[vbatts@dhcp6-118 ~]$ dmesg | grep -i elan
[2.442191] i2c_hid i2c-ELAN0601:00: i2c-ELAN0601:00 supply vdd not found, 
using dummy regulator

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686048/comments/16


On 2019-02-25T19:52:30+00:00 vbatts wrote:

Created attachment 281341
add the ELAN0601 ID

this is the patch i've emailed to Duson Lin

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686048/comments/17


On 2019-02-25T19:54:10+00:00 vbatts wrote:

Confirmed the patch works on the Lenovo s21e-20 laptop with 5.0.0-rc8
kernel. Surely could be backported to other releases.

Duson's EMC email bounced. What subsystem should I mail this patch to

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686048/comments/18


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  Touchpad not detected on Lenovo S21e-20

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

Bug description:
  xinput list
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳  USB OPTICAL MOUSEid=9[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)]
  ↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)]
  ↳ Lenovo EasyCamera

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

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
 

[Kernel-packages] [Bug 1816493] Re: Ralink RT3290 Is Not in Kernel

2019-02-23 Thread Bug Watch Updater
** Changed in: fedora
   Status: Confirmed => 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/1816493

Title:
  Ralink RT3290 Is Not in Kernel

Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  Expired

Bug description:
  Bluetooth in HP laptop doesn't work, because the driver isn't in the kernel 
or packaged.
  There are some guides in the internet, but they aren't integrated in kernel 
and aren't guaranteed to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 19 01:33:46 2019
  InstallationDate: Installed on 2019-02-07 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InterestingModules: bluetooth
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  syslog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sherif 5874 F pulseaudio
  CRDA:
   global
   country EG: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (N/A, 20), (N/A)
(5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-07 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  cosmic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816493/+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 1812359] Re: No login screen displayed on a NETBOX nT-435/535 (kernel reports an LVDS output which does not exist as connected and on)

2019-02-21 Thread Bug Watch Updater
** Changed in: linux
   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/1812359

Title:
  No login screen displayed on a NETBOX nT-435/535 (kernel reports an
  LVDS output which does not exist as connected and on)

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

Bug description:
  On a machine with only one display (VGA), the kernel is reporting two:

  grep . /sys/class/drm/*/enabled

 /sys/class/drm/card0-LVDS-1/enabled:enabled
 /sys/class/drm/card0-VGA-1/enabled:enabled

  ls /sys/class/drm

 card0 card0-LVDS-1 card0-VGA-1 renderD128 version

  grep . /sys/class/drm/*/dpms

 /sys/class/drm/card0-LVDS-1/dpms:On
 /sys/class/drm/card0-VGA-1/dpms:On

  which then triggers bug 1760849 and the login screen is never visible.

  ---

  $ dpkg -s mutter
  Package: mutter
  Status: install ok installed
  Priority: optional
  Section: x11
  Installed-Size: 101
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.3-2~ubuntu18.04.2
  Provides: x-window-manager
  Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), 
libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 
3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 
3.21.4), zenity
  Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs
  Description: lightweight GTK+ window manager
   Mutter is a small window manager, using GTK+ and Clutter to do
   everything.
   .
   Mutter is the clutter-based evolution of Metacity, which, as the
   author says, is a "Boring window manager for the adult in you. Many
   window managers are like Marshmallow Froot Loops; Metacity is like
   Cheerios."
   .
   This package contains the core binaries.
  Original-Maintainer: Debian GNOME Maintainers 


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 18 15:02:22 2019
  InstallationDate: Installed on 2019-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1812359/+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 1816493] Re: Ralink RT3290 Is Not in Kernel

2019-02-18 Thread Bug Watch Updater
Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1662304.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-27T14:07:44+00:00 ali.sherif10 wrote:

Description of problem:
Bluetooth in HP laptop doesn't work, because the driver isn't in the kernel or 
packaged.
There are some guides in the internet, but they aren't integrated in kernel and 
aren't guaranteed to work.

Actual results:
I can't use bluetooth.

Expected results:
I can use bluetooth.

Additional info:
Laptop: HP Pavilion g6.
Ralink wifi works, but the wifi button is always red (It's supposed to be 
white, while wifi is enabled).

Distribution: Fedora 29 KDE Spin (64 bit).
All packages are updated.

The problem isn't fixed in Ubuntu, OpenSUSE and Arch also.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1816493/comments/0


On 2018-12-27T14:09:24+00:00 ali.sherif10 wrote:

Created attachment 1517073
>From Info Center

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1816493/comments/1


On 2018-12-27T14:09:48+00:00 ali.sherif10 wrote:

Created attachment 1517074
>From Info Center

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1816493/comments/2


On 2018-12-27T14:10:15+00:00 ali.sherif10 wrote:

Created attachment 1517075
>From Info Center

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1816493/comments/3


On 2018-12-29T07:09:57+00:00 m8r-sx4s741 wrote:

For completeness, could you post the output from these commands:

$ uname -r
$ lspci -nnk -d 1814:  # include the colon

>From the attached screenshot, the vendor:device id is 1814:3298, which
is mentioned in this bug report from 2013:

Bug 907594 - Bluetooth adapter not found in 3.7 kernel but OK in 3.6

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1816493/comments/4


On 2018-12-29T09:56:36+00:00 ali.sherif10 wrote:

(In reply to Steve from comment #4)
> For completeness, could you post the output from these commands:
> 
> $ uname -r
> $ lspci -nnk -d 1814:  # include the colon
> 
> From the attached screenshot, the vendor:device id is 1814:3298, which is
> mentioned in this bug report from 2013:
> 
> Bug 907594 - Bluetooth adapter not found in 3.7 kernel but OK in 3.6

```uname -r:
4.19.10-300.fc29.x86_64```
```lspci -nnk -d 1814:
07:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
DeviceName: Ralink RT3290LE  802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 
Combo Ad
Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi 
and Bluetooth 4.0 Combo Adapter [103c:18ec]
Kernel driver in use: rt2800pci
Kernel modules: rt2800pci
07:00.1 Bluetooth [0d11]: Ralink corp. RT3290 Bluetooth [1814:3298]
Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi 
and Bluetooth 4.0 Combo Adapter [103c:18ec]```

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1816493/comments/5


On 2018-12-29T09:57:39+00:00 ali.sherif10 wrote:

I tried to format text by adding "```". :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1816493/comments/6


On 2018-12-29T10:26:40+00:00 ali.sherif10 wrote:

bluetoothctl lags, until I close it by CTRL+c.

# dmesg | grep -i bluetooth  # Only gave output after su.
[85022.921931] Bluetooth: Core ver 2.22
[85022.922011] Bluetooth: HCI device and connection manager initialized
[85022.922015] Bluetooth: HCI socket layer initialized
[85022.922017] Bluetooth: L2CAP socket layer initialized
[85022.922024] Bluetooth: SCO socket layer initialized

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1816493/comments/7


On 2018-12-29T10:28:52+00:00 ali.sherif10 wrote:

Now, it worked as non-root.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1816493/comments/8


On 2018-12-29T14:22:01+00:00 m8r-sx4s741 wrote:

> I tried to format text by adding "```". :)

Thanks for posting the uname and lspci output. You don't need to format
anything -- maintainers are used to looking at that stuff ... :-)

> Now, it worked as 

[Kernel-packages] [Bug 1812359] Re: No login screen displayed on a NETBOX nT-435/535 (kernel reports an LVDS output which does not exist as connected and on)

2019-02-18 Thread Bug Watch Updater
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=202487.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-02-02T06:21:08+00:00 daisy.rose021 wrote:

I've installed Ubuntu 19.04 on a NETBOX nT-435/535 and no login screen
displayed whenever the VGA is connected to LG monitor.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812359/comments/84


On 2019-02-02T06:22:48+00:00 daisy.rose021 wrote:

Created attachment 280927
LVDS & VGA status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812359/comments/85


On 2019-02-18T08:53:08+00:00 kai.heng.feng wrote:

Please file i915 bugs to https://bugs.freedesktop.org

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812359/comments/88


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  No login screen displayed on a NETBOX nT-435/535 (kernel reports an
  LVDS output which does not exist as connected and on)

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

Bug description:
  On a machine with only one display (VGA), the kernel is reporting two:

  grep . /sys/class/drm/*/enabled

 /sys/class/drm/card0-LVDS-1/enabled:enabled
 /sys/class/drm/card0-VGA-1/enabled:enabled

  ls /sys/class/drm

 card0 card0-LVDS-1 card0-VGA-1 renderD128 version

  grep . /sys/class/drm/*/dpms

 /sys/class/drm/card0-LVDS-1/dpms:On
 /sys/class/drm/card0-VGA-1/dpms:On

  which then triggers bug 1760849 and the login screen is never visible.

  ---

  $ dpkg -s mutter
  Package: mutter
  Status: install ok installed
  Priority: optional
  Section: x11
  Installed-Size: 101
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.3-2~ubuntu18.04.2
  Provides: x-window-manager
  Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), 
libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 
3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 
3.21.4), zenity
  Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs
  Description: lightweight GTK+ window manager
   Mutter is a small window manager, using GTK+ and Clutter to do
   everything.
   .
   Mutter is the clutter-based evolution of Metacity, which, as the
   author says, is a "Boring window manager for the adult in you. Many
   window managers are like Marshmallow Froot Loops; Metacity is like
   Cheerios."
   .
   This package contains the core binaries.
  Original-Maintainer: Debian GNOME Maintainers 


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 18 15:02:22 2019
  InstallationDate: Installed on 2019-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1812359/+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 1804028] Re: Surface Go - QCA6174 wifi card not correctly recognized and therefore not working

2019-02-16 Thread Bug Watch Updater
Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1651779.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-11-20T19:42:11+00:00 fedora_45sg wrote:

Description of problem:

After booting, the wifi card is not properly recognized.

Version-Release number of selected component (if applicable):

firmware version can be seen in dmesg output.

"[ 4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 168c:3370
[ 4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
[ 4.243006] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 4.308059] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 
from ath10k/QCA6174/hw3.0/board-2.bin
[ 4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a"

How reproducible:

Insert usb-pen, boot Fedora 29 Workstation, open terminal, get dmesg
output


Steps to Reproduce:
1. Boot
2. get dmesg output

Actual results:

dmesg output:


Wifi/bluetooth card not properly recognized and therefore not working

Expected results:

Wifi/bluetooth working.


Additional info:

I added some more results here:

https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1804028

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/1804028/comments/7


On 2018-11-20T22:18:44+00:00 fedora_45sg wrote:

In the .zip from https://www.killernetworking.com/killersupport/item
/killer-drivers-inf in the file ./Killer-Ethernet-
Wireless_INF/Production/Windows10-x64/11AC/netathr10x.inf I finally
found one matching subsystem-device=3370 entry, which leads to:

"
%ATHR.DeviceDesc.6320_3%   = ATHR_DEV_OS63_988x_TX8.ndi,
PCI\VEN_168C_003E_3370168C_32; WiFi Only SKU
"

about this special .ndi there are some entrys later:

"
[ATHR_DEV_OS63_988x_TX8.ndi.NTamd64]
Characteristics = 0x84
BusType = 5
AddReg  = atheros_os63.reg, atheros11n.reg, smpsDynamic.reg, 
qca_utf.reg, D0PC.reg, roam.reg, wmmac.reg, FW_3X.reg, BD_TX8.reg, 
enableTxbfee.reg, wowEnable.reg, ForceWowSleep.reg, fastDlBinary.reg, 
enableSmbios.reg, Ch1213_options_SingleSKU.reg   
CopyFiles   = atheros.CopyFiles, atheros_FW_3X.CopyFiles, 
atheros_BD_TX8.CopyFiles, service.CopyFiles
*IfType = 71; IF_TYPE_IEEE80211
*MediaType  = 16; NdisMediumNative802_11
*PhysicalMediaType = 9  ; NdisPhysicalMediumNative802_11
Include = machine.inf, netvwifibus.inf
Needs   = VWiFiBus.CopyFiles

[ATHR_DEV_OS63_988x_TX8.ndi.NTamd64.Services]
AddService = Qcamain10x64, 2, atheros.Service, atheros.EventLog
Include= netvwifibus.inf
Needs  = VWiFiBus.Services
AddService = QcomWlanSrv, 0x0800, wlanService

[ATHR_DEV_OS63_988x_TX8.ndi.NTamd64.HW]
AddReg  = MSI.reg
Include = netvwifibus.inf
Needs   = PciASPMOptIn.Hw, VWiFiBus.PnPFilterRegistration.Hw, 
PciD3ColdSupported.Hw
"

I am just a bit confused because it just says "Wifi Only SKU" and I know
from the Windows Device Manager that also bluetooth is done with the
same chip, see
https://www.reddit.com/r/Surface/comments/9386l7/surface_go_wifi_qualcomm_qca61x4a/e3bbi1b/
but maybe there are two different build-in, one for wifi and one for
bluetooth?

Anyway, from the quote there is one interesting line:

"
CopyFiles   = atheros.CopyFiles, atheros_FW_3X.CopyFiles, 
atheros_BD_TX8.CopyFiles, service.CopyFiles
"

It seems that there exist just one file with "TX8" in it:
"eeprom_ar6320_3p0_TX8_clpc.bin"

I copied the .bin file as board.bin to
/lib/firmware/ath10k/QCA6174/hw3.0/ and it finally works! Wifi is
directly working and no error messages anymore in dmesg! :-)

So eeprom_ar6320_3p0_TX8_clpc.bin, or the informations of that .bin file
have to be added to
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles and
this should be a clean solution, because the subsystem-device=3370 ID is
matching.

Can someone please double check if this is the correct solution which
could go upstream?

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/1804028/comments/8


On 2018-11-20T22:41:25+00:00 fedora_45sg wrote:

Did some additional tests with "eeprom_ar6320_3p0_TX8_clpc.bin":

The copied and renamed as board.bin file also works with the latest
firmware-6.bin from
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/plain/ath10k/QCA6174/hw3.0/ and also with the one from

[Kernel-packages] [Bug 983681] Re: Floppy keeps running forever after every access

2019-02-15 Thread Bug Watch Updater
Launchpad has imported 5 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=43120.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-04-18T15:59:18+00:00 ticmanis wrote:

The floppy disk drive's motor keeps running forever as soon as the
floppy is accessed (say, by doing a "mdir a:" or a "fdformat /dev/fd0",
or a "dd if=/dev/fd0 ..." ), and the floppy drive's activity LED stays
lit. Only when the disk is removed from the drive, the drive stops. I'd
expect the drive to stop spinning a few seconds after the access is
finished.

The accessing command returns normally and I can still access the drive
normally by giving another command afterwards. The problem is purely the
failure to deselect the drive and/or turn off the drive motor line.

This is a standard IRQ6/DMA2 floppy drive connected directly to the
motherboard's built in FDC with a standard 34-wire ribbon floppy cable.
The bug happens both with a normal 1.44MB drive and with a 1.2MB (5.25
inch) drive. The drives do not exhibit this problem in DOS or Windows
running on the same physical hardware. My motherboard is an ASUS P5B, if
that is important. There was no second drive connected as my motherboard
supports only one floppy.

The bug first occured after upgrading my Ubuntu system to Ubuntu Precise
(12.04) Beta 2, but I have tested with a mainline 3.4.0-rc3 kernel
(though with Ubuntu specific configuration) which I got from here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc3-precise/

The specific package I tested with was called "linux-
image-3.4.0-030400rc3-generic_3.4.0-030400rc3.201204152235_amd64.deb"

The bug was still there in that mainline kernel.

I hope this is the right subsystem for this bug, if not please feel free
to move it and/or to point out where it should go. This is the first
kernel bug I'm reporting upstream so please excuse me if some vital
information is missing. Please just tell me what more info you need.
Thanks!

My original Ubuntu bug report can be found here:

https://bugs.launchpad.net/bugs/983681

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983681/comments/6


On 2012-04-18T16:02:38+00:00 ticmanis wrote:

The kernel where I first noticed the bug is the Ubuntu specific 3.2.0.
Currently "uname -a" gives "Linux linards 3.2.0-23-generic #36-Ubuntu
SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux".

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983681/comments/7


On 2017-03-06T20:29:51+00:00 szg wrote:

Please try to reproduce this bug with latest kernel image.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983681/comments/12


On 2019-02-14T09:29:09+00:00 corti wrote:

The problem still persists. I've tried kernel 4.19.16 from Debian testing. The 
bug somehow lies in the logic for detecting a disk change. If I access the 
floppy the motor won't turn off. But if I force a disk change (ejecting and 
immediately inserting the floppy again) the motor turns off within about two 
seconds - as it should.
Also, if I practically disable the disk change checks with "floppycontrol -C 
2147483647" the motor turns off normally. So I suspect that frequently checking 
for disk changes without the floppy being changed keeps the motor in its 
current state.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983681/comments/13


On 2019-02-14T10:52:18+00:00 corti wrote:

Created attachment 281133
kernel messages

The following kernel messages are repeated every two seconds (after
which the motor should be turned off) when loading the module with
floppy=debug

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983681/comments/14

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

Title:
  Floppy keeps running forever after every access

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

Bug description:
  In Ubuntu Precise, the floppy disk drive's motor keeps running forever
  as soon as the floppy is accessed (say, by doing a "mdir a:" or a
  "fdformat /dev/fd0", or a "dd if=/dev/fd0 ..." ), and the floppy
  drive's activity LED stays lit. Only when the disk is removed from the
  drive, the drive stops. I'd expect the drive to stop spinning a few
  seconds after the access is finished.

  The accessing command returns normally and I can still 

[Kernel-packages] [Bug 1815952] Re: Mute key LED does not work on HP Pavilion x360

2019-02-14 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=202581.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-02-14T19:24:52+00:00 romanescu.2019 wrote:

Open bug in launchpad.net:
https://bugs.launchpad.net/bugs/1815952

---

Description of problem:
The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

Tested with HP Pavilion x360 from 2018.

Version-Release number of selected component (if applicable):

How reproducible:
Always.

Steps to Reproduce:
1. Press mute key on HP laptop

Actual results:
Mute state in software toggles, LED in mute key does not.

Expected results:
Mute state in software and LED in mute key toggle.

Additional info:
This happens on kernel 4.20.8

Other similar errors:
* https://bugs.launchpad.net/bugs/1683277
* https://bugs.launchpad.net/bugs/1705586

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815952/comments/2


On 2019-02-14T20:55:58+00:00 romanescu.2019 wrote:

Ok.

My first patch for the linux kernel:
https://github.com/caravena/linux/commit/c540283416a7756dedaa72aa66a00c897517b113#diff-f52b6863505adc3b972c64d4a22195cc

I would like to have credits for this patch (:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815952/comments/7


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  Mute key LED does not work on HP Pavilion x360

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

Bug description:
  Description of problem:
  The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

  Tested with HP Pavilion x360 from 2018.

  Version-Release number of selected component (if applicable):

  How reproducible:
  Always.

  Steps to Reproduce:
  1. Press mute key on HP laptop

  Actual results:
  Mute state in software toggles, LED in mute key does not.

  Expected results:
  Mute state in software and LED in mute key toggle.

  Additional info:
  This happens on kernel 4.20.8

  Other similar errors:
  * https://bugs.launchpad.net/bugs/1683277
  * https://bugs.launchpad.net/bugs/1705586

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-12-generic 4.19.0-12.13
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 15:56:54 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-12-generic N/A
   linux-backports-modules-4.19.0-12-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (73 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-02-09 Thread Bug Watch Updater
** Changed in: mesa
   Status: Confirmed => Fix Released

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1707167] Re: Kernel CIFS Module ignores USER_SESSION_DELETED PDUs and holds onto dead sessions.

2019-02-07 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=195817.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-05-19T12:26:23+00:00 keith wrote:

The cifs kernel module currently is currently disregarding the nt_status
USER_SESSION_DELETED packets sent to it from remote SMB2+ peers and is
subsequently holding onto clearly dead SMB2+ sessions as a result.

This is causing issues as it appears that the kernel only reconnects
after a delay period, during which time all IO to that network share
(with that session id) results in an I/O error for the user; all the
while the kernel is repeatedly resubmitting the requests in the
background with the server just responding to each of them with the same
error.

This is contrasting to the behaviour on Windows clients - whereby if the
response the client gets is USER_SESSION_DELETED, it will immediately
dump that session and reconnect - transparently to the user.

This causes massive issues multiuser mounts (as is the case for me), as
if a users SMB session is deleted by the server for any reason, that
user essentially loses all access to that share for extended periods,
until the cifs module sees fit to treat that session as dead and
renegotiate or an admin intervenes.

Reproducing the issue is easily done, establish an SMB2+ mount to a
Windows Server machine, open any directory on client to establish a
session, then simply terminate that SMB session from the servers MMC
console, if you then try and run any queries against that mountpoint on
the client you will just end up with a string of I/O errors because its
trying to use a session id which is dead.

For reference I'm testing using the following mount options:
vers=3.02,multiuser,sec=ntlmsspi,file_mode=0750,dir_mode=0755,cache=none,credentials=/etc/smb.credentials.conf

Kernels 4.4 and 4.10 have extended delays until the user is able to
regain access to the mountpoint, the latest rc has cut that down
significantly and its only a few minutes, but even still if the session
has been deleted by the server the client should at least attempt to
reconnect and then resubmit the last command, rather than continue to
submit packets with dead session ID's and return I/O to the user.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707167/comments/0


On 2019-02-07T04:25:43+00:00 lsahlber wrote:

This was fixed in :
commit d81243c697ffc71f983736e7da2db31a8be0001f
Author: Mark Syms 
Date:   Thu May 24 09:47:31 2018 +0100

CIFS: 511c54a2f69195b28afb9dd119f03787b1625bb4 adds a check for session 
expiry, status STATUS_NETWORK_SESSION_EXPIRED, however the server can also 
respond with STATUS_USER_SESSION_DELETED in cases where the session has been 
idle for some time and the server reaps the session to recover resources.

Handle this additional status in the same way as SESSION_EXPIRED.

Signed-off-by: Mark Syms 
Signed-off-by: Steve French 
CC: Stable 

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707167/comments/3


** Changed in: linux
   Status: Unknown => Fix Released

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  Kernel CIFS Module ignores USER_SESSION_DELETED PDUs and holds onto
  dead sessions.

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

Bug description:
  #Summary
  The cifs kernel module currently ignores the nt_status USER_SESSION_DELETED 
PDUs sent to it from remote SMB2+ peers and holds onto clearly dead SMB2+ 
sessions as a result.

  This is causing issues, as it appears that the kernel only reconnects
  after a delay period, during which time all IO to that network share
  (with that session id) results in an I/O error for the user; all the
  while the kernel is repeatedly resubmitting the requests in the
  background with the server just responding to each of them with yet
  more USER_SESSION_DELETED packets.

  This is contrasting to the behaviour on Windows clients - whereby if
  the response the client gets is USER_SESSION_DELETED, it drops that
  session and reconnects - transparently to the user.

  This causes massive issues multiuser mounts (as is the case for me),
  as if a users SMB session is deleted by the server for any reason,
  that user essentially loses all access to that share for extended
  periods, until the cifs module sees fit to treat that session as dead
  and renegotiate or an admin intervenes.

  # Reproducing
  Reproducing the issue is 

[Kernel-packages] [Bug 1725322] Re: kernel 4.4.0.97.102 breaks DFS

2019-02-07 Thread Bug Watch Updater
Launchpad has imported 13 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=196891.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-09-10T18:59:10+00:00 jed-kernel.org wrote:

Ever since updating to 4.12.10, I have been getting "File name too long"
messages when accessing my CIFS share:

  $ ls /nfs/users/test
  ls: cannot access '/nfs/users/test': File name too long

On my system, the CIFS share is mounted on /nfs/users. (An NFS export
was transitioned to CIFS a while back, hence the oddly named mount
point.)

This issue goes away if I revert to 4.12.8. Commit d3edede looks
relevant.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/0


On 2017-09-13T21:58:12+00:00 lsahlber wrote:

Which architecture do you see this on?

Can you attach a network trace including the initial mount, i.e. the query 
calls where cifs.ko will discover what the maximum length the server supports
during the mount.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/1


On 2017-09-14T04:22:44+00:00 lsahlber wrote:

Please also try v4.13 as it contains the change
6e3c1529c39e92ed64ca41d53abadabbaa1d5393

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/2


On 2017-09-14T05:24:15+00:00 jed-kernel.org wrote:

Created attachment 258363
CIFS queries and responses during mount

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/3


On 2017-09-14T05:30:35+00:00 jed-kernel.org wrote:

Both server and client are x86_64. Server is samba 4.6.7.

I've attached a trace excerpt showing the queries and responses during
mount. The very last message shows the server responding with max length
255.

The issue persists with 4.12.12, which includes
77ab9e7fb4312d3b377690660f757d900fa9e171, which I believe is the same as
the change you mention above.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/4


On 2017-09-14T05:46:38+00:00 lsahlber wrote:

That is SMB1.  Can you try with a SMB2 mount too?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/5


On 2017-09-14T15:01:16+00:00 jed-kernel.org wrote:

Created attachment 258383
SMB2.0 fs attr info query & response

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/6


On 2017-09-14T15:01:39+00:00 jed-kernel.org wrote:

Created attachment 258385
SMB2.1 fs attr info query & response

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/7


On 2017-09-14T15:01:57+00:00 jed-kernel.org wrote:

Created attachment 258387
SMB3.0 fs attr info query & response

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/8


On 2017-09-14T15:04:28+00:00 jed-kernel.org wrote:

Same result with SMB2.0, SMB2.1, and SMB3.0. I've attached traces of the
FileFsAttributeInformation queries and responses for all three protocol
versions.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/9


On 2017-09-18T23:40:09+00:00 lsahlber wrote:

I can not reproduce this issue using current linux/master branch.

The queries look sane in the network trace so ...


What fileserver are you using? Windows or Samba? And what version.
Can you try using the same kernel and try accessing a different share on a 
different file server to see if things are different.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/10


On 2017-10-21T14:50:56+00:00 jed-kernel.org wrote:

The server is Samba 4.6.7. Users are stored in LDAP and authenticated
with Kerberos. Here are the mount options I am using:

  user=machine-root,multiuser,sec=krb5,x-systemd.automount

Unfortunately, I don't have a different file server to play with, but I
suspect it is the 'multiuser' option that is breaking things.

Here are the contents of /proc/fs/cifs/DebugData after the initial
mount:

  Display 

[Kernel-packages] [Bug 1443924] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush

2019-02-05 Thread Bug Watch Updater
Launchpad has imported 56 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=61621.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-09-18T14:52:38+00:00 eredar wrote:

It seems that the rt3290 wireless chipset acts very flaky under 3.11.1,
my last kernel before this one was 3.10.3 and it didn't have this
problem. I'm currently compiling 3.10.10 to see if it works again there
as reported in the arch linux forums.

Revelant forum topic where I found other users with the problem:
https://bbs.archlinux.org/viewtopic.php?pid=1326183#p1326183

By flaky I mean that after a while it just refuses to connect, this is
some dmesg output:

[4.949297] wlp1s0f0: authenticate with 5c:7d:5e:de:b6:04
[4.961762] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 1/3)
[4.963279] wlp1s0f0: authenticated
[4.964933] wlp1s0f0: associate with 5c:7d:5e:de:b6:04 (try 1/3)
[4.970465] wlp1s0f0: RX AssocResp from 5c:7d:5e:de:b6:04 (capab=0x431 
status=0 aid=1)
[4.970563] wlp1s0f0: associated
[   28.285869] fuse init (API version 7.22)
[   29.967936] EXT4-fs (sda3): re-mounted. Opts: data=ordered,commit=0
[   29.983555] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
[   30.020684] EXT4-fs (sda4): re-mounted. Opts: data=ordered,commit=0
[   31.468349] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   32.031587] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   32.058518] cfg80211: Calling CRDA for country: GB
[   32.264907] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   32.398225] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   33.482380] wlp1s0f0: authenticate with 5c:7d:5e:de:b6:04
[   33.621406] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   33.628168] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 1/3)
[   34.324623] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 2/3)
[   35.324464] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 3/3)
[   36.334424] wlp1s0f0: authentication with 5c:7d:5e:de:b6:04 timed out
[   36.504382] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   37.137655] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   37.270932] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443924/comments/0


On 2013-09-18T17:38:50+00:00 Fl0w3D wrote:

I have similar errors using a Ralink RT2500 Wireless 802.11bg card,
except that downgrading to an older kernel didn't fix the bug (tried
3.10.10, 3.10.9, 3.10.7). Also, the error is not constant: sometimes, it
works for a few seconds or a few minutes, and then it's back down. And
sometimes, it doesn't work for a long time straight.

Also, same error occurs when trying to connect to an unsecured wifi, so
it doesn't seem to be WPA related.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443924/comments/1


On 2013-09-18T18:28:31+00:00 nicolas wrote:

To report back after downgrading to 3.10.10: it seems to be stable
again. I've not lost connectivity yet and it's been a few hours. With
3.11.1 I lose connectivity quite rapidly, more or less after 15-30
minutes.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443924/comments/2


On 2013-09-19T18:54:32+00:00 vedathallac wrote:

Same problem here. The issue is intermittent - sometimes I cannot even
connect after initial boot, and sometimes I stay connected for long
stretches.

I found that I can trigger the problem by downloading a large file.
After a few megabytes of data, I get a stream of flush errors, then the
number of bars I see on the NM applet drop to zero, and a few seconds
later I lose connection, and cannot connect again. Removing and
reloading rt2800pci module allow me to connect - usually. But attempting
the download will repeat the above symptoms.

One final bit of information: when I boot using pci=nomsi parameter, I
still get the flush errors and the download pauses a bit, but then it
recovers and continues the download. I get between 50-100KB/sec average
and intermittent connectivity problems with this flag, but I haven't
lost connection to my AP yet.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443924/comments/3


On 2013-09-19T19:16:49+00:00 vedathallac wrote:

Commenting out the msi 

[Kernel-packages] [Bug 1239459] Re: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds

2019-02-05 Thread Bug Watch Updater
Launchpad has imported 56 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=61621.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-09-18T14:52:38+00:00 eredar wrote:

It seems that the rt3290 wireless chipset acts very flaky under 3.11.1,
my last kernel before this one was 3.10.3 and it didn't have this
problem. I'm currently compiling 3.10.10 to see if it works again there
as reported in the arch linux forums.

Revelant forum topic where I found other users with the problem:
https://bbs.archlinux.org/viewtopic.php?pid=1326183#p1326183

By flaky I mean that after a while it just refuses to connect, this is
some dmesg output:

[4.949297] wlp1s0f0: authenticate with 5c:7d:5e:de:b6:04
[4.961762] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 1/3)
[4.963279] wlp1s0f0: authenticated
[4.964933] wlp1s0f0: associate with 5c:7d:5e:de:b6:04 (try 1/3)
[4.970465] wlp1s0f0: RX AssocResp from 5c:7d:5e:de:b6:04 (capab=0x431 
status=0 aid=1)
[4.970563] wlp1s0f0: associated
[   28.285869] fuse init (API version 7.22)
[   29.967936] EXT4-fs (sda3): re-mounted. Opts: data=ordered,commit=0
[   29.983555] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
[   30.020684] EXT4-fs (sda4): re-mounted. Opts: data=ordered,commit=0
[   31.468349] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   32.031587] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   32.058518] cfg80211: Calling CRDA for country: GB
[   32.264907] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   32.398225] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   33.482380] wlp1s0f0: authenticate with 5c:7d:5e:de:b6:04
[   33.621406] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   33.628168] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 1/3)
[   34.324623] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 2/3)
[   35.324464] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 3/3)
[   36.334424] wlp1s0f0: authentication with 5c:7d:5e:de:b6:04 timed out
[   36.504382] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   37.137655] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush
[   37.270932] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 
failed to flush

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239459/comments/0


On 2013-09-18T17:38:50+00:00 Fl0w3D wrote:

I have similar errors using a Ralink RT2500 Wireless 802.11bg card,
except that downgrading to an older kernel didn't fix the bug (tried
3.10.10, 3.10.9, 3.10.7). Also, the error is not constant: sometimes, it
works for a few seconds or a few minutes, and then it's back down. And
sometimes, it doesn't work for a long time straight.

Also, same error occurs when trying to connect to an unsecured wifi, so
it doesn't seem to be WPA related.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239459/comments/1


On 2013-09-18T18:28:31+00:00 nicolas wrote:

To report back after downgrading to 3.10.10: it seems to be stable
again. I've not lost connectivity yet and it's been a few hours. With
3.11.1 I lose connectivity quite rapidly, more or less after 15-30
minutes.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239459/comments/2


On 2013-09-19T18:54:32+00:00 vedathallac wrote:

Same problem here. The issue is intermittent - sometimes I cannot even
connect after initial boot, and sometimes I stay connected for long
stretches.

I found that I can trigger the problem by downloading a large file.
After a few megabytes of data, I get a stream of flush errors, then the
number of bars I see on the NM applet drop to zero, and a few seconds
later I lose connection, and cannot connect again. Removing and
reloading rt2800pci module allow me to connect - usually. But attempting
the download will repeat the above symptoms.

One final bit of information: when I boot using pci=nomsi parameter, I
still get the flush errors and the download pauses a bit, but then it
recovers and continues the download. I get between 50-100KB/sec average
and intermittent connectivity problems with this flag, but I haven't
lost connection to my AP yet.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239459/comments/3


On 2013-09-19T19:16:49+00:00 vedathallac wrote:

Commenting out the msi 

[Kernel-packages] [Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

2019-01-31 Thread Bug Watch Updater
** Changed in: ndctl
   Status: New => Fix Released

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in ndctl:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: 

[Kernel-packages] [Bug 400397] Re: Errors (hanging, only continue with Ctrl-c) while prosessing kexec-tools

2019-01-31 Thread Bug Watch Updater
** Changed in: kexec-tools (Debian)
   Status: Unknown => Fix Released

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

Title:
  Errors (hanging,only continue with Ctrl-c) while prosessing kexec-
  tools

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools package in Debian:
  Fix Released

Bug description:
  Karmic
  Binary package hint: kexec-tools

  jarkko@gandalf:/boot/grub$ sudo dpkg --configure -a -D2000
  Setting up kexec-tools (2009-2.0.0ubuntu10) ...
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /vmlinuz-2.6.31-3-generic
  Found kernel: /vmlinuz-2.6.31-2-generic
  Found kernel: /vmlinuz-2.6.31-1-generic
  Found kernel: /vmlinuz-2.6.30-10-generic
  Found kernel: /vmlinuz-2.6.30-9-generic
  Found kernel: /memtest86+.bin

   (hangs here forever) x

  ^Cdpkg: error processing kexec-tools (--configure):
   subprocess installed post-installation script killed by signal (Interrupt)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.31-3-generic
  Errors were encountered while processing:
   kexec-tools
  jarkko@gandalf:/boot/grub$

  Same thing with apt-get dist-upgrade.

  update-grub works when run alone;
  jarkko@gandalf:/boot/grub$ sudo update-grub 
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /vmlinuz-2.6.31-3-generic
  Found kernel: /vmlinuz-2.6.31-2-generic
  Found kernel: /vmlinuz-2.6.31-1-generic
  Found kernel: /vmlinuz-2.6.30-10-generic
  Found kernel: /vmlinuz-2.6.30-9-generic
  Found kernel: /memtest86+.bin
  Updating /boot/grub/menu.lst ... done

  jarkko@gandalf:/boot/grub$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/400397/+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 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

2019-01-30 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=86931.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-10-25T20:23:14+00:00 caravena wrote:

Message with Mouse Bluetooth

[ 32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/4


On 2015-05-04T09:35:57+00:00 csaavedra wrote:

This is still present in 4.0.0. Bluetooth keyboard disconnects,
bluetoothd seems to crash, etc.

Do you need any further information to help debug this? This bug makes
the bluetooth keyboard unusable.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/10


On 2016-03-29T19:52:54+00:00 stephan.diestelhorst wrote:

Same in 4.2.0 (-34-generic in Ubuntu 15.10).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/14


On 2016-03-30T17:53:32+00:00 jbmacbrodie wrote:

Bluetooth behavior was good in ubuntu 15.10 - bluez5.35, blueman device
manager and kernel 4.3.6.  I use a bt mouse and OEM bt keydock (Asus
T100-CHI)

Starting with 4.4 thru 4.6-rc1-next*, I have to open blueman's device
manager to search for devices after idle timeouts.  I also need to leave
the device manager dialogue open/minimized to prevent rapid loss of
connection.  Device pairing is remembered, but manually searching is
difficult when the pointing devices stop working.  My test setup has a
usb mouse as a workaround.

dmesg has "unknown main item tag 0x0" after each idle timeout".  If I
move mouse during boot, it will auto-connect, but it then suffers a
rapid timeout soon after booting.  See dmesg posted at #114561.  It
looks like something is incrementing the bluetooth input assignment #
when anything times out.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/15


On 2018-01-12T09:21:14+00:00 robsmith11 wrote:

Has anyone solved this yet??

I have the same issue with a bluetooth keyboard and kernel 4.14.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/29


On 2018-01-12T17:26:47+00:00 jbmacbrodie wrote:

The issue was fixed for the Asus T100 (baytrail) 2-in-1 family.  See this 
commit.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=c4c285da1ee18582ace366f07e56e355c20ebc49
 which is in kernel 4.15. 

You could try adding the quirk for your device.

(No kernel maintainer has acknowledged this bug report.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/30


On 2019-01-30T18:27:54+00:00 mybigspam wrote:

It's not clear from the description what is the problem exactly?
I have similar symptoms with "unknown main item tag 0x0" message after timeout.

But my problem is that bluetooth keyboard disconnects on timeout (which
is normal), but then, on the first key press it's just loss, while the
keyboard reconnects successfully.

It doesn't occurs on the same system with Windows 10 - the key doesn't
lost on reconnect.

I wonder if it can be the same problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/35


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

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

Bug description:
  Message with Mouse Bluetooth

  [   32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
  0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3344 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 24 05:22:54 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

2019-01-26 Thread Bug Watch Updater
** Changed in: linux (Debian)
   Status: Confirmed => Fix Released

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Fix Released

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel
  (suspicion)

  ---
  // on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
  [ 99.99] ehci-pci :00:1d.0:dma_direct_map_sg: overflow 
0x000223ad7000+2048 of device mask  
  errors on booting 'live' (see #16) for real
  BUT
  the same ISO works fine on same box when a virtual machine (Virtual box on a 
GNU/Linux host and "Type: Linux Version: Ubuntu (32-bit)" virtual machine)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+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 1685442] Re: Errors: flip_done timed out during boot-up; slow boot

2019-01-25 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => Fix Released

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

Title:
  Errors:  flip_done timed out  during boot-up; slow boot

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

Bug description:
  I had been running Ubuntu 16.04 LTS on many laptop computers
  (especially Dell D620, D630, E6400) with no problem.

  I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell
  D630.  It was very slow to boot up (about 90 seconds) as opposed to
  the 30-45 seconds it usually takes. For a few seconds there were error
  messages that included the phrase "flip_done timed out".

  When the Ubuntu desktop appeared, the mouse cursor hung for a while,
  but then came back to life. I didn't do much testing from there.  I
  did a Live session with the 16.04.2 LTS  on a different D630 laptop,
  and the same problem occureed.

  I Googled the problem, and found several hits.
  -
  On an Arch forum, someone reported the problem on a Dell D630, like mine. It 
also occured on other laptops:
  https://bbs.archlinux.org/viewtopic.php?id=218581

  The suggestion was that the bug was related to kernel version 4.8.x
  and the 965GM chipset, which is what the D630 has.

  So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the 
problem DID NOT occur.
  ---
  For a similar boot-up problem, Ubuntu Forum suggested going back to an 
earlier version of Ubuntu.
  https://ubuntuforums.org/showthread.php?t=2348892

  I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and
  the problem did NOT occur.

  So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather 
than 16.04.2.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware  

[Kernel-packages] [Bug 1809206] Re: Amd ACPI Error

2019-01-18 Thread Bug Watch Updater
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201981.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-13T08:35:02+00:00 luya wrote:

I brought a brand new HP Envy x360 laptop and install a distribution.
The issue occurred on both with the following error:

mesg | grep Error
[1.275414] RAS: Correctable Errors collector initialized.
[4.957640] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180810/dsopcode-201)
[4.957647] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180810/psparse-516)
[4.957655] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180810/psparse-516)
[4.957701] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180810/dsopcode-201)
[4.957705] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180810/psparse-516)
[4.957710] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180810/psparse-516)
[4.957755] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180810/dsopcode-201)
[4.957759] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180810/psparse-516)
[4.957764] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180810/psparse-516)
[4.958354] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180810/dsopcode-201)
[4.958358] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180810/psparse-516)
[4.958365] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180810/psparse-516)
[4.958513] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180810/dsopcode-201)
[4.958517] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180810/psparse-516)
[4.958523] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180810/psparse-516)


With some researches, it looks like all HP laptops are affected by this issue
https://bugzilla.kernel.org/show_bug.cgi?id=200999
https://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/acpi-error-with-linux/td-p/6021489

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809206/comments/0


On 2018-12-14T02:29:14+00:00 luya wrote:

Additional link to related bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1520703

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809206/comments/1


On 2018-12-20T04:07:10+00:00 serdar2005 wrote:

Hi
Hp Amd A10 9600p
[3.546921] RAS: Correctable Errors collector initialized.
[9.979321] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
[9.979438] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[9.979484] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[9.979764] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
[9.979872] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[9.988903] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[9.989220] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
[9.989318] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[9.989358] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[9.990180] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
[9.990274] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[9.990312] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[9.990557] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
[9.990646] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[9.990682] ACPI Error: Method 

[Kernel-packages] [Bug 1707695] Re: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec

2019-01-18 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => Won't Fix

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

Title:
  radeon :03:00.0: ring 0 stalled for more than 1msec

Status in Linux:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system intermittently locks up every few days. It does not seem to
  correspond to a particular program or action.  When that happens, the
  screen goes to black, then returns after a few seconds. At that point,
  the time on the clock is static and indicates that the screen is
  frozen, but audio continues to play for 30 seconds to a minute. The
  keyboard and mouse do not affect what's being displayed, but I can Alt
  - SysRq - REISUB to restart.

  Every time (7 crashes and counting), /var/log/kern.log indicates that

  kernel: [353692.378886] radeon :03:00.0: ring 0 stalled for more than 
10280msec
  kernel: [353692.378896] radeon :03:00.0: GPU lockup (current fence id 
0x006e96e5 last fence id 0x006e96e9 on ring 0)

  just before the system locks. Different ring numbers are reported as
  stalling at different times.

  As per the instructions, I posted a question about this issue at:

  https://askubuntu.com/questions/937792/system-lockup-radeon-ring-
  stalled-for-more-than-10280msec?noredirect=1#comment1486875_937792

  but I have not received many responses.

  I'm running 16.04 LTS. 
  :~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  According to the Software Center, I am running Ubuntu Software 3.20.1.

  I have a Radeon HD graphics card.

  :~$ lspci | grep VGA
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]

  :~$ lspci -v -s 03:00.0
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Cedar [Radeon HD 5000/6000/7350/8350 
Series]
  Flags: bus master, fast devsel, latency 0, IRQ 53
  Memory at c000 (64-bit, prefetchable) [size=256M]
  Memory at d3d2 (64-bit, non-prefetchable) [size=128K]
  I/O ports at 7000 [size=256]
  Expansion ROM at d3d0 [disabled] [size=128K]
  Capabilities: 
  Kernel driver in use: radeon
  Kernel modules: radeon

  Please let me know if additional information would be useful, and I
  will be glad to provide it.  Thanks in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-87-generic 4.4.0-87.110
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clapp  3889 F pulseaudio
   /dev/snd/controlC2:  clapp  3889 F pulseaudio
   /dev/snd/controlC1:  clapp  3889 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 31 14:02:27 2017
  HibernationDevice: RESUME=UUID=1b30dad6-8c48-42cf-ae26-66ab8b0eb446
  InstallationDate: Installed on 2013-09-04 (1425 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Dell Inc. Precision T7600
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=33722f76-37fd-4289-b071-d7f48b65dd32 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-87-generic N/A
   linux-backports-modules-4.4.0-87-generic  N/A
   linux-firmware1.157.11
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd05/03/2013:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1707695/+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 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.

2019-01-17 Thread Bug Watch Updater
** Changed in: linux
   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/1799613

Title:
  In kernel 4.14.59, monitor resolution is detected correctly. In
  kernels after that, they are not detected correctly.

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

Bug description:
   dpkg --list | grep linux-image
  ii  linux-image-4.15.0-36-generic   4.15.0-36.39  
   amd64Signed kernel image generic
  ii  linux-image-4.15.0-38-generic   4.15.0-38.41  
   amd64Signed kernel image generic
  ii  linux-image-generic 4.15.0.38.40  
   amd64Generic Linux kernel image
  ii  linux-image-unsigned-4.14.59-041459-generic 
4.14.59-041459.201807280929  amd64Linux kernel 
image for version 4.14.59 on 64 bit x86 SMP

  
  Booting from GRUB into 4.14.59 allows my two monitors to run at their native 
resolution, 2560x1440. Any newer kernel does not allow my two monitors to run 
at their native resolution, only allowing up to 1920x1200. 

  uname -a

  Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28
  09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1799613/+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 1811259] Re: 4.20 kernel on s390x VM crashes

2019-01-16 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => Fix Released

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

Title:
  4.20 kernel on s390x VM crashes

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  Booting with  4.20.0-2-generic on a s390x 2 CPU VM we hit a panic:

  [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc 
version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 
2019 (Ubuntu 4.20.0-2.3-generic 4.20.0)
  [0.394838] setup.289988: Linux is running under KVM in 64-bit mode
  [0.394846] setup.b050d0: The maximum memory size is 2048MB
  [0.394866] numa.196305: NUMA mode: plain
  [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs
  [0.394999] Write protected kernel read-only data: 10464k
  [0.395034] Zone ranges:
  [0.395035]   DMA  [mem 0x-0x7fff]
  [0.395037]   Normal   empty
  [0.395038] Movable zone start for each node
  [0.395039] Early memory node ranges
  [0.395041]   node   0: [mem 0x-0x7fff]
  [0.395042] Initmem setup node 0 [mem 
0x-0x7fff]
  [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 
d32000 u102400
  [0.413824] Built 1 zonelists, mobility grouping on.  Total pages: 516096
  [0.413825] Policy zone: DMA
  [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs
  [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K 
rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved)
  [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 
with crng_init=0
  [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1
  [0.450434] ftrace: allocating 27385 entries in 107 pages
  [0.473325] rcu: Hierarchical RCU implementation.
  [0.473327] rcu:   RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3.
  [0.473328]Tasks RCU enabled.
  [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 
jiffies.
  [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3
  [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
  [0.475402] clocksource: tod: mask: 0x max_cycles: 
0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
  [0.475558] printk: console [ttyS1] enabled
  [0.475623] pid_max: default: 32768 minimum: 301
  [0.475658] LSM: Security Framework initializing
  [0.475660] Yama: becoming mindful.
  [0.475677] AppArmor: AppArmor initialized
  [0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 
bytes)
  [0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 
bytes)
  [0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
  [0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 
bytes)
  [0.476726] rcu: Hierarchical SRCU implementation.
  [0.476927] smp: Bringing up secondary CPUs ...
  [0.477181] smp: Brought up 1 node, 2 CPUs
  [0.477549] devtmpfs: initialized
  [0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 1911260446275 ns
  [0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes)
  [0.478105] NET: Registered protocol family 16
  [0.478134] audit: initializing netlink subsys (disabled)
  [0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized 
audit_enabled=0 res=1
  [0.478222] Spectre V2 mitigation: execute trampolines
  [0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages
  [0.479623] SCSI subsystem initialized
  [0.479856] NetLabel: Initializing
  [0.479858] NetLabel:  domain hash size = 128
  [0.479859] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
  [0.479871] NetLabel:  unlabeled traffic allowed by default
  [0.507362] VFS: Disk quotas dquot_6.6.0
  [0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
  [0.507486] AppArmor: AppArmor Filesystem Enabled
  [0.507847] NET: Registered protocol family 2
  [0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 
16384 bytes)
  [0.507994] TCP established hash table entries: 16384 (order: 5, 131072 
bytes)
  [0.508126] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
  [0.508235] TCP: Hash tables configured (established 16384 bind 16384)
  [0.508269] UDP hash table entries: 1024 (order: 3, 32768 bytes)
  [0.508287] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
  [0.508336] NET: Registered protocol family 1
  [0.508343] NET: Registered protocol family 44
  [0.508374] Unpacking 

[Kernel-packages] [Bug 1811259] Re: 4.20 kernel on s390x VM crashes

2019-01-15 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=202283.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-01-15T14:47:50+00:00 colin.king wrote:

s390x inside VM, hitting the following kernel panic on 4.20:

[ 0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc 
version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 
2019 (Ubuntu 4.20.0-2.3-generic 4.20.0)
[ 0.394838] setup.289988: Linux is running under KVM in 64-bit mode
[ 0.394846] setup.b050d0: The maximum memory size is 2048MB
[ 0.394866] numa.196305: NUMA mode: plain
[ 0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs
[ 0.394999] Write protected kernel read-only data: 10464k
[ 0.395034] Zone ranges:
[ 0.395035] DMA [mem 0x-0x7fff]
[ 0.395037] Normal empty
[ 0.395038] Movable zone start for each node
[ 0.395039] Early memory node ranges
[ 0.395041] node 0: [mem 0x-0x7fff]
[ 0.395042] Initmem setup node 0 [mem 0x-0x7fff]
[ 0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 d32000 
u102400
[ 0.413824] Built 1 zonelists, mobility grouping on. Total pages: 516096
[ 0.413825] Policy zone: DMA
[ 0.413827] Kernel command line: root=LABEL=cloudimg-rootfs
[ 0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K 
rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved)
[ 0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 with 
crng_init=0
[ 0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1
[ 0.450434] ftrace: allocating 27385 entries in 107 pages
[ 0.473325] rcu: Hierarchical RCU implementation.
[ 0.473327] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3.
[ 0.473328] Tasks RCU enabled.
[ 0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 
jiffies.
[ 0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3
[ 0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
[ 0.475402] clocksource: tod: mask: 0x max_cycles: 
0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
[ 0.475558] printk: console [ttyS1] enabled
[ 0.475623] pid_max: default: 32768 minimum: 301
[ 0.475658] LSM: Security Framework initializing
[ 0.475660] Yama: becoming mindful.
[ 0.475677] AppArmor: AppArmor initialized
[ 0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.476726] rcu: Hierarchical SRCU implementation.
[ 0.476927] smp: Bringing up secondary CPUs ...
[ 0.477181] smp: Brought up 1 node, 2 CPUs
[ 0.477549] devtmpfs: initialized
[ 0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 1911260446275 ns
[ 0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes)
[ 0.478105] NET: Registered protocol family 16
[ 0.478134] audit: initializing netlink subsys (disabled)
[ 0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized 
audit_enabled=0 res=1
[ 0.478222] Spectre V2 mitigation: execute trampolines
[ 0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages
[ 0.479623] SCSI subsystem initialized
[ 0.479856] NetLabel: Initializing
[ 0.479858] NetLabel: domain hash size = 128
[ 0.479859] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.479871] NetLabel: unlabeled traffic allowed by default
[ 0.507362] VFS: Disk quotas dquot_6.6.0
[ 0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.507486] AppArmor: AppArmor Filesystem Enabled
[ 0.507847] NET: Registered protocol family 2
[ 0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 
bytes)
[ 0.507994] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.508126] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[ 0.508235] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.508269] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[ 0.508287] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[ 0.508336] NET: Registered protocol family 1
[ 0.508343] NET: Registered protocol family 44
[ 0.508374] Unpacking initramfs...
[ 0.742412] Freeing initrd memory: 15824K
[ 0.742685] kvm-s390: SIE not available
[ 0.742706] hypfs.7f5705: The hardware system does not support hypfs
[ 0.742714] hypfs.7a79f0: Initialization of hypfs failed with rc=-61
[ 0.743110] Initialise system trusted keyrings
[ 0.743119] Key type blacklist registered
[ 0.743140] 

[Kernel-packages] [Bug 571770] Re: Thread [hd-audio0] consuming excessive amounts of CPU, audio crackling

2019-01-15 Thread Bug Watch Updater
** Changed in: linux (Ubuntu)
   Status: Invalid => Fix Released

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

Title:
  Thread [hd-audio0] consuming excessive amounts of CPU, audio crackling

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: linux-image-2.6.32-22-generic

  Sometimes during audio playback, a kernel thread named "[hd-audio0]"
  will consume excessive amounts of CPU and cause  audio crackling. It
  seems to be more easily triggered when displaying video in fullscreen
  (or Rhythmbox visualizations) or dragging windows around while playing
  music, somehow relating it graphics operations (running default radeon
  driver with KMS and Compiz).

  This all started after moving from Ubuntu Karmic to Lucid (never had
  this problem before).

  Setting package to kernel, since it's probably alsa snd_hda_intel
  kernel module which is to blame.

  Ubuntu 10.04 x86, Intel Core Duo 2GHz, 3GB RAM, ATI X1400 Radeon Mobility 
graphics.
  Audio chip: Analog Devices AD1981 [HDA]

  WORKAROUND: Disabling radeon KMS makes all the audio crackling go
  away.

  Attaching:
  * Screenshot of top running over Rhythmbox w/fullscreen visualizations, 
showing [hd-audio0] consuming more CPU than everything else at the time (audio 
crackles).
  * Output of "lspci -vvnn"
  * Output of "dmesg"
  * Contents of /proc/interrupts
  * ALSA info, as provided by the alsa-info.sh script.

  Related to this: https://bugzilla.kernel.org/show_bug.cgi?id=14935 ???

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/571770/+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 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

2019-01-15 Thread Bug Watch Updater
** Changed in: ndctl
   Status: Unknown => 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/1811785

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in ndctl:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area 

[Kernel-packages] [Bug 1806682] Re: ACPI: Invalid passive threshold

2019-01-10 Thread Bug Watch Updater
** Changed in: linux
   Status: Incomplete => Fix Released

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

Title:
  ACPI: Invalid passive threshold

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [1.423794] ACPI: Invalid passive threshold

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806682/+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 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu

2019-01-05 Thread Bug Watch Updater
** Changed in: linux
   Status: In Progress => Fix Released

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

Title:
  Latest ASUS trackpad doesn't work in Ubuntu

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

Bug description:
  It seems there might be a new hardware variant of the elan trackpad in
  the newer ASUS machines.

  The issue is the shown here with some reasonably deep investigation.
  Is this something that I can do or am I reduced to having to find out
  a mouse if I want to use Linux?

  https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/

  user@TUF-GAMING-FX504GD-FX80GD:~$ xinput
   Virtual core pointer  id=2[master pointer  (3)]
     ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
     ↳ Logitech USB Receiver id=12   [slave  pointer  (2)]
     ↳ Logitech USB Receiver id=13   [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)]
  ↳ Asus Wireless Radio Control   id=7[slave  keyboard (3)]
  ↳ Video Bus id=8[slave  keyboard (3)]
  ↳ Video Bus id=9[slave  keyboard (3)]
  ↳ Power Button  id=10   [slave  keyboard (3)]
  ↳ Sleep Button  id=11   [slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam: USB2.0 HD   id=14   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=15   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=16   [slave  keyboard (3)]
  ↳ Logitech USB Receiver id=17   [slave  keyboard (3)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1781879/+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 1810546] Re: AMDGPU VMC page fault with Athlon 200GE APU

2019-01-04 Thread Bug Watch Updater
Launchpad has imported 36 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=199749.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-05-17T09:21:39+00:00 muelladdi wrote:

System video freezes randomly during the day while working on the system 
normally (no 3D).
Logfile shows only:

May 17 11:18:00 ws01 kernel: [11831.268044] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* ring sdma0 timeout, last signaled seq=2081253, last emitted seq=2081256
May 17 11:18:00 ws01 kernel: [11831.268051] [drm] No hardware hang detected. 
Did some blocks stall?


If I can assist any further, please tell.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810546/comments/0


On 2018-06-12T21:27:50+00:00 andrey.grodzovsky wrote:

Can you load kernel with grub command line amdgpu.vm_update_mode=3 to
force CPU VM update mode and see if this makes the issue go away ?


Andrey

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810546/comments/1


On 2018-06-13T07:17:17+00:00 muelladdi wrote:

Added the grub cmdline and will investigate

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810546/comments/2


On 2018-06-16T15:47:54+00:00 song.fc wrote:

Hello, I think I'm experiencing the same problem here. My Ryzen 5 2400G
system freezes often, especially under some high cpu and disk activity,
even after the "Typical Current Idle" UEFI workaround. Sometimes I could
reboot with sysrq, most of the times I need a hard reset. The freezes
never leave a message in kernel log until today, after 2 months I built
my machine.


6月 16 23:29:00 sfc-DESKTOP kernel: [drm] No hardware hang detected. Did some 
blocks stall?
6月 16 23:29:00 sfc-DESKTOP kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring gfx timeout, last signaled seq=1217227, last emitted seq=1217229
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0:   at page 
0x00011241a000 from 27
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: [gfxhub] VMC page fault 
(src_id:0 ring:24 vmid:1 pasid:32768)
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0:   at page 
0x000112414000 from 27
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: [gfxhub] VMC page fault 
(src_id:0 ring:24 vmid:1 pasid:32768)
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0:   at page 
0x000112416000 from 27
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: [gfxhub] VMC page fault 
(src_id:0 ring:24 vmid:1 pasid:32768)
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0:   at page 
0x00011241 from 27
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: [gfxhub] VMC page fault 
(src_id:0 ring:24 vmid:1 pasid:32768)
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0:   at page 
0x000112412000 from 27
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: [gfxhub] VMC page fault 
(src_id:0 ring:24 vmid:1 pasid:32768)
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0:   at page 
0x00011241f000 from 27
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: [gfxhub] VMC page fault 
(src_id:0 ring:24 vmid:1 pasid:32768)
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0:   at page 
0x000112425000 from 27
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: [gfxhub] VMC page fault 
(src_id:0 ring:24 vmid:1 pasid:32768)
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0:   at page 
0x000112427000 from 27
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: [gfxhub] VMC page fault 
(src_id:0 ring:24 vmid:1 pasid:32768)
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x
6月 16 23:28:50 sfc-DESKTOP kernel: amdgpu :38:00.0:   at page 
0x000112429000 from 27
6月 16 23:28:50 

[Kernel-packages] [Bug 1810239] Re: amd_iommu conflict with Marvell Sata controller

2019-01-02 Thread Bug Watch Updater
** Changed in: linux (Debian)
   Status: Unknown => 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/1810239

Title:
  amd_iommu conflict with  Marvell Sata controller

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  This bug is to confirm that the Marvell 88SE9230 chipset bug presents
  under AMD's IOMMU implementation with Ubuntu 18.04 and the latest HWE
  Kernel

  This has similar characteristics to 
   - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089768

  System
   - AMD Athlon 200GE
   - Gigabyte GA-B450M-S2H board
   - Marvell 88SE9230 SATA Controller with latest Firmware

  Kernel
   - Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17

  
  If I boot the HWE 4.18.0-13-generic Kernel I get the errors reported above

  If I boot with "amd_iommu=off" the drives appear to work correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-07-02 (913 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-root ro verbose 
drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (158 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2c
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810239/+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 1518457] Re: kswapd0 100% CPU usage

2019-01-01 Thread Bug Watch Updater
** Bug watch added: Linux Kernel Bug Tracker #110501
   https://bugzilla.kernel.org/show_bug.cgi?id=110501

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

Title:
  kswapd0 100% CPU usage

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  As per bug 721896 and various others:

  I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory).
  Occasionally (about once a day), kswapd0 falls into a busy loop and
  spins on 100% CPU usage indefinitely. This can be provoked by
  copying/writing large files (e.g. dding a 256MB file), but it happens
  occasionally otherwise. System memory usage (not including
  buffers/caches) currently sits at 36%, which is typical[1]. Initially
  I had no swap space configured; I've since tried enabling a 256MB swap
  file, but the problem continues to occur and no swap space is used.
  The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`.

  Happy to provide further information/take further debugging actions.

  
  [1] Full output from `free`:
   total   used   free sharedbuffers cached
  Mem:   1014936 483448 531488  28556   9756 112700
  -/+ buffers/cache: 360992 653944
  Swap:   262140  0 262140

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 19:40 seq
   crw-rw 1 root audio 116, 33 Nov 19 19:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Nov 20 20:44:30 2015
  Ec2AMI: ami-1c552a76
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1518457/+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 1806682] Re: ACPI: Invalid passive threshold

2018-12-27 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => 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/1806682

Title:
  ACPI: Invalid passive threshold

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [1.423794] ACPI: Invalid passive threshold

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806682/+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 1752437] Re: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

2018-12-24 Thread Bug Watch Updater
** Bug watch added: Linux Kernel Bug Tracker #201775
   https://bugzilla.kernel.org/show_bug.cgi?id=201775

** Bug watch added: Linux Kernel Bug Tracker #201885
   https://bugzilla.kernel.org/show_bug.cgi?id=201885

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

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

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [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)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the patch labeled "possible fix for touchscreen" with 
4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  from upstream report:
  https://bugzilla.kernel.org/show_bug.cgi?id=198715

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1752437/+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 1801540] Re: Microphone distorted sound on ALC892

2018-12-20 Thread Bug Watch Updater
Launchpad has imported 4 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201613.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-11-03T17:36:51+00:00 lukycrociato wrote:

Created attachment 279301
alsa-info

I always got this issue only on Linux, every distro I tried including
Manjaro Linux, Debian, ubuntu had this problem.

Basically the microphone input sounds always distorted and "robotic"
even on high pitch. In all the programs I tried.

Workarounds as listed on the ArchWiki --->
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Microphone_crackling_with_Realtek_ALC892
have not changed anything.

Interesting thing though is that on FreeBSD this does not happen.

alsa-info on the attachments

Kernel version: Linux luky-MS-7A37 4.18.0-10-generic #11-Ubuntu SMP

alsa-version
Driver version: k4.18.0-10-generic
Library version:1.1.6
Utilities version:  1.1.6

Obviously this also happens on other kernels.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801540/comments/2


On 2018-11-27T17:14:54+00:00 lukycrociato wrote:

Created attachment 279675
Recording showing the noise

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801540/comments/12


On 2018-12-19T13:05:23+00:00 lukycrociato wrote:

I may confirm that recording without pulseaudio using ffmpeg -alsa
produces the same disturbed sound

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801540/comments/16


On 2018-12-20T11:52:30+00:00 lukycrociato wrote:

Motherboard model is an MSI B350M AM4 for Ryzen CPU's

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801540/comments/20


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  Microphone distorted sound on ALC892

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 50692] Re: New Sony Vaios hotkeys don't work (fn_key polling)

2018-12-19 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => Unknown

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

Title:
  New Sony Vaios hotkeys don't work (fn_key polling)

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

Bug description:
  On new Sony Vaios (FS and FJ series) hotkeys don't work.

  A piece of code that enables them as been released on gentoo forums.
  The programs runs as a service and as a config file in /etc/fsfn.conf.

  Here is the dmidecode output on my laptop:
  System Information
  Manufacturer: Sony Corporation
  Product Name: VGN-FJ3S_W

  Basically, the same config (default) enables hotkeys on all VGN-FN*
  computers and adding BRT_HACK_FJS=1 parameter in /etc/fsfn.conf files,
  enables them for VGN-FJ* series.

  As an attachement to this bug, here is the fsfn tarball (latest
  version from the gentoo boards).

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/50692/+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 1518457] Re: kswapd0 100% CPU usage

2018-12-19 Thread Bug Watch Updater
Launchpad has imported 55 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=65201.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-11-19T19:40:40+00:00 nleo wrote:

kswapd0 randomly load one core of CPU by 100%

Linux localhost 3.12.0-1-ARCH #1 SMP PREEMPT Wed Nov 6 09:06:27 CET 2013
x86_64 GNU/Linux

No swap enabled

Befor on same laptop was installed Ubuntu 12.04 and kernel 3.2 32-bit
pae, and there is no such problem.

[root@localhost ~]# free -mh
 total   used   free sharedbuffers cached
Mem:  3.8G   2.4G   1.3G 0B   150M   508M
-/+ buffers/cache:   1.8G   2.0G
Swap:   0B 0B 0B


[root@localhost ~]# cat /proc/meminfo
MemTotal:3935792 kB
MemFree: 1381360 kB
Buffers:  154216 kB
Cached:   533096 kB
SwapCached:0 kB
Active:  1958896 kB
Inactive: 438004 kB
Active(anon):1740916 kB
Inactive(anon):   136292 kB
Active(file): 217980 kB
Inactive(file):   301712 kB
Unevictable:   0 kB
Mlocked:   0 kB
SwapTotal: 0 kB
SwapFree:  0 kB
Dirty:  2064 kB
Writeback: 0 kB
AnonPages:   1709628 kB
Mapped:   196696 kB
Shmem:167620 kB
Slab:  81516 kB
SReclaimable:  61312 kB
SUnreclaim:20204 kB
KernelStack:1696 kB
PageTables:13088 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit: 1967896 kB
Committed_AS:3498576 kB
VmallocTotal:   34359738367 kB
VmallocUsed:  361304 kB
VmallocChunk:   34359300731 kB
HardwareCorrupted: 0 kB
AnonHugePages:157696 kB
HugePages_Total:   0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
DirectMap4k:   18476 kB
DirectMap2M: 4059136 kB

And I can't kill it. I heared that it's not good idea, but just for
lulz)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/comments/0


On 2013-11-20T23:32:02+00:00 atomlin wrote:

(In reply to nleo from comment #0)
> kswapd0 randomly load one core of CPU by 100%

You cannot issue a SIGKILL to 'kswapd' since it is
a kernel thread.

> CommitLimit: 1967896 kB
> Committed_AS:3498576 kB
   ^^^

Seem to be over committing memory.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/comments/1


On 2013-11-22T00:57:01+00:00 akpm wrote:

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Tue, 19 Nov 2013 19:40:40 + bugzilla-dae...@bugzilla.kernel.org
wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=65201
> 
> Bug ID: 65201
>Summary: kswapd0 randomly high cpu load
>Product: Memory Management
>Version: 2.5
> Kernel Version: 3.12
>   Hardware: x86-64
> OS: Linux
>   Tree: Mainline
> Status: NEW
>   Severity: normal
>   Priority: P1
>  Component: Other
>   Assignee: a...@linux-foundation.org
>   Reporter: n...@nm.ru
> Regression: No
> 
> kswapd0 randomly load one core of CPU by 100%
> 
> Linux localhost 3.12.0-1-ARCH #1 SMP PREEMPT Wed Nov 6 09:06:27 CET 2013
> x86_64
> GNU/Linux
> 
> No swap enabled
> 
> Befor on same laptop was installed Ubuntu 12.04 and kernel 3.2 32-bit pae,
> and
> there is no such problem.
> 
> [root@localhost ~]# free -mh
>  total   used   free sharedbuffers cached
> Mem:  3.8G   2.4G   1.3G 0B   150M   508M
> -/+ buffers/cache:   1.8G   2.0G
> Swap:   0B 0B 0B

hm, I wonder what kswapd is up to.

Could you please make it happen again and then

dmesg -n 7
dmesg -c
echo m > /proc/sysrq-trigger
echo t > /proc/sysrq-trigger
dmesg -s 100 > foo

then send us foo?

> 
> [root@localhost ~]# cat /proc/meminfo
> MemTotal:3935792 kB
> MemFree: 1381360 kB
> Buffers:  154216 kB
> Cached:   533096 kB
> SwapCached:0 kB
> Active:  1958896 kB
> Inactive: 438004 kB
> Active(anon):1740916 kB
> Inactive(anon):   136292 kB
> Active(file): 217980 kB
> Inactive(file):   301712 kB
> Unevictable:   0 kB
> Mlocked:   0 kB
> SwapTotal: 0 kB
> SwapFree:  0 kB
> Dirty:  2064 kB
> Writeback: 0 kB
> AnonPages:   1709628 kB
> Mapped:

[Kernel-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

2018-12-16 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Unknown

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1805154] Re: glibc 2.28-0ubuntu1 ADT test failure with linux 4.19.0-5.6

2018-12-15 Thread Bug Watch Updater
** Changed in: fedora
   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/1805154

Title:
  glibc 2.28-0ubuntu1 ADT test failure with linux 4.19.0-5.6

Status in Linux:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in Fedora:
  Invalid

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-bootstrap/disco/amd64/g/glibc/20181119_075302_9b2e2@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-bootstrap/disco/i386/g/glibc/20181119_064219_9b2e2@/log.gz

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

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


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

2018-12-14 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => Incomplete

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

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

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

Bug description:
  SRU Justification:

  [Impact]

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

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

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

  [Test Case]

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

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

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

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

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

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

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

  managable means every command hangs.

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

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

  thx in advance

  meno

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

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


[Kernel-packages] [Bug 1807608] Re: Not work Bluetooth

2018-12-09 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201945.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-09T18:44:08+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1807608

"I'm working with linux 4.19, and not work bluetooth. Not problem with
linux 4.18.20."

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807608/comments/2


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  Not work Bluetooth

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

Bug description:
  Hello,

  I'm working with linux 4.19, and not work bluetooth. Not problem with
  linux 4.18.20.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1807608/+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 1807406] Re: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device

2018-12-07 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201929.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-07T15:46:45+00:00 caravena wrote:

Hello,

Open bug in laucnhpad.net
https://bugs.launchpad.net/bugs/1807406

"Message after returning from suspension"

dmesg:
hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP 
device

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807406/comments/3


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from
  ISHTP device

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

Bug description:
  Hello,

  Message after returning from suspension

  dmesg:
  [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for 
response from ISHTP device
  [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for 
response from ISHTP device

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1807406/+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 1807375] Re: Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev 826c, hci ver 0008

2018-12-07 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201921.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-07T11:43:32+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1807375

dmesg:
Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev 826c, hci 
ver 0008

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807375/comments/2


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev
  826c, hci ver 0008

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

Bug description:
  Hello,

  dmesg:
  [   13.388386] Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, 
hci rev 826c, hci ver 0008

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1807375/+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 1807377] Re: i2c_hid i2c-ELAN2514:00: failed to change power setting.

2018-12-07 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201923.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-07T11:46:23+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1807377

dmesg:
i2c_hid i2c-ELAN2514:00: failed to change power setting.

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807377/comments/2


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  i2c_hid i2c-ELAN2514:00: failed to change power setting.

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

Bug description:
  Hello,

  dmesg:
  [1.862577] i2c_hid i2c-ELAN2514:00: failed to change power setting.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1807377/+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 1806863] Re: i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, using dummy regulator

2018-12-05 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201899.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-05T11:33:15+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1806863

dmesg:
i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, using dummy 
regulator

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806863/comments/3


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, using
  dummy regulator

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

Bug description:
  Hello,

  dmesg:
  [1.685824] i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, 
using dummy regulator

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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


[Kernel-packages] [Bug 1806649] Re: Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter

2018-12-04 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201875.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-04T10:54:44+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1806649

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

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806649/comments/3


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

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

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

Bug description:
  Hello,

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

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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


[Kernel-packages] [Bug 1806681] Re: hp_wmi: query 0xd returned error 0x5

2018-12-04 Thread Bug Watch Updater
Launchpad has imported 5 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201881.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-04T12:15:04+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1806681

dmesg:
hp_wmi: query 0xd returned error 0x5

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806681/comments/3


On 2018-12-04T12:28:47+00:00 colin.king wrote:

This does not appear to be an error to worry about. The WMI driver for
your machine is performing a feature query with the ACPI driver with
HPWMI_FEATURE2_QUERY. This seems to be a feature that is enabled on HP
WMI firmware from around 2009 onwards. Some machines may support this,
however it seems that your firmware does not seem to have support for
this, hence the query failure.

The kernel throws a warning message to indicate that this feature is not
supported. I doubt this is something you need to worry about.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806681/comments/5


On 2018-12-04T12:40:17+00:00 caravena wrote:

A more friendly message?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806681/comments/6


On 2018-12-04T12:43:30+00:00 colin.king wrote:

If we fill the kernel up with friendly messages it will be massive. It's
already got >100,000 kernel messages.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806681/comments/8


On 2018-12-04T12:45:32+00:00 colin.king wrote:

Most warnings like this are really for the per driver kernel developers.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806681/comments/9


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  hp_wmi: query 0xd returned error 0x5

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

Bug description:
  Hello,

  dmesg:
  [   18.296366] hp_wmi: query 0xd returned error 0x5

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806681/+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 1806437] Re: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)

2018-12-04 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201885.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-04T13:00:48+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1806437

dmesg:
acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first 
instance was on PNP0C14:01)

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806437/comments/5


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  acpi PNP0C14:02: duplicate WMI GUID
  05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on
  PNP0C14:01)

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

Bug description:
  Hello,

  dmesg:
  [   15.390738] acpi PNP0C14:02: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806437/+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 1806682] Re: ACPI: Invalid passive threshold

2018-12-04 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201883.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-04T12:24:33+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1806682

dmesg:
ACPI: Invalid passive threshold

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806682/comments/3


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  ACPI: Invalid passive threshold

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

Bug description:
  Hello,

  dmesg:
  [1.423794] ACPI: Invalid passive threshold

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806682/+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 1806660] Re: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids

2018-12-04 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201877.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-04T11:13:16+00:00 caravena wrote:

Hello,

Open bug in laumchpad.net
https://bugs.launchpad.net/bugs/1806660

The sound from the notebook speakers sounds randomly. However, you can
always listen with hearing aids.

In the upper part of gnome-shell it appears that they are with the
headphones, and it is not like that.

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806660/comments/2


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  The sound from the notebook speakers sounds randomly. However, you can
  always listen with hearing aids

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

Bug description:
  Hello,

  The sound from the notebook speakers sounds randomly. However, you can
  always listen with hearing aids.

  In the upper part of gnome-shell it appears that they are with the
  headphones, and it is not like that.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806660/+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


  1   2   3   4   5   6   7   8   9   >