[Kernel-packages] [Bug 1247723]

[jonas]

Hi

Poll on status for this bug. Does anyone know if/when it will be fixed
upstream?

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

Title:
  [Samsung NP900X3C-A02US] Lid state changes not detected

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

Bug description:
  Neither lid open nor lid close events are detected on Samsung 900X3C
  laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19 [modified: 
boot/vmlinuz-3.11.0-12-generic]
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sahak  1482 F pulseaudio
  Date: Sun Nov  3 23:11:48 2013
  InstallationDate: Installed on 2013-10-26 (8 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=366ff628-3319-488f-b6f2-7b1872de5733 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog: Nov  3 23:05:26 samsung kernel: [ 5958.261114] perf samples too 
long (2517 > 2500), lowering kernel.perf_event_max_sample_rate to 5
  dmi.bios.date: 02/08/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P06AAC
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP06AAC:bd02/08/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 900X3C/900X3D/900X4C/900X4D
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1247723]

[jonas]

Hi

Poll on status for this bug. Does anyone know if/when it will be fixed
upstream?

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

Title:
  [Samsung NP900X3C-A02US] Lid state changes not detected

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

Bug description:
  Neither lid open nor lid close events are detected on Samsung 900X3C
  laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19 [modified: 
boot/vmlinuz-3.11.0-12-generic]
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sahak  1482 F pulseaudio
  Date: Sun Nov  3 23:11:48 2013
  InstallationDate: Installed on 2013-10-26 (8 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=366ff628-3319-488f-b6f2-7b1872de5733 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog: Nov  3 23:05:26 samsung kernel: [ 5958.261114] perf samples too 
long (2517 > 2500), lowering kernel.perf_event_max_sample_rate to 5
  dmi.bios.date: 02/08/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P06AAC
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP06AAC:bd02/08/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 900X3C/900X3D/900X4C/900X4D
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1776563]

[bakarichard91]

gg71, it works almost perfectly, thanks again. I have been working on
this for ca one month. Please write a mail to me if you have any new
info.

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

Title:
  Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven)

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1776563]

[bakarichard91]

gg71, where have you been till now? :D
Thanks, I will try it.

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

Title:
  Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven)

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1776563]

[ggollner]

Hi, 
amdgpu doesn't crash on my a315-41g-r40x (BIOS V1.08) with  
  linux-next-next-20180713 compiled with VGA_SWITCHEROO=N 
and with 
  kernel parameters: ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2

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

Title:
  Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven)

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1776563]

[bakarichard91]

Hi, I was trying another kernel parameters and noapic seems to work. It is not 
needed to disable the whole ACPI "service", however I don't know how important 
apic is. On kernel 4.18 even temperature sensors appear.
Power management is almost perfect if cpu governor is set to powersave.

At least amdgpu crashes now so kernel doesn't start without nomodeset.
Could this be an acpi problem or I should ask kernel firmware
developers?

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

Title:
  Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven)

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1715149] Re: Sometimes whole screen freezes out and sometimes only touchpad. Then at the end I have to reboo it. There is no other way of fixing this. I bought my new laptop jus

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

Title:
  Sometimes whole screen freezes out and sometimes only touchpad. Then
  at the end I have to reboo it. There is no other way of fixing this. I
  bought my new laptop just 2 months ago so its really freak me out.
  Please help me ASAP

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am pretty sure this is a bug because when I used some system with
  windows it was working fine. So, I think it is some kind of bug or may
  be there is some c0mpatibility issue. While I was updating my system i
  was getting following error:-

  "W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915"

  My ubuntu version is :-

  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Please help asap.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  5 18:27:33 2017
  InstallationDate: Installed on 2017-07-24 (43 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1715049] Re: the system reported an error on login

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

Title:
  the system reported an error on login

Status in linux package in Ubuntu:
  Expired

Bug description:
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  5 09:29:57 2017
  InstallationDate: Installed on 2017-08-29 (6 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1716207] Re: WARNING: CPU: 0 PID: 0 at linux-hwe-4.10.0/net/ipv4/tcp_input.c:2241 tcp_mark_head_lost+0x1da/0x2d0

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

Title:
  WARNING: CPU: 0 PID: 0 at linux-hwe-4.10.0/net/ipv4/tcp_input.c:2241
  tcp_mark_head_lost+0x1da/0x2d0

Status in linux package in Ubuntu:
  Expired

Bug description:
  Got this warning a few days after upgrading my Ubuntu 16.04.3 LTS
  server from 4.4 to 4.10.0-33 (linux-hwe), and applying "bbr" as
  congestion control.

  I'm using the following non-default kernel parameters:
  net.core.somaxconn = 512
  net.core.default_qdisc = fq
  net.ipv4.tcp_congestion_control = bbr
  net.ipv4.tcp_slow_start_after_idle = 0
  net.ipv4.tcp_mtu_probing = 1
  net.core.rmem_max = 67108864
  net.core.wmem_max = 67108864
  net.ipv4.tcp_rmem = 4096 87380 33554432
  net.ipv4.tcp_wmem = 4096 65536 33554432

  NIC: HP CN1000E 10GbE
  # ethtool -k enp4s0f0 
  Features for enp4s0f0:
  rx-checksumming: on
  tx-checksumming: on
tx-checksum-ipv4: on
tx-checksum-ip-generic: off [fixed]
tx-checksum-ipv6: on
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
  scatter-gather: on
tx-scatter-gather: on
tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
tx-tcp-segmentation: on
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp-mangleid-segmentation: off
tx-tcp6-segmentation: on
  udp-fragmentation-offload: off [fixed]
  generic-segmentation-offload: on
  generic-receive-offload: on
  large-receive-offload: off [fixed]
  rx-vlan-offload: on [fixed]
  tx-vlan-offload: on
  ntuple-filters: off [fixed]
  receive-hashing: on
  highdma: on [fixed]
  rx-vlan-filter: on [fixed]
  vlan-challenged: off [fixed]
  tx-lockless: off [fixed]
  netns-local: off [fixed]
  tx-gso-robust: off [fixed]
  tx-fcoe-segmentation: off [fixed]
  tx-gre-segmentation: off [fixed]
  tx-gre-csum-segmentation: off [fixed]
  tx-ipxip4-segmentation: off [fixed]
  tx-ipxip6-segmentation: off [fixed]
  tx-udp_tnl-segmentation: off [fixed]
  tx-udp_tnl-csum-segmentation: off [fixed]
  tx-gso-partial: off [fixed]
  tx-sctp-segmentation: off [fixed]
  fcoe-mtu: off [fixed]
  tx-nocache-copy: off
  loopback: off [fixed]
  rx-fcs: off [fixed]
  rx-all: off [fixed]
  tx-vlan-stag-hw-insert: off [fixed]
  rx-vlan-stag-hw-parse: off [fixed]
  rx-vlan-stag-filter: off [fixed]
  l2-fwd-offload: off [fixed]
  busy-poll: on [fixed]
  hw-tc-offload: off [fixed]


  Warning in kernel ring buffer:
  [200448.082342] [ cut here ]
  [200448.082360] WARNING: CPU: 0 PID: 0 at 
/build/linux-hwe-YA6IuF/linux-hwe-4.10.0/net/ipv4/tcp_input.c:2241 
tcp_mark_head_lost+0x1da/0x2d0
  [200448.082362] Modules linked in: binfmt_misc ses enclosure bonding 
intel_rapl sb_edac ipmi_ssif edac_core x86_pkg_temp_thermal intel_powerclamp 
kvm_intel kvm irqbypass mei_me cdc_ether shpchp usbnet intel_cstate 
intel_rapl_perf mii mei ipmi_si input_leds joydev ipmi_devintf ipmi_msghandler 
lpc_ich mac_hid acpi_power_meter acpi_pad sch_fq tcp_bbr ib_iser rdma_cm iw_cm 
ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
coretemp autofs4 btrfs raid10 raid1 raid0 multipath linear raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c mgag200 i2c_algo_bit ttm crct10dif_pclmul crc32_pclmul drm_kms_helper 
ghash_clmulni_intel syscopyarea pcbc mpt3sas hid_generic sysfillrect sysimgblt 
aesni_intel fb_sys_fops tg3 raid_class usbhid aes_x86_64 lpfc crypto_simd
  [200448.082411]  glue_helper ptp scsi_transport_sas megaraid_sas drm hid 
be2net scsi_transport_fc cryptd pps_core wmi fjes
  [200448.082420] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.10.0-33-generic 
#37~16.04.1-Ubuntu
  [200448.082421] Hardware name: Google Inc Google Search Appliance/0JP31P, 
BIOS 2.5.4 01/22/2016
  [200448.082423] Call Trace:
  [200448.082424]  
  [200448.082429]  dump_stack+0x63/0x90
  [200448.082431]  __warn+0xcb/0xf0
  [200448.082433]  warn_slowpath_null+0x1d/0x20
  [200448.082434]  tcp_mark_head_lost+0x1da/0x2d0
  [200448.082436]  tcp_update_scoreboard+0x68/0x70
  [200448.082438]  tcp_fastretrans_alert+0x72c/0xb20
  [200448.082439]  tcp_ack+0x4d8/0xa60
  [200448.082441]  tcp_rcv_established+0x1bc/0x700
  [200448.082444]  ? sk_filter_trim_cap+0x47/0x170
  [200448.082446]  tcp_v4_do_rcv+0x145/0x200
  [200448.082447]  tcp_v4_rcv+0x9bb/0xa40
  [200448.082450]  ? tcp_v6_rcv+0x8e3/0x960
  [200448.082452]  ip_local_deliver_finish+0x94/0x1e0
  [200448.082453]  ip_local_deliver+0x6f/0xe0
  [200448.082455]  ? tcp_v4_early_demux+0x13a/0x150
  [200448.082456]  ip_rcv_finish+0x11b/0x400
  [200448.082457]  ip_rcv+0x28b/0x3a0
  [200448.082461]  __netif_receive_skb_core+0x51e/0xa70
  [200448.082463]  ? free_compound_page+0x1b/0x20
  

[Kernel-packages] [Bug 1720296] Re: System freeze on boot (HP probook 650g1)

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

Title:
  System freeze on boot (HP probook 650g1)

Status in linux package in Ubuntu:
  Expired

Bug description:
  On boot the system freezes sporadically after login when the system is
  plugged in. This forces a hard reset, REISUB doesn't work. I'm
  suspecting a bug in the kernel since 4.8 because on 4.4 the system
  doesn't freeze.

  P.S. This is my first time reporting a bug, so if I forgot to include
  some information or this bug  isn't a kernel bug, I'm sorry.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 29 08:10:40 2017
  InstallationDate: Installed on 2016-10-01 (362 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1716261] Re: Wired connection doesn't work after suspend.

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

Title:
  Wired connection doesn't work after suspend.

Status in linux package in Ubuntu:
  Expired

Bug description:
  Wired connection doesn't connect after suspending PC and starting it
  back. The system is Ubuntu 16.04 LTS.

  Output of lspci command:

  00:00.0 Host bridge: Intel Corporation Device 590f (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation Device 5902 (rev 04)
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#6 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)

  And output of lspci -k | grep -iA3 ethernet (I don't know what does
  this command show but I have come across this command when I was
  looking for the answer in google) command:

  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
  Subsystem: ASRock Incorporation Motherboard (one of many)
  Kernel driver in use: r8169
  Kernel modules: r8169`

  Edit on Sep 9 2017, Sat: I tried to install r8168 driver from
  realtek's site. First, I followed the manual instructions in this
  site: https://unixblogger.com/2016/08/11/how-to-get-your-realtek-
  rtl8111rtl8168-working-updated-guide/

  I tried to install dependencies by entering the code into terminal:

  sudo apt-get install build-essential linux-headers-$(uname -r)

  and then I downloaded the driver from Realtek's site:
  
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1=13=5=5=4=3=false#2

  I downloaded the version which states Linux driver for kernel up to
  4.7. I don't exactly if that is the case, if that one is causing me
  the problems.

  Then I blacklisted my already installed and working r8169 driver by
  this code:

  user@linux:~$ sudo sh -c 'echo blacklist r8169 >>
  /etc/modprobe.d/blacklist.conf'

  Then I untarred the archive by this code: tar xfvj
  0009-r8168-8.044.02.tar.bz2

  which showed me the following output:

  r8168-8.044.02/
  r8168-8.044.02/autorun.sh
  r8168-8.044.02/Makefile
  r8168-8.044.02/README
  r8168-8.044.02/src/
  r8168-8.044.02/src/Makefile
  r8168-8.044.02/src/Makefile_linux24x
  r8168-8.044.02/src/r8168.h
  r8168-8.044.02/src/r8168_asf.c
  r8168-8.044.02/src/r8168_asf.h
  r8168-8.044.02/src/r8168_dash.h
  r8168-8.044.02/src/r8168_fiber.h
  r8168-8.044.02/src/r8168_n.c
  r8168-8.044.02/src/r8168_realwow.h
  r8168-8.044.02/src/rtltool.c
  r8168-8.044.02/src/rtltool.h
  r8168-8.044.02/src/rtl_eeprom.c
  r8168-8.044.02/src/rtl_eeprom.h

  After that I got into that folder r8168-8.044.02/ and compiled the
  script autorun.sh sudo ./autorun.shwhich showed me the following
  output on terminal:

  Check old driver and unload it.
  rmmod r8169
  Build the module and install
  At main.c:158:
  - SSL error:02001002:system library:fopen:No such file or directory: 
bss_file.c:175
  - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
  sign-file: certs/signing_key.pem: No such file or directory
  Backup r8169.ko
  rename r8169.ko to r8169.bak
  DEPMOD 4.10.0-33-generic
  load module r8168
  Updating initramfs. Please wait.
  update-initramfs: Generating /boot/initrd.img-4.10.0-33-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin for 
module i915
  Completed.

  Then I run this code: lsmod | grep r8168 which output: r8168
  499712  0

  Then I run sudo ethtool -i enp2s0.

  After that I suspended my PC and reopened it back, but it had the same
  problem, it did not connect to Wired connection after suspension. I
  had reboot it to get working Ethernet connection. After rebooting I
  tried to install it automatically rather than manually, so I edited
  /etc/apt/sources.list, I changed xenial main restricted to xenial main
  restricted universe. Then I sudo apt-get update, then I sudo apt-get
  

[Kernel-packages] [Bug 1720301] Re: Airplane key not recognized

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

Title:
  Airplane key not recognized

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,
   Computer : Clevo N240JU
   Kernel : 4.10.0-35-generic
   Release : Ubuntu 16.4.03 LTS
   Keyboard : FR_CH layout
   For my computer, when I touch the combination [FN]+[F11] it does something 
unattended. The stroke toggle the bluetooth but don't toggle the wifi. How can 
I make that the key combination work normaly?
   Something really strange too : the combination is not recognized in 
acpi_listen nor xev. But the bluetooth is really toggled...
  Best regards.
  Jean Tinguely Awais.

  PS : in relation with this question 
https://answers.launchpad.net/ubuntu/+question/658741
  PS 2 : detail of more investigations here 
https://swisslinux.org/forum/viewtopic.php?pid=25060#p25060

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 29 08:35:59 2017
  InstallationDate: Installed on 2017-09-25 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1717609] Re: Bluetooth devices not getting recognized

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

Title:
  Bluetooth devices not getting recognized

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm unable to connect my wireless headset. I don't know what to do.
  Could you please suggest me where to start for debugging.

  Thank you and Regards
  Vinod Kumar Metla

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 16 03:37:19 2017
  InstallationDate: Installed on 2017-07-02 (74 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1715606] Re: Memory corruption detected in low memory

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

Title:
  Memory corruption detected in low memory

Status in linux package in Ubuntu:
  Expired

Bug description:
  I saw in the logs

  Sep  7 12:05:21 server kernel: [16100.022290] WARNING: CPU: 0 PID: 9521 at 
/build/linux-hwe-YA6IuF/linux-hwe-4.10.0/arch/x86/kernel/check.c:141 
check_for_bios_corruption.part.1+0xac/0x100
  Sep  7 12:05:21 server kernel: [16100.022291] Memory corruption detected in 
low memory
  Sep  7 12:05:21 server kernel: [16100.022317] Modules linked in: ccm l2tp_ppp 
l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ipt_REJECT 
nf_reject_ipv4 xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 
af_key xfrm_algo xt_recent xt_connlimit xt_conntrack xt_TCPMSS iptable_mangle 
xt_nat xt_tcpudp xt_REDIRECT nf_nat_redirect ipt_MASQUERADE xt_multiport 
nf_nat_masquerade_ipv4 iptable_filter iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 ip_tables x_tables snd_usb_audio snd_usbmidi_lib 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm arc4 intel_rapl ath9k bridge stp 
llc x86_pkg_temp_thermal intel_powerclamp ath9k_common ath9k_hw ath 
snd_seq_midi snd_seq_midi_event kvm_intel mac80211 snd_rawmidi kvm snd_seq 
snd_seq_device snd_timer ath3k
  Sep  7 12:05:21 server kernel: [16100.022346]  btusb btrtl btbcm cfg80211 
irqbypass serio_raw snd btintel intel_cstate mei_me gspca_zc3xx mei uvcvideo 
gspca_main videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 v4l2_common 
videobuf2_core videodev bluetooth intel_rapl_perf media asix usbnet soundcore 
lpc_ich shpchp mac_hid nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp 
nf_conntrack_proto_gre nf_nat nf_conntrack ib_iser rdma_cm iw_cm ib_cm ib_core 
configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi it87 hwmon_vid 
coretemp autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 
i2c_algo_bit crct10dif_pclmul drm_kms_helper crc32_pclmul syscopyarea 
sysfillrect ghash_clmulni_intel sysimgblt uas fb_sys_fops cryptd psmouse r8169 
ahci mii usb_storage
  Sep  7 12:05:21 server kernel: [16100.022378]  libahci drm fjes video
  Sep  7 12:05:21 server kernel: [16100.022382] CPU: 0 PID: 9521 Comm: 
kworker/0:2 Not tainted 4.10.0-33-generic #37~16.04.1-Ubuntu
  Sep  7 12:05:21 server kernel: [16100.022383] Hardware name: DNS ChiefRiver 
Platform/Emerald Lake 2, BIOS W6561023 04/13/2013
  Sep  7 12:05:21 server kernel: [16100.022385] Workqueue: events 
check_corruption
  Sep  7 12:05:21 server kernel: [16100.022386] Call Trace:
  Sep  7 12:05:21 server kernel: [16100.022390]  dump_stack+0x63/0x90
  Sep  7 12:05:21 server kernel: [16100.022392]  __warn+0xcb/0xf0
  Sep  7 12:05:21 server kernel: [16100.022393]  warn_slowpath_fmt+0x5f/0x80
  Sep  7 12:05:21 server kernel: [16100.022394]  
check_for_bios_corruption.part.1+0xac/0x100
  Sep  7 12:05:21 server kernel: [16100.022395]  check_corruption+0x18/0x50
  Sep  7 12:05:21 server kernel: [16100.022397]  process_one_work+0x16b/0x4a0
  Sep  7 12:05:21 server kernel: [16100.022399]  worker_thread+0x4b/0x500
  Sep  7 12:05:21 server kernel: [16100.022401]  kthread+0x109/0x140
  Sep  7 12:05:21 server kernel: [16100.022402]  ? process_one_work+0x4a0/0x4a0
  Sep  7 12:05:21 server kernel: [16100.022404]  ? 
kthread_create_on_node+0x60/0x60
  Sep  7 12:05:21 server kernel: [16100.022406]  ret_from_fork+0x2c/0x40
  Sep  7 12:05:21 server kernel: [16100.022407] ---[ end trace 0fcb7549d875341c 
]---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Sep  7 13:23:05 2017
  InstallationDate: Installed on 2017-09-06 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1717950] Re: START: tid 1 is not agg'able

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

Title:
  START: tid 1 is not agg'able

Status in linux package in Ubuntu:
  Expired

Bug description:
  Battery Drains quickly and "START: tid 1 is not agg'able" this Error I
  see in the Terminal When i use Dmesg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 18 20:34:45 2017
  InstallationDate: Installed on 2017-04-19 (151 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1770993] Re: System freezes, random reboots and browser crashes

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

Title:
  System freezes, random reboots and browser crashes

Status in linux package in Ubuntu:
  Expired

Bug description:
  I've been having this issue with both 18.04 and 16.04 Ubuntu MATE
  since I installed an Nvidia GTX 1060. The system can run stably for
  days, or it can start freezing randomly and I have to manually reset,
  or the system freezes and then reboots itself. Browsers are also
  affected, and I've not found one that doesn't randomly crash, though
  Opera is particularly affected.  This is the hardware spec of my
  system:

  Computer Processor
  AMD FX(tm)-8120 Eight-Core Processor
  Memory
  32938MB (4021MB used)
  Machine Type
  Desktop
  Operating System
  Ubuntu 18.04 LTS
  User Name
  xxx
  Date/Time
  Dydd Mercher 09 mis Mai 2018 00:18:57 BST
  Display
  Resolution
  5760x1080 pixels
  OpenGL Renderer
  GeForce GTX 1060 6GB/PCIe/SSE2
  X11 Vendor
  The X.Org Foundation

  md5sum was fine when I checked the intallation usb, and the fact that
  it's affected both 16.04 and 18.04 (though 18.04 significantly less)
  indicates there is a problem which I suspect is linked to the Nvidia
  graphics card in some way, as it's also been an issue with Second
  Life/OpenSimulator viewers that also randomly freeze requiring a hard
  reboot of the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 13 18:23:17 2018
  InstallationDate: Installed on 2018-04-11 (32 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180410)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1721182] Re: restart on shutdown or suspension

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

Title:
  restart on shutdown or suspension

Status in linux package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Running on an Acer Aspire E1-470 Laptop.

  After a fresh ubuntu installation the power off command didn't worked
  as intended, neither the suspension function, neither the shutdown
  command via terminal.

  It appeared to be a problem with ACPI controlators, sadly, editing on 
/etc/defaut/grub on the line
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off" also disables wifi and 
networking in general.

  The solution was to remove "acpi=off" and instead using, on /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct  4 00:07:08 2017
  InstallationDate: Installed on 2017-09-30 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven)

[Richard Baka]

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

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

Title:
  Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven)

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven)

[Richard Baka]

Dear Ubuntu maintainers,

couldn't this be fixed by an ubuntu kernel patch? The hardest part is to
disable gpu switching at kernel load time. APIC fixing parameters can be
hardcoded for these models I think or search for the correct pci
controller using a smart script.

This was a hell of an investigation, never again. Thanks for gg71,
he/she is a lifesaver.

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

Title:
  Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven)

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven)

[Richard Baka]

The solution for Acer A315-41G-* notebooks: (USE AT YOUR OWN RISK - PLS
be very careful)

1. Load kernel with these parameters: ivrs_ioapic[4]=00:14.0 
ivrs_ioapic[5]=00:00.2 nomodeset
This is how it can be done (1. answer/first half 1-4): 
https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter

1/b.(if it is not installed) Install ubuntu and load installed kernel
again using the parameters (see 1.)

2. Start a terminal and do these steps:
> cd ~
> mkdir kernelbuild
> cd kernelbuild
> wget -c https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.17.6.tar.xz
> tar -xvf linux-4.17.6.tar.xz
> cd linux-4.17.6
> sudo apt install git build-essential kernel-package fakeroot libncurses5-dev 
> libssl-dev ccache bison flex
> make menuconfig
+> Save,OK,EXIT
> nano .config
+> ctrl+w and search for CONFIG_VGA_SWITCHEROO=y
+> replace y with n (this is not ideal and should be fixed later)
+> ctrl+o, enter
> make -j4 (this will take a while, be patient)
> make modules_install
> sudo make install
> sudo nano /etc/default/grub
+> Edit the correct line and add the parameters: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ivrs_ioapic[4]=00:14.0 
ivrs_ioapic[5]=00:00.2"
+>CTRL+O, enter
>sudo update-grub
+> reboot and start the correct kernel 

If you install xsensors (sudo apt install xsensors) and start it
(xsensors) you can monitor the temperature values of your notebook.
(Recommended)

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

Title:
  Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven)

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1283589]

[jonas]

Hi

Poll on status for this bug. Does anyone know if/when it will be fixed
upstream?

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

Title:
  [Samsung NP530U3C-A01] LID close, AC, and battery status events not
  produced anymore

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

Bug description:
  On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery
  status events not produced anymore. The situation is the same (tested
  with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where
  I can put all the information related to this bug here:
  http://zenstep.com.ar/samsung-linux/

  In summary, after a suspend sleep with many events (8 plug/unplug, or
  battery dropping or increasing about 16%, maybe less), the Embedded
  Controller accumulates those events and stops producing GPE 0x17.
  Neither Windows nor Linux query those accumulated events, because the
  EC doesn't produce GPE 0x17 anymore. The issue persists between
  restarts and shutdowns, and even after re-suspending/re-resuming.
  Hitting the reset button through the hole in the back fixes the
  problem temporarily. That is, until the next unlucky suspend.

  IMPORTANT: if the laptop is never ever suspended, the issue never
  comes back.

  To force the issue to happen, you can either:
  1) Sleep the computer in linux (by closing the lid or any other means).
  2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 
actions or more).
  3) Resume from sleep. You'll note that the battery icon is fixed, and 
unplugging or plugging doesn't update battery status anymore. Also note that 
the ability to suspend by closing the LID is lost.

  OR:
  1) echo disable > /sys/firmware/acpi/interrupts/gpe17
  2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions)
  3) echo enable > /sys/firmware/acpi/interrupts/gpe17

  WORKAROUND: Turn off the computer, unplug it, hit the reset button in
  the back of the laptop, and then plug it again.

  WORKAROUND (kernel patch 1):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133

  BETTER WORKAROUND (kernel patch 2):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-11-generic 3.13.0-11.31
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2546 F pulseaudio
  CasperVersion: 1.337
  Date: Sat Feb 22 22:57:34 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-11-generic N/A
   linux-backports-modules-3.13.0-11-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1283589]

[jonas]

Hi

Poll on status for this bug. Does anyone know if/when it will be fixed
upstream?

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

Title:
  [Samsung NP530U3C-A01] LID close, AC, and battery status events not
  produced anymore

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

Bug description:
  On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery
  status events not produced anymore. The situation is the same (tested
  with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where
  I can put all the information related to this bug here:
  http://zenstep.com.ar/samsung-linux/

  In summary, after a suspend sleep with many events (8 plug/unplug, or
  battery dropping or increasing about 16%, maybe less), the Embedded
  Controller accumulates those events and stops producing GPE 0x17.
  Neither Windows nor Linux query those accumulated events, because the
  EC doesn't produce GPE 0x17 anymore. The issue persists between
  restarts and shutdowns, and even after re-suspending/re-resuming.
  Hitting the reset button through the hole in the back fixes the
  problem temporarily. That is, until the next unlucky suspend.

  IMPORTANT: if the laptop is never ever suspended, the issue never
  comes back.

  To force the issue to happen, you can either:
  1) Sleep the computer in linux (by closing the lid or any other means).
  2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 
actions or more).
  3) Resume from sleep. You'll note that the battery icon is fixed, and 
unplugging or plugging doesn't update battery status anymore. Also note that 
the ability to suspend by closing the LID is lost.

  OR:
  1) echo disable > /sys/firmware/acpi/interrupts/gpe17
  2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions)
  3) echo enable > /sys/firmware/acpi/interrupts/gpe17

  WORKAROUND: Turn off the computer, unplug it, hit the reset button in
  the back of the laptop, and then plug it again.

  WORKAROUND (kernel patch 1):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133

  BETTER WORKAROUND (kernel patch 2):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-11-generic 3.13.0-11.31
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2546 F pulseaudio
  CasperVersion: 1.337
  Date: Sat Feb 22 22:57:34 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-11-generic N/A
   linux-backports-modules-3.13.0-11-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1779377] Re: linux-aws: 4.4.0-1025.26 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

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

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

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

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

[Kernel-packages] [Bug 1779376] Re: linux: 4.4.0-131.157 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-131.157 -proposed tracker

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

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

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

  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (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/1779376/+subscriptions

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

[Kernel-packages] [Bug 1781433] Re: linux: 4.15.0-28.30 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.15.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 
(azure), bug 1781074 (azure-edge), bug 1781115 (gcp)
  derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), 
bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem)
  -- 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/1781433/+subscriptions

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

[Kernel-packages] [Bug 1779379] Re: linux-aws: 4.4.0-1063.72 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

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

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

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

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

[Kernel-packages] [Bug 1781066] Re: linux-azure: 4.15.0-1017.17 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow 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: 1781433
  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/1781066/+subscriptions

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

[Kernel-packages] [Bug 1781115] Re: linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  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/1781115/+subscriptions

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

[Kernel-packages] [Bug 1781435] Re: linux-aws: 4.15.0-1015.15 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-aws: 4.15.0-1015.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in 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: 1781433
  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/1781435/+subscriptions

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

[Kernel-packages] [Bug 1779377] Re: linux-aws: 4.4.0-1025.26 -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

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

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

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

** 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779376
  phase: Uploaded
+ kernel-stable-phase-changed:Friday, 13. July 2018 18:32 UTC
+ kernel-stable-phase:Promoted to 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779376
- phase: Uploaded
- kernel-stable-phase-changed:Friday, 13. July 2018 18:32 UTC
- kernel-stable-phase:Promoted to proposed
+ 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1779377

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

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

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

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

[Kernel-packages] [Bug 1781435] Re: linux-aws: 4.15.0-1015.15 -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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded
+ kernel-stable-phase-changed:Friday, 13. July 2018 18:31 UTC
+ kernel-stable-phase:Promoted to 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
- phase: Uploaded
- kernel-stable-phase-changed:Friday, 13. July 2018 18:31 UTC
- kernel-stable-phase:Promoted to proposed
+ 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1781435

Title:
  linux-aws: 4.15.0-1015.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in 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: 1781433
  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/1781435/+subscriptions

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

[Kernel-packages] [Bug 1781578] Re: Call trace observed while disabling PD on Ubuntu 16.04.4

[Murthy Bhat]

Due to nature of the defect, could not run the apport-collect command

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

Title:
  Call trace observed while disabling PD on Ubuntu 16.04.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working on smartpqi linux driver for Microsemi.

  We have a storage controller managment application tool to manage storage 
behind our controller. One of the application option what we have is to disable 
physical device(PD).
  During disable PD opertaion, Disable PD command got timedout. Then I observed 
below mentioned call trace in dmesg log.
  Please note we are running IO stress test on the PD which is being disabled.

  Please let me know if there are any known issues specific to Ubuntu kernel 
with respect to this. 
  If its a known issue specific to Ubuntu 16.04.4 distro, does this issue 
already addressed in latest Ubuntu OS distro ?

  Thanks in advance!

  Sincerely,
  Murthy Bhat

  Call trace:
  smartpqi :92:00.0: removed 5:0:2:0 3d1701cf2001 Direct-Access ATA 
ST1000NX0303 AIO+ qd=32
  [ 1199.201495] Buffer I/O error on dev sdk, logical block 244190645, async 
page read
  [ 1343.006515] sdn:
  [ 1358.264503] INFO: task kworker/173:1:1620 blocked for more than 120 
seconds.
  [ 1358.271550] Tainted: G OE 4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1358.278966] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1358.286806] kworker/173:1 D 0 1620 2 0x
  [ 1358.286832] Workqueue: events pqi_rescan_worker [smartpqi]
  [ 1358.286836] Call trace:
  [ 1358.286844] [] __switch_to+0x90/0xa8
  [ 1358.286855] [] __schedule+0x35c/0x8b0
  [ 1358.286858] [] schedule+0x34/0x90
  [ 1358.286865] [] blk_mq_freeze_queue_wait+0x70/0xd8
  [ 1358.286869] [] blk_mq_freeze_queue+0x28/0x38
  [ 1358.286873] [] blk_freeze_queue+0x20/0x30
  [ 1358.286878] [] blk_cleanup_queue+0x78/0x128
  [ 1358.286883] [] __scsi_remove_device+0x64/0x128
  [ 1358.286884] [] scsi_remove_device+0x30/0x48
  [ 1358.286887] [] scsi_remove_target+0x188/0x1c8
  [ 1358.286899] [] sas_rphy_remove+0x78/0x98 
[scsi_transport_sas]
  [ 1358.286907] [] sas_port_delete+0x38/0x160 
[scsi_transport_sas]
  [ 1358.286918] [] pqi_free_sas_port+0x4c/0x88 [smartpqi]
  [ 1358.286926] [] pqi_remove_sas_device+0x24/0x38 [smartpqi]
  [ 1358.286933] [] pqi_update_device_list+0x520/0x818 
[smartpqi]
  [ 1358.286939] [] pqi_scan_scsi_devices+0x420/0x980 
[smartpqi]
  [ 1358.286946] [] pqi_rescan_worker+0x24/0x30 [smartpqi]
  [ 1358.286955] [] process_one_work+0x14c/0x420
  [ 1358.286957] [] worker_thread+0x12c/0x470
  [ 1358.286961] [] kthread+0x108/0x138
  [ 1358.286963] [] ret_from_fork+0x10/0x30
  [ 1358.287045] INFO: task pain:6788 blocked for more than 120 seconds.
  [ 1358.293326] Tainted: G OE 4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1358.300730] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1358.308567] pain D 0 6788 6633 0x

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

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

[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

[Rod Smith]

This looks to me as if Ubuntu (the kernel, Wayland, and/or the X server,
depending on when the problem occurs) is delivering a video mode that
the display device can't handle. (With VGA, the display should deliver
its capabilities to the computer via EDID, but this doesn't always work
correctly.) Thus, the first question is what that "display device" is.
The screen shots look like a remote KVM of some sort. Is that the BMC's
built-in screen-sharing tool, a network-accessible KVM hardware device
(like a Raritan or Avocent), or something else? If possible, I recommend
testing in person with a plain monitor plugged directly into the
computer, at least as a diagnostic procedure. If that works, then it's
likely that the issue is either a matter of a restrictive set of video
modes in the remote-access tool, miscommunication between the remote-
access tool and the kernel/Wayland/X, or both. Also, if a physical
monitor is plugged into the server while it's being accessed remotely,
it's conceivable that the kernel/Wayland/X is taking its cues about
video mode from the physical monitor rather than from the remote-access
tool, thus creating a mismatch. If the problem is caused by the remote
access tool, or by an interaction between that and the kernel/Wayland/X,
then updating the remote access tool's firmware may fix the problem.

Note that the video mode used can vary depending on the kernel version,
X vs. Wayland, EFI vs. BIOS boot mode, and other factors. Such variables
likely explain why earlier kernels worked but newer ones don't.

As a workaround, it might be possibly to forcibly reconfigure the system
to use a video mode that will work with the display device.
Unfortunately, there are a lot of different ways to do this, depending
on the subsystem involved. For instance:

* Kernel parameters can set the kernel's video mode. Unfortunately, there are
  a lot of possibilities even here, including, but not limited to:
  * nomodeset
  * video=vga16fb:off
  * vga16fb.modeset=0
  * video=efifb:width:640,height:480
  * Try Googling "kernel video mode setting" or something similar for
additional possibilities.
* X configuration
  * If you can get X working, even temporarily, you can use the GUI
setup tools to change the resolution.
  * The xrandr tool can be used to probe and set video options; see
https://www.x.org/wiki/Projects/XRandR/
  * I've not kept up with text-mode (manual) X configuration, but
you may be able to find some documentation on how to get it
to change video mode. Start here:
https://help.ubuntu.com/community/VideoDriverHowto#Xorg.conf.d
* Wayland configuration
  * I'm even less of an expert on this, so I suggest you try
Googling "wayland set resolution" or something similar.

Finally, note that Ubuntu server certification doesn't cover display
devices, so this is NOT a certification blocker.

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

Title:
  Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI
  boot mode

Status in linux package in Ubuntu:
  Triaged
Status in install-package source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

To manage notifications about this 

[Kernel-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Christopher M. Penalver]

Thomas Diesenreiter, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771204/comments/22
regarding how you consider this issue closed. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in linux package in Ubuntu:
  Invalid

Bug description:
  My laptop was running fine for years, but after the latest update to
  18.04 and the reboot there were horizontal lines everywhere.

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

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

[David McWilliams]

I have the same problem as Steve Dodd and MV, it worked fine until
4.15.0-24-generic #26-Ubuntu, now my network will not resume after
suspend.

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

modprobe -r r8169
modprobe -i r8169
... does not help.

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

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

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Kernel-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Thomas Diesenreiter]

ad 1) When I boot the old kernel, the lines start to appear. They stay as long 
as I run the old kernel. When I boot the new kernel, they are there at the 
beginning and then slowly fade away and never come again.
ad 2)3) Even if the cause was different, the reported behavior is the same.

Anyway, its fixed now. Thanks for your help.

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to
  18.04 and the reboot there were horizontal lines everywhere.

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Kernel-packages] [Bug 1772516] Re: [Config] enable EDAC_DEBUG on ARM64

[Manoj Iyer]

Tested Cosmic -proposed kernel on ThunderX, ThunderX2 and QDF2400
server. Comparing before and after dmesg output on these systems
ThunderX has more debug messages in dmesg than other systems.

-- ThunderX --
ubuntu@seuss:~$ uname -a 
Linux seuss 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:52 UTC 2018 
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@seuss:~$ dmesg | grep -i debug
ubuntu@seuss:~$

ubuntu@seuss:~$ uname -a 
Linux seuss 4.17.0-5-generic #6-Ubuntu SMP Tue Jul 10 12:41:51 UTC 2018 aarch64 
aarch64 aarch64 GNU/Linux
ubuntu@seuss:~$ dmesg | grep -i debug
[2.074861] EDAC DEBUG: edac_mc_sysfs_init: device mc created
[   35.269879] EDAC DEBUG: edac_mc_alloc: allocating 2268 bytes for mci data (2 
dimms, 2 csrows/channels)
[   35.270204] EDAC DEBUG: edac_mc_add_mc_with_groups: 
[   35.270208] EDAC DEBUG: edac_create_sysfs_mci_device: creating bus mc0
[   35.270245] EDAC DEBUG: edac_create_sysfs_mci_device: creating device mc0
[   35.270512] EDAC DEBUG: edac_mc_alloc: allocating 2268 bytes for mci data (2 
dimms, 2 csrows/channels)
[   35.270764] EDAC DEBUG: edac_mc_add_mc_with_groups: 
[   35.270768] EDAC DEBUG: edac_create_sysfs_mci_device: creating bus mc1
[   35.270802] EDAC DEBUG: edac_create_sysfs_mci_device: creating device mc1
[   35.271063] EDAC DEBUG: edac_mc_alloc: allocating 2268 bytes for mci data (2 
dimms, 2 csrows/channels)
[   35.271438] EDAC DEBUG: edac_mc_add_mc_with_groups: 
[   35.271442] EDAC DEBUG: edac_create_sysfs_mci_device: creating bus mc2
[   35.271535] EDAC DEBUG: edac_create_sysfs_mci_device: creating device mc2
[   35.272056] EDAC DEBUG: edac_mc_alloc: allocating 2268 bytes for mci data (2 
dimms, 2 csrows/channels)
[   35.272457] EDAC DEBUG: edac_mc_add_mc_with_groups: 
[   35.272461] EDAC DEBUG: edac_create_sysfs_mci_device: creating bus mc3
[   35.272519] EDAC DEBUG: edac_create_sysfs_mci_device: creating device mc3
[   35.272968] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.273265] EDAC DEBUG: edac_device_add_device: 
[   35.273268] EDAC DEBUG: find_edac_device_by_dev: 
[   35.273272] EDAC DEBUG: edac_device_create_sysfs: idx=0
[   35.273313] EDAC DEBUG: edac_device_create_instances: 
[   35.273485] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.273823] EDAC DEBUG: edac_device_add_device: 
[   35.273826] EDAC DEBUG: find_edac_device_by_dev: 
[   35.273828] EDAC DEBUG: edac_device_create_sysfs: idx=1
[   35.273846] EDAC DEBUG: edac_device_create_instances: 
[   35.274003] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.274243] EDAC DEBUG: edac_device_add_device: 
[   35.274245] EDAC DEBUG: find_edac_device_by_dev: 
[   35.274248] EDAC DEBUG: edac_device_create_sysfs: idx=2
[   35.274274] EDAC DEBUG: edac_device_create_instances: 
[   35.274502] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.274751] EDAC DEBUG: edac_device_add_device: 
[   35.274753] EDAC DEBUG: find_edac_device_by_dev: 
[   35.274756] EDAC DEBUG: edac_device_create_sysfs: idx=3
[   35.274760] EDAC DEBUG: edac_device_create_instances: 
[   35.274899] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.275140] EDAC DEBUG: edac_device_add_device: 
[   35.275143] EDAC DEBUG: find_edac_device_by_dev: 
[   35.275145] EDAC DEBUG: edac_device_create_sysfs: idx=4
[   35.275150] EDAC DEBUG: edac_device_create_instances: 
[   35.275294] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.275524] EDAC DEBUG: edac_device_add_device: 
[   35.275535] EDAC DEBUG: find_edac_device_by_dev: 
[   35.275538] EDAC DEBUG: edac_device_create_sysfs: idx=5
[   35.275543] EDAC DEBUG: edac_device_create_instances: 
[   35.275678] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.275906] EDAC DEBUG: edac_device_add_device: 
[   35.275909] EDAC DEBUG: find_edac_device_by_dev: 
[   35.275911] EDAC DEBUG: edac_device_create_sysfs: idx=6
[   35.275916] EDAC DEBUG: edac_device_create_instances: 
[   35.276123] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.276347] EDAC DEBUG: edac_device_add_device: 
[   35.276351] EDAC DEBUG: find_edac_device_by_dev: 
[   35.276354] EDAC DEBUG: edac_device_create_sysfs: idx=7
[   35.276360] EDAC DEBUG: edac_device_create_instances: 
[   35.276490] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.276691] EDAC DEBUG: edac_device_add_device: 
[   35.276700] EDAC DEBUG: find_edac_device_by_dev: 
[   35.276702] EDAC DEBUG: edac_device_create_sysfs: idx=8
[   35.276707] EDAC DEBUG: edac_device_create_instances: 
[   35.276829] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.277027] EDAC DEBUG: edac_device_add_device: 
[   35.277040] EDAC DEBUG: find_edac_device_by_dev: 
[   35.277043] EDAC DEBUG: edac_device_create_sysfs: idx=9
[   35.277048] EDAC DEBUG: edac_device_create_instances: 
[   35.277175] EDAC DEBUG: edac_device_register_sysfs_main_kobj: 
[   35.277403] EDAC DEBUG: edac_device_add_device: 
[   35.277411] EDAC DEBUG: find_edac_device_by_dev: 
[   35.277414] EDAC DEBUG: edac_device_create_sysfs: 

[Kernel-packages] [Bug 1781433] Re: linux: 4.15.0-28.30 -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/1781433

Title:
  linux: 4.15.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 
(azure), bug 1781074 (azure-edge), bug 1781115 (gcp)
  derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), 
bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem)
  -- 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/1781433/+subscriptions

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

[Kernel-packages] [Bug 1781435] Re: linux-aws: 4.15.0-1015.15 -proposed tracker

[Łukasz Zemczak]

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

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

Title:
  linux-aws: 4.15.0-1015.15 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1779377] Re: linux-aws: 4.4.0-1025.26 -proposed tracker

[Łukasz Zemczak]

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

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

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

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

Bug description:
  This bug is for tracking the  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: 1779376
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1781435] Re: linux-aws: 4.15.0-1015.15 -proposed tracker

[Łukasz Zemczak]

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

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

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

Title:
  linux-aws: 4.15.0-1015.15 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1558135] Re: Update firmware lists for udebs

[jonathan]

** Changed in: linux-firmware (Ubuntu)
 Assignee: Seth Forshee (sforshee) => jonathan (ricoh401)

** Changed in: linux-firmware (Ubuntu)
 Assignee: jonathan (ricoh401) => (unassigned)

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

Title:
  Update firmware lists for udebs

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

Bug description:
  These lists haven't been very actively maintained for some time and
  are not up to date wrt the kernel modules included in the installer.

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

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

[Kernel-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Christopher M. Penalver]

Thomas Diesenreiter:

1)
>"Yes, but thats a onetime thing."

To clarify, if you boot into one kernel back from Proposed, then back
into Proposed, do you then have the issue only on the first boot?

2)
>"See the link I posted in the original report"

That report has been resolved for the original reporter since kernel
3.10-rc4, and has nothing to do with your issue.

3)
>"People there reported similar behaviour..."

Unfortunately, what other people reported isn't relevant. What is
though, is what you confirmed with your hardware.

** Description changed:

- My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
- https://bugs.freedesktop.org/show_bug.cgi?id=64332
+ My laptop was running fine for years, but after the latest update to
+ 18.04 and the reboot there were horizontal lines everywhere.
  
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
-  virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
+  virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
+  virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id1495 
-  vendor BOE
+  product id1495
+  vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to
  18.04 and the reboot there were horizontal lines everywhere.

  ProblemType: 

[Kernel-packages] [Bug 1781413] Re: Cannot set MTU higher than 1500 in Xen instance

[Kamal Mostafa]

Fix verified in Bionic linux (4.15.0-28.30) and Bionic linux-aws
(4.15.0-1015.15).

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

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

Title:
  Cannot set MTU higher than 1500 in Xen instance

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  The latest Xenial update has broken MTU functionality in Xen: specifically, 
  setting MTUs larger than 1500 fails. This prevents Jumbo Frames and other 
  features which require larger than 1500 byte MTUs from being used. This can 
  lead to a failure to sync/connect to other components in the cluster/cloud
  which expect higher MTUs and result in unavailable services. 

  This can be worked around by manually using ethtool to set SCATTER/GATHER
  functionality:
  - $ sudo ethtool -K $interface_name sg on 

  
  The issue is caused by the following commit to the xen-netfront driver:
  "xen-netfront: Fix race between device setup and open"
  commit f599c64fdf7d9c108e8717fb04bc41c680120da4
  Introduced: v4.16-rc1

  Reverting the above fix has confirmed that the problem goes away.

  The following commits fix this issue in the mainline kernel:

  "xen-netfront: Fix mismatched rtnl_unlock"
  commit cb257783c2927b73614b20f915a91ff78aa6f3e8
  Introduced: v4.18-rc3
  "xen-netfront: Update features after registering netdev"
  commit 45c8184c1bed1ca8a7f02918552063a00b909bf5
  Introduced: v4.18-rc3

  
  [Test Case]
  1. Launch a Xen instance using the latest kernel version (e.g. 4.4.0-130,
  or  4.4.0-1062-aws)
  2. Change MTU to 9000 or other value > 1500. 

  [Regression Potential]
  The kernel patch might not be able to set MTU.

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

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

[Kernel-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Thomas Diesenreiter]

Yes, but thats a onetime thing. The bug somehow "burns" into the system, and it 
needs time to "heal". Now, when I start the machine, I don't have any issues. 
Thats why I called it weird, I've never seen something like this.
See the link I posted in the original report: 
https://bugs.freedesktop.org/show_bug.cgi?id=64332
People there reported similar behaviour: "Update to the comment above: Even if 
the lines were not gone after the reboot with the new kernel, there are no new 
lines and the old ones seem to disappear one by one over time. It kindof 
"heals". This is a VERY strange bug, but maybe fixed after all. Just to let you 
all know, don't despair if the reboot does not fix the lines promptly. Shuffle 
around some windows and see."

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Kernel-packages] [Bug 1781413] Re: Cannot set MTU higher than 1500 in Xen instance

[Kamal Mostafa]

Fix verified in Xenial linux (4.4.0-131.157) and Xenial linux-aws
(4.4.0-1063.72).


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

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

Title:
  Cannot set MTU higher than 1500 in Xen instance

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  The latest Xenial update has broken MTU functionality in Xen: specifically, 
  setting MTUs larger than 1500 fails. This prevents Jumbo Frames and other 
  features which require larger than 1500 byte MTUs from being used. This can 
  lead to a failure to sync/connect to other components in the cluster/cloud
  which expect higher MTUs and result in unavailable services. 

  This can be worked around by manually using ethtool to set SCATTER/GATHER
  functionality:
  - $ sudo ethtool -K $interface_name sg on 

  
  The issue is caused by the following commit to the xen-netfront driver:
  "xen-netfront: Fix race between device setup and open"
  commit f599c64fdf7d9c108e8717fb04bc41c680120da4
  Introduced: v4.16-rc1

  Reverting the above fix has confirmed that the problem goes away.

  The following commits fix this issue in the mainline kernel:

  "xen-netfront: Fix mismatched rtnl_unlock"
  commit cb257783c2927b73614b20f915a91ff78aa6f3e8
  Introduced: v4.18-rc3
  "xen-netfront: Update features after registering netdev"
  commit 45c8184c1bed1ca8a7f02918552063a00b909bf5
  Introduced: v4.18-rc3

  
  [Test Case]
  1. Launch a Xen instance using the latest kernel version (e.g. 4.4.0-130,
  or  4.4.0-1062-aws)
  2. Change MTU to 9000 or other value > 1500. 

  [Regression Potential]
  The kernel patch might not be able to set MTU.

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

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

[Kernel-packages] [Bug 1779376] Re: linux: 4.4.0-131.157 -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/1779376

Title:
  linux: 4.4.0-131.157 -proposed tracker

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

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

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

  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (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/1779376/+subscriptions

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

[Kernel-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Christopher M. Penalver]

Thomas Diesenreiter, as per your comment 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771204/comments/16 :
>"Although it takes about 30 minutes after the booting with the new kernel for 
>the lines to slowly vanish."

Were you mistaken that the Proposed kernel took 30 minutes after booting
for issue to go away?

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Kernel-packages] [Bug 1771749] Re: Ethernet connection lost after few minutes since starting

[Kai-Heng Feng]

Do you see the issue on latest mainline kernel [0]?
If it still happen to mainline kernel, then find the first bad -rc kernel so we 
can start a kernel bisection.

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  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
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  

[Kernel-packages] [Bug 1781413] Re: Cannot set MTU higher than 1500 in Xen instance

[Kamal Mostafa]

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

Title:
  Cannot set MTU higher than 1500 in Xen instance

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  The latest Xenial update has broken MTU functionality in Xen: specifically, 
  setting MTUs larger than 1500 fails. This prevents Jumbo Frames and other 
  features which require larger than 1500 byte MTUs from being used. This can 
  lead to a failure to sync/connect to other components in the cluster/cloud
  which expect higher MTUs and result in unavailable services. 

  This can be worked around by manually using ethtool to set SCATTER/GATHER
  functionality:
  - $ sudo ethtool -K $interface_name sg on 

  
  The issue is caused by the following commit to the xen-netfront driver:
  "xen-netfront: Fix race between device setup and open"
  commit f599c64fdf7d9c108e8717fb04bc41c680120da4
  Introduced: v4.16-rc1

  Reverting the above fix has confirmed that the problem goes away.

  The following commits fix this issue in the mainline kernel:

  "xen-netfront: Fix mismatched rtnl_unlock"
  commit cb257783c2927b73614b20f915a91ff78aa6f3e8
  Introduced: v4.18-rc3
  "xen-netfront: Update features after registering netdev"
  commit 45c8184c1bed1ca8a7f02918552063a00b909bf5
  Introduced: v4.18-rc3

  
  [Test Case]
  1. Launch a Xen instance using the latest kernel version (e.g. 4.4.0-130,
  or  4.4.0-1062-aws)
  2. Change MTU to 9000 or other value > 1500. 

  [Regression Potential]
  The kernel patch might not be able to set MTU.

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

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

[Kernel-packages] [Bug 1781476] Re: [Bionic] bug fixes that improve stability of the ThunderX2 i2c driver

[Manoj Iyer]

I ran the following tests on a ThunderX2 system with the patched kernel:

for i in {1..100}; do sudo ipmitool sensor list; done
for i in {1..100}; do sudo ipmitool mc info; done

The idea here is to generate a lot of data though the i2c driver, and
trigger any instability that might exist. The tests did not expose any
issues.

** Summary changed:

- bug fixes that improve stability of the ThunderX2 i2c driver
+ [Bionic] bug fixes that improve stability of the ThunderX2 i2c driver

** Summary changed:

- [Bionic] bug fixes that improve stability of the ThunderX2 i2c driver
+ [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver

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

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

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

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

Title:
  [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]
  With ThunderX2 i2c driver, ipmi transfers may get stuck or stack corruption 
might occur.

  [Test]
  Generate data with ipmitool:
  for i in {1..100}; do sudo ipmitool sensor list; done
  for i in {1..100}; do sudo ipmitool mc info; done

  [Fix]
  88b4116e7e98 i2c: xlp9xx: Make sure the transfer size is not more than 
I2C_SMBUS_BLOCK_SIZE
  8d504d804ab6 i2c: xlp9xx: Fix issue seen when updating receive length

  
  [Regression Potential]
  The driver is limited to ThunderX2 hardware, and bug fixes to this driver 
does not have any impact on other platforms. There for risk for regression is 
low.

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

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

[Kernel-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Thomas Diesenreiter]

Ad CHristopher: Maybe you read my last comment wrong? The latest kernel
did fix the bug, so the bug can get closed now, in my humble opinion.

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP

[Mario Limonciello]

The first 2 I have no concerns, but would like to see a tested-by
submitted back to that patch to encourage it to land upstream.

The third patch, there has been a second submission (and will likely be a 3rd 
based on feedback).
https://patchwork.kernel.org/patch/10522375/

Conceptually I have no concern with the 3rd patch but just please track
to make sure the right policy does get adopted from it.

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

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leading to other devices not getting there during long idle or s2idle. 
And it also prevents the system from entering deeper PC state other than PC3.

  [Test]
  Verified the power consumption on some new platforms, it doesn't do too much 
difference on the numbers, but it improves.

  [Fix]
  Suggested from Intel and Dell to contains the 2 commits
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/

  The third commit sets by default link power management policy to min_power
  https://patchwork.kernel.org/patch/10502291/

  [Regression Potential]
  Low, the production machines with suspend-to-idle enabled should have the 
DEVSLP function been validated.

  [Misc]
  Those commits do not show up in any public git tree yet, so let's verify
  them in oem kernel first, and then will submit to bionic kernel later.

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

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

[Kernel-packages] [Bug 1781476] Re: bug fixes that improve stability of the ThunderX2 i2c driver

[Manoj Iyer]

** Description changed:

  [Impact]
  With ThunderX2 i2c driver, ipmi transfers may get stuck or stack corruption 
might occur.
  
  [Test]
+ Generate data with ipmitool:
+ for i in {1..100}; do sudo ipmitool sensor list; done
+ for i in {1..100}; do sudo ipmitool mc info; done
  
  [Fix]
+ 88b4116e7e98 i2c: xlp9xx: Make sure the transfer size is not more than 
I2C_SMBUS_BLOCK_SIZE
+ 8d504d804ab6 i2c: xlp9xx: Fix issue seen when updating receive length
+ 
  
  [Regression Potential]
  The driver is limited to ThunderX2 hardware, and bug fixes to this driver 
does not have any impact on other platforms. There for risk for regression is 
low.

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

Title:
  [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  With ThunderX2 i2c driver, ipmi transfers may get stuck or stack corruption 
might occur.

  [Test]
  Generate data with ipmitool:
  for i in {1..100}; do sudo ipmitool sensor list; done
  for i in {1..100}; do sudo ipmitool mc info; done

  [Fix]
  88b4116e7e98 i2c: xlp9xx: Make sure the transfer size is not more than 
I2C_SMBUS_BLOCK_SIZE
  8d504d804ab6 i2c: xlp9xx: Fix issue seen when updating receive length

  
  [Regression Potential]
  The driver is limited to ThunderX2 hardware, and bug fixes to this driver 
does not have any impact on other platforms. There for risk for regression is 
low.

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

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

[Kernel-packages] [Bug 1779377] Re: linux-aws: 4.4.0-1025.26 -proposed tracker

[Łukasz Zemczak]

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

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

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

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

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

Bug description:
  This bug is for tracking the  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: 1779376
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1781066] Re: linux-azure: 4.15.0-1017.17 -proposed tracker

[Brad Figg]

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow 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: 1781433
  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/1781066/+subscriptions

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

[Kernel-packages] [Bug 1781435] Re: linux-aws: 4.15.0-1015.15 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

Title:
  linux-aws: 4.15.0-1015.15 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1773392] Re: zfs hangs on mount/unmount

[Colin Ian King]

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

** This bug has been marked a duplicate of bug 1781364
   Kernel error "task zfs:pid blocked for more than 120 seconds"

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

Title:
  zfs hangs on mount/unmount

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

Bug description:
  I am running lxd 3.0 on ubuntu 18.04 with kernel 4.15.0-22-generic and
  4.15.0-20-generic (same behaviour) with zfs backend (0.7.5-1ubuntu16;
  also tried 0.7.9).

  Sometimes lxd hangs when I try to stop / restart or "stop && move"
  some containers. Furhter investigation showed that problem is in zfs
  mount or unmount: it just hangs and lxd just wait it. Also commands
  like "zfs list" hangs to.

  It seems that it is not lxd or zfs issue, but kernel bug?
  https://github.com/lxc/lxd/issues/4104#issuecomment-392072939

  I have one test ct that always hangs on restart, so here is info:

  dmesg:
  [ 1330.390938] INFO: task txg_sync:9944 blocked for more than 120 seconds.
  [ 1330.390994]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.391044] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.391101] txg_syncD0  9944  2 0x8000
  [ 1330.391105] Call Trace:
  [ 1330.391117]  __schedule+0x297/0x8b0
  [ 1330.391122]  schedule+0x2c/0x80
  [ 1330.391136]  cv_wait_common+0x11e/0x140 [spl]
  [ 1330.391141]  ? wait_woken+0x80/0x80
  [ 1330.391152]  __cv_wait+0x15/0x20 [spl]
  [ 1330.391234]  rrw_enter_write+0x3c/0xa0 [zfs]
  [ 1330.391306]  rrw_enter+0x13/0x20 [zfs]
  [ 1330.391380]  spa_sync+0x7c9/0xd80 [zfs]
  [ 1330.391457]  txg_sync_thread+0x2cd/0x4a0 [zfs]
  [ 1330.391534]  ? txg_quiesce_thread+0x3d0/0x3d0 [zfs]
  [ 1330.391543]  thread_generic_wrapper+0x74/0x90 [spl]
  [ 1330.391549]  kthread+0x121/0x140
  [ 1330.391558]  ? __thread_exit+0x20/0x20 [spl]
  [ 1330.391562]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 1330.391566]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 1330.391569]  ret_from_fork+0x35/0x40
  [ 1330.391582] INFO: task lxd:12419 blocked for more than 120 seconds.
  [ 1330.391630]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.391679] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.391735] lxd D0 12419  1 0x
  [ 1330.391739] Call Trace:
  [ 1330.391745]  __schedule+0x297/0x8b0
  [ 1330.391749]  schedule+0x2c/0x80
  [ 1330.391752]  rwsem_down_write_failed+0x162/0x360
  [ 1330.391808]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [ 1330.391814]  call_rwsem_down_write_failed+0x17/0x30
  [ 1330.391817]  ? call_rwsem_down_write_failed+0x17/0x30
  [ 1330.391821]  down_write+0x2d/0x40
  [ 1330.391825]  grab_super+0x30/0x90
  [ 1330.391901]  ? zpl_create+0x160/0x160 [zfs]
  [ 1330.391905]  sget_userns+0x91/0x490
  [ 1330.391908]  ? get_anon_bdev+0x100/0x100
  [ 1330.391983]  ? zpl_create+0x160/0x160 [zfs]
  [ 1330.391987]  sget+0x7d/0xa0
  [ 1330.391990]  ? get_anon_bdev+0x100/0x100
  [ 1330.392066]  zpl_mount+0xa8/0x160 [zfs]
  [ 1330.392071]  mount_fs+0x37/0x150
  [ 1330.392077]  vfs_kern_mount.part.23+0x5d/0x110
  [ 1330.392080]  do_mount+0x5ed/0xce0
  [ 1330.392083]  ? copy_mount_options+0x2c/0x220
  [ 1330.392086]  SyS_mount+0x98/0xe0
  [ 1330.392092]  do_syscall_64+0x73/0x130
  [ 1330.392096]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1330.392099] RIP: 0033:0x4db36a
  [ 1330.392101] RSP: 002b:00c4207fa768 EFLAGS: 0216 ORIG_RAX: 
00a5
  [ 1330.392104] RAX: ffda RBX:  RCX: 
004db36a
  [ 1330.392106] RDX: 00c4205984cc RSI: 00c420a6ee00 RDI: 
00c420a23b60
  [ 1330.392108] RBP: 00c4207fa808 R08: 00c4209d4960 R09: 

  [ 1330.392110] R10:  R11: 0216 R12: 

  [ 1330.392112] R13: 0039 R14: 0038 R15: 
0080
  [ 1330.392123] INFO: task lxd:16725 blocked for more than 120 seconds.
  [ 1330.392171]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.392220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.392276] lxd D0 16725  1 0x0002
  [ 1330.392279] Call Trace:
  [ 1330.392284]  __schedule+0x297/0x8b0
  [ 1330.392289]  ? irq_work_queue+0x8d/0xa0
  [ 1330.392293]  schedule+0x2c/0x80
  [ 1330.392297]  io_schedule+0x16/0x40
  [ 1330.392302]  wait_on_page_bit_common+0xd8/0x160
  [ 1330.392305]  ? page_cache_tree_insert+0xe0/0xe0
  [ 1330.392309]  __filemap_fdatawait_range+0xfa/0x160
  [ 1330.392313]  ? _cond_resched+0x19/0x40
  [ 1330.392317]  ? bdi_split_work_to_wbs+0x45/0x2c0
  [ 1330.392321]  ? _cond_resched+0x19/0x40
  [ 1330.392324]  filemap_fdatawait_keep_errors+0x1e/0x40
  [ 

[Kernel-packages] [Bug 1779379] Re: linux-aws: 4.4.0-1063.72 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel error "task zfs:pid blocked for more than 120 seconds"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Committed
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, XENIAL, BIONIC ==

  Exercising ZFS with lxd with many mount/umounts can cause lockups and
  120 second timeout messages.

  == How to reproduce bug ==

  In a VM, 2 CPUs, 16GB of memory running Bionic:

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux
  sudo lxd init

  (and with the default init options)

  then run:

  lxd-benchmark launch --count 96 --parallel 96

  This will reliably show the lockup every time without the fix.  With
  the fix (detailed below) one cannot reproduce the lockup.

  == Fix ==

  Upstream ZFS commit

  commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1
  Author: Brian Behlendorf 
  Date: Wed Jul 11 15:49:10 2018 -0700

  Fix zpl_mount() deadlock

  == Regression Potential ==

  This just changes the locking in the mount path of ZFS and will only
  affect ZFS mount/unmounts.  The regression potential is small as this
  touches a very small code path that has been exhaustively exercises
  this code under multiple thread/CPU contention and shown not to break.

  --

  ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691

  "I am using LXD containers that are configured to use a ZFS storage backend.
  I create many containers using a benchmark tool, which probably stresses the 
use of ZFS.
  In two out of four attempts, I got

  [  725.970508] INFO: task lxd:4455 blocked for more than 120 seconds.
  [  725.976730]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds.
  [  725.998264]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.013313] INFO: task lxd:99919 blocked for more than 120 seconds.
  [  726.019609]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.034560] INFO: task zfs:100513 blocked for more than 120 seconds.
  [  726.040936]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.055791] INFO: task zfs:100584 blocked for more than 120 seconds.
  [  726.062170]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  Describe how to reproduce the problem

  Start an Ubuntu 18.04 LTS server.
  Install LXD if not already installed.

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux

  Configure LXD with sudo lxd init. When prompted for the storage
  backend, select ZFS and specify an empty disk.

  $ sudo lxd init
  Would you like to use LXD clustering? (yes/no) [default=no]:
   Do you want to configure a new storage pool? (yes/no) [default=yes]:
   Name of the new storage pool [default=default]:
   Name of the storage backend to use (dir, zfs) [default=zfs]:
   Create a new ZFS pool? (yes/no) [default=yes]:
   Would you like to use an existing block device? (yes/no) [default=no]: yes
   Path to the existing block device: /dev/sdb
   Would you like to connect to a MAAS server? (yes/no) [default=no]:
   Would you like to create a new local network bridge? (yes/no) [default=yes]: 
no
   Would you like to configure LXD to use an existing bridge or host interface? 
(yes/no) [default=no]: no
   Would you like LXD to be available over the network? (yes/no) [default=no]:
   Would you like stale cached images to be updated automatically? (yes/no) 
[default=yes]
   Would you like a YAML "lxd init" preseed to be printed? (yes/no) 
[default=no]:

  Now run the following to launch 48 containers in batches of 12.

  lxd-benchmark launch --count 48 --parallel 12

  In two out of four attempts, I got the kernel errors.

  I also tried

  echo 1 >/sys/module/spl/parameters/spl_taskq_kick

  but did 

[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel error "task zfs:pid blocked for more than 120 seconds"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Committed
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, XENIAL, BIONIC ==

  Exercising ZFS with lxd with many mount/umounts can cause lockups and
  120 second timeout messages.

  == How to reproduce bug ==

  In a VM, 2 CPUs, 16GB of memory running Bionic:

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux
  sudo lxd init

  (and with the default init options)

  then run:

  lxd-benchmark launch --count 96 --parallel 96

  This will reliably show the lockup every time without the fix.  With
  the fix (detailed below) one cannot reproduce the lockup.

  == Fix ==

  Upstream ZFS commit

  commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1
  Author: Brian Behlendorf 
  Date: Wed Jul 11 15:49:10 2018 -0700

  Fix zpl_mount() deadlock

  == Regression Potential ==

  This just changes the locking in the mount path of ZFS and will only
  affect ZFS mount/unmounts.  The regression potential is small as this
  touches a very small code path that has been exhaustively exercises
  this code under multiple thread/CPU contention and shown not to break.

  --

  ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691

  "I am using LXD containers that are configured to use a ZFS storage backend.
  I create many containers using a benchmark tool, which probably stresses the 
use of ZFS.
  In two out of four attempts, I got

  [  725.970508] INFO: task lxd:4455 blocked for more than 120 seconds.
  [  725.976730]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds.
  [  725.998264]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.013313] INFO: task lxd:99919 blocked for more than 120 seconds.
  [  726.019609]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.034560] INFO: task zfs:100513 blocked for more than 120 seconds.
  [  726.040936]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.055791] INFO: task zfs:100584 blocked for more than 120 seconds.
  [  726.062170]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  Describe how to reproduce the problem

  Start an Ubuntu 18.04 LTS server.
  Install LXD if not already installed.

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux

  Configure LXD with sudo lxd init. When prompted for the storage
  backend, select ZFS and specify an empty disk.

  $ sudo lxd init
  Would you like to use LXD clustering? (yes/no) [default=no]:
   Do you want to configure a new storage pool? (yes/no) [default=yes]:
   Name of the new storage pool [default=default]:
   Name of the storage backend to use (dir, zfs) [default=zfs]:
   Create a new ZFS pool? (yes/no) [default=yes]:
   Would you like to use an existing block device? (yes/no) [default=no]: yes
   Path to the existing block device: /dev/sdb
   Would you like to connect to a MAAS server? (yes/no) [default=no]:
   Would you like to create a new local network bridge? (yes/no) [default=yes]: 
no
   Would you like to configure LXD to use an existing bridge or host interface? 
(yes/no) [default=no]: no
   Would you like LXD to be available over the network? (yes/no) [default=no]:
   Would you like stale cached images to be updated automatically? (yes/no) 
[default=yes]
   Would you like a YAML "lxd init" preseed to be printed? (yes/no) 
[default=no]:

  Now run the following to launch 48 containers in batches of 12.

  lxd-benchmark launch --count 48 --parallel 12

  In two out of four attempts, I got the kernel errors.

  I also tried

  echo 1 >/sys/module/spl/parameters/spl_taskq_kick

  but did 

[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel error "task zfs:pid blocked for more than 120 seconds"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Committed
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, XENIAL, BIONIC ==

  Exercising ZFS with lxd with many mount/umounts can cause lockups and
  120 second timeout messages.

  == How to reproduce bug ==

  In a VM, 2 CPUs, 16GB of memory running Bionic:

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux
  sudo lxd init

  (and with the default init options)

  then run:

  lxd-benchmark launch --count 96 --parallel 96

  This will reliably show the lockup every time without the fix.  With
  the fix (detailed below) one cannot reproduce the lockup.

  == Fix ==

  Upstream ZFS commit

  commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1
  Author: Brian Behlendorf 
  Date: Wed Jul 11 15:49:10 2018 -0700

  Fix zpl_mount() deadlock

  == Regression Potential ==

  This just changes the locking in the mount path of ZFS and will only
  affect ZFS mount/unmounts.  The regression potential is small as this
  touches a very small code path that has been exhaustively exercises
  this code under multiple thread/CPU contention and shown not to break.

  --

  ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691

  "I am using LXD containers that are configured to use a ZFS storage backend.
  I create many containers using a benchmark tool, which probably stresses the 
use of ZFS.
  In two out of four attempts, I got

  [  725.970508] INFO: task lxd:4455 blocked for more than 120 seconds.
  [  725.976730]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds.
  [  725.998264]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.013313] INFO: task lxd:99919 blocked for more than 120 seconds.
  [  726.019609]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.034560] INFO: task zfs:100513 blocked for more than 120 seconds.
  [  726.040936]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.055791] INFO: task zfs:100584 blocked for more than 120 seconds.
  [  726.062170]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  Describe how to reproduce the problem

  Start an Ubuntu 18.04 LTS server.
  Install LXD if not already installed.

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux

  Configure LXD with sudo lxd init. When prompted for the storage
  backend, select ZFS and specify an empty disk.

  $ sudo lxd init
  Would you like to use LXD clustering? (yes/no) [default=no]:
   Do you want to configure a new storage pool? (yes/no) [default=yes]:
   Name of the new storage pool [default=default]:
   Name of the storage backend to use (dir, zfs) [default=zfs]:
   Create a new ZFS pool? (yes/no) [default=yes]:
   Would you like to use an existing block device? (yes/no) [default=no]: yes
   Path to the existing block device: /dev/sdb
   Would you like to connect to a MAAS server? (yes/no) [default=no]:
   Would you like to create a new local network bridge? (yes/no) [default=yes]: 
no
   Would you like to configure LXD to use an existing bridge or host interface? 
(yes/no) [default=no]: no
   Would you like LXD to be available over the network? (yes/no) [default=no]:
   Would you like stale cached images to be updated automatically? (yes/no) 
[default=yes]
   Would you like a YAML "lxd init" preseed to be printed? (yes/no) 
[default=no]:

  Now run the following to launch 48 containers in batches of 12.

  lxd-benchmark launch --count 48 --parallel 12

  In two out of four attempts, I got the kernel errors.

  I also tried

  echo 1 >/sys/module/spl/parameters/spl_taskq_kick

  but 

[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel error "task zfs:pid blocked for more than 120 seconds"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Committed
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, XENIAL, BIONIC ==

  Exercising ZFS with lxd with many mount/umounts can cause lockups and
  120 second timeout messages.

  == How to reproduce bug ==

  In a VM, 2 CPUs, 16GB of memory running Bionic:

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux
  sudo lxd init

  (and with the default init options)

  then run:

  lxd-benchmark launch --count 96 --parallel 96

  This will reliably show the lockup every time without the fix.  With
  the fix (detailed below) one cannot reproduce the lockup.

  == Fix ==

  Upstream ZFS commit

  commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1
  Author: Brian Behlendorf 
  Date: Wed Jul 11 15:49:10 2018 -0700

  Fix zpl_mount() deadlock

  == Regression Potential ==

  This just changes the locking in the mount path of ZFS and will only
  affect ZFS mount/unmounts.  The regression potential is small as this
  touches a very small code path that has been exhaustively exercises
  this code under multiple thread/CPU contention and shown not to break.

  --

  ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691

  "I am using LXD containers that are configured to use a ZFS storage backend.
  I create many containers using a benchmark tool, which probably stresses the 
use of ZFS.
  In two out of four attempts, I got

  [  725.970508] INFO: task lxd:4455 blocked for more than 120 seconds.
  [  725.976730]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds.
  [  725.998264]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.013313] INFO: task lxd:99919 blocked for more than 120 seconds.
  [  726.019609]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.034560] INFO: task zfs:100513 blocked for more than 120 seconds.
  [  726.040936]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.055791] INFO: task zfs:100584 blocked for more than 120 seconds.
  [  726.062170]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  Describe how to reproduce the problem

  Start an Ubuntu 18.04 LTS server.
  Install LXD if not already installed.

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux

  Configure LXD with sudo lxd init. When prompted for the storage
  backend, select ZFS and specify an empty disk.

  $ sudo lxd init
  Would you like to use LXD clustering? (yes/no) [default=no]:
   Do you want to configure a new storage pool? (yes/no) [default=yes]:
   Name of the new storage pool [default=default]:
   Name of the storage backend to use (dir, zfs) [default=zfs]:
   Create a new ZFS pool? (yes/no) [default=yes]:
   Would you like to use an existing block device? (yes/no) [default=no]: yes
   Path to the existing block device: /dev/sdb
   Would you like to connect to a MAAS server? (yes/no) [default=no]:
   Would you like to create a new local network bridge? (yes/no) [default=yes]: 
no
   Would you like to configure LXD to use an existing bridge or host interface? 
(yes/no) [default=no]: no
   Would you like LXD to be available over the network? (yes/no) [default=no]:
   Would you like stale cached images to be updated automatically? (yes/no) 
[default=yes]
   Would you like a YAML "lxd init" preseed to be printed? (yes/no) 
[default=no]:

  Now run the following to launch 48 containers in batches of 12.

  lxd-benchmark launch --count 48 --parallel 12

  In two out of four attempts, I got the kernel errors.

  I also tried

  echo 1 >/sys/module/spl/parameters/spl_taskq_kick

  but 

[Kernel-packages] [Bug 1781413] Re: Cannot set MTU higher than 1500 in Xen instance

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Cannot set MTU higher than 1500 in Xen instance

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  The latest Xenial update has broken MTU functionality in Xen: specifically, 
  setting MTUs larger than 1500 fails. This prevents Jumbo Frames and other 
  features which require larger than 1500 byte MTUs from being used. This can 
  lead to a failure to sync/connect to other components in the cluster/cloud
  which expect higher MTUs and result in unavailable services. 

  This can be worked around by manually using ethtool to set SCATTER/GATHER
  functionality:
  - $ sudo ethtool -K $interface_name sg on 

  
  The issue is caused by the following commit to the xen-netfront driver:
  "xen-netfront: Fix race between device setup and open"
  commit f599c64fdf7d9c108e8717fb04bc41c680120da4
  Introduced: v4.16-rc1

  Reverting the above fix has confirmed that the problem goes away.

  The following commits fix this issue in the mainline kernel:

  "xen-netfront: Fix mismatched rtnl_unlock"
  commit cb257783c2927b73614b20f915a91ff78aa6f3e8
  Introduced: v4.18-rc3
  "xen-netfront: Update features after registering netdev"
  commit 45c8184c1bed1ca8a7f02918552063a00b909bf5
  Introduced: v4.18-rc3

  
  [Test Case]
  1. Launch a Xen instance using the latest kernel version (e.g. 4.4.0-130,
  or  4.4.0-1062-aws)
  2. Change MTU to 9000 or other value > 1500. 

  [Regression Potential]
  The kernel patch might not be able to set MTU.

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

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

[Kernel-packages] [Bug 1781115] Re: linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  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/1781115/+subscriptions

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

[Kernel-packages] [Bug 1781413] Re: Cannot set MTU higher than 1500 in Xen instance

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-bionic

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

Title:
  Cannot set MTU higher than 1500 in Xen instance

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  The latest Xenial update has broken MTU functionality in Xen: specifically, 
  setting MTUs larger than 1500 fails. This prevents Jumbo Frames and other 
  features which require larger than 1500 byte MTUs from being used. This can 
  lead to a failure to sync/connect to other components in the cluster/cloud
  which expect higher MTUs and result in unavailable services. 

  This can be worked around by manually using ethtool to set SCATTER/GATHER
  functionality:
  - $ sudo ethtool -K $interface_name sg on 

  
  The issue is caused by the following commit to the xen-netfront driver:
  "xen-netfront: Fix race between device setup and open"
  commit f599c64fdf7d9c108e8717fb04bc41c680120da4
  Introduced: v4.16-rc1

  Reverting the above fix has confirmed that the problem goes away.

  The following commits fix this issue in the mainline kernel:

  "xen-netfront: Fix mismatched rtnl_unlock"
  commit cb257783c2927b73614b20f915a91ff78aa6f3e8
  Introduced: v4.18-rc3
  "xen-netfront: Update features after registering netdev"
  commit 45c8184c1bed1ca8a7f02918552063a00b909bf5
  Introduced: v4.18-rc3

  
  [Test Case]
  1. Launch a Xen instance using the latest kernel version (e.g. 4.4.0-130,
  or  4.4.0-1062-aws)
  2. Change MTU to 9000 or other value > 1500. 

  [Regression Potential]
  The kernel patch might not be able to set MTU.

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

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

[Kernel-packages] [Bug 1781433] Re: linux: 4.15.0-28.30 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 
(azure), bug 1781074 (azure-edge), bug 1781115 (gcp)
  derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), 
bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem)
- kernel-stable-phase-changed:Thursday, 12. July 2018 18:03 UTC
- kernel-stable-phase:Uploaded
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 13. July 2018 14:08 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 
(azure), bug 1781074 (azure-edge), bug 1781115 (gcp)
  derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), 
bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem)
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 13. July 2018 14:08 UTC
+ bugs-spammed: true
+ 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1781433

Title:
  linux: 4.15.0-28.30 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 
(azure), bug 1781074 (azure-edge), bug 1781115 (gcp)
  derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), 
bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem)
  -- 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/1781433/+subscriptions

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

[Kernel-packages] [Bug 1779376] Re: linux: 4.4.0-131.157 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon)
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 12. July 2018 16:02 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 13. July 2018 14:04 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 13. July 2018 14:04 UTC
+ bugs-spammed: true
+ 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1779376

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

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

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

  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (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/1779376/+subscriptions

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

[Kernel-packages] [Bug 1781066] Re: linux-azure: 4.15.0-1017.17 -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

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

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

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 13. July 2018 14:01 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 13. July 2018 14:01 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1781066

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow 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: 1781433
  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/1781066/+subscriptions

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

[Kernel-packages] [Bug 1779377] Re: linux-aws: 4.4.0-1025.26 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed

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

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

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

Bug description:
  This bug is for tracking the  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: 1779376
  phase: Uploaded

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

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

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

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

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

Title:
  Stress-testing LXD causes kernel hung in cgroups (cgroup_destroy
  css_killed_work_fn)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have been stress-testing LXD and managed to cause the following
  kernel hung:

  [10271.564074] INFO: task systemd:1 blocked for more than 120 seconds.
  [10271.570397]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
  [10271.577212] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10271.585071] systemd D0 1  0 0x
  [10271.585073] Call Trace:
  [10271.585080]  __schedule+0x297/0x8b0
  [10271.585086]  schedule+0x2c/0x80
  [10271.585090]  schedule_preempt_disabled+0xe/0x10
  [10271.585095]  __mutex_lock.isra.2+0x18c/0x4d0
  [10271.585100]  __mutex_lock_slowpath+0x13/0x20
  [10271.585101]  ? __mutex_lock_slowpath+0x13/0x20
  [10271.585102]  mutex_lock+0x2f/0x40
  [10271.585106]  proc_cgroup_show+0x4c/0x2a0
  [10271.585108]  proc_single_show+0x56/0x80
  [10271.585111]  seq_read+0xe5/0x430
  [10271.585114]  __vfs_read+0x1b/0x40
  [10271.585115]  vfs_read+0x8e/0x130
  [10271.585117]  SyS_read+0x55/0xc0
  [10271.585120]  do_syscall_64+0x73/0x130
  [10271.585121]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [10271.585123] RIP: 0033:0x7fd47634d0b4
  [10271.585124] RSP: 002b:7ffe9a186700 EFLAGS: 0246 ORIG_RAX: 

  [10271.585125] RAX: ffda RBX: 0021 RCX: 
7fd47634d0b4
  [10271.585126] RDX: 0400 RSI: 55f70a08c0c0 RDI: 
0021
  [10271.585127] RBP: 55f70a08c0c0 R08:  R09: 

  [10271.585128] R10:  R11: 0246 R12: 
0400
  [10271.585129] R13: 7fd4766252a0 R14: 55f70a0298e0 R15: 
07ff
  [10271.585221] INFO: task lxcfs:84510 blocked for more than 120 seconds.
  [10271.591687]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
  [10271.598531] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10271.606401] lxcfs   D0 84510  1 0x
  [10271.606407] Call Trace:
  [10271.606416]  __schedule+0x297/0x8b0
  [10271.606418]  schedule+0x2c/0x80
  [10271.606420]  schedule_preempt_disabled+0xe/0x10
  [10271.606421]  __mutex_lock.isra.2+0x18c/0x4d0
  [10271.606423]  __mutex_lock_slowpath+0x13/0x20
  [10271.606424]  ? __mutex_lock_slowpath+0x13/0x20
  [10271.606425]  mutex_lock+0x2f/0x40
  [10271.606427]  proc_cgroup_show+0x4c/0x2a0
  [10271.606429]  proc_single_show+0x56/0x80
  [10271.606432]  seq_read+0xe5/0x430
  [10271.606434]  __vfs_read+0x1b/0x40
  [10271.606436]  vfs_read+0x8e/0x130
  [10271.606437]  SyS_read+0x55/0xc0
  [10271.606440]  do_syscall_64+0x73/0x130
  [10271.606441]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [10271.606443] RIP: 0033:0x7f1a50e700b4
  [10271.606443] RSP: 002b:7f1a2b7fd870 EFLAGS: 0246 ORIG_RAX: 

  [10271.606445] RAX: ffda RBX: 0013 RCX: 
7f1a50e700b4
  [10271.606446] RDX: 0400 RSI: 7f1a04000f90 RDI: 
0013
  [10271.606446] RBP: 7f1a04000f90 R08: 0001 R09: 

  [10271.606447] R10:  R11: 0246 R12: 
0400
  [10271.606448] R13: 7f1a511482a0 R14:  R15: 
7f1a38003a40
  [10271.606450] INFO: task lxcfs:84676 blocked for more than 120 seconds.
  [10271.612911]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
  [10271.619722] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10271.627577] lxcfs   D0 84676  1 0x
  [10271.627579] Call Trace:
  [10271.627583]  __schedule+0x297/0x8b0
  [10271.627589]  schedule+0x2c/0x80
  [10271.627594]  schedule_preempt_disabled+0xe/0x10
  [10271.627598]  __mutex_lock.isra.2+0x18c/0x4d0
  [10271.627600]  __mutex_lock_slowpath+0x13/0x20
  [10271.627601]  ? __mutex_lock_slowpath+0x13/0x20
  [10271.627602]  mutex_lock+0x2f/0x40
  [10271.627604]  proc_cgroup_show+0x4c/0x2a0
  [10271.627606]  proc_single_show+0x56/0x80
  [10271.627608]  seq_read+0xe5/0x430
  [10271.627610]  __vfs_read+0x1b/0x40
  [10271.627611] 

[Kernel-packages] [Bug 1781601] [NEW] Stress-testing LXD causes kernel hung in cgroups (cgroup_destroy css_killed_work_fn)

[Simos Xenitellis ]

Public bug reported:

I have been stress-testing LXD and managed to cause the following kernel
hung:

[10271.564074] INFO: task systemd:1 blocked for more than 120 seconds.
[10271.570397]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
[10271.577212] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[10271.585071] systemd D0 1  0 0x
[10271.585073] Call Trace:
[10271.585080]  __schedule+0x297/0x8b0
[10271.585086]  schedule+0x2c/0x80
[10271.585090]  schedule_preempt_disabled+0xe/0x10
[10271.585095]  __mutex_lock.isra.2+0x18c/0x4d0
[10271.585100]  __mutex_lock_slowpath+0x13/0x20
[10271.585101]  ? __mutex_lock_slowpath+0x13/0x20
[10271.585102]  mutex_lock+0x2f/0x40
[10271.585106]  proc_cgroup_show+0x4c/0x2a0
[10271.585108]  proc_single_show+0x56/0x80
[10271.585111]  seq_read+0xe5/0x430
[10271.585114]  __vfs_read+0x1b/0x40
[10271.585115]  vfs_read+0x8e/0x130
[10271.585117]  SyS_read+0x55/0xc0
[10271.585120]  do_syscall_64+0x73/0x130
[10271.585121]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[10271.585123] RIP: 0033:0x7fd47634d0b4
[10271.585124] RSP: 002b:7ffe9a186700 EFLAGS: 0246 ORIG_RAX: 

[10271.585125] RAX: ffda RBX: 0021 RCX: 7fd47634d0b4
[10271.585126] RDX: 0400 RSI: 55f70a08c0c0 RDI: 0021
[10271.585127] RBP: 55f70a08c0c0 R08:  R09: 
[10271.585128] R10:  R11: 0246 R12: 0400
[10271.585129] R13: 7fd4766252a0 R14: 55f70a0298e0 R15: 07ff
[10271.585221] INFO: task lxcfs:84510 blocked for more than 120 seconds.
[10271.591687]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
[10271.598531] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[10271.606401] lxcfs   D0 84510  1 0x
[10271.606407] Call Trace:
[10271.606416]  __schedule+0x297/0x8b0
[10271.606418]  schedule+0x2c/0x80
[10271.606420]  schedule_preempt_disabled+0xe/0x10
[10271.606421]  __mutex_lock.isra.2+0x18c/0x4d0
[10271.606423]  __mutex_lock_slowpath+0x13/0x20
[10271.606424]  ? __mutex_lock_slowpath+0x13/0x20
[10271.606425]  mutex_lock+0x2f/0x40
[10271.606427]  proc_cgroup_show+0x4c/0x2a0
[10271.606429]  proc_single_show+0x56/0x80
[10271.606432]  seq_read+0xe5/0x430
[10271.606434]  __vfs_read+0x1b/0x40
[10271.606436]  vfs_read+0x8e/0x130
[10271.606437]  SyS_read+0x55/0xc0
[10271.606440]  do_syscall_64+0x73/0x130
[10271.606441]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[10271.606443] RIP: 0033:0x7f1a50e700b4
[10271.606443] RSP: 002b:7f1a2b7fd870 EFLAGS: 0246 ORIG_RAX: 

[10271.606445] RAX: ffda RBX: 0013 RCX: 7f1a50e700b4
[10271.606446] RDX: 0400 RSI: 7f1a04000f90 RDI: 0013
[10271.606446] RBP: 7f1a04000f90 R08: 0001 R09: 
[10271.606447] R10:  R11: 0246 R12: 0400
[10271.606448] R13: 7f1a511482a0 R14:  R15: 7f1a38003a40
[10271.606450] INFO: task lxcfs:84676 blocked for more than 120 seconds.
[10271.612911]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
[10271.619722] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[10271.627577] lxcfs   D0 84676  1 0x
[10271.627579] Call Trace:
[10271.627583]  __schedule+0x297/0x8b0
[10271.627589]  schedule+0x2c/0x80
[10271.627594]  schedule_preempt_disabled+0xe/0x10
[10271.627598]  __mutex_lock.isra.2+0x18c/0x4d0
[10271.627600]  __mutex_lock_slowpath+0x13/0x20
[10271.627601]  ? __mutex_lock_slowpath+0x13/0x20
[10271.627602]  mutex_lock+0x2f/0x40
[10271.627604]  proc_cgroup_show+0x4c/0x2a0
[10271.627606]  proc_single_show+0x56/0x80
[10271.627608]  seq_read+0xe5/0x430
[10271.627610]  __vfs_read+0x1b/0x40
[10271.627611]  vfs_read+0x8e/0x130
[10271.627613]  SyS_read+0x55/0xc0
[10271.627615]  do_syscall_64+0x73/0x130
[10271.627617]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[10271.627618] RIP: 0033:0x7f1a50e700b4
[10271.627618] RSP: 002b:7f1a297f9870 EFLAGS: 0246 ORIG_RAX: 

[10271.627620] RAX: ffda RBX: 0014 RCX: 7f1a50e700b4
[10271.627620] RDX: 0400 RSI: 7f1a2c001e80 RDI: 0014
[10271.627621] RBP: 7f1a2c001e80 R08: 0001 R09: 
[10271.627622] R10:  R11: 0246 R12: 0400
[10271.627622] R13: 7f1a511482a0 R14:  R15: 7f1a2c002b10
[10271.627625] INFO: task lxcfs:115507 blocked for more than 120 seconds.
[10271.634180]   Tainted: P   OE4.15.0-20-generic #21-Ubuntu
[10271.641007] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[10271.648870] lxcfs   D0 115507  1 0x
[10271.648872] Call Trace:
[10271.648876]  __schedule+0x297/0x8b0
[10271.648883]  schedule+0x2c/0x80

[Kernel-packages] [Bug 1781115] Re: linux-gcp: 4.15.0-1013.13~16.04.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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 13. July 2018 13:04 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 13. July 2018 13:04 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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1781115

Title:
  linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  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/1781115/+subscriptions

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

[Kernel-packages] [Bug 1779379] Re: linux-aws: 4.4.0-1063.72 -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

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

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

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

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

** 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779376
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 13. July 2018 13:03 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779376
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 13. July 2018 13:03 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1779379

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

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

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

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

[Kernel-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Christopher M. Penalver]

Thomas Diesenreiter:

1) Given the Proposed kernel didn't resolve the issue, this is not a
duplicate of LP#1773520. Hence, to keep this relevant to upstream, one
would want to periodically check for, and test the latest mainline
kernel (now 4.18-rc4) as it is released.

Could you please advise?

2) If reproducible in latest mainline, could you please test drm-tip?

3) If reproducible in drm-tip, could you please confirm the regression
commit following
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771204/comments/10
? The article was written for people who don't know anything about
linux, so it is easy to follow.

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Kernel-packages] [Bug 1779377] Re: linux-aws: 4.4.0-1025.26 -proposed tracker

[Brad Figg]

** 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 --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1779376
  phase: Uploaded

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

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

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

Bug description:
  This bug is for tracking the  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: 1779376
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1780872] Re: wake on lan is not working

[Andreas Hasenack]

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

Title:
  wake on lan is not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm dual-booting Ubuntu 18.04 and Windows 10. If I turn off my
  computer with Windows, I can turn it back on using wol. However, if I
  turn it off using Ubuntu the computer won't turn back on if I use wol.

  These are my network cards:

  ```
  ignacio@ignacio-XPS-8930:~$ ifconfig 
  docker0: flags=4163  mtu 1500
  inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
  inet6 fe80::42:e4ff:fe0a:9fee  prefixlen 64  scopeid 0x20
  ether 02:42:e4:0a:9f:ee  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 165  bytes 24102 (24.1 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enp4s0: flags=4163  mtu 1500
  inet 192.168.86.31  netmask 255.255.255.0  broadcast 192.168.86.255
  inet6 fe80::955b:12c8:20b9:7645  prefixlen 64  scopeid 0x20
  ether d8:9e:f3:85:42:8a  txqueuelen 1000  (Ethernet)
  RX packets 50484  bytes 52395285 (52.3 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 29166  bytes 4575560 (4.5 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 19  

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1000  (Local Loopback)
  RX packets 1124  bytes 95423 (95.4 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 1124  bytes 95423 (95.4 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  veth66fe4e4: flags=4163  mtu 1500
  inet6 fe80::2078:3ff:feb3:2aa1  prefixlen 64  scopeid 0x20
  ether 22:78:03:b3:2a:a1  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 224  bytes 30503 (30.5 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  vethb50cc6f: flags=4163  mtu 1500
  inet6 fe80::5c0b:47ff:fef1:cfc9  prefixlen 64  scopeid 0x20
  ether 5e:0b:47:f1:cf:c9  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 125  bytes 18006 (18.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  wlp3s0: flags=4099  mtu 1500
  ether 5c:ea:1d:4c:61:a7  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  ```

  This is what ethtool tells me about my ethernet card:

  ```
  ignacio@ignacio-XPS-8930:~$ sudo ethtool enp4s0
  Settings for enp4s0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Full 
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Full 
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Current message level: 0x60e4 (24804)
   link ifup rx_err tx_err hw wol
Link detected: yes

  ```

  And this is what happens when I try to activate wake on lan:

  
  ```
  ignacio@ignacio-XPS-8930:~$ sudo ethtool -s enp4s0 wol g
  Cannot get current wake-on-lan settings: Operation not supported
not setting wol
  ```

  Finally, this is the infor about my distro:

  ```
  ignacio@ignacio-XPS-8930:~$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  ```

  Thanks for the help!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ethtool 1:4.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  9 18:58:08 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  

[Kernel-packages] [Bug 1766565] Re: Unable to insert sysdig_probe module on B-KVM kernel

[Po-Hsu Lin]

** Description changed:

- The sysdig-dkms module cannot be installed on the B-KVM kernel before
- (bug 1764693), but the installation works with 4.15.0-1007
+ The sysdig-dkms module cannot be installed on the B-KVM kernel once
+ before (bug 1764693), but now the installation works since 4.15.0-1007
  
  However, when you try to insert the module, it will complain about:
- $ sudo modprobe sysdig-probe 
+ $ sudo modprobe sysdig-probe
  modprobe: ERROR: could not insert 'sysdig_probe': Unknown symbol in module, 
or unknown parameter (see dmesg)
  
  Log in dmesg:
  [ 1989.967807] sysdig_probe: loading out-of-tree module taints kernel.
  [ 1989.967924] sysdig_probe: module verification failed: signature and/or 
required key missing - tainting kernel
  [ 1989.967986] sysdig_probe: Unknown symbol tracepoint_probe_unregister (err 
0)
  [ 1989.968090] sysdig_probe: Unknown symbol for_each_kernel_tracepoint (err 0)
  [ 1989.968094] sysdig_probe: Unknown symbol tracepoint_probe_register (err 0)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1007-kvm 4.15.0-1007.7
  ProcVersionSignature: User Name 4.15.0-1007.7-kvm 4.15.17
  Uname: Linux 4.15.0-1007-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 11:31:08 2018
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Unable to insert sysdig_probe module on B-KVM kernel

Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in sysdig package in Ubuntu:
  New

Bug description:
  The sysdig-dkms module cannot be installed on the B-KVM kernel once
  before (bug 1764693), but now the installation works since 4.15.0-1007

  However, when you try to insert the module, it will complain about:
  $ sudo modprobe sysdig-probe
  modprobe: ERROR: could not insert 'sysdig_probe': Unknown symbol in module, 
or unknown parameter (see dmesg)

  Log in dmesg:
  [ 1989.967807] sysdig_probe: loading out-of-tree module taints kernel.
  [ 1989.967924] sysdig_probe: module verification failed: signature and/or 
required key missing - tainting kernel
  [ 1989.967986] sysdig_probe: Unknown symbol tracepoint_probe_unregister (err 
0)
  [ 1989.968090] sysdig_probe: Unknown symbol for_each_kernel_tracepoint (err 0)
  [ 1989.968094] sysdig_probe: Unknown symbol tracepoint_probe_register (err 0)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1007-kvm 4.15.0-1007.7
  ProcVersionSignature: User Name 4.15.0-1007.7-kvm 4.15.17
  Uname: Linux 4.15.0-1007-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 11:31:08 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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/1766565/+subscriptions

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

[Kernel-packages] [Bug 1654517] Re: ZFS I/O hangs for minutes

[Rafael David Tinoco]

Found one in my Debian box logs:

Jun 11 10:02:37 workstation kernel: [238276.640617] INFO: task txg_sync:5936 
blocked for more than 120 seconds.
Jun 11 10:02:37 workstation kernel: [238276.643806]   Tainted: P   
O 4.16.0-2-amd64 #1 Debian 4.16.12-
Jun 11 10:02:37 workstation kernel: [238276.646803] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this m
Jun 11 10:02:37 workstation kernel: [238276.649819] txg_syncD0  
5936  2 0x8000
Jun 11 10:02:37 workstation kernel: [238276.652850] Call Trace:
Jun 11 10:02:37 workstation kernel: [238276.655776]  ? __schedule+0x291/0x870
Jun 11 10:02:37 workstation kernel: [238276.658671]  ? 
zio_taskq_dispatch+0x6f/0x90 [zfs]
Jun 11 10:02:37 workstation kernel: [238276.661196]  ? zio_nowait+0xa3/0x140 
[zfs]
Jun 11 10:02:37 workstation kernel: [238276.664199]  schedule+0x28/0x80
Jun 11 10:02:37 workstation kernel: [238276.667206]  io_schedule+0x12/0x40
Jun 11 10:02:37 workstation kernel: [238276.670226]  cv_wait_common+0xac/0x130 
[spl]
Jun 11 10:02:37 workstation kernel: [238276.673206]  ? finish_wait+0x80/0x80
Jun 11 10:02:37 workstation kernel: [238276.676522]  zio_wait+0xe6/0x1a0 [zfs]
Jun 11 10:02:37 workstation kernel: [238276.679588]  dsl_pool_sync+0xe6/0x440 
[zfs]
Jun 11 10:02:37 workstation kernel: [238276.682620]  spa_sync+0x424/0xcf0 [zfs]
Jun 11 10:02:37 workstation kernel: [238276.685657]  
txg_sync_thread+0x2ce/0x490 [zfs]
Jun 11 10:02:37 workstation kernel: [238276.688661]  ? txg_delay+0x1b0/0x1b0 
[zfs]
Jun 11 10:02:37 workstation kernel: [238276.691641]  ? __thread_exit+0x20/0x20 
[spl]
Jun 11 10:02:37 workstation kernel: [238276.694604]  
thread_generic_wrapper+0x6f/0x80 [spl]
Jun 11 10:02:37 workstation kernel: [238276.697591]  kthread+0x113/0x130
Jun 11 10:02:37 workstation kernel: [238276.700633]  ? 
kthread_create_worker_on_cpu+0x70/0x70
Jun 11 10:02:37 workstation kernel: [238276.703594]  ret_from_fork+0x22/0x40

Running zfs/spl 0.7.9-3.

I think this still happens from time to time with mainline and lates
zfs/spl (as I tested in another box). So, if its related to zfs cache
dirty ratio, then the zfs_dirty_data_sync could make cache smaller and
the sync wouldn't take so long.. if changing it doesn't solve, then its
likely an intermittent locking issue on the zio_wait logic.

Hope it helps!

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

Title:
  ZFS I/O hangs for minutes

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  I/O for multiple programs, like `thunderbird`, `firefox`, etc., hangs
  for minutes and approx. 100 `z_rd_int_[n]` and `z_wr_int_[n]` kernel
  threads are created, `dmesg` contains

  [ 9184.451606] INFO: task txg_sync:11471 blocked for more than 120 
seconds.
  [ 9184.451610]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
  [ 9184.451611] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [ 9184.451612] txg_syncD a240ab3a7aa8 0 11471  2 
0x
  [ 9184.451616]  a240ab3a7aa8 00ffbb6ade1f a24095148000 
a240e5ca5580
  [ 9184.451618]  0046 a240ab3a8000 a240ff359200 
7fff
  [ 9184.451620]  a23d36cf9050 0001 a240ab3a7ac0 
bbe96b15
  [ 9184.451621] Call Trace:
  [ 9184.451627]  [] schedule+0x35/0x80
  [ 9184.451628]  [] schedule_timeout+0x22a/0x3f0
  [ 9184.451631]  [] ? __switch_to+0x2ce/0x6c0
  [ 9184.451633]  [] ? pick_next_task_fair+0x48c/0x4c0
  [ 9184.451635]  [] ? ktime_get+0x41/0xb0
  [ 9184.451636]  [] io_schedule_timeout+0xa4/0x110
  [ 9184.451644]  [] cv_wait_common+0xb2/0x130 [spl]
  [ 9184.451646]  [] ? wake_atomic_t_function+0x60/0x60
  [ 9184.451650]  [] __cv_wait_io+0x18/0x20 [spl]
  [ 9184.451689]  [] zio_wait+0xfd/0x1d0 [zfs]
  [ 9184.451716]  [] dsl_pool_sync+0xb8/0x480 [zfs]
  [ 9184.451745]  [] spa_sync+0x37f/0xb30 [zfs]
  [ 9184.451747]  [] ? default_wake_function+0x12/0x20
  [ 9184.451779]  [] txg_sync_thread+0x3a5/0x600 [zfs]
  [ 9184.451807]  [] ? txg_delay+0x160/0x160 [zfs]
  [ 9184.451811]  [] thread_generic_wrapper+0x71/0x80 
[spl]
  [ 9184.451815]  [] ? __thread_exit+0x20/0x20 [spl]
  [ 9184.451817]  [] kthread+0xd8/0xf0
  [ 9184.451819]  [] ret_from_fork+0x1f/0x40
  [ 9184.451821]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [ 9184.451849] INFO: task mozStorage #2:21607 blocked for more than 120 
seconds.
  [ 9184.451851]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
  [ 9184.451852] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [ 9184.451853] mozStorage #2   D a23fe8a5bd38 0 21607  19750 
0x0004
  [ 9184.451855]  a23fe8a5bd38 00ffa240ee8feb40 

[Kernel-packages] [Bug 1654517] Re: ZFS I/O hangs for minutes

[Rafael David Tinoco]

Hello Colin, nope.

It looks like ZFS has some sort of contention in waiting the ZIL to
finish the async callbacks from scheduled work, even when more spindles
exist. Not sure if its related to slab merging or getting the objects
from either slab/kmalloc or directly from page allocs. I think its a
locking contention due to zfs scalability iself, to be honest :\. I'm
getting, sometimes, soft lockups here and there (all waiting on on zfs
sync - txg_wait_synced). I'm using a raid-z with 4x480G SSDs and an
extra SSD as L2ARC disk.

Its fairly easy to reproduce, i'm basically compiling kernel tress all
day in this machine, using the zfs pools as ccache's cache and as the
compiled objects repository. I haven't explored tuning it though,
considering its cache is not kept together with the pagecache (like
changing zfs_dirty_data_sync or zfs_sync_taskq_batch_pct to make zfs
cache flush less async, which might help).

Cheers!

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

Title:
  ZFS I/O hangs for minutes

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  I/O for multiple programs, like `thunderbird`, `firefox`, etc., hangs
  for minutes and approx. 100 `z_rd_int_[n]` and `z_wr_int_[n]` kernel
  threads are created, `dmesg` contains

  [ 9184.451606] INFO: task txg_sync:11471 blocked for more than 120 
seconds.
  [ 9184.451610]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
  [ 9184.451611] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [ 9184.451612] txg_syncD a240ab3a7aa8 0 11471  2 
0x
  [ 9184.451616]  a240ab3a7aa8 00ffbb6ade1f a24095148000 
a240e5ca5580
  [ 9184.451618]  0046 a240ab3a8000 a240ff359200 
7fff
  [ 9184.451620]  a23d36cf9050 0001 a240ab3a7ac0 
bbe96b15
  [ 9184.451621] Call Trace:
  [ 9184.451627]  [] schedule+0x35/0x80
  [ 9184.451628]  [] schedule_timeout+0x22a/0x3f0
  [ 9184.451631]  [] ? __switch_to+0x2ce/0x6c0
  [ 9184.451633]  [] ? pick_next_task_fair+0x48c/0x4c0
  [ 9184.451635]  [] ? ktime_get+0x41/0xb0
  [ 9184.451636]  [] io_schedule_timeout+0xa4/0x110
  [ 9184.451644]  [] cv_wait_common+0xb2/0x130 [spl]
  [ 9184.451646]  [] ? wake_atomic_t_function+0x60/0x60
  [ 9184.451650]  [] __cv_wait_io+0x18/0x20 [spl]
  [ 9184.451689]  [] zio_wait+0xfd/0x1d0 [zfs]
  [ 9184.451716]  [] dsl_pool_sync+0xb8/0x480 [zfs]
  [ 9184.451745]  [] spa_sync+0x37f/0xb30 [zfs]
  [ 9184.451747]  [] ? default_wake_function+0x12/0x20
  [ 9184.451779]  [] txg_sync_thread+0x3a5/0x600 [zfs]
  [ 9184.451807]  [] ? txg_delay+0x160/0x160 [zfs]
  [ 9184.451811]  [] thread_generic_wrapper+0x71/0x80 
[spl]
  [ 9184.451815]  [] ? __thread_exit+0x20/0x20 [spl]
  [ 9184.451817]  [] kthread+0xd8/0xf0
  [ 9184.451819]  [] ret_from_fork+0x1f/0x40
  [ 9184.451821]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [ 9184.451849] INFO: task mozStorage #2:21607 blocked for more than 120 
seconds.
  [ 9184.451851]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
  [ 9184.451852] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [ 9184.451853] mozStorage #2   D a23fe8a5bd38 0 21607  19750 
0x0004
  [ 9184.451855]  a23fe8a5bd38 00ffa240ee8feb40 a240ecf72ac0 
a2403803b900
  [ 9184.451857]  bc2c02f7 a23fe8a5c000 a240aa940828 
a240aa940800
  [ 9184.451858]  a240aa940980  a23fe8a5bd50 
bbe96b15
  [ 9184.451860] Call Trace:
  [ 9184.451861]  [] schedule+0x35/0x80
  [ 9184.451866]  [] cv_wait_common+0x110/0x130 [spl]
  [ 9184.451868]  [] ? wake_atomic_t_function+0x60/0x60
  [ 9184.451872]  [] __cv_wait+0x15/0x20 [spl]
  [ 9184.451904]  [] zil_commit.part.11+0x79/0x7a0 [zfs]
  [ 9184.451909]  [] ? tsd_hash_search.isra.0+0x46/0xa0 
[spl]
  [ 9184.451913]  [] ? tsd_set+0x2b4/0x500 [spl]
  [ 9184.451914]  [] ? mutex_lock+0x12/0x30
  [ 9184.451945]  [] zil_commit+0x17/0x20 [zfs]
  [ 9184.451975]  [] zfs_fsync+0x7a/0xf0 [zfs]
  [ 9184.452005]  [] zpl_fsync+0x68/0xa0 [zfs]
  [ 9184.452008]  [] vfs_fsync_range+0x4b/0xb0
  [ 9184.452010]  [] do_fsync+0x3d/0x70
  [ 9184.452011]  [] SyS_fsync+0x10/0x20
  [ 9184.452013]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  [ 9184.452023] INFO: task bitcoin-msghand:663 blocked for more than 120 
seconds.
  [ 9184.452024]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
  [ 9184.452025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [ 9184.452026] bitcoin-msghand D a23eeb23bd38 0   663  26994 
0x
  [ 

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

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

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

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

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

** Tags added: artful

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

Title:
  Call trace observed while disabling PD on Ubuntu 16.04.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am working on smartpqi linux driver for Microsemi.

  We have a storage controller managment application tool to manage storage 
behind our controller. One of the application option what we have is to disable 
physical device(PD).
  During disable PD opertaion, Disable PD command got timedout. Then I observed 
below mentioned call trace in dmesg log.
  Please note we are running IO stress test on the PD which is being disabled.

  Please let me know if there are any known issues specific to Ubuntu kernel 
with respect to this. 
  If its a known issue specific to Ubuntu 16.04.4 distro, does this issue 
already addressed in latest Ubuntu OS distro ?

  Thanks in advance!

  Sincerely,
  Murthy Bhat

  Call trace:
  smartpqi :92:00.0: removed 5:0:2:0 3d1701cf2001 Direct-Access ATA 
ST1000NX0303 AIO+ qd=32
  [ 1199.201495] Buffer I/O error on dev sdk, logical block 244190645, async 
page read
  [ 1343.006515] sdn:
  [ 1358.264503] INFO: task kworker/173:1:1620 blocked for more than 120 
seconds.
  [ 1358.271550] Tainted: G OE 4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1358.278966] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1358.286806] kworker/173:1 D 0 1620 2 0x
  [ 1358.286832] Workqueue: events pqi_rescan_worker [smartpqi]
  [ 1358.286836] Call trace:
  [ 1358.286844] [] __switch_to+0x90/0xa8
  [ 1358.286855] [] __schedule+0x35c/0x8b0
  [ 1358.286858] [] schedule+0x34/0x90
  [ 1358.286865] [] blk_mq_freeze_queue_wait+0x70/0xd8
  [ 1358.286869] [] blk_mq_freeze_queue+0x28/0x38
  [ 1358.286873] [] blk_freeze_queue+0x20/0x30
  [ 1358.286878] [] blk_cleanup_queue+0x78/0x128
  [ 1358.286883] [] __scsi_remove_device+0x64/0x128
  [ 1358.286884] [] scsi_remove_device+0x30/0x48
  [ 1358.286887] [] scsi_remove_target+0x188/0x1c8
  [ 1358.286899] [] sas_rphy_remove+0x78/0x98 
[scsi_transport_sas]
  [ 1358.286907] [] sas_port_delete+0x38/0x160 
[scsi_transport_sas]
  [ 1358.286918] [] pqi_free_sas_port+0x4c/0x88 [smartpqi]
  [ 1358.286926] [] pqi_remove_sas_device+0x24/0x38 [smartpqi]
  [ 1358.286933] [] pqi_update_device_list+0x520/0x818 
[smartpqi]
  [ 1358.286939] [] pqi_scan_scsi_devices+0x420/0x980 
[smartpqi]
  [ 1358.286946] [] pqi_rescan_worker+0x24/0x30 [smartpqi]
  [ 1358.286955] [] process_one_work+0x14c/0x420
  [ 1358.286957] [] worker_thread+0x12c/0x470
  [ 1358.286961] [] kthread+0x108/0x138
  [ 1358.286963] [] ret_from_fork+0x10/0x30
  [ 1358.287045] INFO: task pain:6788 blocked for more than 120 seconds.
  [ 1358.293326] Tainted: G OE 4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1358.300730] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1358.308567] pain D 0 6788 6633 0x

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

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

[Kernel-packages] [Bug 1766565] Re: Unable to insert sysdig_probe module on B-KVM kernel

[Po-Hsu Lin]

This issue only happens on the KVM kernel, Bionic generic works fine
with it.

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

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

Title:
  Unable to insert sysdig_probe module on B-KVM kernel

Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in sysdig package in Ubuntu:
  New

Bug description:
  The sysdig-dkms module cannot be installed on the B-KVM kernel before
  (bug 1764693), but the installation works with 4.15.0-1007

  However, when you try to insert the module, it will complain about:
  $ sudo modprobe sysdig-probe 
  modprobe: ERROR: could not insert 'sysdig_probe': Unknown symbol in module, 
or unknown parameter (see dmesg)

  Log in dmesg:
  [ 1989.967807] sysdig_probe: loading out-of-tree module taints kernel.
  [ 1989.967924] sysdig_probe: module verification failed: signature and/or 
required key missing - tainting kernel
  [ 1989.967986] sysdig_probe: Unknown symbol tracepoint_probe_unregister (err 
0)
  [ 1989.968090] sysdig_probe: Unknown symbol for_each_kernel_tracepoint (err 0)
  [ 1989.968094] sysdig_probe: Unknown symbol tracepoint_probe_register (err 0)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1007-kvm 4.15.0-1007.7
  ProcVersionSignature: User Name 4.15.0-1007.7-kvm 4.15.17
  Uname: Linux 4.15.0-1007-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 11:31:08 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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/1766565/+subscriptions

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

[Kernel-packages] [Bug 1654517] Re: ZFS I/O hangs for minutes

[Colin Ian King]

@Rafael, did the workaround in comment #31 help?

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

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

Title:
  ZFS I/O hangs for minutes

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  I/O for multiple programs, like `thunderbird`, `firefox`, etc., hangs
  for minutes and approx. 100 `z_rd_int_[n]` and `z_wr_int_[n]` kernel
  threads are created, `dmesg` contains

  [ 9184.451606] INFO: task txg_sync:11471 blocked for more than 120 
seconds.
  [ 9184.451610]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
  [ 9184.451611] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [ 9184.451612] txg_syncD a240ab3a7aa8 0 11471  2 
0x
  [ 9184.451616]  a240ab3a7aa8 00ffbb6ade1f a24095148000 
a240e5ca5580
  [ 9184.451618]  0046 a240ab3a8000 a240ff359200 
7fff
  [ 9184.451620]  a23d36cf9050 0001 a240ab3a7ac0 
bbe96b15
  [ 9184.451621] Call Trace:
  [ 9184.451627]  [] schedule+0x35/0x80
  [ 9184.451628]  [] schedule_timeout+0x22a/0x3f0
  [ 9184.451631]  [] ? __switch_to+0x2ce/0x6c0
  [ 9184.451633]  [] ? pick_next_task_fair+0x48c/0x4c0
  [ 9184.451635]  [] ? ktime_get+0x41/0xb0
  [ 9184.451636]  [] io_schedule_timeout+0xa4/0x110
  [ 9184.451644]  [] cv_wait_common+0xb2/0x130 [spl]
  [ 9184.451646]  [] ? wake_atomic_t_function+0x60/0x60
  [ 9184.451650]  [] __cv_wait_io+0x18/0x20 [spl]
  [ 9184.451689]  [] zio_wait+0xfd/0x1d0 [zfs]
  [ 9184.451716]  [] dsl_pool_sync+0xb8/0x480 [zfs]
  [ 9184.451745]  [] spa_sync+0x37f/0xb30 [zfs]
  [ 9184.451747]  [] ? default_wake_function+0x12/0x20
  [ 9184.451779]  [] txg_sync_thread+0x3a5/0x600 [zfs]
  [ 9184.451807]  [] ? txg_delay+0x160/0x160 [zfs]
  [ 9184.451811]  [] thread_generic_wrapper+0x71/0x80 
[spl]
  [ 9184.451815]  [] ? __thread_exit+0x20/0x20 [spl]
  [ 9184.451817]  [] kthread+0xd8/0xf0
  [ 9184.451819]  [] ret_from_fork+0x1f/0x40
  [ 9184.451821]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [ 9184.451849] INFO: task mozStorage #2:21607 blocked for more than 120 
seconds.
  [ 9184.451851]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
  [ 9184.451852] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [ 9184.451853] mozStorage #2   D a23fe8a5bd38 0 21607  19750 
0x0004
  [ 9184.451855]  a23fe8a5bd38 00ffa240ee8feb40 a240ecf72ac0 
a2403803b900
  [ 9184.451857]  bc2c02f7 a23fe8a5c000 a240aa940828 
a240aa940800
  [ 9184.451858]  a240aa940980  a23fe8a5bd50 
bbe96b15
  [ 9184.451860] Call Trace:
  [ 9184.451861]  [] schedule+0x35/0x80
  [ 9184.451866]  [] cv_wait_common+0x110/0x130 [spl]
  [ 9184.451868]  [] ? wake_atomic_t_function+0x60/0x60
  [ 9184.451872]  [] __cv_wait+0x15/0x20 [spl]
  [ 9184.451904]  [] zil_commit.part.11+0x79/0x7a0 [zfs]
  [ 9184.451909]  [] ? tsd_hash_search.isra.0+0x46/0xa0 
[spl]
  [ 9184.451913]  [] ? tsd_set+0x2b4/0x500 [spl]
  [ 9184.451914]  [] ? mutex_lock+0x12/0x30
  [ 9184.451945]  [] zil_commit+0x17/0x20 [zfs]
  [ 9184.451975]  [] zfs_fsync+0x7a/0xf0 [zfs]
  [ 9184.452005]  [] zpl_fsync+0x68/0xa0 [zfs]
  [ 9184.452008]  [] vfs_fsync_range+0x4b/0xb0
  [ 9184.452010]  [] do_fsync+0x3d/0x70
  [ 9184.452011]  [] SyS_fsync+0x10/0x20
  [ 9184.452013]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  [ 9184.452023] INFO: task bitcoin-msghand:663 blocked for more than 120 
seconds.
  [ 9184.452024]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
  [ 9184.452025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [ 9184.452026] bitcoin-msghand D a23eeb23bd38 0   663  26994 
0x
  [ 9184.452028]  a23eeb23bd38 00ffa23eab434000 a240ecf7 
a24095148000
  [ 9184.452030]  a23eeb23bd20 a23eeb23c000 a240aa940828 
a240aa940800
  [ 9184.452031]  a240aa940980  a23eeb23bd50 
bbe96b15
  [ 9184.452033] Call Trace:
  [ 9184.452034]  [] schedule+0x35/0x80
  [ 9184.452039]  [] cv_wait_common+0x110/0x130 [spl]
  [ 9184.452041]  [] ? wake_atomic_t_function+0x60/0x60
  [ 9184.452044]  [] __cv_wait+0x15/0x20 [spl]
  [ 9184.452074]  [] zil_commit.part.11+0x79/0x7a0 [zfs]
  [ 9184.452079]  [] ? tsd_hash_search.isra.0+0x46/0xa0 
[spl]
  [ 9184.452083]  [] ? tsd_set+0x2b4/0x500 [spl]
  [ 9184.452084]  [] ? mutex_lock+0x12/0x30
  [ 9184.452113]  [] zil_commit+0x17/0x20 [zfs]
  [ 

[Kernel-packages] [Bug 1781578] [NEW] Call trace observed while disabling PD on Ubuntu 16.04.4

[Murthy Bhat]

Public bug reported:

I am working on smartpqi linux driver for Microsemi.

We have a storage controller managment application tool to manage storage 
behind our controller. One of the application option what we have is to disable 
physical device(PD).
During disable PD opertaion, Disable PD command got timedout. Then I observed 
below mentioned call trace in dmesg log.
Please note we are running IO stress test on the PD which is being disabled.

Please let me know if there are any known issues specific to Ubuntu kernel with 
respect to this. 
If its a known issue specific to Ubuntu 16.04.4 distro, does this issue already 
addressed in latest Ubuntu OS distro ?

Thanks in advance!

Sincerely,
Murthy Bhat

Call trace:
smartpqi :92:00.0: removed 5:0:2:0 3d1701cf2001 Direct-Access ATA 
ST1000NX0303 AIO+ qd=32
[ 1199.201495] Buffer I/O error on dev sdk, logical block 244190645, async page 
read
[ 1343.006515] sdn:
[ 1358.264503] INFO: task kworker/173:1:1620 blocked for more than 120 seconds.
[ 1358.271550] Tainted: G OE 4.13.0-36-generic #40~16.04.1-Ubuntu
[ 1358.278966] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 1358.286806] kworker/173:1 D 0 1620 2 0x
[ 1358.286832] Workqueue: events pqi_rescan_worker [smartpqi]
[ 1358.286836] Call trace:
[ 1358.286844] [] __switch_to+0x90/0xa8
[ 1358.286855] [] __schedule+0x35c/0x8b0
[ 1358.286858] [] schedule+0x34/0x90
[ 1358.286865] [] blk_mq_freeze_queue_wait+0x70/0xd8
[ 1358.286869] [] blk_mq_freeze_queue+0x28/0x38
[ 1358.286873] [] blk_freeze_queue+0x20/0x30
[ 1358.286878] [] blk_cleanup_queue+0x78/0x128
[ 1358.286883] [] __scsi_remove_device+0x64/0x128
[ 1358.286884] [] scsi_remove_device+0x30/0x48
[ 1358.286887] [] scsi_remove_target+0x188/0x1c8
[ 1358.286899] [] sas_rphy_remove+0x78/0x98 
[scsi_transport_sas]
[ 1358.286907] [] sas_port_delete+0x38/0x160 
[scsi_transport_sas]
[ 1358.286918] [] pqi_free_sas_port+0x4c/0x88 [smartpqi]
[ 1358.286926] [] pqi_remove_sas_device+0x24/0x38 [smartpqi]
[ 1358.286933] [] pqi_update_device_list+0x520/0x818 
[smartpqi]
[ 1358.286939] [] pqi_scan_scsi_devices+0x420/0x980 [smartpqi]
[ 1358.286946] [] pqi_rescan_worker+0x24/0x30 [smartpqi]
[ 1358.286955] [] process_one_work+0x14c/0x420
[ 1358.286957] [] worker_thread+0x12c/0x470
[ 1358.286961] [] kthread+0x108/0x138
[ 1358.286963] [] ret_from_fork+0x10/0x30
[ 1358.287045] INFO: task pain:6788 blocked for more than 120 seconds.
[ 1358.293326] Tainted: G OE 4.13.0-36-generic #40~16.04.1-Ubuntu
[ 1358.300730] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 1358.308567] pain D 0 6788 6633 0x

** Affects: linux (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/1781578

Title:
  Call trace observed while disabling PD on Ubuntu 16.04.4

Status in linux package in Ubuntu:
  New

Bug description:
  I am working on smartpqi linux driver for Microsemi.

  We have a storage controller managment application tool to manage storage 
behind our controller. One of the application option what we have is to disable 
physical device(PD).
  During disable PD opertaion, Disable PD command got timedout. Then I observed 
below mentioned call trace in dmesg log.
  Please note we are running IO stress test on the PD which is being disabled.

  Please let me know if there are any known issues specific to Ubuntu kernel 
with respect to this. 
  If its a known issue specific to Ubuntu 16.04.4 distro, does this issue 
already addressed in latest Ubuntu OS distro ?

  Thanks in advance!

  Sincerely,
  Murthy Bhat

  Call trace:
  smartpqi :92:00.0: removed 5:0:2:0 3d1701cf2001 Direct-Access ATA 
ST1000NX0303 AIO+ qd=32
  [ 1199.201495] Buffer I/O error on dev sdk, logical block 244190645, async 
page read
  [ 1343.006515] sdn:
  [ 1358.264503] INFO: task kworker/173:1:1620 blocked for more than 120 
seconds.
  [ 1358.271550] Tainted: G OE 4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1358.278966] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1358.286806] kworker/173:1 D 0 1620 2 0x
  [ 1358.286832] Workqueue: events pqi_rescan_worker [smartpqi]
  [ 1358.286836] Call trace:
  [ 1358.286844] [] __switch_to+0x90/0xa8
  [ 1358.286855] [] __schedule+0x35c/0x8b0
  [ 1358.286858] [] schedule+0x34/0x90
  [ 1358.286865] [] blk_mq_freeze_queue_wait+0x70/0xd8
  [ 1358.286869] [] blk_mq_freeze_queue+0x28/0x38
  [ 1358.286873] [] blk_freeze_queue+0x20/0x30
  [ 1358.286878] [] blk_cleanup_queue+0x78/0x128
  [ 1358.286883] [] __scsi_remove_device+0x64/0x128
  [ 1358.286884] [] scsi_remove_device+0x30/0x48
  [ 1358.286887] [] scsi_remove_target+0x188/0x1c8
  [ 1358.286899] [] sas_rphy_remove+0x78/0x98 
[scsi_transport_sas]
  [ 1358.286907] [] sas_port_delete+0x38/0x160 
[scsi_transport_sas]
  [ 1358.286918] [] pqi_free_sas_port+0x4c/0x88 

[Kernel-packages] [Bug 1781433] Re: linux: 4.15.0-28.30 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/promote-to-proposed
   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/1781433

Title:
  linux: 4.15.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 
(azure), bug 1781074 (azure-edge), bug 1781115 (gcp)
  derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), 
bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem)
  kernel-stable-phase-changed:Thursday, 12. July 2018 18:03 UTC
  kernel-stable-phase:Uploaded

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

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

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

[Kernel-packages] [Bug 1781435] Re: linux-aws: 4.15.0-1015.15 -proposed tracker

[Brad Figg]

** 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 --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded

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

Title:
  linux-aws: 4.15.0-1015.15 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1776416] Re: Sound stopped working after update 11/06/18 7pm GMT

[Leslie A Bailey]

Sound working again thanks to an engineer. Apparently, the sound drivers
need to be updated. Would have hated to use Windows 10 as their updates
are dreadful.

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

Title:
  Sound stopped working after update 11/06/18 7pm GMT

Status in Linux:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound was working fine until the update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2094 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jun 12 08:30:09 2018
  InstallationDate: Installed on 2017-05-26 (381 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2094 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05 02/23/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67HSHP
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.0502/23/2017:bd02/23/2017:svnPCSpecialistLimited:pnP65_67HSHP:pvrNotApplicable:rvnCLEVO:rnP65_67HSHP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_67HSHP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

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

[Kernel-packages] [Bug 1781115] Re: linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker

[Łukasz Zemczak]

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

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

Title:
  linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Thomas Diesenreiter]

Just tested with the latest proposed kernel: It's working. Although it takes 
about 30 minutes after the booting with the new kernel for the lines to slowly 
vanish. Truly a weird bug.
Thanks for the help, Christopher and Frank!

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Kernel-packages] [Bug 1779379] Re: linux-aws: 4.4.0-1063.72 -proposed tracker

[Łukasz Zemczak]

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

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

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

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

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

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

Bug description:
  This bug is for tracking the  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: 1779376
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1777527] Re: 'ELAN0618 Touchpad' is not recognized on a fresh install

[Mazen elkashef]

Alright. So are there any expectations about the timeline or the
possibility of fixing this issue?

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

Title:
  'ELAN0618 Touchpad' is not recognized on a fresh install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I tried ubuntu 16, 17 and 18. None of them were able to recongize my touchpad 
at all.
  I tried to boot from a windows installation USB, the touchpad worked right 
away.

  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ uname -a
  Linux Mazen-PC 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ dmesg > ~/dmesg
  OUTPUT ATTACHED

  $ cat /proc/bus/input/devices > ~/devices
  OUTPUT ATTACHED

  /var/log/Xorg.0.log
  Doesn't Exist!

  Note: I got the touchpad manufacturer and model (Elan0618) by
  installing Windows to get more info as Ubuntu was unable to detect the
  touchpad at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 18 16:24:57 2018
  InstallationDate: Installed on 2018-06-16 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1779376] Re: linux: 4.4.0-131.157 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   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/1779376

Title:
  linux: 4.4.0-131.157 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon)
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 12. July 2018 16:02 UTC

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

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

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

[Kernel-packages] [Bug 1781115] Re: linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker

[Łukasz Zemczak]

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

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

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

Title:
  linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1781433] Re: linux: 4.15.0-28.30 -proposed tracker

[Łukasz Zemczak]

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

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

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

Title:
  linux: 4.15.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 
(azure), bug 1781074 (azure-edge), bug 1781115 (gcp)
  derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), 
bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem)
  kernel-stable-phase-changed:Thursday, 12. July 2018 18:03 UTC
  kernel-stable-phase:Uploaded

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

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

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

[Kernel-packages] [Bug 1776416] Re: Sound stopped working after update 11/06/18 7pm GMT

[Augustin Riedinger]

Same here. I fix would be great. I haven't tried to boot with older
headers though, maybe you'll get some sound back @surfsecret ?

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

Title:
  Sound stopped working after update 11/06/18 7pm GMT

Status in Linux:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound was working fine until the update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2094 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jun 12 08:30:09 2018
  InstallationDate: Installed on 2017-05-26 (381 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2094 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05 02/23/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67HSHP
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.0502/23/2017:bd02/23/2017:svnPCSpecialistLimited:pnP65_67HSHP:pvrNotApplicable:rvnCLEVO:rnP65_67HSHP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_67HSHP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

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

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

Title:
  Frequent hangs / lockups with "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fairly recently I got an old HP Pavillion 14 laptop and installed
  Kubuntu 17.10 on it. As far as I recall it ran fine, however, not long
  after I upgraded to 18.04 and noticed frequent freezing (approx every
  few hours). When this happens, all of a sudden, the screen just stays
  with it's image immobile and unchanging. There is no visual corruption
  onscreen and even the cursor does not move. Ctrl+alt+F[1-9] and
  alt+ctrl+sysrq+RSEINUB do nothing.

  Often when I look at the logs, at the end of kern.log.1 I see:

  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A (start=96545 end=96546) time 394 us, min 763, max 767, scanline
  start 760, end 778

  Sometimes, earlier on, there is also:

  Could not find key with description: [d4628bf1c812c861]
  process_request_key_err: No key
  Could not find valid key in user session keyring for sig specified in mount 
option: [d4628bf1c812c861]
  One or more global auth toks could not properly register; rc = [-2]
  Error parsing options; rc = [-2]

  I tested, and this also occurs in a brand new live usb of 18.04, and
  noticed that it still happens there, even before any upgrades or
  installation of packages (such as the wireless driver).

  Other than the wireless driver, there are no proprietary drivers
  installed (eg Nvidia, FGLRX etc).

  Is there any more info I can provide to help troubleshoot this?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1152 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jul 13 05:38:09 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ed1ff2d7-7aa5-4119-91ac-2720da50cb7c
  InstallationDate: Installed on 2018-03-20 (115 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=dabc38a5-afcf-4cec-be94-9ee49972e248 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-22 (52 days ago)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1779817] Re: no internet after suspending

[Steve Dodd]

I'm not sure if I'm in the right bug thread, 4.15.0-24 stopped my
r8168/9 NIC working after suspend, was fine in prior versions. I have
tested Kai's lp1779817-2 kernel above but it does not help.

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

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

Title:
  no internet after suspending

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When my computer wakes up from suspending, there's no internet. Unplugging 
and replugging cable doesn't work, restarting network service doesn't work 
also. Only after restarting the computer, internet comes back.
  It only started happening after I freshly installed Ubuntu Budgie (18.04) and 
did all the system updates. Before I was using Ubuntu with Unity (16.04) and 
there was no problems with my internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  minihydra   2085 F pulseaudio
   /dev/snd/controlC0:  minihydra   2085 F pulseaudio
   /dev/snd/controlC1:  minihydra   2085 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Jul  3 10:13:19 2018
  HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd
  InstallationDate: Installed on 2018-07-02 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77T
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1781565] Re: Frequent hangs / lockups with "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A"

[Llord Llama]

It doesn't seem to be overheating related, and I've run the bios memory
check without errors. I also tried adding the file
/etc/modprobe.d/i915.conf with options i915 enable_psr=0 to no avail.

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

Title:
  Frequent hangs / lockups with "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fairly recently I got an old HP Pavillion 14 laptop and installed
  Kubuntu 17.10 on it. As far as I recall it ran fine, however, not long
  after I upgraded to 18.04 and noticed frequent freezing (approx every
  few hours). When this happens, all of a sudden, the screen just stays
  with it's image immobile and unchanging. There is no visual corruption
  onscreen and even the cursor does not move. Ctrl+alt+F[1-9] and
  alt+ctrl+sysrq+RSEINUB do nothing.

  Often when I look at the logs, at the end of kern.log.1 I see:

  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A (start=96545 end=96546) time 394 us, min 763, max 767, scanline
  start 760, end 778

  Sometimes, earlier on, there is also:

  Could not find key with description: [d4628bf1c812c861]
  process_request_key_err: No key
  Could not find valid key in user session keyring for sig specified in mount 
option: [d4628bf1c812c861]
  One or more global auth toks could not properly register; rc = [-2]
  Error parsing options; rc = [-2]

  I tested, and this also occurs in a brand new live usb of 18.04, and
  noticed that it still happens there, even before any upgrades or
  installation of packages (such as the wireless driver).

  Other than the wireless driver, there are no proprietary drivers
  installed (eg Nvidia, FGLRX etc).

  Is there any more info I can provide to help troubleshoot this?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1152 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jul 13 05:38:09 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ed1ff2d7-7aa5-4119-91ac-2720da50cb7c
  InstallationDate: Installed on 2018-03-20 (115 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=dabc38a5-afcf-4cec-be94-9ee49972e248 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-22 (52 days ago)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1777527] Re: 'ELAN0618 Touchpad' is not recognized on a fresh install

[Jelle Witteveen]

I just installed the mainline 4.18 rc4 kernel, it does not work yet.

$ uname -r
4.18.0-041800rc4-generic

ii  linux-image-unsigned-4.18.0-041800rc4-generic
4.18.0-041800rc4.201807082030   amd64Linux kernel
image for version 4.18.0 on 64 bit x86 SMP

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

Title:
  'ELAN0618 Touchpad' is not recognized on a fresh install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I tried ubuntu 16, 17 and 18. None of them were able to recongize my touchpad 
at all.
  I tried to boot from a windows installation USB, the touchpad worked right 
away.

  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ uname -a
  Linux Mazen-PC 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ dmesg > ~/dmesg
  OUTPUT ATTACHED

  $ cat /proc/bus/input/devices > ~/devices
  OUTPUT ATTACHED

  /var/log/Xorg.0.log
  Doesn't Exist!

  Note: I got the touchpad manufacturer and model (Elan0618) by
  installing Windows to get more info as Ubuntu was unable to detect the
  touchpad at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 18 16:24:57 2018
  InstallationDate: Installed on 2018-06-16 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1781565] [NEW] Frequent hangs / lockups with "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A"

[Llord Llama]

Public bug reported:

Fairly recently I got an old HP Pavillion 14 laptop and installed
Kubuntu 17.10 on it. As far as I recall it ran fine, however, not long
after I upgraded to 18.04 and noticed frequent freezing (approx every
few hours). When this happens, all of a sudden, the screen just stays
with it's image immobile and unchanging. There is no visual corruption
onscreen and even the cursor does not move. Ctrl+alt+F[1-9] and
alt+ctrl+sysrq+RSEINUB do nothing.

Often when I look at the logs, at the end of kern.log.1 I see:

[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe
A (start=96545 end=96546) time 394 us, min 763, max 767, scanline start
760, end 778

Sometimes, earlier on, there is also:

Could not find key with description: [d4628bf1c812c861]
process_request_key_err: No key
Could not find valid key in user session keyring for sig specified in mount 
option: [d4628bf1c812c861]
One or more global auth toks could not properly register; rc = [-2]
Error parsing options; rc = [-2]

I tested, and this also occurs in a brand new live usb of 18.04, and
noticed that it still happens there, even before any upgrades or
installation of packages (such as the wireless driver).

Other than the wireless driver, there are no proprietary drivers
installed (eg Nvidia, FGLRX etc).

Is there any more info I can provide to help troubleshoot this?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-24-generic 4.15.0-24.26
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  user   1152 F pulseaudio
CurrentDesktop: KDE
Date: Fri Jul 13 05:38:09 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=ed1ff2d7-7aa5-4119-91ac-2720da50cb7c
InstallationDate: Installed on 2018-03-20 (115 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2)
MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=dabc38a5-afcf-4cec-be94-9ee49972e248 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-24-generic N/A
 linux-backports-modules-4.15.0-24-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-05-22 (52 days ago)
dmi.bios.date: 03/18/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.42
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 227A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 76.35
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion 14 Notebook PC
dmi.product.version: 096C110800405F1620180
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug bionic

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

Title:
  Frequent hangs / lockups with "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fairly recently I got an old HP Pavillion 14 laptop and installed
  Kubuntu 17.10 on it. As far as I recall it ran fine, however, not long
  after I upgraded to 18.04 and noticed frequent freezing (approx every
  few hours). When this happens, all of a sudden, the screen just stays
  with it's image immobile and unchanging. There is no visual corruption
  onscreen and even the cursor does not move. Ctrl+alt+F[1-9] and
  alt+ctrl+sysrq+RSEINUB do nothing.

  Often when I look at the logs, at the end of kern.log.1 I see:

  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A (start=96545 end=96546) time 394 us, min 763, max 767, scanline
  start 760, end 778

  Sometimes, earlier on, there is also:

  Could not find key with description: [d4628bf1c812c861]
  process_request_key_err: No key
  Could not find valid key in user session keyring for sig specified in mount 
option: [d4628bf1c812c861]
  One or more global auth toks could not properly register; rc = [-2]
  Error parsing options; rc = [-2]

  I tested, and this also occurs in a brand new live usb of 18.04, and
  noticed that it still happens there, even before any upgrades or
  installation of packages (such as the wireless driver).

  Other than the wireless driver, there are no proprietary drivers