[Kernel-packages] [Bug 1811194] Re: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic

[Po-Hsu Lin]

** Description changed:

- This issue cannot be reproduced across all of our SUTs, issue found on
- node secchi.
+ This issue cannot be reproduced across all of our SUTs, issue found on node 
secchi (3 out of 3).
+ And sometimes on node amaura (2 out of 4)
  
  selftests: raw_skew
  
  WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
  Estimating clock drift: 29.255(est) 30.529(act)   [FAILED]
  Bail out!
  Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
  1..0
  not ok 1..7 selftests:  raw_skew [FAIL]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jan 10 03:58 seq
-  crw-rw 1 root audio 116, 33 Jan 10 03:58 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Jan 10 03:58 seq
+  crw-rw 1 root audio 116, 33 Jan 10 03:58 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 10 06:25:41 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. 
-  Bus 001 Device 002: ID :0001  
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp.
+  Bus 001 Device 002: ID :0001
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S2600WFT
  PciMultimedia:
-  
+ 
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-43-generic N/A
-  linux-backports-modules-4.15.0-43-generic  N/A
-  linux-firmware 1.173.2
+  linux-restricted-modules-4.15.0-43-generic N/A
+  linux-backports-modules-4.15.0-43-generic  N/A
+  linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C620.86B.01.00.0294.101220161543
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600WFT
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H48104-410
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 23
  dmi.chassis.vendor: ...
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..:
  dmi.product.family: Family
  dmi.product.name: S2600WFT
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

Title:
  raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic

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

Bug description:
  This issue cannot be reproduced across all of our SUTs, issue found on node 
secchi (3 out of 3).
  And sometimes on node amaura (2 out of 4)

  selftests: raw_skew
  
  WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
  Estimating clock drift: 29.255(est) 30.529(act)   [FAILED]
  Bail out!
  Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
  1..0
  not ok 1..7 selftests:  raw_skew [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 03:58 seq
   crw-rw 1 root audio 116, 33 Jan 10 03:58 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 10 06:25:41 2019
  IwConfig: Error: 

[Kernel-packages] [Bug 1811200] [NEW] Add Cavium ThunderX2 SoC UNCORE PMU driver

[Ike Panhc]

Public bug reported:

[Impact]
No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller 
(DMC) for Cavium ThunderX2 SoC

[Test Case]
sudo perf stat -a -e \
> uncore_dmc_0/cnt_cycles/,\
> uncore_dmc_0/data_transfers/,\
> uncore_dmc_0/read_txns/,\
> uncore_dmc_0/write_txns/ sleep 1

sudo perf stat -a -e \
> uncore_l3c_0/read_request/,\
> uncore_l3c_0/read_hit/,\
> uncore_l3c_0/inv_request/,\
> uncore_l3c_0/inv_hit/ sleep 1

sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1

[Fix]
Backport patches
82975c46da  perf: Export perf_event_update_userpage
d6310a3f33  Documentation: perf: Add documentation for ThunderX2 PMU uncore 
driver
69c32972d5  drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
and enable CONFIG_THUNDERX2_PMU=m

[Regression Risk]
This driver only loaded when CAV901C in ACPI table, lowest risk for other 
platform.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ike Panhc (ikepanhc)
 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/1811200

Title:
  Add Cavium ThunderX2 SoC UNCORE PMU driver

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller 
(DMC) for Cavium ThunderX2 SoC

  [Test Case]
  sudo perf stat -a -e \
  > uncore_dmc_0/cnt_cycles/,\
  > uncore_dmc_0/data_transfers/,\
  > uncore_dmc_0/read_txns/,\
  > uncore_dmc_0/write_txns/ sleep 1

  sudo perf stat -a -e \
  > uncore_l3c_0/read_request/,\
  > uncore_l3c_0/read_hit/,\
  > uncore_l3c_0/inv_request/,\
  > uncore_l3c_0/inv_hit/ sleep 1

  sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1

  [Fix]
  Backport patches
  82975c46da  perf: Export perf_event_update_userpage
  d6310a3f33  Documentation: perf: Add documentation for ThunderX2 PMU uncore 
driver
  69c32972d5  drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
  and enable CONFIG_THUNDERX2_PMU=m

  [Regression Risk]
  This driver only loaded when CAV901C in ACPI table, lowest risk for other 
platform.

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

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

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

Title:
  raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic

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

Bug description:
  This issue cannot be reproduced across all of our SUTs, issue found on
  node secchi.

  selftests: raw_skew
  
  WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
  Estimating clock drift: 29.255(est) 30.529(act)   [FAILED]
  Bail out!
  Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
  1..0
  not ok 1..7 selftests:  raw_skew [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 03:58 seq
   crw-rw 1 root audio 116, 33 Jan 10 03:58 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 10 06:25:41 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. 
   Bus 001 Device 002: ID :0001  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S2600WFT
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C620.86B.01.00.0294.101220161543
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600WFT
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H48104-410
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 23
  dmi.chassis.vendor: ...
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..:
  dmi.product.family: Family
  dmi.product.name: S2600WFT
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1811194] [NEW] raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic

[Po-Hsu Lin]

Public bug reported:

This issue cannot be reproduced across all of our SUTs, issue found on
node secchi.

selftests: raw_skew

WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
Estimating clock drift: 29.255(est) 30.529(act) [FAILED]
Bail out!
Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
1..0
not ok 1..7 selftests:  raw_skew [FAIL]

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jan 10 03:58 seq
 crw-rw 1 root audio 116, 33 Jan 10 03:58 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Jan 10 06:25:41 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. 
 Bus 001 Device 002: ID :0001  
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Intel Corporation S2600WFT
PciMultimedia:
 
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-43-generic N/A
 linux-backports-modules-4.15.0-43-generic  N/A
 linux-firmware 1.173.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2016
dmi.bios.vendor: Intel Corporation
dmi.bios.version: SE5C620.86B.01.00.0294.101220161543
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: S2600WFT
dmi.board.vendor: Intel Corporation
dmi.board.version: H48104-410
dmi.chassis.asset.tag: 
dmi.chassis.type: 23
dmi.chassis.vendor: ...
dmi.chassis.version: ..
dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..:
dmi.product.family: Family
dmi.product.name: S2600WFT
dmi.product.version: 
dmi.sys.vendor: Intel Corporation

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug bionic uec-images

** Also affects: ubuntu-kernel-tests
   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/1811194

Title:
  raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic

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

Bug description:
  This issue cannot be reproduced across all of our SUTs, issue found on
  node secchi.

  selftests: raw_skew
  
  WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
  Estimating clock drift: 29.255(est) 30.529(act)   [FAILED]
  Bail out!
  Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
  1..0
  not ok 1..7 selftests:  raw_skew [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 03:58 seq
   crw-rw 1 root audio 116, 33 Jan 10 03:58 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 10 06:25:41 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. 
   Bus 001 Device 002: ID :0001  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S2600WFT
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1805607] Re: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter

[Khaled El Mously]

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

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

Title:
  Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless
  Network Adapter

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  It drains power more than 0.5 Watt after power off(S5) the machine with 
QCA9377 wifi card. The power consumption should be lower than 0.5 Watt, or it 
won't pass E-star 7.

  [Fix]
  Qualcomm provides this fix, and the power consumption becomes 0.23 Watt at 
S5. This fix doesn't submit to upstream yet, Qualcomm is still working on it.

  [Test]
  Verified on Dell machines, it works.

  [Regression Potential]
  Low.

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

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

[Kernel-packages] [Bug 1802050] Re: Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10

[Tamer Hassan]

redhat fixed it https://bugzilla.redhat.com/show_bug.cgi?id=1570493
debian followed also with the same patch 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919

still affects me:

kubuntu 18.10
linux-image-4.18.0-13-generic = 4.18.0-13.14
nvidia-driver-390 = 390.87-0ubuntu1

** Bug watch added: Red Hat Bugzilla #1570493
   https://bugzilla.redhat.com/show_bug.cgi?id=1570493

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

** Package changed: linux (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)

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

Title:
  Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  [   56.996976] [ cut here ]
  [   56.996978] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
  [   56.996985] WARNING: CPU: 3 PID: 2547 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
  [   56.996985] Modules linked in: ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter devlink bpfilter pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) nvidia_uvm(POE) eeepc_wmi asus_wmi 
snd_hda_codec_hdmi mxm_wmi wmi_bmof sparse_keymap nvidia_drm(POE) 
nvidia_modeset(POE) snd_hda_codec_realtek intel_rapl nvidia(POE) 
snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_intel kvm_intel kvm snd_hda_codec joydev snd_hda_core snd_usb_audio 
snd_usbmidi_lib irqbypass snd_hwdep input_leds crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_pcm pcbc aesni_intel snd_seq_midi snd_seq_midi_event 
aes_x86_64 snd_rawmidi crypto_simd cryptd snd_seq glue_helper drm_kms_helper 
intel_cstate drm ipmi_devintf ipmi_msghandler intel_rapl_perf snd_seq_device 
snd_timer fb_sys_fops
  [   56.997003]  syscopyarea sysfillrect sysimgblt snd mac_hid soundcore wmi 
video mei_me mei acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables 
x_tables autofs4 raid10 multipath linear raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid0 libcrc32c raid1 hid_generic 
usbhid hid gpio_ich r8169 i2c_i801 mii lpc_ich ahci libahci
  [   56.997016] CPU: 3 PID: 2547 Comm: Xorg Tainted: P   OE 
4.18.0-10-generic #11-Ubuntu
  [   56.997017] Hardware name: ASUS All Series/Z97-K, BIOS 2902 03/31/2016
  [   56.997018] RIP: 0010:usercopy_warn+0x81/0xa0
  [   56.997018] Code: b0 aa 41 51 4d 89 d8 48 c7 c0 89 8d af aa 49 89 f1 48 89 
f9 48 0f 45 c2 48 c7 c7 f0 a1 b0 aa 4c 89 d2 48 89 c6 e8 f1 cf df ff <0f> 0b 48 
83 c4 18 c9 c3 48 c7 c6 b2 8a b2 aa 49 89 f1 49 89 f3 eb 
  [   56.997030] RSP: 0018:b9550248bb08 EFLAGS: 00010286
  [   56.997031] RAX:  RBX: 90fdc8535cb0 RCX: 
0006
  [   56.997032] RDX: 0007 RSI: 0096 RDI: 
90fdded964b0
  [   56.997032] RBP: b9550248bb20 R08: 0001 R09: 
038f
  [   56.997032] R10: 0004 R11:  R12: 
0003
  [   56.997033] R13: 0001 R14: 90fdc8535cb3 R15: 
90fdc8535cf8
  [   56.997033] FS:  7f854792ba80() GS:90fdded8() 
knlGS:
  [   56.997034] CS:  0010 DS:  ES:  CR0: 80050033
  [   56.997034] CR2: 7f8543fd2110 CR3: 000406668006 CR4: 
001606e0
  [   56.997035] Call Trace:
  [   56.997038]  __check_heap_object+0xc2/0x110
  [   56.997039]  __check_object_size+0x14c/0x178
  [   56.997148]  os_memcpy_to_user+0x26/0x50 [nvidia]
  [   56.997254]  _nv009384rm+0xbf/0xe0 [nvidia]
  [   56.997255] WARNING: kernel stack frame pointer at 8fe294b8 in 
Xorg:2547 has bad value 5fea09aa
  [   56.997256] unwind stack type:0 next_sp:  (null) mask:0x2 
graph_idx:0
  [   56.997257] 1bbff756: b9550248bb30 (0xb9550248bb30)
  [   56.997258] 21ffd201: a9c69a82 
(__check_heap_object+0xc2/0x110)
  [   56.997258] 2ec89026: b9550248bb60 (0xb9550248bb60)
  [   56.997259] 297b0120: a9c91abc 
(__check_object_size+0x14c/0x178)
  [   56.997259] 8569feab: 0003 (0x3)
  [   56.997260] b2feea66: 90fdc8535cb0 (0x90fdc8535cb0)
  [   56.997260] a5345c20: 55924226a63e (0x55924226a63e)
  [   56.997260] 798de38a:  ...
  [   56.997261] 871cf253: b9550248bb88 (0xb9550248bb88)
  [   56.997311] 5645fcd2: c0b305b6 
(os_memcpy_to_user+0x26/0x50 [nvidia])
  [   56.997311] 929e7969: 0003 (0x3)
  [   56.997312] cbb9721c: 55924226a63e (0x55924226a63e)
  [   56.997312] cf624d15: 90fdc8535cb0 (0x90fdc8535cb0)
  [   56.997312] 

[Kernel-packages] [Bug 1806534] Re: Fix USB2 device wrongly detected as USB1

[Khaled El Mously]

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

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

Title:
  Fix USB2 device wrongly detected as USB1

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  USB 2 device may come up as USB 1 if a connection to a USB 1 device is 
followed by another connection to a USB 2 device, the link will come up as USB 
1 for the USB 2 device.

  [Test Case]
  Insert 2 USB devices and they shall appear on lsusb with correct address

  [Fix]
  11644a76 xhci: Add quirk to workaround the errata seen on Cavium Thunder-X2 
Soc

  [Regression Risk]
  It only affect device PCI_VENDOR_ID_CAVIUM:0x9026 and 
PCI_VENDOR_ID_BROADCOM:0x9026.
  Low regression to other device.

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

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

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

[Henry Bigelow]

Hi all,

Just wanted to add my experience with this.  I also have found that my
Synaptics touchpad becomes unresponsive after waking from a suspend.  It
isn't restored by a modprobe -r psmouse / modprobe psmouse.  The only
thing that restores it is a shutdown (without -r option) followed by a
fresh boot.

I noticed also that, when it is showing this unresponsive touchpad
symptom,

sudo cat /dev/input/event8 | hexdump

produces nothing at all when i move my finger around on the touchpad
(event8 is the touchpad in my system, as shown by
/proc/bus/input/devices).  Yet, doing:

sudo cat /dev/input/event16 | hexdump

(which is my usb wireless mouse) does produce output when I move my
mouse around.

I'm not very familiar with kernel, drivers, firmware, etc.  I did think
the bit about /dev/input/event8 was interesting though, but I'm not sure
what to do with that information.

If anyone is interested, please feel free to suggest a set of commands
and their output you might want to see, or procedures to try.  I hope
this new data point is useful.

Thanks in advance!

Henry


Some other things:

henry@henry-gs65:~$ uname -a
Linux henry-gs65 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

henry@henry-gs65:~$ sudo lshw | head -n 25
henry-gs65  
description: Notebook
product: GS65 Stealth Thin 8RF (16Q2.1)
vendor: Micro-Star International Co., Ltd.
version: REV:1.0
serial: 9S716Q211405ZI883
width: 64 bits
capabilities: smbios-3.1 dmi-3.1 smp vsyscall32
configuration: boot=normal chassis=notebook family=GS sku=16Q2.1 
uuid=FCEFF7B9-5244-47ED-B96D-2A2CF506C220
  *-core
   description: Motherboard
   product: MS-16Q2
   vendor: Micro-Star International Co., Ltd.
   physical id: 0
   version: REV:1.0
   serial: BSS-0123456789
   slot: Default string
 *-firmware
  description: BIOS
  vendor: American Megatrends Inc.
  physical id: 1
  version: E16Q2IMS.110
  date: 10/08/2018
  size: 64KiB
  capacity: 15MiB


henry@henry-gs65:~$ grep -B 1 -A 10 Synaptics /proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=0001 Version=
N: Name="PS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input34
U: Uniq=
H: Handlers=mouse0 event8 
B: PROP=1
B: EV=7
B: KEY=7 0 0 0 0
B: REL=3

henry@henry-gs65:~$ journalctl -b 0 | grep -i touchpad | grep kernel
Jan 06 21:02:58 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad 
(PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If 
i2c-hid and hid-rmi are not used, you might want to try setting 
psmouse.synaptics_intertouch to 1 and report this to 
linux-in...@vger.kernel.org.
Jan 06 21:02:58 henry-gs65 kernel: psmouse serio1: synaptics: Touchpad model: 
1, fw: 8.16, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x40, board id: 
3414, fw id: 2667658
Jan 06 21:02:58 henry-gs65 kernel: input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input6
Jan 09 19:40:09 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad 
(PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If 
i2c-hid and hid-rmi are not used, you might want to try setting 
psmouse.synaptics_intertouch to 1 and report this to 
linux-in...@vger.kernel.org.
Jan 09 19:40:09 henry-gs65 kernel: psmouse serio1: synaptics: Touchpad model: 
1, fw: 8.16, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x40, board id: 
3414, fw id: 2667658
Jan 09 19:40:09 henry-gs65 kernel: input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input24
Jan 09 19:43:16 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input26
Jan 09 19:49:15 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input28
Jan 09 20:15:08 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input30
Jan 09 20:15:21 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad 
(PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If 
i2c-hid and hid-rmi are not used, you might want to try setting 
psmouse.synaptics_intertouch to 1 and report this to 
linux-in...@vger.kernel.org.
Jan 09 20:15:21 henry-gs65 kernel: psmouse serio1: synaptics: Touchpad model: 
1, fw: 8.16, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x40, board id: 
3414, fw id: 2667658
Jan 09 20:15:21 henry-gs65 kernel: input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input32
Jan 09 20:30:49 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input34

Jan 06 21:02:58 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad 
(PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If 
i2c-hid and hid-rmi are not used, you might want to try setting 

[Kernel-packages] [Bug 1807334] Re: Add support for ALC3277 codec on new Dell edge gateways

[Khaled El Mously]

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

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

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

Title:
  Add support for ALC3277 codec on new Dell edge gateways

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  
  [Impact]
  The Dell Edge IoT Gateway is based on kabylake, and the audio codec is alc3277
  which is connected to kabylake PCH via SSP0, there is no ASoC machine driver
  for this board, so the audio (line-out and line-in) can't work.

  
  [Fix]
  write a ASoC machine driver for this board, and this driver is based on
  the existing driver kbl_rt5663_max98927.c

  
  [Test Case]
  play sound via line-out jack, record sound via line-in jack, all work well.

  
  [Regression Potential]
  Very low, this machine driver is specific to Dell Edge IoT Gateway. Only
  the machine with the HID:10EC3277 in the BIOS can use this driver.

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

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

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

Title:
  Ubuntu crashed totally. Nothing responded. Could not even shut down.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE 18.10 on AMD 64-bit machine. Working fine until suddenly
  Ubuntu stops responding to the mouse buttons or keyboard (PS2
  keyboard).

  No warning. Was using VueScan and running two bash scripts using
  tesseract and VisualWorks. Chrome and Pluma running but not being
  used.

  No other symptoms visible.

  This is the second time in a week that Ubuntu crashed in the same way
  and I have had to do a hardware reset to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2268 F pulseaudio
   /dev/snd/controlC0:  robert 2268 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Jan  9 22:53:15 2019
  InstallationDate: Installed on 2018-12-16 (24 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  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/1811182/+subscriptions

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

[Kernel-packages] [Bug 1811182] [NEW] Ubuntu crashed totally. Nothing responded. Could not even shut down.

[Robert Pearson]

Public bug reported:

Ubuntu MATE 18.10 on AMD 64-bit machine. Working fine until suddenly
Ubuntu stops responding to the mouse buttons or keyboard (PS2 keyboard).

No warning. Was using VueScan and running two bash scripts using
tesseract and VisualWorks. Chrome and Pluma running but not being used.

No other symptoms visible.

This is the second time in a week that Ubuntu crashed in the same way
and I have had to do a hardware reset to restart.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-13-generic 4.18.0-13.14
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  robert 2268 F pulseaudio
 /dev/snd/controlC0:  robert 2268 F pulseaudio
CurrentDesktop: MATE
Date: Wed Jan  9 22:53:15 2019
InstallationDate: Installed on 2018-12-16 (24 days ago)
InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-13-generic N/A
 linux-backports-modules-4.18.0-13-generic  N/A
 linux-firmware 1.175.1
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-A
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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Ubuntu crashed totally. Nothing responded. Could not even shut down.

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu MATE 18.10 on AMD 64-bit machine. Working fine until suddenly
  Ubuntu stops responding to the mouse buttons or keyboard (PS2
  keyboard).

  No warning. Was using VueScan and running two bash scripts using
  tesseract and VisualWorks. Chrome and Pluma running but not being
  used.

  No other symptoms visible.

  This is the second time in a week that Ubuntu crashed in the same way
  and I have had to do a hardware reset to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2268 F pulseaudio
   /dev/snd/controlC0:  robert 2268 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Jan  9 22:53:15 2019
  InstallationDate: Installed on 2018-12-16 (24 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  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: 

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

Title:
  temporary freeze under opengl, not xrender, 18.10 &  kernel 4.20

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several times an hour, usually when switching focus from one window to
  another, all but the mouse will stop changing for a few seconds to a
  minute or so.  If a video is playing the sound will proceed as if
  normal but the screen will not change.  The shape of the mouse will
  not change.

  This is with stock ubuntu 18.10 under opengl with nouveau and i915
  drivers active (xrandr).  I tried using the latest possible ubuntu-
  compiled kernel, 4.20 with exactly the same results.  This did not
  happen before sometime after the cosmic native initial install.  When
  I change kde to 'xrender' -- the problem disappears.

  The oft reported dmesg content is:

  [83492.038575] WARNING: CPU: 2 PID: 2114 at 
drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau]
  [83492.038576] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache rfcomm ebtable_filter ebtables ip6table_filter ip6_tables devlink 
iptable_filter bpfilter cmac bnep bridge stp llc snd_hda_codec_realtek 
snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
i915 kvm_intel kvmgt vfio_mdev crct10dif_pclmul crc32_pclmul nouveau mdev 
vfio_iommu_type1 ghash_clmulni_intel vfio aesni_intel kvm aes_x86_64 
crypto_simd snd_hda_codec_hdmi cryptd uvcvideo ttm glue_helper 
videobuf2_vmalloc snd_hda_intel irqbypass videobuf2_memops btusb intel_cstate 
drm_kms_helper snd_hda_codec snd_usb_audio videobuf2_v4l2 btrtl dell_wmi 
videobuf2_common dell_smbios btbcm snd_seq_dummy intel_rapl_perf btintel 
sparse_keymap drm dcdbas videodev dell_wmi_descriptor snd_seq_oss 
snd_usbmidi_lib snd_hda_core mxm_wmi media joydev input_leds 8250_dw wmi_bmof 
snd_seq_midi snd_hwdep snd_seq_midi_event bluetooth snd_pcm snd_rawmidi mei_me 
idma64 snd_seq snd_seq_device i2c_algo_bit
  [83492.038598]  mei fb_sys_fops syscopyarea sysfillrect mac_hid virt_dma 
ecdh_generic sysimgblt snd_timer snd soundcore acpi_pad sch_fq_codel parport_pc 
ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress 
raid6_pq libcrc32c hid_generic usbhid uas hid usb_storage alx i2c_i801 ahci 
mdio intel_lpss_pci libahci intel_lpss wmi pinctrl_sunrisepoint video 
pinctrl_intel
  [83492.038611] CPU: 2 PID: 2114 Comm: Xorg Not tainted 4.20.0-042000-generic 
#201812232030
  [83492.038611] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.1.7 07/17/2018
  [83492.038625] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau]
  [83492.038626] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 
48 89 45 e8 e8 a1 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb 
f2 e8 ba c3 7e cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
  [83492.038627] RSP: 0018:ba4a0308fbc0 EFLAGS: 00010282
  [83492.038628] RAX: fffe RBX: ba4a0308fbf0 RCX: 

  [83492.038629] RDX: 0010 RSI: ba4a0308fb30 RDI: 
ba4a0308fbd0
  [83492.038629] RBP: ba4a0308fbe0 R08: c0d05b90 R09: 

  [83492.038630] R10: 91cc290bd310 R11: 0030 R12: 
ba4a0308fc28
  [83492.038630] R13: 91cc2bec60b0 R14:  R15: 
91cc290ba800
  [83492.038631] FS:  7f5a5f2f0a80() GS:91cc2ea8() 
knlGS:
  [83492.038632] CS:  0010 DS:  ES:  CR0: 80050033
  [83492.038633] CR2: 7f5a5800c000 CR3: 00043f42e003 CR4: 
003606e0
  [83492.038633] DR0:  DR1:  DR2: 

  [83492.038634] DR3:  DR6: fffe0ff0 DR7: 
0400
  [83492.038634] Call Trace:
  [83492.038659]  nouveau_vma_del+0x75/0xc0 [nouveau]
  [83492.038682]  nouveau_gem_object_close+0x1e0/0x1f0 [nouveau]
  [83492.038692]  drm_gem_object_release_handle+0x34/0xa0 [drm]
  [83492.038698]  drm_gem_handle_delete+0x61/0x90 [drm]
  [83492.038703]  ? drm_gem_handle_create+0x40/0x40 [drm]
  [83492.038709]  drm_gem_close_ioctl+0x25/0x30 [drm]
  [83492.038715]  drm_ioctl_kernel+0xad/0xf0 [drm]
  [83492.038720]  drm_ioctl+0x237/0x420 [drm]
  [83492.038726]  ? drm_gem_handle_create+0x40/0x40 [drm]
  [83492.038728]  ? do_iter_write+0xdd/0x190
  [83492.038750]  nouveau_drm_ioctl+0x73/0xc0 [nouveau]
  [83492.038752]  do_vfs_ioctl+0xa9/0x640
  [83492.038754]  ? __sys_recvmsg+0x88/0xa0
  [83492.038755]  ksys_ioctl+0x67/0x90
  [83492.038756]  __x64_sys_ioctl+0x1a/0x20
  [83492.038758]  do_syscall_64+0x5a/0x110
  [83492.038759]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [83492.038760] RIP: 0033:0x7f5a606273c7
  [83492.038761] Code: 00 00 90 48 8b 05 c9 3a 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff 

[Kernel-packages] [Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive

[Mauricio Faria de Oliveira]

Patch series posted to kernel-team mailing list:

[SRU B][PATCH 00/13] blk-wbt: fix for LP#1810998
https://lists.ubuntu.com/archives/kernel-team/2019-January/097675.html

[SRU C][PATCH 0/8] blk-wbt: fix for LP#1810998
https://lists.ubuntu.com/archives/kernel-team/2019-January/097689.html

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

Title:
  CPU hard lockup with rigorous writes to NVMe drive

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * Users may experience cpu hard lockups when performing
     rigorous writes to NVMe drives.

   * The fix addresses an scheduling issue in the original
     implementation of wbt/writeback throttling

   * The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
     contention and thundering herd issue in wbt_wait"),
     plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
     waking of tasks").

   * There are additional commits to help with a cleaner
     backport and future maintenance:
     - Cosmic: total of 8 clean cherry picks.
     - Bionic: total of 13 commits, 9 clean cherry-picks
   and 4 backports, which are just changes to context
   lines (i.e. refresh) without any functional changes
   in the backport itself.

  [Test Case]

   * This command has been reported to reproduce the problem:

     $ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
  128

   * It generates stack traces as below in the original kernel,
     and does not generate them in the modified/patched kernel.

   * The user/reporter verified the test kernel with these patches
     resolved the problem.

   * The developer verified in 2 systems (4-core and 24-core but
     no NVMe) for regressions, and no error messages were logged
     to dmesg.

  [Regression Potential]

   * The commits have been verified for fixes in later commits in
     linux-next as of 2019-01-08 and all known fix commits are in.

   * The regression potential is mostly contained in the writeback
     throttling (block/blk-wbt.*), as almost all of the 13 patches
     change exclusively that, except for 4 of them (2 of which are
     sysfs):

     - blk-rq-qos: refactor out common elements of blk-wbt (block/)
     - block: Protect less code with sysfs_lock in blk_{un,}register_queue() 
(blk-sysfs.c)
     - block: Protect less code with sysfs_lock in blk_{un,}register_queue() 
(blk-{mq-}sysfs.c)
     - block: pass struct request instead of struct blk_issue_stat to wbt 
(block/, still mostly blk-wbt.*)

  [Other Info]

   * Alternatively, it is probably possible to introduce just the
     two commits that fix this with some changes to their code in
     the backport, but since the 'blk-rq-qos: refactor ..' commit
     may become a dependency for many additional/future fixes, it
     seemed interesting to pull it in earlier in the 18.04 cycle.

   * The problem has been introduced with the blk-wbt mechanism,
     in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
     so only Bionic and Cosmic needs this.

  [Stack Traces]

  [ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
  ...
  [ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 393.628720] Call Trace:
  [ 393.628721] 
  [ 393.628724] enqueue_task_fair+0x6c/0x7f0
  [ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628731] activate_task+0x57/0xc0
  [ 393.628735] ? sched_clock+0x9/0x10
  [ 393.628736] ? sched_clock+0x9/0x10
  [ 393.628738] ttwu_do_activate+0x49/0x90
  [ 393.628739] try_to_wake_up+0x1df/0x490
  [ 393.628741] default_wake_function+0x12/0x20
  [ 393.628743] autoremove_wake_function+0x12/0x40
  [ 393.628744] __wake_up_common+0x73/0x130
  [ 393.628745] __wake_up_common_lock+0x80/0xc0
  [ 393.628746] __wake_up+0x13/0x20
  [ 393.628749] __wbt_done.part.21+0xa4/0xb0
  [ 393.628749] wbt_done+0x72/0xa0
  [ 393.628753] blk_mq_free_request+0xca/0x1a0
  [ 393.628755] blk_mq_end_request+0x48/0x90
  [ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
  [ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
  [ 393.628764] __blk_mq_complete_request+0xd2/0x140
  [ 393.628766] blk_mq_complete_request+0x18/0x20
  [ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
  [ 393.628768] nvme_irq+0x23/0x50 [nvme]
  [ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
  [ 393.628773] handle_irq_event_percpu+0x32/0x80
  [ 393.628774] handle_irq_event+0x3b/0x60
  [ 393.628778] handle_edge_irq+0x7c/0x190
  [ 393.628779] handle_irq+0x20/0x30
  [ 393.628783] do_IRQ+0x46/0xd0
  [ 393.628784] common_interrupt+0x84/0x84
  [ 393.628785] 
  ...
  [ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
  [ 393.628796] cpuidle_enter+0x17/0x20
  [ 393.628797] call_cpuidle+0x23/0x40
  [ 393.628798] do_idle+0x18c/0x1f0
  [ 393.628799] cpu_startup_entry+0x73/0x80
  [ 

[Kernel-packages] [Bug 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs

[Mauricio Faria de Oliveira]

** Description changed:

- The following iptables connlimit rule can be breached
- with a multithreaded client and network device driver,
- due to a race in the conncount/connlimit code:
+ [Impact]
  
- # iptables -A INPUT -p tcp -m tcp --syn --dport  \
-   -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-   -j DROP
+  * The iptables connection count/limit rules can be breached 
+with multithreaded network driver/server/client (common)
+due to a race in the conncount/connlimit code.
  
- NOTE: Patches will be sent to the kernel-team mailing list
- and more details/testing will be provided later today.
+  * For example:
+ 
+# iptables -A INPUT -p tcp -m tcp --syn --dport  \
+  -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
+  -j DROP
+ 
+  * The fix is a backport from an upstream commit that resolves
+the problem (plus dependencies for a cleaner backport) that
+address the race condition:
+ 
+commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
+collection confirm race").
+ 
+ [Test Case]
+ 
+  * Server-side: (relevant kernel side)
+(limit TCP port  to only 2000 connections)
+ 
+# iptables -A INPUT -p tcp -m tcp --syn --dport  \
+  -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
+  -j DROP
+ 
+# ulimit -SHn 65000   # increase number of open files
+# ruby server.rb  # multi-threaded server
+ 
+  * Client-side:
+ 
+# ulimit -SHn 65000
+# ruby client.rb<# threads> 
+
+ 
+  * Results with Original kernel:
+(client achieves target of 6000 connections > limit of 2000 connections)
+ 
+# ruby client.rb 10.230.56.100  6000 3 
+1
+2
+3
+<...>
+6000
+Target reached. Thread finishing
+6001
+Target reached. Thread finishing
+6002
+Target reached. Thread finishing
+Threads done. 6002 connections
+press enter to exit
+ 
+  * Results with Modified kernel:
+(client is limited to 2000 connections, and times out afterward)
+ 
+# ruby client.rb 10.230.56.100  6000 3
+1
+2
+3
+<...>
+2000
+<... blocks for a few minutes ...>
+failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
+failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
+failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
+Threads done. 2000 connections
+press enter to exit
+ 
+  * Test cases possibly available upon request,
+depending on original author's permission.
+ 
+ [Regression Potential]
+ 
+  * The patchset has been reviewed by a netfilter maintainer [1] in
+stable mailing list, and was considered OK for 4.14, and that's
+essentially the same backport for 4.15 and 4.4. 
+ 
+  * The changes are limited to netfilter conncount/connlimit (names
+change between older/newer kernel versions).
+ 
+ [Other Info]
+  
+  * The backport for 4.14 [2] is applied as of 4.14.92.
+ 
+ [1] https://www.spinics.net/lists/stable/msg276883.html
+ [2] https://www.spinics.net/lists/stable/msg276910.html

** Description changed:

  [Impact]
  
-  * The iptables connection count/limit rules can be breached 
-with multithreaded network driver/server/client (common)
-due to a race in the conncount/connlimit code.
+  * The iptables connection count/limit rules can be breached
+    with multithreaded network driver/server/client (common)
+    due to a race in the conncount/connlimit code.
  
-  * For example:
+  * For example:
  
-# iptables -A INPUT -p tcp -m tcp --syn --dport  \
-  -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-  -j DROP
+    # iptables -A INPUT -p tcp -m tcp --syn --dport  \
+  -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
+  -j DROP
  
-  * The fix is a backport from an upstream commit that resolves
-the problem (plus dependencies for a cleaner backport) that
-address the race condition:
+  * The fix is a backport from an upstream commit that resolves
+    the problem (plus dependencies for a cleaner backport) that
+    address the race condition:
  
-commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
-collection confirm race").
+    commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
+    collection confirm race").
  
  [Test Case]
  
-  * Server-side: (relevant kernel side)
-(limit TCP port  to only 2000 connections)
+  * Server-side: (relevant kernel side)
+    (limit TCP port  to only 2000 connections)
  
-# iptables -A INPUT -p tcp -m tcp --syn --dport  \
-  -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-  -j DROP
+    # iptables -A INPUT -p tcp -m tcp --syn --dport  \
+  -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
+  -j DROP
  
-# ulimit -SHn 65000   # increase number of open files
-# ruby server.rb  # multi-threaded 

[Kernel-packages] [Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive

[Mauricio Faria de Oliveira]

** Description changed:

- [NOTE]
- 
-  * Patches will be sent to the kernel-team mailing list
-    once the test kernel has been verified by the reporter.
- 
  [Impact]
  
   * Users may experience cpu hard lockups when performing
     rigorous writes to NVMe drives.
  
   * The fix addresses an scheduling issue in the original
     implementation of wbt/writeback throttling
  
   * The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
     contention and thundering herd issue in wbt_wait"),
     plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
     waking of tasks").
  
   * There are additional commits to help with a cleaner
     backport and future maintenance:
     - Cosmic: total of 8 clean cherry picks.
     - Bionic: total of 13 commits, 9 clean cherry-picks
   and 4 backports, which are just changes to context
   lines (i.e. refresh) without any functional changes
   in the backport itself.
  
  [Test Case]
  
   * This command has been reported to reproduce the problem:
  
     $ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
  128
  
   * It generates stack traces as below in the original kernel,
-and does not generate them in the modified/patched kernel.
+    and does not generate them in the modified/patched kernel.
  
-  * The user/reporter verified the test kernel with these patches
-resolved the problem.
+  * The user/reporter verified the test kernel with these patches
+    resolved the problem.
  
-  * The developer verified in 2 systems (4-core and 24-core but
-no NVMe) for regressions, and no error messages were logged
-to dmesg.
+  * The developer verified in 2 systems (4-core and 24-core but
+    no NVMe) for regressions, and no error messages were logged
+    to dmesg.
  
  [Regression Potential]
  
   * The commits have been verified for fixes in later commits in
     linux-next as of 2019-01-08 and all known fix commits are in.
  
   * The regression potential is mostly contained in the writeback
     throttling (block/blk-wbt.*), as almost all of the 13 patches
     change exclusively that, except for 4 of them (2 of which are
     sysfs):
  
     - blk-rq-qos: refactor out common elements of blk-wbt (block/)
     - block: Protect less code with sysfs_lock in blk_{un,}register_queue() 
(blk-sysfs.c)
     - block: Protect less code with sysfs_lock in blk_{un,}register_queue() 
(blk-{mq-}sysfs.c)
     - block: pass struct request instead of struct blk_issue_stat to wbt 
(block/, still mostly blk-wbt.*)
  
  [Other Info]
  
   * Alternatively, it is probably possible to introduce just the
     two commits that fix this with some changes to their code in
     the backport, but since the 'blk-rq-qos: refactor ..' commit
     may become a dependency for many additional/future fixes, it
     seemed interesting to pull it in earlier in the 18.04 cycle.
  
   * The problem has been introduced with the blk-wbt mechanism,
     in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
     so only Bionic and Cosmic needs this.
  
  [Stack Traces]
  
  [ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
  ...
  [ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 393.628720] Call Trace:
  [ 393.628721] 
  [ 393.628724] enqueue_task_fair+0x6c/0x7f0
  [ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628731] activate_task+0x57/0xc0
  [ 393.628735] ? sched_clock+0x9/0x10
  [ 393.628736] ? sched_clock+0x9/0x10
  [ 393.628738] ttwu_do_activate+0x49/0x90
  [ 393.628739] try_to_wake_up+0x1df/0x490
  [ 393.628741] default_wake_function+0x12/0x20
  [ 393.628743] autoremove_wake_function+0x12/0x40
  [ 393.628744] __wake_up_common+0x73/0x130
  [ 393.628745] __wake_up_common_lock+0x80/0xc0
  [ 393.628746] __wake_up+0x13/0x20
  [ 393.628749] __wbt_done.part.21+0xa4/0xb0
  [ 393.628749] wbt_done+0x72/0xa0
  [ 393.628753] blk_mq_free_request+0xca/0x1a0
  [ 393.628755] blk_mq_end_request+0x48/0x90
  [ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
  [ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
  [ 393.628764] __blk_mq_complete_request+0xd2/0x140
  [ 393.628766] blk_mq_complete_request+0x18/0x20
  [ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
  [ 393.628768] nvme_irq+0x23/0x50 [nvme]
  [ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
  [ 393.628773] handle_irq_event_percpu+0x32/0x80
  [ 393.628774] handle_irq_event+0x3b/0x60
  [ 393.628778] handle_edge_irq+0x7c/0x190
  [ 393.628779] handle_irq+0x20/0x30
  [ 393.628783] do_IRQ+0x46/0xd0
  [ 393.628784] common_interrupt+0x84/0x84
  [ 393.628785] 
  ...
  [ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
  [ 393.628796] cpuidle_enter+0x17/0x20
  [ 393.628797] call_cpuidle+0x23/0x40
  [ 393.628798] do_idle+0x18c/0x1f0
  [ 393.628799] cpu_startup_entry+0x73/0x80
  [ 393.628802] start_secondary+0x1a6/0x200
  [ 393.628804] secondary_startup_64+0xa5/0xb0
  [ 

[Kernel-packages] [Bug 1811159] Re: temporary freeze under opengl, not xrender, 18.10 & kernel 4.20

[Daniel van Vugt]

It appears the nouveau kernel driver is crashing, which may well be the
main problem here. And thanks for testing kernel 4.20 already.

As a workaround please try installing the official Nvidia driver.


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

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

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

Title:
  temporary freeze under opengl, not xrender, 18.10 &  kernel 4.20

Status in linux package in Ubuntu:
  New

Bug description:
  Several times an hour, usually when switching focus from one window to
  another, all but the mouse will stop changing for a few seconds to a
  minute or so.  If a video is playing the sound will proceed as if
  normal but the screen will not change.  The shape of the mouse will
  not change.

  This is with stock ubuntu 18.10 under opengl with nouveau and i915
  drivers active (xrandr).  I tried using the latest possible ubuntu-
  compiled kernel, 4.20 with exactly the same results.  This did not
  happen before sometime after the cosmic native initial install.  When
  I change kde to 'xrender' -- the problem disappears.

  The oft reported dmesg content is:

  [83492.038575] WARNING: CPU: 2 PID: 2114 at 
drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau]
  [83492.038576] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache rfcomm ebtable_filter ebtables ip6table_filter ip6_tables devlink 
iptable_filter bpfilter cmac bnep bridge stp llc snd_hda_codec_realtek 
snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
i915 kvm_intel kvmgt vfio_mdev crct10dif_pclmul crc32_pclmul nouveau mdev 
vfio_iommu_type1 ghash_clmulni_intel vfio aesni_intel kvm aes_x86_64 
crypto_simd snd_hda_codec_hdmi cryptd uvcvideo ttm glue_helper 
videobuf2_vmalloc snd_hda_intel irqbypass videobuf2_memops btusb intel_cstate 
drm_kms_helper snd_hda_codec snd_usb_audio videobuf2_v4l2 btrtl dell_wmi 
videobuf2_common dell_smbios btbcm snd_seq_dummy intel_rapl_perf btintel 
sparse_keymap drm dcdbas videodev dell_wmi_descriptor snd_seq_oss 
snd_usbmidi_lib snd_hda_core mxm_wmi media joydev input_leds 8250_dw wmi_bmof 
snd_seq_midi snd_hwdep snd_seq_midi_event bluetooth snd_pcm snd_rawmidi mei_me 
idma64 snd_seq snd_seq_device i2c_algo_bit
  [83492.038598]  mei fb_sys_fops syscopyarea sysfillrect mac_hid virt_dma 
ecdh_generic sysimgblt snd_timer snd soundcore acpi_pad sch_fq_codel parport_pc 
ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress 
raid6_pq libcrc32c hid_generic usbhid uas hid usb_storage alx i2c_i801 ahci 
mdio intel_lpss_pci libahci intel_lpss wmi pinctrl_sunrisepoint video 
pinctrl_intel
  [83492.038611] CPU: 2 PID: 2114 Comm: Xorg Not tainted 4.20.0-042000-generic 
#201812232030
  [83492.038611] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.1.7 07/17/2018
  [83492.038625] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau]
  [83492.038626] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 
48 89 45 e8 e8 a1 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb 
f2 e8 ba c3 7e cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
  [83492.038627] RSP: 0018:ba4a0308fbc0 EFLAGS: 00010282
  [83492.038628] RAX: fffe RBX: ba4a0308fbf0 RCX: 

  [83492.038629] RDX: 0010 RSI: ba4a0308fb30 RDI: 
ba4a0308fbd0
  [83492.038629] RBP: ba4a0308fbe0 R08: c0d05b90 R09: 

  [83492.038630] R10: 91cc290bd310 R11: 0030 R12: 
ba4a0308fc28
  [83492.038630] R13: 91cc2bec60b0 R14:  R15: 
91cc290ba800
  [83492.038631] FS:  7f5a5f2f0a80() GS:91cc2ea8() 
knlGS:
  [83492.038632] CS:  0010 DS:  ES:  CR0: 80050033
  [83492.038633] CR2: 7f5a5800c000 CR3: 00043f42e003 CR4: 
003606e0
  [83492.038633] DR0:  DR1:  DR2: 

  [83492.038634] DR3:  DR6: fffe0ff0 DR7: 
0400
  [83492.038634] Call Trace:
  [83492.038659]  nouveau_vma_del+0x75/0xc0 [nouveau]
  [83492.038682]  nouveau_gem_object_close+0x1e0/0x1f0 [nouveau]
  [83492.038692]  drm_gem_object_release_handle+0x34/0xa0 [drm]
  [83492.038698]  drm_gem_handle_delete+0x61/0x90 [drm]
  [83492.038703]  ? drm_gem_handle_create+0x40/0x40 [drm]
  [83492.038709]  drm_gem_close_ioctl+0x25/0x30 [drm]
  [83492.038715]  drm_ioctl_kernel+0xad/0xf0 [drm]
  [83492.038720]  drm_ioctl+0x237/0x420 [drm]
  [83492.038726]  ? drm_gem_handle_create+0x40/0x40 [drm]
  [83492.038728]  ? do_iter_write+0xdd/0x190
  [83492.038750]  nouveau_drm_ioctl+0x73/0xc0 [nouveau]
  [83492.038752]  do_vfs_ioctl+0xa9/0x640
  [83492.038754]  ? __sys_recvmsg+0x88/0xa0
  [83492.038755]  ksys_ioctl+0x67/0x90
  [83492.038756]  __x64_sys_ioctl+0x1a/0x20
  [83492.038758]  

[Kernel-packages] [Bug 1811159] [NEW] temporary freeze under opengl, not xrender, 18.10 & kernel 4.20

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Several times an hour, usually when switching focus from one window to
another, all but the mouse will stop changing for a few seconds to a
minute or so.  If a video is playing the sound will proceed as if normal
but the screen will not change.  The shape of the mouse will not change.

This is with stock ubuntu 18.10 under opengl with nouveau and i915
drivers active (xrandr).  I tried using the latest possible ubuntu-
compiled kernel, 4.20 with exactly the same results.  This did not
happen before sometime after the cosmic native initial install.  When I
change kde to 'xrender' -- the problem disappears.

The oft reported dmesg content is:

[83492.038575] WARNING: CPU: 2 PID: 2114 at 
drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau]
[83492.038576] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache rfcomm ebtable_filter ebtables ip6table_filter ip6_tables devlink 
iptable_filter bpfilter cmac bnep bridge stp llc snd_hda_codec_realtek 
snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
i915 kvm_intel kvmgt vfio_mdev crct10dif_pclmul crc32_pclmul nouveau mdev 
vfio_iommu_type1 ghash_clmulni_intel vfio aesni_intel kvm aes_x86_64 
crypto_simd snd_hda_codec_hdmi cryptd uvcvideo ttm glue_helper 
videobuf2_vmalloc snd_hda_intel irqbypass videobuf2_memops btusb intel_cstate 
drm_kms_helper snd_hda_codec snd_usb_audio videobuf2_v4l2 btrtl dell_wmi 
videobuf2_common dell_smbios btbcm snd_seq_dummy intel_rapl_perf btintel 
sparse_keymap drm dcdbas videodev dell_wmi_descriptor snd_seq_oss 
snd_usbmidi_lib snd_hda_core mxm_wmi media joydev input_leds 8250_dw wmi_bmof 
snd_seq_midi snd_hwdep snd_seq_midi_event bluetooth snd_pcm snd_rawmidi mei_me 
idma64 snd_seq snd_seq_device i2c_algo_bit
[83492.038598]  mei fb_sys_fops syscopyarea sysfillrect mac_hid virt_dma 
ecdh_generic sysimgblt snd_timer snd soundcore acpi_pad sch_fq_codel parport_pc 
ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress 
raid6_pq libcrc32c hid_generic usbhid uas hid usb_storage alx i2c_i801 ahci 
mdio intel_lpss_pci libahci intel_lpss wmi pinctrl_sunrisepoint video 
pinctrl_intel
[83492.038611] CPU: 2 PID: 2114 Comm: Xorg Not tainted 4.20.0-042000-generic 
#201812232030
[83492.038611] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.1.7 07/17/2018
[83492.038625] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau]
[83492.038626] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 
48 89 45 e8 e8 a1 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb 
f2 e8 ba c3 7e cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
[83492.038627] RSP: 0018:ba4a0308fbc0 EFLAGS: 00010282
[83492.038628] RAX: fffe RBX: ba4a0308fbf0 RCX: 
[83492.038629] RDX: 0010 RSI: ba4a0308fb30 RDI: ba4a0308fbd0
[83492.038629] RBP: ba4a0308fbe0 R08: c0d05b90 R09: 
[83492.038630] R10: 91cc290bd310 R11: 0030 R12: ba4a0308fc28
[83492.038630] R13: 91cc2bec60b0 R14:  R15: 91cc290ba800
[83492.038631] FS:  7f5a5f2f0a80() GS:91cc2ea8() 
knlGS:
[83492.038632] CS:  0010 DS:  ES:  CR0: 80050033
[83492.038633] CR2: 7f5a5800c000 CR3: 00043f42e003 CR4: 003606e0
[83492.038633] DR0:  DR1:  DR2: 
[83492.038634] DR3:  DR6: fffe0ff0 DR7: 0400
[83492.038634] Call Trace:
[83492.038659]  nouveau_vma_del+0x75/0xc0 [nouveau]
[83492.038682]  nouveau_gem_object_close+0x1e0/0x1f0 [nouveau]
[83492.038692]  drm_gem_object_release_handle+0x34/0xa0 [drm]
[83492.038698]  drm_gem_handle_delete+0x61/0x90 [drm]
[83492.038703]  ? drm_gem_handle_create+0x40/0x40 [drm]
[83492.038709]  drm_gem_close_ioctl+0x25/0x30 [drm]
[83492.038715]  drm_ioctl_kernel+0xad/0xf0 [drm]
[83492.038720]  drm_ioctl+0x237/0x420 [drm]
[83492.038726]  ? drm_gem_handle_create+0x40/0x40 [drm]
[83492.038728]  ? do_iter_write+0xdd/0x190
[83492.038750]  nouveau_drm_ioctl+0x73/0xc0 [nouveau]
[83492.038752]  do_vfs_ioctl+0xa9/0x640
[83492.038754]  ? __sys_recvmsg+0x88/0xa0
[83492.038755]  ksys_ioctl+0x67/0x90
[83492.038756]  __x64_sys_ioctl+0x1a/0x20
[83492.038758]  do_syscall_64+0x5a/0x110
[83492.038759]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[83492.038760] RIP: 0033:0x7f5a606273c7
[83492.038761] Code: 00 00 90 48 8b 05 c9 3a 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 99 3a 0d 00 f7 d8 64 89 01 48
[83492.038762] RSP: 002b:7ffd2a2c6438 EFLAGS: 3246 ORIG_RAX: 
0010
[83492.038763] RAX: ffda RBX: 555e65a090c0 RCX: 7f5a606273c7
[83492.038763] RDX: 7ffd2a2c6470 RSI: 40086409 RDI: 0012
[83492.038764] RBP: 7ffd2a2c6470 R08: 555e64a01d78 R09: 0001

[Kernel-packages] [Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

[Daniel van Vugt]

No, don't put a semicolon (;) in front. The semicolon is a comment
character which tells the system to ignore everything after it. Just
use:

realtime-scheduling = no

anywhere in that file.

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1809488] Re: armhf guests fail to boot in EFI mode

[Khaled El Mously]

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

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

Title:
  armhf guests fail to boot in EFI mode

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The fix for bug 1786878 introduced a regression that causes armhf guest 
booted in EFI mode to panic.

  [Test Case]
  Boot an armhf guest in EFI mode. Here's how I do that on an arm64 box that 
supports AArch32:

  sudo qemu-system-aarch64 -enable-kvm -M virt,gic_version=host -smp 7
  -m 2048 -cpu host,aarch64=off -nographic -pflash AAVMF32_CODE.fd
  -pflash AAVMF32_VARS.fd -drive if=none,file=bionic-server-cloudimg-
  armhf.img,id=hd0 -device virtio-blk-device,drive=hd0 -drive
  if=none,file=my-seed.img,id=hd1  -device virtio-blk-
  device,drive=hd1 -drive if=none,file=debian.img,id=hd3 -device virtio-
  blk-device,drive=hd3 -netdev type=tap,id=net0  -device virtio-
  net-device,netdev=net0,mac=

  [Fix]
  33412b8673135 efi/arm: Revert deferred unmap of early memmap mapping

  [Regression Risk]
  This change is specific to efi/arm, which currently doesn't boot. The 
reverted change was to allow for ACPI BGRT code, which isn't supported on 
32-bit ARM.

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

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

[Kernel-packages] [Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive

[Mauricio Faria de Oliveira]

** Description changed:

  [NOTE]
  
   * Patches will be sent to the kernel-team mailing list
     once the test kernel has been verified by the reporter.
  
  [Impact]
  
   * Users may experience cpu hard lockups when performing
     rigorous writes to NVMe drives.
  
   * The fix addresses an scheduling issue in the original
     implementation of wbt/writeback throttling
  
   * The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
     contention and thundering herd issue in wbt_wait"),
     plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
     waking of tasks").
  
   * There are additional commits to help with a cleaner
     backport and future maintenance:
     - Cosmic: total of 8 clean cherry picks.
     - Bionic: total of 13 commits, 9 clean cherry-picks
   and 4 backports, which are just changes to context
   lines (i.e. refresh) without any functional changes
   in the backport itself.
  
  [Test Case]
  
   * This command has been reported to reproduce the problem:
  
     $ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
  128
  
-  * It generates stack traces as included below.
+  * It generates stack traces as below in the original kernel,
+and does not generate them in the modified/patched kernel.
+ 
+  * The user/reporter verified the test kernel with these patches
+resolved the problem.
+ 
+  * The developer verified in 2 systems (4-core and 24-core but
+no NVMe) for regressions, and no error messages were logged
+to dmesg.
  
  [Regression Potential]
  
   * The commits have been verified for fixes in later commits in
     linux-next as of 2019-01-08 and all known fix commits are in.
  
   * The regression potential is mostly contained in the writeback
     throttling (block/blk-wbt.*), as almost all of the 13 patches
     change exclusively that, except for 4 of them (2 of which are
     sysfs):
  
     - blk-rq-qos: refactor out common elements of blk-wbt (block/)
     - block: Protect less code with sysfs_lock in blk_{un,}register_queue() 
(blk-sysfs.c)
     - block: Protect less code with sysfs_lock in blk_{un,}register_queue() 
(blk-{mq-}sysfs.c)
     - block: pass struct request instead of struct blk_issue_stat to wbt 
(block/, still mostly blk-wbt.*)
  
  [Other Info]
  
   * Alternatively, it is probably possible to introduce just the
     two commits that fix this with some changes to their code in
     the backport, but since the 'blk-rq-qos: refactor ..' commit
     may become a dependency for many additional/future fixes, it
     seemed interesting to pull it in earlier in the 18.04 cycle.
  
   * The problem has been introduced with the blk-wbt mechanism,
     in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
     so only Bionic and Cosmic needs this.
  
  [Stack Traces]
  
  [ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
  ...
  [ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 393.628720] Call Trace:
  [ 393.628721] 
  [ 393.628724] enqueue_task_fair+0x6c/0x7f0
  [ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628731] activate_task+0x57/0xc0
  [ 393.628735] ? sched_clock+0x9/0x10
  [ 393.628736] ? sched_clock+0x9/0x10
  [ 393.628738] ttwu_do_activate+0x49/0x90
  [ 393.628739] try_to_wake_up+0x1df/0x490
  [ 393.628741] default_wake_function+0x12/0x20
  [ 393.628743] autoremove_wake_function+0x12/0x40
  [ 393.628744] __wake_up_common+0x73/0x130
  [ 393.628745] __wake_up_common_lock+0x80/0xc0
  [ 393.628746] __wake_up+0x13/0x20
  [ 393.628749] __wbt_done.part.21+0xa4/0xb0
  [ 393.628749] wbt_done+0x72/0xa0
  [ 393.628753] blk_mq_free_request+0xca/0x1a0
  [ 393.628755] blk_mq_end_request+0x48/0x90
  [ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
  [ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
  [ 393.628764] __blk_mq_complete_request+0xd2/0x140
  [ 393.628766] blk_mq_complete_request+0x18/0x20
  [ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
  [ 393.628768] nvme_irq+0x23/0x50 [nvme]
  [ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
  [ 393.628773] handle_irq_event_percpu+0x32/0x80
  [ 393.628774] handle_irq_event+0x3b/0x60
  [ 393.628778] handle_edge_irq+0x7c/0x190
  [ 393.628779] handle_irq+0x20/0x30
  [ 393.628783] do_IRQ+0x46/0xd0
  [ 393.628784] common_interrupt+0x84/0x84
  [ 393.628785] 
  ...
  [ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
  [ 393.628796] cpuidle_enter+0x17/0x20
  [ 393.628797] call_cpuidle+0x23/0x40
  [ 393.628798] do_idle+0x18c/0x1f0
  [ 393.628799] cpu_startup_entry+0x73/0x80
  [ 393.628802] start_secondary+0x1a6/0x200
  [ 393.628804] secondary_startup_64+0xa5/0xb0
  [ 393.628805] Code: ...
  
  [ 405.981597] nvme nvme1: I/O 393 QID 6 timeout, completion polled
  
  [ 435.597209] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 435.602858] 30-...0: (1 GPs behind) idle=e26/1/0 softirq=6834/6834 fqs=4485
  [ 

[Kernel-packages] [Bug 1810328] Re: iommu - need to effectively disable iommu if "intel_iommu=off" is passed as a kernel parameter

[Khaled El Mously]

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

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

Title:
  iommu - need to effectively disable iommu if "intel_iommu=off" is
  passed as a kernel parameter

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

Bug description:
  [Impact]

  * If the parameter "intel_iommu=off" is passed for the kernel in a
  boot instance coming from a previously iommu-enabled kernel (like a
  kexec/kdump scenario), currently Xenial kernel (4.4 version) is
  missing a patch to effectively disable the iommu. As a result, the
  previous DMA mappings remain and the new kernel will try to use them,
  which is wrong since we don't have iommu initialized to translate the
  addresses.

  * The upstream patch proposed to SRU here, 161b28aae165 ("iommu/vt-d:
  Make sure IOMMUs are off when intel_iommu=off") fixes the issue by
  effectively disabling the iommu in case it was requested.

  * One important use case is in a scenario of iommu bug that is leading to a 
kernel crash; kdump naturally will have the iommu tables copied from previous 
kernel in kdump boot time, so if iommu
  tables are bogus, we could inherit the bug in the kdump kernel preventing a 
successful dump.
  Have the ability to disable iommu (given that the functionality is there) is 
essential.

  
  [Test Case]

  * Boot a kernel with "intel_iommu=on", and then kexec a new kernel with 
"intel_iommu=off"
  parameter. A kdump test is also possible, by changing the kdump command-line 
to disable
  iommu (after booting a kernel with iommu enabled) - then, induce a crash and 
the issue
  will show.

  * Attached to this Launchpad are 2 files with the kdump test case: 
"iommu-missing" shows
  the issue in a Trusty HWE kernel - without the fix patch, we can see messages 
like

  [36.489918] DMAR: DRHD: handling fault status reg 202
  [36.734830] DMAR: DMAR:[DMA Read] Request device [03:00.0] fault addr 3179a000
  [36.734830] DMAR:[fault reason 06] PTE Read access is not set

  In our case, the rootfs couldn't be initialized since the SCSI adapter
  wasn't initialized due to the DMAR failures (hpsa driver). Also,
  Solarflare NIC (sfc driver) couldn't get initialized too.

  The patch fixed those error messages and the rootfs was mounted (see file 
"iommu-patched").
  Notice the succeeding case couldn't kdump for other reasons, not strictly 
related to the proposed patch here.

  
  [Regression Potential]

  * iommu operations are complex and subject to HW issues eventually. Having 
iommu enabled
  and then boot a kernel with this component disabled is inherently a "danger" 
operation from
  drivers (or any users of such mappings) point-of-view. That said, I don't see 
a potential regression for this patch, in a way currently an user can't disable 
iommu properly if it was
  once enabled, and this simple patch fixes it

  * Care should be taken of course to not confuse regressions with problems 
induced by disabling the
  iommu after it was enabled before (which would show that the patch works fine 
indeed, by allowing iommu to get disabled) - some drivers/devices may require 
iommu to be enabled in order to work, in such case disabling it would prevent 
the device to work.

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

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

[Kernel-packages] [Bug 1809699] Re: cpu-hotplug test in ubuntu_kernel_selftest always return 0 on Xenial

[Khaled El Mously]

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

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

Title:
  cpu-hotplug test in ubuntu_kernel_selftest always return 0 on Xenial

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==
  This cpu-hotplug test will always return PASSED even if there are some 
failures there:

  $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests
  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  for TARGET in cpu-hotplug; do \
   make -C $TARGET; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug'
  for TARGET in cpu-hotplug; do \
   make -C $TARGET run_tests; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug'
  pid 25001's current affinity mask: 3
  pid 25001's new affinity mask: 1
  CPU online/offline summary:
    Cpus in online state: 0-1
    Cpus in offline state: 2
  Limited scope test: one hotplug cpu
    (leaves cpu in the original state):
    online to offline to online: cpu 1
    offline to online to offline: cpu 2
  ./cpu-on-off-test.sh: line 78: /sys/devices/system/cpu/cpu2/online: No such 
file or directory
  online_cpu_expect_success 2: unexpected fail
  ./cpu-on-off-test.sh: line 83: /sys/devices/system/cpu/cpu2/online: No such 
file or directory
  offline_cpu_expect_success 2: unexpected fail
  selftests: cpu-on-off-test.sh [PASS]
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug'
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'

  == Fixes ==
  8fe6e53a8ed5f0 (selftests/cpu-hotplug: exit with failure when test occured 
unexpected behaviors)

  For newer releases, they already have this patch.
  For Trusty and older release, they will need more work to get this patch.

  == Regression Potential ==
  None, fix for testing tools.

  For Trusty, it's missing another 20 commits to reach 8fe6e53:
  4813d2e736 (tools: memory-hotplug fix unexpected operator error)
  da9bc4 (tools: selftests - create a separate hotplug target for full 
range test)
  a88cc108f6 (lib: Export interval_tree)
  93e9ef83f4 (test: add minimal module for verification testing)
  3e2a4c183a (test: check copy_to/from_user boundary validation)
  64a8946b44 (net: filter: BPF testsuite)
  7069a97a14 (selftests/net: move test out of Makefile into a shell script)
  3c25fa14f0 (selftests/user: move test out of Makefile into a shell script)
  24fe831c17 (tools/testing/selftests/sysctl: validate sysctl_writes_strict)
  0a8adf5847 (test: add firmware_class loader test)
  6e68e6c5e4 (ftracetest: Initial commit for ftracetest)
  4f5ce5e8d7 (selftests: add memfd_create() + sealing tests)
  c9b26b81af (syscalls: add selftest for execveat(2))
  3ce51050fa (selftest: size: Add size test for Linux kernel) backport with 
context arrangement
  87b2d44026 (selftests: add memfd/sealing page-pinning tests)
  498b473af9 (tools: selftests: fix build issue with make kselftests target)
  ce6a144a0d (selftests/memfd: Run test on all architectures)
  5e29a9105b (selftests: Introduce minimal shared logic for running tests)
  cc16782169 (selftests: change cpu on-off-test.sh name to be unique)
  8c749ce93e (selftests: create test-specific kconfig fragments)
  8fe6e53a8e (selftests/cpu-hotplug: exit with failure when test occured 
unexpected behaviors)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-141-generic 4.4.0-141.167
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Mon Dec 24 04:08:18 2018
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: 

[Kernel-packages] [Bug 1810891] Re: audio output has constant noise on a Dell machine

[Khaled El Mously]

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

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

** Changed in: linux (Ubuntu Disco)
   Status: In Progress => 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/1810891

Title:
  audio output has constant noise on a Dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Invalid

Bug description:

  [Impact]
  the audio output (headpohne, lineout and internal speaker) has constant
  noise when playing sound.

  [Fix]
  Set the pin configuration and some secret coeff registers, the noise
  disappears. This patch is written by Realtek engineer and is upstreamd
  already.

  
  [Test Case]
  play sound via internal speaker, lineout and headphone, no noise anymore.

  
  [Regression Potential]
  Very low, this patch is upstreamd for a while, no regression is reported.

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

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

[Kernel-packages] [Bug 1809868] Re: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on T

[Khaled El Mously]

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

Title:
  29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed
  on T

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  == Justification ==
  When doing an incremental send on a Btrfs filesystem, if we delete a 
directory that has N > 1 hardlinks for the same file and that file has the 
highest inode number inside the directory contents, an incremental send would 
send N times rmdir operation against the directory. This made the btrfs receive 
command fail on the second rmdir instruction, as the target directory didn't 
exist anymore.

  This issue can be triggered with 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5
  test in ubuntu_btrfs_kernel_fixes test suite.

  The test will fail with:
    "ERROR: rmdir o259-6-0 failed. No such file or directory" with Trusty 
kernel.

  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
   nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2
  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
   nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  At subvol snap1
  At snapshot snap2
  ERROR: rmdir o259-6-0 failed. No such file or directory
  incremental receive failed

  == Fix ==
  29d6d30f5 (Btrfs: send, don't send rmdir for same target multiple times)
  This patch needs to be backported for a variable difference in the 
process_recorded_refs function.

  In the Trusty tree:
  static int process_recorded_refs(struct send_ctx *sctx)

  In the patch:
  static int process_recorded_refs(struct send_ctx *sctx, int *pending_move)

  As the new *pending_move is unrelated here, we can just backport the
  patch with the same logic in this function.

  A test kernel could be found here:
  http://people.canonical.com/~phlin/kernel/lp-1809868-btrfs-2nd-rmdir/
  This test will pass with this kernel.

  == Regression potential ==
  Low,
  this patch just adds an extra check to skip unnecessary rmdir operations.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-164-generic 3.13.0-164.214
  ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-164-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 03:14 seq
   crw-rw 1 root audio 116, 33 Dec 27 03:14 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [13958.095408] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.102670] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.105901] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.106099] btrfs: disk space caching is enabled
   [13958.107771] btrfs: creating UUID tree
  Date: Thu Dec 27 07:11:58 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-164-generic N/A
   linux-backports-modules-3.13.0-164-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

 

[Kernel-packages] [Bug 1801102] Re: Please include this patch in bionic kernel https://www.spinics.net/lists/linux-wireless/msg169994.html

[Khaled El Mously]

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

Title:
  Please include this patch in bionic kernel
  https://www.spinics.net/lists/linux-wireless/msg169994.html

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

Bug description:
  ===SRU Justification===
  [Impact]
  iwlwifi spews "Too many chunks: 20" in dmesg.

  [Fix] 
  From the patch description:
  "
  When we free the TFD, we check its number of valid pointers
  and make sure it doesn't exceed the number of pointers the
  hardware support.
  This check had an off by one bug: it is perfectly valid to
  free the 20 pointers if the TFD has 20 pointers.
  "

  [Test]
  User confirms the patch solves the problem.

  [Regression Potential]
  Low. The fix is limited to iwlwifi, and the patch is in mainline for a
  while.

  ===Original Bug Report===
  Hi:

  I am having the same issue i.e. when downloading torrent with
  KTorrent. Please include this fix https://www.spinics.net/lists/linux-
  wireless/msg169994.html in the release kernel.

  Thanks

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

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

[Kernel-packages] [Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive

[Mauricio Faria de Oliveira]

** Description changed:

  [NOTE]
  
   * Patches will be sent to the kernel-team mailing list
     once the test kernel has been verified by the reporter.
  
  [Impact]
  
   * Users may experience cpu hard lockups when performing
     rigorous writes to NVMe drives.
  
   * The fix addresses an scheduling issue in the original
     implementation of wbt/writeback throttling
  
   * The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
     contention and thundering herd issue in wbt_wait"),
     plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
     waking of tasks").
  
   * There are additional commits to help with a cleaner
     backport and future maintenance:
     - Cosmic: total of 8 clean cherry picks.
-    - Bionic: So, of 13 commits, 9 are clean cherry-picks
+    - Bionic: total of 13 commits, 9 clean cherry-picks
   and 4 backports, which are just changes to context
   lines (i.e. refresh) without any functional changes
   in the backport itself.
  
  [Test Case]
  
   * This command has been reported to reproduce the problem:
  
     $ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
  128
  
   * It generates stack traces as included below.
  
  [Regression Potential]
  
   * The commits have been verified for fixes in later commits in
     linux-next as of 2019-01-08 and all known fix commits are in.
  
   * The regression potential is mostly contained in the writeback
     throttling (block/blk-wbt.*), as almost all of the 13 patches
     change exclusively that, except for 4 of them (2 of which are
     sysfs):
  
     - blk-rq-qos: refactor out common elements of blk-wbt (block/)
     - block: Protect less code with sysfs_lock in blk_{un,}register_queue() 
(blk-sysfs.c)
     - block: Protect less code with sysfs_lock in blk_{un,}register_queue() 
(blk-{mq-}sysfs.c)
     - block: pass struct request instead of struct blk_issue_stat to wbt 
(block/, still mostly blk-wbt.*)
  
  [Other Info]
  
   * Alternatively, it is probably possible to introduce just the
     two commits that fix this with some changes to their code in
     the backport, but since the 'blk-rq-qos: refactor ..' commit
     may become a dependency for many additional/future fixes, it
     seemed interesting to pull it in earlier in the 18.04 branch.
  
   * The problem has been introduced with the blk-wbt mechanism,
     in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
     so only Bionic and Cosmic needs this.
  
  [Stack Traces]
  
  [ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
  ...
  [ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 393.628720] Call Trace:
  [ 393.628721] 
  [ 393.628724] enqueue_task_fair+0x6c/0x7f0
  [ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628731] activate_task+0x57/0xc0
  [ 393.628735] ? sched_clock+0x9/0x10
  [ 393.628736] ? sched_clock+0x9/0x10
  [ 393.628738] ttwu_do_activate+0x49/0x90
  [ 393.628739] try_to_wake_up+0x1df/0x490
  [ 393.628741] default_wake_function+0x12/0x20
  [ 393.628743] autoremove_wake_function+0x12/0x40
  [ 393.628744] __wake_up_common+0x73/0x130
  [ 393.628745] __wake_up_common_lock+0x80/0xc0
  [ 393.628746] __wake_up+0x13/0x20
  [ 393.628749] __wbt_done.part.21+0xa4/0xb0
  [ 393.628749] wbt_done+0x72/0xa0
  [ 393.628753] blk_mq_free_request+0xca/0x1a0
  [ 393.628755] blk_mq_end_request+0x48/0x90
  [ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
  [ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
  [ 393.628764] __blk_mq_complete_request+0xd2/0x140
  [ 393.628766] blk_mq_complete_request+0x18/0x20
  [ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
  [ 393.628768] nvme_irq+0x23/0x50 [nvme]
  [ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
  [ 393.628773] handle_irq_event_percpu+0x32/0x80
  [ 393.628774] handle_irq_event+0x3b/0x60
  [ 393.628778] handle_edge_irq+0x7c/0x190
  [ 393.628779] handle_irq+0x20/0x30
  [ 393.628783] do_IRQ+0x46/0xd0
  [ 393.628784] common_interrupt+0x84/0x84
  [ 393.628785] 
  ...
  [ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
  [ 393.628796] cpuidle_enter+0x17/0x20
  [ 393.628797] call_cpuidle+0x23/0x40
  [ 393.628798] do_idle+0x18c/0x1f0
  [ 393.628799] cpu_startup_entry+0x73/0x80
  [ 393.628802] start_secondary+0x1a6/0x200
  [ 393.628804] secondary_startup_64+0xa5/0xb0
  [ 393.628805] Code: ...
  
  [ 405.981597] nvme nvme1: I/O 393 QID 6 timeout, completion polled
  
  [ 435.597209] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 435.602858] 30-...0: (1 GPs behind) idle=e26/1/0 softirq=6834/6834 fqs=4485
  [ 435.610203] (detected by 8, t=15005 jiffies, g=6396, c=6395, q=146818)
  [ 435.617025] Sending NMI from CPU 8 to CPUs 30:
  [ 435.617029] NMI backtrace for cpu 30
  [ 435.617031] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 435.617047] Call Trace:
  [ 435.617048] 
  [ 435.617051] 

[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

[Hui Wang]

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

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in alsa-lib source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  New

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

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

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

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

[Brian Murray]

I tested this upgrade process and it worked for me, setting to
verification-done.

bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-0vo0ih0i$ grep 
"release-upgrader version" /var/log/dist-upgrade/main.log 
2019-01-09 15:50:20,150 INFO release-upgrader version '18.10.11.3' started
bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-0vo0ih0i$ cat 
/etc/X11/xorg.conf
Section "Device"
Identifier "nvidia"
EndSection
bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-0vo0ih0i$ cat 
/etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.10


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

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  Won't Fix
Status in ubuntu-release-upgrader source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  --
  Users who have manually configured an xorg.conf file with nvidia enabled as a 
driver will be surprised to have disabled on upgrade to a new release of Ubuntu 
and won't have a graphical display.

  Test Case
  -
  If you don't have a system with nvidia hardware to upgrade this is a bit 
convoluted but still works.

  1) Run do-release-upgrade (use -d if upgrading to disco)
  2) Cancel the upgrade
  3) Create an /etc/X11/xorg.conf file with a Device section listed in the 
original description using the nvidia driver.
  4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME
  5) run ./$target-release-name --frontend DistUpgradeViewText
  6) Observe the Driver line is commented out of xorg.conf

  When testing the release-upgrader from -proposed you'll need to use
  the -p switch to get the right tarball. Additionally, you'll want to
  add a step 4.5 where you modify xorg_fix_proprietary.py so nvidia
  defaults to True instead of False (line 106) this'll simulate the
  nvidia driver being loaded.

  Regression Potential
  
  This just changes how xorg_fix_proprietary check for nvidia being in use and 
it only affects people who have an /etc/X11/xorg.conf so the impact of a 
regression is rather small. Additionally, the logic used to determine if nvidia 
in use is the same logic used in the apport package hook for all xorg packages 
so is well tested.

  Original Description
  
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 

[Kernel-packages] [Bug 1811162] Re: Turn on CONFIG_REFCOUNT_FULL for non-x86 arches

[Steve Beattie]

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

Title:
  Turn on CONFIG_REFCOUNT_FULL for non-x86 arches

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The upstream kernel has added refcount protection, in two ways. For
  arches that have provided a fast refcount_t implementation, they get
  it automatically (this is signaled by ARCH_HAS_REFCOUNT, which as of
  4.20 kernels, is only the x86 arch). For other arches, they can get
  refcount protection via the CONFIG_REFCOUNT_FULL configure option. The
  upstream arm64 and arm maintainers have enabled this configuration by
  default for those arches, which has been carried into the ubuntu
  kernel config. We should enable that for our other arches that do not
  provide ARCH_HAS_REFCOUNT, namely ppc64el and s390x, to gain
  protection parity with the rest of the architectures supported by
  ubuntu kernels.

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

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

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

[Khaled El Mously]

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => 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/1791758

Title:
  ldisc crash on reopened tty

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  * Line discipline code is racy when we have buffer being flush while
  the tty is being initialized or reinitialized. For the first problem,
  we have an upstream patch since January 2018: b027e2298bd5 ("tty: fix
  data race between tty_init_dev and flush of buf") - although it is not
  in Ubuntu kernel 4.4, only in kernels 4.15 and subsequent ones.

  * For the race between the buffer flush while tty is being reopened,
  we have a patch that addresses this issue recently merged for 5.0-rc1:
  83d817f41070 ("tty: Hold tty_ldisc_lock() during tty_reopen()"). No
  Ubuntu kernel currently contains this patch, hence we're hereby
  submitting the SRU request. The upstream complete patch series for
  this is in [0].

  * The approach of both patches are similar - they rely in locking/semaphore 
to prevent race conditions. Some additional patches are
  necessary to prevent correlated issues, like preventing a potential deadlock 
due to bad prioritization in servicing I/O over releasing
  tty_ldisc_lock() - refer to c96cf923a98d ("tty: Don't block on IO when ldisc 
change is pending"). All the necessary fixes are grouped here in this SRU 
request.

  * The symptom of the race condition between the buffer flush and the
  tty reopen routine is a kernel crash with the following trace:

  BUG: unable to handle kernel paging request at 2268
  IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [...]
  Call Trace:
  [] ? kvm_sched_clock_read+0x1e/0x30
  [] n_tty_receive_buf2+0x14/0x20
  [] flush_to_ldisc+0xd5/0x120
  [] process_one_work+0x156/0x400
  [] worker_thread+0x11a/0x480
  [...]

  * A kernel crash was collected from an user, analysis is present in
  comment #4 in this LP.

  [Test Case]

  * It is not trivial to trigger this fault, but the usual recipe is to
  keep accessing a machine through SSH (or keep killing getty when in
  IPMI serial console) and in some way run commands before the terminal
  is ready in that machine (like hacking some echo into ttySx or pts in
  an infinite loop).

  * We have reports of users that could reproduce this issue in their
  production environment, and with the patches present in this SRU
  request the problem was fixed.

  [Regression Potential]

  * tty subsystem is highly central and patches in that area are always
  delicate. For example, the upstream series [0] is a re-spin (V6) due
  to a hard to reproduce issue reported in the PA-RISC architecture,
  which was found in the V5 iteration [1] but was fixed by the patch
  c96cf923a98d, present in this SRU request.

  * The patchset [0] is present in tty-next tree since mid-November, and
  the patch b027e2298bd5 is available upstream since January/2018 (it's
  available in both Ubuntu kernels 4.15 and 4.18), so the overall
  likelihood of regressions is low.

  * These patches were sniff-tested for the 3 versions (4.4, 4.15 and
  4.18) and didn't show any issues.

  [0] https://marc.info/?l=linux-kernel=154103190111795
  [1] https://marc.info/?l=linux-kernel=153737852618183

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

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

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

[Khaled El Mously]

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

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => 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/1791758

Title:
  ldisc crash on reopened tty

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  * Line discipline code is racy when we have buffer being flush while
  the tty is being initialized or reinitialized. For the first problem,
  we have an upstream patch since January 2018: b027e2298bd5 ("tty: fix
  data race between tty_init_dev and flush of buf") - although it is not
  in Ubuntu kernel 4.4, only in kernels 4.15 and subsequent ones.

  * For the race between the buffer flush while tty is being reopened,
  we have a patch that addresses this issue recently merged for 5.0-rc1:
  83d817f41070 ("tty: Hold tty_ldisc_lock() during tty_reopen()"). No
  Ubuntu kernel currently contains this patch, hence we're hereby
  submitting the SRU request. The upstream complete patch series for
  this is in [0].

  * The approach of both patches are similar - they rely in locking/semaphore 
to prevent race conditions. Some additional patches are
  necessary to prevent correlated issues, like preventing a potential deadlock 
due to bad prioritization in servicing I/O over releasing
  tty_ldisc_lock() - refer to c96cf923a98d ("tty: Don't block on IO when ldisc 
change is pending"). All the necessary fixes are grouped here in this SRU 
request.

  * The symptom of the race condition between the buffer flush and the
  tty reopen routine is a kernel crash with the following trace:

  BUG: unable to handle kernel paging request at 2268
  IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [...]
  Call Trace:
  [] ? kvm_sched_clock_read+0x1e/0x30
  [] n_tty_receive_buf2+0x14/0x20
  [] flush_to_ldisc+0xd5/0x120
  [] process_one_work+0x156/0x400
  [] worker_thread+0x11a/0x480
  [...]

  * A kernel crash was collected from an user, analysis is present in
  comment #4 in this LP.

  [Test Case]

  * It is not trivial to trigger this fault, but the usual recipe is to
  keep accessing a machine through SSH (or keep killing getty when in
  IPMI serial console) and in some way run commands before the terminal
  is ready in that machine (like hacking some echo into ttySx or pts in
  an infinite loop).

  * We have reports of users that could reproduce this issue in their
  production environment, and with the patches present in this SRU
  request the problem was fixed.

  [Regression Potential]

  * tty subsystem is highly central and patches in that area are always
  delicate. For example, the upstream series [0] is a re-spin (V6) due
  to a hard to reproduce issue reported in the PA-RISC architecture,
  which was found in the V5 iteration [1] but was fixed by the patch
  c96cf923a98d, present in this SRU request.

  * The patchset [0] is present in tty-next tree since mid-November, and
  the patch b027e2298bd5 is available upstream since January/2018 (it's
  available in both Ubuntu kernels 4.15 and 4.18), so the overall
  likelihood of regressions is low.

  * These patches were sniff-tested for the 3 versions (4.4, 4.15 and
  4.18) and didn't show any issues.

  [0] https://marc.info/?l=linux-kernel=154103190111795
  [1] https://marc.info/?l=linux-kernel=153737852618183

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

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

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

[Brian Murray]

** Description changed:

  Impact
  --
- Users who have manually configured and xorg.conf file with nvidia enabled as 
a driver will be surprised to have disabled on upgrade to a new release of 
Ubuntu and won't have a graphical display.
+ Users who have manually configured an xorg.conf file with nvidia enabled as a 
driver will be surprised to have disabled on upgrade to a new release of Ubuntu 
and won't have a graphical display.
  
  Test Case
  -
  If you don't have a system with nvidia hardware to upgrade this is a bit 
convoluted but still works.
  
  1) Run do-release-upgrade (use -d if upgrading to disco)
  2) Cancel the upgrade
  3) Create an /etc/X11/xorg.conf file with a Device section listed in the 
original description using the nvidia driver.
  4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME
  5) run ./$target-release-name --frontend DistUpgradeViewText
  6) Observe the Driver line is commented out of xorg.conf
  
  When testing the release-upgrader from -proposed you'll need to use the
  -p switch to get the right tarball. Additionally, you'll want to add a
  step 4.5 where you modify xorg_fix_proprietary.py so nvidia defaults to
  True instead of False (line 106) this'll simulate the nvidia driver
  being loaded.
  
  Regression Potential
  
  This just changes how xorg_fix_proprietary check for nvidia being in use and 
it only affects people who have an /etc/X11/xorg.conf so the impact of a 
regression is rather small. Additionally, the logic used to determine if nvidia 
in use is the same logic used in the apport package hook for all xorg packages 
so is well tested.
  
  Original Description
  
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:
  
  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection
  
  As the installtion routine backuped my xorg.conf I could verify that the
  line hadn't been commented out before upgrading. Removing the "#" solved
  the problem.
  
  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash 
vt.handoff=1SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  

[Kernel-packages] [Bug 1807686] Re: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set

[Khaled El Mously]

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

Title:
  efi-lockdown patch causes -EPERM for some debugfs files even though
  CONFIG_LOCK_DOWN_KERNEL is not set

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == Comment: #0 - Dominik Klein  - 2018-12-10 
03:58:10 ==
  There seems to be a bug in the efi-lockdown patch as applied on top of 
vanilla for Cosmic kernels:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-cosmic.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  Also seems to be present for Disco as of today:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-disco.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  The problem is that part of the patch modifies kernel behavior
  independently of CONFIG_LOCK_DOWN_KERNEL being set or not causing
  issues on two debugfs files on s390x.

  Vasily Gorbik has already analyzed the problem and has posted a proposed fix 
here:
  https://lkml.org/lkml/2018/11/21/634
  https://lkml.org/lkml/2018/11/21/635

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

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

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

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

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

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

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

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

Title:
  apt cannot find linux-libc-dev

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running: xenial

  Problem:

  After running apt-get update, I still get this upon apt-get install:

  Err:60 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
linux-libc-dev amd64 4.4.0-140.166
404  Not Found [IP: 91.189.88.161 80]

  All other packages install fine.

  Looking at the package repo at http://archive.ubuntu.com/ubuntu/dists
  /xenial-updates/main/ it appears the amd64 entry was updated today, so
  I assume that's when the error was introduced.

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

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

[Kernel-packages] [Bug 1811164] [NEW] apt cannot find linux-libc-dev

[Michael Fischer]

Public bug reported:

Running: xenial

Problem:

After running apt-get update, I still get this upon apt-get install:

Err:60 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
linux-libc-dev amd64 4.4.0-140.166
  404  Not Found [IP: 91.189.88.161 80]

All other packages install fine.

Looking at the package repo at http://archive.ubuntu.com/ubuntu/dists
/xenial-updates/main/ it appears the amd64 entry was updated today, so I
assume that's when the error was introduced.

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


** Tags: linux-libc-dev xenial-updates

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

Title:
  apt cannot find linux-libc-dev

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running: xenial

  Problem:

  After running apt-get update, I still get this upon apt-get install:

  Err:60 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
linux-libc-dev amd64 4.4.0-140.166
404  Not Found [IP: 91.189.88.161 80]

  All other packages install fine.

  Looking at the package repo at http://archive.ubuntu.com/ubuntu/dists
  /xenial-updates/main/ it appears the amd64 entry was updated today, so
  I assume that's when the error was introduced.

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

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

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

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

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

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

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

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

Title:
  Turn on CONFIG_REFCOUNT_FULL for non-x86 arches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The upstream kernel has added refcount protection, in two ways. For
  arches that have provided a fast refcount_t implementation, they get
  it automatically (this is signaled by ARCH_HAS_REFCOUNT, which as of
  4.20 kernels, is only the x86 arch). For other arches, they can get
  refcount protection via the CONFIG_REFCOUNT_FULL configure option. The
  upstream arm64 and arm maintainers have enabled this configuration by
  default for those arches, which has been carried into the ubuntu
  kernel config. We should enable that for our other arches that do not
  provide ARCH_HAS_REFCOUNT, namely ppc64el and s390x, to gain
  protection parity with the rest of the architectures supported by
  ubuntu kernels.

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

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

[Kernel-packages] [Bug 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18

[Rick]

In addition to above commit
255095fa7f62ff09b6f61393414535c59c6b4cb0
media: dvb-usb-v2: Fix incorrect use of transfer_flags URB_FREE_BUFFER

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

Title:
  TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear developer(s),

  I used a vdr-installation on Debian testing, before. Switched over to Ubuntu 
since the release of cosmic because of problems with GPU/steam under Debian. 
Now, I have problems to configure vdr because my TV stick doesn't seem to work 
with kernel 4.18.
  This is what I did: Installed Ubuntu, upgraded via aptitude to the latest 
packages, got the firmware "dvb-demod-si2168-b40-01.fw" and 
"dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* 
openelec.org and the modinfo output of si2168 and si2157), tried w_scan and 
failed (w_scan *can* find some signals but failes in getting the channels). 
That looks like this, f.e.:

  […}
  Scanning DVB-T2...
  474000: (time: 01:38.796) 
  482000: (time: 01:43.155) 
  49: (time: 01:45.163) signal ok:  QAM_AUTO f = 49 kHz 
I999B8C999D999T999G999Y999P0 (0:0:0)
  Info: no data from PAT after 2 seconds
  deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 
(0:0:0))
  […]

  Now, I tried an older kernel - 4.15, because it's still in the
  cosmics' repository and tried w_scan again: Success, although the TV-
  Stick doesn't find all the channels I found with Debian Testing.

  So, maybe there's a regression in the latest kernel regarding the TV-
  Stick-driver or there is another firmware which will work better with
  4.18…?

  Would be glad if someone could help to work that out…

  Greets!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarosch1516 F pulseaudio
   /dev/snd/controlC0:  jarosch1516 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 23:32:50 2018
  InstallationDate: Installed on 2018-10-24 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group Hi-Fi A88S3+
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic 
root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off 
spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: None
  dmi.board.name: Hi-Fi A88S3+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: None
  dmi.product.name: Hi-Fi A88S3+
  dmi.product.sku: None
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18

[Rick]

Kernel 4.21.1 and 4.19.14 have all the fixes.

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

Title:
  TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear developer(s),

  I used a vdr-installation on Debian testing, before. Switched over to Ubuntu 
since the release of cosmic because of problems with GPU/steam under Debian. 
Now, I have problems to configure vdr because my TV stick doesn't seem to work 
with kernel 4.18.
  This is what I did: Installed Ubuntu, upgraded via aptitude to the latest 
packages, got the firmware "dvb-demod-si2168-b40-01.fw" and 
"dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* 
openelec.org and the modinfo output of si2168 and si2157), tried w_scan and 
failed (w_scan *can* find some signals but failes in getting the channels). 
That looks like this, f.e.:

  […}
  Scanning DVB-T2...
  474000: (time: 01:38.796) 
  482000: (time: 01:43.155) 
  49: (time: 01:45.163) signal ok:  QAM_AUTO f = 49 kHz 
I999B8C999D999T999G999Y999P0 (0:0:0)
  Info: no data from PAT after 2 seconds
  deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 
(0:0:0))
  […]

  Now, I tried an older kernel - 4.15, because it's still in the
  cosmics' repository and tried w_scan again: Success, although the TV-
  Stick doesn't find all the channels I found with Debian Testing.

  So, maybe there's a regression in the latest kernel regarding the TV-
  Stick-driver or there is another firmware which will work better with
  4.18…?

  Would be glad if someone could help to work that out…

  Greets!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarosch1516 F pulseaudio
   /dev/snd/controlC0:  jarosch1516 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 23:32:50 2018
  InstallationDate: Installed on 2018-10-24 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group Hi-Fi A88S3+
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic 
root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off 
spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: None
  dmi.board.name: Hi-Fi A88S3+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: None
  dmi.product.name: Hi-Fi A88S3+
  dmi.product.sku: None
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18

[Rick]

Sorry I meant 4.20.1

** Tags removed: kernel-bug-exists-upstream

** Tags added: kernel-fixed-upstream

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

Title:
  TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear developer(s),

  I used a vdr-installation on Debian testing, before. Switched over to Ubuntu 
since the release of cosmic because of problems with GPU/steam under Debian. 
Now, I have problems to configure vdr because my TV stick doesn't seem to work 
with kernel 4.18.
  This is what I did: Installed Ubuntu, upgraded via aptitude to the latest 
packages, got the firmware "dvb-demod-si2168-b40-01.fw" and 
"dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* 
openelec.org and the modinfo output of si2168 and si2157), tried w_scan and 
failed (w_scan *can* find some signals but failes in getting the channels). 
That looks like this, f.e.:

  […}
  Scanning DVB-T2...
  474000: (time: 01:38.796) 
  482000: (time: 01:43.155) 
  49: (time: 01:45.163) signal ok:  QAM_AUTO f = 49 kHz 
I999B8C999D999T999G999Y999P0 (0:0:0)
  Info: no data from PAT after 2 seconds
  deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 
(0:0:0))
  […]

  Now, I tried an older kernel - 4.15, because it's still in the
  cosmics' repository and tried w_scan again: Success, although the TV-
  Stick doesn't find all the channels I found with Debian Testing.

  So, maybe there's a regression in the latest kernel regarding the TV-
  Stick-driver or there is another firmware which will work better with
  4.18…?

  Would be glad if someone could help to work that out…

  Greets!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarosch1516 F pulseaudio
   /dev/snd/controlC0:  jarosch1516 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 23:32:50 2018
  InstallationDate: Installed on 2018-10-24 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group Hi-Fi A88S3+
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic 
root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off 
spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: None
  dmi.board.name: Hi-Fi A88S3+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: None
  dmi.product.name: Hi-Fi A88S3+
  dmi.product.sku: None
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1811162] [NEW] Turn on CONFIG_REFCOUNT_FULL for non-x86 arches

[Steve Beattie]

Public bug reported:

The upstream kernel has added refcount protection, in two ways. For
arches that have provided a fast refcount_t implementation, they get it
automatically (this is signaled by ARCH_HAS_REFCOUNT, which as of 4.20
kernels, is only the x86 arch). For other arches, they can get refcount
protection via the CONFIG_REFCOUNT_FULL configure option. The upstream
arm64 and arm maintainers have enabled this configuration by default for
those arches, which has been carried into the ubuntu kernel config. We
should enable that for our other arches that do not provide
ARCH_HAS_REFCOUNT, namely ppc64el and s390x, to gain protection parity
with the rest of the architectures supported by ubuntu kernels.

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

Title:
  Turn on CONFIG_REFCOUNT_FULL for non-x86 arches

Status in linux package in Ubuntu:
  New

Bug description:
  The upstream kernel has added refcount protection, in two ways. For
  arches that have provided a fast refcount_t implementation, they get
  it automatically (this is signaled by ARCH_HAS_REFCOUNT, which as of
  4.20 kernels, is only the x86 arch). For other arches, they can get
  refcount protection via the CONFIG_REFCOUNT_FULL configure option. The
  upstream arm64 and arm maintainers have enabled this configuration by
  default for those arches, which has been carried into the ubuntu
  kernel config. We should enable that for our other arches that do not
  provide ARCH_HAS_REFCOUNT, namely ppc64el and s390x, to gain
  protection parity with the rest of the architectures supported by
  ubuntu kernels.

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

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

[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4

[P.I.Julius]

Hi Kai-Heng Feng,

I see you wrote me twice with the same suggestion and GOOD S as I
have given it up to easily on the first try but I can say now that GOT
IT WORKING!!!

So here is everything I found out and did to make it work on Fedora 29
(Kernel 4.18.11)

First of all of course rebuild the whole kernel with all the patches from here:
https://github.com/jakeday/linux-surface

FYI: it now supports Surface Pro 5 2017 (including battery and buttons
once qzed's patch is accepted too)

Added pcie_aspm=off to the kernel (NOT Needed, instead please keep
reading on) command but unfortunately that didn't do anything so started
digging and realized drivers/pci/pcie/aspm.c doesn't even compiles when
building the kernel so there is no code to check this command parameter
for the kernel anyway.

Then dug around some more and found I don't even have
"/sys/module/pcie_aspm/parameters/policy" file not even the directory
"/sys/module/pcie_aspm" so it seems the kernel for whatever reason (as
couldn't find PCIE_ASPM config related things in make menuconfig
either).

So wanted to make sure ASPM is indeed turned on for the wireles so I did:
lspci -vvv

and found this device:
01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 
802.11ac Wireless

with the following:
LnkCtl: ASPM L0s L1 Enabled;

Now I started to google around on how to disable ASPM on device basis as it 
seems these values are set from the firmware itself (if I understood things 
correctly) and found baybal's script (which enables ASPM on dell devices):
https://gist.github.com/baybal/b499fc5811a7073df0c03ab8da4be904

and instead of enabling I changed it to disable on the ethernet controller and 
that did the trick!!! Now doing lspci -s 01:00.0 -vvv shows me this instead:
LnkCtl: ASPM Disabled;

and since then I can play a YouTube video in 1440p and it never freezes
(and was freezing like in first minute before that) also realized that
if I changed to 720p it was dying out later bit did die out eventually
but now with ASPM off even 1440p works just fine and plays trough the
whole video.

I'm attaching the shell script that I quickly modified from baybal's
code, it needs to be run every time on startup (not on resume as far as
I could see/tested) and then all should be fine just please make sure
you verify that your Marvell network device is indeed at 01:00.0 and if
not just edit the file and change this.

So will keep on testing but it seems this fixed the problem and all
working just great now so thanks again Kai-Heng Feng for the pointers if
you give me the details I'm ready to send you over the small reward that
I offered for help/solution and it seems yours was the one so just let
me know the PayPal address and it will be on it's way.

Thanks again and hopefully this will be it and all the details/script
will be helpful to the others too.

Regards,
Julius

** Attachment added: "disable_wireless_aspm.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730924/+attachment/5228067/+files/disable_wireless_aspm.sh

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

Title:
  Wifi does down "crash" in Surface Pro 4

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

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  

[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

[Michael Reed]

How to Recreate

1.  Install Ubuntu 18.04.01 on a separate storage disk.
2.  Create VDs on H840/H740 using 9 physical disks 
a. 16 sliced RAID5; 10 GB each 
b. 16 sliced RAID1; 10 GB each 
c. 16 sliced RAID6; 10 GB each 
3.  Install JAVA 
4.  Download and copy vdbench to system 
a. 
https://www.oracle.com/technetwork/server-storage/vdbench-downloads-1901681.html
 
b. I used version 5.4.6 but reporter had 5.4.7 
5.  Run vdbench test “./vdbench -t” 
6.  Edit/create vdbench workprofile to match disks on H840 
a. Use lsscsi to show 48 H840/H740 disks 
7.  Run vd bench with profile 
a. ./vdbench -f vdbenchworkloadprofile.txt

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

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev 

[Kernel-packages] [Bug 1807686] Re: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set

[Seth Forshee]

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

Title:
  efi-lockdown patch causes -EPERM for some debugfs files even though
  CONFIG_LOCK_DOWN_KERNEL is not set

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == Comment: #0 - Dominik Klein  - 2018-12-10 
03:58:10 ==
  There seems to be a bug in the efi-lockdown patch as applied on top of 
vanilla for Cosmic kernels:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-cosmic.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  Also seems to be present for Disco as of today:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-disco.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  The problem is that part of the patch modifies kernel behavior
  independently of CONFIG_LOCK_DOWN_KERNEL being set or not causing
  issues on two debugfs files on s390x.

  Vasily Gorbik has already analyzed the problem and has posted a proposed fix 
here:
  https://lkml.org/lkml/2018/11/21/634
  https://lkml.org/lkml/2018/11/21/635

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

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

[Kernel-packages] [Bug 1807686] Re: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set

[Kamal Mostafa]

https://lists.ubuntu.com/archives/kernel-team/2019-January/097659.html

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

Title:
  efi-lockdown patch causes -EPERM for some debugfs files even though
  CONFIG_LOCK_DOWN_KERNEL is not set

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  == Comment: #0 - Dominik Klein  - 2018-12-10 
03:58:10 ==
  There seems to be a bug in the efi-lockdown patch as applied on top of 
vanilla for Cosmic kernels:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-cosmic.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  Also seems to be present for Disco as of today:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-disco.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  The problem is that part of the patch modifies kernel behavior
  independently of CONFIG_LOCK_DOWN_KERNEL being set or not causing
  issues on two debugfs files on s390x.

  Vasily Gorbik has already analyzed the problem and has posted a proposed fix 
here:
  https://lkml.org/lkml/2018/11/21/634
  https://lkml.org/lkml/2018/11/21/635

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

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

[Kernel-packages] [Bug 1807686] Re: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set

[Kamal Mostafa]

A bug in the pre-release version of efi-lockdown patch* applied to Cosmic and
later kernels improperly results in EPERM failures for some debugfs files.

Fixes: a1ba65da9cea ("UBUNTU: SAUCE: (efi-lockdown) debugfs: Restrict
debugfs when the kernel is locked down")

Upstream's version of this code never introduced the bug, so the fix patch
isn't upstream either.

The fix patch looks correct by inspection.

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

Title:
  efi-lockdown patch causes -EPERM for some debugfs files even though
  CONFIG_LOCK_DOWN_KERNEL is not set

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  == Comment: #0 - Dominik Klein  - 2018-12-10 
03:58:10 ==
  There seems to be a bug in the efi-lockdown patch as applied on top of 
vanilla for Cosmic kernels:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-cosmic.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  Also seems to be present for Disco as of today:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-disco.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  The problem is that part of the patch modifies kernel behavior
  independently of CONFIG_LOCK_DOWN_KERNEL being set or not causing
  issues on two debugfs files on s390x.

  Vasily Gorbik has already analyzed the problem and has posted a proposed fix 
here:
  https://lkml.org/lkml/2018/11/21/634
  https://lkml.org/lkml/2018/11/21/635

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

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

[Kernel-packages] [Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

[Nicholas Johnson]

How exactly should i add the line, just right below the last one? When i
type sudo nano /etc/pulse/daemon.conf i get this

# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; avoid-resampling = false
; enable-remixing = yes
; remixing-use-all-sink-channels = yes
; enable-lfe-remixing = no
; lfe-crossover-freq = 0

flat-volumes = no

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 20

; default-sample-format = s16le
; default-sample-rate = 44100
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right

; default-fragments = 4
; default-fragment-size-msec = 25

; enable-deferred-volume = yes
deferred-volume-safety-margin-usec = 1
; deferred-volume-extra-delay-usec = 0
realtime-scheduling = no

The "realtime-scheduling = no", was put there by me, but should i have
put the ; in front of it like the others or something?

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

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

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   

[Kernel-packages] [Bug 1807686] Re: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set

[Kamal Mostafa]

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
   Status: In Progress

** Changed in: linux (Ubuntu Disco)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Kamal Mostafa 
(kamalmostafa)

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

Title:
  efi-lockdown patch causes -EPERM for some debugfs files even though
  CONFIG_LOCK_DOWN_KERNEL is not set

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  == Comment: #0 - Dominik Klein  - 2018-12-10 
03:58:10 ==
  There seems to be a bug in the efi-lockdown patch as applied on top of 
vanilla for Cosmic kernels:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-cosmic.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  Also seems to be present for Disco as of today:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-disco.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  The problem is that part of the patch modifies kernel behavior
  independently of CONFIG_LOCK_DOWN_KERNEL being set or not causing
  issues on two debugfs files on s390x.

  Vasily Gorbik has already analyzed the problem and has posted a proposed fix 
here:
  https://lkml.org/lkml/2018/11/21/634
  https://lkml.org/lkml/2018/11/21/635

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

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

[Kernel-packages] [Bug 1807686] Re: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set

[Kamal Mostafa]

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

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

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

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  efi-lockdown patch causes -EPERM for some debugfs files even though
  CONFIG_LOCK_DOWN_KERNEL is not set

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  == Comment: #0 - Dominik Klein  - 2018-12-10 
03:58:10 ==
  There seems to be a bug in the efi-lockdown patch as applied on top of 
vanilla for Cosmic kernels:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-cosmic.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  Also seems to be present for Disco as of today:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-disco.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  The problem is that part of the patch modifies kernel behavior
  independently of CONFIG_LOCK_DOWN_KERNEL being set or not causing
  issues on two debugfs files on s390x.

  Vasily Gorbik has already analyzed the problem and has posted a proposed fix 
here:
  https://lkml.org/lkml/2018/11/21/634
  https://lkml.org/lkml/2018/11/21/635

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

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

[Kernel-packages] [Bug 1808567] Re: modules do not have retpoline modinfo

[Seth Forshee]

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

Title:
  modules do not have retpoline modinfo

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Even though they are built with CONFIG_RETPOLINE, modpost won't
  correctly insert the MODULE_INFO after CONFIG_RETPOLINE was made
  dependent on compiler support.

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

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

[Kernel-packages] [Bug 1807334] Re: Add support for ALC3277 codec on new Dell edge gateways

[Seth Forshee]

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

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

Title:
  Add support for ALC3277 codec on new Dell edge gateways

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  
  [Impact]
  The Dell Edge IoT Gateway is based on kabylake, and the audio codec is alc3277
  which is connected to kabylake PCH via SSP0, there is no ASoC machine driver
  for this board, so the audio (line-out and line-in) can't work.

  
  [Fix]
  write a ASoC machine driver for this board, and this driver is based on
  the existing driver kbl_rt5663_max98927.c

  
  [Test Case]
  play sound via line-out jack, record sound via line-in jack, all work well.

  
  [Regression Potential]
  Very low, this machine driver is specific to Dell Edge IoT Gateway. Only
  the machine with the HID:10EC3277 in the BIOS can use this driver.

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

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

[Kernel-packages] [Bug 1810457] Re: Update hisilicon SoC-specific drivers

[Seth Forshee]

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

Title:
  Update hisilicon SoC-specific drivers

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active 
development, including both hardware enablement and bug fix patches. With the 
amount of flux involved, identifying and cherry-picking individual patches 
would be more error prone then re-syncing with current upstream.

  [Test Case]
  The Ubuntu server certification suite, which includes network and storage 
tests.

  [Fix]
  Backport the localized driver changes up to v5.0-rc1.

  [Regression Risk]
  These changes are restricted to the hns and hisi_sas drivers, which only 
impact the D05 and D06 server development board platforms. To mitigate this 
risk, we have explicitly tested the proposed changes on these 2 platforms - 
changes are staged in ppa:pearl2-team/test. Of course, there is risk that these 
changes introduced regressions that our testing did not catch.

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

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

[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4

[Kai-Heng Feng]

What kernel version did you use with `pcie_aspm=off`?
There's bug in older kernel that `pcie_aspm=off` doesn't turn ASPM off.

Please use mainline kernel with that kernel parameter.

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

Title:
  Wifi does down "crash" in Surface Pro 4

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

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

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

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

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

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

[Seth Forshee]

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

Title:
  ldisc crash on reopened tty

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

  * Line discipline code is racy when we have buffer being flush while
  the tty is being initialized or reinitialized. For the first problem,
  we have an upstream patch since January 2018: b027e2298bd5 ("tty: fix
  data race between tty_init_dev and flush of buf") - although it is not
  in Ubuntu kernel 4.4, only in kernels 4.15 and subsequent ones.

  * For the race between the buffer flush while tty is being reopened,
  we have a patch that addresses this issue recently merged for 5.0-rc1:
  83d817f41070 ("tty: Hold tty_ldisc_lock() during tty_reopen()"). No
  Ubuntu kernel currently contains this patch, hence we're hereby
  submitting the SRU request. The upstream complete patch series for
  this is in [0].

  * The approach of both patches are similar - they rely in locking/semaphore 
to prevent race conditions. Some additional patches are
  necessary to prevent correlated issues, like preventing a potential deadlock 
due to bad prioritization in servicing I/O over releasing
  tty_ldisc_lock() - refer to c96cf923a98d ("tty: Don't block on IO when ldisc 
change is pending"). All the necessary fixes are grouped here in this SRU 
request.

  * The symptom of the race condition between the buffer flush and the
  tty reopen routine is a kernel crash with the following trace:

  BUG: unable to handle kernel paging request at 2268
  IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [...]
  Call Trace:
  [] ? kvm_sched_clock_read+0x1e/0x30
  [] n_tty_receive_buf2+0x14/0x20
  [] flush_to_ldisc+0xd5/0x120
  [] process_one_work+0x156/0x400
  [] worker_thread+0x11a/0x480
  [...]

  * A kernel crash was collected from an user, analysis is present in
  comment #4 in this LP.

  [Test Case]

  * It is not trivial to trigger this fault, but the usual recipe is to
  keep accessing a machine through SSH (or keep killing getty when in
  IPMI serial console) and in some way run commands before the terminal
  is ready in that machine (like hacking some echo into ttySx or pts in
  an infinite loop).

  * We have reports of users that could reproduce this issue in their
  production environment, and with the patches present in this SRU
  request the problem was fixed.

  [Regression Potential]

  * tty subsystem is highly central and patches in that area are always
  delicate. For example, the upstream series [0] is a re-spin (V6) due
  to a hard to reproduce issue reported in the PA-RISC architecture,
  which was found in the V5 iteration [1] but was fixed by the patch
  c96cf923a98d, present in this SRU request.

  * The patchset [0] is present in tty-next tree since mid-November, and
  the patch b027e2298bd5 is available upstream since January/2018 (it's
  available in both Ubuntu kernels 4.15 and 4.18), so the overall
  likelihood of regressions is low.

  * These patches were sniff-tested for the 3 versions (4.4, 4.15 and
  4.18) and didn't show any issues.

  [0] https://marc.info/?l=linux-kernel=154103190111795
  [1] https://marc.info/?l=linux-kernel=153737852618183

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

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

[Kernel-packages] [Bug 1810702] Re: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU

[Seth Forshee]

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

Title:
  HP mobile workstations with hybrid graphics support, can not directly
  output to external monitors by dGPU

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

Bug description:
  For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
directly output to external monitors; however, Nvidia and AMD's Linux drivers 
aren't able to support this feature.
  
  The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

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

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

[Kernel-packages] [Bug 1811093] Re: Bogus "Out of Memory" compiz invoked oom-killer

[Craig]

Not sure when it started.  I can only go by the logs I have, and they
only go back nine days.  But the postgres job that I mentioned
previously, and which caused several oom-kill's in a row, was last run a
month and a half ago, and at that time it ran without any problems. But
it may have run without being logged into Unity desktop, not sure.  And
other random oom-kills may have gone unnoticed.

I'll take a look at installing the upstream kernels you cited.  I've
never manually installed a kernel from the .deb's before.  I guess I'll
use
https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show=KernelMainlineBuilds
as a guide.  Looks like I'll have to uninstall VirtualBox.  If that's
all I have to do, and if installing the upstream kernels doesn't
generate any errors, I'll report back with findings.

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

Title:
  Bogus "Out of Memory" compiz invoked oom-killer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has happened five times in the past week (four times in the past
  36 hours):

kernel: compiz invoked oom-killer:

  There is plenty of free core memory and almost no swap in use when it
  happens.  This is Xenial with kernel version is 4.4.0-141, which
  contains fix to previously reported bug #1655842 "Out of Memory"
  oom-killer bug.  I only have one week of logs to go by, which contain
  five occurrences.  It has happened four times in the past 36 hours.
  Sometimes it happens right after logging into the unity / lighdm
  desktop (three out of five times), but not always.  In four out of
  five occurrences a postgres job was running and oom-killer killed
  postgres.  In the one other instance, postgres was quietly idle in the
  background and oom-killer killed Thunderbird.  Kernel messages in
  syslog from five occurrences:

  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0

  Additional info:

  $> lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  $> cat /proc/version_signature
  Ubuntu 4.4.0-141.167-generic 4.4.162

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

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

[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4

[P.I.Julius]

Hi Guys,

Just a note that may be helpful for tracking this down here is what I
found out lately.

If in "drivers/net/wireless/marvell/mwifiex/cmdevt.c" file,
"mwifiex_cmd_timeout_func(struct timer_list *t)" function I comment out
these:

//if (adapter->if_ops.device_dump)
//adapter->if_ops.device_dump(adapter);

//if (adapter->if_ops.card_reset)
//adapter->if_ops.card_reset(adapter);

The wifi will still drop with the timeout command but at least the
mwifiex_pcie module wont freeze and so you will be able to restart or
even put the pc into sleep and after a resume simply continue where you
left off without having to do a hard restart by long pressing power
button.

It seems the card_reset(adapter) function is the one freezing the module
and so freezing the wifi, so will try to see what's there but if any of
you have any idea how we could reset the adapter and even (just for
testing why not) always reload the firmware and see if that fixes it as
it seems the resume does the same thing and that makes things work
again.

Regards,
Julius

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

Title:
  Wifi does down "crash" in Surface Pro 4

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

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

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

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

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

[Kernel-packages] [Bug 1764792] Re: Build Nvidia drivers in conjunction with kernel

[Seth Forshee]

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

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

Title:
  Build Nvidia drivers in conjunction with kernel

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  We want to deliver a great out of the box experience of Ubuntu users
  running on Nvidia GPU enabled platforms (including instances in the
  cloud).  Can we explore the possibility of pre-building the nvidia
  drivers alongside the kernel build, but not pre-link the drivers.

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

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

[Kernel-packages] [Bug 1587087] Re: OOM in guest Ubuntu with inflated balloon

[Joseph Salisbury]

** Changed in: linux-lts-utopic (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  OOM in guest Ubuntu with inflated balloon

Status in linux-lts-utopic package in Ubuntu:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released

Bug description:
  There is QEMU/KVM and a Linux OS running inside the guest.
  Inside the Linux guest a balloon consumes memory in accordance with
  commands performed on the host side in QEMU. Rapid increases of memory 
consumption
  inside the guest may end up with guest OOMs
  since memory locked by balloon couldn’t be returned to the guest OS/vm in 
time.

  The problem is addressed in mainstream Linux with the following
  patchset:

  commit 5a10b7dbf904bfe01bb9fcc6298f7df09eed77d5
  Author: Raushaniya Maksudova 
  Date: Mon Nov 10 09:36:29 2014 +1030
  virtio_balloon: free some memory from balloon on OOM

  Excessive virtio_balloon inflation can cause invocation of OOM-killer,
  when Linux is under severe memory pressure. Various mechanisms are
  responsible for correct virtio_balloon memory management. Nevertheless
  it is often the case that these control tools does not have enough time
  to react on fast changing memory load. As a result OS runs out of memory
  and invokes OOM-killer. The balancing of memory by use of the virtio
  balloon should not cause the termination of processes while there are
  pages in the balloon. Now there is no way for virtio balloon driver to
  free some memory at the last moment before some process will be get
  killed by OOM-killer.

  This does not provide a security breach as balloon itself is running
  inside guest OS and is working in the cooperation with the host. Thus
  some improvements from guest side should be considered as normal.

  To solve the problem, introduce a virtio_balloon callback which is
  expected to be called from the oom notifier call chain in out_of_memory()
  function. If virtio balloon could release some memory, it will make
  the system to return and retry the allocation that forced the out of
  memory killer to run.

  Allocate virtio feature bit for this: it is not set by default,
  the the guest will not deflate virtio balloon on OOM without explicit
  permission from host.

  Signed-off-by: Raushaniya Maksudova 
  Signed-off-by: Denis V. Lunev 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: Rusty Russell 

  commit 1fd9c67203af91977bf3b964ff3744cf74fc6f3f
  Author: Raushaniya Maksudova 
  Date: Mon Nov 10 09:35:29 2014 +1030

  virtio_balloon: return the amount of freed memory from
  leak_balloon()

  This value would be useful in the next patch to provide the amount of
  the freed memory for OOM killer.

  Signed-off-by: Raushaniya Maksudova 
  Signed-off-by: Denis V. Lunev 
  CC: Rusty Russell 
  CC: Michael S. Tsirkin 
  Signed-off-by: Rusty Russell 

  The problem is present in Ubuntu 14.10

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

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

[Kernel-packages] [Bug 1587089] Re: Hide "ballooned" memory from /proc in guest Ubuntu

[Joseph Salisbury]

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

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

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

Title:
  Hide "ballooned" memory from /proc in guest Ubuntu

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux source package in Wily:
  Fix Released
Status in linux-lts-utopic source package in Wily:
  New

Bug description:
  There is QEMU/KVM and a Linux guest running inside the guest. The amount
  of memory available for guest could be adjusted by balloon for better
  host scalability. The problem that this change is visible for end-user
  actually using the guest. This could (potentially) result in lawsuite
  from the end-user to hosting provides. 

  The problem is addressed in mainstream Linux with the following patch
  set:

  commit 997e120843e82609c8d99a9d5714e6cf91e14cbe
  Author: Denis V. Lunev 
  Date:   Thu Aug 20 00:49:49 2015 +0300
  virtio_balloon: do not change memory amount visible via /proc/meminfo
  
  Balloon device is frequently used as a mean of cooperative memory control
  in between guest and host to manage memory overcommitment. This is the
  typical case for any hosting workload when KVM guest is provided for
  end-user.
  
  Though there is a problem in this setup. The end-user and hosting provider
  have signed SLA agreement in which some amount of memory is guaranted for
  the guest. The good thing is that this memory will be given to the guest
  when the guest will really need it (f.e. with OOM in guest and with
  VIRTIO_BALLOON_F_DEFLATE_ON_OOM configuration flag set). The bad thing
  is that end-user does not know this.
  
  Balloon by default reduce the amount of memory exposed to the end-user
  each time when the page is stolen from guest or returned back by using
  adjust_managed_page_count and thus /proc/meminfo shows reduced amount
  of memory.
  
  Fortunately the solution is simple, we should just avoid to call
  adjust_managed_page_count with VIRTIO_BALLOON_F_DEFLATE_ON_OOM set.
  
  Signed-off-by: Denis V. Lunev 
  CC: Michael S. Tsirkin 
  Signed-off-by: Michael S. Tsirkin 

  
  commit b4d34037329f46ed818d3b0a6e1e23b9c8721f79
  Author: Denis V. Lunev 
  Date:   Thu Aug 20 00:49:48 2015 +0300
  virtio_ballon: change stub of release_pages_by_pfn
  
  and rename it to release_pages_balloon. The function originally takes
  arrays of pfns and now it takes pointer to struct virtio_ballon.
  This change is necessary to conditionally call adjust_managed_page_count
  in the next patch.
  
  Signed-off-by: Denis V. Lunev 
  CC: Michael S. Tsirkin 
  Signed-off-by: Michael S. Tsirkin 

  The issue affects ubuntu_server_14.0, ubuntu_server_15.04

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

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

[Kernel-packages] [Bug 1587091] Re: Extended statistics from balloon for proper memory management

[Joseph Salisbury]

** Changed in: linux-lts-utopic (Ubuntu)
   Status: In Progress => Fix Released

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

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

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

Title:
  Extended statistics from balloon for proper memory management

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Won't Fix
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  There is QEMU/KVM and a Linux OS running inside the guest. 
  Inside the Linux guest a balloon consumes memory in accordance with 
  commands performed on the host side in QEMU and reports some statistics 
through memstat structure.
  For the Linux guest reported “free” value doesn’t describe the guest memory 
pressure at all.
  The provided patch set in Linux kernel extends the stat with available field.

  The problem is addressed in mainstream Linux with the following
  patchset:

  commit
  5057dcd0f1aaad57e07e728ba20a99e205c6b9de
  Author: Igor Redko 
  Date: Thu Mar 17 15:09:34 2016 -0700
  virtio_balloon: export 'available' memory to balloon statistics

  Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory
  statistics protocol, corresponding to 'Available' in /proc/meminfo.

  It indicates to the hypervisor how big the balloon can be inflated
  without pushing the guest system to swap.

  Signed-off-by: Igor Redko 
  Signed-off-by: Denis V. Lunev 
  Reviewed-by: Roman Kagan 
  Cc: Michael S. Tsirkin 
  Signed-off-by: Andrew Morton 
  Signed-off-by: Linus Torvalds 

  
  commit d02bd27bd33dd7e8d22594cd568b81be0cb584cd
  Author: Igor Redko 
  Date: Thu Mar 17 15:09:34 2016 -0700
  mm/page_alloc.c: calculate 'available' memory in a separate function

  Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory
  statistics protocol, corresponding to 'Available' in /proc/meminfo.

  It indicates to the hypervisor how big the balloon can be inflated
  without pushing the guest system to swap.  This metric would be very
  useful in VM orchestration software to improve memory management of
  different VMs under overcommit.

  This patch (of 2):

  Factor out calculation of the available memory counter into a separate
  exportable function, in order to be able to use it in other parts of the
  kernel.

  In particular, it appears a relevant metric to report to the hypervisor
  via virtio-balloon statistics interface (in a followup patch).

  Signed-off-by: Igor Redko 
  Signed-off-by: Denis V. Lunev 
  Reviewed-by: Roman Kagan 
  Cc: Michael S. Tsirkin 
  Signed-off-by: Andrew Morton 
  Signed-off-by: Linus Torvalds 

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

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

[Kernel-packages] [Bug 1634862] Re: PPC + kernel 4.8 swap_dup: Bad swap file entry 2c0000000016ed28

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  PPC + kernel 4.8 swap_dup: Bad swap file entry 2c16ed28

Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Yakkety:
  Won't Fix

Bug description:
  Hi 
  on ppc machines with Ubuntu 16.10 (Yakkety Yak), after upgrading to last 
Ubuntu kernel (4.8), and running installation of MLNX_OFED Driver package that 
run a compilation jobs that equal to number of CPUs , the System hangs and we 
got a bad swap file message with pages and pages of the following showing, this 
is just a sample from the system log.
  I had been running with kernel 4.4 and everything worked ok on the same 
machine, so when we upgrade to kernel 4.8 we start to see the following error 

  dmseg log gets lots of this message:

  -
  [10101.785548] swap_dup: Bad swap file entry 2c16ed28
  [10101.785595] swap_dup: Bad swap file entry 2c16ed29
  [10101.785606] swap_dup: Bad swap file entry 2c16ed2a
  [10101.785613] swap_dup: Bad swap file entry 2c16ed2b
  [10101.785622] swap_dup: Bad swap file entry 2c16ed2c
  [10101.785629] swap_dup: Bad swap file entry 2c16ed2d
  [10101.785637] swap_dup: Bad swap file entry 2c16ed2e
  [10101.785648] swap_dup: Bad swap file entry 2c16ed2f
  [10101.785659] swap_dup: Bad swap file entry 2c16ed2e   and call 
trace : 
  Call Trace:  
  [10101.785773] [c002fb923ac0] [c0b9db00] dump_stack+0xb0/0xf0 
(unreliable)  
  [10101.785789] [c002fb923b00] [c0b9b330] dump_header+0x84/0x224   
  
  [10101.785801] [c002fb923bd0] [c025d724] 
oom_kill_process+0x3b4/0x5c0   
  [10101.785811] [c002fb923c80] [c025dc80] 
out_of_memory+0x290/0x580  
  [10101.785822] [c002fb923d30] [c025dff4] 
pagefault_out_of_memory+0x84/0xb0  
  [10101.785836] [c002fb923d80] [c0b94d44] 
do_page_fault+0x7c4/0x7d0  
  [10101.785849] [c002fb923e30] [c0008948] 
handle_page_fault+0x10/0x30   


  
  # cat /etc/*-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.10
  DISTRIB_CODENAME=yakkety
  DISTRIB_DESCRIPTION="Ubuntu 16.10"
  NAME="Ubuntu"
  VERSION="16.10 (Yakkety Yak)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.10"
  VERSION_ID="16.10"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="http://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=yakkety
  UBUNTU_CODENAME=yakkety

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

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

[Kernel-packages] [Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => 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/1648388

Title:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system
  hangs while rebooting

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or 
UEFI mode.
  System hangs while rebooting

  Not found the issue in RAID0
  No issue on Ubuntu14.04
  Driver-OS inbox support

  Below as error messages
  ===
  INFO:  task systemd-shutdow:1 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task  jbd2/md126p2-8:1732 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task ext4lazyinit:1873 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task kworker/u66:4:3139 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ===

  WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't 
hang while rebooting:
  vm.dirty_background_ratio=5
  vm.dirty_ratio=10
  kernel.panic=3
  kernel.hung_task_panic=1
  kernel.hung_task_timeout_secs=30

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b
  InstallationDate: Installed on 2016-12-15 (10 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Dell DCS6430G
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: Dell
  dmi.bios.version: 2.0.3
  dmi.board.name: 038VV0
  dmi.board.vendor: Dell
  dmi.board.version: X01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell
  dmi.modalias: 
dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr:
  dmi.product.name: DCS6430G
  dmi.sys.vendor: Dell

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1648388/+subscriptions

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

[Kernel-packages] [Bug 1640297] Re: 16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 4.4.0-42-generic and older

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab.
  Boots fine in 4.4.0-42-generic and older

Status in linux package in Ubuntu:
  In Progress

Bug description:
  System hangs during boot with 4.4.0-45-generic if /etc/crypptab
  contains a valid entry. Passphrase prompt never seen. Black screen
  with blinking underscore in upper left corner. Repeated attempts to
  type passphrase have no effect.

  There are two workarounds:
  1) Comment out line referring the encrypted partition in /etc/crypttab and 
/etc/fstab. Mount the partition manually after boot completes
  2) Boot in 4.4.0-42-generic which works as do earlier versions. i.e. the user 
provides passphrase at the prompt during boot and the system finishes booting

  robert@kalymnos:~$ cat /etc/crypttab
  spare2 UUID=498b08bb-5e6b-4ddf-8b37-e059665a34e6 none luks
  robert@kalymnos:~$ grep mapper /etc/fstab
  /dev/mapper/spare2/spare2 ext4 defaults 0 2
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2413 F pulseaudio
   /dev/snd/controlC0:  robert 2413 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=291e75f9-3814-499b-bbb2-f385c164b942
  InstallationDate: Installed on 2016-08-18 (83 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-42-generic 
root=UUID=24166ab8-327a-4477-96d2-3f57b4a47657 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 07/29/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SOX5810J.86A.5600.2013.0729.2250
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DX58SO
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE29331-701
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSOX5810J.86A.5600.2013.0729.2250:bd07/29/2013:svn:pn:pvr:rvnIntelCorporation:rnDX58SO:rvrAAE29331-701:cvn:ct2:cvr:
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2413 F pulseaudio
   /dev/snd/controlC0:  robert 2413 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=291e75f9-3814-499b-bbb2-f385c164b942
  InstallationDate: Installed on 2016-08-18 (83 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-42-generic 
root=UUID=24166ab8-327a-4477-96d2-3f57b4a47657 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 07/29/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: 

[Kernel-packages] [Bug 1561830] Re: Hard disk writes fail in 16.04 daily on nForce 430

[Joseph Salisbury]

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Hard disk writes fail in 16.04 daily on nForce 430

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

Bug description:
  I have an old PC I use for testing new operating systems.  It has
  previously had Ubuntu 15.10 installed and working.  The motherboard is
  an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce
  6150 GPU.  I have installed an Nvidia GT220 card to use for more
  modern video support.

  When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop-
  amd64.iso file downloaded 24/03/2016  18:17), it starts to write to
  the hard disk (Samsung HD103UJ), and after a short time the install
  got lots of disk write errors in kern.log.  After the errors, the disk
  was unable to be read either, with "fdisk -l /dev/sda" failing to read
  a sector, where it had worked before starting the install.  Unplugging
  the SATA cable to the drive and plugging it in again made the drive
  work again (on /dev/sdc), but another attempt to install failed with
  the same write errors.

  I noticed that the log had swap write errors also, so I rebooted the
  install DVD again, and this time did a "swapoff -a" command before
  attempting to install, but got the same errors again.  So I found my
  Ubuntu 15.10 install DVD and tried a new install from that, which
  worked just fine.

  On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that
  the DVD based system would run normally, then tried mounting the EXT4
  system partition I had just installed using the 15.10 install DVD.
  That worked, so I tried dd commands to do test writes to that
  partition.  The following commands worked:

dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k
dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k

  but when I did this command:

dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k

  after a while errors started appearing in kern.log, just as with the
  attempts to install 16.04.

  It appears that with sustained write activity, the errors will start
  and then the drive will become unusable until it is unplugged and
  plugged in again.

  I have attached the kern.log and syslog files from the 15.10 install
  that worked, and the 16.04 install attempt that failed.  The first
  error message appears to be this:

  ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF
  ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0
  dhfis 0x1 dmafis 0x0 sdbfis 0x0

  which leads me to suspect a problem with the handling of the SATA 
controller's interrupts.
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2233 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2233 F pulseaudio
  CasperVersion: 1.368
  DistroRelease: Ubuntu 16.04
  IwConfig:
   enp0s20   no wireless extensions.
   
   lono wireless extensions.
   
   enp2s9no wireless extensions.
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/07/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401
  dmi.board.name: M2NPV-VM
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 1.xx
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 1501281] Re: Frequent freezes on 15.04 with kernel 3.19.0-29+

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  Frequent freezes on 15.04 with kernel 3.19.0-29+

Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Vivid:
  Won't Fix

Bug description:
  I am experiencing systematic freezes since my kernel was automatically
  upgraded to 3.19.0-29. Same problem happens if I use kernel 3.19.0-30.
  If I use kernel 3.19.0-28 it does not freeze any more.

  Behaviour is described with more details at

  http://askubuntu.com/questions/679212/frequent-freezes-on-15-04-with-
  kernel-3-19-0-29

  and at

  http://askubuntu.com/questions/673767/frequent-freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrea 3174 F pulseaudio
   /dev/snd/pcmC0D0p:   andrea 3174 F...m pulseaudio
   /dev/snd/controlC0:  andrea 3174 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 30 12:45:03 2015
  HibernationDevice: RESUME=UUID=7f029a53-8d17-4db1-b66f-d131578efe68
  InstallationDate: Installed on 2010-04-15 (1993 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  IwConfig:
   eth2  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic 
root=UUID=5d76a02d-2ed2-484a-81da-3cf5ce0ab3fb ro crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (153 days ago)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0303
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E
  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.:bvr0303:bd04/18/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1381005] Re: Long stdin from terminal can result in code execution

[Joseph Salisbury]

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

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

Title:
  Long stdin from terminal can result in code execution

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

Bug description:
  Under certain conditions, the input entered from a terminal with a
  foreground process waiting for stdin, can be interpreted and executed
  by the shell.

  Steps to reproduce:
  1) Open a terminal
  2) Run a simple program that waits for stdin (like cat, tee, head, tail, ...) 
or even the bash-builtin command read. No need to specify arguments
  3) Type or paste exactly 4096 ASCII characters into the terminal (see sample 
attachment)
  4) Press Enter

  What should happen:
  The program in foreground reads 4097 characters (the last one is new line).

  What actually happens:
  Instead of reading the input, the current program exits (read() only reads 
one character before EOF) and the shell executes the same input starting from 
the second character.

  I believe that the issue can be reproduced with:
  - any terminal (tested on xterm, gnome-terminal, tty)
  - any shell (tested on bash, zsh)
  - any program that reads stdin from terminal (not attached to a pipe)

  Debugging the shell with gdb suggests that the bug is in the implementation 
of read(), hence libc6 or under (kernel).
  Specifically, the bug is caused by read() reading only one character (new 
line) when entering a text of 4096 characters in stdin on the terminal. It 
looks like read() is then closing the stdin descriptor.
  If the input is 4097 characters long, read() will read two characters and the 
shell will interpret from the 3rd character, and so on.

  Verified on:
  Ubuntu 14.04.1 LTS

  Kernel:
  3.13.0-24-generic x86_64
  3.13.0-32-generic x86_64
  3.13.0-36-generic x86_64

  libc6:
  2.19-0ubuntu6
  2.19-0ubuntu6.1
  2.19-0ubuntu6.3

  I'm happy to provide more information if it helps.
  Angelo

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

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

[Kernel-packages] [Bug 1566726] Re: System freeze after update to 3.16.0-69-generic [NULL pointer reference in radeon_fence_ref]

[Joseph Salisbury]

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

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

Title:
  System freeze after update to 3.16.0-69-generic [NULL pointer
  reference in radeon_fence_ref]

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Fix Released

Bug description:
  So far I've seen this happen on 2 systems today. On one only X froze, the 
other one panicked.
  Booting into 3.16.0-67 is the workaround for now

  ProblemType: KernelOops
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Date: Wed Apr  6 09:57:21 2016
  Failure: oops
  OopsText:
   BUG: unable to handle kernel NULL pointer dereference at 0008
   IP: [] radeon_fence_ref+0xd/0x50 [radeon]
   PGD 0
   Oops: 0002 [#1] SMP
   Modules linked in: xt_nat xt_tcpudp veth xt_conntrack ipt_MASQUERADE 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp llc aufs arc4 
md4 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm bnep 
bluetooth 6lowpan_iphc nls_utf8 cifs binfmt_misc fscache snd_hda_codec_via 
snd_hda_codec_generic radeon snd_hda_codec_hdmi snd_hda_intel 
snd_hda_controller snd_hda_codec snd_hwdep joydev snd_pcm snd_seq_midi ttm 
snd_seq_midi_event drm_kms_helper drm snd_rawmidi snd_seq i2c_algo_bit 
snd_seq_device kvm snd_timer snd ppdev serio_raw soundcore shpchp lp edac_core 
edac_mce_amd i2c_nforce2 mac_hid parport_pc asus_atk0110 k10temp parport 
hid_cherry hid_generic usbhid pata_acpi hid psmouse sata_nv forcedeth pata_amd
   CPU: 1 PID: 1543 Comm: Xorg Tainted: G   OE 3.16.0-69-generic 
#89~14.04.1-Ubuntu
   Hardware name: System manufacturer System Product Name/M4N68T-M-V2, BIOS 
050108/03/2010
   task: 8800b9b45bb0 ti: 8800b9e28000 task.ti: 8800b9e28000
   RIP: 0010:[]  [] 
radeon_fence_ref+0xd/0x50 [radeon]
   RSP: 0018:8800b9e2bad0  EFLAGS: 00010286
   RAX:  RBX: 880035cf55f8 RCX: 880035cf4000
   RDX: 0001 RSI:  RDI: 
   RBP: 8800b9e2bbd0 R08: 880035cf4d08 R09: 880035cf4000
   R10:  R11: 8800b9e2bde8 R12: 880035cf5550
   R13: 8800b9e2bba8 R14: 8800b9e2bb78 R15: 0020
   FS:  7f6e2ab398c0() GS:8801bfc4() knlGS:
   CS:  0010 DS:  ES:  CR0: 80050033
   CR2: 0008 CR3: b8192000 CR4: 07e0
   Stack:
    c0414ad4 8800b9b45bb0 8800b9b45bb0 880035cf4000
    8800b9e2bca8 edc0b9e2bb90  00200100
    0004a8e0 8800b9e2bb78  
   Call Trace:
    [] ? radeon_sa_bo_new+0x2b4/0x4f0 [radeon]
    [] ? insert_pfn.isra.61+0x48/0xa0
    [] radeon_ib_get+0x33/0xe0 [radeon]
    [] radeon_cs_ioctl+0x14b/0x770 [radeon]
    [] drm_ioctl+0x1ec/0x660 [drm]
    [] ? __do_page_fault+0x20c/0x560
    [] radeon_drm_ioctl+0x4b/0x80 [radeon]
    [] do_vfs_ioctl+0x2e0/0x4c0
    [] SyS_ioctl+0x81/0xa0
    [] system_call_fastpath+0x1a/0x1f
   Code: dc 48 8b 3b 89 c1 44 89 e2 48 c7 c6 70 66 4a c0 31 c0 e8 d7 75 10 c1 
eb c2 0f 1f 44 00 00 66 66 66 66 90 48 89 f8 ba 01 00 00 00  0f c1 57 08 83 
c2 01 83 fa 01 7e 01 c3 80 3d 5e 8b 11 00 00
   RIP  [] radeon_fence_ref+0xd/0x50 [radeon]
    RSP 
   CR2: 0008
   ---[ end trace 4dfa7ee83f5a67e2 ]---

  Package: linux-image-3.16.0-69-generic 3.16.0-69.89~14.04.1
  SourcePackage: linux
  Tags: kernel-oops
  Uname: Linux 3.16.0-69-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Dependencies:
   adduser 3.113+nmu3ubuntu3
   apt-utils 1.0.1ubuntu2.11
   base-passwd 3.5.33
   busybox-initramfs 1:1.21.0-1ubuntu1
   coreutils 8.21-1ubuntu5.4
   cpio 2.11+dfsg-1ubuntu1.2
   dbus 1.6.18-0ubuntu4.3
   debconf 1.5.51ubuntu2
   debconf-i18n 1.5.51ubuntu2
   debianutils 4.4
   dmsetup 2:1.02.77-6ubuntu2
   dpkg 1.17.5ubuntu5.5
   e2fslibs 1.42.9-3ubuntu1.3
   e2fsprogs 1.42.9-3ubuntu1.3
   findutils 4.4.2-7
   gcc-4.8-base 4.8.4-2ubuntu1~14.04.1
   gcc-4.9-base 4.9.3-0ubuntu4
   gettext-base 0.18.3.1-1ubuntu3
   grub-common 2.02~beta2-9ubuntu1.7
   grub-gfxpayload-lists 0.6
   grub-pc 2.02~beta2-9ubuntu1.7
   grub-pc-bin 2.02~beta2-9ubuntu1.7
   grub2-common 2.02~beta2-9ubuntu1.7
   ifupdown 0.7.47.2ubuntu4.4
   initramfs-tools 0.103ubuntu4.3
   initramfs-tools-bin 0.103ubuntu4.3
   initscripts 2.88dsf-41ubuntu6.3
   insserv 1.14.0-5ubuntu2
   iproute2 3.12.0-2ubuntu1
   isc-dhcp-client 4.2.4-7ubuntu12.4
   isc-dhcp-common 4.2.4-7ubuntu12.4
   klibc-utils 2.0.3-0ubuntu1
   kmod 15-0ubuntu6
   libacl1 2.2.52-1
   libapparmor1 2.8.95~2430-0ubuntu5.3
   libapt-inst1.5 1.0.1ubuntu2.11
   libapt-pkg4.12 1.0.1ubuntu2.11
   

[Kernel-packages] [Bug 1492632] Re: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA

[Joseph Salisbury]

** Changed in: linux (Ubuntu Wily)
   Status: In Progress => Won't Fix

** Changed in: linux (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA

Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Wily:
  Won't Fix

Bug description:
  My Asus Zenbook 303LA (UX303LA-DS51T) eventually gets a corrupted
  display. Everything repeatedly shifts horizontally. I found the
  following in the kernel log. The corruption does not have a 1:1
  relation with the occurrence of the error however.

  ===
  [   99.275807] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
base.adjusted_mode.crtc_clock (expected 138780, found 92519)
  [   99.275810] [ cut here ]
  [   99.275822] WARNING: CPU: 1 PID: 909 at 
/build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 
check_crtc_state+0x2c5/0x440 [i915]()
  [   99.275823] pipe state doesn't match!
  [   99.275824] Modules linked in: bnep arc4 asus_nb_wmi asus_wmi 
sparse_keymap intel_rapl x86_pkg_temp_thermal iwlmvm intel_powerclamp coretemp 
mac80211 snd_soc_rt5640 kvm_intel snd_soc_rl6231 snd_soc_core kvm uv
  cvideo snd_compress ac97_bus snd_hda_codec_hdmi snd_pcm_dmaengine 
snd_hda_codec_conexant videobuf2_vmalloc snd_hda_codec_generic snd_seq_midi 
iwlwifi videobuf2_memops btusb snd_seq_midi_event serio_raw videobuf2_
  core snd_rawmidi btrtl btbcm snd_hda_intel v4l2_common btintel videodev 
snd_hda_codec cfg80211 lpc_ich bluetooth snd_hda_core input_leds joydev mei_me 
hid_multitouch media snd_hwdep mei shpchp snd_pcm processor_t
  hermal_device intel_soc_dts_iosf iosf_mbi snd_seq snd_seq_device snd_timer 
snd soundcore snd_soc_sst_acpi acpi_pad dw_dmac acpi_als int3402_thermal 
i2c_designware_platform dw_dmac_core
  [   99.275856]  kfifo_buf i2c_designware_core 8250_dw spi_pxa2xx_platform 
industrialio int3400_thermal int340x_thermal_zone mac_hid acpi_thermal_rel 
sunrpc parport_pc ppdev lp parport autofs4 jitterentropy_rng dr
  bg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid psmouse 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 
lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_k
  ms_helper ahci drm libahci wmi sdhci_acpi video sdhci i2c_hid hid
  [   99.275877] CPU: 1 PID: 909 Comm: Xorg Not tainted 4.2.0-7-generic 
#7-Ubuntu
  [   99.275878] Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS 
UX303LAB.203 12/11/2014
  [   99.275879]  c02ce1e8 8800d3a977e8 817b0465 

  [   99.275881]  8800d3a97838 8800d3a97828 81076536 
8800d3a97858
  [   99.275883]  8800d3a978c0 8800d374f800 0001 
8800d374fb50
  [   99.275885] Call Trace:
  [   99.275890]  [] dump_stack+0x45/0x57
  [   99.275893]  [] warn_slowpath_common+0x86/0xc0
  [   99.275895]  [] warn_slowpath_fmt+0x46/0x50
  [   99.275906]  [] ? intel_pipe_config_compare+0xb08/0xc60 
[i915]
  [   99.275916]  [] check_crtc_state+0x2c5/0x440 [i915]
  [   99.275929]  [] intel_modeset_check_state+0x20e/0x6b0 
[i915]
  [   99.275940]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
  [   99.275951]  [] ? drm_mode_create+0x25/0x60 [drm]
  [   99.275959]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [   99.275967]  [] drm_mode_setcrtc+0x3a8/0x4c0 [drm]
  [   99.275973]  [] drm_ioctl+0x125/0x610 [drm]
  [   99.275980]  [] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
  [   99.275983]  [] do_vfs_ioctl+0x285/0x470
  [   99.275986]  [] ? recalc_sigpending+0x1f/0x60
  [   99.275988]  [] ? __set_task_blocked+0x32/0x70
  [   99.275990]  [] SyS_ioctl+0x79/0x90
  [   99.275992]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [   99.275994] ---[ end trace 6172e2f40143dd37 ]---
  ===

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1151 F pulseaudio
   /dev/snd/controlC1:  peter  1151 F pulseaudio
  Date: Sat Sep  5 15:15:04 2015
  InstallationDate: Installed on 2015-07-05 (62 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150704)
  MachineType: ASUSTeK COMPUTER INC. UX303LAB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=9b60dccb-1ce9-4ddf-82f6-cc03b3c01b5c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or 

[Kernel-packages] [Bug 1549354] Re: After upgrading to 4.2.0.30 Elantech touchpad not detected

[Joseph Salisbury]

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

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

Title:
  After upgrading to 4.2.0.30 Elantech touchpad not detected

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

Bug description:
  Elan Touchpad not listed as "Elan Touchpad" after "xinput list" or "cat 
/proc/bus/input/devices"
   . Not detected properly? For sure it does not work.
  External mouse working well. 
  Downgrading to 4.2.0-27-generic kernel solves problem(touchpad works). 
  My computer model is Toshiba Chromebook 2 with Gnome ubuntu 15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-30-generic 4.2.0-30.35
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  siulkilulki909 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 24 16:55:47 2016
  InstallationDate: Installed on 2015-12-06 (80 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 04f2:b48b Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 1ea7:0011  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Swanky
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=20463b36-edda-428c-a236-f715f1d7bb85 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/22/2014:svnGOOGLE:pnSwanky:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Swanky
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Zesty)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Broadwell ECRC Support missing in Ubuntu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  In Progress

Bug description:
  Here is the problem statement from the Dell team:

  When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel
  Quick Assist Card, the memory location that corresponds to ECRC is set
  to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.
  This causes the card to not function unless we implement the following
  workaround using setpci.

  “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for
  the Intel Quick Assit Card.

  We’ve verified the memory location is correct when booting to other
  OSes, such as RHEL 7.2 and Windows Server 2012 R2.

  If there is any information you can give as to why this may be
  occurring in Ubuntu or where we may start to debug when the memory is
  changed, we would appreciate it.

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

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

[Kernel-packages] [Bug 1811093] Re: Bogus "Out of Memory" compiz invoked oom-killer

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc1/

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

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

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

Title:
  Bogus "Out of Memory" compiz invoked oom-killer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has happened five times in the past week (four times in the past
  36 hours):

kernel: compiz invoked oom-killer:

  There is plenty of free core memory and almost no swap in use when it
  happens.  This is Xenial with kernel version is 4.4.0-141, which
  contains fix to previously reported bug #1655842 "Out of Memory"
  oom-killer bug.  I only have one week of logs to go by, which contain
  five occurrences.  It has happened four times in the past 36 hours.
  Sometimes it happens right after logging into the unity / lighdm
  desktop (three out of five times), but not always.  In four out of
  five occurrences a postgres job was running and oom-killer killed
  postgres.  In the one other instance, postgres was quietly idle in the
  background and oom-killer killed Thunderbird.  Kernel messages in
  syslog from five occurrences:

  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0

  Additional info:

  $> lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  $> cat /proc/version_signature
  Ubuntu 4.4.0-141.167-generic 4.4.162

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Kleber Sacilotto de Souza]

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

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

-- 
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:
  Triaged
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leads 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.

  [Fix]
  Suggested from Intel and Dell to contains the following 4 commits,
  and all of 4 commits are in v4.19-rc1
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/
  https://patchwork.kernel.org/patch/10535781/
  https://patchwork.kernel.org/patch/10535783/

  [Test]
  Verified the power consumption on some new platforms, it improves the SATA 
HDD power consumption around 0.5w during long idle.

  [Regression Potential]
  Low, the DEVSLP function is already validated when shipped with SLP_S0
  support.

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 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"

[Guilherme G. Piccoli]

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

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

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

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

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

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

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: makedumpfile (Ubuntu Bionic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: makedumpfile (Ubuntu Cosmic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

Title:
  Replace "nousb" option in kdump command-line for the newer
  "usbcore.nousb"

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Disco:
  Confirmed

Bug description:
  Since kernel v4.5, the correct parameter to disable USB subsystem
  initialization is "usbcore.nousb" always (instead of "nousb" in case
  the subsystem is built-in). This was changed by commit 097a9ea0e48
  ("usb: make "nousb" a clear module parameter").

  We need to take this into account in kdump-tools, or else we may boot
  with USB in kdump even the command-line saying the opposite.

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

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

[Kernel-packages] [Bug 1800566] Re: Make the reset_devices parameter default for kdump kernels

[Guilherme G. Piccoli]

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

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

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

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

** Changed in: makedumpfile (Ubuntu Trusty)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

Title:
  Make the reset_devices parameter default for kdump kernels

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  New
Status in makedumpfile source package in Cosmic:
  New
Status in makedumpfile source package in Disco:
  Confirmed

Bug description:
  Kernel has the "reset_devices" parameter that drivers can opt-in, and
  perform special activity in case this parameter is parsed from
  command-line. For example, in kdump kernels it hints the drivers that
  they (maybe) are booting from a non-healthy condition and needs to
  issue some reset to the adapter. Users currently (kernel v4.19) are:
  hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.

  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.

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

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

[Kernel-packages] [Bug 1800873] Re: Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-line

[Guilherme G. Piccoli]

** Changed in: makedumpfile (Ubuntu Trusty)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: makedumpfile (Ubuntu Bionic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: makedumpfile (Ubuntu Cosmic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

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

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

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

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

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

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

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

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

Title:
  Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-
  line

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Disco:
  Confirmed

Bug description:
  Currently kdump has an useful option to append parameters to the kdump
  kernel command-line, "KDUMP_CMDLINE_APPEND". Would be useful to have a
  reciprocal option which users could use to remove parameters without
  needing to rewrite the whole line.

  The option name proposed here is KDUMP_CMDLINE_REMOVE, which would
  tentatively "sed"-out the options from the kernel command-line before
  appending the new ones from KDUMP_CMDLINE_APPEND.

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

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

[Kernel-packages] [Bug 1800873] Re: Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-line

[Eric Desrochers]

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Disco)
   Importance: Low
 Assignee: Guilherme G. Piccoli (gpiccoli)
   Status: Confirmed

** Also affects: makedumpfile (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

Title:
  Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-
  line

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  New
Status in makedumpfile source package in Cosmic:
  New
Status in makedumpfile source package in Disco:
  Confirmed

Bug description:
  Currently kdump has an useful option to append parameters to the kdump
  kernel command-line, "KDUMP_CMDLINE_APPEND". Would be useful to have a
  reciprocal option which users could use to remove parameters without
  needing to rewrite the whole line.

  The option name proposed here is KDUMP_CMDLINE_REMOVE, which would
  tentatively "sed"-out the options from the kernel command-line before
  appending the new ones from KDUMP_CMDLINE_APPEND.

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

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

[Kernel-packages] [Bug 1800566] Re: Make the reset_devices parameter default for kdump kernels

[Eric Desrochers]

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Disco)
   Importance: High
 Assignee: Mauricio Faria de Oliveira (mfo)
   Status: Confirmed

** Also affects: makedumpfile (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

Title:
  Make the reset_devices parameter default for kdump kernels

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  New
Status in makedumpfile source package in Cosmic:
  New
Status in makedumpfile source package in Disco:
  Confirmed

Bug description:
  Kernel has the "reset_devices" parameter that drivers can opt-in, and
  perform special activity in case this parameter is parsed from
  command-line. For example, in kdump kernels it hints the drivers that
  they (maybe) are booting from a non-healthy condition and needs to
  issue some reset to the adapter. Users currently (kernel v4.19) are:
  hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.

  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.

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

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

[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"

[Eric Desrochers]

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Disco)
   Importance: High
 Assignee: Guilherme G. Piccoli (gpiccoli)
   Status: Confirmed

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

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

Title:
  Replace "nousb" option in kdump command-line for the newer
  "usbcore.nousb"

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  New
Status in makedumpfile source package in Cosmic:
  New
Status in makedumpfile source package in Disco:
  Confirmed

Bug description:
  Since kernel v4.5, the correct parameter to disable USB subsystem
  initialization is "usbcore.nousb" always (instead of "nousb" in case
  the subsystem is built-in). This was changed by commit 097a9ea0e48
  ("usb: make "nousb" a clear module parameter").

  We need to take this into account in kdump-tools, or else we may boot
  with USB in kdump even the command-line saying the opposite.

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

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

[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working

[Kenji]

Dont have anything much to add, but just wanted to mention:

I was on Ubuntu for a few months but kept getting freezes randomly. It
would just stop in the middle of anything, could be the browser, could
be a video, could be when it goes to sleep.

Not sure if it was a hardware issue (SSD), but I changed to my NVME
drive and also went to Linux Mint 19.1. Last time I tried (I think mint
19?), the ivrs_ioapic command did not work, however this time it did (at
least on 19.1). Only problem is when you boot into the setup screen, the
screen is fractured, it doesn't display right. So do "nomodeset" to get
it installed. Once you install it and boot into mint, upgrade the kernel
to 4.20. That fixed my screen issue. Everything else works perfect when
the ivrs added. Haven't had and freezing yet either, so crossing my
fingers.

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

Title:
  ELAN469D touch pad not working

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

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Kleber Sacilotto de Souza]

** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1781533

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leads 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.

  [Fix]
  Suggested from Intel and Dell to contains the following 4 commits,
  and all of 4 commits are in v4.19-rc1
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/
  https://patchwork.kernel.org/patch/10535781/
  https://patchwork.kernel.org/patch/10535783/

  [Test]
  Verified the power consumption on some new platforms, it improves the SATA 
HDD power consumption around 0.5w during long idle.

  [Regression Potential]
  Low, the DEVSLP function is already validated when shipped with SLP_S0
  support.

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 1811093] Re: Bogus "Out of Memory" compiz invoked oom-killer

[Craig]

compiz:
  Installed: 1:0.9.12.3+16.04.20180221-0ubuntu1

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

Title:
  Bogus "Out of Memory" compiz invoked oom-killer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This has happened five times in the past week (four times in the past
  36 hours):

kernel: compiz invoked oom-killer:

  There is plenty of free core memory and almost no swap in use when it
  happens.  This is Xenial with kernel version is 4.4.0-141, which
  contains fix to previously reported bug #1655842 "Out of Memory"
  oom-killer bug.  I only have one week of logs to go by, which contain
  five occurrences.  It has happened four times in the past 36 hours.
  Sometimes it happens right after logging into the unity / lighdm
  desktop (three out of five times), but not always.  In four out of
  five occurrences a postgres job was running and oom-killer killed
  postgres.  In the one other instance, postgres was quietly idle in the
  background and oom-killer killed Thunderbird.  Kernel messages in
  syslog from five occurrences:

  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0

  Additional info:

  $> lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  $> cat /proc/version_signature
  Ubuntu 4.4.0-141.167-generic 4.4.162

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

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

[Kernel-packages] [Bug 1808097] Re: Console got stuck using serial tty after logout

[Kleber Sacilotto de Souza]

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

** Changed in: linux (Ubuntu Cosmic)
   Status: New => 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/1808097

Title:
  Console got stuck using serial tty after logout

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

Bug description:
  [Impact]
  The agetty stopped working using serial tty when user logged out, especially 
if there is a remained process. The agetty failed to open tty device due to 
serial port used by previous process was not released.

  [Test Case]
  1. Run background processes from serial console
  $ while true; do sleep 10; done &

  2. Log out
  $ logout

  3. Read journal log by journalctl | tail
  Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0.
  Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0.
  Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty

  [Fix]
  The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if 
port comes from console. The commit is cherry-picked by

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6=2a48602615e0a2f563549c7d5c8d507f904cf96e

  [Regression Potential]
  Should be none, and it's regression becoz 4.4 kernel didn't have this case.

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

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

[Kernel-packages] [Bug 1811093] Re: Bogus "Out of Memory" compiz invoked oom-killer

[Craig]

** Attachment added: "syslog_snippets"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811093/+attachment/5227999/+files/syslog_snippets

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

Title:
  Bogus "Out of Memory" compiz invoked oom-killer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This has happened five times in the past week (four times in the past
  36 hours):

kernel: compiz invoked oom-killer:

  There is plenty of free core memory and almost no swap in use when it
  happens.  This is Xenial with kernel version is 4.4.0-141, which
  contains fix to previously reported bug #1655842 "Out of Memory"
  oom-killer bug.  I only have one week of logs to go by, which contain
  five occurrences.  It has happened four times in the past 36 hours.
  Sometimes it happens right after logging into the unity / lighdm
  desktop (three out of five times), but not always.  In four out of
  five occurrences a postgres job was running and oom-killer killed
  postgres.  In the one other instance, postgres was quietly idle in the
  background and oom-killer killed Thunderbird.  Kernel messages in
  syslog from five occurrences:

  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0

  Additional info:

  $> lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  $> cat /proc/version_signature
  Ubuntu 4.4.0-141.167-generic 4.4.162

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

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

[Kernel-packages] [Bug 1810967] Re: Xenial update: 4.4.166 upstream stable release

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Xenial)
   Status: New => 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/1810967

Title:
  Xenial update: 4.4.166 upstream stable release

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

Bug description:
  
  SRU Justification

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

 4.4.166 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.166
  drm/ast: Remove existing framebuffers before loading driver
  s390/mm: Check for valid vma before zapping in gmap_discard
  namei: allow restricted O_CREAT of FIFOs and regular files
  sched/core: Allow __sched_setscheduler() in interrupts when PI is not used
  btrfs: Ensure btrfs_trim_fs can trim the whole filesystem
  usb: xhci: fix uninitialized completion when USB3 port got wrong status
  tty: wipe buffer if not echoing data
  tty: wipe buffer.
  iwlwifi: mvm: fix regulatory domain update when the firmware starts
  scsi: qla2xxx: do not queue commands when unloading
  scsi: ufshcd: release resources if probe fails
  scsi: ufs: fix race between clock gating and devfreq scaling work
  scsi: ufshcd: Fix race between clk scaling and ungate work
  scsi: ufs: fix bugs related to null pointer access and array size
  netfilter: nf_tables: fix oops when inserting an element into a verdict map
  mwifiex: fix p2p device doesn't find in scan problem
  mwifiex: Fix NULL pointer dereference in skb_dequeue()
  cw1200: Don't leak memory if krealloc failes
  Input: xpad - add support for Xbox1 PDP Camo series gamepad
  Input: xpad - fix GPD Win 2 controller name
  Input: xpad - add GPD Win 2 Controller USB IDs
  Input: xpad - avoid using __set_bit() for capabilities
  Input: xpad - fix some coding style issues
  Input: xpad - add PDP device id 0x02a4
  Input: xpad - add support for PDP Xbox One controllers
  Input: xpad - validate USB endpoint type during probe
  Input: xpad - fix PowerA init quirk for some gamepad models
  Input: xpad - constify usb_device_id
  Input: xpad - sync supported devices with XBCD
  Input: xpad - sync supported devices with 360Controller
  Input: xpad - add USB IDs for Mad Catz Brawlstick and Razer Sabertooth
  Input: xpad - sync supported devices with xboxdrv
  Input: xpad - sort supported devices by USB ID
  Input: xpad - support some quirky Xbox One pads
  Input: xpad - restore LED state after device resume
  Input: xpad - fix stuck mode button on Xbox One S pad
  Input: xpad - don't depend on endpoint order
  Input: xpad - simplify error condition in init_output
  Input: xpad - move reporting xbox one home button to common function
  Input: xpad - correctly sort vendor id's
  Input: xpad - fix Xbox One rumble stopping after 2.5 secs
  Input: xpad - add product ID for Xbox One S pad
  Input: xpad - power off wireless 360 controllers on suspend
  Input: xpad - fix rumble on Xbox One controllers with 2015 firmware
  Input: xpad - xbox one elite controller support
  Input: xpad - add more third-party controllers
  Input: xpad - prevent spurious input from wired Xbox 360 controllers
  Input: xpad - add Mad Catz FightStick TE 2 VID/PID
  Input: xpad - remove unused function
  Input: xpad - correct xbox one pad device name
  Input: xpad - use LED API when identifying wireless controllers
  Input: xpad - workaround dead irq_out after suspend/ resume
  Input: xpad - update Xbox One Force Feedback Support
  Input: xpad - handle "present" and "gone" correctly
  Input: xpad - remove spurious events of wireless xpad 360 controller
  ath10k: fix kernel panic due to race in accessing arvif list
  arm64: remove no-op -p linker flag
  x86/entry/64: Remove %ebx handling from error_entry/exit
  x86/entry: spell EBX register correctly in documentation
  net: bcmgenet: fix OF child-node lookup
  NFC: nfcmrvl_uart: fix OF child-node lookup
  of: add helper to lookup compatible child node
  tmpfs: make lseek(SEEK_DATA/SEK_HOLE) return ENXIO with a negative offset
  powerpc/numa: Suppress "VPHN is not supported" messages
  kdb: Use strscpy with destination buffer size
  SUNRPC: Fix a bogus get/put in generic_key_to_expire()
  cpufreq: imx6q: add return value check for voltage scale
  KVM: PPC: Move and undef TRACE_INCLUDE_PATH/FILE
  usb: xhci: Prevent bus suspend if a port connect change or polling state is 
detected
  can: dev: __can_get_echo_skb(): print error message, if trying to echo non 
existing skb
  can: dev: 

[Kernel-packages] [Bug 1811093] Re: Bogus "Out of Memory" compiz invoked oom-killer

[Craig]

** Attachment added: "lspci-vvnn.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811093/+attachment/5227998/+files/lspci-vvnn.txt

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

Title:
  Bogus "Out of Memory" compiz invoked oom-killer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This has happened five times in the past week (four times in the past
  36 hours):

kernel: compiz invoked oom-killer:

  There is plenty of free core memory and almost no swap in use when it
  happens.  This is Xenial with kernel version is 4.4.0-141, which
  contains fix to previously reported bug #1655842 "Out of Memory"
  oom-killer bug.  I only have one week of logs to go by, which contain
  five occurrences.  It has happened four times in the past 36 hours.
  Sometimes it happens right after logging into the unity / lighdm
  desktop (three out of five times), but not always.  In four out of
  five occurrences a postgres job was running and oom-killer killed
  postgres.  In the one other instance, postgres was quietly idle in the
  background and oom-killer killed Thunderbird.  Kernel messages in
  syslog from five occurrences:

  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0

  Additional info:

  $> lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  $> cat /proc/version_signature
  Ubuntu 4.4.0-141.167-generic 4.4.162

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

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

[Kernel-packages] [Bug 1806952] Re: linux: 4.19.0-8.9 -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
  
  backports: 
  derivatives:
  -- swm properties --
- phase: Testing -- testing in progress
- phase-changed: Wednesday, 09. January 2019 11:18 UTC
+ phase: Testing -- automated-testing in progress
+ phase-changed: Wednesday, 09. January 2019 14:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.19.0-8.9 -proposed tracker

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

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

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

  backports: 
  derivatives:
  -- swm properties --
  phase: Testing -- automated-testing in progress
  phase-changed: Wednesday, 09. January 2019 14:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -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: 1806659
- phase: Testing -- FAILED
- phase-changed: Wednesday, 09. January 2019 11:18 UTC
+ phase: Testing -- automated-testing FAILED
+ phase-changed: Wednesday, 09. January 2019 14:55 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

Title:
  linux-oem: 4.15.0-1031.36 -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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Testing -- automated-testing FAILED
  phase-changed: Wednesday, 09. January 2019 14:55 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed

[Kleber Sacilotto de Souza]

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

Title:
  fanotify10 in ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New

Bug description:
  == Justification ==
  Commit 92183a42898d ("fsnotify: fix ignore mask logic in
  send_to_group()") acknowledges the use case of ignoring an event on
  an inode mark, because of an ignore mask on a mount mark of the same
  group (i.e. I want to get all events on this file, except for the events
  that came from that mount).

  This change depends on correctly merging the inode marks and mount marks
  group lists, so that the mount mark ignore mask would be tested in
  send_to_group(). Alas, the merging of the lists did not take into
  account the case where event in question is not in the mask of any of
  the mount marks.

  To fix this, completely remove the tests for inode and mount event masks
  from the lists merging code.

  == Fix ==
  9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())

  Test kernels for Bionic can be found here:
  http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/

  It seems that T/X poses with the same issue and we might be able to backport
  it with the same logic, but I think we should target Bionic as it's a fix for
  for 92183a42898d which was only applied to Bionic.

  == Regression Potential ==
  Low.

  The backport work is required as it's missing commit 47d9c7cc457 in Bionic,
  which generalizes the iteration of marks for inode_mark and vfsmount_mark, 
from:
  iter_info.inode_mark
  to:
  iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]

  But the patch can still be backported with the same logic without this
  commit.

  The test with the syscalls test in LTP test suite shows no sign of
  regression.

  == Test Case ==
  Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
  with the patched kernel.

  Full LTP syscalls test with 4.15.0-42 in -proposed:
  http://paste.ubuntu.com/p/Wm8nQ932g6/

  Full LTP syscalls test with patched 4.15.0-42:
  http://paste.ubuntu.com/p/nv4jW6shpJ/

  -

  This is a new test case that landed 7 days ago.

  <<>>
  tag=fanotify10 stime=1541744937
  cmdline="fanotify10"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
  mke2fs 1.44.1 (24-Mar-2018)
  tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
  fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific 
file
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another 
file
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific 
mount point
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 1 (prio 1) 

[Kernel-packages] [Bug 1810967] Re: Xenial update: 4.4.166 upstream stable release

[Kleber Sacilotto de Souza]

** Also affects: linux (Ubuntu Xenial)
   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/1810967

Title:
  Xenial update: 4.4.166 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  
  SRU Justification

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

 4.4.166 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.166
  drm/ast: Remove existing framebuffers before loading driver
  s390/mm: Check for valid vma before zapping in gmap_discard
  namei: allow restricted O_CREAT of FIFOs and regular files
  sched/core: Allow __sched_setscheduler() in interrupts when PI is not used
  btrfs: Ensure btrfs_trim_fs can trim the whole filesystem
  usb: xhci: fix uninitialized completion when USB3 port got wrong status
  tty: wipe buffer if not echoing data
  tty: wipe buffer.
  iwlwifi: mvm: fix regulatory domain update when the firmware starts
  scsi: qla2xxx: do not queue commands when unloading
  scsi: ufshcd: release resources if probe fails
  scsi: ufs: fix race between clock gating and devfreq scaling work
  scsi: ufshcd: Fix race between clk scaling and ungate work
  scsi: ufs: fix bugs related to null pointer access and array size
  netfilter: nf_tables: fix oops when inserting an element into a verdict map
  mwifiex: fix p2p device doesn't find in scan problem
  mwifiex: Fix NULL pointer dereference in skb_dequeue()
  cw1200: Don't leak memory if krealloc failes
  Input: xpad - add support for Xbox1 PDP Camo series gamepad
  Input: xpad - fix GPD Win 2 controller name
  Input: xpad - add GPD Win 2 Controller USB IDs
  Input: xpad - avoid using __set_bit() for capabilities
  Input: xpad - fix some coding style issues
  Input: xpad - add PDP device id 0x02a4
  Input: xpad - add support for PDP Xbox One controllers
  Input: xpad - validate USB endpoint type during probe
  Input: xpad - fix PowerA init quirk for some gamepad models
  Input: xpad - constify usb_device_id
  Input: xpad - sync supported devices with XBCD
  Input: xpad - sync supported devices with 360Controller
  Input: xpad - add USB IDs for Mad Catz Brawlstick and Razer Sabertooth
  Input: xpad - sync supported devices with xboxdrv
  Input: xpad - sort supported devices by USB ID
  Input: xpad - support some quirky Xbox One pads
  Input: xpad - restore LED state after device resume
  Input: xpad - fix stuck mode button on Xbox One S pad
  Input: xpad - don't depend on endpoint order
  Input: xpad - simplify error condition in init_output
  Input: xpad - move reporting xbox one home button to common function
  Input: xpad - correctly sort vendor id's
  Input: xpad - fix Xbox One rumble stopping after 2.5 secs
  Input: xpad - add product ID for Xbox One S pad
  Input: xpad - power off wireless 360 controllers on suspend
  Input: xpad - fix rumble on Xbox One controllers with 2015 firmware
  Input: xpad - xbox one elite controller support
  Input: xpad - add more third-party controllers
  Input: xpad - prevent spurious input from wired Xbox 360 controllers
  Input: xpad - add Mad Catz FightStick TE 2 VID/PID
  Input: xpad - remove unused function
  Input: xpad - correct xbox one pad device name
  Input: xpad - use LED API when identifying wireless controllers
  Input: xpad - workaround dead irq_out after suspend/ resume
  Input: xpad - update Xbox One Force Feedback Support
  Input: xpad - handle "present" and "gone" correctly
  Input: xpad - remove spurious events of wireless xpad 360 controller
  ath10k: fix kernel panic due to race in accessing arvif list
  arm64: remove no-op -p linker flag
  x86/entry/64: Remove %ebx handling from error_entry/exit
  x86/entry: spell EBX register correctly in documentation
  net: bcmgenet: fix OF child-node lookup
  NFC: nfcmrvl_uart: fix OF child-node lookup
  of: add helper to lookup compatible child node
  tmpfs: make lseek(SEEK_DATA/SEK_HOLE) return ENXIO with a negative offset
  powerpc/numa: Suppress "VPHN is not supported" messages
  kdb: Use strscpy with destination buffer size
  SUNRPC: Fix a bogus get/put in generic_key_to_expire()
  cpufreq: imx6q: add return value check for voltage scale
  KVM: PPC: Move and undef TRACE_INCLUDE_PATH/FILE
  usb: xhci: Prevent bus suspend if a port connect change or polling state is 
detected
  can: dev: __can_get_echo_skb(): print error message, if trying to echo non 
existing skb
  can: dev: 

[Kernel-packages] [Bug 1805344] Re: SRU: Fix kernel xhci hang when resume from S3

[Kleber Sacilotto de Souza]

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

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

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

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

Title:
  SRU: Fix kernel xhci hang when resume from S3

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

Bug description:
  [Impact]
  On some thinkpad laptops, Realtek USB3.0 Card Reader [0bda:0328] reports 
wrong port status on
  Cannon lake PCH USB3.1 xHCI [8086:a36d] after resume from S3, then kernel 
hang.

  [Fix]
  Restrict the USB2 resume status check in USB2 roothub to fix hang issue.

  [Test Case]
  Suspend/resume 30 times OK.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  These 2 patches are already Cc: sta...@vger.kernel.org, cosmic and
  future kernel will get these 2 patches.

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

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

[Kernel-packages] [Bug 1806488] Re: Support non-strict iommu mode on arm64

[Seth Forshee]

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

Title:
  Support non-strict iommu mode on arm64

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  The Intel IOMMU driver provides an option for strict mode. When disabled, 
batching of IOTLB flush operations is permitted, allowing the user to trade-off 
isolation for improved performance. Ubuntu's kernel currently lacks a parity 
for this feature for ARM.

  There's a significant performance gain to be had by removing the need
  to flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25%
  performance gain w/ fio reads on a single NVMe device.

  This mode of operation is available for x86 via the
  "intel_iommu=strict" parameter. Upstream now exposes an equivalent
  feature for ARM platforms via the "iommu.strict=[0|1]" parameter,
  while retaining the default strict-enabled mode.

  [Test Case]
  $ cat fio.rc
  [global]
  rw=read
  direct=1
  ioengine=libaio
  iodepth=2048
  numjobs=10
  bs=4k
  group_reporting=1
  group_reporting=1
  cpumask=0xff
  runtime=100
  loops = 1

  [job1]
  filename=/dev/nvme0n1

  [Fix]
  44f6876a00e83 iommu/arm-smmu: Support non-strict mode
  b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode
  9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode
  b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode
  68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  2da274cdf998a iommu/dma: Add support for non-strict mode
  07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook
  85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()

  [Regression Risk]
  Most of these patches are specific to ARM, and have been regression tested on 
both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)"

  2 patches do touch arch-indep code however:

  > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  Adds a new command line option and sets an attribute that iommu drivers can 
optionally react to. Doesn't change default behavior.

  > 2da274cdf998a iommu/dma: Add support for non-strict mode
  This driver is only built for arm64 and ppc64el (determined by looking at the 
build logs). Most of this patch only changes behavior in the non-default (and 
new) iommu.strict=0 case. The exception, which is called out in the commit 
message, is this hunk:

  -   WARN_ON(iommu_unmap(domain, dma_addr, size) != size);
  +   WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size);
  +   if (!cookie->fq_domain)
  +   iommu_tlb_sync(domain);

  
  In the default case, where fq_domain will be NULl, we are now factoring 
iommu_unmap() into:
iommu_unmap_fast()
iommu_tlb_sync()

  Looking at the source to iommu_unmap() confirms that this is
  functionally equivalent.

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

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

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

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

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

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

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

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

Title:
  Bogus "Out of Memory" compiz invoked oom-killer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has happened five times in the past week (four times in the past
  36 hours):

kernel: compiz invoked oom-killer:

  There is plenty of free core memory and almost no swap in use when it
  happens.  This is Xenial with kernel version is 4.4.0-141, which
  contains fix to previously reported bug #1655842 "Out of Memory"
  oom-killer bug.  I only have one week of logs to go by, which contain
  five occurrences.  It has happened four times in the past 36 hours.
  Sometimes it happens right after logging into the unity / lighdm
  desktop (three out of five times), but not always.  In four out of
  five occurrences a postgres job was running and oom-killer killed
  postgres.  In the one other instance, postgres was quietly idle in the
  background and oom-killer killed Thunderbird.  Kernel messages in
  syslog from five occurrences:

  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0

  Additional info:

  $> lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  $> cat /proc/version_signature
  Ubuntu 4.4.0-141.167-generic 4.4.162

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

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

Re: [Kernel-packages] [Bug 1810406] Re: Whiptail stucks during kernel upgrade

[mnovait]

I could reproduce it at every kernel upgrade in the past 2 months.

Let me verify if it happens again.

thank you

Il giorno mer 9 gen 2019 alle ore 04:10 Daniel van Vugt <
daniel.van.v...@canonical.com> ha scritto:

> Looks like a repeat of bug 1760876. But that's meant to be fixed
> already!?
>
> DKMS make.log for nvidia-390.77 for kernel 4.15.0-43-generic (x86_64)
> gio  3 gen 2019, 13.02.14, CET
> make[1]: Entering directory '/usr/src/linux-headers-4.15.0-43-generic'
> Makefile:975: "Cannot use CONFIG_STACK_VALIDATION=y, please install
> libelf-dev, libelf-devel or elfutils-libelf-devel"
> test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
>   \
> echo >&2;   \
> echo >&2 "  ERROR: Kernel configuration is invalid.";   \
> echo >&2 " include/generated/autoconf.h or
> include/config/auto.conf are missing.";\
> echo >&2 " Run 'make oldconfig && make prepare' on kernel src to
> fix it.";  \
> echo >&2 ;  \
> /bin/false)
> mkdir -p /var/lib/dkms/nvidia/390.77/build/.tmp_versions ; rm -f
> /var/lib/dkms/nvidia/390.77/build/.tmp_versions/*
>
> ** Summary changed:
>
> - Whiptail stucks during kernel upgrade
> + nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to
> build [Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev,
> libelf-devel or elfutils-libelf-devel]
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1810406
>
> Title:
>   nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed
>   to build [Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-
>   dev, libelf-devel or elfutils-libelf-devel]
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1810406/+subscriptions
>


-- 

: : perchè usare formati aperti: *http://it.wikipedia.org/wiki/Formato_aperto
*

: : Please, consider your environmental responsibility.
: : Before printing this e-mail ask yourself: "Do I need a hard copy?"

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

Title:
  nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed
  to build [Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-
  dev, libelf-devel or elfutils-libelf-devel]

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  While upgrading kernel, whiptail process stucks and the update process
  hangs forever

  nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed
  to build

  
  root 25534  0.0  0.0  63712  4316 pts/0S+   13:02   0:00  |   \_ sudo 
dpkg --configure -a
  root 25535  0.0  0.0  26600 10952 pts/0S+   13:02   0:00  |   \_ 
dpkg --configure -a
  root 25570  0.0  0.0   4628   784 pts/0S+   13:02   0:00  |   
\_ /bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-43-generic.postinst configure
  root 25571  0.0  0.0   4520   768 pts/0S+   13:02   0:00  |   
\_ run-parts --report --exit-on-error --arg=4.15.0-43-generic 
/etc/kernel/header_postinst.d
  root 25572  0.0  0.0   4628  1896 pts/0S+   13:02   0:00  |   
\_ /bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-43-generic
  root 25582  0.0  0.0  15896  6452 pts/0S+   13:02   0:00  |   
\_ /bin/bash /usr/sbin/dkms autoinstall --kernelver 
4.15.0-43-generic
  root 26396  0.0  0.0  16016  5724 pts/0S+   13:02   0:00  |   
\_ /bin/bash /usr/sbin/dkms autoinstall --kernelver 
4.15.0-43-generic
  root  1718  0.1  0.1 104160 22504 pts/0S+   13:02   0:00  |   
\_ /usr/bin/perl -w /usr/share/debconf/frontend 
/usr/sbin/update-secureboot-policy --enroll-key
  root  1750  0.0  0.0   4628  1864 pts/0S+   13:02   0:00  |   
\_ /bin/sh /usr/sbin/update-secureboot-policy 
--enroll-key
  root  1897  0.0  0.0  24924  4320 pts/0S+   13:03   0:00  |   
\_ whiptail --backtitle Package configuration --title 
Configuring Secure Boot --output-fd 12 --inputbox --   
  teo  22242  0.0  0.0  26560  8896 pts/2Ss   13:00   0:00  \_ /bin/bash
  teo   2054  0.0  0.0  37528  3596 pts/2R+   13:03   0:00  \_ ps 
ufax

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-43-generic
  Date: Thu Jan  3 13:02:14 2019
  

[Kernel-packages] [Bug 1811093] [NEW] Bogus "Out of Memory" compiz invoked oom-killer

[Craig]

Public bug reported:

This has happened five times in the past week (four times in the past
36 hours):

  kernel: compiz invoked oom-killer:

There is plenty of free core memory and almost no swap in use when it
happens.  This is Xenial with kernel version is 4.4.0-141, which
contains fix to previously reported bug #1655842 "Out of Memory"
oom-killer bug.  I only have one week of logs to go by, which contain
five occurrences.  It has happened four times in the past 36 hours.
Sometimes it happens right after logging into the unity / lighdm
desktop (three out of five times), but not always.  In four out of
five occurrences a postgres job was running and oom-killer killed
postgres.  In the one other instance, postgres was quietly idle in the
background and oom-killer killed Thunderbird.  Kernel messages in
syslog from five occurrences:

compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0

Additional info:

$> lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04

$> cat /proc/version_signature
Ubuntu 4.4.0-141.167-generic 4.4.162

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


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

Title:
  Bogus "Out of Memory" compiz invoked oom-killer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has happened five times in the past week (four times in the past
  36 hours):

kernel: compiz invoked oom-killer:

  There is plenty of free core memory and almost no swap in use when it
  happens.  This is Xenial with kernel version is 4.4.0-141, which
  contains fix to previously reported bug #1655842 "Out of Memory"
  oom-killer bug.  I only have one week of logs to go by, which contain
  five occurrences.  It has happened four times in the past 36 hours.
  Sometimes it happens right after logging into the unity / lighdm
  desktop (three out of five times), but not always.  In four out of
  five occurrences a postgres job was running and oom-killer killed
  postgres.  In the one other instance, postgres was quietly idle in the
  background and oom-killer killed Thunderbird.  Kernel messages in
  syslog from five occurrences:

  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0

  Additional info:

  $> lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  $> cat /proc/version_signature
  Ubuntu 4.4.0-141.167-generic 4.4.162

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

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

[Kernel-packages] [Bug 1810457] Re: Update hisilicon SoC-specific drivers

[Kleber Sacilotto de Souza]

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

Title:
  Update hisilicon SoC-specific drivers

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active 
development, including both hardware enablement and bug fix patches. With the 
amount of flux involved, identifying and cherry-picking individual patches 
would be more error prone then re-syncing with current upstream.

  [Test Case]
  The Ubuntu server certification suite, which includes network and storage 
tests.

  [Fix]
  Backport the localized driver changes up to v5.0-rc1.

  [Regression Risk]
  These changes are restricted to the hns and hisi_sas drivers, which only 
impact the D05 and D06 server development board platforms. To mitigate this 
risk, we have explicitly tested the proposed changes on these 2 platforms - 
changes are staged in ppa:pearl2-team/test. Of course, there is risk that these 
changes introduced regressions that our testing did not catch.

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

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

[Kernel-packages] [Bug 1811094] [NEW] iptables connlimit allows more connections than the limit when using multiple CPUs

[Mauricio Faria de Oliveira]

Public bug reported:

The following iptables connlimit rule can be breached
with a multithreaded client and network device driver,
due to a race in the conncount/connlimit code:

# iptables -A INPUT -p tcp -m tcp --syn --dport  \
  -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
  -j DROP

NOTE: Patches will be sent to the kernel-team mailing list
and more details/testing will be provided later today.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Mauricio Faria de Oliveira (mfo)
 Status: Confirmed

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

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

Title:
  iptables connlimit allows more connections than the limit when using
  multiple CPUs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following iptables connlimit rule can be breached
  with a multithreaded client and network device driver,
  due to a race in the conncount/connlimit code:

  # iptables -A INPUT -p tcp -m tcp --syn --dport  \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP

  NOTE: Patches will be sent to the kernel-team mailing list
  and more details/testing will be provided later today.

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

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

[Kernel-packages] [Bug 1810818] Re: Cosmic update: 4.18.18 upstream stable release

[Kleber Sacilotto de Souza]

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

Title:
  Cosmic update: 4.18.18 upstream stable release

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

Bug description:
  SRU Justification

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

     4.18.18 upstream stable release
     from git://git.kernel.org/

  eeprom: at24: Add support for address-width property
  vfs: swap names of {do,vfs}_clone_file_range()
  bpf: fix partial copy of map_ptr when dst is scalar
  gpio: mxs: Get rid of external API call
  clk: sunxi-ng: sun4i: Set VCO and PLL bias current to lowest setting
  fscache: Fix incomplete initialisation of inline key space
  cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)
  fscache: Fix out of bound read in long cookie keys
  ptp: fix Spectre v1 vulnerability
  drm/edid: Add 6 bpc quirk for BOE panel in HP Pavilion 15-n233sl
  drm/edid: VSDB yCBCr420 Deep Color mode bit definitions
  drm: fb-helper: Reject all pixel format changing requests
  RDMA/ucma: Fix Spectre v1 vulnerability
  IB/ucm: Fix Spectre v1 vulnerability
  cdc-acm: do not reset notification buffer index upon urb unlinking
  cdc-acm: correct counting of UART states in serial state notification
  cdc-acm: fix race between reset and control messaging
  usb: usbip: Fix BUG: KASAN: slab-out-of-bounds in vhci_hub_control()
  usb: gadget: storage: Fix Spectre v1 vulnerability
  usb: roles: intel_xhci: Fix Unbalanced pm_runtime_enable
  usb: xhci: pci: Enable Intel USB role mux on Apollo Lake platforms
  USB: fix the usbfs flag sanitization for control transfers
  tracing: Fix synthetic event to accept unsigned modifier
  tracing: Fix synthetic event to allow semicolon at end
  Input: elan_i2c - add ACPI ID for Lenovo IdeaPad 330-15IGM
  drm/sun4i: Fix an ulong overflow in the dotclock driver
  sched/fair: Fix throttle_list starvation with low CFS quota
  x86/tsc: Force inlining of cyc2ns bits
  x86, hibernate: Fix nosave_regions setup for hibernation
  x86/percpu: Fix this_cpu_read()
  x86/time: Correct the attribute on jiffies' definition
  x86/swiotlb: Enable swiotlb for > 4GiG RAM on 32-bit kernels
  x86/fpu: Fix i486 + no387 boot crash by only saving FPU registers on context 
switch if there is an FPU
  Linux 4.18.18

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

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

[Kernel-packages] [Bug 1810820] Re: Cosmic update: 4.18.19 upstream stable release

[Kleber Sacilotto de Souza]

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

Title:
  Cosmic update: 4.18.19 upstream stable release

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

Bug description:
  SRU Justification

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

     4.18.19 upstream stable release
     from git://git.kernel.org/

  mtd: rawnand: marvell: fix the IRQ handler complete() condition
  mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB
  mtd: spi-nor: intel-spi: Add support for Intel Ice Lake SPI serial flash
  mtd: spi-nor: fsl-quadspi: Don't let -EINVAL on the bus
  spi: spi-mem: Adjust op len based on message/transfer size limitations
  spi: bcm-qspi: switch back to reading flash using smaller chunks
  spi: bcm-qspi: fix calculation of address length
  bcache: trace missed reading by cache_missed
  bcache: correct dirty data statistics
  bcache: fix miss key refill->end in writeback
  hwmon: (pmbus) Fix page count auto-detection.
  jffs2: free jffs2_sb_info through jffs2_kill_sb()
  block: setup bounce bio_sets properly
  block: don't deal with discard limit in blkdev_issue_discard()
  block: make sure discard bio is aligned with logical block size
  block: make sure writesame bio is aligned with logical block size
  cpufreq: conservative: Take limits changes into account properly
  dma-mapping: fix panic caused by passing empty cma command line argument
  pcmcia: Implement CLKRUN protocol disabling for Ricoh bridges
  ACPI / OSL: Use 'jiffies' as the time bassis for acpi_os_get_timer()
  ACPICA: AML Parser: fix parse loop to correctly skip erroneous extended 
opcodes
  kprobes/x86: Use preempt_enable() in optimized_callback()
  mailbox: PCC: handle parse error
  acpi, nfit: Fix Address Range Scrub completion tracking
  parisc: Fix address in HPMC IVA
  parisc: Fix map_pages() to not overwrite existing pte entries
  parisc: Fix exported address of os_hpmc handler
  ALSA: hda - Add quirk for ASUS G751 laptop
  ALSA: hda - Fix headphone pin config for ASUS G751
  ALSA: hda - Add mic quirk for the Lenovo G50-30 (17aa:3905)
  ALSA: hda: Add 2 more models to the power_save blacklist
  ALSA: ca0106: Disable IZD on SB0570 DAC to fix audio pops
  x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation
  x86/xen: Fix boot loader version reported for PVH guests
  x86/corruption-check: Fix panic in memory_corruption_check() when boot option 
without value is provided
  x86/mm/pat: Disable preemption around __flush_tlb_all()
  ARM: dts: exynos: Disable pull control for MAX8997 interrupts on Origen
  drm: fix use of freed memory in drm_mode_setcrtc
  bpf: do not blindly change rlimit in reuseport net selftest
  nvme: remove ns sibling before clearing path
  Revert "perf tools: Fix PMU term format max value calculation"
  selftests: usbip: add wait after attach and before checking port status
  xsk: do not call synchronize_net() under RCU read lock
  xfrm: policy: use hlist rcu variants on insert
  perf vendor events intel: Fix wrong filter_band* values for uncore events
  r8169: Enable MSI-X on RTL8106e
  nfp: flower: fix pedit set actions for multiple partial masks
  nfp: flower: use offsets provided by pedit instead of index for ipv6
  sched/fair: Fix the min_vruntime update logic in dequeue_entity()
  perf evsel: Store ids for events with their own cpus 
perf_event__synthesize_event_update_cpus
  perf tools: Fix use of alternatives to find JDIR
  perf cpu_map: Align cpu map synthesized events properly.
  perf report: Don't crash on invalid inline debug information
  x86/fpu: Remove second definition of fpu in __fpu__restore_sig()
  net: qla3xxx: Remove overflowing shift statement
  r8169: re-enable MSI-X on RTL8168g
  drm: Get ref on CRTC commit object when waiting for flip_done
  selftests: ftrace: Add synthetic event syntax testcase
  i2c: rcar: cleanup DMA for all kinds of failure
  net: socionext: Reset tx queue in ndo_stop
  locking/lockdep: Fix debug_locks off performance problem
  netfilter: xt_nat: fix DNAT target for shifted portmap ranges
  ataflop: fix error handling during setup
  swim: fix cleanup on setup error
  arm64: cpufeature: ctr: Fix cpu capability check for late CPUs
  nfp: devlink port split support for 1x100G CXP NIC
  tun: Consistently configure generic netdev params via rtnetlink
  s390/sthyi: Fix machine name 

[Kernel-packages] [Bug 1810821] Re: Cosmic update: 4.18.20 upstream stable release

[Kleber Sacilotto de Souza]

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

Title:
  Cosmic update: 4.18.20 upstream stable release

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

Bug description:
  SRU Justification

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

     4.18.20 upstream stable release
     from git://git.kernel.org/

  powerpc/traps: restore recoverability of machine_check interrupts
  powerpc/64/module: REL32 relocation range check
  powerpc/mm: Fix page table dump to work on Radix
  powerpc/mm: fix always true/false warning in slice.c
  drm/amd/display: fix bug of accessing invalid memory
  Input: wm97xx-ts - fix exit path
  powerpc/Makefile: Fix PPC_BOOK3S_64 ASFLAGS
  powerpc/eeh: Fix possible null deref in eeh_dump_dev_log()
  tty: check name length in tty_find_polling_driver()
  tracing/kprobes: Check the probe on unloaded module correctly
  drm/amdgpu/powerplay: fix missing break in switch statements
  ARM: imx_v6_v7_defconfig: Select CONFIG_TMPFS_POSIX_ACL
  powerpc/nohash: fix undefined behaviour when testing page size support
  powerpc/mm: Don't report hugepage tables as memory leaks when using kmemleak
  drm/omap: fix memory barrier bug in DMM driver
  drm/amd/display: fix gamma not being applied
  drm/hisilicon: hibmc: Do not carry error code in HiBMC framebuffer pointer
  media: pci: cx23885: handle adding to list failure
  media: coda: don't overwrite h.264 profile_idc on decoder instance
  MIPS: kexec: Mark CPU offline before disabling local IRQ
  powerpc/boot: Ensure _zimage_start is a weak symbol
  powerpc/memtrace: Remove memory in chunks
  MIPS/PCI: Call pcie_bus_configure_settings() to set MPS/MRRS
  sc16is7xx: Fix for multi-channel stall
  media: tvp5150: fix width alignment during set_selection()
  powerpc/selftests: Wait all threads to join
  staging:iio:ad7606: fix voltage scales
  drm: rcar-du: Update Gen3 output limitations
  drm/amdgpu: Fix SDMA TO after GPU reset v3
  staging: most: video: fix registration of an empty comp core_component
  9p locks: fix glock.client_id leak in do_lock
  udf: Prevent write-unsupported filesystem to be remounted read-write
  ARM: dts: imx6ull: keep IMX6UL_ prefix for signals on both i.MX6UL and 
i.MX6ULL
  9p: clear dangling pointers in p9stat_free
  ovl: fix error handling in ovl_verify_set_fh()
  ovl: check whiteout in ovl_create_over_whiteout()
  serial: sh-sci: Fix could not remove dev_attr_rx_fifo_timeout
  scsi: qla2xxx: Fix incorrect port speed being set for FC adapters
  scsi: qla2xxx: Fix process response queue for ISP26XX and above
  scsi: qla2xxx: Remove stale debug trace message from tcm_qla2xxx
  scsi: qla2xxx: shutdown chip if reset fail
  scsi: qla2xxx: Fix duplicate switch database entries
  scsi: qla2xxx: Fix driver hang when FC-NVMe LUNs are configured
  fuse: Fix use-after-free in fuse_dev_do_read()
  fuse: Fix use-after-free in fuse_dev_do_write()
  fuse: fix blocked_waitq wakeup
  fuse: set FR_SENT while locked
  ovl: fix recursive oi->lock in ovl_link()
  scsi: qla2xxx: Fix re-using LoopID when handle is in use
  scsi: qla2xxx: Fix NVMe session hang on unload
  arm64: dts: stratix10: Support Ethernet Jumbo frame
  arm64: dts: stratix10: fix multicast filtering
  clk: meson-gxbb: set fclk_div3 as CLK_IS_CRITICAL
  clk: meson: axg: mark fdiv2 and fdiv3 as critical
  zram: close udev startup race condition as default groups
  MIPS: Loongson-3: Fix CPU UART irq delivery problem
  MIPS: Loongson-3: Fix BRIDGE irq delivery problem
  xtensa: add NOTES section to the linker script
  xtensa: make sure bFLT stack is 16 byte aligned
  xtensa: fix boot parameters address translation
  um: Drop own definition of PTRACE_SYSEMU/_SINGLESTEP
  clk: s2mps11: Fix matching when built as module and DT node contains 
compatible
  clk: at91: Fix division by zero in PLL recalc_rate()
  clk: sunxi-ng: h6: fix bus clocks' divider position
  clk: rockchip: fix wrong mmc sample phase shift for rk3328
  clk: rockchip: Fix static checker warning in rockchip_ddrclk_get_parent call
  libceph: bump CEPH_MSG_MAX_DATA_LEN
  Revert "ceph: fix dentry leak in splice_dentry()"
  thermal: core: Fix use-after-free in thermal_cooling_device_destroy_sysfs
  mach64: fix display corruption on big endian machines
  mach64: fix image corruption due to reading accelerator registers
  acpi/nfit, x86/mce: Handle only uncorrectable machine 

[Kernel-packages] [Bug 1807375]

[vasthusya]

(In reply to Cristian Aravena Romero from comment #1)
> Created attachment 280099 [details]
> dmesg 4.20.0-042000rc7-generic
> 
> I really do not know if the problem was definitively solved. Because
> Bluetooth devices now appear in GNOME.

It is still affecting me on vanilla 4.20 and 4.19.12.

I was able to modify drivers/bluetooth/btrtl.c to use
rtl_bt/rtl8821c_fw.bin firmware for this device.

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

Title:
  Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev
  826c, hci ver 0008

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

Bug description:
  Hello,

  dmesg:
  [   13.388386] Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, 
hci rev 826c, hci ver 0008

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 08:30:39 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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