[Kernel-packages] [Bug 1745959] Re: linux: 3.2.0-133.179 -proposed tracker

[Po-Hsu Lin]

Our MaaS server is still affected by bug 1739761
Please feel free to set this task to Invalid.

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux: 3.2.0-133.179 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Incomplete
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  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: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

[Kai-Heng Feng]

I guess what we want is btcoex_enable=0 bt_ant_diversity=1.
>From what I can understand, bt_ant_diversity is the one that can use BT's 
>antenna to be WiFi's RX antenna when BT is off.

Peter, can you try if btcoex_enable=0 bt_ant_diversity=1 works for you?

Here's the relevant code:
/*
 * Enable WLAN/BT RX Antenna diversity only when:
 *  
 * - BTCOEX is disabled.
 * - the user manually requests the feature.
 * - the HW cap is set using the platform data.
 */
if (!common->btcoex_enabled && ath9k_bt_ant_diversity &&
(pCap->hw_caps & ATH9K_HW_CAP_BT_ANT_DIV))
common->bt_ant_diversity = 1;

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1746661

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

Title:
  [linux-oem] Use I2C transport for touchpad on Precision M5530

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  === SRU Justification ===
  [Impact] 
  Touchpad on Precision M5530 uses PS/2 instead of I2C as its transport.

  [Test Case]
  The touchpad binds to psmouse instead of i2c_hid.
  With the patch, the touchpad uses i2c_hid instead.

  [Fix]
  LKML Link: https://lkml.org/lkml/2018/1/30/963
  The de facto standard, Windows, parse its DSDT as a term list. The DSDT
  table on Precision M5530 also designed that way, hence we should just
  respect that.
  Add a new quirk for this specific machine.
  I'll backport the patch for stable releases once it's upstreamed.

  [Regression Potential]
  Low. This fix is limited to XPS 15 9570/Precision M5530. Also it's the
  "correct" way to do for this machine.

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

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

[Kernel-packages] [Bug 1746661] [NEW] [linux-oem] Use I2C transport for touchpad on Precision M5530

[Kai-Heng Feng]

Public bug reported:

=== SRU Justification ===
[Impact] 
Touchpad on Precision M5530 uses PS/2 instead of I2C as its transport.

[Test Case]
The touchpad binds to psmouse instead of i2c_hid.
With the patch, the touchpad uses i2c_hid instead.

[Fix]
LKML Link: https://lkml.org/lkml/2018/1/30/963
The de facto standard, Windows, parse its DSDT as a term list. The DSDT
table on Precision M5530 also designed that way, hence we should just
respect that.
Add a new quirk for this specific machine.
I'll backport the patch for stable releases once it's upstreamed.

[Regression Potential]
Low. This fix is limited to XPS 15 9570/Precision M5530. Also it's the
"correct" way to do for this machine.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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


** Tags: originate-from-1742898 somerville

** Tags added: originate-from-1742898 somerville

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

Title:
  [linux-oem] Use I2C transport for touchpad on Precision M5530

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  === SRU Justification ===
  [Impact] 
  Touchpad on Precision M5530 uses PS/2 instead of I2C as its transport.

  [Test Case]
  The touchpad binds to psmouse instead of i2c_hid.
  With the patch, the touchpad uses i2c_hid instead.

  [Fix]
  LKML Link: https://lkml.org/lkml/2018/1/30/963
  The de facto standard, Windows, parse its DSDT as a term list. The DSDT
  table on Precision M5530 also designed that way, hence we should just
  respect that.
  Add a new quirk for this specific machine.
  I'll backport the patch for stable releases once it's upstreamed.

  [Regression Potential]
  Low. This fix is limited to XPS 15 9570/Precision M5530. Also it's the
  "correct" way to do for this machine.

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

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

[Kernel-packages] [Bug 1744712] Re: Dell XPS 13 9360 bluetooth (Atheros) won't connect after resume

[Kai-Heng Feng]

** Description changed:

+ === SRU Justification ===
+ [Impact]
+ Bluetooth (Atheros) won't connect after resume.
+ 
+ [Test Case]
+ Suspend/resume XPS 9360. BT controller is not functional now.
+ With the fix, user confirms the issue is fixed.
+ 
+ [Regression Potential]
+ Low. Limited to Atheros BT. No regression report so far since Hans'
+ patch got merged upstream.
+ 
+ === Original Bug Report ===
+ 
  Sometimes after sleep/resume bluetooth won't reconnect to any device.
  
  I can see this in dmesg:
  [13129.890580] Bluetooth: hci0 command 0x0c1a tx timeout
  
  I tried:
  1. sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)
  
  2. tried reloading modules:
  sudo rmmod btusb
  sudo rmmod btrtl
  sudo rmmod hci_uart
  sudo rmmod btintel
  sudo rmmod btbcm btqca
  sudo rmmod rfcomm
  
  sleep 1
  
  sudo modprobe btusb btrtl hci_uart btintel btbcm btqca rfcomm
  
  no luck.
  
  3. restart bluetoothd - no luck
  
  Only reboot helps.
  
  Laptop is: Dell XPS 13 9360.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 22 12:50:58 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-18 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=e20224ee-6bcd-49a5-b911-a0c129a48da5 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  hciconfig:
-  hci0:Type: Primary  Bus: USB
-   BD Address: 9C:B6:D0:EB:95:A6  ACL MTU: 1024:8  SCO MTU: 50:8
-   DOWN 
-   RX bytes:2301887 acl:127559 sco:0 events:249 errors:0
-   TX bytes:4327 acl:47 sco:0 commands:81 errors:0
+  hci0:Type: Primary  Bus: USB
+   BD Address: 9C:B6:D0:EB:95:A6  ACL MTU: 1024:8  SCO MTU: 50:8
+   DOWN
+   RX bytes:2301887 acl:127559 sco:0 events:249 errors:0
+   TX bytes:4327 acl:47 sco:0 commands:81 errors: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/1744712

Title:
  Dell XPS 13 9360 bluetooth (Atheros) won't connect after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  === SRU Justification ===
  [Impact]
  Bluetooth (Atheros) won't connect after resume.

  [Test Case]
  Suspend/resume XPS 9360. BT controller is not functional now.
  With the fix, user confirms the issue is fixed.

  [Regression Potential]
  Low. Limited to Atheros BT. No regression report so far since Hans'
  patch got merged upstream.

  === Original Bug Report ===

  Sometimes after sleep/resume bluetooth won't reconnect to any device.

  I can see this in dmesg:
  [13129.890580] Bluetooth: hci0 command 0x0c1a tx timeout

  I tried:
  1. sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  2. tried reloading modules:
  sudo rmmod btusb
  sudo rmmod btrtl
  sudo rmmod hci_uart
  sudo rmmod btintel
  sudo rmmod btbcm btqca
  sudo rmmod rfcomm

  sleep 1

  sudo modprobe btusb btrtl hci_uart btintel btbcm btqca rfcomm

  no luck.

  3. restart bluetoothd - no luck

  Only reboot helps.

  Laptop is: Dell XPS 13 9360.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 22 12:50:58 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-18 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=e20224ee-6bcd-49a5-b911-a0c129a48da5 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: 

[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

[Kai-Heng Feng]

Can `sudo dkms install nvidia-381/381.22 -k 4.13.0-25-generic` build the driver 
correctly?
If not, please attach the make.log in its error message.

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/1742302/+subscriptions

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

[Kernel-packages] [Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists

[Kai-Heng Feng]

Do you see the same issue if you boot Bionic live CD/USB in VBox?

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

Title:
  Boots into initramfs with an error stating that the UUID of the main
  partition cannot be found when it actually exists

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently updated Ubuntu 18.04 in a vm have a long dormancy and I
  found the issues I had after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.13.0.17.18
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reg1325 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 18 21:50:54 2018
  InstallationDate: Installed on 2017-11-27 (52 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.

   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=d15b971c-a592-4259-b4fd-b74cf3c4d03c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.170
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-27 (52 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1738491] Re: touchpad not working

[Kai-Heng Feng]

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

** This bug has been marked a duplicate of bug 1728244
   Touchpad stops working after reboot on Apollo Lake

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  chuwi Lapbook Air touch pad not working

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

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

[Kernel-packages] [Bug 1744712] Re: Dell XPS 13 9360 bluetooth (Atheros) won't connect after resume

[Kai-Heng Feng]

https://lists.ubuntu.com/archives/kernel-team/2018-February/089786.html

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

Title:
  Dell XPS 13 9360 bluetooth (Atheros) won't connect after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometimes after sleep/resume bluetooth won't reconnect to any device.

  I can see this in dmesg:
  [13129.890580] Bluetooth: hci0 command 0x0c1a tx timeout

  I tried:
  1. sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  2. tried reloading modules:
  sudo rmmod btusb
  sudo rmmod btrtl
  sudo rmmod hci_uart
  sudo rmmod btintel
  sudo rmmod btbcm btqca
  sudo rmmod rfcomm

  sleep 1

  sudo modprobe btusb btrtl hci_uart btintel btbcm btqca rfcomm

  no luck.

  3. restart bluetoothd - no luck

  Only reboot helps.

  Laptop is: Dell XPS 13 9360.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 22 12:50:58 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-18 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=e20224ee-6bcd-49a5-b911-a0c129a48da5 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 9C:B6:D0:EB:95:A6  ACL MTU: 1024:8  SCO MTU: 50:8
DOWN 
RX bytes:2301887 acl:127559 sco:0 events:249 errors:0
TX bytes:4327 acl:47 sco:0 commands:81 errors:0

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

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

[Kernel-packages] [Bug 1746653] Re: Wayland session got killed.

[Magicloud Magiclouds]

** Package changed: bcmwl (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Wayland session got killed.

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I found that in two cases, my wayland desktop session was killed.
  1. When screen is locked, plugging external monitor in my laptop.
  2. When screen is locked, and with external monitor, at around 0300 UTC. This 
might be because of some background services I am not aware.

  Symptom:
  The monitor is sleep. Type password to unlock.
  The monitor shows Login UI. Do login.
  The monitor shows unlocking UI. Input password again.
  Brand new desktop session. `ps` shows no other applications (including WM and 
so) from last session.
  A huge core file related to Xwayland appears at $HOME.

  The OS is Ubuntu Artful. Version of xwayland is 2:1.19.5-0ubuntu2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1746653/+subscriptions

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

[Kernel-packages] [Bug 1746653] [NEW] Wayland session got killed.

[Magicloud Magiclouds]

Public bug reported:

I found that in two cases, my wayland desktop session was killed.
1. When screen is locked, plugging external monitor in my laptop.
2. When screen is locked, and with external monitor, at around 0300 UTC. This 
might be because of some background services I am not aware.

Symptom:
The monitor is sleep. Type password to unlock.
The monitor shows Login UI. Do login.
The monitor shows unlocking UI. Input password again.
Brand new desktop session. `ps` shows no other applications (including WM and 
so) from last session.
A huge core file related to Xwayland appears at $HOME.

The OS is Ubuntu Artful. Version of xwayland is 2:1.19.5-0ubuntu2.

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


** Tags: wayland

** Attachment added: "core.xz"
   https://bugs.launchpad.net/bugs/1746653/+attachment/5046689/+files/core.xz

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

Title:
  Wayland session got killed.

Status in bcmwl package in Ubuntu:
  New

Bug description:
  I found that in two cases, my wayland desktop session was killed.
  1. When screen is locked, plugging external monitor in my laptop.
  2. When screen is locked, and with external monitor, at around 0300 UTC. This 
might be because of some background services I am not aware.

  Symptom:
  The monitor is sleep. Type password to unlock.
  The monitor shows Login UI. Do login.
  The monitor shows unlocking UI. Input password again.
  Brand new desktop session. `ps` shows no other applications (including WM and 
so) from last session.
  A huge core file related to Xwayland appears at $HOME.

  The OS is Ubuntu Artful. Version of xwayland is 2:1.19.5-0ubuntu2.

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

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

[Kernel-packages] [Bug 1735514] Re: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [kworker/6:1:72]

[Launchpad Bug Tracker]

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

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

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

Title:
  watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [kworker/6:1:72]

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 4.13.0-17.20-generic 4.13.8

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vkareh 1928 F pulseaudio
  Date: Thu Nov 30 12:39:03 2017
  Failure: oops
  InstallationDate: Installed on 2017-11-30 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171130)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:24a0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=019a287c-bc9e-4471-9e47-49616737694f ro quiet splash 
acpi_rev_override=1 vt.handoff=7
  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: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [kworker/6:1:72]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

[Kai-Heng Feng]

@Joseph
The Type-C port (the one with Display port icon) should work out of the box.
At least it works on the XPS 9370 here.

@Mario
I am not talking about lag, mine is like a GPE event storm slow the whole 
machine down.
I'll dig further and see if I can find anything.

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

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate

[Kai-Heng Feng]

I think LP: #1744988 is the same bug as this one.

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

Title:
  systemd-timesyncd doesn't sync time after resume from hibernate

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

Bug description:
  When resuming, the clock remains at the time when the hibernate
  happened, even if timedatectl claims that it is being synced:

  $ timedatectl status
Local time: Вс 2017-12-31 13:46:16 +05
Universal time: Вс 2017-12-31 08:46:16 UTC
  RTC time: Вс 2017-12-31 08:46:16
 Time zone: Asia/Yekaterinburg (+05, +0500)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  I've tried waiting a bit, but this persisted for some minutes, so I
  forced an update with

  systemctl restart systemd-timesyncd.service

  And afterwards the time was (apparently) correctly synced.

  Please, let me know what further informations are needed to debug the
  issue, and I would be happy to do some other test.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 31 13:41:51 2017
  InstallationDate: Installed on 2017-06-05 (208 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 
zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

Re: [Kernel-packages] [Bug 918254] Re: Realtek ALC269VB, needs to manually edit /etc/modprobe.d/alsa-base.conf to work

[Kai-Heng Feng]

> On 31 Jan 2018, at 10:15 PM, ALberto Beltran <918...@bugs.launchpad.net> 
> wrote:
> 
> Dear developers, I have the same problem with my computer Asus
> EEEpc1011px, with the same Realtek ALC269VB. No sound in the internal
> speakers, only headphones. I did the "options snd-hda-intel model=auto"
> in /etc/modprobe.d/alsa-base.conf but did not work. thanks for your
> help.
Please file a separate bug.

Kai-Heng
> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/918254
> 
> Title:
>  Realtek ALC269VB, needs to manually edit /etc/modprobe.d/alsa-
>  base.conf to work
> 
> Status in linux package in Ubuntu:
>  Fix Released
> 
> Bug description:
>  I have a laptop ASUS N53Jq, it mounts Realtek ALC269VB as sound card.
> 
>  Every time I install ubuntu I need to add: "options snd-hda-intel
>  model=auto" in /etc/modprobe.d/alsa-base.conf to get it to work.
> 
>  It is not so annoying, 'cause it is necessary only once per
>  installation, but if it were not necessary it would be great!
> 
>  Regards,
>  - zoff -
>  --- 
>  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
>  ApportVersion: 1.91-0ubuntu1
>  Architecture: amd64
>  ArecordDevices:
>    List of CAPTURE Hardware Devices 
>   card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC1:  zoff   2299 F pulseaudio
>   /dev/snd/controlC0:  zoff   2299 F pulseaudio
>  Card0.Amixer.info:
>   Card hw:0 'Intel'/'HDA Intel at 0xd960 irq 55'
> Mixer name: 'Realtek ALC269VB'
> Components: 'HDA:10ec0269,10431113,00100100'
> Controls  : 22
> Simple ctrls  : 13
>  Card1.Amixer.info:
>   Card hw:1 'NVidia'/'HDA NVidia at 0xd308 irq 17'
> Mixer name: 'Nvidia GPU 14 HDMI/DP'
> Components: 'HDA:10de0014,10de0101,00100100'
> Controls  : 20
> Simple ctrls  : 4
>  DistroRelease: Ubuntu 12.04
>  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac 
> (20111210)
>  Package: alsa-driver (not installed)
>  ProcEnviron:
>   PATH=(custom, no user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
>  Tags:  precise
>  Uname: Linux 3.2.0-9-generic x86_64
>  UpgradeStatus: Upgraded to precise on 2012-01-13 (7 days ago)
>  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
>  dmi.bios.date: 11/05/2010
>  dmi.bios.vendor: American Megatrends Inc.
>  dmi.bios.version: N53Jq.209
>  dmi.board.asset.tag: ATN12345678901234567
>  dmi.board.name: N53Jq
>  dmi.board.vendor: ASUSTeK Computer Inc.
>  dmi.board.version: 1.0
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: ASUSTeK Computer Inc.
>  dmi.chassis.version: 1.0
>  dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvrN53Jq.209:bd11/05/2010:svnASUSTeKComputerInc.:pnN53Jq:pvr1.0:rvnASUSTeKComputerInc.:rnN53Jq:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
>  dmi.product.name: N53Jq
>  dmi.product.version: 1.0
>  dmi.sys.vendor: ASUSTeK Computer Inc.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/918254/+subscriptions

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

Title:
  Realtek ALC269VB, needs to manually edit /etc/modprobe.d/alsa-
  base.conf to work

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a laptop ASUS N53Jq, it mounts Realtek ALC269VB as sound card.

  Every time I install ubuntu I need to add: "options snd-hda-intel
  model=auto" in /etc/modprobe.d/alsa-base.conf to get it to work.

  It is not so annoying, 'cause it is necessary only once per
  installation, but if it were not necessary it would be great!

  Regards,
  - zoff -
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zoff   2299 F pulseaudio
   /dev/snd/controlC0:  zoff   2299 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd960 irq 55'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,10431113,00100100'
 Controls  : 22
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xd308 irq 17'
 Mixer name : 'Nvidia GPU 14 HDMI/DP'
 Components : 'HDA:10de0014,10de0101,00100100'
 Controls  : 20
 Simple ctrls  : 4
  DistroRelease: Ubuntu 12.04
  

[Kernel-packages] [Bug 1726818] Re: vagrant artful64 box filesystem too small

[jxn]

I believe this also affects the bionic64 nightlies.

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [SRU Justfication, Artful]

  [Impact]

  Booting the 4.13 Artful kernel with vagrant using VirtualBox trips the
  warning:

  [ 61.010337] VFS: brelse: Trying to free free buffer
  [ 61.114875] [ cut here ]
  [ 61.114886] WARNING: CPU: 0 PID: 683 at 
/build/linux-XO_uEE/linux-4.13.0/fs/buffer.c:1205 __brelse+0x21/0x30

  and a failed resize of a partition.  The root cause has been bisected
  down to the following commmit:

  commit c20cfc27a47307e811346f85959cf3cc07ae42f9
  Author: Christoph Hellwig 
  Date: Wed Apr 5 19:21:07 2017 +0200

  block: stop using blkdev_issue_write_same for zeroing

  
  [Fix]
  The Upstream commit directly fixes this issue:

  commit d5ce4c31d6df518dd8f63bbae20d7423c5018a6c
  Author: Ilya Dryomov 
  Date:   Mon Oct 16 15:59:10 2017 +0200

  block: cope with WRITE ZEROES failing in blkdev_issue_zeroout()

  ..however we also require a backport of the following upstream commit
  to apply the above commit cleanly.

  commit 425a4dba7953e35ffd096771973add6d2f40d2ed
  Author: Ilya Dryomov 
  Date:   Mon Oct 16 15:59:09 2017 +0200

  block: factor out __blkdev_issue_zero_pages()

  [Testscase]

  On Ubuntu Xenial:

  1. sudo apt-get install virtualbox vagrant
  2. edit /etc/group and add one's user name to the vboxusers group
  3. log out log back
  4. vagrant init ubuntu/artful64
  5. vagrant up
  6. vagrant ssh
  7. dmesg | grep "VFS: brelse"

  without the fix one will see the VFS brelse warning message and the /
  partition will not have been resized.

  with a fixed system there is is no VFS vbrelse warning and / as been
  resized as expected.

  [Regresion potential]
  These patches touch the blk library so potentially it could break the block 
layer and corrupt data on disk.  However these are upstream fixes that address 
the buggy commit c20cfc27a47307e811346f85959cf3cc07ae42f9 and are known to 
address the bug.

  ---


  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev991M 0  991M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   2.2G  2.1G   85M  97% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  182G   28G  87% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev992M 0  992M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   9.7G  2.5G  7.3G  26% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  183G   28G  88% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  With artful64, the size of /dev/sda1 is reported as 2.2G, which
  results in 97% of disk usage immediately after building, even though
  the disk size is 10G, as reported by the fdisk:

  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

  Device Boot Start  End  Sectors Size Id Type
  /dev/sda1  * 2048 20971486 20969439  10G 83 Linux

  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  Almost any additional installation results in a "No space left on
  device" error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1726818/+subscriptions

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

[Kernel-packages] [Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic

[Sandra Ray]

I can confirm that v4.14 final works.

Also, I made an obvious blunder in the initial report: I had to disable
*Wayland* after upgrading to 17.10, not Mir. That must've been a
crossover from an alternate universe where Ubuntu went with Mir :)

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

Title:
  System freezes when starting Xorg after installing linux-
  image-4.13.0-32-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only
  after installing the latest ubuntu kernel for 17.10, linux-
  image-4.13.0-32-generic.

  Am running Xorg instead of MIR due to MIR crashing when I initially
  upgraded from 17.04 to 17.10, but that's a different problem for a
  different day. It's been running with Xorg stably for at least 2-3
  months.

  If I boot with the previous kernel version on my /boot (linux-
  image-4.13.0-25-generic), everything works fine.

  If I boot with the latest mainline kernel from the Ubuntu mainline
  repo (4.15.0), everything works.

  Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I
  am able to use the CLI and access the encrypted root filesystem, which
  is how I generated the apport repo that's attached. It's only when
  telling it to continue Normal booting that it freezes, which is why I
  suspect the problem of being Xorg.

  When the system freezes, the fan starts to spin up. I cannot switch
  virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed
  repeatedly doesn't do anything. To reboot, I have to hold the power
  button until the system powers off.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
03ea8ad78cfb2910862c8dfcd2a627fc04097db2

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745342

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Joseph Salisbury]

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => 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/1743053

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

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

Bug description:
  Some SSD drives made by LiteOn can crash the kernel due to bad
  drivers.  A fix for this issue has been submitted upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  
  At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)

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

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

[Kernel-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Daniel van Vugt]

You can install the kernel by just downloading and installing these
three:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201801282230_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500-generic_4.15.0-041500.201801282230_amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-image-4.15.0-041500-generic_4.15.0-041500.201801282230_amd64.deb

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: 

[Kernel-packages] [Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

[dann frazier]

@Robert: Actually, X-Gene is supported on trusty, which is non-GICv3,
but your point is taken. I personally think option #3 would be the best
option, but wasn't sure of the feasibility. However, I've been working
on the necessary kernel backports in the background over the past week,
and I now have something working that looks pretty clean/minimal. I'm
doing some regression testing now, and plan to submit to the kernel team
later this week.

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

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

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

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

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

Status in cloud-images:
  New
Status in edk2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in edk2 source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  [Impact]
  After upgrading your KVM hypervisor past xenial, your xenial-based guests 
will fail to boot.

  [Test Case]
  Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.

  [Regression Risk]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1744754/+subscriptions

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

[Kernel-packages] [Bug 1724863] Re: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Olver Hernandez]

I tested with the kernel 4.13.0-32 and It works

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-
  edge 4.13.0-16.19~16.04.3

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

Bug description:
  [Impact]

  Currently the DKMS package bcmwl-kernel-source fails to install in
  supported custom kernels that are based on 4.11 or 4.13. That includes
  the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and
  some of the custom and cloud kernels as well.

  [Test Case]

  Install the bcmwl-kernel-source package with the 4.13 hwe-edge kernel
  from -proposed. The package installation should proceed without any
  errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel version.

  Besides that the new package was tested with the following kernels in an
  amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original Description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20171018_120646_2caa6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20171018_120820_2caa6@/log.gz

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

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

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

Hi,

The team has tested the kernel in comment #5 and confirmed that it
resolves the issue.  Thanks!

BTW, we need this patch in Xenial as well since we are using the LTS.

Steve

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

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

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:
  Some SSD drives made by LiteOn can crash the kernel due to bad
  drivers.  A fix for this issue has been submitted upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  
  At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[John Lenton]

I just confirmed that

$ uname -a
Linux flimsy 4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

works, and that

$ uname -a
Linux flimsy 4.12.0-041200rc2-generic #201801312242 SMP Wed Jan 31 22:44:06 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

does not 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/1745342

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

[Joseph Salisbury]

After some more testing, it appears v4.11 final does not have the bug.
Version 4.12-rc1 appears to be the first kernel version to hit the bug.
I'll run a few more tests to confirm this.  Once confirmed, I'll start a
bisect between v4.11 and v4.12-rc1.

If others want to try these two versions, they can be downloaded from:

v4.11: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/
v4.12-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

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

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
edea55abb86ff67afda96120d6254290e7a75d9e

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745342

I figured we would have a few 'good' kernels by now.  There are only a
few more steps in the bisect.  Can you confirm v4.12 final was defiantly
good?  It is available at:


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

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

[Joseph Salisbury]

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

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

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

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[John Lenton]

$ uname -a
Linux flimsy 4.12.0-041200rc2-generic #201801312121 SMP Wed Jan 31 21:23:03 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

did _not_ work...

also plymouthd crashed, but that might be unrelated :-)

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

[Olivier Tilloy]

Just tested in a bionic i386 VM, and unfortunately neither your build of
4.13.0-17 nor upstream 4.15 make the situation better. I'm still seeing
libreoffice base crash when creating a new database, and the crash
happens in
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so.

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

[Joseph Salisbury]

The 4.10 based kernel does not experience this hang, but I am seeing it
with 4.12.  Maybe the 4.12 based kernels does in fact have the bug.
I'll test further to find out.

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

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

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
b040ad9cf6a169cc000a5324fcada695dfa1f4b3

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745342

Hide

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746019] Re: [Artful SRU] Fix capsule update regression

[Manoj Iyer]

** Summary changed:

- [Artful SRU] Fix capsule update regression since kernel v4.13.
+ [Artful SRU] Fix capsule update regression

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

Title:
  [Artful SRU] Fix capsule update regression

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [IMPACT]
  Commit 82c3768b8d68 ("efi/capsule-loader: Use a cached copy of the
  capsule header") refactored the capsule loading code that maps the
  capsule header, to avoid having to map it several times. However,
  as it turns out, the vmap() call we ended up removing did not just
  map the header, but the entire capsule image, and dropping this
  virtual mapping breaks capsules that are processed by the firmware
  immediately (i.e., without a reboot).

  [FIX]
  The following patch fixes the issue
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/efi/capsule-loader.c?id=f24c4d478013d82bd1b943df566fff3561d52864

  [TEST]
  Please see comments below for testing information and details.

  [REGRESSION POTENTIAL]
  This patch fixes a regression in 4.13 and onward.

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

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

[Kernel-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Gediminas]

Problem occured when force shutdown windows and booted up ubuntu. I was
able to bypass this bug by commenting out windows partition mount in
fstab

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

[Christopher M. Penalver]

Sergey Zolotarev, please boot into latest mainline kernel with no
patching/modifications, and provide the information from #5.

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

Title:
  [Asus K501UQ] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When Ubuntu wakes up after suspend the touchpad doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  szx1685 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 31 05:40:49 2018
  InstallationDate: Installed on 2018-01-23 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=04181349-688b-425f-899c-822fcf6a409b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UQ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UQ.300:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnK501UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K501UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[John Lenton]

$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311949 SMP Wed Jan 31 19:50:53 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

did _not_ work.

Thank you.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

[Sergey Zolotarev]

I was wrong, this didn't fix the bug. After a few more suspends and wakes the 
touchpad is dead again.
I think it may depend on how many times the system is suspended or for how long 
it was suspended. 


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

Title:
  [Asus K501UQ] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When Ubuntu wakes up after suspend the touchpad doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  szx1685 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 31 05:40:49 2018
  InstallationDate: Installed on 2018-01-23 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=04181349-688b-425f-899c-822fcf6a409b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UQ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UQ.300:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnK501UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K501UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
a104c9f22c7d073d4ae308ca36383ce5cc4631cc

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745342

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Steve Langasek]

On Wed, Jan 31, 2018 at 06:27:35PM -, Vagrant Cascadian wrote:
> This doesn't sound like the sort of thing to replace ifupdown...  some
> more information about what this actually refers to would be helpful.

The package name is 'nplan' due to conflict with pre-existing (and scarcely
relevant) software.

-- 
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:
  New
Status in chrony package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  New
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:
  New
Status in ifmetric package in Ubuntu:
  New
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  New
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:
  New
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:
  In Progress
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:
  New
Status in vzctl package in Ubuntu:
  New
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: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1710976] Re: Livepatch motd enhancement to show people how livepatch can help protect systems.

[Andreas Hasenack]

This feature is being developed in https://github.com/panlinux/ubuntu-
advantage-script/tree/livepatch-motd

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

Title:
  Livepatch motd enhancement to show people how livepatch can help
  protect systems.

Status in linux package in Ubuntu:
  Invalid
Status in ubuntu-advantage-tools package in Ubuntu:
  In Progress
Status in update-notifier package in Ubuntu:
  Invalid

Bug description:
  This is a request to add an enhancement in our motd.d to inform users
  of the following:

  1) that livepatch is available for their platform/kernel if they don't
  have it set up and installed right now.

  2) When a system is protected by livepatch, and the system is
  currently patched (i.e., canonical-livepatch has active patches
  applied).

  3) when a system is protected by livepatch and no livepatches exist
  yet for the kernel version, a single line message of 'This system is
  protected by canonical-livepatch." or similar.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[Joseph Salisbury]

To build these kernels, I use a script called mainline-build-one, which
is in the kteam-tools repository[0].

The script comes up with the name of the .deb by using the date and the
git command 'git describe SHA1'.  So in the case of the last commit
tested:

git describe fdd050b5b3c96813ae6756ed68157d32ba31b9f2
v4.12-rc5-66-gfdd050b

If the script used '--contains' with git describe, it would report the
actual kernel version that contains that commit, for example:

git describe --contains fdd050b5b3c96813ae6756ed68157d32ba31b9f2
v4.13-rc1~70^2~67^2~42


[0] git://git.launchpad.net/~canonical-kernel/+git/kteam-tools

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1742759] Re: boot failure on AMD Raven + WestonXT

[Timo Aaltonen]

** Description changed:

  This issue has been fixed with with patch:
- https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-
- next=e639173a30efab97dabcf2229362aacd8f46a894
+ 
+ https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
+ next-4.16=052c299080cd6859f82a8154a7a673fafabe644c
  
  drm/amdgpu: add atpx quirk handling (v2)
  Add quirks for handling PX/HG systems.  In this case, add
  a quirk for a weston dGPU that only seems to properly power
  down using ATPX power control rather than HG (_PR3).
  
  v2: append a new weston XT

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

Title:
  boot failure on AMD Raven + WestonXT

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  This issue has been fixed with with patch:

  https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
  next-4.16=052c299080cd6859f82a8154a7a673fafabe644c

  drm/amdgpu: add atpx quirk handling (v2)
  Add quirks for handling PX/HG systems.  In this case, add
  a quirk for a weston dGPU that only seems to properly power
  down using ATPX power control rather than HG (_PR3).

  v2: append a new weston XT

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

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

[Kernel-packages] [Bug 1742759] Re: boot failure on AMD Raven + WestonXT

[Khaled El Mously]

** Summary changed:

- boot failure on AMD Raven + WesternXT
+ boot failure on AMD Raven + WestonXT

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

Title:
  boot failure on AMD Raven + WestonXT

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  This issue has been fixed with with patch:

  https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
  next-4.16=052c299080cd6859f82a8154a7a673fafabe644c

  drm/amdgpu: add atpx quirk handling (v2)
  Add quirks for handling PX/HG systems.  In this case, add
  a quirk for a weston dGPU that only seems to properly power
  down using ATPX power control rather than HG (_PR3).

  v2: append a new weston XT

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[John Lenton]

$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311805 SMP Wed Jan 31 18:06:52 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

did _not_ work.

What's the significance of the "rc5" in this last batch? I would've
thought these were prior to the known-good 4.12 final.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Joseph Salisbury]

I built a test kernel with commit 5aa04b3eb6fca.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1746225

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

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13


  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048 
  [78592.995985] NUMA 
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1 
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 
 
  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10 
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028 
  [78592.996642] GPR12:  c7a8d480  
 
  [78592.996642] GPR16:    
 
  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98 
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0 
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190 
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        
 
  [78592.997664]        
 
  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780] 
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to other CPUs
  [78594.01029

  Steps to reproduce :
  

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  sleep 10
  cd ../fuzzer
  make
  sleep 10

  echo 0 > /proc/sys/kernel/nmi_watchdog
  echo 2 > /proc/sys/kernel/perf_event_paranoid
  echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
  ./perf_fuzzer -r 1492143527

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1744988] Re: time drifting on linux-hwe kernels

[Joseph Salisbury]

I built a test kernel with the three commits: da4ae6c, b511203 and
4b5b212

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1744988

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

Title:
  time drifting on linux-hwe kernels

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

Bug description:
  We observe NTP time drift on two servers running hwe kernels in
  Xenial. A few weeks ago we wanted to switch from 4.4 to 4.10. When
  rebooting the servers to the 4.10 kernel we were seeing a big time
  offset within minutes after booting. Despite running ntpd, it would
  not keep up and the offset stayed and kept growing over t.

  Rebooting back into the 4.4 at the time we immediatly noticed the time
  stayed normal. Over time I have tested about a dozen versions making
  me think something has been introduced in kernel 4.10 that makes the
  clock go out of sync.

  So what do we observe?

  After 1 min uptime:
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *ntp4.bit.nl .PPS.1 u5   1670.497  100.084  81.382
  +ntp1.bit.nl 193.0.0.229  2 u8   1670.603   93.241  70.643
  +ntp2.bit.nl 193.67.79.2022 u8   1670.582   93.218  70.674
  +ntp3.bit.nl 193.79.237.142 u9   1670.781   90.488  70.574

  A couple of minutes later (and also hours/days, the offset just keeps
  growing over time)

   remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *ntp4.bit.nl .PPS.1 u   13   16  3770.447  400.198 151.335
  +ntp1.bit.nl 193.0.0.229  2 u   13   16  3770.313  400.561 151.339
  +ntp2.bit.nl 193.67.79.2022 u   13   16  3770.517  400.445 151.398
  +ntp3.bit.nl 193.79.237.142 u   12   16  3770.934  402.013 151.384

  As mentioned I tested about a dozen of kernels and I thought I got it
  pinpointed to a specific release when the drifting got introduced,
  4.10rc1. Below the test results of the kernels I have tested up till
  today:

  Tested: 4.4.0-112-generic: not affected
  Tested: 4.8.0-41-generic: not affected
  Tested: 4.8.0-58-generic : not affected
  Tested: 4.9.0 mainline: not affected
  Tested: 4.9.66 mainline: not affected
  Tested: 4.10-rc1 mainline: affected
  Tested: 4.10 mainline: affected
  Tested: 4.10.0-38-generic: affected
  Tested: 4.10.0-40-generic: affected
  Tested: 4.13.0-16-generic: affected
  Tested: 4.13.0-31-generic: affected
  Tested: 4.14.3 mainline: affected
  Tested: 4.15-rc1 mainline: affected

  When I was about to file this bugreport about an hour ago I noticed
  4.15-rc9 was present and thought I gave it a go to make sure I really
  tested the latest version. And while running it over an hour now it
  stable.

  Mostl likely the following from the changelog is related the issue we
  are having:

  Len Brown (3):
x86/tsc: Future-proof native_calibrate_tsc()
x86/tsc: Fix erroneous TSC rate on Skylake Xeon
x86/tsc: Print tsc_khz, when it differs from cpu_khz

  Both servers that are having issues on our side our equipped with the
  following cpu:

  Cpu Model (from /proc/cpuinfo)
  vendor_id : GenuineIntel
  cpu family: 6
  model : 85
  model name: Intel(R) Xeon(R) Gold 6136 CPU @ 3.00GHz

  Standard information as requested:
  1:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  2: 
  root@bit-host6:~# apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.13.0.31.51
Candidate: 4.13.0.31.51

  3: Stable time

  4: A big time offset

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

[Joseph Salisbury]

I'm swapping the bug back in and working on the bisect again.  For some
reason, all of the prior kernels that worked, are now freezing on the
test while "Stopping Links":

*** Configuring hosts
h1 h2 h3 h4 h5 h6 h7 h8 h9 h10 h11 h12 h13 h14 
*** Starting controller
c1 
*** Starting 2 switches
s1 s2 ...
INFO:root:Running TCP performance test
*** Iperf: testing TCP bandwidth between h1 and h14 
*** Results: ['20.9 Gbits/sec', '20.9 Gbits/sec']
INFO:root:Stopping network
*** Stopping 1 controllers
c1 
*** Stopping 15 links




Has anyone else seen this?

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

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

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

[Christopher M. Penalver]

Bib:

1) Regarding the error booting Bionic, could you please capture the
error message via video recorder (cell phone, etc.)? The provided
"repetitive ~CRC32~* or something like that" is not enough information
to debug the issue.

2) Regarding the error booting Bionic, is this the same error message
received when not using the WORKAROUNDs with your current release?

3) Alternatively, could you please test
http://cdimage.ubuntu.com/releases/17.10.1/release/ and advise to the
results?

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

[Christopher M. Penalver]

Sergey Zolotarev, the issue you are reporting is an upstream one. Could
you please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel (TO: Marcos Paulo de Souza,
and Dmitry Torokhov CC: linux-input)?

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your help.

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

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

Title:
  [Asus K501UQ] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When Ubuntu wakes up after suspend the touchpad doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  szx1685 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 31 05:40:49 2018
  InstallationDate: Installed on 2018-01-23 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=04181349-688b-425f-899c-822fcf6a409b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UQ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UQ.300:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnK501UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K501UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

[Yasmin Beatriz Alves da Silva]

One minor detail I should mention is that you're going to see 3 patches
on the file instead of 2. That is because h_page_init hypercall depends
on a function `is_ram_address` that didn't exist in v2.5. This patch has
been backported 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/1712803

Title:
  spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe
  kernel

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in qemu source package in Xenial:
  Triaged

Bug description:
  kernel: 4.10.0-33.37~16.04.1

  I think this issue was introduced by the old qemu version (similar
  issue was spotted on Xenial before), will need to investigate this
  further.

  
  qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin 
-display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1
  FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588
  FAIL: hypercall: h_page_init: h_zero_page
  FAIL: hypercall: h_page_init: h_copy_page
  FAIL: hypercall: h_page_init: h_copy_page+h_zero_page
  FAIL: hypercall: h_page_init: h_zero_page unaligned dst
  FAIL: hypercall: h_page_init: h_copy_page unaligned src
  XFAIL: hypercall: h_random: h-call available

  SUMMARY: 9 tests, 8 unexpected failures, 1 expected failures

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

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

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Vagrant Cascadian]

$ apt show plan netplan | grep -A 3 Description

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

Description: X/Motif day planner
 Plan is a schedule planner based on X/Motif. It displays a month calendar
 similar to xcal, but every day box is large enough to show appointments in
 small print. By pressing on a day box, the appointments for that day can be
--
Description: network server for `plan'
 Plan is a schedule planner based on X/Motif.
 .
 Netplan adds to plan multiuser capability using an IP server.


This doesn't sound like the sort of thing to replace ifupdown... some more 
information about what this actually refers to would be helpful.

-- 
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:
  New
Status in chrony package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  New
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:
  New
Status in ifmetric package in Ubuntu:
  New
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  New
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:
  New
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:
  In Progress
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:
  New
Status in vzctl package in Ubuntu:
  New
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: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
fdd050b5b3c96813ae6756ed68157d32ba31b9f2

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745342

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[George Hunter]

I am not sure how I go about installing the 4.15 kernel
I have used Synaptic package manager to upgrade linux-firmware to 1.157.15 and 
the kernel to 4.13.0.32.52. Neither fixed the problem, but the kernal produced 
a second Bluetooth icon on the task bar, with a different drop down menu.

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. 

[Kernel-packages] [Bug 1746324] Re: linux-aws: 4.4.0-1012.12 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


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

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

** Description changed:

  This bug is for tracking the 4.4.0-1012.12 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Wednesday, 31. January 2018 18:00 UTC

** Description changed:

  This bug is for tracking the 4.4.0-1012.12 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: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Wednesday, 31. January 2018 18:00 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1746324

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

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-1012.12 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: 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/1746324/+subscriptions

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

[Kernel-packages] [Bug 1746322] Re: linux-aws: 4.4.0-1050.59 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


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

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

** Description changed:

  This bug is for tracking the 4.4.0-1050.59 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Wednesday, 31. January 2018 18:01 UTC

** Description changed:

  This bug is for tracking the 4.4.0-1050.59 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: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Wednesday, 31. January 2018 18: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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1746322

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

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

Bug description:
  This bug is for tracking the 4.4.0-1050.59 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: 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/1746322/+subscriptions

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

[Kernel-packages] [Bug 1746562] [NEW] segfaults/unusable system with 4.13 kernel under VMware

[Dan Streetman]

Public bug reported:

[impact]

Running the 4.4 kernel, VMware guests were operating ok; then after an
upgrade to the HWE 4.13 kernel and guest reboot, some of the VMware
guests report errors and most of their userspace programs randomly
segfault.  The system is unusable.

The kernel log shows many WARNINGs such as:

[0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:340
 fpu__init_system_xstate+0x538/0x87d
...
[1.560428] WARNING: CPU: 0 PID: 95 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:373
 fpu__clear+0xf6/0x100
...
[1.569011] WARNING: CPU: 0 PID: 95 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:358
 __switch_to+0x50f/0x530
...etc...

Program segfaults appear such as:
[  109.399376] gnome-screensav[2575]: segfault at 0 ip 7efc58809f5e sp 
7ffd54133380 error 6 in libxcb.so.1.1.0[7efc5880+21000]
[  118.647544] lsb_release[2809]: segfault at 7fc1d909a700 ip 7fc1d8fe5730 
sp 7fff83052f10 error 4 in libm-2.23.so[7fc1d8f8+108000]
[  719.675965] unity-greeter[3868]: segfault at 7f0c0d0f7940 ip 
7f0c2d069275 sp 7ffd68b21808 error 4 in 
libm-2.23.so[7f0c2d046000+108000]
[  746.783766] dbus-daemon[4063]: segfault at ff18 ip 
7f95d82bc29d sp 7ffd0f7cf400 error 5 in 
libdbus-1.so.3.14.6[7f95d8288000+4a000]
[  940.161586] unity-settings-[4393]: segfault at 8 ip 7fbe83129aaa sp 
7ffdd7b29a10 error 4 in libpower.so[7fbe8311a000+19000]
[ 1007.871238] traps: grep[4553] general protection ip:7f92bf1941c8 
sp:7fff7a57c648 error:0 in libdl-2.23.so[7f92bf193000+3000]

[Test Case]

This was reported to me, so I can't directly reproduce it; but the
reporter has almost 2000 VMware guests total, and this happens only on
around 50 of those.  It's unclear what specific configuration is causing
this, but reverting affected systems back to the 4.4 kernel "fixes" the
problem.

[regression potential]

The fix for this is not known yet; unknown regression potential
currently.

[other info]

Booting with the "nopti" kernel parameter does not help.

This may be related/sameas debian bug 86:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=86

Looking upstream, possibly commit
d5c8028b4788f62b31fb79a331b3ad3e041fa366 may help:

commit d5c8028b4788f62b31fb79a331b3ad3e041fa366
Author: Eric Biggers 
Date:   Sat Sep 23 15:00:09 2017 +0200

x86/fpu: Reinitialize FPU registers if restoring FPU state fails

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: linux (Ubuntu Artful)
 Importance: High
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  segfaults/unusable system with 4.13 kernel under VMware

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

Bug description:
  [impact]

  Running the 4.4 kernel, VMware guests were operating ok; then after an
  upgrade to the HWE 4.13 kernel and guest reboot, some of the VMware
  guests report errors and most of their userspace programs randomly
  segfault.  The system is unusable.

  The kernel log shows many WARNINGs such as:

  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:340
 fpu__init_system_xstate+0x538/0x87d
  ...
  [1.560428] WARNING: CPU: 0 PID: 95 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:373
 fpu__clear+0xf6/0x100
  ...
  [1.569011] WARNING: CPU: 0 PID: 95 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:358
 __switch_to+0x50f/0x530
  ...etc...

  Program segfaults appear such as:
  [  109.399376] gnome-screensav[2575]: segfault at 0 ip 7efc58809f5e sp 
7ffd54133380 error 6 in libxcb.so.1.1.0[7efc5880+21000]
  [  118.647544] lsb_release[2809]: segfault at 7fc1d909a700 ip 
7fc1d8fe5730 sp 7fff83052f10 error 4 in 
libm-2.23.so[7fc1d8f8+108000]
  [  719.675965] unity-greeter[3868]: segfault at 7f0c0d0f7940 ip 
7f0c2d069275 sp 7ffd68b21808 error 4 in 
libm-2.23.so[7f0c2d046000+108000]
  [  746.783766] dbus-daemon[4063]: 

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: New => In Progress

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

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13


  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048 
  [78592.995985] NUMA 
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1 
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 
 
  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10 
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028 
  [78592.996642] GPR12:  c7a8d480  
 
  [78592.996642] GPR16:    
 
  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98 
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0 
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190 
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        
 
  [78592.997664]        
 
  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780] 
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to other CPUs
  [78594.01029

  Steps to reproduce :
  

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  sleep 10
  cd ../fuzzer
  make
  sleep 10

  echo 0 > /proc/sys/kernel/nmi_watchdog
  echo 2 > /proc/sys/kernel/perf_event_paranoid
  echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
  ./perf_fuzzer -r 1492143527

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

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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

[Yasmin Beatriz Alves da Silva]

Ok Christian I'll just send the patches here then. Let me know if you
need something.

** Patch added: "qemu-2.5_hypercalls_backport.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712803/+attachment/5046479/+files/qemu-2.5_hypercalls_backport.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/1712803

Title:
  spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe
  kernel

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in qemu source package in Xenial:
  Triaged

Bug description:
  kernel: 4.10.0-33.37~16.04.1

  I think this issue was introduced by the old qemu version (similar
  issue was spotted on Xenial before), will need to investigate this
  further.

  
  qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin 
-display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1
  FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588
  FAIL: hypercall: h_page_init: h_zero_page
  FAIL: hypercall: h_page_init: h_copy_page
  FAIL: hypercall: h_page_init: h_copy_page+h_zero_page
  FAIL: hypercall: h_page_init: h_zero_page unaligned dst
  FAIL: hypercall: h_page_init: h_copy_page unaligned src
  XFAIL: hypercall: h_random: h-call available

  SUMMARY: 9 tests, 8 unexpected failures, 1 expected failures

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Jiri Horky]

Hi Dan,

to answer your questions:
1) Yes, it was full output before next "waiting for..." message
2) If I leave the box running (and stops generating the load), it actually does 
not recover itself at all. It keeps outputing the "waiting for..." forever with 
the same device:

# dmesg | grep waiti
[35684.449735] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35694.529742] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35704.609742] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35714.689748] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35724.769751] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35734.849759] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35744.929763] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35755.009758] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35765.089759] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35775.169756] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35785.249761] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35795.329763] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35805.409758] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35815.489753] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35825.569749] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35835.649747] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35845.729752] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35855.809741] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35865.889736] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35875.969733] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35886.049726] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1
[35896.129717] unregister_netdevice: waiting for lo (netns 88cd026e) to 
become free. Usage count = 1

I am happy to continue testing with a new kernel.
Cheers
Jirka H.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Joseph Salisbury]

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

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => 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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  New
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:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13


  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048 
  [78592.995985] NUMA 
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1 
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 
 
  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10 
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028 
  [78592.996642] GPR12:  c7a8d480  
 
  [78592.996642] GPR16:    
 
  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98 
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0 
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190 
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        
 
  [78592.997664]        
 
  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780] 
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to other CPUs
  [78594.01029

  Steps to reproduce :
  

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  

[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

[Joseph Salisbury]

** Tags removed: needs-bisect

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1737640] Re: [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

[Stefan Bader]

I think the previous test was as valid but to be completely sure I added
an additional interface to a VM, installed ifupdown and assigned the
additional interface to ifupdown control. Using 0.12.8~17.10.1 the error
was observable and the status of the interface was incorrect. Upgrading
to 0.12.9~17.10.1, ifup and ifdown worked correctly.

** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

Title:
  [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Invalid
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Won't Fix
Status in ubuntu-fan source package in Artful:
  Fix Committed
Status in ubuntu-fan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * This bug effects anyone deploying LXD with juju on a machine with
  interfaces configured as IP/mask. Since this is a very common use
  case, SRU is needed.

  [Test Case]

   * Detailed process can be seen at https://paste.ubuntu.com/26169937/

  [Regression Potential]

   * Potential for regression is low because of the nature of the error.
  It's just missing a case stanza for interfaces that are defined with
  IP/mask

  [Other Info]

   * Original report:

  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

  [SRU Justification]

  == Impact ==

  Due to unexpectedly passing up a non-critical error to the ifup hooks,
  this causes network interfaces to not come up.

  == Fix ==

  This was fixed in Xenial (and already forward ported to Bionic)
  effectively allowing to bring up network interfaces via ifupdown after
  installing ubuntu-fan.

  == Testcase ==

  Basic installation with ifupdown method for configuring network
  interfaces (no longer default for Artful and later). Then installing
  ubuntu-fan and either reboot or use ifdown -a && ifup -a in case of
  being logged in locally. Without the fix interfaces will not come up
  properly.

  == Regression Risk ==

  Minimal, well tested in Xenial and not impacting Artful and later if
  ifupdown is not used.

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

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

[Kernel-packages] [Bug 1746416] Re: Boston-LC:bos009:Ubuntu18.04: No /dev/disk/by-path link created for Samsung PM1725a NVMe 1.6TB and .8 TB disk drives

[Joseph Salisbury]

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

Title:
  Boston-LC:bos009:Ubuntu18.04: No /dev/disk/by-path link created for
  Samsung PM1725a NVMe 1.6TB and .8 TB disk drives

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

Bug description:
  == Comment: #1 - Application Cdeadmin 
  BMC/PNOR:
  =

  Firmware Revision : 00.37 IP address : 009.003.020.216
  Firmware Build Time : 20171201BMC MAC address : 0c:c4:7a:f4:4d:60
  PNOR Build Time : 20180117
  CPLD Version : B2.91.00

  
  Ubuntu 18.04:
  =

  
  root@bos1u1p1:~# uname -a
  Linux bos1u1p1 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 03:36:42 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  
  root@bos1u1p1:~# ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0 -> 
../../sda
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part1 -> 
../../sda1
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part2 -> 
../../sda2
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:1:0 -> 
../../sdb
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:2:0 -> 
../../sdc
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-0 -> ../../sdd
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-1 -> ../../sde
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-2 -> ../../sdf
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-3 -> ../../sdg
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-0 -> ../../sdh
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-1 -> ../../sdi
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-2 -> ../../sdj
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-3 -> ../../sdk
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-0 -> ../../sdl
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-1 -> ../../sdm
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-2 -> ../../sdn
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-3 -> ../../sdo
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-0 -> ../../sdp
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-1 -> ../../sdq
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-2 -> ../../sdr
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-3 -> ../../sds
  root@bos1u1p1:~# 

  
  Problem Description:
  =
  - I setup my Boston LC system to run with Ubuntu 18.04

  - I tried to test out Samsung PM1725a NVMe 1.6TB and .8 TB disk drives
  on Boston LC system.

  - The disk drive plugged good into the system. However, after boot the
  system did not see the disk.

  - I tried with both Samsung PM1725a NVMe 1.6TB and with .8TB disk
  drives and none of them show up.

  - This disk type plan to supporte in Boston LC system so if the system
  does not recognize it then it is an issue.

  - I checked with Joe W. my team lead and he told me to open github
  issue for further investigation.

  
  root@bos1u1p1:~# ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0 -> 
../../sda
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part1 -> 
../../sda1
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part2 -> 
../../sda2
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:1:0 -> 
../../sdb
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:2:0 -> 
../../sdc

  - If the disk is recognized then it will be
  pci-0003:01:00.0-scsi-0:2:3:0 -> ../../sdd but it's not.

  
  == Comment: #2 - Application Cdeadmin 
  --- Comment From dacng 2018-01-25 11:13:00 EDT ---
  You need to install NMVE HBA in your machine

  == Comment: #3 - Application Cdeadmin 
  --- Comment From nguyenp1 2018-01-26 15:35:40 EDT ---
  - I have NVME HBA adapter installed in the system and 2 Samsung PM1725a NVMe 
1.6TB and .8 TB disk drives  in the system.  The adapter and nvme drives show 
correctly.

  - However, the "ls -l /dev/disk/by-path" command did not show any nvme 
drives.  So it's new issue with 
  Ubuntu 18.04.  Without the PCI path the nvme disks can not be assigned to KVM 
guest.

  
  root@bos1u1p1:/dev/disk/by-path# ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root  9 Jan 26 15:19 

[Kernel-packages] [Bug 1746324] Re: linux-aws: 4.4.0-1012.12 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-1012.12 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1746322] Re: linux-aws: 4.4.0-1050.59 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1050.59 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[John Lenton]

At some point somebody will figure out how to do newton-raphson instead
of bisect.

$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311623 SMP Wed Jan 31 16:25:11 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

did _not_ work.

Can't be much further now...

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745768] Re: system hangs within 10 minutes of logging in and starting browsers

[Joseph Salisbury]

Thanks for the update, Nick.

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

Title:
  system hangs within 10 minutes of logging in and starting browsers

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I cannot run for very long under normal operational load using linux-
  image-4.13.0-32-generic without a complete system freeze (mouse no
  longer moves, keyboard no longer responsive).  I have worked around
  this by booting back into linux-image-4.13.0-31-generic which is
  working fine on my hardware even with loads of browsers up and playing
  video and everything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nick   5584 F pulseaudio
   /dev/snd/controlC0:  nick   5584 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Jan 27 19:18:43 2018
  HibernationDevice: RESUME=UUID=dae1fd50-2dc0-48b2-bd93-5823478772b6
  InstallationDate: Installed on 2014-05-29 (1339 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20ALCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-07 (112 days ago)
  dmi.bios.date: 08/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET76WW (2.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X240
  dmi.product.name: 20ALCTO1WW
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO
  klp-taint: 4097

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

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

[Kernel-packages] [Bug 1746322] Re: linux-aws: 4.4.0-1050.59 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 4.4.0-1050.59

---
linux-aws (4.4.0-1050.59) xenial; urgency=low

  * linux-aws: 4.4.0-1050.59 -proposed tracker (LP: #1746322)

  * linux-aws serial console not recognized (LP: #1746318)
- SAUCE: [aws] serial: 8250_pci: Add Amazon PCI serial device ID
- [aws] config: SERIAL_8250_NR_UARTS=4

 -- Kamal Mostafa   Wed, 24 Jan 2018 12:06:22 -0800

** Changed in: linux-aws (Ubuntu Xenial)
   Status: Confirmed => Fix Released

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1050.59 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1746318] Re: linux-aws serial console not recognized

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 4.4.0-1050.59

---
linux-aws (4.4.0-1050.59) xenial; urgency=low

  * linux-aws: 4.4.0-1050.59 -proposed tracker (LP: #1746322)

  * linux-aws serial console not recognized (LP: #1746318)
- SAUCE: [aws] serial: 8250_pci: Add Amazon PCI serial device ID
- [aws] config: SERIAL_8250_NR_UARTS=4

 -- Kamal Mostafa   Wed, 24 Jan 2018 12:06:22 -0800

** Changed in: linux-aws (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: linux-aws (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  linux-aws serial console not recognized

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Trusty:
  Fix Released
Status in linux-aws source package in Xenial:
  Fix Released

Bug description:
  In order to support serial console on some future instance types:
   - Add Amazon PCI serial device ID to 8250 driver
   - Reduce 8250 number of UART's configs down to 4

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

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

[Kernel-packages] [Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic

[Joseph Salisbury]

I'd like to perform a "Reverse" bisect to figure out what commit fixes
this bug.  We need to identify the last kernel version that had the bug,
and the first kernel version that fixed the bug.

Can you test the following kernels and report back:

v4.14 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/
v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
v4.15-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc4/

You don't have to test every kernel, just up until the first kernel that
does not have the bug.

Thanks in advance!


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

** Tags added: kernel-da-key

** Tags added: performing-bisect

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

Title:
  System freezes when starting Xorg after installing linux-
  image-4.13.0-32-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only
  after installing the latest ubuntu kernel for 17.10, linux-
  image-4.13.0-32-generic.

  Am running Xorg instead of MIR due to MIR crashing when I initially
  upgraded from 17.04 to 17.10, but that's a different problem for a
  different day. It's been running with Xorg stably for at least 2-3
  months.

  If I boot with the previous kernel version on my /boot (linux-
  image-4.13.0-25-generic), everything works fine.

  If I boot with the latest mainline kernel from the Ubuntu mainline
  repo (4.15.0), everything works.

  Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I
  am able to use the CLI and access the encrypted root filesystem, which
  is how I generated the apport repo that's attached. It's only when
  telling it to continue Normal booting that it freezes, which is why I
  suspect the problem of being Xorg.

  When the system freezes, the fan starts to spin up. I cannot switch
  virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed
  repeatedly doesn't do anything. To reboot, I have to hold the power
  button until the system powers off.

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

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

[Kernel-packages] [Bug 1746318] Re: linux-aws serial console not recognized

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 4.4.0-1012.12

---
linux-aws (4.4.0-1012.12) trusty; urgency=low

  * linux-aws: 4.4.0-1012.12 -proposed tracker (LP: #1746324)

  * linux-aws serial console not recognized (LP: #1746318)
- SAUCE: [aws] serial: 8250_pci: Add Amazon PCI serial device ID
- [aws] config: SERIAL_8250_NR_UARTS=4

 -- Kamal Mostafa   Tue, 30 Jan 2018 11:31:59 -0800

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

Title:
  linux-aws serial console not recognized

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Trusty:
  Fix Released
Status in linux-aws source package in Xenial:
  Fix Released

Bug description:
  In order to support serial console on some future instance types:
   - Add Amazon PCI serial device ID to 8250 driver
   - Reduce 8250 number of UART's configs down to 4

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

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

[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0

[Joseph Salisbury]

Can you see if this bug has been fixed in the latest mainline kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/

If the bug still exists in 4.15, we can bisect between 4.12 and 4.13.

** Tags added: kernel-da-key needs-bisect

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

Title:
  mount.cifs stopped working with protocol version != 1.0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Xenial installation after upgrading to the HWE 4.13.0-32-generic
  kernel it is not possible to use mount.cifs with -o vers=x.y different
  than 1.0.

  Steps to reproduce:
  1. Setup a local Samba share.
  2. Run:
  mount.cifs -o user=,vers=2.0 //localhost/theshare/ /mnt/theshare
  (please note that not specifying the vers= option results in using protocol 
SMB2.1 which also results in the error).
  3. This may be repeated for the following versions: 2.0, 2.1, 3.0.

  Expected result:
  The share gets mounted at /mnt/theshare.

  Actual result:
  The share is not mounted, this gets printed in the console (and in dmesg):
  [  232.439162] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2

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

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

[Kernel-packages] [Bug 1729051] Re: dkms mkdeb fails: Can't find package

[Chris J Arges]

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

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

Title:
  dkms mkdeb fails: Can't find package

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Artful:
  New
Status in dkms package in Debian:
  New

Bug description:
  For some reason, the Debian version of dkms mkdeb tries to generate a
  .deb package with the current arch as a suffix in its name, instead of
  'all'. However, since the control file wasn't properly set up, the
  .deb file will have the 'all' suffix and dkms mkdeb will fail.

  This bug is also present in Ubuntu. I added a patch to the original
  Debian bug report, here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558

  but since the original bug report was made about a year ago and nobody
  cared, I'm hoping that someone will at least fix this for Ubuntu.

  The patch looks like this:

  --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:40:41.690069116 -0300
  +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:41:12.137973994 -0300
  @@ -6,6 +6,6 @@
   Standards-Version: 3.8.1

   Package: DEBIAN_PACKAGE-dkms
  -Architecture: all
  +Architecture: DEBIAN_BUILD_ARCH
   Depends: dkms (>= 1.95), ${misc:Depends}
   Description: DEBIAN_PACKAGE driver in DKMS format.

  I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.

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

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

[Kernel-packages] [Bug 1746322] Re: linux-aws: 4.4.0-1050.59 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-xenial

** Tags removed: block-proposed

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1050.59 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1744988] Re: time drifting on linux-hwe kernels

[Joseph Salisbury]

Sorry, you can ignore the request in comment #5.  I missed all the
kenrels you tested in the bug description.

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

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

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

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

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

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

Title:
  time drifting on linux-hwe kernels

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

Bug description:
  We observe NTP time drift on two servers running hwe kernels in
  Xenial. A few weeks ago we wanted to switch from 4.4 to 4.10. When
  rebooting the servers to the 4.10 kernel we were seeing a big time
  offset within minutes after booting. Despite running ntpd, it would
  not keep up and the offset stayed and kept growing over t.

  Rebooting back into the 4.4 at the time we immediatly noticed the time
  stayed normal. Over time I have tested about a dozen versions making
  me think something has been introduced in kernel 4.10 that makes the
  clock go out of sync.

  So what do we observe?

  After 1 min uptime:
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *ntp4.bit.nl .PPS.1 u5   1670.497  100.084  81.382
  +ntp1.bit.nl 193.0.0.229  2 u8   1670.603   93.241  70.643
  +ntp2.bit.nl 193.67.79.2022 u8   1670.582   93.218  70.674
  +ntp3.bit.nl 193.79.237.142 u9   1670.781   90.488  70.574

  A couple of minutes later (and also hours/days, the offset just keeps
  growing over time)

   remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *ntp4.bit.nl .PPS.1 u   13   16  3770.447  400.198 151.335
  +ntp1.bit.nl 193.0.0.229  2 u   13   16  3770.313  400.561 151.339
  +ntp2.bit.nl 193.67.79.2022 u   13   16  3770.517  400.445 151.398
  +ntp3.bit.nl 193.79.237.142 u   12   16  3770.934  402.013 151.384

  As mentioned I tested about a dozen of kernels and I thought I got it
  pinpointed to a specific release when the drifting got introduced,
  4.10rc1. Below the test results of the kernels I have tested up till
  today:

  Tested: 4.4.0-112-generic: not affected
  Tested: 4.8.0-41-generic: not affected
  Tested: 4.8.0-58-generic : not affected
  Tested: 4.9.0 mainline: not affected
  Tested: 4.9.66 mainline: not affected
  Tested: 4.10-rc1 mainline: affected
  Tested: 4.10 mainline: affected
  Tested: 4.10.0-38-generic: affected
  Tested: 4.10.0-40-generic: affected
  Tested: 4.13.0-16-generic: affected
  Tested: 4.13.0-31-generic: affected
  Tested: 4.14.3 mainline: affected
  Tested: 4.15-rc1 mainline: affected

  When I was about to file this bugreport about an hour ago I noticed
  4.15-rc9 was present and thought I gave it a go to make sure I really
  tested the latest version. And while running it over an hour now it
  stable.

  Mostl likely the following from the changelog is related the issue we
  are having:

  Len Brown (3):
x86/tsc: Future-proof native_calibrate_tsc()
x86/tsc: Fix erroneous TSC rate on Skylake Xeon
x86/tsc: Print tsc_khz, when it differs from cpu_khz

  Both servers that are having issues on our side our equipped with the
  following cpu:

  Cpu Model (from /proc/cpuinfo)
  vendor_id : GenuineIntel
  cpu family: 6
  model : 85
  model name: Intel(R) Xeon(R) Gold 6136 CPU @ 3.00GHz

  Standard information as requested:
  1:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  2: 
  root@bit-host6:~# apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.13.0.31.51
Candidate: 4.13.0.31.51

  3: Stable time

  4: A big time offset

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

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

[Kernel-packages] [Bug 1746492] Re: Ubuntu system hangs suddenly

[Joseph Salisbury]

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

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

Title:
  Ubuntu system hangs suddenly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I ran Vlc media player and when I seek in the video, it
  struck automatically, left me to restart again the laptop.

  Also sometimes it happens with other applications too.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jai1870 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 31 16:36:56 2018
  InstallationDate: Installed on 2018-01-25 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
hostname=UUID=6c63ec8a-6551-4f89-a23e-62761ef7c873 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088D110459160:rvnHewlett-Packard:rn183F:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 088D110459160
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1746519] Re: package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  After executing:
  sudo apt-get autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
linux-headers-4.13.0-21 linux-headers-4.13.0-21-generic
linux-image-4.13.0-21-generic linux-image-extra-4.10.0-42-generic
linux-image-extra-4.13.0-21-generic
  0 upgraded, 0 newly installed, 5 to remove and 10 not upgraded.
  7 not fully installed or removed.
  After this operation, 474 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 297436 files and directories currently installed.)
  Removing linux-headers-4.13.0-21-generic (4.13.0-21.24) ...
  Removing linux-headers-4.13.0-21 (4.13.0-21.24) ...
  Removing linux-image-extra-4.13.0-21-generic (4.13.0-21.24) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.13.0-21-generic /boot/vmlinuz-4.13.0-21-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-21-generic 
/boot/vmlinuz-4.13.0-21-generic

  
  dkms process is stuck and does not end

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2144 F pulseaudio
mvh2739 F pulseaudio
   /dev/snd/controlC0:  gdm2144 F pulseaudio
mvh2739 F pulseaudio
  Date: Wed Jan 31 14:41:24 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-04-15 (291 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6540
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic 
root=UUID=aa4075ec-5629-4eb4-9fa7-6e90dd0cd274 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  SourcePackage: linux
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to artful on 2018-01-01 (29 days ago)
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0725FP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd02/02/2015:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

[Joseph Salisbury]

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

Title:
  [Asus K501UQ] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When Ubuntu wakes up after suspend the touchpad doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  szx1685 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 31 05:40:49 2018
  InstallationDate: Installed on 2018-01-23 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=04181349-688b-425f-899c-822fcf6a409b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UQ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UQ.300:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnK501UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K501UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1746513] Re: lot of rx-dropped packets on bridge interface

[Joseph Salisbury]

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

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

Title:
  lot of rx-dropped packets on bridge interface

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  we see a lot of dropped rx packets on almost all bridge interface.
  Related physical interfaces has much less dropped rx packets.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  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'
  Date: Wed Jan 31 14:11:52 2018
  HibernationDevice: RESUME=UUID=f507eae9-a10f-4b3b-a097-e5405ee3d717
  InstallationDate: Installed on 2015-01-29 (1098 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=404057dd-e35f-4325-be5f-d9ce1b199660 ro ipv6.disable=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-10-26 (461 days ago)
  WifiSyslog:
   
  dmi.chassis.type: 23
  dmi.modalias: dmi:bvn:bvr:bd:svn:pn:pvr:rvn:rn:rvr:cvn:ct23:cvr:

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

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

[Kernel-packages] [Bug 1746551] Re: GPU HANG since package update

[Joseph Salisbury]

Does this bug go away if you boot back into the prior kernel version?

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

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

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

Title:
  GPU HANG since package update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since today, I get occasional crashes freeze-ups of the GUI, followed
  by a restart of the X server. In syslog, I find entries like the ones
  below.

  The system was running stably before, so this is a new phenomenon...
  could this be related to the recent kernel updates?

  Obviously, this leads to data loss...

  Jan 31 11:22:42 TP kernel: [14282.025287] [drm] GPU HANG: ecode 
9:0:0x86dd, in Xorg [870], reason: Hang on rcs0, action: reset
  Jan 31 11:22:42 TP kernel: [14282.025322] drm/i915: Resetting chip after gpu 
hang
  Jan 31 11:22:42 TP kernel: [14282.025486] [drm] RC6 on
  Jan 31 11:22:46 TP kernel: [14285.246630] asynchronous wait on fence 
i915:kwin_x11[1506]/1:bd84 timed out
  Jan 31 11:22:50 TP kernel: [14290.046737] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:22:50 TP kernel: [14290.046964] [drm] RC6 on


  Jan 31 11:23:03 TP kernel: [14303.006629] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:03 TP kernel: [14303.006806] [drm] RC6 on


  Jan 31 11:23:11 TP kernel: [14311.006544] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:11 TP kernel: [14311.006715] [drm] RC6 on


  Jan 31 11:23:19 TP kernel: [14319.006432] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:19 TP kernel: [14319.006606] [drm] RC6 on


  Jan 31 11:23:20 TP org.kde.kuiserver[1425]: kuiserver: Fatal IO error: client 
killed  

  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Checking for pam module  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Got pam-login param  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Waiting for hash on 14-  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: waitingForEnvironment on: 18 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client connected 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client disconnected  


  Jan 31 11:23:20 TP org.kde.KScreen[1425]: The X11 connection broke (error 1). 
Did the X11 server die?
  Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
  Jan 31 11:23:20 TP org.kde.kglobalaccel[1425]: The X11 connection broke 
(error 1). Did the X11 server die?
  Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
  Jan 31 11:23:20 TP org.kde.Spectacle[1425]: The X11 connection broke (error 
1). Did the X11 server die?
  Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
  Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]:   after 2218 requests 
(2218 known processed) with 0 events remaining.
  Jan 31 11:23:21 TP sddm[847]: QProcess: Destroyed while process 
("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
  Jan 31 11:23:21 TP systemd[1]: Stopping User Manager for UID 1000...
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Default.
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Basic System.
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Paths.
  Jan 31 11:23:21 TP 

[Kernel-packages] [Bug 1744988] [NEW] time drifting on linux-hwe kernels

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

We observe NTP time drift on two servers running hwe kernels in Xenial.
A few weeks ago we wanted to switch from 4.4 to 4.10. When rebooting the
servers to the 4.10 kernel we were seeing a big time offset within
minutes after booting. Despite running ntpd, it would not keep up and
the offset stayed and kept growing over t.

Rebooting back into the 4.4 at the time we immediatly noticed the time
stayed normal. Over time I have tested about a dozen versions making me
think something has been introduced in kernel 4.10 that makes the clock
go out of sync.

So what do we observe?

After 1 min uptime:
 remote   refid  st t when poll reach   delay   offset  jitter
==
*ntp4.bit.nl .PPS.1 u5   1670.497  100.084  81.382
+ntp1.bit.nl 193.0.0.229  2 u8   1670.603   93.241  70.643
+ntp2.bit.nl 193.67.79.2022 u8   1670.582   93.218  70.674
+ntp3.bit.nl 193.79.237.142 u9   1670.781   90.488  70.574

A couple of minutes later (and also hours/days, the offset just keeps
growing over time)

 remote   refid  st t when poll reach   delay   offset  jitter
==
*ntp4.bit.nl .PPS.1 u   13   16  3770.447  400.198 151.335
+ntp1.bit.nl 193.0.0.229  2 u   13   16  3770.313  400.561 151.339
+ntp2.bit.nl 193.67.79.2022 u   13   16  3770.517  400.445 151.398
+ntp3.bit.nl 193.79.237.142 u   12   16  3770.934  402.013 151.384

As mentioned I tested about a dozen of kernels and I thought I got it
pinpointed to a specific release when the drifting got introduced,
4.10rc1. Below the test results of the kernels I have tested up till
today:

Tested: 4.4.0-112-generic: not affected
Tested: 4.8.0-41-generic: not affected
Tested: 4.8.0-58-generic : not affected
Tested: 4.9.0 mainline: not affected
Tested: 4.9.66 mainline: not affected
Tested: 4.10-rc1 mainline: affected
Tested: 4.10 mainline: affected
Tested: 4.10.0-38-generic: affected
Tested: 4.10.0-40-generic: affected
Tested: 4.13.0-16-generic: affected
Tested: 4.13.0-31-generic: affected
Tested: 4.14.3 mainline: affected
Tested: 4.15-rc1 mainline: affected

When I was about to file this bugreport about an hour ago I noticed
4.15-rc9 was present and thought I gave it a go to make sure I really
tested the latest version. And while running it over an hour now it
stable.

Mostl likely the following from the changelog is related the issue we
are having:

Len Brown (3):
  x86/tsc: Future-proof native_calibrate_tsc()
  x86/tsc: Fix erroneous TSC rate on Skylake Xeon
  x86/tsc: Print tsc_khz, when it differs from cpu_khz

Both servers that are having issues on our side our equipped with the
following cpu:

Cpu Model (from /proc/cpuinfo)
vendor_id   : GenuineIntel
cpu family  : 6
model   : 85
model name  : Intel(R) Xeon(R) Gold 6136 CPU @ 3.00GHz

Standard information as requested:
1:
Description:Ubuntu 16.04.3 LTS
Release:16.04

2: 
root@bit-host6:~# apt-cache policy linux-image-generic-hwe-16.04
linux-image-generic-hwe-16.04:
  Installed: 4.13.0.31.51
  Candidate: 4.13.0.31.51

3: Stable time

4: A big time offset

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: Incomplete


** Tags: patch
-- 
time drifting on linux-hwe kernels
https://bugs.launchpad.net/bugs/1744988
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 1746322] Re: linux-aws: 4.4.0-1050.59 -proposed tracker

[Brad Figg]

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

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1050.59 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

[Joseph Borg]

@Mario,

I've not done the upgrade yet but I can confirm I've already tried all
ports on the laptop and they all behave in exactly the same way.

I've tried several USB storage devices, a USB eth NIC and 2 different
TB3 GFX enclosures.

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

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1744296] Re: After ifdown on underlay interface ifup fails with 'already configured'

[Stefan Bader]

** Changed in: ubuntu-fan (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-fan (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-fan (Ubuntu)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  After ifdown on underlay interface ifup fails with 'already
  configured'

Status in ubuntu-fan package in Ubuntu:
  In Progress

Bug description:
  With following setup:
  <...>
  2: ens192:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether 00:50:56:86:31:a8 brd ff:ff:ff:ff:ff:ff
  inet 10.245.40.80/18 brd 10.245.63.255 scope global ens192
 valid_lft forever preferred_lft forever
  inet6 fe80::250:56ff:fe86:31a8/64 scope link 
 valid_lft forever preferred_lft forever
  <...>
  4: fan-254:  mtu 1450 qdisc noqueue state UP 
group default qlen 1000
  link/ether 8a:f3:53:e5:11:37 brd ff:ff:ff:ff:ff:ff
  inet 254.161.64.1/8 scope global fan-254
 valid_lft forever preferred_lft forever
  inet6 fe80::88f3:53ff:fee5:1137/64 scope link 
 valid_lft forever preferred_lft forever
  5: ftun0:  mtu 1450 qdisc noqueue master 
fan-254 state UNKNOWN group default qlen 1000
  link/ether 8a:f3:53:e5:11:37 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::88f3:53ff:fee5:1137/64 scope link 
 valid_lft forever preferred_lft forever

  
  Doing ifdown ens192; ifup ens192 results in an error:
  # ifdown ens192; echo $?; ifup ens192; echo $?
  Killed old client process
  <... isc-dhcp stuff ...>
  0
  <... isc-dhcp stuff ...>
  /usr/sbin/fanctl: fan-254: already configured
  /usr/sbin/fanctl: /etc/network/fan:40 10.245.0.0/18 254.0.0.0/8  -- failed 
err=1
  run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1
  Failed to bring up ens192.
  1

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

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

[Kernel-packages] [Bug 1746322] Re: linux-aws: 4.4.0-1050.59 -proposed tracker

[Steve Beattie]

No USN needed

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

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1050.59 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  GPU HANG since package update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since today, I get occasional crashes freeze-ups of the GUI, followed
  by a restart of the X server. In syslog, I find entries like the ones
  below.

  The system was running stably before, so this is a new phenomenon...
  could this be related to the recent kernel updates?

  Obviously, this leads to data loss...

  Jan 31 11:22:42 TP kernel: [14282.025287] [drm] GPU HANG: ecode 
9:0:0x86dd, in Xorg [870], reason: Hang on rcs0, action: reset
  Jan 31 11:22:42 TP kernel: [14282.025322] drm/i915: Resetting chip after gpu 
hang
  Jan 31 11:22:42 TP kernel: [14282.025486] [drm] RC6 on
  Jan 31 11:22:46 TP kernel: [14285.246630] asynchronous wait on fence 
i915:kwin_x11[1506]/1:bd84 timed out
  Jan 31 11:22:50 TP kernel: [14290.046737] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:22:50 TP kernel: [14290.046964] [drm] RC6 on


  Jan 31 11:23:03 TP kernel: [14303.006629] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:03 TP kernel: [14303.006806] [drm] RC6 on


  Jan 31 11:23:11 TP kernel: [14311.006544] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:11 TP kernel: [14311.006715] [drm] RC6 on


  Jan 31 11:23:19 TP kernel: [14319.006432] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:19 TP kernel: [14319.006606] [drm] RC6 on


  Jan 31 11:23:20 TP org.kde.kuiserver[1425]: kuiserver: Fatal IO error: client 
killed  

  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Checking for pam module  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Got pam-login param  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Waiting for hash on 14-  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: waitingForEnvironment on: 18 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client connected 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client disconnected  


  Jan 31 11:23:20 TP org.kde.KScreen[1425]: The X11 connection broke (error 1). 
Did the X11 server die?
  Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
  Jan 31 11:23:20 TP org.kde.kglobalaccel[1425]: The X11 connection broke 
(error 1). Did the X11 server die?
  Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
  Jan 31 11:23:20 TP org.kde.Spectacle[1425]: The X11 connection broke (error 
1). Did the X11 server die?
  Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
  Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]:   after 2218 requests 
(2218 known processed) with 0 events remaining.
  Jan 31 11:23:21 TP sddm[847]: QProcess: Destroyed while process 
("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
  Jan 31 11:23:21 TP systemd[1]: Stopping User Manager for UID 1000...
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Default.
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Basic System.
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Paths.
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Sockets.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  

[Kernel-packages] [Bug 1746324] Re: linux-aws: 4.4.0-1012.12 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-trusty

** Tags removed: block-proposed

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1012.12 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1746551] [NEW] GPU HANG since package update

[P]

Public bug reported:

Since today, I get occasional crashes freeze-ups of the GUI, followed by
a restart of the X server. In syslog, I find entries like the ones
below.

The system was running stably before, so this is a new phenomenon...
could this be related to the recent kernel updates?

Obviously, this leads to data loss...

Jan 31 11:22:42 TP kernel: [14282.025287] [drm] GPU HANG: ecode 9:0:0x86dd, 
in Xorg [870], reason: Hang on rcs0, action: reset
Jan 31 11:22:42 TP kernel: [14282.025322] drm/i915: Resetting chip after gpu 
hang
Jan 31 11:22:42 TP kernel: [14282.025486] [drm] RC6 on
Jan 31 11:22:46 TP kernel: [14285.246630] asynchronous wait on fence 
i915:kwin_x11[1506]/1:bd84 timed out
Jan 31 11:22:50 TP kernel: [14290.046737] drm/i915: Resetting chip after gpu 
hang
 
Jan 31 11:22:50 TP kernel: [14290.046964] [drm] RC6 on  

  
Jan 31 11:23:03 TP kernel: [14303.006629] drm/i915: Resetting chip after gpu 
hang
 
Jan 31 11:23:03 TP kernel: [14303.006806] [drm] RC6 on  

  
Jan 31 11:23:11 TP kernel: [14311.006544] drm/i915: Resetting chip after gpu 
hang
 
Jan 31 11:23:11 TP kernel: [14311.006715] [drm] RC6 on  

  
Jan 31 11:23:19 TP kernel: [14319.006432] drm/i915: Resetting chip after gpu 
hang
 
Jan 31 11:23:19 TP kernel: [14319.006606] [drm] RC6 on  

  
Jan 31 11:23:20 TP org.kde.kuiserver[1425]: kuiserver: Fatal IO error: client 
killed  

Jan 31 11:23:20 TP sddm[847]: kwalletd5: Checking for pam module

  
Jan 31 11:23:20 TP sddm[847]: kwalletd5: Got pam-login param

  
Jan 31 11:23:20 TP sddm[847]: kwalletd5: Waiting for hash on 14-

  
Jan 31 11:23:20 TP sddm[847]: kwalletd5: waitingForEnvironment on: 18   

  
Jan 31 11:23:20 TP sddm[847]: kwalletd5: client connected   

  
Jan 31 11:23:20 TP sddm[847]: kwalletd5: client disconnected

  
Jan 31 11:23:20 TP org.kde.KScreen[1425]: The X11 connection broke (error 1). 
Did the X11 server die?
Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
Jan 31 11:23:20 TP org.kde.kglobalaccel[1425]: The X11 connection broke (error 
1). Did the X11 server die?
Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
Jan 31 11:23:20 TP org.kde.Spectacle[1425]: The X11 connection broke (error 1). 
Did the X11 server die?
Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]:   after 2218 requests 
(2218 known processed) with 0 events remaining.
Jan 31 11:23:21 TP sddm[847]: QProcess: Destroyed while process 
("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
Jan 31 11:23:21 TP systemd[1]: Stopping User Manager for UID 1000...
Jan 31 11:23:21 TP systemd[1342]: Stopped target Default.
Jan 31 11:23:21 TP systemd[1342]: Stopped target Basic System.
Jan 31 11:23:21 TP systemd[1342]: Stopped target Paths.
Jan 31 11:23:21 TP systemd[1342]: Stopped target Sockets.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pascal10623 F pulseaudio
CurrentDesktop: KDE
Date: Wed Jan 31 17:48:58 2018
HibernationDevice: RESUME=UUID=cb84af7b-bfe3-432a-a69a-6a448b1f667a
InstallationDate: Installed on 2017-12-01 (60 days 

[Kernel-packages] [Bug 1746324] Re: linux-aws: 4.4.0-1012.12 -proposed tracker

[Steve Beattie]

No USN needed.

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

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1012.12 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

[Sergey Zolotarev]

This patch worked for me with v4.15 kernel:

https://paste.ubuntu.com/26496011/

I basically found the old patch and added an entry for K501UQ there. The
author changed his code from using DMI_PRODUCT_NAME to DMI_CHASSIS_TYPE
since then but that doesn't work for my laptop apparently.

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

Title:
  [Asus K501UQ] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When Ubuntu wakes up after suspend the touchpad doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  szx1685 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 31 05:40:49 2018
  InstallationDate: Installed on 2018-01-23 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=04181349-688b-425f-899c-822fcf6a409b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UQ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UQ.300:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnK501UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K501UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[Joseph Salisbury]

Eventually one of these test kernels should work and narrow down the
bisect :-)

I built the next test kernel, up to the following commit:
d86c4d8ef31b3d99c681c859cb4e936dafc2d7a4

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745342

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Stefan Bader]

** Changed in: ubuntu-fan (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-fan (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-fan (Ubuntu)
 Assignee: (unassigned) => Stefan Bader (smb)

-- 
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:
  New
Status in chrony package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  New
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:
  New
Status in ifmetric package in Ubuntu:
  New
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  New
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:
  New
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:
  In Progress
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:
  New
Status in vzctl package in Ubuntu:
  New
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: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1742712] Re: package removal leave scripts that fail lacking the binaries

[Stefan Bader]

That might be the usual problem with packages removed but not using the
purge option. (leaving things in rC state). Would not be the first time
this causes issues generally speaking. But the ifupdown hook might get
improved. Not that it will likely be used post Xenial with systemd-
networkd taking over.

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

Title:
  package removal leave scripts that fail lacking the binaries

Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  Today I saw on IRC this reported:

  raub@desktop:~$ sudo ifdown --force br0 && sudo brctl delbr br0
  /etc/network/if-down.d/ubuntu-fan: 29: /etc/network/if-down.d/ubuntu-fan: 
/usr/sbin/fanctl: not found
  run-parts: /etc/network/if-down.d/ubuntu-fan exited with return code 127
  bridge br0 doesn't exist; can't delete it

  I checked what that could be and found an interesting case.

  When ubuntu-fan is installed all is fine, we have a hook
/etc/network/if-down.d/ubuntu-fan
  and a binary
/usr/sbin/fanctl

  But if a user removed the package, then we get into trouble.
  The hook is in /etc and therefore by default considered to be a conffile.

  Therefore we only have the hook left which fails by:
/usr/sbin/fanctl: not found

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

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

[Kernel-packages] [Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic

[SkySurfer]

I was able to gather the output by disabling plymoth screen:

[   61.359631] NMI watchdog: Watchdog detected hard LOCKUP on cpu 4
[   64.063967] watchdog: BUG: soft lockup - CPU6 stuck for 22s! [snap-exec:6105]
[   64.063968] watchdog: BUG: soft lockup - CPU7 stuck for 22s! [systemd:6412]
[   80.059966] watchdog: BUG: soft lockup - CPU0 stuck for 22s! [kworker/0::0:3]
[   84.823028] NMI watchdog: Watchdog detected hard LOCKUP on cpu 5

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

Title:
  System freezes when starting Xorg after installing linux-
  image-4.13.0-32-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only
  after installing the latest ubuntu kernel for 17.10, linux-
  image-4.13.0-32-generic.

  Am running Xorg instead of MIR due to MIR crashing when I initially
  upgraded from 17.04 to 17.10, but that's a different problem for a
  different day. It's been running with Xorg stably for at least 2-3
  months.

  If I boot with the previous kernel version on my /boot (linux-
  image-4.13.0-25-generic), everything works fine.

  If I boot with the latest mainline kernel from the Ubuntu mainline
  repo (4.15.0), everything works.

  Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I
  am able to use the CLI and access the encrypted root filesystem, which
  is how I generated the apport repo that's attached. It's only when
  telling it to continue Normal booting that it freezes, which is why I
  suspect the problem of being Xorg.

  When the system freezes, the fan starts to spin up. I cannot switch
  virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed
  repeatedly doesn't do anything. To reboot, I have to hold the power
  button until the system powers off.

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

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

[Kernel-packages] [Bug 1745118] Re: Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on Xenial / Artful

[Damien Buhl]

It looks like the same issue occurs on Intel Core 2 Duo CPU P9400 @
2.40Ghz with i686 Xubuntu with Kernel linux-image-4.13.0-32-generic.

It loops directly after grub before any kernel print out back to bios.

It boots with the previous kernel 4.10.0-42-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/1745118

Title:
  Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on
  Xenial / Artful

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Some SRU testing node cannot boot with the latest 32bit 4.13 linux-hwe
  kernel.

  Take node "fozzie"(Dell PowerEdge R320) for example, it works with
  4.13.0-21.24~16.04.1 but not 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel
  on Xenial.

  From the BMC console, I can see the grub menu on boot and after that
  it will drop into a boot loop.

  This can be reproduced on Artful 4.13 as well.

  Note that this kernel works for some of the node in our test pool
  (Intel SDP - Denlow)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24~16.04.1
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Wed Jan 24 08:49:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 09:17 seq
   crw-rw 1 root audio 116, 33 Jan 24 09:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-21-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746324] Re: linux-aws: 4.4.0-1012.12 -proposed tracker

[Brad Figg]

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

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1012.12 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1746322] Re: linux-aws: 4.4.0-1050.59 -proposed tracker

[Brad Figg]

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

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1050.59 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1746324] Re: linux-aws: 4.4.0-1012.12 -proposed tracker

[Brad Figg]

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

** Tags added: regression-testing-passed

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1012.12 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1746322] Re: linux-aws: 4.4.0-1050.59 -proposed tracker

[Brad Figg]

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

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1050.59 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1746324] Re: linux-aws: 4.4.0-1012.12 -proposed tracker

[Brad Figg]

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

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1012.12 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1745959] Re: linux: 3.2.0-133.179 -proposed tracker

[Kleber Sacilotto de Souza]

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

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

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

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

Title:
  linux: 3.2.0-133.179 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  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: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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