[Kernel-packages] [Bug 1747572] Re: CIFS SMB2/SMB3 does not work for domain based DFS

[Joseph Salisbury]

I built a test kernel with the three commits mentioned in the description.  The 
test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1747572

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

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

Thanks in advance!

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

Title:
  CIFS SMB2/SMB3 does not work for domain based DFS

Status in cifs-utils:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  There is upstream bug report:
  https://bugzilla.samba.org/show_bug.cgi?id=12917

  "Fix was merged upstream and should be in the next kernel update. Ask
  your distribution maintainers to backport it." Aurélien Aptel

  It looks like the following patches should be backported:

  [v3,3/3] CIFS: dump IPC tcon in debug proc file
  [v3,2/3] CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl
  [v3,1/3] CIFS: make IPC a regular tcon

  Link to patchwork: https://patchwork.kernel.org/project/cifs-
  client/list/?submitter=146481

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb  6 09:50:57 2018
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cifs-utils/+bug/1747572/+subscriptions

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

[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

[Joseph Salisbury]

@Johanns, does my test kernel fail for you as well?

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

Title:
  Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

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

Bug description:
  The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when
  booted as a dom0 under Xen.

  A similar bug was reported by someone else for archlinux
  (https://bugs.archlinux.org/task/57500).

  A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it
  fixes the problem for me.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7).

  Xen output:

  (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) 
(gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n  Fri Oct 13 15:58:41 UTC 2017
  (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9
  (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga
  (XEN) Xen image load base address: 0
  (XEN) Video information:
  (XEN)  VGA is text mode 80x25, font 8x16
  (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
  (XEN)  EDID info not retrieved because no DDC retrieval method detected
  (XEN) Disc information:
  (XEN)  Found 1 MBR signatures
  (XEN)  Found 1 EDD information structures
  (XEN) Xen-e820 RAM map:
  (XEN)   - 0009ec00 (usable)
  (XEN)  000f - 0010 (reserved)
  (XEN)  0010 - cb6cfc00 (usable)
  (XEN)  cb6cfc00 - cb723c00 (ACPI NVS)
  (XEN)  cb723c00 - cb725c00 (ACPI data)
  (XEN)  cb725c00 - cc00 (reserved)
  (XEN)  f800 - fc00 (reserved)
  (XEN)  fec0 - fed00400 (reserved)
  (XEN)  fed2 - feda (reserved)
  (XEN)  fee0 - fef0 (reserved)
  (XEN)  ffb0 - 0001 (reserved)
  (XEN)  0001 - 00013000 (usable)
  (XEN) New Xen image base address: 0xcb00
  (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
  (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K  15 ASL61)
  (XEN) ACPI: DSDT FFDC89E4, 47BC (r1   DELLdt_ex 1000 INTL 20050624)
  (XEN) ACPI: FACS CB6CFC00, 0040
  (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1   DELLst_ex 1000 INTL 20050624)
  (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K  15 ASL61)
  (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K  15 ASL61)
  (XEN) System RAM: 4022MB (4118964kB)
  (XEN) Domain heap initialised
  (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23
  (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
  (XEN) Using scheduler: SMP Credit Scheduler (credit)
  (XEN) Platform timer is 14.318MHz HPET
  (XEN) Detected 2926.007 MHz processor.
  (XEN) Initing memory sharing.
  (XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
  (XEN) Intel VT-d Snoop Control enabled.
  (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
  (XEN) Intel VT-d Queued Invalidation enabled.
  (XEN) Intel VT-d Interrupt Remapping not enabled.
  (XEN) Intel VT-d Posted Interrupt not enabled.
  (XEN) Intel VT-d Shared EPT tables not enabled.
  (XEN) :04:00.0: unknown type 4
  (XEN) I/O virtualisation enabled
  (XEN)  - Dom0 mode: Relaxed
  (XEN) Interrupt remapping disabled
  (XEN) ENABLING IO-APIC IRQs
  (XEN)  -> Using new ACK method
  (XEN) Allocated console ring of 16 KiB.
  (XEN) VMX: Supported advanced features:
  (XEN)  - APIC MMIO access virtualisation
  (XEN)  - APIC TPR shadow
  (XEN)  - Extended Page Tables (EPT)
  (XEN)  - Virtual-Processor Identifiers (VPID)
  (XEN)  - Virtual NMI
  (XEN)  - MSR direct-access bitmap
  (XEN) HVM: ASIDs enabled.
  (XEN) HVM: VMX enabled
  (XEN) HVM: Hardware Assisted Paging (HAP) detected
  (XEN) HVM: HAP page sizes: 4kB, 2MB
  (XEN) Brought up 4 CPUs
  (XEN) Dom0 has maximum 600 PIRQs
  (XEN) *** LOADING DOMAIN 0 ***
  (XEN)  Xen  kernel: 64-bit, lsb, compat32
  (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000
  (XEN) PHYSICAL MEMORY ARRANGEMENT:
  (XEN)  Dom0 alloc.:   00012000->00012400 (952940 pages to be 
allocated)
  (XEN)  Init. ramdisk: 00012d251000->00012575
  (XEN) VIRTUAL MEMORY ARRANGEMENT:
  (XEN)  Loaded kernel: 8100->82b69000
  (XEN)  Init. 

[Kernel-packages] [Bug 1744791] Re: [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in repo which is required for crash analysis of vmcore

[Joseph Salisbury]

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

Title:
  [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in
  repo which is required for crash analysis of vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  No debug kernel deb packages available for 4.13.0-25-generic kernel [Ubuntu 
18.04 ]
  Unable to analyze vmcore generated via crash. 

  ---uname output---
  Linux spoon2 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:55 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTC 
   
  ---Steps to Reproduce---
  Install 18.04 ppc64el
  upgrade kernel to 4.13.0-25-generic or 4.13.0-17-generic
  try configuring debug repo
  https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
  http://ddebs.ubuntu.com/pool/main/l/linux/
  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted 
universe multiverse
  EOF

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ECDCAD72428D7C01
  sudo apt-get update
  sudo apt-get install linux-image-$(uname -r)-dbgsym

  Warning /!\ Be aware that those packages are huge! (~600 MB)

  When installed, the debug kernel can be found under
  /usr/lib/debug/boot/ and crash is started by:

  crash  

  Crash command to analyze vmcore will not work as kernel debuginfo deb package 
is not found in repo . 
  root@spoon2:~# sudo apt-get install linux-image-$(uname -r)-dbgsym
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package linux-image-4.13.0-25-generic-dbgsym
  E: Couldn't find any package by glob 'linux-image-4.13.0-25-generic-dbgsym'
  E: Couldn't find any package by regex 'linux-image-4.13.0-25-generic-dbgsym'
  root@spoon2:~# 
   
  I was also not able to find this debug symbol for 18.04 kernel. I understand 
that the current 18.04 kernel is old and was removed from the archive. Is it 
correct?

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [i40e] LACP bonding start up race conditions

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1577140] Re: Wifi Ralink R3290 disabled by default in ubuntu 16.04

[Kai-Heng Feng]

Can you find the first bad -rc* kernel in [1] that has this regression?

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

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

Title:
  Wifi Ralink R3290 disabled by default in ubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have my personal laptop and it contains PCI Ralink r3290 wifi
  adaptor with bluetooth and when i have installed the fresh version of
  Ubuntu 16.04x64 it doesn’t work at all on boot up. The wifi is
  disabled by default and the it doesn’t activates even by pressing the
  key and when i go the network settings airplane mode is also enabled
  and when i try to disable airplane mode it switches back on. I dont
  know whats going wrong. Earlier my wifi works on ubuntu 15.04. I have
  tried almost every solution and none works in the latest LTS release.

  Please help I am unable to use internet in ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shankey1536 F pulseaudio
   /dev/snd/controlC1:  shankey1536 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May  1 17:02:12 2016
  HibernationDevice: RESUME=UUID=9fdda691-a6ae-4494-99e3-b76fde1f33a6
  InstallationDate: Installed on 2016-04-24 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard Compaq 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=609ae58a-a43f-4f7b-9a61-e21d3caf457a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.39
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.52
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.39:bd05/26/2015:svnHewlett-Packard:pnCompaq15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Compaq 15 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Nobuto Murata]

This might be related (not exactly the same):
https://sourceforge.net/p/e1000/bugs/524/
One says 1.6.42 fixed his issue.

Looks like Intel has around 10 releases between 1.4.25 and 2.1.14, so it may 
not be handy to bisect.
https://downloadcenter.intel.com/download/24411/Intel-Network-Adapter-Driver-for-PCIe-40-Gigabit-Ethernet-Network-Connections-Under-Linux-?product=82947

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

Title:
  [i40e] LACP bonding start up race conditions

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1752163] Re: computer freeze

[Kai-Heng Feng]

I guess it's the same one as LP: #1690085.

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

Title:
  computer freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Computer randomly freeze, not possible to do anything than reboot the system.
  Did alot of installs on the same day, not sure what is the cause.
  Running script to not have gpu installed, should not be a problem? am4 cpu 
with no apu.
  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prozac 2113 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 21:22:31 2018
  InstallationDate: Installed on 2018-02-16 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   lono wireless extensions.
   
   enp38s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=779380b7-d22a-4038-a9a4-cdf71b00b881 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0612
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0612:bd05/15/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

[Nobuto Murata]

** Attachment added: "bond2_status.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070466/+files/bond2_status.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/1753662

Title:
  [i40e] LACP bonding start up race conditions

Status in linux package in Ubuntu:
  New

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

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

[Nobuto Murata]

** Attachment added: "interfaces.50-cloud-init.cfg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070467/+files/interfaces.50-cloud-init.cfg

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

Title:
  [i40e] LACP bonding start up race conditions

Status in linux package in Ubuntu:
  New

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

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

[Nobuto Murata]

** Attachment added: "bond1_status.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070465/+files/bond1_status.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/1753662

Title:
  [i40e] LACP bonding start up race conditions

Status in linux package in Ubuntu:
  New

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

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

[Nobuto Murata]

Public bug reported:

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

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

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

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

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

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

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

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

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-116-generic 4.4.0-116.140
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
 crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Mar  6 06:46:32 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 002: ID 8087:8002 Intel Corp. 
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
 Bus 001 Device 002: ID 8087:800a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge R730
PciMultimedia:
 
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-116-generic N/A
 linux-backports-modules-4.4.0-116-generic  N/A
 linux-firmware 1.157.17
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.5
dmi.board.name: 072T6D
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.asset.tag: 0018880
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R730
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug cpe-onsite uec-images 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/1753662

Title:
  [i40e] LACP bonding start up race conditions

Status in linux package in Ubuntu:
  New

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

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

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

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

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

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

[Kernel-packages] [Bug 1326761] Re: Tevii S471 DVB-S2 card hangs on firmware upload

[Kai-Heng Feng]

Does is work prior to Linux kernel v3.13?

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

Title:
  Tevii S471 DVB-S2 card hangs on firmware upload

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have fresh installed Ubuntu Trusty Tahr (Server) with kernel 3.13.0-29.
  Firmware file dvb-fe-ds3000.fw is putted into /lib/firmware
  On a system cold start I see in syslog:

  Jun  5 16:00:54 MMC kernel: [9.601460] cx23885 driver version 0.0.3 loaded
  Jun  5 16:00:54 MMC kernel: [9.601881] CORE cx23885[0]: subsystem: 
d471:9022, board: TeVii S471 [card=35,autodetected]
  Jun  5 16:00:54 MMC kernel: [9.750010] cx23885_dvb_register() allocating 
1 frontend(s)
  Jun  5 16:00:54 MMC kernel: [9.758499] cx23885[0]: cx23885 based dvb card
  Jun  5 16:00:54 MMC kernel: [9.879035] DVB: registering new adapter 
(cx23885[0])
  Jun  5 16:00:54 MMC kernel: [9.879047] cx23885 :01:00.0: DVB: 
registering adapter 0 frontend 0 (Montage Technology DS3000)...
  Jun  5 16:00:54 MMC kernel: [9.894578] cx23885_dev_checkrevision() 
Hardware revision = 0xa5
  Jun  5 16:00:54 MMC kernel: [9.894595] cx23885[0]/0: found at 
:01:00.0, rev: 4, irq: 16, latency: 0, mmio: 0xfe80

  
  But if I try to scan channels by scan or tvheadend I see this repeated lines:

  Jun  5 16:01:04 MMC kernel: [   20.051633] ds3000_firmware_ondemand: Waiting 
for firmware upload (dvb-fe-ds3000.fw)...
  Jun  5 16:01:04 MMC kernel: [   20.052608] ds3000_firmware_ondemand: Waiting 
for firmware upload(2)...

  Card works under Debian linux kernel image from unstable repo (linux-
  image-3.14.1)

  manjur@MMC:~$ lsb_release -rd
  Description:Ubuntu 14.04 LTS
  Release:14.04
  manjur@MMC:~$ apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.29.35
Candidate:   3.13.0.29.35
Version table:
   *** 3.13.0.29.35 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.13.0.27.33 0
  500 http://kz.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   3.13.0.24.28 0
  500 http://kz.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.52
  ProcVersionSignature: Ubuntu 3.13.0-29.52-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Thu Jun  5 17:31:07 2014
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=e93b9d23-aced-4d3c-bb1e-07346406d8de ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-29-generic N/A
   linux-backports-modules-3.13.0-29-generic  N/A
   linux-firmware 1.127.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: E350M1/USB3
  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.60:bd05/21/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnE350M1/USB3: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/1326761/+subscriptions

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

[Kernel-packages] [Bug 1751234] Re: Unable to insert test_bpf module on Bionic s390x

[Po-Hsu Lin]

Note that this commit in #3 has been merged into the Bionic tree, but
it's not available in the 4.15.0-11 proposed kernel yet.

Will retest this for the next kernel.

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

Title:
  Unable to insert test_bpf module on Bionic s390x

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  The ubuntu_bpf_jit test failed on s2lp6g002 with Bionic kernel.

  Error message:
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument

  When you try to insert the module with insmod it shows:
  $ sudo insmod /lib/modules/4.15.0-9-generic/kernel/lib/test_bpf.ko
  insmod: ERROR: could not insert module 
/lib/modules/4.15.0-9-generic/kernel/lib/test_bpf.ko: Invalid module format

  $ dpkg -S /lib/modules/4.15.0-9-generic/kernel/lib/test_bpf.ko
  linux-image-4.15.0-9-generic: 
/lib/modules/4.15.0-9-generic/kernel/lib/test_bpf.ko

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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.8-0ubuntu10
  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 Feb 23 09:31:55 2018
  HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   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=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': '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/1751234/+subscriptions

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

[Kernel-packages] [Bug 1711299] Re: ubuntu_bpf test failed to build on s390x system

[Po-Hsu Lin]

On Bionic, the error message is different:

$ make
make[1]: Entering directory '/tmp/bionic/tools/testing/selftests/bpf'
make -C ../../../lib/bpf OUTPUT=/tmp/bionic/tools/testing/selftests/bpf/
make[2]: Entering directory '/tmp/bionic/tools/lib/bpf'
make[2]: Leaving directory '/tmp/bionic/tools/lib/bpf'
make -C ../../../lib/bpf OUTPUT=/tmp/bionic/tools/testing/selftests/bpf/
make[2]: Entering directory '/tmp/bionic/tools/lib/bpf'
make[2]: Leaving directory '/tmp/bionic/tools/lib/bpf'
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_verifier.c 
/tmp/bionic/tools/testing/selftests/bpf/libbpf.a 
/tmp/bionic/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -lrt -o 
/tmp/bionic/tools/testing/selftests/bpf/test_verifier
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_tag.c 
/tmp/bionic/tools/testing/selftests/bpf/libbpf.a 
/tmp/bionic/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -lrt -o 
/tmp/bionic/tools/testing/selftests/bpf/test_tag
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_maps.c 
/tmp/bionic/tools/testing/selftests/bpf/libbpf.a 
/tmp/bionic/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -lrt -o 
/tmp/bionic/tools/testing/selftests/bpf/test_maps
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_lru_map.c 
/tmp/bionic/tools/testing/selftests/bpf/libbpf.a 
/tmp/bionic/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -lrt -o 
/tmp/bionic/tools/testing/selftests/bpf/test_lru_map
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_lpm_map.c 
/tmp/bionic/tools/testing/selftests/bpf/libbpf.a 
/tmp/bionic/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -lrt -o 
/tmp/bionic/tools/testing/selftests/bpf/test_lpm_map
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_progs.c 
/tmp/bionic/tools/testing/selftests/bpf/libbpf.a 
/tmp/bionic/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -lrt -o 
/tmp/bionic/tools/testing/selftests/bpf/test_progs
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_align.c 
/tmp/bionic/tools/testing/selftests/bpf/libbpf.a 
/tmp/bionic/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -lrt -o 
/tmp/bionic/tools/testing/selftests/bpf/test_align
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_verifier_log.c 
/tmp/bionic/tools/testing/selftests/bpf/libbpf.a 
/tmp/bionic/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -lrt -o 
/tmp/bionic/tools/testing/selftests/bpf/test_verifier_log
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_dev_cgroup.c 
/tmp/bionic/tools/testing/selftests/bpf/libbpf.a 
/tmp/bionic/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -lrt -o 
/tmp/bionic/tools/testing/selftests/bpf/test_dev_cgroup
clang -I. -I./include/uapi -I../../../include/uapi \
 -Wno-compare-distinct-pointer-types  \
 -O2 -target bpf -emit-llvm -c 
/tmp/bionic/tools/testing/selftests/bpf/test_pkt_access.c -o - |  \
llc -march=bpf -mcpu=generic -filetype=obj -o 
/tmp/bionic/tools/testing/selftests/bpf/test_pkt_access.o
In file included from 
/tmp/bionic/tools/testing/selftests/bpf/test_pkt_access.c:8:
/usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not 
found
#include 
 ^~
1 error generated.
clang -I. -I./include/uapi -I../../../include/uapi \
 -Wno-compare-distinct-pointer-types  \
 -O2 -target bpf -emit-llvm -c 
/tmp/bionic/tools/testing/selftests/bpf/test_xdp.c -o - |  \
llc -march=bpf -mcpu=generic -filetype=obj -o 
/tmp/bionic/tools/testing/selftests/bpf/test_xdp.o
In file included from /tmp/bionic/tools/testing/selftests/bpf/test_xdp.c:8:
/usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not 
found
#include 
 ^~
1 error generated.
clang -I. -I./include/uapi -I../../../include/uapi \
 -Wno-compare-distinct-pointer-types  \
 -O2 -target bpf -emit-llvm -c 
/tmp/bionic/tools/testing/selftests/bpf/test_l4lb.c -o - |  \
llc -march=bpf -mcpu=generic -filetype=obj -o 
/tmp/bionic/tools/testing/selftests/bpf/test_l4lb.o
In file included from /tmp/bionic/tools/testing/selftests/bpf/test_l4lb.c:9:
/usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not 
found
#include 
 ^~
1 error generated.
clang -I. -I./include/uapi -I../../../include/uapi \
 -Wno-compare-distinct-pointer-types  \
 

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

[Kai-Heng Feng]

Please find the first bad -rc* kernel that has this issue.

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

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

[bugproxy]

--- Comment From bssrika...@in.ibm.com 2018-03-05 23:31 EDT---
Any updates on which build would this patch be included? this is currently 
gating KVM testing on DD 2.2.

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

Title:
  Power9 DD 2.2 needs HMI fixup backport of upstream
  patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
06:55:23 ==
  ---Problem Description---
  Power9 DD 2.2 needs HMI fixup backport of upstream 
patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   commit d075745d893c78730e4a3b7a60fca23c2f764081
  Author: Paul Mackerras 
  Date:   Wed Jan 17 20:51:13 2018 +1100

  KVM: PPC: Book3S HV: Improve handling of debug-trigger HMIs on POWER9
  

  Dependancy commit, looks like already present.
  commit 5080332c2c893118dbc18755f35c8b0131cf0fc4
  Author: Michael Neuling 
  Date:   Fri Sep 15 15:25:48 2017 +1000

  powerpc/64s: Add workaround for P9 vector CI load issue
  

   
  Contact Information = sathe...@in.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1753191] Re: Touchpad not working after installing Ubuntu 16.04 LTS

[Maksym Zhelyeznyakov]

This started happening once I installed Ubuntu on this PC. In fact, this
issue persists throughout all versions of linux I've installed
(Fedora/Manjaro/Mint). It wasn't happening on my windows install.

The mainline kernel installation didn't solve the issue.

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

** Tags added: kernel-bug-exists-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/1753191

Title:
  Touchpad not working after installing Ubuntu 16.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing Ubuntu 16.04 on my thinkpad x220t, my touchpad
  doesn't work at all.

  I do not see a Synaptics touchpad under cat /proc/bus/input/devices

  I've attached my output from dmesg, and I'll attach my output from
  devices, and my Xorg log in the comments

  Thank you in advance for the help
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demroz 1814 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=09061c6d-7452-46e9-8539-5c6c5078ef2a
  InstallationDate: Installed on 2018-03-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 42983RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70a7bb64-bb83-4ab9-98a4-d3545d1e66ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET73WW (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42983RU
  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:bvr8DET73WW(1.43):bd10/12/2016:svnLENOVO:pn42983RU:pvrThinkPadX220Tablet:rvnLENOVO:rn42983RU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220 Tablet
  dmi.product.name: 42983RU
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demroz 1814 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=09061c6d-7452-46e9-8539-5c6c5078ef2a
  InstallationDate: Installed on 2018-03-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 42983RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70a7bb64-bb83-4ab9-98a4-d3545d1e66ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET73WW (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42983RU
  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:bvr8DET73WW(1.43):bd10/12/2016:svnLENOVO:pn42983RU:pvrThinkPadX220Tablet:rvnLENOVO:rn42983RU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220 Tablet
  dmi.product.name: 42983RU
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1740828] Re: USB devices are detected but not working

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

Title:
  USB devices are detected but not working

Status in linux package in Ubuntu:
  Expired

Bug description:
  USB mouse, keyboard and memory sticks are detected, but not working
  with kernel 4.10.0-37-generic. They how up in lsusb, but moving the
  mouse or typing does not result in any reaction on my laptop. No
  /dev/sdx devices is created for the memory stick. Internal touch pad
  and keyboard of the laptop are working.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  pia2806 F pulseaudio
   /dev/snd/controlC1:  pia2806 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jan  2 09:40:23 2018
  InstallationDate: Installed on 2015-11-05 (788 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Notebook W230SS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=2329e937-a4e4-4efc-a999-c0fa7d44c92b ro uveau.modeset=0 
acpi_enforce_resources=lax nosplash uveau.modeset=0 acpi_enforce_resources=lax 
acpi_enforce_resources=lax
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-10-16 (78 days ago)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1730188] Re: linux-image-4.4.0-98 kernel panic

[Launchpad Bug Tracker]

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

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

Title:
  linux-image-4.4.0-98 kernel panic

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

Bug description:
  Since updating to linux-image-4.4.0-98-generic 2 days ago, I get a kernel 
panic during boot. With 4.4.0-97 the machine boots fine. Screenshot attached.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jos1929 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5577332d-7a0a-4c5a-9c10-93a5cd6f5e65
  InstallationDate: Installed on 2013-01-05 (1764 days ago)
  InstallationMedia: This
  Lsusb:
   Bus 002 Device 003: ID 04f2:b34c Chicony Electronics Co., Ltd 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: wortmann TERRA MOBILE 1512/1712
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=b9e9b26b-d84a-494e-921d-31e5e92726eb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.13
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (454 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/22/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: TERRA MOBILE 1512/1712
  dmi.board.vendor: Wortmann AG
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Wortmann AG
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/22/2012:svnwortmann:pnTERRAMOBILE1512/1712:pvrNotApplicable:rvnWortmannAG:rnTERRAMOBILE1512/1712:rvrV3.0:cvnWortmannAG:ct10:cvrN/A:
  dmi.product.name: TERRA MOBILE 1512/1712
  dmi.product.version: Not Applicable
  dmi.sys.vendor: wortmann

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

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

[Kernel-packages] [Bug 1730188] Re: linux-image-4.4.0-98 kernel panic

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

Title:
  linux-image-4.4.0-98 kernel panic

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

Bug description:
  Since updating to linux-image-4.4.0-98-generic 2 days ago, I get a kernel 
panic during boot. With 4.4.0-97 the machine boots fine. Screenshot attached.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jos1929 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5577332d-7a0a-4c5a-9c10-93a5cd6f5e65
  InstallationDate: Installed on 2013-01-05 (1764 days ago)
  InstallationMedia: This
  Lsusb:
   Bus 002 Device 003: ID 04f2:b34c Chicony Electronics Co., Ltd 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: wortmann TERRA MOBILE 1512/1712
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=b9e9b26b-d84a-494e-921d-31e5e92726eb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.13
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (454 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/22/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: TERRA MOBILE 1512/1712
  dmi.board.vendor: Wortmann AG
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Wortmann AG
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/22/2012:svnwortmann:pnTERRAMOBILE1512/1712:pvrNotApplicable:rvnWortmannAG:rnTERRAMOBILE1512/1712:rvrV3.0:cvnWortmannAG:ct10:cvrN/A:
  dmi.product.name: TERRA MOBILE 1512/1712
  dmi.product.version: Not Applicable
  dmi.sys.vendor: wortmann

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

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

[Kernel-packages] [Bug 1740923] Re: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

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

Title:
  package linux-image-4.13.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  standard system update after first install of lubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  red 862 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with Cx20468-31 at irq 10'
 Mixer name : 'Conexant Cx20468-31'
 Components : 'AC97a:43585430'
 Controls  : 24
 Simple ctrls  : 16
  Date: Tue Jan  2 20:09:24 2018
  DuplicateSignature:
   package:linux-image-4.13.0-21-generic:(not installed)
   Preparing to unpack 
.../71-linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UematV/71-linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=c3bdf7d5-b131-4b28-8b11-ad45372208c2
  InstallationDate: Installed on 2018-01-02 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   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: Acer TravelMate 4000
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=c553c403-6d68-4bee-af31-1b6dc83b7391 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.13.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2004
  dmi.bios.vendor: ACER
  dmi.bios.version: 3A10
  dmi.board.name: TravelMate 4000
  dmi.board.vendor: Acer
  dmi.board.version: Rev 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnACER:bvr3A10:bd10/12/2004:svnAcer:pnTravelMate4000:pvrRev1:rvnAcer:rnTravelMate4000:rvrRev1.0:cvnAcer:ct10:cvrRev.1:
  dmi.product.name: TravelMate 4000
  dmi.product.version: Rev 1
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1741084] Re: rtsx_pci needs to be manually loaded for Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229]

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

Title:
  rtsx_pci needs to be manually loaded for Realtek Semiconductor Co.,
  Ltd. RTS5229 PCI Express Card Reader [10ec:5229]

Status in linux package in Ubuntu:
  Expired

Bug description:
  A friend's card reader in his ThinkPad L430 [10ec:5229] was not
  automatically recognized in 4.10.0-40-generic (amd64) on 16.04. He had
  to manually load the rtsx_pci module.

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

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

[Kernel-packages] [Bug 1741103] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]

Status in linux package in Ubuntu:
  Expired

Bug description:
  starting system

  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: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1027 F pulseaudio
piero  1387 F pulseaudio
  Date: Wed Jan  3 19:19:44 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=83c593ac-9ab2-404e-b14f-1e0c3064bd8a
  InstallationDate: Installed on 2018-01-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.
   
   enp0s15   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=f0dd0298-1769-46a0-9988-d4d0e94a27e1 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N-MX ACPI BIOS Revision 0903
  dmi.board.name: P5N-MX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-MXACPIBIOSRevision0903:bd07/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-MX:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1741042] Re: ubuntu 17.00 kernel freeze

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

Title:
  ubuntu 17.00 kernel freeze

Status in linux package in Ubuntu:
  Expired

Bug description:
  My laptop hangs frequently, with a high cpu comsumption, don't react to 
Ctrl-Alt-whatever, only way to restart is hardware or fn-alt-print screen-B
  any other fn-alt-print screen combination doesn't works.
  I don't know how to trace what's wrong, or what component can be responsible.
  I have tried several X-servers, I have tried to disable hardware nvidia 
acceleration, etc. with no success

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-22-generic 4.13.0-22.25
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rogelio2095 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Jan  3 13:37:36 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1
  InstallationDate: Installed on 2017-05-04 (244 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-22-generic N/A
   linux-backports-modules-4.13.0-22-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  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.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  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/1741042/+subscriptions

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

[Kernel-packages] [Bug 1740906] Re: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

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

Title:
  package linux-image-4.13.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  Fresh install Lubuntu 17.10 desktop i386.  Dell Latitude D600.
  Defaults on install except having to "forcepae" on boot.  "apt --fix-
  broken install" gives the following errors -

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
linux-image-4.13.0-21-generic
  Suggested packages:
fdutils linux-doc-4.13.0 | linux-source-4.13.0 linux-tools
  The following NEW packages will be installed:
linux-image-4.13.0-21-generic
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  88 not fully installed or removed.
  Need to get 19.3 MB of archives.
  After this operation, 50.7 MB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://us.archive.ubuntu.com/ubuntu artful-updates/main i386 
linux-image-4.13.0-21-generic i386 4.13.0-21.24 [19.3 MB]
  Fetched 19.3 MB in 4s (4,423 kB/s)
  (Reading database ... 146408 files and directories currently installed.)
  Preparing to unpack .../linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb 
...
  This kernel does not support a non-PAE CPU.
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb 
(--unpack):
   subprocess new pre-installation script returned error exit status 1
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.13.0-21-generic 
/boot/vmlinuz-4.13.0-21-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.13.0-21-generic 
/boot/vmlinuz-4.13.0-21-generic
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tcs1104 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 5'
 Mixer name : 'SigmaTel STAC9750,51'
 Components : 'AC97a:83847650'
 Controls  : 39
 Simple ctrls  : 24
  Date: Tue Jan  2 09:18:38 2018
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=40d082d2-6dec-4a8f-b207-0f43ebe8a43e
  InstallationDate: Installed on 2018-01-02 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   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: Dell Computer Corporation Latitude D600
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=9a6ff044-01b0-4d97-8198-9c3a200e9f5a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /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: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.13.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2003
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A05
  dmi.board.name: 03U652
  dmi.board.vendor: Dell Computer Corporation
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Computer 

[Kernel-packages] [Bug 1753347] Re: [SRU] Lenovo E41 Mic mute hotkey is not responding

[AaronMa]

** Tags added: originate-from-1734236 sutton

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

Title:
  [SRU] Lenovo E41 Mic mute hotkey is not responding

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  New

Bug description:
  [Impact]
  Mic mute hotkey (F1) is not working due to the delay answer when reading EC 
VPC. 
  The ideapad_laptop module didn't wait enough time to read VPC.

  [Fix]
  Add more time to wait for reading EC VPC, the correct data will be got.
  Hotkey works well then.

  [Test Case]
  Tested on Lenovo E41, hotkey works well with this patch.

  [Regression Potential]
  No regression is expected.

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

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

[Kernel-packages] [Bug 1753346] Re: AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

[Kai-Heng Feng]

I guess it's the same one as [1]?

Does the system freeze when you are using it? Or does it freeze when
it's idle?

[1] https://bugzilla.kernel.org/show_bug.cgi?id=196683

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

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

Title:
  AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is happening every day or so.  I cannot see anything in the
  kern.log or syslog that give me a clue on where/what the issue might.
  I was using Ubuntu 17.10 earlier and upgraded to Ubuntu 18.04 on
  3/3/2018, since I thought kernel 4.15 might have better support for
  the ryzen 7 and also maybe amdgpu for the radeon 580 might be newer.
  I have removed most external devices except for networking and HDMI
  and audio out.

  Attached a tarball of info, although I believe that since I used
  'ubuntu-bug linux' command, the information might be duplicated,
  apologize for any extra attachments.

  $ ls -l dell-5675-sysinfo/
  total 168
  -rw-r--r-- 1 pss pss 83139 Mar  4 19:47 dmesg
  -rw-r--r-- 1 pss pss 26154 Mar  4 19:44 dmidecode
  -rw-r--r-- 1 pss pss  1507 Mar  4 19:45 gpu-manager.log
  -rw-r--r-- 1 pss pss   110 Mar  4 19:44 lsb-release-a
  -rw-r--r-- 1 pss pss  1464 Mar  4 19:44 lscpu
  -rw-r--r-- 1 pss pss  4353 Mar  4 19:46 lspci
  -rw-r--r-- 1 pss pss  4105 Mar  4 20:05 lspci-vvv-radeon-580.txt
  -rw-r--r-- 1 pss pss 19318 Mar  4 19:48 
mprime-p95v294b8.linux64-results-2018-03-04.txt
  -rw-r--r-- 1 pss pss   104 Mar  4 19:44 uname-a
  -rw-r--r-- 1 pss pss35 Mar  4 20:27 version.log

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss1801 F pulseaudio
   /dev/snd/controlC0:  pss1801 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 20:21:55 2018
  InstallationDate: Installed on 2018-02-16 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (1 days ago)
  dmi.bios.date: 12/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.name: 07PR60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.6
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd12/04/2017:svnDellInc.:pnInspiron5675:pvr1.3.6:rvnDellInc.:rn07PR60:rvrA00:cvnDellInc.:ct3:cvr1.3.6:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.version: 1.3.6
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Jamie Strandboge]

This is fixed in xenial 2.3.1-2.1ubuntu2~16.04.1

** Changed in: libseccomp (Ubuntu Xenial)
   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/1567597

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

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

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [libseccomp Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:

  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument

  [Linux Kernel Test Case]

  All of the libseccomp test cases apply here.

  

  Running the seccomp kernel selftests is also a great to exercise
  seccomp and the kernel patch set proposed for the SRU includes
  additional seccomp selftests. To build, enter into the root of the
  kernel source tree and build the seccomp test binary:

  $ make -C tools/testing/selftests TARGETS=seccomp

  Now you can execute tools/testing/selftests/seccomp/seccomp_bpf 

[Kernel-packages] [Bug 1753347] Re: [SRU] Lenovo E41 Mic mute hotkey is not responding

[AaronMa]

** Changed in: hwe-next
 Assignee: (unassigned) => AaronMa (mapengyu)

** Changed in: hwe-next
   Importance: Undecided => Critical

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

Title:
  [SRU] Lenovo E41 Mic mute hotkey is not responding

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  New

Bug description:
  [Impact]
  Mic mute hotkey (F1) is not working due to the delay answer when reading EC 
VPC. 
  The ideapad_laptop module didn't wait enough time to read VPC.

  [Fix]
  Add more time to wait for reading EC VPC, the correct data will be got.
  Hotkey works well then.

  [Test Case]
  Tested on Lenovo E41, hotkey works well with this patch.

  [Regression Potential]
  No regression is expected.

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

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

[Kernel-packages] [Bug 1753298] Re: audio not working, apollo lake 4.16 kernel

[Daniel van Vugt]

It appears you don't have audio because pulseaudio has crashed(?):

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.

Can you please test a newer version by booting this?;

  http://cdimages.ubuntu.com/daily-live/current/

Please also apply the workaround for bug 994921, and if you find any
crash files in /var/crash then report them by running this command:

  ubuntu-bug /var/crash/YOURFILE.crash

And tell us the new bug ID that gets created.

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

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

Title:
  audio not working, apollo lake 4.16 kernel

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I tried a lot of 4.16 ubuntu kenerls and audio is not working.

  Jumper EZ book v4, Ubuntu 16.04.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  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.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.16.0-994-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/1753298/+subscriptions

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

[Kernel-packages] [Bug 1748565] Re: Bluetooth: hci0: last event is not cmd complete (0x0f)

[Daniel van Vugt]

Still incomplete awaiting an answer to comment #5.

I suspect this log message is getting confused for bluetooth audio
skipping, but I think those might be separate issues.

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

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

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1811 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 20:35:29 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1748565] Re: Bluetooth: hci0: last event is not cmd complete (0x0f)

[Daniel van Vugt]

Confirmed this bug occurs with other bluetooth dongles too.

** Summary changed:

- [Intel 6235] Bluetooth: hci0: last event is not cmd complete (0x0f)
+ Bluetooth: hci0: last event is not cmd complete (0x0f)

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

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

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1811 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 20:35:29 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

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

Title:
  ^@ characters appearing on login terminal on 17.10 and 16.04 HWE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing either 17.10 or 16.04 HWE to a minimal/command line
  environment, the login terminal displays a repeating string of ^@
  characters at a rate of approximately one per second. These are
  treated as actual input and prevent login as I am unable to type a
  username or password uninterrupted. Without an SSH server, the machine
  would be unusable. This does not happen under 16.04 using the standard
  non-HWE kernel.

  Hardware is a General Dynamics GD8200 laptop. BIOS has been reset and
  updated to latest version.

  lspci:
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (rev 05)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family 6 port SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  01:00.0 CardBus bridge: Ricoh Co Ltd CardBus bridge (rev 02)
  03:00.0 Ethernet controller: LSI Corporation ET-131x PCI-E Ethernet 
Controller (rev 03)
  04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host 
Controller
  05:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  lsusb:
  Bus 002 Device 005: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
  Bus 002 Device 004: ID 8087:07dc Intel Corp. 
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 005: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader  
  Bus 001 Device 004: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

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

[Kernel-packages] [Bug 1753614] [NEW] ^@ characters appearing on login terminal on 17.10 and 16.04 HWE

[radarexile]

Public bug reported:

After installing either 17.10 or 16.04 HWE to a minimal/command line
environment, the login terminal displays a repeating string of ^@
characters at a rate of approximately one per second. These are treated
as actual input and prevent login as I am unable to type a username or
password uninterrupted. Without an SSH server, the machine would be
unusable. This does not happen under 16.04 using the standard non-HWE
kernel.

Hardware is a General Dynamics GD8200 laptop. BIOS has been reset and
updated to latest version.

lspci:
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (rev 05)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC 
Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 
6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
01:00.0 CardBus bridge: Ricoh Co Ltd CardBus bridge (rev 02)
03:00.0 Ethernet controller: LSI Corporation ET-131x PCI-E Ethernet Controller 
(rev 03)
04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host 
Controller
05:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

lsusb:
Bus 002 Device 005: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
Bus 002 Device 004: ID 8087:07dc Intel Corp. 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader  
Bus 001 Device 004: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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


** Tags: xenial

** Attachment added: "Photograph of login screen behavior."
   
https://bugs.launchpad.net/bugs/1753614/+attachment/5070317/+files/atsymbol.jpg

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

Title:
  ^@ characters appearing on login terminal on 17.10 and 16.04 HWE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing either 17.10 or 16.04 HWE to a minimal/command line
  environment, the login terminal displays a repeating string of ^@
  characters at a rate of approximately one per second. These are
  treated as actual input and prevent login as I am unable to type a
  username or password uninterrupted. Without an SSH server, the machine
  would be unusable. This does not happen under 16.04 using the standard
  non-HWE kernel.

  Hardware is a General Dynamics GD8200 laptop. BIOS has been reset and
  updated to latest version.

  lspci:
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (rev 05)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI 

[Kernel-packages] [Bug 1750245] Re: i915 kbl_guc_ver9_14.bin does not load

[Andrew Crouthamel]

This is 17.10 with linux-firmware 1.169.3. It does seem odd, is there
something else the install script from 01.org does that maybe fixes it?

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

Title:
  i915 kbl_guc_ver9_14.bin does not load

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  The provided i915/kbl_guc_ver9_14.bin does not load when configured to
  do so . If the file is replaced by manually installing with the
  included script from 01.org, it loads properly:
  https://01.org/linuxgraphics/downloads/kabylake-guc-9.14

  Before:
  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  After:
  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 9.14
  version found: 9.14
  header: offset is 0; size = 128
  uCode: offset is 128; size = 142272
  RSA: offset is 142400; size = 256

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

[gumbeto]

Bryce Schober (bryce-schober): I had a very similar issue, but on 16.04
and wanting gcc-7. Adding the the toolchain ppa made gcc-5 subject to
upgrading, triggering this issue. I managed to deal with it with package
pinning and aptitude (see comment 58).

Here are a few more details if in case you want to try this yourself (I
recommend using Timeshift or similar in case you want to go back).

$ cat /etc/apt/preferences.d/toolchain.pref
Package: *
Pin: release o=LP-PPA-ubuntu-toolchain-r-test
Pin-Priority: 60

Here are some quick instructions on how to use aptitude:
https://makandracards.com/makandra/47558-how-to-install-packages-from-
newer-ubuntu-releases#planning-the-upgrade

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

[Alejandro Mery]

Hi Joseph, I removed 4.15.0.11.12 and installed yours.

Linux de2 4.15.0-10-generic #11~lp1752350 SMP Mon Mar 5 08:26:15 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

when booting without Xen it works fine, but if I attempt to boot it as
dom0 is "hangs" ... not sure if it's worse or better than the automatic
reboot I had before. Unfortunately I can't get any useful output as it's
on a machine on a datacenter attached to a kvm. I see Xen's output until
it initialised the vCPUs and then it goes blank. I don't know how to get
useful output to post here in this case

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

Title:
  Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

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

Bug description:
  The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when
  booted as a dom0 under Xen.

  A similar bug was reported by someone else for archlinux
  (https://bugs.archlinux.org/task/57500).

  A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it
  fixes the problem for me.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7).

  Xen output:

  (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) 
(gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n  Fri Oct 13 15:58:41 UTC 2017
  (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9
  (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga
  (XEN) Xen image load base address: 0
  (XEN) Video information:
  (XEN)  VGA is text mode 80x25, font 8x16
  (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
  (XEN)  EDID info not retrieved because no DDC retrieval method detected
  (XEN) Disc information:
  (XEN)  Found 1 MBR signatures
  (XEN)  Found 1 EDD information structures
  (XEN) Xen-e820 RAM map:
  (XEN)   - 0009ec00 (usable)
  (XEN)  000f - 0010 (reserved)
  (XEN)  0010 - cb6cfc00 (usable)
  (XEN)  cb6cfc00 - cb723c00 (ACPI NVS)
  (XEN)  cb723c00 - cb725c00 (ACPI data)
  (XEN)  cb725c00 - cc00 (reserved)
  (XEN)  f800 - fc00 (reserved)
  (XEN)  fec0 - fed00400 (reserved)
  (XEN)  fed2 - feda (reserved)
  (XEN)  fee0 - fef0 (reserved)
  (XEN)  ffb0 - 0001 (reserved)
  (XEN)  0001 - 00013000 (usable)
  (XEN) New Xen image base address: 0xcb00
  (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
  (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K  15 ASL61)
  (XEN) ACPI: DSDT FFDC89E4, 47BC (r1   DELLdt_ex 1000 INTL 20050624)
  (XEN) ACPI: FACS CB6CFC00, 0040
  (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1   DELLst_ex 1000 INTL 20050624)
  (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K  15 ASL61)
  (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K  15 ASL61)
  (XEN) System RAM: 4022MB (4118964kB)
  (XEN) Domain heap initialised
  (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23
  (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
  (XEN) Using scheduler: SMP Credit Scheduler (credit)
  (XEN) Platform timer is 14.318MHz HPET
  (XEN) Detected 2926.007 MHz processor.
  (XEN) Initing memory sharing.
  (XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
  (XEN) Intel VT-d Snoop Control enabled.
  (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
  (XEN) Intel VT-d Queued Invalidation enabled.
  (XEN) Intel VT-d Interrupt Remapping not enabled.
  (XEN) Intel VT-d Posted Interrupt not enabled.
  (XEN) Intel VT-d Shared EPT tables not enabled.
  (XEN) :04:00.0: unknown type 4
  (XEN) I/O virtualisation enabled
  (XEN)  - Dom0 mode: Relaxed
  (XEN) Interrupt remapping disabled
  (XEN) ENABLING IO-APIC IRQs
  (XEN)  -> Using new ACK method
  (XEN) Allocated console ring of 16 KiB.
  (XEN) VMX: Supported advanced features:
  (XEN)  - APIC MMIO access virtualisation
  (XEN)  - APIC TPR shadow
  (XEN)  - Extended Page Tables (EPT)
  (XEN)  - Virtual-Processor Identifiers (VPID)
  (XEN)  - Virtual NMI
  (XEN)  - MSR direct-access bitmap
  (XEN) HVM: ASIDs enabled.
  (XEN) HVM: VMX enabled
  (XEN) HVM: Hardware Assisted Paging (HAP) detected
  (XEN) HVM: HAP page sizes: 

[Kernel-packages] [Bug 1752163] Re: computer freeze

[ProZac]

So tested new kernel, when it comes to what I installed, I did all the installs 
in the same day, so not sure what might cause the bug.
New kernel installed, 14.16-rc3, same issue but took a bit longer before the 
server froze this time.
Same issue doh.

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

Title:
  computer freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Computer randomly freeze, not possible to do anything than reboot the system.
  Did alot of installs on the same day, not sure what is the cause.
  Running script to not have gpu installed, should not be a problem? am4 cpu 
with no apu.
  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prozac 2113 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 21:22:31 2018
  InstallationDate: Installed on 2018-02-16 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   lono wireless extensions.
   
   enp38s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=779380b7-d22a-4038-a9a4-cdf71b00b881 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0612
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0612:bd05/15/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

[Alejandro Mery]

@jsalisbury, I already have 4.15.0.11.12 installed... can you update
your test kernel please?

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

Title:
  Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

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

Bug description:
  The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when
  booted as a dom0 under Xen.

  A similar bug was reported by someone else for archlinux
  (https://bugs.archlinux.org/task/57500).

  A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it
  fixes the problem for me.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7).

  Xen output:

  (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) 
(gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n  Fri Oct 13 15:58:41 UTC 2017
  (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9
  (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga
  (XEN) Xen image load base address: 0
  (XEN) Video information:
  (XEN)  VGA is text mode 80x25, font 8x16
  (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
  (XEN)  EDID info not retrieved because no DDC retrieval method detected
  (XEN) Disc information:
  (XEN)  Found 1 MBR signatures
  (XEN)  Found 1 EDD information structures
  (XEN) Xen-e820 RAM map:
  (XEN)   - 0009ec00 (usable)
  (XEN)  000f - 0010 (reserved)
  (XEN)  0010 - cb6cfc00 (usable)
  (XEN)  cb6cfc00 - cb723c00 (ACPI NVS)
  (XEN)  cb723c00 - cb725c00 (ACPI data)
  (XEN)  cb725c00 - cc00 (reserved)
  (XEN)  f800 - fc00 (reserved)
  (XEN)  fec0 - fed00400 (reserved)
  (XEN)  fed2 - feda (reserved)
  (XEN)  fee0 - fef0 (reserved)
  (XEN)  ffb0 - 0001 (reserved)
  (XEN)  0001 - 00013000 (usable)
  (XEN) New Xen image base address: 0xcb00
  (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
  (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K  15 ASL61)
  (XEN) ACPI: DSDT FFDC89E4, 47BC (r1   DELLdt_ex 1000 INTL 20050624)
  (XEN) ACPI: FACS CB6CFC00, 0040
  (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1   DELLst_ex 1000 INTL 20050624)
  (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K  15 ASL61)
  (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K  15 ASL61)
  (XEN) System RAM: 4022MB (4118964kB)
  (XEN) Domain heap initialised
  (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23
  (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
  (XEN) Using scheduler: SMP Credit Scheduler (credit)
  (XEN) Platform timer is 14.318MHz HPET
  (XEN) Detected 2926.007 MHz processor.
  (XEN) Initing memory sharing.
  (XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
  (XEN) Intel VT-d Snoop Control enabled.
  (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
  (XEN) Intel VT-d Queued Invalidation enabled.
  (XEN) Intel VT-d Interrupt Remapping not enabled.
  (XEN) Intel VT-d Posted Interrupt not enabled.
  (XEN) Intel VT-d Shared EPT tables not enabled.
  (XEN) :04:00.0: unknown type 4
  (XEN) I/O virtualisation enabled
  (XEN)  - Dom0 mode: Relaxed
  (XEN) Interrupt remapping disabled
  (XEN) ENABLING IO-APIC IRQs
  (XEN)  -> Using new ACK method
  (XEN) Allocated console ring of 16 KiB.
  (XEN) VMX: Supported advanced features:
  (XEN)  - APIC MMIO access virtualisation
  (XEN)  - APIC TPR shadow
  (XEN)  - Extended Page Tables (EPT)
  (XEN)  - Virtual-Processor Identifiers (VPID)
  (XEN)  - Virtual NMI
  (XEN)  - MSR direct-access bitmap
  (XEN) HVM: ASIDs enabled.
  (XEN) HVM: VMX enabled
  (XEN) HVM: Hardware Assisted Paging (HAP) detected
  (XEN) HVM: HAP page sizes: 4kB, 2MB
  (XEN) Brought up 4 CPUs
  (XEN) Dom0 has maximum 600 PIRQs
  (XEN) *** LOADING DOMAIN 0 ***
  (XEN)  Xen  kernel: 64-bit, lsb, compat32
  (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000
  (XEN) PHYSICAL MEMORY ARRANGEMENT:
  (XEN)  Dom0 alloc.:   00012000->00012400 (952940 pages to be 
allocated)
  (XEN)  Init. ramdisk: 00012d251000->00012575
  (XEN) VIRTUAL MEMORY ARRANGEMENT:
  (XEN)  Loaded kernel: 

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

[Colin Ian King]

FYI, I've uploaded the same fix to Artful for the SRU

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

Title:
  zfs-import-cache.service fails on startup

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

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

[Bryce Schober]

On Ubuntu 14.04, I've installed the ubuntu-toolchain-r/test ppa in order
to get a gcc-5 compiler, and the assumedly-conflicting
4.8.5-2ubuntu1~14.04.1 came from that PPA along for the ride.

Is there a better PPA option for installing gcc-5 on Ubuntu 14.04?

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1326761] Re: Tevii S471 DVB-S2 card hangs on firmware upload

[Gavin Whitehead]

I'm sseing this issue with a HDStar DVB-S2 USB tuner (uses the same
SU3000 board) on xubuntu 16.04.4.

uname -r
4.4.0-116-generic

>From kern.log
Mar  4 14:22:38 mc04 kernel: [5.876001] dw2102: su3000_identify_state
Mar  4 14:22:38 mc04 kernel: [5.876001]
Mar  4 14:22:38 mc04 kernel: [5.876002] dvb-usb: found a 'SU3000HD DVB-S 
USB2.0' in warm state.
Mar  4 14:22:38 mc04 kernel: [5.876006] dw2102: su3000_power_ctrl: 1, 
initialized 0
Mar  4 14:22:38 mc04 kernel: [5.876006]
Mar  4 14:22:38 mc04 kernel: [5.876825] dvb-usb: will pass the complete 
MPEG2 transport stream to the software demuxer.
Mar  4 14:22:38 mc04 kernel: [5.877514] DVB: registering new adapter 
(SU3000HD DVB-S USB2.0)
Mar  4 14:22:38 mc04 kernel: [5.885052] dvb-usb: MAC address: 
00:af:78:66:69:eb
Mar  4 14:22:38 mc04 kernel: [6.249349] DS3000 chip version: 0.208 attached.
Mar  4 14:22:38 mc04 kernel: [6.368671] ts2020 3-0060: Montage Technology 
TS2022 successfully identified
Mar  4 14:22:38 mc04 kernel: [6.368683] dw2102: Attached DS3000/TS2020!
Mar  4 14:22:38 mc04 kernel: [6.368683]
Mar  4 14:22:38 mc04 kernel: [6.368688] usb 1-1: DVB: registering adapter 0 
frontend 0 (Montage Technology DS3000)...
Mar  4 14:22:38 mc04 kernel: [6.403655] Registered IR keymap rc-su3000
Mar  4 14:22:38 mc04 kernel: [6.403750] input: IR-receiver inside an USB 
DVB receiver as /devices/pci:00/:00:12.2/usb1/1-1/rc/rc1/input16
Mar  4 14:22:38 mc04 kernel: [6.403800] rc1: IR-receiver inside an USB DVB 
receiver as /devices/pci:00/:00:12.2/usb1/1-1/rc/rc1
Mar  4 14:22:38 mc04 kernel: [6.403801] dvb-usb: schedule remote query 
interval to 150 msecs.
Mar  4 14:22:38 mc04 kernel: [6.403803] dw2102: su3000_power_ctrl: 0, 
initialized 1
Mar  4 14:22:38 mc04 kernel: [6.403803]
Mar  4 14:22:38 mc04 kernel: [6.403804] dvb-usb: SU3000HD DVB-S USB2.0 
successfully initialized and connected.
Mar  4 14:22:38 mc04 kernel: [6.403828] usbcore: registered new interface 
driver dw2102

Mar  4 14:22:56 mc04 kernel: [   24.991048] dw2102: su3000_power_ctrl: 1, 
initialized 1
Mar  4 14:22:56 mc04 kernel: [   24.991048]
Mar  4 14:22:56 mc04 kernel: [   24.999193] ds3000_firmware_ondemand: Waiting 
for firmware upload (dvb-fe-ds3000.fw)...
Mar  4 14:22:56 mc04 kernel: [   25.001577] ds3000_firmware_ondemand: Waiting 
for firmware upload(2)...
Mar  4 14:22:57 mc04 kernel: [   26.087688] dw2102: su3000_power_ctrl: 0, 
initialized 1
Mar  4 14:22:57 mc04 kernel: [   26.087688]
Mar  4 14:22:57 mc04 kernel: [   26.122504] dw2102: su3000_power_ctrl: 1, 
initialized 1
Mar  4 14:22:57 mc04 kernel: [   26.122504]
Mar  4 14:22:57 mc04 kernel: [   26.135208] ds3000_firmware_ondemand: Waiting 
for firmware upload (dvb-fe-ds3000.fw)...
Mar  4 14:22:57 mc04 kernel: [   26.135252] ds3000_firmware_ondemand: Waiting 
for firmware upload(2)...
Mar  4 14:23:00 mc04 kernel: [   28.796978] dw2102: su3000_power_ctrl: 0, 
initialized 1
Mar  4 14:23:00 mc04 kernel: [   28.796978]

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

Title:
  Tevii S471 DVB-S2 card hangs on firmware upload

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have fresh installed Ubuntu Trusty Tahr (Server) with kernel 3.13.0-29.
  Firmware file dvb-fe-ds3000.fw is putted into /lib/firmware
  On a system cold start I see in syslog:

  Jun  5 16:00:54 MMC kernel: [9.601460] cx23885 driver version 0.0.3 loaded
  Jun  5 16:00:54 MMC kernel: [9.601881] CORE cx23885[0]: subsystem: 
d471:9022, board: TeVii S471 [card=35,autodetected]
  Jun  5 16:00:54 MMC kernel: [9.750010] cx23885_dvb_register() allocating 
1 frontend(s)
  Jun  5 16:00:54 MMC kernel: [9.758499] cx23885[0]: cx23885 based dvb card
  Jun  5 16:00:54 MMC kernel: [9.879035] DVB: registering new adapter 
(cx23885[0])
  Jun  5 16:00:54 MMC kernel: [9.879047] cx23885 :01:00.0: DVB: 
registering adapter 0 frontend 0 (Montage Technology DS3000)...
  Jun  5 16:00:54 MMC kernel: [9.894578] cx23885_dev_checkrevision() 
Hardware revision = 0xa5
  Jun  5 16:00:54 MMC kernel: [9.894595] cx23885[0]/0: found at 
:01:00.0, rev: 4, irq: 16, latency: 0, mmio: 0xfe80

  
  But if I try to scan channels by scan or tvheadend I see this repeated lines:

  Jun  5 16:01:04 MMC kernel: [   20.051633] ds3000_firmware_ondemand: Waiting 
for firmware upload (dvb-fe-ds3000.fw)...
  Jun  5 16:01:04 MMC kernel: [   20.052608] ds3000_firmware_ondemand: Waiting 
for firmware upload(2)...

  Card works under Debian linux kernel image from unstable repo (linux-
  image-3.14.1)

  manjur@MMC:~$ lsb_release -rd
  Description:Ubuntu 14.04 LTS
  Release:14.04
  manjur@MMC:~$ apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.29.35
Candidate:   3.13.0.29.35
Version table:
   *** 

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

[Per Allansson]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1753583/+attachment/5070244/+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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1753583] ProcCpuinfo.txt

[Per Allansson]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1753583/+attachment/5070245/+files/ProcCpuinfo.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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

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

[Per Allansson]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1753583/+attachment/5070250/+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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

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

[Per Allansson]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1753583/+attachment/5070247/+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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

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

[Per Allansson]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1753583/+attachment/5070248/+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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

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

[Per Allansson]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1753583/+attachment/5070242/+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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

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

[Per Allansson]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1753583/+attachment/5070243/+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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

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

[Per Allansson]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1753583/+attachment/5070249/+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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

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

[Per Allansson]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1753583/+attachment/5070251/+files/WifiSyslog.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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

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

[Per Allansson]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1753583/+attachment/5070246/+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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1753583] Re: Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

[Per Allansson]

apport information

** Tags added: apport-collected xenial

** Description changed:

  I experience random lockups when disabling CPUs, with symptoms very much
  as described here:
  
  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662
  
- and when double-checking the source code for 4.13.0-36.40~16.04.1 I can
- see that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is
- indeed missing.
+ and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
+  crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: [Errno 2] No such file or directory
+ MachineType: FUJITSU PRIMERGY RX2530 M4
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
+ ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
+ RelatedPackageVersions:
+  linux-restricted-modules-4.13.0-36-generic N/A
+  linux-backports-modules-4.13.0-36-generic  N/A
+  linux-firmware 1.157.17
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial
+ Uname: Linux 4.13.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 10/05/2017
+ dmi.bios.vendor: FUJITSU // American Megatrends Inc.
+ dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
+ dmi.board.name: D3383-A1
+ dmi.board.vendor: FUJITSU
+ dmi.board.version: S26361-D3383-A12 WGS03 GS04
+ dmi.chassis.asset.tag: System Asset Tag
+ dmi.chassis.type: 23
+ dmi.chassis.vendor: FUJITSU
+ dmi.chassis.version: RX2530M4R1
+ dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
+ dmi.product.family: SERVER
+ dmi.product.name: PRIMERGY RX2530 M4
+ dmi.product.version: GS01
+ dmi.sys.vendor: FUJITSU

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1753583/+attachment/5070241/+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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  

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

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I
  can see that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702
  is indeed missing.

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

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

[Kernel-packages] [Bug 1753583] Re: Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

[Per Allansson]

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

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I
  can see that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702
  is indeed missing.

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

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

[Kernel-packages] [Bug 1753583] [NEW] Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

[Per Allansson]

Public bug reported:

I experience random lockups when disabling CPUs, with symptoms very much
as described here:

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

and when double-checking the source code for 4.13.0-36.40~16.04.1 I can
see that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is
indeed missing.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1753583

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I
  can see that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702
  is indeed missing.

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

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

[Kernel-packages] [Bug 1752748] Re: nouveau module can't be loaded

[Lucas Clemente Vella]

The issue happened after upgrading from Ubuntu 7.10 to development
version Bioninc Beaver. On Ubuntu 7.10 the module works as expected with
distribution default kernel Linux 4.13.

I've updated to kernel v4.16-rc4 an the problem persists.

** Tags added: kernel-bug-exists-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/1752748

Title:
  nouveau module can't be loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Module nouveou can't be loaded. I get the following error message when
  I try to load it manually:

  # modprobe nouveau
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-lowlatency 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lvella 1453 F pulseaudio
   /dev/snd/controlC0:  lvella 1453 F pulseaudio
   /dev/snd/controlC1:  lvella 1453 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Mar  1 20:37:06 2018
  HibernationDevice: RESUME=UUID=3f064780-2aeb-44b4-a8a3-21e590bd1b8f
  InstallationDate: Installed on 2016-06-02 (637 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-lowlatency.efi.signed 
root=UUID=f127c524-7b47-4ff1-b1d6-620ed6f14a29 ro noprompt persistent quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-lowlatency N/A
   linux-backports-modules-4.15.0-10-lowlatency  N/A
   linux-firmware1.171
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-02-28 (1 days ago)
  dmi.bios.date: 04/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3701:bd04/20/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe

[Per Allansson]

I have similar issues on 16.04.4 with latest HWE kernel - and when
double-checking against the source code I can see that this fix is now
AWOL from:

linux-image-4.13.0-36-generic   4.13.0-36.40~16.04.1

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

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

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

Bug description:
  == SRU Justification ==
  The following mainline commit introduced a regression in v4.14-rc1:
  24247aeeabe9 ("x86/intel_rdt/cqm: Improve limbo list processing")

  This commit made it's way into Artful via Launchpad bug 1591609 as Artful 
commit
  ac2fc5adab0f4b.

  This bug was causing regression tests to hang about one in four
  times when running cpu_offlining tests.

  This patch to fix this regression was just submitted to mainline, so it is 
also
  needed in Bionic.

  == Fix ==
  commit d47924417319e3b6a728c0b690f183e75bc2a702
  Author: Thomas Gleixner 
  Date:   Tue Jan 16 19:59:59 2018 +0100

  x86/intel_rdt/cqm: Prevent use after free

  == Regression Potential ==
  Low.  This patch fixes a current regression that is a use after free.


  ### Original Bug Description ###
  In doing Ubuntu 17.10 regression testing, we've encountered one computer 
(boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when 
running our cpu_offlining test. This test attempts to take all the CPU cores 
offline except one, then brings them back online again. This test ran 
successfully on boldore with previous releases, but with 17.10, the system 
sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found 
no problems; but when I upgraded the 16.04.3 installation to 
linux-image-4.13.0-16-generic, the problem appeared again, so I'm confident 
this is a problem with the kernel. I'm attaching two files, 
dmesg-output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output 
that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 
kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg 
-w" in a second SSH login; the files are cut-and-pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Launchpad Bug Tracker]

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

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

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

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

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

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

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

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

  systemctl restart systemd-timesyncd.service

  And afterwards the time was (apparently) correctly synced.

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

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

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

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

[Kernel-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

[Krister]

I'm sorry for dumping the dmesg output into the thread.  Here it is in a
file.  But it's from after reboot.  Does this have the error messages in
it from the previous session?  Do I have to get a file from /var/log/ ?

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1752145/+attachment/5070185/+files/dmesg.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/1752145

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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

[Kernel-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

[Krister]

Here's dmesg after a freeze of the system when watching a video with
VLC.  The strange snow did not show up this time:

=> dmesg
[0.00] Linux version 4.15.0-10-generic (buildd@lgw01-amd64-036) (gcc 
version 7.3.0 (Ubuntu 7.3.0-3ubuntu1)) #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 
2018 (Ubuntu 4.15.0-10.11-generic 4.15.3)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=7
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0003efff] usable
[0.00] BIOS-e820: [mem 0x0003f000-0x0003] reserved
[0.00] BIOS-e820: [mem 0x0004-0x0009] usable
[0.00] BIOS-e820: [mem 0x0010-0xc93bcfff] usable
[0.00] BIOS-e820: [mem 0xc93bd000-0xc9f5cfff] reserved
[0.00] BIOS-e820: [mem 0xc9f5d000-0xc9fc3fff] ACPI data
[0.00] BIOS-e820: [mem 0xc9fc4000-0xcac90fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xcac91000-0xcb10efff] reserved
[0.00] BIOS-e820: [mem 0xcb10f000-0xcb172fff] type 20
[0.00] BIOS-e820: [mem 0xcb173000-0xcb173fff] usable
[0.00] BIOS-e820: [mem 0xcb174000-0xcb181fff] reserved
[0.00] BIOS-e820: [mem 0xcb182000-0xccff] usable
[0.00] BIOS-e820: [mem 0xcd00-0xcdff] reserved
[0.00] BIOS-e820: [mem 0xd000-0xdfff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00082fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.40 by American Megatrends
[0.00] efi:  ACPI=0xc9f72000  ACPI 2.0=0xc9f72000  SMBIOS=0xf 
[0.00] secureboot: Secure boot could not be determined (mode 0)
[0.00] random: fast init done
[0.00] SMBIOS 2.8 present.
[0.00] DMI: Dell Inc. Precision Tower 7810/0KJCC5, BIOS A20 07/26/2017
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x83 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-D write-protect
[0.00]   E-F uncachable
[0.00] MTRR variable ranges enabled:
[0.00]   0 base E000 mask 3FFFE000 uncachable
[0.00]   1 base D000 mask 3000 uncachable
[0.00]   2 base 0300 mask 3F80 uncachable
[0.00]   3 base CE00 mask 3E00 uncachable
[0.00]   4 base E000 mask 3000 write-through
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.00] e820: last_pfn = 0xcd000 max_arch_pfn = 0x4
[0.00] Scanning 1 areas for low memory corruption
[0.00] Base memory trampoline at [(ptrval)] 99000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x60c93e000, 0x60c93efff] PGTABLE
[0.00] BRK [0x60c93f000, 0x60c93] PGTABLE
[0.00] BRK [0x60c94, 0x60c940fff] PGTABLE
[0.00] BRK [0x60c941000, 0x60c941fff] PGTABLE
[0.00] BRK [0x60c942000, 0x60c942fff] PGTABLE
[0.00] BRK [0x60c943000, 0x60c943fff] PGTABLE
[0.00] BRK [0x60c944000, 0x60c944fff] PGTABLE
[0.00] BRK [0x60c945000, 0x60c945fff] PGTABLE
[0.00] RAMDISK: [mem 0x31b2d000-0x34d8dfff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0xC9F72000 24 (v02 DELL  )
[0.00] ACPI: XSDT 0xC9F72098 B4 (v01 DELL   CBX3 
01072009 AMI  00010013)
[0.00] ACPI: FACP 0xC9F9DEC8 00010C (v05 DELL   CBX3 
01072009 AMI  00010013)
[0.00] ACPI: DSDT 0xC9F721E0 02BCE1 (v02 DELL   

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

[Scott Emmons]

I can confirm that with the latest bionic packages (zfsutils-linux
0.7.5-1ubuntu4) all units start successfully for the case where no ZFS
pools are present. This is exactly as I would expect.

I can't really speak to the discussion about tainted kernel. If I didn't
want ZFS, I wouldn't install zfsutils-linux, so I think it's a
reasonable expectation as-is.

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

Title:
  zfs-import-cache.service fails on startup

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

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

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

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

[bugproxy]

--- Comment From naveed...@in.ibm.com 2018-03-05 14:01 EDT---
Yes we can close this bug as fixed.

Thank you for the support and help.

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

Title:
  [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in
  repo which is required for crash analysis of vmcore

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

Bug description:
  ---Problem Description---
  No debug kernel deb packages available for 4.13.0-25-generic kernel [Ubuntu 
18.04 ]
  Unable to analyze vmcore generated via crash. 

  ---uname output---
  Linux spoon2 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:55 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTC 
   
  ---Steps to Reproduce---
  Install 18.04 ppc64el
  upgrade kernel to 4.13.0-25-generic or 4.13.0-17-generic
  try configuring debug repo
  https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
  http://ddebs.ubuntu.com/pool/main/l/linux/
  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted 
universe multiverse
  EOF

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ECDCAD72428D7C01
  sudo apt-get update
  sudo apt-get install linux-image-$(uname -r)-dbgsym

  Warning /!\ Be aware that those packages are huge! (~600 MB)

  When installed, the debug kernel can be found under
  /usr/lib/debug/boot/ and crash is started by:

  crash  

  Crash command to analyze vmcore will not work as kernel debuginfo deb package 
is not found in repo . 
  root@spoon2:~# sudo apt-get install linux-image-$(uname -r)-dbgsym
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package linux-image-4.13.0-25-generic-dbgsym
  E: Couldn't find any package by glob 'linux-image-4.13.0-25-generic-dbgsym'
  E: Couldn't find any package by regex 'linux-image-4.13.0-25-generic-dbgsym'
  root@spoon2:~# 
   
  I was also not able to find this debug symbol for 18.04 kernel. I understand 
that the current 18.04 kernel is old and was removed from the archive. Is it 
correct?

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

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

[Kernel-packages] [Bug 1749744] Re: kernel warning

[gpunk]

hello
i have installed 

linux-headers-4.16.0-994_4.16.0-994.201803032100_all.deb
linux-headers-4.16.0-994-lowlatency_4.16.0-994.201803032100_amd64.deb
linux-image-4.16.0-994-lowlatency_4.16.0-994.201803032100_amd64.deb


i'll keep you informed .

regards

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

Title:
  kernel warning

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I get very often this kernel oops:

  93228.008170] WARN_ON(i915_gem_object_has_pinned_pages(obj))
  [93228.008241] [ cut here ]
  [93228.008341] WARNING: CPU: 0 PID: 25751 at 
/build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/i915/i915_gem.c:4422 
__i915_gem_free_objects+0x2ba/0x2f0 [i915]
  [93228.008342] Modules linked in: ccm xt_tcpudp ip6t_rpfilter ip6t_REJECT 
nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ip_set nfnetlink 
ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 
nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter rfcomm bnep cdc_ether usbnet mii 
cdc_wdm cdc_acm coretemp kvm_intel snd_hda_codec_conexant snd_hda_codec_generic 
kvm irqbypass btusb btrtl snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm btbcm btintel snd_seq_midi input_leds serio_raw bluetooth arc4 
snd_seq_midi_event thinkpad_acpi nvram wmi_bmof lpc_ich snd_rawmidi
  [93228.008402]  ecdh_generic iwldvm mac80211 iwlwifi cfg80211 snd_seq 
snd_seq_device snd_timer shpchp snd mei_me mei soundcore mac_hid binfmt_misc 
sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic 
usbhid hid psmouse i915 ahci libahci i2c_algo_bit drm_kms_helper e1000e 
syscopyarea ptp sysfillrect sysimgblt fb_sys_fops pps_core drm wmi video
  [93228.008440] CPU: 0 PID: 25751 Comm: kworker/0:0 Tainted: GW   
4.13.0-32-lowlatency #35-Ubuntu
  [93228.008442] Hardware name: LENOVO 7470WGU/7470WGU, BIOS 6DET72WW (3.22 ) 
10/25/2012
  [93228.008485] Workqueue: events __i915_gem_free_work [i915]
  [93228.008488] task: 881ab17d4a00 task.stack: a03e01ca8000
  [93228.008531] RIP: 0010:__i915_gem_free_objects+0x2ba/0x2f0 [i915]
  [93228.008533] RSP: 0018:a03e01cabe00 EFLAGS: 00010286
  [93228.008535] RAX: 002e RBX: 881a37abcdc0 RCX: 
a2a62fc8
  [93228.008537] RDX:  RSI: 0092 RDI: 
0283
  [93228.008538] RBP: a03e01cabe30 R08: 0708 R09: 
a2f73600
  [93228.008540] R10: a03e01cabdd8 R11:  R12: 
8819f5e0ec00
  [93228.008541] R13: 881aac343f2c R14: 881aac34 R15: 
1000
  [93228.008544] FS:  () GS:881abbc0() 
knlGS:
  [93228.008546] CS:  0010 DS:  ES:  CR0: 80050033
  [93228.008547] CR2: 562440d00d80 CR3: 000130214000 CR4: 
06f0
  [93228.008549] Call Trace:
  [93228.008597]  __i915_gem_free_work+0x38/0x50 [i915]
  [93228.008604]  process_one_work+0x1de/0x430
  [93228.008607]  worker_thread+0x48/0x400
  [93228.008611]  kthread+0x125/0x140
  [93228.008613]  ? process_one_work+0x430/0x430
  [93228.008615]  ? kthread_create_on_node+0x70/0x70
  [93228.008620]  ret_from_fork+0x1f/0x30
  [93228.008622] Code: ff e8 18 cd 3a e1 e9 b6 fd ff ff 48 89 df e8 4e ea ff ff 
e9 b2 fe ff ff 48 c7 c6 88 b0 55 c0 48 c7 c7 95 c5 54 c0 e8 17 2d 49 e1 <0f> ff 
c7 83 d0 01 00 00 00 00 00 00 e9 74 fe ff ff 4c 89 f7 e8 
  [93228.008667] ---[ end trace 11aef733e4977a50 ]---


  
  Ubuntu 4.13.0-32.35-lowlatency 4.13.13

  
  00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub [8086:2a40] (rev 07)
  Subsystem: Lenovo Mobile 4 Series Chipset Memory Controller Hub 
[17aa:20e0]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 

  00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series 
Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA 
controller])
  Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics 
Controller [17aa:20e4]
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: i915
  Kernel modules: i915

  00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller [8086:2a43] (rev 07)
  Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics 
Controller 

[Kernel-packages] [Bug 1752946] Re: System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

[Matthias Sommer]

I really tried, but it does not do: I do not get a proposed kernel.

I enabled proposed updates, but I cannot enable the proposed archive in the 
updates tab. The option for proposed simply does not exists.  :-(
(cross checked on two other Ubuntu systems, none of them has the proposed 
option in Updates)

I tried via apt in terminal but no kernel update, not even without the
selective upgrade variant. ( a few others but no kernel.

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.:bvrP2.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Leonardo Müller]

Using the 4.16-rc4 kernel have not made the network card work after
suspension and, when I try to wake up the system it is remounting the
file system as read only and I can't open Firefox, so I'm reporting from
another computer now.

dino99's solution wouldn't break Secure Boot? Also, it works fine on
16.04, as I could suspend the system and it would wake up with no
problems with that version.

** Tags added: kernel-bug-exists-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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1752772

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

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

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

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

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

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

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

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

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

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

[Launchpad Bug Tracker]

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

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

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

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

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

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

  The previous answers listed below suggest the following diagnostics

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

  The service seems to be running

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

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

  and not blocked

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

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

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

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

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

   >hcitool dev
  Devices:
   hci0 24:0A:64:F5:EE:86

  and the output of dmsg is

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

  and of lsusb is

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

  Thanking you in 

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

[Launchpad Bug Tracker]

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

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

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

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

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

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

  The previous answers listed below suggest the following diagnostics

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

  The service seems to be running

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

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

  and not blocked

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

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

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

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

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

   >hcitool dev
  Devices:
   hci0 24:0A:64:F5:EE:86

  and the output of dmsg is

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

  and of lsusb is

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

  Thanking you in anticipation
  ---

[Kernel-packages] [Bug 1753050] Re: Does not recognize external monitor

[Jarno Suni]

As told in the description, with kernel 4.4.0-112-generic the outputs are 
recognized and work fine.
The next kernel I installed was 4.4.0-116-generic with which the bug appears. 
The bug is not fixed in v4.16-rc4.


** Tags added: kernel-bug-exists-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/1753050

Title:
  Does not recognize external monitor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Neither HDMI (digital) nor VGA (analog) output work with the kernel.
  With 4.4.0-112-generic they work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1778 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Mar  3 09:35:16 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=19c075ab-2b2e-4285-a3a5-dbd15ee7b31e
  InstallationDate: Installed on 2015-11-21 (832 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1752785] Re: package linux-image-4.15.0-10-generic 4.15.0-10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 8 when I try to dist-up

[Nicolás]

Resolved, but I can close the bug, the problem were 2 dkms.conf from
nvidia packages and one was empty... I replaced the empty file and
worked...

In spanish: el problema fueron varios dkms.conf, lo pude resolver
empezando a revisar y borrar archivos vacios, entonces ahi aparecio el
error de que "no existia el archivo", encontre que habia dos archivos
dkms de nvidia, copie el completo en el vacio y listo

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

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

Title:
  package linux-image-4.15.0-10-generic 4.15.0-10.11 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 8 when I try to dist-upgrade

Status in dkms package in Ubuntu:
  Invalid

Bug description:
  The link /initrd.img is a dangling linkto /boot/initrd.img-4.15.0-10-generic
  vmlinuz(/boot/vmlinuz-4.15.0-10-generic
  ) points to /boot/vmlinuz-4.15.0-10-generic
   (/boot/vmlinuz-4.15.0-10-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.15.0-10-generic.postinst line 491.
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.15.0-10-generic /boot/vmlinuz-4.15.0-10-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.15.0-10-generic 
/boot/vmlinuz-4.15.0-10-generic
  dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
  dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
  dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
  Error! Bad conf file.
  File: 
  does not represent a valid dkms.conf file.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kosciuk2487 F pulseaudio
   /dev/snd/controlC0:  kosciuk2487 F pulseaudio
  Date: Fri Mar  2 01:08:32 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 8
  HibernationDevice: RESUME=UUID=7eeb3a8c-066e-4883-9f70-6d2fa7cf0738
  InstallationDate: Installed on 2013-08-18 (1657 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=80324639-7326-4734-8b10-41f54ca524f3 ro 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.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions: grub-pc 2.02-2ubuntu7
  RfKill:
   
  SourcePackage: dkms
  Title: package linux-image-4.15.0-10-generic 4.15.0-10.11 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
8
  UpgradeStatus: Upgraded to bionic on 2018-03-01 (0 days ago)
  dmi.bios.date: 03/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1202
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A88-V EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1202:bd03/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

[Jon Bishop]

If it helps I am using Kernalcare so it pushes me to the latest version
which I am seeing might not be a good idea.

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

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

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

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

[Jon Bishop]

I am having the same issue. I tested the C5 instance when it first came
out and it would randomly lock up at 100% CPU. I contacted AWS support
and they could not figure it out. They sent a message to the devs to see
if they could. So I switched back to c4 instances. I decided to try it
again yesterday and it working fine until this morning when it randomly
decided to lock up at 100% CPU again. I looked at all the logs and
nothing is showing me what could be causing issues. I tried multiple
kernels and for me, they all seem to do it. Anyone figure this out? I
would really like to use the C5.

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

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

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

[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Incomplete => Fix Committed

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Andrew Cloke]

** Tags removed: triage-a
** Tags added: triage-g

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Kernel-packages] [Bug 1694485] Re: Ubuntu17.04: CAPI: call trace seen while error injection to the CAPI card.

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1694485

Title:
  Ubuntu17.04: CAPI: call trace seen while error injection to  the CAPI
  card.

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

Bug description:
  == Comment: #0 - SUDEESH JOHN  - 2017-03-18 13:55:03 ==
  ---Problem Description---
  call trace while injecting error to the CAPI card.

  " WARNING: CPU: 31 PID: 491 at 
/build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 
cxl_adapter_context_unlock+0x68/0x90 [cxl] " 

  ---uname output---
  Linux freak 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8247-21L 

  ---Steps to Reproduce---
  1. echo 1 > /sys/kernel/debug/powerpc/eeh_max_freezes
  2. echo 1 > /sys/class/cxl/card0/perst_reloads_same_image
  3.  echo 0x8000 > 
/sys/kernel/debug/powerpc/PCI/err_injct_outbound
   
  ---The complete call trace ---

  Mar 18 14:39:09 freak kernel: [  289.675421] [ cut here 
]
  Mar 18 14:39:09 freak kernel: [  289.675431] WARNING: CPU: 5 PID: 491 at 
/build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 
cxl_adapter_context_unlock+0x68/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675432] Modules linked in: xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter uio_pdrv_genirq uio 
ipmi_powernv ipmi_devintf ipmi_msghandler powernv_op_panel powernv_rng 
vmx_crypto ibmpowernv leds_powernv ib_iser rdma_cm iw_cm ib_cm ib_core configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq raid1 raid0 multipath linear ses enclosure scsi_transport_sas 
bnx2x mlx5_core tg3 cxl mdio ipr libcrc32c devlink crc32c_vpmsum pnv_php
  Mar 18 14:39:09 freak kernel: [  289.675490] CPU: 5 PID: 491 Comm: eehd Not 
tainted 4.10.0-13-generic #15-Ubuntu
  Mar 18 14:39:09 freak kernel: [  289.675492] task: c003bfbfde00 
task.stack: c003bfc5c000
  Mar 18 14:39:09 freak kernel: [  289.675493] NIP: d5cc0ca0 LR: 
d5cc0c9c CTR: c0605aa0
  Mar 18 14:39:09 freak kernel: [  289.675495] REGS: c003bfc5f6a0 TRAP: 
0700   Not tainted  (4.10.0-13-generic)
  Mar 18 14:39:09 freak kernel: [  289.675496] MSR: 9282b033 

  Mar 18 14:39:09 freak kernel: [  289.675504]   CR: 28008282  XER: 2000
  Mar 18 14:39:09 freak kernel: [  289.675504] CFAR: c0b568dc SOFTE: 1
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR00: d5cc0c9c 
c003bfc5f920 d5cf2d88 002f
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR04: 0001 
03fd 63206576 
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR08: c15dc700 
  0001
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR12: 8800 
cfb82d00 c0108c88 c003c51f9f00
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR16:  
  
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR20:  
  c0d53990
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR24: c0d53968 
c14a4330 c003ab8fa800 c003bd2c20c0
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR28: c003c5051098 
 c003ab8fa800 
  Mar 18 14:39:09 freak kernel: [  289.675535] NIP [d5cc0ca0] 
cxl_adapter_context_unlock+0x68/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675540] LR [d5cc0c9c] 
cxl_adapter_context_unlock+0x64/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675541] Call Trace:
  Mar 18 14:39:09 freak kernel: [  289.675547] [c003bfc5f920] 
[d5cc0c9c] cxl_adapter_context_unlock+0x64/0x90 [cxl] (unreliable)
  Mar 18 14:39:09 freak kernel: [  289.675556] [c003bfc5f980] 
[d5cd022c] cxl_configure_adapter+0x954/0x990 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675563] [c003bfc5fa30] 
[d5cd02c0] cxl_pci_slot_reset+0x58/0x240 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675568] [c003bfc5fae0] 
[c003b0d4] eeh_report_reset+0x154/0x190
  Mar 18 14:39:09 freak kernel: [  289.675571] [c003bfc5fb20] 
[c0039428] 

[Kernel-packages] [Bug 1745927] Re: Driver not found in Ubuntu kernel does not detect interface

[Seth Forshee]

@manjo: The fix has been committed but no kernel with the fix has been
released yet, so asking for testing is premature.

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

Title:
  Driver not found in Ubuntu kernel does not detect interface

Status in The Ubuntu-power-systems project:
  Triaged
Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Harish Sriram 
  --Problem Description---
  kernel does not detect interface in Ubuntu, driver missing in kernel

  Contact Information = hasri...@in.ibm.com

  ---Issue observed---
  While installing Ubuntu on a machine with Chelsio card, ubuntu-installer 
fails to show the interface name - probable cause would be due to missing 
driver in Ubuntu kernel. 

  Machine Type = Tuleta/Power 8 BML

  Additional Info-
  Installer Shell
  ---
  BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  ~ # ip a
  1: lo:  mtu 65536 qdisc noop qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: enP5p9s0f0:  mtu 1500 qdisc mq qlen 1000
  link/ether 98:be:94:02:09:7c brd ff:ff:ff:ff:ff:ff
  3: enP5p9s0f1:  mtu 1500 qdisc mq qlen 1000
  link/ether 98:be:94:02:09:7d brd ff:ff:ff:ff:ff:ff
  4: enP5p9s0f2:  mtu 1500 qdisc mq qlen 1000
  link/ether 98:be:94:02:09:7e brd ff:ff:ff:ff:ff:ff
  5: enP5p9s0f3:  mtu 1500 qdisc mq qlen 1000
  link/ether 98:be:94:02:09:7f brd ff:ff:ff:ff:ff:ff

  ~ # lspci -k
  :00:00.0 PCI bridge: IBM Device 03dc
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:03:00.0 Ethernet controller: Chelsio Communications Inc T422-CR Unified 
Wire Ethernet Controller
Subsystem: IBM Device 03e5
  0001:03:00.1 Ethernet controller: Chelsio Communications Inc T422-CR Unified 
Wire Ethernet Controller
Subsystem: IBM Device 03e5
  0001:03:00.2 Ethernet controller: Chelsio Communications Inc Device 4102
Subsystem: IBM Device 03e5
  0001:03:00.3 Ethernet controller: Chelsio Communications Inc Device 4102
Subsystem: IBM Device 03e5
  0001:03:00.4 Ethernet controller: Chelsio Communications Inc T422-CR Unified 
Wire Ethernet Controller
Subsystem: IBM Device 03e5
  0001:03:00.5 SCSI storage controller: Chelsio Communications Inc T422-CR 
Unified Wire Storage Controller
Subsystem: IBM Device 03e5
  0001:03:00.6 Fibre Channel: Chelsio Communications Inc T422-CR Unified Wire 
Storage Controller
Subsystem: IBM Device 03e5
  0001:03:00.7 Ethernet controller: Chelsio Communications Inc Device 
Subsystem: IBM Device 03e5
  0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 02)
Subsystem: IBM Device 03ff
  0004:00:00.0 PCI bridge: IBM Device 03dc
  0004:01:00.0 PCI bridge: Integrated Device Technology, Inc. [IDT] 
PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02)
  0004:02:02.0 PCI bridge: Integrated Device Technology, Inc. [IDT] 
PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02)
  0004:02:03.0 PCI bridge: Integrated Device Technology, Inc. [IDT] 
PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02)
  0004:03:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to 
PCI Express HBA (rev 02)
Subsystem: IBM Device 041e
  0004:03:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to 
PCI Express HBA (rev 02)
Subsystem: IBM Device 041e
  0004:04:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to 
PCI Express HBA (rev 02)
Subsystem: IBM Device 041e
  0004:04:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to 
PCI Express HBA (rev 02)
Subsystem: IBM Device 041e
  0005:00:00.0 PCI bridge: IBM Device 03dc
  0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI 
Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
  0005:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI 
Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
  0005:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI 
Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
  0005:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI 
Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
  

[Kernel-packages] [Bug 1694485] Re: Ubuntu17.04: CAPI: call trace seen while error injection to the CAPI card.

[Frank Heimes]

** Tags removed: triage-a
** Tags added: triage-g

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

Title:
  Ubuntu17.04: CAPI: call trace seen while error injection to  the CAPI
  card.

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

Bug description:
  == Comment: #0 - SUDEESH JOHN  - 2017-03-18 13:55:03 ==
  ---Problem Description---
  call trace while injecting error to the CAPI card.

  " WARNING: CPU: 31 PID: 491 at 
/build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 
cxl_adapter_context_unlock+0x68/0x90 [cxl] " 

  ---uname output---
  Linux freak 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8247-21L 

  ---Steps to Reproduce---
  1. echo 1 > /sys/kernel/debug/powerpc/eeh_max_freezes
  2. echo 1 > /sys/class/cxl/card0/perst_reloads_same_image
  3.  echo 0x8000 > 
/sys/kernel/debug/powerpc/PCI/err_injct_outbound
   
  ---The complete call trace ---

  Mar 18 14:39:09 freak kernel: [  289.675421] [ cut here 
]
  Mar 18 14:39:09 freak kernel: [  289.675431] WARNING: CPU: 5 PID: 491 at 
/build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 
cxl_adapter_context_unlock+0x68/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675432] Modules linked in: xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter uio_pdrv_genirq uio 
ipmi_powernv ipmi_devintf ipmi_msghandler powernv_op_panel powernv_rng 
vmx_crypto ibmpowernv leds_powernv ib_iser rdma_cm iw_cm ib_cm ib_core configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq raid1 raid0 multipath linear ses enclosure scsi_transport_sas 
bnx2x mlx5_core tg3 cxl mdio ipr libcrc32c devlink crc32c_vpmsum pnv_php
  Mar 18 14:39:09 freak kernel: [  289.675490] CPU: 5 PID: 491 Comm: eehd Not 
tainted 4.10.0-13-generic #15-Ubuntu
  Mar 18 14:39:09 freak kernel: [  289.675492] task: c003bfbfde00 
task.stack: c003bfc5c000
  Mar 18 14:39:09 freak kernel: [  289.675493] NIP: d5cc0ca0 LR: 
d5cc0c9c CTR: c0605aa0
  Mar 18 14:39:09 freak kernel: [  289.675495] REGS: c003bfc5f6a0 TRAP: 
0700   Not tainted  (4.10.0-13-generic)
  Mar 18 14:39:09 freak kernel: [  289.675496] MSR: 9282b033 

  Mar 18 14:39:09 freak kernel: [  289.675504]   CR: 28008282  XER: 2000
  Mar 18 14:39:09 freak kernel: [  289.675504] CFAR: c0b568dc SOFTE: 1
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR00: d5cc0c9c 
c003bfc5f920 d5cf2d88 002f
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR04: 0001 
03fd 63206576 
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR08: c15dc700 
  0001
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR12: 8800 
cfb82d00 c0108c88 c003c51f9f00
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR16:  
  
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR20:  
  c0d53990
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR24: c0d53968 
c14a4330 c003ab8fa800 c003bd2c20c0
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR28: c003c5051098 
 c003ab8fa800 
  Mar 18 14:39:09 freak kernel: [  289.675535] NIP [d5cc0ca0] 
cxl_adapter_context_unlock+0x68/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675540] LR [d5cc0c9c] 
cxl_adapter_context_unlock+0x64/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675541] Call Trace:
  Mar 18 14:39:09 freak kernel: [  289.675547] [c003bfc5f920] 
[d5cc0c9c] cxl_adapter_context_unlock+0x64/0x90 [cxl] (unreliable)
  Mar 18 14:39:09 freak kernel: [  289.675556] [c003bfc5f980] 
[d5cd022c] cxl_configure_adapter+0x954/0x990 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675563] [c003bfc5fa30] 
[d5cd02c0] cxl_pci_slot_reset+0x58/0x240 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675568] [c003bfc5fae0] 
[c003b0d4] eeh_report_reset+0x154/0x190
  Mar 18 14:39:09 freak kernel: [  289.675571] [c003bfc5fb20] 
[c0039428] eeh_pe_dev_traverse+0x98/0x170
  Mar 18 

[Kernel-packages] [Bug 1753521] Re: linux: -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow
   Status: New => Invalid

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

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

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

[Kernel-packages] [Bug 1752101] Re: linux-gcp: 4.15.0-1001.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

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

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.15.0-1001.1 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
  
- kernel-phase:Packaging
- kernel-phase-changed:Tuesday, 27. February 2018 16:00 UTC
- 
  -- swm properties --
  phase: Packaging
+ kernel-phase:Uploaded
+ kernel-phase-changed:Monday, 05. March 2018 16:00 UTC

** Description changed:

  This bug is for tracking the 4.15.0-1001.1 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 --
- phase: Packaging
- kernel-phase:Uploaded
- kernel-phase-changed:Monday, 05. March 2018 16:00 UTC
+ phase: Uploaded

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

Title:
  linux-gcp: 4.15.0-1001.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.15.0-1001.1 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 --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1681909] Console log of successful dump capture after adding a time delay of 'sleep 30'

[bugproxy]

Default Comment by Bridge

** Attachment added: "Console log of successful dump capture after adding a 
time delay of 'sleep 30'"
   
https://bugs.launchpad.net/bugs/1681909/+attachment/5070039/+files/kdump-with-sleep30-ssh.log

-- 
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:
  dump is not captured in remote host when kdump over ssh is configured
  on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
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]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 98:be:94:03:18:49
Permanent HW Address: 98:be:94:03:18:49
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Ethernet controller)
  root@ltc-firep3:~# 


  Thanks,
  Pavithra

  == Comment: #6 - PAVITHRA R. PRAKASH  -
  2017-03-07 23:20:47 ==

  
  == Comment: #7 - PAVITHRA R. PRAKASH  - 2017-03-07 

[Kernel-packages] [Bug 1707875] Re: [18.04] include support for Python bindings in "perf"

[Manoj Iyer]

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

** Changed in: ubuntu-power-systems
   Status: Triaged => Fix Committed

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

Title:
  [18.04] include support for Python bindings in "perf"

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

Bug description:
  == Comment: #0 - Paul A. Clarke  - 2017-07-26 09:59:57 ==
  ---Problem Description---
  Request to build python bindings support with perf.

  ---Steps to Reproduce---
   Ubuntu-17.04# perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
   
  Userspace tool common name: perf 
   
  Userspace rpm: linux-tools-common 

  Userspace tool obtained from project website:  na

  == Comment: #2 - MAMATHA INAMDAR  - 2017-08-01 05:02:34 
==
  After installing libpython, downloaded ubuntu 17.04 linux source code and 
compiled perf tool then it works fine.

  # ./perf script  -g python 
  generated Python script: perf-script.py

  but when I run perf tool without rebuilding after installing libpython
  it shows an error

  # perf script  -g python 
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
  root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version
  perf version 4.10.17

  == Comment: #3 - MAMATHA INAMDAR  - 2017-08-01 05:03:44 
==
  Request to build python bindings support with perf.

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

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

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

[Mike Turner]

uname -a shows:-

Linux golf 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

so I obviously haven't implemented your kernel correctly.

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  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.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1752072] Re: [Packaging] Allow overlay of config annotations

[Marcelo Cerri]

Prove of concept:

https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
gcp/+git/bionic/commit/?h=master-
next=2d1d7deafe72c48d1cc1192ed3cefa4d0e1a61b9

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

Title:
  [Packaging] Allow overlay of config annotations

Status in linux package in Ubuntu:
  Incomplete
Status in linux-gcp package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-gcp source package in Bionic:
  Fix Committed

Bug description:
  Currently for custom kernels, it's necessary to keep a separate
  annotations file that often gets out of sync with the corresponding
  file in debian.master/.

  The "debian/scripts/config-check" script can be changed to allow
  additional annotations files to act as overlays over the original
  annotations file, allowing custom kernels to override the policies
  just for the relevant configs.

  As an initial proposal, any file matching the pattern
  "$DEBIAN/config/*.annotations" could be considered as an overlay file
  and policies could be overridden on a config basis. That means that
  any mention to a config in the overlay file would discard all the
  policies for that config in the original file.

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

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

[Kernel-packages] [Bug 1706247] Re: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

[Manoj Iyer]

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

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

Title:
  Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

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

Bug description:
  16G Huge Pages are not supported on PowerNV (bare metal) installations. 
Ubuntu 16.04.2 still allows 16G huge pages to be turned on.
   
  Contact Information = Mike Hollinger (mchol...@us.ibm.com) 
   
  ---uname output---
  Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTB 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Add the following to the kernel boot args (either via editing the 
petitboot boot option manually, or updating /boot/grub/grub.cfg:

  default_hugepagesz=16G hugepagesz=16G hugepages=4

  2. Boot Linux
  3. Observe that the kernel believes 16G huge pages are available:
  ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge
  AnonHugePages:475136 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB
  ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages
  hugepages-1024kB  hugepages-16384kB  hugepages-16777216kB

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  
  This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I 
haven't checked other versions of Ubuntu.

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

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

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

[Kleber Sacilotto de Souza]

Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: Invalid

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

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: xenial

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

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

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

[Kernel-packages] [Bug 1753532] apt sources.list file

[bugproxy]

Default Comment by Bridge

** Attachment added: "apt sources.list file"
   
https://bugs.launchpad.net/bugs/1753532/+attachment/5070071/+files/sources.list

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

Title:
  apt-get update doesn't get new packages

Status in linux package in Ubuntu:
  New

Bug description:
  apt-get update and upgrade do not upgrade the system
   
  --Steps to Reproduce---
   apt-get update and apt-get upgrade.  It shows nothing to upgrade. But the 
kernel level is in an old version. 
   
  New kernel packages are not shown in apt-cache. Somehow, the new packages are 
not being got from repo server when do apt-get update.

  Executed on 16.04.3

  Btw, not all the Ubuntu servers have that issues. I crossed check the
  sources.list among the servers, there is no difference. So don't know
  what caused some of them cannot get any update from ubuntu repo.
  However, I can install individual packages via apt-get install
  command.

  There is not any error during the apt-get update && apt-get upgrade.
  It showed nothing to upgrade.

  Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease
  Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease
  Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease
  Hit:4 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  The servers were able to manually upgrade for a long time. But all the
  sudden, they are not upgradable. It looks it can not retrieve new
  kernel level packages during the apt-get update. The highest kernel
  level can be installed is 4.4.0-97.. not more higher..


  HWS: I mirrored this problem description, to be able to get support
  for getting this fixed. Even it seems to be an environment problem.
  But direct Q will probably help

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

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

[Kernel-packages] [Bug 1753532] [NEW] apt-get update doesn't get new packages

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

apt-get update and upgrade do not upgrade the system
 
--Steps to Reproduce---
 apt-get update and apt-get upgrade.  It shows nothing to upgrade. But the 
kernel level is in an old version. 
 
New kernel packages are not shown in apt-cache. Somehow, the new packages are 
not being got from repo server when do apt-get update.

Executed on 16.04.3

Btw, not all the Ubuntu servers have that issues. I crossed check the
sources.list among the servers, there is no difference. So don't know
what caused some of them cannot get any update from ubuntu repo.
However, I can install individual packages via apt-get install command.

There is not any error during the apt-get update && apt-get upgrade. It
showed nothing to upgrade.

Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease
Hit:4 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

The servers were able to manually upgrade for a long time. But all the
sudden, they are not upgradable. It looks it can not retrieve new kernel
level packages during the apt-get update. The highest kernel level can
be installed is 4.4.0-97.. not more higher..


HWS: I mirrored this problem description, to be able to get support for
getting this fixed. Even it seems to be an environment problem. But
direct Q will probably help

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-164567 severity-high 
targetmilestone-inin---
-- 
apt-get update doesn't get new packages
https://bugs.launchpad.net/bugs/1753532
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 1655280] sosreport

[bugproxy]

Default Comment by Bridge

** Attachment added: "sosreport"
   
https://bugs.launchpad.net/bugs/1655280/+attachment/5070041/+files/sosreport-LTC.150355-20170110022959.tar.xz

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

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

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1655280] console log

[bugproxy]

--- Comment (attachment only) From pavra...@in.ibm.com 2017-07-14 03:58 
EDT---


** Attachment added: "console log"
   
https://bugs.launchpad.net/bugs/1655280/+attachment/5070042/+files/Bug_mem_remove_kdump.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/1655280

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

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

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1655280] /etc/default/kdump-tools

[bugproxy]

Default Comment by Bridge

** Attachment added: "/etc/default/kdump-tools"
   
https://bugs.launchpad.net/bugs/1655280/+attachment/5070040/+files/kdump-tools.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/1655280

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

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

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

-- 
Mailing list: https://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 1749040] Re: KPTI support for arm64 systems

[dann frazier]

On Mon, Mar 5, 2018 at 7:47 AM, Paolo Pisati <1749...@bugs.launchpad.net> wrote:
> Good, any other pending tests?

Yes, just one more. I'm going to run the same test on the kpti kernel
on a different system of the same config, but *without* lvm crypt.
Starting that now.

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1680349] Re: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng.

[Andrew Cloke]

** Summary changed:

- Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine 
crashes while running stress-ng.
+ Kdump fails to capture dump on Firestone NV when machine crashes while 
running stress-ng.

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

Title:
  Kdump fails to capture dump on Firestone NV when machine crashes while
  running stress-ng.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-03-10 02:43:10 ==
  ---Problem Description---

  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng. Machine hangs.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Install stress-ng
  # apt-get install stress-ng
  3. Run stress-ng
  # stress-ng - a 0

  
  Logs:
  
  root@ltc-firep3:~# kdump-config load
  Modified cmdline:root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet 
splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=155200K 
   * loaded kdump kernel
  root@ltc-firep3:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.10.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.10.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash 
irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz
  root@ltc-firep3:~# stress-ng -a 0
  stress-ng: info:  [3900] defaulting to a 86400 second run per stressor
  stress-ng: info:  [3900] dispatching hogs: 160 af-alg, 160 affinity, 160 aio, 
160 aiol, 160 apparmor, 160 atomic, 160 bigheap, 160 brk, 160 bsearch, 160 
cache, 160 cap, 160 chdir, 160 chmod, 160 chown, 160 chroot, 160 clock, 160 
clone, 160 context, 160 copy-file, 160 cpu, 160 cpu-online, 160 crypt, 160 
daemon, 160 dccp, 160 dentry, 160 dir, 160 dirdeep, 160 dnotify, 160 dup, 160 
epoll, 160 eventfd, 160 exec, 160 fallocate, 160 fanotify, 160 fault, 160 
fcntl, 160 fiemap, 160 fifo, 160 filename, 160 flock, 160 fork, 160 fp-error, 
160 fstat, 160 full, 160 futex, 160 get, 160 getdent, 160 getrandom, 160 
handle, 160 hdd, 160 heapsort, 160 hsearch, 160 icache, 160 icmp-flood, 160 
inotify, 160 io, 160 iomix, 160 ioprio, 160 itimer, 160 kcmp, 160 key, 160 
kill, 160 klog, 160 lease, 160 link, 160 locka, 160 lockbus, 160 lockf, 160 
lockofd, 160 longjmp, 160 lsearch, 160 madvise, 160 malloc, 160 matrix, 160 
membarrier, 160 memcpy, 160 memfd, 160 mergesort, 160 mincore, 160 mknod, 160 
mlock, 160 mmap, 160 mmapfork, 160 mmapmany, 160 mq, 160 mremap, 160 msg, 160 
msync, 160 netlink-proc, 160 nice, 160 nop, 160 null, 160 numa, 160 oom-pipe, 
160 opcode, 160 open, 160 personality, 160 pipe, 160 poll, 160 procfs, 160 
pthread, 160 ptrace, 160 pty, 160 qsort, 160 quota, 160 rdrand, 160 readahead, 
160 remap, 160 rename, 160 resources, 160 rlimit, 160 rmap, 160 rtc, 160 
schedpolicy, 160 sctp, 160 seal, 160 seccomp, 160 seek, 160 sem, 160 sem-sysv, 
160 sendfile, 160 shm, 160 shm-sysv, 160 sigfd, 160 sigfpe, 160 sigpending, 160 
sigq, 160 sigsegv, 160 sigsuspend, 160 sleep, 160 sock, 160 sockfd, 160 
sockpair, 160 spawn, 160 splice, 160 stack, 160 stackmmap, 160 str, 160 stream, 
160 switch, 160 symlink, 160 sync-file, 160 sysfs, 160 sysinfo, 160 tee, 160 
timer, 160 timerfd, 160 tlb-shootdown, 160 tmpfs, 160 tsc, 160 tsearch, 160 
udp, 160 udp-flood, 160 unshare, 160 urandom, 160 userfaultfd, 160 utime, 160 
vecmath, 160 vfork, 160 vforkmany, 160 vm, 160 vm-rw, 160 vm-splice, 160 wait, 
160 wcs, 160 xattr, 160 yield, 160 zero, 160 zlib, 160 zombie
  stress-ng: info:  [3900] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [3900] cache allocate: default cache size: 2048K
  stress-ng: info:  [3907] stress-ng-atomic: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [3955] stress-ng-exec: running as root, won't run test.
  stress-ng: info:  [3999] stress-ng-icache: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4040] stress-ng-lockbus: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4313] stress-ng-numa: system has 2 of a maximum 256 memory 
NUMA nodes
  stress-ng: info:  [4455] stress-ng-rdrand: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: fail:  [4558] stress-ng-rtc: 

[Kernel-packages] [Bug 1635597] Re: Ubuntu:talclp1: Kdump failed with multipath disk

[Andrew Cloke]

** Tags removed: triage-a
** Tags added: triage-g

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

Title:
  Ubuntu:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Zesty:
  Won't Fix

Bug description:
  [Impact]
  When the target device where to dump the kernel is under a multipath 
configuration, dumping will fail, possibly leaving the system stuck in the 
kdump kernel.
  The fix is to include some scsi device handlers needed for the multipath 
setup inside the initramfs image that is used by kdump.
  All modules currently loaded in the system are included.

  [Test Case]
  Setting up kdump to target a multipath device using an appropriate storage 
that requires such scsi_dh modules and triggering a crash will demonstrate that 
kdump fails.
  After the fix, it works fine.

  [Regression Potential]
  If a bug is introduced, loading kdump might fail, and a crash will not be 
generated. A worse regression that might be considered is the system is stuck 
in such a kdump kernel and needs to be rebooted locally (and the crash file is 
not generated either). But since this is what we are trying to fix, we don't 
expect other systems to break. This didn't happen on a small (less than 1GiB of 
RAM) x86 VM, though.

  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 

[Kernel-packages] [Bug 1680349] Re: Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng.

[Frank Heimes]

** Tags removed: ubuntu-17.04

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

Title:
  Kdump fails to capture dump on Firestone NV when machine crashes while
  running stress-ng.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-03-10 02:43:10 ==
  ---Problem Description---

  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng. Machine hangs.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Install stress-ng
  # apt-get install stress-ng
  3. Run stress-ng
  # stress-ng - a 0

  
  Logs:
  
  root@ltc-firep3:~# kdump-config load
  Modified cmdline:root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet 
splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=155200K 
   * loaded kdump kernel
  root@ltc-firep3:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.10.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.10.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash 
irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz
  root@ltc-firep3:~# stress-ng -a 0
  stress-ng: info:  [3900] defaulting to a 86400 second run per stressor
  stress-ng: info:  [3900] dispatching hogs: 160 af-alg, 160 affinity, 160 aio, 
160 aiol, 160 apparmor, 160 atomic, 160 bigheap, 160 brk, 160 bsearch, 160 
cache, 160 cap, 160 chdir, 160 chmod, 160 chown, 160 chroot, 160 clock, 160 
clone, 160 context, 160 copy-file, 160 cpu, 160 cpu-online, 160 crypt, 160 
daemon, 160 dccp, 160 dentry, 160 dir, 160 dirdeep, 160 dnotify, 160 dup, 160 
epoll, 160 eventfd, 160 exec, 160 fallocate, 160 fanotify, 160 fault, 160 
fcntl, 160 fiemap, 160 fifo, 160 filename, 160 flock, 160 fork, 160 fp-error, 
160 fstat, 160 full, 160 futex, 160 get, 160 getdent, 160 getrandom, 160 
handle, 160 hdd, 160 heapsort, 160 hsearch, 160 icache, 160 icmp-flood, 160 
inotify, 160 io, 160 iomix, 160 ioprio, 160 itimer, 160 kcmp, 160 key, 160 
kill, 160 klog, 160 lease, 160 link, 160 locka, 160 lockbus, 160 lockf, 160 
lockofd, 160 longjmp, 160 lsearch, 160 madvise, 160 malloc, 160 matrix, 160 
membarrier, 160 memcpy, 160 memfd, 160 mergesort, 160 mincore, 160 mknod, 160 
mlock, 160 mmap, 160 mmapfork, 160 mmapmany, 160 mq, 160 mremap, 160 msg, 160 
msync, 160 netlink-proc, 160 nice, 160 nop, 160 null, 160 numa, 160 oom-pipe, 
160 opcode, 160 open, 160 personality, 160 pipe, 160 poll, 160 procfs, 160 
pthread, 160 ptrace, 160 pty, 160 qsort, 160 quota, 160 rdrand, 160 readahead, 
160 remap, 160 rename, 160 resources, 160 rlimit, 160 rmap, 160 rtc, 160 
schedpolicy, 160 sctp, 160 seal, 160 seccomp, 160 seek, 160 sem, 160 sem-sysv, 
160 sendfile, 160 shm, 160 shm-sysv, 160 sigfd, 160 sigfpe, 160 sigpending, 160 
sigq, 160 sigsegv, 160 sigsuspend, 160 sleep, 160 sock, 160 sockfd, 160 
sockpair, 160 spawn, 160 splice, 160 stack, 160 stackmmap, 160 str, 160 stream, 
160 switch, 160 symlink, 160 sync-file, 160 sysfs, 160 sysinfo, 160 tee, 160 
timer, 160 timerfd, 160 tlb-shootdown, 160 tmpfs, 160 tsc, 160 tsearch, 160 
udp, 160 udp-flood, 160 unshare, 160 urandom, 160 userfaultfd, 160 utime, 160 
vecmath, 160 vfork, 160 vforkmany, 160 vm, 160 vm-rw, 160 vm-splice, 160 wait, 
160 wcs, 160 xattr, 160 yield, 160 zero, 160 zlib, 160 zombie
  stress-ng: info:  [3900] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [3900] cache allocate: default cache size: 2048K
  stress-ng: info:  [3907] stress-ng-atomic: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [3955] stress-ng-exec: running as root, won't run test.
  stress-ng: info:  [3999] stress-ng-icache: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4040] stress-ng-lockbus: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4313] stress-ng-numa: system has 2 of a maximum 256 memory 
NUMA nodes
  stress-ng: info:  [4455] stress-ng-rdrand: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: fail:  [4558] stress-ng-rtc: ioctl RTC_ALRM_READ failed, errno=22 
(Invalid argument)
  stress-ng: fail:  [4017] stress-ng-key: keyctl KEYCTL_DESCRIBE failed, 
errno=127 (Key has expired)
  stress-ng: fail:  [4017] 

[Kernel-packages] [Bug 1681909] Re: dump is not captured in remote host when kdump over ssh is configured on firestone.

[Frank Heimes]

** Tags removed: ubuntu-17.04

-- 
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:
  dump is not captured in remote host when kdump over ssh is configured
  on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
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]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 98:be:94:03:18:49
Permanent HW Address: 98:be:94:03:18:49
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Ethernet controller)
  root@ltc-firep3:~# 


  Thanks,
  Pavithra

  == Comment: #6 - PAVITHRA R. PRAKASH  -
  2017-03-07 23:20:47 ==

  
  == Comment: #7 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:21:27 ==

  
  == Comment: #8 - Urvashi Jawere  - 2017-03-08 02:48:15 ==
  I am able to see some errors in syslog ;

  auxiliary
  Mar  7 04:57:44 ltc-firep3 

[Kernel-packages] [Bug 1681909] Re: dump is not captured in remote host when kdump over ssh is configured on firestone.

[Andrew Cloke]

** Summary changed:

- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is 
configured on firestone.
+ dump is not captured in remote host when kdump over ssh is configured on 
firestone.

-- 
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:
  dump is not captured in remote host when kdump over ssh is configured
  on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
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]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 98:be:94:03:18:49
Permanent HW Address: 98:be:94:03:18:49
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Ethernet controller)
  root@ltc-firep3:~# 


  Thanks,
  Pavithra

  == Comment: #6 - PAVITHRA R. PRAKASH  -
  2017-03-07 23:20:47 ==

  
  == Comment: #7 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:21:27 ==

  
  

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter

[Andrew Cloke]

** Summary changed:

- Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is 
missing as dump kernel parameter
+ Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is 
missing as dump kernel parameter

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

Title:
  Ubuntu 16.04 KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  Invalid
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  

[Kernel-packages] [Bug 1635597] Re: Ubuntu:talclp1: Kdump failed with multipath disk

[Manoj Iyer]

** Changed in: makedumpfile (Ubuntu Zesty)
   Status: Confirmed => Won't Fix

** Changed in: linux (Ubuntu Zesty)
   Status: New => Won't Fix

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

Title:
  Ubuntu:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Zesty:
  Won't Fix

Bug description:
  [Impact]
  When the target device where to dump the kernel is under a multipath 
configuration, dumping will fail, possibly leaving the system stuck in the 
kdump kernel.
  The fix is to include some scsi device handlers needed for the multipath 
setup inside the initramfs image that is used by kdump.
  All modules currently loaded in the system are included.

  [Test Case]
  Setting up kdump to target a multipath device using an appropriate storage 
that requires such scsi_dh modules and triggering a crash will demonstrate that 
kdump fails.
  After the fix, it works fine.

  [Regression Potential]
  If a bug is introduced, loading kdump might fail, and a crash will not be 
generated. A worse regression that might be considered is the system is stuck 
in such a kdump kernel and needs to be rebooted locally (and the crash file is 
not generated either). But since this is what we are trying to fix, we don't 
expect other systems to break. This didn't happen on a small (less than 1GiB of 
RAM) x86 VM, though.

  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Andrew Cloke]

** Summary changed:

- ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad 
address when trying to dump vmcore
+ ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad 
address when trying to dump vmcore

** Changed in: ubuntu-power-systems
   Status: In Progress => 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/1655280

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

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

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Frank Heimes]

** Tags removed: triage-a
** Tags added: triage-g

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

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

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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