[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit

[Ike Panhc]

I can not find "treewide: Use sizeof_member() macro but found a
similiar. Do you mean this patch?

commit c593642c8be046915ca3a4a300243a68077cd207
Author: Pankaj Bharadiya 
Date:   Mon Dec 9 10:31:43 2019 -0800

treewide: Use sizeof_field() macro

Replace all the occurrences of FIELD_SIZEOF() with sizeof_field() except
at places where these are defined. Later patches will remove the unused
definition of FIELD_SIZEOF().


** Description changed:

  [Bug Description]
   hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 
18.04.5 kernel version
  [Steps to Reproduce]
    1)
    2)
    3)
  
  [Actual Results]
  
  [Expected Results]
  
  [Reproducibility]
  
  [Additional information]
    (Firmware version, kernel version, affected hardware, etc. if required):
  
  [Resolution]
  net: hns3: support tx-scatter-gather-fraglist feature
  net: hns3: add support for configuring VF MAC from the host
  net: hns3: add support for configuring bandwidth of VF on the host
  net: hns3: add support for setting VF trust
  net: hns3: add support for spoof check setting
  net: hns3: add support for setting VF link status on the host
  net: hns3: make array tick_array static, makes object smaller
  
  net: hns3: fix a wrong reset interrupt status mask
  net: hns3: cleanup of stray struct hns3_link_mode_mapping
  net: hns3: fix ETS bandwidth validation bug
  net: hns3: reallocate SSU' buffer size when pfc_en changes
  net: hns3: add compatible handling for MAC VLAN switch parameter configuration
  net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE
  net: hns3: remove unused macros
  net: hns3: Use the correct style for SPDX License Identifier
  net: hns3: cleanup byte order issues when printed
  net: hns3: cleanup some print format warning
  net: hns3: add or modify some comments
  net: hns3: optimize local variable initialization
  net: hns3: cleanup a format-truncation warning
  net: hns3: cleanup some coding style issues
  net: hns3: cleanup some magic numbers
  net: hns3: add struct netdev_queue debug info for TX timeout
  net: hns3: dump some debug information when reset fail
  treewide: Use sizeof_member() macro
  net: hns3: log and clear hardware error after reset complete
  net: hns3: do not allocate linear data for fraglist skb
  net: hns3: minor cleanup for hns3_handle_rx_bd()
  net: hns3: make struct hns3_enet_ring cacheline aligned
  net: hns3: introduce ring_to_netdev() in enet module
  net: hns3: minor optimization for barrier in IO path
  net: hns3: optimized MAC address in management table.
  net: hns3: remove struct hns3_nic_ring_data in hns3_enet module
  net: hns3: fix mis-counting IRQ vector numbers issue
    net: hns3: fix VF ID issue for setting VF VLAN
  net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx()
  net: hns3: fix for TX queue not restarted problem
   net: hns3: only print misc interrupt status when handling fails
  net: hns3: add a log for getting chain failure in 
hns3_nic_uninit_vector_data()
  net: hns3: add some VF VLAN information for command "ip link show"
  net: hns3: implement ndo_features_check ops for hns3 driver
  net: hns3: get FD rules location before dump in debugfs
  net: hns3: optimization for CMDQ uninitialization
  net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev
  net: hns3: check FE bit before calling hns3_add_frag()
  net: hns3: do not schedule the periodic task when reset fail
  net: hns3: allocate WQ with WQ_MEM_RECLAIM flag
  net: hns3: remove unnecessary work in hclgevf_main
  net: hns3: remove mailbox and reset work in hclge_main
  net: hns3: schedule hclgevf_service by using delayed workqueue
  net: hns3: refactor the notification scheme of PF reset
  net: hns3: refactor the procedure of VF FLR
  net: hns3: modify hclge_func_reset_sync_vf()'s return type to void
  net: hns3: enlarge HCLGE_RESET_WAIT_CNT
  net: hns3: refactor the precedure of PF FLR
  net: hns3: split hclgevf_reset() into preparing and rebuilding part
  net: hns3: split hclge_reset() into preparing and rebuilding part
  net: hns3: modify an unsuitable reset level for hardware error
  net: hns3: replace an unsuitable variable type in 
hclge_inform_reset_assert_to_vf()
  net: hns3: add protection when get SFP speed as 0
  net: hns3: modify the IRQ name of misc vectors
  net: hns3: modify an unsuitable log in hclge_map_ring_to_vector()
  net: hns3: modify the IRQ name of TQP vector
  net: hns3: re-organize vector handle
  net: hns3: add trace event support for HNS3 driver
+ 
+ [Status]
+ (In Progress): net: hns3: support tx-scatter-gather-fraglist feature
+ (In Progress): net: hns3: add support for configuring VF MAC from the host
+ (In Progress): net: hns3: add support for configuring bandwidth of VF on the 
host
+ (In Progress): net: hns3: add support for setting VF trust
+ (In Progress): net: hns3: add support for spoof check setting
+ (In Progress): net: hns3: add support for setting VF link status on 

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

[Per-Inge]

I get different behavior depending on how I boot the computer using the BIOS 
boot menu
- When I select sda with Ubuntu 20.04, I don't get the error message
- When I select sdc with Fedora 31 and select Ubuntu from Fedora's boot menu I 
get the error message

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

Title:
  initramfs unpacking failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

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

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

[Kernel-packages] [Bug 1859688] Re: Chip Realtek ALC1220 not working properly

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc6

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

Title:
  Chip Realtek ALC1220 not working properly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The problem it is that the new ASUS motherboard doesn't works
  properly, the audio not sounds through the speakers how it shall.

  On "alsamixer" it shows that the card it is a "HDA Intel PCH" and the
  Chip "Realtek ALC1220"

  I read recently that this chip had some problems on users and my question is 
if there is any solution that you could know.
  It's now tested on Ubuntu 19.10; Kernel 5.3.26 (by the moment the S.O. 
doesn't upgrade the kernels to 5.4 or 5.5, and doesn't seems good idea make it 
manually)

  The PC configuration it is a monitor connected via hdmi and Speakers
  "2.1" with power via usb, and output on the second cable from this
  subwoofer. The result it is the sound being hear from left-speaker
  only and quite bad.

  Regards, I left you some extra information below:

  *-core
 descripción: Placa base
 producto: PRIME Z390-A
 fabricante: ASUSTeK COMPUTER INC.
 id físico: 0
 versión: Rev 1.xx
 serie: 190755509801753
 ranura: Default string
   *-firmware
descripción: BIOS
fabricante: American Megatrends Inc.
id físico: 0
versión: 1401
date: 11/26/2019
tamaño: 64KiB
capacidad: 16MiB
capacidades: pci apm upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
   *-memory
descripción: Memoria de sistema
id físico: 4b
ranura: Placa de sistema o placa base
tamaño: 16GiB
  *-bank:0
   descripción: Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL 
NAME PO-Revision-Date: 2012-03-14 06:38+Last-Translator: 
Paco Molinero Language-Team: Spanish MIME-Version: 
1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 
8bitX-Launchpad-Export-Date: 2019-10-10 15:05+X-Generator: Launchpad (build 
af2eefe214bd95389a09b7c956720881bab16807)Project-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME PO-Revision-Date: 2012-03-14 
06:38+Last-Translator: Paco Molinero Language-Team: Spanish 
MIME-Version: 1.0Content-Type: text/plain; 
charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2019-10-10 
15:05+X-Generator: Launchpad (build 
af2eefe214bd95389a09b7c956720881bab16807) [vacío]
   id físico: 0
   ranura: ChannelA-DIMM1
  *-bank:1
   descripción: DIMM DDR4 Síncrono 3200 MHz (0,3 ns)
   producto: CMW16GX4M2C3200C16
   fabricante: Corsair
   id físico: 1
   serie: 
   ranura: ChannelA-DIMM2
   tamaño: 8GiB
   anchura: 64 bits
   reloj: 3200MHz (0.3ns)
  *-bank:2
   descripción: Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL 
NAME PO-Revision-Date: 2012-03-14 06:38+Last-Translator: 
Paco Molinero Language-Team: Spanish MIME-Version: 
1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 
8bitX-Launchpad-Export-Date: 2019-10-10 15:05+X-Generator: Launchpad (build 
af2eefe214bd95389a09b7c956720881bab16807)Project-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME PO-Revision-Date: 2012-03-14 
06:38+Last-Translator: Paco Molinero Language-Team: Spanish 
MIME-Version: 1.0Content-Type: text/plain; 
charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2019-10-10 
15:05+X-Generator: Launchpad (build 
af2eefe214bd95389a09b7c956720881bab16807) [vacío]
   id físico: 2
   ranura: ChannelB-DIMM1
  *-bank:3
   descripción: DIMM DDR4 Síncrono 3200 MHz (0,3 ns)
   producto: CMW16GX4M2C3200C16
   fabricante: Corsair
   id físico: 3
   serie: 
   ranura: ChannelB-DIMM2
   tamaño: 8GiB
   anchura: 64 bits
   reloj: 3200MHz (0.3ns)
   *-cache:0
descripción: L1 caché
id físico: 56
ranura: L1 Cache
tamaño: 256KiB
capacidad: 256KiB
capacidades: synchronous internal write-back unified
configuración: level=1
   *-cache:1
descripción: L2 caché
id físico: 57
ranura: L2 Cache
tamaño: 1MiB
capacidad: 1MiB
capacidades: synchronous internal write-back unified

[Kernel-packages] [Bug 1859781] Re: snd_usb_audio not working in 5.3.0-26-lowlatency

[Kai-Heng Feng]

Please test 5.3.0-28.30 in -proposed.

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

Title:
  snd_usb_audio not working in 5.3.0-26-lowlatency

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  An usb-interface (M-Audio Fast Track C400) is being recognized but not its 
pcm devices.
  The problem does not appear with kernel 5.3.0-24-lowlatency.

  A detailed report can be found here:
  
https://askubuntu.com/questions/1201968/ubuntu-studio-19-10-usb-sound-card-not-working-anymore-appears-in-proc-asound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-26-lowlatency 5.3.0-26.28
  ProcVersionSignature: Ubuntu 5.3.0-26.28-lowlatency 5.3.13
  Uname: Linux 5.3.0-26-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sihorn 1767 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jan 15 09:57:00 2020
  InstallationDate: Installed on 2019-11-27 (48 days ago)
  InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B85-HD3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-lowlatency 
root=UUID=c01dfb46-88ab-4289-8362-b7871c21ef2f ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-lowlatency N/A
   linux-backports-modules-5.3.0-26-lowlatency  N/A
   linux-firmware   1.183.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/04/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85-HD3
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1859979] Re: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing

[Kai-Heng Feng]

Please try 5.3.0-28.30 in -proposed.

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

Title:
  nilfs2 segctord kthread dies after which write to nilfs2 fs freezes
  the process writing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With linux-image-5.3.0-26-lowlatency, segctord kthread encounters a
  "BUG: kernel NULL pointer dereference, address: 00a8" some
  half a minute from boot. Before that, one can log in to the system
  (/home is on a nilfs2 filesystem), but after the kernel BUG report,
  any write to a nilfs2 filesystem freezes the process trying to write,
  or any new login attempt freezes. This bug can be reproduced with
  every boot.

  With linux-image-5.3.0-24-lowlatency and earlier, this doesn't happen.

  Relevant excerpt from syslog:

  ...
  Jan 16 10:56:59 lillukka kernel: [0.00] Linux version 
5.3.0-26-lowlatency (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 
(Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP
   PREEMPT Wed Dec 18 06:21:38 UTC 2019 (Ubuntu 5.3.0-26.28-lowlatency 5.3.13)
  ...
  Jan 16 10:57:13 lillukka kernel: [   28.727753] BUG: kernel NULL pointer 
dereference, address: 00a8
  Jan 16 10:57:13 lillukka kernel: [   28.727852] #PF: supervisor read access 
in kernel mode
  Jan 16 10:57:13 lillukka kernel: [   28.727914] #PF: error_code(0x) - 
not-present page
  Jan 16 10:57:13 lillukka kernel: [   28.727974] PGD 0 P4D 0 
  Jan 16 10:57:13 lillukka kernel: [   28.728012] Oops:  [#1] PREEMPT SMP 
PTI
  Jan 16 10:57:13 lillukka kernel: [   28.728067] CPU: 3 PID: 838 Comm: 
segctord Not tainted 5.3.0-26-lowlatency #28-Ubuntu
  Jan 16 10:57:13 lillukka kernel: [   28.728156] Hardware name: Sony 
Corporation SVP1321C5E/VAIO, BIOS R0280V7 07/11/2013
  Jan 16 10:57:13 lillukka kernel: [   28.728257] RIP: 
0010:percpu_counter_add_batch+0x13/0x80
  Jan 16 10:57:13 lillukka kernel: [   28.728334] Code: e0 41 5c 41 5d 41 5e 5d 
c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 48 89 e5 41 55 41 54 49 89 fc 
53 65 ff 05 b5 5c 
  ed 72 <48> 8b 47 20 48 63 ca 65 44 8b 28 49 63 dd 48 01 f3 48 39 d9 7e 0a
  Jan 16 10:57:13 lillukka kernel: [   28.728536] RSP: 0018:b582c02afcb0 
EFLAGS: 00010082
  Jan 16 10:57:13 lillukka kernel: [   28.728598] RAX: 0002 RBX: 
 RCX: 0001
  Jan 16 10:57:13 lillukka kernel: [   28.728679] RDX: 0018 RSI: 
0001 RDI: 0088
  Jan 16 10:57:13 lillukka kernel: [   28.728760] RBP: b582c02afcc8 R08: 
8f519357ab40 R09: 0018
  Jan 16 10:57:13 lillukka kernel: [   28.728841] R10: 00030140 R11: 
8f5193609eea R12: 0088
  Jan 16 10:57:13 lillukka kernel: [   28.728920] R13: 8f518a3ee498 R14: 
8f518a3ee608 R15: e52b07e5a200
  Jan 16 10:57:13 lillukka kernel: [   28.729001] FS:  () 
GS:8f519798() knlGS:
  Jan 16 10:57:13 lillukka kernel: [   28.729091] CS:  0010 DS:  ES:  
CR0: 80050033
  Jan 16 10:57:13 lillukka kernel: [   28.729157] CR2: 00a8 CR3: 
8d60a002 CR4: 001606e0
  Jan 16 10:57:13 lillukka kernel: [   28.729237] Call Trace:
  Jan 16 10:57:13 lillukka kernel: [   28.729280]  
__test_set_page_writeback+0x2f1/0x310
  Jan 16 10:57:13 lillukka kernel: [   28.729362]  
nilfs_segctor_do_construct+0xd13/0x1260 [nilfs2]
  Jan 16 10:57:13 lillukka kernel: [   28.729432]  ? __switch_to_asm+0x40/0x70
  Jan 16 10:57:13 lillukka kernel: [   28.729496]  
nilfs_segctor_construct+0x1ff/0x2f0 [nilfs2]
  Jan 16 10:57:13 lillukka kernel: [   28.729572]  
nilfs_segctor_thread+0x136/0x3a0 [nilfs2]
  Jan 16 10:57:13 lillukka kernel: [   28.729640]  kthread+0x104/0x140
  Jan 16 10:57:13 lillukka kernel: [   28.729690]  ? 
nilfs_segctor_construct+0x2f0/0x2f0 [nilfs2]
  Jan 16 10:57:13 lillukka kernel: [   28.729760]  ? kthread_park+0x80/0x80
  Jan 16 10:57:13 lillukka kernel: [   28.729807]  ret_from_fork+0x35/0x40
  Jan 16 10:57:13 lillukka kernel: [   28.729854] Modules linked in: ccm rfcomm 
aufs overlay cmac bnep nilfs2 snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi snd_hda_intel pn544_mei mei_phy pn544 
snd_hda_codec hci snd_hda_core snd_hwdep intel_rapl_msr mei_hdcp nfc snd_pcm 
snd_seq_midi snd_seq_midi_event intel_rapl_common x86_pkg_temp_thermal 
intel_powerclamp snd_rawmidi coretemp iwlmvm mac80211 snd_seq btusb btrtl 
libarc4 btbcm uvcvideo btintel kvm videobuf2_vmalloc iwlwifi videobuf2_memops 
bluetooth snd_seq_device videobuf2_v4l2 videobuf2_common irqbypass joydev 
input_leds intel_cstate videodev ecdh_generic snd_timer intel_rapl_perf ecc 
serio_raw mc mei_me cfg80211 mei snd soundcore sony_laptop mac_hid 
intel_smartconnect sch_fq_codel cuse parport_pc ppdev lp parport ip_tables 

[Kernel-packages] [Bug 1859797] Re: trusty/linux-azure: 4.15.0-1067.72~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1859798
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Thursday, 16. January 2020 06:50 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1067.72~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Committed
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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1859798
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Thursday, 16. January 2020 06:50 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
  variant: debs

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

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

[Kernel-packages] [Bug 1859839] Re: the sound is distorted when playing via nvidia hdmi

[Kai-Heng Feng]

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

Title:
  the sound is distorted when playing via nvidia hdmi

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When playing back the sound via nv hdmi, the sound is distorted on Ubuntu 
20.04 LTS with 
  Kernel 5.4.0-9

  No problem if i login with kernel 5.3.0-24-generic

  Ubuntu 20.04 LTS
  nvidia 440.44
  alsa 1.0.25+dfsg-0ubuntu5
  pulseaudio 1:13.0-3ubuntu1
  kernel 5.4.0-9.12
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marco  1792 F pulseaudio
   /dev/snd/controlC1:  marco  1792 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-15 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd MS-7C02
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=30c539b6-2e84-470d-bac2-486e25129f20 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450 TOMAHAWK MAX (MS-7C02)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.50:bd11/07/2019:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWKMAX(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C02
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

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

[Kernel-packages] [Bug 1859797] Re: trusty/linux-azure: 4.15.0-1067.72~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1859798
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Thursday, 16. January 2020 06:50 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   prepare-package: Stalled -- package tag not yet published
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:depwait
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1067.72~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Committed
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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1859798
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Thursday, 16. January 2020 06:50 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
  variant: debs

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

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

[Kernel-packages] [Bug 1859839] Re: the sound is distorted when playing via nvidia hdmi

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc6

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

Title:
  the sound is distorted when playing via nvidia hdmi

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When playing back the sound via nv hdmi, the sound is distorted on Ubuntu 
20.04 LTS with 
  Kernel 5.4.0-9

  No problem if i login with kernel 5.3.0-24-generic

  Ubuntu 20.04 LTS
  nvidia 440.44
  alsa 1.0.25+dfsg-0ubuntu5
  pulseaudio 1:13.0-3ubuntu1
  kernel 5.4.0-9.12
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marco  1792 F pulseaudio
   /dev/snd/controlC1:  marco  1792 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-15 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd MS-7C02
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=30c539b6-2e84-470d-bac2-486e25129f20 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450 TOMAHAWK MAX (MS-7C02)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.50:bd11/07/2019:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWKMAX(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C02
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

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

[Kernel-packages] [Bug 1792672] Re: Regression: acpi reports battery state incorrectly after sleep

[Kai-Heng Feng]

Would it be possible for you to do a kernel bisection?

First, find the last -rc kernel works and the first -rc kernel doesn’t
work from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the working version you found)
$ git bisect bad $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it still have the same issue,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the offending commit.

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

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3D-A03IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1853666] Re: Battery will not charge on Toshiba Satellite Pro A50-C-119

[Kai-Heng Feng]

Please test this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=ff3154d1d89a2343fd5f82e65bc0cf1d4e6659b3

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

Title:
  Battery will not charge on Toshiba Satellite Pro A50-C-119

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I have switched from Windows 10 to Ubuntu, my battery will no
  longer charge. The battery shows 0% charge and says Estimating. Ubuntu
  appears to detect removing the battery as the battery indicator
  disappears and reappears upon replacing the battery. Unplugging the AC
  adaptor with the battery plugged in causes the computer to lose power
  immediately. When the computer is off with battery connected and AC
  adaptor removed, the computer will not switch on. I have bought a new
  battery but that produces the same problem. In Power Settings, the
  battery status is shown as Charging 0%. I believe this to be an ACPI
  issue. I have followed the instructions on these websites:

  https://ubuntu.com/blog/debug-dsdt-ssdt-with-acpica-utilities
  https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips

  The acpi driver loaded is toshiba_acpi. I have extracted some
  information using acpidump and acpiexec which is in the attached file
  acpiexec.log.

  I have delved deeper in to the issue. A search of the DSDT files
  unveiled the following:

  dsdt.dsl:Name (_HID, EisaId ("TOS6208"))  // _HID: Hardware ID
  dsdt.dsl:Name (_HID, EisaId ("TOS620A"))  // _HID: Hardware ID
  dsdt.dsl:Name (_HID, EisaId ("TOS6205"))  // _HID: Hardware ID
  dsdt.dsl:Name (_HID, "ACPI0003" /* Power Source Device */)  // 
_HID: Hardware ID
  dsdt.dsl:Name (_HID, EisaId ("PNP0C0A") /* Control Method Battery 
*/)  // _HID: Hardware ID
  dsdt.dsl:Name (_HID, EisaId ("TOS620D"))  // _HID: Hardware ID

  A search of toshiba_acpi.c shows that TOS6208 is listed as a supported
  device but none of the others are. Please could someone look in to
  this and add the devices to the toshiba_acpi driver if required. Many
  thanks.

  Linux image
  linux-image-5.3.0-23-generic

  cat /proc/version_signature
  Ubuntu 5.3.0-23.25-generic 5.3.7

  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  sudo lspci -vnvn

  00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI 
[8086:1604] (rev 09)
   Subsystem: Toshiba America Info Systems Broadwell-U Host Bridge -OPI 
[1179:0001]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: bdw_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 
[8086:1616] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:000d]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
    DevCap: MaxPayload 128 bytes, PhantFunc 0
     ExtTag- RBE+
    DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
     RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 128 bytes
    DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
    LnkCap: Port #6, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 
<1us, L1 <4us
     ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
     ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s (downgraded), Width x0 (downgraded)
     TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
    SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
     Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
    SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ LinkChg+
     Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
    SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
     Changed: MRL- PresDet- LinkState-
    RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
    RootCap: CRSVisible-
    RootSta: PME ReqID , PMEStatus- PMEPending-
    DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Via WAKE# 
ARIFwd-
  AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
    DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled 
ARIFwd-
  AtomicOpsCtl: ReqEn- EgressBlck-
    LnkCtl2: Target Link Speed: 5GT/s, 

[Kernel-packages] [Bug 1856103] Re: [CML] New device IDs for CMP-V

[You-Sheng Yang]

WIP: https://code.launchpad.net/~vicamo/+git/ubuntu-
kernel/+ref/bug-1856103/new-device-ids-for-cmp-v/oem-osp1-bionic

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

Title:
  [CML] New device IDs for CMP-V

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  new device IDs are required for CMP-V, whether they are published or
  not. Once that is clarified, documentations and device drivers need to
  update accordingly.

  ControllerKernel Version  Commit  Approved to be
  published Comments
  GPIO INT3451| Same as for Sunrisepoint-H 
https://lore.kernel.org/linux-gpio/20200116110951.31644-1-andriy.shevche...@linux.intel.com/
  SPI NOR   0xa3a4
  NPK   0xa3a6v5.5-rc3e4de2a5d51f9
  HS UART   0xa3a7 0xa3a8 0xa3e6 
https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/
  SPI   0xa3a9 0xa3aa 
https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/
 
  I²C   0xa3e0 0xa3e1 0xa3e2 0xa3e3 Next 
https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/
  SMBus 0xa3a3
  USB Device Controller 0xa3b0

  Target Kernel: 5.5
  Target Release: 20.04

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

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

[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit

[Ike Panhc]

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

Title:
  [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE
  kernel branch Edit

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Bug Description]
   hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 
18.04.5 kernel version
  [Steps to Reproduce]
    1)
    2)
    3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
    (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  net: hns3: support tx-scatter-gather-fraglist feature
  net: hns3: add support for configuring VF MAC from the host
  net: hns3: add support for configuring bandwidth of VF on the host
  net: hns3: add support for setting VF trust
  net: hns3: add support for spoof check setting
  net: hns3: add support for setting VF link status on the host
  net: hns3: make array tick_array static, makes object smaller

  net: hns3: fix a wrong reset interrupt status mask
  net: hns3: cleanup of stray struct hns3_link_mode_mapping
  net: hns3: fix ETS bandwidth validation bug
  net: hns3: reallocate SSU' buffer size when pfc_en changes
  net: hns3: add compatible handling for MAC VLAN switch parameter configuration
  net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE
  net: hns3: remove unused macros
  net: hns3: Use the correct style for SPDX License Identifier
  net: hns3: cleanup byte order issues when printed
  net: hns3: cleanup some print format warning
  net: hns3: add or modify some comments
  net: hns3: optimize local variable initialization
  net: hns3: cleanup a format-truncation warning
  net: hns3: cleanup some coding style issues
  net: hns3: cleanup some magic numbers
  net: hns3: add struct netdev_queue debug info for TX timeout
  net: hns3: dump some debug information when reset fail
  treewide: Use sizeof_member() macro
  net: hns3: log and clear hardware error after reset complete
  net: hns3: do not allocate linear data for fraglist skb
  net: hns3: minor cleanup for hns3_handle_rx_bd()
  net: hns3: make struct hns3_enet_ring cacheline aligned
  net: hns3: introduce ring_to_netdev() in enet module
  net: hns3: minor optimization for barrier in IO path
  net: hns3: optimized MAC address in management table.
  net: hns3: remove struct hns3_nic_ring_data in hns3_enet module
  net: hns3: fix mis-counting IRQ vector numbers issue
    net: hns3: fix VF ID issue for setting VF VLAN
  net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx()
  net: hns3: fix for TX queue not restarted problem
   net: hns3: only print misc interrupt status when handling fails
  net: hns3: add a log for getting chain failure in 
hns3_nic_uninit_vector_data()
  net: hns3: add some VF VLAN information for command "ip link show"
  net: hns3: implement ndo_features_check ops for hns3 driver
  net: hns3: get FD rules location before dump in debugfs
  net: hns3: optimization for CMDQ uninitialization
  net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev
  net: hns3: check FE bit before calling hns3_add_frag()
  net: hns3: do not schedule the periodic task when reset fail
  net: hns3: allocate WQ with WQ_MEM_RECLAIM flag
  net: hns3: remove unnecessary work in hclgevf_main
  net: hns3: remove mailbox and reset work in hclge_main
  net: hns3: schedule hclgevf_service by using delayed workqueue
  net: hns3: refactor the notification scheme of PF reset
  net: hns3: refactor the procedure of VF FLR
  net: hns3: modify hclge_func_reset_sync_vf()'s return type to void
  net: hns3: enlarge HCLGE_RESET_WAIT_CNT
  net: hns3: refactor the precedure of PF FLR
  net: hns3: split hclgevf_reset() into preparing and rebuilding part
  net: hns3: split hclge_reset() into preparing and rebuilding part
  net: hns3: modify an unsuitable reset level for hardware error
  net: hns3: replace an unsuitable variable type in 
hclge_inform_reset_assert_to_vf()
  net: hns3: add protection when get SFP speed as 0
  net: hns3: modify the IRQ name of misc vectors
  net: hns3: modify an unsuitable log in hclge_map_ring_to_vector()
  net: hns3: modify the IRQ name of TQP vector
  net: hns3: re-organize vector handle
  net: hns3: add trace event support for HNS3 driver

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1859817] Re: eoan/linux-aws: 5.3.0-1010.11 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859694
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 16. January 2020 23:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 1859816
  variant: debs

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

Title:
  eoan/linux-aws: 5.3.0-1010.11 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 16. January 2020 23:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 1859816
  variant: debs

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

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

[Kernel-packages] [Bug 1859971] Re: Asus ZenBook 14 UX431fl the speakers do not work but the headphones work

[Po-Hsu Lin]

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

Possible fix:
https://github.com/torvalds/linux/commit/436e25505f3458cc92c7f3c985e9cbc198a98209

This has been applied to Eoan master-next branch:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-eoan.git/commit/?h=master-next=0017b78d1701458f5ae37d77c957a60d32955673

The proposed kernel should be available soon, you can test it once it's 
ready[1]. Or wait until it got released to -updates.
I will mark this one as a dup of bug 1856334, which brings in that commit.
Thanks

[1] https://wiki.ubuntu.com/Testing/EnableProposed

** This bug has been marked a duplicate of bug 1856334
   Eoan update: 5.3.16 upstream stable release

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend

[Kai-Heng Feng]

AFAIK there are many fixes in new nvidia driver.

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

Title:
  'gpu has fallen off the bus' after return from suspend

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With this message the only way to resume work is to reboot the system
  using power button.

  With kernel linux-image-5.3.0-13-generic everything is OK.
  Problem appeared afer upgrade to linux-image-5.3.0-17-generic and still 
happens in linux-image-5.3.0-18-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  player 4451 F pulseaudio
   /dev/snd/controlC1:  player 4451 F pulseaudio
   /dev/snd/controlC0:  player 4451 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Oct 14 01:27:04 2019
  HibernationDevice: RESUME=UUID=a58bb700-5818-4ca6-8351-fd4e5e28ea9e
  MachineType: LENOVO 20BG0016US
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=d0c33b75-6f04-4d53-bc3b-91924e3bcf91 ro quiet splash vga=current 
loglevel=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-08 (5 days ago)
  WifiSyslog:
   
  dmi.bios.date: 05/30/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET88WW (2.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BG0016US
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BG0016US
  dmi.product.sku: LENOVO_MT_20BG
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1859096] Re: No sound or Crazy sound on Display port since kernel change to 5.4 (but 5.3.0-24 works)

[Kai-Heng Feng]

There are still too many commits to identify the offending commit.

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

Title:
  No sound or Crazy sound on Display port since kernel change to 5.4
  (but 5.3.0-24 works)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Nvidia driver 440. The sound became crazy on DisplayPort. Volume is not 
adjustable.
  I have either full volume or nothing. sound is crazy on my GTX1650 video card.

  If I use Nouveau driver I have no sound on my Display port.

  If I boot with 5.3.0-24 kernel sound is OK with Nivdia driver.
  But no sound with nouveau driver. Same things append on Focal and on Ubuntu 
19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.44  Sun Dec  8 03:38:56 
UTC 2019
   GCC version:  gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1)
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 10 00:26:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.44, 5.4.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU117 [GeForce GTX 1650] 
[1458:3fcb]
  InstallationDate: Installed on 2020-01-05 (4 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200104)
  MachineType: Micro-Star International Co., Ltd. MS-7B51
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=0b5d6829-5bb4-40e3-9fee-0fdec99e5f5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B51
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1852906] Re: Wifi Problem

[Launchpad Bug Tracker]

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

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

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

Title:
  Wifi Problem

Status in linux package in Ubuntu:
  Expired

Bug description:
  Wifi not working

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

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

[Kernel-packages] [Bug 1860054] Re: the computer freezes at login

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => linux-signed-oem (Ubuntu)

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

Title:
  the computer freezes at login

Status in linux-signed-oem package in Ubuntu:
  New

Bug description:
  At the login page, when the list of users of the computer appears, I have a 
very limited time to press enter, write my password and then press enter again 
to turn on the pc. When I succeeded to do this (otherwise I have to turn of the 
computer pressing the power button), the computer freezed after loading the 
desktop page. In any case, when the pc freezes neither the keyboard, nor the 
mouse work.
  It seems that the problem is related to graphical drivers, since if in the 
grub I start the computer in recovery mode, everything works fine. On Ubuntu 
forums it is suggested that the problem is related to nvidia graphical driver, 
but it is not installed on my computer. 

  Description:  Ubuntu 18.04 LTS (beaver-three-eyed-raven X92)
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1064-oem 4.15.0-1064.73
  ProcVersionSignature: Ubuntu 4.15.0-1064.73-oem 4.15.18
  Uname: Linux 4.15.0-1064-oem x86_64
  NonfreeKernelModules: vtsspp sep5 socperf3 pax wl
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 17 00:58:27 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  InstallationDate: Installed on 2019-10-15 (93 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: linux-signed-oem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1860054] [NEW] the computer freezes at login

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

At the login page, when the list of users of the computer appears, I have a 
very limited time to press enter, write my password and then press enter again 
to turn on the pc. When I succeeded to do this (otherwise I have to turn of the 
computer pressing the power button), the computer freezed after loading the 
desktop page. In any case, when the pc freezes neither the keyboard, nor the 
mouse work.
It seems that the problem is related to graphical drivers, since if in the grub 
I start the computer in recovery mode, everything works fine. On Ubuntu forums 
it is suggested that the problem is related to nvidia graphical driver, but it 
is not installed on my computer. 

Description:Ubuntu 18.04 LTS (beaver-three-eyed-raven X92)
Release:18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1064-oem 4.15.0-1064.73
ProcVersionSignature: Ubuntu 4.15.0-1064.73-oem 4.15.18
Uname: Linux 4.15.0-1064-oem x86_64
NonfreeKernelModules: vtsspp sep5 socperf3 pax wl
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 17 00:58:27 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
InstallationDate: Installed on 2019-10-15 (93 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
SourcePackage: linux-signed-oem
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic
-- 
the computer freezes at login
https://bugs.launchpad.net/bugs/1860054
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-signed-oem in Ubuntu.

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

[Kernel-packages] [Bug 1856103] Re: [CML] New device IDs for CMP-V

[quanxian]

** Description changed:

  new device IDs are required for CMP-V, whether they are published or
  not. Once that is clarified, documentations and device drivers need to
  update accordingly.
  
  ControllerKernel Version  Commit  Approved to be
  published Comments
- GPIO
+ GPIO INT3451| Same as for Sunrisepoint-H 
https://lore.kernel.org/linux-gpio/20200116110951.31644-1-andriy.shevche...@linux.intel.com/
  SPI NOR   0xa3a4
  NPK   0xa3a6v5.5-rc3e4de2a5d51f9
- HS UART   0xa3a7 0xa3a8 0xa3e6
- SPI   0xa3a9 0xa3aa
- I²C   0xa3e0 0xa3e1 0xa3e2 0xa3e3 )
+ HS UART   0xa3a7 0xa3a8 0xa3e6 
https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/
+ SPI   0xa3a9 0xa3aa 
https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/
 
+ I²C   0xa3e0 0xa3e1 0xa3e2 0xa3e3 Next 
https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/
  SMBus 0xa3a3
  USB Device Controller 0xa3b0
  
  Target Kernel: 5.5
  Target Release: 20.04

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

Title:
  [CML] New device IDs for CMP-V

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  new device IDs are required for CMP-V, whether they are published or
  not. Once that is clarified, documentations and device drivers need to
  update accordingly.

  ControllerKernel Version  Commit  Approved to be
  published Comments
  GPIO INT3451| Same as for Sunrisepoint-H 
https://lore.kernel.org/linux-gpio/20200116110951.31644-1-andriy.shevche...@linux.intel.com/
  SPI NOR   0xa3a4
  NPK   0xa3a6v5.5-rc3e4de2a5d51f9
  HS UART   0xa3a7 0xa3a8 0xa3e6 
https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/
  SPI   0xa3a9 0xa3aa 
https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/
 
  I²C   0xa3e0 0xa3e1 0xa3e2 0xa3e3 Next 
https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/
  SMBus 0xa3a3
  USB Device Controller 0xa3b0

  Target Kernel: 5.5
  Target Release: 20.04

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

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

[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic

[Sean Feole]

** Tags added: sru-20200106

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

Title:
  memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with
  Bionic

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

Bug description:
  This failure could be found in the LTP test suite on a Moonshot ARM64
  node with B-4.15, but sometimes it will pass if you try to run it
  manually. (Sometimes not.)

  <<>>
  tag=memcg_test_3 stime=1563249678
  cmdline="memcg_test_3"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  Test timeouted, sending SIGKILL!
  tst_test.c:1140: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1141: BROK: Test killed! (timeout?)

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: 
unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: 
EPERM
  <<>>

  
  When it fails, the attempt to remove files will fail, and most of the 
cgroup_fj_* test will fail:
* cgroup_fj_function_memory
* cgroup_fj_stress_memory_10_3_each
* cgroup_fj_stress_memory_10_3_none
* cgroup_fj_stress_memory_10_3_one
* cgroup_fj_stress_memory_1_200_each
* cgroup_fj_stress_memory_1_200_none
* cgroup_fj_stress_memory_1_200_one
* cgroup_fj_stress_memory_200_1_each
* cgroup_fj_stress_memory_200_1_none
* cgroup_fj_stress_memory_200_1_one
* cgroup_fj_stress_memory_2_2_each
* cgroup_fj_stress_memory_2_2_none
* cgroup_fj_stress_memory_2_2_one
* cgroup_fj_stress_memory_2_9_each
* cgroup_fj_stress_memory_2_9_none
* cgroup_fj_stress_memory_2_9_one
* cgroup_fj_stress_memory_3_3_each
* cgroup_fj_stress_memory_3_3_none
* cgroup_fj_stress_memory_3_3_one
* cgroup_fj_stress_memory_4_4_each
* cgroup_fj_stress_memory_4_4_none
* cgroup_fj_stress_memory_4_4_one

  Steps to run this:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "memcg_test_3memcg_test_3" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 16 03:46 seq
   crw-rw 1 root audio 116, 33 Jul 16 03:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  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: Tue Jul 16 04:16:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.173.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1859793] Re: bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859705
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 16. January 2020 22:41 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Friday, 17. January 2020 02:21 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1859791
  variant: debs

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

Title:
  bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859705
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 17. January 2020 02:21 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1859791
  variant: debs

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

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

[Kernel-packages] [Bug 1852976] Re: zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on D-Oracle

[Sean Feole]

** Tags added: sru-20200106

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

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

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

** Tags added: bionic

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

Title:
  zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on
  D-Oracle

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in linux-signed-oracle package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New
Status in linux-signed-oracle source package in Bionic:
  New
Status in linux-aws source package in Disco:
  New
Status in linux-signed-oracle source package in Disco:
  Invalid

Bug description:
  It looks like the failures in zram01 are causing zram02 and zram03 to
  fail as well.

  Seems that this is broken since commit 7cfac804 (zram: Rewrite shell
  tests into new API)

   tag=zram01 stime=1573887406 dur=300 exit=signaled stat=9 core=no cu=23757 
cs=7590
   startup='Sat Nov 16 06:56:46 2019'
   zram01 1 TINFO: timeout per run is 0h 5m 0s
   zram01 1 TINFO: create '4' zram device(s)
   zram01 1 TPASS: test succeeded
   zram01 1 TCONF: The device attribute max_comp_streams was introduced in 
kernel 3.15 and deprecated in 4.7
   zram01 2 TINFO: test that we can set compression algorithm
   zram01 2 TINFO: supported algs: [lzo] lz4 lz4hc 842 zstd
   zram01 2 TINFO: /sys/block/zram0/comp_algorithm = 'lzo' (1/4)
   zram01 2 TINFO: /sys/block/zram1/comp_algorithm = 'lzo' (2/4)
   zram01 2 TINFO: /sys/block/zram2/comp_algorithm = 'lzo' (3/4)
   zram01 2 TINFO: /sys/block/zram3/comp_algorithm = 'lzo' (4/4)
   zram01 2 TPASS: test succeeded
   zram01 3 TINFO: set disk size to zram device(s)
   zram01 3 TINFO: /sys/block/zram0/disksize = '26214400' (1/4)
   zram01 3 TINFO: /sys/block/zram1/disksize = '26214400' (2/4)
   zram01 3 TINFO: /sys/block/zram2/disksize = '26214400' (3/4)
   zram01 3 TINFO: /sys/block/zram3/disksize = '402653184' (4/4)
   zram01 3 TPASS: test succeeded
   zram01 4 TINFO: set memory limit to zram device(s)
   zram01 4 TINFO: /sys/block/zram0/mem_limit = '25M' (1/4)
   zram01 4 TINFO: /sys/block/zram1/mem_limit = '25M' (2/4)
   zram01 4 TINFO: /sys/block/zram2/mem_limit = '25M' (3/4)
   zram01 4 TINFO: /sys/block/zram3/mem_limit = '384M' (4/4)
   zram01 4 TPASS: test succeeded
   zram01 5 TINFO: make ext3 filesystem on /dev/zram0
   zram01 5 TINFO: make ext4 filesystem on /dev/zram1
   zram01 5 TINFO: make xfs filesystem on /dev/zram2
   zram01 5 TINFO: make btrfs filesystem on /dev/zram3
   zram01 5 TPASS: zram_makefs succeeded
   zram01 6 TINFO: mount /dev/zram0
   zram01 6 TINFO: mount /dev/zram1
   zram01 6 TINFO: mount /dev/zram2
   zram01 6 TINFO: mount /dev/zram3
   zram01 6 TPASS: mount of zram device(s) succeeded
   zram01 7 TINFO: filling zram0 (it can take long time)
   zram01 7 TPASS: zram0 was filled with '20628' KB
   zram01 7 TPASS: compression ratio: 732.90:1
   zram01 7 TINFO: filling zram1 (it can take long time)
   zram01 7 TPASS: zram1 was filled with '20140' KB
   zram01 7 TPASS: compression ratio: 5151.97:1
   zram01 7 TINFO: filling zram2 (it can take long time)
   zram01 7 TPASS: zram2 was filled with '17756' KB
   zram01 7 TPASS: compression ratio: 285.26:1
   zram01 7 TINFO: filling zram3 (it can take long time)
   zram01 1 TBROK: test killed, timeout! If you are running on slow machine, 
try exporting LTP_TIMEOUT_MUL > 1

   tag=zram02 stime=1573887712 dur=0 exit=exited stat=1 core=no cu=2 cs=0
   startup='Sat Nov 16 07:01:52 2019'
   zram02 1 TINFO: timeout per run is 0h 5m 0s
   zram02 1 TINFO: create '1' zram device(s)
   zram02 1 TFAIL: unexpected num of devices: 4
   /opt/ltp/testcases/bin/zram02.sh: 27: echo: echo: I/O error
   zram02 1 TINFO: AppArmor enabled, this may affect test results
   zram02 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
   zram02 1 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 0
   failed 1
   skipped 0
   warnings 0

   tag=zram03 stime=1573887718 dur=0 exit=exited stat=2 core=no cu=0 cs=0
   startup='Sat Nov 16 07:01:58 2019'
   zram03 0 TINFO : create a zram device with 536870912 bytes in size.
   zram03 1 TBROK : safe_file_ops.c:301: Failed to close FILE 
'/sys/block/zram0/disksize' at zram03.c:87: errno=EBUSY(16): Device or resource 
busy
   zram03 2 TBROK : safe_file_ops.c:301: Remaining cases broken

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9
  ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21
  Uname: Linux 5.0.0-1005-oracle x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Nov 18 07:50:37 2019
  

[Kernel-packages] [Bug 1858543] Re: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: '1859724'
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Monday, 13. January 2020 16:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-5.0: bug 1858542
  variant: debs

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

Title:
  disco/linux-oracle: 5.0.0-1010.15 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: '1859724'
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Monday, 13. January 2020 16:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-5.0: bug 1858542
  variant: debs

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

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

[Kernel-packages] [Bug 1858543] Re: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker

[Sean Feole]

Boot/Smoke passed

** Tags added: regression-testing-passed

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

Title:
  disco/linux-oracle: 5.0.0-1010.15 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: '1859724'
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Monday, 13. January 2020 16:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-5.0: bug 1858542
  variant: debs

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

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

[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption

[Daniel van Vugt]

Finally, the problem might be triggered by the atomic modesetting code
used by Xorg sessions. Please try logging into 'Ubuntu on Wayland' and
tell us if that avoids some of the problem.

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

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

Title:
  [comet lake] Gnome freezes, icons missing, graphics corruption

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

Bug description:
  ack please..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jan 14 20:17:26 2020
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
   backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2020-01-13 (1 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0029 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic 
root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1859071] Re: Modesetting randomly fails to offer all modes available in the EDID

[Daniel van Vugt]

Thanks!

The login screen uses Wayland so that's also a good test in itself. If
the issue affects the Wayland backend then it sounds like this is a
kernel or hardware problem. To check that, next time the issue happens,
please run:

  grep . /sys/class/drm/*/modes > modes.txt

and then attach the file 'modes.txt' here.

---

Just a guess: The problem might be timeouts on the i2c bus waiting for
the monitor to return its EDID. So that could happen randomly. In that
case, maybe try a different DisplayPort cable if you can.

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

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

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

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

Title:
  Modesetting randomly fails to offer all modes available in the EDID

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10
  $ apt-cache policy gdm3
  gdm3:
Installed: 3.34.1-1ubuntu1
Candidate: 3.34.1-1ubuntu1
Version table:
   *** 3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt-cache policy lightdm
  lightdm:
Installed: 1.30.0-0ubuntu1
Candidate: 1.30.0-0ubuntu1
Version table:
   *** 1.30.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status
  $ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)

  
  I have a 3rd gen Intel laptop with only Ubuntu 19.10 installed, and a monitor 
attached via DisplayPort. The monitor has a native resolution of 2560x1080. 
When I power on my laptop, it is seemingly random whether one of the three 
following situations occurs. 
  1. Displays at the proper native resolution of 2560x1080,
  2. Displays at 1600x1200 but not let me select a higher resolution in display 
settings, or 
  3. The display will fail to connect and stay blank (when I enter display 
settings it will be on "Single Monitor" mode, but from there I can enable Join 
Displays and set it to its native resolution).

  Please note I selected "I don't know" instead of gdm3 or lightdm since
  i've been having this issue since before installing/switching to
  lightdm.

  Please let me know what additional information I can provide at this time.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f7]
  InstallationDate: Installed on 2020-01-05 (9 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 2478A44
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=5b93649d-7f54-41f8-85e1-dc9d5d494872 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G3ET96WW(2.56)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2478A44
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG3ET96WW(2.56):bd08/23/2013:svnLENOVO:pn2478A44:pvrThinkPadL530:rvnLENOVO:rn2478A44:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L530
  dmi.product.name: 2478A44
  dmi.product.sku: LENOVO_MT_2478
  dmi.product.version: ThinkPad L530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1859718] Re: xenial/linux: 4.4.0-173.203 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 16. January 2020 04:02 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
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-lts-xenial: bug 1859717, bug 1858592
+   trusty/linux-lts-xenial: bug 1859717
xenial/linux-fips: bug 1858589
xenial/linux-raspi2: bug 1858586
xenial/linux-snapdragon: bug 1858588
xenial/linux/caracalla-kernel: bug 1859714
xenial/linux/pc-kernel: bug 1859715
xenial/linux/stlouis-kernel: bug 1859716
  variant: debs

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

Title:
  xenial/linux: 4.4.0-173.203 -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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 16. January 2020 04:02 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
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-lts-xenial: bug 1859717
xenial/linux-fips: bug 1858589
xenial/linux-raspi2: bug 1858586
xenial/linux-snapdragon: bug 1858588
xenial/linux/caracalla-kernel: bug 1859714
xenial/linux/pc-kernel: bug 1859715
xenial/linux/stlouis-kernel: bug 1859716
  variant: debs

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

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

[Kernel-packages] [Bug 1859694] Re: eoan/linux: 5.3.0-28.30 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 16. January 2020 01:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1859693
eoan/linux-aws: bug 1859817
eoan/linux-azure: bug 1859820
-   eoan/linux-raspi2: bug 1858941, bug 1859692
+   eoan/linux-raspi2: bug 1859692
  variant: debs

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

Title:
  eoan/linux: 5.3.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 16. January 2020 01:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1859693
eoan/linux-aws: bug 1859817
eoan/linux-azure: bug 1859820
eoan/linux-raspi2: bug 1859692
  variant: debs

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

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

[Kernel-packages] [Bug 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)

[john]

OK so it's a fairly long time since anyone has said anything thing about this 
problem. I found a resolution after reading about the symtoms online. I have a 
G5 dual without the issues and a Emac G4 single without the issues. However my 
G4 1.5 macmini would constantly freeze up. So the "fix" is to enter at 
install... live video=offb:off video=radeonfb:off radeon.modeset=1 
radeon.agp.mode=-1
after install and reboot at yaboot screen enter... Linux video=offb:off 
video=radeon.modeset=1 radeon.agpmode=-1

This works on the G4 mini but requires the (after install) line
everytime you reboot the computer.Not so much a fix but rather a control
measure and a little bit of a hassle but it does work. I havn't tried it
on my dual G4's or any other mac than the emac G4 but i suspect any card
based mac doed not need it just the ones with  the graphics on the
motherboard (radeon) BTW i want to thank all peoples who work hard to
bring us users the various Linux's for the powermacs. Up until recently
you have kept these machines alive and worthwhile.

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

Title:
  System freezes shortly after reaching the desktop (Ubuntu MATE 16.04,
  PowerPC)

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

Bug description:
  The freeze happens every time unless I use "radeon.agpmode=-1" as a
  kernel parameter.

  Affected machines:
  PowerBook G4 5,6 + PowerMac G5 7,3 (w. "ATI Radeon 9600 AP (AGP)".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-powerpc-smp 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-powerpc-smp 4.4.6
  Uname: Linux 4.4.0-18-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.373
  CurrentDesktop: MATE
  Date: Sun Apr 17 21:08:40 2016
  IwConfig:
   lono wireless extensions.

   enP2p36s15f0  no wireless extensions.
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160417.1)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: ro ramdisk_size=1048576 file=/cdrom/preseed/username.seed 
boot=casper quiet --- radeon.agpmode=-1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-powerpc-smp N/A
   linux-backports-modules-4.4.0-18-powerpc-smp  N/A
   linux-firmware1.157
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1859692] Re: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Promote to Proposed
- phase-changed: Thursday, 16. January 2020 22:06 UTC
+ phase: Testing
+ phase-changed: Thursday, 16. January 2020 23:41 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 16. January 2020 23:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

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

[Kernel-packages] [Bug 1859817] Re: eoan/linux-aws: 5.3.0-1010.11 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859694
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
- phase: Promote to Proposed
- phase-changed: Thursday, 16. January 2020 21:56 UTC
+ phase: Testing
+ phase-changed: Thursday, 16. January 2020 23:36 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 1859816
  variant: debs

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

Title:
  eoan/linux-aws: 5.3.0-1010.11 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 16. January 2020 23:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 1859816
  variant: debs

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

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

[Kernel-packages] [Bug 1858533] Re: bionic/linux-azure: 5.0.0-1029.31~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1858534
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 16. January 2020 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   stakeholder-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1858532
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1029.31~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1858534
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 16. January 2020 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1858532
  variant: debs

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

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

[Kernel-packages] [Bug 1859798] Re: xenial/linux-azure: 4.15.0-1067.72 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859705
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 16. January 2020 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   stakeholder-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1859797
xenial/linux-azure/azure-kernel: bug 1859796
  variant: debs

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

Title:
  xenial/linux-azure: 4.15.0-1067.72 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859705
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 16. January 2020 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1859797
xenial/linux-azure/azure-kernel: bug 1859796
  variant: debs

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

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

[Kernel-packages] [Bug 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859694
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 16. January 2020 11:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   stakeholder-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1859819
  variant: debs

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

Title:
  eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 16. January 2020 11:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1859819
  variant: debs

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

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

[Kernel-packages] [Bug 1859793] Re: bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1859705
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Packaging
- phase-changed: Wednesday, 15. January 2020 21:16 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 16. January 2020 22:41 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1859791
  variant: debs

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

Title:
  bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1859705
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 16. January 2020 22:41 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1859791
  variant: debs

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

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

[Kernel-packages] [Bug 1859801] Re: bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Promote to Proposed
- phase-changed: Thursday, 16. January 2020 21:46 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 16. January 2020 22:31 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
+   promote-signing-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 16. January 2020 22:31 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1859692] Re: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 16. January 2020 21:56 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 16. January 2020 22:06 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 22:06 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 22:06 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

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

[Kernel-packages] [Bug 1859692] Re: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 22:06 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

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

[Kernel-packages] [Bug 1859817] Re: eoan/linux-aws: 5.3.0-1010.11 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859694
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 21:56 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-aws-5.3: bug 1859816
  variant: debs

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

Title:
  eoan/linux-aws: 5.3.0-1010.11 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 21:56 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-aws-5.3: bug 1859816
  variant: debs

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

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

[Kernel-packages] [Bug 1858941] Re: eoan/linux-raspi2: 5.3.0-1016.18 -proposed tracker

[Ubuntu Kernel Bot]

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

** This bug has been marked a duplicate of bug 1859692
   eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

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

Title:
  eoan/linux-raspi2: 5.3.0-1016.18 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: '1859694'
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Friday, 10. January 2020 14:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1858940
eoan/linux-raspi2/pi-kernel: bug 1858939
  variant: debs

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

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

[Kernel-packages] [Bug 1859801] Re: bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 21:46 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
  variant: debs

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

Title:
  bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 21:46 UTC
  reason:
promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
  variant: debs

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

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

[Kernel-packages] [Bug 1859817] Re: eoan/linux-aws: 5.3.0-1010.11 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859694
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 16. January 2020 13:31 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 16. January 2020 21:56 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  trackers:
bionic/linux-aws-5.3: bug 1859816
  variant: debs

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

Title:
  eoan/linux-aws: 5.3.0-1010.11 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 21:56 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  trackers:
bionic/linux-aws-5.3: bug 1859816
  variant: debs

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

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

[Kernel-packages] [Bug 1859692] Re: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-eoan

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 16. January 2020 18:32 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 16. January 2020 21:56 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
- replaces: bug 1858941
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 16. January 2020 21:56 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

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

[Kernel-packages] [Bug 1859817] Re: eoan/linux-aws: 5.3.0-1010.11 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  eoan/linux-aws: 5.3.0-1010.11 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 21:56 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  trackers:
bionic/linux-aws-5.3: bug 1859816
  variant: debs

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

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

[Kernel-packages] [Bug 1859801] Re: bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 16. January 2020 19:52 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 16. January 2020 21:46 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

Title:
  bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 21:46 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1859801] Re: bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Promote to Proposed
  phase-changed: Thursday, 16. January 2020 21:46 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

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

Title:
  BUG: scheduling while atomic: in low latency kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This dmesg report happens with the low latency kernel.

  It does not happen with the generic kernel or the liquorix low latency
  kernels

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-38-lowlatency 5.0.0-38.41
  ProcVersionSignature: Ubuntu 5.0.0-38.41-lowlatency 5.0.21
  Uname: Linux 5.0.0-38-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mac1974 F jackdbus
   /dev/snd/pcmC0D0c:   mac1974 F...m jackdbus
   /dev/snd/pcmC0D0p:   mac1974 F...m jackdbus
  CurrentDesktop: XFCE
  Date: Thu Jan 16 15:56:16 2020
  InstallationDate: Installed on 2018-06-07 (588 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: System76, Inc. Serval WS
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-lowlatency 
root=UUID=786d7ee0-282e-4bfa-aa7f-8596fba803b7 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-38-lowlatency N/A
   linux-backports-modules-5.0.0-38-lowlatency  N/A
   linux-firmware   
1.183.2+system76~1573660723~19.04~813d257~dev
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-06-10 (220 days ago)
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.10RSA1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Serval WS
  dmi.product.sku: Not Applicable
  dmi.product.version: serw9
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1860041] [NEW] shiftfs: prevent lower dentries from going negative during unlink

[Christian Brauner]

Public bug reported:

SRU Justification

Impact: All non-special files (For shiftfs this only includes fifos and
- for this case - unix sockets - since we don't allow character and
block devices to be created.) go through shiftfs_open() and have their
dentry pinned through this codepath preventing it from going negative.
But fifos don't use the shiftfs fops but rather use the pipefifo_fops
which means they do not go through shiftfs_open() and thus don't have
their dentry pinned that way. Thus, the lower dentries for such files
can go negative on unlink causing segfaults. The following C program can
be used to reproduce the crash:

#include 
#include 
#include 
#include 
#include 
#include 
#include 

int main(int argc, char *argv[])
{
struct stat stat;

unlink("./bbb");

int ret = mknod("./bbb", S_IFIFO|0666, 0);
if (ret < 0)
exit(1);

int fd = open("./bbb", O_RDWR);
if (fd < 0)
exit(2);

if (unlink("./bbb"))
exit(4);

fstat(fd, );

return 0;
}

Fix: Similar to ecryptfs we need to dget() the lower dentry before
calling vfs_unlink() on it and dput() it afterwards.

Regression Potential: Limited to shiftfs.

Test Case: Compiled a kernel with the fix and used the reproducer above
to verify that the kernel cannot be crashed anymore.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Christian Brauner (cbrauner)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Christian Brauner (cbrauner)

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

Title:
  shiftfs: prevent lower dentries from going negative during unlink

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: All non-special files (For shiftfs this only includes fifos
  and - for this case - unix sockets - since we don't allow character
  and block devices to be created.) go through shiftfs_open() and have
  their dentry pinned through this codepath preventing it from going
  negative. But fifos don't use the shiftfs fops but rather use the
  pipefifo_fops which means they do not go through shiftfs_open() and
  thus don't have their dentry pinned that way. Thus, the lower dentries
  for such files can go negative on unlink causing segfaults. The
  following C program can be used to reproduce the crash:

  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char *argv[])
  {
struct stat stat;

  unlink("./bbb");

int ret = mknod("./bbb", S_IFIFO|0666, 0);
if (ret < 0)
exit(1);

int fd = open("./bbb", O_RDWR);
if (fd < 0)
exit(2);

if (unlink("./bbb"))
exit(4);

  fstat(fd, );

return 0;
  }

  Fix: Similar to ecryptfs we need to dget() the lower dentry before
  calling vfs_unlink() on it and dput() it afterwards.

  Regression Potential: Limited to shiftfs.

  Test Case: Compiled a kernel with the fix and used the reproducer
  above to verify that the kernel cannot be crashed anymore.

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

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

[Kernel-packages] [Bug 1859694] Re: eoan/linux: 5.3.0-28.30 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 16. January 2020 01:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1859693
eoan/linux-aws: bug 1859817
eoan/linux-azure: bug 1859820
-   eoan/linux-raspi2: bug 1859692
+   eoan/linux-raspi2: bug 1858941, bug 1859692
  variant: debs

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

Title:
  eoan/linux: 5.3.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 16. January 2020 01:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1859693
eoan/linux-aws: bug 1859817
eoan/linux-azure: bug 1859820
eoan/linux-raspi2: bug 1858941, bug 1859692
  variant: debs

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

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

[Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files

[Launchpad Bug Tracker]

This bug was fixed in the package linux-hwe - 5.3.0-26.28~18.04.1

---
linux-hwe (5.3.0-26.28~18.04.1) bionic; urgency=medium

  * bionic/linux-hwe: 5.3.0-26.28~18.04.1 -proposed tracker (LP:
#1856849)

  [ Ubuntu: 5.3.0-26.28 ]

  * eoan/linux: 5.3.0-26.28 -proposed tracker (LP: #1856807)
  * nvidia-435 is in eoan, linux-restricted-modules only builds against 430,
ubiquity gives me the self-signed modules experience instead of using the
Canonical-signed modules (LP: #1856407)
- Add nvidia-435 dkms build

linux-hwe (5.3.0-25.27~18.04.2) bionic; urgency=medium

  * bionic/linux-hwe: 5.3.0-25.27~18.04.2 -proposed tracker (LP:
#1856210)

  * Packaging resync (LP: #1786013)
- [Packaging] HWE kernel is not signed on Bionic

linux-hwe (5.3.0-25.27~18.04.1) bionic; urgency=medium

  * bionic/linux-hwe: 5.3.0-25.27~18.04.1 -proposed tracker (LP:
#1855309)

  [ Ubuntu: 5.3.0-25.27 ]

  * eoan/linux: 5.3.0-25.27 -proposed tracker (LP: #1854762)
  * CVE-2019-14901
- SAUCE: mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame()
  * CVE-2019-14896 // CVE-2019-14897
- SAUCE: libertas: Fix two buffer overflows at parsing bss descriptor
  * CVE-2019-14895
- SAUCE: mwifiex: fix possible heap overflow in mwifiex_process_country_ie()
  * [CML] New device id's for CMP-H (LP: #1846335)
- mmc: sdhci-pci: Add another Id for Intel CML
- i2c: i801: Add support for Intel Comet Lake PCH-H
- mtd: spi-nor: intel-spi: Add support for Intel Comet Lake-H SPI serial 
flash
- mfd: intel-lpss: Add Intel Comet Lake PCH-H PCI IDs
  * i915: Display flickers (monitor loses signal briefly) during "flickerfree"
boot, while showing the BIOS logo on a black background (LP: #1836858)
- [Config] FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y
  * Please add patch fixing RK818 ID detection (LP: #1853192)
- SAUCE: mfd: rk808: Fix RK818 ID template
  * Kernel build log filled with "/bin/bash: line 5: warning: command
substitution: ignored null byte in input" (LP: #1853843)
- [Debian] Fix warnings when checking for modules signatures
  * Lenovo dock MAC Address pass through doesn't work in Ubuntu  (LP: #1827961)
- r8152: Add macpassthru support for ThinkPad Thunderbolt 3 Dock Gen 2
  * Dell XPS 13 9350/9360 headphone audio hiss (LP: #1654448) // [XPS 13 9360,
Realtek ALC3246, Black Headphone Out, Front] High noise floor (LP: #1845810)
- ALSA: hda/realtek: Reduce the Headphone static noise on XPS 9350/9360
  * no HDMI video output since GDM greeter after linux-oem-osp1 version
5.0.0-1026 (LP: #1852386)
- drm/i915: Add new CNL PCH ID seen on a CML platform
- SAUCE: drm/i915: Fix detection for a CMP-V PCH
  * [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer
works on Dell Venue 11 Pro 7140 (LP: #1846539)
- [Config] Drop snd-sof-intel-bdw build
- SAUCE: ASoC: SOF: Intel: Broadwell: clarify mutual exclusion with legacy
  driver
  * [CML-S62] Need enable turbostat patch support for Comet lake- S 6+2
(LP: #1847451)
- SAUCE: tools/power turbostat: Add Cometlake support
  * External microphone can't work on some dell machines with the codec alc256
or alc236 (LP: #1853791)
- SAUCE: ALSA: hda/realtek - Move some alc256 pintbls to fallback table
- SAUCE: ALSA: hda/realtek - Move some alc236 pintbls to fallback table
  * Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection
(LP: #1853197)
- xfrm: Fix memleak on xfrm state destroy
  * CVE-2019-18660: patches for Ubuntu (LP: #1853142) // CVE-2019-18660
- powerpc/64s: support nospectre_v2 cmdline option
- powerpc/book3s64: Fix link stack flush on context switch
- KVM: PPC: Book3S HV: Flush link stack on guest exit to host kernel
  * Raydium Touchscreen on ThinkPad L390 does not work (LP: #1849721)
- HID: i2c-hid: fix no irq after reset on raydium 3118
  * Make Goodix I2C touchpads work (LP: #1853842)
- HID: i2c-hid: Remove runtime power management
- HID: i2c-hid: Send power-on command after reset
  * Touchpad doesn't work on Dell Inspiron 7000 2-in-1 (LP: #1851901)
- Revert "UBUNTU: SAUCE: mfd: intel-lpss: add quirk for Dell XPS 13 7390
  2-in-1"
- lib: devres: add a helper function for ioremap_uc
- mfd: intel-lpss: Use devm_ioremap_uc for MMIO
  * CVE-2019-19055
- nl80211: fix memory leak in nl80211_get_ftm_responder_stats
  * CML: perf enabling for core (LP: #1848978)
- perf/x86/intel: Add Comet Lake CPU support
- perf/x86/msr: Add Comet Lake CPU support
- perf/x86/cstate: Add Comet Lake CPU support
- perf/x86/msr: Add new CPU model numbers for Ice Lake
- perf/x86/cstate: Update C-state counters for Ice Lake
  * Boot hangs after "Loading initial ramdisk ..."  (LP: #1852586)
- SAUCE: Revert "tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for
  interrupts"
- SAUCE: Revert "tpm_tis_core: Turn on the TPM before probing IRQ's"
  * [CML-S62] Need enable intel_rapl 

[Kernel-packages] [Bug 1843327] Re: vmlinuz is world-readable

[Launchpad Bug Tracker]

This bug was fixed in the package linux-signed-hwe - 5.3.0-26.28~18.04.1

---
linux-signed-hwe (5.3.0-26.28~18.04.1) bionic; urgency=medium

  * Master version: 5.3.0-26.28~18.04.1

linux-signed-hwe (5.3.0-25.27~18.04.2) bionic; urgency=medium

  * Master version: 5.3.0-25.27~18.04.2
  * Bump upload number.

linux-signed-hwe (5.3.0-25.27~18.04.1) bionic; urgency=medium

  * Master version: 5.3.0-25.27~18.04.1

  * vmlinuz is world-readable (LP: #1843327)
- fix vmlinuz-* permissions for opal signed kernels

  * Miscellaneous Ubuntu changes
- [Packaging] Rolling hwe-edge into hwe

 -- Kleber Sacilotto de Souza   Wed, 18 Dec
2019 16:20:33 +0100

** Changed in: linux-signed-hwe (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  vmlinuz is world-readable

Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-signed-hwe package in Ubuntu:
  Fix Released
Status in linux-signed source package in Xenial:
  Invalid
Status in linux-signed-hwe source package in Xenial:
  Fix Released
Status in linux-signed source package in Bionic:
  Fix Released
Status in linux-signed-hwe source package in Bionic:
  Fix Released
Status in linux-signed source package in Disco:
  Fix Released
Status in linux-signed-hwe source package in Disco:
  Invalid

Bug description:
  [Impact]
  ppc64el vmlinuz is world-readable, possibly impacting security on that 
platform.

  [Test case]
  Verify vmlinuz is not world-readable after the fix.

  [Regression potential]
  File permissions may be wrong, possibly allowing attack.

  
  --

==
FAIL: test_096_boot_symbols_unreadable (__main__.KernelSecurityTest)
kernel addresses in /boot are not world readable
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1438, in 
test_096_boot_symbols_unreadable
self.assertEqual(os.stat(name).st_mode & mask, expected, '%s is world 
readable' % (name))
AssertionError: /boot/vmlinux-4.15.0-62-generic is world readable

--
Ran 125 tests in 31.183s

FAILED (failures=1)

  This currently affects ppc64el.

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

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

[Kernel-packages] [Bug 1860039] [NEW] BUG: scheduling while atomic: in low latency kernel

[Mac]

Public bug reported:

This dmesg report happens with the low latency kernel.

It does not happen with the generic kernel or the liquorix low latency
kernels

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-38-lowlatency 5.0.0-38.41
ProcVersionSignature: Ubuntu 5.0.0-38.41-lowlatency 5.0.21
Uname: Linux 5.0.0-38-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mac1974 F jackdbus
 /dev/snd/pcmC0D0c:   mac1974 F...m jackdbus
 /dev/snd/pcmC0D0p:   mac1974 F...m jackdbus
CurrentDesktop: XFCE
Date: Thu Jan 16 15:56:16 2020
InstallationDate: Installed on 2018-06-07 (588 days ago)
InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
MachineType: System76, Inc. Serval WS
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-lowlatency 
root=UUID=786d7ee0-282e-4bfa-aa7f-8596fba803b7 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-38-lowlatency N/A
 linux-backports-modules-5.0.0-38-lowlatency  N/A
 linux-firmware   
1.183.2+system76~1573660723~19.04~813d257~dev
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-06-10 (220 days ago)
dmi.bios.date: 07/11/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.10RSA1
dmi.board.asset.tag: Tag 12345
dmi.board.name: Serval WS
dmi.board.vendor: System76, Inc.
dmi.board.version: serw9
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Serval WS
dmi.product.sku: Not Applicable
dmi.product.version: serw9
dmi.sys.vendor: System76, Inc.

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


** Tags: amd64 apport-bug disco

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

Title:
  BUG: scheduling while atomic: in low latency kernel

Status in linux package in Ubuntu:
  New

Bug description:
  This dmesg report happens with the low latency kernel.

  It does not happen with the generic kernel or the liquorix low latency
  kernels

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-38-lowlatency 5.0.0-38.41
  ProcVersionSignature: Ubuntu 5.0.0-38.41-lowlatency 5.0.21
  Uname: Linux 5.0.0-38-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mac1974 F jackdbus
   /dev/snd/pcmC0D0c:   mac1974 F...m jackdbus
   /dev/snd/pcmC0D0p:   mac1974 F...m jackdbus
  CurrentDesktop: XFCE
  Date: Thu Jan 16 15:56:16 2020
  InstallationDate: Installed on 2018-06-07 (588 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: System76, Inc. Serval WS
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-lowlatency 
root=UUID=786d7ee0-282e-4bfa-aa7f-8596fba803b7 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-38-lowlatency N/A
   linux-backports-modules-5.0.0-38-lowlatency  N/A
   linux-firmware   
1.183.2+system76~1573660723~19.04~813d257~dev
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-06-10 (220 days ago)
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.10RSA1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Serval WS
  dmi.product.sku: Not Applicable
  dmi.product.version: serw9
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1859798] Re: xenial/linux-azure: 4.15.0-1067.72 -proposed tracker

[Steve Beattie]

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

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

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

Title:
  xenial/linux-azure: 4.15.0-1067.72 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859705
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 16. January 2020 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1859797
xenial/linux-azure/azure-kernel: bug 1859796
  variant: debs

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

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

[Kernel-packages] [Bug 1859795] Re: bionic/linux-aws: 4.15.0-1058.60 -proposed tracker

[Steve Beattie]

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

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

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

Title:
  bionic/linux-aws: 4.15.0-1058.60 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859705
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 16. January 2020 10:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1859801
bionic/linux-aws/aws-kernel: bug 1859794
xenial/linux-aws-hwe: bug 1859802
  variant: debs

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

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

[Kernel-packages] [Bug 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

[Steve Beattie]

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

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

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

Title:
  eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859694
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 16. January 2020 11:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1859819
  variant: debs

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

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

[Kernel-packages] [Bug 1860013] Re: [thunderx] Synchronous External Abort: synchronous parity or ECC error

[dann frazier]

Also reproducible w/ the 5.0.0-37.40 kernel. I'll try a mainline 5.5-rc6
build next.

[  602.796765] Internal error: synchronous parity or ECC error: 9618 [#1] 
SMP
[  602.803994] Modules linked in: nls_iso8859_1 cavium_rng_vf ipmi_ssif 
ipmi_devintf input_leds joydev ipmi_msghandler thunderx_edac cavium_rng 
sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear aes_ce_blk 
aes_ce_cipher nicvf cavium_ptp ast i2c_algo_bit ttm drm_kms_helper crct10dif_ce 
ghash_ce syscopyarea sysfillrect sha2_ce sysimgblt uas hid_generic nicpf 
fb_sys_fops sha256_arm64 drm sha1_ce usbhid usb_storage hid thunder_bgx ahci 
thunder_xcv i2c_thunderx mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd aes_arm64
[  602.872414] Process cc1 (pid: 40126, stack limit = 0x90887c2f)
[  602.878949] CPU: 10 PID: 40126 Comm: cc1 Not tainted 5.0.0-37-generic 
#40~18.04.1-Ubuntu
[  602.887040] Hardware name: GIGABYTE R120-T33/MT30-GS1, BIOS T49 02/02/2018
[  602.893921] pstate: 8005 (Nzcv daif -PAN -UAO)
[  602.898724] pc : __arch_copy_to_user+0x13c/0x248
[  602.903353] lr : cp_new_stat+0x140/0x178
[  602.907277] sp : 2599bcc0
[  602.910594] x29: 2599bcc0 x28: 800ed0538ec0 
[  602.915912] x27:  x26:  
[  602.921229] x25: 5600 x24: 0015 
[  602.926547] x23: 10c716d8 x22: 2599bd08 
[  602.931865] x21: 800ed0538ec0 x20: 1170c000 
[  602.937181] x19: 2599bdb0 x18:  
[  602.942498] x17:  x16:  
[  602.947818] x15:  x14:  
[  602.953134] x13:  x12:  
[  602.958452] x11:  x10: 152f 
[  602.963769] x9 : 1000 x8 : 000181a4 
[  602.969087] x7 : 00a60da3 x6 : 2599bd20 
[  602.974405] x5 : 2599bd88 x4 : 0008 
[  602.979721] x3 : 0802 x2 : fff8 
[  602.985038] x1 : 2599bd10 x0 : 2599bd08 
[  602.990356] Call trace:
[  602.992821]  __arch_copy_to_user+0x13c/0x248
[  602.997107]  __se_sys_newfstat+0x58/0x88
[  603.001045]  __arm64_sys_newfstat+0x20/0x30
[  603.005243]  el0_svc_common+0x88/0x180
[  603.009005]  el0_svc_handler+0x38/0x78
[  603.012770]  el0_svc+0x8/0xc
[  603.015664] Code: a8c12027 a88120c7 d503201f d503201f (a8c12829) 
[  603.021765] ---[ end trace 08068f2978fb8211 ]---

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

Title:
  [thunderx] Synchronous External Abort: synchronous parity or ECC error

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Triaged
Status in linux source package in Eoan:
  Triaged
Status in linux source package in Focal:
  Triaged

Bug description:
  [Impact]
  Under load, ThunderX systems eventually fail with:

  [  282.360376] Synchronous External Abort: synchronous parity or ECC error 
(0x9618) at 0xa6eb7000
  [  282.372351] Internal error: : 9618 [#1] SMP
  [  282.379152] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
shpchp cavium_rng_vf cavium_rng gpio_keys uio_pdrv_genirq uio ipmi_ssif 
ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf 
nicpf uas usb_storage ast i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt aes_ce_blk fb_sys_fops aes_ce_cipher drm crc32_ce 
crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce ahci libahci thunder_bgx 
thunder_xcv i2c_thunderx mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd aes_arm64
  [  282.467284] Process cc1 (pid: 39700, stack limit = 0xe0c44146)
  [  282.477172] CPU: 25 PID: 39700 Comm: cc1 Not tainted 4.15.0-75-generic 
#85+lp1857074.1
  [  282.488379] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [  282.500121] pstate: 8005 (Nzcv daif -PAN -UAO)
  [  282.508297] pc : __arch_copy_to_user+0x13c/0x248
  [  282.516430] lr : cp_new_stat+0x140/0x178
  [  282.523768] sp : 2e4d3d40
  [  282.530369] x29: 2e4d3d40 x28: 801f51fa2d00 
  [  282.538988] x27: 08b52000 x26: 0050 
  [  282.548031] x25: 0124 x24: 0015 
  [  282.556872] x23:  x22: 2e4d3d88 
  [  282.565449] x21: 

[Kernel-packages] [Bug 1857073] Re: Cavium ThunderX CN88XX Oops at smi_send.isra.4+0x80/0x158 [ipmi_msghandler]

[dann frazier]

** Summary changed:

- Cavium ThunderX CN88XX Crashes : Internal error Ooops(Possibly IPMI related)
+ Cavium ThunderX CN88XX Oops at smi_send.isra.4+0x80/0x158 [ipmi_msghandler]

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

Title:
  Cavium ThunderX CN88XX Oops at smi_send.isra.4+0x80/0x158
  [ipmi_msghandler]

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

Bug description:
  Series: Bionic 
  Kernel: 4.15.0-74.84  linux-generic

  The following crash was observed while testing the proposed kernel for the 
2019.12.02 SRU Cycle. 
  This kernel was built to include fixes for the following bugs:

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
  (LP: #1853326)
  - Revert "arm64: Use firmware to detect CPUs that are not affected by
Spectre-v2"
  - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
  Kunpeng920 (LP: #1852723)
  - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to
correct place
  The following crash appears to be a NEW bug. not related to the prior bugs 
listed above.

  system hostname: wright

  Possible Cause: wright's crash possibly is caused by faulty error
  handling in the ipmi driver (notice this in its dmesg: [ 52.150201]
  ipmi_ssif 0-0012: Unable to get the device id: -5)

  [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
  [  OK  ] FounBYZ-011FA0 efi.
   Mounting /boot/[  OK  ] Mounted /boot/efi.
  [  OK  ] Reached target Local File Systems.
   Starting Set console font and keymap...
   Starting Create Volatile Files and Directories...
   Starting ebtables ruleset management...
   Starting AppArmor initialization...
   Starting Tell Plymouth To Write Out Runtime Data...
  [  OK  nsole font and keymap.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [  OK  ] Started Create Volatile Files and Directories.
   Starting Network Time Synchronization...
   Starting Update UTMP about Syst
  [  OK  ] Started Update UTMP utdown.
  [  OK  ] Started ebtables ruleset management.
  [  OK  ] Starnization.
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Started AppArmor initialization.
  [   50.689136] cloud-init[1246]: Cloud-init v. 
19.3-41-gc4735dd3-0ubuntu1~18.04.1 running 'init-local' at Thu, 19 Dec 20 50.28 
seconds.
  [   50.712486] cloud-init[1246]: 2019-12-19 22:40:37,893 - 
handlers.py[WARNING]: failed posting event: start: init-local/check-cache: 
attempting to read from cache [trust]
  [   50.736307] cloud-init[1246]: 2019-12-19 22:40:37,941 - 
handlers.py[WARNING]: failed posting event: finish: init-local/check-cache: 
SUCCESS: restored from cache: DataSourceMAAS 
[http://10.229.32.21:5248/MAAS/metadata/]
  [   51.244224] cloud-init[1246]: 2019-12-19 22:40:38,450 - 
handlers.py[WARNING]: failed posting event: finish: init-local: SUCCESS: 
searching for local datasources
  [  OK  ] Started Initial cloud-init job (pre-networking).
  [  OK  ] Reached target Network (Pre).
   Starting Network Service...
  [  OK  ] Started Network Service.
   Starting Wait for Network to be Configured...
   Starting Network Name Resolution...
  [   52.150201] ipmi_ssif 0-0012: Unable to get the device id: -5
  [   52.300309] Unable to handle kernel read fromvirtual address 0018
  [   52.311284] Mem abort info:
  [   52.316895]  604
  [   52.322622]   Exception class = DABT (current EL), IL = 32 bits
  [   52.331061]   SET = 0, FnV = 0
  [   52.336639]   EA = 0, S1PTW = 0
  [   52.342311] Data abort info:
  [   52.347731]   ISV = 0, ISS = 0x0004
  [   52.354131]   CM = 0, WnR = 0
  [   52.359739] user pgtable: 4k pages, 48-bit VAs, pgd = 44052f71
  [   52.368909] [0018] *pgd=
  [   52.376522] Internal error: Oops: 9604 [#1] SMP
  [   52.384039] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq uio ipmi_ssif(+) 
ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf 
nicpf ast i2c_algo_bit aes_ce_blk ttm aes_ce_cipher crc32_ce drm_kms_helper 
crct10dif_ce ghash_ce syscopyarea sha2_ce sysfillrect sysimgblt sha256_arm64 
fb_sys_fops thunder_bgx sha1_ce drm ahci libahci thunder_xcv i2c_thunderx 
mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd 
cryptd aes_arm64
  [   52.473094] Process kworker/87:1 (pid: 674, stack limit = 
0x4907a88f)
  [   

[Kernel-packages] [Bug 1859387] Re: intel/sof: update the intel sof firmware to v1.3-0f73628 for cml and cnl

[Launchpad Bug Tracker]

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

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

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

Title:
  intel/sof: update the intel sof firmware to v1.3-0f73628 for cml and
  cnl

Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Intel released a new version sof firmware to Canonical, they suggested
  that we should integrate the version v1.3-0f73628 and we should only
  pick the cml and cnl firmwares since other firmwares are not fully
  tested. Since we have a couple of Lenovo and Dell cnl and cml machines
  which need to enable sof driver, we integrate the firmwares to
  ubuntu.

  [Fix]
   - fix the hang issue in the firmware for the cml and cnl
   - introduce the ldc file which helps to do the firmware debug
   - divide the firmware to cml and cnl specific ones

  
  [Test Case]
  These firmwares are already widely used in oem project, the audio
  functions worked very well under both Lenovo and Dell dmic machines.

  [Regression Risk]
  Low, Intel released these firmware to us, and we already did large
  numbers audio test in the oem project.

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

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

[Kernel-packages] [Bug 1857074] Re: Cavium ThunderX CN88XX crashes on boot

[dann frazier]

** Summary changed:

- Cavium ThunderX CN88XX Panic : Unknown reason
+ Cavium ThunderX CN88XX crashes on boot

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

Title:
  Cavium ThunderX CN88XX crashes on boot

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

Bug description:
  Series: Bionic
  Kernel: 4.15.0-74.84 linux-generic
  Steps to reproduce:  Install 4.15.0-74.84 Kernel and boot the system.

  The following crash was observed while testing the proposed kernel for the 
2019.12.02 SRU Cycle.
  This kernel was built to include fixes for the following bugs:

    * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
  (LP: #1853326)
  - Revert "arm64: Use firmware to detect CPUs that are not affected by
    Spectre-v2"
  - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"

    * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
  Kunpeng920 (LP: #1852723)
  - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to
    correct place

  The following crash appears to be a NEW bug. not related to the prior bugs 
listed above.
  This bug DOES NOT APPEAR to be related to LP#1857073.

  This is another NEW BUG.

  Hostname: Starmie

  Probable Cause is unknown at this point and still under investigation.

  [  OK  ] Found device WDC_WD5003ABYZ-011FA0 efi.
   Mounting /boot/efi...
  [  OK  ] Mounted /boot/efi.
  [  OK  ] Reached target Local File Systems.
   Starting AppArmor initialization...
   Starting Tell Plymouth To Write Out Runtime Data...
   Starting ebtables ruleset management...
  [   20.942427] kernel BUG at 
/build/linux-pWET3k/linux-4.15.0/fs/buffer.c:1240!
  [   20.951416] Internal error: Oops - BUG: 0 [#1] SMP
  [   20.958153] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq ipmi_ssif uio 
ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf 
nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect aes_ce_blk 
sysimgblt fb_sys_fops aes_ce_cipher crc32_ce drm crct10dif_ce ghash_ce sha2_ce 
sha256_arm64 sha1_ce ahci thunder_bgx libahci thunder_xcv i2c_thunderx 
mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd 
cryptd aes_arm64
  [   21.044326] Process systemd (pid: 1, stack limit = 0x5af6f18b)
  [   21.053858] CPU: 1 PID: 1 Comm: systemd Not tainted 4.15.0-74-generic 
#84-Ubuntu
  [   21.063931] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [   21.074790] pstate: 20400085 (nzCv daIf +PAN -UAO)
  [   21.082096] pc : __find_get_block+0x2e8/0x398
  [   21.088917] lr : __getblk_gfp+0x3c/0x2a8
  [   21.095379] sp : 099ab7e0
  [   21.101062] x29: 099ab7e0 x28: 
  [   21.108699] x27:  x26: 
  [   21.116265] x25: 0001 x24: 
  [   21.123788] x23: 0008 x22: 801f26116c80
  [   21.131302] x21: 801f26116c80 x20: 245c
  [   21.138808] x19: 1000 x18: a59c3a70
  [   21.146300] x17:  x16: 
  [   21.153730] x15: 0020 x14: 0012
  [   21.161083] x13: 2f7374696e752f64 x12: 0101010101010101
  [   21.168397] x11: 7f7f7f7f7f7f7f7f x10: 0972d000
  [   21.175689] x9 :  x8 : 801f7ba7e3c0
  [   21.183042] x7 : 801f7ba7e3e0 x6 : 
  [   21.190667] x5 : 0004 x4 : 0020
  [   21.197955] x3 : 0008 x2 : 1000
  [   21.205680] x1 : 245c x0 : 0080
  [   21.212918] Call trace:
  [   21.217257]  __find_get_block+0x2e8/0x398
  [   21.223160]  __getblk_gfp+0x3c/0x2a8
  [   21.228644]  ext4_getblk+0xcc/0x1b0
  [   21.233991]  ext4_bread_batch+0x78/0x1c8
  [   21.239726]  ext4_find_entry+0x2d4/0x598
  [   21.245416]  ext4_lookup+0xac/0x278
  [   21.250612]  lookup_slow+0xac/0x190
  [   21.255736]  walk_component+0x228/0x340
  [   21.261151]  link_path_walk+0x2f4/0x568
  [   21.266499]  path_parentat+0x44/0x88
  [   21.271521]  filename_parentat+0xa0/0x170
  [   21.276924]  filename_create+0x60/0x168
  [   21.282082]  SyS_symlinkat+0x80/0x128
  [   21.287013]  el0_svc_naked+0x30/0x34
  [   21.291835] Code: 17e7 a90363b7 a9046bb9 f9002bbb (d421)
  [   21.299191] ---[ end trace b07cecc329f07f48 ]---
  [   21.347488] systemd: 35 output lines suppressed due to ratelimiting
  [   21.355094] Kernel panic - not syncing: Attempted to kill init! 

[Kernel-packages] [Bug 1859801] Re: bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 16. January 2020 16:51 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 16. January 2020 19:52 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 16. January 2020 19:52 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1859692] Re: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 16. January 2020 18:32 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building
+   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  replaces: bug 1858941
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 16. January 2020 18:32 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  replaces: bug 1858941
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

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

[Kernel-packages] [Bug 1859801] Re: bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 16. January 2020 16:51 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  variant: debs

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

Title:
  bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 16. January 2020 16:51 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  variant: debs

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

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

[Kernel-packages] [Bug 1859692] Re: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Packaging
- phase-changed: Wednesday, 15. January 2020 21:11 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 16. January 2020 18:32 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building
  replaces: bug 1858941
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1859694
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 16. January 2020 18:32 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building
  replaces: bug 1858941
  trackers:
bionic/linux-raspi2-5.3: bug 1859691
eoan/linux-raspi2/pi-kernel: bug 1859690
  variant: debs

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

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

[Kernel-packages] [Bug 1741860] Re: Use the kernel default for crashkernel offset

[Andrew Cloke]

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

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

Title:
  Use the kernel default for crashkernel offset

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released
Status in makedumpfile source package in Disco:
  Fix Released
Status in makedumpfile source package in Eoan:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * The value chosen for ppc64el of 128MB aligns with that of the
  kernel default. That may change some day, so it would be best to let
  the kernel decide what value it should use. If the value does change
  and the kernel is not allowed to choose a value, this may stop the
  kernel from booting on a production system.

  [Test Case]

   Run `cat /etc/default/grub.d/kdump-tools.cfg`

   * Expected result: there is no offset specified at the end of the
  line (.e.g, @128M).

   * Actual result: For Xenial, Bionic, Disco, and Eoan there are
  offsets specified.

  [Regression Potential]

   * Right now, the offset described in the kdump-tools.cfg aligns with
  that of what the kernel would select, so since they are the same we
  would expect no change in operation.

  
  Original bug description follows:
  -

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-08 
01:06:41 ==
  ---Problem Description---
  A default offset of 128MB is enforced for crashkernel by kdump-tools utility
  overriding the kernel default.

  While the kernel default offset for crashkernel is also 128MB, that may change
  and the right thing to do would be to let the kernel decide on the offset of
  crashkernel in the default scenario..

  Get rid of "@128M" in kdump-tools.cfg file

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

  ---uname output---
  na

  Machine Type = na

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

  ---Steps to Reproduce---
   # cat /etc/default/grub.d/kdump-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M"
  ---

  The offset is specified via kdump-tools where as the kernel may be the right 
place to
  set an offset by default..

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - MAMATHA INAMDAR  - 2018-01-08 03:05:05 
==
  This bug is opened to follow-up other bug based on the comment 19
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical 
Launchpad1676884 )

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

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

[Kernel-packages] [Bug 1858941] Re: eoan/linux-raspi2: 5.3.0-1016.18 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1858943
+ kernel-stable-master-bug: '1859694'
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Friday, 10. January 2020 14:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1858940
eoan/linux-raspi2/pi-kernel: bug 1858939
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1016.18 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: '1859694'
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Friday, 10. January 2020 14:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1858940
eoan/linux-raspi2/pi-kernel: bug 1858939
  variant: debs

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

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

[Kernel-packages] [Bug 1839758] Re: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.

[Oleh Dmytrychenko]

Not reproducible anymore with all the latest updates applied. Future
regression testing isn't possible either due to hardware change. It's
fair to close this.

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

Title:
  [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE
  kernel 5.0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since kernel 5.0 rolled out through HWE last week my system is
  consistently locking up upon launch of Steam or 3D applications in
  WINE.

  Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/

  Worked around by using pre-update 4.18 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 15:47:27 2019
  DistUpgraded: 2018-03-26 22:50:10,989 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed
   virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  InstallationDate: Installed on 2018-03-26 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago)
  dmi.bios.date: 01/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F25
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming K7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se3
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming K7
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Kernel-packages] [Bug 1741860] Re: Use the kernel default for crashkernel offset

[bugproxy]

--- Comment From hbath...@in.ibm.com 2020-01-16 13:15 EDT---
With kdump-tools version 1:1.6.3-2~16.04.2 on Xenial,
crashkernel parameter offset is dropped (in
/etc/default/grub.d/kdump-tools.cfg file) making sure
the default offset enforced by the kernel is used.

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

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

Title:
  Use the kernel default for crashkernel offset

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released
Status in makedumpfile source package in Disco:
  Fix Released
Status in makedumpfile source package in Eoan:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * The value chosen for ppc64el of 128MB aligns with that of the
  kernel default. That may change some day, so it would be best to let
  the kernel decide what value it should use. If the value does change
  and the kernel is not allowed to choose a value, this may stop the
  kernel from booting on a production system.

  [Test Case]

   Run `cat /etc/default/grub.d/kdump-tools.cfg`

   * Expected result: there is no offset specified at the end of the
  line (.e.g, @128M).

   * Actual result: For Xenial, Bionic, Disco, and Eoan there are
  offsets specified.

  [Regression Potential]

   * Right now, the offset described in the kdump-tools.cfg aligns with
  that of what the kernel would select, so since they are the same we
  would expect no change in operation.

  
  Original bug description follows:
  -

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-08 
01:06:41 ==
  ---Problem Description---
  A default offset of 128MB is enforced for crashkernel by kdump-tools utility
  overriding the kernel default.

  While the kernel default offset for crashkernel is also 128MB, that may change
  and the right thing to do would be to let the kernel decide on the offset of
  crashkernel in the default scenario..

  Get rid of "@128M" in kdump-tools.cfg file

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

  ---uname output---
  na

  Machine Type = na

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

  ---Steps to Reproduce---
   # cat /etc/default/grub.d/kdump-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M"
  ---

  The offset is specified via kdump-tools where as the kernel may be the right 
place to
  set an offset by default..

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - MAMATHA INAMDAR  - 2018-01-08 03:05:05 
==
  This bug is opened to follow-up other bug based on the comment 19
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical 
Launchpad1676884 )

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

-- 
Mailing list: https://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 1799497] Re: 4.15 kernel hard lockup about once a week

[Luis Rodriguez]

It sounds like what I was getting.


On Thu, Jan 16, 2020 at 11:05 PM Colin Ian King <1799...@bugs.launchpad.net>
wrote:

> After quite a bit of experimentation I found that I can reproduce the bug
> if I have zram *and* also swap on the filesystem enabled while exercising
> the brk stressors and aiol (to cause lots of I/O). Eventually the system
> grinds to a halt, we lose interactivity and we eventually get lockups as
> follows:
> [ 2012.040006] watchdog: BUG: soft lockup - CPU#2 stuck for 22s!
> [stress-ng-brk:1632]
> [ 2012.040922] Modules linked in: zram(E) kvm_intel(E) kvm(E) irqbypass(E)
> crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) pcbc(E)
> aesni_intel(E) aes_x86_64(E) crypto_simd(E) glue_helper(E) cryptd(E)
> psmouse(E) input_leds(E) floppy(E) virtio_scsi(E) serio_raw(E) i2c_piix4(E)
> mac_hid(E) pata_acpi(E) qemu_fw_cfg(E) 9pnet_virtio(E) 9p(E) 9pnet(E)
> fscache(E)
> [ 2012.044655] CPU: 2 PID: 1632 Comm: stress-ng-brk Tainted: G
> EL   4.15.18 #1
> [ 2012.045581] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
> 1.13.0-1 04/01/2014
> [ 2012.046555] RIP:
> 0010:__raw_callee_save___pv_queued_spin_unlock+0x10/0x17
> [ 2012.047340] RSP: 0018:b73382083718 EFLAGS: 0246 ORIG_RAX:
> ff11
> [ 2012.048238] RAX: 0001 RBX:  RCX:
> 0002
> [ 2012.049078] RDX:  RSI: 9d327c2f6918 RDI:
> a3269978
> [ 2012.049909] RBP: b73382083720 R08: 9d327c2f6918 R09:
> 9d327c0a5328
> [ 2012.050746] R10: 9d327c1e2310 R11: 9d327c1e2328 R12:
> 9d327c2f6800
> [ 2012.051574] R13: 9d327c1e2328 R14: 9d327c1e2310 R15:
> 9d327c1e2200
> [ 2012.052436] FS:  7f89f2ccd740() GS:9d327f28()
> knlGS:
> [ 2012.053382] CS:  0010 DS:  ES:  CR0: 80050033
> [ 2012.054058] CR2: 7f1350a8dd90 CR3: 311a4004 CR4:
> 00160ee0
> [ 2012.054889] Call Trace:
> [ 2012.055192]  get_swap_pages+0x193/0x360
> [ 2012.055652]  get_swap_page+0x13f/0x1e0
> [ 2012.056123]  add_to_swap+0x14/0x70
> [ 2012.056530]  shrink_page_list+0x81d/0xbc0
> [ 2012.057013]  shrink_inactive_list+0x242/0x590
> [ 2012.057523]  shrink_node_memcg+0x364/0x770
> [ 2012.058012]  shrink_node+0xf7/0x300
> [ 2012.058432]  ? shrink_node+0xf7/0x300
> [ 2012.058863]  do_try_to_free_pages+0xc9/0x330
> [ 2012.059368]  try_to_free_pages+0xee/0x1b0
> [ 2012.059842]  __alloc_pages_slowpath+0x3fc/0xe00
> [ 2012.060424]  __alloc_pages_nodemask+0x29a/0x2c0
> [ 2012.060963]  alloc_pages_vma+0x88/0x1f0
> [ 2012.061414]  __handle_mm_fault+0x8b7/0x12e0
> [ 2012.061909]  handle_mm_fault+0xb1/0x210
> [ 2012.062375]  __do_page_fault+0x281/0x4b0
> [ 2012.062848]  do_page_fault+0x2e/0xe0
> [ 2012.063274]  ? async_page_fault+0x2f/0x50
> [ 2012.063751]  do_async_page_fault+0x51/0x80
> [ 2012.064262]  async_page_fault+0x45/0x50
> [ 2012.064719] RIP: 0033:0x55ec1997bd0a
> [ 2012.065147] RSP: 002b:7ffeacd21600 EFLAGS: 00010246
> [ 2012.065754] RAX: 55ec28601000 RBX: 0005 RCX:
> 7f89f2de956b
> [ 2012.066580] RDX: 55ec28601000 RSI: 7ffeacd216d0 RDI:
> 55ec28602000
> [ 2012.067410] RBP: 7ffeacd216c0 R08:  R09:
> 7f89f3d0c2f0
> [ 2012.068290] R10:  R11: 0246 R12:
> 
> [ 2012.069129] R13: 0002 R14: 0001 R15:
> 7ffeacd216d0
> [ 2012.069965] Code: 50 41 51 41 52 41 53 e8 3b 05 00 00 41 5b 41 5a 41 59
> 41 58 5f 5e 5a 59 5d c3 90 55 48 89 e5 52 b8 01 00 00 00 31 d2 f0 0f b0 17
> <3c> 01 75 03 5a 5d c3 56 0f b6 f0 e8 bc ff ff ff 5e 5a 5d c3 0f
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1799497
>
> Title:
>   4.15 kernel hard lockup about once a week
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in zram-config package in Ubuntu:
>   Incomplete
> Status in linux source package in Bionic:
>   Confirmed
> Status in zram-config source package in Bionic:
>   Confirmed
>
> Bug description:
>   My main server has been running into hard lockups about once a week
>   ever since I switched to the 4.15 Ubuntu 18.04 kernel.
>
>   When this happens, nothing is printed to the console, it's effectively
>   stuck showing a login prompt. The system is running with panic=1 on
>   the cmdline but isn't rebooting so the kernel isn't even processing
>   this as a kernel panic.
>
>
>   As this felt like a potential hardware issue, I had my hosting provider
> give me a completely different system, different motherboard, different
> CPU, different RAM and different storage, I installed that system on 18.04
> and moved my data over, a week later, I hit the issue again.
>
>   We've since also had a LXD user reporting similar symptoms here also on
> varying hardware:
> https://github.com/lxc/lxd/issues/5197
>
>
>   My system doesn't have a lot of memory pressure with about 50% of free
> memory:
>
>   

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Frank Heimes]

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

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  [Impact]
  After a DLPAR memory/CPU add/remove operation, kdump tools need to be 
restarted or else kdump tools will fail to capture the crash. 

  [Test]

  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system

  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie
  Mitsuyoshi/carri...@us.ibm.com

  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

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

  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

  [Regression Potential]
  The fix applies to makedumpfile, and could impact dump capture.

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

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

[Kernel-packages] [Bug 1860014] [NEW] Disco update: upstream stable patchset 2020-01-16

[Kamal Mostafa]

Public bug reported:

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:

   upstream stable patchset 2020-01-16

Ported from the following upstream stable releases:
v4.19.92, v5.4.7

   from git://git.kernel.org/

af_packet: set defaule value for tmo
fjes: fix missed check in fjes_acpi_add
mod_devicetable: fix PHY module format
net: dst: Force 4-byte alignment of dst_metrics
net: gemini: Fix memory leak in gmac_setup_txqs
net: hisilicon: Fix a BUG trigered by wrong bytes_compl
net: nfc: nci: fix a possible sleep-in-atomic-context bug in 
nci_uart_tty_receive()
net: qlogic: Fix error paths in ql_alloc_large_buffers()
net: usb: lan78xx: Fix suspend/resume PHY register access error
qede: Disable hardware gro when xdp prog is installed
qede: Fix multicast mac configuration
sctp: fully initialize v4 addr in some functions
selftests: forwarding: Delete IPv6 address at the end
btrfs: don't double lock the subvol_sem for rename exchange
btrfs: do not call synchronize_srcu() in inode_tree_del
Btrfs: fix missing data checksums after replaying a log tree
btrfs: send: remove WARN_ON for readonly mount
btrfs: abort transaction after failed inode updates in create_subvol
btrfs: skip log replay on orphaned roots
btrfs: do not leak reloc root if we fail to read the fs root
btrfs: handle ENOENT in btrfs_uuid_tree_iterate
Btrfs: fix removal logic of the tree mod log that leads to use-after-free issues
ALSA: pcm: Avoid possible info leaks from PCM stream buffers
ALSA: hda/ca0132 - Keep power on during processing DSP response
ALSA: hda/ca0132 - Avoid endless loop
ALSA: hda/ca0132 - Fix work handling in delayed HP detection
drm: mst: Fix query_payload ack reply struct
drm/panel: Add missing drm_panel_init() in panel drivers
drm/bridge: analogix-anx78xx: silence -EPROBE_DEFER warnings
iio: light: bh1750: Resolve compiler warning and make code more readable
drm/amdgpu: grab the id mgr lock while accessing passid_mapping
spi: Add call to spi_slave_abort() function when spidev driver is released
staging: rtl8192u: fix multiple memory leaks on error path
staging: rtl8188eu: fix possible null dereference
rtlwifi: prevent memory leak in rtl_usb_probe
libertas: fix a potential NULL pointer dereference
ath10k: fix backtrace on coredump
IB/iser: bound protection_sg size by data_sg size
media: am437x-vpfe: Setting STD to current value is not an error
media: i2c: ov2659: fix s_stream return value
media: ov6650: Fix crop rectangle alignment not passed back
media: i2c: ov2659: Fix missing 720p register config
media: ov6650: Fix stored frame format not in sync with hardware
media: ov6650: Fix stored crop rectangle not in sync with hardware
tools/power/cpupower: Fix initializer override in hsw_ext_cstates
media: venus: core: Fix msm8996 frequency table
ath10k: fix offchannel tx failure when no ath10k_mac_tx_frm_has_freq
pinctrl: devicetree: Avoid taking direct reference to device name string
drm/amdkfd: fix a potential NULL pointer dereference (v2)
selftests/bpf: Correct path to include msg + path
media: venus: Fix occasionally failures to suspend
usb: renesas_usbhs: add suspend event support in gadget mode
hwrng: omap3-rom - Call clk_disable_unprepare() on exit only if not idled
regulator: max8907: Fix the usage of uninitialized variable in 
max8907_regulator_probe()
media: flexcop-usb: fix NULL-ptr deref in flexcop_usb_transfer_init()
media: cec-funcs.h: add status_req checks
drm/bridge: dw-hdmi: Refuse DDC/CI transfers on the internal I2C controller
samples: pktgen: fix proc_cmd command result check logic
block: Fix writeback throttling W=1 compiler warnings
mwifiex: pcie: Fix memory leak in mwifiex_pcie_init_evt_ring
drm/drm_vblank: Change EINVAL by the correct errno
media: cx88: Fix some error handling path in 'cx8800_initdev()'
media: ti-vpe: vpe: Fix Motion Vector vpdma stride
media: ti-vpe: vpe: fix a v4l2-compliance warning about invalid pixel format
media: ti-vpe: vpe: fix a v4l2-compliance failure about frame sequence number
media: ti-vpe: vpe: Make sure YUYV is set as default format
media: ti-vpe: vpe: fix a v4l2-compliance failure causing a kernel panic
media: ti-vpe: vpe: ensure buffers are cleaned up properly in abort cases
media: ti-vpe: vpe: fix a v4l2-compliance failure about invalid sizeimage
syscalls/x86: Use the correct function type in SYSCALL_DEFINE0
drm/amd/display: Fix dongle_caps containing stale information.
extcon: sm5502: Reset registers during initialization
x86/mm: Use the correct function type for native_set_fixmap()
ath10k: Correct error handling of dma_map_single()

[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week

[Colin Ian King]

After quite a bit of experimentation I found that I can reproduce the bug if I 
have zram *and* also swap on the filesystem enabled while exercising the brk 
stressors and aiol (to cause lots of I/O). Eventually the system grinds to a 
halt, we lose interactivity and we eventually get lockups as follows:
[ 2012.040006] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! 
[stress-ng-brk:1632]
[ 2012.040922] Modules linked in: zram(E) kvm_intel(E) kvm(E) irqbypass(E) 
crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) pcbc(E) 
aesni_intel(E) aes_x86_64(E) crypto_simd(E) glue_helper(E) cryptd(E) psmouse(E) 
input_leds(E) floppy(E) virtio_scsi(E) serio_raw(E) i2c_piix4(E) mac_hid(E) 
pata_acpi(E) qemu_fw_cfg(E) 9pnet_virtio(E) 9p(E) 9pnet(E) fscache(E)
[ 2012.044655] CPU: 2 PID: 1632 Comm: stress-ng-brk Tainted: GEL   
4.15.18 #1
[ 2012.045581] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1 04/01/2014
[ 2012.046555] RIP: 0010:__raw_callee_save___pv_queued_spin_unlock+0x10/0x17
[ 2012.047340] RSP: 0018:b73382083718 EFLAGS: 0246 ORIG_RAX: 
ff11
[ 2012.048238] RAX: 0001 RBX:  RCX: 0002
[ 2012.049078] RDX:  RSI: 9d327c2f6918 RDI: a3269978
[ 2012.049909] RBP: b73382083720 R08: 9d327c2f6918 R09: 9d327c0a5328
[ 2012.050746] R10: 9d327c1e2310 R11: 9d327c1e2328 R12: 9d327c2f6800
[ 2012.051574] R13: 9d327c1e2328 R14: 9d327c1e2310 R15: 9d327c1e2200
[ 2012.052436] FS:  7f89f2ccd740() GS:9d327f28() 
knlGS:
[ 2012.053382] CS:  0010 DS:  ES:  CR0: 80050033
[ 2012.054058] CR2: 7f1350a8dd90 CR3: 311a4004 CR4: 00160ee0
[ 2012.054889] Call Trace:
[ 2012.055192]  get_swap_pages+0x193/0x360
[ 2012.055652]  get_swap_page+0x13f/0x1e0
[ 2012.056123]  add_to_swap+0x14/0x70
[ 2012.056530]  shrink_page_list+0x81d/0xbc0
[ 2012.057013]  shrink_inactive_list+0x242/0x590
[ 2012.057523]  shrink_node_memcg+0x364/0x770
[ 2012.058012]  shrink_node+0xf7/0x300
[ 2012.058432]  ? shrink_node+0xf7/0x300
[ 2012.058863]  do_try_to_free_pages+0xc9/0x330
[ 2012.059368]  try_to_free_pages+0xee/0x1b0
[ 2012.059842]  __alloc_pages_slowpath+0x3fc/0xe00
[ 2012.060424]  __alloc_pages_nodemask+0x29a/0x2c0
[ 2012.060963]  alloc_pages_vma+0x88/0x1f0
[ 2012.061414]  __handle_mm_fault+0x8b7/0x12e0
[ 2012.061909]  handle_mm_fault+0xb1/0x210
[ 2012.062375]  __do_page_fault+0x281/0x4b0
[ 2012.062848]  do_page_fault+0x2e/0xe0
[ 2012.063274]  ? async_page_fault+0x2f/0x50
[ 2012.063751]  do_async_page_fault+0x51/0x80
[ 2012.064262]  async_page_fault+0x45/0x50
[ 2012.064719] RIP: 0033:0x55ec1997bd0a
[ 2012.065147] RSP: 002b:7ffeacd21600 EFLAGS: 00010246
[ 2012.065754] RAX: 55ec28601000 RBX: 0005 RCX: 7f89f2de956b
[ 2012.066580] RDX: 55ec28601000 RSI: 7ffeacd216d0 RDI: 55ec28602000
[ 2012.067410] RBP: 7ffeacd216c0 R08:  R09: 7f89f3d0c2f0
[ 2012.068290] R10:  R11: 0246 R12: 
[ 2012.069129] R13: 0002 R14: 0001 R15: 7ffeacd216d0
[ 2012.069965] Code: 50 41 51 41 52 41 53 e8 3b 05 00 00 41 5b 41 5a 41 59 41 
58 5f 5e 5a 59 5d c3 90 55 48 89 e5 52 b8 01 00 00 00 31 d2 f0 0f b0 17 <3c> 01 
75 03 5a 5d c3 56 0f b6 f0 e8 bc ff ff ff 5e 5a 5d c3 0f

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

Title:
  4.15 kernel hard lockup about once a week

Status in linux package in Ubuntu:
  Incomplete
Status in zram-config package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed
Status in zram-config source package in Bionic:
  Confirmed

Bug description:
  My main server has been running into hard lockups about once a week
  ever since I switched to the 4.15 Ubuntu 18.04 kernel.

  When this happens, nothing is printed to the console, it's effectively
  stuck showing a login prompt. The system is running with panic=1 on
  the cmdline but isn't rebooting so the kernel isn't even processing
  this as a kernel panic.

  
  As this felt like a potential hardware issue, I had my hosting provider give 
me a completely different system, different motherboard, different CPU, 
different RAM and different storage, I installed that system on 18.04 and moved 
my data over, a week later, I hit the issue again.

  We've since also had a LXD user reporting similar symptoms here also on 
varying hardware:
https://github.com/lxc/lxd/issues/5197

  
  My system doesn't have a lot of memory pressure with about 50% of free memory:

  root@vorash:~# free -m
totalusedfree  shared  buff/cache   
available
  Mem:  31819   17574 402 513   13842   
13292
  Swap: 159092687   13222

  I will now try to increase 

[Kernel-packages] [Bug 1859724] Re: disco/linux: 5.0.0-40.44 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 16. January 2020 04:03 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
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oem-osp1: bug 1859722
disco/linux-aws: bug 1858531
+   disco/linux-azure: bug 1858534
disco/linux-gcp: bug 1858539
+   disco/linux-kvm: bug 1858541
disco/linux-oracle: bug 1858543
+   disco/linux-raspi2: bug 1858529
disco/linux-snapdragon: bug 1858544
  variant: debs

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

Title:
  disco/linux: 5.0.0-40.44 -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-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 16. January 2020 04:03 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
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oem-osp1: bug 1859722
disco/linux-aws: bug 1858531
disco/linux-azure: bug 1858534
disco/linux-gcp: bug 1858539
disco/linux-kvm: bug 1858541
disco/linux-oracle: bug 1858543
disco/linux-raspi2: bug 1858529
disco/linux-snapdragon: bug 1858544
  variant: debs

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

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

[Kernel-packages] [Bug 1859971] PulseList.txt

[CiberWeb]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1859971/+attachment/5320913/+files/PulseList.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/1859971

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[CiberWeb]

apport information

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

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1859971] Re: Asus ZenBook 14 UX431fl the speakers do not work but the headphones work

[CiberWeb]

Executed the command.

I have already solved it ... I have installed alsa-tools-gui and I have
been able to analyze the problem better. Apparently for some reason
after the installation leaves the speakers deactivated, using this tool
I have been able to see this problem and I have activated ... I don't
know very well what it does since it does not touch the alsa conf but I
can already hear the speakers internal The headphones still work as
before.

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[CiberWeb]

apport information

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

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[CiberWeb]

apport information

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

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[CiberWeb]

apport information

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

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[CiberWeb]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1859971/+attachment/5320908/+files/ProcCpuinfo.txt

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1859971] RfKill.txt

[CiberWeb]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1859971/+attachment/5320914/+files/RfKill.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/1859971

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[CiberWeb]

apport information

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

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[CiberWeb]

apport information

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

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1859799] Re: xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1859704
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
- phase: Ready for Packaging
- phase-changed: Wednesday, 15. January 2020 12:49 UTC
+ phase: Packaging
+ phase-changed: Thursday, 16. January 2020 17:22 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

Title:
  xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1859704
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Packaging
  phase-changed: Thursday, 16. January 2020 17:22 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

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

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

[CiberWeb]

apport information

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

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[CiberWeb]

apport information

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

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[CiberWeb]

apport information

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

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[CiberWeb]

apport information

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

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

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FLC_UX431FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1859971] Re: Asus ZenBook 14 UX431fl the speakers do not work but the headphones work

[CiberWeb]

apport information

** Tags added: apport-collected eoan

** Description changed:

  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.
  
  I have installed ubuntu 19.10 and everything is correct but the speakers
  do not work. The headphones works perfect.
  
  I have tried all kinds of solutions with alsa conf but fruitless
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  alfonso2297 F pulseaudio
+  /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2020-01-15 (1 days ago)
+ InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
+  Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-26-generic N/A
+  linux-backports-modules-5.3.0-26-generic  N/A
+  linux-firmware1.183.3
+ Tags:  eoan
+ Uname: Linux 5.3.0-26-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/09/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX431FLC.203
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX431FLC
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: No  Asset  Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FLC.203:bd10/09/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FLC_UX431FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: ZenBook
+ dmi.product.name: ZenBook UX431FLC_UX431FL
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1859971/+attachment/5320903/+files/AlsaInfo.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/1859971

Title:
   Asus ZenBook 14 UX431fl the speakers do not work but the headphones
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I bought a:
  Asus ZenBook 14 UX431fl
  Standard comes with windows and the speakers work.

  I have installed ubuntu 19.10 and everything is correct but the
  speakers do not work. The headphones works perfect.

  I have tried all kinds of solutions with alsa conf but fruitless
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfonso2297 F pulseaudio
   /dev/snd/pcmC0D0p:   alfonso2297 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (1 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FLC_UX431FL
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FLC.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  

[Kernel-packages] [Bug 1859718] Re: xenial/linux: 4.4.0-173.203 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 16. January 2020 04:02 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
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-lts-xenial: bug 1859717
+   trusty/linux-lts-xenial: bug 1859717, bug 1858592
xenial/linux-fips: bug 1858589
xenial/linux-raspi2: bug 1858586
xenial/linux-snapdragon: bug 1858588
xenial/linux/caracalla-kernel: bug 1859714
xenial/linux/pc-kernel: bug 1859715
xenial/linux/stlouis-kernel: bug 1859716
  variant: debs

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

Title:
  xenial/linux: 4.4.0-173.203 -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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 16. January 2020 04:02 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
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-lts-xenial: bug 1859717, bug 1858592
xenial/linux-fips: bug 1858589
xenial/linux-raspi2: bug 1858586
xenial/linux-snapdragon: bug 1858588
xenial/linux/caracalla-kernel: bug 1859714
xenial/linux/pc-kernel: bug 1859715
xenial/linux/stlouis-kernel: bug 1859716
  variant: debs

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

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

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[bugproxy]

--- Comment From hbath...@in.ibm.com 2020-01-16 11:01 EDT---
Issue resolved on xenial with kdump-tools version
1:1.6.3-2~16.04.2

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

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  [Impact]
  After a DLPAR memory/CPU add/remove operation, kdump tools need to be 
restarted or else kdump tools will fail to capture the crash. 

  [Test]

  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system

  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie
  Mitsuyoshi/carri...@us.ibm.com

  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

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

  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

  [Regression Potential]
  The fix applies to makedumpfile, and could impact dump capture.

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

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

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

[bugproxy]

--- Comment From hbath...@in.ibm.com 2020-01-16 11:02 EDT---
(In reply to comment #78)
> Hello Hari,
>
> Glad to see you around on bugs again. :)

Thanks, Mauricio :)

> Could you please confirm whether the fix for this bug also addresses LP bug
> 1655280?
> (i.e., the verification for xenial would be equivalent/also validate that
> other bug.)

Yes, it does. Updated that bug..

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

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Won't Fix
Status in makedumpfile source package in Eoan:
  Fix Committed
Status in makedumpfile source package in Focal:
  Fix Released

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

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

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

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

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

[Kernel-packages] [Bug 1859799] Re: xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker

[Manoj Iyer]

** Summary changed:

- xenial/linux-deeplens:  -proposed tracker
+ xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer 
(manjo)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer 
(manjo)

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

Title:
  xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1859704
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Packaging
  phase-changed: Thursday, 16. January 2020 17:22 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

-- 
Mailing list: https://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 1857074] Re: Cavium ThunderX CN88XX Panic : Unknown reason

[dann frazier]

On Wed, Jan 15, 2020 at 11:28 PM Juerg Haefliger
 wrote:
>
> On Thu, 16 Jan 2020 02:14:16 -
> dann frazier  wrote:
>
> > I built a kernel with the proposed patches[*] and ran a reboot/kernel
> > compile test on 4 systems. The tests survived 46 total iterations
> > (~12/system) before I interrupted. Two systems failed with "Synchronous
> > External Abort: synchronous parity or ECC error" errors.
> >
> > I've reverted the systems back to 4.15.0-70 - the kernel before the
> > cpufeature/errata patches that caused this - to see if these SEA errors
> > are a regression.
> >
> > [*] https://lists.ubuntu.com/archives/kernel-
> > team/2020-January/106909.html
> >
>
> I've ran 75 iterations of reboot/compile-kernel and encountered 3 gcc
> segmentation faults. Unfortunately, my test didn't capture the dmesg log but
> it's likely that these are due to the ECC problems we're (still?) seeing.

I've seen those on every machine so far when ran long enough. Since I
believe we've clearly demonstrated that this is an unrelated failure,
I've split it out into bug 1860013 - let's track it there.

> There was also another issue during one of the reboots which is probably
> unrelated and due to a flaky BMC:

Let's track that in bug 1857073. Even if it is a flaky BMC, the IPMI
driver should handle the failure gracefully.
Did you see this on host 'wright' as well?

 -dann

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

Title:
  Cavium ThunderX CN88XX Panic : Unknown reason

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

Bug description:
  Series: Bionic
  Kernel: 4.15.0-74.84 linux-generic
  Steps to reproduce:  Install 4.15.0-74.84 Kernel and boot the system.

  The following crash was observed while testing the proposed kernel for the 
2019.12.02 SRU Cycle.
  This kernel was built to include fixes for the following bugs:

    * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
  (LP: #1853326)
  - Revert "arm64: Use firmware to detect CPUs that are not affected by
    Spectre-v2"
  - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"

    * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
  Kunpeng920 (LP: #1852723)
  - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to
    correct place

  The following crash appears to be a NEW bug. not related to the prior bugs 
listed above.
  This bug DOES NOT APPEAR to be related to LP#1857073.

  This is another NEW BUG.

  Hostname: Starmie

  Probable Cause is unknown at this point and still under investigation.

  [  OK  ] Found device WDC_WD5003ABYZ-011FA0 efi.
   Mounting /boot/efi...
  [  OK  ] Mounted /boot/efi.
  [  OK  ] Reached target Local File Systems.
   Starting AppArmor initialization...
   Starting Tell Plymouth To Write Out Runtime Data...
   Starting ebtables ruleset management...
  [   20.942427] kernel BUG at 
/build/linux-pWET3k/linux-4.15.0/fs/buffer.c:1240!
  [   20.951416] Internal error: Oops - BUG: 0 [#1] SMP
  [   20.958153] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq ipmi_ssif uio 
ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf 
nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect aes_ce_blk 
sysimgblt fb_sys_fops aes_ce_cipher crc32_ce drm crct10dif_ce ghash_ce sha2_ce 
sha256_arm64 sha1_ce ahci thunder_bgx libahci thunder_xcv i2c_thunderx 
mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd 
cryptd aes_arm64
  [   21.044326] Process systemd (pid: 1, stack limit = 0x5af6f18b)
  [   21.053858] CPU: 1 PID: 1 Comm: systemd Not tainted 4.15.0-74-generic 
#84-Ubuntu
  [   21.063931] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [   21.074790] pstate: 20400085 (nzCv daIf +PAN -UAO)
  [   21.082096] pc : __find_get_block+0x2e8/0x398
  [   21.088917] lr : __getblk_gfp+0x3c/0x2a8
  [   21.095379] sp : 099ab7e0
  [   21.101062] x29: 099ab7e0 x28: 
  [   21.108699] x27:  x26: 
  [   21.116265] x25: 0001 x24: 
  [   21.123788] x23: 0008 x22: 801f26116c80
  [   21.131302] x21: 801f26116c80 x20: 245c
  [   21.138808] x19: 1000 x18: a59c3a70
  [   21.146300] x17:  x16: 
  [   21.153730] x15: 0020 x14: 0012
  [   21.161083] x13: 2f7374696e752f64 x12: 0101010101010101
  [   

[Kernel-packages] [Bug 1860013] [NEW] [thunderx] Synchronous External Abort: synchronous parity or ECC error

[dann frazier]

Public bug reported:

[Impact]
Under load, ThunderX systems eventually fail with:

[  282.360376] Synchronous External Abort: synchronous parity or ECC error 
(0x9618) at 0xa6eb7000
[  282.372351] Internal error: : 9618 [#1] SMP
[  282.379152] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
shpchp cavium_rng_vf cavium_rng gpio_keys uio_pdrv_genirq uio ipmi_ssif 
ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf 
nicpf uas usb_storage ast i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt aes_ce_blk fb_sys_fops aes_ce_cipher drm crc32_ce 
crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce ahci libahci thunder_bgx 
thunder_xcv i2c_thunderx mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd aes_arm64
[  282.467284] Process cc1 (pid: 39700, stack limit = 0xe0c44146)
[  282.477172] CPU: 25 PID: 39700 Comm: cc1 Not tainted 4.15.0-75-generic 
#85+lp1857074.1
[  282.488379] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 
5.11 12/12/2012
[  282.500121] pstate: 8005 (Nzcv daif -PAN -UAO)
[  282.508297] pc : __arch_copy_to_user+0x13c/0x248
[  282.516430] lr : cp_new_stat+0x140/0x178
[  282.523768] sp : 2e4d3d40
[  282.530369] x29: 2e4d3d40 x28: 801f51fa2d00 
[  282.538988] x27: 08b52000 x26: 0050 
[  282.548031] x25: 0124 x24: 0015 
[  282.556872] x23:  x22: 2e4d3d88 
[  282.565449] x21: 801f51fa2d00 x20: 09588000 
[  282.574109] x19: 2e4d3e30 x18: a87e7a70 
[  282.582790] x17: a8756110 x16: 082f4448 
[  282.591433] x15:  x14: 0012 
[  282.599986] x13: 00682e6c746e6366 x12: 2f78756e696c2f69 
[  282.608730] x11:  x10: 0cf0 
[  282.617283] x9 : 1000 x8 : 000181a4 
[  282.625839] x7 : 01001a2b x6 : 2e4d3da0 
[  282.634238] x5 : 2e4d3e08 x4 : 0008 
[  282.642754] x3 : 0802 x2 : fff8 
[  282.651250] x1 : 2e4d3d90 x0 : 2e4d3d88 
[  282.660013] Call trace:
[  282.665421]  __arch_copy_to_user+0x13c/0x248
[  282.672979]  SyS_newfstat+0x58/0x88
[  282.679272]  el0_svc_naked+0x30/0x34
[  282.685605] Code: a8c12027 a88120c7 d503201f d503201f (a8c12829) 
[  282.694411] ---[ end trace 863693cf0c3fd297 ]---

[Test Case]
We found this by doing a reboot/kernel build loop. (The reboot maybe 
unnecessary). Code to automate this setup is at:
  https://code.launchpad.net/~dannf/+git/kernel-build-reboot-loop

[Fix]
[Regression Risk]

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

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

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Status: Triaged

** Affects: linux (Ubuntu Eoan)
 Importance: Undecided
 Status: Triaged

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Triaged

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
   Status: New => 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/1860013

Title:
  [thunderx] Synchronous External Abort: synchronous parity or ECC error

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Triaged
Status in linux source package in Eoan:
  Triaged
Status in linux source package in Focal:
  Triaged

Bug description:
  [Impact]
  Under load, ThunderX systems eventually fail with:

  [  282.360376] Synchronous External Abort: synchronous parity or ECC error 
(0x9618) at 0xa6eb7000
  [  282.372351] Internal error: : 9618 [#1] SMP
  [  282.379152] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
shpchp cavium_rng_vf cavium_rng gpio_keys uio_pdrv_genirq uio ipmi_ssif 
ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress 

[Kernel-packages] [Bug 1859801] Re: bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Packaging
- phase-changed: Thursday, 16. January 2020 14:27 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 16. January 2020 16:51 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-lrm: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
  variant: debs

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

Title:
  bionic/linux-aws-fips: 4.15.0-2007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1859795
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 16. January 2020 16:51 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
  variant: debs

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

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

[Kernel-packages] [Bug 1858534] Re: disco/linux-azure: 5.0.0-1029.31 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: '1859724'
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 14. January 2020 16:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1858533
  variant: debs

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

Title:
  disco/linux-azure: 5.0.0-1029.31 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: '1859724'
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 14. January 2020 16:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1858533
  variant: debs

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

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

[Kernel-packages] [Bug 1858541] Re: disco/linux-kvm: 5.0.0-1025.27 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1858547
+ kernel-stable-master-bug: '1859724'
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Tuesday, 14. January 2020 16:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: '1859724'
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Tuesday, 14. January 2020 16:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  disco/linux-kvm: 5.0.0-1025.27 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: '1859724'
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Tuesday, 14. January 2020 16:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1858534] Re: disco/linux-azure: 5.0.0-1029.31 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1858547
+ kernel-stable-master-bug: '1859724'
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 14. January 2020 16:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1858533
  variant: debs

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

Title:
  disco/linux-azure: 5.0.0-1029.31 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: '1859724'
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 14. January 2020 16:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1858533
  variant: debs

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

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