[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

[Kai-Heng Feng]

The Bluetooth controller wakes up early when USB Controller is trying to
suspend.

Please enable LE privacy before suspend, and see if it helps:
$ btmgmt power off
$ btmgmt privacy on
$ btmgmt power on

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system...
  Apr 02 

[Kernel-packages] [Bug 1823346] Re: SD card stays locked even when unlocked

[Kai-Heng Feng]

Did this ever happen to kernel v4.4, which is kernel for 16.04?

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

Title:
  SD card stays locked even when unlocked

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  After card reader device is used with write-protected SD card, write-
  protection incorrectly persists to future SD cards, even non-protected
  ones.

  To reproduce:
  1) Insert non-protected SD card in card reader (confirm system normal):
  $ sudo hdparm -r /dev/sdd
   /dev/sdd:
readonly  =  0 (off)
  [result is correct]

  2) Eject card, set physical lock on side of card, reinsert:
  $ sudo hdparm -r /dev/sdd
  /dev/sdd:
readonly  =  1 (on)
  [result is correct - card read-only]

  3) Eject card again, unlock card, reinsert
  $ sudo hdparm -r /dev/sdd
  /dev/sdd:
readonly  =  1 (on)
  [result is **incorrect** (card still locked)]

  Because the lock is still set, the device always appears read-only.
  (For example, I cannot "dd" to /dev/sdd)

  Workaround:
  after removing the locked card, issue "sudo hdparm -r0" to turn off the lock. 
 Then insert the unlocked card and the device will appear read/write.

  (I don't know if this is the right package to report against.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-3ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  CustomUdevRuleFiles: 69-basler-cameras.rules 99-realsense-libusb.rules
  Date: Fri Apr  5 14:50:32 2019
  InstallationDate: Installed on 2016-09-28 (919 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Z620 Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=1a9272d2-8838-4bb4-8f63-ce571641c48c ro quiet splash vt.handoff=1
  SourcePackage: udisks2
  Symptom: storage
  Title: No permission to access files on storage device
  UpgradeStatus: Upgraded to bionic on 2019-01-14 (81 days ago)
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.88
  dmi.board.asset.tag: CZC4086C7Q
  dmi.board.name: 158A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.asset.tag: CZC4086C7Q
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z620 Workstation
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1824259

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

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

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

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

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

Title:
  Headphone jack switch sense is inverted: plugging in headphones
  disables headphone output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My machine is a LattePanda board, which uses a "chtrt5645" device as a
  sound card. It has a single headphone output jack, which I think is a
  TRRS jack, with a mic input, such as is normally used on phones.

  When I don't have headphones plugged in, the system thinks headphones
  *are* plugged in. Gnome Control Center shows my audio device as being
  headphones. If I insert a headphone connector partway into the jack, I
  can even get sound in the headphones.

  But if I plug the headphones all the way in, the system decided that I
  have *un*plugged the headphones, and switches output over to
  "Speaker". The system doesn't actually have a speaker, only a
  headphone jack. And when the system switches over to "Speaker", I get
  no sound out of the headphones, even if I open "pavucontrol" and swap
  over to "Headphones (unplugged)" on the "Output Devices" tab.

  This is what "pacmd"'s "list-cards" command says with my headphones
  *unplugged*:

  2 card(s) available.
  index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path = 
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: 
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
  index: 1
name: 
driver: 
owner module: 8
properties:
alsa.card = "0"
alsa.card_name = "chtrt5645"
alsa.long_card_name = 
"AMICorporation-Defaultstring-Defaultstring-CherryTrailCR"
alsa.driver_name = 

[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

[You-Sheng Yang]

Most of the time you need only "linux-image-4.9.0+_4.9.0+-1_amd64.deb".
But if you have also some dkms based modules installed, you may want to
install linux-headers-* as well.

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

Title:
  Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works 
in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel 
Kentsfield QX6800 system with classic BIOS (non UEFI).
  There are no devices connected to PCI USB card during boot.

  The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this
  card during boot (see attached "photo log" with boot and grub
  options). I can't access/login Ubuntu or console. It was checked and
  confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with
  acpi=off option too).

  Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card 
[1033:0194], which was partially workable under my installation of Ubuntu 18.04 
and Windows. It had problems from time to time with FW load from card on start 
and not detecting USB devices connected even if FW present.
  I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] 
which also was partially workable in the same way (other card bios and newer 
NEC chip). System was fully bootable with NEC cards.

  The Etron EJ168 works superb on Windows OS's with directly or with hub 
connections with USB devices.
  I can assist in any way to solve this bug as IT Professional.

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

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

[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output

[Adam Novak]

This is actually a kernel bug, in Linux. The issue is the absence of
platform data for this particular board in the snd_soc_rt5645 module.

The issue can be worked around by creating
/etc/modprobe.d/hacksound.conf with the following contents:

# Invert jack detection (1) and use detection mode 2 (2).
options snd_soc_rt5645 quirk=0x21

This takes advantage of the "quirk" option for the module, added in
https://github.com/torvalds/linux/commit/4999b0214b05a08b42bbafcb29a0b9c413002d3f,
which allows overriding the platform data it usually just has built into
it about how audio jacks are hooked up on particular systems.

It looks like this board needs special system info added to
sound/soc/codecs/rt5645.c, keyed on DMI data. The platform data would
look something like:

static const struct rt5645_platform_data lattepanda_platform_data = {
.jd_mode = 2,
.inv_jd1_1 = true
};

Here's the DMI data for the motherboard; it's a bit generic. I can
provide other DMI data to match on if needed.

Base Board Information
Manufacturer: AMI Corporation
Product Name: Cherry Trail CR
Version: Default string
Serial Number: Default string
Asset Tag: Default string
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Default string
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0


** Package changed: alsa-lib (Ubuntu) => linux (Ubuntu)

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

Title:
  Headphone jack switch sense is inverted: plugging in headphones
  disables headphone output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My machine is a LattePanda board, which uses a "chtrt5645" device as a
  sound card. It has a single headphone output jack, which I think is a
  TRRS jack, with a mic input, such as is normally used on phones.

  When I don't have headphones plugged in, the system thinks headphones
  *are* plugged in. Gnome Control Center shows my audio device as being
  headphones. If I insert a headphone connector partway into the jack, I
  can even get sound in the headphones.

  But if I plug the headphones all the way in, the system decided that I
  have *un*plugged the headphones, and switches output over to
  "Speaker". The system doesn't actually have a speaker, only a
  headphone jack. And when the system switches over to "Speaker", I get
  no sound out of the headphones, even if I open "pavucontrol" and swap
  over to "Headphones (unplugged)" on the "Output Devices" tab.

  This is what "pacmd"'s "list-cards" command says with my headphones
  *unplugged*:

  2 card(s) available.
  index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path = 
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: 
ports:
hdmi-output-0: 

[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

[Mike]

Ok, I have retried to bitsect under main kernel 4.8.0 for 16.04.02 LTS instead 
installed on 4.9-rc8.
Using:
$ git bisect good v4.9-rc8
$ git bisect bad v4.10-rc8
I have built kernel under 4.8.0 with default (Enter) options becouse I don't 
know nuances in them yet.
I have got many files from kernel build and I need advice, what shall I install 
for test:

linux-4.9.0+_4.9.0+-1.debian.tar.gz
linux-4.9.0+_4.9.0+.orig.tar.gz
linux-firmware-image-4.9.0+_4.9.0+-1_amd64.deb
linux-headers-4.9.0+_4.9.0+-1_amd64.deb
linux-image-4.9.0+_4.9.0+-1_amd64.deb
linux-image-4.9.0+-dbg_4.9.0+-1_amd64.deb
linux-libc-dev_4.9.0+-1_amd64.deb

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

Title:
  Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works 
in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel 
Kentsfield QX6800 system with classic BIOS (non UEFI).
  There are no devices connected to PCI USB card during boot.

  The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this
  card during boot (see attached "photo log" with boot and grub
  options). I can't access/login Ubuntu or console. It was checked and
  confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with
  acpi=off option too).

  Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card 
[1033:0194], which was partially workable under my installation of Ubuntu 18.04 
and Windows. It had problems from time to time with FW load from card on start 
and not detecting USB devices connected even if FW present.
  I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] 
which also was partially workable in the same way (other card bios and newer 
NEC chip). System was fully bootable with NEC cards.

  The Etron EJ168 works superb on Windows OS's with directly or with hub 
connections with USB devices.
  I can assist in any way to solve this bug as IT Professional.

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

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

[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output

[Adam Novak]

This may be a kernel driver bug, and a regression from 4.12. See
http://www.lattepanda.com/topic-p24689.html?sid=1fa88916eb19dd9d65e0abd3ecbf6210#p24689

This may be a missing piece of platform data in the kernel that would
tell it to invert jack detection on this particular board. I will try
testing with the functionality added to the kernel in
https://github.com/torvalds/linux/commit/4999b0214b05a08b42bbafcb29a0b9c413002d3f
which lets you tinker with the platform data at runtime.

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

Title:
  Headphone jack switch sense is inverted: plugging in headphones
  disables headphone output

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  My machine is a LattePanda board, which uses a "chtrt5645" device as a
  sound card. It has a single headphone output jack, which I think is a
  TRRS jack, with a mic input, such as is normally used on phones.

  When I don't have headphones plugged in, the system thinks headphones
  *are* plugged in. Gnome Control Center shows my audio device as being
  headphones. If I insert a headphone connector partway into the jack, I
  can even get sound in the headphones.

  But if I plug the headphones all the way in, the system decided that I
  have *un*plugged the headphones, and switches output over to
  "Speaker". The system doesn't actually have a speaker, only a
  headphone jack. And when the system switches over to "Speaker", I get
  no sound out of the headphones, even if I open "pavucontrol" and swap
  over to "Headphones (unplugged)" on the "Output Devices" tab.

  This is what "pacmd"'s "list-cards" command says with my headphones
  *unplugged*:

  2 card(s) available.
  index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path = 
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: 
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
  index: 1
name: 
driver: 
owner module: 8
properties:
alsa.card = "0"
alsa.card_name = "chtrt5645"
alsa.long_card_name = 
"AMICorporation-Defaultstring-Defaultstring-CherryTrailCR"
alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645"
device.bus_path = "platform-cht-bsw-rt5645"
sysfs.path = 

[Kernel-packages] [Bug 1814628] Re: divide error: 0000 with Ubuntu 18.04

[Launchpad Bug Tracker]

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

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

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

Title:
  divide error:  with Ubuntu 18.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  Got a host running lots of virtual machines crashing today with the
  following terminal output (if that's to any help):

  [3430458.298979] divide error:  [#1] SMP PTI
  [3430458.304484] Modules linked in: cpuid vhost_net vhost tap 
nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink 
kvm_intel kvm irqbypass rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace 
sunrpc cachefiles fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge ebtable_filter ebtables ip6table_filter ip6_tables devlink 
iptable_filter 8021q garp mrp stp llc bonding ipmi_ssif intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas intel_cstate 
intel_rapl_perf ipmi_si mei_me ipmi_devintf lpc_ich mei shpchp ipmi_msghandler 
acpi_power_meter mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi
  [3430458.389747]  scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul mgag200 
crc32_pclmul i2c_algo_bit ghash_clmulni_intel ttm pcbc mxm_wmi drm_kms_helper 
bnx2x aesni_intel syscopyarea sysfillrect aes_x86_64 sysimgblt fb_sys_fops 
crypto_simd glue_helper ptp cryptd drm pps_core ahci mdio libahci libcrc32c wmi 
[last unloaded: irqbypass]
  [3430458.440756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-43-generic 
#46-Ubuntu
  [3430458.450411] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 
01/26/2018
  [3430458.460008] RIP: 0010:update_group_capacity+0x19d/0x1f0
  [3430458.467098] RSP: 0018:91043ec03bd8 EFLAGS: 00010247
  [3430458.474207] RAX: 006314d6 RBX: 0001 RCX: 
024d
  [3430458.483490] RDX:  RSI:  RDI: 
00022880
  [3430458.492769] RBP: 91043ec03c00 R08: 9104376dc940 R09: 
1dcd6500
  [3430458.502071] R10: 91043ec0 R11: 0001 R12: 
910437625000
  [3430458.511391] R13: 9104376dc940 R14:  R15: 
91043ec03c30
  [3430458.520724] FS:  () GS:91043ec0() 
knlGS:
  [3430458.531161] CS:  0010 DS:  ES:  CR0: 80050033
  [3430458.538994] CR2: 00010960b008 CR3: 003f8300a002 CR4: 
003626e0
  [3430458.548416] DR0:  DR1:  DR2: 

  [3430458.557858] DR3:  DR6: fffe0ff0 DR7: 
0400
  [3430458.567298] Call Trace:
  [3430458.571507]  
  [3430458.575253]  find_busiest_group+0xff/0x9c0
  [3430458.581327]  load_balance+0x164/0x9c0
  [3430458.586928]  ? sched_clock+0x9/0x10
  [3430458.592347]  ? sched_clock_cpu+0x11/0xb0
  [3430458.598249]  rebalance_domains+0x245/0x2d0
  [3430458.604372]  run_rebalance_domains+0x139/0x1f0
  [3430458.610901]  __do_softirq+0xe4/0x2bb
  [3430458.616459]  irq_exit+0xb8/0xc0
  [3430458.621538]  scheduler_ipi+0xea/0x130
  [3430458.627201]  smp_reschedule_interrupt+0x39/0xe0
  [3430458.633860]  reschedule_interrupt+0x84/0x90
  [3430458.640138]  
  [3430458.644096] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0
  [3430458.651289] RSP: 0018:a90100107e68 EFLAGS: 0246 ORIG_RAX: 
ff02
  [3430458.661431] RAX: 91043ec22880 RBX: 000c2ffbd05252a7 RCX: 
001f
  [3430458.671114] RDX: 000c2ffbd05252a7 RSI: ff1e5f04e459 RDI: 

  [3430458.680819] RBP: a90100107ea8 R08:  R09: 
0d17
  [3430458.690557] R10: a90100107e38 R11: 0eca R12: 
c900ff401f58
  [3430458.700303] R13: 0004 R14: 9bb71d18 R15: 

  [3430458.710075]  ? cpuidle_enter_state+0x97/0x2f0
  [3430458.716723]  cpuidle_enter+0x17/0x20
  [3430458.722455]  call_cpuidle+0x23/0x40
  [3430458.728041]  do_idle+0x18c/0x1f0
  [3430458.733312]  cpu_startup_entry+0x73/0x80
  [3430458.739293]  start_secondary+0x1ab/0x200
  [3430458.745229]  secondary_startup_64+0xa5/0xb0
  [3430458.751415] Code: 34 10 48 8b 96 38 0a 00 00 48 8b 86 30 0a 00 00 48 8b 
b6 a0 09 00 00 49 d1 e9 48 29 d6 ba 00 00 00 00 48 0f 48 f2 31 d2 44 01 ce <48> 
f7 f6 48 3d ff 03 00 00 77 0c ba 00 04 00 00 48 29 c2 48 0f
  [3430458.775397] RIP: update_group_capacity+0x19d/0x1f0 RSP: 91043ec03bd8
  [3430458.784442] ---[ end trace c1ae6368b9740f8a ]---
  [3430458.866540] Kernel panic - not syncing: 

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

[bugproxy]

--- Comment From mranw...@us.ibm.com 2019-04-10 23:12 EDT---
Hi Manoj,

Looks good, I think, here's some output:
mranweil@ltc-wspoon5:~$ cat /proc/version
Linux version 4.15.0-48-generic (buildd@bos02-ppc64el-015) (gcc version 7.3.0 
(Ubuntu 7.3.0-27ubuntu1~18.04)) #51~lp1822870+build.2-Ubuntu SMP Wed Apr 10 
21:12:08 UTC 2019
mranweil@ltc-wspoon5:~$ dmesg |grep count-cache-flush
[0.00] count-cache-flush: hardware assisted flush sequence enabled
mranweil@ltc-wspoon5:~$ grep -H . 
/sys/devices/system/cpu/vulnerabilities/spectre_v2
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Software count 
cache flush (hardware acceleratd)

29:mon> di $_switch 20

c000db54  f8010170  std r0,368(r1)
c000db58  7ee00026  mfcrr23
c000db5c  fae101a0  std r23,416(r1)
c000db60  f823  std r1,0(r3)
c000db64  4bffdb1d  bl  c000b680# 
flush_count_cache+0x0/0x2480
c000db68  3cc06000  lis r6,24576
29:mon> di $flush_count_cache 4d
c000b680  7d2802a6  mflrr9
c000b684  4805  bl  c000b688# 
flush_count_cache+0x8/0x2480
...
c000b784  481c  b   c000b7a0# 
flush_count_cache+0x120/0x2480
c000b788  6000  nop
...
c000b7a0  7d2803a6  mtlrr9
c000b7a4  39207fff  li  r9,32767
c000b7a8  7d2903a6  mtctr   r9
c000b7ac  4c400420  bcctr-  2,lt
c000b7b0  4e800020  blr
29:mon>

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

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

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

[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output

[Adam Novak]

If I save the ALSA state with the headphones unplugged to a file:

sudo alsactl --file=settings-out.txt store

And then plug in the headphones and restore it:

sudo alsactl --file=settings-out.txt restore

I still get no sound. But then diffing the final state against the
unplugged state did find this:

control.175 {
iface CARD
name 'Headphone Jack'
-   value false
+   value true
comment {
access read
type BOOLEAN
count 1
}
}
control.176 {
iface CARD
name 'Headset Mic Jack'
-   value false
+   value true
comment {
access read
type BOOLEAN
count 1
}
}

I need to convince ALSA to report/interpret those boolean jack states
the other way around.

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

Title:
  Headphone jack switch sense is inverted: plugging in headphones
  disables headphone output

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  My machine is a LattePanda board, which uses a "chtrt5645" device as a
  sound card. It has a single headphone output jack, which I think is a
  TRRS jack, with a mic input, such as is normally used on phones.

  When I don't have headphones plugged in, the system thinks headphones
  *are* plugged in. Gnome Control Center shows my audio device as being
  headphones. If I insert a headphone connector partway into the jack, I
  can even get sound in the headphones.

  But if I plug the headphones all the way in, the system decided that I
  have *un*plugged the headphones, and switches output over to
  "Speaker". The system doesn't actually have a speaker, only a
  headphone jack. And when the system switches over to "Speaker", I get
  no sound out of the headphones, even if I open "pavucontrol" and swap
  over to "Headphones (unplugged)" on the "Output Devices" tab.

  This is what "pacmd"'s "list-cards" command says with my headphones
  *unplugged*:

  2 card(s) available.
  index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path = 
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: 
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency 
offset 0 usec, available: no)

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

[Nicolás Abel Carbone]

Suffering from this bug in a Dell XPS 9360 with Killer WiFi. It happened
in 18.10 and still happens in 19.04. :/

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions

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

[Kernel-packages] [Bug 1824259] [NEW] Headphone jack switch sense is inverted: plugging in headphones disables headphone output

[Adam Novak]

Public bug reported:

My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.

When I don't have headphones plugged in, the system thinks headphones
*are* plugged in. Gnome Control Center shows my audio device as being
headphones. If I insert a headphone connector partway into the jack, I
can even get sound in the headphones.

But if I plug the headphones all the way in, the system decided that I
have *un*plugged the headphones, and switches output over to "Speaker".
The system doesn't actually have a speaker, only a headphone jack. And
when the system switches over to "Speaker", I get no sound out of the
headphones, even if I open "pavucontrol" and swap over to "Headphones
(unplugged)" on the "Output Devices" tab.

This is what "pacmd"'s "list-cards" command says with my headphones
*unplugged*:

2 card(s) available.
index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path = 
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: 
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
index: 1
name: 
driver: 
owner module: 8
properties:
alsa.card = "0"
alsa.card_name = "chtrt5645"
alsa.long_card_name = 
"AMICorporation-Defaultstring-Defaultstring-CherryTrailCR"
alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645"
device.bus_path = "platform-cht-bsw-rt5645"
sysfs.path = 
"/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card"
profiles:
HiFi: Default (priority 8000, available: unknown)
off: Off (priority 0, available: unknown)
active profile: 
sinks:

alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink/#0: Built-in Audio 
Headphones + Speaker
sources:

alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink.monitor/#0: 
Monitor of Built-in Audio Headphones + Speaker

alsa_input.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__source/#1: 

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

[Daniel van Vugt]

Hmm, actually, if the problem did get worse or more common in 19.04 then
we should use bug 1822179 instead.

Certainly after July [1], Ubuntu 18.10 won't be relevant any more.

[1] https://wiki.ubuntu.com/Releases

** Summary changed:

- [nvidia] After resume the unlock screen is a black background with pixel 
garbage. Bitmap garbage flashes on the screen when interacting with anything.
+ [nvidia] Corrupted wallpaper after resuming from sleep

** Summary changed:

- [nvidia] Corrupted wallpaper after resuming from sleep
+ [nvidia] Corrupted wallpaper after resuming from suspend

** Tags added: xenial

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend

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

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

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

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

[Joe Barnett]

here's the bottom of journalctl -b -1 from a boot with
"usbcore.dyndbg=+p" that reproduced the issue (let me know if there's a
better way to get the kernel log you're looking for):

Apr 10 17:31:18 taplop systemd-sleep[8074]: Suspending system...
Apr 10 17:31:18 taplop kernel: PM: suspend entry (deep)
Apr 10 17:31:18 taplop kernel: PM: Syncing filesystems ... done.
Apr 10 17:31:20 taplop kernel: Freezing user space processes ... (elapsed 0.004 
seconds) done.
Apr 10 17:31:20 taplop kernel: OOM killer disabled.
Apr 10 17:31:20 taplop kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
Apr 10 17:31:20 taplop kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
Apr 10 17:31:20 taplop kernel: usb usb2: usb auto-resume
Apr 10 17:31:20 taplop kernel: hub 2-0:1.0: hub_resume
Apr 10 17:31:20 taplop kernel: hub 2-0:1.0: hub_suspend
Apr 10 17:31:20 taplop kernel: usb usb2: bus suspend, wakeup 0
Apr 10 17:31:20 taplop kernel: usb 1-6: usb suspend, wakeup 1
Apr 10 17:31:20 taplop kernel: hub 1-0:1.0: hub_suspend
Apr 10 17:31:20 taplop kernel: usb usb1: bus suspend, wakeup 0
Apr 10 17:31:20 taplop kernel: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 
returns -16
Apr 10 17:31:20 taplop kernel: dpm_run_callback(): pci_pm_suspend+0x0/0x130 
returns -16
Apr 10 17:31:20 taplop kernel: PM: Device :00:14.0 failed to suspend async: 
error -16
Apr 10 17:31:20 taplop kernel: PM: Some devices failed to suspend, or early 
wake event detected
Apr 10 17:31:20 taplop kernel: usb usb1: usb resume
Apr 10 17:31:20 taplop kernel: hub 1-0:1.0: hub_resume
Apr 10 17:31:20 taplop kernel: usb usb1-port1: status 0507 change 
Apr 10 17:31:20 taplop kernel: usb usb1-port6: status 0103 change 0004
Apr 10 17:31:20 taplop kernel: usb usb1-port10: status 0107 change 
Apr 10 17:31:20 taplop kernel: usb usb2: usb resume
Apr 10 17:31:20 taplop kernel: hub 2-0:1.0: hub_resume
Apr 10 17:31:20 taplop kernel: usb 1-6: Waited 0ms for CONNECT
Apr 10 17:31:20 taplop kernel: usb 1-6: finish resume
Apr 10 17:31:20 taplop kernel: ACPI: button: The lid device is not compliant to 
SW_LID.
Apr 10 17:31:20 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
Apr 10 17:31:20 taplop kernel: usb 1-1: usb resume
Apr 10 17:31:20 taplop kernel: usb 1-10: usb resume
Apr 10 17:31:20 taplop kernel: usb 1-1: Waited 0ms for CONNECT
Apr 10 17:31:20 taplop kernel: usb 1-1: finish resume
Apr 10 17:31:20 taplop kernel: usb 1-10: Waited 0ms for CONNECT
Apr 10 17:31:20 taplop kernel: usb 1-10: finish resume
Apr 10 17:31:20 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
Apr 10 17:31:20 taplop kernel: nvme nvme0: 8/0/0 default/read/poll queues
Apr 10 17:31:20 taplop kernel: [drm] VCE initialized successfully.
Apr 10 17:31:20 taplop kernel: OOM killer enabled.
Apr 10 17:31:20 taplop kernel: Restarting tasks ... 
Apr 10 17:31:20 taplop kernel: hub 2-0:1.0: state 7 ports 8 chg  evt 
Apr 10 17:31:20 taplop kernel: hub 1-0:1.0: state 7 ports 16 chg 0040 evt 0402
Apr 10 17:31:20 taplop kernel: usb usb1-port6: status 0103, change , 12 Mb/s
Apr 10 17:31:20 taplop kernel: hub 2-0:1.0: hub_suspend
Apr 10 17:31:20 taplop kernel: usb usb2: bus auto-suspend, wakeup 1
Apr 10 17:31:20 taplop kernel: done.

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:  

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

[Joe Barnett]

** Attachment added: "full kernel log from that boot extracted via: journalctl 
-b-1 -k > kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823029/+attachment/5254820/+files/kern.log

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system...
  Apr 02 

[Kernel-packages] [Bug 1822870] Could you please test the PPA kernel?

[Manoj Iyer]

Michael,

I have test kernel with the patches cherry-picked/backported to 4.15 
bionic. We do not have a dd2.3 hw in-house, could you please validate that 
this kernel works for you and report back in the bug report?

https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/lp1822870/

Once I get the validation results I can send a pull request to the kernel 
team.

Thanks
--

Manoj Iyer
Ubuntu/Canonical


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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

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

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

[Kernel-packages] [Bug 1715552] Re: VMWare does not start

[John Drake]

Running Ubuntu 18.04.1 LTS with Workstation 12.5.9 installed.
Encountered the dreaded error:

/usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
symbol `clock_gettime'

Following @iLugo directions exactly, VMware Workstation is now working.

I followed the git clone directions, checked out the workstation-12.5.9
branch, ran make and make install. Don't forget step 4 above!

Once completing this patching, VMware workstation starts and runs
perfectly.

Absolutely a life saver. 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/1715552

Title:
  VMWare does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started:

  /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
  gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
  symbol `clock_gettime'

  Works under Ubuntu 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   9336 F pulseaudio
   /dev/snd/controlC0:  wolf   9336 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 07:53:43 2017
  HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-13-generic N/A
   linux-backports-modules-4.12.0-13-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1823220] Re: linux-azure: 5.0.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1823936
- phase: Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 19:41 UTC
+ phase: Testing
+ phase-changed: Wednesday, 10. April 2019 21:40 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   stakeholder-signoff: Pending -- waiting for signoff

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

Title:
  linux-azure: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  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: 1823936
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 21:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

Might be a duplicate of this bug?:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1823221] Re: linux-gcp: 5.0.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1823936
- phase: Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 19:42 UTC
+ phase: Testing
+ phase-changed: Wednesday, 10. April 2019 21:40 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
+   regression-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  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: 1823936
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 21:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1823936] Re: linux: 5.0.0-10.11 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1823224 (bionic/linux-hwe-edge), bug 1824008 
(bionic/linux-oem-osp1)
  derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 
(linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 
(linux-snapdragon)
  
  -- swm properties --
- phase: Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 19:34 UTC
+ phase: Testing
+ phase-changed: Wednesday, 10. April 2019 21:33 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress

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

Title:
  linux: 5.0.0-10.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1823224 (bionic/linux-hwe-edge), bug 1824008 
(bionic/linux-oem-osp1)
  derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 
(linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 
(linux-snapdragon)

  -- swm properties --
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 21:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1823222] Re: linux-kvm: 5.0.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1823936
- phase: Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 19:42 UTC
+ phase: Testing
+ phase-changed: Wednesday, 10. April 2019 21:10 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  New
Status in linux-kvm source package in Disco:
  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: 1823936
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 21:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1823219] Re: linux-aws: 5.0.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1823936
- phase: Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 19:41 UTC
+ phase: Testing
+ phase-changed: Wednesday, 10. April 2019 21:10 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  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: 1823936
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 21:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1823218] Re: linux-raspi2: 5.0.0-1005.5 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1823936
- phase: Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 19:41 UTC
+ phase: Testing
+ phase-changed: Wednesday, 10. April 2019 21:10 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Disco:
  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: 1823936
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 21:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

Here's a link to the Fedora bug report tracking the same issue:

https://bugzilla.redhat.com/show_bug.cgi?id=1695275 which also includes
lots of useful information.

** Bug watch added: Red Hat Bugzilla #1695275
   https://bugzilla.redhat.com/show_bug.cgi?id=1695275

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

Unfortunately due to the nature of this bug, it's very hard to get any
concrete logs (at least I'm not sure how to).  If I boot with kernel
modesetting for i915, then I can't even get to the ttys to pull down a
dmesg.  I'd rather not install 19.04 (wiping out my existing 18.10
installation) to track down the logs.  The links that I provided do
contain very detailed information about the problem.  I've also
confirmed that Fedora 30 beta also has the same problems - although
there's a proposed patch/fix with kernel 5.0.7 that might make it in
before release.

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** 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: 1822834
- phase: Holding before Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 18:39 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 20:38 UTC
  reason:
-   promote-to-proposed: Holding -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

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

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 20:38 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1824233] [NEW] linux-signed is still producing snapdragon packages

[Seth Forshee]

Public bug reported:

SRU Justification

Impact: Support for snapdragon was split out from the linux package into
a linux-snapdragon package, so linux-signed should no longer produce any
packages for snapdragon. They aren't causing problems currently but need
to be removed.

Fix: Remove the snapdragon packages from linux-signed.

Regression Potential: There should be no chance for regressions, the
snapdragon meta packages will refer to kernels build from linux-
snapdragon.

** Affects: linux-signed (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: linux-signed (Ubuntu Disco)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Also affects: linux-signed (Ubuntu Disco)
   Importance: Medium
 Assignee: Seth Forshee (sforshee)
   Status: In Progress

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

Title:
  linux-signed is still producing snapdragon packages

Status in linux-signed package in Ubuntu:
  In Progress
Status in linux-signed source package in Disco:
  In Progress

Bug description:
  SRU Justification

  Impact: Support for snapdragon was split out from the linux package
  into a linux-snapdragon package, so linux-signed should no longer
  produce any packages for snapdragon. They aren't causing problems
  currently but need to be removed.

  Fix: Remove the snapdragon packages from linux-signed.

  Regression Potential: There should be no chance for regressions, the
  snapdragon meta packages will refer to kernels build from linux-
  snapdragon.

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

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

[Kernel-packages] [Bug 1821152] Re: LXC test on KVM instances failed with Temporary failure resolving 'archive.ubuntu.com'

[Sean Feole]

** Tags added: aws azure bionic

** Tags removed: aws
** Tags added: kvm

** Summary changed:

- LXC test on KVM instances failed with Temporary failure resolving 
'archive.ubuntu.com'
+ lxc-test-no-new-privs failed with Temporary failure resolving 
'archive.ubuntu.com'

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

Title:
  lxc-test-no-new-privs failed with Temporary failure resolving
  'archive.ubuntu.com'

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  It seems this failure only exist in KVM instances.

FAIL: lxc-tests: lxc-test-no-new-privs (37s)
---
+ DONE=0
+ trap cleanup EXIT SIGHUP SIGINT SIGTERM
+ mkdir -p /etc/lxc/
+ cat
+ ARCH=i386
+ type dpkg
++ dpkg --print-architecture
+ ARCH=amd64
+ lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
Setting up the GPG keyring
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created an Ubuntu xenial amd64 (20190320_07:42) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
+ echo 'lxc.no_new_privs = 1'
+ lxc-start -n c1
++ lxc-info -n c1 -p -H
+ p1=8818
+ '[' 8818 '!=' -1 ']'
+ sleep 5s
+ lxc-attach -n c1 --clear-env -- apt update -y

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
+ lxc-attach -n c1 --clear-env -- apt install -y gcc make

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev 
libcc1-0
  libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 
libmpfr4
  libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages 
manpages-dev
Suggested packages:
  binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool
  flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg
  libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
  libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc
  make-doc man-browser
The following NEW packages will be installed:
  binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev
  libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 
libmpc3
  libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make
  manpages manpages-dev
0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.7 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 
3.1.4-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 
1.0.3-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2
  Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils 
amd64 2.26.1-1ubuntu1~16.04.8
  Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 
0.16.1-1
  Temporary failure resolving 'archive.ubuntu.com'

  
  It's a bit weird that if I run the command manually, it looks OK
  lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
  lxc-start -n c1
  lxc-attach -n c1 

[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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
  
  derivatives: bug 1822789 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow 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:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  derivatives: bug 1822789 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow 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:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  derivatives: bug 1822789 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests

[Sean Feole]

also affects bionic, linux-azure 4.18.0-1015.15~18.04.1

** Tags added: bionic

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

Title:
  ept test fails in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  Reproducible: Yes,
  Series: cosmic
  Kernel: "linux-azure 4.18.0-1015.15"
  Steps:

  1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,host-phys-bits,+vmx -m 2560 -append "ept_access*"
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 
1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd 
/tmp/tmp.RcwfbGP5Ou
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 477000
  cr4 = 20

  Test suite: ept_access_test_not_present

  Test suite: ept_access_test_read_only

  Test suite: ept_access_test_write_only

  Test suite: ept_access_test_read_write

  Test suite: ept_access_test_execute_only

  Test suite: ept_access_test_read_execute

  Test suite: ept_access_test_write_execute

  Test suite: ept_access_test_read_write_execute

  Test suite: ept_access_test_reserved_bits

  Test suite: ept_access_test_ignored_bits

  Test suite: ept_access_test_paddr_not_present_ad_disabled

  Test suite: ept_access_test_paddr_not_present_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_only_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312

  Test suite: ept_access_test_paddr_read_only_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_write

  Test suite: ept_access_test_paddr_read_write_execute

  Test suite: ept_access_test_paddr_read_execute_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fe15 401577 4039d0 

[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** 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: 1822808
- phase: Holding before Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 15:12 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 20:11 UTC
  reason:
-   promote-to-proposed: Holding -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822808
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 20:11 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1823221] Re: linux-gcp: 5.0.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1823936
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:42 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-gcp: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  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: 1823936
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:42 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1823220] Re: linux-azure: 5.0.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1823936
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:41 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-azure: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  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: 1823936
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:41 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1823936] Re: linux: 5.0.0-10.11 -proposed tracker

[Ubuntu Kernel Bot]

** 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 1823224 (bionic/linux-hwe-edge), bug 1824008 
(bionic/linux-oem-osp1)
  derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 
(linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 
(linux-snapdragon)
  
  -- swm properties --
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:34 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux: 5.0.0-10.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1823224 (bionic/linux-hwe-edge), bug 1824008 
(bionic/linux-oem-osp1)
  derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 
(linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 
(linux-snapdragon)

  -- swm properties --
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:34 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1821152] Re: LXC test on KVM instances failed with Temporary failure resolving 'archive.ubuntu.com'

[Sean Feole]

appears to affect linux-azure: 4.18.0-1015.15, Standard_F2s_v2-ubuntu_lxc
04/05 16:42:33 DEBUG| utils:0153| [stdout] FAIL: lxc-tests: 
lxc-test-no-new-privs (37s)


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

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

Title:
  LXC test on KVM instances failed with Temporary failure resolving
  'archive.ubuntu.com'

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  It seems this failure only exist in KVM instances.

FAIL: lxc-tests: lxc-test-no-new-privs (37s)
---
+ DONE=0
+ trap cleanup EXIT SIGHUP SIGINT SIGTERM
+ mkdir -p /etc/lxc/
+ cat
+ ARCH=i386
+ type dpkg
++ dpkg --print-architecture
+ ARCH=amd64
+ lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
Setting up the GPG keyring
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created an Ubuntu xenial amd64 (20190320_07:42) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
+ echo 'lxc.no_new_privs = 1'
+ lxc-start -n c1
++ lxc-info -n c1 -p -H
+ p1=8818
+ '[' 8818 '!=' -1 ']'
+ sleep 5s
+ lxc-attach -n c1 --clear-env -- apt update -y

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
+ lxc-attach -n c1 --clear-env -- apt install -y gcc make

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev 
libcc1-0
  libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 
libmpfr4
  libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages 
manpages-dev
Suggested packages:
  binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool
  flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg
  libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
  libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc
  make-doc man-browser
The following NEW packages will be installed:
  binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev
  libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 
libmpc3
  libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make
  manpages manpages-dev
0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.7 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 
3.1.4-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 
1.0.3-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2
  Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils 
amd64 2.26.1-1ubuntu1~16.04.8
  Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 
0.16.1-1
  Temporary failure resolving 'archive.ubuntu.com'

  
  It's a bit weird that if I run the command manually, it looks OK
  lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
  lxc-start -n c1
  lxc-attach -n c1 --clear-env -- apt 

[Kernel-packages] [Bug 1822791] Re: linux-azure: 4.18.0-1015.15 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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 1822790 (bionic/linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Thursday, 04. April 2019 17:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822790 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Thursday, 04. April 2019 17:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822791] Re: linux-azure: 4.18.0-1015.15 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

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

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822790 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Thursday, 04. April 2019 17:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824008] Re: linux-oem-osp1: 5.0.0-1002.3 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** 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: 1823936
- phase: Holding before Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 05:10 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 19:43 UTC
  reason:
-   promote-to-proposed: Holding -- master bug not ready for proposed
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-oem-osp1: 5.0.0-1002.3 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1823936
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:43 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1823222] Re: linux-kvm: 5.0.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

** Tags added: block-proposed-disco

** Tags added: block-proposed

** 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: 1823936
- phase: Packaging
- phase-changed: Tuesday, 09. April 2019 20:42 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 19:42 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-kvm: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-kvm source package in Disco:
  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: 1823936
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:42 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1823219] Re: linux-aws: 5.0.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

** Tags added: block-proposed-disco

** Tags added: block-proposed

** 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: 1823936
- phase: Packaging
- phase-changed: Tuesday, 09. April 2019 16:10 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 19:41 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-aws: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  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: 1823936
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:41 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1823221] Re: linux-gcp: 5.0.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

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

** Tags added: block-proposed-disco

** Tags added: block-proposed

** 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: 1823936
- phase: Packaging
- phase-changed: Wednesday, 10. April 2019 13:10 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 19:42 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

Title:
  linux-gcp: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  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: 1823936
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:42 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

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

[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests

[Sean Feole]

Affected instances:
Standard_D2s_v3
Standard_D2_v3
Standard_DC2s
Standard_E2s_v3
Standard_F2s_v2

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

Title:
  ept test fails in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  Reproducible: Yes,
  Series: cosmic
  Kernel: "linux-azure 4.18.0-1015.15"
  Steps:

  1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,host-phys-bits,+vmx -m 2560 -append "ept_access*"
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 
1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd 
/tmp/tmp.RcwfbGP5Ou
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 477000
  cr4 = 20

  Test suite: ept_access_test_not_present

  Test suite: ept_access_test_read_only

  Test suite: ept_access_test_write_only

  Test suite: ept_access_test_read_write

  Test suite: ept_access_test_execute_only

  Test suite: ept_access_test_read_execute

  Test suite: ept_access_test_write_execute

  Test suite: ept_access_test_read_write_execute

  Test suite: ept_access_test_reserved_bits

  Test suite: ept_access_test_ignored_bits

  Test suite: ept_access_test_paddr_not_present_ad_disabled

  Test suite: ept_access_test_paddr_not_present_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_only_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312

  Test suite: ept_access_test_paddr_read_only_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_write

  Test suite: ept_access_test_paddr_read_write_execute

  Test suite: ept_access_test_paddr_read_execute_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 

[Kernel-packages] [Bug 1823220] Re: linux-azure: 5.0.0-1002.2 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

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

** Tags added: block-proposed-disco

** Tags added: block-proposed

** 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: 1823936
- phase: Packaging
- phase-changed: Tuesday, 09. April 2019 18:41 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 19:41 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

Title:
  linux-azure: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  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: 1823936
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:41 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

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

[Kernel-packages] [Bug 1823218] Re: linux-raspi2: 5.0.0-1005.5 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

** Tags added: block-proposed-disco

** Tags added: block-proposed

** 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: 1823936
- phase: Packaging
- phase-changed: Tuesday, 09. April 2019 21:11 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 19:41 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Disco:
  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: 1823936
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:41 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1824228] [NEW] ept test fails in kvm_unit_tests

[Sean Feole]

Public bug reported:

Reproducible: Yes,
Series: cosmic
Kernel: "linux-azure 4.18.0-1015.15"
Steps:

1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib
2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
3.) cd kvm-unit-tests; ./configure; make
4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,host-phys-bits,+vmx -m 2560 -append "ept_access*"
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu 
host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd 
/tmp/tmp.RcwfbGP5Ou
enabling apic
paging enabled
cr0 = 80010011
cr3 = 477000
cr4 = 20

Test suite: ept_access_test_not_present

Test suite: ept_access_test_read_only

Test suite: ept_access_test_write_only

Test suite: ept_access_test_read_write

Test suite: ept_access_test_execute_only

Test suite: ept_access_test_read_execute

Test suite: ept_access_test_write_execute

Test suite: ept_access_test_read_write_execute

Test suite: ept_access_test_reserved_bits

Test suite: ept_access_test_ignored_bits

Test suite: ept_access_test_paddr_not_present_ad_disabled

Test suite: ept_access_test_paddr_not_present_ad_enabled
Host skipping test: EPT AD bits not supported.

Test suite: ept_access_test_paddr_read_only_ad_disabled
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312

Test suite: ept_access_test_paddr_read_only_ad_enabled
Host skipping test: EPT AD bits not supported.

Test suite: ept_access_test_paddr_read_write

Test suite: ept_access_test_paddr_read_write_execute

Test suite: ept_access_test_paddr_read_execute_ad_disabled
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fe15 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fe42 401577 4039d0 400312

Test suite: ept_access_test_paddr_read_execute_ad_enabled

[Kernel-packages] [Bug 1823936] Re: linux: 5.0.0-10.11 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

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

** Tags added: block-proposed-disco

** Tags added: block-proposed

** 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 1823224 (bionic/linux-hwe-edge), bug 1824008 
(bionic/linux-oem-osp1)
  derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 
(linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 
(linux-snapdragon)
  
  -- swm properties --
- phase: Packaging
- phase-changed: Tuesday, 09. April 2019 13:42 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 19:34 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

Title:
  linux: 5.0.0-10.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1823224 (bionic/linux-hwe-edge), bug 1824008 
(bionic/linux-oem-osp1)
  derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 
(linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 
(linux-snapdragon)

  -- swm properties --
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 19:34 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1824216

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

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

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

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

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

[Sean Feole]

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

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

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
  FAIL: Enable-EPT 

[Kernel-packages] [Bug 1824216] [NEW] Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

Public bug reported:

On my Dell XPS 9575, I get a black screen on boot when running the 19.04
live image, OR after updating from 18.10 to 19.04.  It appears to be a
kernel related bug that was introduced in 5.0 that is affected by
certain laptop panels not conforming to their stated specifications.

Several other Dell systems exhibit the same issue, and it's very
possible that there are other panels used on other systems that will
also have the same issues.

Intel is aware of this issue and has already created a patch.  You can
see the relevant threads here:

https://bugs.freedesktop.org/show_bug.cgi?id=109959

And the patch here:

https://patchwork.freedesktop.org/patch/296411/

It would be fantastic to get this patch applied before release, as it
would be very difficult install 19.04 on the affected systems otherwise.
I was able to get the live image booted by adding the nomodeset kernel
parameter to grub, so as a work around you can use this approach to
install.

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


** Tags: disco

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  New

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
- phase: Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 17:08 UTC
+ phase: Testing
+ phase-changed: Wednesday, 10. April 2019 18:38 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): amd64:latest/beta'
+   snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): amd64:latest/edge'
+   verification-testing: Ongoing -- testing in progress

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

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

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 18:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): amd64:latest/beta'
snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): amd64:latest/edge'
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   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 --
  kernel-stable-master-bug: 1822834
- phase: Packaging
- phase-changed: Tuesday, 09. April 2019 23:09 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 18:39 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Holding -- builds not complete

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1822834
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 18:39 UTC
  reason:
promote-to-proposed: Holding -- builds not complete

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

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

[Kernel-packages] [Bug 1822832] Re: linux-aws: 4.4.0-1041.44 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 17:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1822834
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 17:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops

[dann frazier]

On Wed, Apr 10, 2019 at 11:01 AM Ard Biesheuvel
 wrote:
>
> On Tue, 9 Apr 2019 at 16:30, dann frazier  wrote:
> >
> > Yeah, no crash anymore - thanks Ard!
> >
> > ubuntu@d06-4:~$ echo function | sudo tee 
> > /sys/kernel/debug/tracing/current_tracer
> > function
> > [   72.778123] ftrace: far branches to multiple entry points unsupported 
> > inside a single module
> >
> > ^ I assume this is expected
> >
>
> Uhm, not really.

:(

> You don't have any out of tree live patching code in your kernel,
right?

I see the same behavior w/ just-this-patch on top of upstream:

[  431.876690] ftrace: far branches to multiple entry points
unsupported inside a single module
[  431.885157] WARNING: CPU: 21 PID: 3388 at
kernel/trace/ftrace.c:2008 ftrace_bug+0xb0/0x2b0
[  431.885158] Modules linked in: nls_iso8859_1 ipmi_ssif joydev
input_leds hns_roce_hw_v2 hns_roce ipmi_si ib_uverbs tpm_tis_spi
ipmi_devintf ipmi_msghandler spi_dw_mmio spi_dw cppc_cpufreq
sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp
libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4
ses enclosure btrfs zstd_compress raid10 raid456 async_raid6_recov
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq
libcrc32c raid1 raid0 multipath linear marvell aes_ce_blk
aes_ce_cipher hid_generic hibmc_drm crct10dif_ce ttm ghash_ce
drm_kms_helper sha2_ce syscopyarea sha256_arm64 sysfillrect sha1_ce
hisi_sas_v3_hw sysimgblt ixgbe usbhid hns3 fb_sys_fops hisi_sas_main
igb drm hclge libsas i2c_algo_bit hid xfrm_algo ahci mdio hnae3
scsi_transport_sas libahci hinic gpio_dwapb aes_neon_bs aes_neon_blk
crypto_simd cryptd aes_arm64
[  431.885213] CPU: 21 PID: 3388 Comm: tee Not tainted 5.1.0-rc4+ #79
[  431.885215] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA
BIOS 2280-A CS V2.17.01 03/30/2019
[  431.885217] pstate: 6049 (nZCv daif +PAN -UAO)
[  431.885219] pc : ftrace_bug+0xb0/0x2b0
[  431.885221] lr : ftrace_replace_code+0xa8/0xc0
[  431.885222] sp : 20d6bb20
[  431.885223] x29: 20d6bb20 x28: 97b7828e1d80
[  431.885225] x27:  x26: 
[  431.885227] x25: e3d7c228 x24: 20d6bd13
[  431.885229] x23: 0002 x22: 0001
[  431.885231] x21: 3ed411993928 x20: 97b7c5810010
[  431.885232] x19: 97b7c5810010 x18: 
[  431.885234] x17:  x16: 3ed4ff397168
[  431.885236] x15: 3ed50005c708 x14: 7320612065646973
[  431.885237] x13: 6e6920646574726f x12: 707075736e752073
[  431.885239] x11: 746e696f70207972 x10: 746e6520656c7069
[  431.885241] x9 : 3ed50005d168 x8 : 3ed4ff141588
[  431.885243] x7 : 0945 x6 : 3ed500095308
[  431.885244] x5 : 97b7cfaef150 x4 : 3ed4feba7480
[  431.885246] x3 :  x2 : 12122b60e4976500
[  431.885248] x1 : 97b7c5810010 x0 : ffea
[  431.885250] Call trace:
[  431.885252]  ftrace_bug+0xb0/0x2b0
[  431.885254]  ftrace_replace_code+0xa8/0xc0
[  431.885256]  ftrace_modify_all_code+0xc8/0x160
[  431.885262]  arch_ftrace_update_code+0x10/0x18
[  431.885264]  ftrace_run_update_code+0x20/0x70
[  431.885266]  ftrace_startup_enable+0x4c/0x58
[  431.885268]  ftrace_startup+0xa4/0x140
[  431.885270]  register_ftrace_function+0x64/0x80
[  431.885272]  function_trace_init+0x50/0x98
[  431.885275]  tracing_set_tracer+0x124/0x200
[  431.885277]  tracing_set_trace_write+0x10c/0x168
[  431.885280]  __vfs_write+0x48/0x80
[  431.885281]  vfs_write+0xac/0x1b8
[  431.885283]  ksys_write+0x74/0xf0
[  431.885284]  __arm64_sys_write+0x24/0x30
[  431.885286]  el0_svc_common+0x74/0x118
[  431.885288]  el0_svc_handler+0x38/0x78
[  431.885290]  el0_svc+0x8/0xc
[  431.885292] ---[ end trace d418734dc3074a2a ]---
[  431.885294] ftrace failed to modify
[  431.885297] [] aes_decrypt+0x20/0x50 [aes_arm64]
[  431.885298]  actual:   1f:20:03:d5
[  431.885302] Setting ftrace call site to call ftrace function
[  431.885303] ftrace record flags: 8001
[  431.885304]  (1)
expected tramp: 3ed4fea40c24


** Attachment added: ".config"
   https://bugs.launchpad.net/bugs/1822871/+attachment/5254769/+files/.config

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

Title:
  enabling ftrace on Hi1620 CS causes an Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Attempting to enable the function tracer causes an Oops. This impacts the 
current disco kernel, as well as latest upstream 
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).

  This is 100% reproducible on D06 CS systems, but not reproducible on
  D06 ES systems (the previous silicon rev).

  [Test Case]
  $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer

  [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
  [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
  [ 3125.661551] Modules linked in: 

[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

[decimus]

Ok, I meant "still present in Ubuntu 19.04" in the last comment :D

Also worth mentioning: the "sudo modprobe i2c-i801" fix also restores
the two-finger-tap right clicking behavior, which was also broken
alongside two-finger scrolling. But there was no three-finger-tapping
instead, so unlike the case how two-finger-scrolling broke.

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

Title:
  Two-finger scrolling no longer works after resuming from suspend

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

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

[decimus]

For Robin (brobert420), who in comment #69:

> Commenting out blacklist i2c_i801 did end with mouse not working at all after 
> wakeup […]. I got an L440. Ubuntu 18.04 4.19rc1

I had the same problem with a ThinkPad T440s on Ubuntu 19.10 beta. (Just
that there was no blacklist entry in /etc/modprobe.d/blacklist.conf so I
used "modprobe i2c_i801" instead.)

However, when I instead use the module name with a "-" instead of "_":

modprobe i2c-i801

then it works immediately to restore two-finger scrolling, and two-
finger scrolling keeps working after a suspend-and-resume cycle.

In other news, this bug is still present in Ubuntu 19.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/1722478

Title:
  Two-finger scrolling no longer works after resuming from suspend

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

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

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

[Bug Watch Updater]

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

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

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

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

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

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

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

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

  I attached a kernel log.

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

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

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

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

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

[Kernel-packages] [Bug 1747463]

[alexdeucher]

https://bugs.freedesktop.org/show_bug.cgi?id=110360

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

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

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

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

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

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

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

  I attached a kernel log.

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

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

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

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

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

[Kernel-packages] [Bug 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops

[dann frazier]

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

Title:
  enabling ftrace on Hi1620 CS causes an Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Attempting to enable the function tracer causes an Oops. This impacts the 
current disco kernel, as well as latest upstream 
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).

  This is 100% reproducible on D06 CS systems, but not reproducible on
  D06 ES systems (the previous silicon rev).

  [Test Case]
  $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer

  [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
  [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
  [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds 
tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw 
ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher hibmc_drm 
hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce syscopyarea 
sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid fb_sys_fops 
hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio hid drm hnae3 
libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs aes_neon_blk 
crypto_simd cryptd aes_arm64
  [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12
  [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 
2280-A CS V2.16.01 03/16/2019
  [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO)
  [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80
  [ 3125.766979] sp : 2837b9f0
  [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880
  [ 3125.775591] x27:  x26: 
  [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000
  [ 3125.786200] x23: 0002 x22: 3dce9d2289a4
  [ 3125.791504] x21: 2837ba8c x20: 2837b000
  [ 3125.796808] x19: 3dce9d228000 x18: 
  [ 3125.802112] x17:  x16: 3dceb7742780
  [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001
  [ 3125.812720] x13: bef50bb9e188 x12: 
  [ 3125.818023] x11: 7efba3e79608 x10: 0a70
  [ 3125.823327] x9 : 3dceb6deeacc x8 : 
  [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10
  [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8
  [ 3125.839239] x3 :  x2 : 9000
  [ 3125.844543] x1 :  x0 : 
  [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476)
  [ 3125.856281] Call trace:
  [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.863593] plt_entries_equal.part.3+0x40/0x80
  [ 3125.868115] plt_entries_equal+0x5c/0x70
  [ 3125.872031] ftrace_make_call+0xf0/0x150
  [ 3125.875950] __ftrace_replace_code+0xe8/0xf8
  [ 3125.880212] ftrace_replace_code+0x64/0xc0
  [ 3125.884301] ftrace_modify_all_code+0xb0/0x148
  [ 3125.888738] arch_ftrace_update_code+0x10/0x18
  [ 3125.893174] ftrace_run_update_code+0x20/0x70
  [ 3125.897524] ftrace_startup_enable+0x4c/0x58
  [ 3125.901788] ftrace_startup+0xa4/0x140
  [ 3125.905531] register_ftrace_function+0x64/0x80
  [ 3125.910059] function_trace_init+0x50/0x98
  [ 3125.914149] tracing_set_tracer+0xf4/0x1c0
  [ 3125.918238] tracing_set_trace_write+0x10c/0x168
  [ 3125.922852] __vfs_write+0x60/0x1a8
  [ 3125.926333] vfs_write+0xac/0x1b8
  [ 3125.929641] ksys_write+0x6c/0xd8
  [ 3125.932949] __arm64_sys_write+0x24/0x30
  [ 3125.936866] el0_svc_common+0x78/0x120
  [ 3125.940608] el0_svc_handler+0x38/0x78
  [ 3125.944349] el0_svc+0x8/0xc
  [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421)
  [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]---

  [Fix]
  TBD

  [Regression Risk]
  TBD

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

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

[Kernel-packages] [Bug 1747463]

[alexdeucher]

Does booting with amdgpu.runpm=0 on the kernel command line help?

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

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

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

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

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

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

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

  I attached a kernel log.

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

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

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

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

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

[Kernel-packages] [Bug 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR

[Launay Théo]

I searched a bit about the changes in the kernel. I've found that : 
https://lore.kernel.org/patchwork/patch/1030491/

I don't know the C language but if it can help.

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

Title:
  Internal microphone not working on Lenovo Ideapad 330S-15ARR

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

Bug description:
  The internal microphone on this troublesome laptop stopped working
  after upgrading from Bionic to Cosmic.  There is no signal from the
  microphone with kernel 4.18.0-7 or 4.18.0-8.

  This DOES work correctly with kernel 4.15.0-34 that is still present
  on Cosmic after the upgrade.

  I recommend Canonical gets this laptop for testing since a ton of
  stuff is troublesome on this Raven Ridge laptop.  Would be a good
  specimen to get support for this platform improved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2295 F pulseaudio
   /dev/snd/controlC0:  xorbit 2295 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct  7 12:02:45 2018
  InstallationDate: Installed on 2018-09-20 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago)
  dmi.bios.date: 09/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN26WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1824211] Re: Ubiquity in 18.04.2 does not install nvidia driver when requested to do so

[Will Cooke]

This is probably a packaging problem on the nvidia drivers rather than a
bug in Ubiquiuty.  Moving there for more ideas.


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

** No longer affects: ubiquity (Ubuntu)

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

Title:
  Ubiquity in 18.04.2 does not install nvidia driver when requested to
  do so

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

Bug description:
  Installed 18.04.2 on a laptop with nvidia GTX 960.
  I enabled wireless network and ticked the box to install 3rd party 
proprietary stuff.
  Rebooted to the installed system and found no nvidia driver installed.

  Found this in the installer/syslog (full syslog attached)

  Apr 10 16:44:54 ubuntu ubiquity: The following packages have unmet 
dependencies:
  Apr 10 16:44:54 ubuntu ubiquity:  nvidia-driver-390 : Depends: 
xserver-xorg-video-nvidia-390 (= 390.77-0ubuntu0.18.04.1) but it is not going 
to be installed
  Apr 10 16:44:54 ubuntu ubiquity:  Recommends: 
libnvidia-compute-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable
  Apr 10 16:44:54 ubuntu ubiquity:  Recommends: 
libnvidia-decode-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable
  Apr 10 16:44:54 ubuntu ubiquity:  Recommends: 
libnvidia-encode-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable
  Apr 10 16:44:54 ubuntu ubiquity:  Recommends: 
libnvidia-ifr1-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable
  Apr 10 16:44:54 ubuntu ubiquity:  Recommends: 
libnvidia-fbc1-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable
  Apr 10 16:44:54 ubuntu ubiquity:  Recommends: 
libnvidia-gl-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable
  Apr 10 16:44:54 ubuntu ubiquity: E
  Apr 10 16:44:54 ubuntu ubiquity: : Unable to correct problems, you have held 
broken packages.
  Apr 10 16:44:54 ubuntu ubiquity: ubuntu-drivers autoinstall failed with code: 
100

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:01:03 2019
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb
  InstallationDate: Installed on 2019-04-10 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1824211/+subscriptions

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

[Kernel-packages] [Bug 1824050] Re: access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints

[Ryan Stark]

This linux-nfs list member found the origin of the problem:
https://marc.info/?l=linux-nfs=155480197614448=2

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

Title:
  access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
  hwe-16.04 (4.15.0-47) I am no longer able to run an application that
  checks it's data directory for write access/path traversal when that
  directory is an NFS share. This works on 4.4 and 3.13 kernels that I
  tested with but fails on 4.15. I'm using NFSv3 and have seen the
  behavior with both a synology NAS as the nfs-server as well as my
  xenial desktop as the nfs-server.

  To reproduce:
  0.) Boot test machine with kernel 4.15.0-47
  1.) set up a NFS export on another machine (nfs-server)
  /etc/exports:
  /srv/nfstest   192.168.100.100(rw,sync,no_subtree_check)

  2.) mount the NFS share on the test machine and give a non-root user
  ownership of the mount, in my case I have a user: aptly, with
  home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
  aptly:aptly owns /var/lib/aptly/test.

  /etc/fstab:
  192.168.100.101:/srv/nfstest/var/lib/aptly/test  nfs rw,mountvers=3

  
  3.) attempt to call access.W_OK on the mount as the non-root user `strace 
./testaccess.py`
  stderr:
  ...
  access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
  ...
  stdout:
  ('Writeable:', False)
  ('user r,e,s', (5062, 5062, 5062))
  ('group r,e,s', (5062, 5062, 5062))
  posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3, 
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490, 
st_mtime=1554858633, st_ctime=1554858633)

  testaccess.py:
  #!/usr/bin/python

  import os
  import sys
  from pprint import pprint
  directory = '/var/lib/aptly/test'

  if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  9 18:53 seq
   crw-rw 1 root audio 116, 33 Apr  9 18:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
  InstallationDate: Installed on 2019-04-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=/dev/mapper/pao03--aptly01--vg-root ro
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.15.0-47-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 07/28/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** 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 1822807 (xenial/linux-gcp)
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Holding before Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 12:06 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 17:06 UTC
  reason:
-   promote-to-proposed: Holding -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

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

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822807 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 17:06 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1822809] Re: linux-kvm: 4.15.0-1032.32 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1822820
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 05. April 2019 10:36 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 17:06 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress

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

Title:
  linux-kvm: 4.15.0-1032.32 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 17:06 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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

[Kernel-packages] [Bug 1822832] Re: linux-aws: 4.4.0-1041.44 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
- phase: Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 09:39 UTC
+ phase: Testing
+ phase-changed: Wednesday, 10. April 2019 17:09 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1822834
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 17:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1822834
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 05. April 2019 10:07 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 17:08 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 17:08 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

[Seth Forshee]

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

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  In Progress
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  SRU Justification

  Impact: iptables does not work in disco with linux-virtual.

  Fix: Add bpfilter to the generic inclusion list.

  Regression Potential: There are no code changes and thus minimal
  potential for regressions.

  Test Case: Verify that bpffilter.ko is shipped in linux-modues instead
  of linux-module-extra and that iptables commands work in disco with
  the linux-virtual kernel installed.

  ---

  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Kernel-packages] [Bug 1824039] Re: linux-fips: 4.15.0-1004.5 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** 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: 1822820
- phase: Holding before Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 03:08 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 17:08 UTC
  reason:
-   promote-to-proposed: Holding -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-fips: 4.15.0-1004.5 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 17:08 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker

[Kleber Sacilotto de Souza]

** 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 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
- derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822981 (linux), bug 1823254 
(linux), bug 1823755 (linux-gke), bug 1824039 (linux-fips)
+ derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822981 (linux), bug 1823254 
(linux), bug 1823755 (linux-gke), bug 1824039 (linux-fips), bug 1824204 
(linux-snapdragon)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.15.0-48.51 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822981 (linux), bug 1823254 
(linux), bug 1823755 (linux-gke), bug 1824039 (linux-fips), bug 1824204 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops

[Ard Biesheuvel]

On Tue, 9 Apr 2019 at 16:30, dann frazier  wrote:
>
> Yeah, no crash anymore - thanks Ard!
>
> ubuntu@d06-4:~$ echo function | sudo tee 
> /sys/kernel/debug/tracing/current_tracer
> function
> [   72.778123] ftrace: far branches to multiple entry points unsupported 
> inside a single module
>
> ^ I assume this is expected
>

Uhm, not really.

You don't have any out of tree live patching code in your kernel, right?

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1822871
>
> Title:
>   enabling ftrace on Hi1620 CS causes an Oops
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   [Impact]
>   Attempting to enable the function tracer causes an Oops. This impacts the 
> current disco kernel, as well as latest upstream 
> (@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).
>
>   This is 100% reproducible on D06 CS systems, but not reproducible on
>   D06 ES systems (the previous silicon rev).
>
>   [Test Case]
>   $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer
>
>   [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
>   [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
>   [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds 
> tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw 
> ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm 
> ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
> x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
> async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c 
> raid1 raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher 
> hibmc_drm hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce 
> syscopyarea sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid 
> fb_sys_fops hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio 
> hid drm hnae3 libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs 
> aes_neon_blk crypto_simd cryptd aes_arm64
>   [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12
>   [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 
> 2280-A CS V2.16.01 03/16/2019
>   [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO)
>   [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38
>   [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80
>   [ 3125.766979] sp : 2837b9f0
>   [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880
>   [ 3125.775591] x27:  x26: 
>   [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000
>   [ 3125.786200] x23: 0002 x22: 3dce9d2289a4
>   [ 3125.791504] x21: 2837ba8c x20: 2837b000
>   [ 3125.796808] x19: 3dce9d228000 x18: 
>   [ 3125.802112] x17:  x16: 3dceb7742780
>   [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001
>   [ 3125.812720] x13: bef50bb9e188 x12: 
>   [ 3125.818023] x11: 7efba3e79608 x10: 0a70
>   [ 3125.823327] x9 : 3dceb6deeacc x8 : 
>   [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10
>   [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8
>   [ 3125.839239] x3 :  x2 : 9000
>   [ 3125.844543] x1 :  x0 : 
>   [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476)
>   [ 3125.856281] Call trace:
>   [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38
>   [ 3125.863593] plt_entries_equal.part.3+0x40/0x80
>   [ 3125.868115] plt_entries_equal+0x5c/0x70
>   [ 3125.872031] ftrace_make_call+0xf0/0x150
>   [ 3125.875950] __ftrace_replace_code+0xe8/0xf8
>   [ 3125.880212] ftrace_replace_code+0x64/0xc0
>   [ 3125.884301] ftrace_modify_all_code+0xb0/0x148
>   [ 3125.888738] arch_ftrace_update_code+0x10/0x18
>   [ 3125.893174] ftrace_run_update_code+0x20/0x70
>   [ 3125.897524] ftrace_startup_enable+0x4c/0x58
>   [ 3125.901788] ftrace_startup+0xa4/0x140
>   [ 3125.905531] register_ftrace_function+0x64/0x80
>   [ 3125.910059] function_trace_init+0x50/0x98
>   [ 3125.914149] tracing_set_tracer+0xf4/0x1c0
>   [ 3125.918238] tracing_set_trace_write+0x10c/0x168
>   [ 3125.922852] __vfs_write+0x60/0x1a8
>   [ 3125.926333] vfs_write+0xac/0x1b8
>   [ 3125.929641] ksys_write+0x6c/0xd8
>   [ 3125.932949] __arm64_sys_write+0x24/0x30
>   [ 3125.936866] el0_svc_common+0x78/0x120
>   [ 3125.940608] el0_svc_handler+0x38/0x78
>   [ 3125.944349] el0_svc+0x8/0xc
>   [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421)
>   [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]---
>
>   [Fix]
>   TBD
>
>   [Regression Risk]
>   TBD
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822871/+subscriptions

-- 
You received this bug notification because you are a 

[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

[Seth Forshee]

** Description changed:

+ SRU Justification
+ 
+ Impact: iptables does not work in disco with linux-virtual.
+ 
+ Fix: Add bpfilter to the generic inclusion list.
+ 
+ Regression Potential: There are no code changes and thus minimal
+ potential for regressions.
+ 
+ Test Case: Verify that bpffilter.ko is shipped in linux-modues instead
+ of linux-module-extra and that iptables commands work in disco with the
+ linux-virtual kernel installed.
+ 
+ ---
+ 
  Fresh install of disco:
  
  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name
  
  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory
  
  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory
  
  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory
  
  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  
  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
-  TERM=screen-256color
-  PATH=(custom, no user)
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=screen-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  SRU Justification

  Impact: iptables does not work in disco with linux-virtual.

  Fix: Add bpfilter to the generic inclusion list.

  Regression Potential: There are no code changes and thus minimal
  potential for regressions.

  Test Case: Verify that bpffilter.ko is shipped in linux-modues instead
  of linux-module-extra and that iptables commands work in disco with
  the linux-virtual kernel installed.

  ---

  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Kernel-packages] [Bug 1822809] Re: linux-kvm: 4.15.0-1032.32 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-kvm: 4.15.0-1032.32 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 05. April 2019 10:36 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1824194] [NEW] hns3: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1]

[dann frazier]

Public bug reported:

[Impact]
Transmit errors may occur under load, resulting in device reset and an unusable 
NIC.

[Test Case]
Server:
ethtool -K enp129s0f0 rx off
ethtool -K enp129s0f0 gro off
ifconfig enp129s0f0 mtu 1501
iperf -s

Client:
ethtool -K enp129s0f0 tx off
ethtool -K enp129s0f0 gso off
ifconfig enp129s0f0 mtu 1501
iperf -c  -l 64K -t 3

[Fix]
5f543a54eec08 net: hns3: fix for not calculating tx bd num correctly
[Regression Risk]
Fix is restricted to a driver only used in Hi1620 SoC-based systems.

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

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

Title:
  hns3: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1]

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Transmit errors may occur under load, resulting in device reset and an 
unusable NIC.

  [Test Case]
  Server:
  ethtool -K enp129s0f0 rx off
  ethtool -K enp129s0f0 gro off
  ifconfig enp129s0f0 mtu 1501
  iperf -s

  Client:
  ethtool -K enp129s0f0 tx off
  ethtool -K enp129s0f0 gso off
  ifconfig enp129s0f0 mtu 1501
  iperf -c  -l 64K -t 3

  [Fix]
  5f543a54eec08 net: hns3: fix for not calculating tx bd num correctly
  [Regression Risk]
  Fix is restricted to a driver only used in Hi1620 SoC-based systems.

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

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

[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker

[Łukasz Zemczak]

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 05. April 2019 10:07 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1823862

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

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

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

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

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

[James Page]

Tested with the kernel+modules linked in #22

I can confirm I was able to enable ufw and query the installed iptables
rules:

$ uname -a
Linux juju-0f0cbd-disco-testing-38 5.0.0-10-generic #11+lp1823862v201904100938 
SMP Wed Apr 10 14:40:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Firewall is active and enabled on system startup

$ sudo iptables-save
# Generated by iptables-save v1.6.1 on Wed Apr 10 16:15:01 2019
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
:ufw-after-forward - [0:0]
:ufw-after-input - [0:0]
:ufw-after-logging-forward - [0:0]
:ufw-after-logging-input - [0:0]
:ufw-after-logging-output - [0:0]
:ufw-after-output - [0:0]
:ufw-before-forward - [0:0]
:ufw-before-input - [0:0]
:ufw-before-logging-forward - [0:0]
:ufw-before-logging-input - [0:0]
:ufw-before-logging-output - [0:0]
:ufw-before-output - [0:0]
:ufw-logging-allow - [0:0]
:ufw-logging-deny - [0:0]
:ufw-not-local - [0:0]
:ufw-reject-forward - [0:0]
:ufw-reject-input - [0:0]
:ufw-reject-output - [0:0]
:ufw-skip-to-policy-forward - [0:0]
:ufw-skip-to-policy-input - [0:0]
:ufw-skip-to-policy-output - [0:0]
:ufw-track-forward - [0:0]
:ufw-track-input - [0:0]
:ufw-track-output - [0:0]
:ufw-user-forward - [0:0]
:ufw-user-input - [0:0]
:ufw-user-limit - [0:0]
:ufw-user-limit-accept - [0:0]
:ufw-user-logging-forward - [0:0]
:ufw-user-logging-input - [0:0]
:ufw-user-logging-output - [0:0]
:ufw-user-output - [0:0]
-A INPUT -j ufw-before-logging-input
-A INPUT -j ufw-before-input
-A INPUT -j ufw-after-input
-A INPUT -j ufw-after-logging-input
-A INPUT -j ufw-reject-input
-A INPUT -j ufw-track-input
-A FORWARD -j ufw-before-logging-forward
-A FORWARD -j ufw-before-forward
-A FORWARD -j ufw-after-forward
-A FORWARD -j ufw-after-logging-forward
-A FORWARD -j ufw-reject-forward
-A FORWARD -j ufw-track-forward
-A OUTPUT -j ufw-before-logging-output
-A OUTPUT -j ufw-before-output
-A OUTPUT -j ufw-after-output
-A OUTPUT -j ufw-after-logging-output
-A OUTPUT -j ufw-reject-output
-A OUTPUT -j ufw-track-output
-A ufw-after-input -p udp -m udp --dport 137 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 138 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp -m tcp --dport 139 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp -m tcp --dport 445 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 67 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 68 -j ufw-skip-to-policy-input
-A ufw-after-input -m addrtype --dst-type BROADCAST -j ufw-skip-to-policy-input
-A ufw-after-logging-forward -m limit --limit 3/min --limit-burst 10 -j LOG 
--log-prefix "[UFW BLOCK] "
-A ufw-after-logging-input -m limit --limit 3/min --limit-burst 10 -j LOG 
--log-prefix "[UFW BLOCK] "
-A ufw-before-forward -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 3 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 11 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 12 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A ufw-before-forward -j ufw-user-forward
-A ufw-before-input -i lo -j ACCEPT
-A ufw-before-input -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-input -m conntrack --ctstate INVALID -j ufw-logging-deny
-A ufw-before-input -m conntrack --ctstate INVALID -j DROP
-A ufw-before-input -p icmp -m icmp --icmp-type 3 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 11 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 12 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A ufw-before-input -p udp -m udp --sport 67 --dport 68 -j ACCEPT
-A ufw-before-input -j ufw-not-local
-A ufw-before-input -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT
-A ufw-before-input -d 239.255.255.250/32 -p udp -m udp --dport 1900 -j ACCEPT
-A ufw-before-input -j ufw-user-input
-A ufw-before-output -o lo -j ACCEPT
-A ufw-before-output -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-output -j ufw-user-output
-A ufw-logging-allow -m limit --limit 3/min --limit-burst 10 -j LOG 
--log-prefix "[UFW ALLOW] "
-A ufw-logging-deny -m conntrack --ctstate INVALID -m limit --limit 3/min 
--limit-burst 10 -j RETURN
-A ufw-logging-deny -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix 
"[UFW BLOCK] "
-A ufw-not-local -m addrtype --dst-type LOCAL -j RETURN
-A ufw-not-local -m addrtype --dst-type MULTICAST -j RETURN
-A ufw-not-local -m addrtype --dst-type BROADCAST -j RETURN
-A ufw-not-local -m limit --limit 3/min --limit-burst 10 -j ufw-logging-deny
-A ufw-not-local -j DROP
-A ufw-skip-to-policy-forward -j DROP
-A ufw-skip-to-policy-input -j DROP
-A ufw-skip-to-policy-output -j ACCEPT
-A ufw-track-output -p tcp -m conntrack --ctstate NEW -j ACCEPT
-A ufw-track-output -p udp -m conntrack --ctstate NEW -j ACCEPT
-A ufw-user-limit -m limit --limit 3/min -j LOG 

[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 05. April 2019 10:07 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

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

[bugproxy]

--- Comment From leona...@ibm.com 2019-04-10 12:08 EDT---
(In reply to comment #68)
> In comment #22 above, it states that "In a meeting with lagarcia, I was
> informed this patch is very important, and that it is already on kernel
> 4.18-15 onwards."
>
> So, I assume that the required patchset(s) are already applied to the 18.04
> HWE kernel, and this bug requests a backport to the bionic 4.15 kernel.
>
> Next step is for the Canonical kernel team to analyse this backport request,
> dropping the commit fb1522e099f0 ("KVM: update to new mmu_notifier semantic
> v2", 2017-08-31), to assess whether it can be SRU'ed into the bionic 4.15
> kernel.

I may be wrong, but the patch to be dropped is "KVM: PPC: Remove unused
kvm_unmap_hva callback" (7fe24f427a09).

On this commit, it says it's removing code that is dead since commit
fb1522e099f0.

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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

[Kernel-packages] [Bug 1824177] Re: dmesg spammed with nvidia-nvlink messages during install

[Steve Langasek]

This looks like a problem with the integration in the nvidia drivers
package, which should not be trying to load modules immediately after
installation and prior to a reboot.  Reassigning for investigation.

** Package changed: ubiquity (Ubuntu) => nvidia-graphics-drivers-410
(Ubuntu)

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

Title:
  dmesg spammed with nvidia-nvlink messages during install

Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

Bug description:
  I'm doing an install of Ubuntu 19.04 on an nVidia equipped laptop.
  I've selected the 3rd party driver option in ubiquity and now my dmesg
  is spammed 10x per second with this chunk. This appears to be slowing
  down the install.

  [Wed Apr 10 16:30:12 2019] nvidia-nvlink: Unregistered the Nvlink Core, major 
device number 235
  [Wed Apr 10 16:30:12 2019] nvidia-nvlink: Nvlink Core is being initialized, 
major device number 235
  [Wed Apr 10 16:30:12 2019] NVRM: The NVIDIA probe routine was not called for 
1 device(s).
  [Wed Apr 10 16:30:12 2019] NVRM: This can occur when a driver such as: 
 NVRM: nouveau, rivafb, nvidiafb or rivatv 
 NVRM: was loaded and obtained ownership of the 
NVIDIA device(s).
  [Wed Apr 10 16:30:12 2019] NVRM: Try unloading the conflicting kernel module 
(and/or
 NVRM: reconfigure your kernel without the 
conflicting
 NVRM: driver(s)), then try loading the NVIDIA 
kernel module
 NVRM: again.
  [Wed Apr 10 16:30:12 2019] NVRM: No NVIDIA graphics adapter probed!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 16:29:38 2019
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-410/+bug/1824177/+subscriptions

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

[Kernel-packages] [Bug 1824177] [NEW] dmesg spammed with nvidia-nvlink messages during install

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm doing an install of Ubuntu 19.04 on an nVidia equipped laptop. I've
selected the 3rd party driver option in ubiquity and now my dmesg is
spammed 10x per second with this chunk. This appears to be slowing down
the install.

[Wed Apr 10 16:30:12 2019] nvidia-nvlink: Unregistered the Nvlink Core, major 
device number 235
[Wed Apr 10 16:30:12 2019] nvidia-nvlink: Nvlink Core is being initialized, 
major device number 235
[Wed Apr 10 16:30:12 2019] NVRM: The NVIDIA probe routine was not called for 1 
device(s).
[Wed Apr 10 16:30:12 2019] NVRM: This can occur when a driver such as: 
   NVRM: nouveau, rivafb, nvidiafb or rivatv 
   NVRM: was loaded and obtained ownership of the 
NVIDIA device(s).
[Wed Apr 10 16:30:12 2019] NVRM: Try unloading the conflicting kernel module 
(and/or
   NVRM: reconfigure your kernel without the conflicting
   NVRM: driver(s)), then try loading the NVIDIA kernel 
module
   NVRM: again.
[Wed Apr 10 16:30:12 2019] NVRM: No NVIDIA graphics adapter probed!

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu26
Architecture: amd64
CasperVersion: 1.402
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 10 16:29:38 2019
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-410 (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug disco rls-dd-incoming ubiquity-19.04.9 ubuntu
-- 
dmesg spammed with nvidia-nvlink messages during install
https://bugs.launchpad.net/bugs/1824177
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-410 in Ubuntu.

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

Re: [Kernel-packages] [Bug 1768208] Re: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness

[marvin]

Hey. Cool.

Yea. I have a key board combination now which uses the xrander command, so
I have a work around. But the oled screen is not working on linux in
general because of the backlight issue. oled has no backlight.

What I find strange is that lenovo is not doing anything.

For example here. One of many posts.
https://forums.lenovo.com/t5/Other-Linux-Discussions/X-1-Yoga-OLED-brightness-control-under-linux/td-p/3948282


On Wed, Apr 10, 2019 at 5:21 PM Kai-Heng Feng 
wrote:

> Sorry for not following this - does this still happen?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768208
>
> Title:
>   [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The screen brightness cannot be changed.
>
>   In 16.04, I could change the brightness via:
>   xrandr --output eDP-1 --brightness 0.7
>
>   WORKAROUND: Execute at a terminal:
>   xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8
>
>   WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/
>
>   ---
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  marvin 1768 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.04
>   HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
>   MachineType: LENOVO 20FRS2M600
>   Package: linux (not installed)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-20-generic N/A
>linux-backports-modules-4.15.0-20-generic  N/A
>linux-firmware 1.173
>   Tags:  bionic
>   Uname: Linux 4.15.0-20-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 06/23/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N1FET41W (1.15 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20FRS2M600
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: None
>   dmi.modalias:
> dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
>   dmi.product.family: ThinkPad X1 Yoga 1st
>   dmi.product.name: 20FRS2M600
>   dmi.product.version: ThinkPad X1 Yoga 1st
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+subscriptions
>

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

Title:
  [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The screen brightness cannot be changed.

  In 16.04, I could change the brightness via:
  xrandr --output eDP-1 --brightness 0.7

  WORKAROUND: Execute at a terminal:
  xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8

  WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/

  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marvin 1768 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
  MachineType: LENOVO 20FRS2M600
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2M600
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2M600
  

[Kernel-packages] [Bug 1776563]

[erikjohansson]

As i wrote i still use parameters.
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2
For me i couldn't boot with anything other then pci=noacpi before, but now ivrs 
parameters work and i got a working touchpad.
"Things seem to work" is because i have only used the laptop for a day and i 
haven't tested every single scenario, but as far as i can tell it works.
I wasn't able to boot with ivrs parameter before and i had no use of the laptop 
that was only useful as an paperweight, it couldn't suspend or hibernate. 
Now i have a working laptop that i can finally use and no fans going berserk.

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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: 1822820
- phase: Ready for Packaging
- phase-changed: Wednesday, 03. April 2019 09:02 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 10. April 2019 15:36 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded

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

Title:
  linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
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:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Packaging
  phase-changed: Wednesday, 10. April 2019 15:36 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1822816] Re: linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1822817
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 05. April 2019 17:41 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 15:42 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1822817
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 15:42 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

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

[Kernel-packages] [Bug 1822832] Re: linux-aws: 4.4.0-1041.44 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1822834
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 09:39 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1822834
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 09:39 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1264125] Re: kernel crash with "alx 0000:03:00.0 eth2: fatal interrupt 0x4019607, resetting"

[Raushan Kumar Pandey]

Facing this bug on ubuntu 19.04

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

Title:
  kernel crash with "alx :03:00.0 eth2: fatal interrupt 0x4019607,
  resetting"

Status in linux package in Ubuntu:
  Expired

Bug description:
  
  Crash happened while playing video in browser.

  in syslog:
  Dec 25 15:17:01 peter-Lenovo-G510 CRON[17742]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)
  Dec 25 15:17:33 peter-Lenovo-G510 kernel: [111598.474218] alx :03:00.0 
eth2: fatal interrupt 0x4019607, resetting
  Dec 25 15:17:33 peter-Lenovo-G510 kernel: [111598.474324] alx :03:00.0 
eth2: fatal interrupt 0x4019607, resetting
  Dec 25 15:17:33 peter-Lenovo-G510 kernel: [111598.474525] alx :03:00.0 
eth2: fatal interrupt 0x4019607, resetting
  same message repeats until  reset 
  Dec 25 15:17:34 peter-Lenovo-G510 kernel: [111598.919434] alx :03:00.0 
eth2: fatal interrupt 0x4019607, resetting
  Dec 25 15:17:34 peter-Lenovo-G510 kernel: [111598.919647] alx :03:00.0 
eth2: fatal interrupt 0x4019607, resetting

  peter@peter-Lenovo-G510:~$ uname -a
  Linux peter-Lenovo-G510 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

  peter@peter-Lenovo-G510:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #2 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation HM86 Express LPC Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
  02:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
  03:00.0 Ethernet controller: Qualcomm Atheros QCA8172 Fast Ethernet (rev 10)

  peter@peter-Lenovo-G510:~$ dmesg | grep alx
  [4.478587] alx :03:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet 
[xx:xx:xx:xx:xx:xx]
  [   15.221697] alx :03:00.0: irq 46 for MSI/MSI-X
  [   15.223260] alx :03:00.0 eth2: NIC Up: 100 Mbps Full

  peter@peter-Lenovo-G510:/var/log$ lsb_release -rd
  Description:Ubuntu 13.10
  Release:13.10

  
  peter@peter-Lenovo-G510:/var/log$ grep alx pm-suspend.log
  alx32792  0 
  mdio   13807  1 alx
  Running hook /usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend:
  Unloading alx kernel module ...
  /usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend: success.
  Running hook /usr/lib/pm-utils/sleep.d/50unload_alx resume suspend:
  Reloading alx kernel module ...
  /usr/lib/pm-utils/sleep.d/50unload_alx resume suspend: success.
  alx32792  0 
  mdio   13807  1 alx
  Running hook /usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend:
  Unloading alx kernel module ...
  /usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend: success.
  Running hook /usr/lib/pm-utils/sleep.d/50unload_alx resume suspend:
  Reloading alx kernel module ...
  /usr/lib/pm-utils/sleep.d/50unload_alx resume suspend: success.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1944 F pulseaudio
   /dev/snd/controlC1:  peter  1944 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=8de0eb76-c3d0-4219-b6a2-0837381be140
  InstallationDate: Installed on 2013-11-16 (39 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20238
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  iGVT-g guest does not load graphics: kernel WARNING and wedged GPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu 19.04 Disco Dingo Beta (both live and installed) Intel
  GVT-g guest, it was noticed that the graphical interface does not
  load. The following message appears:

  [   19.844904] i915 :00:03.0: Failed to initialize GPU, declaring
  it wedged!

  And there are two kernel WARNING that appear. The first WARNING seems
  harmless and it was already reported:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102 and is
  related to the host kernel, on this case 4.18.0-17 from HWE.

  The second WARNING is new and probably is related to the failure to
  load the graphics.

  It is possible to access the guest using the serial console. While the
  system claims GDM is working, there is no graphical interface visible.

  I have tested with Xubuntu 19.04 Disco Dingo Beta too and the same
  problem was noticed: two kernel WARNING, a wedged GPU and failure to
  load the graphics, even if the LightDM services was shown as running
  by systemctl status.

  Ubuntu 18.04 guests with kernel 4.15 and 4.18 are working. Mageia 7
  guests with kernel 5.0.7 are working too, this seems related to the
  5.0.0 kernel from Disco. Tested with both 5.0.0-7 and 5.0.0-8.

  Example of QEMU command line used:

  qemu-system-x86_64 -global PIIX4_PM.disable_s4=1 -M pc,usb=false
  -machine kernel_irqchip=on -global PIIX4_PM.disable_s3=1 -name "Ubuntu
  Disco" -k pt-br -nodefaults -accel kvm -m 2G -cpu host -smp
  cores=2,threads=1 -netdev user,id=net0 -device
  e1000,netdev=net0,addr=8 -device vfio-
  pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/84de120a-c340-48fc-
  ba40-62f54c76f3ad,rombar=0,display=on,addr=0x3,id=iHD520 -device nec-
  usb-xhci,id=xhcihub -device usb-audio,id=usbaudio,buffer=6144 -device
  usb-tablet,id=usbtablet -bios /usr/share/ovmf/OVMF.fd -display
  gtk,gl=on -hda
  /home/usuario/.local/share/libvirt/images/ubuntu_disco.qcow2 -monitor
  vc -serial vc

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-8-generic 5.0.0-8.9
  ProcVersionSignature: User Name 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Apr 10 12:04:47 2019
  InstallationDate: Installed on 2019-04-09 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  IwConfig:
   ens8  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 002: ID 46f4:0002  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=deb9f102-2eaf-4c05-96da-8c541c55726b ro quiet splash console=ttyS0
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.1
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.1
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1822788] Re: linux-aws: 4.18.0-1013.15 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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 1822787 (bionic/linux-aws-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 03. April 2019 23:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.18.0-1013.15 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822787 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 03. April 2019 23:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1815061] Re: linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

[Juerg Haefliger]

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

** This bug is no longer a duplicate of bug 1819701
   linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** This bug has been marked a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

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

Title:
  linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Ready for Testing
  phase-changed: Sunday, 03. March 2019 06:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

[Juerg Haefliger]

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

** This bug has been marked a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

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

Title:
  linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Ready for Release
  phase-changed: Tuesday, 02. April 2019 09:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
promote-to-updates: Pending -- ready to copy

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

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

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

[Sean Feole]

affects 4.18.0-1013.15 linux-aws

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

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8192: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits 

[Kernel-packages] [Bug 1811850] Re: linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

[Juerg Haefliger]

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

** This bug is no longer a duplicate of bug 1819701
   linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** This bug has been marked a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

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

Title:
  linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 18:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

[Seth Forshee]

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

** This bug has been marked a duplicate of bug 1823862
   disco: unable to use iptables/enable ufw under -virtual kernel

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

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

[Launchpad Bug Tracker]

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

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

Title:
  linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed 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:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Ready for Packaging
  phase-changed: Wednesday, 03. April 2019 09:02 UTC
  reason:
prepare-package: Pending -- version not specified

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

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

[Kernel-packages] [Bug 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

[Juerg Haefliger]

** Summary changed:

- linux-ibm-gt:  -proposed tracker
+ linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

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

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

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

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

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

Title:
  linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed 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:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Ready for Packaging
  phase-changed: Wednesday, 03. April 2019 09:02 UTC
  reason:
prepare-package: Pending -- version not specified

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

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

[Kernel-packages] [Bug 1822816] Re: linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1822817
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 05. April 2019 17:41 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1822788] Re: linux-aws: 4.18.0-1013.15 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  linux-aws: 4.18.0-1013.15 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822787 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 03. April 2019 23:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

[Seth Forshee]

All that seems to be missing is bpffilter. I've made a test build with
this moved to linux-modules. It appears to be working for check-
requirements. Can you test and make sure everything is working as
expected? Thanks!

http://people.canonical.com/~sforshee/lp1823862/

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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