date:20190607

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

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

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

Title:
  [nouveau] Scrolling screen flicker, especially on default Ubuntu lock
  screen

Status in linux package in Ubuntu:
  Expired

Bug description:
  My screen is experiencing a weird "scrolling" flicker, especially
  while displaying blue, indigo, and violet hues/colors, such as on the
  default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker
  scrolls up and down, with the brightest part of the flicker being
  towards the top, with a gradient that fades back to the original color
  near the bottom.

  Problem occurs on any one monitor on any one video output protocol
  (DVI-D, HDMI, and VGA).

  
  I will upload an illustration or render as soon as possible for better 
explanation.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 10:39:50 2019
  DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828]
  InstallationDate: Installed on 2018-08-17 (202 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: BIOSTAR Group A880G+
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (139 days ago)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A880G+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A880G+
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.sys.vendor: BIOSTAR Group
  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/1819023/+subscriptions

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

[Kernel-packages] [Bug 1815691] Re: disk not detected on an Intel NUC7i5BNHXF

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

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

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

Title:
  disk not detected on an Intel NUC7i5BNHXF

Status in linux package in Ubuntu:
  Expired
Status in ubiquity package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Expired
Status in ubiquity source package in Disco:
  Invalid

Bug description:
  I attempted to install Ubuntu from multiple ISOs, made with dd to a
  USB disk, onto an Intel NUC7i5BNHXF and none of them were able to
  detect the disk on the system. I was able to successfully install
  Ubuntu 16.04! using the image identified linked to from here:

  https://www.ubuntu.com/download/iot/intel-nuc-desktop

  Attached you will find the syslog files from the the different live
  environments from which I was unable to install Ubuntu.

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

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

[Kernel-packages] [Bug 1823261] Re: PCI/internal sound card not detected

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

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

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

Title:
  PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Expired

Bug description:
  It was ok previously but it stopped some days back. my tracking results no 
sound card found.
  may be a driver problem or something.
  no hardware changes have been made since i started using the device.
  lspci -v says there is intel corp. broadwell-U audio controller is there.
  please help or advise.
  i am using ubuntu 14.04 lts.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-52-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: Fri Apr  5 02:13:22 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-19 (16 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: 10/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0RG2FR
  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.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn0RG2FR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1815691] Re: disk not detected on an Intel NUC7i5BNHXF

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

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

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

Title:
  disk not detected on an Intel NUC7i5BNHXF

Status in linux package in Ubuntu:
  Expired
Status in ubiquity package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Expired
Status in ubiquity source package in Disco:
  Invalid

Bug description:
  I attempted to install Ubuntu from multiple ISOs, made with dd to a
  USB disk, onto an Intel NUC7i5BNHXF and none of them were able to
  detect the disk on the system. I was able to successfully install
  Ubuntu 16.04! using the image identified linked to from here:

  https://www.ubuntu.com/download/iot/intel-nuc-desktop

  Attached you will find the syslog files from the the different live
  environments from which I was unable to install Ubuntu.

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

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

[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade

[Expired for linux-hwe (Ubuntu Bionic) because there has been no
activity for 60 days.]

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

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

Title:
  4.18.0-17 crashes on i915 driver with multiple monitors since upgrade

Status in linux package in Ubuntu:
  Expired
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe source package in Bionic:
  Expired
Status in linux source package in Cosmic:
  Expired
Status in linux-hwe source package in Cosmic:
  Invalid

Bug description:
  On 2019-04-03 I updated to the latest linux-image-generic-
  hwe-18.04:amd64 and then I got on a trip where things worked fine at
  first. Back home I realized that the new version 4.18.0-17-generic has
  issues initializing gnome with multiple monitors.

  Steps to reproduce:
  - boot into 4.18.0-17-generic (to be specific Ubuntu 
4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log)
  - start Ubuntu Desktop (gdm works fine at first)
  - Log in

  I have found that this only triggers:
  - with multiple monitors attached ( I have laptop fullHD + 2* external 
fullHD; with just the laptop screen it works)
  - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine 
(=>upgrade-regression?)

  On init of the gnome shell the system crashes with:
  kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A 
FIFO underrun
  [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, 
found 296999)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 
d293602a, found 7548bc60)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 
(expected 0x0003, found 0x0001)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in 
base.adjusted_mode.crtc_clock (expected 148500, found 296999)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, 
found 54)

  Keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to
  consoles anymore. I can only hard reset via 5sec power button.

  I'll attach a full journal of the system and run an apport run on it.
  Let me know if I can help any further.

  So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16
  right away.

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

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

[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade

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

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

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

Title:
  4.18.0-17 crashes on i915 driver with multiple monitors since upgrade

Status in linux package in Ubuntu:
  Expired
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe source package in Bionic:
  Expired
Status in linux source package in Cosmic:
  Expired
Status in linux-hwe source package in Cosmic:
  Invalid

Bug description:
  On 2019-04-03 I updated to the latest linux-image-generic-
  hwe-18.04:amd64 and then I got on a trip where things worked fine at
  first. Back home I realized that the new version 4.18.0-17-generic has
  issues initializing gnome with multiple monitors.

  Steps to reproduce:
  - boot into 4.18.0-17-generic (to be specific Ubuntu 
4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log)
  - start Ubuntu Desktop (gdm works fine at first)
  - Log in

  I have found that this only triggers:
  - with multiple monitors attached ( I have laptop fullHD + 2* external 
fullHD; with just the laptop screen it works)
  - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine 
(=>upgrade-regression?)

  On init of the gnome shell the system crashes with:
  kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A 
FIFO underrun
  [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, 
found 296999)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 
d293602a, found 7548bc60)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 
(expected 0x0003, found 0x0001)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in 
base.adjusted_mode.crtc_clock (expected 148500, found 296999)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, 
found 54)

  Keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to
  consoles anymore. I can only hard reset via 5sec power button.

  I'll attach a full journal of the system and run an apport run on it.
  Let me know if I can help any further.

  So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16
  right away.

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

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

[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade

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

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

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

Title:
  4.18.0-17 crashes on i915 driver with multiple monitors since upgrade

Status in linux package in Ubuntu:
  Expired
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe source package in Bionic:
  Expired
Status in linux source package in Cosmic:
  Expired
Status in linux-hwe source package in Cosmic:
  Invalid

Bug description:
  On 2019-04-03 I updated to the latest linux-image-generic-
  hwe-18.04:amd64 and then I got on a trip where things worked fine at
  first. Back home I realized that the new version 4.18.0-17-generic has
  issues initializing gnome with multiple monitors.

  Steps to reproduce:
  - boot into 4.18.0-17-generic (to be specific Ubuntu 
4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log)
  - start Ubuntu Desktop (gdm works fine at first)
  - Log in

  I have found that this only triggers:
  - with multiple monitors attached ( I have laptop fullHD + 2* external 
fullHD; with just the laptop screen it works)
  - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine 
(=>upgrade-regression?)

  On init of the gnome shell the system crashes with:
  kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A 
FIFO underrun
  [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, 
found 296999)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 
d293602a, found 7548bc60)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 
(expected 0x0003, found 0x0001)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in 
base.adjusted_mode.crtc_clock (expected 148500, found 296999)
  [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, 
found 54)

  Keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to
  consoles anymore. I can only hard reset via 5sec power button.

  I'll attach a full journal of the system and run an apport run on it.
  Let me know if I can help any further.

  So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16
  right away.

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

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

[Kernel-packages] [Bug 1823534] Re: bugs, but i don't know. Experienced a lot, so

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

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

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

Title:
  bugs, but i don't know. Experienced a lot, so

Status in linux package in Ubuntu:
  Expired

Bug description:
   am a newbie. Shouldn't have tested 18.10. Instead should have gone
  for LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-17-generic 4.18.0-17.18
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pranav 2979 F pulseaudio
   /dev/snd/controlC0:  pranav 2979 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 19:19:30 2019
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=09e25397-4a2c-4fb0-a605-a7013eecb59c
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  MachineType: Dell Inc. Inspiron 5548
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=aad43495-2006-41af-bcb1-f91673ac405e ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-17-generic N/A
   linux-backports-modules-4.18.0-17-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  StagingDrivers: r8188eu
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   19:19:36.717: The udisks-daemon is running (name-owner :1.11).
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 05/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0FFJC4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/15/2018:svnDellInc.:pnInspiron5548:pvrA09:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Inspiron 5548
  dmi.product.sku: 0641
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1823725] Re: packet: reset network header if packet shorter than ll reserved space

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

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

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

Title:
  packet: reset network header if packet shorter than ll reserved space

Status in linux package in Ubuntu:
  Expired

Bug description:
  After backport of linux upstream commit 9ed988cd5915 ("packet:
  validate variable length ll headers")
  (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
  missing :

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ed988cd5915

  9ed988cd5915 ("packet: validate variable length ll headers")

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

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

[Kernel-packages] [Bug 1831873] Re: test_095_kernel_symbols_missing_proc_net_tcp from ubuntu_qrt_kernel_security failed on B/C KVM

2019-06-07 Thread Steve Beattie

Hi,

This was an interesting little bug to invstigate. Here's what was
happening. The test checks to see that when kptr_restrict == 1, the sock
addresses reported in /proc/net/tcp are all zero for non-root users. It
then sets kptr_restrict == 0 and attempts to verify that real pointers
are reported to root and non-root users. However, recently the kernel
started to hash these pointers instead, returning the hash value in it's
place, *and* (the source of this bug) if insufficient entropy had been
collected by the kernel up to this point, making the hash "weak", the
values "(ptrval)" and "(ptrval)" would be returned instead. The
QRT script assumed that whatever it read would at least be a hex number
of some kind captured in a string and attempt to convert it to an int.

The insufficient entropy bit is why you would only see this failure on
the first run of the test.

This has been addressed in qrt commit https://git.launchpad.net/qa-
regression-testing/commit/?id=46f217b3f9aa0e53bb18bd2049f934199870ed1c .

Reference on the source of the values and insufficient entropy:
https://www.kernel.org/doc/Documentation/core-api/printk-formats.rst
(section on Plain Pointers)

** Changed in: qa-regression-testing
   Status: New => Fix Released

** Changed in: linux-kvm (Ubuntu)
   Status: New => Invalid

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

Title:
  test_095_kernel_symbols_missing_proc_net_tcp from
  ubuntu_qrt_kernel_security failed on B/C KVM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  Invalid

Bug description:
  This issue can only be reproduced on the first run. The second run it
  will pass.

ERROR: test_095_kernel_symbols_missing_proc_net_tcp 
(__main__.KernelSecurityTest)
kernel addresses in /proc/net/tcp are zeroed out
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1392, in 
test_095_kernel_symbols_missing_proc_net_tcp
self._check_pK_files(self. _095_kernel_symbols_missing_proc_net_tcp)
  File "./test-kernel-security.py", line 1235, in _check_pK_files
test_function(expected_unrestricted)
  File "./test-kernel-security.py", line 1350, in 
_095_kernel_symbols_missing_proc_net_tcp
expected)
  File "./test-kernel-security.py", line 1153, in _read_twice
self.assertFalse(0 == int(address, 16), "%s: root saw %s - 
contents:\n%s" % (filename, address, root))
ValueError: invalid literal for int() with base 16: '(ptrval)'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1013-kvm 4.18.0-1013.13
  ProcVersionSignature: User Name 4.18.0-1013.13-kvm 4.18.20
  Uname: Linux 4.18.0-1013-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Thu Jun  6 09:25:10 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1831873/+subscriptions

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

[Kernel-packages] [Bug 1792189] Re: linux-firmware does not depend on initramfs-tools

I.e. instead of the current

$ cat debian/linux-firmware.postinst

#!/bin/sh

set -e

if [ -x /usr/sbin/update-initramfs ]; then
/usr/sbin/update-initramfs -u -k all
fi

#DEBHELPER#

It should do instead

$ cat  cat debian/linux-firmware.triggers 
activate-noawait update-initramfs


** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Won't Fix

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

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

Title:
  linux-firmware does not depend on initramfs-tools

Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  In bug #1646197 the linux-firmware.postinst was added to call update-
  initramfs (provided by initramfs-tools.  If the initramfs-tools
  package is not installed the installation of linux-firmware will fail.

  Recreate:
  sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs*
  sudo apt-get install --assume-yes linux-generic

  Result:
  Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ...
  Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ...
  Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ...
  Setting up initramfs-tools-bin (0.130ubuntu3.3) ...
  Setting up linux-firmware (1.173.1) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm
  /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf
  update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2.
  dpkg: error processing package linux-firmware (--configure):
   installed linux-firmware package post-installation script subprocess 
returned error exit status 2
  ...
  Errors were encountered while processing:
   linux-firmware
   linux-image-generic
   linux-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Impact:
  Builds of minimized images start with an image that has the linux-kvm kernel 
but lack initramfs-tools.  Derivative builds that require a different kernel, 
linux-generic for example, will purge the existing kernel and install the 
correct kernel which could pull in linux-firmware and initramfs-tools.  In that 
case the builds fail unless initramfs-tools is installed prior to kernel 
installation as a workaround for this missing package dependency.

  This has been recreated on cosmic and bionic, a fix is desired on
  each.  (I was unable to recreate on Xenial but that package lacks the
  dependency as well).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792189/+subscriptions

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

[Kernel-packages] [Bug 1832048] [NEW] hinic: fix oops due to race in set_rx_mode

2019-06-07 Thread dann frazier

Public bug reported:

[Impact]
It is possible for the hinic driver to oops after the module is removed and 
reinserted.

[Test Case]
while :; do sudo modprobe -r hinic; modprobe hinic; done

[Fix]
>From linux-next:
  66350023d5756 hinic: fix a bug in set rx mode

[Regression Risk]
Patch is local to the hinic driver.

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

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

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

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

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
 Assignee: dann frazier (dannf)
   Status: In Progress

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

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

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

Title:
  hinic: fix oops due to race in set_rx_mode

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  [Impact]
  It is possible for the hinic driver to oops after the module is removed and 
reinserted.

  [Test Case]
  while :; do sudo modprobe -r hinic; modprobe hinic; done

  [Fix]
  From linux-next:
66350023d5756 hinic: fix a bug in set rx mode

  [Regression Risk]
  Patch is local to the hinic driver.

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

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

[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot

2019-06-07 Thread Seth Forshee

** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  We enabled CONFIG_DMA_CMA to fix bug 1803206, but that led to a regression
  on other arm64 systems that began spewing these messages on boot - sometimes 
> 10K of them:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  In a previous SRU (bug 1828092), we worked around this by just rate-
  limiting these messages. These are "err" priority messages though, so
  even a lower number of them is still disconcerting.

  [Fix]
  1) Bump up the amount of available CMA on arm64 to 32M (same as upstream 
defconfig)
  2) A patch-set from linux-next that redirects dma-direct contiguous 
allocations to alloc_pages() for single page allocations (single pages are by 
definition contiguous), avoiding CMA usage/fragmentation.

  [Test Case]
  dmesg | grep "cma_alloc: alloc failed"
  Some system configs will still have some of these errors even after this fix 
- but this should reduce them significantly. Per-driver optimizations can be 
used to make further improvements, but we should track those in other bugs.

  [Regression Risk]
  Tested on a HiSilicon D06 and HP m400 (Hi1620 & X-Gene arm64).
  Regression tested on:
   - Raspberry Pi 3B (see Comment #22)
   - Power9 system (ppc64el)
   - z/VM instance (s390x)
   - Intel Centerton system (amd64)

  Test builds are staged at http://ppa.launchpad.net/~dannf/ubuntu/cma

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

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

[Kernel-packages] [Bug 668148] Re: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug

2019-06-07 Thread Marco Sulla

Hello?

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

Title:
  pci using host bridge windows from ACPI; if necessary, use "pci=nocrs"
  and report a bug

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using a toshiba Qosmio x505-887, Running Ubuntu 10.10 up to date
  and see this message in dmesg

  [1.762496] PCI: Using host bridge windows from ACPI; if necessary,
  use "pci=nocrs" and report a bug

  I am not sure if this is related to a package or not. My system BIOS
  is as updated as Toshiba gets.

  :~$ lsb_release -rd
  Description:  Ubuntu 10.10
  Release:  10.10
  Linux FEDUAV 2.6.35-23-generic #36-Ubuntu SMP Tue Oct 26 17:13:06 UTC 2010 
x86_64 GNU/Linux
  was there on previous kernel as well. 

  I have yet to try this as a boot option on my system, I have only been
  having that I know of so far issues with my wifi but thats a realtek
  driver issue. I have not noticed or seen any other problems as of yet.
  With that I am not sure as to what other info I should post yet that
  would be of help. Please let me know what else I should post to be
  able to help with this issue or any logs or what not. Thanks for any
  info and or help with this.

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

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

[Kernel-packages] [Bug 1827916] Re: Enable eBPF JIT in the linux-azure kernels

2019-06-07 Thread Marcelo Cerri

https://lists.ubuntu.com/archives/kernel-team/2019-June/101209.html
https://lists.ubuntu.com/archives/kernel-team/2019-June/101210.html
https://lists.ubuntu.com/archives/kernel-team/2019-June/101211.html
https://lists.ubuntu.com/archives/kernel-team/2019-June/101212.html

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

Title:
  Enable eBPF JIT in the linux-azure kernels

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

Bug description:
  eBPF is available as of kernel version 4.15, which is used on AKS nodes.
  Enabling JIT eBPF (built-in kernel feature) will speed-up execution of eBPF 
aware tools.
  eBPF JIT is controlled by the file /proc/sys/net/core/bpf_jit_enable.
  More details for eBPF JIT - 
https://www.kernel.org/doc/Documentation/sysctl/net.txt
   
  The file /proc/sys/net/core/bpf_jit_enable is not present on AKS nodes.  

  Also, to support eBPF in AKS, we are requesting to switch the mlx* and
  ib* drivers to loadable modules instead of static.

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

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

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

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

Title:
  Network issue, speeds throttled, wired fails.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have been having an issue with my networking on Ubuntu, when I am on
  wireless, after some time, my speeds get throttled down to slow
  speeds, I have a 50 Mbps connection and have did a speed test and got
  8 Mbps. https://www.speedtest.net/result/8314420338.png According to
  this link. I was going to try a test directly connected to my modem
  and Ubuntu wouldn't even connect to the Internet, it kept failing, I
  got in contact with my ISP and they say that they are one of the few
  companies that don't throttle and that my signals are healthy. My WiFi
  will also drop out completely and I will get the no active connection
  error notification when my router is completely fine. I will attach
  the logs to this report. I am using Ubuntu 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tsynk  1793 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  7 13:31:20 2019
  HibernationDevice: RESUME=UUID=d95a55cf-d759-409b-959c-b084a127520b
  InstallationDate: Installed on 2018-06-09 (363 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: HP HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=f8e13e40-d565-4652-ae79-e143635c868e ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-26 (41 days ago)
  dmi.bios.date: 06/09/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8175
  dmi.board.vendor: HP
  dmi.board.version: 37.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd06/09/2017:svnHP:pnHP15NotebookPC:pvrType1ProductConfigId:rvnHP:rn8175:rvr37.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP 15 Notebook PC
  dmi.product.sku: L0T33UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1832040] [NEW] Network issue, speeds throttled, wired fails.

2019-06-07 Thread Tsynk "Z" ZVoin

Public bug reported:

I have been having an issue with my networking on Ubuntu, when I am on
wireless, after some time, my speeds get throttled down to slow speeds,
I have a 50 Mbps connection and have did a speed test and got 8 Mbps.
https://www.speedtest.net/result/8314420338.png According to this link.
I was going to try a test directly connected to my modem and Ubuntu
wouldn't even connect to the Internet, it kept failing, I got in contact
with my ISP and they say that they are one of the few companies that
don't throttle and that my signals are healthy. My WiFi will also drop
out completely and I will get the no active connection error
notification when my router is completely fine. I will attach the logs
to this report. I am using Ubuntu 19.04.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-16-generic 5.0.0-16.17
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tsynk  1793 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  7 13:31:20 2019
HibernationDevice: RESUME=UUID=d95a55cf-d759-409b-959c-b084a127520b
InstallationDate: Installed on 2018-06-09 (363 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: HP HP 15 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=f8e13e40-d565-4652-ae79-e143635c868e ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-16-generic N/A
 linux-backports-modules-5.0.0-16-generic  N/A
 linux-firmware1.178.1
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-04-26 (41 days ago)
dmi.bios.date: 06/09/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.36
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8175
dmi.board.vendor: HP
dmi.board.version: 37.13
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd06/09/2017:svnHP:pnHP15NotebookPC:pvrType1ProductConfigId:rvnHP:rn8175:rvr37.13:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP 15 Notebook PC
dmi.product.sku: L0T33UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug disco

** Attachment added: "Logs with the wired issues and WiFi."
   
https://bugs.launchpad.net/bugs/1832040/+attachment/5269401/+files/Combined%20logs

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

Title:
  Network issue, speeds throttled, wired fails.

Status in linux package in Ubuntu:
  New

Bug description:
  I have been having an issue with my networking on Ubuntu, when I am on
  wireless, after some time, my speeds get throttled down to slow
  speeds, I have a 50 Mbps connection and have did a speed test and got
  8 Mbps. https://www.speedtest.net/result/8314420338.png According to
  this link. I was going to try a test directly connected to my modem
  and Ubuntu wouldn't even connect to the Internet, it kept failing, I
  got in contact with my ISP and they say that they are one of the few
  companies that don't throttle and that my signals are healthy. My WiFi
  will also drop out completely and I will get the no active connection
  error notification when my router is completely fine. I will attach
  the logs to this report. I am using Ubuntu 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tsynk  1793 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  7 13:31:20 2019
  HibernationDevice: RESUME=UUID=d95a55cf-d759-409b-959c-b084a127520b
  InstallationDate: Installed on 2018-06-09 (363 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: HP HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=f8e13e40-d565-4652-ae79-e143635c868e ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-26 (41 days ago)
  dmi.bios.date: 06/09/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8175
  dmi.board.vendor: HP

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

2019-06-07 Thread bugproxy

--- Comment From youh...@us.ibm.com 2019-06-07 14:04 EDT---
I don't know if this is a BMC issue either.  With your latest note,  I still do 
not understand the problem on Boston.  Whether this is a HWCLOCK setting issue 
or HWCLOCK setting is working but have a long delay...  Can you help clarify 
that?

Here is how you create a problem tracking for Boston.

1) You will need github ID
2) If you do not have access, send your github ID to Maurice Zipse to request 
for access.  If you do not have github ID, get one.
3) Link to github issue:  https://github.com/open-power/boston-openpower/issues/
4)  Click on "New issue" top right to create a new issue for P9 Boston.  
Provide details of the problem so that we can understand your issue.

Let me know if you have any other question.

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

Title:
  hwclock test failed on Power9 due to 0.x sec differences / time out
  waiting for time change

Status in ubuntu-kernel-tests:
  New
Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The hwclock test will fail on the Power9 system "baltar" due to a
  <0.02 second difference.

  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
    File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in 
run_once
  raise error.TestFail("Failed to set hwclock back to Warthog's birthday. 
Output of hwclock is '%s'" % date)
  TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock 
is '2004-10-20 04:09:59.582146+'

  Didn't see this on Power8 boxes

  Sometimes it will fail because "time out waiting for time change" on the same 
node:
  $ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
  hwclock: Timed out waiting for time change.

  Workaround for these is to add "sleep 1".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 03:45 seq
   crw-rw 1 root audio 116, 33 Nov  8 03:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: ppc64el
  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:
  CurrentDmesg:

  Date: Thu Nov  8 06:03:54 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3544 00:17:582 0 EOF
   2: POSIX  ADVISORY  WRITE 1798 00:17:338 0 EOF
   3: POSIX  ADVISORY  WRITE 3603 00:17:576 0 EOF
   4: FLOCK  ADVISORY  WRITE 3535 00:17:564 0 EOF
   5: FLOCK  ADVISORY  WRITE 4081 00:17:481 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 40
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 159)
   max: 2.862 GHz (cpu 1)
   avg: 2.862 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No

[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-06-07 Thread Michael

Thanks Tyler, greatly appreciated
nopti workaround all good on Asus W1N Pentium M banias also.

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

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE: 
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running. 
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs 
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  
  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try the older kernel.

  
  More Info on what I've already tried for troubleshooting (on the HP6710b) is 
outlined in https://answers.launchpad.net/ubuntu/+question/680486

  Happy to provide more info if needed, but I'm just an end user user
  and new to Linux, so will be on a learning curve at this end.  (and
  apologies in advance if this a user problem, and not an actual bug).
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1681 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May  6 21:16:34 2019
  MachineType: Hewlett-Packard HP Compaq 6710b
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.13
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: SGH8080272
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1034 F pulseaudio
   /dev/snd/controlC0:  michael1034 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  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 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. W1N
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=5e6f46b1-73a8-4779-bc20-414a46286723 ro forcepae quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A

[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption

2019-06-07 Thread Jeff Lane

SRU Request submitted

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

Title:
  amd_iommu possible data corruption

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]
  If a device has an exclusion range specified in the IVRS
  table, this region needs to be reserved in the iova-domain
  of that device. This hasn't happened until now and can cause
  data corruption on data transfered with these devices.

  The exlcusion range limit register needs to contain the
  base-address of the last page that is part of the range, as
  bits 0-11 of this register are treated as 0xfff by the
  hardware for comparisons.

  So correctly set the exclusion range in the hardware to the
  last page which is _in_ the range.

  [Fixes]
  Cherry pick the following from Mainline
  fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range 
in iova-domain
  3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range 
correctly

  These can be picked from my branches here:
  Bionic:
  https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic 
1823037-amd_iommu-cherrypick
  b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range 
in iova-domain
  ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range 
correctly

  Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic 
1823037-amd_iommu-cherrypick
  0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range 
in iova-domain
  fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range 
correctly

  Disco:
  https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco 
1823037-amd_iommu-cherrypick
  6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range 
correctly

  Note Disco only required f1cd47fe12 as the first patch was already
  picked in LP: #1830934

  Not necessary for Eoan as these are already upstream in 5.2-rc1

  [Regression Risk]
  Low,this adds memory protection to the driver and has already been applied 
upstream and tested by Dell for 24 hours with no failures noted.

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

-- 
Mailing list: https://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 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-06-07 Thread Tyler Hicks

On 2019-06-07 17:32:04, Thomas Lenarz wrote:
> Boot switch "nopti" solves the problem as well on Asus X51R (Laptop).
> However, I think it is not a final solution, cause its Processor Celeron M 
> 520 is on the vulnerability list.

It most definitely isn't a final solution. However, the i386 PTI changes
are what's causing you problems and it is a temporary workaround to
disable it in the meantime until we can identify the proper fix. Once
the bug is fixed and you install the updated kernel with the bug fix,
you should remember to remove the 'nopti' boot option.

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

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE: 
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running. 
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs 
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  
  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try the older kernel.

  
  More Info on what I've already tried for troubleshooting (on the HP6710b) is 
outlined in https://answers.launchpad.net/ubuntu/+question/680486

  Happy to provide more info if needed, but I'm just an end user user
  and new to Linux, so will be on a learning curve at this end.  (and
  apologies in advance if this a user problem, and not an actual bug).
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1681 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May  6 21:16:34 2019
  MachineType: Hewlett-Packard HP Compaq 6710b
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.13
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: SGH8080272
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1034 F pulseaudio
   /dev/snd/controlC0:  michael1034 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  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 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. W1N
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:

[Kernel-packages] [Bug 1811723] Re: Samba client freeze during write when using higher than vers=1.0

2019-06-07 Thread zorlax

I still have the bug in 4.15.0-51-generic #55-Ubuntu SMP.

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

Title:
  Samba client freeze during write when using higher than vers=1.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
   My issue is that whenever I try to write new files (copy or move) to my file 
server something in the samba client freezes and I can't do anything samba 
until the system is rebooted. 

  To get write access I mount with uid ie "sudo mount //server/share
  /mountpoint -o user=write,uid=1000". Using this command the server and
  client negotiates smb protocol version 3.02.

  When this happens the server is still happily serving files to other machines.
  If I just read files everything works fine.
  If I connect from a windows client there is no issue.
  If I add "vers=1.0" everything works but transfers are really slow. 
Specifying version 3 produces a fail.
  Trying the same operation (different hw) with Mint 18 Mate produces the same 
fault.
  Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live 
everything works as expected.

  Both client and server are running fully updated, as of posting,
  bionic.

  Using 'dmesg -w' too see what's going on I can see that there is a
  general protection fault somehow related to cifsd. I am however unable
  to tell if it is relevant to my issue, from kern.log:

  Jan  9 21:03:49 ubnu kernel: [  410.357213] general protection fault:  
[#1] SMP PTI
  Jan  9 21:03:49 ubnu kernel: [  410.357224] Modules linked in: cmac arc4 md4 
nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp 
snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl 
btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm 
snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul 
crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth 
ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 
crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms 
snd_seq_device
  Jan  9 21:03:49 ubnu kernel: [  410.357357]  wmi_bmof snd_timer memstick 
intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal 
acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e 
i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect 
sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video
  Jan  9 21:03:49 ubnu kernel: [  410.357447] CPU: 2 PID: 1822 Comm: cifsd 
Tainted: G   OE4.15.0-43-generic #46-Ubuntu
  Jan  9 21:03:49 ubnu kernel: [  410.357453] Hardware name:  /NUC7i3BNB, BIOS 
BNKBL357.86A.0069.2018.0920.1250 09/20/2018
  Jan  9 21:03:49 ubnu kernel: [  410.357468] RIP: 
0010:prefetch_freepointer+0x15/0x30
  Jan  9 21:03:49 ubnu kernel: [  410.357474] RSP: 0018:b16201ae3da0 
EFLAGS: 00010282
  Jan  9 21:03:49 ubnu kernel: [  410.357482] RAX:  RBX: 
e90527c744fff71a RCX: 3ea9
  Jan  9 21:03:49 ubnu kernel: [  410.357488] RDX: 3ea8 RSI: 
e90527c744fff71a RDI: 9d7079255080
  Jan  9 21:03:49 ubnu kernel: [  410.357494] RBP: b16201ae3da0 R08: 
9d707ed2b650 R09: b16201ae3db0
  Jan  9 21:03:49 ubnu kernel: [  410.357499] R10: b16201ae3de8 R11: 
 R12: 01011200
  Jan  9 21:03:49 ubnu kernel: [  410.357505] R13: 9d7079255080 R14: 
9d7016478c40 R15: 9d7079255080
  Jan  9 21:03:49 ubnu kernel: [  410.357512] FS:  () 
GS:9d707ed0() knlGS:
  Jan  9 21:03:49 ubnu kernel: [  410.357519] CS:  0010 DS:  ES:  CR0: 
80050033
  Jan  9 21:03:49 ubnu kernel: [  410.357525] CR2: 7f0a2802d028 CR3: 
3760a006 CR4: 003606e0
  Jan  9 21:03:49 ubnu kernel: [  410.357530] Call Trace:
  Jan  9 21:03:49 ubnu kernel: [  410.357545]  kmem_cache_alloc+0xa2/0x1b0
  Jan  9 21:03:49 ubnu kernel: [  410.357558]  ? mempool_alloc_slab+0x15/0x20
  Jan  9 21:03:49 ubnu kernel: [  410.357570]  ? wait_woken+0x80/0x80
  Jan  9 21:03:49 ubnu kernel: [  410.357580]  mempool_alloc_slab+0x15/0x20
  Jan  9 21:03:49 ubnu kernel: [  410.357590]  mempool_alloc+0x71/0x190
  Jan  9 21:03:49 ubnu kernel: [  410.357660]  ? smb2_add_credits+0xb0/0x250 
[cifs]
  Jan  9 21:03:49 ubnu kernel: [  410.357709]  cifs_small_buf_get+0x1a/0x30 
[cifs]
  Jan  9 21:03:49 ubnu kernel: [  410.357751]  
cifs_demultiplex_thread+0x5c7/0xaf0 [cifs]
  Jan  9 21:03:49 ubnu kernel: [  410.357762]  ? __schedule+0x299/0x8a0

[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-06-07 Thread Thomas Lenarz

Boot switch "nopti" solves the problem as well on Asus X51R (Laptop).
However, I think it is not a final solution, cause its Processor Celeron M 520 
is on the vulnerability 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/1827884

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE: 
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running. 
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs 
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  
  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try the older kernel.

  
  More Info on what I've already tried for troubleshooting (on the HP6710b) is 
outlined in https://answers.launchpad.net/ubuntu/+question/680486

  Happy to provide more info if needed, but I'm just an end user user
  and new to Linux, so will be on a learning curve at this end.  (and
  apologies in advance if this a user problem, and not an actual bug).
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1681 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May  6 21:16:34 2019
  MachineType: Hewlett-Packard HP Compaq 6710b
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.13
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: SGH8080272
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1034 F pulseaudio
   /dev/snd/controlC0:  michael1034 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  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 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. W1N
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=5e6f46b1-73a8-4779-bc20-414a46286723 ro forcepae quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18

[Kernel-packages] [Bug 1832022] [NEW] Kworker stuck 100% high Workqueue: netns cleanup_net _raw_spin_lock

2019-06-07 Thread matthew loschiavo

Public bug reported:

I read your following post (https://lkml.org/lkml/2019/5/29/309).Is
there any other configuration to disable or which patch is required to
resolve this issue?

I am facing a very similar issue with almost identical output from dmesg
call trace.  This occurs with high frequency.   It's fairly easy to
identify as kworker usage gets stuck very high when the problem occurs,
but this manifests into a bigger problem as docker containers cannot
start/restart and host requires a reboot to resolve.   I have machines
running Ubuntu with various kernels (4.15.0-1031-azure through
4.15.0-1041-azure) and problem occurs randomly on every kernel version.
Using weave plugins vs docker overlay drivers for swarm scope, docker
overlay drivers seem to have the problem more frequently, but weave has
same kworker issue with a lower frequency.   I have also disabled ipv6
on many nodes, but this doesn't solve the issue either.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.15.0-1040-azure 4.15.0-1040.44
ProcVersionSignature: User Name 4.15.0-1040.44-azure 4.15.18
Uname: Linux 4.15.0-1040-azure x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Jun  7 17:14:08 2019
SourcePackage: linux-signed-azure
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-azure (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images xenial

** Attachment added: "output.log"
   https://bugs.launchpad.net/bugs/1832022/+attachment/5269380/+files/output.log

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

Title:
  Kworker stuck 100% high Workqueue: netns cleanup_net _raw_spin_lock

Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  I read your following post (https://lkml.org/lkml/2019/5/29/309).
  Is there any other configuration to disable or which patch is required
  to resolve this issue?

  I am facing a very similar issue with almost identical output from
  dmesg call trace.  This occurs with high frequency.   It's fairly easy
  to identify as kworker usage gets stuck very high when the problem
  occurs, but this manifests into a bigger problem as docker containers
  cannot start/restart and host requires a reboot to resolve.   I have
  machines running Ubuntu with various kernels (4.15.0-1031-azure
  through 4.15.0-1041-azure) and problem occurs randomly on every kernel
  version.Using weave plugins vs docker overlay drivers for swarm
  scope, docker overlay drivers seem to have the problem more
  frequently, but weave has same kworker issue with a lower frequency.
  I have also disabled ipv6 on many nodes, but this doesn't solve the
  issue either.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-1040-azure 4.15.0-1040.44
  ProcVersionSignature: User Name 4.15.0-1040.44-azure 4.15.18
  Uname: Linux 4.15.0-1040-azure x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Jun  7 17:14:08 2019
  SourcePackage: linux-signed-azure
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-06-07 Thread Thomas Lenarz

Similar/same problem affects me on
Asus X51R (Laptop).

OS: Lubuntu 18.04. 32-Bit

Occured after automatic update including Kernel probably around
4.15.0-48

Ubuntu seems to boot up, switches on and off screen several times.
Logon screen does NOT appear.
Instead, it restarts itself. After restarting itself it gets stuck onto a black
screeen showing a very big mouse-pointer. (Mouse-Pointer can be moved using the
track-pad. However not further interaction with the system is possible.)

Booting up the system in recovery mode is possible. However, screen resolution
is restricted.
Booting up the system using an older kernel (4.09.xxx) is possible. Screen
resolution is OK, but WIFI is not available, then.

Thanks a lot,
Thomas

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

Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
Confirmed

Bug description:
NOTE: Boot problems on TWO different laptops after Software Updater
updated to kernel 4.15.0-48

Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
desktop. Both fresh installs from minimal CD in early April,
originally kernel 0.4.15.0-47, both working fine.

Bug report filed on THIS MACHINE:
HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel
integrated graphics controller GM965/GL960 (with kernel command line parameter
¨video=SVIDEO-1:d¨)

SYMPTOM:
4.15.0-48 requires a second ´recovery´ boot to get it up and running.
Will not boot properly after a normal shutdown - screen goes funny and it
hangs
Does boot successfully after a hard shutdown - detects improper shutdown,
loads grub menu, then boot successfully

Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots
normally after a normal shutdown)

OTHER MACHINE:
Even older!!! ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility
Radeon 9600 GPU. Running with command line parameter "forcepae".
SYMPTOM:
Won't boot at all.
Was working fine under 4.15.0-47 as originally installed, until software
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I
can't even get into the grub menu to try the older kernel.

More Info on what I've already tried for troubleshooting (on the HP6710b) is
outlined in https://answers.launchpad.net/ubuntu/+question/680486

Happy to provide more info if needed, but I'm just an end user user
and new to Linux, so will be on a learning curve at this end. (and
apologies in advance if this a user problem, and not an actual bug).
Thanks

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-48-generic 4.15.0-48.51
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic i686
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: michael1681 F pulseaudio
CurrentDesktop: XFCE
Date: Mon May 6 21:16:34 2019
MachineType: Hewlett-Packard HP Compaq 6710b
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
RelatedPackageVersions:
linux-restricted-modules-4.15.0-48-generic N/A
linux-backports-modules-4.15.0-48-generic N/A
linux-firmware 1.173.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DDU Ver. F.13
dmi.board.name: 30C0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2E
dmi.chassis.asset.tag: SGH8080272
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP Compaq 6710b
dmi.product.version: F.13
dmi.sys.vendor: Hewlett-Packard
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: michael1034 F pulseaudio
/dev/snd/controlC0: michael1034 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
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 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile

Re: [Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-06-07 Thread Tyler Hicks

On 2019-06-07 16:11:07, Brad Evans wrote:
> The nopti switch is working for me with 4.15.0-51-generic.
> 
> I think possibly  the mitigations=off was not working for me because I
> positioned it at the wrong part (the end) of the linux arguments list.

The 'mitigations=off' option wasn't working for you because the
4.15.0-48.51 kernel didn't know about that option. It was first
backported in 4.15.0-50.54. Sorry for the confusion.

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

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE: 
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running. 
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs 
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  
  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try the older kernel.

  
  More Info on what I've already tried for troubleshooting (on the HP6710b) is 
outlined in https://answers.launchpad.net/ubuntu/+question/680486

  Happy to provide more info if needed, but I'm just an end user user
  and new to Linux, so will be on a learning curve at this end.  (and
  apologies in advance if this a user problem, and not an actual bug).
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1681 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May  6 21:16:34 2019
  MachineType: Hewlett-Packard HP Compaq 6710b
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.13
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: SGH8080272
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1034 F pulseaudio
   /dev/snd/controlC0:  michael1034 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  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 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. W1N
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:

[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-06-07 Thread Brad Evans

Thank you

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

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE: 
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running. 
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs 
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  
  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try the older kernel.

  
  More Info on what I've already tried for troubleshooting (on the HP6710b) is 
outlined in https://answers.launchpad.net/ubuntu/+question/680486

  Happy to provide more info if needed, but I'm just an end user user
  and new to Linux, so will be on a learning curve at this end.  (and
  apologies in advance if this a user problem, and not an actual bug).
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1681 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May  6 21:16:34 2019
  MachineType: Hewlett-Packard HP Compaq 6710b
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.13
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: SGH8080272
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1034 F pulseaudio
   /dev/snd/controlC0:  michael1034 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  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 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. W1N
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=5e6f46b1-73a8-4779-bc20-414a46286723 ro forcepae quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  RfKill:

[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-06-07 Thread Brad Evans

The nopti switch is working for me with 4.15.0-51-generic.

I think possibly  the mitigations=off was not working for me because I
positioned it at the wrong part (the end) of the linux arguments list. I
put nopti closer to the front of the arguments 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/1827884

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE: 
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running. 
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs 
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  
  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try the older kernel.

  
  More Info on what I've already tried for troubleshooting (on the HP6710b) is 
outlined in https://answers.launchpad.net/ubuntu/+question/680486

  Happy to provide more info if needed, but I'm just an end user user
  and new to Linux, so will be on a learning curve at this end.  (and
  apologies in advance if this a user problem, and not an actual bug).
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1681 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May  6 21:16:34 2019
  MachineType: Hewlett-Packard HP Compaq 6710b
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.13
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: SGH8080272
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1034 F pulseaudio
   /dev/snd/controlC0:  michael1034 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  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 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. W1N
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=5e6f46b1-73a8-4779-bc20-414a46286723 ro forcepae quiet splash

[Kernel-packages] [Bug 1832012] Re: Initial support for Qualcomm Snapdragon 820 chipset

** Description changed:

  Impact:
  
- Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm
+ Although the Bionic/snapdragon kernel contains the BSP from the Qualcomm
  landing tree kernel[1], it didn't work on Snapdragon 820 based board
  (e.g.  Qualcomm DB820C APQ8096).
  
  Fix:
  
  Import the necessary patches to make it boot on such board (and clones).
  
  How to test:
  
  1) put the board in fastboot mode (see [2])
  2) generate a compatible boot.img:
  
  $ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
  $ touch ramdisk
  $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb 
--ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 
--ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 
'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 
init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 
fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output 
bionic-snapdragon-db820c-boot.img
  
  3) boot the board using the generated boot.img:
  
  $ fastboot boot bionic-snapdragon-db820c-boot.img
  
  Regression potential:
  
  With new code there's always a degree of regression potential, but all
  patches (but one) came from Linus's upstream tree, and the only external
  one, came direclty from the qcom-lt 4.14 tree.
  
  1: 
https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
  2: 
https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html

** Description changed:

  Impact:
  
  Although the Bionic/snapdragon kernel contains the BSP from the Qualcomm
  landing tree kernel[1], it didn't work on Snapdragon 820 based board
  (e.g.  Qualcomm DB820C APQ8096).
  
  Fix:
  
- Import the necessary patches to make it boot on such board (and clones).
+ Import the necessary patches to make it boot on such a board (and
+ clones).
  
  How to test:
  
  1) put the board in fastboot mode (see [2])
  2) generate a compatible boot.img:
  
  $ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
  $ touch ramdisk
  $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb 
--ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 
--ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 
'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 
init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 
fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output 
bionic-snapdragon-db820c-boot.img
  
  3) boot the board using the generated boot.img:
  
  $ fastboot boot bionic-snapdragon-db820c-boot.img
  
  Regression potential:
  
  With new code there's always a degree of regression potential, but all
  patches (but one) came from Linus's upstream tree, and the only external
  one, came direclty from the qcom-lt 4.14 tree.
  
  1: 
https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
  2: 
https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html

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

Title:
  Initial support for Qualcomm Snapdragon 820 chipset

Status in linux-snapdragon package in Ubuntu:
  New

Bug description:
  Impact:

  Although the Bionic/snapdragon kernel contains the BSP from the
  Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820
  based board (e.g.  Qualcomm DB820C APQ8096).

  Fix:

  Import the necessary patches to make it boot on such a board (and
  clones).

  How to test:

  1) put the board in fastboot mode (see [2])
  2) generate a compatible boot.img:

  $ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
  $ touch ramdisk
  $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb 
--ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 
--ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 
'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 
init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 
fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output 
bionic-snapdragon-db820c-boot.img

  3) boot the board using the generated boot.img:

  $ fastboot boot bionic-snapdragon-db820c-boot.img

  Regression potential:

  With new code there's always a degree of regression potential, but all
  patches (but one) came from Linus's upstream tree, and the only
  external one, came direclty from the qcom-lt 4.14 tree.

  1: 
https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
  2:

[Kernel-packages] [Bug 1832012] Re: Initial support for Qualcomm Snapdragon 820 chipset

** Description changed:

  Impact:
  
- The bionic/snapdragon kernel should work on qcom410 and qcom820
- chipsets, but due to some bugs, it never booted on any qcom820 board
- (e.g. Qualcomm DB820C APQ8096).
+ Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm 
landing
+ tree kernel[1], it didn't work on Snapdragon 820 based board (e.g.  Qualcomm
+ DB820C APQ8096).
  
  Fix:
  
- Import all the necessary patches (see the pull request below).
+ Import the necessary patches to make it boot on such board (and clones).
  
  How to test:
  
- 1) put the board in fastboot mode (see [1])
+ 1) put the board in fastboot mode (see [2])
  2) generate a compatible boot.img:
  
  $ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
  $ touch ramdisk
  $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb 
--ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 
--ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 
'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 
init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 
fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output 
bionic-snapdragon-db820c-boot.img
  
- 3) fastboot the board using the freshly generated boot.img:
+ 3) boot the board using the generated boot.img:
  
  $ fastboot boot bionic-snapdragon-db820c-boot.img
  
  Regression potential:
  
- With new code there's always a degree of regression potential, but all
- patches (but one) were cherry-picked from Linus's upstream tree, and the
- only external one, came direclty from the qcom-lt 4.14 tree.
+ With new code there's always a degree of regression potential, but all patches
+ (but one) came from Linus's upstream tree, and the only external one, came
+ direclty from the qcom-lt 4.14 tree.
  
- 1:
- 
https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation
- /board-recovery.md.html
+ 1: 
https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
+ 2: 
https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html

** Description changed:

  Impact:
  
- Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm 
landing
- tree kernel[1], it didn't work on Snapdragon 820 based board (e.g.  Qualcomm
- DB820C APQ8096).
+ Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm
+ landing tree kernel[1], it didn't work on Snapdragon 820 based board
+ (e.g.  Qualcomm DB820C APQ8096).
  
  Fix:
  
  Import the necessary patches to make it boot on such board (and clones).
  
  How to test:
  
  1) put the board in fastboot mode (see [2])
  2) generate a compatible boot.img:
  
  $ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
  $ touch ramdisk
  $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb 
--ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 
--ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 
'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 
init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 
fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output 
bionic-snapdragon-db820c-boot.img
  
  3) boot the board using the generated boot.img:
  
  $ fastboot boot bionic-snapdragon-db820c-boot.img
  
  Regression potential:
  
- With new code there's always a degree of regression potential, but all patches
- (but one) came from Linus's upstream tree, and the only external one, came
- direclty from the qcom-lt 4.14 tree.
+ With new code there's always a degree of regression potential, but all
+ patches (but one) came from Linus's upstream tree, and the only external
+ one, came direclty from the qcom-lt 4.14 tree.
  
  1: 
https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
  2: 
https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html

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

Title:
  Initial support for Qualcomm Snapdragon 820 chipset

Status in linux-snapdragon package in Ubuntu:
  New

Bug description:
  Impact:

  Although the Bionic/snapdragon kernel contains the BSP from the
  Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820
  based board (e.g.  Qualcomm DB820C APQ8096).

  Fix:

  Import the necessary patches to make it boot on such a board (and
  clones).

  How to test:

  1) put the board in fastboot mode (see [2])
  2) generate a compatible boot.img:

  $ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
  $ touch ramdisk
  $ python android/system/core/mkbootimg/mkbootimg.py --kernel

[Kernel-packages] [Bug 1832012] Re: Initial support for Qualcomm Snapdragon 820 chipset

** Summary changed:

- Enable the Qualcomm DB820C board
+ Initial support for Qualcomm Snapdragon 820 chipset

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

Title:
  Initial support for Qualcomm Snapdragon 820 chipset

Status in linux-snapdragon package in Ubuntu:
  New

Bug description:
  Impact:

  The bionic/snapdragon kernel should work on qcom410 and qcom820
  chipsets, but due to some bugs, it never booted on any qcom820 board
  (e.g. Qualcomm DB820C APQ8096).

  Fix:

  Import all the necessary patches (see the pull request below).

  How to test:

  1) put the board in fastboot mode (see [1])
  2) generate a compatible boot.img:

  $ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
  $ touch ramdisk
  $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb 
--ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 
--ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 
'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 
init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 
fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output 
bionic-snapdragon-db820c-boot.img

  3) fastboot the board using the freshly generated boot.img:

  $ fastboot boot bionic-snapdragon-db820c-boot.img

  Regression potential:

  With new code there's always a degree of regression potential, but all
  patches (but one) were cherry-picked from Linus's upstream tree, and
  the only external one, came direclty from the qcom-lt 4.14 tree.

  1:
  
https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation
  /board-recovery.md.html

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

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

[Kernel-packages] [Bug 1832012] [NEW] Enable the Qualcomm DB820C board

Public bug reported:

Impact:

The bionic/snapdragon kernel should work on qcom410 and qcom820
chipsets, but due to some bugs, it never booted on any qcom820 board
(e.g. Qualcomm DB820C APQ8096).

Fix:

Import all the necessary patches (see the pull request below).

How to test:

1) put the board in fastboot mode (see [1])
2) generate a compatible boot.img:

$ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
$ touch ramdisk
$ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb 
--ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 
--ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 
'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 
init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 
fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output 
bionic-snapdragon-db820c-boot.img

3) fastboot the board using the freshly generated boot.img:

$ fastboot boot bionic-snapdragon-db820c-boot.img

Regression potential:

With new code there's always a degree of regression potential, but all
patches (but one) were cherry-picked from Linus's upstream tree, and the
only external one, came direclty from the qcom-lt 4.14 tree.

1:
https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation
/board-recovery.md.html

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

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

Title:
  Enable the Qualcomm DB820C board

Status in linux-snapdragon package in Ubuntu:
  New

Bug description:
  Impact:

  The bionic/snapdragon kernel should work on qcom410 and qcom820
  chipsets, but due to some bugs, it never booted on any qcom820 board
  (e.g. Qualcomm DB820C APQ8096).

  Fix:

  Import all the necessary patches (see the pull request below).

  How to test:

  1) put the board in fastboot mode (see [1])
  2) generate a compatible boot.img:

  $ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
  $ touch ramdisk
  $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb 
--ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 
--ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 
'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 
init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 
fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output 
bionic-snapdragon-db820c-boot.img

  3) fastboot the board using the freshly generated boot.img:

  $ fastboot boot bionic-snapdragon-db820c-boot.img

  Regression potential:

  With new code there's always a degree of regression potential, but all
  patches (but one) were cherry-picked from Linus's upstream tree, and
  the only external one, came direclty from the qcom-lt 4.14 tree.

  1:
  
https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation
  /board-recovery.md.html

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

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

[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-06-07 Thread Tyler Hicks

Hello - The 'mitigations=off' option is not the best workaround as it
disables all CPU mitigations.

Since this bug is about 4.15.0-48.51 and i386 installations, the bug is
most likely caused by the addition of Page Table Isolation (PTI) for
i386. It landed in the aforementioned kernel release.

To be selective and only disable PTI, please use the 'nopti' boot option
rather than 'mitigations=off'.

In the meantime, we'll start working to figure out the cause of this
problem. Thanks for the bug report.

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

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE: 
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running. 
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs 
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  
  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try the older kernel.

  
  More Info on what I've already tried for troubleshooting (on the HP6710b) is 
outlined in https://answers.launchpad.net/ubuntu/+question/680486

  Happy to provide more info if needed, but I'm just an end user user
  and new to Linux, so will be on a learning curve at this end.  (and
  apologies in advance if this a user problem, and not an actual bug).
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1681 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May  6 21:16:34 2019
  MachineType: Hewlett-Packard HP Compaq 6710b
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.13
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: SGH8080272
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1034 F pulseaudio
   /dev/snd/controlC0:  michael1034 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  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 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. W1N
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product

[Kernel-packages] [Bug 1830905] Re: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

2019-06-07 Thread Dan Watkins

Applying the latest vbios update (F52) has caused this problem to go
away; this isn't a kernel issue.

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

Title:
  Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

Status in linux package in Ubuntu:
  Invalid

Bug description:
  From dmesg:

  [0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0
  [5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC 
bug?) status = 0x801
  [5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 
took 5615333 usecs

  

  [9.984204] kernel: usb 1-7: new full-speed USB device number 4 using 
xhci_hcd
  [   10.308689] kernel: usb 1-7: New USB device found, idVendor=8087, 
idProduct=0a2b, bcdDevice= 0.10
  [   10.308690] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [   34.654721] kernel: xhci_hcd :07:00.2: can't setup: -110
  [   34.654730] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered
  [   34.654769] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110
  [   34.654771] kernel: xhci_hcd: probe of :07:00.2 failed with error -110

  $ lspci -k -s :07:00
  07:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 
Rev. A] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
  07:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio 
Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 High Definition Audio 
Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  07:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev 
a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB 3.1 Host Controller
  07:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C 
Port Policy Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB Type-C Port Policy 
Controller
Kernel driver in use: nvidia-gpu
Kernel modules: i2c_nvidia_gpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 4470 F pulseaudio
   /dev/snd/controlC1:  daniel 4470 F pulseaudio
   /dev/snd/controlC2:  daniel 4470 F pulseaudio
  CurrentDesktop: i3
  Date: Wed May 29 09:36:51 2019
  InstallationDate: Installed on 2019-05-07 (21 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.179
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

2019-06-07 Thread bugproxy

--- Comment From rjbr...@us.ibm.com 2019-06-07 09:22 EDT---
added you specifically as a reader frank - try now ?

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

Title:
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in
  kernel virtual address space

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New

Bug description:
  == Comment: #0 - Robert J. Brenneman  - 2019-05-30 
11:16:45 ==
  ---Problem Description---
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in virtual 
kernel address space
   
  Contact Information = rjbr...@us.ibm.com 
   
  ---uname output---
  Linux ECOS0018 4.15.0-50-generic #54-Ubuntu SMP Tue May 7 05:57:08 UTC 2019 
s390x s390x s390x GNU/Linux
   
  Machine Type = z13   2964 NE1 
   
  ---System Hang---
   z/VM took a VMDUMP and reIPLed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   boot system, start jenkins, let it run a couple days
   
  Stack trace output:
   05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70 
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570 
  05/29/19 13:24:06   ?<008e92d4>? __do_softirq+0x124/0x358 
  05/29/19 13:24:06   ?<00179d52>? irq_exit+0xba/0xd0 
  05/29/19 13:24:06   ?<0010c412>? do_IRQ+0x8a/0xb8 
  05/29/19 13:24:06   ?<008e87f0>? ext_int_handler+0x134/0x138 
  05/29/19 13:24:06   ?<00102cee>? enabled_wait+0x4e/0xe0 
  05/29/19 13:24:06  (?<1201>? 0x1201)
  05/29/19 13:24:06   ?<0010303a>? arch_cpu_idle+0x32/0x48 
  05/29/19 13:24:06   ?<001c5ae8>? do_idle+0xe8/0x1a8 

   
  Oops output:
   05/29/19 13:24:06  User process fault: interruption code 003b ilc:3 in 
libc-2.23.so?3ffaca0+185000?
  05/29/19 13:24:06  Failing address:  TEID: 0800
  05/29/19 13:24:06  Fault in primary space mode while using user ASCE.
  05/29/19 13:24:06  AS:000710b241c7 R3:0024 
  05/29/19 13:24:06  Unable to handle kernel pointer dereference in virtual 
kernel address space
  05/29/19 13:24:06  Failing address: 03dbe000 TEID: 03dbe403
  05/29/19 13:24:06  Fault in home space mode while using kernel ASCE.
  05/29/19 13:24:06  AS:00ea8007 R3:0024 
  05/29/19 13:24:06  Oops: 003b ilc:3 ?#1? SMP 
  05/29/19 13:24:06  Modules linked in: veth xt_nat xt_tcpudp ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_con
  05/29/19 13:24:06   ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 
sha256_s390 dasd_fba_mod dasd_eckd_mod sha1_s390 sha_common dasd_mod
  05/29/19 13:24:06  CPU: 7 PID: 0 Comm: swapper/7 Not tainted 
4.15.0-50-generic #54-Ubuntu
  05/29/19 13:24:06  Hardware name: IBM 2964 NE1 798 (z/VM 6.4.0)
  05/29/19 13:24:06  Krnl PSW : dcb002be 72762961 
(__tlb_remove_table+0x56/0xd0)
  05/29/19 13:24:06 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 
PM:0 RI:0 EA:3
  05/29/19 13:24:06  Krnl GPRS: ffba 02b8 
02b80003 00eacac8
  05/29/19 13:24:06 ffba 00b9 
0700 000a
  05/29/19 13:24:06 0404c001 0007d2fb5c38 
0007cf71fdf0 03dbe000
  05/29/19 13:24:06 03dbe018 008fe740 
0007cf71fd08 0007cf71fcd8
  05/29/19 13:24:06  Krnl Code: 0012b956: ec2c002a027f   clij
%r2,2,12,12b9aa
  05/29/19 13:24:06 0012b95c: ec26001d037e   cij 
%r2,3,6,12b996
  05/29/19 13:24:06#0012b962: 41c0b018   la  
%r12,24(%r11)
  05/29/19 13:24:06>0012b966: e548b008   mvghi   
8(%r11),0
  05/29/19 13:24:06 0012b96c: a7390008   lghi
%r3,8
  05/29/19 13:24:06 0012b970: b904002b   lgr 
%r2,%r11
  05/29/19 13:24:06 0012b974: c0e5000e8f8a   brasl   
%r14,2fd888
  05/29/19 13:24:06 0012b97a: a718   lhi 
%r1,-1
  05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70 
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570 
  05/29/19 13:24:06   ?<008e92d4>? __do_softirq+0x124/0x358 
  05/29/19 13:24:06   ?<00179d52>? irq_exit+0xba/0xd0 
  05/29/19 13:24:06   ?<0010c412>? do_IRQ+0x8a/0xb8 
  05/29/19 13:24:06

[Kernel-packages] [Bug 1808056] Re: vmlinuz is very large in arm64 -raspi2

On the kernel side, the switch to a compressed kernel is a trivial
change:

diff --git a/debian.raspi2/rules.d/arm64.mk b/debian.raspi2/rules.d/arm64.mk
index ada61b8..9f82433 100644
--- a/debian.raspi2/rules.d/arm64.mk
+++ b/debian.raspi2/rules.d/arm64.mk
@@ -3,7 +3,7 @@ build_arch  = arm64
 header_arch= arm64
 defconfig  = defconfig
 flavours   = raspi2
-build_image= Image
+build_image= Image.gz
 kernel_file= arch/$(build_arch)/boot/Image
 install_file   = vmlinuz
 no_dumpfile= true

Feel free to send such a change to the kernel ml once userspace issues
(classic and core) are sorted out.

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

Title:
  vmlinuz is very large in arm64 -raspi2

Status in flash-kernel package in Ubuntu:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Triaged

Bug description:
  The debs are close to the same size:

  mwhudson@ringil:~/Downloads$ ls -l 
linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb 
  -rw-rw-r-- 1 mwhudson mwhudson 5398652 Dec 12 10:42 
linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb
  mwhudson@ringil:~/Downloads$ ls -l 
linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb 
  -rw-rw-r-- 1 mwhudson mwhudson 6640960 Dec 12 10:42 
linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb

  But the vmlinuz on arm64 is several times larger:

  $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb 
  -rw--- root/root   6633048 2018-12-07 06:38 
./boot/vmlinuz-4.15.0-1030-raspi2
  $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb 
  -rw--- root/root  23914504 2018-12-07 06:38 
./boot/vmlinuz-4.15.0-1030-raspi2

  This forced us to make the boot partition larger for the raspi3 b+
  arm64 image we made.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1808056/+subscriptions

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

[Kernel-packages] [Bug 1831736] Re: [MIR] lz4 by default

** Description changed:

  Use `lz4 -9 -l` compression for initramfs by default as discussed on
  ubuntu-devel.
  
  This would also pull the lz4 package into main
  
  https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html
  
  [Regression Potential]
  
  We are trying to optimize for total boot speed, but performing a micro-
  optimization upon time to create/unpack kernel/initrd is an insufficient
  benchmark for total boot speed. This is because it ignores time to load
  the kernel/initrd, and whether the firmware/bootloader were able to
  stream decompress it whilst loading it. I.e. it is argued that in the
  real world, subsecond decompression gains are irrelevant if UEFI
  firmware, tftp boot, etc. take a lot longer than that to read extra 10s
  of MBs of boot material.
  
  [TODO]
  Measure pure i/o load speed with stopwatch, to figure out MB/s speed of 
loading initrds/kernel off FAT32, EXT4, TFTP, HTTP.
  Re-evaluate if we should provide different compression mechanisms:
  - ie. gzip instead of lz4 for most cases (revert)
  - ie. xz for painful i/o cases (e.g. netboot)
+ 
+ I booted grub2 and measured loading largish amount of files, ie. $ date;
+ initrd (hd0,gpt5)/initrd.img;  initrd (hd0,gpt5)/initrd.img; initrd
+ (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd
+ (hd0,gpt5)/initrd.img; date
+ 
+ To get a rough speed between 30 and 44 MB/s of loading these files off
+ ext4 on nvme.
+ 
+ With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o
+ penalty is 0.18s whilst I gain over a second in faster decompression
+ time. Overall a win.
+ 
+ xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining
+ 2.4s of decompression time, meaning overall worse than gzip.

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

Title:
  [MIR] lz4 by default

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in live-build package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lz4 package in Ubuntu:
  Fix Released
Status in partman-auto package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  Use `lz4 -9 -l` compression for initramfs by default as discussed on
  ubuntu-devel.

  This would also pull the lz4 package into main

  https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html

  [Regression Potential]

  We are trying to optimize for total boot speed, but performing a
  micro-optimization upon time to create/unpack kernel/initrd is an
  insufficient benchmark for total boot speed. This is because it
  ignores time to load the kernel/initrd, and whether the
  firmware/bootloader were able to stream decompress it whilst loading
  it. I.e. it is argued that in the real world, subsecond decompression
  gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot
  longer than that to read extra 10s of MBs of boot material.

  [TODO]
  Measure pure i/o load speed with stopwatch, to figure out MB/s speed of 
loading initrds/kernel off FAT32, EXT4, TFTP, HTTP.
  Re-evaluate if we should provide different compression mechanisms:
  - ie. gzip instead of lz4 for most cases (revert)
  - ie. xz for painful i/o cases (e.g. netboot)

  I booted grub2 and measured loading largish amount of files, ie. $
  date; initrd (hd0,gpt5)/initrd.img;  initrd (hd0,gpt5)/initrd.img;
  initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd
  (hd0,gpt5)/initrd.img; date

  To get a rough speed between 30 and 44 MB/s of loading these files off
  ext4 on nvme.

  With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o
  penalty is 0.18s whilst I gain over a second in faster decompression
  time. Overall a win.

  xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining
  2.4s of decompression time, meaning overall worse than gzip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+subscriptions

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

[Kernel-packages] [Bug 1831979] Re: linux: -proposed tracker

** Tags removed: kernel-release-tracking-bug-live

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

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

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

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

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 1831976 (pc-kernel), bug 1831977 (pc-lowlatency-
  kernel)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Friday, 07. June 2019 09:50 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak

2019-06-07 Thread TJ

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1831751

Title:
  rtlwifi: aggresive memory leak

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI) 
the memory usage grows slowly to take all the available RAM when i let the 
computer running over the night (with just top and irssi), and i have to reboot 
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i 
was still flooded with message about pci aer taking lots of disk space in the 
logs, but pci=noaer fixed this problem and i had no memory leak.
  The computer is a common laptop: HP Pavilion.

  ---
  Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly 
disabled to capture the AERs.

  Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
  overnight booted just to console (systemd.unit=multi-user.target).

  The memory leak doesn't affect Windows but owner is going to check
  Windows Event Log for signs of AERs being logged.

  ---

  Original suspect of AER is not guilty.

  This turns out to be a bug in the rtlwifi driver where in some rare
  circumstances it fails to free an sk_buf.

  Reporter has been testing a DKMS build of rtlwfi with the fix applied
  and confirms it solves the issue.

  Upstream has the commit. Can we get this cherry-picked into all
  releases?

  commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
  Author: Larry Finger 
  Date:   Sat Nov 17 20:55:03 2018 -0600

  rtlwifi: Fix leak of skb when processing C2H_BT_INFO
  
  With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
  C2H_BT_INFO"), calling rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
  the routine returns without freeing that skb, thereby leaking it.
  
  This issue has been discussed at 
https://github.com/lwfinger/rtlwifi_new/issues/401
  and the fix tested there.
  
  Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing 
C2H_BT_INFO")
  Reported-and-tested-by: Francisco Machado Magalhães Neto 

  Cc: Francisco Machado Magalhães Neto 
  Cc: Ping-Ke Shih 
  Cc: Stable  # 4.18+
  Signed-off-by: Larry Finger 
  Signed-off-by: Kalle Valo 

  diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c 
b/drivers/net/wireless/realtek/rtlwifi/base.c
  index f4122c8fdd97..ef9b502ce576 100644
  --- a/drivers/net/wireless/realtek/rtlwifi/base.c
  +++ b/drivers/net/wireless/realtek/rtlwifi/base.c
  @@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct 
sk_buff *skb)
   
  if (rtl_c2h_fast_cmd(hw, skb)) {
  rtl_c2h_content_parsing(hw, skb);
  +   kfree_skb(skb);
  return;
  }

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

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

[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak

2019-06-07 Thread roussel geoffrey

Ok the bug is fixed, it was in fact the same issue as discussed here:

https://github.com/lwfinger/rtlwifi_new/issues/401

And the fix:

https://github.com/0day-
ci/linux/commit/3e10e17914a56b27007604880d6de7e7ff241e14

Rebuilding the rtlwifi module with the patch fixed the problem, memory is 
stable not leaking anymore!
Thanks a lot #ubuntu-discuss and especially TJ-!

** Bug watch added: github.com/lwfinger/rtlwifi_new/issues #401
   https://github.com/lwfinger/rtlwifi_new/issues/401

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

Title:
  rtlwifi: aggresive memory leak

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI) 
the memory usage grows slowly to take all the available RAM when i let the 
computer running over the night (with just top and irssi), and i have to reboot 
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i 
was still flooded with message about pci aer taking lots of disk space in the 
logs, but pci=noaer fixed this problem and i had no memory leak.
  The computer is a common laptop: HP Pavilion.

  ---
  Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly 
disabled to capture the AERs.

  Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
  overnight booted just to console (systemd.unit=multi-user.target).

  The memory leak doesn't affect Windows but owner is going to check
  Windows Event Log for signs of AERs being logged.

  ---

  Original suspect of AER is not guilty.

  This turns out to be a bug in the rtlwifi driver where in some rare
  circumstances it fails to free an sk_buf.

  Reporter has been testing a DKMS build of rtlwfi with the fix applied
  and confirms it solves the issue.

  Upstream has the commit. Can we get this cherry-picked into all
  releases?

  commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
  Author: Larry Finger 
  Date:   Sat Nov 17 20:55:03 2018 -0600

  rtlwifi: Fix leak of skb when processing C2H_BT_INFO
  
  With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
  C2H_BT_INFO"), calling rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
  the routine returns without freeing that skb, thereby leaking it.
  
  This issue has been discussed at 
https://github.com/lwfinger/rtlwifi_new/issues/401
  and the fix tested there.
  
  Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing 
C2H_BT_INFO")
  Reported-and-tested-by: Francisco Machado Magalhães Neto 

  Cc: Francisco Machado Magalhães Neto 
  Cc: Ping-Ke Shih 
  Cc: Stable  # 4.18+
  Signed-off-by: Larry Finger 
  Signed-off-by: Kalle Valo 

  diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c 
b/drivers/net/wireless/realtek/rtlwifi/base.c
  index f4122c8fdd97..ef9b502ce576 100644
  --- a/drivers/net/wireless/realtek/rtlwifi/base.c
  +++ b/drivers/net/wireless/realtek/rtlwifi/base.c
  @@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct 
sk_buff *skb)
   
  if (rtl_c2h_fast_cmd(hw, skb)) {
  rtl_c2h_content_parsing(hw, skb);
  +   kfree_skb(skb);
  return;
  }

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

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

[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak

2019-06-07 Thread TJ

** Description changed:

  Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI) 
the memory usage grows slowly to take all the available RAM when i let the 
computer running over the night (with just top and irssi), and i have to reboot 
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i 
was still flooded with message about pci aer taking lots of disk space in the 
logs, but pci=noaer fixed this problem and i had no memory leak.
  The computer is a common laptop: HP Pavilion.
  
  ---
  Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly 
disabled to capture the AERs.
  
  Memory seems to be consumed (~6 GB of 8GB) just by leaving PC overnight
  booted just to console (systemd.unit=multi-user.target).
  
  The memory leak doesn't affect Windows but owner is going to check
  Windows Event Log for signs of AERs being logged.
  
  ---
  
- ## AERs (repeated several times per second)
+ Original suspect of AER is not guilty.
  
- [   34.978011] pcieport :00:1d.0:   device [8086:9d1b] error 
status/mask=0001/2000
- [   34.978013] pcieport :00:1d.0:[ 0] Receiver Error (First)
- [   34.978038] pcieport :00:1d.0: AER: Corrected error received: 
:00:1d.0
- [   34.978042] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
+ This turns out to be a bug in the rtlwifi driver where in some rare
+ circumstances it fails to free an sk_buf.
  
- ## PCI device
+ Reporter has been testing a DKMS build of rtlwfi with the fix applied
+ and confirms it solves the issue.
  
-   +-1d.0-[04]00.0  Realtek Semiconductor Co., Ltd. RTL8723BE PCIe
- Wireless Network Adapter [10ec:b723]
+ Upstream has the commit. Can we get this cherry-picked into all
+ releases?
  
- 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9d1b] (rev f1) 
(prog-if 00 [Normal decode])
-   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
-   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
-   PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
-   Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
-   DevCap: MaxPayload 128 bytes, PhantFunc 0
-   ExtTag- RBE+
-   DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
-   RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
-   MaxPayload 128 bytes, MaxReadReq 128 bytes
-   DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
-   LnkCap: Port #12, Speed 8GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <16us
-   ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
-   LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
-   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
-   LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt+ ABWMgmt-
-   SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
-   Slot #11, PowerLimit 10.000W; Interlock- NoCompl+
-   SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
-   Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
-   SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
-   Changed: MRL- PresDet- LinkState+
-   RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ 
CRSVisible-
-   RootCap: CRSVisible-
-   RootSta: PME ReqID , PMEStatus- PMEPending-
-   DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF 
Not Supported ARIFwd+
-   DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Disabled ARIFwd-
-   LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
-Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
-Compliance De-emphasis: -6dB
-   LnkSta2: Current De-emphasis Level: -3.5dB, 
EqualizationComplete-, EqualizationPhase1-
-EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
-   Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
-   Address: fee002d8  Data: 
-   Capabilities: [90] Subsystem: Hewlett-Packard Company Device [103c:820a]
-   Capabilities: [a0] Power Management version 3
-   Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
-   Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
-   Capabilities: [100 v1] Advanced Error Reporting
-   UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
-

[Kernel-packages] [Bug 1831995] [NEW] Bluetooth earphone is connected but disconnected immediately.

2019-06-07 Thread 이야기

Public bug reported:


I have erased and reinstalled Pulseaudio.
It seems like this can not be done since.

I tried the following.
sudo apt-get remove alsa-base pulseaudio
sudo apt-get install alsa-base pulseaudio

I did this again.
sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
sudo apt-get install linux-sound-base alsa-base alsa-utils

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: bluetooth 5.50-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Fri Jun  7 20:33:05 2019
InstallationDate: Installed on 2019-04-04 (64 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Inspiron 7559
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.9
dmi.board.name: 0H0CC0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7559
dmi.product.sku: 0706
dmi.product.version: 1.2.9
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 58:FB:84:C1:51:50  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:125274 acl:68 sco:0 events:1720 errors:0
TX bytes:15000 acl:64 sco:0 commands:861 errors:0

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


** Tags: amd64 apport-bug disco

** Attachment added: "Reference"
   
https://bugs.launchpad.net/bugs/1831995/+attachment/5269290/+files/vokoscreen-2019-06-07_20-25-29.mkv

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

Title:
  Bluetooth earphone is connected but disconnected immediately.

Status in bluez package in Ubuntu:
  New

Bug description:

  I have erased and reinstalled Pulseaudio.
  It seems like this can not be done since.

  I tried the following.
  sudo apt-get remove alsa-base pulseaudio
  sudo apt-get install alsa-base pulseaudio

  I did this again.
  sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
  sudo apt-get install linux-sound-base alsa-base alsa-utils

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluetooth 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Jun  7 20:33:05 2019
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7559
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.9
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.sku: 0706
  dmi.product.version: 1.2.9
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 58:FB:84:C1:51:50  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:125274 acl:68 sco:0 events:1720 errors:0
TX bytes:15000 acl:64 sco:0 commands:861 errors:0

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

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

[Kernel-packages] [Bug 1831736] Re: [MIR] lz4 by default

** Description changed:

  Use `lz4 -9 -l` compression for initramfs by default as discussed on
  ubuntu-devel.
  
  This would also pull the lz4 package into main
  
  https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html
+ 
+ [Regression Potential]
+ 
+ We are trying to optimize for total boot speed, but performing a micro-
+ optimization upon time to create/unpack kernel/initrd is an insufficient
+ benchmark for total boot speed. This is because it ignores time to load
+ the kernel/initrd, and whether the firmware/bootloader were able to
+ stream decompress it whilst loading it. I.e. it is argued that in the
+ real world, subsecond decompression gains are irrelevant if UEFI
+ firmware, tftp boot, etc. take a lot longer than that to read extra 10s
+ of MBs of boot material.
+ 
+ [TODO]
+ Measure pure i/o load speed with stopwatch, to figure out MB/s speed of 
loading initrds/kernel off FAT32, EXT4, TFTP, HTTP.
+ Re-evaluate if we should provide different compression mechanisms:
+ - ie. gzip instead of lz4 for most cases (revert)
+ - ie. xz for painful i/o cases (e.g. netboot)

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

Title:
  [MIR] lz4 by default

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in live-build package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lz4 package in Ubuntu:
  Fix Released
Status in partman-auto package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  Use `lz4 -9 -l` compression for initramfs by default as discussed on
  ubuntu-devel.

  This would also pull the lz4 package into main

  https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html

  [Regression Potential]

  We are trying to optimize for total boot speed, but performing a
  micro-optimization upon time to create/unpack kernel/initrd is an
  insufficient benchmark for total boot speed. This is because it
  ignores time to load the kernel/initrd, and whether the
  firmware/bootloader were able to stream decompress it whilst loading
  it. I.e. it is argued that in the real world, subsecond decompression
  gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot
  longer than that to read extra 10s of MBs of boot material.

  [TODO]
  Measure pure i/o load speed with stopwatch, to figure out MB/s speed of 
loading initrds/kernel off FAT32, EXT4, TFTP, HTTP.
  Re-evaluate if we should provide different compression mechanisms:
  - ie. gzip instead of lz4 for most cases (revert)
  - ie. xz for painful i/o cases (e.g. netboot)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+subscriptions

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

[Kernel-packages] [Bug 1831736] Re: [MIR] lz4 by default

** Changed in: lz4 (Ubuntu)
   Status: Confirmed => Fix Released

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

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

Title:
  [MIR] lz4 by default

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in live-build package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lz4 package in Ubuntu:
  Fix Released
Status in partman-auto package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  Use `lz4 -9 -l` compression for initramfs by default as discussed on
  ubuntu-devel.

  This would also pull the lz4 package into main

  https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+subscriptions

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

[Kernel-packages] [Bug 1829179] Re: linux-azure: 4.18.0-1019.19~18.04.1 -proposed tracker

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

** 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 1829178 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829180
- phase: Holding before Security
- phase-changed: Thursday, 06. June 2019 11:05 UTC
+ phase: Ready for Security
+ phase-changed: Friday, 07. June 2019 11:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Pending -- ready to copy

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

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

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

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 1829178 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829180
  phase: Ready for Security
  phase-changed: Friday, 07. June 2019 11:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy

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

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

[Kernel-packages] [Bug 1829180] Re: linux-azure: 4.18.0-1019.19 -proposed tracker

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

** 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 1829179 (bionic/linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829186
- phase: Holding before Security
- phase-changed: Thursday, 06. June 2019 11:00 UTC
+ phase: Ready for Security
+ phase-changed: Friday, 07. June 2019 11:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Pending -- ready to copy

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

Title:
  linux-azure: 4.18.0-1019.19 -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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

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 1829179 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829186
  phase: Ready for Security
  phase-changed: Friday, 07. June 2019 11:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy

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

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

[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-06-07 Thread Michael

Hi @kaihengfeng

Yes, mitigations=off works on my ASUS pentium M (banias) machine with with ATI 
Mobility Radeon graphics, for all of 4.15.0-48, 4.15.0-50 and 4.15.0-51.
At the moment, unable to check on the HP6710b laptop this bug was originally 
reported on, as I've loaned it to my brother.

Q: Were you suggesting mitigations=off as a solution (given the
theoretical security vulnerabilities of spectre/meltdown), or just as a
troubleshooting/diagnostic measure?

I'm wondering if I would be better off sticking to 4.15.0-47 with
mitigations on, or allowing other kernel patches with mitigations=off?
Or 64bit linux may be the better solution, where possible/practicable.

Thanks for suggesting the mitigations workaround!!!

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

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE: 
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running. 
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs 
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  
  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try the older kernel.

  
  More Info on what I've already tried for troubleshooting (on the HP6710b) is 
outlined in https://answers.launchpad.net/ubuntu/+question/680486

  Happy to provide more info if needed, but I'm just an end user user
  and new to Linux, so will be on a learning curve at this end.  (and
  apologies in advance if this a user problem, and not an actual bug).
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1681 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May  6 21:16:34 2019
  MachineType: Hewlett-Packard HP Compaq 6710b
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.13
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: SGH8080272
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1034 F pulseaudio
   /dev/snd/controlC0:  michael1034 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  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 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile
   Bus 002

[Kernel-packages] [Bug 1829213] Re: linux-azure: 4.15.0-1046.50~14.04.1 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

** Changed in: kernel-sru-workflow
   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: 1829214
- phase: Holding before Security
- phase-changed: Thursday, 06. June 2019 10:35 UTC
+ phase: Ready for Security
+ phase-changed: Friday, 07. June 2019 10:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Pending -- Ready

** Tags removed: kernel-release-tracking-bug-live

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

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

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1829214
  phase: Ready for Security
  phase-changed: Friday, 07. June 2019 10:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- Ready

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

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

[Kernel-packages] [Bug 1826125]

2019-06-07 Thread Paulo Matos

Apologies, I dropped the ball on this one. I will do that today.

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

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

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

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

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

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

[Kernel-packages] [Bug 1826125]

2019-06-07 Thread Timo Aaltonen

Paulo, please test kernel build -10

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

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

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

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

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

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

[Kernel-packages] [Bug 1831979] Re: linux: -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 1831976 (pc-kernel), bug 1831977 (pc-lowlatency-kernel)
  
  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Friday, 07. June 2019 09:50 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 verification-testing series:
  New
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

  derivatives:bug 1831976 (pc-kernel), bug 1831977 (pc-lowlatency-
  kernel)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Friday, 07. June 2019 09:50 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1829219] Re: linux: 4.15.0-51.55 -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
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
- derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829191 (linux-oem), bug 1829194 (linux-aws), bug 1829200 (linux-gcp), bug 
1829202 (linux-gke-4.15), bug 1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), 
bug 1829210 (linux-oracle), bug 1829211 (linux-fips), bug 1829846 (linux)
+ derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1831978 (linux-oem), bug 1829194 (linux-aws), bug 1829200 (linux-gcp), bug 
1829202 (linux-gke-4.15), bug 1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), 
bug 1829210 (linux-oracle), bug 1829211 (linux-fips), bug 1829846 (linux)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Security
  phase-changed: Wednesday, 05. June 2019 13:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

Title:
  linux: 4.15.0-51.55 -proposed tracker

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

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 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
  derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1831978 (linux-oem), bug 1829194 (linux-aws), bug 1829200 (linux-gcp), bug 
1829202 (linux-gke-4.15), bug 1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), 
bug 1829210 (linux-oracle), bug 1829211 (linux-fips), bug 1829846 (linux)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Security
  phase-changed: Wednesday, 05. June 2019 13:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1831978] Re: linux-oem: -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
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- kernel-stable-master-bug: 1831979
- phase: Holding before Packaging
- phase-changed: Friday, 07. June 2019 10:07 UTC
- reason:
-   prepare-package: Stalled -- waiting for master bug
+ kernel-stable-master-bug: 1829219
  variant: debs

** Tags removed: kernel-sru-derivative-of-1831979
** Tags added: kernel-sru-derivative-of-1829219

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

Title:
  linux-oem:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1829219
  phase: Ready for Packaging
  phase-changed: Friday, 07. June 2019 10:13 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1831978] Re: linux-oem: -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 --
  kernel-stable-master-bug: 1831979
+ phase: Holding before Packaging
+ phase-changed: Friday, 07. June 2019 10:07 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-oem:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1829219
  phase: Ready for Packaging
  phase-changed: Friday, 07. June 2019 10:13 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1831978] Re: linux-oem: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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 --
  kernel-stable-master-bug: 1829219
+ phase: Ready for Packaging
+ phase-changed: Friday, 07. June 2019 10:13 UTC
+ reason:
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-oem:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1829219
  phase: Ready for Packaging
  phase-changed: Friday, 07. June 2019 10:13 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1831979] Re: linux: -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
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- derivatives:bug 1831976 (pc-kernel), bug 1831977 (pc-lowlatency-kernel),
- bug 1831978 (linux-oem)
+ derivatives:bug 1831976 (pc-kernel), bug 1831977 (pc-lowlatency-kernel)
  
  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Friday, 07. June 2019 09:50 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 verification-testing series:
  New
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

  derivatives:bug 1831976 (pc-kernel), bug 1831977 (pc-lowlatency-
  kernel)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Friday, 07. June 2019 09:50 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1829214] Re: linux-azure: 4.15.0-1046.50 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => 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 1829213 (trusty/linux-azure)
  derivatives: bug 1829212 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
- phase: Ready for Release
- phase-changed: Wednesday, 05. June 2019 16:02 UTC
+ phase: Holding before Security
+ phase-changed: Friday, 07. June 2019 10:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-updates: Pending -- ready to copy

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

Title:
  linux-azure: 4.15.0-1046.50 -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:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Holding before Security
  phase-changed: Friday, 07. June 2019 10:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-06-07 Thread Michael Kozma

Hi,

Adding "mitigations=off" to kernel parameters solved issue for me too.

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

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE: 
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running. 
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs 
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  
  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try the older kernel.

  
  More Info on what I've already tried for troubleshooting (on the HP6710b) is 
outlined in https://answers.launchpad.net/ubuntu/+question/680486

  Happy to provide more info if needed, but I'm just an end user user
  and new to Linux, so will be on a learning curve at this end.  (and
  apologies in advance if this a user problem, and not an actual bug).
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1681 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May  6 21:16:34 2019
  MachineType: Hewlett-Packard HP Compaq 6710b
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.13
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: SGH8080272
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1034 F pulseaudio
   /dev/snd/controlC0:  michael1034 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  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 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. W1N
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=5e6f46b1-73a8-4779-bc20-414a46286723 ro forcepae quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A

[Kernel-packages] [Bug 1831979] Re: linux: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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 1831976 (pc-kernel), bug 1831977 (pc-lowlatency-kernel),
  bug 1831978 (linux-oem)
  
  -- swm properties --
+ phase: Ready for Packaging
+ phase-changed: Friday, 07. June 2019 09:50 UTC
+ reason:
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 verification-testing series:
  New
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

  derivatives:bug 1831976 (pc-kernel), bug 1831977 (pc-lowlatency-
  kernel), bug 1831978 (linux-oem)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Friday, 07. June 2019 09:50 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1831978] [NEW] linux-oem: -proposed tracker

Public bug reported:

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 --
kernel-stable-master-bug: 1831979
variant: debs

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem (Ubuntu Bionic)
 Importance: Medium
 Status: New


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.05.13-4 kernel-sru-derivative-of-1831979

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: bionic

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee:

[Kernel-packages] [Bug 1831979] [NEW] linux: -proposed tracker

Public bug reported:

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 1831976 (pc-kernel), bug 1831977 (pc-lowlatency-kernel),
bug 1831978 (linux-oem)

-- swm properties --
phase: Ready for Packaging
phase-changed: Friday, 07. June 2019 09:50 UTC
reason:
  prepare-package: Pending -- version not specified
variant: debs

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: New


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.05.13-4

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: bionic

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

**

[Kernel-packages] [Bug 1829214] Re: linux-azure: 4.15.0-1046.50 -proposed tracker

2019-06-07 Thread Łukasz Zemczak

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

** Changed in: kernel-sru-workflow/promote-to-updates
 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1829214

Title:
  linux-azure: 4.15.0-1046.50 -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:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Ready for Release
  phase-changed: Wednesday, 05. June 2019 16:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy

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

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

[Kernel-packages] [Bug 1829214] Re: linux-azure: 4.15.0-1046.50 -proposed tracker