[Kernel-packages] [Bug 1413020] Re: [Hyper-V] IP injection adds the line “# The following stanza(s) added by hv_set_ifconfig” for every pass.

[tomas]

** Changed in: linux (Ubuntu Trusty)
 Assignee: Andy Whitcroft (apw) => (unassigned)

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

Title:
  [Hyper-V] IP injection adds  the line “# The following stanza(s) added
  by hv_set_ifconfig” for every pass.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  This is new bug branched off Bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360580

  The IP injection problem has been fixed, but a small problem remains:
   
  There is one small glitch in how hv_set_ifconfig runs, as after several runs 
it keeps adding the line “# The following stanza(s) added by hv_set_ifconfig” 
for every pass.

  This is the setip execution output:
  PS C:\Users\Administrator\Desktop> .\setip.ps1
  -
  SetGuestNetworkAdapterConfiguration
  -

  Msvm_GuestNetworkAdapterConfiguration before update .. please make
  sure that VM is running ...

  IPAddresses: : {10.100.20.108, fe80::215:5dff:fe01:6c76}
  ProtocolIFType: : 4098
  DHCPEnabled: : True
  InstanceID: : 
Microsoft:GuestNetwork\9ADF60A7-E268-4039-88B0-372D3F2703D1\1A2B0CAB-5074-4551-88A8-EE39EC094A26
  Subnets: : {255.255.255.0, /64}
  DNSServers: : {8.8.8.8}
  DefaultGateways: : {10.100.20.1}

  SetGuestNetworkAdapterConfiguration
  SetGuestNetworkAdapterConfiguration success.
  Msvm_GuestNetworkAdapterConfiguration After update .. please make sure VM is 
running ...
  IPAddresses: : {10.100.20.208, fe80::215:5dff:fe01:6c76}
  ProtocolIFType: : 4098
  DHCPEnabled: : False
  InstanceID: : 
Microsoft:GuestNetwork\9ADF60A7-E268-4039-88B0-372D3F2703D1\1A2B0CAB-5074-4551-88A8-EE39EC094A26
  Subnets: : {255.0.0.0, /64}
  DNSServers: : {8.8.8.8, 8.8.4.4}
  DefaultGateways: : {10.100.20.1}

  Sample interfaces file content after running the script 3 times:

  root@ubuntu1410:~# cat /etc/network/interfaces
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  # The following stanza(s) added by hv_set_ifconfig
  # The following stanza(s) added by hv_set_ifconfig
  # The following stanza(s) added by hv_set_ifconfig
  auto eth0
  iface eth0 inet static
  address 10.100.20.108
  gateway 10.100.20.1
  dns-nameservers 8.8.4.4

  #End of hv_set_ifconfig stanzas

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

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

[Kernel-packages] [Bug 1794641] Re: Slow boot caused by unresponsive internal sd card reader

[recovered buzzy]

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

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

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

Title:
  Slow boot caused by unresponsive internal sd card reader

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.04 / Mac OS High Sierra Dual Boot on Macbook Pro
  11,1. I've had a long standing kernel problem, that is still present
  for Ubuntu's linux-generic 4.15.0-34 kernel.

  Since roughly December the system has two kinds of boots: good and
  bad. I had been running 16.04 until a few days ago. I was hoping an
  18.04 update would get rid of this problem. The problem remains, both
  with the canonical's 4.15 generic kernel and the 4.19 rc4 kernel. I
  even updated Mac OS to High Sierra in hopes that would update any
  potential firmware updates might resolve the issue.

  No dice. Hope this bug report can get the ball rolling.

  The Boots--
  Good Boot:
  5 seconds from power on chime to refind bootmanager, 5 seconds to kernel 
space, 10-15 userspace.
  Bad Boot:
  it takes about 20-30 to get to my boot manager after I select the kernel to 
use, it takes roughly 50 seconds, most of that time is spent with the kernel 
trying to assign an address to usb 2-3: my computer's SD Card Reader. Something 
prevents it from doing so and it gives up after trying all 4 usb ports twice. 
(Eats 40 seconds).

  On a Good Boot the SD Card Reader works just fine. On a Bad Boot it is
  completely nonfunctional.

  When are Good Boot and Bad Boots?-
  Cold Reboots are always Bad.
  After a Bad Boot, a warm reboot is always Good.
  A warm reboot after a Good boot is always Bad.

  I've compared the dmesg logs between the different boots and they are
  quite different. Something in the shutdown/reboot process is really
  altering how the kernel behaves. Since the slowdown starts before the
  boot manager I've been suspicious of the EFI. Checking EFI variables
  between these two boots shows an EFI variable is present after a good
  boot that is not present after a bad boot: usb-cr-rec-7c436110-ab2a-
  4bbb-a880-fe41995c9f82. This appears to be a Mac specific setting. I
  don't know what it does, but I can confirm that speeds up the boot
  process when present, regardless of which operating system I boot.

  I'm aware this might be an EFI issue that I might have to talk to
  Apple about. However, Apple's kernel seems to handle the SD card
  reader gracefully, rather than leave a 40 unresponsive blank screen
  whilst booting.

  I have attached the slow boot dmesg logs for Canonical's 4.15.0-34
  kernel. The big gaps of kernel time are generally accompanied by lines
  like

  usb 2-3: device not accepting address 4, error -62.

  I'd like to attach files for for current 4.15 Ubuntu and 4.19 Mainline fast 
and slow boots, but there
  only seems to be one attachment allowed. 

  General info
  ==
  uname -all
  ==

  Linux james-MacBookPro 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27
  15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  ==
  lspci -vvnn
  ==

  00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller 
[8086:0a04] (rev 09)
Subsystem: Apple Inc. Haswell-ULT DRAM Controller [106b:011a]
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: hsw_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA 
controller])
Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
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:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio 
Controller [8086:0a0c] (rev 09)
Subsystem: Apple Inc. Haswell-ULT HD Audio Controller [106b:011a]
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: snd_hda_intel
Kernel modules: snd_hda_intel

  00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI HC 
[8086:9c31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Intel Corporation Apple MacBookAir6,2 / MacBookPro11,1 
[8086:7270]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- F

[Kernel-packages] [Bug 1783607] Re: keine LAN verbindung mehr nach StandBy

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

Title:
  keine LAN verbindung mehr nach StandBy

Status in linux package in Ubuntu:
  Expired

Bug description:
  Nutze ein Sony Notebook VPCEC4L1E 64 bit, Kernel 4.14.57.041457 mit Kubuntu 
16.04 LTS.
  Nach Updates am 23.07.2018, u. a. auch auf den Kernel v4.15.9 stellte ich 
fest, dass sobald
  das Notebook in den StandBy Modus geht, danach keine LAN Verbindung mehr 
möglich ist.
  Dieser Fehler besteht bei allen Kernel beginnend mit v4.15 bis v4.17.9

  Use a Sony notebook VPCEC4L1E 64 bit, Kernel 4.14.57.041457 with Kubuntu 
16.04 LTS.
  After updates on 23.07.2018, u. a. also on the kernel v4.15.9 I realized that 
as soon as
  the notebook goes into standby mode, then no LAN connection is possible 
anymore.
  This bug exists with all kernels beginning with v4.15 through v4.17.9

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

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

[Kernel-packages] [Bug 1782125] Re: sound not working but driver all set

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

Title:
  sound not working but driver all set

Status in linux package in Ubuntu:
  Expired

Bug description:
  sound not working and some issue to rum kali linux packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-131-generic 4.4.0-131.157
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Jul 17 16:52:55 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=f8021436-59da-47fb-a06e-75f56c298fd1
  InstallationDate: Installed on 2017-11-27 (232 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Vostro 15-3568
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed 
root=UUID=2b2cc385-d110-4524-aada-58e05aefbc62 ro acpi_rev_override 
drm.debug=0xe plymouth:debug quiet splash
  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-131-generic N/A
   linux-backports-modules-4.4.0-131-generic  N/A
   linux-firmware 1.157.20
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-05-16 (62 days ago)
  dmi.bios.date: 11/13/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.4
  dmi.board.name: 06XGVW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn06XGVW:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 15-3568
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

[Guo Yaowen]

hi Guilherme,
I have tested kernel 4.17.0,but the issuse is same.The 4.17.0 testing results 
are as below:
uname -r
4.17.0-041700rc1-generic

cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc1-generic 
root=UUID=3e875566-3c1b-4bda-a869-6eb59ff1624a ro nvme_core.multipath=0

ls -l /sys/block/*
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/loop0 -> 
../devices/virtual/block/loop0
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/loop1 -> 
../devices/virtual/block/loop1
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/loop2 -> 
../devices/virtual/block/loop2
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/loop3 -> 
../devices/virtual/block/loop3
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/loop4 -> 
../devices/virtual/block/loop4
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/loop5 -> 
../devices/virtual/block/loop5
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/loop6 -> 
../devices/virtual/block/loop6
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/loop7 -> 
../devices/virtual/block/loop7
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/nvme0n1 -> 
../devices/pci:80/:80:03.2/:83:00.0/nvme/nvme2/nvme0n1
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/nvme1n1 -> 
../devices/pci:80/:80:03.3/:84:00.0/nvme/nvme3/nvme1n1
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/nvme1n2 -> 
../devices/pci:80/:80:03.3/:84:00.0/nvme/nvme3/nvme1n2
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/nvme2n1 -> 
../devices/pci:80/:80:03.1/:82:00.0/nvme/nvme1/nvme2n1
lrwxrwxrwx 1 root root 0 Sep 29 11:19 /sys/block/nvme3n1 -> 
../devices/pci:80/:80:03.0/:81:00.0/nvme/nvme0/nvme3n1


Or can you provide a download link for the Ubuntu kernel? Let me do the same 
test. 

Thanks,
Guo Yaowen

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

Title:
  nvme name floated after boot with 4.15.0 kernel

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

Bug description:
  nvme device name such as /dev/nvme?n?p? would be floated that is
  symbol link to different real ssd device after reboot in 4.15.0 kernel
  for 16.04.5 HWE and 18.04 GA-kernel. This are not found on 16.04.5 GA-
  kernel ( 4.4.0)

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

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

[Kernel-packages] [Bug 1760338] Re: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)

[hbchoong]

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

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

Title:
  Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)

Status in Ubuntu:
  Confirmed
Status in linux-signed package in Ubuntu:
  Confirmed
Status in xinput package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  All the Fn keys are working (audio, mute, bright, volume and even
  wifi) except for enable/disable touchpad. No display info and no
  effect.

  PS: Fn Bright up/down takes about 3s to work the first time or if not
  used for about 2 minutes. Volume also have a similar problem but only
  the first time it is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xinput 1.6.2-1build1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-13ubuntu1)
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Mar 31 15:41:59 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.42, 4.15.0-12-generic, x86_64: installed
   nvidia, 390.42, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840]
  InstallationDate: Installed on 2018-03-09 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 008: ID 04f2:b446 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 248a:8366  
   Bus 001 Device 002: ID 04f3:2228 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA Satellite S55t-C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=62fa4fcd-f1c6-43f5-a86d-ccaae2565dac ro locale=pt_BR quiet splash 
vt.handoff=1
  SourcePackage: xinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.20
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite S55t-C
  dmi.product.version: PSPUGU-00200D
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Chris Guiver]

Downloaded
http://archive.ubuntu.com/ubuntu/dists/cosmic/main/installer-i386/current/images/netboot/mini.iso

wrote to usb & booted on dc7700.   It mainly has 'install' options, I'm
not willing to install to test; so selected 'rescue mode' ...

it asked a number of questions (keyboard, mirror..) then started
downloads; about 40% done it went purple-screen ("Rescue mode" top left
in white, white bar on bottom line, black space bottom left) & stopped
dead. ctrl-alt-f2 asked me to press enter to open console, which put me
at BusyBox v1.27.2  ctrl-alt-f1 is static screen... i waited

eventually i hit enter, white bar increased in size (two lines); 'rescue
mode' now gone, enter a few more times & white area is increasing.. I
`ls` & enter and a line just has 'ls' on it now.

because I've not used this installer; I don't know if this behavior is
normal, or wrong... the test cases in iso.QA are for 'install'.

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Unknown

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

[Kernel-packages] [Bug 1760338] Re: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)

[hbchoong]

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

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

Title:
  Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)

Status in Ubuntu:
  Confirmed
Status in linux-signed package in Ubuntu:
  New
Status in xinput package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  All the Fn keys are working (audio, mute, bright, volume and even
  wifi) except for enable/disable touchpad. No display info and no
  effect.

  PS: Fn Bright up/down takes about 3s to work the first time or if not
  used for about 2 minutes. Volume also have a similar problem but only
  the first time it is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xinput 1.6.2-1build1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-13ubuntu1)
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Mar 31 15:41:59 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.42, 4.15.0-12-generic, x86_64: installed
   nvidia, 390.42, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840]
  InstallationDate: Installed on 2018-03-09 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 008: ID 04f2:b446 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 248a:8366  
   Bus 001 Device 002: ID 04f3:2228 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA Satellite S55t-C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=62fa4fcd-f1c6-43f5-a86d-ccaae2565dac ro locale=pt_BR quiet splash 
vt.handoff=1
  SourcePackage: xinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.20
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite S55t-C
  dmi.product.version: PSPUGU-00200D
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Chris Guiver]

Lubuntu 18.10 (today's daily image) on dc7700

"ehci-pci :00:1a.7: dma_direct_map_sg: overflow
0x00016233c000+2048 of device mask "

(alt-f1 = lubuntu plymouth dots; alt-f2 just scrolling "[  999.99]
ehci-pci.." messages

I have no idea what the overflow number means; but it's different.  I copied
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 of 
device mask "  from earlier in lp.bug.report; and had to alter it.

I'll shutdown machine at 2400.  (~40mins)

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Unknown

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Chris Guiver]

I've re-run zsync for latest image; no 'ehci-pci' messages on either
dc7700 or 755 for Xubuntu x86  (but both drop to BusyBox/initramfs)

Given different messages - I reported as a different bug (for QA tracker)
http://launchpad.net/bugs/1795092
providing link to here of course; inc. your upstream possible link..
(I am yet to try lubuntu image today)

-- hp dc7700 (c2d, 5gb ram, nvidia quadro nvs290/g86)
guiverc@dc7700ub:~$ lscpi|grep HCI
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #5 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #2 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #2 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #1 (rev 02)

-- dell 755 (c2d, 5gb ram, rv516/x1300/x1550 radeon)
755-suse:/home/guiverc # lspci |grep HCI
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port 
SATA Controller [AHCI mode] (rev 02)

Sorry Walter, I'm lost with the following

> It also might be good to check a 32 bit kernel on a 64 bit machine if you can 
> get 
> that test out of the way
> If it's possible, checking all those different ones will likely prove helping 
> in
> understanding the scope of the problem.

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Unknown

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

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

[NJ]

I've encountered the same error, on Mint 19 - based on Ubuntu 18.04 -
with kernel 4.19.0-041900rc4-generic.

I encountered the problem while trying to re-enable my touchpad after
resume from sleep - on the infamous Lenovo X1 Carbon Sixth Generation.

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

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

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

Bug description:
  Got this bug/oops while running with the linux-image-4.4.0-113-generic
  (4.4.0-113.136) kernel from -proposed:

  BUG: unable to handle kernel NULL pointer dereference at 0009
  IP: [] csum_and_copy_from_iter+0x55/0x4c0
  PGD 0 
  Oops:  [#1] SMP 
  Modules linked in: ctr ccm veth xt_CHECKSUM iptable_mangle xt_comment ec_sys 
bridge stp llc nf_log_ipv6 ip6table_filter ip6t_MASQUERADE 
nf_nat_masquerade_ipv6 ip6table_nat nf_nat_ipv6 ip6_tables nf_log_ip
   snd ghash_clmulni_intel soundcore r8169 psmouse input_leds cfg80211 rtsx_pci 
mii vhost_net vhost media ahci libahci macvtap macvlan mei_me mei kvm_intel kvm 
irqbypass tpm_crb i2c_hid intel_lpss_acpi inte
  CPU: 2 PID: 3997 Comm: dnsmasq Tainted: PW  O4.4.0-113-generic 
#136-Ubuntu
  Hardware name: System76Lemur/Lemur, BIOS 5.12 
02/17/2017
  task: 880830269e00 ti: 880035c44000 task.ti: 880035c44000
  RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
  RSP: 0018:880035c47a18  EFLAGS: 00010246
  RAX: ab729fd0 RBX: 001c RCX: 880035c47e98
  RDX: 880035c47a94 RSI: 001c RDI: 8807ef1a7424
  RBP: 880035c47a80 R08:  R09: 8807ef1a7424
  R10: 8807ef1a7424 R11: 8807ef1a7400 R12: 880035c47e98
  R13:  R14: 00ffabea6920 R15: 0001
  FS:  7ff2b234d880() GS:88086ed0() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0009 CR3: 35c1e000 CR4: 00360670
  Stack:
   88084e001600 ab72d1d7 880830f18500 880035c47aaf
   880035c47a94 01c0  b0f4001fc4815eea
   001c 880830f18500  880035c47d30
  Call Trace:
   [] ? __alloc_skb+0x87/0x1f0
   [] ip_generic_getfrag+0x56/0xe0
   [] raw_getfrag+0xaf/0x100
   [] __ip_append_data.isra.45+0x98a/0xb90
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ip_append_data.part.46+0x7a/0xe0
   [] ip_append_data+0x34/0x40
   [] raw_sendmsg+0x724/0xc00
   [] ? aa_sk_perm+0x70/0x210
   [] ? aa_sock_msg_perm+0x61/0x150
   [] inet_sendmsg+0x6b/0xa0
   [] sock_sendmsg+0x3e/0x50
   [] SYSC_sendto+0x101/0x190
   [] ? sock_setsockopt+0x180/0x830
   [] ? apparmor_socket_setsockopt+0x22/0x30
   [] SyS_sendto+0xe/0x10
   [] entry_SYSCALL_64_fastpath+0x1c/0x93
  Code: f3 48 0f 47 de 48 85 db 0f 84 8b 01 00 00 8b 02 49 89 f9 49 89 cc 4c 8b 
71 08 89 45 c4 8b 01 a8 04 0f 85 79 01 00 00 4c 8b 79 18 <4d> 8b 6f 08 4d 29 f5 
49 39 dd 4c 0f 47 eb a8 02 0f 85 36 02 00 
  RIP  [] csum_and_copy_from_iter+0x55/0x4c0
   RSP 
  CR2: 0009
  ---[ end trace bdd9157c94a456b6 ]---

  The trigger is when I start an artful lxd container and it tries to
  get an IPv4/IPv6. Oddly enough, the same thing works perfectly for my
  xenial container. My lxd-bridge has dnsmasq contained by Apparmor
  which is non standard but always worked flawlessly.

  I can trigger the bug 100% of the time so validating any tentative fix
  should be easy.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-113-generic 4.4.0-113.136
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  7244 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sat Feb 10 16:45:26 2018
  HibernationDevice: RESUME=/dev/mapper/nvme0n1p3_crypt
  InstallationDate: Installed on 2016-12-06 (431 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  MachineType: System76 Lemur
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=49432620-38ed-44bd-912a-7bc51eec3a35 ro quiet splash possible_cpus=4 
nmi_watchdog=0 kaslr vsyscall=none vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.16
  RfKill: Error: [Errno 2] No such f

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Chris Guiver]

another update on xubuntu 18.10 (x86) iso
the same thumb-drive image runs fine on d610 (dell latitude laptop)
(no zsync yet)

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Unknown

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Chris Guiver]

update on xubuntu 18.10 (x86) iso 
both systems get to busybox; the dc7700 (other box) didn't show hundreds of 
those ehci-pci messages...

BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) bui...
Enter 'help'...
(initramfs) Unable to find a medium containing a live file system

It was yesterday's daily; I'll re-zsync it, then re-write & re-test both
(after confirming image runs fine on d610 laptop) - but later... (UWN
summaries..)

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Unknown

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Chris Guiver]

Reply to "Ubuntu Kernel Bot"

> This bug is missing log files that will aid in diagnosing the problem.
> While running an Ubuntu kernel

The ISO doesn't boot on those machines, so I can't get to a terminal.

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

Done

Walter, thanks again!

I'll have to learn a little about EHCI so I can recognize it.

As for xubuntu x86 daily ISO - I wrote one yesterday to test, but never got 
around to it
I booted it on dell 755 (next to me as I type this), and

"ehci-pci 000:00:1a.7: dma_direct_map_sg: overflow
0x16ca56000+2048 of device mask "

(typed, so may not be exact).  It did't continue endlessly, eventually
getting to BusyBox.

I only left one (lubuntu 18.10 image) system go for 30 mins (can't
recall which; both use same keyd/mouse/screen), so maybe a lubuntu image
will also drop to busybox if you want me to try...

I'll add more when I can..

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Unknown

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Chris Guiver]

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Unknown

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

[Kernel-packages] [Bug 1794807] Re: linux-kvm: 4.18.0-1001.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

** Description changed:

  This bug is for tracking the 4.18.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 --
  kernel-master-bug: 1791663
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Friday, 28. September 2018 21:31 UTC

** Description changed:

  This bug is for tracking the 4.18.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 --
  kernel-master-bug: 1791663
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Friday, 28. September 2018 21:31 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-kvm: 4.18.0-1001.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.18.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 --
  kernel-master-bug: 1791663
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Olivier Tilloy]

@Seth: I can reliably reproduce the crash in an up-to-date i386 cosmic
VM. You need to install libreoffice-base (which is not installed by
default, and pulls in all the java dependencies), then run it with
"libreoffice --base", go through the initial wizard to create a new
HSQLDB database, and that's when the crash happens.

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

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

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

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

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

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

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


  uname -a:

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


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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1794807] Re: linux-kvm: 4.18.0-1001.1 -proposed tracker

[Brad Figg]

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

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

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.18.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 --
  kernel-master-bug: 1791663
+ kernel-phase:Uploaded
+ kernel-phase-changed:Friday, 28. September 2018 20:31 UTC

** Description changed:

  This bug is for tracking the 4.18.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 --
  kernel-master-bug: 1791663
- kernel-phase:Uploaded
- kernel-phase-changed:Friday, 28. September 2018 20:31 UTC
+ phase: Uploaded

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

Title:
  linux-kvm: 4.18.0-1001.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.18.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 --
  kernel-master-bug: 1791663
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1791663] Re: linux: 4.18.0-8.9 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-cosmic

** Tags removed: block-proposed

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

Title:
  linux: 4.18.0-8.9 -proposed tracker

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

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

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

  backports:
  derivatives: bug 1791664 (linux-azure)
  -- swm properties --
  backports: null
  derivatives: null
  phase: Promoted to proposed

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

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

[Kernel-packages] [Bug 1795036] Re: iptables --list --numeric fails on -virtual kernel

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/355867

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

Title:
  iptables --list --numeric fails on -virtual kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh instance of cosmic, run:

  $ sudo iptables --list --numeric; echo $?
  iptables: No chain/target/match by that name.
  1

  Expected result is something like:

  $ iptables --list --numeric
  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain FORWARD (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  target prot opt source   destination

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: User Name 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 28 16:47 seq
   crw-rw 1 root audio 116, 33 Sep 28 16:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Sep 28 16:48:51 2018
  Ec2AMI: ami-018b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr17.0.4:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.family: Virtual Machine
  dmi.product.name: OpenStack Nova
  dmi.product.version: 17.0.4
  dmi.sys.vendor: OpenStack Foundation

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

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

[Kernel-packages] [Bug 1791663] Re: linux: 4.18.0-8.9 -proposed tracker

[Seth Forshee]

** Tags added: regression-testing-passed

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

Title:
  linux: 4.18.0-8.9 -proposed tracker

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

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

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

  backports:
  derivatives: bug 1791664 (linux-azure)
  -- swm properties --
  backports: null
  derivatives: null
  phase: Promoted to proposed

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

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

[Kernel-packages] [Bug 1778844] Re: nvme multipath does not report path relationships

[Thadeu Lima de Souza Cascardo]

First piece of the puzzle submitted:
http://lists.infradead.org/pipermail/linux-nvme/2018-September/020174.html

Tested with a small change on initramfs-tools, though I will wait for
comments on the first one before submitting that to initramfs-tools
upstream.

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Invalid

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  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.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa4

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

[Seth Forshee]

I've tried to reproduce the crash in a vm running up-to-date i386
cosmic, kernel version 4.18.0-7.8. I'm not seeing any crashes opening up
the libreoffice apps. Can you give instructions on how to reproduce?
Thanks.

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

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

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

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

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

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

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


  uname -a:

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


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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1794454] Re: linux: 3.13.0-160.210 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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/1794454

Title:
  linux: 3.13.0-160.210 -proposed tracker

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

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

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

  backports: bug 1794455 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog

[Philipp]

Thanks for your reply.
This is a new laptop, so I am not able to say anything about prior kernel 
versions.
With upstream kernel v4.19 the issue 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/1793960

Title:
  Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The trackpad is working, but syslog is full of kernel errors regarding
  "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id
  data (ff)" if the trackpad is touched.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlku   1269 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Sep 23 15:48:36 2018
  HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561
  InstallationDate: Installed on 2018-09-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80XR
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5RCN36WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IAP
  dmi.modalias: 
dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP:
  dmi.product.family: ideapad 320-15IAP
  dmi.product.name: 80XR
  dmi.product.version: Lenovo ideapad 320-15IAP
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1793584] Re: i2c_hid module randomly dies and needs to be restarted

[wmdiem]

Also, right click doesn't work (ever) under the test kernel (by right click
I mean depressing the pad itself while touching the right side of the pad.
Double-tap still works to simulate right click.

Further, if I reload the module, the error changes (note the numbers at the
end):
[ 1451.670747] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete
report (707/65535)

Note that it is on reload that the jittery cursor movement starts (it looks
like the cursor position is being updated ~10 times a second, rather than
more than 30 times a second).


On Fri, Sep 28, 2018 at 12:29 PM William Diem  wrote:

> Okay, I haven't yet lost the trackpad completely, but twice now tap to
> click has stopped working. The first time I rebooted to make sure it had
> actually been working under the test kernel (I was pretty sure it had, but
> wanted to confirm). The second time I removed and reloaded the i2c_hid
> module; tap to touch returned, but there now a visible jitter in moving the
> cursor.
>
> On Fri, Sep 28, 2018 at 11:47 AM William Diem  wrote:
>
>> Okay, have installed the new kernel.
>>
>> 1) I got an error
>> installing linux-headers-4.19.0-1-generic_4.19.0-1.2_elan+i2c_amd64.deb
>> because of unmet dependency, but I installed with "--force-depends".
>> 2) The log is still getting spammed with "incomplete report" errors.
>> 3)  But the touchpad is working for the moment. It has only been up for a
>> few minutes. I'll keep running it and see if it continues to work. And
>> report back.
>>
>> On Fri, Sep 28, 2018 at 3:05 AM Kai-Heng Feng <
>> kai.heng.f...@canonical.com> wrote:
>>
>>> Ok, please try the kernel inside the link.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1793584
>>>
>>> Title:
>>>   i2c_hid module randomly dies and needs to be restarted
>>>
>>> Status in linux package in Ubuntu:
>>>   Incomplete
>>>
>>> Bug description:
>>>   From 4.15.0-24 (not in 4.15.0-23) i2c_hid spams the log with messages
>>>   like this:
>>>
>>>   [ 6079.727465] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete
>>> report (14/65535)
>>>   [ 6079.733692] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete
>>> report (14/65535)
>>>
>>>   It then randomly stops working (and stops spamming the log), and there
>>>   is no trackpad response until I reload the module.
>>>
>>>   Again, this was introduced in 4.15.0-24.
>>>
>>> To manage notifications about this bug go to:
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793584/+subscriptions
>>>
>>

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

Title:
  i2c_hid module randomly dies and needs to be restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  From 4.15.0-24 (not in 4.15.0-23) i2c_hid spams the log with messages
  like this:

  [ 6079.727465] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete report 
(14/65535)
  [ 6079.733692] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete report 
(14/65535)

  It then randomly stops working (and stops spamming the log), and there
  is no trackpad response until I reload the module.

  Again, this was introduced in 4.15.0-24.

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

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

[Kernel-packages] [Bug 1794387] Re: Colour banding in HP Pavilion 15-n233sl integrated display

[Mattia Orlandi]

Using the kernel provided by Kai-Heng Feng solves the issue, now colour banding 
is gone.
Thank you very much!

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

Title:
  Colour banding in HP Pavilion 15-n233sl integrated display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Colour bandind is visible everywhere in the system, and it appeared
  after I had my integrated monitor replaced. I believe it's not a
  hardware problem, since booting with 'nomodeset' works as expected.

  There were already two similar bugs,
  https://bugs.launchpad.net/bugs/1749420 and
  https://bugs.launchpad.net/bugs/1788308, but the fixes provided for
  those bugs did not work for my specific monitor.

  I'm running Ubuntu 18.04 with kernel linux-image-4.15.0-34-generic,
  installing linux-image-4.18.8 with UKUU didn't help.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  sudo get-edid | edid-decode in a file named edid-decoded.txt
  cat /proc/version_signature in version.log
  sudo lspci -vnvn in lspci-vnvn.log.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   1796 F pulseaudio
   /dev/snd/controlC1:  matt   1796 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2018-09-27 (0 days ago)
  InstallationMedia: neon devunstable "Bionic" - Build amd64 LIVE Binary 
20180924-13:08
  Lsusb:
   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 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=c3f61207-d13e-474b-a499-98030ddef8e1 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UnreportableReason: Questa segnalazione riguarda un pacchetto che non è 
installato.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 03/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.71
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2166
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.71:bd03/13/2017:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1795036] Re: iptables --list --numeric fails on -virtual kernel

[Scott Moser]

Originally ran into this trying to use lxd on cosmic as described in
 https://github.com/lxc/lxd/issues/5081

Simple test case was just:
 a.) launch fresh cosmic instance
 b.) sudo snap install lxd
 c.) sudo lxd waitready
 d.) sudo lxd init --auto --storage-backend=dir

In the failure case, that takes quite a while, exits 1 and writes:

Error: Failed to create network 'lxdbr0': Failed to list ipv4 rules for
LXD network lxdbr0 (table filter)

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

Title:
  iptables --list --numeric fails on -virtual kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh instance of cosmic, run:

  $ sudo iptables --list --numeric; echo $?
  iptables: No chain/target/match by that name.
  1

  Expected result is something like:

  $ iptables --list --numeric
  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain FORWARD (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  target prot opt source   destination

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: User Name 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 28 16:47 seq
   crw-rw 1 root audio 116, 33 Sep 28 16:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Sep 28 16:48:51 2018
  Ec2AMI: ami-018b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr17.0.4:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.family: Virtual Machine
  dmi.product.name: OpenStack Nova
  dmi.product.version: 17.0.4
  dmi.sys.vendor: OpenStack Foundation

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

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

[Kernel-packages] [Bug 1795036] Re: iptables --list --numeric fails on -virtual kernel

[Scott Moser]

The module needed to magically make this work is 'bpfilter.ko'.

So at least one solution for this is to move bpfilter.ko from
the linux-modules-extra to linux-modules.

Currently linux-modules-extra-4.18.0-7-generic but we would want it
in linux-modules-4.18.0-7-generic.


bpfilter is described at https://lwn.net/Articles/747551/

** Bug watch added: LXD bug tracker #5081
   https://github.com/lxc/lxd/issues/5081

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

Title:
  iptables --list --numeric fails on -virtual kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh instance of cosmic, run:

  $ sudo iptables --list --numeric; echo $?
  iptables: No chain/target/match by that name.
  1

  Expected result is something like:

  $ iptables --list --numeric
  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain FORWARD (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  target prot opt source   destination

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: User Name 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 28 16:47 seq
   crw-rw 1 root audio 116, 33 Sep 28 16:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Sep 28 16:48:51 2018
  Ec2AMI: ami-018b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr17.0.4:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.family: Virtual Machine
  dmi.product.name: OpenStack Nova
  dmi.product.version: 17.0.4
  dmi.sys.vendor: OpenStack Foundation

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

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

[Kernel-packages] [Bug 1791942] Re: Xenial update to 4.4.145 stable release

[Kleber Sacilotto de Souza]

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

Title:
  Xenial update to 4.4.145 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.145 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.145 stable release shall be applied:
  * MIPS: ath79: fix register address in ath79_ddr_wb_flush()
  * ip: hash fragments consistently
  * net/mlx4_core: Save the qpn from the input modifier in RST2INIT wrapper
  * rtnetlink: add rtnl_link_state check in rtnl_configure_link
  * tcp: fix dctcp delayed ACK schedule
  * tcp: helpers to send special DCTCP ack
  * tcp: do not cancel delay-AcK on DCTCP special ACK
  * tcp: do not delay ACK in DCTCP upon CE status change
  * ip: in cmsg IP(V6)_ORIGDSTADDR call pskb_may_pull
  * usb: cdc_acm: Add quirk for Castles VEGA3000
  * usb: core: handle hub C_PORT_OVER_CURRENT condition
  * usb: gadget: f_fs: Only return delayed status when len is 0
  * driver core: Partially revert "driver core: correct device's shutdown order"
  * can: xilinx_can: fix RX loop if RXNEMP is asserted without RXOK
  * can: xilinx_can: fix recovery from error states not being propagated
  * can: xilinx_can: fix device dropping off bus on RX overrun
  * can: xilinx_can: keep only 1-2 frames in TX FIFO to fix TX accounting
  * can: xilinx_can: fix incorrect clear of non-processed interrupts
  * can: xilinx_can: fix RX overflow interrupt not being enabled
  * turn off -Wattribute-alias
  * ARM: fix put_user() for gcc-8
  * Linux 4.4.145

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

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

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

Title:
  iptables --list --numeric fails on -virtual kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh instance of cosmic, run:

  $ sudo iptables --list --numeric; echo $?
  iptables: No chain/target/match by that name.
  1

  Expected result is something like:

  $ iptables --list --numeric
  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain FORWARD (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  target prot opt source   destination

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: User Name 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 28 16:47 seq
   crw-rw 1 root audio 116, 33 Sep 28 16:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Sep 28 16:48:51 2018
  Ec2AMI: ami-018b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr17.0.4:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.family: Virtual Machine
  dmi.product.name: OpenStack Nova
  dmi.product.version: 17.0.4
  dmi.sys.vendor: OpenStack Foundation

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

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

[Kernel-packages] [Bug 1791953] Re: Xenial update to 4.4.146 stable release

[Kleber Sacilotto de Souza]

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

Title:
  Xenial update to 4.4.146 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.146 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.146 stable release shall be applied:
  * MIPS: Fix off-by-one in pci_resource_to_user()
  * Input: elan_i2c - add ACPI ID for lenovo ideapad 330
  * Input: i8042 - add Lenovo LaVie Z to the i8042 reset list
  * Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST
  * tracing: Fix double free of event_trigger_data
  * tracing: Fix possible double free in event_enable_trigger_func()
  * tracing/kprobes: Fix trace_probe flags on enable_trace_kprobe() failure
  * tracing: Quiet gcc warning about maybe unused link variable
  * xen/netfront: raise max number of slots in xennet_get_responses()
  * ALSA: emu10k1: add error handling for snd_ctl_add
  * ALSA: fm801: add error handling for snd_ctl_add
  * nfsd: fix potential use-after-free in nfsd4_decode_getdeviceinfo
  * mm: vmalloc: avoid racy handling of debugobjects in vunmap
  * mm/slub.c: add __printf verification to slab_err()
  * rtc: ensure rtc_set_alarm fails when alarms are not supported
  * netfilter: ipset: List timing out entries with "timeout 1" instead of zero
  * infiniband: fix a possible use-after-free bug
  * hvc_opal: don't set tb_ticks_per_usec in udbg_init_opal_common()
  * powerpc/64s: Fix compiler store ordering to SLB shadow area
  * RDMA/mad: Convert BUG_ONs to error flows
  * disable loading f2fs module on PAGE_SIZE > 4KB
  * f2fs: fix to don't trigger writeback during recovery
  * usbip: usbip_detach: Fix memory, udev context and udev leak
  * perf/x86/intel/uncore: Correct fixed counter index check in generic code
  * perf/x86/intel/uncore: Correct fixed counter index check for NHM
  * iwlwifi: pcie: fix race in Rx buffer allocator
  * Bluetooth: hci_qca: Fix "Sleep inside atomic section" warning
  * Bluetooth: btusb: Add a new Realtek 8723DE ID 2ff8:b011
  * ASoC: dpcm: fix BE dai not hw_free and shutdown
  * mfd: cros_ec: Fail early if we cannot identify the EC
  * mwifiex: handle race during mwifiex_usb_disconnect
  * wlcore: sdio: check for valid platform device data before suspend
  * media: videobuf2-core: don't call memop 'finish' when queueing
  * btrfs: add barriers to btrfs_sync_log before log_commit_wait wakeups
  * btrfs: qgroup: Finish rescan when hit the last leaf of extent tree
  * PCI: Prevent sysfs disable of device while driver is attached
  * ath: Add regulatory mapping for FCC3_ETSIC
  * ath: Add regulatory mapping for ETSI8_WORLD
  * ath: Add regulatory mapping for APL13_WORLD
  * ath: Add regulatory mapping for APL2_FCCA
  * ath: Add regulatory mapping for Uganda
  * ath: Add regulatory mapping for Tanzania
  * ath: Add regulatory mapping for Serbia
  * ath: Add regulatory mapping for Bermuda
  * ath: Add regulatory mapping for Bahamas
  * powerpc/32: Add a missing include header
  * powerpc/chrp/time: Make some functions static, add missing header include
  * powerpc/powermac: Add missing prototype for note_bootable_part()
  * powerpc/powermac: Mark variable x as unused
  * powerpc/8xx: fix invalid register expression in head_8xx.S
  * pinctrl: at91-pio4: add missing of_node_put
  * PCI: pciehp: Request control of native hotplug only if supported
  * mwifiex: correct histogram data with appropriate index
  * scsi: ufs: fix exception event handling
  * ALSA: emu10k1: Rate-limit error messages about page errors
  * regulator: pfuze100: add .is_enable() for pfuze100_swb_regulator_ops
  * md: fix NULL dereference of mddev->pers in remove_and_add_spares()
  * media: smiapp: fix timeout checking in smiapp_read_nvm
  * ALSA: usb-audio: Apply rate limit to warning messages in URB complete 
callback
  * HID: hid-plantronics: Re-resend Update to map button for PTT products
  * drm/radeon: fix mode_valid's return type
  * powerpc/embedded6xx/hlwd-pic: Prevent interrupts from being handled by 
Starlet
  * HID: i2c-hid: check if device is there before really probing
  * tty: Fix data race in tty_insert_flip_string_fixed_flag
  * dma-iommu: Fix compilation when !CONFIG_IOMMU_DMA
  * media: rcar_jpu: Add missing clk_disable_

[Kernel-packages] [Bug 1795036] [NEW] iptables --list --numeric fails on -virtual kernel

[Scott Moser]

Public bug reported:

On a fresh instance of cosmic, run:

$ sudo iptables --list --numeric; echo $?
iptables: No chain/target/match by that name.
1

Expected result is something like:

$ iptables --list --numeric
Chain INPUT (policy ACCEPT)
target prot opt source   destination 

Chain FORWARD (policy ACCEPT)
target prot opt source   destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-7-generic 4.18.0-7.8
ProcVersionSignature: User Name 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Sep 28 16:47 seq
 crw-rw 1 root audio 116, 33 Sep 28 16:47 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Date: Fri Sep 28 16:48:51 2018
Ec2AMI: ami-018b
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: OpenStack Foundation OpenStack Nova
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-7-generic N/A
 linux-backports-modules-4.18.0-7-generic  N/A
 linux-firmwareN/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-bionic
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr17.0.4:cvnQEMU:ct1:cvrpc-i440fx-bionic:
dmi.product.family: Virtual Machine
dmi.product.name: OpenStack Nova
dmi.product.version: 17.0.4
dmi.sys.vendor: OpenStack Foundation

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


** Tags: amd64 apport-bug cosmic ec2-images

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

Title:
  iptables --list --numeric fails on -virtual kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh instance of cosmic, run:

  $ sudo iptables --list --numeric; echo $?
  iptables: No chain/target/match by that name.
  1

  Expected result is something like:

  $ iptables --list --numeric
  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain FORWARD (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  target prot opt source   destination

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: User Name 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 28 16:47 seq
   crw-rw 1 root audio 116, 33 Sep 28 16:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Sep 28 16:48:51 2018
  Ec2AMI: ami-018b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic

Re: [Kernel-packages] [Bug 1793584] Re: i2c_hid module randomly dies and needs to be restarted

[wmdiem]

Okay, I haven't yet lost the trackpad completely, but twice now tap to
click has stopped working. The first time I rebooted to make sure it had
actually been working under the test kernel (I was pretty sure it had, but
wanted to confirm). The second time I removed and reloaded the i2c_hid
module; tap to touch returned, but there now a visible jitter in moving the
cursor.

On Fri, Sep 28, 2018 at 11:47 AM William Diem  wrote:

> Okay, have installed the new kernel.
>
> 1) I got an error
> installing linux-headers-4.19.0-1-generic_4.19.0-1.2_elan+i2c_amd64.deb
> because of unmet dependency, but I installed with "--force-depends".
> 2) The log is still getting spammed with "incomplete report" errors.
> 3)  But the touchpad is working for the moment. It has only been up for a
> few minutes. I'll keep running it and see if it continues to work. And
> report back.
>
> On Fri, Sep 28, 2018 at 3:05 AM Kai-Heng Feng 
> wrote:
>
>> Ok, please try the kernel inside the link.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1793584
>>
>> Title:
>>   i2c_hid module randomly dies and needs to be restarted
>>
>> Status in linux package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   From 4.15.0-24 (not in 4.15.0-23) i2c_hid spams the log with messages
>>   like this:
>>
>>   [ 6079.727465] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete
>> report (14/65535)
>>   [ 6079.733692] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete
>> report (14/65535)
>>
>>   It then randomly stops working (and stops spamming the log), and there
>>   is no trackpad response until I reload the module.
>>
>>   Again, this was introduced in 4.15.0-24.
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793584/+subscriptions
>>
>

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

Title:
  i2c_hid module randomly dies and needs to be restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  From 4.15.0-24 (not in 4.15.0-23) i2c_hid spams the log with messages
  like this:

  [ 6079.727465] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete report 
(14/65535)
  [ 6079.733692] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete report 
(14/65535)

  It then randomly stops working (and stops spamming the log), and there
  is no trackpad response until I reload the module.

  Again, this was introduced in 4.15.0-24.

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

-- 
Mailing list: https://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 1793584] Re: i2c_hid module randomly dies and needs to be restarted

[wmdiem]

Okay, have installed the new kernel.

1) I got an error
installing linux-headers-4.19.0-1-generic_4.19.0-1.2_elan+i2c_amd64.deb
because of unmet dependency, but I installed with "--force-depends".
2) The log is still getting spammed with "incomplete report" errors.
3)  But the touchpad is working for the moment. It has only been up for a
few minutes. I'll keep running it and see if it continues to work. And
report back.

On Fri, Sep 28, 2018 at 3:05 AM Kai-Heng Feng 
wrote:

> Ok, please try the kernel inside the link.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1793584
>
> Title:
>   i2c_hid module randomly dies and needs to be restarted
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   From 4.15.0-24 (not in 4.15.0-23) i2c_hid spams the log with messages
>   like this:
>
>   [ 6079.727465] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete
> report (14/65535)
>   [ 6079.733692] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete
> report (14/65535)
>
>   It then randomly stops working (and stops spamming the log), and there
>   is no trackpad response until I reload the module.
>
>   Again, this was introduced in 4.15.0-24.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793584/+subscriptions
>

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

Title:
  i2c_hid module randomly dies and needs to be restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  From 4.15.0-24 (not in 4.15.0-23) i2c_hid spams the log with messages
  like this:

  [ 6079.727465] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete report 
(14/65535)
  [ 6079.733692] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete report 
(14/65535)

  It then randomly stops working (and stops spamming the log), and there
  is no trackpad response until I reload the module.

  Again, this was introduced in 4.15.0-24.

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

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

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Walter Lapchynski]

Also let's check Xubuntu and netboot, too. They both have i386 images.

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

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

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Walter Lapchynski]

I note the linked report is 32 bit as well. Can you confirm this does
NOT occur on a 64 bit machine? Be very careful if you're using a 64 bit
machine that it's more likely to not have an EHCI controller. Roughly
speaking, EHCI is 2.0-level USB while xHCI is 3.0 (UHCI being 1.0, which
requires some additional memory hardware to support 64 bit FWIW). Since
the errors relate to EHCI, this is going to be crucial. `lspci | grep
HCI` should help out in that regard. It also might be good to check a 32
bit kernel on a 64 bit machine if you can get that test out of the way.

It is possible this may affect other controller architectures, but I
doubt it. On the other hand, EHCI can handle 1.0 and 2.0 devices and
will likely downgrade a 3.0 device to 2.0 speeds. If it's possible,
checking all those different ones will likely prove helping in
understanding the scope of the problem.

** Tags removed: cosmic
** Tags added: lubuntu

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

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

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

[Kernel-packages] [Bug 1791664] Re: linux-azure: 4.18.0-1002.2 -proposed tracker

[Brad Figg]

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

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

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

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

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

** Description changed:

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1791663
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1794455] Re: linux-lts-trusty: 3.13.0-160.210~precise1 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-lts-trusty: 3.13.0-160.210~precise1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794454
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1794454] Re: linux: 3.13.0-160.210 -proposed tracker

[Kleber Sacilotto de Souza]

Verification tests completed for trusty-proposed.

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

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

Title:
  linux: 3.13.0-160.210 -proposed tracker

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

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

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

  backports: bug 1794455 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

[Alistair Sutter]

Is it ok if I do that with my current working kernel(4.18.0)?

The previous kernel (4.19.0-1.2) messed things up so bad that I had to
reinstall my working kernel (4.18.0) and Nvidia drivers in recovery mode
which took a lot of time.

Let me know if the debug output from (4.18.0) is enough or if you need
me to reinstall (4.19.0-1.2). I'd like to avoid (4.19.0-1.2) but I will
reinstall if you really need that output.

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

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

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: cosmic

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

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

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Walter Lapchynski]

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

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

** Bug watch added: Debian Bug tracker #908924
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908924

** Also affects: linux (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908924
   Importance: Unknown
   Status: Unknown

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

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

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

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

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

[Kernel-packages] [Bug 1795017] [NEW] linux-azure on cosmic minimal image boot speed

[Philip Roche]

Public bug reported:

Hi,

We're planning to share a new Cosmic minimal image for Azure including
the linux-azure custom kernel.

I have found boot speed increase from ~55s in non minimal image to over
6mins for minimal image.

I have gathered boot log, systemd logs and cloud-init logs for this
instance @ https://private-fileshare.canonical.com/~philroche/azure-
cosmic-20180927/minimal/. You can see the same logs for the non minimal
image @ https://private-fileshare.canonical.com/~philroche/azure-
cosmic-20180927/base

Most of the time seems to be spent in crng and "task swapper/0:1" (?)

[5.774760] sd 3:0:0:0: [sdc] Attached SCSI disk
[   71.388989] random: crng init done
[  242.656057] INFO: task swapper/0:1 blocked for more than 120 seconds.
[  242.688434]   Not tainted 4.15.0-1018-azure #18-Ubuntu

Source: https://private-fileshare.canonical.com/~philroche/azure-
cosmic-20180927/minimal/iengal3seeSee-vm-imagedebug-boot.log

Please let me know if you need any more information or would like me to
launch an instance for testing.


I understand that minimal images are intended to boot without initramfs but I 
did install initramfs-tools in another test image which did result in much 
better boot times.

See https://private-fileshare.canonical.com/~philroche/azure-
cosmic-20180928/ for logs.

Minimal image boot time 48.784s

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

** Attachment added: "cosmic minimal image with linux-azure boot log"
   
https://bugs.launchpad.net/bugs/1795017/+attachment/5194121/+files/iengal3seeSee-vm-imagedebug-boot.log

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

Title:
  linux-azure on cosmic minimal image boot speed

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Hi,

  We're planning to share a new Cosmic minimal image for Azure including
  the linux-azure custom kernel.

  I have found boot speed increase from ~55s in non minimal image to
  over 6mins for minimal image.

  I have gathered boot log, systemd logs and cloud-init logs for this
  instance @ https://private-fileshare.canonical.com/~philroche/azure-
  cosmic-20180927/minimal/. You can see the same logs for the non
  minimal image @ https://private-fileshare.canonical.com/~philroche
  /azure-cosmic-20180927/base

  Most of the time seems to be spent in crng and "task swapper/0:1" (?)

  [5.774760] sd 3:0:0:0: [sdc] Attached SCSI disk
  [   71.388989] random: crng init done
  [  242.656057] INFO: task swapper/0:1 blocked for more than 120 seconds.
  [  242.688434]   Not tainted 4.15.0-1018-azure #18-Ubuntu

  Source: https://private-fileshare.canonical.com/~philroche/azure-
  cosmic-20180927/minimal/iengal3seeSee-vm-imagedebug-boot.log

  Please let me know if you need any more information or would like me
  to launch an instance for testing.

  
  I understand that minimal images are intended to boot without initramfs but I 
did install initramfs-tools in another test image which did result in much 
better boot times.

  See https://private-fileshare.canonical.com/~philroche/azure-
  cosmic-20180928/ for logs.

  Minimal image boot time 48.784s

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

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

[Kernel-packages] [Bug 1794922] [NEW] lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

-- Background --
Testing the x86 (32bit) ISO image on various machines.

After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 & hp
dx6120), however

-- Issue --

dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.

switching to messages, it's just the following repeating

// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 of 
device mask "

// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 of 
device mask "

NOTE:  I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've manually
typed it; so typo's could have been made.

A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -

---
 guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
 seems like it's a usb issue of some kind with 4.18
---

This fits because whilst I do my testing mostly on d610 & t43 (no issues
today), I'd tested Lubuntu 18.10 before on the dell 755 with no issues.
My last test was also long enough ago to be on 4.17 kernel.

I'll add `lshw` files for the two failed systems

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


** Tags: iso-testing
-- 
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7: 
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask " 
repeats
https://bugs.launchpad.net/bugs/1794922
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 1794431] Re: linux-azure: 4.15.0-1025.26 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux-azure: 4.15.0-1025.26 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1794454] Re: linux: 3.13.0-160.210 -proposed tracker

[Brad Figg]

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

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

Title:
  linux: 3.13.0-160.210 -proposed tracker

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

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

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

  backports: bug 1794455 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1794444] Re: linux: 4.4.0-137.163 -proposed tracker

[Taihsiang Ho]

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

** Tags added: certification-testing-passed

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

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

Title:
  linux: 4.4.0-137.163 -proposed tracker

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

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

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

  backports: bug 1794445 (linux-aws), bug 1794446 (linux-lts-xenial)
  derivatives: bug 1794447 (linux-aws), bug 1794448 (linux-euclid), bug 1794449 
(linux-kvm), bug 1794452 (linux-raspi2), bug 1794453 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1763323] Re: ubuntu_fan_smoke_test failed on 4.4/4.15 kvm & azure kernel

[Sean Feole]

** Summary changed:

- ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel
+ ubuntu_fan_smoke_test failed on 4.4/4.15 kvm & azure kernel

** Tags added: azure

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

Title:
  ubuntu_fan_smoke_test failed on 4.4/4.15 kvm & azure kernel

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in linux-kvm source package in Xenial:
  New

Bug description:
  The "enable disable fan test" will fail with Xenial KVM kernel

  Error message:
RTNETLINK answers: Operation not supported
/usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev ens4 dstport 
0 local 10.246.72.56 fan-map 250.0.0.0/8:10.246.0.0/16
/usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation
RTNETLINK answers: Cannot assign requested address
iptables v1.6.0: Couldn't load target `fan-egress':No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
/usr/sbin/fanatic: unable to bring fan up, unable to configure

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26
  ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117
  Uname: Linux 4.4.0-1021-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 12 10:22:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1794428] Re: linux-oem: 4.15.0-1021.24 -proposed tracker

[Taihsiang Ho]

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-oem: 4.15.0-1021.24 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Sean Feole]

Still valid for azure : 4.15.0-1008.8 / Bionic ,

http://10.246.72.46/4.15.0-1016.16-azure/bionic-linux-azure-
azure-4.15.0-Standard_D32_v3-monotonic_time/monotonic_time/results/monotonic_time.tsc/debug/monotonic_time.tsc.DEBUG.html

** Tags added: azure

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

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

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Kernel-packages] [Bug 1794454] Re: linux: 3.13.0-160.210 -proposed tracker

[Taihsiang Ho]

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

** Tags added: certification-testing-passed

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

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

Title:
  linux: 3.13.0-160.210 -proposed tracker

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

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

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

  backports: bug 1794455 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

[Guilherme G. Piccoli]

Hi Mao, I see...the partner is not using a regular Ubuntu build.
This patch was introduced upstream in kernel 4.17, so it's not present in a 
regular 4.15 or 4.16. It is present in our Ubuntu kernel though, because it was 
backported and added, but I can't guarantee it's present in the custom kernels 
the partner is using.

Some alternatives for us to resolve this issue:

a) If I could access the source tree of the partner kernel, I can check
and even add myself the patch in case it's not there;

b) The partner could test Ubuntu official kernel 4.15.0-34;

c) The partner could test upstream kernel 4.17 (or 4.18).

Preference is alternative (b), but (c) is ok too. The first alternative is the 
least preferred.
Cheers,


Guilherme

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

Title:
  nvme name floated after boot with 4.15.0 kernel

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

Bug description:
  nvme device name such as /dev/nvme?n?p? would be floated that is
  symbol link to different real ssd device after reboot in 4.15.0 kernel
  for 16.04.5 HWE and 18.04 GA-kernel. This are not found on 16.04.5 GA-
  kernel ( 4.4.0)

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

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

[Kernel-packages] [Bug 1791377] Re: linux-azure: 4.18.0-1001.1 -proposed tracker

[Marcelo Cerri]

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

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the 4.18.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

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

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

[Kernel-packages] [Bug 1794426] Re: linux: 4.15.0-36.39 -proposed tracker

[Taihsiang Ho]

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

** Tags added: certification-testing-passed

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

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

Title:
  linux: 4.15.0-36.39 -proposed tracker

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

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

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

  backports: bug 1794435 (linux-azure), bug 1794436 (linux-azure), bug 1794438 
(linux-azure-edge), bug 1794439 (linux-gcp), bug 1794441 (linux-hwe), bug 
1794442 (linux-hwe-edge)
  derivatives: bug 1794427 (linux-raspi2), bug 1794428 (linux-oem), bug 1794430 
(linux-aws), bug 1794431 (linux-azure), bug 1794432 (linux-gcp), bug 1794433 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

[Cyril Soler]

Same for me: ubuntu 18.04 just installed on Dell Precision M3800.

Before I was on 16.04 and CPU temp during normal session was about 47-55
deg.

Now, it's constantly at 63-80 deg.

I tried lots of tweaks (install thermald, tlp, cpufreq-selector, etc).
Nothing worked until now. I'm seriously considering to go back to 16.04,
or switch to anything else that would not slowly kill  my hardware.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.versi

[Kernel-packages] [Bug 1794346] Re: check and fix zkey required kernel modules locations in debs, udebs, and initramfs

[Dimitri John Ledkov]

linux-modules-4.18.0-8-generic has:
./lib/modules/4.18.0-8-generic/kernel/arch/s390/crypto/paes_s390.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/pkey.ko   
 
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt.ko 
 
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex2a.ko   
 
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex4.ko
 
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_pcixcc.ko

All of the above appear to be missing from the crypto-modules-4.18.0-8
-generic-di, please ship them in crypto-modules udeb.

To avoid discrepancies as to what crypto is supported by the installed
system, versus d-i environment, it would be nice to make udebs and
linux-modules packages roughly the same.

Does it at all make sense to ship matching set of
kernel/{arch,drivers}/s390/crypto/*.ko in crypto-modules udeb, as
shilled in linux-modules deb?

** Description changed:

- for zkey feature, check that all the required modules are in -image
- package, not extras.
+ todo: check that these modules are included in the initramfs as well.
  
- check that these are also shipped in udebs (probably like crypto-modules
- udeb and/or disk drivers).
+ === linux crypto-modules udeb task ==
+ linux-modules-4.18.0-8-generic has:
+ ./lib/modules/4.18.0-8-generic/kernel/arch/s390/crypto/paes_s390.ko
+ ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/pkey.ko
+ ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt.ko
+ ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex2a.ko
+ ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex4.ko
+ ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_pcixcc.ko
  
- check that these modules are included in the initramfs as well.
+ All of the above appear to be missing from the crypto-modules-4.18.0-8
+ -generic-di, please ship them in crypto-modules udeb.
+ 
+ To avoid discrepancies as to what crypto is supported by the installed
+ system, versus d-i environment, it would be nice to make udebs and
+ linux-modules packages roughly the same.
+ 
+ Does it at all make sense to ship matching set of 
kernel/{arch,drivers}/s390/crypto/*.ko in crypto-modules udeb, as shilled in 
linux-modules deb?
+ ===

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

Title:
  check and fix zkey required kernel modules locations in debs, udebs,
  and initramfs

Status in linux package in Ubuntu:
  Triaged

Bug description:
  todo: check that these modules are included in the initramfs as well.

  === linux crypto-modules udeb task ==
  linux-modules-4.18.0-8-generic has:
  ./lib/modules/4.18.0-8-generic/kernel/arch/s390/crypto/paes_s390.ko
  ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/pkey.ko
  ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt.ko
  ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex2a.ko
  ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex4.ko
  ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_pcixcc.ko

  All of the above appear to be missing from the crypto-modules-4.18.0-8
  -generic-di, please ship them in crypto-modules udeb.

  To avoid discrepancies as to what crypto is supported by the installed
  system, versus d-i environment, it would be nice to make udebs and
  linux-modules packages roughly the same.

  Does it at all make sense to ship matching set of 
kernel/{arch,drivers}/s390/crypto/*.ko in crypto-modules udeb, as shilled in 
linux-modules deb?
  ===

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

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

[Kernel-packages] [Bug 1793369] Re: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc/sysrq-trigger

[Dimitri John Ledkov]

The default sysctl setting for kernel.sysrq in Ubuntu is 176 (and was in
bionic and xenial) and it is shipped in /etc/sysctl.d/10-magic-
sysrq.conf file. This file is provided by a required package from the
minimal task, called `procps`.

176 enables:
128 - allow reboot/poweroff
32 - enable remount read-only
16 - enable sync command

Do you have `procps` package installed on your system?

Is anything else overriding that setting?

If that setting is not suitable for you, I recommend to either modify
/etc/sysctl.d/10-magic-sysrq.conf or to add another .conf drop in, with
a higher number in /etc/sysctl.d directory to suit your system better.

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

Title:
  Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc
  /sysrq-trigger

Status in The Ubuntu-power-systems project:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2018-09-19 
04:49:39 ==
  ---Problem Description---
   [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] : Sysrq trigger disabled 
when writing to /proc/sysrq-trigger 

  while  testing kdump trying trigger kdump panic via /proc/sysrq-trigger it 
failed as : SysRq : This sysrq operation is disabled
  LOG:

  root@test:~# cat /proc/sys/kernel/sysrq 
  176
  root@test:~# echo c > /proc/sysrq-trigger
  root@test:~# dmesg
  [  380.340051] mlx5_core :01:00.1 enp1s0f1: Self test out: status 
flags(0x2)
  [  389.404239] sysrq: SysRq : This sysrq operation is disabled.
  root@test~# cat /boot/config-4.18.0-7-generic | grep CONFIG_MAGIC_SYSRQ
  CONFIG_MAGIC_SYSRQ=y
  CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6
  CONFIG_MAGIC_SYSRQ_SERIAL=y
  root@test:~# cat /etc/sysctl.conf | grep kernel.sysrq
  #kernel.sysrq=438
  root@test:~# 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.18.0-7-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.18.0-7-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=c0302064-c5a3-49a7-8bd4-402283e6fcbe ro quiet splash 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@test:~# 

  Regards
  Praveen

  == Comment: #2 - Praveen K. Pandey  - 2018-09-19 
05:16:11 ==
  when i enable  in /etc/sysctl.conf it works  . i append below value in  
sysctl.conf

  echo "kernel.sysrq = 1" >> /etc/sysctl.conf

  I think this is should be enable by default  in ubuntu 18.10 as
  earlier ubuntu distro it has , not sure why it got removed as kdump
  mechanism require this .

  Praveen
  Regards

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

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

[Kernel-packages] [Bug 1792957] Re: Provide mode where all vCPUs on a core must be the same VM

[Breno Leitão]

Hi Joseph,

> I built a test kernel with the requested commit.
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1792957
> 
> Can you test this kernel and see if it resolves this bug?

I tested this kernel in the following scenarios:

 - Booted the host on a P9 machine and started an 18.04 guest using the default 
parameters.
 - Removed the kvm_hv module and reinstalled it using the 'one_vm_per_core' 
parameter, shut down the 18.04 guest and restarted it.

➜  ~ sudo virsh destroy breno-1804
➜  ~ sudo rmmod kvm_hv
➜  ~ sudo modprobe kvm_hv one_vm_per_core=1
➜  ~ sudo virsh start --console breno-1804

On both guests I ran sysbench, as:

breno@ubuntu:~$ sysbench  --threads=16 cpu run
sysbench 1.0.11 (using system LuaJIT 2.1.0-beta3)

Running the test with following options:

breno@ubuntu:~$ sysbench  --threads=16 cpu run
   Number of threads: 16
   Initializing random number generator from current time
   Prime numbers limit: 1
   Initializing worker threads...
   Threads started!

   CPU speed:
   events per second: 33648.49
   . 

Everything worked fine. I think this patch is good to get accepted.

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

Title:
  Provide mode where all vCPUs on a core must be the same VM

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

Bug description:
  == Comment: #0 - Leonardo Augusto Guimaraes Garcia  - 
2018-09-13 07:12:48 ==
  +++ This bug was initially created as a clone of Bug #171443 +++

  Please, add the following patch:

  http://patchwork.ozlabs.org/patch/968786/

  which adds a mode where all vCPUs on a core must be the same VM on
  POWER8 and POWER9.

  This is intended for use in security-conscious settings where users
  are concerned about possible side-channel attacks between threads
  which could perhaps enable one VM to attack another VM on the same
  core, or the host.

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

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

[Kernel-packages] [Bug 1778844] Re: nvme multipath does not report path relationships

[Thadeu Lima de Souza Cascardo]

Just create a /etc/modprobe.d/nvme.conf file with the following
contents, recreate initrd, remove kdump initrds so they are recreated in
the next boot, then reboot.

# cat /etc/modprobe.d/nvme.conf
options nvme-core multipath=0
# update-initramfs -u
# rm /var/lib/kdump/initrd.img*
# reboot

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Invalid

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  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.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24

[Kernel-packages] [Bug 1788817] Re: BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:1:1119]

[Juerg Haefliger]

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

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

Title:
  BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:1:1119]

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  == SRU Justification ==

  Booting Trusty with kernel 3.13.0-156-generic on a fairly new Intel
  box results in stuck CPU warnings:

  [   33.551942] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:1:1119]
  [   33.558560] Modules linked in: hid_generic ast(+) crct10dif_pclmul 
syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel sysimgblt aesni_intel 
i2c_algo_bit aes_x86_64 lrw ttm gf128mul glue_helper drm_kms_helper ablk_helper 
usbhid cryptd ahci drm hid libahci wmi
  [   33.583971] CPU: 0 PID: 1119 Comm: kworker/0:1 Not tainted 
3.13.0-156-generic #206-Ubuntu
  [   33.592270] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS 
SE5C620.86B.01.00.0294.101220161543 10/12/2016
  [   33.602836] Workqueue: events work_for_cpu_fn
  [   33.607351] task: 88084ddbc6b0 ti: 88084dd98000 task.ti: 
88084dd98000
  [   33.614957] RIP: 0010:[]  [] 
ioread32+0x42/0x50
  [   33.622805] RSP: 0018:88084dd99d18  EFLAGS: 0292
  [   33.628201] RAX:  RBX: 880851265000 RCX: 
28a6
  [   33.635429] RDX: c90016bd RSI: c90016bd RDI: 
c90016bd
  [   33.642653] RBP: 88084dd99d40 R08: 0092 R09: 
079e
  [   33.649877] R10: 813df570 R11: 88084dd99a46 R12: 
16bc
  [   33.657104] R13: a01b2ab0 R14: 88084dd99cc8 R15: 

  [   33.664329] FS:  () GS:88085f20() 
knlGS:
  [   33.672541] CS:  0010 DS:  ES:  CR0: 80050033
  [   33.678380] CR2: 7f3613be4000 CR3: 01c0e000 CR4: 
00360770
  [   33.685605] DR0:  DR1:  DR2: 

  [   33.692829] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   33.700052] Stack:
  [   33.702150]  a01a89e0 880851265000  

  [   33.709948]  a01b4100 88084dd99d68 a0073e88 
880851265000
  [   33.717751]  880850dee000 880850dee098 88084dd99db8 
a0075d92
  [   33.725550] Call Trace:
  [   33.728085]  [] ? ast_driver_load+0x320/0x540 [ast]
  [   33.734634]  [] drm_dev_register+0xa8/0x1f0 [drm]
  [   33.741000]  [] drm_get_pci_dev+0x92/0x140 [drm]
  [   33.747268]  [] ast_pci_probe+0x15/0x20 [ast]
  [   33.753282]  [] local_pci_probe+0x4a/0xb0
  [   33.758947]  [] work_for_cpu_fn+0x1a/0x30
  [   33.764613]  [] process_one_work+0x17e/0x480
  [   33.770536]  [] worker_thread+0x29b/0x410
  [   33.776205]  [] ? rescuer_thread+0x430/0x430
  [   33.782130]  [] kthread+0xcb/0xf0
  [   33.787101]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [   33.793721]  [] ret_from_fork+0x6e/0xa0
  [   33.799211]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [   33.805828] Code: 66 0f 1f 84 00 00 00 00 00 55 48 c7 c6 80 57 a9 81 48 89 
e5 e8 f0 fe ff ff b8 ff ff ff ff 5d c3 66 0f 1f 84 00 00 00 00 00 8b 07  66 
66 66 66 2e 0f 1f 84 00 00 00 00 00 48 81 fe ff ff 03 00

  == Fix ==

  Backport commit 6c971c09f387 ("drm/ast: Fixed system hanged if disable
  P2A")

  
  == Regression Potential ==

  Low. The patch only touches the ast driver and the modifications are
  fairly small. The patch is also in Xenial (via a stable upstream
  update) and received testing there.

  == Test Case ==

  Booted a patched kernel on HW to verify it comes up without stuck CPU
  warnings.

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

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

[Kernel-packages] [Bug 1767706] Re: Ubuntu 18.04 no guest session

[Michel-Ekimia]

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

** Also affects: gdm3 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Summary changed:

- Ubuntu 18.04 no guest session
+ Ubuntu 18.04 no guest session available in gdm

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

Title:
  Ubuntu 18.04 no guest session available in gdm

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04 no option to switch to a guest session.
  Regression against 16.04 LTS.
  Usecase: let someone try Ubuntu, when giving a presentation

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

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

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume

[Kai-Heng Feng]

When the bug is triggered.

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

Title:
  Bluetooth (btintel) stops working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run cosmic on my Dell Latitude E7470, which has an intel usb
  bluetooth device (8087:0a2b).

  Sometimes (not every time) after a suspend/resume cycle, my laptop's
  bluetooth stops working.  hciconfig shows:

  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

  and dmesg tells me (various combinations of):

  [237660.728312] Bluetooth: hci0: command tx timeout
  [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
  [237925.202500] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  
  Trying to reinitialize the device by reloading the driver has no effect:

  ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe
  btusb

  shows in dmesg:

  [237938.219190] usbcore: deregistering interface driver btusb
  [237938.601731] usbcore: registered new interface driver btusb
  [237940.626392] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [237940.626426] Bluetooth: hci0: command tx timeout

  Strangely enough, reloading the module sometimes does work, upon which the 
kernel tells me :
  aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 
2 week 52 2014
  aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download 
to complete
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 
usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-11-5.ddc
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters 
completed

  
  Looking further back in the kernel log, the difference between failed and 
successful resumes seems to be this:

  Resume with broken bt:
  [236481.370814] Restarting tasks ... 
  [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)

  Resume with working bt:
  [16562.706263] Restarting tasks ... 
  [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [16562.716050] Bluetooth: hci0: Device revision is 5
  [16562.716052] Bluetooth: hci0: Secure boot is enabled
  [16562.716053] Bluetooth: hci0: OTP lock is enabled
  [16562.716054] Bluetooth: hci0: API lock is enabled
  [16562.716055] Bluetooth: hci0: Debug lock is disabled
  [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
  [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
  [16564.203091] Bluetooth: hci0: Waiting for device to boot
  [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
  [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
  [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed

  
  and everything works fine after that.


  The first kernel on which this error occurred was 4.17.0-6-generic.  Before 
that, I used 4.15.0-25-generic which works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bas4871 F...m pulseaudio
   /dev/snd/controlC0:  bas4871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice:
   RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93
   #RESUME=/dev/dm-2
   #RESUME=/dev/mapper/regan-swap
  InstallationDate: Installed on 2016-12-22 (619 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Latitude E7470
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.17.0-7-generi

[Kernel-packages] [Bug 1787904] Re: [radeon] machine crash after GPU reset

[Christoph Löhr]

[Fri Sep 28 00:06:28 2018] radeon :01:00.0: ring 0 stalled for more than 
10248msec
[Fri Sep 28 00:06:28 2018] radeon :01:00.0: GPU lockup (current fence id 
0x00404e50 last fence id 0x00404edc on ring 0)
[Fri Sep 28 00:06:28 2018] radeon :01:00.0: ring 3 stalled for more than 
10204msec
[Fri Sep 28 00:06:28 2018] radeon :01:00.0: GPU lockup (current fence id 
0x00b9d1c3 last fence id 0x00b9d21e on ring 3)
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: Saved 8932 dwords of commands 
on ring 0.
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: GPU softreset: 0x004C
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   GRBM_STATUS   = 
0xA0003028
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   GRBM_STATUS_SE0   = 
0x0006
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   GRBM_STATUS_SE1   = 
0x0006
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   SRBM_STATUS   = 
0x2AC0
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   SRBM_STATUS2  = 
0x
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 
0x2000
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 
0x
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 
0x0042
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_008680_CP_STAT  = 
0x8C028647
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 
0x44C83146
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_00D834_DMA_STATUS_REG   = 
0x44C83D57
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: GRBM_SOFT_RESET=0xDDFF
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: SRBM_SOFT_RESET=0x00100100
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   GRBM_STATUS   = 
0x3028
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   GRBM_STATUS_SE0   = 
0x0006
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   GRBM_STATUS_SE1   = 
0x0006
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   SRBM_STATUS   = 
0x20C0
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   SRBM_STATUS2  = 
0x
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 
0x
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 
0x
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 
0x
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_008680_CP_STAT  = 
0x
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 
0x44C83D57
[Fri Sep 28 00:06:29 2018] radeon :01:00.0:   R_00D834_DMA_STATUS_REG   = 
0x44C83D57
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: GPU reset succeeded, trying to 
resume
[Fri Sep 28 00:06:29 2018] [drm] probing gen 2 caps for device 8086:1901 = 
261ad03/e
[Fri Sep 28 00:06:29 2018] [drm] PCIE gen 3 link speeds already enabled
[Fri Sep 28 00:06:29 2018] [drm] PCIE GART of 2048M enabled (table at 
0x001D6000).
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: WB enabled
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: fence driver on ring 0 use gpu 
addr 0x8c00 and cpu addr 0x70214f68
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: fence driver on ring 1 use gpu 
addr 0x8c04 and cpu addr 0xb5b3fa4b
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: fence driver on ring 2 use gpu 
addr 0x8c08 and cpu addr 0x552c5fb0
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: fence driver on ring 3 use gpu 
addr 0x8c0c and cpu addr 0xec35d8ef
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: fence driver on ring 4 use gpu 
addr 0x8c10 and cpu addr 0x2cca1ee6
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: fence driver on ring 5 use gpu 
addr 0x00075a18 and cpu addr 0xf6c849cc
[Fri Sep 28 00:06:29 2018] radeon :01:00.0: failed VCE resume (-22).
[Fri Sep 28 00:06:30 2018] [drm] ring test on 0 succeeded in 2 usecs
[Fri Sep 28 00:06:30 2018] [drm] ring test on 1 succeeded in 1 usecs
[Fri Sep 28 00:06:30 2018] [drm] ring test on 2 succeeded in 1 usecs
[Fri Sep 28 00:06:30 2018] [drm] ring test on 3 succeeded in 9 usecs
[Fri Sep 28 00:06:30 2018] [drm] ring test on 4 succeeded in 3 usecs
[Fri Sep 28 00:06:30 2018] [drm] ring test on 5 succeeded in 2 usecs
[Fri Sep 28 00:06:30 2018] [drm] UVD initialized successfully.
[Fri Sep 28 00:06:30 2018] [drm:si_dpm_set_power_state [radeon]] *ERROR* 
si_set_sw_state failed
[Fri Sep 28 00:06:31 2018] [drm:r600_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
[Fri Sep 28 00:06:31 2018] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB 

[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

[Romano Asciutto]

Sorry, I forgot to attach the output of `udevadm info -e`. Here is the
result for my Dell Inspiron 15 7559

** Attachment added: "`udevadm info -e` for Dell Inspiron 15 7559"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+attachment/5193975/+files/info.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/1784152

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume

[Bas Zoetekouw]

Do you need a dmesg when the bug is triggered, or does a regular boot
log suffice?   It's hard to trigger the bug manually (but it occurs
every couple of days).

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

Title:
  Bluetooth (btintel) stops working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run cosmic on my Dell Latitude E7470, which has an intel usb
  bluetooth device (8087:0a2b).

  Sometimes (not every time) after a suspend/resume cycle, my laptop's
  bluetooth stops working.  hciconfig shows:

  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

  and dmesg tells me (various combinations of):

  [237660.728312] Bluetooth: hci0: command tx timeout
  [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
  [237925.202500] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  
  Trying to reinitialize the device by reloading the driver has no effect:

  ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe
  btusb

  shows in dmesg:

  [237938.219190] usbcore: deregistering interface driver btusb
  [237938.601731] usbcore: registered new interface driver btusb
  [237940.626392] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [237940.626426] Bluetooth: hci0: command tx timeout

  Strangely enough, reloading the module sometimes does work, upon which the 
kernel tells me :
  aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 
2 week 52 2014
  aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download 
to complete
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 
usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-11-5.ddc
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters 
completed

  
  Looking further back in the kernel log, the difference between failed and 
successful resumes seems to be this:

  Resume with broken bt:
  [236481.370814] Restarting tasks ... 
  [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)

  Resume with working bt:
  [16562.706263] Restarting tasks ... 
  [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [16562.716050] Bluetooth: hci0: Device revision is 5
  [16562.716052] Bluetooth: hci0: Secure boot is enabled
  [16562.716053] Bluetooth: hci0: OTP lock is enabled
  [16562.716054] Bluetooth: hci0: API lock is enabled
  [16562.716055] Bluetooth: hci0: Debug lock is disabled
  [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
  [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
  [16564.203091] Bluetooth: hci0: Waiting for device to boot
  [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
  [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
  [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed

  
  and everything works fine after that.


  The first kernel on which this error occurred was 4.17.0-6-generic.  Before 
that, I used 4.15.0-25-generic which works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bas4871 F...m pulseaudio
   /dev/snd/controlC0:  bas4871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice:
   RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93
   #RESUME=/dev/dm-2
   #RESUME=/dev/mapper/regan-swap
  InstallationDate: Installed on 2016-12-22 (619 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Del

[Kernel-packages] [Bug 1794847] Re: Installing proprietary drivers causes font glitches

[fcole90]

I fixed the issue deleting some fontconfig configurations in my home
folder. I don't really know how this caused the issue, and how the files
were created in first place.

Use with caution:

rm -rf ~/.local/share/fontconfig ~/.fonts.conf.d ~/.fonts.conf

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Invalid

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

Title:
  Installing proprietary drivers causes font glitches

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  I recently enabled the nvidia proprietary drivers and since then I'm
  experiencing font glitches which are making it difficult for me to
  read the text.

  The glitch consist in slight "shadow" lines on the right or left of a
  letter, in red or green.

  I recently also installed wine and wine-staging, with their
  recommended packages.

  My graphic card is an optimus one, so I have both an nvidia and Intel
  card. Unfortunately when I try to switch back to the Intel card, the
  nouveau drivers are loaded instead, so I cannot test if reverting to
  Intel can solve the glitch.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 27 20:30:28 2018
  InstallationDate: Installed on 2017-08-21 (402 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1794847/+subscriptions

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

[Kernel-packages] [Bug 1788321] Re: swapon failed: invalid argument

[Lutz Schwarz]

I am running

Linux 4.4.0-135-generic #161~14.04.1-Ubuntu SMP Tue Aug 28 11:19:03 UTC
2018 GNU/Linux

as a virtual machine in VMWare and got the same problem with swapon.

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

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

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

[Kernel-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

[Timo Aaltonen]

and again comparing to Debian, it doesn't have efifb messing around at
any stage, though it's enabled in the kernel config

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  New
Status in gdm3 source package in Cosmic:
  Won't Fix
Status in kmod source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in xorg source package in Cosmic:
  New

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty

  When this issue happens there is a plymouth crash reported in bug
  1794292


  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

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

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

[Kernel-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

[Timo Aaltonen]

and compared to Debian, our kernel doesn't seem to enable bochs-drm
because of an old bug

https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

which probably should be re-enabled by now

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

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

** Also affects: kmod (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  New
Status in gdm3 source package in Cosmic:
  Won't Fix
Status in kmod source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in xorg source package in Cosmic:
  New

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty

  When this issue happens there is a plymouth crash reported in bug
  1794292


  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

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

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

[Kernel-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

[Timo Aaltonen]

while enabling bochs-drm just works around the actual bug, I think it's
best for cosmic at this stage

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  New
Status in gdm3 source package in Cosmic:
  Won't Fix
Status in kmod source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in xorg source package in Cosmic:
  New

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty

  When this issue happens there is a plymouth crash reported in bug
  1794292


  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

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

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

[Kernel-packages] [Bug 1794387] Re: Colour banding in HP Pavilion 15-n233sl integrated display

[Kai-Heng Feng]

Please try this kernel:
https://people.canonical.com/~khfeng/lp1794387/

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

Title:
  Colour banding in HP Pavilion 15-n233sl integrated display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Colour bandind is visible everywhere in the system, and it appeared
  after I had my integrated monitor replaced. I believe it's not a
  hardware problem, since booting with 'nomodeset' works as expected.

  There were already two similar bugs,
  https://bugs.launchpad.net/bugs/1749420 and
  https://bugs.launchpad.net/bugs/1788308, but the fixes provided for
  those bugs did not work for my specific monitor.

  I'm running Ubuntu 18.04 with kernel linux-image-4.15.0-34-generic,
  installing linux-image-4.18.8 with UKUU didn't help.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  sudo get-edid | edid-decode in a file named edid-decoded.txt
  cat /proc/version_signature in version.log
  sudo lspci -vnvn in lspci-vnvn.log.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   1796 F pulseaudio
   /dev/snd/controlC1:  matt   1796 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2018-09-27 (0 days ago)
  InstallationMedia: neon devunstable "Bionic" - Build amd64 LIVE Binary 
20180924-13:08
  Lsusb:
   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 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=c3f61207-d13e-474b-a499-98030ddef8e1 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UnreportableReason: Questa segnalazione riguarda un pacchetto che non è 
installato.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 03/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.71
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2166
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.71:bd03/13/2017:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1782934] Re: XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic

[Christopher Torgalson]

It was still happening on 4.19-rc1. I'll test on later 4.19 rcs over the
weekend.

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

Title:
  XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu
  Budgie), the graphical installer works correctly, but on every post-
  install login, the screen goes black at the disk decryption screen.

  The kernel version post-install is 4.14.0-29-generic (edited to add:
  this SHOULD have read '4.15.0-29-generic').

  Other things seem to be working. If I'm careful, I can enter the disk
  decryption password and tell (via sounds) that I've gotten through to
  the login screen, but the screen remains dark.

  This happens with standard or minimal installs.

  If I then try to boot with the previous kernel--4.15.0-20-generic--
  everything works flawlessly.

  The only non-standard thing about this system is that I replaced the
  onboard wireless card with an Intel Dual Band Wireless-AC 8625.

  ---

  I don't have a clue about kernel debugging, but I can provide further
  system info as needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jul 21 20:35:45 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Iris Graphics 540 [1028:0704]
  InstallationDate: Installed on 2018-07-21 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

[Kai-Heng Feng]

Because I only added ID for Ascaris's device.

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume

[Kai-Heng Feng]

Can you attach full dmesg with `usbcore.dyndbg=+p`?

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

Title:
  Bluetooth (btintel) stops working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run cosmic on my Dell Latitude E7470, which has an intel usb
  bluetooth device (8087:0a2b).

  Sometimes (not every time) after a suspend/resume cycle, my laptop's
  bluetooth stops working.  hciconfig shows:

  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

  and dmesg tells me (various combinations of):

  [237660.728312] Bluetooth: hci0: command tx timeout
  [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
  [237925.202500] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  
  Trying to reinitialize the device by reloading the driver has no effect:

  ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe
  btusb

  shows in dmesg:

  [237938.219190] usbcore: deregistering interface driver btusb
  [237938.601731] usbcore: registered new interface driver btusb
  [237940.626392] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [237940.626426] Bluetooth: hci0: command tx timeout

  Strangely enough, reloading the module sometimes does work, upon which the 
kernel tells me :
  aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 
2 week 52 2014
  aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download 
to complete
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 
usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-11-5.ddc
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters 
completed

  
  Looking further back in the kernel log, the difference between failed and 
successful resumes seems to be this:

  Resume with broken bt:
  [236481.370814] Restarting tasks ... 
  [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)

  Resume with working bt:
  [16562.706263] Restarting tasks ... 
  [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [16562.716050] Bluetooth: hci0: Device revision is 5
  [16562.716052] Bluetooth: hci0: Secure boot is enabled
  [16562.716053] Bluetooth: hci0: OTP lock is enabled
  [16562.716054] Bluetooth: hci0: API lock is enabled
  [16562.716055] Bluetooth: hci0: Debug lock is disabled
  [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
  [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
  [16564.203091] Bluetooth: hci0: Waiting for device to boot
  [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
  [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
  [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed

  
  and everything works fine after that.


  The first kernel on which this error occurred was 4.17.0-6-generic.  Before 
that, I used 4.15.0-25-generic which works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bas4871 F...m pulseaudio
   /dev/snd/controlC0:  bas4871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice:
   RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93
   #RESUME=/dev/dm-2
   #RESUME=/dev/mapper/regan-swap
  InstallationDate: Installed on 2016-12-22 (619 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Latitude E7470
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE

[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

[Romano Asciutto]

I have installed your kernel build and removed all kernel parameters but
it unfortunately didn't fix the issue.

'uname -a'
Linux Kubuntu 4.19.0-1-generic #2~elan+i2c SMP Fri Sep 28 04:25:10 CST 2018 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working aster suspend/resume

[Bas Zoetekouw]

I can confirm that the bug still occurs in 4.19.0-041900rc5-generic.

The first kernel on which this error occurred was 4.17.0-6-generic.
Before that, I used 4.15.0-25-generic which works perfectly.

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

** Tags added: kernel-bug-exists-upstream

** Summary changed:

- Bluetooth (btintel) stops working aster suspend/resume
+ Bluetooth (btintel) stops working after suspend/resume

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

Title:
  Bluetooth (btintel) stops working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run cosmic on my Dell Latitude E7470, which has an intel usb
  bluetooth device (8087:0a2b).

  Sometimes (not every time) after a suspend/resume cycle, my laptop's
  bluetooth stops working.  hciconfig shows:

  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

  and dmesg tells me (various combinations of):

  [237660.728312] Bluetooth: hci0: command tx timeout
  [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
  [237925.202500] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  
  Trying to reinitialize the device by reloading the driver has no effect:

  ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe
  btusb

  shows in dmesg:

  [237938.219190] usbcore: deregistering interface driver btusb
  [237938.601731] usbcore: registered new interface driver btusb
  [237940.626392] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [237940.626426] Bluetooth: hci0: command tx timeout

  Strangely enough, reloading the module sometimes does work, upon which the 
kernel tells me :
  aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 
2 week 52 2014
  aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download 
to complete
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 
usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-11-5.ddc
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters 
completed

  
  Looking further back in the kernel log, the difference between failed and 
successful resumes seems to be this:

  Resume with broken bt:
  [236481.370814] Restarting tasks ... 
  [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)

  Resume with working bt:
  [16562.706263] Restarting tasks ... 
  [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [16562.716050] Bluetooth: hci0: Device revision is 5
  [16562.716052] Bluetooth: hci0: Secure boot is enabled
  [16562.716053] Bluetooth: hci0: OTP lock is enabled
  [16562.716054] Bluetooth: hci0: API lock is enabled
  [16562.716055] Bluetooth: hci0: Debug lock is disabled
  [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
  [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
  [16564.203091] Bluetooth: hci0: Waiting for device to boot
  [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
  [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
  [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed

  
  and everything works fine after that.


  The first kernel on which this error occurred was 4.17.0-6-generic.  Before 
that, I used 4.15.0-25-generic which works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bas4871 F...m pulseaudio
   /dev/snd/controlC0:  bas4871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 1

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume

[Bas Zoetekouw]

Adding to that, there is a (somewhat) reliable way to get bluetooth back.  It 
involves goign to the following process _twice_: stopping the bluetooth 
service, unloading all relevant modules, suspending the laptop, resuming, 
reloading all modules, starting the bluetooth service.
Rather cumbersome, but it might help other experiencing this issue.

I use the following script for "convenience" (en remeber to run it twice
to get bt back):

#!/bin/bash
if [[ $EUID -ne 0 ]]; then
exec /usr/bin/sudo $0
fi
modules=(btusb btintel btbcm bnep rfcomm bluetooth)
/bin/systemctl stop bluetooth
for (( i=0; i<${#modules[@]}; i++ ))
do
/sbin/modprobe -r "${modules[i]}"
done
/bin/systemctl suspend
for (( i=${#modules[@]}-1; i>=0; i-- ))
do
/sbin/modprobe "${modules[i]}"
done
/bin/systemctl start bluetooth
exit 0

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

Title:
  Bluetooth (btintel) stops working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run cosmic on my Dell Latitude E7470, which has an intel usb
  bluetooth device (8087:0a2b).

  Sometimes (not every time) after a suspend/resume cycle, my laptop's
  bluetooth stops working.  hciconfig shows:

  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

  and dmesg tells me (various combinations of):

  [237660.728312] Bluetooth: hci0: command tx timeout
  [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
  [237925.202500] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  
  Trying to reinitialize the device by reloading the driver has no effect:

  ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe
  btusb

  shows in dmesg:

  [237938.219190] usbcore: deregistering interface driver btusb
  [237938.601731] usbcore: registered new interface driver btusb
  [237940.626392] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [237940.626426] Bluetooth: hci0: command tx timeout

  Strangely enough, reloading the module sometimes does work, upon which the 
kernel tells me :
  aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 
2 week 52 2014
  aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download 
to complete
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 
usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-11-5.ddc
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters 
completed

  
  Looking further back in the kernel log, the difference between failed and 
successful resumes seems to be this:

  Resume with broken bt:
  [236481.370814] Restarting tasks ... 
  [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)

  Resume with working bt:
  [16562.706263] Restarting tasks ... 
  [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [16562.716050] Bluetooth: hci0: Device revision is 5
  [16562.716052] Bluetooth: hci0: Secure boot is enabled
  [16562.716053] Bluetooth: hci0: OTP lock is enabled
  [16562.716054] Bluetooth: hci0: API lock is enabled
  [16562.716055] Bluetooth: hci0: Debug lock is disabled
  [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
  [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
  [16564.203091] Bluetooth: hci0: Waiting for device to boot
  [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
  [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
  [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed

  
  and everything works fine after that.


  The first kernel on which this error occurred wa

[Kernel-packages] [Bug 1793584] Re: i2c_hid module randomly dies and needs to be restarted

[Kai-Heng Feng]

Ok, please try the kernel inside the link.

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

Title:
  i2c_hid module randomly dies and needs to be restarted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  From 4.15.0-24 (not in 4.15.0-23) i2c_hid spams the log with messages
  like this:

  [ 6079.727465] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete report 
(14/65535)
  [ 6079.733692] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete report 
(14/65535)

  It then randomly stops working (and stops spamming the log), and there
  is no trackpad response until I reload the module.

  Again, this was introduced in 4.15.0-24.

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

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