date:20180402

I don't know how to add a tag on a Bug Report ...

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

Title:
  Broadcom B43 Wireless Driver Not Functional after Update to Linux
  Kernel 4.15

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

Bug description:
  I was upgrading my Ubuntu Xenial 16.04 from linux-hwe kernel 4.13.0-38
  to linux-hwe-edge 4.15.0-13.

  After reboot my Broadcom network adapter (requiring package
  firmware-b43-installer) is not recognized by the new kernel 4.15.0-13.

  Running the lspci command lists the device as 'UNCLAIMED' in linux
  kernel 4.15.

  $ lspci
  [...]
  *-pci:4
   description: PCI bridge
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 1c
   bus info: pci@:00:1c.0
   version: f0
   width: 32 bits
   clock: 33MHz
   capabilities: pci pciexpress msi pm normal_decode bus_master 
cap_list
   configuration: driver=pcieport
   resources: irq:123 memory:ef50-ef5f
     *-network UNCLAIMED
  description: Network controller
  product: BCM4331 802.11a/b/g/n
  vendor: Broadcom Corporation
  physical id: 0
  bus info: pci@:05:00.0
  version: 02
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress cap_list
  configuration: latency=0
  resources: memory:ef50-ef503fff
  [...]
  $

  The lspci -vv -pci:4 commands with the relevant devices are shown
  below.

  $ lspci -vv -pci:4
  [...]
  05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 
02)
   Subsystem: Apple Inc. AirPort Extreme
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
    Address:   Data: 
   Capabilities: [d0] Express (v1) Endpoint, MSI 00
    DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
     ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
     RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 
<4us, L1 <64us
     ClockPM+ Surprise- LLActRep+ BwNot- ASPMOptComp-
    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
     ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ 
BWMgmt- ABWMgmt-
   Capabilities: [100 v1] Advanced Error Reporting
    UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ 
MalfTLP+ ECRC- UnsupReq- ACSViol-
    CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
    CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
    AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
   Capabilities: [13c v1] Virtual Channel
    Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
    Arb:Fixed- WRR32- WRR64- WRR128-
    Ctrl:   ArbSelect=Fixed
    Status: InProgress-
    VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
     Arb:   Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
     Ctrl:  Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
     Status:NegoPending- InProgress-
   Capabilities: [160 v1] Device Serial Number c6-d6-51-ff-ff-e6-f4-f9
   Capabilities: [16c v1] Power Budgeting 
   Kernel modules: bcma
  [...]
  $

  The circumstances of this bug is well described on this webpage:

  https://bbs.archlinux.org/viewtopic.php?id=234122

  Furthermore a patch has been provided upstream:
  [UPDATE]: This patch is already part of the used kernel version.
Hence this bug is not related to this patch.

  https://patchwork.kernel.org/patch/10185397/
  
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=a9e6d44ddeccd3522670e641f1ed9b068e746ff7

  But is still not implemented in any Ubuntu release.

  If this is not corrected on time, then the new Bionic 18.04 will fail to 
connect to Internet and the local network as well if it uses a Broadcom network 
adapter requiring the package firmware-b43-installer.
  ---

[Kernel-packages] [Bug 1760108] Re: Broadcom B43 Wireless Driver Not Functional after Update to Linux Kernel 4.15

After some deciphering I see that on the Network controller I get:

Capabilities: 
Kernel modules: bcma

May it's blacklisted somewhere and upon proper action, I can get a fully
functional Wi-Fi in Kernel 4.16.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/1760108

Title:
  Broadcom B43 Wireless Driver Not Functional after Update to Linux
  Kernel 4.15

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

Bug description:
  I was upgrading my Ubuntu Xenial 16.04 from linux-hwe kernel 4.13.0-38
  to linux-hwe-edge 4.15.0-13.

  After reboot my Broadcom network adapter (requiring package
  firmware-b43-installer) is not recognized by the new kernel 4.15.0-13.

  Running the lspci command lists the device as 'UNCLAIMED' in linux
  kernel 4.15.

  $ lspci
  [...]
  *-pci:4
   description: PCI bridge
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 1c
   bus info: pci@:00:1c.0
   version: f0
   width: 32 bits
   clock: 33MHz
   capabilities: pci pciexpress msi pm normal_decode bus_master 
cap_list
   configuration: driver=pcieport
   resources: irq:123 memory:ef50-ef5f
     *-network UNCLAIMED
  description: Network controller
  product: BCM4331 802.11a/b/g/n
  vendor: Broadcom Corporation
  physical id: 0
  bus info: pci@:05:00.0
  version: 02
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress cap_list
  configuration: latency=0
  resources: memory:ef50-ef503fff
  [...]
  $

  The lspci -vv -pci:4 commands with the relevant devices are shown
  below.

  $ lspci -vv -pci:4
  [...]
  05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 
02)
   Subsystem: Apple Inc. AirPort Extreme
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
    Address:   Data: 
   Capabilities: [d0] Express (v1) Endpoint, MSI 00
    DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
     ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
     RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 
<4us, L1 <64us
     ClockPM+ Surprise- LLActRep+ BwNot- ASPMOptComp-
    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
     ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ 
BWMgmt- ABWMgmt-
   Capabilities: [100 v1] Advanced Error Reporting
    UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ 
MalfTLP+ ECRC- UnsupReq- ACSViol-
    CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
    CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
    AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
   Capabilities: [13c v1] Virtual Channel
    Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
    Arb:Fixed- WRR32- WRR64- WRR128-
    Ctrl:   ArbSelect=Fixed
    Status: InProgress-
    VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
     Arb:   Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
     Ctrl:  Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
     Status:NegoPending- InProgress-
   Capabilities: [160 v1] Device Serial Number c6-d6-51-ff-ff-e6-f4-f9
   Capabilities: [16c v1] Power Budgeting 
   Kernel modules: bcma
  [...]
  $

  The circumstances of this bug is well described on this webpage:

  https://bbs.archlinux.org/viewtopic.php?id=234122

  Furthermore a patch has been provided upstream:
  [UPDATE]: This patch is already part of the used kernel version.
Hence this bug is not related to this patch.

  https://patchwork.kernel.org/patch/10185397/
  
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=a9e6d44ddeccd3522670e641f1ed9b068e746ff7

  But is still not implemented in any Ubuntu release.

  If this is not corrected on time, then the new

[Kernel-packages] [Bug 1760108] Re: Broadcom B43 Wireless Driver Not Functional after Update to Linux Kernel 4.15

Well, I did test the Mainline Build Kernel 4.16 as suggested. Here are
the results:

$ lspci
00:00.0 Host bridge: Intel Corporation Device 3ec2 (rev 07)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)
00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Device a2af
00:16.0 Communication controller: Intel Corporation Device a2ba
00:17.0 SATA controller: Intel Corporation Device a282
00:1b.0 PCI bridge: Intel Corporation Device a2e7 (rev f0)
00:1b.2 PCI bridge: Intel Corporation Device a2e9 (rev f0)
00:1b.4 PCI bridge: Intel Corporation Device a2eb (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a290 (rev f0)
00:1c.1 PCI bridge: Intel Corporation Device a291 (rev f0)
00:1c.2 PCI bridge: Intel Corporation Device a292 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device a294 (rev f0)
00:1c.6 PCI bridge: Intel Corporation Device a296 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device a298 (rev f0)
00:1d.5 PCI bridge: Intel Corporation Device a29d (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a2c9
00:1f.2 Memory controller: Intel Corporation Device a2a1
00:1f.3 Audio device: Intel Corporation Device a2f0
00:1f.4 SMBus: Intel Corporation Device a2a3
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] 
(rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1)
05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02)
07:00.0 Ethernet controller: Qualcomm Atheros Device e0b1 (rev 10)
08:00.0 USB controller: ASMedia Technology Inc. Device 2142
09:00.0 USB controller: ASMedia Technology Inc. Device 2142
0b:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 10)
$ 

$ lspci -vv
[...]
05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02)
Subsystem: Apple Inc. AirPort Extreme
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: bcma

07:00.0 Ethernet controller: Qualcomm Atheros Device e0b1 (rev 10)
Subsystem: Gigabyte Technology Co., Ltd Device e000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: alx
Kernel modules: alx
[...]
$ 

So this time it looks like the network adapter is recognized by the
kernel 4.16 (it was UNCLAIMED by kernel 4.15).

Both the Wi-Fi network adapter and Bluetooth are recognized. However,
Ubuntu System Settings does not see any Wi-Fi ... So it can't connect
through anything Wi-Fi ...

It looks like there is definitely a bug in kernel 4.15.0, although I
don't know why Ubuntu can't see the recognized Wi-Fi network adapter in
kernel 4.16.0.

How can we label this bug then ? Is it considered kernel-fixed-upstream
? though there is no Wi-Fi recognized by Ubuntu Xenial 16.04 ?

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

Title:
  Broadcom B43 Wireless Driver Not Functional after Update to Linux
  Kernel 4.15

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

Bug description:
  I was upgrading my Ubuntu Xenial 16.04 from linux-hwe kernel 4.13.0-38
  to linux-hwe-edge 4.15.0-13.

  After reboot my Broadcom network adapter (requiring package
  firmware-b43-installer) is not recognized by the new kernel 4.15.0-13.

  Running the lspci command lists the device as 'UNCLAIMED' in linux
  kernel 4.15.

  $ lspci
  [...]
  *-pci:4
   description: PCI bridge
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 1c
   bus info: pci@:00:1c.0
   version: f0
   width: 32 bits
   clock: 33MHz
   capabilities: pci pciexpress msi pm normal_decode bus_master 
cap_list
   configuration: driver=pcieport
   resources: irq:123 memory:ef50-ef5f
     *-network UNCLAIMED
  description: Network controller
  product: BCM4331 802.11a/b/g/n
  vendor: Broadcom Corporation
  physical id: 0
  bus info: pci@:05:00.0
  version: 02
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress cap_list
  configuration: latency=0
  resources: memory:ef50-ef503fff
  [...]
  $

  The lspci -vv -pci:4 commands with the relevant devices are shown
  below.

  $ lspci -vv

[Kernel-packages] [Bug 1756240] Update Released

2018-04-02 Thread Steve Langasek

The verification of the Stable Release Update for lttng-modules has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Unable to build lttng-module with Artful kernel

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in lttng-modules source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Invalid
Status in lttng-modules source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lttng-modules source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * The 4.13.0-38 artful kernel included a change (backported from
  4.15) that modifies the definition of kvm_mmio(). This breaks the
  lttng-modules-dkms package because it is using the old (<4.15)
  definition.

   * lttng-modules-dkms already has a list of kernel version
  "exceptions" with which it uses the >=4.15 definition. Proposed
  solution is to add the Ubuntu kernel range 4.13.0-38 up to
  4.14.255-255 to that list of exceptions.

  
  [Test Case]

   * Tested by first successfully building lttng-modules-dkms on
  4.13.0-37, then reproducing the problem described here on 4.13.0-38,
  then applying the code-change and confirming that I can successfully
  build on both 4.13.0-37 and 4.13.0-38 after that.

  [Regression Potential]

   * Low-regression potential. Could prevent lttng-modules-dkms from
  being built for specific kernel versions, but this is unlikely as the
  change was tested to confirm that it works as expected on 4.13.0-37
  and 4.13.0-38 - and should work fine for other Ubuntu kernels as well.




  The lttng module failed to build with the proposed Artful kernel
  (4.13.0-38), it works with 4.13.0-37

  Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 16 04:13 seq
   crw-rw 1 root audio 116, 33 Mar 16 04:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  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:
  CurrentDmesg:

  Date: Fri Mar 16 04:17:14 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-38-generic N/A
   linux-backports-modules-4.13.0-38-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+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 1756240] Re: Unable to build lttng-module with Artful kernel

This bug was fixed in the package lttng-modules - 2.8.0-1ubuntu1~16.04.5

---
lttng-modules (2.8.0-1ubuntu1~16.04.5) xenial; urgency=medium

  * Fix builds for 4.13.0-38 kernel (LP: #1756240)
- Update definition of kvm_mmio() to match the new kernel

 -- Khalid Elmously   Thu, 22 Mar 2018
12:08:10 -0400

** Changed in: lttng-modules (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Unable to build lttng-module with Artful kernel

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in lttng-modules source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Invalid
Status in lttng-modules source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lttng-modules source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * The 4.13.0-38 artful kernel included a change (backported from
  4.15) that modifies the definition of kvm_mmio(). This breaks the
  lttng-modules-dkms package because it is using the old (<4.15)
  definition.

   * lttng-modules-dkms already has a list of kernel version
  "exceptions" with which it uses the >=4.15 definition. Proposed
  solution is to add the Ubuntu kernel range 4.13.0-38 up to
  4.14.255-255 to that list of exceptions.

  
  [Test Case]

   * Tested by first successfully building lttng-modules-dkms on
  4.13.0-37, then reproducing the problem described here on 4.13.0-38,
  then applying the code-change and confirming that I can successfully
  build on both 4.13.0-37 and 4.13.0-38 after that.

  [Regression Potential]

   * Low-regression potential. Could prevent lttng-modules-dkms from
  being built for specific kernel versions, but this is unlikely as the
  change was tested to confirm that it works as expected on 4.13.0-37
  and 4.13.0-38 - and should work fine for other Ubuntu kernels as well.




  The lttng module failed to build with the proposed Artful kernel
  (4.13.0-38), it works with 4.13.0-37

  Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 16 04:13 seq
   crw-rw 1 root audio 116, 33 Mar 16 04:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  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:
  CurrentDmesg:

  Date: Fri Mar 16 04:17:14 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-38-generic N/A
   linux-backports-modules-4.13.0-38-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel

This bug was fixed in the package lttng-modules - 2.9.0-1ubuntu3.2

---
lttng-modules (2.9.0-1ubuntu3.2) artful; urgency=medium

  * Fix builds for 4.13.0-38 kernel (LP: #1756240)
- Update definition of kvm_mmio() to match the new kernel

 -- Khalid Elmously   Wed, 21 Mar 2018
19:12:27 -0400

** Changed in: lttng-modules (Ubuntu Artful)
   Status: Fix Committed => 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/1756240

Title:
  Unable to build lttng-module with Artful kernel

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in lttng-modules source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Invalid
Status in lttng-modules source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lttng-modules source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * The 4.13.0-38 artful kernel included a change (backported from
  4.15) that modifies the definition of kvm_mmio(). This breaks the
  lttng-modules-dkms package because it is using the old (<4.15)
  definition.

   * lttng-modules-dkms already has a list of kernel version
  "exceptions" with which it uses the >=4.15 definition. Proposed
  solution is to add the Ubuntu kernel range 4.13.0-38 up to
  4.14.255-255 to that list of exceptions.

  
  [Test Case]

   * Tested by first successfully building lttng-modules-dkms on
  4.13.0-37, then reproducing the problem described here on 4.13.0-38,
  then applying the code-change and confirming that I can successfully
  build on both 4.13.0-37 and 4.13.0-38 after that.

  [Regression Potential]

   * Low-regression potential. Could prevent lttng-modules-dkms from
  being built for specific kernel versions, but this is unlikely as the
  change was tested to confirm that it works as expected on 4.13.0-37
  and 4.13.0-38 - and should work fine for other Ubuntu kernels as well.




  The lttng module failed to build with the proposed Artful kernel
  (4.13.0-38), it works with 4.13.0-37

  Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 16 04:13 seq
   crw-rw 1 root audio 116, 33 Mar 16 04:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  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:
  CurrentDmesg:

  Date: Fri Mar 16 04:17:14 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-38-generic N/A
   linux-backports-modules-4.13.0-38-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1760327] Re: linux: 4.4.0-119.143 -proposed tracker

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.4.0-119.143 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.4.0-119.143 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-02 Thread Carl van Schaik

Affects me on:
Intel(R) Xeon(R) CPU E3-1240 v5 @ 3.50GHz (family: 0x6, model: 0x5e, stepping: 
0x3)

uninstall / disable intel-microcode has restored service on my DL20 G9
server.

Kernel cmdline dis_ucode_ldr worked to allow me to boot and uninstall
the package.

> By any chance, do all of you have sssd installed?
This server has sssd, but unclear if its related.

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 997085] Re: Unable to install Ubuntu 12.04 (neither 32 nor 64 bit)

2018-04-02 Thread Simon Quigley

** No longer affects: 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/997085

Title:
  Unable to install Ubuntu 12.04 (neither 32 nor 64 bit)

Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  1. Launch Ubuntu lice-CD via CD or USB
  2. Select "Install" in menu - gnome screen is shown, mouse works
  3. Wait 20-30 seconds
  Actual result:
  a. mouse moves with huge lags
  b. then it lags disappears, but you can't click any entry
  c. keyboard seems doesn't work too (when I click Num Lock or Caps Lock - 
indicators don't highlight on keyboard)

  NOTE1: if I click any entry on screen before installation window
  appears - it won't appear (please find attached video)

  NOTE2: tried plugging to USB 2.0 and USB 3.0

  NOTE3: tried load optimized defaults in BIOS

  Expected result: keyboard and mouse work correctly, I'm able to
  install Ubuntu

  My PC specs:
  Core i7 2600k, ASUS p8p67 Deluxe, 2x4Gb of Ram (@1866Mhz), Nvidia GTX590, KB: 
logitech media keyboard elite, Mouse: logitech G9

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

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

[Kernel-packages] [Bug 1760073] Re: No network from suspend resume

2018-04-02 Thread TJ

Network issue is either kernel or Network Manager.

After the issue occurs we need to see the current 'dmesg' log (which
will show if devices resumed successfully) and /var/log/syslog (where
Network Manager is very verbose).

We also need to know which devices the system has:

lspci -nnk
lsusb

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

Title:
  No network from suspend resume

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following a resume from suspend - no network available on machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:53:22 2018
  InstallationDate: Installed on 2018-03-08 (21 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-08 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-08 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-08 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1760261] Re: log in to GUI in U-MATE daily 18.04 fails

2018-04-02 Thread Fritz Hudnut

@ Joseph S:

So I downloaded the daily from the Ubuntu-MATE daily, as that is the
package I have been working with and having the problem with, so the
4/2/18 daily and burned it to DVD as previously, install runs well, no
errors or crashes . . . but this time I tried the old recommendation to
shut down after install, rather than just reboot . . . GRUB window loads
fine . . . but, the problem remains--entering password in the GUI log in
window . . . goes to various forms of black . . . and then back into the
log in window.  Previous to the install I booted the live session and it
loaded the system just fine and I fiddled with a few apps, set the time
. . . all that more or less went well, I tried to launch "Appearance"
and that did crash, and I tried again and it opened--but the crash
reporter opened and I added my name to a previous bug . . . and then I
tried the fresh install after that.

As part of the back story, I "zsync'd" the daily and zsync showed the
previous file was "94.3% complete" . . . so after the daily was zsync'd
I thought I would just try to update/upgrade the prior installation to
see if the log in problem was fixed . . . going that way by using the
TTY . . . and that didn't fix the problem, so I went to fresh install.

Also, following a recommend from the U-MATE forum I tried to reboot into
Recovery . . . and in selecting "enable networking" . . . a menu like
list of tasks started . . . ending with "reached target swap" and then
it returned to a blinking cursor for several minutes . . . when I ctrl
C'd out of it the rest of the ?? dmesg??  hardware items ran through,
but the recovery menu did not load again to try to run "dpkg" . . . so
it appears things still aren't correct in Recovery??

Again, after the install I rebooted several times, logged into a TTY
session, ran update/upgrade, there were "21 packages" to install . . .
it seemed to "get" 4 of them, but then other packages were seemingly
"unpacked" . . . packages that were nabbed in recovery?? but not
"installed" . . . it's still a bit odd.  In the TTY I ran "ls -l
/home/username" . . . and as before it shows the directories and files
that are in the /home filesystem . . . so the TTY is letting me log in
upgrade/update . . . the /home filesystem is "found" but the GUI is not
letting me log in.

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

Title:
  log in to GUI in U-MATE daily 18.04 fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tried two installs on a daily of U-MATE 18.04 burned to DVD, and each
  time the install seemed to go well, no errors reported, no crash
  reports filed . . . on reboot, grub loads and the MATE log in window
  opens, typing the password brings a black screen for a few seconds,
  and then back to the log in window.

  Tried to install another DE to test whether that would work and that
  also failed.  Ran "dpkg" in the recovery system . . . found some
  updates but couldn't seem to download them; back into TTY and ran
  update/upgrade . . . showed 75 packages, which it installed . . .
  didn't fix the failure to log in problem.  Did an "ls -l
  /home/username" . . . and it showed the /home contents of the
  directory as being there, but the system is not logging into the GUI.

  F

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

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

[Kernel-packages] [Bug 1760108] Re: Broadcom B43 Wireless Driver Not Functional after Update to Linux Kernel 4.15

In addition if I had 'something' blacklisting the module I would find
very strange that it would not do so with Kernel 4.13 ... While doing it
on Kernel 4.15, this is not plausible.

Right now in Kernel 4.13 I have:

$ modprobe --show-depends pci:v14E4d4331sv14E4sd4331bc02sc80i00
insmod /lib/modules/4.13.0-38-generic/kernel/net/wireless/cfg80211.ko 
insmod /lib/modules/4.13.0-38-generic/updates/dkms/wl.ko 
$

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

Title:
  Broadcom B43 Wireless Driver Not Functional after Update to Linux
  Kernel 4.15

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

Bug description:
  I was upgrading my Ubuntu Xenial 16.04 from linux-hwe kernel 4.13.0-38
  to linux-hwe-edge 4.15.0-13.

  After reboot my Broadcom network adapter (requiring package
  firmware-b43-installer) is not recognized by the new kernel 4.15.0-13.

  Running the lspci command lists the device as 'UNCLAIMED' in linux
  kernel 4.15.

  $ lspci
  [...]
  *-pci:4
   description: PCI bridge
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 1c
   bus info: pci@:00:1c.0
   version: f0
   width: 32 bits
   clock: 33MHz
   capabilities: pci pciexpress msi pm normal_decode bus_master 
cap_list
   configuration: driver=pcieport
   resources: irq:123 memory:ef50-ef5f
     *-network UNCLAIMED
  description: Network controller
  product: BCM4331 802.11a/b/g/n
  vendor: Broadcom Corporation
  physical id: 0
  bus info: pci@:05:00.0
  version: 02
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress cap_list
  configuration: latency=0
  resources: memory:ef50-ef503fff
  [...]
  $

  The lspci -vv -pci:4 commands with the relevant devices are shown
  below.

  $ lspci -vv -pci:4
  [...]
  05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 
02)
   Subsystem: Apple Inc. AirPort Extreme
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
    Address:   Data: 
   Capabilities: [d0] Express (v1) Endpoint, MSI 00
    DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
     ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
     RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 
<4us, L1 <64us
     ClockPM+ Surprise- LLActRep+ BwNot- ASPMOptComp-
    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
     ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ 
BWMgmt- ABWMgmt-
   Capabilities: [100 v1] Advanced Error Reporting
    UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ 
MalfTLP+ ECRC- UnsupReq- ACSViol-
    CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
    CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
    AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
   Capabilities: [13c v1] Virtual Channel
    Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
    Arb:Fixed- WRR32- WRR64- WRR128-
    Ctrl:   ArbSelect=Fixed
    Status: InProgress-
    VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
     Arb:   Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
     Ctrl:  Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
     Status:NegoPending- InProgress-
   Capabilities: [160 v1] Device Serial Number c6-d6-51-ff-ff-e6-f4-f9
   Capabilities: [16c v1] Power Budgeting 
   Kernel modules: bcma
  [...]
  $

  The circumstances of this bug is well described on this webpage:

  https://bbs.archlinux.org/viewtopic.php?id=234122

  Furthermore a patch has been provided upstream:
  [UPDATE]: This patch is already part of the used kernel version.
Hence this bug is not related to this patch.

  https://patchwork.kernel.org/patch/10185397/

[Kernel-packages] [Bug 1760108] Re: Broadcom B43 Wireless Driver Not Functional after Update to Linux Kernel 4.15

I believe I did install the complete set of packages:

linux-generic-hwe-16.04-edge_4.15.0.13.39_amd64.deb
linux-headers-4.15.0-13_4.15.0-13.14~16.04.1_all.deb
linux-headers-4.15.0-13-generic_4.15.0-13.14~16.04.1_amd64.deb
linux-headers-generic-hwe-16.04-edge_4.15.0.13.39_amd64.deb
linux-image-4.15.0-13-generic_4.15.0-13.14~16.04.1_amd64.deb
linux-image-extra-4.15.0-13-generic_4.15.0-13.14~16.04.1_amd64.deb
linux-image-generic-hwe-16.04-edge_4.15.0.13.39_amd64.deb
linux-signed-generic-hwe-16.04-edge_4.15.0.13.39_amd64.deb
linux-signed-image-4.15.0-13-generic_4.15.0-13.14~16.04.1_amd64.deb
linux-signed-image-generic-hwe-16.04-edge_4.15.0.13.39_amd64.deb

However right now I did remove this non functional kernel.
I will re-install soon to check for your request.

I have another question If I test Kernel 4.16 what set of packages
should I install from the webpage provided ?

linux-headers-4.16.0-041600_4.16.0-041600.201804012230_all.deb
linux-headers-4.16.0-041600-generic_4.16.0-041600.201804012230_amd64.deb
linux-image-4.16.0-041600-generic_4.16.0-041600.201804012230_amd64.deb

I miss a linux-image-extra is it ok though ?

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

Title:
  Broadcom B43 Wireless Driver Not Functional after Update to Linux
  Kernel 4.15

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

Bug description:
  I was upgrading my Ubuntu Xenial 16.04 from linux-hwe kernel 4.13.0-38
  to linux-hwe-edge 4.15.0-13.

  After reboot my Broadcom network adapter (requiring package
  firmware-b43-installer) is not recognized by the new kernel 4.15.0-13.

  Running the lspci command lists the device as 'UNCLAIMED' in linux
  kernel 4.15.

  $ lspci
  [...]
  *-pci:4
   description: PCI bridge
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 1c
   bus info: pci@:00:1c.0
   version: f0
   width: 32 bits
   clock: 33MHz
   capabilities: pci pciexpress msi pm normal_decode bus_master 
cap_list
   configuration: driver=pcieport
   resources: irq:123 memory:ef50-ef5f
     *-network UNCLAIMED
  description: Network controller
  product: BCM4331 802.11a/b/g/n
  vendor: Broadcom Corporation
  physical id: 0
  bus info: pci@:05:00.0
  version: 02
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress cap_list
  configuration: latency=0
  resources: memory:ef50-ef503fff
  [...]
  $

  The lspci -vv -pci:4 commands with the relevant devices are shown
  below.

  $ lspci -vv -pci:4
  [...]
  05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 
02)
   Subsystem: Apple Inc. AirPort Extreme
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
    Address:   Data: 
   Capabilities: [d0] Express (v1) Endpoint, MSI 00
    DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
     ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
     RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 
<4us, L1 <64us
     ClockPM+ Surprise- LLActRep+ BwNot- ASPMOptComp-
    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
     ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ 
BWMgmt- ABWMgmt-
   Capabilities: [100 v1] Advanced Error Reporting
    UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ 
MalfTLP+ ECRC- UnsupReq- ACSViol-
    CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
    CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
    AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
   Capabilities: [13c v1] Virtual Channel
    Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
    Arb:Fixed- WRR32- WRR64- WRR128-
    Ctrl:   ArbSelect=Fixed
    Status: InProgress-
    VC0:Caps:

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

2018-04-02 Thread bugproxy

--- Comment From lagar...@br.ibm.com 2018-04-02 19:22 EDT---
The patches that make it possible to use HTM in guests running on POWER9 
processors are now in the PowerPC kernel maintainer tree and will be requested 
to get merged into kernel 4.17:

681c617b7c42 KVM: PPC: Book3S HV: Work around TEXASR bug in fake suspend state
87a11bb6a7f7 KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode
4bb3c7a0208f KVM: PPC: Book3S HV: Work around transactional memory bugs in 
POWER9
7672691a08c8 powerpc/powernv: Provide a way to force a core into SMT4 mode
b5af4f279323 powerpc: Add CPU feature bits for TM bug workarounds on POWER9 v2.2
9bbf0b576d32 powerpc: Free up CPU feature bits on 64-bit machines
dd0efb3f11cc powerpc: Book E: Remove unused CPU_FTR_L2CSR bit
c0d64cf9fefd powerpc: Use feature bit for RTC presence rather than timebase 
presence

Fom Paul Mackerras: for a backport, we can probably avoid the feature
bit rework, I hope, and just find two free CPU feature bits. If there
aren't 2 free feature bits then let me know, we might be able to
scavenge some that are only used on Book E or something.

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

Title:
  Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default
  machine type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails

[Kernel-packages] [Bug 1749685] Re: Kernel panic on ThunderX

Since this appears to be a hardware issue, I'll mark Invalid. fyi, we're
working with the vendor to figure out next steps for lundmark.

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

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

Title:
  Kernel panic on ThunderX

Status in linux package in Ubuntu:
  Invalid

Bug description:
  While doing testing on lundmark, i observed (from time to time) panics
  on 4.13.0-32.35~16.04.1-generic - i got this one while deploying the
  board:

  Booting under MAAS direction... [ grub.cfg-40:8d:5c:ba  606B  100%  1.56KiB/s 
]
  EFI stub: Booting Linux Kernel...[ boot-initrd  46.78MiB  100%  6.57MiB/s 
]
  EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services and installing virtual address map...
  [0.00] Booting Linux on physical CPU 0x0
  [0.00] random: get_random_bytes called from start_kernel+0x50/0x460 
with crng_init=0
  [0.00] Linux version 4.13.0-32-generic (buildd@bos01-arm64-018) (gcc 
version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.5)) #35~16.04.1-
  Ubuntu SMP Thu Jan 25 10:10:26 UTC 2018 (Ubuntu 4.13.0-32.35~16.04.1-generic 
4.13.13)
  [0.00] Boot CPU: AArch64 Processor [431f0a11]
  [0.00] Machine model: cavium,thunder-88xx
  [0.00] efi: Getting EFI parameters from FDT:
  [0.00] efi: EFI v2.40 by American Megatrends
  [0.00] efi:  ESRT=0x1ffce5ac18  SMBIOS 3.0=0x1ffce5a918  ACPI 
2.0=0x1ffeb46000 
  [0.00] esrt: Reserving ESRT space from 0x001ffce5ac18 to 
0x001ffce5ac50.
  [0.00] NUMA: NODE_DATA [mem 0x1fff0c4d00-0x1fff0c7fff]
  [0.00] Zone ranges:
  [0.00]   DMA  [mem 0x0050-0x]
  [0.00]   Normal   [mem 0x0001-0x001fff0f]
  [0.00] Movable zone start for each node
  [0.00] Early memory node ranges
  ...
  [0.00] Kernel command line: 
BOOT_IMAGE=ubuntu/arm64/hwe-16.04/xenial/daily/boot-kernel nomodeset 
root=squash:http://10.229.32.21:5248/images/ubu
  ntu/arm64/hwe-16.04/xenial/daily/squashfs ro ip=lundmark:BOOTIF ip6=off 
overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}e
  nd_cc 
cloud-config-url=http://10.229.32.21:5240/MAAS/metadata/latest/by-id/ttctk4/?op=get_preseed
 apparmor=0 log_host=10.229.32.21 log_port=514 BOOTIF=0
  1-40:8d:5c:ba:cd:d4
  ...
  [9.058541] Synchronous External Abort: synchronous parity or ECC error 
(0x8618) at 0x9658fc9c
  [9.058545] Internal error: : 8618 [#1] SMP
  [9.058548] Modules linked in: ast(+) i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect aes_ce_blk sysimgblt aes_ce_cipher fb_sys_fops crc32_ce
   crct10dif_ce drm ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx(+) 
i2c_thunderx(+) thunder_xcv i2c_smbus ipmi_ssif mdio_thunder thunderx_mmc 
mdio_ca
  vium ipmi_devintf ipmi_msghandler aes_neon_bs aes_neon_blk crypto_simd cryptd
  [9.058588] CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.13.0-32-generic 
#35~16.04.1-Ubuntu
  [9.058589] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [9.058591] task: 801f700c6900 task.stack: 801f700cc000
  [9.058600] PC is at __remove_hrtimer+0x48/0xa8
  [9.058602] LR is at __remove_hrtimer+0x5c/0xa8
  [9.058604] pc : [] lr : [] pstate: 
004001c5
  [9.058606] sp : 801f79787e60
  [9.058607] x29: 801f79787e60 x28: 801f700c6900 
  [9.058611] x27: 00021bc7a0ca x26: 08fcd000 
  [9.058614] x25: 0001 x24: 08fcd000 
  [9.058617] x23: 093b9658 x22: 801f7978f598 
  [9.058620] x21: 801f7978f5c0 x20: 801f7978f580 
  [9.058624] x19: 801f7978fa00 x18: c8e8cb78 
  [9.058627] x17: 668a x16:  
  [9.058630] x15: 968adcc0 x14: 343030302c333030 
  [9.058633] x13: 302c323030302c31 x12: 3030302c30303030 
  [9.058636] x11: c635fa10 x10: 0b00 
  [9.058639] x9 : 0040 x8 : 801f780026f0 
  [9.058643] x7 :  x6 : 801f7978fa00 
  [9.058646] x5 :  x4 : 801f7978fb58 
  [9.058649] x3 : 801f7978fb58 x2 : 801f7978fb58 
  [9.058652] x1 : 801f7978f5d0 x0 : 0001 
  [9.058656] Process swapper/7 (pid: 0, stack limit = 0x801f700cc000)
  [9.058658] Stack: (0x801f79787e60 to 0x801f700d)
  [9.058660] Call trace:
  [9.058662] Exception stack(0x801f79787c70 to 0x801f79787da0)
  [9.058665] 7c60:   801f7978fa00 
0001
  [9.058668] 7c80: 0242d000 08153d88 004001c5 
801f79787d38
  [9.058671]

[Kernel-packages] [Bug 1428075] Re: [12.04.2] Realtek r8169 driver is unstable (link up / link down)

2018-04-02 Thread victor00000

L~$ readlink /in*g
/boot/initrd.img-3.13.0-117-generic
L~$

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

Title:
  [12.04.2] Realtek r8169 driver is unstable (link up / link down)

Status in linux package in Ubuntu:
  Expired

Bug description:
  My Realtek RTL8111/8168/8411 card is very unstable:
  - led only goes on  30 seconds after pluggin in the cable
  - it takes even longer until I can ping the interface; often it does not 
become possible at all

  dmesg show the link is brought up and down again and again.

  [ 1490.791721] usb 2-3: ep 0x81 - rounding interval to 64 microframes, ep 
desc says 80 micro$
  [ 1490.793653] input: Logitech USB Optical Mouse as 
/devices/pci:00/:00:14.0/usb2/2-$
  [ 1490.793817] hid-generic 0003:046D:C05A.001B: input,hidraw0: USB HID v1.11 
Mouse [Logitech$
  [ 1493.001767] r8169 :02:00.0 p5p1: link down
  [ 1506.635177] r8169 :02:00.0 p5p1: link up
  [ 1513.960191] r8169 :02:00.0 p5p1: link down
  [ 1532.077450] r8169 :02:00.0 p5p1: link up
  [ 1532.433100] r8169 :02:00.0 p5p1: link down
  [ 1550.846755] usb 2-3: USB disconnect, device number 27
  [ 1550.883189] r8169 :02:00.0 p5p1: link up

  There is more often problem with the linux driver:
  
https://www.google.nl/search?q=r8169%20%20%22link%20up%22%20%22link%20down%22=j
  ; same bug applies to Oneiric 11.10 (#839393) and was closed (Won't
  fix) because it is no longer supported. It is not fixed, despite the
  suggestion that the 3.1/3.2 kernel would improve the situation.

  As 14.04.2 is LTS, I hereby report it again.

  version: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  see also dmesg.log and lspci-vnvn.log

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

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

[Kernel-packages] [Bug 1759445] Re: kernel panic when trying to reboot in bionic

It's possible that the message is related, but it would be difficult to
track down without shortening the number of commits to search through
between 4.4 and 4.15.

It sounds like you can't reproduce this error with Artful and 4.13 based
kernels.  Is that correct?

If so, it would be worth testing the 4.14 final kernel and possibly some
of the 4.15 release candidates if 4.14. is good.  All the kernels are
available from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/

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

Title:
  kernel panic when trying to reboot in bionic

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

Bug description:
  cpe_foundation test deployment of Bionic failed.
  After some investigation, it looks like the nodes deployed and installed 
bionic, but never came back from a reboot.

  Accessing the ILO console of a node in question (all nodes failed), it
  revealed a kernel panic (attached)

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

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

[Kernel-packages] [Bug 1428075] Re: [12.04.2] Realtek r8169 driver is unstable (link up / link down)

2018-04-02 Thread victor00000

my error - No such file or ... (/lib/firmware/rtl_nic/rtl8411-2.fw)

L~$ 
L~$ apt-file search /rtl8411-2.fw
linux-image-3.11.0-26-generic: 
/lib/firmware/3.11.0-26-generic/rtl_nic/rtl8411-2.fw
L~$ 
L~$ readlink /in*g/boot/initrd.img-3.13.0-117-generic
L~$ 
L~$ 
:(

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

Title:
  [12.04.2] Realtek r8169 driver is unstable (link up / link down)

Status in linux package in Ubuntu:
  Expired

Bug description:
  My Realtek RTL8111/8168/8411 card is very unstable:
  - led only goes on  30 seconds after pluggin in the cable
  - it takes even longer until I can ping the interface; often it does not 
become possible at all

  dmesg show the link is brought up and down again and again.

  [ 1490.791721] usb 2-3: ep 0x81 - rounding interval to 64 microframes, ep 
desc says 80 micro$
  [ 1490.793653] input: Logitech USB Optical Mouse as 
/devices/pci:00/:00:14.0/usb2/2-$
  [ 1490.793817] hid-generic 0003:046D:C05A.001B: input,hidraw0: USB HID v1.11 
Mouse [Logitech$
  [ 1493.001767] r8169 :02:00.0 p5p1: link down
  [ 1506.635177] r8169 :02:00.0 p5p1: link up
  [ 1513.960191] r8169 :02:00.0 p5p1: link down
  [ 1532.077450] r8169 :02:00.0 p5p1: link up
  [ 1532.433100] r8169 :02:00.0 p5p1: link down
  [ 1550.846755] usb 2-3: USB disconnect, device number 27
  [ 1550.883189] r8169 :02:00.0 p5p1: link up

  There is more often problem with the linux driver:
  
https://www.google.nl/search?q=r8169%20%20%22link%20up%22%20%22link%20down%22=j
  ; same bug applies to Oneiric 11.10 (#839393) and was closed (Won't
  fix) because it is no longer supported. It is not fixed, despite the
  suggestion that the 3.1/3.2 kernel would improve the situation.

  As 14.04.2 is LTS, I hereby report it again.

  version: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  see also dmesg.log and lspci-vnvn.log

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

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2018-04-02 Thread Tyler Hicks

@Breno ack, I'll look at bringing them in, as well.

Do you want these changes (both patch sets) in 18.04 only or are you
asking for them to be in 17.10, 16.04, and 14.04, as well?

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2018-04-02 Thread Breno Leitão

Hey Tyler,

I thought these patches were in already, so, let's bring them also.

Backporting without these fixes might not be easy to accomplish, and
nothing something we want to keep for the whole 18.04 life. Let's try to
be as near as possible to upstream and bring the required patches in.

Thanks for asking,
Breno

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1627905] Re: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.

2018-04-02 Thread Ryan

This bug is old and Lenovo fixed the issue upstream with a corrected
BIOS that users can optionally install, which enables AHCI mode.

Also, from my understanding, Linux installs even in the default
configuration now, including on the more recent Yoga 910 and 920 models
thanks to some patches from Intel that went into the upstream Linux
kernel.

Unless anyone objects, I think this should be closed as fixed upstream.

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

Title:
  Ubuntu can't be installed to certain Lenovo Yoga laptops because the
  fakeraid storage mode is not supported.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Several Lenovo Yoga laptops do not allow the user to install any
  current Linux distributions due to being BIOS-locked to a RAID mode
  and Linux does not support this. You can boot a Linux live
  environment, but when you go to install, it will not see the Solid
  State Drive and it does not appear as a PCI device.

  The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for
  Business, and probably the new Yoga Book and Yoga 910 as well.

  Lenovo has stated that removing the AHCI option from the BIOS is a
  feature and that they don't plan to fix this.

  There have been some blog postings and news articles about this issue
  lately.

  Here is the Lenovo Forums topic:

  https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS-
  update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false

  (Note that this says it is solved, but it is not. Lenovo replied that
  they won't fix it and that Linux is not supported on these laptops.)

  Matthew Garrett's blog post is here:
  https://mjg59.dreamwidth.org/44694.html

  I approached him with the idea that perhaps the Linux kernel could be
  modified to reset the hardware and put it into AHCI mode after GRUB
  loads the kernel (according to him, GRUB doesn't need to be modified
  because it uses the uEFI firmware's disk access), and then Linux could
  proceed to boot.

  Here's what he said:

  "If you wanted to try that, the best place to do it would be the UEFI
  setup code in the kernel under arch/x86/boot/compressed/eboot.c - that
  way you can do it independent of bootloader. Grub's able to read files
  anyway since it's using the firmware calls to do that.

  The power management thing isn't about the SSD itself, it's about
  ensuring that the controller is programmed correctly so that the
  entire CPU package can enter deep sleep states. Modern systems should
  idle at around 4W at most, so small amounts make abig difference
  here."

  [...]

  "If the firmware hasn't locked the control bit and if the hardware is
  ok with suddenly being reconfigured, sure, that ought to work. Doing
  it in eboot.c means you're doing it before any PCI enumeration has
  occurred, which makes it more likely that things will work out well."

  [...]

  "I'll take a quick look at the 10-series chipset docs to see if it's
  documented, and if so I'll throw a quick patch together - but I'm
  probably not going to try pushing it upstream, I'm afraid. If it does
  work, I'm fine with anybody else doing so."

  
  I heaven't heard anything back lately, so I am putting this in a bug report 
so that the Ubuntu maintainers are aware of the issue.

  It seems like a few lines of kernel code are all that is really required to 
fix this and restore the ability of Linux distributions to be installed on half 
a dozen laptops (probably more to come, since Lenovo says that the industry is 
moving to this!).
  --- 
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ryan   1604 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 5986:068c Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80UE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-22-generic x86_64
  UpgradeStatus: No upgrade log

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-02 Thread Gordon Lack

>> And adding 'noibpb' kernel boot parameter helps, at least in my case.

However, according to:
   
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown/MitigationControls
doing that, 
"Disabling these features removes mitigations for CVE-2017-5715 (aka Spectre / 
Variant 2).", which sort-of defeats what the microcode fix is for.

However, the rest of the thread for Bug #1746418 does explain why my
18.04beta system is OK - it's running 4.15.0-xxx

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5715

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1598312] Re: Cannot scale AMD Turion CPU frequency. It runs on lowest 800MHz

2018-04-02 Thread Vladimir Marko

Upstream:
Linux 4.14: BAD
Linux 4.16: GOOD

I did not bisect to find out which CL fixed 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/1598312

Title:
  Cannot scale AMD Turion CPU frequency. It runs on lowest 800MHz

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed

Bug description:
  http://askubuntu.com/questions/789096/cant-scale-frequencies-of-amd-
  turion-cpu-it-always-jumps-to-lowest

  The CPU does not scale frequency on kernel "4.2.0-41-generic
  #48~14.04.1-Ubuntu SMP Fri Jun 24 17:09:15". The notebook behaves very
  slow despite on Windows Vista it works great.

  Cpufreq-info program shows that there is a limit on the frequency setting 
between 800MHz and 800MHz. I tried to impose the frequency by setting the 
"performance policy" or by setting the limit in /etc/default/cpufrequency, but 
it does not work. 
  Next I tried to check the BIOS limits, because there are some suggestions 
that some battery/power supply problems could cause the BIOS to set the limits 
on CPU freq but it is not there.

  The CPU freq scaling works good on 'linux-image-4.1.26-040126-generic'
  kernel. It does not work on this kernel "4.2.0-41-generic" and "linux-
  headers-4.2.0-38-generic". The current workaround is to switch off the
  ACPI by "acpi=off" boot parameter. Using this setting the CPU
  frequency scaling works but it makes the system single CPU core only.

  Hardware: HP Compaq 6715B notebook with AMD Turion CPU TL-58 and
  powernow-k8 cpufreq driver. I've heard some posts that on others HP
  notebooks there are similar problems with the freq scaling.

  
  $ cpufreq-info 
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 109 us.
hardware limits: 800 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 1.80 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.90 GHz:0,07%, 1.80 GHz:0,00%, 1.60 GHz:0,00%, 800 
MHz:99,93%  (1)
  analyzing CPU 1:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 109 us.
hardware limits: 800 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 1.80 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.90 GHz:0,07%, 1.80 GHz:0,00%, 1.60 GHz:0,00%, 800 
MHz:99,93%  (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-41-generic 4.2.0-41.48~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  Uname: Linux 4.2.0-41-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jul  1 23:49:34 2016
  InstallationDate: Installed on 2016-04-08 (83 days ago)
  InstallationMedia: Kubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2018-04-02 Thread Tyler Hicks

@Breno the changes in this patch set touch some of the same areas of
code:

  http://patchwork.ozlabs.org/project/linuxppc-
dev/list/?series=33861=*

  [v3,5/5] rfi-flush: Call setup_rfi_flush() after LPM migration
  [v3,4/5] rfi-flush: Differentiate enabled and patched flush types
  [v3,3/5] rfi-flush: Always enable fallback flush on pseries
  [v3,2/5] rfi-flush: Make it possible to call setup_rfi_flush() again
  [v3,1/5] rfi-flush: Move the logic to avoid a redo into the debugfs code

Should we backport around those changes or are they also required?

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1760712] [NEW] perf vendor events arm64: Enable JSON events for ThunderX2 B0

Public bug reported:

[Impact]
We enabled ThunderX2 vendor events in LP: #1747523. That was sufficient for A2 
silicon, but needs an update to recognize B0 silicon.

[Test Case]
Successful output on ThunderX2 B0 silicon:
$ sudo perf list | grep thunderx2
thunderx2 imp def:
$

[Regression Risk]
This teaches existing code about a new SoC, which should mitigate regressions 
for all other platforms.

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

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

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

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

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

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

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

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

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

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

Title:
  perf vendor events arm64: Enable JSON events for ThunderX2 B0

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

Bug description:
  [Impact]
  We enabled ThunderX2 vendor events in LP: #1747523. That was sufficient for 
A2 silicon, but needs an update to recognize B0 silicon.

  [Test Case]
  Successful output on ThunderX2 B0 silicon:
  $ sudo perf list | grep thunderx2
  thunderx2 imp def:
  $

  [Regression Risk]
  This teaches existing code about a new SoC, which should mitigate regressions 
for all other platforms.

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

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

[Kernel-packages] [Bug 1747523] Re: support thunderx2 vendor pmu events

Ignore comment #4 - was meant for a different 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/1747523

Title:
  support thunderx2 vendor pmu events

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

Bug description:
  [Impact]
  ThunderX2 vendor pmu events are not supported.

  [Test Case]
  Successful output:
  $ sudo perf list | grep thunderx2
  thunderx2 imp def:
  $

  [Regression Risk]
  The code changes are restricted to the perf utility, so there's negligible 
risk to the kernel itself. All patches are clean cherry-picks except 1 where a 
hunk is dropped that was updating an API in code that didn't exist yet.

  I've tested on Cavium Sabre (a thunderx2 system), and smoke tested
  perf commands for regression on x86 (Dell XPS13 9350).

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

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

[Kernel-packages] [Bug 1747523] Re: support thunderx2 vendor pmu events

public bug 1760712

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

Title:
  support thunderx2 vendor pmu events

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

Bug description:
  [Impact]
  ThunderX2 vendor pmu events are not supported.

  [Test Case]
  Successful output:
  $ sudo perf list | grep thunderx2
  thunderx2 imp def:
  $

  [Regression Risk]
  The code changes are restricted to the perf utility, so there's negligible 
risk to the kernel itself. All patches are clean cherry-picks except 1 where a 
hunk is dropped that was updating an API in code that didn't exist yet.

  I've tested on Cavium Sabre (a thunderx2 system), and smoke tested
  perf commands for regression on x86 (Dell XPS13 9350).

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

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Artful)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

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

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

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1760108] Re: Broadcom B43 Wireless Driver Not Functional after Update to Linux Kernel 4.15

2018-04-02 Thread Seth Forshee

The pci ids for your device should be handled by the bcma module, but
that module is not loaded. Can you confirm that you have the
corresponding linux-image-extra package installed? If so, please run:

  modprobe --show-depends
pci:v14E4d4331sv14E4sd4331bc02sc80i00

and provide the output. Also check that nothing in /etc/modprobe.d is
blacklisting the module.

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

Title:
  Broadcom B43 Wireless Driver Not Functional after Update to Linux
  Kernel 4.15

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

Bug description:
  I was upgrading my Ubuntu Xenial 16.04 from linux-hwe kernel 4.13.0-38
  to linux-hwe-edge 4.15.0-13.

  After reboot my Broadcom network adapter (requiring package
  firmware-b43-installer) is not recognized by the new kernel 4.15.0-13.

  Running the lspci command lists the device as 'UNCLAIMED' in linux
  kernel 4.15.

  $ lspci
  [...]
  *-pci:4
   description: PCI bridge
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 1c
   bus info: pci@:00:1c.0
   version: f0
   width: 32 bits
   clock: 33MHz
   capabilities: pci pciexpress msi pm normal_decode bus_master 
cap_list
   configuration: driver=pcieport
   resources: irq:123 memory:ef50-ef5f
     *-network UNCLAIMED
  description: Network controller
  product: BCM4331 802.11a/b/g/n
  vendor: Broadcom Corporation
  physical id: 0
  bus info: pci@:05:00.0
  version: 02
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress cap_list
  configuration: latency=0
  resources: memory:ef50-ef503fff
  [...]
  $

  The lspci -vv -pci:4 commands with the relevant devices are shown
  below.

  $ lspci -vv -pci:4
  [...]
  05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 
02)
   Subsystem: Apple Inc. AirPort Extreme
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
    Address:   Data: 
   Capabilities: [d0] Express (v1) Endpoint, MSI 00
    DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
     ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
     RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 
<4us, L1 <64us
     ClockPM+ Surprise- LLActRep+ BwNot- ASPMOptComp-
    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
     ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ 
BWMgmt- ABWMgmt-
   Capabilities: [100 v1] Advanced Error Reporting
    UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ 
MalfTLP+ ECRC- UnsupReq- ACSViol-
    CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
    CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
    AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
   Capabilities: [13c v1] Virtual Channel
    Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
    Arb:Fixed- WRR32- WRR64- WRR128-
    Ctrl:   ArbSelect=Fixed
    Status: InProgress-
    VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
     Arb:   Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
     Ctrl:  Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
     Status:NegoPending- InProgress-
   Capabilities: [160 v1] Device Serial Number c6-d6-51-ff-ff-e6-f4-f9
   Capabilities: [16c v1] Power Budgeting 
   Kernel modules: bcma
  [...]
  $

  The circumstances of this bug is well described on this webpage:

  https://bbs.archlinux.org/viewtopic.php?id=234122

  Furthermore a patch has been provided upstream:
  [UPDATE]: This patch is already part of the used kernel version.
Hence this bug is not related to this patch.

[Kernel-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

2018-04-02 Thread Mario Limonciello

** Summary changed:

- Enable configuring resume offset via sysfs
+ FFe: Enable configuring resume offset via sysfs

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

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

[Kernel-packages] [Bug 1760680] Re: linux-aws: -proposed tracker

** 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-master-bug: 1760678
+ kernel-phase-changed:Monday, 02. April 2018 20:31 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1760678
- kernel-phase-changed:Monday, 02. April 2018 20:31 UTC
- kernel-phase:Packaging
+ phase: Packaging

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws 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-master-bug: 1760678
  phase: Packaging

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

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

[Kernel-packages] [Bug 1760678] Re: linux: 4.15.0-14.15 -proposed tracker

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

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

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

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

** Tags added: block-proposed-bionic

** 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
  
  backports: bug 1760684 (linux-hwe-edge)
  derivatives: bug 1760679 (linux-raspi2), bug 1760680 (linux-aws), bug 1760681 
(linux-azure), bug 1760682 (linux-gcp), bug 1760683 (linux-kvm)
+ kernel-phase-changed:Monday, 02. April 2018 20:31 UTC
+ kernel-phase:Uploaded

** 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 1760684 (linux-hwe-edge)
  derivatives: bug 1760679 (linux-raspi2), bug 1760680 (linux-aws), bug 1760681 
(linux-azure), bug 1760682 (linux-gcp), bug 1760683 (linux-kvm)
  kernel-phase-changed:Monday, 02. April 2018 20:31 UTC
  kernel-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.15.0-14.15 -proposed tracker

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

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

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

  backports: bug 1760684 (linux-hwe-edge)
  derivatives: bug 1760679 (linux-raspi2), bug 1760680 (linux-aws), bug 1760681 
(linux-azure), bug 1760682 (linux-gcp), bug 1760683 (linux-kvm)
  kernel-phase-changed:Monday, 02. April 2018 20:31 UTC
  kernel-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1760683] Re: linux-kvm: -proposed tracker

** 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-master-bug: 1760678
+ kernel-phase-changed:Monday, 02. April 2018 20:32 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1760678
- kernel-phase-changed:Monday, 02. April 2018 20:32 UTC
- kernel-phase:Packaging
+ phase: Packaging

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm 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-master-bug: 1760678
  phase: Packaging

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

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

** Changed in: linux (Ubuntu Xenial)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Artful)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1760127] Re: BCM2045B: Integrated Bluetooth adapter needs to be enabled twice to work on ThinkPad T400

2018-04-02 Thread Dimitar Milkov

The 3.13 kernel in Trusty was not affected by this. I have tested all the 
kernels since 4.4 and they are affected.
I can confirm that the bug is fixed in the 4.15 and 4.16 kernels.

** Tags added: kernel-fixed-upstream

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

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

Title:
  BCM2045B: Integrated Bluetooth adapter needs to be enabled twice to
  work on ThinkPad T400

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug has been around since the 4.x kernels.

  When the system boots up, Bluetooth is disabled as expected:

  $ rfkill list
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  2: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no

  After we try to enable it with 'rfkill unblock bluetooth', the
  Bluetooth interface hci0 is now present, but is soft blocked:

  $ rfkill unblock bluetooth

  $ rfkill list
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  2: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: noDescription:Linux Mint 18.3 Sylvia
  Release:  18.3

Hard blocked: no
  10: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

  However, Bluetooth is considered enabled by the thinkpad-acpi driver,
  as we can see:

  $ cat /proc/acpi/ibm/bluetooth
  status:   enabled
  commands: enable, disable

  The Bluetooth LED is also on.

  'hciconfig' is seeing the Bluetooth adapter as being DOWN:

  $ hciconfig

  hci0: Type: BR/EDR  Bus: USB
BD Address: 00:22:68:E4:BF:27  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN 
RX bytes:511 acl:0 sco:0 events:23 errors:0
TX bytes:339 acl:0 sco:0 commands:23 errors:0

  To remove the soft block of hci0 and make the Bluetooth adapter fully
  operational, we should run 'rfkill unblock bluetooth' one more time.

  $ rfkill unblock bluetooth

  $ rfkill list
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  2: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
  10: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

  $ hciconfig

  hci0: Type: BR/EDR  Bus: USB
BD Address: 00:22:68:E4:BF:27  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1046 acl:0 sco:0 events:50 errors:0
TX bytes:943 acl:0 sco:0 commands:50 errors:0

  Now the adapter is fully operational.

  This behavior confuses most of the GUI applets that are used by the
  modern distributions, since they expect to have an operational adapter
  after the first attempt to enable it. This makes it impossible to use
  the Bluetooth adapter through them.

  I`m currently testing on Linux Mint 18.3 MATE (with Ubuntu package
  base) that is shipped with the 'blueberry' applet, it uses bt-adapter
  from the BlueZ suite in the background to manage the Bluetooth
  adapter. Because of this bug, it crashes and 'blueberry' is unable to
  use the Bluetooth.

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

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

[Kernel-packages] [Bug 1760461] Re: BUG: unable to handle kernel paging request at ffffdc73f60aba40

Also trying to see if I can get the updated kernel into a live usb
environment so I can test that without corruption from any local
configured setup.

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

Title:
  BUG: unable to handle kernel paging request at dc73f60aba40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Autogenerated bug - might be dupe of 1759865 and 1759947

  QEMU hung. Couldn't close window. kill -9'd the processes, but window
  remained. xkill'd the window, but zombie remained - owned by systemd-
  pam.

  Apport tried to report it, but hung machine in the process.

  As a side note, the requested `sudo lspci -vnvn > lspci-vnvn.log` also says:
  pcilib: sysfs_read_vpd: read failed: Input/output error

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Sun Apr  1 10:02:32 2018
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: kmem_cache_alloc_trace+0x85/0x1b0 RSP: aaaf27b33bc0
  Failure: oops
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off iommu=pt ---
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at dc73f60aba40
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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/1760461/+subscriptions

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

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

2018-04-02 Thread Ubuntu Foundations Team Bug Bot

The attachment "debdiff for Xenial qemu" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  ubuntu-kvm-unit test failed with emulator test on ppc64le

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New

Bug description:
  Similar to bug 1723904, bug 1712803.
  The failed "emulator" test from kvm-unit-test will pass with qemu-2.7.1 built 
from source.

  ubuntu@modoc:~/kvm-unit-tests$ sudo /bin/bash -c "TESTNAME=emulator 
TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1
  > "
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults 
-machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial 
stdio -kernel powerpc/emulator.elf -smp 1 # -initrd /tmp/tmp.BJ2sE7V2Jc
  FAIL: emulator: 64bit: detected
  PASS: emulator: invalid: exception
  PASS: emulator: lswx: alignment
  PASS: emulator: lswi: alignment
  SUMMARY: 4 tests, 1 unexpected failures

  EXIT: STATUS=3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
  ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: ppc64el
  Date: Mon Oct 16 10:10:46 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.00 0.00 0.57 1/1457 83356
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1604 00:14:19651 0 EOF
   2: POSIX  ADVISORY  WRITE 2937 00:14:55331 0 EOF
   3: FLOCK  ADVISORY  WRITE 3046 00:14:67623 0 EOF
   4: POSIX  ADVISORY  WRITE 3124 00:14:57398 0 EOF
   5: POSIX  ADVISORY  WRITE 3047 00:14:87068 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.10.0-37-generic (buildd@bos01-ppc64el-026) (gcc 
version 5.4.0 20160609 (User Name/IBM 5.4.0-6ubuntu1~16.04.4) ) 
#41~16.04.1-User Name SMP Fri Oct 6 22:44:24 UTC 2017
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT is off

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

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

[Kernel-packages] [Bug 1760461] Re: BUG: unable to handle kernel paging request at ffffdc73f60aba40

I did a fresh install on new hardware on 3/26.  Been trying to get it
stable since (which meant a lot of apt updates and dpkg --configure).  I
tried to install kernel 4.16.0-041600rc7 this weekend, but it needs me
to disable nvidia,etc so still trying to get that to 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/1760461

Title:
  BUG: unable to handle kernel paging request at dc73f60aba40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Autogenerated bug - might be dupe of 1759865 and 1759947

  QEMU hung. Couldn't close window. kill -9'd the processes, but window
  remained. xkill'd the window, but zombie remained - owned by systemd-
  pam.

  Apport tried to report it, but hung machine in the process.

  As a side note, the requested `sudo lspci -vnvn > lspci-vnvn.log` also says:
  pcilib: sysfs_read_vpd: read failed: Input/output error

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Sun Apr  1 10:02:32 2018
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: kmem_cache_alloc_trace+0x85/0x1b0 RSP: aaaf27b33bc0
  Failure: oops
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off iommu=pt ---
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at dc73f60aba40
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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/1760461/+subscriptions

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2018-04-02 Thread Frank Heimes

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: Triaged

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

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1759445] Re: kernel panic when trying to reboot in bionic

2018-04-02 Thread Jason Hobbs

So far we've only been able to produce this by doing bionic deploys.

One thing that stands out in the rsyslog for bionic deploys is this
failure:

http://paste.ubuntu.com/p/y8xXc7PYjp/

Apr  2 17:48:35 leafeon blkdeactivate[1782]: /sbin/blkdeactivate: line
345: /bin/sort: No such file or directory

Could it be related?

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

Title:
  kernel panic when trying to reboot in bionic

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

Bug description:
  cpe_foundation test deployment of Bionic failed.
  After some investigation, it looks like the nodes deployed and installed 
bionic, but never came back from a reboot.

  Accessing the ILO console of a node in question (all nodes failed), it
  revealed a kernel panic (attached)

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

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

[Kernel-packages] [Bug 1760152] Re: nfp: request backport of ethtool flashing

I built a test kernel with commits 7a7415659144 and 87a23801e502.  The test 
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1760152

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

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

Title:
  nfp: request backport of ethtool flashing

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

Bug description:
  
  Backport recently upstreamed changes to the nfp driver to allow flash updates 
to be written to Netronome SmartNICs using ethtool.

  f.e.
  # ethtool -f netdev_name flash-nic.bin

  This feature is not currently present in the Bionic kernel and the above 
command results in the following error:
  Error return + "Flashing failed: Operation not supported\n"

  This feature is implemented by the following upstream commits.

  7a7415659144 ("nfp: implement firmware flashing")
  87a23801e502 ("nfp: extend NSP infrastructure for configurable timeouts")

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

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

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

2018-04-02 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 1751990

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1760377] Re: Ubuntu 17.10 freezes on login with kernel 4.13.0-37-generic

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

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

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

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

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

** This bug has been marked a duplicate of bug 1759920
   intel-microcode 3.20180312.0 causes lockup at login screen(w/ 
linux-image-4.13.0-37-generic)

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

Title:
  Ubuntu 17.10 freezes on login with kernel 4.13.0-37-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I updated kernel to 4.13.0-37-generic, and after reboot, it freezes on
  the kde login screen. Even sysrq keys does not work. I rebooted again,
  and be able to enter password, then it freezes again on plasma loading
  screen. I finally selected 4.13.0-36-generic kernel from grub, and my
  computer booted normally. I guess there was a kernel panic, but it
  didn't show on screen, nor in system logs, or I cannot find it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Apr  1 11:14:39 2018
  DistUpgraded: 2017-10-02 23:05:26,340 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: kubuntu
  DpkgLog:
   
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: QUANTA Computer Inc 2nd Generation Core Processor Family 
Integrated Graphics Controller [152d:0875]
   NVIDIA Corporation GF106M [GeForce GT 555M] [10de:0dce] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: QUANTA Computer Inc GF106M [GeForce GT 555M] [152d:0875]
  InstallationDate: Installed on 2012-12-20 (1927 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Hasee QTH6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=5e2d0528-b52e-4165-9c44-c18ef0338b43 ro quiet splash video=VGA-2:d
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-02 (180 days ago)
  dmi.bios.date: 12/16/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: SU272
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: HM65
  dmi.board.vendor: Hasee
  dmi.board.version: TBD
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hasee
  dmi.chassis.version: US
  dmi.modalias: 
dmi:bvnINSYDE:bvrSU272:bd12/16/2011:svnHasee:pnQTH6:pvr03:rvnHasee:rnHM65:rvrTBD:cvnHasee:ct10:cvrUS:
  dmi.product.family: Intel_Mobile
  dmi.product.name: QTH6
  dmi.product.version: 03
  dmi.sys.vendor: Hasee
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Apr  1 11:07:30 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

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

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

[Kernel-packages] [Bug 1760273] Re: kernel: (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info()

Do you happen to know if this bug also exists in Bionic?

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

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

Title:
  kernel: (NULL device *): hwmon_device_register() is deprecated. Please
  convert the driver to use hwmon_device_register_with_info()

Status in linux package in Ubuntu:
  Triaged
Status in lm-sensors package in Ubuntu:
  New

Bug description:
  That error is logged since a while with all the supported kernels.
  Please apply the patch on them:

  https://github.com/torvalds/linux/blob/master/drivers/hwmon/hwmon.c

  To get a maintained version of lm-sensors:
  https://github.com/groeck/lm-sensors

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsensors4 1:3.4.0-4
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar 31 10:42:25 2018
  Dependencies:
   gcc-7-base 7.2.0-8ubuntu3.2
   libc6 2.26-0ubuntu2.1
   libgcc1 1:7.2.0-8ubuntu3.2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lm-sensors
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1760461] Re: BUG: unable to handle kernel paging request at ffffdc73f60aba40

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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

Thanks in advance.

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

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

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

Title:
BUG: unable to handle kernel paging request at dc73f60aba40

Status in linux package in Ubuntu:
Incomplete

Bug description:
Autogenerated bug - might be dupe of 1759865 and 1759947

QEMU hung. Couldn't close window. kill -9'd the processes, but window
remained. xkill'd the window, but zombie remained - owned by systemd-
pam.

Apport tried to report it, but hung machine in the process.

As a side note, the requested `sudo lspci -vnvn > lspci-vnvn.log` also says:
pcilib: sysfs_read_vpd: read failed: Input/output error

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Annotation: Your system might become unstable now and might need to be
restarted.
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Sun Apr 1 10:02:32 2018
DuplicateSignature: BUG: unable to handle kernel paging request at location
RIP: kmem_cache_alloc_trace+0x85/0x1b0 RSP: aaaf27b33bc0
Failure: oops
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed
root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off iommu=pt ---
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at dc73f60aba40
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0902
dmi.board.asset.tag: Default string
dmi.board.name: ROG ZENITH EXTREME
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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/1760461/+subscriptions

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

[Kernel-packages] [Bug 1760379] Re: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [colord-sane:11175]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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


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

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

Title:
  watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [colord-sane:11175]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  machine successfully kept ssh connect open to a 2nd machine over
  night.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2951 F pulseaudio
dietmar5359 F pulseaudio
   /dev/snd/controlC0:  gdm2951 F pulseaudio
dietmar5359 F pulseaudio
  Date: Sun Apr  1 00:48:23 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=6cc53691-8a2d-45f2-a78c-e5126db414aa
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=bdd1754a-b8b4-4d5c-bdad-2275569c1c25 ro plymouth:debug drm.debug=0xe
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [colord-sane:11175]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88X-D3HP
  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.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP: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/1760379/+subscriptions

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

[Kernel-packages] [Bug 1760375] Re: cgroup blkio throttle does not work on root group

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

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

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

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


Thanks in advance.

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


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

** Tags added: kernel-da-key xenial

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

Title:
  cgroup blkio throttle does not work on root group

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  from kernel document, 
https://www.kernel.org/doc/Documentation/cgroup-v1/blkio-controller.txt
  ```
  Throttling/Upper Limit policy
  -
  - Enable Block IO controller
CONFIG_BLK_CGROUP=y

  - Enable throttling in block layer
CONFIG_BLK_DEV_THROTTLING=y

  - Mount blkio controller (see cgroups.txt, Why are cgroups needed?)
  mount -t cgroup -o blkio none /sys/fs/cgroup/blkio

  - Specify a bandwidth rate on particular device for root group. The format
for policy is ":  ".

  echo "8:16  1048576" >
  /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device

Above will put a limit of 1MB/second on reads happening for root group
on device having major/minor number 8:16.

  - Run dd to read a file and see if rate is throttled to 1MB/s or not.

  # dd iflag=direct if=/mnt/common/zerofile of=/dev/null bs=4K 
count=1024
  1024+0 records in
  1024+0 records out
  4194304 bytes (4.2 MB) copied, 4.0001 s, 1.0 MB/s

   Limits for writes can be put using blkio.throttle.write_bps_device file.
  ```

  tested with ubuntu 16.04(xenial) and seems throttle not working, but
  on my virtual machine, ubuntu 14.04(trusty) works.

  ```
  ubuntu16.04(xenial)

  root@i-x3mn8m8i:~# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  vda 253:0 0 20G 0 disk
  `-vda1 253:1 0 20G 0 part /
  vdb 253:16 0 1G 0 disk [SWAP]
  root@i-x3mn8m8i:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C16246+0 records in
  16246+0 records out
  66543616 bytes (67 MB, 63 MiB) copied, 3.15081 s, 21.1 MB/s

  root@i-x3mn8m8i:~# echo 253:0 1000 > 
/sys/fs/cgroup/blkio/blkio.throttle.write_iops_device
  root@i-x3mn8m8i:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C26702+0 records in
  26702+0 records out
  109371392 bytes (109 MB, 104 MiB) copied, 5.2413 s, 20.9 MB/s

  ubuntu14.04(trusty)

  root@i-ulhx27oo:~# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  vda 253:0 0 20G 0 disk
  `-vda1 253:1 0 20G 0 part /
  vdb 253:16 0 1G 0 disk [SWAP]

  root@i-ulhx27oo:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C27679+0 records in
  27679+0 records out
  113373184 bytes (113 MB) copied, 5.43766 s, 20.8 MB/s

  root@i-ulhx27oo:~# echo 253:0 1000 > 
/sys/fs/cgroup/blkio/blkio.throttle.write_iops_device
  root@i-ulhx27oo:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C7553+0 records in
  7553+0 records out
  30937088 bytes (31 MB) copied, 7.60268 s, 4.1 MB/s
  ```

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

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

[Kernel-packages] [Bug 1760284] Re: Regression, system unresponsible few seconds after showing gdm3, Sysrq doesn't work

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

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

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

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


Thanks in advance.

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


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

** Tags added: needs-bisect

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

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

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

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

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

Title:
  Regression, system unresponsible  few seconds after showing gdm3,
  Sysrq doesn't work

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

Bug description:
  After upgrading from ubuntu 17.04 to 17.10 with new kernel
  4.13.0-37-generic system stopped to work few seconds after showing
  display manager(a while after WiFi changes icon to connected). This
  his hard crash, SysRq command doesn't work. This is not an issue on
  the same environment with old kernel 4.10.0-43-generic booted

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.10.0-43.47-generic 4.10.17
  Uname: Linux 4.10.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nusch  3173 F pulseaudio
   /dev/snd/controlC0:  nusch  3173 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 12:17:44 2018
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2015-05-08 (1058 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-43-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash 
log_buf_len=1M crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-43-generic N/A
   linux-backports-modules-4.10.0-43-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-03-31 (0 days ago)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  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.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1760638] Re: dccp test in ubuntu_stress_smoke_test failed with 4.4/4.15 KVM kernel

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Triaged

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

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

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

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

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

** Tags added: kernel-da-key

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

Title:
  dccp test in ubuntu_stress_smoke_test failed with 4.4/4.15 KVM kernel

Status in linux package in Ubuntu:
  Triaged
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in linux-kvm source package in Xenial:
  New
Status in linux source package in Bionic:
  Triaged
Status in linux-kvm source package in Bionic:
  New

Bug description:
  The test failed with:
  16:26:24 DEBUG| [stdout] dccp STARTING
  16:26:24 DEBUG| [stdout] dccp RETURNED 2
  16:26:24 DEBUG| [stdout] dccp FAILED
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] 2 processors online, 2 
processors configured
  16:26:24 DEBUG| [stdout] stress-ng: info:  [2228] dispatching hogs: 4 dccp
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] cache allocate: reducing 
cache level from L3 (too high) to L2
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] cache allocate: default 
cache size: 4096K
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] starting stressors
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] 4 stressors spawned
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: started 
[2231] (instance 2)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: started 
[2232] (instance 3)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: started 
[2229] (instance 0)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: started 
[2230] (instance 1)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: process 
[2231] using socket port 10002
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: process 
[2229] using socket port 1
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: process 
[2232] using socket port 10003
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: process 
[2230] using socket port 10001
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: socket 
failed, errno=94 (Socket type not supported)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: 0 messages 
sent
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: exited 
[2231] (instance 2)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2239] stress-ng-dccp: socket 
failed, errno=94 (Socket type not supported)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: socket 
failed, errno=94 (Socket type not supported)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: 0 messages 
sent
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: exited 
[2230] (instance 1)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: socket 
failed, errno=94 (Socket type not supported)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: 0 messages 
sent
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: exited 
[2232] (instance 3)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2235] stress-ng-dccp: socket 
failed, errno=94 (Socket type not supported)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: socket 
failed, errno=94 (Socket type not supported)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: 0 messages 
sent
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: exited 
[2229] (instance 0)
  16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2229 
(stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core 
failure)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2229] terminated
  16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2230 
(stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core 
failure)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2230] terminated
  16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2231 
(stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core 
failure)
  16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2231] terminated
  16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2232 
(stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core 
failure)
  16:26:24

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

2018-04-02 Thread Murilo Opsfelder Araújo

** Patch added: "debdiff for Xenial qemu"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723914/+attachment/5099155/+files/debdiff_qemu_xenial.patch

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

Title:
  ubuntu-kvm-unit test failed with emulator test on ppc64le

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New

Bug description:
  Similar to bug 1723904, bug 1712803.
  The failed "emulator" test from kvm-unit-test will pass with qemu-2.7.1 built 
from source.

  ubuntu@modoc:~/kvm-unit-tests$ sudo /bin/bash -c "TESTNAME=emulator 
TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1
  > "
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults 
-machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial 
stdio -kernel powerpc/emulator.elf -smp 1 # -initrd /tmp/tmp.BJ2sE7V2Jc
  FAIL: emulator: 64bit: detected
  PASS: emulator: invalid: exception
  PASS: emulator: lswx: alignment
  PASS: emulator: lswi: alignment
  SUMMARY: 4 tests, 1 unexpected failures

  EXIT: STATUS=3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
  ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: ppc64el
  Date: Mon Oct 16 10:10:46 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.00 0.00 0.57 1/1457 83356
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1604 00:14:19651 0 EOF
   2: POSIX  ADVISORY  WRITE 2937 00:14:55331 0 EOF
   3: FLOCK  ADVISORY  WRITE 3046 00:14:67623 0 EOF
   4: POSIX  ADVISORY  WRITE 3124 00:14:57398 0 EOF
   5: POSIX  ADVISORY  WRITE 3047 00:14:87068 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.10.0-37-generic (buildd@bos01-ppc64el-026) (gcc 
version 5.4.0 20160609 (User Name/IBM 5.4.0-6ubuntu1~16.04.4) ) 
#41~16.04.1-User Name SMP Fri Oct 6 22:44:24 UTC 2017
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT is off

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

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

[Kernel-packages] [Bug 1760539] Re: QCA9377 WIFI does not work full speed

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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


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

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

Title:
  QCA9377 WIFI does not work full speed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 18.04, development branch, and I have 
  QCA9377 802.11ac Wireless Network Adapter

  When I connect it to WiFi hotspot in 2.4G mode I will get only 1MBps, and 
  When I connect it to WiFi hotspot in   5G mode I will get only 6MBps.

  I think an updated firmware is needed.

  Running:
  Ubuntu 4.15.0-13.14-generic 4.15.10

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

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

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

2018-04-02 Thread Murilo Opsfelder Araújo

Manoj, Christian,

Please refer to the attached debdiff (it was my first debdiff, so it
might contain errors :)).

Let me know if you need anything else.

Cheers
Murilo

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

Title:
  ubuntu-kvm-unit test failed with emulator test on ppc64le

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New

Bug description:
  Similar to bug 1723904, bug 1712803.
  The failed "emulator" test from kvm-unit-test will pass with qemu-2.7.1 built 
from source.

  ubuntu@modoc:~/kvm-unit-tests$ sudo /bin/bash -c "TESTNAME=emulator 
TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1
  > "
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults 
-machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial 
stdio -kernel powerpc/emulator.elf -smp 1 # -initrd /tmp/tmp.BJ2sE7V2Jc
  FAIL: emulator: 64bit: detected
  PASS: emulator: invalid: exception
  PASS: emulator: lswx: alignment
  PASS: emulator: lswi: alignment
  SUMMARY: 4 tests, 1 unexpected failures

  EXIT: STATUS=3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
  ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: ppc64el
  Date: Mon Oct 16 10:10:46 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.00 0.00 0.57 1/1457 83356
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1604 00:14:19651 0 EOF
   2: POSIX  ADVISORY  WRITE 2937 00:14:55331 0 EOF
   3: FLOCK  ADVISORY  WRITE 3046 00:14:67623 0 EOF
   4: POSIX  ADVISORY  WRITE 3124 00:14:57398 0 EOF
   5: POSIX  ADVISORY  WRITE 3047 00:14:87068 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.10.0-37-generic (buildd@bos01-ppc64el-026) (gcc 
version 5.4.0 20160609 (User Name/IBM 5.4.0-6ubuntu1~16.04.4) ) 
#41~16.04.1-User Name SMP Fri Oct 6 22:44:24 UTC 2017
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT is off

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

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

[Kernel-packages] [Bug 1759947] Re: BUG: unable to handle kernel paging request at 0000200000000020

This has been happening since fresh install on new hardware.
Tried to do 4.16.0-041600rc7 this weekend, but couldn't get it to install. 
Trying to figure out how to determine what all has to be uninstalled for it to 
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/1759947

Title:
  BUG: unable to handle kernel paging request at 2020

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Unclear what happened.  It said chrome was dying, but then nothing
  including mouse and keyboard worked.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Thu Mar 29 13:56:40 2018
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: find_get_entry+0x42/0x110 RSP: b73c51c3fbe8
  Failure: oops
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 2020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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/1759947/+subscriptions

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

** Tags added: pti

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

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

** Tags added: kernel-da-key

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1760163] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038

I was trying to test out the upstream kernel this weekend.  One of the
steps is to disable 3rd party libraries (like nvidia).  Is there any way
to identify all the libraries that have to be disabled?  Or better yet -
any way to install the kernel into a live usb image?

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0038

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Chrome hung. Then the rest of the machine hung.

  Might be related to the other bugs recently auto-reported.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Fri Mar 30 09:09:52 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: hide_cursor+0x25/0x90 RSP: af9647f0fbc8
  Failure: oops
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off iommu=pt ---
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0038
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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/1760163/+subscriptions

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

[Kernel-packages] [Bug 1760152] Re: nfp: request backport of ethtool flashing

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Triaged

** Tags added: 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/1760152

Title:
  nfp: request backport of ethtool flashing

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

Bug description:
  
  Backport recently upstreamed changes to the nfp driver to allow flash updates 
to be written to Netronome SmartNICs using ethtool.

  f.e.
  # ethtool -f netdev_name flash-nic.bin

  This feature is not currently present in the Bionic kernel and the above 
command results in the following error:
  Error return + "Flashing failed: Operation not supported\n"

  This feature is implemented by the following upstream commits.

  7a7415659144 ("nfp: implement firmware flashing")
  87a23801e502 ("nfp: extend NSP infrastructure for configurable timeouts")

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

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

[Kernel-packages] [Bug 1747890] Re: Update the source code location in the debian package for cloud kernels

This bug was fixed in the package linux-azure-edge - 4.15.0-1005.5

---
linux-azure-edge (4.15.0-1005.5) xenial; urgency=medium

  * linux-azure-edge: 4.15.0-1005.5 -proposed tracker (LP: #1759923)

  * [Hyper-V] hv_netvsc: enable multicast if necessary (LP: #1759885)
- hv_netvsc: fix filter flags
- SAUCE: hv_netvsc: enable multicast if necessary

linux-azure-edge (4.15.0-1004.4) xenial; urgency=medium

  * linux-azure-edge: 4.15.0-1004.4 -proposed tracker (LP: #1759673)

  * [Hyper-V][linux-azure] Change config for MLX4 and MLX5 (LP: #1759656)
- [Config] azure: CONFIG_MLX{4,5}_INFINIBAND=y

  * [Hyper-V] Improvements for UDP on SRIOV (LP: #1756414)
- SAUCE: hv_netvsc: avoid retry on send during shutdown
- SAUCE: hv_netvsc: only wake transmit queue if link is up
- SAUCE: hv_netvsc: fix error unwind handling if vmbus_open fails
- SAUCE: hv_netvsc: cancel subchannel setup before halting device
- SAUCE: hv_netvsc: fix race in napi poll when rescheduling
- SAUCE: hv_netvsc: use napi_schedule_irqoff
- SAUCE: hv_netvsc: defer queue selection to VF
- SAUCE: hv_netvsc: filter multicast/broadcast
- SAUCE: hv_netvsc: propagate rx filters to VF

  * [Hyper-V] PCI: hv: Fix 2 hang issues in hv_compose_msi_msg (LP: #1758378)
- SAUCE: PCI: hv: Serialize the present and eject work items
- SAUCE: PCI: hv: Fix 2 hang issues in hv_compose_msi_msg()
- SAUCE: PCI: hv: Fix a comment typo in _hv_pcifront_read_config()
- SAUCE: PCI: hv: Remove the bogus test in hv_eject_device_work()
- SAUCE: PCI: hv: Only queue new work items in hv_pci_devices_present() if
  necessary

linux-azure-edge (4.15.0-1003.3) xenial; urgency=medium

  * linux-azure-edge: 4.15.0-1003.3 -proposed tracker (LP: #1755769)

  * linux-azure: 4.15.0-1003.3 -proposed tracker (LP: #1757167)

  * Enable secure boot on linux-azure (LP: #1754042)
- Revert "UBUNTU: [debian] azure: do not build uefi signed binary"

  * [Hyper-v] Set CONFIG_I2C_PIIX4 to "n" (LP: #1752999)
- [Config] azure: CONFIG_I2C_PIIX4=n

  * [Hyper-V] set config: CONFIG_EDAC_DECODE_MCE=y (LP: #1751123)
- [Config] azure: CONFIG_EDAC_DECODE_MCE=y

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after rebase to Ubuntu-4.15.0-13.14
- [Config] fix up retpoline abi files

  [ Ubuntu: 4.15.0-13.14 ]

  * linux: 4.15.0-13.14 -proposed tracker (LP: #1756408)
  * devpts: handle bind-mounts (LP: #1755857)
- SAUCE: devpts: hoist out check for DEVPTS_SUPER_MAGIC
- SAUCE: devpts: resolve devpts bind-mounts
- SAUCE: devpts: comment devpts_mntget()
- SAUCE: selftests: add devpts selftests
  * [bionic][arm64] d-i: add hisi_sas_v3_hw to scsi-modules (LP: #1756103)
- d-i: add hisi_sas_v3_hw to scsi-modules
  * [Bionic][ARM64] enable ROCE and HNS3 driver support for hip08 SoC
(LP: #1756097)
- RDMA/hns: Refactor eq code for hip06
- RDMA/hns: Add eq support of hip08
- RDMA/hns: Add detailed comments for mb() call
- RDMA/hns: Add rq inline data support for hip08 RoCE
- RDMA/hns: Update the usage of sr_max and rr_max field
- RDMA/hns: Set access flags of hip08 RoCE
- RDMA/hns: Filter for zero length of sge in hip08 kernel mode
- RDMA/hns: Fix QP state judgement before sending work requests
- RDMA/hns: Assign dest_qp when deregistering mr
- RDMA/hns: Fix endian problems around imm_data and rkey
- RDMA/hns: Assign the correct value for tx_cqn
- RDMA/hns: Create gsi qp in hip08
- RDMA/hns: Add gsi qp support for modifying qp in hip08
- RDMA/hns: Fill sq wqe context of ud type in hip08
- RDMA/hns: Assign zero for pkey_index of wc in hip08
- RDMA/hns: Update the verbs of polling for completion
- RDMA/hns: Set the guid for hip08 RoCE device
- net: hns3: Refactor of the reset interrupt handling logic
- net: hns3: Add reset service task for handling reset requests
- net: hns3: Refactors the requested reset & pending reset handling code
- net: hns3: Add HNS3 VF IMP(Integrated Management Proc) cmd interface
- net: hns3: Add mailbox support to VF driver
- net: hns3: Add HNS3 VF HCL(Hardware Compatibility Layer) Support
- net: hns3: Add HNS3 VF driver to kernel build framework
- net: hns3: Unified HNS3 {VF|PF} Ethernet Driver for hip08 SoC
- net: hns3: Add mailbox support to PF driver
- net: hns3: Change PF to add ring-vect binding & resetQ to mailbox
- net: hns3: Add mailbox interrupt handling to PF driver
- net: hns3: add support to query tqps number
- net: hns3: add support to modify tqps number
- net: hns3: change the returned tqp number by ethtool -x
- net: hns3: free the ring_data structrue when change tqps
- net: hns3: get rss_size_max from configuration but not hardcode
- net: hns3: add a mask initialization for mac_vlan table
- net: hns3: add vlan offload config command
- net: hns3: add ethtool related offload command
- net: hns3: add

[Kernel-packages] [Bug 1747890] Re: Update the source code location in the debian package for cloud kernels

This bug was fixed in the package linux-azure-edge - 4.15.0-1005.5

---
linux-azure-edge (4.15.0-1005.5) xenial; urgency=medium

  * linux-azure-edge: 4.15.0-1005.5 -proposed tracker (LP: #1759923)

  * [Hyper-V] hv_netvsc: enable multicast if necessary (LP: #1759885)
- hv_netvsc: fix filter flags
- SAUCE: hv_netvsc: enable multicast if necessary

linux-azure-edge (4.15.0-1004.4) xenial; urgency=medium

  * linux-azure-edge: 4.15.0-1004.4 -proposed tracker (LP: #1759673)

  * [Hyper-V][linux-azure] Change config for MLX4 and MLX5 (LP: #1759656)
- [Config] azure: CONFIG_MLX{4,5}_INFINIBAND=y

  * [Hyper-V] Improvements for UDP on SRIOV (LP: #1756414)
- SAUCE: hv_netvsc: avoid retry on send during shutdown
- SAUCE: hv_netvsc: only wake transmit queue if link is up
- SAUCE: hv_netvsc: fix error unwind handling if vmbus_open fails
- SAUCE: hv_netvsc: cancel subchannel setup before halting device
- SAUCE: hv_netvsc: fix race in napi poll when rescheduling
- SAUCE: hv_netvsc: use napi_schedule_irqoff
- SAUCE: hv_netvsc: defer queue selection to VF
- SAUCE: hv_netvsc: filter multicast/broadcast
- SAUCE: hv_netvsc: propagate rx filters to VF

  * [Hyper-V] PCI: hv: Fix 2 hang issues in hv_compose_msi_msg (LP: #1758378)
- SAUCE: PCI: hv: Serialize the present and eject work items
- SAUCE: PCI: hv: Fix 2 hang issues in hv_compose_msi_msg()
- SAUCE: PCI: hv: Fix a comment typo in _hv_pcifront_read_config()
- SAUCE: PCI: hv: Remove the bogus test in hv_eject_device_work()
- SAUCE: PCI: hv: Only queue new work items in hv_pci_devices_present() if
  necessary

linux-azure-edge (4.15.0-1003.3) xenial; urgency=medium

  * linux-azure-edge: 4.15.0-1003.3 -proposed tracker (LP: #1755769)

  * linux-azure: 4.15.0-1003.3 -proposed tracker (LP: #1757167)

  * Enable secure boot on linux-azure (LP: #1754042)
- Revert "UBUNTU: [debian] azure: do not build uefi signed binary"

  * [Hyper-v] Set CONFIG_I2C_PIIX4 to "n" (LP: #1752999)
- [Config] azure: CONFIG_I2C_PIIX4=n

  * [Hyper-V] set config: CONFIG_EDAC_DECODE_MCE=y (LP: #1751123)
- [Config] azure: CONFIG_EDAC_DECODE_MCE=y

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after rebase to Ubuntu-4.15.0-13.14
- [Config] fix up retpoline abi files

  [ Ubuntu: 4.15.0-13.14 ]

  * linux: 4.15.0-13.14 -proposed tracker (LP: #1756408)
  * devpts: handle bind-mounts (LP: #1755857)
- SAUCE: devpts: hoist out check for DEVPTS_SUPER_MAGIC
- SAUCE: devpts: resolve devpts bind-mounts
- SAUCE: devpts: comment devpts_mntget()
- SAUCE: selftests: add devpts selftests
  * [bionic][arm64] d-i: add hisi_sas_v3_hw to scsi-modules (LP: #1756103)
- d-i: add hisi_sas_v3_hw to scsi-modules
  * [Bionic][ARM64] enable ROCE and HNS3 driver support for hip08 SoC
(LP: #1756097)
- RDMA/hns: Refactor eq code for hip06
- RDMA/hns: Add eq support of hip08
- RDMA/hns: Add detailed comments for mb() call
- RDMA/hns: Add rq inline data support for hip08 RoCE
- RDMA/hns: Update the usage of sr_max and rr_max field
- RDMA/hns: Set access flags of hip08 RoCE
- RDMA/hns: Filter for zero length of sge in hip08 kernel mode
- RDMA/hns: Fix QP state judgement before sending work requests
- RDMA/hns: Assign dest_qp when deregistering mr
- RDMA/hns: Fix endian problems around imm_data and rkey
- RDMA/hns: Assign the correct value for tx_cqn
- RDMA/hns: Create gsi qp in hip08
- RDMA/hns: Add gsi qp support for modifying qp in hip08
- RDMA/hns: Fill sq wqe context of ud type in hip08
- RDMA/hns: Assign zero for pkey_index of wc in hip08
- RDMA/hns: Update the verbs of polling for completion
- RDMA/hns: Set the guid for hip08 RoCE device
- net: hns3: Refactor of the reset interrupt handling logic
- net: hns3: Add reset service task for handling reset requests
- net: hns3: Refactors the requested reset & pending reset handling code
- net: hns3: Add HNS3 VF IMP(Integrated Management Proc) cmd interface
- net: hns3: Add mailbox support to VF driver
- net: hns3: Add HNS3 VF HCL(Hardware Compatibility Layer) Support
- net: hns3: Add HNS3 VF driver to kernel build framework
- net: hns3: Unified HNS3 {VF|PF} Ethernet Driver for hip08 SoC
- net: hns3: Add mailbox support to PF driver
- net: hns3: Change PF to add ring-vect binding & resetQ to mailbox
- net: hns3: Add mailbox interrupt handling to PF driver
- net: hns3: add support to query tqps number
- net: hns3: add support to modify tqps number
- net: hns3: change the returned tqp number by ethtool -x
- net: hns3: free the ring_data structrue when change tqps
- net: hns3: get rss_size_max from configuration but not hardcode
- net: hns3: add a mask initialization for mac_vlan table
- net: hns3: add vlan offload config command
- net: hns3: add ethtool related offload command
- net: hns3: add

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

Just curious if you had a chance to test the kernel posted in #77?

I compared the configs between these two kernels:
v4.12-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3/
v4.12-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc4/

Nothing sticks out as a fix in v4.12-rc4.  I'll attach a screen shot of
the diffs.

We could try reverse bisecting with the Ubuntu kernels instead of
mainline kernels.


** Attachment added: "ConfigDiffs-rc3-rc4.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5099154/+files/ConfigDiffs-rc3-rc4.png

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

Title:
  [i40e] LACP bonding start up race conditions

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1760110] Re: Kernel 4.15.0-13.14 reboots instead of powering off (when on battery) on HP Spectre x360 ae-000x

2018-04-02 Thread Dmitry Malykhanov

The system was originally installed using a snapshot ISO which had
kernel 4.15.0-10. And everything was working great, system was powering
off as expected. I still keep this kernel installed and actually use it
daily. So everything was working fine with 4.15.0-10.11.

I have not tried the 4.16 release yet (will do soon), but
4.16.0-041600rc7 was sort of similar. The 4.15.0-12 and 4.15.0-13 just
do not power off (and instead reboot the machine) 100% of the time. With
4.16rc7 it was more like 50/50 (could not figure out the pattern yet).
Will try the 4.16 release and report back.

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

Title:
  Kernel 4.15.0-13.14 reboots instead of powering off (when on battery)
  on HP Spectre x360 ae-000x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This might be a duplicate of #1756455

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-13 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot instead of turning hardware off. 4.15.0-12 has the same problem
  (see #1756455). Booting with kernel 4.15.0-10 resolves the issue,
  system turns off power and stays powered off.

  * secure boot enabled or disabled makes no difference

  * kernel 4.15.0-10 correctly powers off system (halt -p) every time,
  power source makes no difference

  * kernel 4.15.0-13 correctly powers off system only when running on AC

  * kernel 4.15.0-13 does NOT power off system (reboots instead) when AC
  power is NOT connected (running on battery) every time

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1648 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Mar 30 14:39:28 2018
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (20 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1759997] Re: intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1759920
   intel-microcode 3.20180312.0 causes lockup at login screen(w/ 
linux-image-4.13.0-37-generic)

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

Title:
  intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  I have Lenovo P50 with E3-1505M. After intel-microcode
  3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time
  after graphic display interface - exact time of hang differs from boot
  to boot. Rolling intel-microcode back to 3.20170707.1 fixes the
  problem.

  This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic 
kernels.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kolya  2039 F pulseaudio
   /dev/snd/controlC1:  kolya  2039 F pulseaudio
   /dev/snd/pcmC0D0p:   kolya  2039 F...m pulseaudio
   /dev/snd/controlC0:  kolya  2039 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6
  InstallationDate: Installed on 2016-02-20 (768 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20EN001SUS
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago)
  UserGroups: dialout kismet libvirt sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET73W (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001SUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1760684 (linux-hwe-edge)
+ derivatives: bug 1760679 (linux-raspi2), bug 1760680 (linux-aws), bug 1760681 
(linux-azure), bug 1760682 (linux-gcp), bug 1760683 (linux-kvm)

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.15.0-14.15 -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) => Thadeu Lima de 
Souza Cascardo (cascardo)

** 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) => Thadeu Lima de 
Souza Cascardo (cascardo)

** 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) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  linux: 4.15.0-14.15 -proposed tracker

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

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

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

  backports: bug 1760684 (linux-hwe-edge)
  derivatives: bug 1760679 (linux-raspi2), bug 1760680 (linux-aws), bug 1760681 
(linux-azure), bug 1760682 (linux-gcp), bug 1760683 (linux-kvm)

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

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

[Kernel-packages] [Bug 1760678] [NEW] linux: 4.15.0-14.15 -proposed tracker

Public bug reported:

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

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

backports: bug 1760684 (linux-hwe-edge)
derivatives: bug 1760679 (linux-raspi2), bug 1760680 (linux-aws), bug 1760681 
(linux-azure), bug 1760682 (linux-gcp), bug 1760683 (linux-kvm)

** 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/prepare-package
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: Confirmed

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


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.02-1 kernel-sru-master-kernel

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

** Also affects: kernel-sru-workflow/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-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-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/prepare-package
   Importance: Undecided => Medium

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

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

** Tags added: kernel-sru-cycle-2018.04.02-1

** Tags added: kernel-sru-master-kernel

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux

[Kernel-packages] [Bug 1751990] Re: problems with kernel 4.13

2018-04-02 Thread Brian Murray

** Package changed: ubuntu-release-upgrader (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/1751990

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  New

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-02 Thread kolya

It looks like this is the same problem as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746418. And adding
'noibpb' kernel boot parameter helps, at least in my case.

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1751990] [NEW] problems with kernel 4.13

You have been subscribed to a public bug:

I have a laptop call dc pro. it is made in china. processor is Intel(R)
Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The problems are:

1 the ubuntu 16.04.03 installation will hang somewhere. luckily 16.04.02
will go through.

2 the system will not boot after upgrade to kernel 4.13. the old kernel
4.8 will boot without problem.

3 After install the cuda 9.1 both kernel will boot, but nvidia did not
come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" ) for
the kernel 4.13, the old kernel 4.8 is ok though

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.24
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Tue Feb 27 13:39:45 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-02-17 (10 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade xenial
-- 
problems with kernel 4.13
https://bugs.launchpad.net/bugs/1751990
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 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

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

** Also affects: laptop-mode-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

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

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Confirmed
Status in laptop-mode-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send

Re: [Kernel-packages] [Bug 1760261] Re: log in to GUI in U-MATE daily 18.04 fails

2018-04-02 Thread Fritz Hudnut

Thanks for the request . . . it will take me several hours to get the
download, burn to DVD, etc . . . but I will try that and post back on it
when I get it done.

F

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

Title:
  log in to GUI in U-MATE daily 18.04 fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tried two installs on a daily of U-MATE 18.04 burned to DVD, and each
  time the install seemed to go well, no errors reported, no crash
  reports filed . . . on reboot, grub loads and the MATE log in window
  opens, typing the password brings a black screen for a few seconds,
  and then back to the log in window.

  Tried to install another DE to test whether that would work and that
  also failed.  Ran "dpkg" in the recovery system . . . found some
  updates but couldn't seem to download them; back into TTY and ran
  update/upgrade . . . showed 75 packages, which it installed . . .
  didn't fix the failure to log in problem.  Did an "ls -l
  /home/username" . . . and it showed the /home contents of the
  directory as being there, but the system is not logging into the GUI.

  F

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

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

[Kernel-packages] [Bug 1759947] Re: BUG: unable to handle kernel paging request at 0000200000000020

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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


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

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

Title:
  BUG: unable to handle kernel paging request at 2020

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Unclear what happened.  It said chrome was dying, but then nothing
  including mouse and keyboard worked.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Thu Mar 29 13:56:40 2018
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: find_get_entry+0x42/0x110 RSP: b73c51c3fbe8
  Failure: oops
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 2020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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/1759947/+subscriptions

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

[Kernel-packages] [Bug 1760141] Re: zfs-dkms 0.6.5.6-0ubuntu20: zfs kernel module failed to build

2018-04-02 Thread Seth Arnold

On Ubuntu 16.04 LTS and newer, there's no need to use the zfs DKMS
packages.

Thanks

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu20: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Erro ao rodar zfs-dkms 0.6.5.6-0ubuntu20:

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu20
  ProcVersionSignature: Ubuntu 4.4.0-118.142-generic 4.4.114
  Uname: Linux 4.4.0-118-generic i686
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-118-generic (i686)
   Sex Mar 30 11:52:36 -03 2018
   make: *** Nenhum alvo indicado e nenhum arquivo make encontrado.  Pare.
  DKMSKernelVersion: 4.4.0-118-generic
  Date: Fri Mar 30 11:54:00 2018
  InstallationDate: Installed on 2016-07-16 (622 days ago)
  InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  PackageVersion: 0.6.5.6-0ubuntu20
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu20: zfs kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1759848] Re: Allow multiple mounts of zfs datasets

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

** Also affects: zfs-linux (Ubuntu Bionic)
   Importance: Medium
 Assignee: Colin Ian King (colin-king)
   Status: Fix Released

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

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

Title:
  Allow multiple mounts of zfs datasets

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

Bug description:
  Pull upstream fix https://trello.com/c/l89Ygj28/352-allow-multiple-
  mounts-of-zfs-datasets to allow multiple mounts

  An attempt to mount an already mounted zfs dataset should return a new
  mount referencing the existing super block, but instead it returns an
  error. Operations such as bind mounts and unsharing mount namespaces
  create new mounts for the sb, which can cause operations to fail which
  involve unmounting and remounting the dataset.  This fix from Seth
  addresses this issue

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

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

[Kernel-packages] [Bug 1760585] Re: Bionic update to 4.15.15 stable release

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

Title:
  Bionic update to 4.15.15 stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.15.15 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.15.15 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1757169] Re: linux-kvm: 4.15.0-1003.3 -proposed tracker

The package has been published and the bug is being set to Fix Released


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

** Changed in: kernel-sru-workflow
   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-master-bug: 1757164
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-phase:Released
+ kernel-phase-changed:Monday, 02. April 2018 19:01 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1757164
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-phase:Released
- kernel-phase-changed:Monday, 02. April 2018 19:01 UTC

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

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

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

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Bionic:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1757164
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

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

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

Title:
  ubuntu-kvm-unit test failed with sprs test on ppc64le

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

Bug description:
  The sprs test has failed on ppc64le
  This issue can be spotted on Zesty and Xenial. There is no history for this 
test on Artful

  $ sudo /bin/bash -c "MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= 
./powerpc/run powerpc/sprs.elf -smp 1 -append '-w'"
  run_migration timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 
-nodefaults -machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none 
-serial stdio -kernel powerpc/sprs.elf -smp 1 -append -w # -initrd 
/tmp/tmp.RUTL6E2JSi
  Settings SPRs to 0xcafefacec0debabe...
  Now migrate the VM, then press a key or send NMI...
  Checking SPRs...
  PASS: SPR 3:  0x00debabe <==> 0x00debabe
  PASS: SPR 13: 0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 17: 0x00debabe <==> 0x00debabe
  PASS: SPR 18: 0xc0debabe <==> 0xc0debabe
  PASS: SPR 19: 0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 29: 0xcafefacec0debabe <==> 0xcafefacec0debabe
  FAIL: SPR 61: 0x4054504440541014 <==> 00
  PASS: SPR 153:0x0a84 <==> 0x0a84
  PASS: SPR 157:0xcfcfc0cf <==> 0xcfcfc0cf
  FAIL: SPR 159:0xc0debabe <==> 00
  PASS: SPR 256:0xc0debabe <==> 0xc0debabe
  PASS: SPR 259:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 274:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 275:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 769:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 770:0xcafefacec006babe <==> 0xcafefacec006babe
  PASS: SPR 771:0xc0debabe <==> 0xc0debabe
  PASS: SPR 772:0xc0debabe <==> 0xc0debabe
  PASS: SPR 773:0xc0debabe <==> 0xc0debabe
  PASS: SPR 774:0xc0debabe <==> 0xc0debabe
  PASS: SPR 775:0xc0debabe <==> 0xc0debabe
  PASS: SPR 776:0xc0debabe <==> 0xc0debabe
  PASS: SPR 779:0xfa8b1afe <==> 0xfa8b1afe
  PASS: SPR 780:0xcafefacec0debabc <==> 0xcafefacec0debabc
  PASS: SPR 781:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 782:0xcafefacec0debabe <==> 0xcafefacec0debabe
  FAIL: SPR 784:0xcafefacec0debabe <==> 00
  PASS: SPR 785:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 786:0xcafefacec006babe <==> 0xcafefacec006babe
  PASS: SPR 787:0xc0debabe <==> 0xc0debabe
  PASS: SPR 788:0xc0debabe <==> 0xc0debabe
  PASS: SPR 789:0xc0debabe <==> 0xc0debabe
  PASS: SPR 790:0xc0debabe <==> 0xc0debabe
  PASS: SPR 791:0xc0debabe <==> 0xc0debabe
  PASS: SPR 792:0xc0debabe <==> 0xc0debabe
  PASS: SPR 795:0xfa8b1afe <==> 0xfa8b1afe
  PASS: SPR 796:0xcafefacec0debabc <==> 0xcafefacec0debabc
  PASS: SPR 797:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 798:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 800:0x8000c000 <==> 0x8000c000
  PASS: SPR 801:0x8000 <==> 0x8000
  PASS: SPR 802:0x8000c000 <==> 0x8000c000
  PASS: SPR 803:0x8000 <==> 0x8000
  PASS: SPR 804:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 805:0xcafefacec0debabc <==> 0xcafefacec0debabc
  PASS: SPR 806:0x8000c000 <==> 0x8000c000
  FAIL: SPR 815:0xcafefacec0debabe <==> 00
  SUMMARY: 47 tests, 4 unexpected failures

  EXIT: STATUS=3

  $ qemu-system-ppc --version
  QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.16), Copyright (c) 
2003-2008 Fabrice Bellard

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
  ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: ppc64el
  Date: Mon Oct 16 09:16:08 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.02 0.14 0.17 1/1464 15093
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1604 00:14:19651 0 EOF
   2: POSIX  ADVISORY  WRITE 2937 00:14:55331 0 EOF
   3: FLOCK  ADVISORY  WRITE 3046 00:14:67623 0 EOF
   4: POSIX  ADVISORY  WRITE 3124

Re: [Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-04-02 Thread Steve Langasek

On Thu, Mar 29, 2018 at 06:27:18PM -, Alkis Georgopoulos wrote:

> For the maintainers of the affected packages to be able to help in this
> issue, addressing the main question already stated above would be most
> helpful:

> To support netplan, do we have to implement netlink events listeners 
> ourselves?
> I'm not sure all maintainers are willing to do that.

> Or is there another package that provides this functionality that we could
> rely on?  E.g.  NetworkManager does have a dispatcher.d directory that we
> can use, but does Ubuntu ship something similar (networkd-dispatcher?) in
> systems that don't use NetworkManager?

We are looking at integrating networkd-dispatcher for 18.04.

Many of these package tasks may become SRU material after 18.04 releases,
due to the timing.

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus:

[Kernel-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Confirmed

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

** Tags added: bionic kernel-da-key

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

Title:
  Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

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

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

Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: Invalid

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

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

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

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

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: Confirmed

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


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

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

** Also affects: kernel-sru-workflow/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-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-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/prepare-package
   Importance: Undecided => Medium

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed

[Kernel-packages] [Bug 1760108] Re: Broadcom B43 Wireless Driver Not Functional after Update to Linux Kernel 4.15

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

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

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

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


Thanks in advance.

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: High
   Status: Confirmed

** Tags added: kernel-key

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

Title:
  Broadcom B43 Wireless Driver Not Functional after Update to Linux
  Kernel 4.15

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

Bug description:
  I was upgrading my Ubuntu Xenial 16.04 from linux-hwe kernel 4.13.0-38
  to linux-hwe-edge 4.15.0-13.

  After reboot my Broadcom network adapter (requiring package
  firmware-b43-installer) is not recognized by the new kernel 4.15.0-13.

  Running the lspci command lists the device as 'UNCLAIMED' in linux
  kernel 4.15.

  $ lspci
  [...]
  *-pci:4
   description: PCI bridge
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 1c
   bus info: pci@:00:1c.0
   version: f0
   width: 32 bits
   clock: 33MHz
   capabilities: pci pciexpress msi pm normal_decode bus_master 
cap_list
   configuration: driver=pcieport
   resources: irq:123 memory:ef50-ef5f
     *-network UNCLAIMED
  description: Network controller
  product: BCM4331 802.11a/b/g/n
  vendor: Broadcom Corporation
  physical id: 0
  bus info: pci@:05:00.0
  version: 02
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress cap_list
  configuration: latency=0
  resources: memory:ef50-ef503fff
  [...]
  $

  The lspci -vv -pci:4 commands with the relevant devices are shown
  below.

  $ lspci -vv -pci:4
  [...]
  05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 
02)
   Subsystem: Apple Inc. AirPort Extreme
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
    Address:   Data: 
   Capabilities: [d0] Express (v1) Endpoint, MSI 00
    DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
     ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
     RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 
<4us, L1 <64us
     ClockPM+ Surprise- LLActRep+ BwNot- ASPMOptComp-
    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
     ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ 
BWMgmt- ABWMgmt-
   Capabilities: [100 v1] Advanced Error Reporting
    UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ 
MalfTLP+ ECRC- UnsupReq- ACSViol-
    CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
    CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
    AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
   Capabilities: [13c v1] Virtual Channel
    Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
    Arb:Fixed- WRR32- WRR64- WRR128-
    Ctrl:   ArbSelect=Fixed
    Status: InProgress-
    VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
     Arb:   Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
     Ctrl:  Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
     Status:NegoPending- InProgress-
   Capabilities: [160 v1] Device Serial Number c6-d6-51-ff-ff-e6-f4-f9
   Capabilities: [16c v1] Power Budgeting 
   Kernel modules: bcma
  [...]
  $

  The circumstances of this bug is well described on this webpage:

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1760680] [NEW] linux-aws: -proposed tracker

Public bug reported:

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

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

** 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/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux-aws (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-aws (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.02-1 kernel-sru-derivative-of-1760678

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/regression-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/prepare-package
   Importance: Undecided => Medium

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

** Tags added: kernel-sru-cycle-2018.04.02-1

** Tags added: kernel-sru-derivative-of-1760678

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

Title:
  linux-aws:  -proposed tracker

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

Bug description:
  This bug is for tracking the  upload

[Kernel-packages] [Bug 1760683] [NEW] linux-kvm: -proposed tracker

Public bug reported:

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

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

** 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/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux-kvm (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-kvm (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.02-1 kernel-sru-derivative-of-1760678

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/regression-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/prepare-package
   Importance: Undecided => Medium

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

** Tags added: kernel-sru-cycle-2018.04.02-1

** Tags added: kernel-sru-derivative-of-1760678

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

Title:
  linux-kvm:  -proposed tracker

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

Bug description:
  This bug is for tracking the  upload

[Kernel-packages] [Bug 1760110] Re: Kernel 4.15.0-13.14 reboots instead of powering off (when on battery) on HP Spectre x360 ae-000x

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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


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

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

Title:
  Kernel 4.15.0-13.14 reboots instead of powering off (when on battery)
  on HP Spectre x360 ae-000x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This might be a duplicate of #1756455

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-13 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot instead of turning hardware off. 4.15.0-12 has the same problem
  (see #1756455). Booting with kernel 4.15.0-10 resolves the issue,
  system turns off power and stays powered off.

  * secure boot enabled or disabled makes no difference

  * kernel 4.15.0-10 correctly powers off system (halt -p) every time,
  power source makes no difference

  * kernel 4.15.0-13 correctly powers off system only when running on AC

  * kernel 4.15.0-13 does NOT power off system (reboots instead) when AC
  power is NOT connected (running on battery) every time

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1648 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Mar 30 14:39:28 2018
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (20 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1760163] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038

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

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

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

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


Thanks in advance.

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


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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0038

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Chrome hung. Then the rest of the machine hung.

  Might be related to the other bugs recently auto-reported.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Fri Mar 30 09:09:52 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: hide_cursor+0x25/0x90 RSP: af9647f0fbc8
  Failure: oops
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off iommu=pt ---
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0038
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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/1760163/+subscriptions

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

[Kernel-packages] [Bug 1760261] Re: log in to GUI in U-MATE daily 18.04 fails

Can you see if this issue also happens with the latest daily image?  It can be 
downloaded from:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/


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

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

Title:
  log in to GUI in U-MATE daily 18.04 fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tried two installs on a daily of U-MATE 18.04 burned to DVD, and each
  time the install seemed to go well, no errors reported, no crash
  reports filed . . . on reboot, grub loads and the MATE log in window
  opens, typing the password brings a black screen for a few seconds,
  and then back to the log in window.

  Tried to install another DE to test whether that would work and that
  also failed.  Ran "dpkg" in the recovery system . . . found some
  updates but couldn't seem to download them; back into TTY and ran
  update/upgrade . . . showed 75 packages, which it installed . . .
  didn't fix the failure to log in problem.  Did an "ls -l
  /home/username" . . . and it showed the /home contents of the
  directory as being there, but the system is not logging into the GUI.

  F

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

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

[Kernel-packages] [Bug 1760259] Re: Touchpad never worked in ubuntu (ASUS FX503DV-EH73)

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

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

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

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


Thanks in advance.

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


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

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

Title:
  Touchpad never worked in ubuntu  (ASUS FX503DV-EH73)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Laptop: Asus FX503DV-EH73
  Touchpad: ELAN1200:00 04F3:303E Touchpad
  It did not work in "Try ubuntu" nor after installing Ubuntu.

  I added i8042.reset to grub and now it "works", but it not responding
  correctly. It has some lag and sometimes it doesn't move.

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

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

[Kernel-packages] [Bug 1760169] Re: usb 3-1.3: rtl8192eu_rx_iqk_path_a: Path A RX IQK failed!

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

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

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

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


Thanks in advance.

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


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

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

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

Title:
  usb 3-1.3: rtl8192eu_rx_iqk_path_a: Path A RX IQK failed!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [   65.120857] usb 3-1.3: rtl8192eu_rx_iqk_path_a: Path A RX IQK failed!
  [   65.145503] usb 3-1.3: rtl8192eu_rx_iqk_path_a: Path A RX IQK failed!

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1938 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Mar 30 15:03:23 2018
  InstallationDate: Installed on 2017-10-13 (168 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-13-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  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/1760169/+subscriptions

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

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

Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: Invalid

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

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

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

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

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: Confirmed

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


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

** Tags added: kernel-release-tracking-bug

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

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

** Tags added: bionic

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

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

** Also affects: kernel-sru-workflow/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-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-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/prepare-package
   Importance: Undecided => Medium

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

** Changed in: kernel-sru-workflow/prepare-package
   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/1760675

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in

[Kernel-packages] [Bug 1760172] Re: Not Work: usb 3-1.3: New USB device found, idVendor=0bda, idProduct=a811

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

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

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

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


Thanks in advance.

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


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

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

Title:
  Not Work: usb 3-1.3: New USB device found, idVendor=0bda,
  idProduct=a811

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello

  dmesg:
  [   75.043376] usb 3-1.3: new high-speed USB device number 5 using xhci_hcd
  [   75.155709] usb 3-1.3: New USB device found, idVendor=0bda, idProduct=a811
  [   75.155715] usb 3-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [   75.155719] usb 3-1.3: Product: 802.11ac WLAN Adapter 
  [   75.155722] usb 3-1.3: Manufacturer: Realtek 
  [   75.155726] usb 3-1.3: SerialNumber: 00e04c01

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1817 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Mar 30 15:12:03 2018
  InstallationDate: Installed on 2017-10-13 (168 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-13-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  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/1760172/+subscriptions

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

[Kernel-packages] [Bug 1760127] Re: BCM2045B: Integrated Bluetooth adapter needs to be enabled twice to work on ThinkPad T400

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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


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

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

Title:
  BCM2045B: Integrated Bluetooth adapter needs to be enabled twice to
  work on ThinkPad T400

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug has been around since the 4.x kernels.

  When the system boots up, Bluetooth is disabled as expected:

  $ rfkill list
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  2: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no

  After we try to enable it with 'rfkill unblock bluetooth', the
  Bluetooth interface hci0 is now present, but is soft blocked:

  $ rfkill unblock bluetooth

  $ rfkill list
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  2: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: noDescription:Linux Mint 18.3 Sylvia
  Release:  18.3

Hard blocked: no
  10: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

  However, Bluetooth is considered enabled by the thinkpad-acpi driver,
  as we can see:

  $ cat /proc/acpi/ibm/bluetooth
  status:   enabled
  commands: enable, disable

  The Bluetooth LED is also on.

  'hciconfig' is seeing the Bluetooth adapter as being DOWN:

  $ hciconfig

  hci0: Type: BR/EDR  Bus: USB
BD Address: 00:22:68:E4:BF:27  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN 
RX bytes:511 acl:0 sco:0 events:23 errors:0
TX bytes:339 acl:0 sco:0 commands:23 errors:0

  To remove the soft block of hci0 and make the Bluetooth adapter fully
  operational, we should run 'rfkill unblock bluetooth' one more time.

  $ rfkill unblock bluetooth

  $ rfkill list
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  2: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
  10: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

  $ hciconfig

  hci0: Type: BR/EDR  Bus: USB
BD Address: 00:22:68:E4:BF:27  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1046 acl:0 sco:0 events:50 errors:0
TX bytes:943 acl:0 sco:0 commands:50 errors:0

  Now the adapter is fully operational.

  This behavior confuses most of the GUI applets that are used by the
  modern distributions, since they expect to have an operational adapter
  after the first attempt to enable it. This makes it impossible to use
  the Bluetooth adapter through them.

  I`m currently testing on Linux Mint 18.3 MATE (with Ubuntu package
  base) that is shipped with the 'blueberry' applet, it uses bt-adapter
  from the BlueZ suite in the background to manage the Bluetooth
  adapter. Because of this bug, it crashes and 'blueberry' is unable to
  use the Bluetooth.

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

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

[Kernel-packages] [Bug 1745282] Re: Freezes XPS 13