[Kernel-packages] [Bug 1816783] Re: linux-azure: 4.18.0-1012.12 -proposed tracker

2019-02-26 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1012.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816783/+subscriptions

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


[Kernel-packages] [Bug 397750] Re: mouse : input : event field not found

2019-02-26 Thread Christopher M. Penalver
Stephan Berger, it will help immensely if you use Ubuntu with the computer the 
problem is reproducible with and file a new report via a terminal to provide 
necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
   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/397750

Title:
  mouse : input : event field not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Jul 10 10:33:55 jxt4210i2 kernel: [ 8136.876360] input input18: event field 
not found
  Jul 10 10:33:55 jxt4210i2 kernel: [ 8136.876367] input input18: event field 
not found

  This message is flooding my kern.log, messages and syslog

  Reason for this message is USB mouse Verbatim Rapier V2 bought on the 
beginning of 2009.
  Message is flooding my logs since then.

  That time I was using 2.6.27 on intrepid.
  Then short time 2.6.28 on jaunty.
  Currently 2.6.30-9 from https://launchpad.net/~xorg-edgers/+archive/ppa (on 
jaunty)
  (I will update to 2.6.30-10 but I'm convinced it will not help.)
  I tryed also server and rt versions of kernel.

  Similar Bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/386671
  Reporter closed as hardware problem.
  But I have here 2 same Rapier V2 and multiple notebooks, kernels .. all the 
same.

  Identical problem on Arch linux bugs: http://bugs.archlinux.org/task/15461
  No answer and different mouse.

  Importance of this is low.
  In truth, it's only an annoyance.
  But as I'm trying to help with bug reports, and it's not very helpful to have 
that message all over important logs.

  If I misjudged the right package for report, please move it on the right 
place. I really don't know which part of the system is doing it (apart from the 
"kernel" string in messages).
  --- 
  AlsaVersion:
   Advanced Linux Sound Architecture Driver Version 1.0.22.1.
   Compiled on Mar 28 2010 for kernel 2.6.32-18-generic (SMP).
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jay5925 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf064 irq 30'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:83847616,10cf,00100201 
HDA:11c11040,11c10001,00100200'
 Controls  : 21
 Simple ctrls  : 14
  DistroRelease: Ubuntu 10.04
  HibernationDevice: RESUME=UUID=0ba96fad-f105-435f-bab0-40db015d72c3
  MachineType: FUJITSU SIEMENS LIFEBOOK T4210
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 product info: "O2Micro", "SmartCardBus Reader", "V1.0", ""
 manfid: 0x, 0x0001
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 5.0V 16-bit PC Card
 Subdevice 0 (function 0) [unbound]
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-18-generic root=/dev/mapper/vgk-root 
ro quiet splash
  ProcEnviron:
   LANGUAGE=sk_SK:sk:en_GB:en
   PATH=(custom, no user)
   LANG=sk_SK.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
  Regression: No
  RelatedPackageVersions: linux-firmware 1.33
  Reproducible: Yes
  Tags: lucid kconfig needs-upstream-testing
  Uname: Linux 2.6.32-18-generic i686
  UserGroups: adm admin cdrom dialout dip fuse lpadmin netdev plugdev 
sambashare video
  dmi.bios.date: 12/21/2006
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.09
  dmi.board.name: FJNB1B9
  dmi.board.vendor: FUJITSU
  dmi.board.version: CP291221-01
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: T42__
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd12/21/2006:svnFUJITSUSIEMENS:pnLIFEBOOKT4210:pvr:rvnFUJITSU:rnFJNB1B9:rvrCP291221-01:cvnFUJITSUSIEMENS:ct10:cvrT42__:
  dmi.product.name: LIFEBOOK T4210
  dmi.sys.vendor: FUJITSU SIEMENS

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

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


[Kernel-packages] [Bug 1814760] Re: linux-kvm: 4.18.0-1008.8 -proposed tracker

2019-02-26 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.18.0-1008.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814760/+subscriptions

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


[Kernel-packages] [Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list

2019-02-26 Thread Kai-Heng Feng
kamiccolo, Nebojsa Grujic,

Is secure boot enabled?

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

Title:
  MODSIGN: Couldn't get UEFI db list

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Kernel is having problem loading or validating certificates. Looking
  over the internet looks like this is a kernel issue.

  Patchs from other distro:
  https://bugzilla.redhat.com/show_bug.cgi?id=1497559
  - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch
  - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch
  - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch

  
  [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: 
ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734'
  [1.203352] Couldn't get size: 0x800e
  [1.203354] MODSIGN: Couldn't get UEFI db list
  [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate 
Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys 
keyring
  [1.205102] Couldn't get size: 0x800e
  [1.205103] MODSIGN: Couldn't get UEFI dbx list

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wellington   1429 F pulseaudio
   /dev/snd/pcmC1D3p:   wellington   1429 F...m pulseaudio
   /dev/snd/controlC1:  wellington   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 22:37:13 2018
  HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e
  InstallationDate: Installed on 2018-01-16 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD5 R5
  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: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


Re: [Kernel-packages] [Bug 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-26 Thread Christopher M. Penalver
opensas:

1)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816947/comments/43
 >"Then I tried with several versions from the upstream kernels..."

Which upstream kernels did you test precisely?

2)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816947/comments/46
 >"Any idea about how should I proceed?"

If it is confirmed via your testing that it doesn't work in Ubuntu 
kernel 4.13.0-19, then one could reverse commit bisect from 4.13.0-19 to 
4.13.0-21 to find which commit(s) is the fix following 
https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_Ubuntu_kernels 
.

-- 
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] Touchpad not working after last apt-get upgrade

Status in libinput package in Ubuntu:
  Invalid
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 

[Kernel-packages] [Bug 1814760] Re: linux-kvm: 4.18.0-1008.8 -proposed tracker

2019-02-26 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux-kvm: 4.18.0-1008.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814760/+subscriptions

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


[Kernel-packages] [Bug 1817832] Re: qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256

2019-02-26 Thread Frank Heimes
** Changed in: ubuntu-power-systems
 Assignee: Canonical Server Team (canonical-server) => Canonical Kernel 
Team (canonical-kernel-team)

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

Title:
  qemu crashes with `kvm_init_vcpu failed: Invalid argument` during
  guest boot cores >256

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2019-02-14 
23:48:15 ==
  ---Problem Description---
  qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot 
cores >256 but the error message is not clearly explains it.
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-1016-ibm-gt
   
  Machine Type = power9 ppc64le
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   # /usr/bin/qemu-system-ppc64 -smp 257 -enable-kvm -monitor stdio
  qemu-system-ppc64: warning: Number of SMP cpus requested (257) exceeds the 
recommended cpus supported by KVM (128)
  qemu-system-ppc64: warning: Number of hotpluggable cpus requested (257) 
exceeds the recommended cpus supported by KVM (128)
  QEMU 2.11.1 monitor - type 'help' for more information
  (qemu) kvm_init_vcpu failed: Invalid argument

  Expected Result:
  1. Guest should boot fine or
  2.  Proper error message stating cores >256 need to have thread>1 because 
smp=512 with threads=2 works fine like below

  # /usr/bin/qemu-system-ppc64 -smp 512,cores=256,threads=2 -enable-kvm 
-monitor stdio
  qemu-system-ppc64: warning: Number of SMP cpus requested (512) exceeds the 
recommended cpus supported by KVM (128)
  qemu-system-ppc64: warning: Number of hotpluggable cpus requested (512) 
exceeds the recommended cpus supported by KVM (128)
  QEMU 2.11.1 monitor - type 'help' for more information
  (qemu) VNC server running on ::1:5900
  (qemu) info status
  VM status: running

  
   
  Userspace tool common name: ii  qemu-system-ppc   
   1:2.11+dfsg-1ubuntu7.8-1ibm3   ppc64el  QEMU full system 
emulation binaries (ppc) 
   
  The userspace tool has the following bit modes: both 

  Userspace rpm: ii  qemu-system-ppc
  1:2.11+dfsg-1ubuntu7.8-1ibm3   ppc64el  QEMU full system
  emulation binaries (ppc)

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  commit 1e175d2e07c71d9574f5b1c74523abca54e2654f
  Author: Sam Bobroff 
  Date:   Wed Jul 25 16:12:02 2018 +1000

  commit b5c6f7607b908b1445f2556c8d2f3b1ec5fc5aa8
  Author: Paul Mackerras 
  Date:   Thu Jul 26 15:38:41 2018 +1000

  commit 1ebe6b81ebdba8faf377d1d7d84ad9368e7a0bae
  Author: Paul Mackerras 
  Date:   Thu Jul 26 14:53:54 2018 +1000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1817832/+subscriptions

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


[Kernel-packages] [Bug 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-26 Thread opensas
All right, I took your advice and tested several older kernels:

linux-headers-4.10.0-19_4.10.0-19.21_all.deb
linux-headers-4.10.0-19-generic_4.10.0-19.21_amd64.deb
linux-headers-4.10.0-26_4.10.0-26.30_all.deb
linux-headers-4.10.0-26-generic_4.10.0-26.30_amd64.deb
linux-headers-4.11.0-13_4.11.0-13.19_all.deb
linux-headers-4.11.0-13-generic_4.11.0-13.19_amd64.deb
linux-headers-4.12.0-13_4.12.0-13.14_all.deb
linux-headers-4.12.0-13-generic_4.12.0-13.14_amd64.deb
linux-image-4.10.0-19-generic_4.10.0-19.21_amd64.deb
linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb
linux-image-4.11.0-13-generic_4.11.0-13.19_amd64.deb
linux-image-4.12.0-13-generic_4.12.0-13.14_amd64.deb

I installed all these deb files, and booted with them, and the bug is
STILL present.

It seems like I can't reproduce the working kernel of the artful livecd.

Any idea about how should I proceed?

-- 
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] Touchpad not working after last apt-get upgrade

Status in libinput package in Ubuntu:
  Invalid
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
  

[Kernel-packages] [Bug 1817832] Re: qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256

2019-02-26 Thread Christian Ehrhardt 
TBH this isn't about "a warning/error message to be missing" - it is a request 
to add the feature to be able to "Allow creating max number of VCPUs on POWER9" 
and should be declared like that.
@JFH/@Manjo - I leave it to you to discuss that and make the change.

Furthermore the patches referred are kernel only, so qemu task is
invalid and I'm adding a kernel task instead.

And finally all patches are in 4.19 upstream, so Disco is already fix-released 
except for SRU considerations. Since Power9 is >=Bionic that is the max SRU 
target (if any).
I'll add the bug tasks but leave it to JFH/Manjo/Kernel Team to set them to 
anything but "NEW".

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

** Also affects: qemu (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

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

** No longer affects: qemu (Ubuntu Bionic)

** No longer affects: qemu (Ubuntu Cosmic)

** Changed in: qemu (Ubuntu)
   Status: New => Invalid

** Changed in: qemu (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
(unassigned)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

Title:
  qemu crashes with `kvm_init_vcpu failed: Invalid argument` during
  guest boot cores >256

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2019-02-14 
23:48:15 ==
  ---Problem Description---
  qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot 
cores >256 but the error message is not clearly explains it.
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-1016-ibm-gt
   
  Machine Type = power9 ppc64le
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   # /usr/bin/qemu-system-ppc64 -smp 257 -enable-kvm -monitor stdio
  qemu-system-ppc64: warning: Number of SMP cpus requested (257) exceeds the 
recommended cpus supported by KVM (128)
  qemu-system-ppc64: warning: Number of hotpluggable cpus requested (257) 
exceeds the recommended cpus supported by KVM (128)
  QEMU 2.11.1 monitor - type 'help' for more information
  (qemu) kvm_init_vcpu failed: Invalid argument

  Expected Result:
  1. Guest should boot fine or
  2.  Proper error message stating cores >256 need to have thread>1 because 
smp=512 with threads=2 works fine like below

  # /usr/bin/qemu-system-ppc64 -smp 512,cores=256,threads=2 -enable-kvm 
-monitor stdio
  qemu-system-ppc64: warning: Number of SMP cpus requested (512) exceeds the 
recommended cpus supported by KVM (128)
  qemu-system-ppc64: warning: Number of hotpluggable cpus requested (512) 
exceeds the recommended cpus supported by KVM (128)
  QEMU 2.11.1 monitor - type 'help' for more information
  (qemu) VNC server running on ::1:5900
  (qemu) info status
  VM status: running

  
   
  Userspace tool common name: ii  qemu-system-ppc   
   1:2.11+dfsg-1ubuntu7.8-1ibm3   ppc64el  QEMU full system 
emulation binaries (ppc) 
   
  The userspace tool has the following bit modes: both 

  Userspace rpm: ii  qemu-system-ppc
  1:2.11+dfsg-1ubuntu7.8-1ibm3   ppc64el  QEMU full system
  emulation binaries (ppc)

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  commit 1e175d2e07c71d9574f5b1c74523abca54e2654f
  Author: Sam Bobroff 
  Date:   Wed Jul 25 16:12:02 2018 +1000

  commit b5c6f7607b908b1445f2556c8d2f3b1ec5fc5aa8
  Author: Paul Mackerras 
  Date:   Thu Jul 26 15:38:41 2018 +1000

  commit 1ebe6b81ebdba8faf377d1d7d84ad9368e7a0bae
  Author: Paul Mackerras 
  Date:   Thu Jul 26 14:53:54 2018 +1000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1817832/+subscriptions

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


[Kernel-packages] [Bug 1787695] Re: : unable to handle kernel paging request at ffff9f2ed2aa5844

2019-02-26 Thread Kai-Heng Feng
Thanks for the info.

** Changed in: linux (Ubuntu)
   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/1787695

Title:
  : unable to handle kernel paging request at 9f2ed2aa5844

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Since going from 4.13 to 4.15, I'm getting crashes where the system
  completely locks up and display freezes. Below is what syslog had
  after my most recent.

  I'm on Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18, the system is a
  Ryzen 1600 on AsRock AB350M with latest UEFI, RX 480 using open
  drivers.

  (I would have used ubuntu-bug, but it says "not an official package"
  even with ubuntu-bug linux. Also, lspci -vnvn says Input/output error
  so I could not include that.)

  Aug 18 08:39:19 freyja kernel: [20514.280608] BUG: unable to handle kernel 
paging request at 9f2ed2aa5844
  Aug 18 08:39:19 freyja kernel: [20514.280621] IP: SyS_read+0x16/0xc0
  Aug 18 08:39:19 freyja kernel: [20514.280623] PGD 81e875067 P4D 81e875067 PUD 
0 
  Aug 18 08:39:19 freyja kernel: [20514.280630] Oops: 0002 [#1] SMP NOPTI
  Aug 18 08:39:19 freyja kernel: [20514.280633] Modules linked in: xt_CHECKSUM 
iptable_mangle nls_iso8859_1 ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo 
xt_addrtype ebtable_filter xt_conntrack ebtables br_netfilter bridge stp llc 
aufs ip6table_filter ip6_tables xt_TCPMSS acpi_call(OE) ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack xt_tcpudp pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) iptable_filter ip_tables x_tables sch_fq_codel 
binfmt_misc nct6775 btrfs zstd_compress lm78 hwmon_vid snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_seq_midi snd_seq_midi_event 
snd_hda_intel snd_rawmidi snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep 
crct10dif_pclmul crc32_pclmul joydev ghash_clmulni_intel snd_pcm ccp snd_seq 
pcbc snd_seq_device
  Aug 18 08:39:19 freyja kernel: [20514.280692]  snd_timer snd aesni_intel 
soundcore aes_x86_64 input_leds crypto_simd glue_helper cryptd serio_raw 
wmi_bmof i2c_piix4 k10temp shpchp mac_hid kvm irqbypass parport_pc ppdev lp 
parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
hid_generic usbhid hid amdkfd amd_iommu_v2 amdgpu chash i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt uas fb_sys_fops drm nvme r8169 
usb_storage ahci nvme_core mii libahci wmi gpio_amdpt gpio_generic
  Aug 18 08:39:19 freyja kernel: [20514.280737] CPU: 1 PID: 4527 Comm: 
Chrome_IOThread Tainted: GW  OE4.15.0-32-generic #35~16.04.1-Ubuntu
  Aug 18 08:39:19 freyja kernel: [20514.280739] Hardware name: To Be Filled By 
O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P4.90 07/06/2018
  Aug 18 08:39:19 freyja kernel: [20514.280743] RIP: 0010:SyS_read+0x16/0xc0
  Aug 18 08:39:19 freyja kernel: [20514.280746] RSP: 0018:9f2e8a453f08 
EFLAGS: 00010246
  Aug 18 08:39:19 freyja kernel: [20514.280749] RAX: 8c078eb0 RBX: 
9f2e8a453f58 RCX: 7f040245d9e0
  Aug 18 08:39:19 freyja kernel: [20514.280751] RDX: 0001 RSI: 
7f040245d9d7 RDI: 0010
  Aug 18 08:39:19 freyja kernel: [20514.280754] RBP: 9f2e8a453f28 R08: 
7f03f8001a30 R09: 0001
  Aug 18 08:39:19 freyja kernel: [20514.280756] R10:  R11: 
 R12: 
  Aug 18 08:39:19 freyja kernel: [20514.280758] R13: 7f040245d9d7 R14: 
0001 R15: 
  Aug 18 08:39:19 freyja kernel: [20514.280761] FS:  7f040245e700() 
GS:8a775ec4() knlGS:
  Aug 18 08:39:19 freyja kernel: [20514.280763] CS:  0010 DS:  ES:  
CR0: 80050033
  Aug 18 08:39:19 freyja kernel: [20514.280766] CR2: 9f2ed2aa5844 CR3: 
0007a29a2000 CR4: 003406e0
  Aug 18 08:39:19 freyja kernel: [20514.280768] Call Trace:
  Aug 18 08:39:19 freyja kernel: [20514.280775]  do_syscall_64+0x73/0x130
  Aug 18 08:39:19 freyja kernel: [20514.280781]  
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  Aug 18 08:39:19 freyja kernel: [20514.280784] RIP: 0033:0x7f0412e6b51d
  Aug 18 08:39:19 freyja kernel: [20514.280786] RSP: 002b:7f040245d9c0 
EFLAGS: 0293 ORIG_RAX: 
  Aug 18 08:39:19 freyja kernel: [20514.280789] RAX: ffda RBX: 
0010 RCX: 7f0412e6b51d
  Aug 18 08:39:19 freyja kernel: [20514.280791] RDX: 0001 RSI: 
7f040245d9d7 RDI: 0010
  Aug 18 08:39:19 freyja kernel: [20514.280793] RBP: 7f040245d9f0 R08: 
7f03f8001a30 R09: 0001
  Aug 18 08:39:19 freyja kernel: [20514.280795] R10: 7f040245d9e0 R11: 
0293 R12: 7f03f8002420
  Aug 18 08:39:19 freyja kernel: [20514.280797] R13: 

[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport

2019-02-26 Thread md_5
Thanks for the link Guilherme, guess that answers that question.
Given March 4 is just round the corner, I am not sure there is much can be done 
at this point, but I will however just echo what Tom beat me to saying:

As a software developer I fully understand and recognise the need to
delay things for various reasons even if it may seem everything is
primed and ready to go.

That being said I think the overall response time here has not been
great at all.

A kernel regression which breaks user space programs (including the
default TTY login), and has a small, tested patch available should
absolutely not take 3-4 weeks to be released.

I understand that this new March 4 release will have additional
unrelated patches that need that testing time, but I think breaking from
the standard SRU cycle to either revert the problematic patches, or
apply the fix would absolutely have been worth it - just look at the 13
duplicates of this bug and the posts on various other web forums /
support sites.

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

Title:
  Userspace break as a result of missing patch backport

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Hi,

  The most recent set of Ubuntu kernels applied a variety of tty patches
  including:
  
https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b

  But have not applied the more recent
  
https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0
  patch.

  This second patch is required to prevent a rather serious regression
  where userspace applications reading from stdin can receive EAGAIN
  when they should not.

  I will try to link correspondence from the mailing list archives once
  they are available, but for now if you have access to the linux-
  console mailing list you can find discussion under the thread
  "Userspace break? read from STDIN returns EAGAIN if tty is "touched"".

  I would appreciate it if this could be examined soon as it is a
  regression on userspace.

  Thanks
  Michael

  
  Good:
  4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018

  
  Bad:
  4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019

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

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


[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport

2019-02-26 Thread Tom Reynolds
Considering that this is a regression, with major impact (TTY login no
longer possible, often no graphical login either), many affected users
on (amongst other) the latest LTS release, and both this fact and how to
fix it has been known since at least January 30, I am puzzled as to why
this is being handled as an update with the default stable release
cadence.

Could you kindly explain the following (since I may just be misunderstanding 
how things are handled):
Was rolling back the breaking (since incomplete) patchset (which introduced 
this issue) not an option?
Has testing on 18.04 and 16.04 brought up new problems, which would have had 
even more serious impact?
How is "importance" calculated (personally I would have set it to "critical" or 
"major", if those are available)?

Thanks.

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

Title:
  Userspace break as a result of missing patch backport

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Hi,

  The most recent set of Ubuntu kernels applied a variety of tty patches
  including:
  
https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b

  But have not applied the more recent
  
https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0
  patch.

  This second patch is required to prevent a rather serious regression
  where userspace applications reading from stdin can receive EAGAIN
  when they should not.

  I will try to link correspondence from the mailing list archives once
  they are available, but for now if you have access to the linux-
  console mailing list you can find discussion under the thread
  "Userspace break? read from STDIN returns EAGAIN if tty is "touched"".

  I would appreciate it if this could be examined soon as it is a
  regression on userspace.

  Thanks
  Michael

  
  Good:
  4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018

  
  Bad:
  4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019

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

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


[Kernel-packages] [Bug 1787695] Re: : unable to handle kernel paging request at ffff9f2ed2aa5844

2019-02-26 Thread Otus
I upgraded to 18.04 in the meanwhile and am running 4.18 from linux-
generic-hwe-18.04. It has not given me these errors so far.

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

Title:
  : unable to handle kernel paging request at 9f2ed2aa5844

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since going from 4.13 to 4.15, I'm getting crashes where the system
  completely locks up and display freezes. Below is what syslog had
  after my most recent.

  I'm on Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18, the system is a
  Ryzen 1600 on AsRock AB350M with latest UEFI, RX 480 using open
  drivers.

  (I would have used ubuntu-bug, but it says "not an official package"
  even with ubuntu-bug linux. Also, lspci -vnvn says Input/output error
  so I could not include that.)

  Aug 18 08:39:19 freyja kernel: [20514.280608] BUG: unable to handle kernel 
paging request at 9f2ed2aa5844
  Aug 18 08:39:19 freyja kernel: [20514.280621] IP: SyS_read+0x16/0xc0
  Aug 18 08:39:19 freyja kernel: [20514.280623] PGD 81e875067 P4D 81e875067 PUD 
0 
  Aug 18 08:39:19 freyja kernel: [20514.280630] Oops: 0002 [#1] SMP NOPTI
  Aug 18 08:39:19 freyja kernel: [20514.280633] Modules linked in: xt_CHECKSUM 
iptable_mangle nls_iso8859_1 ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo 
xt_addrtype ebtable_filter xt_conntrack ebtables br_netfilter bridge stp llc 
aufs ip6table_filter ip6_tables xt_TCPMSS acpi_call(OE) ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack xt_tcpudp pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) iptable_filter ip_tables x_tables sch_fq_codel 
binfmt_misc nct6775 btrfs zstd_compress lm78 hwmon_vid snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_seq_midi snd_seq_midi_event 
snd_hda_intel snd_rawmidi snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep 
crct10dif_pclmul crc32_pclmul joydev ghash_clmulni_intel snd_pcm ccp snd_seq 
pcbc snd_seq_device
  Aug 18 08:39:19 freyja kernel: [20514.280692]  snd_timer snd aesni_intel 
soundcore aes_x86_64 input_leds crypto_simd glue_helper cryptd serio_raw 
wmi_bmof i2c_piix4 k10temp shpchp mac_hid kvm irqbypass parport_pc ppdev lp 
parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
hid_generic usbhid hid amdkfd amd_iommu_v2 amdgpu chash i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt uas fb_sys_fops drm nvme r8169 
usb_storage ahci nvme_core mii libahci wmi gpio_amdpt gpio_generic
  Aug 18 08:39:19 freyja kernel: [20514.280737] CPU: 1 PID: 4527 Comm: 
Chrome_IOThread Tainted: GW  OE4.15.0-32-generic #35~16.04.1-Ubuntu
  Aug 18 08:39:19 freyja kernel: [20514.280739] Hardware name: To Be Filled By 
O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P4.90 07/06/2018
  Aug 18 08:39:19 freyja kernel: [20514.280743] RIP: 0010:SyS_read+0x16/0xc0
  Aug 18 08:39:19 freyja kernel: [20514.280746] RSP: 0018:9f2e8a453f08 
EFLAGS: 00010246
  Aug 18 08:39:19 freyja kernel: [20514.280749] RAX: 8c078eb0 RBX: 
9f2e8a453f58 RCX: 7f040245d9e0
  Aug 18 08:39:19 freyja kernel: [20514.280751] RDX: 0001 RSI: 
7f040245d9d7 RDI: 0010
  Aug 18 08:39:19 freyja kernel: [20514.280754] RBP: 9f2e8a453f28 R08: 
7f03f8001a30 R09: 0001
  Aug 18 08:39:19 freyja kernel: [20514.280756] R10:  R11: 
 R12: 
  Aug 18 08:39:19 freyja kernel: [20514.280758] R13: 7f040245d9d7 R14: 
0001 R15: 
  Aug 18 08:39:19 freyja kernel: [20514.280761] FS:  7f040245e700() 
GS:8a775ec4() knlGS:
  Aug 18 08:39:19 freyja kernel: [20514.280763] CS:  0010 DS:  ES:  
CR0: 80050033
  Aug 18 08:39:19 freyja kernel: [20514.280766] CR2: 9f2ed2aa5844 CR3: 
0007a29a2000 CR4: 003406e0
  Aug 18 08:39:19 freyja kernel: [20514.280768] Call Trace:
  Aug 18 08:39:19 freyja kernel: [20514.280775]  do_syscall_64+0x73/0x130
  Aug 18 08:39:19 freyja kernel: [20514.280781]  
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  Aug 18 08:39:19 freyja kernel: [20514.280784] RIP: 0033:0x7f0412e6b51d
  Aug 18 08:39:19 freyja kernel: [20514.280786] RSP: 002b:7f040245d9c0 
EFLAGS: 0293 ORIG_RAX: 
  Aug 18 08:39:19 freyja kernel: [20514.280789] RAX: ffda RBX: 
0010 RCX: 7f0412e6b51d
  Aug 18 08:39:19 freyja kernel: [20514.280791] RDX: 0001 RSI: 
7f040245d9d7 RDI: 0010
  Aug 18 08:39:19 freyja kernel: [20514.280793] RBP: 7f040245d9f0 R08: 
7f03f8001a30 R09: 0001
  Aug 18 08:39:19 freyja kernel: [20514.280795] R10: 7f040245d9e0 R11: 
0293 R12: 7f03f8002420
  Aug 18 08:39:19 freyja 

[Kernel-packages] [Bug 1816782] Re: linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

2019-02-26 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in 18/candidate channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in 18/candidate channel
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816782/+subscriptions

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


[Kernel-packages] [Bug 1815808] Re: Thunderbolt Ethernet high-traffic exception

2019-02-26 Thread Kai-Heng Feng
The TB16's ASMedia xHC (USB controller) dies:
[89535.271614] xhci_hcd :0a:00.0: xHCI host not responding to stop endpoint 
command.
[89535.271945] xhci_hcd :0a:00.0: xHCI host controller not responding, 
assume dead

I'll escalate this issue to Dell.

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

Title:
  Thunderbolt Ethernet high-traffic exception

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running iperf3 on Dell XP-15 with TB-10 Thunderbolt dock causes a
  kernel exception and ethernet failure after about 30 seconds.

  Easy to reproduce.  Connect to another machine via Gig-E and run
  iperf3 in either direction until the problem occurs.  Should run 900+
  Mb in either direction.  On one occasion I also lost the USB ports.
  However the display continues to work.

  
  # uname -a
  Linux hauser 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  # apt install iperf3
  # iperf3 -s

  
  # apt install iperf3
  # iperf3 -c my-machine -t 1000 # send to my machine
  # iperf3 -c my-machine -t 1000 -R  # receive data from my machine

  When the bitrate drops to zero, look in syslog for the exception.

  Note: Until recently the TB-10 Ethernet would not receive full speed.
  (prior to -43 kernel) Did not see this problem before the Ethernet
  performance increased.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1994 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 13 13:54:28 2019
  HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
  InstallationDate: Installed on 2018-11-19 (86 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0 
mem_sleep_default=deep
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 02MJVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1787695] Re: : unable to handle kernel paging request at ffff9f2ed2aa5844

2019-02-26 Thread Kai-Heng Feng
Do you still have this issue on latest HWE kernel?

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

Title:
  : unable to handle kernel paging request at 9f2ed2aa5844

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since going from 4.13 to 4.15, I'm getting crashes where the system
  completely locks up and display freezes. Below is what syslog had
  after my most recent.

  I'm on Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18, the system is a
  Ryzen 1600 on AsRock AB350M with latest UEFI, RX 480 using open
  drivers.

  (I would have used ubuntu-bug, but it says "not an official package"
  even with ubuntu-bug linux. Also, lspci -vnvn says Input/output error
  so I could not include that.)

  Aug 18 08:39:19 freyja kernel: [20514.280608] BUG: unable to handle kernel 
paging request at 9f2ed2aa5844
  Aug 18 08:39:19 freyja kernel: [20514.280621] IP: SyS_read+0x16/0xc0
  Aug 18 08:39:19 freyja kernel: [20514.280623] PGD 81e875067 P4D 81e875067 PUD 
0 
  Aug 18 08:39:19 freyja kernel: [20514.280630] Oops: 0002 [#1] SMP NOPTI
  Aug 18 08:39:19 freyja kernel: [20514.280633] Modules linked in: xt_CHECKSUM 
iptable_mangle nls_iso8859_1 ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo 
xt_addrtype ebtable_filter xt_conntrack ebtables br_netfilter bridge stp llc 
aufs ip6table_filter ip6_tables xt_TCPMSS acpi_call(OE) ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack xt_tcpudp pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) iptable_filter ip_tables x_tables sch_fq_codel 
binfmt_misc nct6775 btrfs zstd_compress lm78 hwmon_vid snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_seq_midi snd_seq_midi_event 
snd_hda_intel snd_rawmidi snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep 
crct10dif_pclmul crc32_pclmul joydev ghash_clmulni_intel snd_pcm ccp snd_seq 
pcbc snd_seq_device
  Aug 18 08:39:19 freyja kernel: [20514.280692]  snd_timer snd aesni_intel 
soundcore aes_x86_64 input_leds crypto_simd glue_helper cryptd serio_raw 
wmi_bmof i2c_piix4 k10temp shpchp mac_hid kvm irqbypass parport_pc ppdev lp 
parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
hid_generic usbhid hid amdkfd amd_iommu_v2 amdgpu chash i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt uas fb_sys_fops drm nvme r8169 
usb_storage ahci nvme_core mii libahci wmi gpio_amdpt gpio_generic
  Aug 18 08:39:19 freyja kernel: [20514.280737] CPU: 1 PID: 4527 Comm: 
Chrome_IOThread Tainted: GW  OE4.15.0-32-generic #35~16.04.1-Ubuntu
  Aug 18 08:39:19 freyja kernel: [20514.280739] Hardware name: To Be Filled By 
O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P4.90 07/06/2018
  Aug 18 08:39:19 freyja kernel: [20514.280743] RIP: 0010:SyS_read+0x16/0xc0
  Aug 18 08:39:19 freyja kernel: [20514.280746] RSP: 0018:9f2e8a453f08 
EFLAGS: 00010246
  Aug 18 08:39:19 freyja kernel: [20514.280749] RAX: 8c078eb0 RBX: 
9f2e8a453f58 RCX: 7f040245d9e0
  Aug 18 08:39:19 freyja kernel: [20514.280751] RDX: 0001 RSI: 
7f040245d9d7 RDI: 0010
  Aug 18 08:39:19 freyja kernel: [20514.280754] RBP: 9f2e8a453f28 R08: 
7f03f8001a30 R09: 0001
  Aug 18 08:39:19 freyja kernel: [20514.280756] R10:  R11: 
 R12: 
  Aug 18 08:39:19 freyja kernel: [20514.280758] R13: 7f040245d9d7 R14: 
0001 R15: 
  Aug 18 08:39:19 freyja kernel: [20514.280761] FS:  7f040245e700() 
GS:8a775ec4() knlGS:
  Aug 18 08:39:19 freyja kernel: [20514.280763] CS:  0010 DS:  ES:  
CR0: 80050033
  Aug 18 08:39:19 freyja kernel: [20514.280766] CR2: 9f2ed2aa5844 CR3: 
0007a29a2000 CR4: 003406e0
  Aug 18 08:39:19 freyja kernel: [20514.280768] Call Trace:
  Aug 18 08:39:19 freyja kernel: [20514.280775]  do_syscall_64+0x73/0x130
  Aug 18 08:39:19 freyja kernel: [20514.280781]  
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  Aug 18 08:39:19 freyja kernel: [20514.280784] RIP: 0033:0x7f0412e6b51d
  Aug 18 08:39:19 freyja kernel: [20514.280786] RSP: 002b:7f040245d9c0 
EFLAGS: 0293 ORIG_RAX: 
  Aug 18 08:39:19 freyja kernel: [20514.280789] RAX: ffda RBX: 
0010 RCX: 7f0412e6b51d
  Aug 18 08:39:19 freyja kernel: [20514.280791] RDX: 0001 RSI: 
7f040245d9d7 RDI: 0010
  Aug 18 08:39:19 freyja kernel: [20514.280793] RBP: 7f040245d9f0 R08: 
7f03f8001a30 R09: 0001
  Aug 18 08:39:19 freyja kernel: [20514.280795] R10: 7f040245d9e0 R11: 
0293 R12: 7f03f8002420
  Aug 18 08:39:19 freyja kernel: [20514.280797] R13: 7f03f8002440 R14: 
7f03f80019f0 R15: 

[Kernel-packages] [Bug 1816669] Missing required logs.

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

apport-collect 1816669

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

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

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

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

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

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

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

Title:
  AMD Rome :  Minimal support patches

Status in amd:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  The following 3 patches need to be back ported to ubuntu 18.04.2(Linux
  4.18) to complete the minimal support for Rome :

  818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum
  e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register
  90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode

  --thanks
  --kim

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

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


[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches

2019-02-26 Thread Khaled El Mously
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  AMD Rome :  Minimal support patches

Status in amd:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  The following 3 patches need to be back ported to ubuntu 18.04.2(Linux
  4.18) to complete the minimal support for Rome :

  818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum
  e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register
  90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode

  --thanks
  --kim

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

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


[Kernel-packages] [Bug 1814120] Re: Troubles w/ Bluetooth @ usb device 04ca:3002

2019-02-26 Thread Kai-Heng Feng
[   34.784492] Bluetooth: Can't change to loading configuration err
[   34.784572] ath3k: probe of 2-4:1.0 failed with error -110

Can you do a cold boot and see if it helps?

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

Title:
  Troubles w/ Bluetooth @ usb device 04ca:3002

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My BT card, AR3011 by Lite-On (VID=0x04CA, PID=0x3002) doesn't work
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  szn-lip8283 F pulseaudio
   /dev/snd/pcmC1D0p:   szn-lip8283 F...m pulseaudio
   /dev/snd/controlC0:  szn-lip8283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Jan 31 17:58:30 2019
  InstallationDate: Installed on 2019-01-20 (10 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: ASUSTeK Computer Inc. K53TA
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=79395a0d-4877-4391-8026-62fbb66fac2e ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 214
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K53TA
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr214:bd04/06/2012:svnASUSTeKComputerInc.:pnK53TA:pvr1.0:rvnASUSTeKComputerInc.:rnK53TA:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53TA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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


[Kernel-packages] [Bug 1816269] Re: No image on KVM switch

2019-02-26 Thread Kai-Heng Feng
Please attach dmesg.

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

Title:
  No image on KVM switch

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to
  a dual DisplayPort adapter, to an Avocent SV340D KVM.

  If I have the KVM on the switch for the NUC, everything works great.
  If I switch the KVM to another channel, and then switch back to the
  NUC, I only get black screens. The only solution is to hard reboot the
  NUC.

  Any help would be appreciated.

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

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


[Kernel-packages] [Bug 1817513] Re: 4.19 causes disk read errors on CT256M550SSD3 SSD

2019-02-26 Thread Kai-Heng Feng
Disco will use v5.0.

It's in unstable PPA now:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable

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

Title:
  4.19 causes disk read errors on CT256M550SSD3 SSD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to disco, and I noticed that my SSD had read errors while
  looking at dmesg.  When I rebooted, it won't boot any more due to disk
  errors.

  But when I tried booting with a 4.18 kernel, it allows me to boot
  successfully without any errors.  Also, I booted an 18.10 USB disk to
  check which SSD was failing and when I used GNOME disks to check the
  filesystem, and there were no errors.

  I'll try download disco-current to see if the errors can be shown and
  be submitted here since I can't boot using 4.19 with my SSD.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-13-generic 4.19.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shemgp13115 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Feb 25 15:12:17 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cc5ba738-82e8-404a-9bcc-f1dfed94fce0
  InstallationDate: Installed on 2015-09-28 (1245 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 34361A0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-02-16 (9 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB1WW (2.71 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB1WW(2.71):bd06/19/2018:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.sku: LENOVO_MT_3436
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1809993] Re: Lenovo X1C6 trackpad functions broken

2019-02-26 Thread Kai-Heng Feng
Joshua,

Do you still have this issue on latest Ubuntu kernel?

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

Title:
  Lenovo X1C6 trackpad functions broken

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Summary:
  After kernel update the trackpad advanced functions, like two finger 
scrolling and mouse acceleration have stopped working.

  Expected Result:
  Two finer scroll works and the mouse has acceleration features work

  Actual Result:
  Two finer scroll works and the mouse has acceleration features do not work

  Steps to reproduce:
  1. Lenovo X1C6 (LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET59W (1.34 ) 
11/08/2018)
  2. Install 18.04 LTS
  3. config-4.15.0-42-generic acceleration works, while 
config-4.15.0-43-generic does not

  This appears to be some sort of regression or change in behavior between 
kernel versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  powersj1597 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7
  InstallationDate: Installed on 2018-12-06 (22 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KHCTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1809864] Re: BUG: unable to handle kernel paging request at ffffffffc08a5550

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

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

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

Title:
  BUG: unable to handle kernel paging request at c08a5550

Status in linux package in Ubuntu:
  Expired

Bug description:
  # symptom
  OS hang, able to ping. Must do hard reboot.

  # kernel info
  Ubuntu 16.04.5 LTS
  Kernel: Ubuntut 4.4.0-135.161-generic

  # Kernel log
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673329] BUG: unable to handle 
kernel paging request at c08a5550
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673365] IP: [] 
__remove_mapping+0x8d/0x190
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673394] PGD 1e0f067 PUD 1e11067 
PMD 84e42a067 PTE 0
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673420] Oops:  [#1] SMP 
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673436] Modules linked in: 
openafs(POE) binfmt_misc ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs skx_edac 
edac_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
irqbypass ipmi_ssif joydev input_leds mei_me mei shpchp ioatdma dca ipmi_si 
8250_fintek ipmi_msghandler acpi_power_meter acpi_pad mac_hid 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 raid0 multipath linear raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c ses enclosure scsi_transport_sas raid1 crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw hid_generic gf128mul glue_helper 
ablk_helper cryptd ast i2c_algo_bit ttm drm_kms_helper i40e syscopyarea 
sysfillrect vxlan sysimgblt ip6_udp_tunnel fb_sys_fops udp_tunnel ptp 
megaraid_sas nvme usbhid drm pps_core ahci hid libahci wmi fjes [last unloaded: 
openafs]
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673861] CPU: 5 PID: 187 Comm: 
kswapd0 Tainted: PB  OE   4.4.0-135-generic #161-Ubuntu
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673892] Hardware name: 
Supermicro SSG-6029P-E1CR12T/X11DPH-T, BIOS 2.1 06/15/2018
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673919] task: 881054c85500 
ti: 8808518c8000 task.ti: 8808518c8000
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673945] RIP: 
0010:[]  [] __remove_mapping+0x8d/0x190
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673978] RSP: 
0018:8808518cba40  EFLAGS: 00010002
  Dec 27 11:42:02 fileserver7 kernel: [8092783.673998] RAX: c08a5500 
RBX: ea00191c1500 RCX: 0246
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674022] RDX:  
RSI:  RDI: 8807f9104d80
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674047] RBP: 8808518cba78 
R08:  R09: 8807f9104d68
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674072] R10: 8808518cb9f8 
R11:  R12: 8807f9104d80
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674097] R13: 0001 
R14: 88084e39d800 R15: 8807f9104d68
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674122] FS:  
() GS:88085cb4() knlGS:
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674150] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674171] CR2: c08a5550 
CR3: 000844156000 CR4: 00360670
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674196] DR0:  
DR1:  DR2: 
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674221] DR3:  
DR6: fffe0ff0 DR7: 0400
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674246] Stack:
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674256]  811d45f0 
 8808518cbe50 ea00191c1500
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674286]  8808518cbc00 
ea00191c1520 8808518cbb28 8808518cbb78
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674317]  811aaf43 
881054c85500 00010001 88087fffbf80
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674348] Call Trace:
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674363]  [] ? 
page_get_anon_vma+0x80/0x80
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674388]  [] 
shrink_page_list+0x453/0x7a0
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674411]  [] 
shrink_inactive_list+0x209/0x520
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674434]  [] 
shrink_lruvec+0x58e/0x760
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674457]  [] ? 
__schedule+0x301/0x7f0
  Dec 27 11:42:02 fileserver7 kernel: [8092783.674486]  [] ? 
css_next_descendant_pre+0x4c/0x60
  Dec 27 11:42:02 fileserver7 kernel: [8092783.675452]  [] ? 
css_next_descendant_pre+0x4c/0x60
  Dec 27 11:42:02 fileserver7 kernel: [8092783.676382]  

[Kernel-packages] [Bug 1813372] Re: Realtek r8822be kernel module does not negotiate 802.11ac connection

2019-02-26 Thread David R. Bergstein
Per the request above, a message has been sent to the maintainers list
in entry #20 (below is a copy).

Subject: Realtek r8822be kernel module does not negotiate 802.11ac
connection

To: pks...@realtek.com, linux-wirel...@vger.kernel.org,
 net...@vger.kernel.org, linux-ker...@vger.kernel.org

This message is in regard to a bug I have open on bugs.launchpad.net,
1813372, linked below.  This issue, originally identified in an Ubuntu
kernel, has been duplicated in the most current mainline kernel,
5.0-rc8, and is in regard to problems attaining a wireless connection at
802.11ac speeds.

https://bugs.launchpad.net/bugs/1813372

At your earliest convenience, please see the bug report above, and
advise if a fix will be available for the r8822be kernel module.

Sincerely,

David R. Bergstein

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

Title:
  Realtek r8822be kernel module does not negotiate 802.11ac connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an HP Omen laptop with dual boot installed.  It has the Realtek
  8822BE wireless chip set installed, which when running Windows 10
  works as intended, i.e., it establishes an 802.11ac connection with my
  wireless router with speeds up to 866 mbps. However when running my
  Linux environment, Ubuntu Studio, the connection speed is established
  as 802.11n, and is limited to 300 mbps.

  I also see the following message in my logs which might be related to
  this issue:

  wlo1: capabilities/regulatory prevented using AP HT/VHT configuration,
  downgraded

  Please advise if additional information is needed. Per the bug
  reporting guidelines also see below.

  1) lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  2) apt-cache policy linux-modules-4.18.0-13-lowlatency
  linux-modules-4.18.0-13-lowlatency:
Installed: 4.18.0-13.14
Candidate: 4.18.0-13.14
Version table:
   *** 4.18.0-13.14 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What I expected to happen - connection at 802.11ac speeds
  4) What happened instead - 802.11n connection
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dbergst1852 F pulseaudio
   /dev/snd/pcmC0D0p:   dbergst1852 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (67 days ago)
  InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:58e6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-lowlatency 
root=UUID=e50d64b3-9d61-4d85-bf8f-c30c4759d7e4 ro quiet splash acpi_osi=! 
"acpi_osi=Windows 2009" vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-lowlatency 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-lowlatency N/A
   linux-backports-modules-4.18.0-15-lowlatency  N/A
   linux-firmware1.175.1
  StagingDrivers: r8822be
  Tags:  cosmic staging
  Uname: Linux 4.18.0-15-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 846A
  dmi.board.vendor: HP
  dmi.board.version: 68.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.08:bd11/09/2018:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn846A:rvr68.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop
  dmi.product.sku: 2XP11AV
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2019-02-26 Thread Kai-Heng Feng
Oh it's a merge point so there are still some commits:
$ git diff e5770b7bdbfe..32c1431eea48

So probably a good idea to bisect between e5770b7bdbfe and 32c1431eea48.

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2019-02-26 Thread Kai-Heng Feng
You are right.

Apparently something's wrong with my git,

$ git show 7bf1e44f865523aa16e0eb340a82d643da9215b5
commit 7bf1e44f865523aa16e0eb340a82d643da9215b5
Merge: e5770b7bdbfe 32c1431eea48
Author: Greg Kroah-Hartman 
Date:   Mon Jun 12 08:20:47 2017 +0200

Merge 4.12-rc5 into staging-next

We want the IIO fixes and other staging driver fixes in here as
well.

Signed-off-by: Greg Kroah-Hartman 

diff --cc drivers/staging/ccree/ssi_buffer_mgr.c
index 1ff603f8f8f5,6471d3d2d375..88ebda854377
--- a/drivers/staging/ccree/ssi_buffer_mgr.c
+++ b/drivers/staging/ccree/ssi_buffer_mgr.c
@@@ -136,13 -210,14 +136,14 @@@ void ssi_buffer_mgr_zero_sgl(struct sca
   */
  void ssi_buffer_mgr_copy_scatterlist_portion(
u8 *dest, struct scatterlist *sg,
 -  uint32_t to_skip,  uint32_t end,
 +  u32 to_skip,  u32 end,
enum ssi_sg_cpy_direct direct)
  {
 -  uint32_t nents, lbytes;
 +  u32 nents, lbytes;

nents = ssi_buffer_mgr_get_sgl_nents(sg, end, , NULL);
-   sg_copy_buffer(sg, nents, (void *)dest, (end - to_skip), 0, (direct == 
SSI_SG_TO_BUF));
+   sg_copy_buffer(sg, nents, (void *)dest, (end - to_skip + 1), to_skip,
+  (direct == SSI_SG_TO_BUF));
  }

  static inline int ssi_buffer_mgr_render_buff_to_mlli(

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO


[Kernel-packages] [Bug 1813372] Re: Realtek r8822be kernel module does not negotiate 802.11ac connection

2019-02-26 Thread Kai-Heng Feng
Please raise the issue to mailing list:
Ping-Ke Shih  (maintainer:REALTEK WIRELESS DRIVER (rtlwifi 
family))
linux-wirel...@vger.kernel.org (open list:REALTEK WIRELESS DRIVER (rtlwifi 
family))
net...@vger.kernel.org (open list:NETWORKING DRIVERS)
linux-ker...@vger.kernel.org (open list)

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

Title:
  Realtek r8822be kernel module does not negotiate 802.11ac connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an HP Omen laptop with dual boot installed.  It has the Realtek
  8822BE wireless chip set installed, which when running Windows 10
  works as intended, i.e., it establishes an 802.11ac connection with my
  wireless router with speeds up to 866 mbps. However when running my
  Linux environment, Ubuntu Studio, the connection speed is established
  as 802.11n, and is limited to 300 mbps.

  I also see the following message in my logs which might be related to
  this issue:

  wlo1: capabilities/regulatory prevented using AP HT/VHT configuration,
  downgraded

  Please advise if additional information is needed. Per the bug
  reporting guidelines also see below.

  1) lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  2) apt-cache policy linux-modules-4.18.0-13-lowlatency
  linux-modules-4.18.0-13-lowlatency:
Installed: 4.18.0-13.14
Candidate: 4.18.0-13.14
Version table:
   *** 4.18.0-13.14 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What I expected to happen - connection at 802.11ac speeds
  4) What happened instead - 802.11n connection
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dbergst1852 F pulseaudio
   /dev/snd/pcmC0D0p:   dbergst1852 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (67 days ago)
  InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:58e6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-lowlatency 
root=UUID=e50d64b3-9d61-4d85-bf8f-c30c4759d7e4 ro quiet splash acpi_osi=! 
"acpi_osi=Windows 2009" vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-lowlatency 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-lowlatency N/A
   linux-backports-modules-4.18.0-15-lowlatency  N/A
   linux-firmware1.175.1
  StagingDrivers: r8822be
  Tags:  cosmic staging
  Uname: Linux 4.18.0-15-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 846A
  dmi.board.vendor: HP
  dmi.board.version: 68.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.08:bd11/09/2018:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn846A:rvr68.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop
  dmi.product.sku: 2XP11AV
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1808116] Re: 4.15 and higher kernels do not read the SD card

2019-02-26 Thread Kai-Heng Feng
https://askubuntu.com/questions/158871/how-do-i-enable-the-source-code-
repositories

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

Title:
  4.15 and higher kernels do not read the SD card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  4.15 and higher kernels do not read the SD card.
  kernel 4.13 reads the SD card.

  Checked with a 64GB Samsung and 16 GB card from another manufacturer.
  Also 4.19.8 kernel does not read cards

  
  inxi -Fxz 
  System:    Host: ASUS Kernel: 4.13.0-45-generic x86_64 (64 bit gcc: 5.4.0) 
Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) 
    Distro: Linux Mint 18.3 Sylvia 
  Machine:   Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: 
E200HA.303 date: 12/21/2016 
  CPU:   Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB 
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 
    clock speeds: max: 1920 MHz 1: 1920 MHz 2: 1920 MHz 3: 486 MHz 4: 
505 MHz 
  Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0 
    Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1366x768@60.06hz 
    GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail) 
    GLX Version: 3.0 Mesa 18.0.5 Direct Rendering: Yes 
  Audio: Card Intel HDMI/DP LPE Audio driver: HdmiLpeAudio Sound: ALSA v: 
k4.13.0-45-generic 
  Network:   Card: Qualcomm Atheros Device 0042 driver: ath10k_pci bus-ID: 
01:00.0 
    IF: wlp1s0 state: up speed: N/A duplex: N/A mac:  
  Drives:    HDD Total Size: NA (-) ID-1: /dev/mmcblk0 model: N/A size: 31.3GB 
  Partition: ID-1: / size: 25G used: 21G (89%) fs: ext4 dev: /dev/mmcblk0p2 
    ID-2: swap-1 size: 4.18GB used: 0.00GB (0%) fs: swap dev: 
/dev/mmcblk0p3 
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present 
  Sensors:   System Temperatures: cpu: 40.0C mobo: N/A 
    Fan Speeds (in rpm): cpu: 0 
  Info:  Processes: 225 Uptime: 1 min Memory: 1101.6/3839.9MB Init: systemd 
runlevel: 5 Gcc sys: 5.4.0 
    Client: Shell (bash 4.3.481) inxi: 2.2.35 


  without a SD card inserted

  dmesg | grep mmc 
  [    2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA 
  [    3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA 
  [    3.323762] mmc0: new HS200 MMC card at address 0001 
  [    3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB  
  [    3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB 
  [    3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB 
  [    3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB 
  [    3.334332]  mmcblk0: p1 p2 p3 
  [    4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null) 
  [    5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro 
  [    6.827393] Adding 4085756k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 
across:4085756k SSFS

  
  with inserted SD card

  dmesg | grep mmc 
  [    2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA 
  [    3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA 
  [    3.323762] mmc0: new HS200 MMC card at address 0001 
  [    3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB  
  [    3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB 
  [    3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB 
  [    3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB 
  [    3.334332]  mmcblk0: p1 p2 p3 
  [    4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null) 
  [    5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro 
  [    6.827393] Adding 4085756k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 
across:4085756k SSFS 
  [  216.577900] mmc1: new ultra high speed SDR104 SDXC card at address 59b4 
  [  216.578575] mmcblk1: mmc1:59b4 0 59.7 GiB  
  [  216.580031]  mmcblk1: p1 
  [  216.857616] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some 
data may be corrupt. Please run fsck.

  
===

  inxi -Fxz 
  System:    Host: ASUS Kernel: 4.15.0-42-generic x86_64 (64 bit gcc: 5.4.0) 
Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) 
    Distro: Linux Mint 18.3 Sylvia 
  Machine:   Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: 
E200HA.303 date: 12/21/2016 
  CPU:   Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB 
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 
    clock speeds: max: 1920 MHz 1: 839 MHz 2: 816 MHz 3: 480 MHz 4: 480 
MHz 
  Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0 
    Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1366x768@60.06hz 
    GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail) 
     

[Kernel-packages] [Bug 1817793] Re: Audio is not switchable through Plasma widgets

2019-02-26 Thread Kai-Heng Feng
** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1817817] Re: To add power setting bin file for SAR support (QCA6174)

2019-02-26 Thread AceLan Kao
commit 97b1f938bf7e25b196c149991f5a07ab62f3a801
Author: Kalle Valo 
Date:   Fri Feb 1 17:22:54 2019 +0200

ath10k: QCA6174 hw3.0: update board-2.bin

Signed-off-by: Kalle Valo 


** Tags added: originate-from-1800773 somerville

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

Title:
  To add power setting bin file for SAR support (QCA6174)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  To meet the policy requirement of the RF radiation, we need to reduce the 
power of the device.

  [Fix]
  Qualcomm provides a new firmware for this.
  97b1f938 ath10k: QCA6174 hw3.0: update board-2.bin

  [Test]
  We can't verify it.

  [Regression Potential]
  Low, it's a fix from upstream.

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

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


[Kernel-packages] [Bug 1817817] [NEW] To add power setting bin file for SAR support (QCA6174)

2019-02-26 Thread AceLan Kao
Public bug reported:

[Impact]
To meet the policy requirement of the RF radiation, we need to reduce the power 
of the device.

[Fix]
Qualcomm provides a new firmware for this.
97b1f938 ath10k: QCA6174 hw3.0: update board-2.bin

[Test]
We can't verify it.

[Regression Potential]
Low, it's a fix from upstream.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress


** Tags: originate-from-1800773 somerville

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

Title:
  To add power setting bin file for SAR support (QCA6174)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  To meet the policy requirement of the RF radiation, we need to reduce the 
power of the device.

  [Fix]
  Qualcomm provides a new firmware for this.
  97b1f938 ath10k: QCA6174 hw3.0: update board-2.bin

  [Test]
  We can't verify it.

  [Regression Potential]
  Low, it's a fix from upstream.

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

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


[Kernel-packages] [Bug 1816768] Re: nvidia module fails to build [error: too many arguments to function ‘get_user_pages’]

2019-02-26 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1573508 ***
https://bugs.launchpad.net/bugs/1573508

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1573508, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- nvidia module fails to build
+ nvidia module fails to build [error: too many arguments to function 
‘get_user_pages’]

** This bug has been marked a duplicate of bug 1573508
   nvidia-*: nvidia-* kernel module failed to build [error: too many arguments 
to function ‘get_user_pages’]

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

Title:
  nvidia module fails to build [error: too many arguments to function
  ‘get_user_pages’]

Status in linux-meta-lts-xenial package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  With the update to linux-meta-lts-xenial (4.4.0.143.124 nvidia fails
  to load. Reinstalling the driver (nvidia-384) shows this

  Building initial module for 4.4.0-143-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/nvidia-384.0.crash'
  Error! Bad return status for module build on kernel: 4.4.0-143-generic 
(x86_64)
  Consult /var/lib/dkms/nvidia-384/384.130/build/make.log for more information.

  Log attached

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-generic-lts-xenial 4.4.0.143.124
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 20 09:08:28 2019
  InstallationDate: Installed on 2016-03-12 (1075 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-meta-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1816768/+subscriptions

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


[Kernel-packages] [Bug 1788321] Re: swapon failed: invalid argument

2019-02-26 Thread utnubudnai
ubuntu 16.04, hit the same issue as this. swapon -v shows these:

```
swapon: /my/swap: found swap signature: version 1d, page-size 4, same byte order
swapon: /my/swap: pagesize=4096, swapsize=13..., devsize=13
swapon: /my/swap: swapon failed: Invalid argument
```

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

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

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


[Kernel-packages] [Bug 1605433] Re: [Dell Alienware 17 R3] FN+F11 Enable/Disable touchpad not working

2019-02-26 Thread adin
The output is as follows.  Note that I tried to trigger some of the
events by doing the Fn+FX, but none gave a response.

$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  Lid Switch
/dev/input/event1:  Power Button
/dev/input/event2:  Power Button
/dev/input/event3:  AT Translated Set 2 keyboard
/dev/input/event4:  SynPS/2 Synaptics TouchPad
/dev/input/event5:  Video Bus
/dev/input/event6:  Video Bus
/dev/input/event7:  Integrated_Webcam_HD: Integrate
/dev/input/event8:  Dell WMI hotkeys
/dev/input/event9:  HDA Intel PCH Mic
/dev/input/event10: HDA Intel PCH Headphone
/dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7
/dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8
/dev/input/event14: HDA Intel PCH HDMI/DP,pcm=9
/dev/input/event15: HDA Intel PCH HDMI/DP,pcm=10
/dev/input/event16: Logitech Wireless Mouse M560
Select the device event number [0-16]: 8
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
Input device name: "Dell WMI hotkeys"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
Event code 148 (KEY_PROG1)
Event code 149 (KEY_PROG2)
Event code 161 (KEY_EJECTCD)
Event code 202 (KEY_PROG3)
Event code 203 (KEY_PROG4)
Event code 224 (KEY_BRIGHTNESSDOWN)
Event code 225 (KEY_BRIGHTNESSUP)
Event code 227 (KEY_SWITCHVIDEOMODE)
Event code 236 (KEY_BATTERY)
Event code 238 (KEY_WLAN)
Event code 240 (KEY_UNKNOWN)
Event code 248 (KEY_MICMUTE)
Event code 431 (KEY_DISPLAYTOGGLE)
  Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)

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

Title:
  [Dell Alienware 17 R3] FN+F11 Enable/Disable touchpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touchpad does not work as expected. It can't be enabled or
  disabled through FN+F11 combination.

  The light (in the pad) always turns on, regardless of its non
  functionality.

  The problem seems related to bug #1523738, and some say solution #24
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/comments/24)
  works, but it didn't for me.

  WORKAROUND: Executing the following via a terminal allows one to disable and 
enable the touchpad:
  xinput set-prop 13 "Device Enabled" 1
  xinput set-prop 13 "Device Enabled" 0

  But it only works if it is enabled from the beginning from the systems
  configuration GUI. If it is disabled, it doesn't do the expected
  behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Jul 21 21:07:42 2016
  InstallationDate: Installed on 2016-07-03 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2016-07-16T11:29:07.694480
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adin   4247 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd
  InstallationDate: Installed on 2016-07-03 (24 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Alienware Alienware 17 R3
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-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/11/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.3
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not 

[Kernel-packages] [Bug 1817784] Re: libsas disks can have non-unique by-path names

2019-02-26 Thread dann frazier
** Changed in: linux (Ubuntu Xenial)
   Status: New => 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/1817784

Title:
  libsas disks can have non-unique by-path names

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  Multiple disks in a system can end up having the same BY_PATH name, making 
the corresponding symlinks in /dev/disk/by-path non-unique. This can result in 
a user performing an operation on the wrong disk, possibly resulting in data 
loss.

  [Test Case]
  $ ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root  9 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0 -> ../../sdb
  lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part1 -> ../../sdb1
  lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part2 -> ../../sdb2
  lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part3 -> ../../sdc3

  
  Notice that there is no symlink for /dev/sdc.

  [Fix]
  ffeafdd2bf0b2 scsi: libsas: Fix rphy phy_identifier for PHYs with end devices 
attached

  [Regression Risk]
  This may change the by-path symlinks for disks on the system. While the new 
name would be the correct one - users maybe relying on the incorrect version. 
This could result in an unbootable system, requiring manual intervention to 
repair.

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

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


[Kernel-packages] [Bug 1814648] Re: linux-aws: 4.4.0-1039.42 -proposed tracker

2019-02-26 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:29 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.4.0-1039.42 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:29 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814648/+subscriptions

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


[Kernel-packages] [Bug 1814648] Re: linux-aws: 4.4.0-1039.42 -proposed tracker

2019-02-26 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  linux-aws: 4.4.0-1039.42 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:29 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814648/+subscriptions

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


[Kernel-packages] [Bug 1817738] Missing required logs.

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

apport-collect 1817738

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

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

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

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

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

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

Title:
  Can't change virtual terminal when auto-login is enabled

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in gdm3 source package in Bionic:
  New
Status in linux source package in Bionic:
  Incomplete

Bug description:
  sudo strace chvt 4
  execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
  brk(NULL) = 0x561e1843
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
  mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
  close(3) = 0
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) = 
832
  fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f5059e7b000
  mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f5059878000
  mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
  mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
  mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
  mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
  mprotect(0x561e17e87000, 4096, PROT_READ) = 0
  mprotect(0x7f5059e9, 4096, PROT_READ) = 0
  munmap(0x7f5059e7d000, 74655) = 0
  brk(NULL) = 0x561e1843
  brk(0x561e18451000) = 0x561e18451000
  openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
  mmap(NULL, 10281936, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
  close(3) = 0
  openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
  ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
  ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for 
device)
  close(3) = 0
  openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
  ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
  ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for 
device)
  close(3) = 0
  openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
  ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
  ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
  ioctl(3, VT_ACTIVATE, 0x4) = 0
  ioctl(3, VT_WAITACTIVE, 0x4

  VT_ACTIVATE will cause a switch to VT number.
  VT_WAITACTIVE will sleep/wait until the specified VT has been activated.

  $ sudo cat /proc/$(pidof chvt)/stack
  [<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
  [<0>] vt_waitactive+0x80/0xd0
  [<0>] vt_ioctl+0xd26/0x1140
  [<0>] tty_ioctl+0xf6/0x8c0
  [<0>] do_vfs_ioctl+0xa8/0x630
  [<0>] SyS_ioctl+0x79/0x90
  [<0>] do_syscall_64+0x73/0x130
  [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [<0>] 0x

  Enable debuglogs doesn't provide additional details.

  As soon as auto-login is turned off, chvt is back to normal.

  The above has been reproduced on Ubuntu:
  - Ubuntu Bionic w/ gdm3 3.28.3 & kbd 2.0.4
  - Ubuntu disco w/ gdm3 3.30.1 & kbd 2.0.4

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled

2019-02-26 Thread Eric Desrochers
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can't change virtual terminal when auto-login is enabled

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in gdm3 source package in Bionic:
  New
Status in linux source package in Bionic:
  New

Bug description:
  sudo strace chvt 4
  execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
  brk(NULL) = 0x561e1843
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
  mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
  close(3) = 0
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) = 
832
  fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f5059e7b000
  mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f5059878000
  mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
  mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
  mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
  mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
  mprotect(0x561e17e87000, 4096, PROT_READ) = 0
  mprotect(0x7f5059e9, 4096, PROT_READ) = 0
  munmap(0x7f5059e7d000, 74655) = 0
  brk(NULL) = 0x561e1843
  brk(0x561e18451000) = 0x561e18451000
  openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
  mmap(NULL, 10281936, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
  close(3) = 0
  openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
  ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
  ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for 
device)
  close(3) = 0
  openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
  ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
  ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for 
device)
  close(3) = 0
  openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
  ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
  ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
  ioctl(3, VT_ACTIVATE, 0x4) = 0
  ioctl(3, VT_WAITACTIVE, 0x4

  VT_ACTIVATE will cause a switch to VT number.
  VT_WAITACTIVE will sleep/wait until the specified VT has been activated.

  $ sudo cat /proc/$(pidof chvt)/stack
  [<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
  [<0>] vt_waitactive+0x80/0xd0
  [<0>] vt_ioctl+0xd26/0x1140
  [<0>] tty_ioctl+0xf6/0x8c0
  [<0>] do_vfs_ioctl+0xa8/0x630
  [<0>] SyS_ioctl+0x79/0x90
  [<0>] do_syscall_64+0x73/0x130
  [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [<0>] 0x

  Enable debuglogs doesn't provide additional details.

  As soon as auto-login is turned off, chvt is back to normal.

  The above has been reproduced on Ubuntu:
  - Ubuntu Bionic w/ gdm3 3.28.3 & kbd 2.0.4
  - Ubuntu disco w/ gdm3 3.30.1 & kbd 2.0.4

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1817793] Re: Audio is not switchable through Plasma widgets

2019-02-26 Thread udippel
apport information

** Tags added: apport-collected bionic

** Description changed:

  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 
  
  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%
  
  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  udippel1822 F pulseaudio
+  /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
+  /dev/snd/controlC0:  udippel1822 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
+ InstallationDate: Installed on 2019-02-16 (10 days ago)
+ InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ MachineType: LENOVO 20CHS10P02
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-45-generic N/A
+  linux-backports-modules-4.15.0-45-generic  N/A
+  linux-firmware 1.173.3
+ Tags:  bionic
+ Uname: Linux 4.15.0-45-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/31/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N17ETA2W (2.02 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20CHS10P02
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0E50510 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 11
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
+ dmi.product.family: ThinkPad Helix 2nd
+ dmi.product.name: 20CHS10P02
+ dmi.product.version: ThinkPad Helix 2nd
+ dmi.sys.vendor: LENOVO

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio 

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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread udippel
apport information

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1814095] Re: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

2019-02-26 Thread Terry Rudd
Nivedita, per the request to test this patch, determining the correct FW
version seems an open issue.  There is also the issue of having hardware
available to properly test.

Have you been able to determine a reproducer for this bug?  
Do you know if anyone has been able to test the backport?  
Can you confirm if the request is to actually get the patch merged to xenial at 
this time?

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

Title:
  bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

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

Bug description:
  [Impact]

  The bnxt_en_bpo driver experienced tx timeouts causing the system to
  experience network stalls and fail to send data and heartbeat packets.

  The following 25Gb Broadcom NIC error was seen on Xenial
  running the 4.4.0-141-generic kernel on an amd64 host
  seeing moderate-heavy network traffic (just once):

  * The bnxt_en_po driver froze on a "TX timed out" error
    and triggered the Netdev Watchdog timer under load.

  * From kernel log:
    "NETDEV WATCHDOG: eno2d1 (bnxt_en_bpo): transmit queue 0 timed out"
    See attached kern.log excerpt file for full excerpt of error log.

  * Release = Xenial
    Kernel = 4.4.0-141-generic #167
    eno2d1 = Product Name: Broadcom Adv. Dual 25Gb Ethernet

  * This caused the driver to reset in order to recover:

    "bnxt_en_bpo :19:00.1 eno2d1: TX timeout detected, starting
  reset task!"

    driver: bnxt_en_bpo
    version: 1.8.1
    source: ubuntu/bnxt/bnxt.c: bnxt_tx_timeout()

  * The loss of connectivity and softirq stall caused other failures
    on the system.

  * The bnxt_en_po driver is the imported Broadcom driver
    pulled in to support newer Broadcom HW (specific boards)
    while the bnx_en module continues to support the older
    HW. The current Linux upstream driver does not compile
    easily with the 4.4 kernel (too many changes).

  * This upstream and bnxt_en driver fix is a likely solution:
     "bnxt_en: Fix TX timeout during netpoll"
     commit: 73f21c653f930f438d53eed29b5e4c65c8a0f906

    This fix has not been applied to the bnxt_en_po driver
    version, but review of the code indicates that it is
    susceptible to the bug, and the fix would be reasonable.

  [Test Case]

  * Unfortunately, this is not easy to reproduce. Also, it is only seen
  on 4.4 kernels with newer Broadcom NICs supported by the bnxt_en_bpo
  driver.

  [Regression Potential]

  * The patch is restricted to the bpo driver, with very constrained
  scope - just the newest Broadcom NICs being used by the Xenial 4.4
  kernel (as opposed to the hwe 4.15 etc. kernels, which would have the
  in-tree fixed driver).

  * The patch is very small and backport is fairly minimal and simple.

  * The fix has been running on the in-tree driver in upstream mainline
  as well as the Ubuntu Linux in-tree driver, although the Broadcom
  driver has a lot of lower level code that is different, this piece is
  still the same.

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

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


[Kernel-packages] [Bug 1817793] Missing required logs.

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

apport-collect 1817793

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

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

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

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

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.

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

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


[Kernel-packages] [Bug 1817793] Re: Audio is not switchable through Plasma widgets

2019-02-26 Thread udippel
** Attachment added: "PulseAudio_Playback is the only place to effectuate the 
necessary switching"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817793/+attachment/5241908/+files/PulseAudio_Playback.png

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.

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

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


[Kernel-packages] [Bug 1817793] Re: Audio is not switchable through Plasma widgets

2019-02-26 Thread udippel
** Attachment added: "PulseAudio Volume Control does not allow switching in 
Configuration"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817793/+attachment/5241907/+files/Screenshot_20190226_215906.png

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.

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

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


[Kernel-packages] [Bug 1817793] Re: Audio is not switchable through Plasma widgets

2019-02-26 Thread udippel
** Attachment added: "Reasonable location for manual switching, but doesn't 
offer this"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817793/+attachment/5241909/+files/Screenshot_20190226_221825.png

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.

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

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


[Kernel-packages] [Bug 1817793] [NEW] Audio is not switchable through Plasma widgets

2019-02-26 Thread udippel
Public bug reported:

On my convertible, there seems to be no way to adept to changing audio drains; 
except of starting and re-configuring PulseAudio Volume Control. 
I have a tablet, with a detachable keyboard and an external monitor with audio. 
What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

I have attached 4 screenshots: 
 - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
 - The PulseAudio Volume Control Configuration. Also that doesn't help.
 - The PulseAudio Volume Control Playback is the only place to select to where 
the audio goes. Alas, if one or even more disappear, here it is getting stuck 
there. Leaving the user without sound.
 - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.

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

** Attachment added: "Shows that there is no control to switch the audio"
   
https://bugs.launchpad.net/bugs/1817793/+attachment/5241903/+files/PlasmaApp_useless.png

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.

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

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


[Kernel-packages] [Bug 1808116] Re: 4.15 and higher kernels do not read the SD card

2019-02-26 Thread Andrzej
andrzej@ASUS ~ $ sudo apt build-dep linux
Czytanie list pakietów... Gotowe
E: Nie udało się odnaleźć źródła dla pakietu linux

"andrzej @ ASUS ~ $ sudo apt build-dep linux
Reading package lists ... Ready
E: The source for the linux package could not be found"

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

Title:
  4.15 and higher kernels do not read the SD card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  4.15 and higher kernels do not read the SD card.
  kernel 4.13 reads the SD card.

  Checked with a 64GB Samsung and 16 GB card from another manufacturer.
  Also 4.19.8 kernel does not read cards

  
  inxi -Fxz 
  System:    Host: ASUS Kernel: 4.13.0-45-generic x86_64 (64 bit gcc: 5.4.0) 
Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) 
    Distro: Linux Mint 18.3 Sylvia 
  Machine:   Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: 
E200HA.303 date: 12/21/2016 
  CPU:   Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB 
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 
    clock speeds: max: 1920 MHz 1: 1920 MHz 2: 1920 MHz 3: 486 MHz 4: 
505 MHz 
  Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0 
    Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1366x768@60.06hz 
    GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail) 
    GLX Version: 3.0 Mesa 18.0.5 Direct Rendering: Yes 
  Audio: Card Intel HDMI/DP LPE Audio driver: HdmiLpeAudio Sound: ALSA v: 
k4.13.0-45-generic 
  Network:   Card: Qualcomm Atheros Device 0042 driver: ath10k_pci bus-ID: 
01:00.0 
    IF: wlp1s0 state: up speed: N/A duplex: N/A mac:  
  Drives:    HDD Total Size: NA (-) ID-1: /dev/mmcblk0 model: N/A size: 31.3GB 
  Partition: ID-1: / size: 25G used: 21G (89%) fs: ext4 dev: /dev/mmcblk0p2 
    ID-2: swap-1 size: 4.18GB used: 0.00GB (0%) fs: swap dev: 
/dev/mmcblk0p3 
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present 
  Sensors:   System Temperatures: cpu: 40.0C mobo: N/A 
    Fan Speeds (in rpm): cpu: 0 
  Info:  Processes: 225 Uptime: 1 min Memory: 1101.6/3839.9MB Init: systemd 
runlevel: 5 Gcc sys: 5.4.0 
    Client: Shell (bash 4.3.481) inxi: 2.2.35 


  without a SD card inserted

  dmesg | grep mmc 
  [    2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA 
  [    3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA 
  [    3.323762] mmc0: new HS200 MMC card at address 0001 
  [    3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB  
  [    3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB 
  [    3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB 
  [    3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB 
  [    3.334332]  mmcblk0: p1 p2 p3 
  [    4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null) 
  [    5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro 
  [    6.827393] Adding 4085756k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 
across:4085756k SSFS

  
  with inserted SD card

  dmesg | grep mmc 
  [    2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA 
  [    3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA 
  [    3.323762] mmc0: new HS200 MMC card at address 0001 
  [    3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB  
  [    3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB 
  [    3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB 
  [    3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB 
  [    3.334332]  mmcblk0: p1 p2 p3 
  [    4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null) 
  [    5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro 
  [    6.827393] Adding 4085756k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 
across:4085756k SSFS 
  [  216.577900] mmc1: new ultra high speed SDR104 SDXC card at address 59b4 
  [  216.578575] mmcblk1: mmc1:59b4 0 59.7 GiB  
  [  216.580031]  mmcblk1: p1 
  [  216.857616] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some 
data may be corrupt. Please run fsck.

  
===

  inxi -Fxz 
  System:    Host: ASUS Kernel: 4.15.0-42-generic x86_64 (64 bit gcc: 5.4.0) 
Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) 
    Distro: Linux Mint 18.3 Sylvia 
  Machine:   Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: 
E200HA.303 date: 12/21/2016 
  CPU:   Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB 
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 
    clock speeds: max: 1920 MHz 1: 839 MHz 2: 816 MHz 3: 480 MHz 4: 480 
MHz 
  Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0 
    

[Kernel-packages] [Bug 1817038] Re: linux-azure: 4.15.0-1040.44 -proposed tracker

2019-02-26 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in candidate channel
-   stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1040.44 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in candidate channel
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1817038/+subscriptions

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


[Kernel-packages] [Bug 1816783] Re: linux-azure: 4.18.0-1012.12 -proposed tracker

2019-02-26 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1012.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816783/+subscriptions

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


[Kernel-packages] [Bug 1817786] [NEW] tcm_loop.ko: move from modules-extra into main modules-gcp package

2019-02-26 Thread Kamal Mostafa
Public bug reported:

Please move the tcm_loop.ko module from the linux-modules-extra-*-gcp to
main linux-modules-*-gcp package.

** Affects: linux-gcp (Ubuntu)
 Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Affects: linux-gcp (Ubuntu Xenial)
 Importance: Undecided
 Status: In Progress

** Affects: linux-gcp (Ubuntu Bionic)
 Importance: Undecided
 Status: In Progress

** Affects: linux-gcp (Ubuntu Cosmic)
 Importance: Undecided
 Status: In Progress

** Affects: linux-gcp (Ubuntu Disco)
 Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Affects: linux-gcp (Ubuntu Ee-series)
 Importance: Undecided
 Status: New

** Affects: linux-gcp (Ubuntu Ff-series)
 Importance: Undecided
 Status: New

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

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

** Also affects: linux-gcp (Ubuntu Ee-series)
   Importance: Undecided
   Status: New

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

** Also affects: linux-gcp (Ubuntu Disco)
   Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
   Status: New

** Also affects: linux-gcp (Ubuntu Ff-series)
   Importance: Undecided
   Status: New

** Changed in: linux-gcp (Ubuntu Disco)
   Status: New => In Progress

** Changed in: linux-gcp (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: linux-gcp (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-gcp (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  tcm_loop.ko: move from modules-extra into main modules-gcp package

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Xenial:
  In Progress
Status in linux-gcp source package in Bionic:
  In Progress
Status in linux-gcp source package in Cosmic:
  In Progress
Status in linux-gcp source package in Disco:
  In Progress
Status in linux-gcp source package in EE-Series:
  New
Status in linux-gcp source package in FF-Series:
  New

Bug description:
  Please move the tcm_loop.ko module from the linux-modules-extra-*-gcp
  to main linux-modules-*-gcp package.

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

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


[Kernel-packages] [Bug 1816782] Re: linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

2019-02-26 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in 18/candidate channel
-   stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in 18/candidate channel
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816782/+subscriptions

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


[Kernel-packages] [Bug 1816783] Re: linux-azure: 4.18.0-1012.12 -proposed tracker

2019-02-26 Thread Joshua R. Poulson
tests complete

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: Confirmed => Fix Released

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

Title:
  linux-azure: 4.18.0-1012.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816783/+subscriptions

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


[Kernel-packages] [Bug 1817038] Re: linux-azure: 4.15.0-1040.44 -proposed tracker

2019-02-26 Thread Joshua R. Poulson
tests complete

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: Confirmed => Fix Released

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

Title:
  linux-azure: 4.15.0-1040.44 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in candidate channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1817038/+subscriptions

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


[Kernel-packages] [Bug 1817036] Re: linux-azure: 4.15.0-1040.44~14.04.1 -proposed tracker

2019-02-26 Thread Joshua R. Poulson
tests complete

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Fix Released

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

Title:
  linux-azure: 4.15.0-1040.44~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 26. February 2019 14:18 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1817036/+subscriptions

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


[Kernel-packages] [Bug 1816782] Re: linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

2019-02-26 Thread Joshua R. Poulson
tests complete

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: Confirmed => Fix Released

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

Title:
  linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in 18/candidate channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816782/+subscriptions

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


[Kernel-packages] [Bug 1816782] Re: linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

2019-02-26 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in 18/beta channel
-   snap-release-to-edge: Pending -- snap not in 18/edge channel
+   snap-release-to-candidate: Pending -- snap not in 18/candidate channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in 18/candidate channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816782/+subscriptions

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


[Kernel-packages] [Bug 1817784] [NEW] libsas disks can have non-unique by-path names

2019-02-26 Thread dann frazier
Public bug reported:

[Impact]
Multiple disks in a system can end up having the same BY_PATH name, making the 
corresponding symlinks in /dev/disk/by-path non-unique. This can result in a 
user performing an operation on the wrong disk, possibly resulting in data loss.

[Test Case]
$ ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root  9 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part3 -> ../../sdc3


Notice that there is no symlink for /dev/sdc.

[Fix]
ffeafdd2bf0b2 scsi: libsas: Fix rphy phy_identifier for PHYs with end devices 
attached

[Regression Risk]
This may change the by-path symlinks for disks on the system. While the new 
name would be the correct one - users maybe relying on the incorrect version. 
This could result in an unbootable system, requiring manual intervention to 
repair.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: New

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Cosmic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: dann frazier (dannf)
   Status: New

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Disco)
   Status: New => In Progress

** Changed in: linux (Ubuntu Cosmic)
   Status: New => In Progress

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

Title:
  libsas disks can have non-unique by-path names

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  Multiple disks in a system can end up having the same BY_PATH name, making 
the corresponding symlinks in /dev/disk/by-path non-unique. This can result in 
a user performing an operation on the wrong disk, possibly resulting in data 
loss.

  [Test Case]
  $ ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root  9 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0 -> ../../sdb
  lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part1 -> ../../sdb1
  lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part2 -> ../../sdb2
  lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part3 -> ../../sdc3

  
  Notice that there is no symlink for /dev/sdc.

  [Fix]
  ffeafdd2bf0b2 scsi: libsas: Fix rphy phy_identifier for PHYs with end devices 
attached

  [Regression Risk]
  This may change the by-path symlinks for disks on the system. While the new 
name would be the correct one - users maybe relying on the incorrect version. 
This could result in an unbootable system, requiring manual intervention to 
repair.

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

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


[Kernel-packages] [Bug 1817038] Re: linux-azure: 4.15.0-1040.44 -proposed tracker

2019-02-26 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in beta channel
-   snap-release-to-edge: Pending -- snap not in edge channel
+   snap-release-to-candidate: Pending -- snap not in candidate channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1040.44 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in candidate channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1817038/+subscriptions

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


[Kernel-packages] [Bug 1816782] Re: linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

2019-02-26 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

Title:
  linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816782/+subscriptions

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


[Kernel-packages] [Bug 1814481] Re: bluetooth keyboard not working

2019-02-26 Thread Alejandro Mery
I just realised the keyboard works in lightdm, and the stops working
after logging in.

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

Title:
  bluetooth keyboard not working

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

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

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

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

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

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

[Kernel-packages] [Bug 1813372] Re: Realtek r8822be kernel module does not negotiate 802.11ac connection

2019-02-26 Thread David R. Bergstein
Although iwconfig reports a bit rate of 866.7 Mb/s, it still appears
that my wireless connection speeds are less than 300 Mb/s.  I recommend
this bug report stay open until information can be obtained on the
r8822be kernel module and any required fixes.

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

Title:
  Realtek r8822be kernel module does not negotiate 802.11ac connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an HP Omen laptop with dual boot installed.  It has the Realtek
  8822BE wireless chip set installed, which when running Windows 10
  works as intended, i.e., it establishes an 802.11ac connection with my
  wireless router with speeds up to 866 mbps. However when running my
  Linux environment, Ubuntu Studio, the connection speed is established
  as 802.11n, and is limited to 300 mbps.

  I also see the following message in my logs which might be related to
  this issue:

  wlo1: capabilities/regulatory prevented using AP HT/VHT configuration,
  downgraded

  Please advise if additional information is needed. Per the bug
  reporting guidelines also see below.

  1) lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  2) apt-cache policy linux-modules-4.18.0-13-lowlatency
  linux-modules-4.18.0-13-lowlatency:
Installed: 4.18.0-13.14
Candidate: 4.18.0-13.14
Version table:
   *** 4.18.0-13.14 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What I expected to happen - connection at 802.11ac speeds
  4) What happened instead - 802.11n connection
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dbergst1852 F pulseaudio
   /dev/snd/pcmC0D0p:   dbergst1852 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (67 days ago)
  InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:58e6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-lowlatency 
root=UUID=e50d64b3-9d61-4d85-bf8f-c30c4759d7e4 ro quiet splash acpi_osi=! 
"acpi_osi=Windows 2009" vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-lowlatency 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-lowlatency N/A
   linux-backports-modules-4.18.0-15-lowlatency  N/A
   linux-firmware1.175.1
  StagingDrivers: r8822be
  Tags:  cosmic staging
  Uname: Linux 4.18.0-15-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 846A
  dmi.board.vendor: HP
  dmi.board.version: 68.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.08:bd11/09/2018:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn846A:rvr68.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop
  dmi.product.sku: 2XP11AV
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker

2019-02-26 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1814646 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Testing
- phase-changed: Tuesday, 26. February 2019 14:27 UTC
+ phase: Ready for Testing
+ phase-changed: Tuesday, 26. February 2019 18:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing 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/1814645

Title:
  linux: 3.13.0-166.216 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1814646 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Tuesday, 26. February 2019 18:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814645/+subscriptions

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


[Kernel-packages] [Bug 1813372] Re: Realtek r8822be kernel module does not negotiate 802.11ac connection

2019-02-26 Thread David R. Bergstein
It appears there is a problem with my Verizon router.  If I manually set
the 5 Hz wi-fi channel number to any available channel, I see bit rates
of 866.7 Mb/s on my Ubuntu Studio machine.

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

Title:
  Realtek r8822be kernel module does not negotiate 802.11ac connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an HP Omen laptop with dual boot installed.  It has the Realtek
  8822BE wireless chip set installed, which when running Windows 10
  works as intended, i.e., it establishes an 802.11ac connection with my
  wireless router with speeds up to 866 mbps. However when running my
  Linux environment, Ubuntu Studio, the connection speed is established
  as 802.11n, and is limited to 300 mbps.

  I also see the following message in my logs which might be related to
  this issue:

  wlo1: capabilities/regulatory prevented using AP HT/VHT configuration,
  downgraded

  Please advise if additional information is needed. Per the bug
  reporting guidelines also see below.

  1) lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  2) apt-cache policy linux-modules-4.18.0-13-lowlatency
  linux-modules-4.18.0-13-lowlatency:
Installed: 4.18.0-13.14
Candidate: 4.18.0-13.14
Version table:
   *** 4.18.0-13.14 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What I expected to happen - connection at 802.11ac speeds
  4) What happened instead - 802.11n connection
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dbergst1852 F pulseaudio
   /dev/snd/pcmC0D0p:   dbergst1852 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (67 days ago)
  InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:58e6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-lowlatency 
root=UUID=e50d64b3-9d61-4d85-bf8f-c30c4759d7e4 ro quiet splash acpi_osi=! 
"acpi_osi=Windows 2009" vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-lowlatency 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-lowlatency N/A
   linux-backports-modules-4.18.0-15-lowlatency  N/A
   linux-firmware1.175.1
  StagingDrivers: r8822be
  Tags:  cosmic staging
  Uname: Linux 4.18.0-15-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 846A
  dmi.board.vendor: HP
  dmi.board.version: 68.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.08:bd11/09/2018:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn846A:rvr68.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop
  dmi.product.sku: 2XP11AV
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1788098] Comment bridged from LTC Bugzilla

2019-02-26 Thread bugproxy
--- Comment From leona...@ibm.com 2019-02-26 12:58 EDT---
Here are the patches:

https://gitlab.com/LeoBras/bionic/compare/master...lp1788098

Also, I attached a tgz with the patches.

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions

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


[Kernel-packages] [Bug 1788098] Comment bridged from LTC Bugzilla

2019-02-26 Thread bugproxy
--- Comment From leona...@ibm.com 2019-02-26 12:36 EDT---
(In reply to comment #41)
> ...or perhaps I've misunderstood. Are the patches listed in comment #23 the
> complete set required to resolve the issue (with no complex backporting
> required)?

Yes, the patches listed by Paul are the only ones required to fix the
issue.

As noted by Paul, there is only one patch that causes some conflict.
I have solved this conflict and I will soon attach the full patch series.

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions

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


[Kernel-packages] [Bug 1814726] Re: linux: 4.15.0-46.49 -proposed tracker

2019-02-26 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1814741 (linux-azure), bug 1814742 (linux-aws-hwe), bug 
1814743 (linux-azure), bug 1817551 (xenial/linux-azure-edge)
  derivatives: bug 1814728 (linux-raspi2), bug 1814730 (linux-oem), bug 1814731 
(linux-aws)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing 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/1814726

Title:
  linux: 4.15.0-46.49 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1814741 (linux-azure), bug 1814742 (linux-aws-hwe), bug 
1814743 (linux-azure), bug 1817551 (xenial/linux-azure-edge)
  derivatives: bug 1814728 (linux-raspi2), bug 1814730 (linux-oem), bug 1814731 
(linux-aws)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814726/+subscriptions

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


[Kernel-packages] [Bug 1813372] Re: Realtek r8822be kernel module does not negotiate 802.11ac connection

2019-02-26 Thread David R. Bergstein
** Tags added: staging

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

Title:
  Realtek r8822be kernel module does not negotiate 802.11ac connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an HP Omen laptop with dual boot installed.  It has the Realtek
  8822BE wireless chip set installed, which when running Windows 10
  works as intended, i.e., it establishes an 802.11ac connection with my
  wireless router with speeds up to 866 mbps. However when running my
  Linux environment, Ubuntu Studio, the connection speed is established
  as 802.11n, and is limited to 300 mbps.

  I also see the following message in my logs which might be related to
  this issue:

  wlo1: capabilities/regulatory prevented using AP HT/VHT configuration,
  downgraded

  Please advise if additional information is needed. Per the bug
  reporting guidelines also see below.

  1) lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  2) apt-cache policy linux-modules-4.18.0-13-lowlatency
  linux-modules-4.18.0-13-lowlatency:
Installed: 4.18.0-13.14
Candidate: 4.18.0-13.14
Version table:
   *** 4.18.0-13.14 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What I expected to happen - connection at 802.11ac speeds
  4) What happened instead - 802.11n connection
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dbergst1852 F pulseaudio
   /dev/snd/pcmC0D0p:   dbergst1852 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (67 days ago)
  InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:58e6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-lowlatency 
root=UUID=e50d64b3-9d61-4d85-bf8f-c30c4759d7e4 ro quiet splash acpi_osi=! 
"acpi_osi=Windows 2009" vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-lowlatency 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-lowlatency N/A
   linux-backports-modules-4.18.0-15-lowlatency  N/A
   linux-firmware1.175.1
  StagingDrivers: r8822be
  Tags:  cosmic staging
  Uname: Linux 4.18.0-15-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 846A
  dmi.board.vendor: HP
  dmi.board.version: 68.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.08:bd11/09/2018:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn846A:rvr68.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop
  dmi.product.sku: 2XP11AV
  dmi.sys.vendor: HP

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-26 Thread Cs-gon
apport information

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.

  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.

  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.

  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem
  is still present in kernel 5.0-rc8.

  I've done a git bisect and the following commit seems to have
  introduced the problem:

  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100

  ACPI / EC: Restore polling during noirq suspend/resume phases

  BugLink: http://bugs.launchpad.net/bugs/1774063

  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]

  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.

  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.

  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.

  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  m5250252871 F pulseaudio
   /dev/snd/controlC0:  m5250252871 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
  MachineType: LENOVO 20BWS00V00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dvi lapadmins projekt-lap
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1817562] Re: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station

2019-02-26 Thread Cs-gon
apport information

** Tags added: apport-collected xenial

** Description changed:

  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the systems are unable to
  send/receive any packages.
  
  Issuing the command "ethtool -r eth0" does not lead to a successful
  renegotiation. To get a correct link, I have to either undock the
  notebook for about 15 seconds, and then re-dock it, or disconnect the
  LAN cable for about 15 seconds, and then reconnect the cable.
  
  In my case the problem appears about one time in 10-20 suspend/resume
  cycles.
  
  I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem is
  still present in kernel 5.0-rc8.
  
  I've done a git bisect and the following commit seems to have introduced
  the problem:
  
  commit 04e04009bb01502f8023c707d7569ea42fba903b
  Author: Rafael J. Wysocki 
  Date:   Fri Feb 9 22:55:28 2018 +0100
  
  ACPI / EC: Restore polling during noirq suspend/resume phases
  
  BugLink: http://bugs.launchpad.net/bugs/1774063
  
  [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ]
  
  Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
  regression) modified the ACPI EC driver so that it doesn't switch
  over to busy polling mode during noirq stages of system suspend and
  resume in an attempt to fix an issue resulting from that behavior.
  
  However, that modification introduced a system resume regression on
  Thinkpad X240, so make the EC driver switch over to the polling mode
  during noirq stages of system suspend and resume again, which
  effectively reverts the problematic commit.
  
  Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
  Reported-by: Markus Demleitner 
  Tested-by: Markus Demleitner 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 
  
  I have reverted the commit in the Ubuntu Bionic kernel, and cannot
  reproduce the problem any longer.
  
  
  I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: 
https://bugzilla.kernel.org/show_bug.cgi?id=202675
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.18
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  m5250252871 F pulseaudio
+  /dev/snd/controlC0:  m5250252871 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv
+ MachineType: LENOVO 20BWS00V00
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 
ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 
i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-45-generic N/A
+  linux-backports-modules-4.15.0-45-generic  N/A
+  linux-firmware 1.157.21
+ Tags:  xenial
+ Uname: Linux 4.15.0-45-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: dvi lapadmins projekt-lap
+ WifiSyslog:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 02/27/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: JBET68WW (1.32 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20BWS00V00
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad T450s
+ dmi.product.name: 20BWS00V00
+ dmi.product.version: ThinkPad T450s
+ dmi.sys.vendor: LENOVO

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

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

Title:
  Autonegotiation fails for various Lenovo notebooks when resuming
  inside the docking station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autonegotiation fails sporadically for various Lenovo notebooks
  (e.g. T450s, T550, W540) when resuming inside the docking station. The
  speed ethtool reports is 10Mb/s, full duplex, even though that is not
  the speed the connected switch uses. So the 

[Kernel-packages] [Bug 1813372] Re: Realtek r8822be kernel module does not negotiate 802.11ac connection

2019-02-26 Thread David R. Bergstein
I have tested with kernel version 5.0-rc8 and the issue with connection
speed is still there (see below)

wlo1  IEEE 802.11  ESSID:"-5G"  
  Mode:Managed  Frequency:5.66 GHz  Access Point: 20:C0:47:FA:F6:40   
  Bit Rate=300 Mb/s   Tx-Power=23 dBm   
  Retry short limit:7   RTS thr=2347 B   Fragment thr:off
  Power Management:on
  Link Quality=59/70  Signal level=-51 dBm  
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:7   Missed beacon:0

** Tags removed: staging
** Tags added: kernel-bug-exists-upstream

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

Title:
  Realtek r8822be kernel module does not negotiate 802.11ac connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an HP Omen laptop with dual boot installed.  It has the Realtek
  8822BE wireless chip set installed, which when running Windows 10
  works as intended, i.e., it establishes an 802.11ac connection with my
  wireless router with speeds up to 866 mbps. However when running my
  Linux environment, Ubuntu Studio, the connection speed is established
  as 802.11n, and is limited to 300 mbps.

  I also see the following message in my logs which might be related to
  this issue:

  wlo1: capabilities/regulatory prevented using AP HT/VHT configuration,
  downgraded

  Please advise if additional information is needed. Per the bug
  reporting guidelines also see below.

  1) lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  2) apt-cache policy linux-modules-4.18.0-13-lowlatency
  linux-modules-4.18.0-13-lowlatency:
Installed: 4.18.0-13.14
Candidate: 4.18.0-13.14
Version table:
   *** 4.18.0-13.14 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What I expected to happen - connection at 802.11ac speeds
  4) What happened instead - 802.11n connection
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dbergst1852 F pulseaudio
   /dev/snd/pcmC0D0p:   dbergst1852 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (67 days ago)
  InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:58e6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-lowlatency 
root=UUID=e50d64b3-9d61-4d85-bf8f-c30c4759d7e4 ro quiet splash acpi_osi=! 
"acpi_osi=Windows 2009" vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-lowlatency 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-lowlatency N/A
   linux-backports-modules-4.18.0-15-lowlatency  N/A
   linux-firmware1.175.1
  StagingDrivers: r8822be
  Tags:  cosmic staging
  Uname: Linux 4.18.0-15-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 846A
  dmi.board.vendor: HP
  dmi.board.version: 68.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.08:bd11/09/2018:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn846A:rvr68.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop
  dmi.product.sku: 2XP11AV
  dmi.sys.vendor: HP

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

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


Re: [Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-02-26 Thread Tyler Hicks
On 2019-02-25 22:44:17, Tony Espy wrote:
> So it looks like we landed this just in time for the new SRU cycle,
> which means we're looking at a tentative release to proposed on Mar 25.
> Does that sound right?

Yes, that's correct according to the SRU cycle announcement here:

  https://lists.ubuntu.com/archives/kernel-sru-
announce/2019-February/000143.html

> If so, I may check with Anthony to see if there's a possibility that
> linux-oem could possibly re-spin and release earlier...

I'm not sure how common that is. I'll leave it up to you to discuss with
Anthony. Thanks!

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

Title:
  TPM intermittently fails after cold-boot

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

Bug description:
  [Impact]
  On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.

  This bug was originally reported on a Dell XPS 13, but has also
  recently been reported on a Dell Edge Gateway 3000.

  The bug has been confirmed to be fixed in the current development
  release (19.04/Cosmic).

  [Test Case]
  Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:

  "tpm tpm0: A TPM error (2314) occurred continue selftest"

  Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
  should produce errors.

  As this bug is due to a race condition, ideally this test case would
  be run multiple times (20+ cold boots).

  Once the patch is installed the following error message may still be
  present in the syslog, however attempts to use the TPM should work:

  "tpm tpm0: A TPM error (2314) occurred attempting the self test"

  [Regression Potential]
  The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.

  [Original Description]
  After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:

  [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
   [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

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

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


[Kernel-packages] [Bug 397750] Re: mouse : input : event field not found

2019-02-26 Thread Stephan Berger
I can confirm that the syslog gets spammed with 
kernel: [14704.131463] input input10: event field not found

I am also using a Rapier v2 mouse on

4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux

Cheers, Stephan


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

Title:
  mouse : input : event field not found

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Jul 10 10:33:55 jxt4210i2 kernel: [ 8136.876360] input input18: event field 
not found
  Jul 10 10:33:55 jxt4210i2 kernel: [ 8136.876367] input input18: event field 
not found

  This message is flooding my kern.log, messages and syslog

  Reason for this message is USB mouse Verbatim Rapier V2 bought on the 
beginning of 2009.
  Message is flooding my logs since then.

  That time I was using 2.6.27 on intrepid.
  Then short time 2.6.28 on jaunty.
  Currently 2.6.30-9 from https://launchpad.net/~xorg-edgers/+archive/ppa (on 
jaunty)
  (I will update to 2.6.30-10 but I'm convinced it will not help.)
  I tryed also server and rt versions of kernel.

  Similar Bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/386671
  Reporter closed as hardware problem.
  But I have here 2 same Rapier V2 and multiple notebooks, kernels .. all the 
same.

  Identical problem on Arch linux bugs: http://bugs.archlinux.org/task/15461
  No answer and different mouse.

  Importance of this is low.
  In truth, it's only an annoyance.
  But as I'm trying to help with bug reports, and it's not very helpful to have 
that message all over important logs.

  If I misjudged the right package for report, please move it on the right 
place. I really don't know which part of the system is doing it (apart from the 
"kernel" string in messages).
  --- 
  AlsaVersion:
   Advanced Linux Sound Architecture Driver Version 1.0.22.1.
   Compiled on Mar 28 2010 for kernel 2.6.32-18-generic (SMP).
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jay5925 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf064 irq 30'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:83847616,10cf,00100201 
HDA:11c11040,11c10001,00100200'
 Controls  : 21
 Simple ctrls  : 14
  DistroRelease: Ubuntu 10.04
  HibernationDevice: RESUME=UUID=0ba96fad-f105-435f-bab0-40db015d72c3
  MachineType: FUJITSU SIEMENS LIFEBOOK T4210
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 product info: "O2Micro", "SmartCardBus Reader", "V1.0", ""
 manfid: 0x, 0x0001
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 5.0V 16-bit PC Card
 Subdevice 0 (function 0) [unbound]
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-18-generic root=/dev/mapper/vgk-root 
ro quiet splash
  ProcEnviron:
   LANGUAGE=sk_SK:sk:en_GB:en
   PATH=(custom, no user)
   LANG=sk_SK.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
  Regression: No
  RelatedPackageVersions: linux-firmware 1.33
  Reproducible: Yes
  Tags: lucid kconfig needs-upstream-testing
  Uname: Linux 2.6.32-18-generic i686
  UserGroups: adm admin cdrom dialout dip fuse lpadmin netdev plugdev 
sambashare video
  dmi.bios.date: 12/21/2006
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.09
  dmi.board.name: FJNB1B9
  dmi.board.vendor: FUJITSU
  dmi.board.version: CP291221-01
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: T42__
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd12/21/2006:svnFUJITSUSIEMENS:pnLIFEBOOKT4210:pvr:rvnFUJITSU:rnFJNB1B9:rvrCP291221-01:cvnFUJITSUSIEMENS:ct10:cvrT42__:
  dmi.product.name: LIFEBOOK T4210
  dmi.sys.vendor: FUJITSU SIEMENS

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

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


[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2019-02-26 Thread bmaupin
This is the correct commit, right?:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7bf1e44f865523aa16e0eb340a82d643da9215b5

It looks to me like there are a lot more than just ARM changes there,
but I don't know anything about kernel development so I might not be .
I'm surprised to see so many changes committed all at once.

Is there any way to narrow down which change is causing the regression?

>From skimming the changes, one thing that stands out to me was a change
to the intel microcode, only because when my computer started having
problems initially I had ran into one or more other bugs related to the
microcode and I had to upgrade my BIOS to get the latest microcode
working:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751584
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920

... but I'm honestly not sure if any of that was related or just a
timing coincidence.

Thanks!

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1811470] Missing required logs.

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

apport-collect 1811470

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

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

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

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

** Tags added: cosmic

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

Title:
  [witherspoon] removing module nouveau causes cpu hard lockup

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed 18.04 and upgraded kernel to linux-image-generic-hwe-18.04
  (4.18.0-13-generic #14~18.04.1-Ubuntu SMP Thu Dec 6 14:03:47). Copied
  gv100 firmware to /lib/firmware/nvidia, removed and reloaded nouveau
  (modprobe -r and modprobe). Tried to remove nouveau again using
  modprobe -r and I see the trace below. After a while the modprobe -r
  command completed the module was removed successfully.

  [  618.185258] nouveau 0035:04:00.0: DRM: failed to idle channel 1 [DRM]
  [  630.314599] watchdog: CPU 4 self-detected hard LOCKUP @ ioread32+0x2c/0x170
  [  630.314601] watchdog: CPU 4 TB:415266697100, last heartbeat 
TB:410146341428 (1ms ago)
  [  630.314601] Modules linked in: nouveau(-) ofpart at24 cmdlinepart 
uio_pdrv_genirq ipmi_powernv ipmi_devintf powernv_flash uio mtd opal_prd 
ipmi_msghandler ibmpowernv vmx_crypto sch_fq_codel ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
fb_sys_fops drm crct10dif_vpmsum ahci crc32c_vpmsum tg3 libahci 
drm_panel_orientation_quirks [last unloaded: nouveau]
  [  630.314629] CPU: 4 PID: 6623 Comm: modprobe Not tainted 4.18.0-13-generic 
#14~18.04.1-Ubuntu
  [  630.314630] NIP:  c0729afc LR: c0080f766990 CTR: 
c0729ad0
  [  630.314630] REGS: c03fffd87d80 TRAP: 0900   Not tainted  
(4.18.0-13-generic)
  [  630.314631] MSR:  9280b033   
CR: 44002824  XER: 
  [  630.314638] CFAR: c0080f7b2ac4 IRQMASK: 1
  [  630.314639] GPR00: c0080f7ad3f8 c03f6c1bb850 c178c200 
c00c8e7e
  [  630.314642] GPR04:    
0008
  [  630.314644] GPR08: c03fa800 7fff c00c8e7e 
c0080f7b2ab0
  [  630.314647] GPR12: c0729ad0 c03fa800 0001 

  [  630.314649] GPR16:   039a7cc60074 
039a7cc3c978
  [  630.314652] GPR20: 039a7cc60070  78448f88 

  [  630.314654] GPR24: 039a8bf40ee8  c0080f82dca0 
c03fed072098
  [  630.314657] GPR28: c000203968a2c290 c000203968840908 c000203968840900 
0001
  [  630.314660] NIP [c0729afc] ioread32+0x2c/0x170
  [  630.314660] LR [c0080f766990] nouveau_bo_rd32+0x48/0x70 [nouveau]
  [  630.314661] Call Trace:
  [  630.314662] [c03f6c1bb850] [c03f6c1bb890] 0xc03f6c1bb890 
(unreliable)
  [  630.314663] [c03f6c1bb880] [c03f6c1bb8b0] 0xc03f6c1bb8b0
  [  630.314664] [c03f6c1bb8a0] [c0080f7ad3f8] 
nv84_fence_read+0x40/0x60 [nouveau]
  [  630.314666] [c03f6c1bb8c0] [c0080f7aab3c] 
nouveau_fence_update+0x44/0x100 [nouveau]
  [  630.314667] [c03f6c1bb900] [c0080f7ab5d8] 
nouveau_fence_done+0x100/0x180 [nouveau]
  [  630.314668] [c03f6c1bb940] [c0080f7ab8c8] 
nouveau_fence_wait+0x90/0x150 [nouveau]
  [  630.314669] [c03f6c1bb970] [c0080f7a8f90] 
nouveau_channel_idle+0xd8/0x140 [nouveau]
  [  630.314670] [c03f6c1bba00] [c0080f75f75c] 
nouveau_accel_fini+0x74/0xe0 [nouveau]
  [  630.314671] [c03f6c1bba30] [c0080f75f8e8] 
nouveau_drm_unload+0x60/0x130 [nouveau]
  [  630.314672] [c03f6c1bba60] [c00813b1b118] 
drm_dev_unregister+0x70/0x160 [drm]
  [  630.314673] [c03f6c1bbaa0] [c00813b1b3f0] drm_put_dev+0x48/0xa0 
[drm]
  [  630.314675] [c03f6c1bbb10] [c0080f760f8c] 
nouveau_drm_device_remove+0x54/0x90 [nouveau]
  [  630.314676] [c03f6c1bbb50] [c07a746c] 
pci_device_remove+0x6c/0x120
  [  630.314677] [c03f6c1bbb90] [c08a7014] 
device_release_driver_internal+0x294/0x380
  [  630.314678] [c03f6c1bbbe0] [c08a719c] driver_detach+0x7c/0x140
  [  630.314679] 

  1   2   3   >