date:20180523

You have been subscribed to a public bug:

Samsug Series7 laptop NP730UE-S01PL keybord light (more\less) shortcuts
fn+F10\F11 don't work

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: compiz-core 1:0.9.12.1+15.10.20150627.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
CasperVersion: 1.362
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Aug 10 21:22:58 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c0e8]
LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150808)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 730U3E/740U3E
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
SourcePackage: compiz
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P07ABW.065.140226.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP730U3E-S01PL
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07ABW.065.140226.dg:bd02/26/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn730U3E/740U3E:pvrP07ABW:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP730U3E-S01PL:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 730U3E/740U3E
dmi.product.version: P07ABW
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.62-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Mon Aug 10 21:05:18 2015
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4931 
 vendor CMN
xserver.version: 2:1.17.2-1ubuntu3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu wily
-- 
laptop keybord light (more\less) shortcuts don't work
https://bugs.launchpad.net/bugs/1483416
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1771344] Re: Fix enabling bridge MMIO windows

2018-05-23 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1771344

Title:
  Fix enabling bridge MMIO windows

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

Bug description:
  == Comment: #0 - Breno Leitao  
  On boot we save the configuration space of PCIe bridges. We do this so
  when we get an EEH event and everything gets reset that we can restore
  them.
  
  Unfortunately we save this state before we've enabled the MMIO space
  on the bridges. Hence if we have to reset the bridge when we come back
  MMIO is not enabled and we end up taking an PE freeze when the driver
  starts accessing again.
  
  This patch forces the memory/MMIO and bus mastering on when restoring
  bridges on EEH. Ideally we'd do this correctly by saving the
  configuration space writes later, but that will have to come later in
  a larger EEH rewrite. For now we have this simple fix.
  
  The original bug can be triggered on a boston machine by doing:
   echo 0x8000 > 
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
  On boston, this PHB has a PCIe switch on it.  Without this patch,
  you'll see two EEH events, 1 expected and 1 the failure we are fixing
  here. The second EEH event causes the anything under the PHB to
  disappear (i.e. the i40e eth).
  
  With this patch, only 1 EEH event occurs and devices properly recover.

  This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should
  be part of Ubuntu 18.04 kernel.

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

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

[Kernel-packages] [Bug 1483416] Re: laptop keybord light (more\less) shortcuts don't work

2018-05-23 Thread Timo Aaltonen

that's a kernel bug,  and you provided no info.. could be fixed by now

** Package changed: xserver-xorg-input-keyboard (Ubuntu) => linux
(Ubuntu)

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

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

Title:
  laptop keybord light (more\less) shortcuts don't work

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Samsug Series7 laptop NP730UE-S01PL keybord light (more\less)
  shortcuts  fn+F10\F11 don't work

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: compiz-core 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.362
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Aug 10 21:22:58 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c0e8]
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150808)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 730U3E/740U3E
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P07ABW.065.140226.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP730U3E-S01PL
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07ABW.065.140226.dg:bd02/26/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn730U3E/740U3E:pvrP07ABW:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP730U3E-S01PL:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 730U3E/740U3E
  dmi.product.version: P07ABW
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.62-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Aug 10 21:05:18 2015
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4931 
   vendor CMN
  xserver.version: 2:1.17.2-1ubuntu3

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-05-23 Thread David Franko

Oliver & Hans, thank you!

After reverting that patch and applying the other one + resolving the 
conflicts, i can confirm it works  on 4.17.0-rc6 (chuwi lapbook air).
Movement, tap, scroll, left and right button.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)

2018-05-23 Thread Volodymyr Shymanskyi

Lenovo IdeaPad 720s (i5-8250U), the same issue.

On resume, I get:
[  213.347656] usb 1-7: device descriptor read/64, error -110

➜  ~ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
|__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 7: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 7: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M

This way, i was getting my BT adapter disconnected.
But also I was experiencing a USB3 flash drive reconnecting unexpectedly during 
normal operation (no sleep/resume).

'pci=nomsi iommu=soft' helped, at least for now.

➜  ~ lsb_release -a  
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic
➜  ~ uname -a  
Linux vshymanskyy-720S 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  USB stops working after a while (xhci_hcd :00:14.0: Timeout while
  waiting for setup device command)

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my laptop the kernel will sometimes drop the USB hub. After this,
  the laptop doesn't recognise any device plugged in to the USB ports -
  plugging and unplugging any device I've tried into any of the USB
  ports produces no response, not even dmesg entries.

  Strangely this also applies to bluetooth - it no longer works once USB
  has dropped (possibly the module is hung of the bus internally).

  Once this has happened only a reboot fixes it; I've not managed to
  find any combination of module unload/reload or suspend cycles to
  reinitialise things correctly.

  Relevant snippet of dmesg:
  [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe 
the host is dead
  [48838.079742] xhci_hcd :00:14.0: Abort command ring failed
  [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up
  [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079806] sched: RT throttling activated
  [48838.079981] usb 1-1: USB disconnect, device number 16
  [48838.079985] usb 1-1.2: USB disconnect, device number 18
  [48838.079987] usb 1-1.2.3: USB disconnect, device number 19
  [48838.080285] usb 1-1.2.4: USB disconnect, device number 20
  [48838.111892] usb 1-1.4: USB disconnect, device number 17
  [48838.191292] usb 1-4: USB disconnect, device number 6
  [48838.267550] usb 1-10: USB disconnect, device number 8
  [48838.282968] usb 2-1: device not accepting address 8, error -62
  [48838.282983] usb 2-1: USB disconnect, device number 8
  [48838.282986] usb 2-1.2: USB disconnect, device number 9

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  4255 F pulseaudio
   /dev/snd/controlC0:  chris  4255 F pulseaudio
  CRDA:
   country AU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (3, 23), (N/A)
(5250 - 5330 @ 40), (3, 23), (0 ms), DFS
(5735 - 5835 @ 40), (3, 30), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jan 22 12:59:27 2015
  InstallationDate: Installed on 2013-08-06 (533 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Galago UltraPro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd break=mount
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, I

[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

2018-05-23 Thread Claudio Castelpietra

Sorry, how can I undo the "fix released" status?

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

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  This bug causes a Dell Latitude 5490/5590 with BIOS update 1.1.9 to get a
  black screen at boot. Specifying 'nomodeset' on the kernel command line works
  around the problem.

  Intel resolved the problem in upstream commit a3520b8992e5.  This commit
  is now in mainline as of 4.17.rc2.  It has also been cc'd to upstream
  stable.

  
  == Fix ==
  a3520b8992e5 ("drm/i915/bios: filter out invalid DDC pins from VBT child 
devices")

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable, so it recieved
  additional upstream review.


  
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
  laptops, originally running BIOS version 1.0.8. The install media and
  the installed OS was running linux-generic-hwe kernel 4.13.0.

  After upgrading BIOS to latest version 1.1.9, the kernel no longer
  boots: right after loading the i915 drm driver, the screen goes black,
  and the machine can only be reset or power cycled. This is true for
  both the installation media, and the OS instance previously installed
  to the disk and updated to the latest hwe kernel 4.13.0-38.

  Specifying 'nomodeset' on the kernel command line works around the
  problem by disabling the i915 drm driver functionality. In that case,
  several display driver function are obviously missing (eg GLX &
  xrandr).

  The problem manifested itself even when using the drm upstream latest 
git-head version. A custom built kernel was used to provide logs for this 
upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=105549

  The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
  https://patchwork.freedesktop.org/patch/216371/
  
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

  I backported this fix to ubuntu-xenial hwe git-head, and tested the
  result successfully. I'd like this fix to be added to the ubuntu-
  xenial linux-generic-hwe kernel.

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

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

[Kernel-packages] [Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

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

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

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

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

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

Title:
  Kernel panic on boot (m1.small in cn-north-1)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-aws source package in Bionic:
  In Progress

Bug description:
  We're observing the following panic on boot when trying to boot an
  m1.small in cn-north-1 (which is a region in AWS China):

  [2.271681] Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
  [2.271681] RIP: 0010:__xen_evtchn_do_upcall+0x24/0x80
  [2.271681] RSP: :8e21aa003ea0 EFLAGS: 00010046
  [2.271681] RAX: 9dd82920 RBX: ff20 RCX: 
8728b34e
  [2.271681] RDX: 8e21a3252800 RSI: 8e21a724e000 RDI: 
001c
  [2.271681] RBP: 8e21aa003eb8 R08: 9ea05040 R09: 

  [2.271681] R10: 8e21aa003f28 R11:  R12: 
0001
  [2.271681] R13:  R14: 0022 R15: 
8e21a3246900
  [2.271681] FS:  () GS:8e21aa00() 
knlGS:
  [2.271681] CS:  0010 DS:  ES:  CR0: 80050033
  [2.271681] CR2: ff20 CR3: 0b80a000 CR4: 
06f0
  [2.271681] Call Trace:
  [2.271681]  
  [2.271681]  xen_hvm_evtchn_do_upcall+0xe/0x10
  [2.271681]  do_hvm_evtchn_intr+0xe/0x20
  [2.271681]  __handle_irq_event_percpu+0x44/0x1a0
  [2.271681]  handle_irq_event_percpu+0x32/0x80
  [2.271681]  handle_irq_event+0x3b/0x60
  [2.271681]  handle_fasteoi_irq+0x75/0x130
  [2.271681]  handle_irq+0x20/0x30
  [2.271681]  do_IRQ+0x46/0xd0
  [2.271681]  common_interrupt+0x84/0x84
  [2.271681]  
  [2.271681] RIP: 0010:native_safe_halt+0x6/0x10
  [2.271681] RSP: :9ea03e28 EFLAGS: 0246 ORIG_RAX: 
ffdd
  [2.271681] RAX: 9e12fba0 RBX:  RCX: 

  [2.271681] RDX:  RSI:  RDI: 

  [2.271681] RBP: 9ea03e28 R08: 0002 R09: 
9ea03e18
  [2.271681] R10: 9ea03da0 R11: eb8a1d25 R12: 

  [2.271681] R13:  R14:  R15: 

  [2.271681]  ? __cpuidle_text_start+0x8/0x8
  [2.271681]  default_idle+0x20/0x100
  [2.271681]  arch_cpu_idle+0x15/0x20
  [2.271681]  default_idle_call+0x23/0x30
  [2.271681]  do_idle+0x17f/0x1b0
  [2.271681]  cpu_startup_entry+0x73/0x80
  [2.271681]  rest_init+0xae/0xb0
  [2.271681]  start_kernel+0x4dc/0x4fd
  [2.271681]  x86_64_start_reservations+0x24/0x26
  [2.271681]  x86_64_start_kernel+0x74/0x77
  [2.271681]  secondary_startup_64+0xa5/0xb0
  [2.271681] Code: 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 
54 53 65 48 8b 1d 92 dc 29 62 41 bc 01 00 00 00 65 44 8b 2d 8c 8c 29 62  03 
00 44 89 e0 65 0f c1 05 2e 96 2a 62 85 c0 75 3b 48 8b 05 
  [2.271681] RIP: __xen_evtchn_do_upcall+0x24/0x80 RSP: 8e21aa003ea0
  [2.271681] CR2: ff20
  [2.271681] ---[ end trace 956d0f4244642614 ]---
  [2.271681] Kernel panic - not syncing: Fatal exception in interrupt

  I've attached the full console log.

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

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

[Kernel-packages] [Bug 1768526] Re: Include nfp driver in linux-modules

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

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

Title:
  Include nfp driver in linux-modules

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification:
  --

  [Impact]

   * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included 
in linux-moudles-extra.
     An implication of this is that on minimal installs, where the 
linux-modules but not linux-modules-extra
     packages are available, the nfp.ko module cannot be installed. In 
particular this means the driver for
     any VFs of Netronome Agilio SmartNICs which have been made available to 
guests using PCI pass-through
     cannot be used by those guests if they have installed using Canonical 
cloud images, a likely scenario.

     In contrast the driver for the i40e is provided in the linux-modules 
package and thus guests can
     access their VFs in the scenario described above.

     Thus we do not believe it is unreasonable to request that nfp.ko be 
included in linux-modules rather
     than linux-modules-extras. And we believe that this warrants SRU inclusion 
as it is the difference between
     users-of guests being able to use Netronome Agilio SmartNICs and not be 
able to use them.

     This is a packaging update request and included no request to change the 
kernel source code,
     thus no backports are requred.

  [Test Case]

   * Install system using Canonical cloud images

   * Observer that
  /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is
  missing;

   * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or 
otherwise,
     that the nfp driver is not loaded and no netdevs are present for the 
Netronome Agilio SmartNIC.

  [Regression Potential]

   * Any bugs present in the nfp.ko will now be exposted to guests. However as 
the same nfp.ko driver binary
     is already included in and available on installs that have access to 
linux-modules-extra, this does not
     seem an unreasonable burden.

  [Other Info]

   * None

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

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

[Kernel-packages] [Bug 1767490] Re: Add d-i support for Huawei NICs

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

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

** Description changed:

  [Impact]
  The hinic driver isn't included in the installer, so it isn't possible to use 
Huawei NICs for network installs.
  
  [Test Case]
  Boot d-i on a system with a Huawei PCIe card. Proceed to the network 
configuration screen, and see if that NIC is displayed.
  
+ [Fix]
+ Adding the module to the nic-modules list for d-i.
+ 
  [Regression Risk]
  Including a new driver is a common practice that should have minimal 
regression risk.

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

Title:
  Add d-i support for Huawei NICs

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  The hinic driver isn't included in the installer, so it isn't possible to use 
Huawei NICs for network installs.

  [Test Case]
  Boot d-i on a system with a Huawei PCIe card. Proceed to the network 
configuration screen, and see if that NIC is displayed.

  [Fix]
  Adding the module to the nic-modules list for d-i.

  [Regression Risk]
  Including a new driver is a common practice that should have minimal 
regression risk.

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

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

[Kernel-packages] [Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5

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

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

Title:
  unregister_netdevice: waiting for eth0 to become free. Usage count = 5

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Commit 52df157f17e5 introduced a regression in v4.13-rc1.  This regression
  causes a stack trace to occur when tearing down an LXD container.  The process
  hangs with the following message:

  "unregister_netdevice: waiting for eth0 to become free. Usage count =
  5"

  This regression is fixed by commit 510c321b5571, which is in mainline as of
  v4.16-rc7.  The fix is needed in Artful and Bionic.  However, Artful needs
  a prereq commit, so it's SRU request will be sent separately.

  
  == Fix ==
  510c321b5571 ("xfrm: reuse uncached_list to track xdsts")

  == Regression Potential ==
  Low.  This commit is to fix a current regression.

  
  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  This occurs when tearing down an LXD container.

  LXD monitor process hangs with the following stack:

  $ sudo cat /proc/27043/stack
  [] msleep+0x2e/0x40
  [] netdev_run_todo+0x11f/0x310
  [] rtnetlink_rcv+0x2d/0x30
  [] netlink_unicast+0x18c/0x240
  [] netlink_sendmsg+0x2dd/0x3c0
  [] sock_sendmsg+0x38/0x50
  [] ___sys_sendmsg+0x2e3/0x2f0
  [] __sys_sendmsg+0x54/0x90
  [] SyS_sendmsg+0x12/0x20
  [] do_syscall_64+0x5b/0xc0
  [] entry_SYSCALL64_slow_path+0x8/0x8
  [] 0x

  Issue submitted to LXD as well ([1]), though as indicated there, it
  seems to be a kernel bug.

  [1] https://github.com/lxc/lxd/issues/4208

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jan 31 11:42:59 2018
  InstallationDate: Installed on 2016-11-09 (447 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1772682] Re: No sound for Dell Inspiron 5758

2018-05-23 Thread Po-Hsu Lin

Hi Andrew,

Ubuntu 14.04 Trusty was released in 2014 Apr., which is relatively old
to your system (probably released in mid-2015) so it's Wifi driver and
the sound card driver might not be available.

I would recommend you to give 18.04 Bionic a try, you can just test it
with a LiveUSB.

(Marking this bug as Incomplete base on Joseph's request in comment#2)

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

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

Title:
  No sound for Dell Inspiron 5758

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have

  
  I tried to update system but the computer did not finish updating, and 
informed me that there is no internet connection, while the connection was OK. 
  As a result, I still  have not been any sound in the computer. 

  
  Sincerely yours, Andrew.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-147-generic 3.13.0-147.196
  ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-147-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Date: Tue May 22 19:03:51 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436
  InstallationDate: Installed on 2016-01-25 (848 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5758
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic 
root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash radeon.modeset=0 
nouveau.modeset=0 vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-147-generic N/A
   linux-backports-modules-3.13.0-147-generic  N/A
   linux-firmware  1.127.24
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 09CGRW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5758
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1772859] [NEW] Network Manager is not able to manage the devices on Ubuntu 18.04

You have been subscribed to a public bug:

NetworkManager is not able to manage the devices on latest Ubuntu(18.04)
 
---uname output---
Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x 
s390x s390x GNU/Linux
 
Machine Type = z14 s390 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4).
2. Configure a network device and login to the partition through ssh.
3. Now you can see the following output
root@(none):~# nmcli d s
DEVICE  TYPE  STATE  CONNECTION
eth0ethernet  unmanaged  --
eth1ethernet  unmanaged  --
lo  loopback  unmanaged  --
 
Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el 
s390x 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: NetworkManager --version 1.10.4

Userspace tool obtained from project website:  na 
 

Some more information about the issue:

Network device has been configured manually after the image is up from Support 
Element(SE):
- znetconf -a 
- cat /sys/bus/ccwgroup/drivers/qeth//if_name
- ifconfig   netmask 255.255.255.0
- route add default gw  
- SSH service has been configured

This helped us to login to the Lpar. In Lpar
- output of znetconf -c
Device IDs TypeCard Type  CHPID Drv. Name   
  State

-
0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0   
  online
0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000  D0 qeth eth1   
  online

- output of nmcli c s
root@(none):~# nmcli c s
NAME  UUID  TYPE  DEVICE

- output of nmcli d s
root@(none):~# nmcli d s
DEVICE  TYPE  STATE  CONNECTION
eth0ethernet  unmanaged  --
eth1ethernet  unmanaged  --
lo  loopback  unmanaged  --

* The above output shows that devices are not managed by nmcli

After some investigation we found couple of suggestions like
1. Ubuntu(version <17.04): Creating an empty 
file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and 
restarting NM,
   solved the issue.
   
2. Ubuntu(version 17.10): Copying the said 
file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the 
   "unmanaged-devices" to none, resolved the issue.

* link for reference: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1638842

For the latest version(18.04), none of the above solutions worked.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-all bugnameltc-168090 severity-critical 
targetmilestone-inin---
-- 
Network Manager is not able to manage the devices on Ubuntu 18.04
https://bugs.launchpad.net/bugs/1772859
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1770849] Re: Ubuntu 18.04 kernel crashed while in degraded mode

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

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

Title:
  Ubuntu 18.04 kernel crashed while in degraded mode

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  IBM reports a kernel crash with Bionic while in degraded mode(Degraded
  cores).

  IBM created a patch to resolve this bug and has submitted it upstream:
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-May/172835.html

  The patch has not landed in mainline as of yet, so it is being submitted
  as a SAUCE patch.

  == Fix ==
  UBUNTU: SAUCE: powerpc/perf: Fix memory allocation for core-imc based on 
num_possible_cpus()

  == Regression Potential ==
  Low.  Limited to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  kernel crash

  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   64.713154] kexec_core: Starting new kernel
  [  156.281504630,5] OPAL: Switch to big-endian OS
  [  158.440263459,5] OPAL: Switch to little-endian OS
  [1.889211] Unable to handle kernel paging request for data at address 
0x678e549df9e2878c
  [1.889289] Faulting instruction address: 0xc038aa30
  [1.889344] Oops: Kernel access of bad area, sig: 11 [#1]
  [1.889386] LE SMP NR_CPUS=2048 NUMA PowerNV
  [1.889432] Modules linked in:
  [1.889468] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.15.0-20-generic 
#21-Ubuntu
  [1.889545] NIP:  c038aa30 LR: c038aa1c CTR: 

  [1.889608] REGS: c03fed193840 TRAP: 0380   Not tainted  
(4.15.0-20-generic)
  [1.889670] MSR:  90009033   CR: 28000884 
 XER: 2004
  [1.889742] CFAR: c0016e1c SOFTE: 1
  [1.889742] GPR00: c038a914 c03fed193ac0 c16eae00 
0001
  [1.889742] GPR04: c03fd754c7f8 002c 0001 
002b
  [1.889742] GPR08: 678e549df9e28874   
fffe
  [1.889742] GPR12: 28000888 cfa82100 c000d3b8 

  [1.889742] GPR16:    

  [1.889742] GPR20:    
a78e54a22eb64f8c
  [1.889742] GPR24: c03fd754c800 678e549df9e2878c 0300 
c02bd05c
  [1.889742] GPR28: c03fed01ea00 014080c0 c03fd754c800 
c03fed01ea00
  [1.890286] NIP [c038aa30] kmem_cache_alloc_trace+0x2d0/0x330
  [1.890340] LR [c038aa1c] kmem_cache_alloc_trace+0x2bc/0x330
  [1.890391] Call Trace:
  [1.890416] [c03fed193ac0] [c038a914] 
kmem_cache_alloc_trace+0x1b4/0x330 (unreliable)
  [1.890491] [c03fed193b30] [c02bd05c] pmu_dev_alloc+0x3c/0x170
  [1.890547] [c03fed193bb0] [c10e3210] 
perf_event_sysfs_init+0x8c/0xf0
  [1.890611] [c03fed193c40] [c000d144] 
do_one_initcall+0x64/0x1d0
  [1.890676] [c03fed193d00] [c10b4400] 
kernel_init_freeable+0x280/0x374
  [1.890740] [c03fed193dc0] [c000d3d4] kernel_init+0x24/0x160
  [1.890795] [c03fed193e30] [c000b528] 
ret_from_kernel_thread+0x5c/0xb4
  [1.890857] Instruction dump:
  [1.890909] 7c97ba78 fb210038 38a50001 7f19ba78 fb29 f8aa 4bc8c3f1 
6000
  [1.890978] 7fb8b840 419e0028 e93f0022 e91f0140 <7d59482a> 7d394a14 
7d4a4278 7fa95040
  [1.891050] ---[ end trace 41b3fe7a827f3888 ]---
  [2.900027]
  [3.900175] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
  [3.900175]
  [4.71868[  175.340944355,5] OPAL: Reboot request...
  2] Rebooting in 10 seconds..

  This fix is needed to resolve the crash

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-May/172835.html

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

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

[Kernel-packages] [Bug 1768898] Re: smp_call_function_single/many core hangs with stop4 alone

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

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

Title:
  smp_call_function_single/many core hangs with stop4 alone

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  IBM reports that this bug occurs with stop4 which results in soft lockups/rcu 
stalls.
  This is a kernel synchronization issue leading to a dead lock.

  This bug was introduced by commit 7bc54b652f13 in v4.8-rc1.  This
  regression is fixed by mainline commit c0f7f5b6c6910.

  == Fix ==
  c0f7f5b6c6910 ("cpufreq: powernv: Fix hardlockup due to synchronous smp_call 
in timer interrupt")

  == Regression Potential ==
  Low. Fixes current regression.  Cc'd to upstream stable, so it has had
  additon upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  Recently we discovered this bug occurs just alone with stop4 which
  results in soft lockups/rcu stalls.

  ```
  root@ltc-boston125:~# [15523.619395] systemd[1]: systemd-journald.service: 
Processes still around after final SIGKILL. Entering failed mode.
  [15523.619508] systemd[1]: systemd-journald.service: Failed with result 
'timeout'.
  [15523.619769] systemd[1]: Failed to start Journal Service.
  [15523.620618] systemd[1]: systemd-journald.service: Service has no hold-off 
time, scheduling restart.
  [15523.620774] systemd[1]: systemd-journald.service: Scheduled restart job, 
restart counter is at 21.
  [15523.621462] systemd[1]: Stopped Journal Service.
  [15523.621635] systemd[1]: systemd-journald.service: Found left-over process 
1561 (systemd-journal) in control group while starting unit. Ignoring.
  [15523.621756] systemd[1]: This usually indicates unclean termination of a 
previous run, or service implementation deficiencies.
  [15523.621888] systemd[1]: systemd-journald.service: Found left-over process 
69060 (systemd-journal) in control group while starting unit. Ignoring.
  [15523.622029] systemd[1]: This usually indica[15541.629904] INFO: rcu_sched 
self-detected stall on CPU
  [15541.629958]60-: (2 GPs behind) idle=146/142/0 
softirq=300022/300022 fqs=999069
  [15541.630046] (t=2415546 jiffies g=184827 c=184826 q=57111)
  [15541.630101] NMI backtrace for cpu 60
  [15541.630135] CPU: 60 PID: 4810 Comm: tlbie_test Tainted: G L   
4.15.0-15-generic #16-Ubuntu
  [15541.630207] Call Trace:
  [15541.630232] [c000201a1da96b00] [c0ceb35c] dump_stack+0xb0/0xf4 
(unreliable)
  [15541.630298] [c000201a1da96b40] [c0cf4d48] 
nmi_cpu_backtrace+0x1f8/0x200
  [15541.630363] [c000201a1da96bd0] [c0cf4ee8] 
nmi_trigger_cpumask_backtrace+0x198/0x1f0
  [15541.630429] [c000201a1da96c60] [c002f2d8] 
arch_trigger_cpumask_backtrace+0x28/0x40
  [15541.630495] [c000201a1da96c80] [c01a913c] 
rcu_dump_cpu_stacks+0xf4/0x158
  [15541.630560] [c000201a1da96cd0] [c01a81e8] 
rcu_check_callbacks+0x8e8/0xb40
  [15541.630625] [c000201a1da96e00] [c01b64a8] 
update_process_times+0x48/0x90
  [15541.630689] [c000201a1da96e30] [c01ce1f4] 
tick_sched_handle.isra.5+0x34/0xd0
  [15541.630753] [c000201a1da96e60] [c01ce2f0] 
tick_sched_timer+0x60/0xe0
  [15541.630818] [c000201a1da96ea0] [c01b7054] 
__hrtimer_run_queues+0x144/0x370
  [15541.630883] [c000201a1da96f20] [c01b7fac] 
hrtimer_interrupt+0xfc/0x350
  [15541.630948] [c000201a1da96ff0] [c00248f0] 
__timer_interrupt+0x90/0x260
  [15541.631013] [c000201a1da97040] [c0024d08] timer_interrupt+0x98/0xe0
  [15541.631069] [c000201a1da97070] [c0009014] 
decrementer_common+0x114/0x120
  [15541.631135] --- interrupt: 901 at smp_call_function_single+0x134/0x180
  [15541.631135] LR = smp_call_function_single+0x110/0x180
  [15541.631230] [c000201a1da973d0] [c01d55e0] 
smp_call_function_any+0x180/0x250
  [15541.631294] [c000201a1da97430] [c0acd3e8] 
gpstate_timer_handler+0x1e8/0x580
  [15541.631359] [c000201a1da974e0] [c01b46b0] call_timer_fn+0x50/0x1c0
  [15541.631433] [c000201a1da97560] [c01b4958] expire_timers+0x138/0x1f0
  [15541.631488] [c000201a1da975d0] [c01b4bf8] 
run_timer_softirq+0x1e8/0x270
  [15541.631553] [c000201a1da97670] [c0d0d6c8] __do_softirq+0x158/0x3e4
  [15541.631608] [c000201a1da97750] [c0114be8] irq_exit+0xe8/0x120
  [15541.631663] [c000201a1da97770] [c0024d0c] timer_interrupt+0x9c/0xe0
  [15541.631718] [c000201a1da977a0] [c0009014] 
decrementer_common+0x114/0x120
  [15541.631784] --- interrupt: 901 at smp_call_function_many+0x330/0x450
  [15541.631784]

[Kernel-packages] [Bug 1771620] Re: Hang on network interface removal in Xen virtual machine

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

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

Title:
Hang on network interface removal in Xen virtual machine

Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed

Bug description:

== SRU Justification ==
Upstream commit 5b5971df3bc2 introduced a regression in v4.15-rc2. This
regression causes a hang on network interface removal in Xen virtual machine.

This regression is fixed by commit c2d2e6738a209 in v4.16-rc4.

== Fix ==
c2d2e6738a20 ("xen-netfront: Fix hang on device removal")

== Regression Potential ==
Low. Fixes a current regression and specific to Xen.

== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.

On a hosting platform running Xen hypervisor, in a virtual machine
with Ubuntu 18.04 system and the default kernel from Ubuntu, I try to
detach a virtual network interface. On the Xen side, the virtual
interface is removed from the VM but the kernel still has the
interface. Then a couple of minutes afterwards, the kernel log show
this kernel trace:

INFO: task xenwatch:108 blocked for more than 120 seconds.
Tainted: GW4.15.0-20-generic #21-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
xenwatchD0 108 2 0x8000
Call Trace:
__schedule+0x297/0x8b0
schedule+0x2c/0x80
xennet_remove+0xda/0x1c0
? wait_woken+0x80/0x80
xenbus_dev_remove+0x54/0xa0
device_release_driver_internal+0x15b/0x220
device_release_driver+0x12/0x20
bus_remove_device+0xec/0x160
? xenbus_otherend_changed+0x110/0x110
device_del+0x13d/0x360
? xenbus_otherend_changed+0x110/0x110
? xenbus_otherend_changed+0x110/0x110
device_unregister+0x1a/0x60
xenbus_dev_changed+0xa3/0x1e0
? xenwatch_thread+0xcc/0x160
frontend_changed+0x21/0x50
xenwatch_thread+0xc4/0x160
? wait_woken+0x80/0x80
kthread+0x121/0x140
? find_watch+0x40/0x40
? kthread_create_worker_on_cpu+0x70/0x70
ret_from_fork+0x35/0x40

In the git repository of Linux, the commit
c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 (xen-netfront: Fix hang on
device removal)

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c2d2e6738a209f0f9dffa2dc8e7292fc45360d61
seems to be related to this situation.

I rebuilded the Ubuntu kernel from the package source and applied this
patch. Once the VM has booted with the new kernel, I was able to
remove network interface without hangs from the kernel.

I also booted the VM with the Ubuntu kernel 4.13.0-42-generic and was
able to remove the network interface with success.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 16 16:36:06 2018
ProcEnviron:
TERM=rxvt-unicode
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

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

--
Mailing list: https://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 1772682] Re: No sound for Dell Inspiron 5758

2018-05-23 Thread Andrew

Hello,

I did not manage to boot 18.04 by usb driver. Some problems in the BIOS
configuration arose.
Please, tell me BIOS setting in this case.

P.S. Note, I tried to boot via Legacy optiion.

Andrew.

On Wed, May 23, 2018 at 11:22 AM, Po-Hsu Lin 
wrote:

> Hi Andrew,
>
> Ubuntu 14.04 Trusty was released in 2014 Apr., which is relatively old
> to your system (probably released in mid-2015) so it's Wifi driver and
> the sound card driver might not be available.
>
> I would recommend you to give 18.04 Bionic a try, you can just test it
> with a LiveUSB.
>
> (Marking this bug as Incomplete base on Joseph's request in comment#2)
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1772682
>
> Title:
>   No sound for Dell Inspiron 5758
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have
>
>
>   I tried to update system but the computer did not finish updating, and
> informed me that there is no internet connection, while the connection was
> OK.
>   As a result, I still  have not been any sound in the computer.
>
>
>   Sincerely yours, Andrew.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.13.0-147-generic 3.13.0-147.196
>   ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
>   Uname: Linux 3.13.0-147-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.23
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CRDA:
>country RU:
> (2402 - 2482 @ 40), (N/A, 20)
> (5735 - 5835 @ 20), (N/A, 30)
>   Date: Tue May 22 19:03:51 2018
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see http://wiki.ubuntu.com/
> DistributionChannelDescriptor
>canonical-oem-somerville-trusty-amd64-20140620-0
>   HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436
>   InstallationDate: Installed on 2016-01-25 (848 days ago)
>   InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary
> 20140620-04:25
>   MachineType: Dell Inc. Inspiron 5758
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic
> root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash
> radeon.modeset=0 nouveau.modeset=0 vt.handoff=7
>   PulseList:
>Error: command ['pacmd', 'list'] failed with exit code 1: Home
> directory not accessible: Permission denied
>No PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-3.13.0-147-generic N/A
>linux-backports-modules-3.13.0-147-generic  N/A
>linux-firmware  1.127.24
>   SourcePackage: linux
>   StagingDrivers: rts5139
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 11/06/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A07
>   dmi.board.name: 09CGRW
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:
> pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 5758
>   dmi.product.version: 01
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1772682/+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/1772682

Title:
  No sound for Dell Inspiron 5758

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have

  
  I tried to update system but the computer did not finish updating, and 
informed me that there is no internet connection, while the connection was OK. 
  As a result, I still  have not been any sound in the computer. 

  
  Sincerely yours, Andrew.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-147-generic 3.13.0-147.196
  ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-147-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Date: Tue May 22 19:03:51 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  HibernationDevice: RESUME=UUID=e4298f48-6ba8-489

[Kernel-packages] [Bug 1772859] [NEW] Network Manager is not able to manage the devices on Ubuntu 18.04

2018-05-23 Thread bugproxy

Public bug reported:

NetworkManager is not able to manage the devices on latest Ubuntu(18.04)
 
---uname output---
Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x 
s390x s390x GNU/Linux
 
Machine Type = z14 s390 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4).
2. Configure a network device and login to the partition through ssh.
3. Now you can see the following output
root@(none):~# nmcli d s
DEVICE  TYPE  STATE  CONNECTION
eth0ethernet  unmanaged  --
eth1ethernet  unmanaged  --
lo  loopback  unmanaged  --
 
Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el 
s390x 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: NetworkManager --version 1.10.4

Userspace tool obtained from project website:  na 
 

Some more information about the issue:

Network device has been configured manually after the image is up from Support 
Element(SE):
- znetconf -a 
- cat /sys/bus/ccwgroup/drivers/qeth//if_name
- ifconfig   netmask 255.255.255.0
- route add default gw  
- SSH service has been configured

This helped us to login to the Lpar. In Lpar
- output of znetconf -c
Device IDs TypeCard Type  CHPID Drv. Name   
  State

-
0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0   
  online
0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000  D0 qeth eth1   
  online

- output of nmcli c s
root@(none):~# nmcli c s
NAME  UUID  TYPE  DEVICE

- output of nmcli d s
root@(none):~# nmcli d s
DEVICE  TYPE  STATE  CONNECTION
eth0ethernet  unmanaged  --
eth1ethernet  unmanaged  --
lo  loopback  unmanaged  --

* The above output shows that devices are not managed by nmcli

After some investigation we found couple of suggestions like
1. Ubuntu(version <17.04): Creating an empty 
file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and 
restarting NM,
   solved the issue.
   
2. Ubuntu(version 17.10): Copying the said 
file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the 
   "unmanaged-devices" to none, resolved the issue.

* link for reference: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1638842

For the latest version(18.04), none of the above solutions worked.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-all bugnameltc-168090 severity-critical 
targetmilestone-inin---

** Tags added: architecture-all bugnameltc-168090 severity-critical
targetmilestone-inin---

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

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Network Manager is not able to manage the devices on Ubuntu 18.04

Status in linux package in Ubuntu:
  New

Bug description:
  NetworkManager is not able to manage the devices on latest Ubuntu(18.04)
   
  ---uname output---
  Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = z14 s390 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4).
  2. Configure a network device and login to the partition through ssh.
  3. Now you can see the following output
  root@(none):~# nmcli d s
  DEVICE  TYPE  STATE  CONNECTION
  eth0ethernet  unmanaged  --
  eth1ethernet  unmanaged  --
  lo  loopback  unmanaged  --
   
  Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el 
s390x 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: NetworkManager --version 1.10.4

  Userspace tool obtained from project website:  na 
   

  Some more information about the issue:

  Network device has been configured manually after the image is up from 
Support Element(SE):
  - znetconf -a 
  - cat /sys/bus/ccwgroup/drivers/qeth//if_name
  - ifconfig   netmask 255.255.255.0
  - route add default gw  
  - SSH service has been configured
  
  This helped us to login to the Lpar. In Lpar
  - output of znetconf -c
  Device IDs TypeCard Type  CHPID Drv. Name 
State
  
--

[Kernel-packages] [Bug 1765977] Re: HiSilicon HNS NIC names are truncated in /proc/interrupts

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

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

Title:
  HiSilicon HNS NIC names are truncated in /proc/interrupts

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  HiSilicon HNS NIC names are truncated in /proc/interrupts, making it 
difficult for an admin to associate activity among adapters in the system.

  [Test Case]
  $ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
  Without the fix:
enahisic2i0-tx0
enahisic2i0-tx1
[...]
enahisic2i0-tx8
enahisic2i0-tx9
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
  With the fix:
enahisic2i0-tx0
enahisic2i0-tx1
enahisic2i0-tx2
[...]
enahisic2i0-tx8
enahisic2i0-tx9
enahisic2i0-tx10
enahisic2i0-tx11
enahisic2i0-tx12
enahisic2i0-tx13
enahisic2i0-tx14
enahisic2i0-tx15

  [Regression Risk]
  Upstream patch, restricted to a single driver for a system we can directly 
test.

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

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

[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

2018-05-23 Thread Claudio Castelpietra

Hi everybody.
I have Ubuntu 18.04 in dual-boot with Windows 10.
With Windows, I downloaded and executed/installed Bios version 1.2.3 from Dell 
support site.
Now Ubuntu 18.04 is back to work.
I hope this helps someone.

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  This bug causes a Dell Latitude 5490/5590 with BIOS update 1.1.9 to get a
  black screen at boot. Specifying 'nomodeset' on the kernel command line works
  around the problem.

  Intel resolved the problem in upstream commit a3520b8992e5.  This commit
  is now in mainline as of 4.17.rc2.  It has also been cc'd to upstream
  stable.

  
  == Fix ==
  a3520b8992e5 ("drm/i915/bios: filter out invalid DDC pins from VBT child 
devices")

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable, so it recieved
  additional upstream review.


  
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
  laptops, originally running BIOS version 1.0.8. The install media and
  the installed OS was running linux-generic-hwe kernel 4.13.0.

  After upgrading BIOS to latest version 1.1.9, the kernel no longer
  boots: right after loading the i915 drm driver, the screen goes black,
  and the machine can only be reset or power cycled. This is true for
  both the installation media, and the OS instance previously installed
  to the disk and updated to the latest hwe kernel 4.13.0-38.

  Specifying 'nomodeset' on the kernel command line works around the
  problem by disabling the i915 drm driver functionality. In that case,
  several display driver function are obviously missing (eg GLX &
  xrandr).

  The problem manifested itself even when using the drm upstream latest 
git-head version. A custom built kernel was used to provide logs for this 
upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=105549

  The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
  https://patchwork.freedesktop.org/patch/216371/
  
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

  I backported this fix to ubuntu-xenial hwe git-head, and tested the
  result successfully. I'd like this fix to be added to the ubuntu-
  xenial linux-generic-hwe kernel.

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

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-05-23 Thread Kai-Heng Feng

Please test the kernel here, it fixes the issue for me:
https://people.canonical.com/~khfeng/lp1752772-r8169-intx/

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
 Mixer name : 'VIA VT1818S'
 Components : 'HDA:11060440,18492818,0010'
 Controls  : 40
 Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1770770] Re: Switch Build-Depends: transfig to fig2dev

** Description changed:

- We are still depending on a transitional package for transfig.  Switch
- to the real package fig2dev.  This is contributing to NBS in cosmic but
- is also valid in bionic.  We need to bear in mind it is _not_ valid in
- xenial.
+ [SRU Justification]
+ 
+ == Impact ==
+ We are still depending on a transitional package for transfig.  Switch to the 
real package fig2dev.  This is contributing to NBS in cosmic but is also valid 
in bionic.  We need to bear in mind it is _not_ valid in xenial.
+ 
+ == Fix ==
+ Change the dependency from transfig into fig2dev in the source package 
control file(s).
+ 
+ == Testcase ==
+ This is a build dependency for the architecture independent part, so 
successful build of amd64 is the testing.
+ 
+ == Regression Potential ==
+ Minimal, this affects only build and even there only generating documentation 
files.

** Changed in: linux-aws (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux-aws (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-azure (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux-azure (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-gcp (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux-gcp (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-kvm (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux-kvm (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-oem (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-raspi2 (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

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

Title:
  Switch Build-Depends: transfig to fig2dev

Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Bionic:
  Fix Committed
Status in linux-kvm source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-raspi2 source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]

  == Impact ==
  We are still depending on a transitional package for transfig.  Switch to the 
real package fig2dev.  This is contributing to NBS in cosmic but is also valid 
in bionic.  We need to bear in mind it is _not_ valid in xenial.

  == Fix ==
  Change the dependency from transfig into fig2dev in the source package 
control file(s).

  == Testcase ==
  This is a build dependency for the architecture independent part, so 
successful build of amd64 is the testing.

  == Regression Potential ==
  Minimal, this affects only build and even there only generating documentation 
files.

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

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

[Kernel-packages] [Bug 1768948] Re: Hotplugging a SATA disk into a SAS controller may cause crash

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

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

Title:
  Hotplugging a SATA disk into a SAS controller may cause crash

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Hotplugging a SATA disk into a SAS controller may trigger a NULL pointer 
dereference, leading to a crash:

  [ 2366.923208] Unable to handle kernel NULL pointer dereference
  at virtual address 07b8
  ...
  [ 2368.766334] Call trace:
  [ 2368.781712] [] sas_find_dev_by_rphy+0x48/0x118
  [ 2368.800394] [] sas_target_alloc+0x28/0x98
  [ 2368.817975] [] scsi_alloc_target+0x248/0x308
  [ 2368.835570] [] __scsi_add_device+0xb8/0x160
  [ 2368.853034] [] ata_scsi_scan_host+0x190/0x230
  [ 2368.871614] [] ata_scsi_hotplug+0xc8/0xe8
  [ 2368.889152] [] process_one_work+0x164/0x438
  [ 2368.908003] [] worker_thread+0x144/0x4b0
  [ 2368.924613] [] kthread+0xfc/0x110

  [Test Case]
  Unplug a SATA disk from a SAS controller and insert a new SATA disk in its 
place.

  [Fix]
  The ATA_PFLAG_SCSI_HOTPLUG flag is what causes libsas to attempt to handle 
hot add/remove. However, for ata devices on a SAS controller, this should be 
handled by libata. The solution is to not set this flag for ATA devices on a 
SAS controller.

  [Regression Risk]
  The fix is a clean cherry-pick from upstream that is tagged for stable. No 
subsequent patches in linux-next have a "Fixes:" marker referencing this patch, 
suggesting no regressions have been found since its introduction.

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

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

[Kernel-packages] [Bug 1767927] Re: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE!

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow
  by CPU ATTEMPT TO RE-ENTER FIRMWARE!

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2018-03-20 14:10:53 ==

  
  == Comment: #1 - Application Cdeadmin  - 2018-03-20 
14:10:54 ==
  == Comment: #2 - Application Cdeadmin  - 2018-03-20 
14:10:56 ==
  --- Comment From dougmill-ibm 2018-03-20 13:51:47 EDT ---
  This problem is not tied to a Linux distro. It will be fixed in firmware, as 
I understand it. Let us close any redundant issues for this same problem. Mark 
them as duplicate.

  == Comment: #3 - Application Cdeadmin  - 2018-03-20 
15:50:54 ==
  --- Comment From mzipse 2018-03-20 15:44:26 EDT ---
  @stewart-ibm @svaidy , I need to you take a first look.  The stop fixes that 
Vaidy had previously highlighted in a recent note are included in the 3/15 PNOR.

  == Comment: #5 - Application Cdeadmin  - 2018-04-04 
16:10:56 ==
  --- Comment From haochanh 2018-04-04 16:04:07 EDT ---
  We update to 0330, bmc=1.18, then we hit bug 1134. Currently we are running 
with disable stop5 but still see the watchdog: hard lockup.
  After 2 hours of test run, I am seeing the "Watchdog: Lockup' and "became 
unstuck"
  
  [Wed Apr  4 13:38:25 2018] Watchdog CPU:42 Hard LOCKUP
  [Wed Apr  4 13:38:25 2018] Modules linked in: vhost_net vhost macvtap macvlan 
tap xfs 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 libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter 
rpcsec_gss_krb5 nfsv4 nfs fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload 
esp4 xfrm_algo mlx5_fpga_tools(OE) mlx5_ib(OE) mlx5_core(OE) mlxfw(OE) cxl 
pnv_php mlx4_en(OE) mlx4_ib(OE) ib_core(OE) mlx4_core(OE) devlink 
mlx_compat(OE) kvm_hv kvm binfmt_misc dm_service_time dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua input_leds joydev mac_hid idt_89hpesx ipmi_powernv
  [Wed Apr  4 13:38:25 2018]  vmx_crypto ipmi_devintf at24 ofpart 
uio_pdrv_genirq cmdlinepart uio powernv_flash ipmi_msghandler mtd 
crct10dif_vpmsum opal_prd ibmpowernv nfsd sch_fq_codel auth_rpcgss nfs_acl 
lockd grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress 
raid6_pq ses enclosure scsi_transport_sas hid_generic usbhid hid lpfc ast 
i2c_algo_bit ttm drm_kms_helper nvmet_fc syscopyarea sysfillrect nvmet 
sysimgblt fb_sys_fops nvme_fc nvme_fabrics crc32c_vpmsum drm i40e 
scsi_transport_fc aacraid [last unloaded: mlxfw]
  [Wed Apr  4 13:38:25 2018] CPU: 42 PID: 0 Comm: swapper/42 Tainted: G 
  OE4.15.0-12-generic #13
  [Wed Apr  4 13:38:25 2018] NIP:  c00a3ca4 LR: c00a3ca4 CTR: 
c0008000
  [Wed Apr  4 13:38:25 2018] REGS: c00ff596fc40 TRAP: 0100   Tainted: G 
  OE (4.15.0-12-generic)
  [Wed Apr  4 13:38:25 2018] MSR:  90001033   CR: 
24004482  XER: 2004
  [Wed Apr  4 13:38:25 2018] CFAR: c00ff596fda0 SOFTE: 42
 GPR00: c00a3ca4 c00ff596fda0 
c16eb200 c00ff596fc40
 GPR04: b0001033 c00a3690 
24004484 000ffa45
 GPR08: 0001 c0d10ed8 
00ff 
 GPR12: 90121033 c7a3ce00 
c00ff596ff90 
 GPR16:  c0047840 
c0047810 c11b5380
 GPR20: 0800 c1722484 
002a 
 GPR24: 00a8 0007 
 0007
 GPR28: c161d270 c00ffb666fd8 
c161d528 0007
  [Wed Apr  4 13:38:25 2018] NIP [c00a3ca4] power9_idle_type+0x24/0x40
  [Wed Apr  4 13:38:25 2018] LR [c00a3ca4] power9_idle_type+0x24/0x40
  [Wed Apr  4 13:38:25 2018] Call Trace:
  [Wed Apr  4 13:38:25 2018] [c00ff596fda0] [c00a3ca4] 
power9_idle_type+0x24/0x40 (unreliable)
  [Wed Apr  4 13:38:25 2018] [c00ff596fdc0] [c0ad1240] 
stop_loop+0x40/0x5c
  [Wed Apr  4 13:38:25 2018] [c00ff596fdf0] [c0acd9a4] 
cpuidle_enter_state+0xa4/0x450
  [Wed Apr  4 13:38:25 2018] [c00ff596fe50] [c017195c] 
call_cpuidle+0x4

[Kernel-packages] [Bug 1765564] Re: fsnotify: Fix fsnotify_mark_connector race

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

** Changed in: linux (Ubuntu Artful)
   Status: Incomplete => Fix Committed

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

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

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

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

Title:
  fsnotify: Fix fsnotify_mark_connector race

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux-azure source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released

Bug description:
  On Azure we have had sporadic cases of soft lockups in fsnotify that
  may very well be mitigated by the following fix. The LKML thread is
  "kernel panics with 4.14.X".

  This should be applied to 4.13 and 4.15 versions of the linux-azure
  kernel, and possibly the 4.15 generic kernel in bionic as well.

  -

  fsnotify() acquires a reference to a fsnotify_mark_connector through
  the SRCU-protected pointer to_tell->i_fsnotify_marks. However, it
  appears that no precautions are taken in fsnotify_put_mark() to
  ensure that fsnotify() drops its reference to this
  fsnotify_mark_connector before assigning a value to its 'destroy_next'
  field. This can result in fsnotify_put_mark() assigning a value
  to a connector's 'destroy_next' field right before fsnotify() tries to
  traverse the linked list referenced by the connector's 'list' field.
  Since these two fields are members of the same union, this behavior
  results in a kernel panic.

  This issue is resolved by moving the connector's 'destroy_next' field
  into the object pointer union. This should work since the object pointer
  access is protected by both a spinlock and the value of the 'flags'
  field, and the 'flags' field is cleared while holding the spinlock in
  fsnotify_put_mark() before 'destroy_next' is updated. It shouldn't be
  possible for another thread to accidentally read from the object pointer
  after the 'destroy_next' field is updated.

  The offending behavior here is extremely unlikely; since
  fsnotify_put_mark() removes references to a connector (specifically,
  it ensures that the connector is unreachable from the inode it was
  formerly attached to) before updating its 'destroy_next' field, a
  sizeable chunk of code in fsnotify_put_mark() has to execute in the
  short window between when fsnotify() acquires the connector reference
  and saves the value of its 'list' field. On the HEAD kernel, I've only
  been able to reproduce this by inserting a udelay(1) in fsnotify().
  However, I've been able to reproduce this issue without inserting a
  udelay(1) anywhere on older unmodified release kernels, so I believe
  it's worth fixing at HEAD.

  References: https://bugzilla.kernel.org/show_bug.cgi?id=199437
  Fixes: 08991e83b7286635167bab40927665a90fb00d81
  CC: sta...@vger.kernel.org
  Signed-off-by: Robert Kolchmeyer 
  Signed-off-by: Jan Kara 

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

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

[Kernel-packages] [Bug 1770770] Re: Switch Build-Depends: transfig to fig2dev

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

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

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

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

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

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

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

Title:
  Switch Build-Depends: transfig to fig2dev

Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Bionic:
  Fix Committed
Status in linux-kvm source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in linux-raspi2 source package in Bionic:
  New

Bug description:
  [SRU Justification]

  == Impact ==
  We are still depending on a transitional package for transfig.  Switch to the 
real package fig2dev.  This is contributing to NBS in cosmic but is also valid 
in bionic.  We need to bear in mind it is _not_ valid in xenial.

  == Fix ==
  Change the dependency from transfig into fig2dev in the source package 
control file(s).

  == Testcase ==
  This is a build dependency for the architecture independent part, so 
successful build of amd64 is the testing.

  == Regression Potential ==
  Minimal, this affects only build and even there only generating documentation 
files.

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

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

[Kernel-packages] [Bug 1764982] Re: [bionic] machine stuck and bonding not working well when nvmet_rdma module is loaded

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

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

Title:
  [bionic] machine stuck and bonding not working well when nvmet_rdma
  module is loaded

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:

  == SRU Justification ==
  This bug causes the machine to get stuck and bonding to not work when
  the nvmet_rdma module is loaded.

  Both of these commits are in mainline as of v4.17-rc1.

  == Fixes ==
  a3dd7d0022c3 ("nvmet-rdma: Don't flush system_wq by default during 
remove_one")
  9bad0404ecd7 ("nvme-rdma: Don't flush delete_wq by default during remove_one")

  == Regression Potential ==
  Low.  Limited to nvme driver and tested by Mellanox.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  == Original Bug Description ==

  Hi
  Machine stuck after unregistering bonding interface when the nvmet_rdma 
module is loading.

  scenario:

   # modprobe nvmet_rdma
   # modprobe -r bonding
   # modprobe bonding  -v mode=1 miimon=100 fail_over_mac=0
   # ifdown eth4
   # ifdown eth5
   # ip addr add 15.209.12.173/8 dev bond0
   # ip link set bond0 up
   # echo +eth5 > /sys/class/net/bond0/bonding/slaves
   # echo +eth4 > /sys/class/net/bond0/bonding/slaves
   # echo -eth4 > /sys/class/net/bond0/bonding/slaves
   # echo -eth5 > /sys/class/net/bond0/bonding/slaves
   # echo -bond0 > /sys/class/net/bonding_masters

  dmesg:

  kernel: [78348.225556] bond0 (unregistering): Released all slaves
  kernel: [78358.339631] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78368.419621] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78378.499615] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78388.579625] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78398.659613] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78408.739655] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78418.819634] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78428.899642] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78438.979614] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78449.059619] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78459.139626] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78469.219623] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78479.299619] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78489.379620] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78499.459623] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78509.539631] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78519.619629] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2

  The following upstream commits that fix this issue

  commit a3dd7d0022c347207ae931c753a6dc3e6e8fcbc1
  Author: Max Gurtovoy 
  Date:   Wed Feb 28 13:12:38 2018 +0200

  nvmet-rdma: Don't flush system_wq by default during remove_one

  The .remove_one function is called for any ib_device removal.
  In case the removed device has no reference in our driver, there
  is no need to flush the system work queue.

  Reviewed-by: Israel Rukshin 
  Signed-off-by: Max Gurtovoy 
  Reviewed-by: Sagi Grimberg 
  Signed-off-by: Keith Busch 
  Signed-off-by: Jens Axboe 

  diff --git a/drivers/nvme/target/rdma.c b/drivers/nvme/target/rdma.c
  index aa8068f..a59263d 100644
  --- a/drivers/nvme/target/rdma.c
  +++ b/drivers/nvme/target/rdma.c
  @@ -1469,8 +1469,25 @@ static struct nvmet_fabrics_ops nvmet_rdma_ops = {
   static void nvmet_rdma_remove_one(struct ib_device *ib_device, void 
*client_data)
   {
  struct nvmet_rdma_queue *queue, *tmp;
  + struct nvmet_rdma_device *ndev;
  + bool found = false;
  +
  + mutex_lock(&device_list_mutex);
  + list_for_each_entry(ndev, &device_list, entry) {
  + if (ndev->device == ib_device) {
  + found = true;
  + break;
  + }
  + }
  + mutex_unlock(&device_list_mutex);
  +
  + if (!found)
  + return;

  -   /* Device is being removed, delete all queues using this device */
  + /*
  +  * IB Device that is used by nvmet controllers is being removed,
  +  * delete all queues using this

[Kernel-packages] [Bug 1768971] Re: Warnings/hang during error handling of SATA disks on SAS controller

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

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

Title:
  Warnings/hang during error handling of SATA disks on SAS controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  When a SATA device, attached to a SAS controller, begins generating errors 
(e.g. device failing, or someone yanked it), the SAS error handling will 
complete, but may leave zombie ATA commands that never get properly 
processed/freed. This can cause some ugly messages on the console, and 
eventually leads to a system hang-up.

  WARNING: CPU: 0 PID: 28512 at drivers/ata/libata-eh.c:4037
  ata_eh_finish+0xb4/0xcc
  CPU: 0 PID: 28512 Comm: kworker/u32:2 Tainted: G W  OE 4.14.0#1
  ..
  Call trace:
  [] ata_eh_finish+0xb4/0xcc
  [] ata_do_eh+0xc4/0xd8
  [] ata_std_error_handler+0x44/0x8c
  [] ata_scsi_port_error_handler+0x480/0x694
  [] async_sas_ata_eh+0x4c/0x80
  [] async_run_entry_fn+0x4c/0x170
  [] process_one_work+0x144/0x390
  [] worker_thread+0x144/0x418
  [] kthread+0x10c/0x138
  [] ret_from_fork+0x10/0x18

  [Test Case]
  I don't have a reliable reproducer for this, but one possible test is to yank 
an active/hotpluggable SATA disk from its controller and see if the above 
symptoms occur.

  [Fix] 
  The solution here is to call into libata to have it process the remaining 
commands, allowing us to free up the zombie commands, preventing the leak and 
eventual starvation.

  [Regression Risk]
  This is a clean cherry-pick from upstream, so any regressions should have 
upstream support. As of this writing, there are no changesets in linux-next 
marked as Fixing this commit, implying that upstream has not yet found/fixed 
any bugs related to it.

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

-- 
Mailing list: https://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 1772682] Re: No sound

2018-05-23 Thread Andrew

Dear Joseph,

Which the build (from BUILD.LOG.amd64

 in v4.17-rc6) should me run?

Andrew.

On Tue, May 22, 2018 at 7:23 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.17 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6
>
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1772682
>
> Title:
>   No sound
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have
>
>
>   I tried to update system but the computer did not finish updating, and
> informed me that there is no internet connection, while the connection was
> OK.
>   As a result, I still  have not been any sound in the computer.
>
>
>   Sincerely yours, Andrew.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.13.0-147-generic 3.13.0-147.196
>   ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
>   Uname: Linux 3.13.0-147-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.23
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CRDA:
>country RU:
> (2402 - 2482 @ 40), (N/A, 20)
> (5735 - 5835 @ 20), (N/A, 30)
>   Date: Tue May 22 19:03:51 2018
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see http://wiki.ubuntu.com/
> DistributionChannelDescriptor
>canonical-oem-somerville-trusty-amd64-20140620-0
>   HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436
>   InstallationDate: Installed on 2016-01-25 (848 days ago)
>   InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary
> 20140620-04:25
>   MachineType: Dell Inc. Inspiron 5758
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic
> root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash
> radeon.modeset=0 nouveau.modeset=0 vt.handoff=7
>   PulseList:
>Error: command ['pacmd', 'list'] failed with exit code 1: Home
> directory not accessible: Permission denied
>No PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-3.13.0-147-generic N/A
>linux-backports-modules-3.13.0-147-generic  N/A
>linux-firmware  1.127.24
>   SourcePackage: linux
>   StagingDrivers: rts5139
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 11/06/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A07
>   dmi.board.name: 09CGRW
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:
> pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 5758
>   dmi.product.version: 01
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1772682/+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/1772682

Title:
  No sound for Dell Inspiron 5758

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have

  
  I tried to update system but the computer did not finish updating, and 
informed me that there is no internet connection, while the connection was OK. 
  As a result, I still  have not been any sound in the computer. 

  
  Sincerely yours, Andrew.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-147-generic 3.13.0-147.196
  ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-147-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Date: Tue May 22 19:03:51 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
ht

[Kernel-packages] [Bug 1768974] Re: Several hisi_sas bug fixes

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

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

Title:
  Several hisi_sas bug fixes

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Several issues have been fixed upstream in the hisi_sas driver:
   - Driver may configure the wrong signal attenuation setting
   - Driver may not negotiate the correct max link rate supported by the phy
   - phy must be disabled before trying to change its link rate
   - Internal abort timeout doesn't take into account link negotiation time
   - Driver returns incorrect values to upper levels

  [Test Case]
  Regression testing on D05 and D06 systems, which have different versions of 
this controller.

  [Regression Risk]
  Code changes are restricted to the hisi_sas driver, and the HisSilicon D05 
and D06 are the only two boards Ubuntu supports that use this driver. Explicit 
testing on these two boards should mitigate the regression risk.

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

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

[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

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

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  IBM is requesting these nine patches to be SRU'd to Bionic.  IBM found
  that the current Bionic kernel contains a problem related to qla2xxx
  driver which causes the following:

  [   66.295233] Unable to handle kernel paging request for data at address 
0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
     msr: 90009033
     dar: 8882f6ed90e9151a
    current = 0xc698fd00
    paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-20.21-generic 4.15.20)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace

  We were able to get rid of this problem cherry picking some of the
  upstream patches. Do you think they might fit in the SRU criteria?

  The commit ids are below and they were easily cherry picked.

  eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug 
after firmware timeout
  6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin 
trigger from sending too many commands
  7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in 
qla2x00_async_iocb_timeout()
  045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call 
dma_free_coherent with IRQ disabled.
  1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session 
free in qlt_free_session_done
  d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session 
deletion by using work_lock
  Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: 
Fixup locking for session deletion')
  94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused 
argument from qlt_schedule_sess_for_dele?
  9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup 
for N2N


  == Regression Potential ==
  Medium.  There are nine patches in this pull request.  They are not specific 
to a
  paticular arch, but they are specific to qla2xxx.

  == Test Case ==
  A test kernel was built with these patches and tested by IBM.
  IBM states the test kernel resolved the bug.

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

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

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

** Attachment added: "Screen picture after kernel crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+attachment/5143246/+files/2018-05-23%2003.21.31.jpg

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

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

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

After reviewing both screen shots I see that I miss read the timestamps
in the first image, so the crash on my second machine has higher
timestamp numbers NOT lower ones. Opps!

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

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

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

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

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

OK, I've had time to try the latest kernel from the daily-live/current
directory called 'cosmic' and it does the same thing. I've tried it on
my second machine and like I said earlier it has the same results but
the timestamps are lower. I'll post a new picture of the screen results.

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

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

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-05-23 Thread Zhanglei Mao

In #18, 4.13 should replaced with 4.4.0-116 which used by 16.04.4 ISO.

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

Title:
  Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI
  boot mode

Status in linux package in Ubuntu:
  Triaged
Status in install-package source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

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

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

[Kernel-packages] [Bug 1769730] Re: Some PCIe errors not surfaced through rasdaemon

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

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

Title:
  Some PCIe errors not surfaced through rasdaemon

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe 
errors to the AER (Advanced Error Reporting) driver, which surfaces them to 
userspace. However, we're currently only reporting "recoverable" errors and not 
errors of other types (e.g. correctable), thus hiding signs of faulty hardware 
from the user.

  [Test Case]
  $ sudo apt install rasdaemon
  # On a system that supports ACPI EINJ (dmesg | grep "ACPI: EINJ"), use the 
attached script to inject a correctable PCIe error.
  $ sudo ras-mc-ctl --errors
  # There should be an entry for the injected error, as shown below:
  No Memory errors.

  PCIe AER events:
  1 2018-05-07 17:55:46 + Fatal error: Receiver Error

  No Extlog errors.

  No MCE errors.

  [Fix]
  There is a 2-patch upstream fix that addresses this issue and cleanly 
cherry-picks into Ubuntu. The solution is to not artficially limit which PCIe 
errors are reported down to the AER driver to those that are recoverable.

  [Regression Risk]
  Above test was ran on x86 & ARM platforms to mitigate regression risk.

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

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

[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

2018-05-23 Thread Vinay Kumar

root@ubuntu18-04:~# uname -a
Linux ubuntu18-04 4.15.0-20-generic #21~lp1768103 SMP Thu May 3 22:29:48 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu18-04:~#

I think we have booted to correct 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/1768103

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.   

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update. 

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue&id=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

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

[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status

2018-05-23 Thread Hajo Locke

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

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

Title:
  Kernel produces empty lines in /proc/PID/status

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

Bug description:
  Hello,

  after running updates today to linux-
  image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that
  iotop is not working any more. Reason are empty lines in
  /proc/PID/status, which confuse iotop (and me)

  In new view there is an empy line between Seccomp and
  Speculation_Store_Bypass:

  
  Seccomp:0

  Speculation_Store_Bypass:   vulnerable
  
  Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a 
relation to spectre/meltdown patches.

  iotop is first application which is failing here, but iam afraid of
  more.

  Thanks

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

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

[Kernel-packages] [Bug 1353947] Re: Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with CirrOS or Ubuntu 12.04

2018-05-23 Thread Thomas Huth

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

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

Title:
  Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with
  CirrOS or Ubuntu 12.04

Status in QEMU:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The issue observed when running an hypervisor with QEMU 2.0/libvirtd 1.2.2
  The VM network interface is attached to a PCI virtual function (SR-IOV).

  When we ran VM with guest OS CirrOS or Ubuntu 12.04 we observed an hipervisor 
hang shortly after the VM is loaded
  We observed the same issue with Mellanox NIC and with Intel NIC

  We’ve tried few combinations of {GuestOS}X{Hypervisor} and we got the 
following findings:
  When a hypervisor is running QEMU 1.5/libvirtd 1.1.1 - no issue observed
  When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CirrOS and Ubuntu 
12.04 guest OSes caused hypervisor hang
  When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CentOS 6.4 and Ubuntu 
13.10 - no issue observed

  The problematic guest OSes are with kernel versions ~3.2.y

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

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

[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status

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

** Changed in: iotop (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/1772671

Title:
  Kernel produces empty lines in /proc/PID/status

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

Bug description:
  Hello,

  after running updates today to linux-
  image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that
  iotop is not working any more. Reason are empty lines in
  /proc/PID/status, which confuse iotop (and me)

  In new view there is an empy line between Seccomp and
  Speculation_Store_Bypass:

  
  Seccomp:0

  Speculation_Store_Bypass:   vulnerable
  
  Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a 
relation to spectre/meltdown patches.

  iotop is first application which is failing here, but iam afraid of
  more.

  Thanks

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

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

[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status

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

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

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

Title:
  Kernel produces empty lines in /proc/PID/status

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

Bug description:
  Hello,

  after running updates today to linux-
  image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that
  iotop is not working any more. Reason are empty lines in
  /proc/PID/status, which confuse iotop (and me)

  In new view there is an empy line between Seccomp and
  Speculation_Store_Bypass:

  
  Seccomp:0

  Speculation_Store_Bypass:   vulnerable
  
  Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a 
relation to spectre/meltdown patches.

  iotop is first application which is failing here, but iam afraid of
  more.

  Thanks

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

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

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

2018-05-23 Thread bugproxy

--- Comment From kamale...@in.ibm.com 2018-05-23 06:27 EDT---
(In reply to comment #7)
> I built a new test kernel and included the source package.
>
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1771844

Thanks for sharing the kernel sources. I was able to verify the patch with 
livepatch-sample.ko :
[ 4772.567633] livepatch_sample: tainting kernel with TAINT_LIVEPATCH
[ 4772.569747] livepatch_sample: module verification failed: signature and/or 
required key missing - tainting kernel
[ 4772.579440] livepatch: enabling patch 'livepatch_sample'
[ 4772.580686] livepatch: 'livepatch_sample': starting patching transition
[ 4777.032952] livepatch: 'livepatch_sample': patching complete
[ 4800.732461] livepatch: 'livepatch_sample': starting unpatching transition
[ 4804.969121] livepatch: 'livepatch_sample': unpatching complete

transition (un)patching works as expected.

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

Title:
  powerpc/livepatch: Implement reliable stack tracing for the
  consistency model

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 ==
  Livepatch has a consistency model which is a hybrid of kGraft and kpatch:  it 
uses kGraft's per-task consistency and syscall barrier switching combined with 
kpatch's stack trace switching. The current approach is stack checking of 
sleeping tasks.  If no affected functions are on the stack of a given task, the 
task is patched.  In most cases this will patch most or all of the tasks on the 
first try.  Otherwise, it'll keep trying periodically.  This patch implements 
the reliable stack tracing for consistency model a.k.a 
HAVE_RELIABLE_STACKTRACE. 

  This will help in switching livepatching implementation to basic per-
  task consistency model. It is the foundation, which will help us
  enable security patches changing function or data semantics. This is
  the biggest remaining piece needed on ppc64le to make livepatch more
  generally useful.

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac

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

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

[Kernel-packages] [Bug 1748345] Re: QCA9377 requires more IRAM banks for its new firmware

2018-05-23 Thread Chih-Hsyuan Ho

Based on Alex's comments, on Whitetail with X36 image, the amdgpu-
pro-18.10-572953 works fine while the 18.20RC'1 showed regression
issues.

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

Title:
  QCA9377 requires more IRAM banks for its new firmware

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

Bug description:
  [Impact]
  The new firmware for QCA9377 supports Qualcomm's RED(Radio Equipment 
Directive) compliance and requires more IRAM banks. The origin 4 banks doesn't 
fit the new BDF and firmware.

  [Fix]
  Change the bank number from 4 to 9.

  [Regression Potential]
  Low, increasing the number of IRAM banks should be no harm.

  [Misc]
  Currently, both driver patch and new firmware do not upstream yet. For the 
sake of avoiding dkms package, we can change t
  he IRAM bank number before their patch is ready.

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

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

[Kernel-packages] [Bug 1772641] Re: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package post-installation script subprocess re

2018-05-23 Thread giancarlo

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => giancarlo (giama956)

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

Title:
  package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to
  install/upgrade: installed linux-image-4.15.0-22-generic package post-
  installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed PyCharm from jetbrains > get this error when starting the 
application.
  Thx for your help!
  Pom

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May 22 08:29:45 2018
  ErrorMessage: installed linux-image-4.15.0-22-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-08 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: linux-signed
  Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: installed linux-image-4.15.0-22-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

2018-05-23 Thread laurie barry

We apparently have a bug in our patch for this regression and have a fix
in hand that we are verifying internally.  Once we push that fix
upstream and have a commit id, we will update this bug.

thank you
Laurie

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

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.   

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update. 

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue&id=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

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

[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status

2018-05-23 Thread Russell Jones

A colleague tried installing a later 4.4.0 kernel, 4.4.0-129 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.129/ (as below) on
16.04.4 LTS and we then don't see the iotop problem.

Linux version 4.4.129-0404129-generic (kernel@kathleen) (gcc version
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) ) #201804240833 SMP Tue
Apr 24 08:35:28 UTC 2018

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

Title:
  Kernel produces empty lines in /proc/PID/status

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

Bug description:
  Hello,

  after running updates today to linux-
  image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that
  iotop is not working any more. Reason are empty lines in
  /proc/PID/status, which confuse iotop (and me)

  In new view there is an empy line between Seccomp and
  Speculation_Store_Bypass:

  
  Seccomp:0

  Speculation_Store_Bypass:   vulnerable
  
  Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a 
relation to spectre/meltdown patches.

  iotop is first application which is failing here, but iam afraid of
  more.

  Thanks

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

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

[Kernel-packages] [Bug 1771301] Re: Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for VXLAN tunnels

2018-05-23 Thread Eric Desrochers

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Eric Desrochers (slashd)

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

Title:
  Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for
  VXLAN tunnels

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  When booting with ipv6.disable=1, vxlan tunnels will fail to
  initialize with the error "vxlan: Cannot bind port 4789, err=-97"
  which is EAFNOSUPPORT.

  Expected result is that vxlan tunnels work when ipv6 is disabled.

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  linux-image-4.4.0-124-generic

  bug is fixed in RHEL in
  https://bugzilla.redhat.com/show_bug.cgi?id=1445054

  Steps to reproduce:

  Deploy two identical 14.04 nodes with the following configuration:

  Add the following to /etc/default/grub then run 'sudo update-grub'
  GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"

  Reboot both nodes
  sudo reboot

  Set up a tunnel using the following commands on each node modifying
  remote_ip to be the ip of the other node. modify veth0 ip to be subnet
  using the tunnel 10.10.10.x/24

  ovs-vsctl del-port br-int vx1
  ovs-vsctl del-port br-int veth1
  ip link del veth0

  ovs-vsctl add-port br-int vx1 -- set interface vx1 type=vxlan 
options:remote_ip=192.168.122.161
  # remote_ip should be the ip of the other node

  ip link add type veth
  ip link set veth0 up
  ip link set veth1 up
  ovs-vsctl add-port br-int veth1
  ip addr add 10.10.10.2/24 dev veth0 # on the second node use 10.10.10.3/24

  Expected result is once the tunnel is configured on each side, you
  should be able to ping the ip of veth0 on the remote side while ipv6
  is disabled.

  ping 10.10.10.2 or 10.10.10.3, whichever is the remote side.

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

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

[Kernel-packages] [Bug 1748345] Re: QCA9377 requires more IRAM banks for its new firmware

** No longer affects: linux-oem (Ubuntu Xenial)

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

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

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

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

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

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

Title:
  QCA9377 requires more IRAM banks for its new firmware

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  The new firmware for QCA9377 supports Qualcomm's RED(Radio Equipment 
Directive) compliance and requires more IRAM banks. The origin 4 banks doesn't 
fit the new BDF and firmware.

  [Fix]
  Change the bank number from 4 to 9.

  [Regression Potential]
  Low, increasing the number of IRAM banks should be no harm.

  [Misc]
  Currently, both driver patch and new firmware do not upstream yet. For the 
sake of avoiding dkms package, we can change t
  he IRAM bank number before their patch is ready.

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

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

[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

2018-05-23 Thread Rachel Greenham

I hid my earlier posts because I reckoned they were noise, tbh. This one
less so. :-)

I have replaced the firmware files with those from the windows driver as
described above and in the linked-to askubuntu. It worked brilliantly
for a few days, no problems at all, but just now failed: Similar to what
I found with btusb.enable_autosuspend=n, after one more sleep/wake cycle
it came up with both bluetooth *and* wifi interfaces absent.

It does at least replicate my earlier findings, that now when it fails,
it kills *both* interfaces, not just bluetooth. Maybe that points to a
slightly different cause. And at least it does happen far less
frequently. Still, the recovery remains to reboot into bios and switch
both interfaces off and on again.

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

Title:
  Bluetooth issues with Dell XPS 13 (9370)

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

Bug description:
  I have the following problem with my Bluetooth module on my new Dell
  XPS 13 (9370) with Ubuntu preinstalled.

  The bluetooth module gets disabled for some reason. The bluetooth
  devices (keyboard and mouse) just stop working in the middle of the
  work, the Bluetooth indicator goes away and the module is also gone in
  the rfkill list.

  To get it back working I need to reboot the machine, start the BIOS,
  disable the Bluetooth module and re-enable it or I have to turn the
  machine completely off and on again. After that, the bluetooth module
  is available again. That's pretty annoying.

  My syslog when this happens:

  Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB 
disconnect, device number 3
  Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 
22
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch 
Status.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
  Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 
21
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSource
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSink
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 
12120 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basi

[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

2018-05-23 Thread Anthony Wong

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

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

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

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

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  New
Status in wireless-regdb source package in Xenial:
  New
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

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

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

[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)

2018-05-23 Thread Volodymyr Shymanskyi

OK, still saw it at least once after applying 'pci=nomsi iommu=soft'.
But in general, it is much much better ;)

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

Title:
  USB stops working after a while (xhci_hcd :00:14.0: Timeout while
  waiting for setup device command)

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my laptop the kernel will sometimes drop the USB hub. After this,
  the laptop doesn't recognise any device plugged in to the USB ports -
  plugging and unplugging any device I've tried into any of the USB
  ports produces no response, not even dmesg entries.

  Strangely this also applies to bluetooth - it no longer works once USB
  has dropped (possibly the module is hung of the bus internally).

  Once this has happened only a reboot fixes it; I've not managed to
  find any combination of module unload/reload or suspend cycles to
  reinitialise things correctly.

  Relevant snippet of dmesg:
  [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe 
the host is dead
  [48838.079742] xhci_hcd :00:14.0: Abort command ring failed
  [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up
  [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079806] sched: RT throttling activated
  [48838.079981] usb 1-1: USB disconnect, device number 16
  [48838.079985] usb 1-1.2: USB disconnect, device number 18
  [48838.079987] usb 1-1.2.3: USB disconnect, device number 19
  [48838.080285] usb 1-1.2.4: USB disconnect, device number 20
  [48838.111892] usb 1-1.4: USB disconnect, device number 17
  [48838.191292] usb 1-4: USB disconnect, device number 6
  [48838.267550] usb 1-10: USB disconnect, device number 8
  [48838.282968] usb 2-1: device not accepting address 8, error -62
  [48838.282983] usb 2-1: USB disconnect, device number 8
  [48838.282986] usb 2-1.2: USB disconnect, device number 9

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  4255 F pulseaudio
   /dev/snd/controlC0:  chris  4255 F pulseaudio
  CRDA:
   country AU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (3, 23), (N/A)
(5250 - 5330 @ 40), (3, 23), (0 ms), DFS
(5735 - 5835 @ 40), (3, 30), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jan 22 12:59:27 2015
  InstallationDate: Installed on 2013-08-06 (533 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Galago UltraPro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd break=mount
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1772760] Re: Touchpad slows down and then stops working

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6

** Changed in: linux-signed (Ubuntu)
   Importance: Undecided => Medium

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

** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  New

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6

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

** Tags added: kernel-da-key

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

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

Title:
  4.4.0-127.153 generates many "sit: non-ECT" messages

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a
  Xenial VM with a sit tunnel, I get such messages:

  May 22 10:49:38 gw kernel: [   68.121601] sit: non-ECT from 0.0.0.0
  with TOS=0x5

  Those are logged quite often:

  # grep -cF 'sit: non-ECT' /var/log/syslog
  9108

  Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the
  issue.

  # lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  # apt-cache policy linux-image-4.4.0-127-generic
  linux-image-4.4.0-127-generic:
Installed: 4.4.0-127.153
Candidate: 4.4.0-127.153
Version table:
   *** 4.4.0-127.153 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-127-generic 4.4.0-127.153
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 20:08 seq
   crw-rw 1 root audio 116, 33 May 22 20:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Tue May 22 21:18:45 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 
kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-127-generic N/A
   linux-backports-modules-4.4.0-127-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.5
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.5
  dmi.sys.vendor: QEMU
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 21:33 seq
   crw-rw 1 root audio 116, 33 May 22 21:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 
nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-b

[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

Thank you for the update, Laurie.

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

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.   

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update. 

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue&id=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

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

[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status

2018-05-23 Thread Hajo Locke

yes, 4.4.0-129 also seems to be ok, but again no
Speculation_Store_Bypass line in /proc/PID/status.

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

Title:
  Kernel produces empty lines in /proc/PID/status

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

Bug description:
  Hello,

  after running updates today to linux-
  image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that
  iotop is not working any more. Reason are empty lines in
  /proc/PID/status, which confuse iotop (and me)

  In new view there is an empy line between Seccomp and
  Speculation_Store_Bypass:

  
  Seccomp:0

  Speculation_Store_Bypass:   vulnerable
  
  Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a 
relation to spectre/meltdown patches.

  iotop is first application which is failing here, but iam afraid of
  more.

  Thanks

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

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

[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)

2018-05-23 Thread Sebastiaan Breedveld

@vshymanskyi: did you fully restart after adding these options to GRUB?
I.e. not boot, add to GRUB, hibernate, boot again and resume. The system
really needs to boot with these options prior to the first hibernate.

Another option you can try: intel_iommu=off (or perhaps amd_iommu=off,
depending on your chipset).

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

Title:
  USB stops working after a while (xhci_hcd :00:14.0: Timeout while
  waiting for setup device command)

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my laptop the kernel will sometimes drop the USB hub. After this,
  the laptop doesn't recognise any device plugged in to the USB ports -
  plugging and unplugging any device I've tried into any of the USB
  ports produces no response, not even dmesg entries.

  Strangely this also applies to bluetooth - it no longer works once USB
  has dropped (possibly the module is hung of the bus internally).

  Once this has happened only a reboot fixes it; I've not managed to
  find any combination of module unload/reload or suspend cycles to
  reinitialise things correctly.

  Relevant snippet of dmesg:
  [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe 
the host is dead
  [48838.079742] xhci_hcd :00:14.0: Abort command ring failed
  [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up
  [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079806] sched: RT throttling activated
  [48838.079981] usb 1-1: USB disconnect, device number 16
  [48838.079985] usb 1-1.2: USB disconnect, device number 18
  [48838.079987] usb 1-1.2.3: USB disconnect, device number 19
  [48838.080285] usb 1-1.2.4: USB disconnect, device number 20
  [48838.111892] usb 1-1.4: USB disconnect, device number 17
  [48838.191292] usb 1-4: USB disconnect, device number 6
  [48838.267550] usb 1-10: USB disconnect, device number 8
  [48838.282968] usb 2-1: device not accepting address 8, error -62
  [48838.282983] usb 2-1: USB disconnect, device number 8
  [48838.282986] usb 2-1.2: USB disconnect, device number 9

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  4255 F pulseaudio
   /dev/snd/controlC0:  chris  4255 F pulseaudio
  CRDA:
   country AU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (3, 23), (N/A)
(5250 - 5330 @ 40), (3, 23), (0 ms), DFS
(5735 - 5835 @ 40), (3, 30), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jan 22 12:59:27 2015
  InstallationDate: Installed on 2013-08-06 (533 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Galago UltraPro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd break=mount
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

2018-05-23 Thread Anthony Wong

crda debdiff for Xenial

** Patch added: "crda_3.13-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/bionic/+source/crda/+bug/1769980/+attachment/5143283/+files/crda_3.13-1ubuntu1.debdiff

** Description changed:

  Intel wireless driver and firmware require updates in order to meet the
  new ETSI regulation [1] for OEM machines shipped from factories.
  
  Intel provided us the following information for what are required to
  update:
  
  1. Kernel driver:
  
  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/
  
  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.
  
  2. linux-firmware
  Requires latest versions from linux-firmware.git
  
  3. wireless-regdb update
  
  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
  
  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.
  
  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.
  
  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.
+ 
+ == SRU Justification for crda ==
+ [Impact]
+ We need crda to include Seth Forshee's public key to support wireless-regdb's 
new format.
+ 
+ [Test Case]
+ Check the key is installed at /lib/crda/pubkeys/sforshee.key.pub.pem.
+ 
+ [Regression Potential]
+ As this is a new file, no regression should happen.

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

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  New
Status in wireless-regdb source package in Xenial:
  New
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

  == SRU Justification for crda ==
  [Impact]
  We need crda to include Seth Forshee's public key to support wireless-regdb's 
new format.

  [Test Case]
  Check the key is instal

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

2018-05-23 Thread Ubuntu Kernel Bot

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

apport-collect 1772760

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1771301] Re: Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for VXLAN tunnels

2018-05-23 Thread Eric Desrochers

** Description changed:

+ [Impact]
+ 
+ When booting with ipv6.disable=1, vxlan tunnels will fail to initialize
+ with the error "vxlan: Cannot bind port 4789, err=-97" which is
+ EAFNOSUPPORT.
+ 
+ Expected result is that vxlan tunnels work when ipv6 is disabled.
+ 
+ # Tested on :
+ Description:  Ubuntu 16.04.4 LTS
+ Release:  16.04
+ Kernel : linux-image-4.4.0-124-generic
+ 
+ [Test Case]
+ 
+ Deploy two identical 14.04 nodes with the following configuration:
+ 
+ Add the following to /etc/default/grub then run 'sudo update-grub'
+ GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
+ 
+ Reboot both nodes
+ sudo reboot
+ 
+ Set up a tunnel using the following commands on each node modifying
+ remote_ip to be the ip of the other node. modify veth0 ip to be subnet
+ using the tunnel 10.10.10.x/24
+ 
+ ovs-vsctl del-port br-int vx1
+ ovs-vsctl del-port br-int veth1
+ ip link del veth0
+ 
+ ovs-vsctl add-port br-int vx1 -- set interface vx1 type=vxlan 
options:remote_ip=192.168.122.161
+ # remote_ip should be the ip of the other node
+ 
+ ip link add type veth
+ ip link set veth0 up
+ ip link set veth1 up
+ ovs-vsctl add-port br-int veth1
+ ip addr add 10.10.10.2/24 dev veth0 # on the second node use 10.10.10.3/24
+ 
+ Expected result is once the tunnel is configured on each side, you
+ should be able to ping the ip of veth0 on the remote side while ipv6 is
+ disabled.
+ 
+ ping 10.10.10.2 or 10.10.10.3, whichever is the remote side.
+ 
+ [Regression Potential]
+ 
+ Regression Potential = Low.
+ 
+ This has been tested by more than one person (pre-SRU) and the patch
+ provide the expected behaviour for this particular bug.
+ 
+ 
+ [Other Info]
+  
+ * Upstream commit:
+ 
https://github.com/torvalds/linux/commit/d074bf9600443403aa24fbc12c1f18eadc90f5aa
+ 
+ * RHEL bug equivalent :
+ https://bugzilla.redhat.com/show_bug.cgi?id=1445054
+ 
+ [Original Description]
+ 
  When booting with ipv6.disable=1, vxlan tunnels will fail to initialize
  with the error "vxlan: Cannot bind port 4789, err=-97" which is
  EAFNOSUPPORT.
  
  Expected result is that vxlan tunnels work when ipv6 is disabled.
  
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  
  linux-image-4.4.0-124-generic
  
  bug is fixed in RHEL in
  https://bugzilla.redhat.com/show_bug.cgi?id=1445054
  
  Steps to reproduce:
  
  Deploy two identical 14.04 nodes with the following configuration:
  
  Add the following to /etc/default/grub then run 'sudo update-grub'
  GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
  
  Reboot both nodes
  sudo reboot
  
  Set up a tunnel using the following commands on each node modifying
  remote_ip to be the ip of the other node. modify veth0 ip to be subnet
  using the tunnel 10.10.10.x/24
  
  ovs-vsctl del-port br-int vx1
  ovs-vsctl del-port br-int veth1
  ip link del veth0
  
  ovs-vsctl add-port br-int vx1 -- set interface vx1 type=vxlan 
options:remote_ip=192.168.122.161
  # remote_ip should be the ip of the other node
  
  ip link add type veth
  ip link set veth0 up
  ip link set veth1 up
  ovs-vsctl add-port br-int veth1
  ip addr add 10.10.10.2/24 dev veth0 # on the second node use 10.10.10.3/24
  
  Expected result is once the tunnel is configured on each side, you
  should be able to ping the ip of veth0 on the remote side while ipv6 is
  disabled.
  
  ping 10.10.10.2 or 10.10.10.3, whichever is the remote side.

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

Title:
  Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for
  VXLAN tunnels

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  [Impact]

  When booting with ipv6.disable=1, vxlan tunnels will fail to
  initialize with the error "vxlan: Cannot bind port 4789, err=-97"
  which is EAFNOSUPPORT.

  Expected result is that vxlan tunnels work when ipv6 is disabled.

  # Tested on :
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  Kernel : linux-image-4.4.0-124-generic

  [Test Case]

  Deploy two identical 14.04 nodes with the following configuration:

  Add the following to /etc/default/grub then run 'sudo update-grub'
  GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"

  Reboot both nodes
  sudo reboot

  Set up a tunnel using the following commands on each node modifying
  remote_ip to be the ip of the other node. modify veth0 ip to be subnet
  using the tunnel 10.10.10.x/24

  ovs-vsctl del-port br-int vx1
  ovs-vsctl del-port br-int veth1
  ip link del veth0

  ovs-vsctl add-port br-int vx1 -- set interface vx1 type=vxlan 
options:remote_ip=192.168.122.161
  # remote_ip should be the ip of the other node

  ip link add type veth
  ip link set veth0 up
  ip link set veth1 up
  ovs-vsctl add-port br-int veth1
  ip addr add 10.10.10.2/24 dev veth0 # on the second node use 10.10.10.3/24

  Expected result is once the tunnel is configured on

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

2018-05-23 Thread bugproxy

--- Comment From cdead...@us.ibm.com 2018-05-23 09:11 EDT---
is there a patch available for this issue?

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

Title:
  [OPAL] Assert fail:
  core/mem_region.c:447:lock_held_by_me(®ion->free_list_lock)

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

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2018-04-03 05:20:56 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-04-05 01:30:56 ==
  --- Comment From pridhiviraj 2018-04-05 01:30:25 EDT ---
  The disto needs 47712a921bb781caf69fca9eae43be19968816cb this level of 
commits need to be backported as suggested by Nick piggin.

  == Comment: #2 - PAWAN K. SINGH <> - 2018-04-06 03:35:49 ==
  which is 
  >>>

  From 47712a921bb781caf69fca9eae43be19968816cb Mon Sep 17 00:00:00 2001
  From: Nicholas Piggin 
  Date: Wed, 17 Jan 2018 22:47:22 +1000
  Subject: [PATCH] powerpc/watchdog: remove arch_trigger_cpumask_backtrace

  The powerpc NMI IPIs may not be recoverable if they are taken in
  some sections of code, and also there have been and still are issues
  with taking NMIs (in KVM guest code, in firmware, etc) which makes them
  a bit dangerous to use.

  Generic code like softlockup detector and rcu stall detectors really
  hammer on trigger_*_backtrace, which has lead to further problems
  because we've implemented it with the NMI.

  So stop providing NMI backtraces for now. Importantly, the powerpc code
  uses NMI IPIs in crash/debug, and the SMP hardlockup watchdog. So if the
  softlockup and rcu hang detection traces are not being printed because
  the CPU is stuck with interrupts off, then the hard lockup watchdog
  should get it with the NMI IPI.

  Fixes: 2104180a5369 ("powerpc/64s: implement arch-specific hardlockup 
watchdog")
  Signed-off-by: Nicholas Piggin 
  Signed-off-by: Michael Ellerman 
  ---
   arch/powerpc/include/asm/nmi.h |  4 
   arch/powerpc/kernel/watchdog.c | 22 --
   2 files changed, 26 deletions(-)

  diff --git a/arch/powerpc/include/asm/nmi.h b/arch/powerpc/include/asm/nmi.h
  index e97f586..9c80939 100644
  --- a/arch/powerpc/include/asm/nmi.h
  +++ b/arch/powerpc/include/asm/nmi.h
  @@ -4,10 +4,6 @@
   
   #ifdef CONFIG_PPC_WATCHDOG
   extern void arch_touch_nmi_watchdog(void);
  -extern void arch_trigger_cpumask_backtrace(const cpumask_t *mask,
  -bool exclude_self);
  -#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace
  -
   #else
   static inline void arch_touch_nmi_watchdog(void) {}
   #endif
  diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c
  index 87da80c..3963baa 100644
  --- a/arch/powerpc/kernel/watchdog.c
  +++ b/arch/powerpc/kernel/watchdog.c
  @@ -393,25 +393,3 @@ int __init watchdog_nmi_probe(void)
}
return 0;
   }
  -
  -static void handle_backtrace_ipi(struct pt_regs *regs)
  -{
  - nmi_cpu_backtrace(regs);
  -}
  -
  -static void raise_backtrace_ipi(cpumask_t *mask)
  -{
  - unsigned int cpu;
  -
  - for_each_cpu(cpu, mask) {
  - if (cpu == smp_processor_id())
  - handle_backtrace_ipi(NULL);
  - else
  - smp_send_nmi_ipi(cpu, handle_backtrace_ipi, 100);
  - }
  -}
  -
  -void arch_trigger_cpumask_backtrace(const cpumask_t *mask, bool exclude_self)
  -{
  - nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi);
  -}
  -- 
  2.7.4

  
  >>>

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

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

[Kernel-packages] [Bug 1772031] Re: kernel backtrace when receiving large UDP packages

2018-05-23 Thread Martin Habets

Many thanks Joseph, I'll give this a try soon.

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

Title:
  kernel backtrace when receiving large UDP packages

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  In Progress

Bug description:
  kernel 4.13.0-41-generic is missing commit a90bcb86ae70:

  Author: Petar Penkov 
  Date:   Tue Aug 29 11:20:32 2017 -0700

  iov_iter: fix page_copy_sane for compound pages
  
  Issue is that if the data crosses a page boundary inside a compound
  page, this check will incorrectly trigger a WARN_ON.
  
  To fix this, compute the order using the head of the compound page and
  adjust the offset to be relative to that head.
  
  Fixes: 72e809ed81ed ("iov_iter: sanity checks for copy to/from page
  primitives")
  
  Signed-off-by: Petar Penkov 
  CC: Al Viro 
  CC: Eric Dumazet 
  Signed-off-by: Al Viro 

  Commit 72e809ed81ed is in kernel 4.13.0-41-generic.
  As a result, when receiving large UDP packages with a small MTU we get 
backtraces like:

  [  361.260969] [ cut here ]
  [  361.260974] WARNING: CPU: 4 PID: 2541 at 
/build/linux-hwe-v6kHHF/linux-hwe-4.13.0/lib/iov_iter.c:693 
copy_page_to_iter+0x194/0x2d0
  [  361.260975] Modules linked in: cmdlinepart sfc(OE) hwmon_vid crc32_generic 
mii rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache 8021q garp mrp 
stp llc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
i]
  [  361.261002] CPU: 4 PID: 2541 Comm: udp_recv Tainted: G   OE   
4.13.0-39-generic #44~16.04.1-Ubuntu
  [  361.261003] Hardware name: Dell Inc. PowerEdge R220/05Y15N, BIOS 1.4.0 
10/23/2014
  [  361.261004] task: 91630b2bae80 task.stack: bb19c2bfc000
  [  361.261005] RIP: 0010:copy_page_to_iter+0x194/0x2d0
  [  361.261006] RSP: 0018:bb19c2bffc60 EFLAGS: 00010202
  [  361.261007] RAX: 1000 RBX: 00df RCX: 
0017c000
  [  361.261008] RDX: 00df RSI: 0f8e RDI: 
f666895279c0
  [  361.261009] RBP: bb19c2bffca0 R08: 106d R09: 
1024
  [  361.261009] R10:  R11: 91630ccc9b00 R12: 
91630d27a300
  [  361.261010] R13: bb19c2bffde0 R14: 00df R15: 
0175
  [  361.261011] FS:  7fb8e7649700() GS:91631fd0() 
knlGS:
  [  361.261012] CS:  0010 DS:  ES:  CR0: 80050033
  [  361.261013] CR2: 14588da85624 CR3: 00024bad2002 CR4: 
001606e0
  [  361.261013] Call Trace:
  [  361.261017]  ? proto_init_net+0x40/0x40
  [  361.261019]  skb_copy_datagram_iter+0x171/0x270
  [  361.261022]  udp_recvmsg+0x108/0x490
  [  361.261024]  inet_recvmsg+0x51/0xc0
  [  361.261026]  sock_recvmsg+0x43/0x50
  [  361.261028]  sock_read_iter+0x90/0xe0
  [  361.261030]  new_sync_read+0xe2/0x130
  [  361.261032]  __vfs_read+0x29/0x40
  [  361.261033]  vfs_read+0x93/0x130
  [  361.261034]  SyS_read+0x55/0xc0
  [  361.261037]  entry_SYSCALL_64_fastpath+0x24/0xab
  [  361.261038] RIP: 0033:0x7fb8e7160260
  [  361.261039] RSP: 002b:7ffed9dd9e38 EFLAGS: 0246 ORIG_RAX: 

  [  361.261040] RAX: ffda RBX:  RCX: 
7fb8e7160260
  [  361.261041] RDX: ffe3 RSI: 5622ad02f0a0 RDI: 
0003
  [  361.261041] RBP: 7ffed9dd9e70 R08:  R09: 
0011
  [  361.261042] R10:  R11: 0246 R12: 
5622ace2e800
  [  361.261043] R13: 7ffed9dd9f50 R14:  R15: 

  [  361.261044] Code: de 4c 89 e7 e8 be fa ff ff 41 83 af a0 12 00 00 01 48 83 
c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 8b 4f 6c 48 d3 e0 e9 9d fe ff ff <0f> ff 
48 83 c4 18 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 49 83 
  [  361.261064] ---[ end trace c0b23bf37be9874d ]---

  This is a request to pull in commit a90bcb86ae70.

  # lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  # uname -a
  Linux c6320f 4.13.0-41-generic #46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  # cat /proc/version_signature 
  Ubuntu 4.13.0-41.46-generic 4.13.16

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

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

[Kernel-packages] [Bug 1768208] Re: OLED X1 yoga lenove, screen ubuntu, brightness issue

2018-05-23 Thread marvin

kernel-bug-exists-upstream-v4.17-rc6

Tested with v4.17-rc6 (771c577c23bac90597c685971d7297ea00f99d11) generic

Screen brightness canot be adapted in any way.

problem persists. If you have any lead, let me know what to test.

** Package changed: linux (Ubuntu) => ubuntu

** Changed in: 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/1768208

Title:
  OLED X1 yoga lenove, screen ubuntu, brightness issue

Status in Ubuntu:
  Confirmed

Bug description:
  As with all the proceeding distros from ubuntu 16.10 the brightness of the 
OLED screen canot be set. Since xrander is no more present there is also no 
hack around this problem anymore. This bug is a killer for using the system as 
full brightness drains the battery quickly.
  OLED screens have no backlight, thus this might be the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 10:45:56 2018
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  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/+bug/1768208/+subscriptions

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-05-23 Thread eric-1111

> https://people.canonical.com/~khfeng/lp1752772-r8169-intx/

It works for me.

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
 Mixer name : 'VIA VT1818S'
 Components : 'HDA:11060440,18492818,0010'
 Controls  : 40
 Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

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

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

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


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.05.21-1 kernel-sru-master-kernel

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

** Changed in: ker

[Kernel-packages] [Bug 1768630] Re: arm64 SDEI support needs trampoline code for KPTI

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

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

Title:
  arm64 SDEI support needs trampoline code for KPTI

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  In bug 1756096, we backported SDEI (Software Delegated Exception Interface) 
support for arm64. However, this backport missed 2 changes that make the SDEI 
entry point a trampoline which make sure the kernel is mapped before 
processing. (The kernel may not be mapped if KPTI is enabled and the exception 
comes in while e.g. executing in usermode). This may lead to a crash.

  [Test Case]
  I haven't yet found a way to inject/simulate an SDEI, so I can only 
regression test by boot testing.

  [Regression Risk]
  The code is restricted to arm64, and should only run on systems that support 
SDEI. I'm unaware of any production firmware that expose the SDEI ACPI table, 
which means this code isn't actively used yet anyway.

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

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

[Kernel-packages] [Bug 1772934] [NEW] linux-gcp: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1772927

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

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

** Affects: linux-gcp (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.05.21-1 kernel-sru-derivative-of-1772927

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecide

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

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1772927

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.05.21-1 kernel-sru-derivative-of-1772927

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1772932] [NEW] linux-kvm: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1772927

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-kvm (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.05.21-1 kernel-sru-derivative-of-1772927

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

2018-05-23 Thread Timo Aaltonen

Hello Anthony, or anyone else affected,

Accepted crda into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/crda/3.13-1ubuntu0.16.04.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: crda (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags removed: verification-done-xenial
** Tags added: verification-needed verification-needed-xenial

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

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  New
Status in wireless-regdb source package in Xenial:
  New
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

  == SRU Justification for crda ==
  [Impact]
  We need crda to include Seth Forshee's public key to support wireless-regdb's 
new format.

  [Test Case]
  Check the key is installed at /lib/crda/pubkeys/sforshee.key.pub.pem.

  [Regression Potential]
  As this is a new file, no regression should happen.

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

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

[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value

2018-05-23 Thread Srinivas Pandruvada

If /var/run points to tmpfs then you can't change. Let me update a new
version of thermald by working around this issue. But you have to build
it yourself and try.

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

Title:
  CPU frequency stuck at minimum value

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

Bug description:
  I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13
  laptop.  Performance is poor.  The CPU (an i7-8550U) is running at
  400MHz, and never speeds up, even when running some of the Phoronix
  Test Suite benchmarks.

  I can use cpupower to switch to the "performance" cpufreq governor,
  but cannot change the frequency with either governor.

  Here is the output of some experiments I ran while Phoronix's c-ray test was 
running.
  __

  gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz
  cpu MHz : 400.008
  cpu MHz : 400.002
  cpu MHz : 400.002
  cpu MHz : 400.003
  cpu MHz : 400.005
  cpu MHz : 400.003
  cpu MHz : 400.001
  cpu MHz : 400.004

  gjditchf@copperplate:/var/log$ cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 400 MHz - 4.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 1.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 400 MHz (asserted by call to kernel)
boost state support:
  Supported: yes
  Active: yes

  gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz
  Setting cpu: 0
  Error setting new values. Common errors:
  - Do you have proper administration rights? (super-user?)
  - Is the governor you requested available and modprobed?
  - Trying to set an invalid policy?
  - Trying to set a specific frequency, but userspace governor is not available,
 for example because of hardware which cannot be set to a specific frequency
 or because the userspace governor isn't loaded?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May  4 12:57:25 2018
  InstallationDate: Installed on 2018-04-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gjditchf   1190 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (10 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre Laptop 13-af0xx
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1
  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 monotone plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A2
  dmi.board.vendor: HP
  dmi.board.version: 55.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre Laptop 1

[Kernel-packages] [Bug 1772931] [NEW] linux-aws: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1772927

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-aws (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.05.21-1 kernel-sru-derivative-of-1772927

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1772930] [NEW] linux-azure: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1772927

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: Joshua R. Poulson (jrp)
 Status: New

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

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

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

** Affects: linux-azure (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.05.21-1 kernel-sru-derivative-of-1772927

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1772940] [NEW] linux-azure: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1772927

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: Joshua R. Poulson (jrp)
 Status: New

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

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

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

** Affects: linux-azure (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1772927 kernel-sru-cycle-2018.05.21-1 xenial

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance:

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1772935 (linux-hwe-edge), bug 1772940 (linux-azure), bug 
1772942 (linux-azure-edge)
+ derivatives: bug 1772929 (linux-raspi2), bug 1772930 (linux-azure), bug 
1772931 (linux-aws), bug 1772932 (linux-kvm), bug 1772933 (linux-oem), bug 
1772934 (linux-gcp)

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
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 is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1772935 (linux-hwe-edge), bug 1772940 (linux-azure), bug 
1772942 (linux-azure-edge)
  derivatives: bug 1772929 (linux-raspi2), bug 1772930 (linux-azure), bug 
1772931 (linux-aws), bug 1772932 (linux-kvm), bug 1772933 (linux-oem), bug 
1772934 (linux-gcp)

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

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

[Kernel-packages] [Bug 1760643] Re: test_072_config_debug_rodata in kernel security test failed with 4.4 X-kvm

** Changed in: linux-kvm (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  test_072_config_debug_rodata in kernel security test failed with 4.4
  X-kvm

Status in QA Regression Testing:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Fix Committed

Bug description:
  == Justification ==
  In Xenial KVM kernel, the CONFIG_DEBUG_KERNEL is enabled, security team would 
like to see CONFIG_DEBUG_RODATA to be enabled as well.

  == Test ==
  Before enabling the config the test_072_config_debug_rodata test from 
qa-regression-testing will fail. After that, the test will pass.
  A test kernel with CONFIG_DEBUG_RODATA enabled in Xenial KVM could be found 
here:
  http://people.canonical.com/~phlin/kernel/lp-1760643/

  == Fix ==
  Enable the CONFIG_DEBUG_RODATA.
  Some other configs were enabled just for skipping the interaction during the 
compilation.

  == Regression Potential ==
  Minimal.
  No code changes, just one config enabled without disabling any other configs.

  The test failed with:
    FAIL: test_072_config_debug_rodata (__main__.KernelSecurityTest)
    CONFIG_DEBUG_RODATA/CONFIG_STRICT_KERNEL_RWX enabled
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 642, in 
test_072_config_debug_rodata
    self.assertEqual(self._test_config(option), expected)
    AssertionError: False != True

  Steps to reproduce:
    Deploy the node with Xenial 4.4 kernel, install linux-kvm
    sudo apt-get install python-minimal
    git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
    git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
    rm -fr autotest/client/tests
    ln -sf ~/autotest-client-tests autotest/client/tests
    AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 16:54:36 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1643558] Re: bnx2x driver crash

2018-05-23 Thread admgsic

Good afternoon, I do not know if this could be related to the same
problem.

I have a network card with 2 ports 10 gb.

05: 00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 
Gigabit Ethernet (rev 10)
05: 00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 
Gigabit Ethernet (rev 10)

They use bnx2x

Then I have an integrated network card with four ports but I have not had a 
problem with it.
02: 00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit 
Ethernet PCIe (rev 01)
02: 00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit 
Ethernet PCIe (rev 01)
02: 00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit 
Ethernet PCIe (rev 01)
02: 00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit 
Ethernet PCIe (rev 01)

They use tg3


The machine is an HP Proliant DL 360 Gen9

And I use it as a cloud driver in OpenStack and at the same time it is
used to provide access to cloud vxlan networks.

The fact is that I had never had problems until 21 days ago in which I
lost the connectivity of a port of 10 GB and restarted the server and
returned to normal.

Other data:

Ubuntu Server 16.04
Kernel: 4.4.0-104-generic
OpenStack: Pike release

The port that failed: ens2f0
driver: bnx2x
version: 1.712.30-0
firmware-version: bc 7.13.23 phy 1.34
expansion-rom-version:
bus-info: : 05: 00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

I have also occupied the other port ens2f1 of the 10gb card but it did
not give me problems and it has less traffic than ens2f0.

LOGS KERNEL:

May  2 02:50:22 hermes kernel: [7904456.095764] bnx2x: 
[bnx2x_stats_update:1232(ens2f0)]storm stats were not updated for 3 times
May  2 02:50:22 hermes kernel: [7904456.095772] bnx2x: 
[bnx2x_stats_update:1233(ens2f0)]driver assert
May  2 02:50:22 hermes kernel: [7904456.095776] bnx2x: 
[bnx2x_panic_dump:919(ens2f0)]begin crash dump -
May  2 02:50:22 hermes kernel: [7904456.095780] bnx2x: 
[bnx2x_panic_dump:929(ens2f0)]def_idx(0x928c)  def_att_idx(0x66d8)  
attn_state(0x0)  spq_prod_idx(0xa5) next_stats_cnt(0x927a)
May  2 02:50:22 hermes kernel: [7904456.095783] bnx2x: 
[bnx2x_panic_dump:934(ens2f0)]DSB: attn bits(0x0)  ack(0x10)  id(0x0)  
idx(0x66d8)
May  2 02:50:22 hermes kernel: [7904456.095785] bnx2x: 
[bnx2x_panic_dump:935(ens2f0)] def (0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xb97 0x0 
0x0 0x0 0x0 0x0 0x0 0x0 0x0)  igu_sb_id(0x0)  igu_seg_id(0x1) pf_id(0x0)  
vnic_id(0x0)  vf_id(0xff)  vf_valid (0x0) state(0x1)
May  2 02:50:22 hermes kernel: [7904456.095807] bnx2x: 
[bnx2x_panic_dump:986(ens2f0)]fp0: rx_bd_prod(0x4278)  rx_bd_cons(0xb1)  
rx_comp_prod(0xb72b)  rx_comp_cons(0xb55f)  *rx_cons_sb(0xb55f)
May  2 02:50:22 hermes kernel: [7904456.095809] bnx2x: 
[bnx2x_panic_dump:989(ens2f0)] rx_sge_prod(0x2b00)  last_max_sge(0x273b)  
fp_hc_idx(0x7dbb)
May  2 02:50:22 hermes kernel: [7904456.095813] bnx2x: 
[bnx2x_panic_dump:1006(ens2f0)]fp0: tx_pkt_prod(0x79cb)  tx_pkt_cons(0x79cb)  
tx_bd_prod(0xe2cc)  tx_bd_cons(0xe2cb)  *tx_cons_sb(0x79cb)
May  2 02:50:22 hermes kernel: [7904456.095816] bnx2x: 
[bnx2x_panic_dump:1006(ens2f0)]fp0: tx_pkt_prod(0x0)  tx_pkt_cons(0x0)  
tx_bd_prod(0x0)  tx_bd_cons(0x0)  *tx_cons_sb(0x0)
May  2 02:50:22 hermes kernel: [7904456.095818] bnx2x: 
[bnx2x_panic_dump:1006(ens2f0)]fp0: tx_pkt_prod(0x0)  tx_pkt_cons(0x0)  
tx_bd_prod(0x0)  tx_bd_cons(0x0)  *tx_cons_sb(0x0)
May  2 02:50:22 hermes kernel: [7904456.095821] bnx2x: 
[bnx2x_panic_dump:1017(ens2f0)] run indexes (0x7dbb 0x0)
May  2 02:50:22 hermes kernel: [7904456.095824] bnx2x: 
[bnx2x_panic_dump:1023(ens2f0)] indexes (0x0 0xb55f 0x0 0x0 0x0 0x79cb 0x0 
0x0)pf_id(0x0)  vf_id(0xff)  vf_valid(0x0) vnic_id(0x0)  same_igu_sb_1b(0x1) 
state(0x1)
May  2 02:50:22 hermes kernel: [7904456.095847] SM[0] __flags (0x0) igu_sb_id 
(0x2)  igu_seg_id(0x0) time_to_expire (0x1504213f) timer_value(0xff)
May  2 02:50:22 hermes kernel: [7904456.095849] SM[1] __flags (0x0) igu_sb_id 
(0x2)  igu_seg_id(0x0) time_to_expire (0x115edd65) timer_value(0xff)
May  2 02:50:22 hermes kernel: [7904456.095851] INDEX[0] flags (0x0) timeout 
(0x0)
May  2 02:50:22 hermes kernel: [7904456.095852] INDEX[1] flags (0x2) timeout 
(0x6)
May  2 02:50:22 hermes kernel: [7904456.095854] INDEX[2] flags (0x0) timeout 
(0x0)
May  2 02:50:22 hermes kernel: [7904456.095855] INDEX[3] flags (0x0) timeout 
(0x0)
May  2 02:50:22 hermes kernel: [7904456.095857] INDEX[4] flags (0x1) timeout 
(0x0)
May  2 02:50:22 hermes kernel: [7904456.095859] INDEX[5] flags (0x3) timeout 
(0xc)
May  2 02:50:22 hermes kernel: [7904456.095860] INDEX[6] flags (0x3) timeout 
(0xc)
May  2 02:50:22 hermes kernel: [7904456.095862] INDEX[7] flags (0x3) timeout 
(0xc)
May  2 02:50:22 hermes kernel: [7904456.095865] bnx2x: 
[bnx2x_panic_dump:986(ens2f0)]fp1: rx_bd_prod(0x827)  rx_bd_cons(0x660)  
rx_comp_prod(0xdbce)  rx_comp_c

[Kernel-packages] [Bug 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest

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

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

Title:
  [LTC Test] Ubuntu 18.04:  tm_sigreturn failed on P8 compat mode
  16.04.04 guest

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  
  == SRU Justification ==
  IBM is seeing tm_sigreturn test failures on P8 and P9 hosts.  The bad thing
  exception is being raised when executing the following line:

  c004fcfc: b0 04 03 e8 ld r0,1200(r3)
  -> c004fd00: a6 23 02 7c mtspr 130,r0

  Which is basically restoring TEXASR in the thread.

  ISA says "These registers can be written only when in Non-transactional
  state" and the MSR is set to be transactional (suspended):

  MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]

  That explains why they are getting the "bad thing exception". A mtspr is
  being called with a transaction suspended.

  This test failure is fixed by upstream commit 78a3e8889b4b.
  Upstream commit 78a3e8889b4b is in mainline as of 4.8-rc5.

  == Fix ==
  78a3e8889b4b ("powerpc: signals: Discard transaction state from signal 
frames")

  == Regression Potential ==
  Low.  Specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  This test fails in the same way on a P8 host, so it is nothing to do with P9.

  There have been many TM bugs fixed upstream since 4.4. I would suggest
  starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state
  in signal handler", 2017-08-22) and see if that helps.

  The bad thing exception is being raised when executing the following
  line:

   c004fcfc:   b0 04 03 e8 ld  r0,1200(r3)
    ->   c004fd00:   a6 23 02 7c mtspr   130,r0

  Which is basically restoring TEXASR in the thread.

  ISA says "These registers can be written only when in Non-
  transactional state" and the MSR is set to be transactional
  (suspended):

  MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]

  That explains why we are getting the "bad thing exception". A mtspr is
  being called with a transaction suspended.

  I think we need the following commit to have this fixed:

  commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
  Author: Cyril Bur 
  Date:   Tue Aug 23 10:46:17 2016 +1000

  powerpc: signals: Discard transaction state from signal frames

  Userspace can begin and suspend a transaction within the signal
  handler which means they might enter sys_rt_sigreturn() with the
  processor in suspended state.

  sys_rt_sigreturn() wants to restore process context (which may have
  been in a transaction before signal delivery). To do this it must
  restore TM SPRS. To achieve this, any transaction initiated within the
  signal frame must be discarded in order to be able to restore TM SPRs
  as TM SPRs can only be manipulated non-transactionally..
  >From the PowerPC ISA:
    TM Bad Thing Exception [Category: Transactional Memory]
     An attempt is made to execute a mtspr targeting a TM register in
     other than Non-transactional state.

  Not doing so results in a TM Bad Thing:
  [12045.221359] Kernel BUG at c0050a40 [verbose debug info 
unavailable]
  [12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr 
0x201033)
  [12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
  [12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
  [12045.221634] Modules linked in: 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 stp 
llc ebtable_filter
   ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
kvm_hv kvm
   uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses 
enclosure
   scsi_transport_sas bnx2x ipr mdio libcrc32c
  [12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0 
#34
  [12045.24] task: c000fce38600 ti: c000fceb4000 task.ti: 
c000fceb4000
  [12045.93] NIP: c0050a40 LR: c00163bc CTR: 

  [12045.222361] REGS: c000fceb7ac0 TRAP: 0700   Not tainted (4.7.0)
  [12045.222418] MSR: 900300201033  CR: 
28444280  XER: 2000
  [12045.222625] CFAR: c00163b8 SOFTE: 0 PACATMSCRATCH: 
90014280f033
  GPR00: 0110b801 c000fceb7d40 c139c100 c000fce390d0
  GPR04: 90034280f033   
  GPR08: 000

[Kernel-packages] [Bug 1766573] Re: linux < 4.11: unable to use netfilter logging from non-init namespaces

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

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

Title:
  linux < 4.11: unable to use netfilter logging from non-init namespaces

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

Bug description:
  Was disabled by the following patch (linux 3.10):
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2
  netfilter: xt_LOG: add net namespace support for xt_LOG

  And fixed in linux 4.11:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3
  netfilter: allow logging from non-init namespaces

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

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

[Kernel-packages] [Bug 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation

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

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

Title:
  [Ubuntu 16.04] kernel: fix rwlock implementation

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  IBM reported this bug due to a regression introduced by mainline commit
  94232a4332de.  IBM has requested this SAUCE backport to resolve this
  regression in Artful and Xenial.

  With Bionic and v4.15, the rwlock code has been rewritten. See upstream 
gitcommit:
  eb3b7b848fb3 ("s390/rwlock: introduce rwlock wait queueing").

  Since the upstream code has been rewritten there also won't be an upstream
  git commit id available which contains the attached fix.

  == Fix ==
  UBUNTU: SAUCE: (no-up) s390: fix rwlock implementation

  == Regression Potential ==
  Low.  The backport was written and tested by IBM. It is specific to s390.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  Description:  kernel: fix rwlock implementation
  Symptom:  Kernel hangs, due to deadlock on an rwlock.
  Problem:  With upstream commit 94232a4332de ("s390/rwlock: improve writer
    fairness") rwlock writer fairness was supposed to be
    implemented. If a writer tries to take an rwlock it sets
    unconditionally the writer bit within the lock word and waits
    until all readers have released the lock. This however can lead
    to a deadlock since rwlocks can be taken recursively by readers.
    If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to
    write-lock the lock, then CPU 1 sets the writer bit and
    afterwards busy waits for CPU 0 to release the lock. If now CPU 0
    tries to read-lock the lock again (recursively) it will also 
busy
    wait until CPU 1 removes the writer bit, which will never 
happen,
    since it waits for the first reader on CPU 0 to release the 
lock.
  Solution: Revert the rwlock writer fairness semantics again.

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

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

[Kernel-packages] [Bug 1772490] Re: 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error

2018-05-23 Thread Jason Hobbs

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

** This bug has been marked a duplicate of bug 1768893
   installation on several nodes failed with errors relating to dmsetup remove 
of ceph devices.

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

Title:
  'Deploying' timed out after 40 minutes / Failedbcache:
  register_bcache() error

Status in curtin:
  Invalid
Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have a few runs over the weekend failed to deploy with maas 2.3.3.

  May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from 
DEPLOYING to FAILED_DEPLOYMENT
  May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node 
operation 'Deploying' timed out after 40 minutes.

  https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e-
  4de1-9b30-0ecb28eb3c35

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

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

[Kernel-packages] [Bug 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking

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

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

Title:
  [SRU][Bionic/Artful] fix false positives in W+X checking

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping 
at address 00a99000/0xa99000" while booting. These messages are a false 
positive and triggered at random.

  [Test]
  There is no reliable way to reproduce these warnings, they are triggered at 
random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. 
A test kernel is available in
  ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and 
Cavium Thunderx.

  ubuntu@awrep2:~$ uname -a
  Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 
16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux

  ubuntu@boomer:~$ uname -a 
  Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 
16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
  ubuntu@boomer:~$ 

  
  [Fix]
  Upstream fix is available in linux-next

  65d313ee1a7d init: fix false positives in W+X checking

  [Regression Potential]
  potential for any regression is low.

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

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

[Kernel-packages] [Bug 1765668] Re: Unable to boot Xenial cloud image on Bionic ARM64 ThunderX / Azure

2018-05-23 Thread  Christian Ehrhardt 

I implemented this in uvtool for Bionic, which is why it work.
It is clearly a feature - I don't think it is SRUable.

If you think it is, pull the changes out of the repo and ask to push it to 
xenial and artful, but you'd need to convince rbasak twice that it is SRUable 
(once for uvtool and once for SRU).
Or just use uvtool from the master ppa [1] and it will work.4

[1]: https://launchpad.net/~uvtool-dev/+archive/ubuntu/master

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

Title:
  Unable to boot Xenial cloud image on Bionic ARM64 ThunderX / Azure

Status in linux-azure package in Ubuntu:
  New
Status in uvtool package in Ubuntu:
  Incomplete
Status in linux-azure source package in Bionic:
  New
Status in uvtool source package in Bionic:
  Incomplete

Bug description:
  Similar to bug 1744754, I can create an Artful KVM on this ThunderX
  ARM64 node with Bionic installed. But not with Xenial.

  Steps:
 # uvt-simplestreams-libvirt sync release=xenial arch=arm64
 # uvt-kvm create test release=xenial arch=arm64
 # uvt-kvm wait test --insecure
 uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:72:91:3a.
 # uvt-kvm ip test
 uvt-kvm: error: no IP address found for libvirt machine 'test'.

  With Artful, although it will return error due to the "Permission Denied" 
error, but you can still ssh into that KVM:
  # uvt-simplestreams-libvirt sync release=artful arch=arm64
  # uvt-kvm create a-test release=artful arch=arm64
  # uvt-kvm wait a-test --insecure
  ubuntu@192.168.122.119: Permission denied (publickey).
  Traceback (most recent call last):
File "/usr/bin/uvt-kvm", line 35, in 
  uvtool.libvirt.kvm.main_cli_wrapper(sys.argv[1:])
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 861, in 
main_cli_wrapper
  main(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 856, in 
main
  args.func(parser, args)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 782, in 
main_wait
  main_wait_remote(parser, args)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 745, in 
main_wait_remote
  insecure=args.insecure,
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 614, in 
ssh
  ssh_call, preexec_fn=subprocess_setup, close_fds=True, stdin=stdin
File "/usr/lib/python2.7/subprocess.py", line 190, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '[u'ssh', u'-o', 
u'UserKnownHostsFile=/tmp/uvt-kvm.known_hoststmpnK_mba', u'-l', u'ubuntu', 
u'192.168.122.119', u'env', u'UVTOOL_WAIT_INTERVAL=8.0', 
u'UVTOOL_WAIT_TIMEOUT=120.0', u'sh', u'-']' returned non-zero exit status 255
  # uvt-kvm ip a-test
  192.168.122.119
  # ssh ubuntu@192.168.122.119 "lsb_release -a"
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: User Name 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 20 09:15 seq
   crw-rw 1 root audio 116, 33 Apr 20 09:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Apr 20 10:33:57 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro acpi=force iommu.passthrough=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.vers

[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

2018-05-23 Thread Seth Forshee

Turns out there's a hiccup with the crda update for xenial, unbeknownst
to us wireless-regdb is (incorrectly) already installing my public key.
The easiest path forward seems to be just leaving crda as is and making
the regdb update continue to install my key. As such I'm marking
verification for xenial as failed.

** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial

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

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  New
Status in wireless-regdb source package in Xenial:
  New
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

  == SRU Justification for crda ==
  [Impact]
  We need crda to include Seth Forshee's public key to support wireless-regdb's 
new format.

  [Test Case]
  Check the key is installed at /lib/crda/pubkeys/sforshee.key.pub.pem.

  [Regression Potential]
  As this is a new file, no regression should happen.

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

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

[Kernel-packages] [Bug 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation

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

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

Title:
  [Ubuntu 16.04] kernel: fix rwlock implementation

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  IBM reported this bug due to a regression introduced by mainline commit
  94232a4332de.  IBM has requested this SAUCE backport to resolve this
  regression in Artful and Xenial.

  With Bionic and v4.15, the rwlock code has been rewritten. See upstream 
gitcommit:
  eb3b7b848fb3 ("s390/rwlock: introduce rwlock wait queueing").

  Since the upstream code has been rewritten there also won't be an upstream
  git commit id available which contains the attached fix.

  == Fix ==
  UBUNTU: SAUCE: (no-up) s390: fix rwlock implementation

  == Regression Potential ==
  Low.  The backport was written and tested by IBM. It is specific to s390.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  Description:  kernel: fix rwlock implementation
  Symptom:  Kernel hangs, due to deadlock on an rwlock.
  Problem:  With upstream commit 94232a4332de ("s390/rwlock: improve writer
    fairness") rwlock writer fairness was supposed to be
    implemented. If a writer tries to take an rwlock it sets
    unconditionally the writer bit within the lock word and waits
    until all readers have released the lock. This however can lead
    to a deadlock since rwlocks can be taken recursively by readers.
    If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to
    write-lock the lock, then CPU 1 sets the writer bit and
    afterwards busy waits for CPU 0 to release the lock. If now CPU 0
    tries to read-lock the lock again (recursively) it will also 
busy
    wait until CPU 1 removes the writer bit, which will never 
happen,
    since it waits for the first reader on CPU 0 to release the 
lock.
  Solution: Revert the rwlock writer fairness semantics again.

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

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

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

Public bug reported:

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

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

backports: bug 1772953 (linux-gcp), bug 1772956 (linux-oem), bug 1772957 
(linux-hwe)
derivatives: bug 1772952 (linux-raspi2)

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

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

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

** Affects: linux (Ubuntu Artful)
 Importance: Medium
 Status: Confirmed


** Tags: artful kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.05.21-1 kernel-sru-master-kernel

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: artful

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1770565] Re: [i915_bpo] Fix flickering issue after panel change

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  [i915_bpo] Fix flickering issue after panel change

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  A certain OEM laptop changed the panel type/vendor, and the change regressed 
the driver causing a flickering image. The ODM has tools to measure various 
values of the driver/panel combination, and determined that some voltage levels 
were way too low to pass the spec. The process to bisect the commits took 
weeks, so while it's technically possible that this issue was fixed by a single 
commit (drm/i915: Ignore OpRegion panel type except on select machines), we've 
also kept another 10 commits which upstream thought should help (and did, they 
improved the measured values but not enough).

  So, this backport carries all 11 commits from 4.8/4.9 that the ODM
  verified to pass the tests.

  [Test case]
  Needs to be tested with the ODM tools to be sure.

  [Regression potential]
  There is some, but apart from the necessary refactoring the rest are bugfixes 
to match the HW specs, so this should in fact fix a lot more than just this 
certain machine.

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

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

[Kernel-packages] [Bug 1772950] [NEW] dkms key enrolled in mok, but dkms module fails to load

2018-05-23 Thread Dan Watkins

Public bug reported:

At my last reboot, I was prompted to enable SecureBoot, so I did.

When I booted, however, I noticed that the virtualbox service failed to
start because it couldn't load its kernel module.  If I attempt the same
thing, I see that there's an issue with keys:

$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available

I do have keys enrolled; `mokutil --list-enrolled` produces
http://paste.ubuntu.com/p/rntTQr5XJV/

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

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

Title:
  dkms key enrolled in mok, but dkms module fails to load

Status in dkms package in Ubuntu:
  New

Bug description:
  At my last reboot, I was prompted to enable SecureBoot, so I did.

  When I booted, however, I noticed that the virtualbox service failed
  to start because it couldn't load its kernel module.  If I attempt the
  same thing, I see that there's an issue with keys:

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available

  I do have keys enrolled; `mokutil --list-enrolled` produces
  http://paste.ubuntu.com/p/rntTQr5XJV/

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

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

[Kernel-packages] [Bug 1772490] Re: 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error

2018-05-23 Thread Andres Rodriguez

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

As such, I don't believe this is a MAAS issue.

** Changed in: maas
   Status: Incomplete => Invalid

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

Title:
  'Deploying' timed out after 40 minutes / Failedbcache:
  register_bcache() error

Status in curtin:
  Invalid
Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have a few runs over the weekend failed to deploy with maas 2.3.3.

  May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from 
DEPLOYING to FAILED_DEPLOYMENT
  May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node 
operation 'Deploying' timed out after 40 minutes.

  https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e-
  4de1-9b30-0ecb28eb3c35

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

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

[Kernel-packages] [Bug 1772490] Re: 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error

2018-05-23 Thread Andres Rodriguez

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

After further looking into this, I can determine that:

1. Curtin installed successfully despite the kernel issues
1. Curtin told MAAS the installation completed successfully.
3. cloud-init told the machine to reboot.

At this point, we lose all logs, but from what we can see is that:

1. The machine never attempted to PXE boot post-deployment
2. There's no indication that the machine actually booted into the installed 
environment.

This leads me to believe that due to the kernel error above, the kernel
could have crashed right before the machine rebooted, which prevented
the machine from rebooting into the installed system. This is not
something available in the rsyslog because at the time, networking is
down. This would only show on a console log.

That said, the logs definitely show that the machine never came up
again.

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

Title:
  'Deploying' timed out after 40 minutes / Failedbcache:
  register_bcache() error

Status in curtin:
  Invalid
Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have a few runs over the weekend failed to deploy with maas 2.3.3.

  May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from 
DEPLOYING to FAILED_DEPLOYMENT
  May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node 
operation 'Deploying' timed out after 40 minutes.

  https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e-
  4de1-9b30-0ecb28eb3c35

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

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

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

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1772951

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-oem (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1772951 kernel-sru-cycle-2018.05.21-1 xenial

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1772950] Re: dkms key enrolled in mok, but dkms module fails to load

2018-05-23 Thread Dan Watkins

term.log for installation of my current kernel:
https://paste.ubuntu.com/p/3TVVFpFSNX/

term.log from the last time I see virtualbox DKMS stuff happening:
https://paste.ubuntu.com/p/7f7p6t48pn/

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

Title:
  dkms key enrolled in mok, but dkms module fails to load

Status in dkms package in Ubuntu:
  Incomplete

Bug description:
  At my last reboot, I was prompted to enable SecureBoot, so I did.

  When I booted, however, I noticed that the virtualbox service failed
  to start because it couldn't load its kernel module.  If I attempt the
  same thing, I see that there's an issue with keys:

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available

  I do have keys enrolled; `mokutil --list-enrolled` produces
  http://paste.ubuntu.com/p/rntTQr5XJV/

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

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

[Kernel-packages] [Bug 1772953] [NEW] linux-gcp: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1772951

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

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

** Affects: linux-gcp (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1772951 kernel-sru-cycle-2018.05.21-1 xenial

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1772953 (linux-gcp), bug 1772956 (linux-oem), bug 1772957 
(linux-hwe)
+ derivatives: bug 1772952 (linux-raspi2)

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

Title:
  linux:  -proposed tracker

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

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

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

  backports: bug 1772953 (linux-gcp), bug 1772956 (linux-oem), bug 1772957 
(linux-hwe)
  derivatives: bug 1772952 (linux-raspi2)

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

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

[Kernel-packages] [Bug 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation

2018-05-23 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  [Ubuntu 16.04] kernel: fix rwlock implementation

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  IBM reported this bug due to a regression introduced by mainline commit
  94232a4332de.  IBM has requested this SAUCE backport to resolve this
  regression in Artful and Xenial.

  With Bionic and v4.15, the rwlock code has been rewritten. See upstream 
gitcommit:
  eb3b7b848fb3 ("s390/rwlock: introduce rwlock wait queueing").

  Since the upstream code has been rewritten there also won't be an upstream
  git commit id available which contains the attached fix.

  == Fix ==
  UBUNTU: SAUCE: (no-up) s390: fix rwlock implementation

  == Regression Potential ==
  Low.  The backport was written and tested by IBM. It is specific to s390.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  Description:  kernel: fix rwlock implementation
  Symptom:  Kernel hangs, due to deadlock on an rwlock.
  Problem:  With upstream commit 94232a4332de ("s390/rwlock: improve writer
    fairness") rwlock writer fairness was supposed to be
    implemented. If a writer tries to take an rwlock it sets
    unconditionally the writer bit within the lock word and waits
    until all readers have released the lock. This however can lead
    to a deadlock since rwlocks can be taken recursively by readers.
    If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to
    write-lock the lock, then CPU 1 sets the writer bit and
    afterwards busy waits for CPU 0 to release the lock. If now CPU 0
    tries to read-lock the lock again (recursively) it will also 
busy
    wait until CPU 1 removes the writer bit, which will never 
happen,
    since it waits for the first reader on CPU 0 to release the 
lock.
  Solution: Revert the rwlock writer fairness semantics again.

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

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

[Kernel-packages] [Bug 1771344] Re: Fix enabling bridge MMIO windows

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092677.html

** Description changed:

- == Comment: #0 - Breno Leitao  
+ == SRU Justification ==
+ IBM is requesting this patch in Bionic and Artful to fix a regression.  The
+ regression was introduced in v3.11-rc1.  The patch fixes enabling bridge
+ MMIO windows.  Commit 13a83eac373c was also cc'd to upstream stable, and
+ has already landed in Xenial via upstream stable updates.
+ 
+ == Fix ==
+ 13a83eac373c ("powerpc/eeh: Fix enabling bridge MMIO windows")
+ 
+ == Regression Potential ==
+ Low.  Limited to powerpc and fixes a current regression.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ == Comment: #0 - Breno Leitao 
  On boot we save the configuration space of PCIe bridges. We do this so
  when we get an EEH event and everything gets reset that we can restore
  them.
- 
+ 
  Unfortunately we save this state before we've enabled the MMIO space
  on the bridges. Hence if we have to reset the bridge when we come back
  MMIO is not enabled and we end up taking an PE freeze when the driver
  starts accessing again.
- 
+ 
  This patch forces the memory/MMIO and bus mastering on when restoring
  bridges on EEH. Ideally we'd do this correctly by saving the
  configuration space writes later, but that will have to come later in
  a larger EEH rewrite. For now we have this simple fix.
- 
+ 
  The original bug can be triggered on a boston machine by doing:
-  echo 0x8000 > 
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
+  echo 0x8000 > 
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
  On boston, this PHB has a PCIe switch on it.  Without this patch,
  you'll see two EEH events, 1 expected and 1 the failure we are fixing
  here. The second EEH event causes the anything under the PHB to
  disappear (i.e. the i40e eth).
- 
+ 
  With this patch, only 1 EEH event occurs and devices properly recover.
  
  This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should be
  part of Ubuntu 18.04 kernel.

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Also affects: linux (Ubuntu Cosmic)
   Importance: High
 Assignee: Joseph Salisbury (jsalisbury)
   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/1771344

Title:
  Fix enabling bridge MMIO windows

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == SRU Justification ==
  IBM is requesting this patch in Bionic and Artful to fix a regression.  The
  regression was introduced in v3.11-rc1.  The patch fixes enabling bridge
  MMIO windows.  Commit 13a83eac373c was also cc'd to upstream stable, and
  has already landed in Xenial via upstream stable updates.

  == Fix ==
  13a83eac373c ("powerpc/eeh: Fix enabling bridge MMIO windows")

  == Regression Potential ==
  Low.  Limited to powerpc and fixes a current regression.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Comment: #0 - Breno Leitao 
  On boot we save the configuration space of PCIe bridges. We do this so
  when we get an EEH event and everything gets reset that we can restore
  them.

  Unfortunately we save this state before we've enabled the MMIO space
  on the bridges. Hence if we have to reset the bridge when we come back
  MMIO is not enabled and we end up taking an PE freeze when the driver
  starts accessing again.

  This patch forces the memory/MMIO and bus mastering on when restoring
  bridges on EEH. Ideally we'd do this correctly by saving the
  configuration space writes later, but that will have to come later in
  a larger EEH rewrite. For now we have this simple fix.

  The original bug can be triggered on a boston machine by doing:
   echo 0x8000 > 
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
  On boston, this PHB has a PCIe switch on it.  Without this patch,
  you'll see two EEH events, 1 expected and 1 the failure we are fixing
  here. The second EEH event causes the anything under the PHB to
  disappear (i.e. the i40e eth).

  With this patch, only 1 EEH event occurs and devices properly recover.

  This is commit id 13a83eac373c49c0a081cb

[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

2018-05-23 Thread Anthony Wong

** Changed in: crda (Ubuntu Xenial)
   Status: Fix Committed => Invalid

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

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  New
Status in wireless-regdb source package in Xenial:
  New
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

  == SRU Justification for crda ==
  [Impact]
  We need crda to include Seth Forshee's public key to support wireless-regdb's 
new format.

  [Test Case]
  Check the key is installed at /lib/crda/pubkeys/sforshee.key.pub.pem.

  [Regression Potential]
  As this is a new file, no regression should happen.

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

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

[Kernel-packages] [Bug 1772966] [NEW] linux-aws: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1772960

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

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

** Affects: linux-aws (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.05.21-1 kernel-sru-derivative-of-1772960 xenial

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecide

[Kernel-packages] [Bug 1772964] [NEW] linux-kvm: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1772960

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-kvm (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.05.21-1 kernel-sru-derivative-of-1772960 xenial

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1772963] [NEW] linux-aws: -proposed tracker