date:20190321

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Bluetooth audio skips when waking a bluetooth mouse

Status in bluez package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  When I use my Bluetooth A2DP headset together with my mouse, I notice
  this:

  Whenever I leave the mouse still for a few seconds (it seems to enter
  some kind of lower-power-mode) and then start to move it, my music
  most of the time skips for a second. This makes using these two
  bluetooth devices together quite annoying...

  It exists with every bluetooth adapter and any mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 18:59:22 2019
  InstallationDate: Installed on 2019-01-19 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: TOSHIBA Satellite Radius P55W-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=c23973fb-1c63-4119-86be-0b17173e5a2a ro quiet splash acpi_osi=Linux 
"acpi_osi=!Windows 2012" acpi=force acpi_enforce_resources=lax 
i915.enable_rc6=1 i915.enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 
drm.vblankoffdelay=1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.60:bd12/23/2014:svnTOSHIBA:pnSatelliteRadiusP55W-B:pvrPSVP2U-003004:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: INVALID
  dmi.product.name: Satellite Radius P55W-B
  dmi.product.sku: INVALID
  dmi.product.version: PSVP2U-003004
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E8:2A:EA:6E:E5:28  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:309822 acl:9284 sco:0 events:14449 errors:0
TX bytes:9130591 acl:13720 sco:0 commands:309 errors:0

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

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

[Kernel-packages] [Bug 1812502] Re: Bluetooth audio skips when waking a bluetooth mouse

[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Bluetooth audio skips when waking a bluetooth mouse

Status in bluez package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  When I use my Bluetooth A2DP headset together with my mouse, I notice
  this:

  Whenever I leave the mouse still for a few seconds (it seems to enter
  some kind of lower-power-mode) and then start to move it, my music
  most of the time skips for a second. This makes using these two
  bluetooth devices together quite annoying...

  It exists with every bluetooth adapter and any mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 18:59:22 2019
  InstallationDate: Installed on 2019-01-19 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: TOSHIBA Satellite Radius P55W-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=c23973fb-1c63-4119-86be-0b17173e5a2a ro quiet splash acpi_osi=Linux 
"acpi_osi=!Windows 2012" acpi=force acpi_enforce_resources=lax 
i915.enable_rc6=1 i915.enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 
drm.vblankoffdelay=1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.60:bd12/23/2014:svnTOSHIBA:pnSatelliteRadiusP55W-B:pvrPSVP2U-003004:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: INVALID
  dmi.product.name: Satellite Radius P55W-B
  dmi.product.sku: INVALID
  dmi.product.version: PSVP2U-003004
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E8:2A:EA:6E:E5:28  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:309822 acl:9284 sco:0 events:14449 errors:0
TX bytes:9130591 acl:13720 sco:0 commands:309 errors:0

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

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

[Kernel-packages] [Bug 1819694] Re: linux-aws: 4.15.0-1035.37 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => In Progress

** 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 1819693 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
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
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/1819694

Title:
  linux-aws: 4.15.0-1035.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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 snap-release-to-beta series:
  Confirmed
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 verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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 1819693 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1819713] Re: linux-azure: 4.15.0-1041.45 -proposed tracker

** 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 1819711 (trusty/linux-azure)
  derivatives: bug 1819710 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 20:04 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
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/1819713

Title:
  linux-azure: 4.15.0-1041.45 -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:
  Confirmed
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 verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

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 1819711 (trusty/linux-azure)
  derivatives: bug 1819710 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 20:04 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-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in 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/1819713/+subscriptions

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

[Kernel-packages] [Bug 1719545] Re: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

2019-03-21 Thread Khaled El Mously

@sthou...@in.ibm.com: Thanks for that test. Unfortunately I'm not quite sure 
why the patch isn't fixing the problem. This was the patch that IBM submitted 
upstream and reported that it fixes the problem. The patch applied cleanly to 
bionic. I'm still investigating this further and may require your help in 
testing it again if I can't reproduce the issue myself. Will update again 
shortly.
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/1719545

Title:
  [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop
  Idle_Stats

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
  ---Problem Description---
  cpupower monitor shows multiple stop Idle_Stats
   

   
  ---uname output---
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
  Then execute the cpupower monitor command to fetch all the Idle_Stats values.

  root@zz376p1:~# cpupower monitor
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop
 0|   8|   0|  0.00|  0.00|  2.79
 0|   8|   1|  0.00|  0.00| 70.68
 0|   8|   2|  0.00|  0.00| 99.87
 0|   8|   3|  0.00|  0.00| 67.28
 0|  12|   4|  0.00|  0.00|  5.17
 0|  12|   5|  0.00|  0.00| 12.50
 0|  12|   6|  0.00|  0.00| 99.74
 0|  12|   7|  0.00|  0.00|  0.00
 8|2048|   8|  0.00|  0.00| 22.14
 8|2048|   9|  0.00|  0.00| 102.3
 8|2048|  10|  0.00|  0.00|  0.00
 8|2048|  11|  0.00|  0.00| 99.97
 8|2052|  12|  0.00|  0.00| 99.70
 8|2052|  13|  0.00|  0.00| 23.86
 8|2052|  14|  0.00|  0.00| 113.1
 8|2052|  15|  0.00|  0.00|  0.00

  As can be seen it shows 2 columns for stop.

  root@zz376p1:~# uname -a
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  root@zz376p1:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  root@zz376p1:~# cat /proc/cpuinfo | tail
  processor   : 15
  cpu : POWER9 (raw), altivec supported
  clock   : 2600.00MHz
  revision: 1.0 (pvr 004e 0100)

  timebase: 51200
  platform: PowerNV
  model   : 8375-42A
  machine : PowerNV 8375-42A
  firmware: OPAL
   
  Userspace tool common name: /usr/bin/cpupower 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: linux-tools-common

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@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.

  
  .
  There are 3 idle_stats (3 states) in this system. 

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 224
  Duration: 423
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 1685
  Duration: 530522
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 12693
  Duration: 5405898106

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite
  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 272
  Duration: 905
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 2141
  Duration: 536399
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 15396
  Duration: 6625668881

  
  cpu monitor will print the results of all the 3 available idle_stats .

  The

[Kernel-packages] [Bug 1819620] Re: linux-gcp: 4.18.0-1008.9 -proposed tracker

** 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 1819619 (bionic/linux-gcp-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 20:31 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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1819620

Title:
  linux-gcp: 4.18.0-1008.9 -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 verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  New

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 1819619 (bionic/linux-gcp-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 20:31 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/1819620/+subscriptions

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

[Kernel-packages] [Bug 1821271] Re: New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in Ubuntu system

02:00.0 Network controller [0280]: Intel Corporation Device [8086:2526] (rev 29)
 Subsystem: Intel Corporation Device [8086:4018]

** Tags added: originate-from-1820564 somerville

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

Title:
  New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in
  Ubuntu system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  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] 
  New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not 
correctly probed without the corresponding id entry in kernel.

  [Fix]
  Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".

  [Test Case]
  Verified on Intel 9260D2WL.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device 
only.

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

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

[Kernel-packages] [Bug 1821271] [NEW] New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in Ubuntu system

Public bug reported:

[Impact] 
New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not 
correctly probed without the corresponding id entry in kernel.

[Fix]
Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".

[Test Case]
Verified on Intel 9260D2WL.

[Regression Risk]
Low. This patch effectively adds new id match for a unsupported (yet) device 
only.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: linux (Ubuntu Cosmic)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress


** Tags: originate-from-1820564 somerville

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

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

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

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

Title:
  New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in
  Ubuntu system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  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] 
  New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not 
correctly probed without the corresponding id entry in kernel.

  [Fix]
  Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".

  [Test Case]
  Verified on Intel 9260D2WL.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device 
only.

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

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

[Kernel-packages] [Bug 1819692] Re: linux-oem: 4.15.0-1035.40 -proposed tracker

** 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 08:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1819692

Title:
  linux-oem: 4.15.0-1035.40 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 08:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
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/1819692/+subscriptions

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

[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260

** Tags removed: originate-from-1820564 somerville

** Changed in: linux (Ubuntu)
 Assignee: You-Sheng Yang (vicamo) => (unassigned)

** Summary changed:

- iwlwifi not working with Intel AC 9260
+ iwlwifi not working with Intel AC 9260 on kernel 4.15

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

Title:
  iwlwifi not working with Intel AC 9260 on kernel 4.15

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [   22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 
9260, REV=0x324
  [   22.208574] [ cut here ]
  [   22.208575] kernel BUG at 
/build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425!
  [   22.208578] invalid opcode:  [#1] SMP NOPTI
  [   22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek 
snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel 
snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi 
irqbypass uvcvideo mxm_wmi intel_wmi_thunderb
  olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb 
ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer 
intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore
   ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid 
sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) aesni_intel aes_x86_64 crypto_simd
  [   22.208598]  cryptd glue_helper drm_kms_helper syscopyarea sysfillrect 
input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci 
ipmi_msghandler video mac_hid
  [   22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P   OE
4.15.0-43-generic #46-Ubuntu
  [   22.208605] Hardware name: Notebook 
P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018
  [   22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  [   22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286
  [   22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: 
e4b2e1c6ab60
  [   22.208612] RDX: 99b9b38b61a8 RSI:  RDI: 
99b9b8280078
  [   22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 
007690c8
  [   22.208614] R10:  R11: 99b9b8280050 R12: 
99b9b828
  [   22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 
99b9b38b61d0
  [   22.208615] FS:  7fb8c9ec9540() GS:99b9be30() 
knlGS:
  [   22.208616] CS:  0010 DS:  ES:  CR0: 80050033
  [   22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 
003606e0
  [   22.208618] DR0:  DR1:  DR2: 

  [   22.208619] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   22.208619] Call Trace:
  [   22.208623]  _iwl_pcie_rx_init+0x252/0x710 [iwlwifi]
  [   22.208626]  iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi]
  [   22.208631]  ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm]
  [   22.208635]  iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi]
  [   22.208639]  iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm]
  [   22.208640]  ? 0xc198e000
  [   22.208644]  iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208647]  ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208650]  ? iwl_wait_init_complete+0x20/0x20 [iwlmvm]
  [   22.208654]  iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208657]  ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208660]  _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi]
  [   22.208663]  iwl_opmode_register+0x75/0xe0 [iwlwifi]
  [   22.208664]  ? 0xc19e8000
  [   22.208668]  iwl_mvm_init+0x38/0x1000 [iwlmvm]
  [   22.208671]  do_one_initcall+0x52/0x19f
  [   22.208672]  ? _cond_resched+0x19/0x40
  [   22.208674]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [   22.208676]  ? do_init_module+0x27/0x209
  [   22.208678]  do_init_module+0x5f/0x209
  [   22.208679]  load_module+0x191e/0x1f10
  [   22.208681]  ? ima_post_read_file+0x96/0xa0
  [   22.208682]  SYSC_finit_module+0xfc/0x120
  [   22.208683]  ? SYSC_finit_module+0xfc/0x120
  [   22.208685]  SyS_finit_module+0xe/0x10
  [   22.208686]  do_syscall_64+0x73/0x130
  [   22.208688]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   22.208689] RIP: 0033:0x7fb8c99ef839
  [   22.208690] RSP: 002b:7ffecf171ea8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   22.208691] RAX: ffda RBX: 55c40d7462f0 RCX: 
7fb8c99ef839
  [   22.208691] RDX:  RSI: 55c40c09cd2e RDI: 
0001
  [   22.208692] RBP: 55c40c09cd2e R08:  R09: 

  [   22.208693] R10: 0001 R11: 0246 R12: 

  [

[Kernel-packages] [Bug 1819698] Re: linux-gcp: 4.15.0-1029.31 -proposed tracker

** 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 1819695 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 18:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
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
verification-testing: Ongoing -- testing 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/1819698

Title:
  linux-gcp: 4.15.0-1029.31 -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:
  Confirmed
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 verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

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 1819695 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 18:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260

70:00.0 Network controller [0280]: Intel Corporation Device [8086:2526] (rev 29)
Subsystem: Intel Corporation Device [8086:0014]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

The reported device has subsystem id 0014, not 4018 that I was working
on. Will rollback all the changes later.

** No longer affects: linux (Ubuntu Trusty)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: hwe-next

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Cosmic)

** No longer affects: linux (Ubuntu Disco)

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

Title:
  iwlwifi not working with Intel AC 9260

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [   22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 
9260, REV=0x324
  [   22.208574] [ cut here ]
  [   22.208575] kernel BUG at 
/build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425!
  [   22.208578] invalid opcode:  [#1] SMP NOPTI
  [   22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek 
snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel 
snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi 
irqbypass uvcvideo mxm_wmi intel_wmi_thunderb
  olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb 
ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer 
intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore
   ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid 
sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) aesni_intel aes_x86_64 crypto_simd
  [   22.208598]  cryptd glue_helper drm_kms_helper syscopyarea sysfillrect 
input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci 
ipmi_msghandler video mac_hid
  [   22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P   OE
4.15.0-43-generic #46-Ubuntu
  [   22.208605] Hardware name: Notebook 
P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018
  [   22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  [   22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286
  [   22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: 
e4b2e1c6ab60
  [   22.208612] RDX: 99b9b38b61a8 RSI:  RDI: 
99b9b8280078
  [   22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 
007690c8
  [   22.208614] R10:  R11: 99b9b8280050 R12: 
99b9b828
  [   22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 
99b9b38b61d0
  [   22.208615] FS:  7fb8c9ec9540() GS:99b9be30() 
knlGS:
  [   22.208616] CS:  0010 DS:  ES:  CR0: 80050033
  [   22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 
003606e0
  [   22.208618] DR0:  DR1:  DR2: 

  [   22.208619] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   22.208619] Call Trace:
  [   22.208623]  _iwl_pcie_rx_init+0x252/0x710 [iwlwifi]
  [   22.208626]  iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi]
  [   22.208631]  ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm]
  [   22.208635]  iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi]
  [   22.208639]  iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm]
  [   22.208640]  ? 0xc198e000
  [   22.208644]  iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208647]  ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208650]  ? iwl_wait_init_complete+0x20/0x20 [iwlmvm]
  [   22.208654]  iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208657]  ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208660]  _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi]
  [   22.208663]  iwl_opmode_register+0x75/0xe0 [iwlwifi]
  [   22.208664]  ? 0xc19e8000
  [   22.208668]  iwl_mvm_init+0x38/0x1000 [iwlmvm]
  [   22.208671]  do_one_initcall+0x52/0x19f
  [   22.208672]  ? _cond_resched+0x19/0x40
  [   22.208674]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [   22.208676]  ? do_init_module+0x27/0x209
  [   22.208678]  do_init_module+0x5f/0x209
  [   22.208679]  load_module+0x191e/0x1f10
  [   22.208681]  ? ima_post_read_file+0x96/0xa0
  [   22.208682]  SYSC_finit_module+0xfc/0x120
  [   22.208683]  ? SYSC_finit_module+0xfc/0x120
  [   22.208685]  SyS_finit_module+0xe/0x10
  [   22.208686]  do_syscall_64+0x73/0x130
  [   22.208688]

[Kernel-packages] [Bug 1819617] Re: linux-azure: 4.18.0-1014.14~18.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => In Progress

** 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
  
  derivatives: bug 1819616 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819618
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 19:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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:
  Confirmed
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 verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

  derivatives: bug 1819616 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819618
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 19:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
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/1819617/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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-03-21 Thread AceLan Kao

** Changed in: hwe-next
   Status: New => Fix Released

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

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

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  Fix Committed

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 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

2019-03-21 Thread Daniel van Vugt

If you can still ssh in while the screen is frozen then please do so and
run:

  dmesg > frozendmesg.txt

and send us the file 'frozendmesg.txt'

** Summary changed:

- Screen frozen after switch to other tty  and do login & logout
+ [nvidia] Screen frozen after switch to other tty  and do login & logout

** Package changed: gdm3 (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)

** Also affects: nvidia-graphics-drivers-410 (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: nvidia

** Tags added: bionic cosmic

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

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

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Incomplete

** Changed in: nvidia-graphics-drivers-410 (Ubuntu)
   Status: New => Incomplete

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

Title:
  [nvidia] Screen frozen after switch to other tty  and do login &
  logout

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Incomplete

Bug description:
  To simplify reproduce steps, one only has to:
  1. install (tested so far) Ubuntu Bionic
  2. switch to other tty by pressing Ctrl+Alt+Fn
  3. login and logout
  Then it should try to switch back to GDM (no matter you have logged in GUI or 
not), triggers vt-switch bug and lock up.

  Some more findings:

  1. So far we know all other newer Ubuntu versions are immune, e.g.
  Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5).

  2. login _and_ logout from another virtual console is required.
  Switching between text console and GUI back and forth before logging
  out doesn't trigger this bug. So this might(?) also involves systemd-
  logind as well;

  3. while gdm locked up, kernel and the rest of the system are actually
  still alive. Networking is still available, and even the input devices
  are still functioning well. Only gdm fails to grab the device inputs.

  4. when gdm locks up due to either resume from suspend or vt-switch,
  restart gdm (from remote ssh) will bring the system back.

  ### Disco
  | |4.15|4.18|4.19|5.0
  |---||||---
  |nouveau| | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410|Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.

   Packages:
  * kernel:
 * 4.15.0-46-generic
 * 4.18.0-16-generic
 * 4.19.0-13-generic
 * 5.0.0-7-generic
  * nvidia-driver:
 * 390.116-0ubuntu0.18.04.1
 * 390.116-0ubuntu0.18.10.1
 * 410.104-0ubuntu1
  * systemd:
 * 240-6ubuntu1
  * gdm3:
 * 3.31.4+git20190225-1ubuntu1
   Hardware
  * 201811-26623

  Summary: in Ubuntu Disco, nouveau driver is immune from this issue in
  all kernel versions tested. In contrary, nVIDIA driver fails every
  case.

   ### Cosmic
  | |4.15|4.18|4.19|5.0
  |-||||---
  |nouveau | | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410 |Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
   Packages:
  * kernel:
 * 4.15.0-46-generic
 * 4.18.0-16-generic
 * 4.19.0-13-generic
 * 5.0.0-7-generic
  * nvidia-driver:
 * 390.116-0ubuntu0.18.04.1
 * 390.116-0ubuntu0.18.10.1
 * 410.104-0ubuntu1
  * systemd:
 * 239-7ubuntu10
  * gdm3:
 * 3.30.1-1ubuntu5
   Hardware
  * 201811-26623

  Summary: in Ubuntu Cosmic, same with Disco.

  # Bionic
  | |4.15|4.18 |4.19
  |-|||
  |nouveau|Affected[1]| |Affected[1]
  |hwe xorg|Affected[1]| |Affected[1]
  |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1]
  |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1]
  |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1]
  |nvidia-410 |Affected[2]|Affected[1]|Affected[3]
  [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only 
gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a 
remote shell.
  [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm 
(but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` 
to switch to other vt in a remote shell.
  [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm 
instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
  ## Packages:
  * kernel:
 * 4.15.0-46-generic
 * 4.18.0-16-generic
 * 4.19.0-13-generic
  * nvidia-driver:
 *

[Kernel-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "ERROR Atomic update failure on pipe A"

2019-03-21 Thread Daniel van Vugt

Browsing the Xorg modesetting source code it appears that might be to
blame too, since it seems to try to use atomic mode setting.

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

Title:
  Frequent system freezing with i915 error "*ERROR* Atomic update
  failure on pipe A"

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

Bug description:
  My system keeps freezing on a brand new install of Kubuntu 18.10,
  always with the kern.log error "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235)
  time 486 us, min 763, max 767, scanline start 760, end 783"

  I think it's probably a duplicate of these bugs which were closed unresolved:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was 
on an older version of Ubuntu)
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because 
it was a duplicate of the first bug)

  It happens far more frequently if I have desktop effects turned on,
  and far less frequently when using a live USB key (at always happens
  eventually though. Usually once every few hours.)

  Please advise how I can help triage / test. My system is a new install
  now, so I'm perfectly willing to modify / reinstall to help testing
  (I've reinstalled 5 times to test things, but never managed to find a
  solution)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jan 26 14:19:52 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:227a]
  InstallationDate: Installed on 2019-01-18 (8 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager 
modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia 
intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 
i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 
i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.sku: J9L01UA#ABL
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1820997] Re: Ubuntu is freezing with two video monitors

2019-03-21 Thread Daniel van Vugt

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

Yes, the differences in hardware model and software don't matter here.
What's common is that it's an Intel GPU using the Xorg modesetting
driver, which uses the i915 kernel driver.

Your Nvidia GPU doesn't appear to be a problem here.

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

Title:
Ubuntu is freezing with two video monitors

Status in linux package in Ubuntu:
New

Bug description:
Hello,
As you can see in the attached report, I have a Dell, Inspiron notebook with
Nvidia 1050 etc ... I connected to this notebook (through the HDMI port) a
monitor LG 23EA53 ...
Initially the Nouveau driver never worked properly with this video card. It
is a huge pain to do a Ubuntu installation on this notebook because it is very
expensive after installation to get the notebook to start in a text mode
session with internet... and then manually install the Nvidia driver ... But
even with those difficulties (that simply prevent a lay user from having Ubuntu
on their Dell notebook with Nvidia 1050) I was able to give outline solutions
for this.
I always try to use the development version of Ubuntu with the expectation of
being able to help with the tests. So I'm currently using a "Disco" completely
updated... At first (up to 3 months ago) I was working on a Ubuntu session on
Xorg because the Wayland session did not allow me to use another video monitor
connected to my notebook. However, from that time, there was a reversal, the
Xorg session stopped working with the HDMI monitor and Xwayland started
detecting and setting normally this monitor via HDMI.
Well, that's where the problem is! The video monitor is detected, gnome-shell
appears and runs normally on both monitors, but after a few moments of use, the
GUI simply freezes! It always freezes on a point where the mouse cursor is in
background processing mode. In this situation Linux gets completely frozen, not
even the CapsLock, or Ctrl+Shift+F"n" keys work.
The only way out is to completely turn off the notebook using the power
button, then turn the notebook on again with the HDMI monitor disconnected to
prevent further freezing.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xwayland 2:1.20.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.43 Tue Feb 19 01:12:11
CST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 20 08:43:48 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.43, 5.0.0-8-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA
controller])
Subsystem: Dell HD Graphics 630 [1028:0798]
NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
InstallationDate: Installed on 2019-01-30 (48 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190119)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications
Bus 001 Device 002: ID 413c:301d Dell Computer Corp.
Bus 001 Device 004: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 15 7000 Gaming
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic
root=UUID=11a759f5-c884-4c9a-87f0-22554753d054 ro quiet splash vt.handoff=1
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.1
dmi.board.name: 0P84C9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 15 7000 Gaming
dmi.product.sku: 0798
dmi.sys.vendor: Dell Inc.
nvidia-settings:
ERROR: Unable to find display on any available system

ERROR: Unable to find display on any

[Kernel-packages] [Bug 1821194] [NEW] [nvidia] Screen frozen after switch to other tty and do login & logout

You have been subscribed to a public bug:

To simplify reproduce steps, one only has to:
1. install (tested so far) Ubuntu Bionic
2. switch to other tty by pressing Ctrl+Alt+Fn
3. login and logout
Then it should try to switch back to GDM (no matter you have logged in GUI or 
not), triggers vt-switch bug and lock up.

Some more findings:

1. So far we know all other newer Ubuntu versions are immune, e.g.
Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5).

2. login _and_ logout from another virtual console is required.
Switching between text console and GUI back and forth before logging out
doesn't trigger this bug. So this might(?) also involves systemd-logind
as well;

3. while gdm locked up, kernel and the rest of the system are actually
still alive. Networking is still available, and even the input devices
are still functioning well. Only gdm fails to grab the device inputs.

4. when gdm locks up due to either resume from suspend or vt-switch,
restart gdm (from remote ssh) will bring the system back.

### Disco
| |4.15|4.18|4.19|5.0
|---||||---
|nouveau| | | |
|nvidia-390 bionic|Affected|Affected|Affected|Affected
|nvidia-390 cosmic|Affected|Affected|Affected|Affected
|nvidia-410|Affected|Affected|Affected|Affected
Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.

 Packages:
* kernel:
   * 4.15.0-46-generic
   * 4.18.0-16-generic
   * 4.19.0-13-generic
   * 5.0.0-7-generic
* nvidia-driver:
   * 390.116-0ubuntu0.18.04.1
   * 390.116-0ubuntu0.18.10.1
   * 410.104-0ubuntu1
* systemd:
   * 240-6ubuntu1
* gdm3:
   * 3.31.4+git20190225-1ubuntu1
 Hardware
* 201811-26623

Summary: in Ubuntu Disco, nouveau driver is immune from this issue in
all kernel versions tested. In contrary, nVIDIA driver fails every case.

 ### Cosmic
| |4.15|4.18|4.19|5.0
|-||||---
|nouveau | | | |
|nvidia-390 bionic|Affected|Affected|Affected|Affected
|nvidia-390 cosmic|Affected|Affected|Affected|Affected
|nvidia-410 |Affected|Affected|Affected|Affected
Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
 Packages:
* kernel:
   * 4.15.0-46-generic
   * 4.18.0-16-generic
   * 4.19.0-13-generic
   * 5.0.0-7-generic
* nvidia-driver:
   * 390.116-0ubuntu0.18.04.1
   * 390.116-0ubuntu0.18.10.1
   * 410.104-0ubuntu1
* systemd:
   * 239-7ubuntu10
* gdm3:
   * 3.30.1-1ubuntu5
 Hardware
* 201811-26623

Summary: in Ubuntu Cosmic, same with Disco.

# Bionic
| |4.15|4.18 |4.19
|-|||
|nouveau|Affected[1]| |Affected[1]
|hwe xorg|Affected[1]| |Affected[1]
|nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1]
|nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1]
|nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1]
|nvidia-410 |Affected[2]|Affected[1]|Affected[3]
[1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only 
gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a 
remote shell.
[2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm 
(but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` 
to switch to other vt in a remote shell.
[3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm 
instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
## Packages:
* kernel:
   * 4.15.0-46-generic
   * 4.18.0-16-generic
   * 4.19.0-13-generic
* nvidia-driver:
   * 390.116-0ubuntu0.18.04.1
   * 390.116-0ubuntu0.18.10.1
   * 410.104-0ubuntu1
* systemd:
   * 237-3ubuntu10.12
* gdm3:
   * 3.28.3-0ubuntu18.04.3
## Hardware
* 201811-26623

Summary: only 4.18 kernel with nouveau driver is immune from this issue,
which follows some changes in user land should be necessary to stabilize
all the (nouveau) cases. But even with that, from previous results of
Cosmic/Disco, there should still some works to be done in the nvidia
driver.

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

-- 
[nvidia] Screen frozen after switch to other tty  and do login & logout
https://bugs.launchpad.net/bugs/1821194
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.

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

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2019-03-21 Thread Bug Watch Updater

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

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

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

To manage notifications about this bug go to:

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

2019-03-21 Thread Bug Watch Updater

Launchpad has imported 21 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=194521.

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

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

Created attachment 254611
crash logged using netconsole

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

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

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

Attached are kernel messages using netconsle.

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

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

Created attachment 254621
nomodeset - no crash

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

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

Created attachment 254631
iommu=off - no crash

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

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

Created attachment 254641
lspci -vvv

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

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

Created attachment 254651
/proc/cpuinfo

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

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

Created attachment 254661
crash logged using netconsole

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

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

Do you have the amdgpu firmware installed?

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

Problems might be fixed in the latest code.

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

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

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

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

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

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

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

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

I will try a newer kernel.

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

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

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

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

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

I'm attaching netconsole logs...

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

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

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

[Kernel-packages] [Bug 1690085]

2019-03-21 Thread cevelnet

@Borislav has the fix for erratum 1033 "A Lock Operation May Cause the
System to Hang" been applied so far? The suggested workaround was
"Program MSRC001_1020[4] to 1b", but I couldn't find anything about it
in master branch. According to the document, 1033 only affects B1.

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

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

[Kernel-packages] [Bug 1690085]

2019-03-21 Thread bp

There's a patch in comment #526 for people to test before we include it
so that there's at least *some* fix in the kernel, going forward...

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

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

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1690085]

2019-03-21 Thread jvdelisle

I am running Fedora on AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
with Gnome.

I use kernel parameters idle=nomwait iommu=pt processor.max_cstate=1 set
via grubby.

I am not getting any hangs unless I suspend with lid close or suspend on
power button. It would probably be better to not execute an MWAIT per
the errata.  The method in comment 561 would work for those who have the
gumption to build their own kernel.

The iommu=pt I read about somewhere as useful to do, but I don't know if
it helps. Some suggest set idle=halt which also avoids the MWAIT
instruction.

I am also told that the DRI driver has an issue with loading at boot
which will hang the kernel.
https://bugs.freedesktop.org/show_bug.cgi?id=109206

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04

[Kernel-packages] [Bug 1690085]

2019-03-21 Thread bp

(In reply to alfie from comment #566)
> But I really want C6/P6 and ignoring the BIOS seems to get me there...

Why do you think the patch I pointed to won't give you C6?

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

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

To manage notifications about this

[Kernel-packages] [Bug 1690085]

2019-03-21 Thread alfie

(In reply to Another User from comment #564)
> Can your system reach turbo frequencies with this patch?
> Maybe I understand something wrongly...

Yes, I have a ryzen 1600 and I can see 1/2 cores running at ~3.6 GHz
under some peculiar stress case.


(In reply to Borislav Petkov from comment #565)
> There's a patch in comment #526 for people to test before we include it so
> that there's at least *some* fix in the kernel, going forward...

But I really want C6/P6 and ignoring the BIOS seems to get me there...

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color

[Kernel-packages] [Bug 1690085]

2019-03-21 Thread zao

(In reply to Borislav Petkov from comment #569)
> (In reply to Tolga Cakir from comment #568)
> Such a "fix" does not exist. Possibly because it is unlikely this is causing
> it and BIOS might be applying the fix already. People with B1s (model 1,
> stepping 1) could test though by doing as root:
> 
> # modprobe msr
> # rdmsr -a 0xc0011020
> 
> and looking at bit 4 in the result.

I've got an ASUS PRIME X370-PRO with the B1 CPU mentioned on firmware 4024
(from 2018/09/28).

rdmsr yields 68010, which has bit 4 set.

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:

[Kernel-packages] [Bug 1690085]

2019-03-21 Thread bp

(In reply to Tolga Cakir from comment #568)
> @Borislav has the fix for erratum 1033 "A Lock Operation May Cause the
> System to Hang" been applied so far? The suggested workaround was "Program
> MSRC001_1020[4] to 1b", but I couldn't find anything about it in master
> branch. According to the document, 1033 only affects B1.

Such a "fix" does not exist. Possibly because it is unlikely this is
causing it and BIOS might be applying the fix already. People with B1s
(model 1, stepping 1) could test though by doing as root:

# modprobe msr
# rdmsr -a 0xc0011020

and looking at bit 4 in the result.

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64

[Kernel-packages] [Bug 1690085]

2019-03-21 Thread to_load

(In reply to alfie from comment #561)
> This is pretty strange, could someone explain it to me? Wasn't mwait bugged
> in ryzen?

Looks like this patch makes kernel to ignore BIOS messages about unsupported 
C-state.
this function used in "acpi_processor_ffh_cstate_probe" which further used in 
"processor_idle.c" file. It cause "cx.entry_method" value change from 
ACPI_CSTATE_SYSTEMIO to ACPI_CSTATE_FFH.

It is really strange that this patch works but idle=halt is not. Maybe this is 
somehow silently disables C6 state.
Can your system reach turbo frequencies with this patch?
Maybe I understand something wrongly...

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" -

[Kernel-packages] [Bug 1821259] Re: Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

[X][PATCH 0/4] LP#1821259 Fix for deadlock in cpu_stopper
https://lists.ubuntu.com/archives/kernel-team/2019-March/099427.html

[B][PATCH 0/2] Fix for LP#1821259 (pending patches for) Fix for deadlock in 
cpu_stopper
https://lists.ubuntu.com/archives/kernel-team/2019-March/099432.html

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

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

** No longer affects: linux (Ubuntu)

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

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

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

Title:
  Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

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

Bug description:
  [Impact]

   * This problem hard locks up 2 CPUs in a deadlock, and this
 soft locks up other CPUs as an effect; the system becomes
 unusable.

   * This is relatively rare / difficult to hit because it's a
 corner case in scheduling/load balancing that needs timing
 with CPU stopper code. And it needs SMP plus _NUMA_ system.
 (but it can be hit with synthetic test case attached in LP.)

   * Since SMP plus NUMA usually equals _servers_ it looks like
 a good idea to prevent this bug / hard lockups / rebooting.

   * The fix resolves the potential deadlock by removing one of
 the calls required to deadlock from under the locked code.

  [Test Case]

   * There's a synthetic test case to reproduce this problem
 (although without the stack traces - just a system hang)
 attached to this LP bug.

   * It uses kprobes/mdelay/cpu stopper calls to force the code
 to execute and force the timing/locking condition to occur.

   * $ sudo insmod kmod-stopper.ko

 Some dmesg logging occurs, and systems either hangs or not.
 See examples in comments.
 
  [Regression Potential] 

   * These are patches to the cpu stop_machine.c code, and they
 change a bit how it works;  however, there are no upstream
 fixes for these patches anymore and they are still the top
 of the 'git log --oneline -- kernel/stop_machine.c' output.

   * These patches have been verified with the synthetic test case
 and 'stress-ng --class scheduler --sequential 0' (no regressions)
 on guest with 2 CPUs and one physical system with 24 CPUs.

  [Other Info]
   
   * The patches are required on Xenial and later.
   * There are 4 patches for Xenial, and 2 patches pending for Bionic.
   * All patches are applied from Cosmic onwards.

  [Original Description]

  These 2 hard lockups happened all of a sudden in the logs, and many
  soft lockups occur after them as a fallout.

  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.477086] NMI watchdog: 
Watchdog detected hard LOCKUP on cpu 10
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.483800] Modules linked in: 
<...>
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484066] CPU: 10 PID: 58 
Comm: migration/10 Not tainted 4.4.0-116-generic #140~14.04.1-Ubuntu
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484068] Hardware name: HP 
ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 02/17/2017
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484070] task: 
883ff2a76200 ti: 883ff211 task.ti: 883ff211
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484071] RIP: 
0010:[]  [] 
native_queued_spin_lock_slowpath+0x160/0x170
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484079] RSP: 
:883ff2113c58  EFLAGS: 0002
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484080] RAX: 
0101 RBX: 0086 RCX: 0001
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484081] RDX: 
0101 RSI: 0001 RDI: 881fff991ba8
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484083] RBP: 
883ff2113c58 R08: 0101 R09: 883ff082e200
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484084] R10: 
2e04 R11: 2e04 R12: 881fff997c60
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484085] R13: 
881fff991ba8 R14:  R15: 881fff997300
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484087] FS:  
() GS:883fff00() knlGS:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484088] CS:  0010 DS:  
ES:  CR0: 80050033
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484090] CR2: 
7f7caaa23020 CR3: 001f4674 CR4: 00160670
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484091] Stack:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484092]  883ff2113c68 
811870eb 883ff2113c80 81819907
  Nov 23 15:48:33 SYSTEM_NAME

[Kernel-packages] [Bug 1821259] Re: Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Since Bionic already has the fix commit applied,
the original kernel version doesn't hit the problem.

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

Title:
  Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * This problem hard locks up 2 CPUs in a deadlock, and this
 soft locks up other CPUs as an effect; the system becomes
 unusable.

   * This is relatively rare / difficult to hit because it's a
 corner case in scheduling/load balancing that needs timing
 with CPU stopper code. And it needs SMP plus _NUMA_ system.
 (but it can be hit with synthetic test case attached in LP.)

   * Since SMP plus NUMA usually equals _servers_ it looks like
 a good idea to prevent this bug / hard lockups / rebooting.

   * The fix resolves the potential deadlock by removing one of
 the calls required to deadlock from under the locked code.

  [Test Case]

   * There's a synthetic test case to reproduce this problem
 (although without the stack traces - just a system hang)
 attached to this LP bug.

   * It uses kprobes/mdelay/cpu stopper calls to force the code
 to execute and force the timing/locking condition to occur.

   * $ sudo insmod kmod-stopper.ko

 Some dmesg logging occurs, and systems either hangs or not.
 See examples in comments.
 
  [Regression Potential] 

   * These are patches to the cpu stop_machine.c code, and they
 change a bit how it works;  however, there are no upstream
 fixes for these patches anymore and they are still the top
 of the 'git log --oneline -- kernel/stop_machine.c' output.

   * These patches have been verified with the synthetic test case
 and 'stress-ng --class scheduler --sequential 0' (no regressions)
 on guest with 2 CPUs and one physical system with 24 CPUs.

  [Other Info]
   
   * The patches are required on Xenial and later.
   * There are 4 patches for Xenial, and 2 patches pending for Bionic.
   * All patches are applied from Cosmic onwards.

  [Original Description]

  These 2 hard lockups happened all of a sudden in the logs, and many
  soft lockups occur after them as a fallout.

  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.477086] NMI watchdog: 
Watchdog detected hard LOCKUP on cpu 10
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.483800] Modules linked in: 
<...>
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484066] CPU: 10 PID: 58 
Comm: migration/10 Not tainted 4.4.0-116-generic #140~14.04.1-Ubuntu
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484068] Hardware name: HP 
ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 02/17/2017
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484070] task: 
883ff2a76200 ti: 883ff211 task.ti: 883ff211
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484071] RIP: 
0010:[]  [] 
native_queued_spin_lock_slowpath+0x160/0x170
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484079] RSP: 
:883ff2113c58  EFLAGS: 0002
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484080] RAX: 
0101 RBX: 0086 RCX: 0001
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484081] RDX: 
0101 RSI: 0001 RDI: 881fff991ba8
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484083] RBP: 
883ff2113c58 R08: 0101 R09: 883ff082e200
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484084] R10: 
2e04 R11: 2e04 R12: 881fff997c60
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484085] R13: 
881fff991ba8 R14:  R15: 881fff997300
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484087] FS:  
() GS:883fff00() knlGS:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484088] CS:  0010 DS:  
ES:  CR0: 80050033
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484090] CR2: 
7f7caaa23020 CR3: 001f4674 CR4: 00160670
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484091] Stack:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484092]  883ff2113c68 
811870eb 883ff2113c80 81819907
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484094]  881fff991ba0 
883ff2113cb0 8111c600 881fff997300
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484096]  881fff997c90 
881ff03dd400  883ff2113cc0
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484098] Call Trace:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484105]  
[] queued_spin_lock_slowpath+0xb/0xf
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484109]  
[] _raw_spin_lock_irqsave+0x37/0x40
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484113]  
[] cpu_stop_queue_work+0x30/0x80
  Nov

[Kernel-packages] [Bug 1821259] Re: Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Both xenial and bionic original/patched kernels
were tested with stress-ng scheduler class, and
no regressions were observed.

$ stress-ng --version
stress-ng, version 0.09.56 (gcc 8.3, x86_64 Linux 4.15.0-47-generic) 

$ sudo stress-ng --class scheduler --sequential 0

$ uname -rv
4.4.0-144-generic #170-Ubuntu SMP Thu Mar 14 11:56:20 UTC 2019

$ uname -rv
4.4.0-144-generic #170+test20190320b1 SMP Wed Mar 20 18:35:06 UTC 2019

$ uname -rv
4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019

$ uname -rv
4.15.0-47-generic #50+test20190320b1 SMP Wed Mar 20 20:08:03 UTC 2019

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

Title:
  Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * This problem hard locks up 2 CPUs in a deadlock, and this
 soft locks up other CPUs as an effect; the system becomes
 unusable.

   * This is relatively rare / difficult to hit because it's a
 corner case in scheduling/load balancing that needs timing
 with CPU stopper code. And it needs SMP plus _NUMA_ system.
 (but it can be hit with synthetic test case attached in LP.)

   * Since SMP plus NUMA usually equals _servers_ it looks like
 a good idea to prevent this bug / hard lockups / rebooting.

   * The fix resolves the potential deadlock by removing one of
 the calls required to deadlock from under the locked code.

  [Test Case]

   * There's a synthetic test case to reproduce this problem
 (although without the stack traces - just a system hang)
 attached to this LP bug.

   * It uses kprobes/mdelay/cpu stopper calls to force the code
 to execute and force the timing/locking condition to occur.

   * $ sudo insmod kmod-stopper.ko

 Some dmesg logging occurs, and systems either hangs or not.
 See examples in comments.
 
  [Regression Potential] 

   * These are patches to the cpu stop_machine.c code, and they
 change a bit how it works;  however, there are no upstream
 fixes for these patches anymore and they are still the top
 of the 'git log --oneline -- kernel/stop_machine.c' output.

   * These patches have been verified with the synthetic test case
 and 'stress-ng --class scheduler --sequential 0' (no regressions)
 on guest with 2 CPUs and one physical system with 24 CPUs.

  [Other Info]
   
   * The patches are required on Xenial and later.
   * There are 4 patches for Xenial, and 2 patches pending for Bionic.
   * All patches are applied from Cosmic onwards.

  [Original Description]

  These 2 hard lockups happened all of a sudden in the logs, and many
  soft lockups occur after them as a fallout.

  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.477086] NMI watchdog: 
Watchdog detected hard LOCKUP on cpu 10
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.483800] Modules linked in: 
<...>
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484066] CPU: 10 PID: 58 
Comm: migration/10 Not tainted 4.4.0-116-generic #140~14.04.1-Ubuntu
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484068] Hardware name: HP 
ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 02/17/2017
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484070] task: 
883ff2a76200 ti: 883ff211 task.ti: 883ff211
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484071] RIP: 
0010:[]  [] 
native_queued_spin_lock_slowpath+0x160/0x170
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484079] RSP: 
:883ff2113c58  EFLAGS: 0002
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484080] RAX: 
0101 RBX: 0086 RCX: 0001
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484081] RDX: 
0101 RSI: 0001 RDI: 881fff991ba8
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484083] RBP: 
883ff2113c58 R08: 0101 R09: 883ff082e200
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484084] R10: 
2e04 R11: 2e04 R12: 881fff997c60
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484085] R13: 
881fff991ba8 R14:  R15: 881fff997300
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484087] FS:  
() GS:883fff00() knlGS:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484088] CS:  0010 DS:  
ES:  CR0: 80050033
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484090] CR2: 
7f7caaa23020 CR3: 001f4674 CR4: 00160670
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484091] Stack:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484092]  883ff2113c68 
811870eb 883ff2113c80 81819907
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484094]  881fff991ba0 
883ff2113cb0 8111c600 881fff997300
  Nov 23

[Kernel-packages] [Bug 1821259] Re: Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Test-case on Xenial;

$ ls -1d /sys/devices/system/cpu/cpu[0-9]*
/sys/devices/system/cpu/cpu0
/sys/devices/system/cpu/cpu1


Original


$ uname -rv
4.4.0-144-generic #170-Ubuntu SMP Thu Mar 14 11:56:20 UTC 2019

$ sudo insmod kmod-stopper/kmod-stopper.ko
[   74.198379] mod_init() :: this cpu = 0x1, that cpu = 0x0
[   74.199613] mod_init() :: that_cpu_stopper_task = 88003d80e600, comm = 
migration/0
[   74.206194] kp2/stop_two_cpus() :: this cpu = 0x1, that cpu = 0x0
[   74.206196] do_nothing() :: this cpu = 0x0, that cpu = 0x1
[   74.206201] kp1/pick_next_task_fair() :: this cpu = 0x0, that cpu = 0x1
[   74.206203] kp1/pick_next_task_fair() :: before sleep (1000 msecs)
[   74.212759] kp2/stop_two_cpus() :: before sleep (500 msecs)
[   74.710138] kp2/stop_two_cpus() :: after  sleep (500 msecs)
[   75.198324] kp1/pick_next_task_fair() :: after  sleep (1000 msecs)
[   75.199814] kp1/pick_next_task_fair() :: stopping other cpu...


The test-case only failed 2 out of 50+ tests.


Patched:
---

$ uname -rv
4.4.0-144-generic #170+test20190320b1 SMP Wed Mar 20 18:35:06 UTC 2019

$ sudo insmod kmod-stopper/kmod-stopper.ko
[   85.958527] mod_init() :: this cpu = 0x1, that cpu = 0x0
[   85.965876] mod_init() :: that_cpu_stopper_task = 88003d80e600, comm = 
migration/0
[   85.993446] kp2/stop_two_cpus() :: this cpu = 0x1, that cpu = 0x0
[   85.993471] do_nothing() :: this cpu = 0x0, that cpu = 0x1
[   85.993477] kp1/pick_next_task_fair() :: this cpu = 0x0, that cpu = 0x1
[   85.993480] kp1/pick_next_task_fair() :: before sleep (1000 msecs)
[   86.019469] kp2/stop_two_cpus() :: before sleep (500 msecs)
[   86.521688] kp2/stop_two_cpus() :: after  sleep (500 msecs)
[   86.987662] kp1/pick_next_task_fair() :: after  sleep (1000 msecs)
[   86.989427] kp1/pick_next_task_fair() :: stopping other cpu...
[   86.991109] do_nothing() :: this cpu = 0x1, that cpu = 0x0
[   86.992615] do_nothing() :: this cpu = 0x1, that cpu = 0x0


It passes every time (50+ tests).

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

Title:
  Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * This problem hard locks up 2 CPUs in a deadlock, and this
 soft locks up other CPUs as an effect; the system becomes
 unusable.

   * This is relatively rare / difficult to hit because it's a
 corner case in scheduling/load balancing that needs timing
 with CPU stopper code. And it needs SMP plus _NUMA_ system.
 (but it can be hit with synthetic test case attached in LP.)

   * Since SMP plus NUMA usually equals _servers_ it looks like
 a good idea to prevent this bug / hard lockups / rebooting.

   * The fix resolves the potential deadlock by removing one of
 the calls required to deadlock from under the locked code.

  [Test Case]

   * There's a synthetic test case to reproduce this problem
 (although without the stack traces - just a system hang)
 attached to this LP bug.

   * It uses kprobes/mdelay/cpu stopper calls to force the code
 to execute and force the timing/locking condition to occur.

   * $ sudo insmod kmod-stopper.ko

 Some dmesg logging occurs, and systems either hangs or not.
 See examples in comments.
 
  [Regression Potential] 

   * These are patches to the cpu stop_machine.c code, and they
 change a bit how it works;  however, there are no upstream
 fixes for these patches anymore and they are still the top
 of the 'git log --oneline -- kernel/stop_machine.c' output.

   * These patches have been verified with the synthetic test case
 and 'stress-ng --class scheduler --sequential 0' (no regressions)
 on guest with 2 CPUs and one physical system with 24 CPUs.

  [Other Info]
   
   * The patches are required on Xenial and later.
   * There are 4 patches for Xenial, and 2 patches pending for Bionic.
   * All patches are applied from Cosmic onwards.

  [Original Description]

  These 2 hard lockups happened all of a sudden in the logs, and many
  soft lockups occur after them as a fallout.

  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.477086] NMI watchdog: 
Watchdog detected hard LOCKUP on cpu 10
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.483800] Modules linked in: 
<...>
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484066] CPU: 10 PID: 58 
Comm: migration/10 Not tainted 4.4.0-116-generic #140~14.04.1-Ubuntu
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484068] Hardware name: HP 
ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 02/17/2017
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484070] task: 
883ff2a76200 ti: 883ff211 task.ti: 883ff211
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484071] RIP: 
0010:[]  [] 
native_queued_spin_lock_slowpath+0x160/0x170
  Nov 23 15:48:33 SYSTEM_NAME

[Kernel-packages] [Bug 1821259] Re: Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

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

Title:
  Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * This problem hard locks up 2 CPUs in a deadlock, and this
 soft locks up other CPUs as an effect; the system becomes
 unusable.

   * This is relatively rare / difficult to hit because it's a
 corner case in scheduling/load balancing that needs timing
 with CPU stopper code. And it needs SMP plus _NUMA_ system.
 (but it can be hit with synthetic test case attached in LP.)

   * Since SMP plus NUMA usually equals _servers_ it looks like
 a good idea to prevent this bug / hard lockups / rebooting.

   * The fix resolves the potential deadlock by removing one of
 the calls required to deadlock from under the locked code.

  [Test Case]

   * There's a synthetic test case to reproduce this problem
 (although without the stack traces - just a system hang)
 attached to this LP bug.

   * It uses kprobes/mdelay/cpu stopper calls to force the code
 to execute and force the timing/locking condition to occur.

   * $ sudo insmod kmod-stopper.ko

 Some dmesg logging occurs, and systems either hangs or not.
 See examples in comments.
 
  [Regression Potential] 

   * These are patches to the cpu stop_machine.c code, and they
 change a bit how it works;  however, there are no upstream
 fixes for these patches anymore and they are still the top
 of the 'git log --oneline -- kernel/stop_machine.c' output.

   * These patches have been verified with the synthetic test case
 and 'stress-ng --class scheduler --sequential 0' (no regressions)
 on guest with 2 CPUs and one physical system with 24 CPUs.

  [Other Info]
   
   * The patches are required on Xenial and later.
   * There are 4 patches for Xenial, and 2 patches pending for Bionic.
   * All patches are applied from Cosmic onwards.

  [Original Description]

  These 2 hard lockups happened all of a sudden in the logs, and many
  soft lockups occur after them as a fallout.

  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.477086] NMI watchdog: 
Watchdog detected hard LOCKUP on cpu 10
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.483800] Modules linked in: 
<...>
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484066] CPU: 10 PID: 58 
Comm: migration/10 Not tainted 4.4.0-116-generic #140~14.04.1-Ubuntu
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484068] Hardware name: HP 
ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 02/17/2017
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484070] task: 
883ff2a76200 ti: 883ff211 task.ti: 883ff211
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484071] RIP: 
0010:[]  [] 
native_queued_spin_lock_slowpath+0x160/0x170
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484079] RSP: 
:883ff2113c58  EFLAGS: 0002
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484080] RAX: 
0101 RBX: 0086 RCX: 0001
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484081] RDX: 
0101 RSI: 0001 RDI: 881fff991ba8
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484083] RBP: 
883ff2113c58 R08: 0101 R09: 883ff082e200
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484084] R10: 
2e04 R11: 2e04 R12: 881fff997c60
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484085] R13: 
881fff991ba8 R14:  R15: 881fff997300
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484087] FS:  
() GS:883fff00() knlGS:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484088] CS:  0010 DS:  
ES:  CR0: 80050033
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484090] CR2: 
7f7caaa23020 CR3: 001f4674 CR4: 00160670
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484091] Stack:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484092]  883ff2113c68 
811870eb 883ff2113c80 81819907
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484094]  881fff991ba0 
883ff2113cb0 8111c600 881fff997300
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484096]  881fff997c90 
881ff03dd400  883ff2113cc0
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484098] Call Trace:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484105]  
[] queued_spin_lock_slowpath+0xb/0xf
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484109]  
[] _raw_spin_lock_irqsave+0x37/0x40
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484113]  
[] cpu_stop_queue_work+0x30/0x80
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484116]  
[] stop_one_cpu_nowait+0x30/0x40
  Nov 23

[Kernel-packages] [Bug 1821259] Re: Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Test-case (kmod-stopper.c)
-

$ sudo apt-get -y install gcc make libelf-dev linux-headers-$(uname -r)

$ touch Makefile # fake it, and use this make line:
$ make -C /lib/modules/$(uname -r)/build M=$(pwd) obj-m=kmod-stopper.o modules

$ echo 9 | sudo tee /proc/sys/kernel/printk

$ sudo insmod kmod-stopper.ko



$ sudo rmmod kmod-stopper


** Attachment added: "kmod-stopper.c"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821259/+attachment/5248313/+files/kmod-stopper.c

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

Title:
  Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * This problem hard locks up 2 CPUs in a deadlock, and this
 soft locks up other CPUs as an effect; the system becomes
 unusable.

   * This is relatively rare / difficult to hit because it's a
 corner case in scheduling/load balancing that needs timing
 with CPU stopper code. And it needs SMP plus _NUMA_ system.
 (but it can be hit with synthetic test case attached in LP.)

   * Since SMP plus NUMA usually equals _servers_ it looks like
 a good idea to prevent this bug / hard lockups / rebooting.

   * The fix resolves the potential deadlock by removing one of
 the calls required to deadlock from under the locked code.

  [Test Case]

   * There's a synthetic test case to reproduce this problem
 (although without the stack traces - just a system hang)
 attached to this LP bug.

   * It uses kprobes/mdelay/cpu stopper calls to force the code
 to execute and force the timing/locking condition to occur.

   * $ sudo insmod kmod-stopper.ko

 Some dmesg logging occurs, and systems either hangs or not.
 See examples in comments.
 
  [Regression Potential] 

   * These are patches to the cpu stop_machine.c code, and they
 change a bit how it works;  however, there are no upstream
 fixes for these patches anymore and they are still the top
 of the 'git log --oneline -- kernel/stop_machine.c' output.

   * These patches have been verified with the synthetic test case
 and 'stress-ng --class scheduler --sequential 0' (no regressions)
 on guest with 2 CPUs and one physical system with 24 CPUs.

  [Other Info]
   
   * The patches are required on Xenial and later.
   * There are 4 patches for Xenial, and 2 patches pending for Bionic.
   * All patches are applied from Cosmic onwards.

  [Original Description]

  These 2 hard lockups happened all of a sudden in the logs, and many
  soft lockups occur after them as a fallout.

  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.477086] NMI watchdog: 
Watchdog detected hard LOCKUP on cpu 10
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.483800] Modules linked in: 
<...>
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484066] CPU: 10 PID: 58 
Comm: migration/10 Not tainted 4.4.0-116-generic #140~14.04.1-Ubuntu
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484068] Hardware name: HP 
ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 02/17/2017
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484070] task: 
883ff2a76200 ti: 883ff211 task.ti: 883ff211
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484071] RIP: 
0010:[]  [] 
native_queued_spin_lock_slowpath+0x160/0x170
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484079] RSP: 
:883ff2113c58  EFLAGS: 0002
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484080] RAX: 
0101 RBX: 0086 RCX: 0001
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484081] RDX: 
0101 RSI: 0001 RDI: 881fff991ba8
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484083] RBP: 
883ff2113c58 R08: 0101 R09: 883ff082e200
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484084] R10: 
2e04 R11: 2e04 R12: 881fff997c60
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484085] R13: 
881fff991ba8 R14:  R15: 881fff997300
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484087] FS:  
() GS:883fff00() knlGS:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484088] CS:  0010 DS:  
ES:  CR0: 80050033
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484090] CR2: 
7f7caaa23020 CR3: 001f4674 CR4: 00160670
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484091] Stack:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484092]  883ff2113c68 
811870eb 883ff2113c80 81819907
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484094]  881fff991ba0 
883ff2113cb0 8111c600 881fff997300
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484096]  881fff997c90 
881ff03dd400

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

2019-03-21 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 1821259

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: xenial

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

Title:
  Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * This problem hard locks up 2 CPUs in a deadlock, and this
 soft locks up other CPUs as an effect; the system becomes
 unusable.

   * This is relatively rare / difficult to hit because it's a
 corner case in scheduling/load balancing that needs timing
 with CPU stopper code. And it needs SMP plus _NUMA_ system.
 (but it can be hit with synthetic test case attached in LP.)

   * Since SMP plus NUMA usually equals _servers_ it looks like
 a good idea to prevent this bug / hard lockups / rebooting.

   * The fix resolves the potential deadlock by removing one of
 the calls required to deadlock from under the locked code.

  [Test Case]

   * There's a synthetic test case to reproduce this problem
 (although without the stack traces - just a system hang)
 attached to this LP bug.

   * It uses kprobes/mdelay/cpu stopper calls to force the code
 to execute and force the timing/locking condition to occur.

   * $ sudo insmod kmod-stopper.ko

 Some dmesg logging occurs, and systems either hangs or not.
 See examples in comments.
 
  [Regression Potential] 

   * These are patches to the cpu stop_machine.c code, and they
 change a bit how it works;  however, there are no upstream
 fixes for these patches anymore and they are still the top
 of the 'git log --oneline -- kernel/stop_machine.c' output.

   * These patches have been verified with the synthetic test case
 and 'stress-ng --class scheduler --sequential 0' (no regressions)
 on guest with 2 CPUs and one physical system with 24 CPUs.

  [Other Info]
   
   * The patches are required on Xenial and later.
   * There are 4 patches for Xenial, and 2 patches pending for Bionic.
   * All patches are applied from Cosmic onwards.

  [Original Description]

  These 2 hard lockups happened all of a sudden in the logs, and many
  soft lockups occur after them as a fallout.

  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.477086] NMI watchdog: 
Watchdog detected hard LOCKUP on cpu 10
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.483800] Modules linked in: 
<...>
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484066] CPU: 10 PID: 58 
Comm: migration/10 Not tainted 4.4.0-116-generic #140~14.04.1-Ubuntu
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484068] Hardware name: HP 
ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 02/17/2017
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484070] task: 
883ff2a76200 ti: 883ff211 task.ti: 883ff211
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484071] RIP: 
0010:[]  [] 
native_queued_spin_lock_slowpath+0x160/0x170
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484079] RSP: 
:883ff2113c58  EFLAGS: 0002
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484080] RAX: 
0101 RBX: 0086 RCX: 0001
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484081] RDX: 
0101 RSI: 0001 RDI: 881fff991ba8
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484083] RBP: 
883ff2113c58 R08: 0101 R09: 883ff082e200
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484084] R10: 
2e04 R11: 2e04 R12: 881fff997c60
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484085] R13: 
881fff991ba8 R14:  R15: 881fff997300
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484087] FS:  
() GS:883fff00() knlGS:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484088] CS:  0010 DS:  
ES:  CR0: 80050033
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484090] CR2: 
7f7caaa23020 CR3: 001f4674 CR4: 00160670
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484091] Stack:
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484092]  883ff2113c68 
811870eb 883ff2113c80 81819907
  Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484094]  881fff991ba0 
883ff2113cb0

[Kernel-packages] [Bug 1821259] Re: Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Analysis


The 1st hard lockup is harder to get the interesting data out of, as apparently 
the registers with variables
related to the cpu number have been clobbered by more recent calls in the 
spinlock path.

Looking at the 2nd hard lockup:

addr2line + code shows us that try_to_wake_up() in line 1997 is indeed
looping with IRQs disabled in line 1939 (thus a hard lockup):

$ addr2line -pifae 
ddeb-116.140/usr/lib/debug/boot/vmlinux-4.4.0-116-generic 0x810aacb6
 
0x810aacb6: try_to_wake_up at 
/build/linux-lts-xenial-ozsla7/linux-lts-xenial-4.4.0/kernel/sched/core.c:1997

1926 static int
1927 try_to_wake_up(struct task_struct *p, unsigned int state, int 
wake_flags)
1928 {
...
1939 raw_spin_lock_irqsave(>pi_lock, flags);
...
1993 /*
1994  * If the owning (remote) cpu is still in the middle of 
schedule() with
1995  * this task as prev, wait until its done referencing the task.
1996  */
1997 while (p->on_cpu)
1998 cpu_relax();
...
2027 raw_spin_unlock_irqrestore(>pi_lock, flags);
2028 
2029 return success;
2030 }

The objdump disassembly of try_to_wake_up() in vmlinux for the RIP instruction 
address (810aacb6),
shows a while loop that just checks for non-zero 'p->on_cpu' and calls 
cpu_relax() (which translates to the 'pause' instruction):

810aacb1:   f3 90   pause
810aacb3:   8b 43 28mov0x28(%rbx),%eax
810aacb6:   85 c0   test   %eax,%eax
810aacb8:   75 f7   jne810aacb1 


So, it checks for the value in pointer in RBX + offset 0x28, which
according to the 'pahole' tool, is indeed the 'on_cpu' field:

$ pahole --hex -C task_struct 
ddeb-116.140/usr/lib/debug/boot/vmlinux-4.4.0-116-generic | grep on_cpu 
 
inton_cpu;   /*  0x28   0x4 */

So, the task_struct pointer is in RBX, which is:

RBX: 883ff2a76200

And that matches the other hard locked up task on CPU 10 (see its
'task:' field).

Per the stack trace in CPU 10, and the identical timestamp of the two hard 
lockup messages, and the fact both stack traces are cpu_stopper related,
it does look like CPU 10 is waiting on the spinlock of one of the 2 cpu 
stoppers held by CPU 6, which is exactly the scenario in the suggested patch.

The problem/fix has been verified with a synthetic test-case (attached).


commit 0b26351b910fb8fe6a056f8a1bbccabe50c0e19f
Author: Peter Zijlstra 
Date:   Fri Apr 20 11:50:05 2018 +0200

stop_machine, sched: Fix migrate_swap() vs. active_balance() deadlock

Matt reported the following deadlock:

CPU0CPU1

schedule(.prev=migrate/0)   
  pick_next_task()...
idle_balance()  migrate_swap()
  active_balance()stop_two_cpus()
spin_lock(stopper0->lock)
spin_lock(stopper1->lock)
ttwu(migrate/0)
  smp_cond_load_acquire() 
-- waits for schedule()
stop_one_cpu(1)
  spin_lock(stopper1->lock) -- waits for stopper lock

Fix this deadlock by taking the wakeups out from under stopper->lock.
This allows the active_balance() to queue the stop work and finish the
context switch, which in turn allows the wakeup from migrate_swap() to
observe the context and complete the wakeup.
<...>


The stop_two_cpus() call can only happen in a NUMA system per it's caller chain:
  stop_two_cpus() <- migrate_swap() <- task_numa_migrate() <- 
numa_migrate_preferred() <- [task_numa_placement()] <- task_numa_fault()

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

Title:
  Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * This problem hard locks up 2 CPUs in a deadlock, and this
 soft locks up other CPUs as an effect; the system becomes
 unusable.

   * This is relatively rare / difficult to hit because it's a
 corner case in scheduling/load balancing that needs timing
 with CPU stopper code. And it needs SMP plus _NUMA_ system.
 (but it can be hit with synthetic test case attached in LP.)

   * Since SMP plus NUMA usually equals _servers_ it looks like
 a good idea to prevent this bug / hard lockups / rebooting.

   * The fix resolves the potential deadlock by removing one of
 the calls required to

[Kernel-packages] [Bug 1821259] [NEW] Hard lockup in 2 CPUs due to deadlock in cpu_stoppers

Public bug reported:

[Impact]

 * This problem hard locks up 2 CPUs in a deadlock, and this
   soft locks up other CPUs as an effect; the system becomes
   unusable.

 * This is relatively rare / difficult to hit because it's a
   corner case in scheduling/load balancing that needs timing
   with CPU stopper code. And it needs SMP plus _NUMA_ system.
   (but it can be hit with synthetic test case attached in LP.)

 * Since SMP plus NUMA usually equals _servers_ it looks like
   a good idea to prevent this bug / hard lockups / rebooting.

 * The fix resolves the potential deadlock by removing one of
   the calls required to deadlock from under the locked code.

[Test Case]

 * There's a synthetic test case to reproduce this problem
   (although without the stack traces - just a system hang)
   attached to this LP bug.

 * It uses kprobes/mdelay/cpu stopper calls to force the code
   to execute and force the timing/locking condition to occur.

 * $ sudo insmod kmod-stopper.ko

   Some dmesg logging occurs, and systems either hangs or not.
   See examples in comments.
   
[Regression Potential] 

 * These are patches to the cpu stop_machine.c code, and they
   change a bit how it works;  however, there are no upstream
   fixes for these patches anymore and they are still the top
   of the 'git log --oneline -- kernel/stop_machine.c' output.

 * These patches have been verified with the synthetic test case
   and 'stress-ng --class scheduler --sequential 0' (no regressions)
   on guest with 2 CPUs and one physical system with 24 CPUs.

[Other Info]
 
 * The patches are required on Xenial and later.
 * There are 4 patches for Xenial, and 2 patches pending for Bionic.
 * All patches are applied from Cosmic onwards.

[Original Description]

These 2 hard lockups happened all of a sudden in the logs, and many soft
lockups occur after them as a fallout.

Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.477086] NMI watchdog: Watchdog 
detected hard LOCKUP on cpu 10
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.483800] Modules linked in: 
<...>
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484066] CPU: 10 PID: 58 Comm: 
migration/10 Not tainted 4.4.0-116-generic #140~14.04.1-Ubuntu
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484068] Hardware name: HP 
ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 02/17/2017
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484070] task: 883ff2a76200 
ti: 883ff211 task.ti: 883ff211
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484071] RIP: 
0010:[]  [] 
native_queued_spin_lock_slowpath+0x160/0x170
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484079] RSP: 
:883ff2113c58  EFLAGS: 0002
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484080] RAX: 0101 
RBX: 0086 RCX: 0001
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484081] RDX: 0101 
RSI: 0001 RDI: 881fff991ba8
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484083] RBP: 883ff2113c58 
R08: 0101 R09: 883ff082e200
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484084] R10: 2e04 
R11: 2e04 R12: 881fff997c60
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484085] R13: 881fff991ba8 
R14:  R15: 881fff997300
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484087] FS:  
() GS:883fff00() knlGS:
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484088] CS:  0010 DS:  ES: 
 CR0: 80050033
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484090] CR2: 7f7caaa23020 
CR3: 001f4674 CR4: 00160670
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484091] Stack:
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484092]  883ff2113c68 
811870eb 883ff2113c80 81819907
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484094]  881fff991ba0 
883ff2113cb0 8111c600 881fff997300
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484096]  881fff997c90 
881ff03dd400  883ff2113cc0
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484098] Call Trace:
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484105]  [] 
queued_spin_lock_slowpath+0xb/0xf
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484109]  [] 
_raw_spin_lock_irqsave+0x37/0x40
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484113]  [] 
cpu_stop_queue_work+0x30/0x80
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484116]  [] 
stop_one_cpu_nowait+0x30/0x40
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484119]  [] 
load_balance+0x71b/0x940
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484122]  [] 
pick_next_task_fair+0x275/0x4b0
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484126]  [] 
__schedule+0x6c6/0x7f0
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484132]  [] 
? sort_range+0x30/0x30
Nov 23 15:48:33 SYSTEM_NAME kernel: [4603802.484134]  []

[Kernel-packages] [Bug 1819656] Re: linux-raspi2: 4.4.0-1105.113 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
certification-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
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.4.0-1105.113 -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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1819612] Re: linux-raspi2: 4.18.0-1011.13 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Thursday, 21. March 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
certification-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-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1819612

Title:
  linux-raspi2: 4.18.0-1011.13 -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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Cosmic:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Thursday, 21. March 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-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/1819612/+subscriptions

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

[Kernel-packages] [Bug 1820308] Re: linux-raspi2: 5.0.0-1004.4 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

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

** Tags removed: block-proposed-disco

** Tags removed: block-proposed

** 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 --
  kernel-master-bug: 1819759
- phase: Testing
- phase-changed: Friday, 15. March 2019 20:01 UTC
+ phase: Ready for Release
+ phase-changed: Thursday, 21. March 2019 21:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   promote-to-release: Pending -- ready to copy

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

Title:
  linux-raspi2: 5.0.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Disco:
  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 --
  kernel-master-bug: 1819759
  phase: Ready for Release
  phase-changed: Thursday, 21. March 2019 21:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy

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

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

[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp

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

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

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

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xrdp package in Ubuntu:
  Confirmed

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rushik 4016 F pulseaudio
   /dev/snd/controlC1:  rushik 4016 F pulseaudio
   /dev/snd/controlC0:  rushik 4016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c
  InstallationDate: Installed on 2019-01-11 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  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: 01/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z390-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp

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

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

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

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xrdp package in Ubuntu:
  Confirmed

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rushik 4016 F pulseaudio
   /dev/snd/controlC1:  rushik 4016 F pulseaudio
   /dev/snd/controlC0:  rushik 4016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c
  InstallationDate: Installed on 2019-01-11 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  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: 01/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z390-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1776563]

2019-03-21 Thread eutychios23

Ness are you using secure boot?

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1776563]

2019-03-21 Thread eutychios23

your fan runs at 100% because you use pci=noacpi

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1761379] Comment bridged from LTC Bugzilla

2019-03-21 Thread bugproxy

--- Comment From grom...@br.ibm.com 2019-03-21 16:33 EDT---
Hi Cascardo,

(In reply to comment #36)
> I would like to ask if using the same location as the real perf binary
> itself would be fine for your needs.
>
> That is, a symlink at /usr/lib/linux-tools/`uname -r`/libperf_jvmti.so
> pointing at /usr/lib/linux-tools-SRCVERSION-ABINUMBER/libperf_jvmti.so.

That location and symlink are perfectly fine for me.

Just a nit: you probably meant libperf-jvmti.so (with dash) instead of
libperf_jvmti.so, right? If not, although that won't impact much in
practice, I would like to keep the upstream default file name, with
dash.

Thanks a lot & best regards,
Gustavo

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

Title:
  [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
  deb on Ubuntu

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
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:
  ---Problem Description---
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods
   
  ---uname output---
  inux-image-4.13.0-36-generic
   
  Machine Type = not relevant 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   File libperf-jvmti.so is missing in linux-tools-common deb provided for 
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

  I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
  apparently it's no being packaged in any .deb file?

  Thanks. 
   

   
  Userspace tool common name: perf 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace tool obtained from project website:  na

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

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

[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed

2019-03-21 Thread Tyler Hicks

Hello Talat - You said that this test passes on the 18.04 LTS kernel so
it is worth nothing that the commit you identified is also present in
that kernel. It was released in 4.15.0-32.34:

  https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?id=77a24c313d21e3765b04d90521e9228a9bb6e332

All that patch does is change the defaults of the following two sysctls:

  /proc/sys/net/ipv4/ipfrag_high_thresh
  /proc/sys/net/ipv4/ipfrag_low_thresh

To temporarily go back to the old defaults (you'll lose these changes on
reboot), you can run the following commands (be sure to run them in this
order):

$ echo 4194304 | sudo tee /proc/sys/net/ipv4/ipfrag_high_thresh
$ echo 3145728 | sudo tee /proc/sys/net/ipv4/ipfrag_low_thresh

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

Title:
  [cosmic] ipoib ping with large message size failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We see that ping over ipoib interface stuck with large packets, this is a new 
degradation, this test pass on Ubuntu 18.04.
  After investigating the issue, we see that commit [1] introduce the issue, 
and it is not an upstream commit, it is canonical commit.
  Could you please check with the canonical kernel team why they revert that 
commit? 
  To reproduce the bug, please use ConnectX-3 devices with ipoib connection 
with 2044 MTU (default) and run command [2].
  Is there open Launchpad on it?
   
  [1]
  commit 77a24c313d21e3765b04d90521e9228a9bb6e332
  Author: Tyler Hicks 
  Date:   Fri Aug 3 21:53:15 2018 +
   
  Revert "net: increase fragment memory usage limits"
   
  This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It
  made denial of service attacks on the IP fragment handling easier to
  carry out.
   
  CVE-2018-5391
   
  Signed-off-by: Tyler Hicks 
  Signed-off-by: Stefan Bader 
   
  [2]
  ping 13.194.22.1 -I 13.194.23.1 -s 65507

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

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

[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed

2019-03-21 Thread Jeff Lane

Hi Talat,

Something else occurs to me, could you list which kernels are affected?
Is this correct so far:

4.15: Not affected
4.18: Affected
How about 5.0 and perhaps 4.4 (not sure if 4.4 includes support for this 
though, so that may be not worth investigating.)

And for failing kernels, could you provide the full version (per uname)?
that helps too.

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

Title:
  [cosmic] ipoib ping with large message size failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We see that ping over ipoib interface stuck with large packets, this is a new 
degradation, this test pass on Ubuntu 18.04.
  After investigating the issue, we see that commit [1] introduce the issue, 
and it is not an upstream commit, it is canonical commit.
  Could you please check with the canonical kernel team why they revert that 
commit? 
  To reproduce the bug, please use ConnectX-3 devices with ipoib connection 
with 2044 MTU (default) and run command [2].
  Is there open Launchpad on it?
   
  [1]
  commit 77a24c313d21e3765b04d90521e9228a9bb6e332
  Author: Tyler Hicks 
  Date:   Fri Aug 3 21:53:15 2018 +
   
  Revert "net: increase fragment memory usage limits"
   
  This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It
  made denial of service attacks on the IP fragment handling easier to
  carry out.
   
  CVE-2018-5391
   
  Signed-off-by: Tyler Hicks 
  Signed-off-by: Stefan Bader 
   
  [2]
  ping 13.194.22.1 -I 13.194.23.1 -s 65507

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

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

[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed

2019-03-21 Thread Jeff Lane

Err... nevermind 4.4 anyway. just 5.0 would be interesting to see if
this persisted into Disco.

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

Title:
  [cosmic] ipoib ping with large message size failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We see that ping over ipoib interface stuck with large packets, this is a new 
degradation, this test pass on Ubuntu 18.04.
  After investigating the issue, we see that commit [1] introduce the issue, 
and it is not an upstream commit, it is canonical commit.
  Could you please check with the canonical kernel team why they revert that 
commit? 
  To reproduce the bug, please use ConnectX-3 devices with ipoib connection 
with 2044 MTU (default) and run command [2].
  Is there open Launchpad on it?
   
  [1]
  commit 77a24c313d21e3765b04d90521e9228a9bb6e332
  Author: Tyler Hicks 
  Date:   Fri Aug 3 21:53:15 2018 +
   
  Revert "net: increase fragment memory usage limits"
   
  This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It
  made denial of service attacks on the IP fragment handling easier to
  carry out.
   
  CVE-2018-5391
   
  Signed-off-by: Tyler Hicks 
  Signed-off-by: Stefan Bader 
   
  [2]
  ping 13.194.22.1 -I 13.194.23.1 -s 65507

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

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

[Kernel-packages] [Bug 1819028] Re: Intel 9260 WiFi adapter doesn't work on B450 motherboard

2019-03-21 Thread bionicle159

just tried the firmware after updating, unfortunately doesn't work

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

Title:
  Intel 9260 WiFi adapter doesn't work on B450 motherboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, I know this has been a well discussed issue on Linux forums, but I
  am having extreme issues maintaining the built-in Intel WiFi in my
  motherboard, it resets everytime I update my distros (Ubuntu 18.04 and
  Linux Mint Cinnamon 18.3). My best fix for it is following the guide
  at [https://askubuntu.com/questions/1038242/no-wifi-option-on-
  ubuntu-18-04-and-16-04].

  I am wanting to know if there is a way to make this process more streamlined 
for users as this affects many and is a hassle to maintain properly. I know 
this has been addressed before with Ryzen CPUs but this shouldn't have to be 
necessary if the driver is baked into the kernel as this is quite frustrating 
for any user to go through, as it requires what is causing the problem to fix - 
a network connection. I don't mind if it's simpler to have a on/off feature 
like the Nvidia drivers have, as that is still a lot simpler than writing out a 
paragraphs of code.
   
  TL;DR I'm asking if changes could be added so that instead of needing a 
network connection (something that you can't have if the driver isn't built 
into/available through the distro) and writing a dissertation of code, they 
have a driver automatically work or a switch option like Broadcom and Nvidia 
have in this photo 
[https://linuxhint.com/wp-content/uploads/2017/11/driver-manager-1.png]

  I was referred here by the Linux Mint forum, please refer to the page
  in case any questions have already been answered there
  
[https://forums.linuxmint.com/viewtopic.php?f=49=289358=1=unread#unread]

  My system is a AMD Ryzen 2700x B450 with built-in Intel 9260 WiFi,
  Linux Mint 18.3/Ubuntu 18.04 dual boot.

  Thanks, Bionicle159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amir   2179 F pulseaudio
   /dev/snd/controlC1:  amir   2179 F pulseaudio
   /dev/snd/controlC2:  amir   2179 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b
  InstallationDate: Installed on 2018-08-22 (210 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Micro-Star International Co., Ltd. MS-7B85
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=4c3c212e-59c3-4de8-a1a2-24acc6e040d6 ro quiet splash 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:  sylvia
  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: 08/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450 GAMING PRO CARBON AC (MS-7B85)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd08/06/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B85:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450GAMINGPROCARBONAC(MS-7B85):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B85
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amir   2179 F pulseaudio
   /dev/snd/controlC1:  amir   2179 F pulseaudio
   /dev/snd/controlC2:  amir   2179 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b
  InstallationDate: Installed on 2018-08-22 (210 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Micro-Star International Co., Ltd. MS-7B85
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine:

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-03-21 Thread Seth Forshee

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: Incomplete => Fix Committed

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  New
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in The Cosmic Cuttlefish:
  New
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13 11:53:36 james-x1 kernel: [  856.845103] iwlwifi

[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic

2019-03-21 Thread Seth Forshee

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

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

Title:
  Missing firmware in linux-image-4.15.0-10-generic

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  linux-image-4.15.0-10-generic doesn't have the firmware that linux-
  image-4.13.0-32-generic has. It doesn't have any of the files that are
  present in 4.13 in /lib/firmware/4.13.0-32-generic/.

  For me, this means i can boot 4.15, but my network wont work because
  of:

  kernel: [   13.468996] bnx2 :0b:00.0: Direct firmware load for 
bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2
  kernel: [   13.468998] bnx2: Can't load firmware file 
"bnx2/bnx2-mips-09-6.2.1b.fw"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 feb 23 13:12 seq
   crw-rw 1 root audio 116, 33 feb 23 13:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Feb 23 13:50:38 2018
  InstallationDate: Installed on 2018-02-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180212)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM System x3550 M3 -[7944S77]-
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[D6E158AUS-1.16]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 00D4062
  dmi.board.vendor: IBM
  dmi.board.version: (none)
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone:
  dmi.product.family: System x
  dmi.product.name: System x3550 M3 -[7944S77]-
  dmi.product.version: 00
  dmi.sys.vendor: IBM

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

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

[Kernel-packages] [Bug 1819698] Re: linux-gcp: 4.15.0-1029.31 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** 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 1819695 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 18:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
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
verification-testing: Ongoing -- testing 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/1819698

Title:
  linux-gcp: 4.15.0-1029.31 -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:
  Confirmed
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 verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

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 1819695 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 18:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

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

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
- phase: Promote to Proposed
- phase-changed: Thursday, 21. March 2019 16:59 UTC
+ phase: Testing
+ phase-changed: Thursday, 21. March 2019 19:41 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: Pending -- snap not in 18-pi3/beta channel
+   snap-release-to-edge: Pending -- snap not in 18-pi3/edge 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-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1819691

Title:
  linux-raspi2: 4.15.0-1033.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18-pi3/beta channel
snap-release-to-edge: Pending -- snap not in 18-pi3/edge channel
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1819656] Re: linux-raspi2: 4.4.0-1105.113 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

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

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
- phase: Promote to Proposed
- phase-changed: Thursday, 21. March 2019 18:04 UTC
+ phase: Testing
+ phase-changed: Thursday, 21. March 2019 19:40 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-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
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.4.0-1105.113 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1820409] Re: Audio stutter after update

2019-03-21 Thread Johnny Izzo

Yes, tried a few back now. 4.15.0-43-generic is the last good one.


-44 has the weird things, Youtube video goes slower (or stops for while) and 
then speeds too much and audio gets out of sync with that.

In VLC audio stutter starts at about after first 10 to 12 seconds.

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

Title:
  Audio stutter after update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After some update:
  Audio stutters in VLC
  Video and audio stutters in Youtube

  I think cpu usage might be bigger in VLC too, over 20% vs. below 20%
  earlier (one thread gets full 100%?)

  Stuttering kernel at the moment is 4.15.0-46-generic.

  Kernel version 4.15.0-43-generic definitely worked good.
  Cant remember if i could get slight stutter from previous version version -45.

  
  Tried also lowlatency and 4.18 kernel, bad stuttering in those.

  (Distro is Lubuntu)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-46-generic.
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: CX20751/2 Analog [CX20751/2 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meie855 F pulseaudio
   /dev/snd/controlC1:  meie855 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf711c000 irq 50'
 Mixer name : 'Intel Broadwell HDMI'
 Components : 'HDA:80862808,80860101,0010'
 Controls  : 35
 Simple ctrls  : 5
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xf7118000 irq 47'
 Mixer name : 'Conexant CX20751/2'
 Components : 'HDA:14f1510f,1043181d,00100100'
 Controls  : 20
 Simple ctrls  : 9
  CurrentDesktop: LXDE
  Date: Sat Mar 16 18:02:18 2019
  InstallationDate: Installed on 2018-07-04 (255 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305FA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=a032fe2a-8284-47a9-a0d1-cfa1f01a5812 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305FA.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305FA
  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.:bvrUX305FA.210:bd05/19/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305FA
  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/1820409/+subscriptions

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

[Kernel-packages] [Bug 1757445] Re: Suspend does not always resume

2019-03-21 Thread Gary Kenneth Krueger

I've found that I can make the system stable with the following
settings:

System Settings:
Privacy>Screen Lock:On
Power>Dim screen when inactive:  Off
Power>Blank screen: 10m
Power>Automatic suspend:
On Battery Power:   On
Delay:  20m
Plugged In: On
Delay:  1h
Power>When the Power Button is pressed:  Suspend
Devices>Displays>Night LightOff
Gnome Tweaks (installed):
Power>Suspend when laptop lid is closed:  On

Upgraded BIOS.

Graphics are:
Intel® Sandybridge Mobile
NVidia Optimus

It seems to hang with "Night Light" and "Dim screen when inactive"
enabled.  So, I have those off.  I originally had "Night Light" enabled
with sunrise and sunset.  That caused my system to try to hang around
sunrise and sunset.  And it generally would hang when unsuspending after
one of those options activated.

Anyhow, I will be trying this out sometime soon to prevent that sort of
trouble:

http://www.akitaonrails.com/2017/03/14/enabling-optimus-nvidia-gpu-on-
the-dell-xps-15-with-linux-even-on-battery

I expect that will allow me to use the "Night Light" and "Dim screen
when inactive" options.

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

Title:
  Suspend does not always resume

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Dell XPS 13 9350 on AC power left running overnight, suspends after a
  given timeout. When coming back the next morning sometimes the laptop
  resumes to an aubergine desktop (just the screen, no GDM) and cursor
  and sits there forever. Sometimes it resumes to a black screen and
  cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 14:15:04 2018
  InstallationDate: Installed on 2018-02-13 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

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

2019-03-21 Thread Michael J

Bugs still persist with bios 1.13 and 5.0+ kernels. Advanced touchpad
doesn't work out the box like 4.19 and 4.20 did, new dmesg errors about
pcie powersaving [use pcie_aspm=off to fix], complaints about not
locating smbus and iommu too late in the boot (sometimes causing
softlocks [fix with Ives args]), and acpi tables not all loading [11
successful]. These bugs persist, so should not be closed. I think
someone with some handy bios skills should look at what Lenovo and HP
have done with their bioses vs ours as their MBs [same] work well now.
It's been over a year since these computers have been on the market
without much in the way of Linux compatibility. I doubt Acer will bother
to debug correctly as it works with Windows and that's the only thing
they're concerned about supporting, unfortunately. If we close this bug
report, then we all might as well give up on these machines.

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1821068] Re: Touchpad not detected on Dell XPS 13 model 9370

2019-03-21 Thread Kai-Heng Feng

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

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

Title:
  Touchpad not detected on Dell XPS 13 model 9370

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Touchpad is not working.

  I've run "sudo apt update", run "sudo apt dist-upgrade" and rebooted.
  Problem still exists.

  When I run "cat /proc/bus/input/devices", the touchpad is not listed.

  
  I ran "ubuntu-bug linux".

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mike   1509 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 21 07:26:01 2019
  HibernationDevice: RESUME=UUID=43c674f8-b23d-4a8f-b188-d60f44b8b754
  InstallationDate: Installed on 2019-02-14 (34 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=faf516f1-21f1-41b1-8fe6-0454c10f66d0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0H6H3J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H6H3J:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

2019-03-21 Thread Steve Beattie

The linux kernel apport hook is provided by apport directly, so needs to
be fixed there:

  $ grep -i Wifi /usr/share/apport/package-hooks/source_linux.py
apport.hookutils.attach_wifi(report)
  $ dpkg -S /usr/share/apport/package-hooks/source_linux.py
apport: /usr/share/apport/package-hooks/source_linux.py

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

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

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

[Kernel-packages] [Bug 1819656] Re: linux-raspi2: 4.4.0-1105.113 -proposed tracker

** 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 18:04 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copies requested
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-raspi2: 4.4.0-1105.113 -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:
  New
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 Committed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 18:04 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1756700] Re: Ryzen/Raven Ridge USB ports do not work

2019-03-21 Thread Kai-Heng Feng

When I wrote the workaround, I didn't observe this:
[   60.486464] xhci_hcd :05:00.3: Refused to change power state, currently 
in D3
[   60.486471] xhci_hcd :05:00.4: Refused to change power state, currently 
in D3

So please file a new bug report.

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

Title:
  Ryzen/Raven Ridge USB ports do not work

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

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

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

[Kernel-packages] [Bug 1819698] Re: linux-gcp: 4.15.0-1029.31 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

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

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** 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 1819695 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
- phase: Promote to Proposed
- phase-changed: Thursday, 21. March 2019 15:06 UTC
+ phase: Testing
+ phase-changed: Thursday, 21. March 2019 18:39 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
+   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
+   verification-testing: Ongoing -- testing 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/1819698

Title:
  linux-gcp: 4.15.0-1029.31 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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:
  Confirmed
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 verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

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 1819695 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 18:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
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
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1819028] Re: Intel 9260 WiFi adapter doesn't work on B450 motherboard

2019-03-21 Thread bionicle159

I'm going to update the Linux kernel to the latest option (4.15.0-46.49)
This will probably stop the Intel wifi from working, this should be a great
way to test the new firmware you sent

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

Title:
  Intel 9260 WiFi adapter doesn't work on B450 motherboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, I know this has been a well discussed issue on Linux forums, but I
  am having extreme issues maintaining the built-in Intel WiFi in my
  motherboard, it resets everytime I update my distros (Ubuntu 18.04 and
  Linux Mint Cinnamon 18.3). My best fix for it is following the guide
  at [https://askubuntu.com/questions/1038242/no-wifi-option-on-
  ubuntu-18-04-and-16-04].

  I am wanting to know if there is a way to make this process more streamlined 
for users as this affects many and is a hassle to maintain properly. I know 
this has been addressed before with Ryzen CPUs but this shouldn't have to be 
necessary if the driver is baked into the kernel as this is quite frustrating 
for any user to go through, as it requires what is causing the problem to fix - 
a network connection. I don't mind if it's simpler to have a on/off feature 
like the Nvidia drivers have, as that is still a lot simpler than writing out a 
paragraphs of code.
   
  TL;DR I'm asking if changes could be added so that instead of needing a 
network connection (something that you can't have if the driver isn't built 
into/available through the distro) and writing a dissertation of code, they 
have a driver automatically work or a switch option like Broadcom and Nvidia 
have in this photo 
[https://linuxhint.com/wp-content/uploads/2017/11/driver-manager-1.png]

  I was referred here by the Linux Mint forum, please refer to the page
  in case any questions have already been answered there
  
[https://forums.linuxmint.com/viewtopic.php?f=49=289358=1=unread#unread]

  My system is a AMD Ryzen 2700x B450 with built-in Intel 9260 WiFi,
  Linux Mint 18.3/Ubuntu 18.04 dual boot.

  Thanks, Bionicle159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amir   2179 F pulseaudio
   /dev/snd/controlC1:  amir   2179 F pulseaudio
   /dev/snd/controlC2:  amir   2179 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b
  InstallationDate: Installed on 2018-08-22 (210 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Micro-Star International Co., Ltd. MS-7B85
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=4c3c212e-59c3-4de8-a1a2-24acc6e040d6 ro quiet splash 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:  sylvia
  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: 08/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450 GAMING PRO CARBON AC (MS-7B85)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd08/06/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B85:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450GAMINGPROCARBONAC(MS-7B85):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B85
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amir   2179 F pulseaudio
   /dev/snd/controlC1:  amir   2179 F pulseaudio
   /dev/snd/controlC2:  amir   2179 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b
  InstallationDate: Installed on 2018-08-22 (210 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Micro-Star International Co., Ltd. MS-7B85
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset

[Kernel-packages] [Bug 1819704] Re: linux-oracle: 4.15.0-1010.12 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** 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 1819703 (xenial/linux-oracle)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 17:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   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-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1819704

Title:
  linux-oracle: 4.15.0-1010.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 verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Bionic:
  New

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 1819703 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 17:00 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/1819704/+subscriptions

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

[Kernel-packages] [Bug 1819612] Re: linux-raspi2: 4.18.0-1011.13 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
- phase: Promote to Proposed
- phase-changed: Thursday, 21. March 2019 16:34 UTC
+ phase: Testing
+ phase-changed: Thursday, 21. March 2019 18:31 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-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-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1819612

Title:
  linux-raspi2: 4.18.0-1011.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Cosmic:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Thursday, 21. March 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-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/1819612/+subscriptions

-- 
Mailing list: https://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 1821068] Re: Touchpad not detected on Dell XPS 13 model 9370

2019-03-21 Thread Michael Nahas

Replaced motherboard and trackpad.  The problem is fixed.  Seems to have been a 
hardware issue. 
You can mark the issue as "closed" or "not (our) bug".
On Thursday, March 21, 2019, 11:06:24 AM CDT, Michael Nahas 
 wrote:  
 
  No, "sudo modprobe hid-multitouch" did nothing.
FYI, my laptop started suffering problems after a trip to New Zealand.  It 
started shutting down randomly every 10 minutes or so.  Dell support had me 
upgrade the BIOS.  The laptop stopped rebooting, but then the touchpad stopped 
being detected.  (I also did "sudo apt update", "sudo apt dist-upgrade" at the 
time, so it wasn't just BIOS updates.)  The BIOS Settings interface doesn't 
recognize the touchpad, so Dell believes there may be a hardware problem and is 
sending a new motherboard and touchpad. 
I'll let you know what happens with the hardware.  I'll also make a bootable 
USB version of Ubuntu so that we can test it with a known image.
On Thursday, March 21, 2019, 2:10:52 AM CDT, Kai-Heng Feng 
 wrote:  
 
 Does "sudo modprobe hid-multitouch" make the touchpad work?

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1821068

Title:
  Touchpad not detected on Dell XPS 13 model 9370

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad is not working.

  I've run "sudo apt update", run "sudo apt dist-upgrade" and rebooted.
  Problem still exists.

  When I run "cat /proc/bus/input/devices", the touchpad is not listed.

  
  I ran "ubuntu-bug linux".

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC0:  mike      1509 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 21 07:26:01 2019
  HibernationDevice: RESUME=UUID=43c674f8-b23d-4a8f-b188-d60f44b8b754
  InstallationDate: Installed on 2019-02-14 (34 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
  TERM=xterm-256color
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=faf516f1-21f1-41b1-8fe6-0454c10f66d0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
  linux-restricted-modules-4.15.0-46-generic N/A
  linux-backports-modules-4.15.0-46-generic  N/A
  linux-firmware                            1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0H6H3J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H6H3J:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

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

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

Title:
  Touchpad not detected on Dell XPS 13 model 9370

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad is not working.

  I've run "sudo apt update", run "sudo apt dist-upgrade" and rebooted.
  Problem still exists.

  When I run "cat /proc/bus/input/devices", the touchpad is not listed.

  
  I ran "ubuntu-bug linux".

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mike   1509 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 21 07:26:01 2019
  HibernationDevice: RESUME=UUID=43c674f8-b23d-4a8f-b188-d60f44b8b754
  InstallationDate: Installed on 2019-02-14 (34 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=faf516f1-21f1-41b1-8fe6-0454c10f66d0 ro quiet splash vt.handoff=1

Re: [Kernel-packages] [Bug 1820371] Re: PCI/internal sound card not detected

2019-03-21 Thread dirk dröge

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

Title:
  PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   no sound in dell inspirion soundcard unknown

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-166-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sat Mar 16 06:55:24 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2019-03-15 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 04XH5N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3551:pvrA00:rvnDellInc.:rn04XH5N:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3551
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=798b4a3a-8afa-4527-ada8-2538fc712f3e
  InstallationDate: Installed on 2019-03-15 (3 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 3551
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-167-generic 
root=UUID=a3fd2b91-69cd-47e9-a167-818ec7ea3d7d ro quiet splash radeon.modeset=0 
nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-167-generic N/A
   linux-backports-modules-3.13.0-167-generic  N/A
   linux-firmware  1.127.24
  StagingDrivers: rts5139
  Tags:  trusty staging
  Uname: Linux 3.13.0-167-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/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 04XH5N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3551:pvrA00:rvnDellInc.:rn04XH5N:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3551
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1819698] Re: linux-gcp: 4.15.0-1029.31 -proposed tracker

** 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 1819695 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 15:06 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copies requested
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029

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

Title:
  linux-gcp: 4.15.0-1029.31 -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:
  Fix Committed
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

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 1819695 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 15:06 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029

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

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

[Kernel-packages] [Bug 1819656] Re: linux-raspi2: 4.4.0-1105.113 -proposed tracker

** 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 15. March 2019 19:31 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 21. March 2019 18:04 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- packages copies requested

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

Title:
  linux-raspi2: 4.4.0-1105.113 -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:
  New
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 Committed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 18:04 UTC
  reason:
promote-to-proposed: Ongoing -- packages copies requested

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

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

[Kernel-packages] [Bug 1819656] Re: linux-raspi2: 4.4.0-1105.113 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-raspi2: 4.4.0-1105.113 -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:
  New
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 Committed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 15. March 2019 19:31 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/1819656/+subscriptions

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

[Kernel-packages] [Bug 1776563]

2019-03-21 Thread eutychios23

So can we close this bug report now or not?

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1776563]

2019-03-21 Thread piroisl33t

Created attachment 281951
attachment-3442-0.html

I'll compile a 5 series kernel and get back sometime this week week.

On Thu, Mar 21, 2019, 10:49  wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=200087
>
> --- Comment #121 from Vladislav Kamenev (mazahakafore...@ya.ru) ---
> I think we should wait till more people try 1.13 bios with 5.0 kernel and
> confirm that laptop is now usable
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1776563]

2019-03-21 Thread nessnesn65

Running a 2200U with Bios 1.13 and Kernel 5.0.3, and I still soft lock
without pci=noacpi in grub before boot. Fan definitely is running at
100% after booting as well. With pci=noacpi, I can boot, but the
touchpad does not work, although I haven't attempted to work on that
problem yet.

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1776563]

2019-03-21 Thread mazahakaforever

I think we should wait till more people try 1.13 bios with 5.0 kernel
and confirm that laptop is now usable

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker

** 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 16:59 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-raspi2: 4.15.0-1033.35 -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:
  New
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 Committed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 16:59 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1821053] Re: [disco] [5.0.0-7.8] can't mount guest cifs share

2019-03-21 Thread Andreas Hasenack

Thanks for the build. Unfortunately, that patch didn't work. I followed
up in the mailing 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/1821053

Title:
  [disco] [5.0.0-7.8] can't mount guest cifs share

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  with a simple smb.conf setup like this:
  [pub]
  path = /pub
  guest ok = yes

  The following mount command fails when the running kernel is 5.0.0-7:
  root@ubuntu:~# dmesg -C
  root@ubuntu:~# mount //localhost/pub /mnt -o guest
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
  root@ubuntu:~# dmesg
  [  178.469307] CIFS: Attempting to mount //localhost/pub
  [  178.469343] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.
  [  178.481741] CIFS VFS: failed to connect to IPC (rc=-13)
  [  178.485272] CIFS VFS: cifs_mount failed w/return code = -13

  samba server logs, in debug 5, show:
  [2019/03/20 17:25:19.365445,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.365524,  0] ../../lib/util/util.c:508(dump_data)
[] A6 62 5F 50 9C D7 31 42   14 34 52 9F AA 49 C8 31   .b_P..1B .4R..I.1
  [2019/03/20 17:25:19.365562,  0] ../../lib/util/util.c:508(dump_data)
[] 31 37 12 A2 D5 D4 59 99   0B 63 C5 21 EB 86 70 74   17Y. .c.!..pt
  [2019/03/20 17:25:19.369055,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.369092,  0] ../../lib/util/util.c:508(dump_data)
[] 23 2C 4F 10 0E 4E 46 2E   8A 5B E3 70 0F B3 D3 FB   #,O..NF. .[.p
  [2019/03/20 17:25:19.369120,  0] ../../lib/util/util.c:508(dump_data)
[] 50 F7 C6 8A 6E BC B2 B7   1C 2F 43 30 90 6A 25 CA   P...n... ./C0.j%.

  
  With kernel 4.19.0-12-generic, the exact same system, the command works:

  root@ubuntu:~# dmesg -C

  root@ubuntu:~# mount //localhost/pub /mnt -o guest

  root@ubuntu:~# dmesg
  [  277.745885] FS-Cache: Loaded
  [  277.768408] FS-Cache: Netfs 'cifs' registered for caching
  [  277.768495] Key type cifs.spnego registered
  [  277.768498] Key type cifs.idmap registered
  [  277.768707] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.

  root@ubuntu:~# mount -t cifs
  //localhost/pub on /mnt type cifs 
(rw,relatime,vers=default,sec=none,cache=strict,uid=0,noforceuid,gid=0,noforcegid,addr=127.0.0.1,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  root@ubuntu:~# uname -r
  4.19.0-12-generic

  
  Just looking at the list of patches queued up for the next upstream kernel 
release, at 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0,
 this one looks promising:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0/cifs-do-not-skip-smb2-message-ids-on-send-failures.patch


  I can easily test a new kernel for you.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 18:04 seq
   crw-rw 1 root audio 116, 33 Mar 20 18:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=PARTUUID=e2b8e290-77c5-437c-a78d-b59424881b58 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UnreportableReason: This report is about a package that is not installed.

[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-raspi2: 4.15.0-1033.35 -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:
  New
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 Committed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 16:59 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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

[Kernel-packages] [Bug 1756700] Re: Ryzen/Raven Ridge USB ports do not work

2019-03-21 Thread Adam Gausmann

I fail to see how it is not the same issue; I am receiving the same
error that the commit (621faf4f) claims to fix.

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

Title:
  Ryzen/Raven Ridge USB ports do not work

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

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

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

[Kernel-packages] [Bug 1819612] Re: linux-raspi2: 4.18.0-1011.13 -proposed tracker

** 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 16:34 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-raspi2: 4.18.0-1011.13 -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:
  New
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 Committed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Cosmic:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 16:34 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1819698] Re: linux-gcp: 4.15.0-1029.31 -proposed tracker

** 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 1819695 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 15:06 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
-   promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
+   promote-to-proposed: Ongoing -- packages copies requested

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

Title:
  linux-gcp: 4.15.0-1029.31 -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:
  Fix Committed
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

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 1819695 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 15:06 UTC
  reason:
promote-to-proposed: Ongoing -- packages copies requested

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

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

[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-raspi2: 4.15.0-1033.35 -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:
  New
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:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 16:59 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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

[Kernel-packages] [Bug 1819704] Re: linux-oracle: 4.15.0-1010.12 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** 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 1819703 (xenial/linux-oracle)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
- phase: Promote to Proposed
- phase-changed: Thursday, 21. March 2019 13:32 UTC
+ phase: Testing
+ phase-changed: Thursday, 21. March 2019 17:00 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages copies requested
+   automated-testing: Ongoing -- testing in progress
+   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-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1819704

Title:
  linux-oracle: 4.15.0-1010.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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 verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Bionic:
  New

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 1819703 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 17:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
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/1819704/+subscriptions

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

[Kernel-packages] [Bug 1819612] Re: linux-raspi2: 4.18.0-1011.13 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-raspi2: 4.18.0-1011.13 -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:
  New
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 Committed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Cosmic:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 16:34 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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

[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker

** 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 15. March 2019 18:38 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 21. March 2019 16:59 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress

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

Title:
  linux-raspi2: 4.15.0-1033.35 -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:
  New
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:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 16:59 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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

[Kernel-packages] [Bug 1819653] Re: linux-aws: 4.4.0-1078.88 -proposed tracker

** 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 13:31 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-beta: Pending -- snap not in b,e,t,a channel
-   snap-release-to-edge: Pending -- snap not in e,d,g,e channel
+   snap-release-to-beta: Pending -- snap not in beta channel
+   snap-release-to-edge: Pending -- snap not in edge 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1819653

Title:
  linux-aws: 4.4.0-1078.88 -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 snap-release-to-beta series:
  Confirmed
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 verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 13:31 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-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1819617] Re: linux-azure: 4.18.0-1014.14~18.04.1 -proposed tracker

** 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
  
  derivatives: bug 1819616 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819618
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 19:39 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 1,8,/,b,e,t,a channel
-   snap-release-to-edge: Pending -- snap not in 1,8,/,e,d,g,e channel
+   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

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

Title:
  linux-azure: 4.18.0-1014.14~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:
  Confirmed
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 verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

  derivatives: bug 1819616 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819618
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 19:39 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/1819617/+subscriptions

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

[Kernel-packages] [Bug 1819694] Re: linux-aws: 4.15.0-1035.37 -proposed tracker

** 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 1819693 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 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 1,8,/,b,e,t,a channel
-   snap-release-to-edge: Pending -- snap not in 1,8,/,e,d,g,e channel
+   snap-release-to-beta: Pending -- snap not in 18/beta channel
+   snap-release-to-edge: Pending -- snap not in 18/edge 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1819694

Title:
  linux-aws: 4.15.0-1035.37 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
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 verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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 1819693 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1819716] Re: linux: 4.15.0-47.50 -proposed tracker

** 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 1819713 (xenial/linux-azure), bug 1819715 (xenial/linux-hwe)
  derivatives: bug 1819691 (linux-raspi2), bug 1819692 (linux-oem), bug 1819694 
(linux-aws), bug 1819698 (linux-gcp), bug 1819699 (linux-kvm), bug 1819701 
(linux-ibm-gt), bug 1819704 (linux-oracle), bug 1819707 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 15. March 2019 23:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in 1,8,/,b,e,t,a channel
-   snap-release-to-edge: Pending -- snap not in 1,8,/,e,d,g,e channel
+   snap-release-to-beta: Pending -- snap not in 18/beta channel
+   snap-release-to-edge: Pending -- snap not in 18/edge 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1819716

Title:
  linux: 4.15.0-47.50 -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:
  In Progress
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:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

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 1819713 (xenial/linux-azure), bug 1819715 (xenial/linux-hwe)
  derivatives: bug 1819691 (linux-raspi2), bug 1819692 (linux-oem), bug 1819694 
(linux-aws), bug 1819698 (linux-gcp), bug 1819699 (linux-kvm), bug 1819701 
(linux-ibm-gt), bug 1819704 (linux-oracle), bug 1819707 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 15. March 2019 23:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1819759] Re: linux: 5.0.0-8.9 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

** Tags removed: block-proposed-disco

** Tags removed: block-proposed

** 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 --
  backports: null
  derivatives: bug 1820878 (linux-aws)
- phase: Testing
- phase-changed: Thursday, 14. March 2019 14:44 UTC
+ phase: Ready for Release
+ phase-changed: Thursday, 21. March 2019 16:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   promote-to-release: Pending -- ready to copy

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

Title:
  linux: 5.0.0-8.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-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-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  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 --
  backports: null
  derivatives: bug 1820878 (linux-aws)
  phase: Ready for Release
  phase-changed: Thursday, 21. March 2019 16:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy

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

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

[Kernel-packages] [Bug 1819713] Re: linux-azure: 4.15.0-1041.45 -proposed tracker

** 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 1819711 (trusty/linux-azure)
  derivatives: bug 1819710 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 20:04 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 b,e,t,a channel
-   snap-release-to-edge: Pending -- snap not in e,d,g,e channel
+   snap-release-to-beta: Pending -- snap not in beta channel
+   snap-release-to-edge: Pending -- snap not in edge 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/1819713

Title:
  linux-azure: 4.15.0-1041.45 -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:
  Confirmed
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 verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

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 1819711 (trusty/linux-azure)
  derivatives: bug 1819710 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 20:04 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
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/1819713/+subscriptions

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

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

2019-03-21 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  "couldn't find IFLA_VF_INFO for VF 1 in netlink response" when trying
  to start libvirt VM with Chelsio VF

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have a Chelsio T62100-LP-CR and I'm trying to create a libvirt VM
  that gets a VF from the NIC.

  The following XML is used :

  


  


  

  When starting the VM, libvirt fails with the following :
  ubuntu@lubbock:~$ sudo virsh start vmaxino
  error: Failed to start domain vmaxino
  error: internal error: couldn't find IFLA_VF_INFO for VF 1 in netlink response

  This is similar to bug 1496942.

  I can create the VM with the VF if I pass it as a  like this :
  

  


  

  More info :
  ubuntu@lubbock:~$ sudo virsh nodedev-dumpxml pci__21_01_4
  
pci__21_01_4
/sys/devices/pci:20/:20:03.1/:21:01.4
pci__20_03_1

  vfio-pci


  0
  33
  1
  4
  T62100-LP-CR Unified Wire Ethernet Controller 
[VF]
  Chelsio Communications Inc
  

  
  

  
  
  


  

  

  pcap of netlink exchange is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 15:42 seq
   crw-rw 1 root audio 116, 33 Mar 21 15:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Mar 21 16:16:41 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Supermicro AS -2023US-TR4
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=7a2aa06e-2ea8-451c-9b77-e0c5cdc445ce ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.1c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H11DSU-iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: AS -2023US-TR4
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1819660] Re: linux: 4.4.0-144.170 -proposed tracker

** 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 1819658 (trusty/linux-aws), bug 1819659 
(trusty/linux-lts-xenial)
  derivatives: bug 1819653 (linux-aws), bug 1819654 (linux-euclid), bug 1819655 
(linux-kvm), bug 1819656 (linux-raspi2), bug 1819657 (linux-snapdragon), bug 
1820326 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 15. March 2019 20:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in b,e,t,a channel
-   snap-release-to-edge: Pending -- snap not in e,d,g,e channel
+   snap-release-to-beta: Pending -- snap not in beta channel
+   snap-release-to-edge: Pending -- snap not in edge 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1819660

Title:
  linux: 4.4.0-144.170 -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:
  In Progress
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:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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 1819658 (trusty/linux-aws), bug 1819659 
(trusty/linux-lts-xenial)
  derivatives: bug 1819653 (linux-aws), bug 1819654 (linux-euclid), bug 1819655 
(linux-kvm), bug 1819656 (linux-raspi2), bug 1819657 (linux-snapdragon), bug 
1820326 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 15. March 2019 20:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel

2019-03-21 Thread James Hanna

Follow up of my previous comment:

Compiled and installed RHEL 8 kernel. RHEL 8 aacraid driver does not
seem to have the bug.

System Rescue CD v5.2.2 (http://www.system-rescue-cd.org) aacraid module
does not encounter the bug.

However Debian did not boot "out of the box" if I installed either of
these kernels and generated initrd. It would always drop to a shell
after failing to mount the root volume, which was an ext4 MBR partition.
The partition mounts fine after booting System Rescue CD, and does not
suffer from the aacraid module bug.

Speculation: failure to mount at boot with RHEL 8 or System Rescue CD is
a Debian-specific init issue. Did not perform further troubleshooting
using the RAID card.

Pulled the CERC 1.5/6 ch RAID card and attached directly to the SATA
ports on the motherboard, to continue the project.

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

Title:
System won't boot after upgrade to 16.04 with 4.4.0 kernel

Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Invalid
Status in linux source package in Yakkety:
Won't Fix

Bug description:
I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in
it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to
16.04.1 the system won't boot. It can't find the root filesystem. I
see errors about host adapter dead on the screen many times. This is
with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel
3.13.0-105 the system boots just fine.

I have mptbios 5.06.04.
The CERC card says bios version 4.1-0 [Build 7403]

When booting into the ercovery kernel I'm getting error messages about host
adapter dead.
Eventually I get a message:
"aacraid: aac_fib_send: first asynchronous command timed out.
Usually a result of a PCI interrupt routing problem
update moher board BIOS or consider utilizing one of
the SAFE mode kernel options (acpi, apic etc)"

Using kernel parameter "intel_iommu=on" doesn't help. This was suggested on a
post that I saw about these errors.

Booting with "noapic" didn't help.
Booting with "noapic noacpi" didn't help.

I've also tried the dkms modules from Adaptec and that doesn't seem to help
either.

I can't figure out how to upgrade the firmware or BIOS on the system from
Ubuntu either.

This may be related to this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551?comments=all
---
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77
InstallationDate: Installed on 2014-02-24 (1039 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
IwConfig:
eth1 no wireless extensions.

lono wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Computer Corporation PowerEdge 1800
Package: linux (not installed)
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic
root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth
ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.13.0-105-generic N/A
linux-backports-modules-3.13.0-105-generic N/A
linux-firmware 1.157.6
RfKill:

Tags: xenial
Uname: Linux 3.13.0-105-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-12-25 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/01/2004
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A00
dmi.board.name: 0X7500
dmi.board.vendor: Dell Computer Corporation
dmi.board.version: A00
dmi.chassis.type: 17
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias:
dmi:bvnDellComputerCorporation:bvrA00:bd09/01/2004:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0X7500:rvrA00:cvnDellComputerCorporation:ct17:cvr:
dmi.product.name: PowerEdge 1800
dmi.sys.vendor: Dell Computer Corporation

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

--
Mailing

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-03-21 Thread Christian Ehrhardt 

Ok, thanks Jason.
That is great info, but about as much as we had so far :-/

Can you set your deployment up in a way that if that happens again you
can collect these binaries?

If it right now still triggers if you (re)deploy a 2G guest use the
chance to finally give us the bits that we will need to reach the next
stage of debugging.

Lesson learned from before on this bug, it might already be gone by
tomorrow, so I hope you have time and chance to get those
xml+image+kernel+initrd.

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1821205] [NEW] "couldn't find IFLA_VF_INFO for VF 1 in netlink response" when trying to start libvirt VM with Chelsio VF

2019-03-21 Thread Junien Fridrick

Public bug reported:

Hi,

I have a Chelsio T62100-LP-CR and I'm trying to create a libvirt VM that
gets a VF from the NIC.

The following XML is used :


  
  

  
  


When starting the VM, libvirt fails with the following :
ubuntu@lubbock:~$ sudo virsh start vmaxino
error: Failed to start domain vmaxino
error: internal error: couldn't find IFLA_VF_INFO for VF 1 in netlink response

This is similar to bug 1496942.

I can create the VM with the VF if I pass it as a  like this :

  

  
  


More info :
ubuntu@lubbock:~$ sudo virsh nodedev-dumpxml pci__21_01_4

  pci__21_01_4
  /sys/devices/pci:20/:20:03.1/:21:01.4
  pci__20_03_1
  
vfio-pci
  
  
0
33
1
4
T62100-LP-CR Unified Wire Ethernet Controller 
[VF]
Chelsio Communications Inc

  


  



  
  

  


pcap of netlink exchange is attached.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-46-generic 4.15.0-46.49
ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 21 15:42 seq
 crw-rw 1 root audio 116, 33 Mar 21 15:42 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Mar 21 16:16:41 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Supermicro AS -2023US-TR4
PciMultimedia:
 
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=7a2aa06e-2ea8-451c-9b77-e0c5cdc445ce ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-46-generic N/A
 linux-backports-modules-4.15.0-46-generic  N/A
 linux-firmware 1.173.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/04/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.1c
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H11DSU-iN
dmi.board.vendor: Supermicro
dmi.board.version: 1.02A
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 1
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: AS -2023US-TR4
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

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


** Tags: amd64 apport-bug bionic

** Attachment added: "pcap of netlink exchange"
   https://bugs.launchpad.net/bugs/1821205/+attachment/5248235/+files/pcap.bz2

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

Title:
  "couldn't find IFLA_VF_INFO for VF 1 in netlink response" when trying
  to start libvirt VM with Chelsio VF

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  I have a Chelsio T62100-LP-CR and I'm trying to create a libvirt VM
  that gets a VF from the NIC.

  The following XML is used :

  


  


  

  When starting the VM, libvirt fails with the following :
  ubuntu@lubbock:~$ sudo virsh start vmaxino
  error: Failed to start domain vmaxino
  error: internal error: couldn't find IFLA_VF_INFO for VF 1 in netlink response

  This is similar to bug 1496942.

  I can create the VM with the VF if I pass it as a  like this :
  

  


  

  More info :
  ubuntu@lubbock:~$ sudo virsh nodedev-dumpxml pci__21_01_4
  
pci__21_01_4
/sys/devices/pci:20/:20:03.1/:21:01.4
pci__20_03_1

  vfio-pci


  0
  33
  1
  4
  T62100-LP-CR Unified Wire Ethernet Controller 
[VF]
  Chelsio Communications Inc
  

  
  

  
  
  


  

  

  pcap of netlink exchange is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 15:42

[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386