[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker

2019-02-28 Thread Stefan Bader
** Tags added: kernel-block-proposed

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

Title:
  linux: 4.4.0-143.169 -proposed tracker

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

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

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

  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:24 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-02-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-02-28 Thread Andrii Motsok
Also have the issue since yesterday:

modprobe: ERROR: could not insert 'wl': Package not installed

sudo lshw -C network
  *-network UNCLAIMED 
   description: Network controller
   product: BCM43142 802.11b/g/n
   vendor: Broadcom Inc. and subsidiaries
   physical id: 0
   bus info: pci@:06:00.0
   version: 01
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress cap_list
   configuration: latency=0
   resources: memory:f720-f7207fff
  *-network
   description: Ethernet interface
   product: RTL810xE PCI Express Fast Ethernet controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:07:00.0
   logical name: eth0
   version: 07
   serial: 74:e6:e2:3b:6a:b5
   size: 100Mbit/s
   capacity: 100Mbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8106e-1_0.0.1 06/29/12 
ip=10.0.0.87 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
   resources: irq:63 ioport:e000(size=256) memory:f710-f7100fff 
memory:f210-f2103fff

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

-- 
Mailing list: https://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 1811755] Re: X1 Extreme: only one of the two SSDs is loaded

2019-02-28 Thread Tim Penhey
Yes I intend to test the mainline kernel when I'm back home from the
sprint

On 20/02/19 2:59 AM, Kai-Heng Feng wrote:
> Hi Tim,
>
> Would it be possible for you to test mainline kernel [1]? It probably
> requires more commits to be backported. But first let's make sure it's
> fully fixed in mainline kernel.
>
> [1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc7/
>

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

Title:
  X1 Extreme: only one of the two SSDs is loaded

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

Bug description:
  [Impact]
  On Thinkpad X1 Extreme with two SSDs, if NQN in the firmware are 
  identical, then only one drive can be seen. NQN is supposed to be unique
  but some Intel drives do not follow that.

  [Fix]
  The device-supplied subnqn is ignored and one will be generated as if
  the field is empty.

  The upstream patch conflicts with a value in 'enum nvme_quirks' that we
  added in a SAUCE patch, changed that from (1<<8) to (1<<15).

  [Test]
  With this fix, both drives can be seen.

  [Regression Potential]
  The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been
  verified by the bug reporter.

  -

  I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
  256G and the other 512G with the intention of keeping the windows on
  the 256G disk and using the 512G for linux.

  When dealing with the installer, it only ever saw one of the SSDs. I
  did manged to get bionic installed on the 512, but on boot, sometimes
  it doesn't find the 512G disk and I just get a blank screen.  After a
  hard power-off, and reboot, it drops into the grub selector, and
  choosing linux, it failed again, but this time dropped into a VT.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2003 F pulseaudio
   /dev/snd/controlC0:  tim2003 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 18:53:34 2019
  InstallationDate: Installed on 2019-01-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109)
  MachineType: LENOVO 20MFCTO1WW
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1816493] Re: Ralink RT3290 Is Not in Kernel

2019-02-28 Thread Sherif
I commented blacklist... then added it to /etc/modules. Now, it's always on.
In first attempt, I failed to receive files from mobile. Now, I can.

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

Title:
  Ralink RT3290 Is Not in Kernel

Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  Expired

Bug description:
  Bluetooth in HP laptop doesn't work, because the driver isn't in the kernel 
or packaged.
  There are some guides in the internet, but they aren't integrated in kernel 
and aren't guaranteed to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 19 01:33:46 2019
  InstallationDate: Installed on 2019-02-07 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InterestingModules: bluetooth
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  syslog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sherif 5874 F pulseaudio
  CRDA:
   global
   country EG: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (N/A, 20), (N/A)
(5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-07 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  cosmic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1813957] Re: T480: closed lid and touchpad

2019-02-28 Thread AaronMa
Could you try these steps:

1, remove i2c_i801 from /etc/modprobe.d/blacklist.conf
2, update-initramfs -u -k all
3, Then boot with "psmouse.synaptics_intertouch=1" in cmdline.

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

Title:
  T480: closed lid and touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After closing the lid and working with externals screens and mouse and
  keyboard, the mouse cursor jumps. The effect is caused by touchpad:
  the workaround is to completely disable it in settings.

  
  This bug is 4.15.0-44 kernel specific. With the previous version 4.15.0-43 
the problem was not observed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  afiergol   9976 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   9976 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   9976 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 30 17:29:35 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (300 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (161 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  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:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-28 Thread bugproxy
--- Comment From cls...@us.ibm.com 2019-03-01 00:25 EDT---
I did verified this bugzilla but I reverified with this level. 
(4.18.0-16-generic)
uname -r
4.18.0-16-generic
# netstat -in
Kernel Interface table
Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
enP2p1s0  1500 9161  0  9 0   379  0  0  0 BMRU
enp1s0f0  1500  5459302  0  0 0   5455281  0  0  0 BMRU
lo   65536   12  0  0 012  0  0  0 LRU
virbr015000  0  0 0 0  0  0  0 BMU
# ethtool -S enp1s0f0 | grep rx_wqe
rx_wqe_err: 0

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

Title:
  Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)

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

Bug description:
  
  == SRU Justification ==
  The requested commit fixes a regression introduce by mainline commit
  3a2f70331226, in v4.18-rc1.  The commit is only needed in Cosmic.  Do to
  the regression, A Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)

  == Fix ==
  37fdffb217a4 ("net/mlx5: WQ, fixes for fragmented WQ buffers API")

  == Regression Potential ==
  Low. This commit has been cc'd to stable, so it has had additional
  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.


  
  == Comment: #0 - Michael Ranweiler  - 2018-10-18 11:34:40 ==

  ---Problem Description---
  At the system if u do
  ethtool -S enP48p1s0f0 | grep wqe_err
   rx_wqe_err: 1
   rx0_wqe_err: 0
   rx1_wqe_err: 0
   rx2_wqe_err: 0
   rx3_wqe_err: 1
   rx4_wqe_err: 0
   rx5_wqe_err: 0
   rx6_wqe_err: 0
   rx7_wqe_err: 0
   rx8_wqe_err: 0
   rx9_wqe_err: 0
   rx10_wqe_err: 0
   rx11_wqe_err: 0
   rx12_wqe_err: 0
   rx13_wqe_err: 0
   rx14_wqe_err: 0
   rx15_wqe_err: 0

  Will see that rx side is hitting issue.

  ---Additional Hardware Info---
  Mellanox CX5 Ethernet 100G
  lspci
  0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]

  Machine Type = P9

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
  Using a CX5 Ethernet 100G card
  lspci
  0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]

  just configure IP
  ifconfig enP48p1s0f0 33.33.33.33 netmask 255.255.255.0 up
  then partner system configure IP and then try ping -f
  ping -f 33.33.33.33
  PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data.
  ^C
  --- 33.33.33.33 ping statistics ---
  5413 packets transmitted, 5373 received, 0% packet loss, time 934ms
  rtt min/avg/max/mdev = 0.015/0.019/0.669/0.010 ms, ipg/ewma 0.172/0.020 ms
  # ping 33.33.33.33
  PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data.
  ^C
  --- 33.33.33.33 ping statistics ---
  2 packets transmitted, 0 received, 100% packet loss, time 1071ms

  then at the recv system then do
  ethtool -S enP48p1s0f0 | grep wqe_err
   rx_wqe_err: 1
   rx0_wqe_err: 0
   rx1_wqe_err: 0
   rx2_wqe_err: 0
   rx3_wqe_err: 1
   rx4_wqe_err: 0
   rx5_wqe_err: 0
   rx6_wqe_err: 0
   rx7_wqe_err: 0
   rx8_wqe_err: 0
   rx9_wqe_err: 0
   rx10_wqe_err: 0
   rx11_wqe_err: 0
   rx12_wqe_err: 0
   rx13_wqe_err: 0
   rx14_wqe_err: 0
   rx15_wqe_err: 0
  you will see rx_wqe_err with a counter non-zero.

  This is fixed by this patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=37fdffb217a45609edccbb8b407d031143f551c0

  == Comment: #1 - Carol L. Soto  - 2018-10-18 11:46:00 ==
  I did a git clone to the cosmic tree and loaded the kernel in a system.

  kernel 4.18.12 and I can recreate it.

  lspci | grep Mell | grep ConnectX-5
  :01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  :01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  0030:01:00.0 Infiniband controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  0030:01:00.1 Infiniband controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  :~# ethtool -S enp1s0f0 | grep wqe_err
   rx_wqe_err: 2
   rx0_wqe_err: 1
   rx1_wqe_err: 1
   rx2_wqe_err: 0
   rx3_wqe_err: 0
   rx4_wqe_err: 0
   rx5_wqe_err: 0
   rx6_wqe_err: 0
   rx7_wqe_err: 0
   rx8_wqe_err: 0
   rx9_wqe_err: 0
   

[Kernel-packages] [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded

2019-02-28 Thread Terry Rudd
Final reminder to please test the kernel above to ensure it fixes the
problem for which this bug was filed.  Thanks in advance!

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

Title:
  X1 Extreme: only one of the two SSDs is loaded

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

Bug description:
  [Impact]
  On Thinkpad X1 Extreme with two SSDs, if NQN in the firmware are 
  identical, then only one drive can be seen. NQN is supposed to be unique
  but some Intel drives do not follow that.

  [Fix]
  The device-supplied subnqn is ignored and one will be generated as if
  the field is empty.

  The upstream patch conflicts with a value in 'enum nvme_quirks' that we
  added in a SAUCE patch, changed that from (1<<8) to (1<<15).

  [Test]
  With this fix, both drives can be seen.

  [Regression Potential]
  The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been
  verified by the bug reporter.

  -

  I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
  256G and the other 512G with the intention of keeping the windows on
  the 256G disk and using the 512G for linux.

  When dealing with the installer, it only ever saw one of the SSDs. I
  did manged to get bionic installed on the 512, but on boot, sometimes
  it doesn't find the 512G disk and I just get a blank screen.  After a
  hard power-off, and reboot, it drops into the grub selector, and
  choosing linux, it failed again, but this time dropped into a VT.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2003 F pulseaudio
   /dev/snd/controlC0:  tim2003 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 18:53:34 2019
  InstallationDate: Installed on 2019-01-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109)
  MachineType: LENOVO 20MFCTO1WW
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818126] Re: linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker

2019-02-28 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:36 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1795453] Re: [SRU] IO's are issued with incorrect Scatter Gather Buffer

2019-02-28 Thread Terry Rudd
This is the final reminder to please verify that the kernel in -proposed
resolves the issue for which you've filed this bug report.   Canonical
is planning to release these kernels early next week.   Thank you in
advance!

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

Title:
  [SRU] IO's are issued with incorrect Scatter Gather Buffer

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

Bug description:
  [Impact]
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  Here is the data we captured in our driver (Printed the SGE details
  which was sent by OS)

  sgl_ptr->Address = f000
  [14547.313240]
  sgl_ptr->Length = 1000
  [14547.313241]
  sge_count = 18
  [14547.313242]
  cmd->index = 9d9

  Note : This issue is observed only when virtualization is enabled

  Product : Broadcom (LSI) Megaraid H840 controller

  
  [Test Case]
  Steps found in comment #60
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60

  
  [Regression Potential]

  The patches in Comment #59 have been accepted upstream.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59


  [Other Info]

  Product : Broadcom (LSI) Megaraid H840 controller
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

2019-02-28 Thread Terry Rudd
This is the final reminder to please verify that the kernel in -proposed
resolves the issue for which you've filed this bug report.   Canonical
is planning to release these kernels early next week.   Thank you in
advance!

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

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

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

[Kernel-packages] [Bug 1811777] Re: Fix non-working pinctrl-intel

2019-02-28 Thread Terry Rudd
This is the final reminder to please verify that the kernel in -proposed
resolves the issue for which you've filed this bug report.   Canonical
is planning to release these kernels early next week.   Thank you in
advance!

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

Title:
  Fix non-working pinctrl-intel

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Intel pinctrl doesn't work.
  There's a WWAN card needs to use pinctrl to reset itself after firmware 
update. Currently we can't use pinctrl to reset it.

  [Fix]
  Translate GPIO to pinctrl pins correctly.

  [Test]
  The WWAN reset function works once the fix is applied.

  [Regression Potential]
  Low. Limits to pinctrl-intel and it's in mainline for a while.

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

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


[Kernel-packages] [Bug 1812198] Re: user_copy in user from ubuntu_kernel_selftests failed on KVM kernel

2019-02-28 Thread Terry Rudd
This is the final reminder to please verify that the kernel in -proposed
resolves the issue for which you've filed this bug report.   Canonical
is planning to release these kernels early next week.   Thank you in
advance!

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

Title:
  user_copy in user from ubuntu_kernel_selftests failed on KVM kernel

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Xenial:
  Fix Released
Status in linux-kvm source package in Bionic:
  Fix Committed
Status in linux-kvm source package in Cosmic:
  Fix Released

Bug description:
  == Justification ==
  This user_copy test has failed while attempting to insert the test_user_copy 
module, but this module does not exist in the Bionic KVM kernel as the 
CONFIG_TEST_USER_COPY was not enabled.

  # modprobe test_user_copy
  modprobe: FATAL: Module test_user_copy not found in directory 
/lib/modules/4.15.0-1028-kvm

  == Fix ==
  d7d5311 (selftests: user: return Kselftest Skip code for skipped tests)
  3c07aae (selftests: kselftest: change KSFT_SKIP=4 instead of KSFT_PASS)
  c31d02d (selftests: kselftest: Remove outdated comment)

  This fix will make the test return a skipped retun code if the
  test_user_copy module does not exist.

  This patch set can be cherry-picked into Bionic, and we already have
  it in Cosmic / Disco.

  For Xenial, it already got d7d5311 and does not need the other two.

  == Test ==
  With this patch, the test will return "skipped" as expected:
  $ sudo ./test_user_copy.sh
  user: module test_user_copy is not found [SKIP]
  $ echo $?
  4

  Note that the test framework will need another fix to treat the SKIP
  return code properly. (bug 1812352)

  == Regression potential ==
  None,
  this patch just change the code for the testing tool.

  --

  This test_user_copy module will need the CONFIG_TEST_USER_COPY to be enabled
  https://cateee.net/lkddb/web-lkddb/TEST_USER_COPY.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 10:57:57 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1785816] Re: Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING

2019-02-28 Thread Terry Rudd
Mark, if you want to kick the tires on this capability before it goes
out, we're planning to release early next week, just FYI.

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

Title:
  Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING

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

Bug description:
  SRU Justification

  Impact: CONFIG_NETWORK_PHY_TIMESTAMPING is disabled, preventing PTP
  time synchronization using the DP83640 PHYTER.

  Fix: Enable this option and set CONFIG_DP83640_PHY=m to enable the
  DP83640 PHYTER driver.

  Regression Potential: The kconfig help text warns of adding overhead
  to network tx and rx, but our analysis finds this to be negligible
  (see comment #6). Beyond this we are enabling a new driver which does
  little unless timestamping is explicitly activated, so regressions are
  not expected.

  ---

  Hi folks, is there a reason we do not enable
  CONFIG_NETWORK_PHY_TIMESTAMPING ? I'm not sure of the tradeoffs but I
  think this config option is required for PTP time syncronization which
  would be useful in telco and financial (and OCD :)) environments.

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

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


[Kernel-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

2019-02-28 Thread Anthony Wong
** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Cosmic)

** Description changed:

  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs
  on boot.
  
  After blacklisting i2c_i801 everything works great again.
  
  I realize that this was a fix for bug 1786574, and that helps some other
  folks out.  I'm not sure what the right fix is but there's got to be
  something that works for everyone.
+ 
+ ==
+ 
+ The fix for the root cause of the hang is tracked in bug 1804604.

** Description changed:

  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs
  on boot.
  
  After blacklisting i2c_i801 everything works great again.
  
  I realize that this was a fix for bug 1786574, and that helps some other
  folks out.  I'm not sure what the right fix is but there's got to be
  something that works for everyone.
  
  ==
  
- The fix for the root cause of the hang is tracked in bug 1804604.
+ The fix for the root cause of this hang issue is tracked in bug 1804604.

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in kmod source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

  ==

  The fix for the root cause of this hang issue is tracked in bug
  1804604.

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

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


[Kernel-packages] [Bug 1810128] Re: Network is disconnected

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

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

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

Title:
  Network is disconnected

Status in linux package in Ubuntu:
  Expired

Bug description:
  
  Ubuntu 4.15.0-43.46-generic 4.15.18

  Network is not working after computer wakes up from sleep mode.

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

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


[Kernel-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

2019-02-28 Thread Adam Jacobs
Yes, confirmed.  On my Lenovo x240, kernel 4.18.0-15-generic, I removed
i2c_i801 from the blacklist and no longer can reproduce the hang.

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

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

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

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

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


[Kernel-packages] [Bug 1730782] Re: [Bug] [KNL] ~5x slowdown of application when attaching by perf on KNL

2019-02-28 Thread quanxian
has been fixed in 4.17

** Changed in: intel
   Status: New => 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/1730782

Title:
  [Bug] [KNL] ~5x slowdown of application when attaching by perf on KNL

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  Description:

  Workload slows down for default sampling cycles in KNL. There are some 
processing in perf that's single threaded and bottlenecked when number of cores 
really go up.
  A second issue is that things slow down when we issue
  perf record – workload
  vs
  perf record -a – workload

  Patch is submitted for review

  https://www.spinics.net/lists/kernel/msg2552460.html
  https://www.spinics.net/lists/kernel/msg2552461.html
  https://www.spinics.net/lists/kernel/msg2552462.html
  https://www.spinics.net/lists/kernel/msg2552463.html

  Target kernel: 5.2
  Target Release: 19.04

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

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


[Kernel-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

2019-02-28 Thread Anthony Wong
I have confirmed with Adam Jacobs on email that he runs latest 18.10
kernel, and his system no longer hangs after i2c_i801 is removed from
blacklist.

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

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

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

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

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


[Kernel-packages] [Bug 1818152] Re: Nvidia 340

2019-02-28 Thread Anthony Wong
** Also affects: nvidia-graphics-drivers-340 (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/1818152

Title:
  Nvidia 340

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  After installing NVIDIA driver, the screen brightness is freezed by
  100%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   senne  2237 F...m pulseaudio
   /dev/snd/controlC0:  senne  2237 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Feb 28 23:00:25 2019
  InstallationDate: Installed on 2018-12-24 (66 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Apple Inc. MacBook5,1
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8980397b-61c8-4011-a75c-9777552c623c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1817971] Re: Ubuntu freezes and do not respond to mouseclicks or keyboard.

2019-02-28 Thread Anthony Wong
Do you hard reset when you have this problem? Can you attach
/var/log/kern.log to the bug?

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

Title:
  Ubuntu freezes and do not respond to mouseclicks or keyboard.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The mouse moves on the screen but it is not possible to click on
  anything and ctrl+alt+F1 doesn't do anything. I think it happens more
  often when VS code is open.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joakim 1857 F pulseaudio
   /dev/snd/controlC1:  joakim 1857 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:42:12 2019
  InstallationDate: Installed on 2019-02-07 (20 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=7da0b25e-0d4f-48bf-8785-730733ff3aee ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4024
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X470-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX470-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1818025] Re: ethernet card not detected

2019-02-28 Thread Anthony Wong
Lucian, you need the 'apport' package, I believe it is in the default
installation but if you don't have it, just install it, and then run
'apport-collect 1818025'.

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

Title:
  ethernet card not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  06:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
  07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI 
Express Fast/Gigabit Ethernet controller (rev 07) Device: eth0 
-
Type:  Wired
Driver:r8169
State: unavailable
Default:   no
HW Address:28:F1:0E:27:81:D1

Capabilities:
  Carrier Detect:  yes
  Speed:   100 Mb/s

Wired Properties
  Carrier: off

  It does not see the ethernet controller card. I cannot use Wi-Fi anymore. 
Need it asap.
  Please help.
  Thank you in advance.

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

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


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

2019-02-28 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  [Dell DW1560 / BCM20702A1] kobject_add_internal failed for hci0:11
  with --EEXIST, don't try to register things with the same name in the
  same directory

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to
  register things with the same name in the same directory

  This issue is about kernel - it shouldn't rely on state of unrealiable
  propertary drivers. Sometimes rmmod all bluetooth modules helps,
  sometimes restart is just faster.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 28 21:13:21 2019
  InstallationDate: Installed on 2015-05-08 (1392 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash 
log_buf_len=1M crashkernel=384M-:128M
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (185 days ago)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09K8G1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd09/27/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 34:68:95:ED:83:EA  ACL MTU: 1021:8  SCO MTU: 64:1
    UP RUNNING PSCAN
    RX bytes:1283292 acl:65502 sco:1441 events:1266 errors:0
    TX bytes:360374 acl:522 sco:1436 commands:565 errors:0

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

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


[Kernel-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

2019-02-28 Thread Anthony Wong
I have confirmed with both Chad billman (cabillman) and Earle Lyons
(earlev4) through email that when running 4.15.0-45 and i2c_i801 removed
from blacklist, their touchpads still work.

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

Title:
  broken touchpad after i2c-i801 blacklist change

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

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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


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

2019-02-28 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 1818170

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

Title:
  linux 4.4.0-143.169 ADT test failure with linux 4.4.0-143.169

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20190228_103241_6fdc6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190226_190740_8dbe6@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20190226_183159_8dbe6@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20190226_174407_8dbe6@/log.gz

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

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


[Kernel-packages] [Bug 1818101] Re: nvidia dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’]

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

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


** Summary changed:

- nvidia dkms modules fail to build with linux 4.4.0-143.169
+ nvidia dkms modules fail to build with linux 4.4.0-143.169 [error: too many 
arguments to function ‘get_user_pages’]

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

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

Title:
  nvidia dkms modules fail to build with linux 4.4.0-143.169 [error: too
  many arguments to function ‘get_user_pages’]

Status in Nvidia:
  New
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-304 source package in Trusty:
  New
Status in nvidia-graphics-drivers-340 source package in Trusty:
  New
Status in nvidia-graphics-drivers-384 source package in Trusty:
  New
Status in nvidia-graphics-drivers-304 source package in Xenial:
  New
Status in nvidia-graphics-drivers-340 source package in Xenial:
  New
Status in nvidia-graphics-drivers-384 source package in Xenial:
  New

Bug description:
  [Impact]
  nvidia dkms modules (304, 340, 384) fail to build after Ubuntu kernel 4.4 
backported the following fix from upstream stable, which is included on xenial 
kernel 4.4.0-143.169 that's currently in -proposed.

  mm: replace get_user_pages() write/force parameters with gup_flags
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?h=master-next=9c72ad08f1510332e9314046e6a2adba5064f39a

  Excerpt from ./nvidia-304/304.135/build/make.log:
  
  /var/lib/dkms/nvidia-304/304.135/build/nv-linux.h:1941:9: error: too many 
arguments to function ‘get_user_pages’
   get_user_pages(current, current->mm, start, nr_pages, write, force, 
pages, vmas)
   ^
  /var/lib/dkms/nvidia-304/304.135/build/nv-mlock.c:52:11: note: in expansion 
of macro ‘NV_GET_USER_PAGES’
   ret = NV_GET_USER_PAGES((unsigned long)address,
 ^
  In file included from /var/lib/dkms/nvidia-304/304.135/build/nv-linux.h:82:0,
   from /var/lib/dkms/nvidia-304/304.135/build/nv-mlock.c:15:
  include/linux/mm.h:1222:6: note: declared here
   long get_user_pages(struct task_struct *tsk, struct mm_struct *mm,
^
  

  [Test case]
  Install nvidia dkms packages (nvidia-graphics-drivers-304, 
nvidia-graphics-drivers-340, nvidia-graphics-drivers-384) with Ubuntu linux 4.4 
later or equal than 4.4.0-143.

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

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


[Kernel-packages] [Bug 1818140] Re: Kernel module race condition during bluetooth discovery

2019-02-28 Thread Daniel van Vugt
Sorry, I see now. It was just a typo in the bug description:

  kobject_add_internal_failed

should be

  kobject_add_internal failed

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

** Summary changed:

- Kernel module race condition during bluetooth discovery
+ kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to register 
things with the same name in the same directory

** Summary changed:

- kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to register 
things with the same name in the same directory
+ kobject_add_internal failed for hci0:11 with --EEXIST, don't try to register 
things with the same name in the same directory

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

** Summary changed:

- kobject_add_internal failed for hci0:11 with --EEXIST, don't try to register 
things with the same name in the same directory
+ [Dell DW1560 / BCM20702A1] kobject_add_internal failed for hci0:11 with 
--EEXIST, don't try to register things with the same name in the same directory

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

Title:
  [Dell DW1560 / BCM20702A1] kobject_add_internal failed for hci0:11
  with --EEXIST, don't try to register things with the same name in the
  same directory

Status in linux package in Ubuntu:
  New

Bug description:
  kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to
  register things with the same name in the same directory

  This issue is about kernel - it shouldn't rely on state of unrealiable
  propertary drivers. Sometimes rmmod all bluetooth modules helps,
  sometimes restart is just faster.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 28 21:13:21 2019
  InstallationDate: Installed on 2015-05-08 (1392 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash 
log_buf_len=1M crashkernel=384M-:128M
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (185 days ago)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09K8G1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd09/27/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 34:68:95:ED:83:EA  ACL MTU: 1021:8  SCO MTU: 64:1
    UP RUNNING PSCAN
    RX bytes:1283292 acl:65502 sco:1441 events:1266 errors:0
    TX bytes:360374 acl:522 sco:1436 commands:565 errors:0

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

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


[Kernel-packages] [Bug 1818170] Re: linux 4.4.0-143.169 ADT test failure with linux 4.4.0-143.169

2019-02-28 Thread Khaled El Mously
Upstream stable 4.4.169 changed the permissions on /proc/timer_list so
the test needs to be updated.

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

Title:
  linux 4.4.0-143.169 ADT test failure with linux 4.4.0-143.169

Status in linux package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20190228_103241_6fdc6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190226_190740_8dbe6@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20190226_183159_8dbe6@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20190226_174407_8dbe6@/log.gz

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

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


[Kernel-packages] [Bug 1818170] [NEW] linux 4.4.0-143.169 ADT test failure with linux 4.4.0-143.169

2019-02-28 Thread Khaled El Mously
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20190228_103241_6fdc6@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190226_190740_8dbe6@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20190226_183159_8dbe6@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20190226_174407_8dbe6@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  linux 4.4.0-143.169 ADT test failure with linux 4.4.0-143.169

Status in linux package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20190228_103241_6fdc6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190226_190740_8dbe6@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20190226_183159_8dbe6@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20190226_174407_8dbe6@/log.gz

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

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


[Kernel-packages] [Bug 1818140] Re: Kernel module race condition during bluetooth discovery

2019-02-28 Thread Daniel van Vugt
> Bluetooth: hci0: last event is not cmd complete (0x0f)
> 
> are causing:
> 
> kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to register 
> things with the same > name in the same directory

Those are two separate issues. The first one is bug 1748565. So let's
make this bug about the second issue. I can't see the
kobject_add_internal_failed error in your kernel log, so where do you
see it?



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

** Description changed:

- Bugs probably in firmware:
- 
- Bluetooth: hci0: last event is not cmd complete (0x0f)
- 
- are causing:
- 
  kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to
  register things with the same name in the same directory
  
- 
- This issue is about kernel - it shouldn't rely on state of unrealiable 
propertary drivers. Sometimes rmmod all bluetooth modules helps, sometimes 
restart is just faster.
+ This issue is about kernel - it shouldn't rely on state of unrealiable
+ propertary drivers. Sometimes rmmod all bluetooth modules helps,
+ sometimes restart is just faster.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 28 21:13:21 2019
  InstallationDate: Installed on 2015-05-08 (1392 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=pl_PL.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pl_PL.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash 
log_buf_len=1M crashkernel=384M-:128M
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (185 days ago)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09K8G1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd09/27/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  hciconfig:
-  hci0:Type: Primary  Bus: USB
-   BD Address: 34:68:95:ED:83:EA  ACL MTU: 1021:8  SCO MTU: 64:1
-   UP RUNNING PSCAN 
-   RX bytes:1283292 acl:65502 sco:1441 events:1266 errors:0
-   TX bytes:360374 acl:522 sco:1436 commands:565 errors:0
+  hci0:Type: Primary  Bus: USB
+   BD Address: 34:68:95:ED:83:EA  ACL MTU: 1021:8  SCO MTU: 64:1
+   UP RUNNING PSCAN
+   RX bytes:1283292 acl:65502 sco:1441 events:1266 errors:0
+   TX bytes:360374 acl:522 sco:1436 commands:565 errors:0

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

Title:
  Kernel module race condition during bluetooth discovery

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to
  register things with the same name in the same directory

  This issue is about kernel - it shouldn't rely on state of unrealiable
  propertary drivers. Sometimes rmmod all bluetooth modules helps,
  sometimes restart is just faster.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 28 21:13:21 2019
  InstallationDate: Installed on 2015-05-08 (1392 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash 
log_buf_len=1M crashkernel=384M-:128M
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (185 days ago)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09K8G1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd09/27/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 

[Kernel-packages] [Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0

2019-02-28 Thread Quiksmage
Was this one forgotten, haha? If I can help in any way, please let me know.
Thanks!

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

Title:
  Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  
  == SRU Justification ==
  Mainline commit introduced a regression in v4.15-rc1.  The regression
  causes a kernel panic during system shutdown.  This commit fixes
  that regression.  This commit was also cc'd to upstream stable, but it
  has not landed in Bionic as of yet.

  == Fix ==
  0d98ba8d70b0 ("scsi: hpsa: disable device during shutdown")

  == Regression Potential ==
  Low.  This patch fixes a current regression.  It has been 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.


  Verified on multiple DL360 Gen9 servers with up to date firmware.
  Just before reboot or shutdown, there is the following panic:

  [  289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware 
Error Source: 1
  [  289.093085] {1}[Hardware Error]: event severity: fatal
  [  289.093087] {1}[Hardware Error]:  Error 0, type: fatal
  [  289.093088] {1}[Hardware Error]:   section_type: PCIe error
  [  289.093090] {1}[Hardware Error]:   port_type: 4, root port
  [  289.093091] {1}[Hardware Error]:   version: 1.16
  [  289.093093] {1}[Hardware Error]:   command: 0x6010, status: 0x0143
  [  289.093094] {1}[Hardware Error]:   device_id: :00:01.0
  [  289.093095] {1}[Hardware Error]:   slot: 0
  [  289.093096] {1}[Hardware Error]:   secondary_bus: 0x03
  [  289.093097] {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x2f02
  [  289.093098] {1}[Hardware Error]:   class_code: 040600
  [  289.093378] {1}[Hardware Error]:   bridge: secondary_status: 0x2000, 
control: 0x0003
  [  289.093380] {1}[Hardware Error]:  Error 1, type: fatal
  [  289.093381] {1}[Hardware Error]:   section_type: PCIe error
  [  289.093382] {1}[Hardware Error]:   port_type: 4, root port
  [  289.093383] {1}[Hardware Error]:   version: 1.16
  [  289.093384] {1}[Hardware Error]:   command: 0x6010, status: 0x0143
  [  289.093386] {1}[Hardware Error]:   device_id: :00:01.0
  [  289.093386] {1}[Hardware Error]:   slot: 0
  [  289.093387] {1}[Hardware Error]:   secondary_bus: 0x03
  [  289.093388] {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x2f02
  [  289.093674] {1}[Hardware Error]:   class_code: 040600
  [  289.093676] {1}[Hardware Error]:   bridge: secondary_status: 0x2000, 
control: 0x0003
  [  289.093678] Kernel panic - not syncing: Fatal hardware error!
  [  289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [  289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.

  It does eventually restart after this.  Then during the subsequent
  POST, the following warning appears:

  Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
  Drive(s) - Operation Failed
   - 1719-Slot 0 Drive Array - A controller failure event occurred prior
     to this power-up.  (Previous lock up code = 0x13) Action: Install the
     latest controller firmware. If the problem persists, replace the
     controller.

  The latter's symptoms are described in
  https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
  but the running storage controller firmware is much newer than the
  doc's resolution.

  Neither of these problems occur during shutdown/reboot on the xenial
  kernel.

  FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56
  (01/22/2018)), the shutdown failure mode was a loop like so:

  [529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
  [529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
  [529153.222884] Do you have a strange power saving mode enabled?
  [529153.222884] Dazed and confused, but trying to continue
  [529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
  [529153.554448] Do you have a strange power saving mode enabled?
  [529153.554449] Dazed and confused, but trying to continue
  [529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
  [529153.554451] Do you have a strange power saving mode enabled?
  [529153.554452] Dazed and confused, but trying to continue
  [529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
  [529153.554453] Do you have a strange power saving mode enabled?
  [529153.554454] Dazed and confused, but trying to continue
  [529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0.
  [529153.554455] Do you have a strange power saving 

[Kernel-packages] [Bug 1818128] Re: linux-azure: 4.18.0-1013.13 -proposed tracker

2019-02-28 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1814749
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 28. February 2019 23:31 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Friday, 01. March 2019 01:26 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1818138] Re: Add CONFIG_NO_HZ_FULL=y to linux-azure kernels

2019-02-28 Thread Marcelo Cerri
** Also affects: linux-azure (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux-azure (Ubuntu Xenial)
   Status: Incomplete => Fix Committed

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

** Changed in: linux-azure (Ubuntu Xenial)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux-azure (Ubuntu Cosmic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  Add CONFIG_NO_HZ_FULL=y to linux-azure kernels

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  This is a request to enable CONFIG_NO_HZ_FULL=y in the linux-azure
  kernels(currently 4.15 and 4.18) in order to increase NVME disks
  performance.

  The current CONFIG_NO_HZ configuration in linux-azure kernels is the
  following (tested on 4.15.0-1037, 4.15.0-1039 and 4.18.0-1011):

  CONFIG_NO_HZ=y
  CONFIG_NO_HZ_COMMON=y
  # CONFIG_NO_HZ_FULL is not set
  CONFIG_NO_HZ_IDLE=y

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

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


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

2019-02-28 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  package linux-image-extra-3.13.0-158-generic 3.13.0-158.208 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  running on a flash drive, a bit beyond support for Xubuntu 14.04. I
  may have altered the boot directory to save space. I will look. thank
  you.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-158-generic 3.13.0-158.208
  ProcVersionSignature: Ubuntu 3.13.0-158.208-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-158-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ted1601 F pulseaudio
  Date: Thu Feb 28 17:28:08 2019
  DpkgHistoryLog:
   
  DpkgTerminalLog:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=b19220b6-a5a1-401c-ba85-ba1258cebf42
  InstallationDate: Installed on 2014-04-19 (1776 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-158-generic 
root=/dev/mapper/hostname-root ro acpi.power_nocheck=0 elevator=noop quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.16
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-158-generic 3.13.0-158.208 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 03XK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 530U3BI/530U4BI/530U4BH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr03XK:bd01/04/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3BI/530U4BI/530U4BH
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1764956] Re: Guests using IBRS incur a large performance penalty

2019-02-28 Thread Terry Rudd
Final reminder: We are at the end of the SRU Cycle and request that you
please provide verification the kernel in proposed resolves the problem
for which this bug was submitted.  -Thank you!

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

Title:
  Guests using IBRS incur a large performance penalty

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  the IBRS would be mistakenly enabled in the host when the switching
  from an IBRS-enabled VM and that causes the performance overhead in
  the host. The other condition could also mistakenly disables the IBRS
  in VM when context-switching from the host. And this could be
  considered a CVE host.

  [Fix]
  The patch fixes the logic inside the x86_virt_spec_ctrl that it checks
  the ibrs_enabled and _or_ the hostval with the SPEC_CTRL_IBRS as the
  x86_spec_ctrl_base by default is zero. Because the upstream
  implementation is not equal to the Xenial's implementation. Upstream
  doesn't use the IBRS as the formal fix. So, by default, it's zero.

  On the other hand, after the VM exit, the SPEC_CTRL register also
  needs to be saved manually by reading the SPEC_CTRL MSR as the MSR
  intercept is disabled by default in the hardware_setup(v4.4) and
  vmx_init(v3.13). The access to SPEC_CTRL MSR in VM is direct and
  doesn't trigger a trap. So, the vmx_set_msr() function isn't called.

  The v3.13 kernel hasn't been tested. However, the patch can be viewed
  at:
  
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=sf00191076-sru

  The v4.4 patch:
  
http://kernel.ubuntu.com/git/gavinguo/ubuntu-xenial.git/log/?h=sf00191076-spectre-v2-regres-backport-juerg

  [Test]

  The patch has been tested on the 4.4.0-140.166 and works fine.

  The reproducing environment:
  Guest kernel version: 4.4.0-138.164
  Host kernel version: 4.4.0-140.166

  (host IBRS, guest IBRS)

  - 1). (0, 1).
  The case can be reproduced by the following instructions:
  guest$ echo 1 | sudo tee /proc/sys/kernel/ibrs_enabled
  1

  

  host$ cat /proc/sys/kernel/ibrs_enabled
  0
  host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
  110001001010

  Some of the IBRS bit inside the SPEC_CTRL MSR are mistakenly
  enabled.

  host$ taskset -c 5 stress-ng -c 1 --cpu-ops 2500
  stress-ng: info:  [11264] defaulting to a 86400 second run per stressor
  stress-ng: info:  [11264] dispatching hogs: 1 cpu
  stress-ng: info:  [11264] cache allocate: default cache size: 35840K
  stress-ng: info:  [11264] successful run completed in 33.48s

  The host kernel didn't notice the IBRS bit is enabled. So, the situation
  is the same as "echo 2 > /proc/sys/kernel/ibrs_enabled" in the host.
  And running the stress-ng is a pure userspace CPU capability
  calculation. So, the performance downgrades to about 1/3. Without the
  IBRS enabled, it needs about 10s.

  - 2). (1, 1) disables IBRS in host -> (0, 1) actually it becomes (0, 0).
  The guest IBRS has been mistakenly disabled.

  guest$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
  guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
  

  host$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
  host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
  
  host$ echo 0 | sudo tee /proc/sys/kernel/ibrs_enabled
  host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
  

  guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
  

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

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


[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT

2019-02-28 Thread Khaled El Mously
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  installer does not support iSCSI iBFT

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

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
 (settings for network interface, initiator, and target) in the installer
 because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
 thus any settings are ignored, and iSCSI-related configuration has to
 be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
 deployments which actually do provide the iBFT feature and information,
 but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
 and automatic iSCSI-related configuration) users will be able to rely on
 iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
 and configure network/iSCSI according to iBFT information in disk-detect.

 This is done in disk-detect so that the iSCSI LUNs are detected as disks
 (useful in case of no other disks in the system so the installer doesn't
 complain nor wait too long) and that any partman-related preseed options
 are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

 $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

 Check the module loads in the installer environment.
 See comment with example for disco.

   * d-i/hw-detect package:
 (to be done)

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
 and only checks whether iBFT information is present in firmware,
 then exposes that in sysfs in read-only mode.

   * d-i/hw-detect:
 (to be done)

  [Other Info]
   
   * This has been verified both by the developer with a simple iSCSI
 iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)
 and by an user with system/firmware that supports iBFT for iSCSI.

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

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


[Kernel-packages] [Bug 1813869] Re: Redpine: Driver crash with network-manager 1.10 and above

2019-02-28 Thread Terry Rudd
Final reminder: We are at the end of the SRU Cycle and request that you
please provide verification the kernel in proposed resolves the problem
for which this bug was submitted.  -Thank you!

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

Title:
  Redpine: Driver crash with network-manager 1.10 and above

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification:
  --

  Impact: 
  ---
Kernel crash upon inserting Redpine driver

  Test case:
  --
1) Install network-manager v(1.10) snap.
2) Insert Redpine modules.
3) Observe the behavior.

  Result:
  ---
 Redpine driver crashes the entire kernel and below is the crash log.
 ... skipping ...
 [ 49.130185] BUG: unable to handle kernel NULL pointer dereference at 
0134
 [ 49.138969] IP: [] rsi_prepare_mgmt_desc+0xd3/0x2d0 
[ven_rsi_91x]
 [ 49.244030] CPU: 0 PID: 31 Comm: kworker/u4:1 Not tainted 
4.4.0-139-generic #165-Ubuntu
 [ 49.252988] Hardware name: Dell Inc. Edge Gateway 3001/, BIOS 
01.00.00 04/17/2017
 [ 49.261374] Workqueue: rsi_scan_worker rsi_scan_start [ven_rsi_91x]
 [ 49.268385] task: 880078538cc0 ti: 8800785e4000 task.ti: 
8800785e4000
 [ 49.276765] rsi_prepare_mgmt_desc+0xd3/0x2d0 [ven_rsi_91x]
 [ 49.387307] [] rsi_send_probe_request+0x2c7/0x350 
[ven_rsi_91x]
 [ 49.395784] [] rsi_scan_start+0x222/0x380 
[ven_rsi_91x]
 [ 49.403486] [] ? __schedule+0x301/0x7f0
 [ 49.409633] [] process_one_work+0x16b/0x490
 [ 49.416164] [] worker_thread+0x4b/0x4d0
 [ 49.422306] [] ? process_one_work+0x490/0x490
 [ 49.429032] [] kthread+0xe7/0x100
 [ 49.434589] [] ? __schedule+0x301/0x7f0
 [ 49.440731] [] ? kthread_create_on_node+0x1e0/0x1e0
 [ 49.448042] [] ret_from_fork+0x55/0x80
 [ 49.454086] [] ? kthread_create_on_node+0x1e0/0x1e0 


  Root cause analysis:
  
 In nm-1.10 and above versions, MAC spoof is enabled by default. In 
Redpine
 driver, this handling is missed. Hence, Added the fix for the same.

  Fix:
  
 Copied the Custom MAC address into driver global structure.

  Regression Petential:
  -
  This is a very direct issue Since the driver is crashing upon 
inserting the
  modules. we ran the multiple times insertion and deletion of modules 
and connected
  to third-party AP, did data transfer.

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

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


[Kernel-packages] [Bug 1813001] Re: test_095_kernel_symbols_missing_proc_self_stack failed on P-LTS

2019-02-28 Thread Terry Rudd
Final reminder: We are at the end of the SRU Cycle and request that you
please provide verification the kernel in proposed resolves the problem
for which this bug was submitted.  -Thank you!

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

Title:
  test_095_kernel_symbols_missing_proc_self_stack failed on P-LTS

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  The testcase test_095_kernel_symbols_missing_proc_self_stack from
  ubuntu_qrt_kernel_security testsuite started to fail with Trusty
  kernel (3.13) after the fix for CVE-2018-17972 ("proc: restrict kernel
  stack dumps to root"), which prevents a regular user to read from
  /proc/self/stack.

  Kernel: 3.13.0-165.215~precise1
  The test failed with:
  AssertionError: cat: /proc/self/stack: Permission denied

  FAIL: test_095_kernel_symbols_missing_proc_self_stack 
(__main__.KernelSecurityTest)
  kernel addresses in /proc/self/stack are zeroed out
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1364, in 
test_095_kernel_symbols_missing_proc_self_stack
  self._check_pK_files(self._095_kernel_symbols_missing_proc_self_stack, 
expected=expected)
  File "./test-kernel-security.py", line 1209, in _check_pK_files
  test_function(expected_restricted)
  File "./test-kernel-security.py", line 1320, in 
_095_kernel_symbols_missing_proc_self_stack
  expected, retry=True)
  File "./test-kernel-security.py", line 1146, in _read_twice
  self.assertEqual(rc, 0, regular)
  AssertionError: cat: /proc/self/stack: Permission denied

  The testcase checks the file permission before trying to read it, and
  for kernel 3.13 the permissions became inconsistent with what the user
  can actually do:

  $ cat /proc/self/stack
  cat: /proc/self/stack: Permission denied
  $ ls -l /proc/self/stack
  -r--r--r-- 1 ubuntu ubuntu 0 Jan 24 04:06 /proc/self/stack

  [Test Case]
  Run 'cat' and 'ls' on the file as stated above, or run the 
ubuntu_qrt_kernel_security testsuite and check for the results of the 
test_095_kernel_symbols_missing_proc_self_stack testcase.

  [Fix]
  Upstream commit 35a35046e4f9 ("procfs: make 
/proc/*/{stack,syscall,personality} 0400") applied for v3.15-rc1 fixes the 
issue.

  [Regression Potential]
  The upstream fix changes the permissions of the files 
/proc/*/{stack,syscall,personality}, so userspace which relies on reading these 
files as regular users might fail. However, this fixes a security issue and is 
already applied on our later series.

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

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


[Kernel-packages] [Bug 1818164] [NEW] package linux-image-extra-3.13.0-158-generic 3.13.0-158.208 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-02-28 Thread Ted Pomeroy
Public bug reported:

running on a flash drive, a bit beyond support for Xubuntu 14.04. I may
have altered the boot directory to save space. I will look. thank you.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-158-generic 3.13.0-158.208
ProcVersionSignature: Ubuntu 3.13.0-158.208-generic 3.13.11-ckt39
Uname: Linux 3.13.0-158-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ted1601 F pulseaudio
Date: Thu Feb 28 17:28:08 2019
DpkgHistoryLog:
 
DpkgTerminalLog:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
HibernationDevice: RESUME=UUID=b19220b6-a5a1-401c-ba85-ba1258cebf42
InstallationDate: Installed on 2014-04-19 (1776 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-158-generic 
root=/dev/mapper/hostname-root ro acpi.power_nocheck=0 elevator=noop quiet 
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.16
SourcePackage: linux
Title: package linux-image-extra-3.13.0-158-generic 3.13.0-158.208 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/04/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 03XK
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 530U3BI/530U4BI/530U4BH
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr03XK:bd01/04/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3BI/530U4BI/530U4BH
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: apport-package i386 trusty

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

Title:
  package linux-image-extra-3.13.0-158-generic 3.13.0-158.208 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  running on a flash drive, a bit beyond support for Xubuntu 14.04. I
  may have altered the boot directory to save space. I will look. thank
  you.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-158-generic 3.13.0-158.208
  ProcVersionSignature: Ubuntu 3.13.0-158.208-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-158-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ted1601 F pulseaudio
  Date: Thu Feb 28 17:28:08 2019
  DpkgHistoryLog:
   
  DpkgTerminalLog:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=b19220b6-a5a1-401c-ba85-ba1258cebf42
  InstallationDate: Installed on 2014-04-19 (1776 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-158-generic 
root=/dev/mapper/hostname-root ro acpi.power_nocheck=0 elevator=noop quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.16
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-158-generic 3.13.0-158.208 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 03XK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 530U3BI/530U4BI/530U4BH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 

[Kernel-packages] [Bug 1818162] [NEW] arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout

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

[Impact]
During heavy load, the following message may appear on the console of a 
HiSilicon D06 system:

arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout

This is due to a bug that can also impact system performance, as the CPU
is blocked until the timeout occurs.

[Test Case]
The Ubuntu server certification test suite hits this pretty reliably during the 
stress-ng tests, although I haven't narrowed it down to exactly which test yet.

[Regression Risk]
Limited to arm64 systems. This change has been upstream since 4.20 w/o any 
noticed regressions (based on lack of Fixes: commits). Regressions could 
manifest as a performance hit.

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

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

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

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

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

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

Title:
  arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout

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

Bug description:
  [Impact]
  During heavy load, the following message may appear on the console of a 
HiSilicon D06 system:

  arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout

  This is due to a bug that can also impact system performance, as the
  CPU is blocked until the timeout occurs.

  [Test Case]
  The Ubuntu server certification test suite hits this pretty reliably during 
the stress-ng tests, although I haven't narrowed it down to exactly which test 
yet.

  [Regression Risk]
  Limited to arm64 systems. This change has been upstream since 4.20 w/o any 
noticed regressions (based on lack of Fixes: commits). Regressions could 
manifest as a performance hit.

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

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


[Kernel-packages] [Bug 1818126] Re: linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker

2019-02-28 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

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

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:36 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


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

2019-02-28 Thread Marcelo Cerri
*** This bug is a duplicate of bug 1818126 ***
https://bugs.launchpad.net/bugs/1818126

** This bug has been marked a duplicate of bug 1818126
   linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker

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

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

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

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

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

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

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


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

2019-02-28 Thread Christopher M. Penalver
** Tags removed: bios-outdated-1.6.1 kernel-bug-exists-upstream-4.7 
needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-5.0-rc8 latest-bios-1.6.1

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

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

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

Status in linux package in Ubuntu:
  Triaged

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1818128] Re: linux-azure: 4.18.0-1013.13 -proposed tracker

2019-02-28 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
- phase: Packaging
- phase-changed: Thursday, 28. February 2019 21:41 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 28. February 2019 23:31 UTC
  reason:
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 28. February 2019 23:31 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

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

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


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

2019-02-28 Thread adin
I'm completing the reports below:

3. $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for adin:
1.6.1
07/17/2018

4. On kernel version 5.0.0-05rc8-generic the problem persists.

* I also ran the previously requested `evtest` and got

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

[Kernel-packages] [Bug 1818126] Re: linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker

2019-02-28 Thread Marcelo Cerri
** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker

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

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

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

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

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

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:36 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1735159] Re: powerpc/powernv: Flush console before platform error reboot

2019-02-28 Thread bugproxy
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1710

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

Title:
  powerpc/powernv: Flush console before platform error reboot

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Released

Bug description:
  == SRU Justification ==
  IBM unrecovered MCE and HMI errors are sent through a special restart OPAL
  call to log the platform error. The downside is that they don't go
  through normal Linux crash paths, so they don't give much information
  to the Linux console.

  IBM is requesting to have the commit b746e3e01e70d23ef53dcde1203ab78a1b7ac514
  in the Zesty kernel.

  Commit b746e3e01e70d2 is in mainline as of 4.14-rc1.

  Breno Leitao from IBM did a backport of this commit.

  == Fix ==
  commit b746e3e01e70d23ef53dcde1203ab78a1b7ac514
  Author: Nicholas Piggin 
  Date:   Wed Jul 19 16:59:10 2017 +1000

  powerpc/powernv: Flush console before platform error reboot

  == Regression Potential ==
  This patch is specific to powerpc, and it has been backported, reviewed and 
  tested by IBM.

  == 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.

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

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


[Kernel-packages] [Bug 1818128] Re: linux-azure: 4.18.0-1013.13 -proposed tracker

2019-02-28 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Packaging
  phase-changed: Thursday, 28. February 2019 21:41 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Packaging
  phase-changed: Thursday, 28. February 2019 21:41 UTC
  reason:
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1817628] Re: Regular D-state processes impacting LXD containers

2019-02-28 Thread Khaled El Mously
** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

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

Title:
  Regular D-state processes impacting LXD containers

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

Bug description:
  [Impact]

   * Systems running under memory pressure may hit stalls in the
 order of seconds to minutes in systemd-logind and lxd mount
 operations (e.g., ZFS backend), which get stuck in D state.

   * The processes stuck in D state have a common stack trace,
 (cat /proc/PID/stack) all blocked in register_shrinker().

   * The fix checks in shrink_slab() (shrinkers are called under
 memory pressure) for contention/usage of the semaphore used
 by register_shrinker() and returns early in that case.

 This allows the register_shrinker() callers to unblock,
 and not stall until the shrink operation releases that lock.

  [Test Case]

   * In a system under memory pressure, specifically having the
 memory shrinkers being called often and taking time to run,
 perform mount operations (or other operations that acquire
 the shrinker_rwsem semaphore).

   * The user who reported the problem has verified the fix in
 systems that exhibted the problem often (sometimes daily),
 and tells it resolves the problem.

  [Regression Potential]

   * Low. The fix just returns early from slab memory shrinker
 if there's usage/contention for 'shrinker_rwsem'.

   * In some scenarios, this may cause the slab memory shrinker
 to require more invocations to actually finish and potentially
 release memory, but this seems minor since other shrinkers can
 release memory as well, and compared to the fact that this fix
 allows other applications to make progress / continue to run,
 which would otherwise be stalled.

  [Other Info]
   
   * This patch is already applied in Cosmic and later (v4.16+).
 It is needed only in Xenial and Bionic at this time.

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

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


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

2019-02-28 Thread Marcelo Cerri
*** This bug is a duplicate of bug 1818128 ***
https://bugs.launchpad.net/bugs/1818128

** This bug has been marked a duplicate of bug 1818128
   linux-azure: 4.18.0-1013.13 -proposed tracker

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

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

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

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

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

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

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


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

2019-02-28 Thread Khaled El Mously
** Changed in: linux-gcp (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

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

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

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Xenial:
  Fix Committed
Status in linux-gcp source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Cosmic:
  Fix Committed
Status in linux-gcp source package in Disco:
  In Progress

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

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

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


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

2019-02-28 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 1818148

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

Title:
  virtualbox-guest-x11 does not work with 4.4.0-143-generic from xenial-
  proposed

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

Bug description:
  Steps to reproduce:
  1. Have 16.04 LTS installed
  2. Enable xenial-proposed repository
  3. Install `virtualbox-guest-x11` package

  Expected results:
  * virtualbox-guest-x11 is working as before

  Actual results:
  * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: 
Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Mar  1 00:38:30 2019
  InstallationDate: Installed on 2018-08-07 (205 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1818141] Re: linux-azure - Add the same 4.15 InfiniBand configuration settings to the 4.18 kernel

2019-02-28 Thread Marcelo Cerri
** Also affects: linux-azure (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: linux-azure (Ubuntu Cosmic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

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

Title:
  linux-azure - Add the same 4.15 InfiniBand configuration settings to
  the 4.18 kernel

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  The InfiniBand configuration settings from the 4.15 linux-azure kernel
  are not in the 4.18 linux-azure kernel.

  This is a request to apply the same InfiniBand settings to the 4.18
  linux-azure kernel.

  The following settings are only in the 4.15 linux-azure kernel (tested
  with 4.15.0-1037 vs 4.18.0-1011):

  CONFIG_INFINIBAND_IPOIB=y
  CONFIG_INFINIBAND_IPOIB_DEBUG=y
  CONFIG_INFINIBAND_USER_MAD=y

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

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


[Kernel-packages] [Bug 1684971] Re: [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain

2019-02-28 Thread Marcelo Cerri
** Also affects: linux-azure (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

** Changed in: linux-azure (Ubuntu Cosmic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

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

Title:
  [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  Fix Released
Status in linux-azure source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  Fix Released
Status in linux-azure source package in Zesty:
  Invalid
Status in linux source package in Artful:
  Fix Released
Status in linux-azure source package in Artful:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  The following patch fixes a problem with "[PATCH] pci-hyperv: Use
  device serial number as PCI domain" where some drivers were expecting
  a u16 instead of a u32 for PCI device serial numbers, as observed by
  Oops and hangs in Azure on NC and NV GPU instances.

  From: Haiyang Zhang 

  This patch uses the lower 16 bits of the serial number as PCI
  domain, otherwise some drivers may not be able to handle it.

  Signed-off-by: Haiyang Zhang 
  ---
   drivers/pci/host/pci-hyperv.c |4 +++-
   1 files changed, 3 insertions(+), 1 deletions(-)

  diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
  index e73880c..b18dff3 100644
  --- a/drivers/pci/host/pci-hyperv.c
  +++ b/drivers/pci/host/pci-hyperv.c
  @@ -1334,9 +1334,11 @@ static void put_pcichild(struct hv_pci_dev *hpdev,
 * can have shorter names than based on the bus instance UUID.
 * Only the first device serial number is used for domain, so the
 * domain number will not change after the first device is added.
  +  * The lower 16 bits of the serial number is used, otherwise some
  +  * drivers may not be able to handle it.
 */
if (list_empty(>children))
  - hbus->sysdata.domain = desc->ser;
  + hbus->sysdata.domain = desc->ser & 0x;
list_add_tail(>list_entry, >children);
spin_unlock_irqrestore(>device_list_lock, flags);
return hpdev;
  -- 
  1.7.1

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

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


[Kernel-packages] [Bug 1818148] Re: virtualbox-guest-x11 does not work with 4.4.0-143-generic from xenial-proposed

2019-02-28 Thread Ubuntu Kernel Bot
** Package changed: linux-meta (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/1818148

Title:
  virtualbox-guest-x11 does not work with 4.4.0-143-generic from xenial-
  proposed

Status in linux package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have 16.04 LTS installed
  2. Enable xenial-proposed repository
  3. Install `virtualbox-guest-x11` package

  Expected results:
  * virtualbox-guest-x11 is working as before

  Actual results:
  * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: 
Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Mar  1 00:38:30 2019
  InstallationDate: Installed on 2018-08-07 (205 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2019-02-28 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Nvidia 340

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing NVIDIA driver, the screen brightness is freezed by
  100%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   senne  2237 F...m pulseaudio
   /dev/snd/controlC0:  senne  2237 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Feb 28 23:00:25 2019
  InstallationDate: Installed on 2018-12-24 (66 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Apple Inc. MacBook5,1
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8980397b-61c8-4011-a75c-9777552c623c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1818148] Re: virtualbox-guest-x11 does not work with 4.4.0-143-generic from xenial-proposed

2019-02-28 Thread Norbert
The previous 4.4.0-143-generic is also affected.

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

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

Title:
  virtualbox-guest-x11 does not work with 4.4.0-143-generic from xenial-
  proposed

Status in linux-meta package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have 16.04 LTS installed
  2. Enable xenial-proposed repository
  3. Install `virtualbox-guest-x11` package

  Expected results:
  * virtualbox-guest-x11 is working as before

  Actual results:
  * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: 
Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Mar  1 00:38:30 2019
  InstallationDate: Installed on 2018-08-07 (205 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1818152] [NEW] Nvidia 340

2019-02-28 Thread Senne
Public bug reported:

After installing NVIDIA driver, the screen brightness is freezed by 100%

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   senne  2237 F...m pulseaudio
 /dev/snd/controlC0:  senne  2237 F pulseaudio
CurrentDesktop: XFCE
Date: Thu Feb 28 23:00:25 2019
InstallationDate: Installed on 2018-12-24 (66 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Apple Inc. MacBook5,1
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8980397b-61c8-4011-a75c-9777552c623c ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-45-generic N/A
 linux-backports-modules-4.15.0-45-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/27/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB51.88Z.007D.B03.0904271443
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F42D89C8
dmi.board.vendor: Apple Inc.
dmi.board.version: Proto
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42D89C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:
dmi.product.family: MacBook
dmi.product.name: MacBook5,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  Nvidia 340

Status in linux package in Ubuntu:
  New

Bug description:
  After installing NVIDIA driver, the screen brightness is freezed by
  100%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   senne  2237 F...m pulseaudio
   /dev/snd/controlC0:  senne  2237 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Feb 28 23:00:25 2019
  InstallationDate: Installed on 2018-12-24 (66 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Apple Inc. MacBook5,1
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8980397b-61c8-4011-a75c-9777552c623c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1818149] [NEW] backport relevant patches for support of the base_frequency attribute of intel_pstate

2019-02-28 Thread Terry Rudd
Public bug reported:

Need to back port the following HWE commits from 4.20/5.0 kernel to 4.18, then 
4.15 kernels for Cosmic and Bionic HWE
29523f095397637edca60c627bc3e5c25a02c40f 
86d333a8cc7f66c2314ab1e147834a1cd95ec2de

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Terry Rudd (terrykrudd)
 Status: Incomplete

** Changed in: qemu (Ubuntu)
 Assignee: (unassigned) => Terry Rudd (terrykrudd)

** Package changed: qemu (Ubuntu) => kernel-package (Ubuntu)

** Changed in: kernel-package (Ubuntu)
   Importance: Undecided => High

** Changed in: kernel-package (Ubuntu)
 Assignee: Terry Rudd (terrykrudd) => (unassigned)

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

** Description changed:

- Need to back port the following HWE commits from 4.20/5.0 kernel to
- 4.18, then 4.15 kernels for Cosmic and Bionic HWE
+ Need to back port the following HWE commits from 4.20/5.0 kernel to 4.18, 
then 4.15 kernels for Cosmic and Bionic HWE
+ 29523f095397637edca60c627bc3e5c25a02c40f 
+ 86d333a8cc7f66c2314ab1e147834a1cd95ec2de

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Terry Rudd (terrykrudd)

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

Title:
  backport relevant patches for support of the base_frequency attribute
  of intel_pstate

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Need to back port the following HWE commits from 4.20/5.0 kernel to 4.18, 
then 4.15 kernels for Cosmic and Bionic HWE
  29523f095397637edca60c627bc3e5c25a02c40f 
  86d333a8cc7f66c2314ab1e147834a1cd95ec2de

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

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


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

2019-02-28 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 1818149

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

Title:
  backport relevant patches for support of the base_frequency attribute
  of intel_pstate

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Need to back port the following HWE commits from 4.20/5.0 kernel to 4.18, 
then 4.15 kernels for Cosmic and Bionic HWE
  29523f095397637edca60c627bc3e5c25a02c40f 
  86d333a8cc7f66c2314ab1e147834a1cd95ec2de

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

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


[Kernel-packages] [Bug 1818149] [NEW] backport relevant patches for support of the base_frequency attribute of intel_pstate

2019-02-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Need to back port the following HWE commits from 4.20/5.0 kernel to
4.18, then 4.15 kernels for Cosmic and Bionic HWE

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

-- 
backport relevant patches for support of the base_frequency attribute of 
intel_pstate
https://bugs.launchpad.net/bugs/1818149
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 1818128] Re: linux-azure: 4.18.0-1013.13 -proposed tracker

2019-02-28 Thread Brad Figg
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu
   Status: New => Invalid

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
- phase: Ready for Packaging
- phase-changed: Thursday, 28. February 2019 18:41 UTC
+ phase: Packaging
+ phase-changed: Thursday, 28. February 2019 21:41 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Packaging
  phase-changed: Thursday, 28. February 2019 21:41 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1817944] Re: Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

2019-02-28 Thread udippel
** Attachment added: "For completeness: xrandr for the micro-HDMI output on the 
tablet which works fine."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817944/+attachment/5242437/+files/xrandr_via_microHDMI

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818128] Re: linux-azure: 4.18.0-1013.13 -proposed tracker

2019-02-28 Thread Marcelo Cerri
** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.18.0-1013.13 -proposed tracker

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

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

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

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

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

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:41 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1814393] Re: "make: write error: stdout" on parallel builds

2019-02-28 Thread Éric Hoffman
I have yet to see any issue (i.e. it's working fine) with 4.15.0.46 (I
used xenial-proposed to upgrade).

As the rest of you, I had constant issue with this in 4.15.0-45

So yes, maybe it is related to the tty bug.  This does seem to be
consistent with the behavior I was seeing with current kernel.  For
example, I had many 'resources busy' and other output-related messages
on make output.

And, doing:

  make -j8 2>&1 | tee outfile.txt

I often saw the console just stop outpointing any text (although the
compilation continued, and completed, in the background).

So, Jburgess777 you may be correct about the duplicate...

Regards,
Eric

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

Title:
  "make: write error: stdout" on parallel builds

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  - Release of Ubuntu: 18.04.1 LTS (Kubuntu).
  - Package version: linux-image-4.15.0-44-generic, 
linux-image-4.15.0-45-generic.
  - Expected outcome: Large parallel make build completing properly.
  - What happened instead: Build stops with "make: write error: stdout".

  Full explanation:

  Since the update to kernel 4.15.0-44 (linux-image-4.15.0-44-generic)
  in Kubuntu Bionic I'm experiencing issues in my ThinkPad P52 laptop
  during large parallel builds of source code (eg: a buildroot full
  rebuild for a work project). Note that this reports isn't about kernel
  builds, but about large project builds in general.

  I don't think it's relevant, but I'm running those builds in an
  schroot with the same Ubuntu Bionic distro I'm also using as main host
  distro.

  The specific error I get is this (in Spanish):

make[4]: error al escribir: stdout

  I call Buildroot's make like this from KDE Konsole with "infinite
  history buffer" enabled (uses a tmp file to store the logs):

V=1 make ...some stuff... 2>&1

  However, the error is reproducible in Konsole even if I call make
  without options and also if I use "limited (in-memory) history buffer"
  as well as "no history buffer". Buildroot autoselects a
  parallelization level (-j) automatically. In my case, I'm using a Xeon
  E-2176 CPU with 12 threads.

  Searching on the Internet I found a thread[1] where people from the
  GNU Make project say that the error may be coming from the C runtime
  library (and I suspect originating from the kernel).

  I can NOT reproduce the issue on linux-image-4.15.0-43-generic
  (selected from grub at boot), but I experience it with linux-
  image-4.15.0-44-generic and linux-image-4.15.0-45-generic. That's why
  I'm reporting this bug against the linux package.

  Interestingly enough, I can NOT reproduce the issue on linux-
  image-4.15.0-45-generic (haven't tried previous versions) when
  building from xterm instead of Konsole. Unfortunately, this laptop has
  a 4K screen and xterm isn't an option for me.

  If I build redirecting stdout and stderr to different files to avoid
  terminal output and then watching the stdout file with tail -f, the
  tail command eventually finishes although the build continues and I
  can keep watching it by running tail again. An infinite build loop
  never finishes with this redirection (error not reproducible). Same
  results with the 2>&1 redirection to a single file.

  All this looks a bit like a poltergeist, but the only thing I'm sure
  about is that it all started with the upgrade from 4.15.0-43 to -44
  and it continues on -45.

  Thank you.

  
  [1] 
http://gnu-make.2324884.n4.nabble.com/Spurious-quot-write-error-quot-on-parallel-builds-td15695.html

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

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


[Kernel-packages] [Bug 1818140] [NEW] Kernel module race condition during bluetooth discovery

2019-02-28 Thread Bartłomiej Żogała
Public bug reported:

Bugs probably in firmware:

Bluetooth: hci0: last event is not cmd complete (0x0f)

are causing:

kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to
register things with the same name in the same directory


This issue is about kernel - it shouldn't rely on state of unrealiable 
propertary drivers. Sometimes rmmod all bluetooth modules helps, sometimes 
restart is just faster.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 28 21:13:21 2019
InstallationDate: Installed on 2015-05-08 (1392 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
InterestingModules: btusb rfcomm bnep bluetooth
MachineType: Dell Inc. XPS 13 9343
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash 
log_buf_len=1M crashkernel=384M-:128M
SourcePackage: bluez
UpgradeStatus: Upgraded to bionic on 2018-08-26 (185 days ago)
dmi.bios.date: 09/27/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.name: 09K8G1
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd09/27/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 34:68:95:ED:83:EA  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1283292 acl:65502 sco:1441 events:1266 errors:0
TX bytes:360374 acl:522 sco:1436 commands:565 errors:0

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


** Tags: amd64 apport-bug bionic

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

Title:
  Kernel module race condition during bluetooth discovery

Status in bluez package in Ubuntu:
  New

Bug description:
  Bugs probably in firmware:

  Bluetooth: hci0: last event is not cmd complete (0x0f)

  are causing:

  kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to
  register things with the same name in the same directory

  
  This issue is about kernel - it shouldn't rely on state of unrealiable 
propertary drivers. Sometimes rmmod all bluetooth modules helps, sometimes 
restart is just faster.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 28 21:13:21 2019
  InstallationDate: Installed on 2015-05-08 (1392 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash 
log_buf_len=1M crashkernel=384M-:128M
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (185 days ago)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09K8G1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd09/27/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 34:68:95:ED:83:EA  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1283292 acl:65502 sco:1441 events:1266 errors:0
TX bytes:360374 acl:522 sco:1436 commands:565 errors:0

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

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


[Kernel-packages] [Bug 1818141] [NEW] linux-azure - Add the same 4.15 InfiniBand configuration settings to the 4.18 kernel

2019-02-28 Thread David Coronel
Public bug reported:

The InfiniBand configuration settings from the 4.15 linux-azure kernel
are not in the 4.18 linux-azure kernel.

This is a request to apply the same InfiniBand settings to the 4.18
linux-azure kernel.

The following settings are only in the 4.15 linux-azure kernel (tested
with 4.15.0-1037 vs 4.18.0-1011):

CONFIG_INFINIBAND_IPOIB=y
CONFIG_INFINIBAND_IPOIB_DEBUG=y
CONFIG_INFINIBAND_USER_MAD=y

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

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

Title:
  linux-azure - Add the same 4.15 InfiniBand configuration settings to
  the 4.18 kernel

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The InfiniBand configuration settings from the 4.15 linux-azure kernel
  are not in the 4.18 linux-azure kernel.

  This is a request to apply the same InfiniBand settings to the 4.18
  linux-azure kernel.

  The following settings are only in the 4.15 linux-azure kernel (tested
  with 4.15.0-1037 vs 4.18.0-1011):

  CONFIG_INFINIBAND_IPOIB=y
  CONFIG_INFINIBAND_IPOIB_DEBUG=y
  CONFIG_INFINIBAND_USER_MAD=y

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

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


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

2019-02-28 Thread David Rasch
I spoke too soon, back to "question mark" state and no connection.

[16070.951387] ath10k_pci :02:00.0: firmware crashed! (guid 
a288f3c4-d6a5-43f2-8c18-2ef3ed9d63f6)
[16070.951424] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 1a56:143a
[16070.951433] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
[16070.953085] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[16070.954386] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
[16070.954407] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp 
max-sta 32 raw 0 hwcrypto 1
[16070.964559] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
[16070.964581] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[16070.964588] ath10k_pci :02:00.0: Copy Engine register dump:
[16070.964608] ath10k_pci :02:00.0: [00]: 0x00034400  11  11   3   3
[16070.964626] ath10k_pci :02:00.0: [01]: 0x00034800  31  31 395 396
[16070.964641] ath10k_pci :02:00.0: [02]: 0x00034c00  38  37 100 101
[16070.964663] ath10k_pci :02:00.0: [03]: 0x00035000  15  15  17  15
[16070.964679] ath10k_pci :02:00.0: [04]: 0x00035400 347 337 233 169
[16070.964693] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
[16070.964710] ath10k_pci :02:00.0: [06]: 0x00035c00  14  13  14  12
[16070.964730] ath10k_pci :02:00.0: [07]: 0x00036000   0   0   0   1
[16071.003122] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
[16071.088236] ieee80211 phy0: Hardware restart was requested
[16071.309828] ath10k_pci :02:00.0: unsupported HTC service id: 1536
[16071.430225] ath10k_pci :02:00.0: device successfully recovered

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress

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

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

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

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

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


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

2019-02-28 Thread bmaupin
This is what I'm getting:

63db7c815bc0997c29e484d2409684fdd9fcd93b is the first bad commit

But that feels wrong; it looks like it's a fix for XFS?:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=63db7c815bc0997c29e484d2409684fdd9fcd93b

... and I'm not using XFS:

$ cat /etc/fstab | grep -i xfs
$ mount | grep -i xfs

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1818138] [NEW] Add CONFIG_NO_HZ_FULL=y to linux-azure kernels

2019-02-28 Thread David Coronel
Public bug reported:

This is a request to enable CONFIG_NO_HZ_FULL=y in the linux-azure
kernels(currently 4.15 and 4.18) in order to increase NVME disks
performance.

The current CONFIG_NO_HZ configuration in linux-azure kernels is the
following (tested on 4.15.0-1037, 4.15.0-1039 and 4.18.0-1011):

CONFIG_NO_HZ=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_NO_HZ_FULL is not set
CONFIG_NO_HZ_IDLE=y

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

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

Title:
  Add CONFIG_NO_HZ_FULL=y to linux-azure kernels

Status in linux-azure package in Ubuntu:
  New

Bug description:
  This is a request to enable CONFIG_NO_HZ_FULL=y in the linux-azure
  kernels(currently 4.15 and 4.18) in order to increase NVME disks
  performance.

  The current CONFIG_NO_HZ configuration in linux-azure kernels is the
  following (tested on 4.15.0-1037, 4.15.0-1039 and 4.18.0-1011):

  CONFIG_NO_HZ=y
  CONFIG_NO_HZ_COMMON=y
  # CONFIG_NO_HZ_FULL is not set
  CONFIG_NO_HZ_IDLE=y

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

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


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

2019-02-28 Thread David Rasch
** Attachment added: "dmesg-56.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799988/+attachment/5242422/+files/dmesg-56.txt

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress

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

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

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

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

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


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

2019-02-28 Thread David Rasch
Tried the kernel in #50 and seeing better stability.

Still seeing firmware crashes. But recovery seems to work and wifi
restored:

[ 4064.530572] ath10k_pci :02:00.0: firmware crashed! (guid 
96a14669-a82f-4941-a3b3-690b13b81df9)
[ 4064.530628] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 1a56:143a
[ 4064.530639] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
[ 4064.532787] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 4064.534233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
[ 4064.534258] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp 
max-sta 32 raw 0 hwcrypto 1
[ 4064.544704] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
[ 4064.544710] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 4064.544712] ath10k_pci :02:00.0: Copy Engine register dump:
[ 4064.544722] ath10k_pci :02:00.0: [00]: 0x00034400  11  11   3   3
[ 4064.544732] ath10k_pci :02:00.0: [01]: 0x00034800   8   7 500 501
[ 4064.544741] ath10k_pci :02:00.0: [02]: 0x00034c00   8   7   6   7
[ 4064.544750] ath10k_pci :02:00.0: [03]: 0x00035000  15  15  17  15
[ 4064.544759] ath10k_pci :02:00.0: [04]: 0x00035400 1631 1629 111  47
[ 4064.544770] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
[ 4064.544779] ath10k_pci :02:00.0: [06]: 0x00035c00  16  14  16  14
[ 4064.544793] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
[ 4064.557821] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
[ 4064.642187] ieee80211 phy0: Hardware restart was requested
[ 4064.852139] ath10k_pci :02:00.0: unsupported HTC service id: 1536
[ 4064.980877] ath10k_pci :02:00.0: device successfully recovered


I will attach full dmesg.

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress

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

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

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

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

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

[Kernel-packages] [Bug 1814651] Re: linux-aws: 4.4.0-1076.86 -proposed tracker

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

** Description changed:

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1814651] Re: linux-aws: 4.4.0-1076.86 -proposed tracker

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1814730] Re: linux-oem: 4.15.0-1034.39 -proposed tracker

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

** Description changed:

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

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

Title:
  linux-oem: 4.15.0-1034.39 -proposed tracker

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

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

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

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

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


[Kernel-packages] [Bug 1814730] Re: linux-oem: 4.15.0-1034.39 -proposed tracker

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

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

Title:
  linux-oem: 4.15.0-1034.39 -proposed tracker

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

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

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

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

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


[Kernel-packages] [Bug 1818134] [NEW] modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

2019-02-28 Thread id prism
Public bug reported:

when installing bcmwl-kernel-source to build wl.ko

package version: 6.30.223.248+bdcom-0ubuntu0.2

Expected behavior: kernel module wl.ko loads.
What happened: finit_module returns ENOPKG


My device is: BCM4352 [14e4:43b1] (rev 03)

Happened after latest OS update, downgrading kernel to 164 did not fix,
downgrading package did not work.

secure boot mode is off.

A few others are having this issue
https://ubuntuforums.org/showthread.php?t=2413303

There is a possibility it is a modaliases problem -- 2015 chagelog
states that there was a capitalization problem, but I don't know how to
check this.

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


** Tags: broadcom dell interface missing wifi wlan xps

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  New

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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


[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage

2019-02-28 Thread Keith Hutton
Further, to my comment above, if I enable swap, the program continues to
run using up all the swap, and then terminates without a system freeze.
The program pauses for about 1/3 second intervals as swap gets used. The
higher vm.min_free_kbytes the pauses are less. I have a third memory
eater and I managed to get up to 66 Gb virtual memory allocated. My old
laptop (9 years) has only 2Gb Ram.

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

Title:
  When DMA is disabled system freeze on high memory usage

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Arch Linux:
  New

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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

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


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

2019-02-28 Thread Kamal Pandey
after resetting the bios to factory reset I was able to avoid the
following error :

Couldn't get size: 0x800e
MODSIGN: Couldn't get UEFI db list

But I still got the following error:
[5.354582] Couldn't get size: 0x800e
[5.354610] MODSIGN: Couldn't get UEFI MokListRT

the setting which got changed is as follows
In the security tab of the BIOS secure boot mode --> custom was changed to 
secure boot mode --> standard

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

Title:
  MODSIGN: Couldn't get UEFI db list

Status in linux package in Ubuntu:
  Fix Released

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

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

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

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

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

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


[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage

2019-02-28 Thread Keith Hutton
Try increasing vm.min_free_kbytes

I have two memory eater programs, one uses 1Mb steps and the other 1Kb steps. 
When I run the 1Mb, the oom killer cuts in. When I run the 1Kb program the oom 
does not.
If I raise the vm.min_free_kbytes = 17-25 both programs are terminated, 
no system freeze.

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

Title:
  When DMA is disabled system freeze on high memory usage

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Arch Linux:
  New

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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

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


[Kernel-packages] [Bug 1818126] Re: linux-azure: -proposed tracker

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

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:36 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- version not specified

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:36 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1818126] Re: linux-azure: -proposed tracker

2019-02-28 Thread Kleber Sacilotto de Souza
** Tags removed: kernel-sru-cycle-2019.01.14-5
** Tags added: kernel-sru-cycle-2019.02.04-3

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
- kernel-stable-master-bug: 1816783
+ kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:36 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- version not specified

** Tags removed: kernel-sru-backport-of-1816783
** Tags added: kernel-sru-backport-of-1814749

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:36 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1818128] Re: linux-azure: -proposed tracker

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

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:41 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- version not specified

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:41 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1818128] Re: linux-azure: -proposed tracker

2019-02-28 Thread Kleber Sacilotto de Souza
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
- kernel-stable-master-bug: 1816783
+ kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:41 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- version not specified

** Tags removed: kernel-sru-derivative-of-1816783
** Tags added: kernel-sru-derivative-of-1814749

** Tags removed: kernel-sru-cycle-2019.01.14-5
** Tags added: kernel-sru-cycle-2019.02.04-3

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:41 UTC
  reason:
    prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:24 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.4.0-143.169 -proposed tracker

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

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

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

  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:24 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker

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

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

Title:
  linux: 4.4.0-143.169 -proposed tracker

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

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

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

  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:24 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1818126] Re: linux-azure: -proposed tracker

2019-02-28 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1816783
+ phase: Ready for Packaging
+ phase-changed: Thursday, 28. February 2019 18:36 UTC
+ reason:
+   prepare-package: Pending -- version not specified

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1816783
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:36 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1818128] Re: linux-azure: -proposed tracker

2019-02-28 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1816783
+ phase: Ready for Packaging
+ phase-changed: Thursday, 28. February 2019 18:41 UTC
+ reason:
+   prepare-package: Pending -- version not specified

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1816783
  phase: Ready for Packaging
  phase-changed: Thursday, 28. February 2019 18:41 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


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

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

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

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

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

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

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

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

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

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


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

2019-02-28 Thread Kleber Sacilotto de Souza
** Tags removed: kernel-sru-master-kernel

** Tags removed: kernel-sru-cycle-2019.01.14-5

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

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

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

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

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

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

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


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

2019-02-28 Thread Marcelo Cerri
** Description changed:

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

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

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

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

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

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

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

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


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

2019-02-28 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

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

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

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

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

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

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

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


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

2019-02-28 Thread Marcelo Cerri
** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Released => Confirmed

** Tags added: kernel-sru-cycle-2019.01.14-5

** Tags added: kernel-sru-master-kernel

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1818126] [NEW] linux-azure: -proposed tracker

2019-02-28 Thread Marcelo Cerri
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: 1816783

** 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: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa-dnu
 Importance: Medium
 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-backport-of-1816783 kernel-sru-cycle-2019.01.14-5

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

[Kernel-packages] [Bug 1818128] [NEW] linux-azure: -proposed tracker

2019-02-28 Thread Marcelo Cerri
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: 1816783

** 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: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa-dnu
 Importance: Medium
 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 Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.01.14-5 kernel-sru-derivative-of-1816783

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: cosmic

** Changed in: linux-azure (Ubuntu Cosmic)
   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-dnu
   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-packages] [Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list

2019-02-28 Thread Kamal Pandey
I am also facing this issue the logs are as follows:

[5.325847] Couldn't get size: 0x800e
[5.325850] MODSIGN: Couldn't get UEFI db list
[5.325867] Couldn't get size: 0x800e
[5.325868] MODSIGN: Couldn't get UEFI MokListRT
[5.327139] zswap: loaded using pool lzo/zbud

My kernel and ubuntu version is:
Linux kk 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

kk  
description: Notebook
product: 20245 (LENOVO_MT_20245)
vendor: LENOVO
version: Lenovo G500s
serial: 3285914003773
width: 64 bits
capabilities: smbios-2.7 dmi-2.7 smp vsyscall32
configuration: boot=normal chassis=notebook family=IDEAPAD 
sku=LENOVO_MT_20245 uuid=3FAFF882-37A5-11E3-A363-201A06349678
  *-core
   description: Motherboard
   product: INVALID
   vendor: LENOVO
   physical id: 0
   version: 3194Std
   serial: CB27477093
   slot: Type2 - Board Chassis Location
 *-firmware
  description: BIOS
  vendor: LENOVO
  physical id: 0
  version: 7BCN36WW(V2.02)
  date: 08/28/2013
  size: 128KiB
  capacity: 4544KiB
  capabilities: pci upgrade shadowing cdboot bootselect edd 
int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 
int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi
 *-cpu
  description: CPU
  product: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz
  vendor: Intel Corp.
  physical id: 4
  bus info: cpu@0
  version: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz
  serial: To Be Filled By O.E.M.
  slot: U3E1
  size: 2294MHz
  capacity: 2400MHz
  width: 64 bits
  clock: 100MHz
  capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce 
cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss 
ht tm pbe syscall nx rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer xsave avx f16c lahf_lm cpuid_fault epb pti ssbd ibrs ibpb 
stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm 
arat pln pts flush_l1d cpufreq
  configuration: cores=2 enabledcores=2 threads=4


any workaround will help too

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

Title:
  MODSIGN: Couldn't get UEFI db list

Status in linux package in Ubuntu:
  Fix Released

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wellington   1429 F pulseaudio
   /dev/snd/pcmC1D3p:   wellington   1429 F...m pulseaudio
   /dev/snd/controlC1:  wellington   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 22:37:13 2018
  HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e
  InstallationDate: Installed on 2018-01-16 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  

[Kernel-packages] [Bug 1811979] Re: My bluetooth (RT3290) is not working since i am using ubuntu 18.04, it works fine in windows 7

2019-02-28 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1816493 ***
https://bugs.launchpad.net/bugs/1816493

** This bug has been marked a duplicate of bug 1816493
   Ralink RT3290 Is Not in Kernel

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

Title:
  My bluetooth (RT3290) is not working since i am using ubuntu 18.04, it
  works fine in windows 7

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  bluetooth network in my ubuntu is not working.actually the on button in the 
setting does not turn bluetooth button in to ON, it remains OFF even if i click 
on it.i already installed bluez and blueman .
  i am using this version of ubuntu

  Description:Ubuntu 18.04.1 LTS

  Release:18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 16 15:10:56 2019
  InterestingModules: bluetooth
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=1a5a1726-0948-424a-a01e-de88efc704ca ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 226E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 74.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn226E:rvr74.19:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:

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

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


[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

2019-02-28 Thread Khaled El Mously
** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

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

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

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

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


[Kernel-packages] [Bug 1817969] Re: hns3 nic speed may not match optical port speed

2019-02-28 Thread Khaled El Mously
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  hns3 nic speed may not match optical port speed

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

Bug description:
  [Impact]
  The onboard optical NICs on HiSilicon D06 systems do not adjust to match the 
actual optical module speed.

  [Test Case]
  Verify that linked speed of interface matches the optical port speed.

  [Fix]
  5d497936756fa net: hns3: Config NIC port speed same as that of optical module

  [Regression Risk]
  Fix is restricted to a driver that is only used for the Hi1620 SoC. Note: for 
pre-GA hardware, this does require a firmware fix as well. Without it, users 
will see messages like this on the console:

  [ 769.833818] hns3 :bd:00.0: get sfp speed failed -5

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

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


[Kernel-packages] [Bug 1818124] Re: Bluetooth device not found

2019-02-28 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1816493 ***
https://bugs.launchpad.net/bugs/1816493

Thank you for your bug report, that's known and reported as bug #1811979

https://ubuntuforums.org/showthread.php?t=2383479 mention a dmks driver
build, maybe you want to try that

** This bug has been marked a duplicate of bug 1816493
   Ralink RT3290 Is Not in Kernel

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

Title:
  Bluetooth device not found

Status in bluez package in Ubuntu:
  New

Bug description:
  I have a  dual  booted laptop with windows and ubuntu 18.04lts dual booted. 
The bluetooth device works very well in windows 10 but when i try to enable it 
in ubuntu it shows in settings menu that there is no bluetooth device connected 
to the laptop. "lspci" command reports that there is infact a bluetooth device 
connected-
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.5 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 6 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI 
mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI 
Express Card Reader (rev 01)
  08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 07)
  09:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
  09:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth

  the command "sudo rfkill list" shows no signs of a bluetooth device.

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

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


  1   2   >