[Kernel-packages] [Bug 1732686] Re: Asus Fx553VD - Keyboard LED backlight controls are not working # kernel-bug-reported-upstream

[R.Erol]

** Summary changed:

- Asus Fx553VD - Keyboard LED backlight controls are not working
+ Asus Fx553VD - Keyboard LED backlight controls are not working # 
kernel-bug-reported-upstream

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

Title:
  Asus Fx553VD - Keyboard LED backlight controls are not working #
  kernel-bug-reported-upstream

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi , i'm using this laptop with it's latest bios (V303 -
  https://www.asus.com/Laptops/ASUS-FX553VD/HelpDesk_BIOS/ )

  Kernel : 4.14.0-041400-generic x86_64

  I can't control keyboard LED backlight level with it's dedicated FN
  keys or anything else. FN keys are recognized by Linux Mint 18.2 and
  Ubuntu 16.04 but pressing them have no effect.

  Kernels from 4.10 to 4.14 are the same on that regard.

  And also i have these errors on "inxi -F && dmesg | grep -i error"

  [0.031175] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20170728/dswload-378)
  [0.040665] ACPI Error: 1 table load failures, 10 successful 
(20170728/tbxfload-246)
  [0.506425] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
  [1.694527] RAS: Correctable Errors collector initialized.
  [9.833145] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

  I'm not a developer but only a user. So if i opened that issue to the
  wrong place can you point me the correct place to open it?

  Thanks.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-10-22 (24 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  Tags:  sonya
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1731269] Re: linux: 4.10.0-40.44 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-zesty

** Tags removed: block-proposed

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

Title:
  linux: 4.10.0-40.44 -proposed tracker

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

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

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

[Kernel-packages] [Bug 1731269] Re: linux: 4.10.0-40.44 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/zesty/4.10.0-40.44
/zesty-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux: 4.10.0-40.44 -proposed tracker

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

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

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

[Kernel-packages] [Bug 1732804] Re: [Zesty/Artful] On ARM64 PCIE physical function passthrough guest fails to boot

[Manoj Iyer]

** Description changed:

  [Impact]
- Passing through a physical function like the Mellanox PCIE ethernet 
controller causes the guest to fail booting, and host reports Hardware Error. 
+ Passing through a physical function like the Mellanox PCIE ethernet 
controller causes the guest to fail booting, and host reports Hardware Error.
  == Host ==
  [109920.834703] {1}[Hardware Error]: Hardware error from APEI Generic 
Hardware Error Source: 4
  [109920.842142] {1}[Hardware Error]: event severity: recoverable
  [109920.847848] {1}[Hardware Error]:  precise tstamp: 2017-11-16 23:20:05
  [109920.854385] {1}[Hardware Error]:  Error 0, type: recoverable
  [109920.860111] {1}[Hardware Error]:   section_type: PCIe error
  [109920.865718] {1}[Hardware Error]:   port_type: 0, PCIe end point
  [109920.871708] {1}[Hardware Error]:   version: 3.0
  [109920.876343] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
  [109920.882559] {1}[Hardware Error]:   device_id: :01:00.0
  [109920.888113] {1}[Hardware Error]:   slot: 0
  [109920.892285] {1}[Hardware Error]:   secondary_bus: 0x00
  [109920.897489] {1}[Hardware Error]:   vendor_id: 0x15b3, device_id: 0x1013
  [109920.904172] {1}[Hardware Error]:   class_code: 02
  [109920.909378] vfio-pci :01:00.0: aer_status: 0x0004, aer_mask: 
0x
  [109920.916675] Malformed TLP
  [109920.916678] vfio-pci :01:00.0: aer_layer=Transaction Layer, 
aer_agent=Receiver ID
  [109920.924573] vfio-pci :01:00.0: aer_uncor_severity: 0x00062010
  [109920.930736] vfio-pci :01:00.0:   TLP Header: 4a008040 0100 
0100 
  [109920.938548] vfio-pci :01:00.0: broadcast error_detected message
  [109921.965056] pcieport :00:00.0: downstream link has been reset
  [109921.965062] vfio-pci :01:00.0: broadcast mmio_enabled message
  [109921.965066] vfio-pci :01:00.0: broadcast resume message
  [109921.965070] vfio-pci :01:00.0: AER: Device recovery successful
  == Guest ==
  EFI stub: Booting Linux Kernel...
  EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services and installing virtual address map...
  [1.518252] kvm [1]: HYP mode not available
  [2.578929] mlx5_core :05:00.0: mlx5_core_set_issi:778:(pid 152): 
Failed to query ISSI err(-1) status(0) synd(0)
  [2.582424] mlx5_core :05:00.0: failed to set issi
  [2.616756] mlx5_core :05:00.0: mlx5_load_one failed with error code -1
  
  This is because, virtualization of physical functions are broken on
  systems with Maximum Payload Size bigger than 128. QDF2400 FW tries to
  maximize this setting. We have observed an MPS of 512 on QDF2400
  systems.
  
  [Fix]
  Patches are in linux-next:
- 523184972b28 vfio/pci: Virtualize Maximum Payload Size
+ cf0d53ba4947 vfio/pci: Virtualize Maximum Read Request Size
  523184972b28 vfio/pci: Virtualize Maximum Payload Size
  
  [Testing]
- With the above patches applied the guest is able to boot when PCIE physical 
function is passthrough and we don't see the errors on the host system. 
+ With the above patches applied the guest is able to boot when PCIE physical 
function is passthrough and we don't see the errors on the host system.
  == On the Guest ==
  ubuntu@ubuntu-pcitest:~$ lspci
  00:00.0 Host bridge: Red Hat, Inc. Device 0008
  00:01.0 PCI bridge: Red Hat, Inc. Device 000c
  00:01.1 PCI bridge: Red Hat, Inc. Device 000c
  00:01.2 PCI bridge: Red Hat, Inc. Device 000c
  00:01.3 PCI bridge: Red Hat, Inc. Device 000c
  00:01.4 PCI bridge: Red Hat, Inc. Device 000c
  00:01.5 PCI bridge: Red Hat, Inc. Device 000c
  01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01)
  02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01)
  03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
  04:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
  05:00.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]
  
  ubuntu@ubuntu-pcitest:~$ lsmod | grep mlx
  mlx5_core 471040 0
  devlink 36864 1 mlx5_core
  ptp 28672 1 mlx5_core
  
  [Regression Potential]
  Two patches to drivers/vfio/pci were cleanly cherry picked from linux-next 
and applied to Artful/Zesty. Tested on ARM64 QDF2400 system and no regressions 
were found.

** Description changed:

  [Impact]
  Passing through a physical function like the Mellanox PCIE ethernet 
controller causes the guest to fail booting, and host reports Hardware Error.
  == Host ==
  [109920.834703] {1}[Hardware Error]: Hardware error from APEI Generic 
Hardware Error Source: 4
  [109920.842142] {1}[Hardware Error]: event severity: recoverable
  [109920.847848] {1}[Hardware Error]:  precise tstamp: 2017-11-16 23:20:05
  [109920.854385] {1}[Hardware Error]:  Error 0, type: recoverable
  [109920.860111] {1}[Hardware Error]:   section_type: PCIe error
  [109920.865718] {1}[Hardware Error]:   port_type: 0, PCIe end 

[Kernel-packages] [Bug 1732990] Re: [Artful/Zesty] ACPI APEI error handling bug fixes

[Manoj Iyer]

Test kernel available at PPA https://launchpad.net/~centriq-
team/+archive/ubuntu/lp1732990

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

Title:
  [Artful/Zesty] ACPI APEI error handling bug fixes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Error records which have multiple errors in them will incorrectly report all 
errors after the first one. This results in garbage non-standard error trace 
events to be generated, and for AER and MC errors there will be no kernel 
action to help recover from these errors in the AER and EDAC drivers.

  [Fix]
  Patches in Linus tree fixes this issue:
  aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error
  c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block

  [Testing]
  Insert a e1000 pcie card into the system, run the following command that 
should generate PCIe correctable errors, you will see only the first error in 
each GHES report go to the AER driver rather than all errors from the GHES 
reports.

  $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s
  0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0
  CAP_EXP+0x10.B=0x48

  Where "0002:00:00.0" being the root hub for the card.

  [Regression Potential]
  The two patches to ACPI APEI driver was cleanly cherry picked from linus's 
tree and applied to Artful and Zesty. The patches were tested on QDF2400 
platform where it was found to issue and don't introduce any regressions.

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

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

[Kernel-packages] [Bug 1715861] Re: r592 & r852 IRQ: DMA errors cause excessive log file entries

[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/1715861

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Expired

Bug description:
   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am not 
making hardware changes at the times these entries are made. Entires are of the 
form:
  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  The laptop reports itself as having the problematic Ricoh devices. Relevant 
hwinfo attached. grepped extract follows
Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  WORKAROUND: Blacklist devices by adding the following lines at the end
  of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1717132] Re: P4D 4400c067

[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/1717132

Title:
  P4D 4400c067

Status in linux package in Ubuntu:
  Expired

Bug description:
  I just started firefox 56.0b3, but it opened normally;

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1717 F pulseaudio
  Date: Wed Sep 13 07:30:03 2017
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=4facb53f-bb13-43c4-8315-c7be76755529 ro quiet splash zswap.enabled=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: P4D 4400c067
  UpgradeStatus: No upgrade log present (probably fresh install)
  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.family: Virtual Machine
  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/1717132/+subscriptions

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

[Kernel-packages] [Bug 1717607] Re: Bluetooth

[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/1717607

Title:
  Bluetooth

Status in linux package in Ubuntu:
  Expired

Bug description:
  It seems that there is an issue with the Bluetooth connection for the
  linux system.. if i connect it starts off fine... but after a little
  bit it begins to slow my computer... specifically when watching
  youtube or streaming any video... at one point it actually crashed the
  OS... and i had to reboot from the repair options..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darkpirate   1946 F pulseaudio
   /dev/snd/controlC1:  darkpirate   1946 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 15 16:31:13 2017
  HibernationDevice: RESUME=UUID=4a471530-5e9d-4eb5-9272-a9630d8acccb
  InstallationDate: Installed on 2017-09-08 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. Q302LAB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=24233149-7a11-4b65-9166-1fe8959e4dc7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Q302LAB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Q302LAB
  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.:bvrQ302LAB.203:bd11/27/2014:svnASUSTeKCOMPUTERINC.:pnQ302LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ302LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: Q302LAB
  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/1717607/+subscriptions

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

[Kernel-packages] [Bug 1717963] Re: Cannot connect to PEAP-protected Wifi

[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/1717963

Title:
   Cannot connect to PEAP-protected Wifi

Status in linux package in Ubuntu:
  Expired

Bug description:
  When I try to connect to my workplace's WiFi network with settings:
  WP2
  PEAP authentication
  MSCHAPv2 Inner

  It does not connect and I get a stack trace in dmesg.  This happens
  every time I try to connect to this network.  My coworkers can connect
  without a problem and I can connect to my home WPA2 network without
  problems.

  I have attached the info collected from ubuntu-bug, please let me know
  if there is any more info I can give you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nate   2905 F pulseaudio
   /dev/snd/controlC0:  nate   2905 F pulseaudio
  Date: Mon Sep 18 12:03:13 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=46cd9de2-66d8-46a2-8141-1f2c3e871f90
  InstallationDate: Installed on 2015-11-23 (665 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. MacBookAir7,2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=UUID=0320e15e-7d64-454f-bd71-3b0edadab1c8 ro quiet splash 
acpi_backlight=vendor intel_idle.max_cstate=1 acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-93-generic N/A
   linux-backports-modules-4.4.0-93-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-11-20 (302 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA71.88Z.0166.B09.1510261436
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-937CB26E2E02BB01
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir7,2
  dmi.chassis.asset.tag: Chassis Board Asset Tag#
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-937CB26E2E02BB01
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA71.88Z.0166.B09.1510261436:bd10/26/2015:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01:
  dmi.product.name: MacBookAir7,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1717841] Re: PUD 54823067

[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/1717841

Title:
  PUD 54823067

Status in linux package in Ubuntu:
  Expired

Bug description:
  Spontaneous after boot

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   2064 F pulseaudio
  Date: Sat Sep 16 19:50:24 2017
  Failure: oops
  InstallationDate: Installed on 2017-07-28 (51 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170725.1)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=d03aab5f-253e-46dd-b7fa-d000f748a776 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: PUD 54823067
  UpgradeStatus: No upgrade log present (probably fresh install)
  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.family: Virtual Machine
  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/1717841/+subscriptions

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

[Kernel-packages] [Bug 1717999] Re: After installing linux kernel 4.10.35, linux couldnt opened

[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/1717999

Title:
  After installing linux kernel 4.10.35, linux couldnt opened

Status in linux package in Ubuntu:
  Expired

Bug description:
  After installing linux kernel 4.10.35, mylinux couldn't opened. I
  could opened by old kernel 4.8.0-53.

  
  Graphic card - GTX 1050 ti
  Processor - Intel i7-7700hq

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

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

[Kernel-packages] [Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

[Bug Watch Updater]

** Changed in: bluez
   Status: New => Incomplete

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

Title:
  bluetooth unavailable after rfkill hard (or soft) unblocking and after
  suspend/resume

Status in Bluez Utilities:
  Incomplete
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  DELL Latitude E5510 has a hardware switch to disable and enable
  bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
  terms of wifi, this works great: After hard unblocking, the device
  resumes back to normal operation without any manual intervention. That
  was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
  is not working any more:

  After hard blocking and unblocking

  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  8: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

  Workaround: After a

  sudo service bluetooth restart

  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).

  Suggested fix: Make the workaround obsolete.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1717992] Re: Sound silently plays to "Dummy Output"

[isaac]

The same issue here, on Ubuntu 17.10. Only "Dummy Output" found in
Output window.

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

Title:
  Sound silently plays to "Dummy Output"

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

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed 
root=/dev/mapper/ubu-root ro quiet splash zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: 

[Kernel-packages] [Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-fan - 0.12.8

---
ubuntu-fan (0.12.8) bionic; urgency=medium

  * fanatic: Optionally provide DNS server for docker test (LP:
#1732717)

ubuntu-fan (0.12.7) bionic; urgency=medium

  * fanctl: cmd_up needs to proparate scan_config errors (LP: #1719644)
  * fanatic: Clean up config if bringup fails (LP: #1728050)

 -- Stefan Bader   Thu, 16 Nov 2017 18:44:06
+0100

** Changed in: ubuntu-fan (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  fanatic enable-fan does not clean up config after failed bringup

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed
Status in ubuntu-fan source package in Artful:
  Fix Committed

Bug description:
  SRU Justification (for Artful/Zesty/Xenial):

  Impact:
  "fanatic enable-fan" calls to fanctl to actually bring up the Fan bridge. 
However it is possible that this returns with an error and in that case fanatic 
must undo previously done configuration changes or otherwise any following 
attempt to run enable-fan will incorrectly believe the bridge is up and do 
nothing.

  Fix:
  Adding a remove config stage if the call to fanctl returns with an error.

  Testcase:
    [fan is installed but not enabled]
    - sudo flock -x /run/xtables.lock sleep 300
    - fanatic enable-fan -u 192.168.0.0/16 -o 250.0.0.0/8; echo $?

  Note: It seems in Artful, the default for iptables is to wait until
  the lock is released (without -w) so the test here won't work without
  adding -w to all iptables calls in fanctl. :/

  Regression potential:
  Cleanup called only on failure and the used function is also used in fanatic 
disable-fan. -> Low

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

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

[Kernel-packages] [Bug 1732717] Re: docker test broken by systemd-resolv environment

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-fan - 0.12.8

---
ubuntu-fan (0.12.8) bionic; urgency=medium

  * fanatic: Optionally provide DNS server for docker test (LP:
#1732717)

ubuntu-fan (0.12.7) bionic; urgency=medium

  * fanctl: cmd_up needs to proparate scan_config errors (LP: #1719644)
  * fanatic: Clean up config if bringup fails (LP: #1728050)

 -- Stefan Bader   Thu, 16 Nov 2017 18:44:06
+0100

** Changed in: ubuntu-fan (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  docker test broken by systemd-resolv environment

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  New
Status in ubuntu-fan source package in Artful:
  New

Bug description:
  Inside a docker container DNS lookups are routed to 127.0.0.11:53 which is 
provided by the docker environment in some way. The real DNS service is taken 
from the hosts /etc/resolv.conf. The docker man page claims that selecting a 
good automatic default would not work if the hosts uses local resolvers 
(127.0.0.0/8).
  Since switching to netplan/systemd-resolvd there is only a local resolver 
(127.0.0.53) added to /etc/resolv.conf on the host. Surprisingly this does not 
seem to be an issue for an artful(or later) VM running on my own local desktop. 
But in the Canonical CI environment DNS lookups fail inside a docker container.

  SRU Justification:

  Impact: DNS lookups inside docker containers can fail if the host
  environment is set up to only use a local resolver. The built-in
  docker test of fanatic will always fail in that case.

  Fix: Add code to built-in tests which detect systemd-resolvd being in
  use and pass the IP address which systemd-resolv is using as forwarder
  with the --dns option to the docker run command.

  Testcase:
    - If the test host is using systemd-resolvd as its primary DNS
  server, there will be the following message in the test log:
    local docker test: *** Using DNS override ***
    --dns=
    - Otherwise no message is printed.
    - For all cases docker ADT test should (continue to) pass

  Risk of regression: minimal, only testing affected which is run as ADT
  tests.

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

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

[Kernel-packages] [Bug 1731031] Re: Kernel Oops with 17.10

[Henning Meyer]

no crashes with 4.14-rc1 either

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

Title:
  Kernel Oops with 17.10

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

Bug description:
  have captured dmesg just before oops

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Nov  8 20:41:14 2017
  DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to 
load user image: Failed to open file '/home/hmeyer/.face': No such file or 
directory
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B17.1602221718
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Nov  8 20:39:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

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

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

[Kernel-packages] [Bug 1730864] Re: Shutdown crashing when connected to AC adapter

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1730864

Title:
  Shutdown crashing when connected to AC adapter

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

Bug description:
  Hello there,

  I'm using Ubuntu 17.10 (fully updated) and my system is crashing at
  shutdown when connected to an AC adapter.

  The error is:

  Nov  6 22:16:49 rene-Inspiron-5447 kernel: [  248.294280] [drm:atom_op_jump 
[amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting
  Nov  6 22:16:49 rene-Inspiron-5447 kernel: [  248.294336] 
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck 
executing 75A8 (len 272, WS 0, PS 4) @ 0x75F1
  Nov  6 22:16:49 rene-Inspiron-5447 kernel: [  248.294384] 
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck 
executing 640C (len 68, WS 0, PS 8) @ 0x6430]

  This behavior is only happening when my laptop is charging. When
  running on battery I got a clean shutdown/reboot.

  Already tried to run the latest kernel package (from Mainline) and the
  problem is exactly the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rene   1249 F pulseaudio
   /dev/snd/controlC0:  rene   1249 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Nov  8 01:00:51 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0f3b9237-1086-430d-be15-043b9ca00fd2
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Inspiron 5447
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1237aa76-9a2f-4a06-8552-526f124914ff ro quiet splash 
acpi_backlight=intel_backlight
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0MHP6R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5447
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1732686] Re: Asus Fx553VD - Keyboard LED backlight controls are not working

[R.Erol]

Hi Joseph.

I already did it actually but i don't know if it is in at the right
place or not.

https://bugzilla.kernel.org/show_bug.cgi?id=197889

On thing to note ; as i mentioned above this keyboard backlight issue
also happened with Ubuntu provided kernels also , from 4.10 to 4.13.

And because of that i decided to install a more recent one via Ukuu to
see if it helps.

So it is not only an upstream specific bug , it is also an Ubuntu kernel
bug.

Is there any information i can provide here or there to ease committers
work?

** Bug watch added: Linux Kernel Bug Tracker #197889
   https://bugzilla.kernel.org/show_bug.cgi?id=197889

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

Title:
  Asus Fx553VD - Keyboard LED backlight controls are not working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi , i'm using this laptop with it's latest bios (V303 -
  https://www.asus.com/Laptops/ASUS-FX553VD/HelpDesk_BIOS/ )

  Kernel : 4.14.0-041400-generic x86_64

  I can't control keyboard LED backlight level with it's dedicated FN
  keys or anything else. FN keys are recognized by Linux Mint 18.2 and
  Ubuntu 16.04 but pressing them have no effect.

  Kernels from 4.10 to 4.14 are the same on that regard.

  And also i have these errors on "inxi -F && dmesg | grep -i error"

  [0.031175] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20170728/dswload-378)
  [0.040665] ACPI Error: 1 table load failures, 10 successful 
(20170728/tbxfload-246)
  [0.506425] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
  [1.694527] RAS: Correctable Errors collector initialized.
  [9.833145] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

  I'm not a developer but only a user. So if i opened that issue to the
  wrong place can you point me the correct place to open it?

  Thanks.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-10-22 (24 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  Tags:  sonya
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

[Iain Lane]

OK a few days ago apw pointed me at http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.13.8/ which is the mainline kernel that the artful-
proposed one I identified as bad is based on.

I ran 35 instances and rebooted them 30 times - all successful. So I
think that says this kernel is good.

Will try another one later on.

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

Title:
  Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
  for 22s! [systemd:1]"

Status in linux package in Ubuntu:
  In Progress
Status in qemu-kvm package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Incomplete
Status in qemu-kvm source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress
Status in qemu-kvm source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in qemu-kvm source package in Bionic:
  Confirmed

Bug description:
  This is impacting us for ubuntu autopkgtests. Eventually the whole
  region ends up dying because each worker is hit by this bug in turn
  and backs off until the next reset (6 hourly).

  17.10 (and bionic) guests are sometimes failing to reboot. When this
  happens, you see the following in the console

    [[0;32m  OK  [0m] Reached target Shutdown.
    [  191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
    [  226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
    [  226.706093] All QSes seen, last rcu_sched kthread activity 15002 
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
    [  226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

  One host that exhibits this behaviour was:

    Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  guest running:

    Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
  (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  (Ubuntu 4.13.0-16.19-generic 4.13.4)

  The affected cloud region is running the xenial/Ocata cloud archive,
  so the version of qemu-kvm in there may also be relevant.

  Here's how I reproduced it in lcy01:

    $ for n in {1..30}; do nova boot --flavor m1.small --image 
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name 
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; 
done
    $  sudo reboot
    # wait a minute or so for the instances to all reboot
    $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} 
| tail; done

  On bad instances you'll see the "soft lockup" message - on good it'll
  reboot as normal.

  We've seen good and bad instances on multiple compute hosts - it
  doesn't feel to me like a host problem but rather a race condition
  somewhere that's somehow either triggered or triggered much more often
  by what lcy01 is running. I always saw this on the first reboot -
  never on first boot, and never on n>1th boot. (But if it's a race then
  that might not mean much.)

  I'll attach a bad and a good console-log for reference.

  If you're at Canonical then see internal rt #107135 for some other
  details.

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

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

[Kernel-packages] [Bug 1732990] 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 1732990

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

** Tags added: artful

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

Title:
  [Artful/Zesty] ACPI APEI error handling bug fixes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Error records which have multiple errors in them will incorrectly report all 
errors after the first one. This results in garbage non-standard error trace 
events to be generated, and for AER and MC errors there will be no kernel 
action to help recover from these errors in the AER and EDAC drivers.

  [Fix]
  Patches in Linus tree fixes this issue:
  aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error
  c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block

  [Testing]
  Insert a e1000 pcie card into the system, run the following command that 
should generate PCIe correctable errors, you will see only the first error in 
each GHES report go to the AER driver rather than all errors from the GHES 
reports.

  $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s
  0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0
  CAP_EXP+0x10.B=0x48

  Where "0002:00:00.0" being the root hub for the card.

  [Regression Potential]
  The two patches to ACPI APEI driver was cleanly cherry picked from linus's 
tree and applied to Artful and Zesty. The patches were tested on QDF2400 
platform where it was found to issue and don't introduce any regressions.

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

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

[Kernel-packages] [Bug 1732990] [NEW] [Artful/Zesty] ACPI APEI error handling bug fixes

[Manoj Iyer]

Public bug reported:

[Impact]
Error records which have multiple errors in them will incorrectly report all 
errors after the first one. This results in garbage non-standard error trace 
events to be generated, and for AER and MC errors there will be no kernel 
action to help recover from these errors in the AER and EDAC drivers.

[Fix]
Patches in Linus tree fixes this issue:
aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error
c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block

[Testing]
Insert a e1000 pcie card into the system, run the following command that should 
generate PCIe correctable errors, you will see only the first error in each 
GHES report go to the AER driver rather than all errors from the GHES reports.

$ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s
0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0
CAP_EXP+0x10.B=0x48

Where "0002:00:00.0" being the root hub for the card.

[Regression Potential]
The two patches to ACPI APEI driver was cleanly cherry picked from linus's tree 
and applied to Artful and Zesty. The patches were tested on QDF2400 platform 
where it was found to issue and don't introduce any regressions.

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Manoj Iyer (manjo)
 Status: New


** Tags: qdf2400

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

Title:
  [Artful/Zesty] ACPI APEI error handling bug fixes

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  Error records which have multiple errors in them will incorrectly report all 
errors after the first one. This results in garbage non-standard error trace 
events to be generated, and for AER and MC errors there will be no kernel 
action to help recover from these errors in the AER and EDAC drivers.

  [Fix]
  Patches in Linus tree fixes this issue:
  aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error
  c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block

  [Testing]
  Insert a e1000 pcie card into the system, run the following command that 
should generate PCIe correctable errors, you will see only the first error in 
each GHES report go to the AER driver rather than all errors from the GHES 
reports.

  $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s
  0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0
  CAP_EXP+0x10.B=0x48

  Where "0002:00:00.0" being the root hub for the card.

  [Regression Potential]
  The two patches to ACPI APEI driver was cleanly cherry picked from linus's 
tree and applied to Artful and Zesty. The patches were tested on QDF2400 
platform where it was found to issue and don't introduce any regressions.

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

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

[Kernel-packages] [Bug 1732978] [NEW] Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

[bugproxy]

Public bug reported:

== Comment: #0 - Paulo Flabiano Smorigo  - 2017-11-17 
10:29:14 ==
Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback 
cipher for CTR mode. The commit bellow fixes this problem by using the new 
structure for the generic ciphers. Please add it to the kernel package.

https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

== Comment: #1 - VIPIN K. PARASHAR  - 2017-11-17 13:38:05 
==
(In reply to comment #0)
> Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
> cipher for CTR mode. The commit bellow fixes this problem by using the new
> structure for the generic ciphers. Please add it to the kernel package.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
> commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

Which is commit e666d4e9ceec94

commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
Author: Paulo Flabiano Smorigo 
Date:   Mon Oct 16 20:54:19 2017 -0200

crypto: vmx - Use skcipher for ctr fallback

Signed-off-by: Paulo Flabiano Smorigo 
Signed-off-by: Herbert Xu 

Its available with 4.14 kernel.


Hello Canonical,

Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr 
fallback"
with Ubuntu 17.10 kernel.

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


** Tags: architecture-ppc64le bugnameltc-161493 severity-high 
targetmilestone-inin1710

** Tags added: architecture-ppc64le bugnameltc-161493 severity-high
targetmilestone-inin1710

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

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

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

Title:
  Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
  fallback"

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Paulo Flabiano Smorigo  - 2017-11-17 
10:29:14 ==
  Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback 
cipher for CTR mode. The commit bellow fixes this problem by using the new 
structure for the generic ciphers. Please add it to the kernel package.

  
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  == Comment: #1 - VIPIN K. PARASHAR  - 2017-11-17 
13:38:05 ==
  (In reply to comment #0)
  > Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
  > cipher for CTR mode. The commit bellow fixes this problem by using the new
  > structure for the generic ciphers. Please add it to the kernel package.
  > 
  > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
  > commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  Which is commit e666d4e9ceec94

  commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
  Author: Paulo Flabiano Smorigo 
  Date:   Mon Oct 16 20:54:19 2017 -0200

  crypto: vmx - Use skcipher for ctr fallback
  
  Signed-off-by: Paulo Flabiano Smorigo 
  Signed-off-by: Herbert Xu 

  Its available with 4.14 kernel.

  
  Hello Canonical,

  Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr 
fallback"
  with Ubuntu 17.10 kernel.

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

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

[Kernel-packages] [Bug 1732978] [NEW] Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Paulo Flabiano Smorigo  - 2017-11-17 
10:29:14 ==
Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback 
cipher for CTR mode. The commit bellow fixes this problem by using the new 
structure for the generic ciphers. Please add it to the kernel package.

https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

== Comment: #1 - VIPIN K. PARASHAR  - 2017-11-17 13:38:05 
==
(In reply to comment #0)
> Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
> cipher for CTR mode. The commit bellow fixes this problem by using the new
> structure for the generic ciphers. Please add it to the kernel package.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
> commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

Which is commit e666d4e9ceec94

commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
Author: Paulo Flabiano Smorigo 
Date:   Mon Oct 16 20:54:19 2017 -0200

crypto: vmx - Use skcipher for ctr fallback

Signed-off-by: Paulo Flabiano Smorigo 
Signed-off-by: Herbert Xu 

Its available with 4.14 kernel.


Hello Canonical,

Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr 
fallback"
with Ubuntu 17.10 kernel.

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


** Tags: architecture-ppc64le bugnameltc-161493 severity-high 
targetmilestone-inin1710
-- 
Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"
https://bugs.launchpad.net/bugs/1732978
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 1732535] Re: linux-aws: 4.4.0-1041.50 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-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/1732535

Title:
  linux-aws: 4.4.0-1041.50 -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:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing 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-1041.50 upload package. This bug
  will contain status and testing results related to that upload.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1731264
  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/1732535/+subscriptions

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

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Dave Chiluk]

udevadm info -e as requested.

** Attachment added: "udevadminfo"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+attachment/5010640/+files/udevadminfo

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

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

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

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

[Kernel-packages] [Bug 1732804] Re: [Zesty/Artful] On ARM64 PCIE physical function passthrough guest fails to boot

[Sinan Kaya]

I confirm that the test kernel fixes the issue. I was able to assign
intel e1000e card to the guest machine and shutdown properly without
observing any errors on the host OS.

guest lspci

[root@localhost ~]# lspci
00:00.0 Host bridge: Red Hat, Inc. Device 0008
00:01.0 PCI bridge: Red Hat, Inc. Device 000c
00:01.1 PCI bridge: Red Hat, Inc. Device 000c
00:01.2 PCI bridge: Red Hat, Inc. Device 000c
01:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet 
Controller (Copper) (rev 06)
02:00.0 SCSI storage controller: Red Hat, Inc Virtio SCSI (rev 01)
[root@localhost ~]# 

host lspci
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.13.0-17-generic #20~lp1732804+build.1-Ubuntu SMP Fri Nov 17 
00:45:36 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux

ubuntu@ubuntu:~$ lspci
0001:00:00.0 PCI bridge: Qualcomm Datacenter Technologies QDF2400 PCI Express 
Root Port
0002:00:00.0 PCI bridge: Qualcomm Datacenter Technologies QDF2400 PCI Express 
Root Port
0002:01:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet 
Controller (Copper) (rev 06)
0004:00:00.0 PCI bridge: Qualcomm Datacenter Technologies QDF2400 PCI Express 
Root Port
0005:00:00.0 PCI bridge: Qualcomm Datacenter Technologies QDF2400 PCI Express 
Root Port

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

Title:
  [Zesty/Artful] On ARM64 PCIE physical function passthrough guest fails
  to boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Passing through a physical function like the Mellanox PCIE ethernet 
controller causes the guest to fail booting, and host reports Hardware Error. 
  == Host ==
  [109920.834703] {1}[Hardware Error]: Hardware error from APEI Generic 
Hardware Error Source: 4
  [109920.842142] {1}[Hardware Error]: event severity: recoverable
  [109920.847848] {1}[Hardware Error]:  precise tstamp: 2017-11-16 23:20:05
  [109920.854385] {1}[Hardware Error]:  Error 0, type: recoverable
  [109920.860111] {1}[Hardware Error]:   section_type: PCIe error
  [109920.865718] {1}[Hardware Error]:   port_type: 0, PCIe end point
  [109920.871708] {1}[Hardware Error]:   version: 3.0
  [109920.876343] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
  [109920.882559] {1}[Hardware Error]:   device_id: :01:00.0
  [109920.888113] {1}[Hardware Error]:   slot: 0
  [109920.892285] {1}[Hardware Error]:   secondary_bus: 0x00
  [109920.897489] {1}[Hardware Error]:   vendor_id: 0x15b3, device_id: 0x1013
  [109920.904172] {1}[Hardware Error]:   class_code: 02
  [109920.909378] vfio-pci :01:00.0: aer_status: 0x0004, aer_mask: 
0x
  [109920.916675] Malformed TLP
  [109920.916678] vfio-pci :01:00.0: aer_layer=Transaction Layer, 
aer_agent=Receiver ID
  [109920.924573] vfio-pci :01:00.0: aer_uncor_severity: 0x00062010
  [109920.930736] vfio-pci :01:00.0:   TLP Header: 4a008040 0100 
0100 
  [109920.938548] vfio-pci :01:00.0: broadcast error_detected message
  [109921.965056] pcieport :00:00.0: downstream link has been reset
  [109921.965062] vfio-pci :01:00.0: broadcast mmio_enabled message
  [109921.965066] vfio-pci :01:00.0: broadcast resume message
  [109921.965070] vfio-pci :01:00.0: AER: Device recovery successful
  == Guest ==
  EFI stub: Booting Linux Kernel...
  EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services and installing virtual address map...
  [1.518252] kvm [1]: HYP mode not available
  [2.578929] mlx5_core :05:00.0: mlx5_core_set_issi:778:(pid 152): 
Failed to query ISSI err(-1) status(0) synd(0)
  [2.582424] mlx5_core :05:00.0: failed to set issi
  [2.616756] mlx5_core :05:00.0: mlx5_load_one failed with error code -1

  This is because, virtualization of physical functions are broken on
  systems with Maximum Payload Size bigger than 128. QDF2400 FW tries to
  maximize this setting. We have observed an MPS of 512 on QDF2400
  systems.

  [Fix]
  Patches are in linux-next:
  523184972b28 vfio/pci: Virtualize Maximum Payload Size
  523184972b28 vfio/pci: Virtualize Maximum Payload Size

  [Testing]
  With the above patches applied the guest is able to boot when PCIE physical 
function is passthrough and we don't see the errors on the host system. 
  == On the Guest ==
  ubuntu@ubuntu-pcitest:~$ lspci
  00:00.0 Host bridge: Red Hat, Inc. Device 0008
  00:01.0 PCI bridge: Red Hat, Inc. Device 000c
  00:01.1 PCI bridge: Red Hat, Inc. Device 000c
  00:01.2 PCI bridge: Red Hat, Inc. Device 000c
  00:01.3 PCI bridge: Red Hat, Inc. Device 000c
  00:01.4 PCI bridge: Red Hat, Inc. Device 000c
  00:01.5 PCI bridge: Red Hat, Inc. Device 000c
  01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01)
  02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01)
  03:00.0 SCSI 

[Kernel-packages] [Bug 1729128] Re: Raspberry Pi 3 microSD support missing from the installer

[Paolo Pisati]

Ok, it appears uboot couldn't recognize my usb pen (it was an old 4GB
usb2.0) but worked fine with a more recent 16GB stick, go figure.

After that, I followed all the steps above, and i got to the point of
partitioning the disk, but even after inserting the bcm2835 module, i
coudln't see any /dev/mmc* device and, indeed, the installer could only
find the usb pen as a viable installation media.

Anyhow, i'm not sure how to test it, but here is the bionic generic
kernel (and relative debs and udebs) if you want to try it out:

http://people.canonical.com/~ppisati/lp1729128/

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

Title:
  Raspberry Pi 3 microSD support missing from the installer

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

Bug description:
  Please add bcm2835 to block-modules on arm64 (and armhf?).

  artful's arm64 d-i mini.iso works fine on Raspberry Pi 3 when booting
  with a UEFI-capable u-boot, except for one detail: mmc/host/bcm2835.ko
  is missing from block-modules, so you can't install to microSD without
  manually grabbing and loading the module.

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

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

[Kernel-packages] [Bug 1732945] WifiSyslog.txt

[fbnts]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1732945/+attachment/5010574/+files/WifiSyslog.txt

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

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  

[Kernel-packages] [Bug 1732945] Lspci.txt

[fbnts]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1732945/+attachment/5010567/+files/Lspci.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: [39934.913877]  [] 

[Kernel-packages] [Bug 1732945] UdevDb.txt

[fbnts]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1732945/+attachment/5010573/+files/UdevDb.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: [39934.913877]  

[Kernel-packages] [Bug 1732945] Lsusb.txt

[fbnts]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1732945/+attachment/5010568/+files/Lsusb.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: [39934.913877]  [] 

[Kernel-packages] [Bug 1732945] ProcCpuinfoMinimal.txt

[fbnts]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1732945/+attachment/5010569/+files/ProcCpuinfoMinimal.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 

[Kernel-packages] [Bug 1732945] JournalErrors.txt

[fbnts]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1732945/+attachment/5010566/+files/JournalErrors.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: 

[Kernel-packages] [Bug 1732945] ProcEnviron.txt

[fbnts]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1732945/+attachment/5010570/+files/ProcEnviron.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: 

[Kernel-packages] [Bug 1732945] ProcInterrupts.txt

[fbnts]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1732945/+attachment/5010571/+files/ProcInterrupts.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: 

[Kernel-packages] [Bug 1732945] CRDA.txt

[fbnts]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1732945/+attachment/5010563/+files/CRDA.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: [39934.913877]  [] 

[Kernel-packages] [Bug 1732945] IwConfig.txt

[fbnts]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1732945/+attachment/5010565/+files/IwConfig.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: 

[Kernel-packages] [Bug 1732945] ProcModules.txt

[fbnts]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1732945/+attachment/5010572/+files/ProcModules.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: 

[Kernel-packages] [Bug 1732945] CurrentDmesg.txt

[fbnts]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1732945/+attachment/5010564/+files/CurrentDmesg.txt

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: 

[Kernel-packages] [Bug 1732945] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); tty_poll+0x55/0x90

[fbnts]

apport information

** Tags added: apport-collected

** Description changed:

  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.
  
  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: [39934.913877]  [] 
core_sys_select+0x1cf/0x2f0
  Nov 17 15:07:47 server1 kernel: [39934.913880]  [] ? 
__wake_up+0x44/0x50
  Nov 17 15:07:47 server1 kernel: [39934.913883]  [] ? 
tty_write_unlock+0x31/0x40
  Nov 17 15:07:47 server1 kernel: [39934.913885]  [] ? 
tty_ldisc_deref+0x16/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913887]  [] ? 
n_tty_open+0xe0/0xe0
  Nov 17 15:07:47 server1 kernel: 

[Kernel-packages] [Bug 1728762] Re: Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D

[Seth Forshee]

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

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

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

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

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

Title:
  Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D

Status in intel:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  There are two parts of WIFI firmware update. Please double check if
  Ubuntu release has include them.

  A new firmware version for 8260 and 8265 WiFi devices.
  This our Core31 release (-34.ucode).
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=348d2b53326bcef4c260037cc7a6006fc80ca5bb

  
  A new firmware version  for 3160, 3168, 7260, 7265 and 7265D
  Note: This firmware version hasn't been pulled into mainline yet.
  This includes a security fix.
  The patch in iwlwifi/linux-firmware.git is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=11e310f97470f91e26e6f3408b09871fd6cd3c5c

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

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

[Kernel-packages] [Bug 1728908] Re: a300_[pfp|pm4].fw clashes when installing linux-firmware

[Seth Forshee]

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

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

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

Title:
  a300_[pfp|pm4].fw clashes when installing linux-firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware-snapdragon package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware-snapdragon source package in Xenial:
  In Progress
Status in linux-firmware source package in Artful:
  Fix Committed
Status in linux-firmware-snapdragon source package in Artful:
  In Progress

Bug description:
  [Impact]

  Starting with linux-firmware 1.157.13, two files (a300_[pfp|pm4].fw)
  that were previously part of linux-firmware-snapdragon 1.2-0ubuntu1,
  are now integrated in the linux-firmware package itself, resulting in
  a file clash when these two packages are installed together:

  ..
  Selecting previously unselected package linux-firmware-snapdragon.
  Preparing to unpack .../linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb ...
  Unpacking linux-firmware-snapdragon (1.2-0ubuntu1) ...
  dpkg: error processing archive
  /var/cache/apt/archives/linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb
  (--unpack):
   trying to overwrite '/lib/firmware/a300_pm4.fw', which is also in
  package linux-firmware 1.157.13
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Selecting previously unselected package linux-image-snapdragon.
  Preparing to unpack .../linux-image-snapdragon_4.4.0.1077.69_arm64.deb ...
  Unpacking linux-image-snapdragon (4.4.0.1077.69) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  make: *** [all] Error 100
  ...

  This problem is particularly evident when a new snapdragon kernel snap
  is assembled, since the the building process breaks (and no kernel
  snap is generated):

  https://launchpadlibrarian.net/343287945
  /buildlog_snap_ubuntu_xenial_arm64_snapdragon-kernel-
  test_BUILDING.txt.gz

  To fix the problem i removed the two files from linux-firmware-
  snapdragon 1.3-0ubuntu1 and pushed this new version to my ppa:

  https://launchpad.net/~p-pisati/+archive/ubuntu/embedded/+packages
  linux-firmware-snapdragon - 1.3-0ubuntu1

  [Test case]

  Try to build a snapdragon kernel snap using Xenial/updates - with
  linux-firmware 1.157.13 and linux-firmware-snapdragon 1.2-0ubuntu1 it
  won't complete, while with linux-firmware-snapdragon 1.3-0ubuntu1 it
  will successfully complete.

  [Regression risk]

  The files imported in linux-firmware are the same files we
  shipped in linux-firmware-snapdragon:

  $ md5sum /lib/firmware/qcom/a300_pfp.fw
  25aa81977303142bdc4490efad16138b  /lib/firmware/qcom/a300_pfp.fw
  $ md5sum /lib/firmware/qcom/a300_pm4.fw
  d657cacd951742d9bbbe74224347cffe  /lib/firmware/qcom/a300_pm4.fw

  $ md5sum dragon410c-firmware.orig/lib/a300_pfp.fw
  25aa81977303142bdc4490efad16138b  dragon410c-firmware.orig/lib/a300_pfp.fw
  $ md5sum dragon410c-firmware.orig/lib/a300_pm4.fw
  d657cacd951742d9bbbe74224347cffe  dragon410c-firmware.orig/lib/a300_pm4.fw

  so the regression risk is very low.

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

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

[Kernel-packages] [Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

[Joseph Salisbury]

** Tags removed: 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/1729878

Title:
  stress-ng triggering oomkiller running brk and stack stressors on all
  arches.

Status in Stress-ng:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  During regression testing on a z/VM instance, I noticed call traces
  being dumped to dmesg that seem to be related to stress-ng.

  The stress-ng invocation we're using is:
  stress-ng --aggressive --verify --timeout $runtime \
   --metrics-brief --tz --times \
   --af-alg 0 --bsearch 0 --context 0 --cpu 0 \
   --crypt 0 --hsearch 0 --longjmp 0 --lsearch 
0 \
   --matrix 0 --qsort 0 --str 0 --stream 0 \
   --tsearch 0 --vecmath 0 --wcs 0

  as executed by the cpu_stress script from the cpu/cpu_stress_ng test
  in the certification suite.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic s390x
  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': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Nov  3 11:12:04 2017
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  --- 
  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
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  artful
  Uname: Linux 4.13.0-16-generic s390x
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1729878/+subscriptions

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

[Kernel-packages] [Bug 1724796] Re: Picture is heavily malformed

[Joseph Salisbury]

This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

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

** Tags removed: 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/1724796

Title:
  Picture is heavily malformed

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On boot screen with disk decrypt password and gdm are heavily deformed
  (check attachment). After login wayland session is also deformed, then
  if I logout and login to Xorg, picture is fine. After that if I logout
  and login back to Wayland session picture is also fine.

  GDM -> https://imgur.com/a/MhHbd
  Disk decrypt -> https://imgur.com/a/UP0rL

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 12:29:31 2017
  DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
  InstallationDate: Installed on 2017-08-25 (54 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1732945] 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 1732945

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

** Tags added: xenial

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 

[Kernel-packages] [Bug 1732945] [NEW] Kernel Oops - unable to handle kernel NULL pointer dereference at (null); tty_poll+0x55/0x90

[fbnts]

Public bug reported:

I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
hangs and requires a hard power cycle.  I have managed to capture the
following Kernel Oops from the log but I unsure what the cause is.

Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 PMD 
0 
Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[]  
[] tty_poll+0x55/0x90
Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  CR0: 
80050033
Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
Nov 17 15:07:47 server1 kernel: [39934.913877]  [] 
core_sys_select+0x1cf/0x2f0
Nov 17 15:07:47 server1 kernel: [39934.913880]  [] ? 
__wake_up+0x44/0x50
Nov 17 15:07:47 server1 kernel: [39934.913883]  [] ? 
tty_write_unlock+0x31/0x40
Nov 17 15:07:47 server1 kernel: [39934.913885]  [] ? 
tty_ldisc_deref+0x16/0x20
Nov 17 15:07:47 server1 kernel: [39934.913887]  [] ? 
n_tty_open+0xe0/0xe0
Nov 17 15:07:47 server1 kernel: [39934.913888]  [] 
SyS_select+0xba/0x110
Nov 17 15:07:47 server1 kernel: [39934.913892]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
Nov 17 15:07:47 server1 

[Kernel-packages] [Bug 1732945] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); tty_poll+0x55/0x90

[fbnts]

** Attachment added: "lspci-vvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732945/+attachment/5010546/+files/lspci-vvnn.log

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: 

[Kernel-packages] [Bug 1732945] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); tty_poll+0x55/0x90

[fbnts]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732945/+attachment/5010544/+files/version.log

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: 

[Kernel-packages] [Bug 1732945] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); tty_poll+0x55/0x90

[fbnts]

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732945/+attachment/5010545/+files/uname-a.log

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

Title:
  Kernel Oops - unable to handle kernel NULL pointer dereference at
  (null); tty_poll+0x55/0x90

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an ubuntu server 16.04.3 running 4.4.0-98-generic.  It randomly
  hangs and requires a hard power cycle.  I have managed to capture the
  following Kernel Oops from the log but I unsure what the cause is.

  Nov 17 15:07:47 server1 kernel: [39934.913759] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
  Nov 17 15:07:47 server1 kernel: [39934.913767] IP: [] 
tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913775] PGD 7197ed067 PUD 6d7040067 
PMD 0 
  Nov 17 15:07:47 server1 kernel: [39934.913781] Oops:  [#1] SMP 
  Nov 17 15:07:47 server1 kernel: [39934.913785] Modules linked in: ipmi_si 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport 
mpt3sas raid_class scsi_transport_sas mptctl mptbase ip_gre ip_tunnel gre 
dell_rbu ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_iprange xt_conntrack 
iptable_filter iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables binfmt_misc joydev 
input_leds ipmi_ssif ipmi_devintf hid_generic gpio_ich usbhid dcdbas hid 
intel_powerclamp kvm_intel kvm irqbypass i7core_edac edac_core lpc_ich shpchp 
ipmi_msghandler 8250_fintek mac_hid acpi_power_meter coretemp parport_pc ppdev 
sunrpc lp parport autofs4 bnx2 megaraid_sas wmi fjes [last unloaded: ipmi_si]
  Nov 17 15:07:47 server1 kernel: [39934.913819] CPU: 0 PID: 22392 Comm: telnet 
Tainted: G   OE   4.4.0-98-generic #121-Ubuntu
  Nov 17 15:07:47 server1 kernel: [39934.913821] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013
  Nov 17 15:07:47 server1 kernel: [39934.913822] task: 8808140fa640 ti: 
8806d16c task.ti: 8806d16c
  Nov 17 15:07:47 server1 kernel: [39934.913823] RIP: 0010:[] 
 [] tty_poll+0x55/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913826] RSP: 0018:8806d16c3978  
EFLAGS: 00010246
  Nov 17 15:07:47 server1 kernel: [39934.913827] RAX:  RBX: 
88071f498700 RCX: 0009
  Nov 17 15:07:47 server1 kernel: [39934.913828] RDX: 8000 RSI: 
 RDI: 88071943ac28
  Nov 17 15:07:47 server1 kernel: [39934.913829] RBP: 8806d16c39a0 R08: 
88071f498700 R09: 88071f498700
  Nov 17 15:07:47 server1 kernel: [39934.913830] R10: 0001009732b3 R11: 
 R12: 88071943ac00
  Nov 17 15:07:47 server1 kernel: [39934.913831] R13:  R14: 
8806d16c3aa0 R15: 
  Nov 17 15:07:47 server1 kernel: [39934.913832] FS:  7f2d745ec740() 
GS:88081ee0() knlGS:
  Nov 17 15:07:47 server1 kernel: [39934.913834] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov 17 15:07:47 server1 kernel: [39934.913835] CR2:  CR3: 
0007b3e7 CR4: 26f0
  Nov 17 15:07:47 server1 kernel: [39934.913836] Stack:
  Nov 17 15:07:47 server1 kernel: [39934.913837]  0009 
0040  0001
  Nov 17 15:07:47 server1 kernel: [39934.913838]  0004 
8806d16c3d48 81225873 880814379400
  Nov 17 15:07:47 server1 kernel: [39934.913840]  8806d16c4000 
  8808140fa640
  Nov 17 15:07:47 server1 kernel: [39934.913842] Call Trace:
  Nov 17 15:07:47 server1 kernel: [39934.913846]  [] 
do_select+0x383/0x810
  Nov 17 15:07:47 server1 kernel: [39934.913850]  [] ? 
__dev_queue_xmit+0x286/0x590
  Nov 17 15:07:47 server1 kernel: [39934.913852]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913853]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913855]  [] ? 
poll_select_copy_remaining+0x140/0x140
  Nov 17 15:07:47 server1 kernel: [39934.913858]  [] ? 
enqueue_task_fair+0xaa/0x8b0
  Nov 17 15:07:47 server1 kernel: [39934.913861]  [] ? 
sched_clock+0x9/0x10
  Nov 17 15:07:47 server1 kernel: [39934.913864]  [] ? 
sched_clock_cpu+0x8f/0xa0
  Nov 17 15:07:47 server1 kernel: [39934.913866]  [] ? 
check_preempt_curr+0x54/0x90
  Nov 17 15:07:47 server1 kernel: [39934.913868]  [] ? 
ttwu_do_wakeup+0x19/0xe0
  Nov 17 15:07:47 server1 kernel: [39934.913869]  [] ? 
ttwu_do_activate.constprop.90+0x5d/0x70
  Nov 17 15:07:47 server1 kernel: [39934.913871]  [] ? 
try_to_wake_up+0x49/0x3f0
  Nov 17 15:07:47 server1 kernel: [39934.913872]  [] ? 
wake_up_process+0x15/0x20
  Nov 17 15:07:47 server1 kernel: [39934.913875]  [] ? 
insert_work+0x81/0xc0
  Nov 17 15:07:47 server1 kernel: 

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

[Joseph Salisbury]

The bisect must have gone wrong.  It might not be possible to perform a
bisect in this case.  I think what would be best is to post all the HW
info into the bug.  Then I can review the commits between
Ubuntu-4.0.0-4.7 and Ubuntu-4.1.0-3.3 to see what could be relevant.

Can you run the following command and then attach the report.1646277 file:
apport-bug --save /tmp/report.1646277 linux

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

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

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

[bugproxy]

--- Comment From b...@us.ibm.com 2017-11-17 11:07 EDT---
I was told that this issue is due to a mis-configuration where if end to end 
MTU isn't set correctly then you will see this problem. So as long as the user 
sets the MTU end to end correctly you shouldn't see this problem.

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

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  
  == SRU Justification ==
  Commit 66aa0678ef is request to fix four issues with the ibmveth driver.
  The issues are as follows:
  - Issue 1: ibmveth doesn't support largesend and checksum offload features 
when configured as "Trunk".
  - Issue 2: SYN packet drops seen at destination VM. When the packet
  originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO
  server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth
  receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag.
  - Issue 3: First packet of a TCP connection will be dropped, if there is
  no OVS flow cached in datapath.
  - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.

  The details for the fixes to these issues are described in the commits
  git log.



  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---

   - Issue 1: ibmveth doesn't support largesend and checksum offload features
     when configured as "Trunk". Driver has explicit checks to prevent
     enabling these offloads.

   - Issue 2: SYN packet drops seen at destination VM. When the packet
     originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
     IO server's inbound Trunk ibmveth, on validating "checksum good" bits
     in ibmveth receive routine, SKB's ip_summed field is set with
     CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
     Bridge) and delivered to outbound Trunk ibmveth. At this point the
     outbound ibmveth transmit routine will not set "no checksum" and
     "checksum good" bits in transmit buffer descriptor, as it does so only
     when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
     delivered to destination VM, TCP layer receives the packet with checksum
     value of 0 and with no checksum related flags in ip_summed field. This
     leads to packet drops. So, TCP connections never goes through fine.

   - Issue 3: First packet of a TCP connection will be dropped, if there is
     no OVS flow cached in datapath. OVS while trying to identify the flow,
     computes the checksum. The computed checksum will be invalid at the
     receiving end, as ibmveth transmit routine zeroes out the pseudo
     checksum value in the packet. This leads to packet drop.

   - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
     When Physical NIC has GRO enabled and when OVS bridges these packets,
     OVS vport send code will end up calling dev_queue_xmit, which in turn
     calls validate_xmit_skb.
     In validate_xmit_skb routine, the larger packets will get segmented into
     MSS sized segments, if SKB has a frag_list and if the driver to which
     they are delivered to doesn't support NETIF_F_FRAGLIST feature.

  Contact Information = Bryant G. Ly/b...@us.ibm.com

  ---uname output---
  4.8.0-51.54

  Machine Type = p8

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

  ---Steps to Reproduce---
   Increases performance greatly

  The patch has been accepted upstream:
  https://patchwork.ozlabs.org/patch/764533/

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

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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

[dann frazier]

I've verified this for zesty, using my patched zesty kernel.
Demonstration of that follows. However, the kernel patches have not yet
been approved for zesty, and may never be. I'll hold-off on updating the
tags here until a) we have a final answer on the kernel patches or b) we
decide there is value in updating QEMU w/o the kernel side.

= Verification log =

ubuntu@dawes:~$ uname -a
Linux dawes 4.10.0-40-generic #44+gicv3sr.1-Ubuntu SMP Thu Nov 9 22:53:54 UTC 
2017 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@dawes:~$ cd vm-save-restore/
ubuntu@dawes:~/vm-save-restore$ ./setup.sh 
+ set -e
+ cloudrel=zesty
+ cloudimg=zesty-server-cloudimg-arm64.img
+ sudo apt-get install -y cloud-image-utils qemu-kvm qemu-utils qemu-efi 
libvirt-bin screen uuid-runtime
Reading package lists... Done
Building dependency tree   
Reading state information... Done
cloud-image-utils is already the newest version (0.30-0ubuntu2).
screen is already the newest version (4.5.0-5ubuntu1).
qemu-efi is already the newest version (0~20161202.7bbe0b3e-1).
uuid-runtime is already the newest version (2.29-1ubuntu2.1).
libvirt-bin is already the newest version (2.5.0-3ubuntu5.6).
qemu-kvm is already the newest version (1:2.8+dfsg-3ubuntu2.8).
qemu-utils is already the newest version (1:2.8+dfsg-3ubuntu2.8).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ test -f zesty-server-cloudimg-arm64.img
+ echo #!/bin/sh
+ sudo tee /etc/qemu-ifup
+ echo 
+ sudo tee -a /etc/qemu-ifup
+ echo set -e
+ sudo tee -a /etc/qemu-ifup
+ echo 
+ sudo tee -a /etc/qemu-ifup
+ echo ip link set "$1" up
+ sudo tee -a /etc/qemu-ifup
+ echo ip link set "$1" master virbr0
+ sudo tee -a /etc/qemu-ifup
ubuntu@dawes:~/vm-save-restore$ ./test.sh 
+ i=0
+ [ -f /var/log/libvirt/qemu/4273-0.log ]
+ name=4273-0
+ ./randmac.py
+ mac=00:16:3e:1c:57:55
+ uuidgen
+ uuid=1578301c-e2fe-4981-87b5-bee2c56fa14c
+ mktemp
+ xml=/tmp/tmp.D9DXzEvOHn
+ cp template.xml /tmp/tmp.D9DXzEvOHn
+ trap cleanup EXIT
+ mkdir -p vms
+ dd if=/dev/zero of=./vms/4273-0_CODE.fd bs=1M count=64
64+0 records in
64+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 0.166913 s, 402 MB/s
+ dd if=/usr/share/qemu-efi/QEMU_EFI.fd of=./vms/4273-0_CODE.fd conv=notrunc
4096+0 records in
4096+0 records out
2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.0602123 s, 34.8 MB/s
+ dd if=/dev/zero of=./vms/4273-0_VARS.fd bs=1M count=64
64+0 records in
64+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 0.16786 s, 400 MB/s
+ cat
+ cloud-localds vms/4273-0_seed.img vms/4273-0_user-data
+ pwd
+ qemu-img create -f qcow2 -o 
backing_file=/home/ubuntu/vm-save-restore/zesty-server-cloudimg-arm64.img 
./vms/4273-0.img
Formatting './vms/4273-0.img', fmt=qcow2 size=2361393152 
backing_file=/home/ubuntu/vm-save-restore/zesty-server-cloudimg-arm64.img 
encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
+ sed -i s/\#VM\#/4273-0/ /tmp/tmp.D9DXzEvOHn
+ pwd
+ sed -i s,\#DIR\#,/home/ubuntu/vm-save-restore, /tmp/tmp.D9DXzEvOHn
+ sed -i s/\#UUID\#/1578301c-e2fe-4981-87b5-bee2c56fa14c/ /tmp/tmp.D9DXzEvOHn
+ sed -i s/\#MAC\#/00:16:3e:1c:57:55/ /tmp/tmp.D9DXzEvOHn
+ sudo virsh define /tmp/tmp.D9DXzEvOHn
Domain 4273-0 defined from /tmp/tmp.D9DXzEvOHn

+ sudo virsh start 4273-0
Domain 4273-0 started

+ sleep 60
+ sudo virsh save 4273-0 ./vms/4273-0.sav

Domain 4273-0 saved to ./vms/4273-0.sav

+ sudo virsh restore ./vms/4273-0.sav
Domain restored from ./vms/4273-0.sav

+ sleep 5
+ sudo virsh save 4273-0 ./vms/4273-0.sav

Domain 4273-0 saved to ./vms/4273-0.sav

+ sudo virsh restore ./vms/4273-0.sav
Domain restored from ./vms/4273-0.sav

+ sudo virsh save 4273-0 ./vms/4273-0.sav

Domain 4273-0 saved to ./vms/4273-0.sav

+ sudo virsh restore ./vms/4273-0.sav
Domain restored from ./vms/4273-0.sav

+ cleanup
+ sudo virsh destroy 4273-0
Domain 4273-0 destroyed

+ sudo virsh undefine 4273-0 --nvram
Domain 4273-0 has been undefined

+ rm -f ./vms/4273-0.img ./vms/4273-0_CODE.fd ./vms/4273-0_VARS.fd
/tmp/tmp.D9DXzEvOHn ./vms/4273-0.sav vms/4273-0_user-data
vms/4273-0_seed.img

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

Title:
  support GICv3 ITS save/restore & migration

Status in Ubuntu Cloud Archive:
  New
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  In Progress
Status in qemu source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in qemu source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  

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

[Scott Moser]

** Changed in: cloud-images
   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/1726818

Title:
  vagrant artful64 box filesystem too small

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

Bug description:
  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 1725350] Re: KVM on 17.10 crashes the machine

[Joseph Salisbury]

Commit 67f8a8c1151c is now in the -proposed 4.13.0-17.20 Artful kernel.

Would it be possible for you to test the proposed kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed. 

Thank you in advance!

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

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

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

Title:
  KVM on 17.10 crashes the machine

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  When you start qemu on a 17.10 machine, the whole machine goes down
  and crashes:

  [   90.689627] Unable to handle kernel paging request for data at address 
0xf2d3bda0
  [   90.689705] Faulting instruction address: 0xc0361224
  [   90.689840] Oops: Kernel access of bad area, sig: 11 [#1]
  [   90.689911] SMP NR_CPUS=2048 
  [   90.689912] NUMA 
  [   90.690053] PowerNV
  [   90.690092] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat xt_conntrack ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack_netlink nf_conntrack nfnetlink idt_89hpesx snd_hda_codec_hdmi xfs 
joydev input_leds mac_hid snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_timer snd soundcore ofpart opal_prd cmdlinepart powernv_flash mtd 
at24 ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng uio_pdrv_genirq 
vmx_crypto ibmpowernv uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables
  [   90.690724]  autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 
raid0 multipath linear uas usb_storage ast crct10dif_vpmsum i2c_algo_bit 
crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
drm tg3 ahci libahci
  [   90.690937] CPU: 48 PID: 3986 Comm: qemu-system-ppc Not tainted 
4.13.0-12-generic #13-Ubuntu
  [   90.691001] task: c00b122d8700 task.stack: c00b431cc000
  [   90.691167] NIP: c0361224 LR: c0998960 CTR: 
c09a19b0
  [   90.691223] REGS: c00bff61b800 TRAP: 0300   Not tainted  
(4.13.0-12-generic)
  [   90.691277] MSR: 90009033 
  [   90.691282]   CR: 88002844  XER: 
  [   90.691347] CFAR: c099895c DAR: f2d3bda0 DSISR: 4000 
SOFTE: 0 
  [   90.691347] GPR00: c0998960 c00bff61ba80 c15e3000 
c00b4ef61f20 
  [   90.691347] GPR04: c00b44c61680  001f 
001f 
  [   90.691347] GPR08: 001f 02d3bd80 c178e8e8 
c00b5a0c26f0 
  [   90.691347] GPR12: 28002842 cfadf800 c00b52d07880 
c00b44c61680 
  [   90.691347] GPR16:  001f 001f 
c553a560 
  [   90.691347] GPR20: 0001 0002 08000553a560 
c00b5c62a228 
  [   90.691347] GPR24: c5531110 c00b5c632238 0210 
 
  [   90.691347] GPR28: c0998960 c00bff61bc20 c00b4ef61f20 
f2d3bd80 
  [   90.692089] NIP [c0361224] kfree+0x54/0x270
  [   90.692133] LR [c0998960] xhci_urb_free_priv+0x20/0x40
  [   90.692325] Call Trace:
  [   90.692345] [c00bff61ba80] [c00bff61bad0] 0xc00bff61bad0 
(unreliable)
  [   90.692402] [c00bff61bac0] [c0998960] 
xhci_urb_free_priv+0x20/0x40
  [   90.692459] [c00bff61bae0] [c099bfc8] 
xhci_giveback_urb_in_irq.isra.22+0x78/0x190
  [   90.692645] [c00bff61bb40] [c099c350] 
xhci_td_cleanup+0x130/0x200
  [   90.692702] [c00bff61bbc0] [c09a175c] 
handle_tx_event+0x74c/0x1380
  [   90.692759] [c00bff61bcc0] [c09a2894] xhci_irq+0x504/0xf20
  [   90.692808] [c00bff61bde0] [c017b110] 
__handle_irq_event_percpu+0x90/0x300
  [   90.692977] [c00bff61bea0] [c017b3b8] 
handle_irq_event_percpu+0x38/0x90
  [   90.693038] [c00bff61bee0] [c017b474] 
handle_irq_event+0x64/0xb0
  [   90.693094] [c00bff61bf10] [c0180da0] 
handle_fasteoi_irq+0xc0/0x230
  [   90.693155] [c00bff61bf40] [c017972c] 
generic_handle_irq+0x4c/0x70
  [   90.693332] [c00bff61bf60] [c001767c] __do_irq+0x7c/0x1c0
  [   90.693383] [c00bff61bf90] [c002ab70] call_do_irq+0x14/0x24
  [   90.693431] [c00b431cf9d0] 

Re: [Kernel-packages] [Bug 1732424] Re: Surface Pro 4. System hangs when suspended or hibernated

[Hicks]

Will do.

El 17 nov. 2017 4:41 p. m., "Joseph Salisbury" <
joseph.salisb...@canonical.com> escribió:

> This issue appears to be an upstream bug, since you tested the latest
> upstream kernel. Would it be possible for you to open an upstream bug
> report[0]? That will allow the upstream Developers to examine the issue,
> and may provide a quicker resolution to the bug.
>
> Please follow the instructions on the wiki page[0]. The first step is to
> email the appropriate mailing list. If no response is received, then a
> bug may be opened on bugzilla.kernel.org.
>
> Once this bug is reported upstream, please add the tag: 'kernel-bug-
> reported-upstream'.
>
> [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1732424
>
> Title:
>   Surface Pro 4. System hangs when suspended or hibernated
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1732424/+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/1732424

Title:
  Surface Pro 4. System hangs when suspended or hibernated

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have a Surface Pro 4. I have problems with sleep and hibernation on
  my computer, because once it's turned on, the system won't wake up and
  you have to force the power off.

  I have tried several kernels:

  *The normal version

  *linux-image-4.9.0-rc8-mssp4+_4.9.0-rc8-mssp4+-10.00. Custom_amd64
  (special for Surface)

  *The last 4.14 kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1532 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov 15 13:13:19 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (24 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://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 1732568] Re: [ASUSTeK Computer Inc. N55SF] hibernate/resume failure

[Furkan keskin]

When I try to hibernate my computer, it sometimes does'nt take action. If
it successed when I wake up my computer, it shows me an error and suggests
me to report that.


2017-11-17 18:30 GMT+03:00 Joseph Salisbury 
:

> Can you describe the issue you are seeing?
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1732568
>
> Title:
>   [ASUSTeK Computer Inc. N55SF] hibernate/resume failure
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   asdfasdf
>
>   ProblemType: KernelOops
>   DistroRelease: Ubuntu 17.10
>   Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified:
> boot/vmlinuz-4.13.0-16-generic]
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   Annotation: This occurred during a previous hibernation, and prevented
> the system from resuming properly.
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC0D0p:   furkan16312 F...m pulseaudio
>/dev/snd/controlC0:  gdm1166 F pulseaudio
> furkan16312 F pulseaudio
>   Date: Tue Nov 14 15:40:53 2017
>   DuplicateSignature: hibernate/resume:ASUSTeK Computer Inc.
> N55SF:N55SF.207
>   ExecutablePath: /usr/share/apport/apportcheckresume
>   Failure: hibernate/resume
>   HibernationDevice: RESUME=UUID=2342e5a4-757e-4272-8f09-83da2f709745
>   InstallationDate: Installed on 2017-11-07 (8 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20171018)
>   InterpreterPath: /usr/bin/python3.6
>   MachineType: ASUSTeK Computer Inc. N55SF
>   ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
>   ProcFB:
>0 nouveaufb
>1 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed
> root=UUID=62e32f5e-91c0-4dba-b66e-ad6145724175 ro
> resume=UUID=2342e5a4-757e-4272-8f09-83da2f709745 quiet splash
>   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: /root/Error: command ['which', 'python'] failed with exit
> code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command
> ['which', 'python'] failed with exit code 1:": "/root/Error: command
> ['which', 'python'] failed with exit code 1:", unpackaged
>   RelatedPackageVersions:
>linux-restricted-modules-4.13.0-16-generic N/A
>linux-backports-modules-4.13.0-16-generic  N/A
>linux-firmware 1.169
>   SourcePackage: linux
>   Title: [ASUSTeK Computer Inc. N55SF] hibernate/resume failure
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   dmi.bios.date: 08/29/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: N55SF.207
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: N55SF
>   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.:bvrN55SF.207:bd08/29/2011:
> svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:
> rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
>   dmi.product.family: N
>   dmi.product.name: N55SF
>   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/
> 1732568/+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/1732568

Title:
  [ASUSTeK Computer Inc. N55SF] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  asdfasdf

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   furkan16312 F...m pulseaudio
   /dev/snd/controlC0:  gdm1166 F pulseaudio
furkan16312 F pulseaudio
  Date: Tue Nov 14 15:40:53 2017
  DuplicateSignature: hibernate/resume:ASUSTeK Computer Inc. N55SF:N55SF.207
  

[Kernel-packages] [Bug 1718193] Re: NEW RYZEN 7 SYSTEM WAKEUP

[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.14 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.14

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

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1732568] Re: [ASUSTeK Computer Inc. N55SF] hibernate/resume failure

[Joseph Salisbury]

Can you describe the issue you are seeing?

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

Title:
  [ASUSTeK Computer Inc. N55SF] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  asdfasdf

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   furkan16312 F...m pulseaudio
   /dev/snd/controlC0:  gdm1166 F pulseaudio
furkan16312 F pulseaudio
  Date: Tue Nov 14 15:40:53 2017
  DuplicateSignature: hibernate/resume:ASUSTeK Computer Inc. N55SF:N55SF.207
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=2342e5a4-757e-4272-8f09-83da2f709745
  InstallationDate: Installed on 2017-11-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterpreterPath: /usr/bin/python3.6
  MachineType: ASUSTeK Computer Inc. N55SF
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=62e32f5e-91c0-4dba-b66e-ad6145724175 ro 
resume=UUID=2342e5a4-757e-4272-8f09-83da2f709745 quiet splash
  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: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  Title: [ASUSTeK Computer Inc. N55SF] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/29/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N55SF.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N55SF
  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.:bvrN55SF.207:bd08/29/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N55SF
  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/1732568/+subscriptions

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

[Kernel-packages] [Bug 1732686] Re: Asus Fx553VD - Keyboard LED backlight controls are not working

[Joseph Salisbury]

This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

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

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

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

Title:
  Asus Fx553VD - Keyboard LED backlight controls are not working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi , i'm using this laptop with it's latest bios (V303 -
  https://www.asus.com/Laptops/ASUS-FX553VD/HelpDesk_BIOS/ )

  Kernel : 4.14.0-041400-generic x86_64

  I can't control keyboard LED backlight level with it's dedicated FN
  keys or anything else. FN keys are recognized by Linux Mint 18.2 and
  Ubuntu 16.04 but pressing them have no effect.

  Kernels from 4.10 to 4.14 are the same on that regard.

  And also i have these errors on "inxi -F && dmesg | grep -i error"

  [0.031175] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20170728/dswload-378)
  [0.040665] ACPI Error: 1 table load failures, 10 successful 
(20170728/tbxfload-246)
  [0.506425] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
  [1.694527] RAS: Correctable Errors collector initialized.
  [9.833145] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

  I'm not a developer but only a user. So if i opened that issue to the
  wrong place can you point me the correct place to open it?

  Thanks.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-10-22 (24 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  Tags:  sonya
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1732370] Re: ThunderX arm64 system failed with test 079 in zfs_xfs_generic

[Joseph Salisbury]

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

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

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

Title:
  ThunderX arm64 system failed with test 079 in zfs_xfs_generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This system constantly fails with the generic test 079 in
  ubuntu_zfs_xfs_generic test suite, even with the latest code from
  upstream.

  07:59:46 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_zfs_xfs_generic.079', 'ubuntu_zfs_xfs_generic.079')
  07:59:46 DEBUG| Waiting for pid 12399 for 3600 seconds
  07:59:47 INFO | Running: 
/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 079 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  07:59:51 DEBUG| [stdout]
  08:00:01 ERROR| Exception escaping from test:
  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
    File 
"/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.py",
 line 98, in run_once
  self.results = utils.system_output(cmd, retain_output=True)
    File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in 
system_output
  verbose=verbose, args=args).stdout
    File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
  "Command returned non-zero exit status")
  CmdError: Command 
 failed, rc=1, 
Command returned non-zero exit status
  * Command:
  /home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_
  generic.sh 079 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  Exit status: 1
  Duration: 13.813601017

  stdout:
  Creating zfs pool testpool..
  Creating zfs file systems test and scratch in testpool..
  VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  FSTYP -- zfs
  PLATFORM  -- Linux/aarch64 wright-kernel 4.10.0-38-generic
  MKFS_OPTIONS  -- testpool/scratch
  MOUNT_OPTIONS -- testpool/scratch /mnt/scratch

  generic/079- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad)
  --- tests/generic/079.out 2017-11-15 07:40:51.054794973 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad
2017-11-15 07:59:52.910100549 +
  @@ -1,7 +1,6 @@
   QA output created by 079
   *** starting up
  -testing immutable...PASS.
  -testing append-only...PASS.
  -testing immutable as non-root...PASS.
  -testing append-only as non-root...PASS.
  +acl: Function not implemented
  ...
  (Run 'diff -u tests/generic/079.out 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad'
  to see the entire diff)
  Ran: generic/079
  Failures: generic/079
  Failed 1 of 1 tests

  Destroying zfs pool testpool
  Removing VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42
  ProcVersionSignature: User Name 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic aarch64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 15 03:29 seq
   crw-rw 1 root audio 116, 33 Nov 15 03:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:

  Date: Wed Nov 15 06:27:54 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-38-generic N/A
   linux-backports-modules-4.10.0-38-generic  N/A
   linux-firmware 1.164.1

[Kernel-packages] [Bug 1731269] Re: linux: 4.10.0-40.44 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza 
(kleber-souza)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza 
(kleber-souza)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza 
(kleber-souza)

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1731270
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Friday, 17. November 2017 15:33 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1731270
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Promoted to proposed
+ phase: Uploaded
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 17. November 2017 15:33 UTC

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

Title:
  linux: 4.10.0-40.44 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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: 1731270
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1731269] Re: linux: 4.10.0-40.44 -proposed tracker

[Kleber Sacilotto de Souza]

** Summary changed:

- linux: 4.10.0-41.45 -proposed tracker
+ linux: 4.10.0-40.44 -proposed tracker

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

Title:
  linux: 4.10.0-40.44 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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: 1731270
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1732424] Re: Surface Pro 4. System hangs when suspended or hibernated

[Joseph Salisbury]

This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

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

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

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

Title:
  Surface Pro 4. System hangs when suspended or hibernated

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have a Surface Pro 4. I have problems with sleep and hibernation on
  my computer, because once it's turned on, the system won't wake up and
  you have to force the power off.

  I have tried several kernels:

  *The normal version

  *linux-image-4.9.0-rc8-mssp4+_4.9.0-rc8-mssp4+-10.00. Custom_amd64
  (special for Surface)

  *The last 4.14 kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1532 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov 15 13:13:19 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (24 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1732238] Re: arm64: Unfair rwlock can stall the system

[dann frazier]

This has been resolved with the following commits upstream:


commit d133166146333e1f13fc81c0e6c43c8d99290a8a
Author: Will Deacon 

locking/qrwlock: Prevent slowpath writers getting held up by
fastpath

commit 087133ac90763cd339b6b67f2998f87dcc136c52
Author: Will Deacon 

locking/qrwlock, arm64: Move rwlock implementation over to qrwlocks

commit b519b56e378ee82caf9b079b04f5db87dedc3251
Author: Will Deacon 

locking/qrwlock: Use atomic_cond_read_acquire() when spinning in
qrwlock

commit 4df714be4dcf40bfb0d4af0f851a6e1977afa02e
Author: Will Deacon 

locking/atomic: Add atomic_cond_read_acquire()

commit e0d02285f16e8d5810f3d5d5e8a5886ca0015d3b
Author: Will Deacon 

locking/qrwlock: Use 'struct qrwlock' instead of 'struct __qrwlock

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

Title:
  arm64: Unfair rwlock can stall the system

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

Bug description:
  [Impact]
  There is a long-standing upstream bug with the ARM64 specific implementation 
of RW locks. The implementation can starve writers under lock contention 
leading to RCU stalls and general system instability.

  [Test Case]
  $ stress-ng --kill 0 -t 300 -v

  You'll see the console fill with messages like:

  [ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 2534.428606]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=6770 
  [ 2534.437029](detected by 0, t=15005 jiffies, g=1479, c=1478, q=473)
  [ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 2714.629181]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=12819 
  [ 2714.637692](detected by 116, t=60058 jiffies, g=1479, c=1478, 
q=1736)
  [ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[kworker/0:5:1464]
  [ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s! 
[systemd-network:2936]

  [Regression Risk]
  TBD

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

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

[Kernel-packages] [Bug 1732620] Re: AMD Naples server failed with the tsc test in monotonic_time testsuite

[Joseph Salisbury]

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

Title:
  AMD Naples server failed with the tsc test in monotonic_time testsuite

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This test failed on node lodygin (AMD Naples) constantly against every
  kernel. This issue can be found in older kernel as well.

  Steps:
   1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
   2. make -C autotest-client-tests/monotonic_time/src
   3. sudo 

  $ sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc
  INFO: time_test: new tsc-warp maximum:  -931
  INFO: time_test: running tsc test on 128 cpus for 300 seconds
  INFO: time_test: new tsc-warp maximum: -9576
  INFO: time_test: new tsc-warp maximum:-10583
  INFO: time_test: new tsc-warp maximum:-10640
  INFO: time_test: new tsc-warp maximum:-10925
  FAIL: tsc-worst-warp=-10925

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: User Name 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 15 09:23 seq
   crw-rw 1 root audio 116, 33 Nov 15 09:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Nov 16 07:28:18 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AMD Corporation Speedway
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RSW1001E
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Speedway
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRSW1001E:bd07/24/2017:svnAMDCorporation:pnSpeedway:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnSpeedway:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: Speedway
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

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

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

[Kernel-packages] [Bug 1732755] Re: package linux-image-generic 4.4.0.98.103 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127

[Joseph Salisbury]

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

Title:
  package linux-image-generic 4.4.0.98.103 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return
  code 127

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tengo constantes reinicios del sistema, y me aparecen carteles con
  informes de errores de forma permanente. Necesito una solución también
  ya que el audacius no permite que las canciones que se suben se puedan
  seguir escuchando luego de apagar el sistema o de que se reinicie ya
  que también marca constantes errores.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.98.103
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fofi   1620 F pulseaudio
  Date: Thu Nov 16 10:55:54 2017
  ErrorMessage: problemas de dependencias - se deja sin configurar
  HibernationDevice: RESUME=UUID=62b92eab-31f1-4a15-88b4-d9e9dac0ab1f
  InstallationDate: Installed on 2016-12-23 (328 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=39dc8038-c0b3-4768-91a6-e72cf0f6c7f3 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.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6
  RfKill:
   
  SourcePackage: linux-meta
  StagingDrivers: r8188eu
  Title: package linux-image-generic 4.4.0.98.103 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: G31M-VS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd04/13/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-VS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   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/1731264

Title:
  linux: 4.4.0-101.124 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1731266
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1728927] Re: linux: 4.13.0-17.20 -proposed tracker

[Taihsiang Ho]

Due to the limited lab resource this week for the certification lab
migration. Only partial features of this kernel are available to be
tested. Set it as invalid so the flow could move forward as usual.

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

Title:
  linux: 4.13.0-17.20 -proposed tracker

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

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

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

  backports: 1728930,1728935,1728937
  derivatives: 1730611
  -- 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/1728927/+subscriptions

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

[Kernel-packages] [Bug 1732804] Re: [Zesty/Artful] On ARM64 PCIE physical function passthrough guest fails to boot

[Manoj Iyer]

A test kernel is available in this PPA:
https://launchpad.net/~centriq-team/+archive/ubuntu/lp1732804/

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

Title:
  [Zesty/Artful] On ARM64 PCIE physical function passthrough guest fails
  to boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Passing through a physical function like the Mellanox PCIE ethernet 
controller causes the guest to fail booting, and host reports Hardware Error. 
  == Host ==
  [109920.834703] {1}[Hardware Error]: Hardware error from APEI Generic 
Hardware Error Source: 4
  [109920.842142] {1}[Hardware Error]: event severity: recoverable
  [109920.847848] {1}[Hardware Error]:  precise tstamp: 2017-11-16 23:20:05
  [109920.854385] {1}[Hardware Error]:  Error 0, type: recoverable
  [109920.860111] {1}[Hardware Error]:   section_type: PCIe error
  [109920.865718] {1}[Hardware Error]:   port_type: 0, PCIe end point
  [109920.871708] {1}[Hardware Error]:   version: 3.0
  [109920.876343] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
  [109920.882559] {1}[Hardware Error]:   device_id: :01:00.0
  [109920.888113] {1}[Hardware Error]:   slot: 0
  [109920.892285] {1}[Hardware Error]:   secondary_bus: 0x00
  [109920.897489] {1}[Hardware Error]:   vendor_id: 0x15b3, device_id: 0x1013
  [109920.904172] {1}[Hardware Error]:   class_code: 02
  [109920.909378] vfio-pci :01:00.0: aer_status: 0x0004, aer_mask: 
0x
  [109920.916675] Malformed TLP
  [109920.916678] vfio-pci :01:00.0: aer_layer=Transaction Layer, 
aer_agent=Receiver ID
  [109920.924573] vfio-pci :01:00.0: aer_uncor_severity: 0x00062010
  [109920.930736] vfio-pci :01:00.0:   TLP Header: 4a008040 0100 
0100 
  [109920.938548] vfio-pci :01:00.0: broadcast error_detected message
  [109921.965056] pcieport :00:00.0: downstream link has been reset
  [109921.965062] vfio-pci :01:00.0: broadcast mmio_enabled message
  [109921.965066] vfio-pci :01:00.0: broadcast resume message
  [109921.965070] vfio-pci :01:00.0: AER: Device recovery successful
  == Guest ==
  EFI stub: Booting Linux Kernel...
  EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services and installing virtual address map...
  [1.518252] kvm [1]: HYP mode not available
  [2.578929] mlx5_core :05:00.0: mlx5_core_set_issi:778:(pid 152): 
Failed to query ISSI err(-1) status(0) synd(0)
  [2.582424] mlx5_core :05:00.0: failed to set issi
  [2.616756] mlx5_core :05:00.0: mlx5_load_one failed with error code -1

  This is because, virtualization of physical functions are broken on
  systems with Maximum Payload Size bigger than 128. QDF2400 FW tries to
  maximize this setting. We have observed an MPS of 512 on QDF2400
  systems.

  [Fix]
  Patches are in linux-next:
  523184972b28 vfio/pci: Virtualize Maximum Payload Size
  523184972b28 vfio/pci: Virtualize Maximum Payload Size

  [Testing]
  With the above patches applied the guest is able to boot when PCIE physical 
function is passthrough and we don't see the errors on the host system. 
  == On the Guest ==
  ubuntu@ubuntu-pcitest:~$ lspci
  00:00.0 Host bridge: Red Hat, Inc. Device 0008
  00:01.0 PCI bridge: Red Hat, Inc. Device 000c
  00:01.1 PCI bridge: Red Hat, Inc. Device 000c
  00:01.2 PCI bridge: Red Hat, Inc. Device 000c
  00:01.3 PCI bridge: Red Hat, Inc. Device 000c
  00:01.4 PCI bridge: Red Hat, Inc. Device 000c
  00:01.5 PCI bridge: Red Hat, Inc. Device 000c
  01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01)
  02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01)
  03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
  04:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
  05:00.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]

  ubuntu@ubuntu-pcitest:~$ lsmod | grep mlx
  mlx5_core 471040 0
  devlink 36864 1 mlx5_core
  ptp 28672 1 mlx5_core

  [Regression Potential]
  Two patches to drivers/vfio/pci were cleanly cherry picked from linux-next 
and applied to Artful/Zesty. Tested on ARM64 QDF2400 system and no regressions 
were found.

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

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

[Kernel-packages] [Bug 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-101.124
/xenial-proposed-published.html

** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: In Progress => Fix Released

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

Title:
  linux: 4.4.0-101.124 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1731266
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-101.124
/xenial-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux: 4.4.0-101.124 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1731266
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1730449] Re: linux-azure-edge: 4.13.0-1003.3 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux-azure-edge: 4.13.0-1003.3 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.13.0-1003.3 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/1730449/+subscriptions

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

[Kernel-packages] [Bug 1730660] Re: Set PANIC_TIMEOUT=10 on Power Systems

[Stefan Bader]

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

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

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

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

Title:
  Set PANIC_TIMEOUT=10 on Power Systems

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

Bug description:
  [Impact]
  When stopping CPUs fail when doing kdump, the system will hang 
indefinitively, instead of rebooting. With this option set, it will reboot 
after 10 seconds when that happens.

  This setting has been the default for trusty, where panic_timeout is
  10. Later releases set it to 0.

  [Test Case]
  When booting a kernel, /proc/sys/kernel/panic should be 10. It's 0 for 
xenial, zesty and artful. After the fix, it's 10.

  [Regression Potential]
  For users that rely on the setting as 0, they will see their system reboot 10 
seconds after a panic. They can set it back to 0 or other value. Though, on 
some rare cases, the system might not boot enough for this setting to be set. 
Balancing that with the case where kdump is used and the system is expected to 
boot, we expect the 10 seconds setting is okay.

  ===

  For ppc64le, in some rare crash cases, kdump won't load unless timeout
  is greater than 0. Only 10 has been tested by IBM, so using a smaller
  value may not work.

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

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

[Kernel-packages] [Bug 1729119] Re: NVMe timeout is too short

[Stefan Bader]

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

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

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

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

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

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

Title:
  NVMe timeout is too short

Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  New
Status in linux-aws source package in Zesty:
  Invalid
Status in linux source package in Artful:
  New
Status in linux-aws source package in Artful:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some NVMe operations time out too quickly. The module parameters allow the 
timeouts to be extended, but only up to 255s, as the counters are bytes. 

  [Fix]
  The underlying parameters are unsigned ints, so make the module parameters 
unsigned ints too, by picking patch 
http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html

  [Regression Potential]
  Very limited: only types of module parameters are changing, the patch is 
easily reviewable.

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

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

[Kernel-packages] [Bug 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

[Daniel Axtens]

Just as an update: I am working with Jay V on a set of patches to drop
the oversized packets at the openvswitch/bridge level to prevent the
crash I mentioned.

But that is not sufficient to solve the underlying problem: there will
still be packet loss when there's an MTU mismatch here. A device in AIX
with a 64k MTU being bridged (via openvswitch or a native bridge) to a
device with a 1500 or 9000 byte MTU is never going to work reliably and
efficiently, and IBM will need to figure out how they want to solve
this.

Regards,
Daniel

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

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  
  == SRU Justification ==
  Commit 66aa0678ef is request to fix four issues with the ibmveth driver.
  The issues are as follows:
  - Issue 1: ibmveth doesn't support largesend and checksum offload features 
when configured as "Trunk".
  - Issue 2: SYN packet drops seen at destination VM. When the packet
  originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO
  server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth
  receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag.
  - Issue 3: First packet of a TCP connection will be dropped, if there is
  no OVS flow cached in datapath.
  - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.

  The details for the fixes to these issues are described in the commits
  git log.



  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---

   - Issue 1: ibmveth doesn't support largesend and checksum offload features
     when configured as "Trunk". Driver has explicit checks to prevent
     enabling these offloads.

   - Issue 2: SYN packet drops seen at destination VM. When the packet
     originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
     IO server's inbound Trunk ibmveth, on validating "checksum good" bits
     in ibmveth receive routine, SKB's ip_summed field is set with
     CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
     Bridge) and delivered to outbound Trunk ibmveth. At this point the
     outbound ibmveth transmit routine will not set "no checksum" and
     "checksum good" bits in transmit buffer descriptor, as it does so only
     when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
     delivered to destination VM, TCP layer receives the packet with checksum
     value of 0 and with no checksum related flags in ip_summed field. This
     leads to packet drops. So, TCP connections never goes through fine.

   - Issue 3: First packet of a TCP connection will be dropped, if there is
     no OVS flow cached in datapath. OVS while trying to identify the flow,
     computes the checksum. The computed checksum will be invalid at the
     receiving end, as ibmveth transmit routine zeroes out the pseudo
     checksum value in the packet. This leads to packet drop.

   - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
     When Physical NIC has GRO enabled and when OVS bridges these packets,
     OVS vport send code will end up calling dev_queue_xmit, which in turn
     calls validate_xmit_skb.
     In validate_xmit_skb routine, the larger packets will get segmented into
     MSS sized segments, if SKB has a frag_list and if the driver to which
     they are delivered to doesn't support NETIF_F_FRAGLIST feature.

  Contact Information = Bryant G. Ly/b...@us.ibm.com

  ---uname output---
  4.8.0-51.54

  Machine Type = p8

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

  ---Steps to Reproduce---
   Increases performance greatly

  The patch has been accepted upstream:
  https://patchwork.ozlabs.org/patch/764533/

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

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

[Kernel-packages] [Bug 1732651] Re: lttng-smoke-test failed on Xenial s390x

[Colin Ian King]

I tried the machine where this had failed to pass and observed that the
DKMS modules for lttng had not been built by DKMS for some reason.

Looking at /var/log/apt/history.log the following happened:

1. lttng 2.8.0-1ubuntu1~16.04.2 was installed
2. new kernel 4.4.0-101 was installed
3. possibly failed to build lttng for 4.4.0-101
4. update, pulled in lttng 2.8.0-1ubuntu1~16.04.3
5. this didn't build for 4.4.0-101 
6. lttng test fail because there were no lttng built modules

I just ran sudo apt-get install --reinstall lttng-modules-dkms to ensure
it got rebuild and then I was able to run the tests perfectly well.

Looking at https://wiki.kubuntu.org/Kernel/Dev/DKMSPackaging it states:

"Limitation of DKMS

1. DKMS may not work well after a large change of kernel ABI - Using DKMS on a 
stable release kernel will be a better idea.
2. Make sure the we have toolchains and kernel header installed.
3. Using DKMS on a netbook is not a smart idea - It takes too much time to 
build the kernel module after kernel upgrading.
4. DKMS modules will not be loaded if there are another ones in initrd."

I wonder if the change in ABI was the issue.


I suspect the following is necessary if a large ABI change occurs:

ls /usr/src/linux-headers-* -d | sed -e 's/.*linux-headers-//' | \
> sort -V | tac | sudo xargs -n1 /usr/lib/dkms/dkms_autoinstaller start

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

Title:
  lttng-smoke-test failed on Xenial s390x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With lttng-module-dkms version 2.8.0-1ubuntu1~16.04.3, this test will
  failed on s390x instances.

  == lttng smoke test of session create/destroy ==
  Spawning a session daemon
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-113358-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)
   
  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)
   
  lttng smoke test trace open/close system calls SKIPPED for s390x
   
  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-113358-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed
   
  Summary: 3 passed, 3 failed
  stderr:
  Error: Unable to list kernel events: Kernel tracer not available
  Error: Command error
  Error: Event sched_switch: Kernel tracer not available (channel channel0, 
session test-kernel-session)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  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.12
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [ 1758.314033] docker0: port 1(veth38d28b9) entered disabled state
   [ 1758.314450] device veth38d28b9 left promiscuous mode
   [ 1758.314452] docker0: port 1(veth38d28b9) entered disabled state
  Date: Thu Nov 16 04:21:00 2017
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-101-generic N/A
   linux-backports-modules-4.4.0-101-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1728927] Re: linux: 4.13.0-17.20 -proposed tracker

[Po-Hsu Lin]

4.13.0-17.20 - generic
Regression test CMPL.

Issue to note in amd64:
  hwclock - lodygin will have time changed to 2080, bug 1714229
  libhugetlbfs - failed 7 (Heap did not shrink, small_const is not hugepage), 
killed by signal 7, bad config 1
  monotonic_time - tsc failed on lodygin, bug 1732620
  ubuntu_ecryptfs - directory-concurrent.sh.ext2 failed with "failed to 
fork child" on michael only
  ubuntu_fan_smoke_test - fanatic docker test failed, unable to fetch file 
(systemd issue)
  ubuntu_kvm_unit_tests - 6 failed on michael, 59 failed on lodygin, 25 failed 
on amaura

Issue to note in arm64:
  libhugetlbfs - failed 1 (Heap did not shrink), killed by signal 1, bad config 
1
  rtc - Update IRQs not supported
  ubuntu_docker_smoke_test - Failed to fetch file, looks like a firewall issue
  ubuntu_fan_smoke_test - fanatic docker test failed, unable to fetch file 
(systemd issue)
  ubuntu_kvm_smoke_test - Failed to fetch file, looks like a firewall issue
  ubuntu_stress_smoke_test - Failed to fetch file, looks like a firewall issue
  ubuntu_zfs_xfs_generic - test 079 (bug 1732370), 317 failed

Issue to note in i386:
  libhugetlbfs - failed 4 (Heap did not shrink, small_bss is not hugepage), 
killed by signal 4, bad config 1
  ubuntu_fan_smoke_test - fanatic docker test failed, unable to fetch file 
(systemd issue)

Issue to note in ppc64le:
  libhugetlbfs - 7 failed (Heap did not shrink, small_const is not hugepage), 
killed by signal 6
  rtc - Update IRQs not supported
  ubuntu_fan_smoke_test - fanatic docker test failed, unable to fetch file 
(systemd issue)
  ubuntu_kvm_smoke_test - uvtool issue, bug 1452016

Issue to note in s390x (Ubuntu on LPAR):
  aio_dio_bugs - event res -22, bug 1730895
  libhugetlbfs - failed 11 (Address is not hugepage, Heap not on hugepages, 
small_const/small_data is not hugepage), killed by signal 7, bad config 1
  scrashme - failed to build bug 1689240
  ubuntu_kvm_smoke_test - uvtool issue, bug 1452016

Issue to note in s390x (zKVM):
  aio_dio_bugs - event res -22, bug 1730895
  libhugetlbfs - failed 11 (Address is not hugepage, Heap not on hugepage, 
small_const/small_data is not hugepage), killed by signal 7, bad config 1
  scrashme - failed to build bug 1689240
  ubuntu_fan_smoke_test - fanatic docker test failed, unable to fetch file 
(systemd issue)
  ubuntu_kvm_smoke_test - uvtool issue, bug 1452016

Issue to note in s390x (zVM):
  aio_dio_bugs - event res -22, bug 1730895
  libhugetlbfs - IOError: [Errno 95] Operation not supported, bug 1729510
  scrashme - failed to build bug 1689240
  ubuntu_fan_smoke_test - fanatic docker test failed, unable to fetch file 
(systemd issue)
  ubuntu_kvm_smoke_test - uvtool issue, bug 1452016

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

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

** Tags added: regression-testing-passed

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

Title:
  linux: 4.13.0-17.20 -proposed tracker

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

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

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

  backports: 1728930,1728935,1728937
  derivatives: 1730611
  -- 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/1728927/+subscriptions

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

[Kernel-packages] [Bug 1732739] Re: lxd test broken by test systemd-resolv environment

[Andy Whitcroft]

** Also affects: ubuntu-fan (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-fan (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-fan (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  lxd test broken by test systemd-resolv environment

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  New
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  Switching the test environment to use netplan/systemd-resolvd
  uncovered an issue in the DEP8 test script for testing lxd. It is
  possible that there is more than one default route found, so we need
  to limit our scope to just the first one found.

  SRU justification:

  Impact: The environment running the DEP8 tests may have multiple
  default routes set. This is not anticipated by the test script running
  the lxd test and thus causes test failures. While this was uncovered
  by the netplan changes that happened in Artful, it potentially can
  happen in older releases, too.

  Fix: Adding an exit statement to the awk script after finding the fist
  default route.

  Testcase: For the Canonical CI environment the fix will only be
  obvious for Artful and later releases. Backported into older releases
  / environments will only make the test more robust and verification
  criteria is to not break.

  Regression risk: minimal as the change is only in the dep8 code.

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

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

[Kernel-packages] [Bug 1732739] Re: lxd test broken by test systemd-resolv environment

[Stefan Bader]

This part was fixed 0.12.6

** Changed in: ubuntu-fan (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: ubuntu-fan (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: ubuntu-fan (Ubuntu Artful)
   Status: New => Fix Released

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

Title:
  lxd test broken by test systemd-resolv environment

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  New
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  Switching the test environment to use netplan/systemd-resolvd
  uncovered an issue in the DEP8 test script for testing lxd. It is
  possible that there is more than one default route found, so we need
  to limit our scope to just the first one found.

  SRU justification:

  Impact: The environment running the DEP8 tests may have multiple
  default routes set. This is not anticipated by the test script running
  the lxd test and thus causes test failures. While this was uncovered
  by the netplan changes that happened in Artful, it potentially can
  happen in older releases, too.

  Fix: Adding an exit statement to the awk script after finding the fist
  default route.

  Testcase: For the Canonical CI environment the fix will only be
  obvious for Artful and later releases. Backported into older releases
  / environments will only make the test more robust and verification
  criteria is to not break.

  Regression risk: minimal as the change is only in the dep8 code.

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

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

[Kernel-packages] [Bug 1732717] Re: docker test broken by systemd-resolv environment

[Andy Whitcroft]

** Also affects: ubuntu-fan (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-fan (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-fan (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  docker test broken by systemd-resolv environment

Status in ubuntu-fan package in Ubuntu:
  In Progress
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  New
Status in ubuntu-fan source package in Artful:
  New

Bug description:
  Inside a docker container DNS lookups are routed to 127.0.0.11:53 which is 
provided by the docker environment in some way. The real DNS service is taken 
from the hosts /etc/resolv.conf. The docker man page claims that selecting a 
good automatic default would not work if the hosts uses local resolvers 
(127.0.0.0/8).
  Since switching to netplan/systemd-resolvd there is only a local resolver 
(127.0.0.53) added to /etc/resolv.conf on the host. Surprisingly this does not 
seem to be an issue for an artful(or later) VM running on my own local desktop. 
But in the Canonical CI environment DNS lookups fail inside a docker container.

  SRU Justification:

  Impact: DNS lookups inside docker containers can fail if the host
  environment is set up to only use a local resolver. The built-in
  docker test of fanatic will always fail in that case.

  Fix: Add code to built-in tests which detect systemd-resolvd being in
  use and pass the IP address which systemd-resolv is using as forwarder
  with the --dns option to the docker run command.

  Testcase:
    - If the test host is using systemd-resolvd as its primary DNS
  server, there will be the following message in the test log:
    local docker test: *** Using DNS override ***
    --dns=
    - Otherwise no message is printed.
    - For all cases docker ADT test should (continue to) pass

  Risk of regression: minimal, only testing affected which is run as ADT
  tests.

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

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

[Kernel-packages] [Bug 1732747] Re: Add additional checks and information to testbed setup

[Stefan Bader]

This was fixed in 0.12.6

** Changed in: ubuntu-fan (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: ubuntu-fan (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: ubuntu-fan (Ubuntu Artful)
   Status: New => Fix Released

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

Title:
  Add additional checks and information to testbed setup

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  New
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  There are cases (main reason is to have more info when using the
  built-in fanatic tests for dep8 ADT tests) when additional info about
  the primary network interface used for Fan and about the DNS setup
  outside and inside the containers is useful. This gets added to the
  __payload_prepare function of fanatic which is used by both host and
  container setup.

  SRU justification:

  Impact: This changes only the built-in local docker and lxd test
  functionality of fanatic. It has no impact on normal operation. At the
  same time the additional code will be used for the changes which allow
  to make the docker test more robust in case of using systemd-resolvd
  as sole local resolver.

  Fix: Adding checks to __payload_prepare which print information but
  also will optionally wait if DNS seems not ready, yet.

  Testcase: Either running the build-in tests manually or checking the log 
files of ADT testing for statements like:
  - detected primary route through 
  - DNS: (systemd()|)

  Regression risk: low (verified by passing ADT testing)

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

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

[Kernel-packages] [Bug 1732747] Re: Add additional checks and information to testbed setup

[Andy Whitcroft]

** Also affects: ubuntu-fan (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-fan (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-fan (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  Add additional checks and information to testbed setup

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  New
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  There are cases (main reason is to have more info when using the
  built-in fanatic tests for dep8 ADT tests) when additional info about
  the primary network interface used for Fan and about the DNS setup
  outside and inside the containers is useful. This gets added to the
  __payload_prepare function of fanatic which is used by both host and
  container setup.

  SRU justification:

  Impact: This changes only the built-in local docker and lxd test
  functionality of fanatic. It has no impact on normal operation. At the
  same time the additional code will be used for the changes which allow
  to make the docker test more robust in case of using systemd-resolvd
  as sole local resolver.

  Fix: Adding checks to __payload_prepare which print information but
  also will optionally wait if DNS seems not ready, yet.

  Testcase: Either running the build-in tests manually or checking the log 
files of ADT testing for statements like:
  - detected primary route through 
  - DNS: (systemd()|)

  Regression risk: low (verified by passing ADT testing)

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

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

[Kernel-packages] [Bug 1732651] Re: lttng-smoke-test failed on Xenial s390x

[Colin Ian King]

Hrm, tried this on an s390x VM:

$ uname -a
Linux ckingvm2 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:39 UTC 2017 
s390x s390x s390x GNU/Linux

dpkg -l | grep lttng
ii  liblttng-ctl0:s390x  2.7.1-2ubuntu1 
s390xLTTng control and utility library
ii  liblttng-ust-ctl2:s390x  2.7.1-1
s390xLTTng 2.0 Userspace Tracer (trace control library)
ii  liblttng-ust-dev:s390x   2.7.1-1
s390xLTTng 2.0 Userspace Tracer (development files)
ii  liblttng-ust-python-agent0:s390x 2.7.1-1
s390xLTTng 2.0 Userspace Tracer (Python agent native library)
ii  liblttng-ust0:s390x  2.7.1-1
s390xLTTng 2.0 Userspace Tracer (tracing libraries)
ii  lttng-modules-dkms   2.8.0-1ubuntu1~16.04.3 
all  Linux Trace Toolkit (LTTng) kernel modules (DKMS)
ii  lttng-tools  2.7.1-2ubuntu1 
s390xLTTng control and utility programs

ubuntu@ckingvm2:~$ sudo autotest/client/autotest-local 
autotest/client/tests/ubuntu_lttng_smoke_test/control
11:29:35 INFO | Writing results to /home/ubuntu/autotest/client/results/default
11:29:35 INFO | START   timestamp=1510918175localtime=Nov 
17 11:29:35   
11:29:35 INFO | START   ubuntu_lttng_smoke_test.lttng-smoke-test
ubuntu_lttng_smoke_test.lttng-smoke-testtimestamp=1510918175
localtime=Nov 17 11:29:35   
11:29:40 ERROR| [stderr] [warning] Tracer discarded 1340 events between 
[11:29:38.065061128] and [11:29:38.150240071] in trace UUID 
6614a11b486b459bce703191741816, at path: 
"/tmp/lttng-kernel-trace-1494-session/kernel", within stream id 0, at relative 
path: "channel0_0". You should consider recording a new trace with larger 
buffers or with fewer events enabled.
11:29:40 INFO | == lttng smoke test of session create/destroy ==
11:29:40 INFO | Session test-kernel-session created.
11:29:40 INFO | Traces will be written in /tmp/lttng-kernel-trace-1494-session
11:29:40 INFO | PASSED (lttng create)
11:29:40 INFO | Session test-kernel-session destroyed
11:29:40 INFO | PASSED (lttng destroy)
11:29:40 INFO |  
11:29:40 INFO | == lttng smoke test list kernel events ==
11:29:40 INFO | PASSED (lttng list --kernel)
11:29:40 INFO |  
11:29:40 INFO | lttng smoke test trace open/close system calls SKIPPED for s390x
11:29:40 INFO |  
11:29:40 INFO | == lttng smoke test trace context switches ==
11:29:40 INFO | Session test-kernel-session created.
11:29:40 INFO | Traces will be written in /tmp/lttng-kernel-trace-1494-session
11:29:40 INFO | PASSED (lttng create)
11:29:40 INFO | Kernel event sched_switch created in channel channel0
11:29:40 INFO | PASSED (lttng enable-event)
11:29:40 INFO | Tracing started for session test-kernel-session
11:29:40 INFO | PASSED (lttng start)
11:29:40 INFO | Waiting for data availability.
11:29:40 INFO | Tracing stopped for session test-kernel-session
11:29:40 INFO | PASSED (lttng stop)
11:29:40 INFO | Session test-kernel-session destroyed
11:29:40 INFO | PASSED (lttng destroy)
11:29:40 INFO | Found 19932 dd and 44645 context switches
11:29:40 INFO | PASSED (simple system call tracing with babeltrace)
11:29:40 INFO |  
11:29:40 INFO | Summary: 8 passed, 0 failed
11:29:40 INFO | GOOD
ubuntu_lttng_smoke_test.lttng-smoke-test
ubuntu_lttng_smoke_test.lttng-smoke-testtimestamp=1510918180
localtime=Nov 17 11:29:40   completed successfully
11:29:40 INFO | END GOOD
ubuntu_lttng_smoke_test.lttng-smoke-test
ubuntu_lttng_smoke_test.lttng-smoke-testtimestamp=1510918180
localtime=Nov 17 11:29:40   
11:29:40 INFO | END GOODtimestamp=1510918180
localtime=Nov 17 11:29:40   
11:29:40 INFO | Report successfully generated at 
/home/ubuntu/autotest/client/results/default/job_report.html

I just can't seem reproduce this issue.

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

Title:
  lttng-smoke-test failed on Xenial s390x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With lttng-module-dkms version 2.8.0-1ubuntu1~16.04.3, this test will
  failed on s390x instances.

  == lttng smoke test of session create/destroy ==
  Spawning a session daemon
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-113358-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)
   
  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)
   
  lttng smoke test trace open/close system calls SKIPPED for s390x
   
  == lttng smoke test 

[Kernel-packages] [Bug 1732894] [NEW] CPU call trace on AMD Raven Ridge after S3

[Timo Aaltonen]

Public bug reported:

[Impact]

Dmesg shows a call trace after S3 cycle.

This has been fixed in v4.14-rc1 with

commit 9662d43f523dfc0dc242ec29c2921c43898d6ae5
Author: Yazen Ghannam 
Date:   Mon Jul 24 12:12:28 2017 +0200

x86/mce/AMD: Allow any CPU to initialize the smca_banks array

Current SMCA implementations have the same banks on each CPU with the
non-core banks only visible to a "master thread" on each die. Practically,
this means the smca_banks array, which describes the banks, only needs to
be populated once by a single master thread.

CPU 0 seemed like a good candidate to do the populating. However, it's
possible that CPU 0 is not enabled in which case the smca_banks array won't
be populated.

Rather than try to figure out another master thread to do the populating,
we should just allow any CPU to populate the array.

Drop the CPU 0 check and return early if the bank was already initialized.
Also, drop the WARNing about an already initialized bank, since this will
be a common, expected occurrence.

The smca_banks array is only populated at boot time and CPUs are brought
online sequentially. So there's no need for locking around the array.

If the first CPU up is a master thread, then it will populate the array
with all banks, core and non-core. Every CPU afterwards will return
early. If the first CPU up is not a master thread, then it will populate
the array with all core banks. The first CPU afterwards that is a master
thread will skip populating the core banks and continue populating the
non-core banks.

Signed-off-by: Yazen Ghannam 
Signed-off-by: Borislav Petkov 
Acked-by: Jack Miller 
Cc: Linus Torvalds 
Cc: Peter Zijlstra 
Cc: Thomas Gleixner 
Cc: Tony Luck 
Cc: linux-edac 
Link: http://lkml.kernel.org/r/20170724101228.17326-4...@alien8.de
Signed-off-by: Ingo Molnar 

[Test case]

Suspend/resume Raven Ridge, see that it doesn't show the call trace any
more.

[Regression potential]

4.14 released with it, and it fixes code which "for now" checked only
CPU 0, so regressions potential is slim to none.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: Confirmed

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  CPU call trace on AMD Raven Ridge after S3

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

Bug description:
  [Impact]

  Dmesg shows a call trace after S3 cycle.

  This has been fixed in v4.14-rc1 with

  commit 9662d43f523dfc0dc242ec29c2921c43898d6ae5
  Author: Yazen Ghannam 
  Date:   Mon Jul 24 12:12:28 2017 +0200

  x86/mce/AMD: Allow any CPU to initialize the smca_banks array

  Current SMCA implementations have the same banks on each CPU with the
  non-core banks only visible to a "master thread" on each die. Practically,
  this means the smca_banks array, which describes the banks, only needs to
  be populated once by a single master thread.
  
  CPU 0 seemed like a good candidate to do the populating. However, it's
  possible that CPU 0 is not enabled in which case the smca_banks array 
won't
  be populated.
  
  Rather than try to figure out another master thread to do the populating,
  we should just allow any CPU to populate the array.
  
  Drop the CPU 0 check and return early if the bank was already initialized.
  Also, drop the WARNing about an already initialized bank, since this will
  be a common, expected occurrence.
  
  The smca_banks array is only populated at boot time and CPUs are brought
  online sequentially. So there's no need for locking around the array.
  
  If the first CPU up is a master thread, then it will populate the array
  with all banks, core and non-core. Every CPU afterwards will return
  early. If the first CPU up is not a master thread, then it will populate
  the array with all core banks. The first CPU afterwards that is a master
  thread will skip populating the core banks and continue populating the
  non-core banks.
  
  Signed-off-by: Yazen Ghannam 
  Signed-off-by: Borislav 

[Kernel-packages] [Bug 1730762] Re: 17.10 - suspend/resume failure - kernel-bug-exists-upstream

[venturia]

The two versions were not working.

A-

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

Title:
  17.10 - suspend/resume failure - kernel-bug-exists-upstream

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a failure in the resume process after the suspend.
  When I try to resume the system start, but the screen stay black while
  the disk seem be really busy.

  The only way to exit from this status is unplug the system before
  restart it.

  Let me know how to collect additional info (if necessary).

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   1948 F pulseaudio
   /dev/snd/controlC0:  alessandro   1948 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 22:59:45 2017
  HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13
  InstallationDate: Installed on 2016-07-09 (486 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp2s5no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Packard Bell NEC IMEDIA 5204
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Louis Bouchard]

Hello,

I would like to add that triggering a kernel dump in seconds following
the installation of the package remains a corner case in a test context
and not the usual behavior.

I have seen that too in my test scripts and syncing right after the
installation fixed the issue as well.

Bringing in the upstream change is a good solution.

...Louis

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  New
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Louis Bouchard]

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

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: In Progress

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

** Also affects: makedumpfile (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  New
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1730449] Re: linux-azure-edge: 4.13.0-1003.3 -proposed tracker

[Po-Hsu Lin]

4.13.0-1003.3 - azure
Regression test CMPL.

Issue to note in x86_64 (azure):
  ebizzy - failed on two instances (Basic_A0, Standard_A0), passed on the rest
  libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad 
config 3, passed on the rest
  monotonic_time - all three tests (or just tsc test) failed on some instances, 
passed on the rest
  ubuntu_kvm_smoke_test - CPU does not support KVM extensions
  ubuntu_kvm_unit_tests - test disabled
  ubuntu_ltp - test disabled
  ubuntu_lttng_smoke_test - some instances (Basic_A0, Standard_A0) failed with 
bug 1732651, passed on the rest
  ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in 
ubuntu-cloud container, Failed creating ubuntu-cloud container due to too many 
open files), passed on the rest
  ubuntu_qrt_kernel_panic - failed on only one instance (Basic_A4)
  ubuntu_unionmount_overlayfs_suite - bug 1727290

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => Po-Hsu 
Lin (cypressyew)

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

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

** Tags added: regression-testing-passed

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

Title:
  linux-azure-edge: 4.13.0-1003.3 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.13.0-1003.3 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/1730449/+subscriptions

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

[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[Anton Rostotskyi]

I see graphic errors on external monitors and following messages in logs
with 4.13.0 kernel. Errors appear after laptop works for 3-4 days
without reboot.

kernel: [173125.746076] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] 
*ERROR* uncleared fifo underrun on pipe A
kernel: [173125.746104] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] 
*ERROR* CPU pipe A FIFO underrun
kernel: [173125.795556] [drm:intel_check_cpu_fifo_underruns [i915]] *ERROR* 
fifo underrun on pipe B

Ubuntu 17.10, hardware is Dell Latitude E5540

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9.1

To 

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

[bugproxy]

--- Comment From hbath...@in.ibm.com 2017-11-17 03:21 EDT---
(In reply to comment #32)
> Hi, I am a little eager to add this without trying to resort to other
> solutions first.
>
> So, options are:
>
> 1) For some reason, this driver is not behaving correctly. Can you add the
> PowerIO folks to this bug on IBM side and let them do some investigation?

done.

>
> 2) network-online is not doing the correct thing. Well, from what I read,
> they indeed don't care much about this and think the program should wait for
> the network to be available. After eliminating 1, we should look into why
> network-online decides the network is online or why systemd would start
> kdump after that, and the ssh host would still not be reachable.
>

> 3) I would rather add the timeout but also conditionally checking for the
> host availability. That is: wait until it's available, then dump. If not
> available for the timeout duration, reboot.

Sounds reasonable.

Thanks
Hari

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

Title:
  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 98:be:94:03:18:48
Permanent HW Address: 98:be:94:03:18:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (Ethernet controller)

  39: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: VwX_.ndpeucax6V1
Parent ID: DUng.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f3
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f3
HW Address: 98:be:94:03:18:4b
Permanent HW Address: 98:be:94:03:18:4b
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (Ethernet controller)

  40: None 00.0: 10701 Ethernet
[Created at net.126]

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

[bugproxy]

--- Comment From hbath...@in.ibm.com 2017-11-17 03:10 EDT---
(In reply to comment #16)
> Noticed that the offset for crashkernel is set to 32MB in
> /etc/default/grub.d/kdump-tools..ppc64el file . Any specific reason
> why this value is chosen? With the default offset on powerpc being
> 128MB, this seems way off (considering there is only so much real
> memory available.) Can the offset (@32M) be stripped from
> /etc/default/grub.d/kdump-tools..ppc64el file to fall back to the
> kernel default..

The above concern seems to be addressed with the patch attached in bug 1658733.
I would rather prefer no offset though (letting the kernel to decide on the 
default offset)

btw, it is targeted for artful. Would that make it into 17.04 as well?

Thanks
Hari

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

Title:
  kdump-tools uses the wrong crashkernel command line parameter in
  ppc64le

Status in The Ubuntu-power-systems project:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  == Comment: #0 - Thiago Jung Bauermann  - 2017-03-24 
11:44:39 ==
  ---Problem Description---
  kdump-tools uses the wrong crashkernel command line parameter in ppc64le:

  u1704le?? grep crashkernel /boot/grub/grub.cfg
  linux   /boot/vmlinux-4.10.0-13-generic 
root=UUID=2d6f73c7-b463-4f02-9ec4-8d4afed0635d ro   crashkernel=384M-:128M

  128M of reserved memory is too small for ppc64le.

  That happens because /etc/default/grub.d/kdump-tools.cfg links to the
  wrong file:

  u1704le??  ls -l /etc/default/grub.d/
  total 8.0K
  lrwxrwxrwx 1 root root  39 Mar 24 13:34 kdump-tools.cfg -> 
/etc/default/grub.d/kdump-tools.default
  -rw-r--r-- 1 root root  80 Jan  5 08:07 kdump-tools.default
  -rw-r--r-- 1 root root 137 Jan  5 08:07 kdump-tools..ppc64el
  u1704le?? 

  As can be seen, it should be pointing to kdump-tools..ppc64el but
  isn't.

  Also, kdump-tools..ppc64el has two dots in it. That doesn't seem right.
  Possibly just a cosmetic issue, but it would be nice if that was fixed.
   
  Contact Information = thiag...@br.ibm.com 
   
  ---uname output---
  Linux u1704le 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Any ppc64le machine. In this case, a KVM guest hosted on an 
8286-42A. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   sudo apt intall kdump-tools
  Select 'Yes' when asked whether kdump should be enabled.
   
  Userspace tool common name: kdump 
   
  The userspace tool has the following bit modes: 64 bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for thiag...@br.ibm.com:
  -Attach ltrace and strace of userspace application.

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

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

[Kernel-packages] [Bug 1721511] Re: [Xenial] update OpenNSL kernel modules to 6.5.10

[Jesse Sung]

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

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

Title:
  [Xenial] update OpenNSL kernel modules to 6.5.10

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Currently we have 6.4.10 in the Xenial kernel. The latest OpenNSL
  Sep-27 release[1] updates kernel modules to 6.5.10.

  Since the module doesn't load automatically, this update shouldn't
  have any impact for people don't use the module.

  For the module itself, it loads without problem on a test system.

  [1] https://github.com/Broadcom-Switch/OpenNSL/tree/v3.4.1.5

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

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

[Kernel-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

[Kai-Heng Feng]

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

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Kernel-packages] [Bug 1722719] Re: HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

[Kai-Heng Feng]

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

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

Title:
  HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Alps touchpad with ID 0x120A + trackpoint will not be used for mass 
production machines.
  Touchpad 0x120A w/o trackpoint still reports it has a trackpoint, this will 
confuse userspace apps.

  [Fix]
  Reverts commit fcaa4a07d2a4b541e91da7a55d8b3331f96d1865, so 0x120A device is 
no longer a MT_CLS_WIN_8_DUAL device.

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  Minimal.
  This patch is for a single device in a specific driver.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1718654] Re: Touchpad input doesn't work after longer suspend.

[Jeppe Bundsgaard]

Kernel 4.14.0 and 4.13.12 fixes the problem. Thanks!

** Tags added: kernel-fixed-upstream

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

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

Title:
  Touchpad input doesn't work after longer suspend.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I resume my laptop from a longer (not sure what the threshold is
  yet) suspend, I don't get input from the touchpad, a short suspend
  cycle fixes it.

  Touchscreen works all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:20:56 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718654/+subscriptions

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

[Kernel-packages] [Bug 1729391] Re: Trackpad stops responding after suspend

[Jeppe Bundsgaard]

Kernel 4.14.0 and 4.13.12 fix the problem.

** Tags added: kernel-fixed-upstream

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

Title:
  Trackpad stops responding after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, the trackpad
  stops working after suspend (it actually works for a few seconds, then
  doesn't react). I can still use the touch screen.

  Please tell me which log-files to upload.

  Thanks

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

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