date:20190429

@You-Sheng

Sorry, our messages must have crossed paths.

Appears to be the third device from the strace of the fwupd process in
the hung state.

$ grep -i drm strace.log | tail -n 2
2897  20:01:01.099170 lseek(19, 1200, SEEK_SET) = 1200
2897  20:01:01.099193 read(19,  ) = ?

So as you suspected, when I ran your test program I got the same hang.

sudo ./read-dpcd /dev/drm_dp_aux3

Hangs forever. Does not respond to various kill signals. Must be the
caps aux_read call because there are no prints before the hang.

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

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone 
dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport

[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot

2019-04-29 Thread You-Sheng Yang

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

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

Title:
  amdgpu resume failure: failed to allocate wb slot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Systems with video cards using amdgpu driver may fail to resume due to 
resource leakage.

  [Fix]
  73469585510d drm/amdgpu: fix&cleanups for wb_clear

  [Test Case]
  Verified with fwts for a thounsand runs.

  [Regression Risk]
  Low. This patch has been included in stable kernel v4.16.y and on, and
  it's mostly a trivial bug fix.

   Original Bug Report 
  [Summary]
  When do the S3 stress test with AMD RX550 installed, the system hung after 
resume from S3 at 112nd S3.

  The kernel message:
  [ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
  [ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 11 (-22).
  [ 8120.979662] [drm] ib test on ring 12 succeeded
  [ 8120.981952] [drm] ib test on ring 13 succeeded
  [ 8120.984578] [drm] ib test on ring 14 succeeded
  [ 8120.984813] [drm] ib test on ring 15 succeeded
  [ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test 
failed (-22).
  [ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
  [ 8121.022465] [drm] 92GH: [Block 0]
  [ 8121.022465] [drm] 92GH: [Block 1]
  [ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id = 
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18, 
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
  [ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1, 
channel_count = 2, sample_rate = 7, sample_size = 7
  [ 8121.022573] PM: resume of devices complete after 412.170 msecs
  [ 8121.023076] acpi LNXPOWER:04: Turning OFF
  [ 8121.023113] PM: Finishing wakeup.
  [ 8121.023114] OOM killer enabled.
  [ 8121.023114] Restarting tasks ...
  [ 8121.023455] pci_bus :04: Allocating resources
  [ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04] 
add_size 1000
  [ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 04] add_size 20 add_align 10
  [ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to 
[bus 04] add_size 20 add_align 10
  [ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
  [ 8121.024358] done.
  [ 8121.082344] video LNXVIDEO:00: Restoring backlight state
  [ 8121.082346] PM: suspend exit
  [ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
  [ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
  [ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
  [ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
  [ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
  [ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8122.183439] [drm] RC6 on
  [ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  [ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8125.089448] [drm:amd_sc

[Kernel-packages] [Bug 1825778] Re: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest

2019-04-29 Thread Po-Hsu Lin

https://github.com/torvalds/linux/commit/8c03557c3f25271e62e39154af66ebdd1b59c9ca

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

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

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

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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  False positive test result in run_afpackettests from net in
  ubuntu_kernel_selftest

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  New

Bug description:
  The run_afpackettests will be marked as passed regardless the return
  value of those sub-tests in the script:
  
  running psock_tpacket test
  
  [FAIL]
  selftests: run_afpackettests [PASS]

  Fix this by changing the return value for each tests.

  Patch sent to upstream.

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

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

[Kernel-packages] [Bug 1673535] Re: drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

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

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1704

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

Title:
  drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

Status in linux package in Ubuntu:
  New

Bug description:
  Canonical,

  Please add patch into 17.04:

  commit 3856081eede297b617560b85e948cfb00bb395ec

  
  drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS
  
  The current POST code for the AST2300/2400 family doesn't work properly
  if the chip hasn't been initialized previously by either the BMC own FW
  or the VBIOS. This fixes it.

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

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

[Kernel-packages] [Bug 1818490] Re: Intel I210 Ethernet card not working after hotplug [8086:1533]

2019-04-29 Thread You-Sheng Yang

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

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

Title:
  Intel I210 Ethernet card not working after hotplug [8086:1533]

Status in HWE Next:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Summary:
  Intel I210 Ethernet card not working after hotplug

  Steps to reproduce:
  1. Power on system with ethernet cable on Intel I210
  2. Check ethernet is workable
  3. Unplug then plug the ethernet cable

  Expected result:
  Intel I210 Ethernet card is working, e.g. IP address acquired automatically 
if configured as DHCP.

  Actual result:
  Intel I210 Ethernet card not working after hotplug. dmesg has following error 
messages instead:
  [ 16.464321] [ cut here ]
  [ 16.464326] PCI PM: State of device not saved by 
igb_runtime_suspend+0x0/0x90 [igb]
  [ 16.464334] WARNING: CPU: 2 PID: 49 at 
/build/linux-oem-ta19Pv/linux-oem-4.15.0/drivers/pci/pci-driver.c:1282 
pci_pm_runtime_suspend+0x175/0x180
  [ 16.464334] Modules linked in: joydev input_leds nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_intel 
irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core crc32_pclmul snd_hwdep 
ghash_clmulni_intel pcbc snd_pcm dell_smm_hwmon aesni_intel aes_x86_64 
snd_seq_midi crypto_simd snd_seq_midi_event glue_helper cryptd snd_rawmidi 
intel_cstate snd_seq intel_rapl_perf dell_wmi snd_seq_device dell_smbios dcdbas 
snd_timer dell_wmi_aio dell_wmi_descriptor intel_wmi_thunderbolt snd 
sparse_keymap wmi_bmof soundcore idma64 virt_dma mei_me intel_lpss_pci 
intel_pch_thermal mei intel_lpss mac_hid acpi_pad sch_fq_codel parport_pc ppdev 
lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456
  [ 16.464354] async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
hid_generic usbhid hid i915 igb drm_kms_helper syscopyarea dca sysfillrect 
i2c_algo_bit e1000e sysimgblt ptp fb_sys_fops pps_core ahci libahci drm wmi 
video
  [ 16.464366] CPU: 2 PID: 49 Comm: kworker/2:1 Not tainted 4.15.0-1032-oem 
#37-Ubuntu
  [ 16.464367] Hardware name: Dell Inc. Precision 3630 Tower/, BIOS 99.2.2 
01/14/2019
  [ 16.464369] Workqueue: pm pm_runtime_work
  [ 16.464370] RIP: 0010:pci_pm_runtime_suspend+0x175/0x180
  [ 16.464371] RSP: 0018:a968c3363d48 EFLAGS: 00010282
  [ 16.464372] RAX:  RBX: 8a2557aee0a0 RCX: 0006
  [ 16.464372] RDX: 0007 RSI: 0096 RDI: 8a257c496490
  [ 16.464373] RBP: a968c3363d70 R08: 0001 R09: 0373
  [ 16.464373] R10:  R11:  R12: 
  [ 16.464373] R13: c0481540 R14: 8a2557aee000 R15: 
  [ 16.464374] FS: () GS:8a257c48() 
knlGS:
  [ 16.464375] CS: 0010 DS:  ES:  CR0: 80050033
  [ 16.464375] CR2: 7f30b3e93170 CR3: 000842c0a004 CR4: 003606e0
  [ 16.464376] DR0:  DR1:  DR2: 
  [ 16.464376] DR3:  DR6: fffe0ff0 DR7: 0400
  [ 16.464376] Call Trace:
  [ 16.464379] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464380] __rpm_callback+0xca/0x210
  [ 16.464381] ? __switch_to_asm+0x40/0x70
  [ 16.464382] ? __switch_to_asm+0x34/0x70
  [ 16.464382] rpm_callback+0x59/0x80
  [ 16.464383] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464384] rpm_suspend+0x137/0x640
  [ 16.464385] ? __switch_to_asm+0x40/0x70
  [ 16.464386] pm_runtime_work+0x81/0xa0
  [ 16.464388] process_one_work+0x1de/0x410
  [ 16.464389] worker_thread+0x32/0x410
  [ 16.464390] kthread+0x121/0x140
  [ 16.464391] ? process_one_work+0x410/0x410
  [ 16.464392] ? kthread_create_worker_on_cpu+0x70/0x70
  [ 16.464392] ret_from_fork+0x35/0x40
  [ 16.464393] Code: 2b ff ff ff 80 3d 21 c6 11 01 00 0f 85 1e ff ff ff 49 8b 
b5 a0 00 00 00 48 c7 c7 a0 56 b2 ad c6 05 06 c6 11 01 01 e8 0b 74 b9 ff <0f> 0b 
e9 fd fe ff ff 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 53
  [ 16.464408] ---[ end trace 97e5f2cf651b62e6 ]---

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

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

[Kernel-packages] [Bug 1803474] Re: ELANTECH touchpad detected as PS/2 Logitech Wheel Mouse on Compaq Presario 21-N1F3AR

2019-04-29 Thread Florencia

Thank you so much, it was as simple as adding
GRUB_CMDLINE_LINUX="i8042.nomux=1 i8042.reset"   on grub, updating and
rebooting.

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

Title:
  ELANTECH touchpad detected as PS/2 Logitech Wheel Mouse on Compaq
  Presario 21-N1F3AR

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, I formerly had installed Ubuntu 18.04 with the same problem, my
  touchpad was detected as a generic PS2 mouse so I thought that if I
  upgraded my Ubuntu version (currently 18.10) my problem would be
  solved. I tried several fixes that I found on different forums with my
  previous version but they didn't work. I'm not an advanced user and I
  was looking forward to finally switch to linux but this is a big
  problem for me. I attached some files except cat /var/log/Xorg.0.log >
  Xorg.0.log

  cat: /var/log/Xorg.0.log: No existe el archivo o el directorio
  (missing file or directory)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  flor   2769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 14 22:27:10 2018
  InstallationDate: Installed on 2018-11-10 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 058f:3822 Alcor Micro Corp. 
   Bus 001 Device 002: ID 8087:07dc Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: COMPAQ Presario 21 VerK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=39b22cde-4b65-4213-8812-e830a36afe55 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-11-14 (0 days ago)
  dmi.bios.date: 02/27/2016
  dmi.bios.vendor: COMPAQ
  dmi.bios.version: fd
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: K21
  dmi.board.vendor: EA
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnCOMPAQ:bvrfd:bd02/27/2016:svnCOMPAQ:pnPresario21VerK:pvrTBDbyOEM:rvnEA:rnK21:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Presario 21 VerK
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: COMPAQ

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

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

[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

You're probably right about the driver. I've seen other complaints from
the drm layer around amdgpu. I'll try to watch dmesg more often to catch
more of these.

Just added the files from apport.

As for the rest:

> 1) Can you please follow the things that the bot said to add your logs
to the bug.

Done

> 2) Can you please try latest mainline (5.1rc7:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc7/) and confirm it
doesn't help? I don't expect it to.

I'll look into this. May be the weekend before I get some more time.

> 3) If the fwupd workaround does end up being backported to Disco,
please test it for the purposes of the SRU, you would see notification
in this bug.

Will do.


FWIW, I finally got fwupd to compile fully. I was missing gio-cli. If I
can figure out how to set a prefix in meson to something I can easily
uninstall, I'll test an install of the 1.2.8 tag or a cherry pick of
that patch on 1.2.5.

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

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descr

[Kernel-packages] [Bug 1826730] Re: [ASUS X555YI] audio crackle when the sound a little loud.

2019-04-29 Thread widon1104

1805077 do not appear again.
1826730 is a different bug exist for a very long time(few years I think).

My kernel version now is:
widon@widon-MS-7A69:~$ uname -a
Linux widon-MS-7A69 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  [ASUS X555YI] audio crackle when the sound a little loud.

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

Bug description:
  both mpv and vlc have this problem, even when I use firefox see youtube 
video, if I turn the sound a little loud, the sound will with a lot of crackle 
sound.
  I ubuntu18.04 all the thing update to date.
  widon@widon-X555YI:~$ dpkg -l | grep pulseaudio
  ii  gstreamer1.0-pulseaudio:amd64 
1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for 
PulseAudio
  ii  pulseaudio1:11.1-1ubuntu7.2   
 amd64PulseAudio sound server
  ii  pulseaudio-module-bluetooth   1:11.1-1ubuntu7.2   
 amd64Bluetooth module for PulseAudio sound server
  ii  pulseaudio-utils  1:11.1-1ubuntu7.2   
 amd64Command line tools for the PulseAudio sound server
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon  1517 F pulseaudio
   /dev/snd/controlC0:  widon  1517 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-24 (156 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  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/1826730/+subscriptions

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

[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

2019-04-29 Thread You-Sheng Yang

This is a small C program doing exactly the same thing as fwupd does to
trigger this issue. Usage: `sudo ./read-dpcd /dev/drm_dp_aux`.

To find out what  is, replace ExecStart property in
`/lib/systemd/system/fwupd.service` from `/usr/lib/fwupd/fwupd` to
`/usr/bin/strace -D -tt -y -f -o /var/lib/fwupd/strace.log
/usr/lib/fwupd/fwupd`. Find the last open /dev/drm_dp_aux*.

This was first reported on a premature hardware platform. It was fixed
automatically with a second DVT release and without additional effort
being done in the kernel space.

** Attachment added: "read-dpcd.c"
   
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1826691/+attachment/5260188/+files/read-dpcd.c

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

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal t

[Kernel-packages] [Bug 1826730] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1826730

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

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

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

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

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

Title:
  [ASUS X555YI] audio crackle when the sound a little loud.

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

Bug description:
  both mpv and vlc have this problem, even when I use firefox see youtube 
video, if I turn the sound a little loud, the sound will with a lot of crackle 
sound.
  I ubuntu18.04 all the thing update to date.
  widon@widon-X555YI:~$ dpkg -l | grep pulseaudio
  ii  gstreamer1.0-pulseaudio:amd64 
1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for 
PulseAudio
  ii  pulseaudio1:11.1-1ubuntu7.2   
 amd64PulseAudio sound server
  ii  pulseaudio-module-bluetooth   1:11.1-1ubuntu7.2   
 amd64Bluetooth module for PulseAudio sound server
  ii  pulseaudio-utils  1:11.1-1ubuntu7.2   
 amd64Command line tools for the PulseAudio sound server
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon  1517 F pulseaudio
   /dev/snd/controlC0:  widon  1517 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-24 (156 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  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/1826730/+subscriptions

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

[Kernel-packages] [Bug 1826730] Re: [ASUS X555YI] audio crackle when the sound a little loud.

2019-04-29 Thread Daniel van Vugt

Is this an improvement or change compared to when you reported bug
1805077 a few months ago?

If this bug is only new then we should look at different kernel versions
between then and now.

** Summary changed:

- mp4 audio Crackle when the sound a little loud.
+ [ASUS X555YI] audio crackle when the sound a little loud.

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

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

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

Title:
  [ASUS X555YI] audio crackle when the sound a little loud.

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  both mpv and vlc have this problem, even when I use firefox see youtube 
video, if I turn the sound a little loud, the sound will with a lot of crackle 
sound.
  I ubuntu18.04 all the thing update to date.
  widon@widon-X555YI:~$ dpkg -l | grep pulseaudio
  ii  gstreamer1.0-pulseaudio:amd64 
1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for 
PulseAudio
  ii  pulseaudio1:11.1-1ubuntu7.2   
 amd64PulseAudio sound server
  ii  pulseaudio-module-bluetooth   1:11.1-1ubuntu7.2   
 amd64Bluetooth module for PulseAudio sound server
  ii  pulseaudio-utils  1:11.1-1ubuntu7.2   
 amd64Command line tools for the PulseAudio sound server
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon  1517 F pulseaudio
   /dev/snd/controlC0:  widon  1517 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-24 (156 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  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/1826730/+subscriptions

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

[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2019-04-29 Thread Haydenbriese

Linux: 5.0.0-13-generic
intel-microcode: 3.20190312.1

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Won't Fix

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1826691] modified.conffile..etc.fwupd.daemon.conf.txt

apport information

** Attachment added: "modified.conffile..etc.fwupd.daemon.conf.txt"
   
https://bugs.launchpad.net/bugs/1826691/+attachment/5260183/+files/modified.conffile..etc.fwupd.daemon.conf.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/1826691

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone 
dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci 
nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel
  Apr 23 19:29:14 texas kernel: [  133.673381] CPU: 6 PID: 2467 Comm: fwupd 
Tainted: G   OE 5.0.0-13-generic #14-Ubuntu

[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

apport information

** Tags added: apport-collected

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04
  
  Being a firmware updater, the machine is probably relevant - Dell 7730.
  
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  
  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.
  
  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 
  
  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill -9
  the process does not work - in uninterruptible sleep (D).
  
  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.
  
  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone 
dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci 
nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel
  Apr 23 19:29:14 texas kernel: [  133.673381] CPU: 6 PID: 2467 Comm: fwupd 
Tainted: G   OE 5.0.0-13-generic #14-Ubuntu
  Apr 23 19:29:14 texas kernel: [  133.673382] Hardware name: Dell Inc. 
Precision 7730/05W5TJ, BIOS 1.7.0 02/19/2019
  Apr 23 19:29:14 texas kernel: [  133.673417] RIP: 
0010:generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673418] Code: e9 37 7e fe ff 44 8b 45 20 
48 8b 4d 18 48 c7 c7 40 34 17 c1 8b 55 10 8b 75 d4 e8 3b ce 82 e1 41 83 7d 20 
01 0f 84 0c c3 fe ff <0f> 0b e9 05 c3 fe ff 55 48 89 e5 e8 5d de ec ff 48 c7 c7 
00 a0 18
  Apr 23 19:29:14 texas kernel: [  133.673419] RSP: 0018:bbaa0612fbb0 
EFLAGS: 00010297
  Apr 23 19:29:14 texas kernel: [  133.673420] RAX: 0049 RBX: 
00a1 R

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

apport information

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

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone 
dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci 
nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel
  Apr 23 19:29:14 texas kernel: [  133.673381] CPU: 6 PID: 2467 Comm: fwupd 
Tainted: G   OE 5.0.0-13-generic #14-Ubuntu
  Apr 23 19:29:14 texas kernel: [  133.673382]

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

apport information

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

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone 
dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci 
nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel
  Apr 23 19:29:14 texas kernel: [  133.673381] CPU: 6 PID: 2467 Comm: fwupd 
Tainted: G   OE 5.0.0-13-generic #14-Ubuntu
  Apr 23 19:29:14 texas kernel: [  133.673382] Hardware name

[Kernel-packages] [Bug 1826626] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

2019-04-29 Thread Terry Rudd

This bug is a duplicate of LP 1825420.  I was going to mark it so but
Launchpad warns this bug has duplicates itself so I am going to leave it
as is.  Work is ongoing on LP 1825420

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  upgrade to new ubuntu version failed.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kunalss1554 F pulseaudio
   /dev/snd/controlC1:  kunalss1554 F pulseaudio
  Date: Sat Apr 27 09:42:43 2019
  ErrorMessage: triggers looping, abandoned
  HibernationDevice: RESUME=UUID=27221f04-7abb-4a16-8bf9-0d223f3559d6
  InstallationDate: Installed on 2016-10-23 (915 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E7250
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=485acc8d-1178-4d60-baef-b2674d600e32 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  SourcePackage: linux
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-27 (0 days ago)
  dmi.bios.date: 05/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.asset.tag: 72608
  dmi.board.name: 0V8RX3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 72608
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/13/2015:svnDellInc.:pnLatitudeE7250:pvr01:rvnDellInc.:rn0V8RX3:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7250
  dmi.product.sku: Latitude E7250
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1125595] Re: /usr/sbin/dkms: line echo: write error: Broken pipe

2019-04-29 Thread ALinuxUser

I see the problem on Linux Mint 19.1, which is based on Ubuntu bionic.

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

Title:
  /usr/sbin/dkms: line   echo: write error: Broken pipe

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  There are appearing errors within uninstall of kernel/s deb packages.

  
   Uninstall Beginning 
  Module:  fglrx
  Version: 9.012
  Kernel:  3.5.0-23-lowlatency (x86_64)
  -

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  fglrx.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe

  depmod

  DKMS: uninstall completed.
  dkms: removing: vboxhost 4.2.6 (3.5.0-23-lowlatency) (x86_64)

   Uninstall Beginning 
  Module:  vboxhost
  Version: 4.2.6
  Kernel:  3.5.0-23-lowlatency (x86_64)
  -

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  vboxdrv.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe

  
  vboxnetflt.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe

  
  vboxnetadp.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe

  
  vboxpci.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe

  depmod

  DKMS: uninstall completed.
  dkms: removing: vhba 20130121 (3.5.0-23-lowlatency) (x86_64)

   Uninstall Beginning 
  Module:  vhba
  Version: 20130121
  Kernel:  3.5.0-23-lowlatency (x86_64)
  -

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  vhba.ko:
   - Uninstallation
 - Deleting from: /lib/modules/3.5.0-23-lowlatency/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1907: echo: write error: Broken pipe
  /usr/sbin/dkms: line 1905: echo: write error: Broken pipe
  /usr/sbin/dkms: line 19

[Kernel-packages] [Bug 1819786] Re: 4.15 kernel ip_vs --ops causes performance and hang problem

2019-04-29 Thread Marc Hasson

I'd like to note that I tested/verified BOTH these kernel version in
their respective Proposed states that have the ipvs fix.   We really
most need the 16.04 4.15 hwe kernel released, which appears to be in
progress but this is a bionic bug so its unclear if another step is
required.

These kernels passed my ipvs tests properly, the fix worked perfectly:

4.15.0-49.52~16.04.1 (xenial-proposed)
Linux director-16-04 4.15.0-49-generic #52~16.04.1-Ubuntu SMP Thu Apr 25 
18:54:26 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

4.15.0-49.53 (bionic-proposed)
Linux direct-18-04 4.15.0-49-generic #53-Ubuntu SMP Fri Apr 26 06:45:49 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux


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

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

Title:
  4.15 kernel ip_vs --ops causes performance and hang problem

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

Bug description:
  === SRU Justification ===
  [Impact]
  From the commit message:
  "Connections in One-packet scheduling mode (-o, --ops) are
  removed with refcnt=0 because they are not hashed in conn table."

  [Fix]
  From the commit message:
  "To avoid refcount_dec reporting this as error, change them to be
  removed with refcount_dec_if_one as all other connections."

  [Test]
  The bug reporter has a reproducer and confirmed this commit fixes the
  issue.

  [Regression Potential]
  Low. Fix for a specific use case, and it's in upstream for a while.

  === Original Bug Report ===
  On our 16.04LTS (and earlier) systems we used the ipvsadm --ops UDP
  support (one-packet scheduling) to get a better distribution amongst
  our real servers behind the load-balancer for some small subset of
  applications.

  This has worked fine through the 4.4.0-xxx kernels. But when we started
  a program to upgrade systems to use the 4.15 series of kernels to take
  advantage of new facilities, the subset of systems which used the --ops
  option ran into problems. Everything else with the 4.15 kernels appeared
  to work well.

  This issue was reported in #1817247 against 16.04LTS with the HWE 4.15 kernel
  but has not received any acknowledgement after having been reported weeks
  ago.   So we have moved on to confirm that a stock 18.04LTS system with the
  latest expected/standard 4.15 kernel also has this issue as well and report
  that here.  Perhaps this will get more attention.

  The issue appears to have been the change in the ip_vs module from using
  "atomic_*()" increment/decrement functions in the 4.4 kernel to instead
  use "refcount_*()" functions in a later kernel, including the 4.15 one
  we switched to. Unfortunately, the simple refcount_dec() function was
  inadequate, in putting out a time-consuming message and handling when
  the refcount dropped to zero, which is expected in the case of --ops
  support that retains no state post packet delivery. I will upload an
  attachment with the sample messages that get put out at packet arrival
  rate, which destroys performance of course. This test VM reports the
  identical errors we see in our production servers, but at least throwing
  only a couple of test --ops packets at it doesn't crash/hang the 18.04 system
  as it did in the 16.04 VM reported earlier.   And in production, with the
  far greater packet rates, our systems fail since the attached call backtrace
  *** appears on every packet!! ***

  This issue was apparently already recognized as an error and has appeared
  as a fix in upstream kernels. This is a reference to the 4.17 version
  of the fix that we'd like to see incorporated into the next possible
  kernel maintenance release:

  
https://github.com/torvalds/linux/commit/a050d345cef0dc6249263540da1e902bba617e43
  #diff-75923493f6e3f314b196a8223b0d6342

  We have successfully used the livepatch facility to build a livepatch .ko
  with the above diffs on our 4.15.0-36 system and successfully demonstrated
  the contrast in good/bad behavior with/without the livepatch module
  loaded. But we'd rather not have to build a version of livepatch.ko for
  each kernel maintenance release, such as the 4.5.0-46 kernel here used to
  demonstrate the issue persists in the Ubuntu mainline distro.

  The problem is easy to generate, with only a couple of packets
  and a simple configuration. Here's a very basic test (addresses
  rewritten/obscured) version of an example configuration for 2 servers
  that worked on my test VM:

  ipvsadm -A -f 100 -s rr --ops
  ipvsadm -a -f 100 -r 10.129.131.227:0 -g -w 
  ipvsadm -a -f 100 -r 10.129.131.228:0 -g -w 
  iptables -t mangle -A PREROUTING -d 172.16.5.1/32 -j MARK --set-xmark 
0x64/0x
  ifconfig lo:0 172.16.5.1/32 up

  Routing and addressing to achieve the above, or adaptation for one's
  own test environment, is

[Kernel-packages] [Bug 988799]

2019-04-29 Thread mpartap

Can 'someone' please open a bounty on creation of a VM test case, f.e. with 
`vagrant` or `phoronix test suite`?
Basically, a way to reproduce and quantify the perceived/actual performance 
difference between
> Linux 2.6.17 Released 17 June, 2006
and
> Linux 5.0 Released Sun, 3 Mar 2019 
…

(In reply to Alex Efros from comment #666)
> Not as bad as years ago […]
> And that's on powerful and modern enough system with
> kernel 4.19.27, CPU i7-2600K @ 4.5GHz, RAM 24GB, and HDD 3TB […]
> This is annoying, and I remember time before
> 12309 when rtorrent without any throttling won't make mplayer to freeze on
> less powerful hardware.

Oh yeah, this... i can clearly remember back then when on a then mid-
range machine with a lot of compiling (gentoo => 100% cpu �[U+1F923]�)
and filesystem work, VLC used to play an HD video stream even under
heavy load without any hiccups and micro-stuttering.. It was impressive
at the time.. and then.. it broke �[U+1F928]�

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

Title:
  Precise freezes under heavy i/o

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

Bug description:
  Whilst creating a VM with 20 GB persistent HD and my system froze
  until the disk was created.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-23-generic 3.2.0-23.36
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gema   2526 F pulseaudio
   /dev/snd/controlC0:  gema   2526 F pulseaudio
   /dev/snd/controlC1:  gema   2526 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,104383c4,0010'
 Controls  : 45
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:081d'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 16
 Mono: Capture 12 [75%] [24.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Thu Apr 26 11:59:11 2012
  HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IwConfig:
   lono wireless extensions.
   
   virbr0no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago)
  dmi.bios.date: 03/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D-E LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd03/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

--- Comment From leona...@ibm.com 2019-04-29 18:50 EDT---
(In reply to comment #70)
> Leonardo, since you seem to have a reliable reproducer now, could you give
> this test kernel [1] a try? It just contains commit c066fafc595e ("KVM: PPC:
> Book3S HV: Use correct pagesize in kvm_unmap_radix()") and is basically what
> Joe gave you (comment #5) but at that time you weren't able to reproduce the
> issue.
>
> [1] https://kernel.ubuntu.com/~juergh/lp1788098/

Hello Juerg,

As you pointed, this kernel has only one of the 19 patches of the patch series.
IMHO it would't be very productive to test this kernel as is. It can as well 
work just fine, but it doesn't have the complete solution to this problems.
The kernel with the whole patch series is already tested, and solves many other 
possible issues.

But If you think it's really important to test this one, I will try to
schedule it for testing ASAP.

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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

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

--- Comment From mranw...@us.ibm.com 2019-04-29 18:21 EDT---
I think this can be closed now, Bala said:

Tested with latest Ubuntu 1810 build and issue is not observed,

JOB ID : 254e98b7377aa595d0659c48d5ee3af601594eab
JOB LOG: 
/home/bala/avocado-fvt-wrapper/results/job-2019-04-24T03.17-254e98b/job.log
(1/1) 
guest_migration.qemu.qcow2.virtio_scsi.smp2.virtio_net.Guest.Ubuntu.18.10.ppc64le.powerkvm-libvirt.virsh.migrate.there_and_back.normal_test.without_cpu_hotplug.compat_migration.non_compat_migration.without_postcopy:
 PASS (506.14 s)
RESULTS: PASS 1 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
JOB TIME   : 509.27 s
JOB HTML   : 
/home/bala/avocado-fvt-wrapper/results/job-2019-04-24T03.17-254e98b/results.html

Observation:
No kernel oops observed inside guest while migrating back to source.

System configuration:

Host (source and target)
Kernel: 4.18.0-17-generic
Qemu: 1:2.12+dfsg-3ubuntu8.6
SLOF: 20170724+dfsg-1ubuntu1
Libvirt: 4.6.0-2ubuntu3.4

Guest
Kernel: 4.18.0-17-generic

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

Title:
  [Ubuntu 1810] Migrating Power9 guest back to source causes kernel Oops
  inside guest

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Migrating back Power9 to source cause Kernel Oops inside guest
   
  Contact Information = Balamuruhan S / balamuruh...@in.ibm.com 
   
  ---uname output---
  source and target host Kernel: 4.18.0-8-generic
  Guest Kernel: 4.18.0-8-generic
   
  Machine Type = Boston 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---

  Due to Bug 172310, Turn off the firewalld in source and target host
  machines.

  1. Define a healthy guest and placed image in NFS share.

  2. Mounted the image location in destination and start the guest to
  perform migration.

  3. Perform migration from source to target,
  08:07:54 INFO | Migrating VM avocado-vt-vm1-migration from qemu:///system to 
qemu+ssh://9.40.194.13/system
  08:07:54 DEBUG| Running virsh command: migrate --live --domain 
avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60
  08:07:54 INFO | Running '/usr/bin/virsh -c 'qemu:///system' migrate --live 
--domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system 
--timeout 60'
  08:08:21 DEBUG| [stdout]
  08:08:21 INFO | Command '/usr/bin/virsh -c 'qemu:///system' migrate --live 
--domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system 
--timeout 60' finished with 0 after 26.9465551376s
  08:08:21 DEBUG| status: 0
  08:08:21 DEBUG| stdout:
  08:08:21 DEBUG| stderr:
  08:08:21 INFO | Migration exit status: 0

  4. check VM uptime after successful migration,
  08:07:44 INFO | Check VM uptime before migration: 57.66

  5. Migration is successful from source to destination, now perform
  migration back to source

  08:08:49 INFO | Migrating VM avocado-vt-vm1-migration from 
qemu+ssh://9.40.194.13/system to qemu:///system
  08:08:49 DEBUG| Running virsh command: migrate --live --domain 
avocado-vt-vm1-migration --desturi qemu:///system --timeout 60
  08:08:49 INFO | Running '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' 
migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system 
--timeout 60'
  08:09:22 DEBUG| [stdout]
  08:09:22 INFO | Command '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' 
migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system 
--timeout 60' finished with 0 after 32.8640539646s
  08:09:22 DEBUG| status: 0
  08:09:22 DEBUG| stdout:
  08:09:22 DEBUG| stderr:
  08:09:22 INFO | Migration exit status: 0

  6. check uptime of VM after migration and it is observed that VM have
  gone for reboot

  08:10:22 INFO | Check VM uptime after migrating back to source: 31.09

  5. By checking the VM console Call Trace is observed as mentioned
  below

  The time stamp during the call trace observed inside guest matches with the 
timestamp during which
  migration is triggered.
   
  Stack trace output:
   no

  Attachment:
  1. VM sosreport
  2. source and target sosreport
  3. VM console log with call trace
  4. Guest xml
  5. Test job log
   
  Oops output:
   2018-10-26 08:08:26: root@ubuntu1810:~#
  2018-10-26 08:09:11: [  144.512549] Unable to handle kernel paging request 
for data at address 0x71ff9672fa0e0989
  2018-10-26 08:09:11: [  144.512655] Faulting instruction address: 
0xc03af7cc
  2018-10-26 08:09:11: [  144.512741] Oops: Kernel access of bad area, sig: 11 
[#1]
  2018-10-26 08:09:11: [  144.512789] LE SMP NR_CPUS=2048 NUMA pSeries
  2018-10-26 08:09:11: [  144.512859] Modules linked in: iscsi_target_mod 
target_core_mod xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntr

[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

2019-04-29 Thread Hui Wang

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

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

Title:
  [regression][snd_hda_codec_realtek] repeating crackling noise after
  19.04 upgrade

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM 
is
  enabled, on some codecs or for some hw design, there is noise with the codec
  runtime PM enabled.

  
  [Fix]
  put the machine in the power_save_black_list, this will set the power_save=0

  [Test Case]
  just boot up and do some audio operations, there is no noise anymore

  [Regression Risk]
  Low. this patch ony applies to the specific machines.


  
  I'm experiencing a repeating crackling noise after 19.04 upgrade that start 
just after the boot and before the login.

  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
   and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.

  The command "killall pulseaudio" usually stop the noise for 10
  seconds, then the noise restart.

  The system was running smoothly on 18.10

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   3310 F pulseaudio
   /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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

[Kernel-packages] [Bug 1825272] Re: headset-mic doesn't work on two Dell laptops.

2019-04-29 Thread Hui Wang

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

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

Title:
  headset-mic doesn't work on two Dell laptops.

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

Bug description:
  [Impact]
  the headset-mic can't be detected after we plug the headset into the audio 
jack

  [Fix]
  Apply the fixup of ALC255_FIXUP_DELL1_MIC_NO_PRESENCE.

  [Test Case]
  Boot up the system
  plug the headset into the audio jack
  The audio device selecting dialogue will show up
  selecting headset-mic icon, then rerord sound from headset-mic, it works well.

  [Regression Risk]
  Low. this patch only applies to specific dell machines which have the same 
pin config
  as defined in the patch.

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

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

[Kernel-packages] [Bug 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card

2019-04-29 Thread vseguip

I'm having the same problem with a Sandisk 64G.

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

Title:
  SD card error mmc0: error -110 whilst initialising SD card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When inserting card to internal card reader:

  laurynas@laurynas-ThinkPad-T450:~$ dmesg
  [342809.333716] mmc0: error -110 whilst initialising SD card

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

  
  SanDisk Extreme 64GB UHS 3. Working fine on windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  laurynas   3963 F pulseaudio
   /dev/snd/controlC0:  laurynas   3963 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  3 16:09:26 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4
  InstallationDate: Installed on 2017-02-18 (683 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20BUS3GN07
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago)
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BUS3GN07
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BUS3GN07
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

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

--- Comment From mranw...@us.ibm.com 2019-04-29 17:43 EDT---
I did some more testing, including toggling 
/sys/kernel/debug/powerpc/count_cache_flush and checking the code in xmon 
before:
c000db58  7ee00026  mfcrr23
c000db5c  fae101a0  std r23,416(r1)
c000db60  f823  std r1,0(r3)
c000db64  4bffdb1d  bl  c000b680# 
flush_count_cache+0x0/0x2480

and after:
c000db58  7ee00026  mfcrr23
c000db5c  fae101a0  std r23,416(r1)
c000db60  f823  std r1,0(r3)
c000db64  6000  nop

All looks correct.  Thanks for flipping the tag, I think it looks good.
I'll run some regression on it now, too.

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

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

Bug description:
  [IMPACT]
  Need to further address the Spectre v2 and Meltdown vulnerability in Power 
with software count cache flush Spectre v2 mitigation support for Power9 DD2.3, 
and additional Spectre/Meltdown related patches for Power9.

  [Fix]
  List of upstream patches identified by IBM in comment #4, #5, and #8.

  [Test]
  Pre-req: requires Power9 DD2.3 hardware.
  A test kernel is available in PPA ppa:ubuntu-power-triage/lp1822870 and the 
kernel was tested by IBM. Please see comment #11 and #14 for details.

  [REGRESSION POTENTIAL]
  The patches are isolated to the ppc64el architecture and does not impact 
generic code. ppc64el test kernel was tested by IBM and no regressions were 
reported.

  [OTHER INFO]
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

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

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

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

** Tags removed: targetmilestone-inin1704
** Tags added: targetmilestone-inin1710

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-29 Thread Jakob Unterwurzacher

$ apt-cache policy linux-generic-hwe-16.04
linux-generic-hwe-16.04:
  Installed: 4.15.0.49.70
  Candidate: 4.15.0.49.70
  Version table:
 *** 4.15.0.49.70 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 4.15.0.48.69 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages

$ uname -a
Linux osboxes 4.15.0-49-generic #52~16.04.1-Ubuntu SMP Thu Apr 25 18:54:26 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux


Issue is fixed.

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

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

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

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

Bug description:
  SRU Justification:

  [Impact]

   * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a
  race condition that leave fuse inode's mutex held, triggering a
  deadlock

   * The problem is that the lock and unlock paths are relying on
  get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to
  be acquired/released, but its value might be set in the lock path and
  unset in the unlock path (leaving the mutex held)

  [Test Case]

   * A test case that triggers the bug almost immediately can be found
  here https://github.com/hanwen/go-fuse/pull/288

  [Fix]

   * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in
  fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the
  locking path and pass a variable to fuse_unlock_inode() to determine
  if the mutex was acquired or not

  [Regression Potential]

   * Fix has been tested on the affected platform. It is an upstream fix
  that seems to affect only 4.7+ kernels, more exactly in our case only
  Bionic kernels (and derived) are affected. Cosmic and above already
  include this fix. So regression potential is minimal.

  [Original bug report]

  Hello up there,

  We were reported about a deadlock in the kernel while using a FUSE-based 
filesystem on Ubuntu.
  The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We 
tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the 
following patch, in despite the patch being marked as needed for v4.7+ stable 
kernels:

  https://git.kernel.org/linus/63576c13bd

  Please see the following go-fuse issue for full details:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562

  The bug is potentially applicable to libfuse users too since libfuse
  by default enables parallel dirops whenever kernel claims support for
  it, which libfuse maintained confirmed:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381

  We tested that cherry-picking 63576c13bd into 4.15.x series makes the
  problem go away:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969

  So please include https://git.kernel.org/linus/63576c13bd into Ubuntu
  4.15.x kernel series which are bionic/master and xenial/hwe, and which
  currently don't have this patch.

  

  Here is a full list of FUSE patches marked to be needed in stable
  kernels starting from v4.15:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 
--grep="stable@" -- fs/fuse/
  a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page
  9509941e9c53 fuse: call pipe_buf_release() under pipe lock
  8a3177db59cd cuse: fix ioctl
  97e1532ef81a fuse: handle zero sized retrieve correctly
  2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  ebacb8127359 fuse: fix use-after-free in fuse_direct_IO()
  2d84a2d19b61 fuse: fix possibly missed wake-up after abort
  7fabaf303458 fuse: fix leaked notify reply
  908a572b80f6 fuse: fix blocked_waitq wakeup
  4c316f2f3ff3 fuse: set FR_SENT while locked
  d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write()
  bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read()
  a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock()
  63576c13bd17 fuse: fix initial parallel dirops
  e8f3bd773d22 fuse: Fix oops at process_init_reply()
  b8f95e5d13f5 fuse: umount should wait for all requests
  45ff350bbd9d fuse: fix unlocked access to processing queue
  87114373ea50 fuse: fix double request_end()
  543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at 
fuse_fill_super().
  6becdb601bae fuse: fix control dir setup and teardown
  8a301eb16d99 fuse: fix congested state leak on aborted connections
  df0e91d48827 fuse: atomic_o_trunc should truncate pagecache

  Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied
  to 4.15.x becuase they cure a problem introduced in a lat

[Kernel-packages] [Bug 1732978] Re: Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

** Tags removed: verification-needed-artful
** Tags added: bugnameltc-161493 severity-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/1732978

Title:
Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
fallback"

Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Released

Bug description:
== SRU Justification ==
Artful uses the 4.13 kernel which has an issue with the fallback cipher for
CTR mode. Commit e666d4e9ceec fixes this problem by using a new structure
for the generic ciphers.

This commit is also needed in Bionic until it gets rebased to 4.15.

Commit e666d4e9ceec was added to mainline in v4.15-rc2

== Fix ==
commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
Author: Paulo Flabiano Smorigo
Date: Mon Oct 16 20:54:19 2017 -0200

crypto: vmx - Use skcipher for ctr fallback

== Regression Potential ==
This commit is specific to crypto, and adds a new structure for the generic
ciphers.

== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.

== Original Bug Desription: ==
== Comment: #0 - Paulo Flabiano Smorigo - 2017-11-17
10:29:14 ==
Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
cipher for CTR mode. The commit bellow fixes this problem by using the new
structure for the generic ciphers. Please add it to the kernel package.

https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

== Comment: #1 - VIPIN K. PARASHAR - 2017-11-17
13:38:05 ==
(In reply to comment #0)
> Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
> cipher for CTR mode. The commit bellow fixes this problem by using the new
> structure for the generic ciphers. Please add it to the kernel package.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
> commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

Which is commit e666d4e9ceec94

commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
Author: Paulo Flabiano Smorigo
Date: Mon Oct 16 20:54:19 2017 -0200

crypto: vmx - Use skcipher for ctr fallback

Signed-off-by: Paulo Flabiano Smorigo
Signed-off-by: Herbert Xu

Its available with 4.14 kernel.

Hello Canonical,

Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr
fallback"
with Ubuntu 17.10 kernel.

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

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

[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat

2019-04-29 Thread Christoph Probst

Oh no. Had a strcat buffer overflow with 4.15.0-48-generic. Issue is NOT
solved.


Apr 29 19:29:00 kernel: [78713.491646] detected buffer overflow in strcat
Apr 29 19:29:00 kernel: [78713.491685] [ cut here ]
Apr 29 19:29:00 kernel: [78713.491686] kernel BUG at 
/build/linux-fkZVDM/linux-4.15.0/lib/string.c:1052!
Apr 29 19:29:00 kernel: [78713.491709] invalid opcode:  [#1] SMP PTI
Apr 29 19:29:00 kernel: [78713.491721] Modules linked in: ufs qnx4 hfsplus hfs 
minix ntfs msdos jfs xfs mpt3sas raid_class scsi_transport_sas mptctl mptbase 
cmac arc4 md4 nls_utf8 cifs ccm fscache dell_rbu bonding nls_iso8859_1 
intel_rapl skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm joydev input_leds dell_smbios irqbypass dcdbas intel_cstate intel_rapl_perf 
ipmi_ssif wmi_bmof dell_wmi_descriptor shpchp mei_me lpc_ich ipmi_si 
ipmi_devintf ipmi_msghandler mei mac_hid acpi_power_meter 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 
raid1 raid0 multipath linear hid_generic crct10dif_pclmul mgag200 crc32_pclmul 
i2c_algo_bit
Apr 29 19:29:00 kernel: [78713.491911]  ghash_clmulni_intel usbhid ttm pcbc 
drm_kms_helper aesni_intel syscopyarea hid sysfillrect aes_x86_64 bnx2x 
crypto_simd sysimgblt glue_helper ptp fb_sys_fops cryptd pps_core uas drm mdio 
ahci megaraid_sas usb_storage libcrc32c libahci wmi
Apr 29 19:29:00 kernel: [78713.491975] CPU: 24 PID: 2242 Comm: perl Not tainted 
4.15.0-48-generic #51-Ubuntu
Apr 29 19:29:00 kernel: [78713.491993] Hardware name: Dell Inc. PowerEdge 
R740/0923K0, BIOS 1.6.11 11/20/2018
Apr 29 19:29:00 kernel: [78713.492014] RIP: 0010:fortify_panic+0x13/0x22
Apr 29 19:29:00 kernel: [78713.492027] RSP: 0018:bb8b35b07940 EFLAGS: 
00010286
Apr 29 19:29:00 kernel: [78713.492041] RAX: 0022 RBX: 
0004 RCX: 
Apr 29 19:29:00 kernel: [78713.492058] RDX:  RSI: 
91acc0b16498 RDI: 91acc0b16498
Apr 29 19:29:00 kernel: [78713.492074] RBP: bb8b35b07940 R08: 
 R09: 0681
Apr 29 19:29:00 kernel: [78713.492090] R10: bb8b35b079f0 R11: 
 R12: 91a0d3461e50
Apr 29 19:29:00 kernel: [78713.492106] R13: 0001 R14: 
0003 R15: 91c0acd1ac00
Apr 29 19:29:00 kernel: [78713.492123] FS:  14ed8f19ffc0() 
GS:91acc0b0() knlGS:
Apr 29 19:29:00 kernel: [78713.492141] CS:  0010 DS:  ES:  CR0: 
80050033
Apr 29 19:29:00 kernel: [78713.492155] CR2: 14ed8e3ff110 CR3: 
000423a5c001 CR4: 007606e0
Apr 29 19:29:00 kernel: [78713.492171] DR0:  DR1: 
 DR2: 
Apr 29 19:29:00 kernel: [78713.492187] DR3:  DR6: 
fffe0ff0 DR7: 0400
Apr 29 19:29:00 kernel: [78713.492203] PKRU: 5554
Apr 29 19:29:00 kernel: [78713.492210] Call Trace:
Apr 29 19:29:00 kernel: [78713.492241]  smb21_set_oplock_level+0x147/0x1a0 
[cifs]
Apr 29 19:29:00 kernel: [78713.492265]  smb3_set_oplock_level+0x22/0x90 [cifs]
Apr 29 19:29:00 kernel: [78713.492285]  smb2_set_fid+0x76/0xb0 [cifs]
Apr 29 19:29:00 kernel: [78713.492303]  cifs_new_fileinfo+0x259/0x390 [cifs]
Apr 29 19:29:00 kernel: [78713.492321]  ? smb2_get_lease_key+0x40/0x40 [cifs]
Apr 29 19:29:00 kernel: [78713.492338]  ? cifs_new_fileinfo+0x259/0x390 [cifs]
Apr 29 19:29:00 kernel: [78713.492355]  cifs_open+0x3db/0x8d0 [cifs]
Apr 29 19:29:00 kernel: [78713.492370]  do_dentry_open+0x1c2/0x310
Apr 29 19:29:00 kernel: [78713.492384]  ? 
cifs_uncached_writev_complete+0x3f0/0x3f0 [cifs]
Apr 29 19:29:00 kernel: [78713.492399]  ? do_dentry_open+0x1c2/0x310
Apr 29 19:29:00 kernel: [78713.492411]  ? __inode_permission+0x5b/0x160
Apr 29 19:29:00 kernel: [78713.492427]  ? 
cifs_uncached_writev_complete+0x3f0/0x3f0 [cifs]
Apr 29 19:29:00 kernel: [78713.492441]  vfs_open+0x4f/0x80
Apr 29 19:29:00 kernel: [78713.492451]  path_openat+0x66e/0x1770
Apr 29 19:29:00 kernel: [78713.492464]  ? mem_cgroup_commit_charge+0x82/0x530
Apr 29 19:29:00 kernel: [78713.492477]  do_filp_open+0x9b/0x110
Apr 29 19:29:00 kernel: [78713.492489]  ? _cond_resched+0x19/0x40
Apr 29 19:29:00 kernel: [78713.493055]  ? __kmalloc+0x19b/0x220
Apr 29 19:29:00 kernel: [78713.493574]  ? security_prepare_creds+0x9c/0xc0
Apr 29 19:29:00 kernel: [78713.494088]  do_open_execat+0x7e/0x1e0
Apr 29 19:29:00 kernel: [78713.494595]  ? prepare_creds+0xd5/0x110
Apr 29 19:29:00 kernel: [78713.495095]  ? do_open_execat+0x7e/0x1e0
Apr 29 19:29:00 kernel: [78713.495590]  do_execveat_common.isra.34+0x1c7/0x810
Apr 29 19:29:00 kernel: [78713.496074]  SyS_execve+0x31/0x40
Apr 29 19:29:00 kernel: [78713.496542]  do_syscall_64+0x73/0x130
Apr 29 19:29:00 kernel: [78713.496997]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Apr 29 19:29:00 kernel: [78713.

[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

2019-04-29 Thread Mario Limonciello

This is definitely a kernel bug, but it's exaggerated by userspace.
So whether it should be worked around in userspace or fixed in the kernel space 
is debatable.

For now, I believe you can employ that workaround to keep your system
stable, but I would ask the following.

1) Can you please follow the things that the bot said to add your logs to the 
bug.
2) Can you please try latest mainline (5.1rc7: 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc7/) and confirm it 
doesn't help?  I don't expect it to.
3) If the fwupd workaround does end up being backported to Disco, please test 
it for the purposes of the SRU, you would see notification in this bug.

** Changed in: fwupd (Ubuntu)
   Status: New => Triaged

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

** Also affects: fwupd (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Incomplete

** Also affects: fwupd (Ubuntu Eoan)
   Importance: Undecided
   Status: Triaged

** Changed in: fwupd (Ubuntu Disco)
   Status: New => Triaged

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

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

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

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

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

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

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2

[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches

2019-04-29 Thread Kim Naru

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

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

Title:
  AMD Rome :  Minimal support patches

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

Bug description:
  The following 3 patches need to be back ported to ubuntu 18.04.2(Linux
  4.18) to complete the minimal support for Rome :

  818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum
  e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register
  90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode

  --thanks
  --kim
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-28 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp33s0f0  no wireless extensions.
   
   lono wireless extensions.
   
   enp33s0f1  no wireless extensions.
  MachineType: AMD Corporation DAYTONA_X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RDY0071B
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DAYTONA_X
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 2
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: DAYTONA_X
  dmi.product.sku: Default string
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

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

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

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

apport information

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

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

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

apport information

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

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

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

apport information

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

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

[Kernel-packages] [Bug 1825753] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1825753/+attachment/5260058/+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/1825753

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

[Kernel-packages] [Bug 1825753] Re: fan speed not reported with Ubuntu 18.10 and 19.04

apport information

** Tags added: apport-collected disco

** Description changed:

- after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the
- list of available sensors
+ after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
+  /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
+  /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2019-04-21 (8 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ MachineType: Dell Inc. XPS13 9333
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
+ RelatedPackageVersions:
+  linux-restricted-modules-5.0.0-13-generic N/A
+  linux-backports-modules-5.0.0-13-generic  N/A
+  linux-firmware1.178
+ Tags:  disco
+ Uname: Linux 5.0.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/27/2015
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A07
+ dmi.board.name: 0D13CR
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.chassis.version: 0.1
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
+ dmi.product.family: Shark Bay System
+ dmi.product.name: XPS13 9333
+ dmi.product.sku: 060A
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1825753/+attachment/5260055/+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/1825753

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

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

apport information

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

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

[Kernel-packages] [Bug 1825753] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1825753/+attachment/5260060/+files/Lsusb.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/1825753

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

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

apport information

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

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

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

apport information

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

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

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

apport information

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

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

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

apport information

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

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

[Kernel-packages] [Bug 1825753] CRDA.txt

apport information

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

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

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

apport information

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

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

[Kernel-packages] [Bug 1825753] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1825753/+attachment/5260066/+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/1825753

Title:
  fan speed not reported with Ubuntu 18.10 and 19.04

Status in Hardware Sensors Indicator:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list 
of available sensors
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-luc   1975 F pulseaudio
   /dev/snd/controlC1:  jean-luc   1975 F pulseaudio
   /dev/snd/pcmC1D0p:   jean-luc   1975 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-21 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions

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

[Kernel-packages] [Bug 1826334] Re: linux-raspi2: 4.15.0-1035.37 -proposed tracker

** 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: 1826358
- phase: Ready for Testing
- phase-changed: Monday, 29. April 2019 15:09 UTC
+ phase: Signoff
+ phase-changed: Monday, 29. April 2019 20:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.15.0-1035.37 -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:
  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:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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: 1826358
  phase: Signoff
  phase-changed: Monday, 29. April 2019 20:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

2019-04-29 Thread Frank Heimes

Adjusting tag according to IBM's test result in comment #19

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

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

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

Bug description:
  [IMPACT]
  Need to further address the Spectre v2 and Meltdown vulnerability in Power 
with software count cache flush Spectre v2 mitigation support for Power9 DD2.3, 
and additional Spectre/Meltdown related patches for Power9.

  [Fix]
  List of upstream patches identified by IBM in comment #4, #5, and #8.

  [Test]
  Pre-req: requires Power9 DD2.3 hardware.
  A test kernel is available in PPA ppa:ubuntu-power-triage/lp1822870 and the 
kernel was tested by IBM. Please see comment #11 and #14 for details.

  [REGRESSION POTENTIAL]
  The patches are isolated to the ppc64el architecture and does not impact 
generic code. ppc64el test kernel was tested by IBM and no regressions were 
reported.

  [OTHER INFO]
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

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

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

[Kernel-packages] [Bug 1826334] Re: linux-raspi2: 4.15.0-1035.37 -proposed tracker

** 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-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1826334

Title:
  linux-raspi2: 4.15.0-1035.37 -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:
  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:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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: 1826358
  phase: Ready for Testing
  phase-changed: Monday, 29. April 2019 15:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826335] Re: linux-snapdragon: 4.15.0-1052.56 -proposed tracker

** 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-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1826335

Title:
  linux-snapdragon: 4.15.0-1052.56 -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 promote-to-proposed series:
  Incomplete
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:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  New

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: 1826358
  phase: Promote to Proposed
  phase-changed: Monday, 29. April 2019 10:39 UTC
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
promote-to-proposed: Stalled -- packages are in the wrong component
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826338] Re: linux-aws: 4.15.0-1038.40 -proposed tracker

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

Title:
  linux-aws: 4.15.0-1038.40 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

  backports: bug 1826337 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Testing
  phase-changed: Friday, 26. April 2019 18:41 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

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

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

[Kernel-packages] [Bug 1826358] Re: linux: 4.15.0-49.53 -proposed tracker

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

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

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

Title:
  linux: 4.15.0-49.53 -proposed tracker

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

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

  backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe)
  derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 
1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 
1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), 
bug 1826348 (linux-oracle), bug 1826350 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 29. April 2019 16: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
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826336] Re: linux-oem: 4.15.0-1037.42 -proposed tracker

** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1826336

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

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

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: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 14:09 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

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

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

[Kernel-packages] [Bug 1826346] Re: linux-oracle: 4.15.0-1012.14~16.04.1 -proposed tracker

** 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-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1826346

Title:
  linux-oracle: 4.15.0-1012.14~16.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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

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: 1826348
  phase: Testing
  phase-changed: Monday, 29. April 2019 14:13 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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826348] Re: linux-oracle: 4.15.0-1012.14 -proposed tracker

** 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-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1826348

Title:
  linux-oracle: 4.15.0-1012.14 -proposed tracker

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

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

  backports: bug 1826346 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 12:10 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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826340] Re: linux-gcp: 4.15.0-1031.33 -proposed tracker

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

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

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

Title:
  linux-gcp: 4.15.0-1031.33 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

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

  backports: bug 1826339 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 14:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1031
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826343] Re: linux-kvm: 4.15.0-1033.33 -proposed tracker

** 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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1826343

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

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: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 14: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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1825968] Re: dep8/lxd: test fails due to unrelated message to stderr

2019-04-29 Thread Stefan Bader

Since the only change was a modification to dep8 tests, there is nothing
else to validate than the successful pass of all arches in xenial
(http://autopkgtest.ubuntu.com/packages/u/ubuntu-fan).

** 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 ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1825968

Title:
  dep8/lxd: test fails due to unrelated message to stderr

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Bionic:
  Triaged

Bug description:
  [SRU Justification]

  == Impact ==
  The LXD DEP8 test fails because of an unrelated message to stderr during 
containser setup (sd_bus_open_system: No such file or directory Exit request 
sent.). The test itself successfully runs to completion.

  == Fix ==
  Change the test control to ignore messages on stderr sicne the test itself 
should exit with a non-zero return code if some test error happens.

  == Testcase ==
  ADT testing

  == Risk of Regression ==
  None, no code change, only DEP8 testing modified

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

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

[Kernel-packages] [Bug 1822821] Re: TSC clocksource not available in nested guests

2019-04-29 Thread Heitor Alves de Siqueira

Validated on linux 4.4.0-147.173 from xenial-proposed:

ubuntu@xenial-l2:~$ uname -r
4.4.0-147-generic

ubuntu@xenial-l2:~$ cat 
/sys/devices/system/clocksource/clocksource0/available_clocksource
kvm-clock tsc hpet acpi_pm

ubuntu@xenial-l2:~$ dmesg | grep -i tsc
[0.00] tsc: Detected 1997.765 MHz processor
[1.705310] clocksource: tsc: mask: 0x max_cycles: 
0x3997de66ec2, max_idle_ns: 881590642279 ns


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

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

Title:
  TSC clocksource not available in nested guests

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

Bug description:
  [Impact]
   * TSC clocksource not available in nested guests

  [Test Case]
   * Spin up a nested Xenial/Bionic guest and check for 'tsc' at
     /sys/devices/system/clocksource/clocksource0/available_clocksource

  [Regression Potential]
   * The regression potential is low. Upstream code still maintains this
     behaviour of skipping calibration on guests, and tsc code verifies if
     the frequency is known before registering the clocksource

   * Patches were verified against the above test case, and also tested
     with stress-ng in both nested and non-nested guest scenarios

  [Fix]
   * By applying the upstream commits [0] [1], we skip refined calibration and
     register TSC as a clocksource directly if its frequency is known (via
     MSR or CPUID)

   * Cosmic onwards (kernel 4.18+) are already fixed

  [0] For Xenial only - https://git.kernel.org/linus/47c95a46d0f
  [1] https://git.kernel.org/linus/e10f78050323

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

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

[Kernel-packages] [Bug 1822821] Re: TSC clocksource not available in nested guests

2019-04-29 Thread Heitor Alves de Siqueira

Validated on linux 4.15.0-49.53 from bionic-proposed:

ubuntu@bionic-l2:~$ uname -r
4.15.0-49-generic

ubuntu@bionic-l2:~$ cat 
/sys/devices/system/clocksource/clocksource0/available_clocksource
kvm-clock tsc hpet acpi_pm

ubuntu@bionic-l2:~$ dmesg | grep -i tsc
[0.04] tsc: Detected 1997.765 MHz processor
[1.310296] clocksource: tsc: mask: 0x max_cycles: 
0x3997de66ec2, max_idle_ns: 881590642279 ns


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

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

Title:
  TSC clocksource not available in nested guests

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

Bug description:
  [Impact]
   * TSC clocksource not available in nested guests

  [Test Case]
   * Spin up a nested Xenial/Bionic guest and check for 'tsc' at
     /sys/devices/system/clocksource/clocksource0/available_clocksource

  [Regression Potential]
   * The regression potential is low. Upstream code still maintains this
     behaviour of skipping calibration on guests, and tsc code verifies if
     the frequency is known before registering the clocksource

   * Patches were verified against the above test case, and also tested
     with stress-ng in both nested and non-nested guest scenarios

  [Fix]
   * By applying the upstream commits [0] [1], we skip refined calibration and
     register TSC as a clocksource directly if its frequency is known (via
     MSR or CPUID)

   * Cosmic onwards (kernel 4.18+) are already fixed

  [0] For Xenial only - https://git.kernel.org/linus/47c95a46d0f
  [1] https://git.kernel.org/linus/e10f78050323

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

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

[Kernel-packages] [Bug 1826165] Re: linux-azure: 4.18.0-1017.17~18.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => 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
  
  derivatives: bug 1826164 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826166
  phase: Testing
  phase-changed: Monday, 29. April 2019 16: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
-   snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected 
channel(s):
- arch=amd64:channel=18/candidate:rev=54'
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1017.17~18.04.1 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

  derivatives: bug 1826164 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826166
  phase: Testing
  phase-changed: Monday, 29. April 2019 16: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
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

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

--- Comment From mranw...@us.ibm.com 2019-04-29 14:42 EDT---
An initial test looks good, thank you!

mranweil@ltc-wspoon5:~$ dpkg --list |grep linux-image-4\.15\.0-49
ii  linux-image-4.15.0-49-generic4.15.0-49.53   
ppc64el  Signed kernel image generic
mranweil@ltc-wspoon5:~$ cat /proc/version
Linux version 4.15.0-49-generic (buildd@bos02-ppc64el-016) (gcc version 7.3.0 
(Ubuntu 7.3.0-16ubuntu3)) #53-Ubuntu SMP Fri Apr 26 06:44:38 UTC 2019
mranweil@ltc-wspoon5:~$ dmesg |grep count-cache-flush
[0.00] count-cache-flush: hardware assisted flush sequence enabled
mranweil@ltc-wspoon5:~$ grep -H . 
/sys/devices/system/cpu/vulnerabilities/spectre_v2
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Software count 
cache flush (hardware accelerated)
mranweil@ltc-wspoon5:~$ cat /proc/cpuinfo |head
processor   : 0
cpu : POWER9, altivec supported
clock   : 3683.00MHz
revision: 2.3 (pvr 004e 1203)

processor   : 1
cpu : POWER9, altivec supported
clock   : 3683.00MHz
revision: 2.3 (pvr 004e 1203)

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

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

Bug description:
  [IMPACT]
  Need to further address the Spectre v2 and Meltdown vulnerability in Power 
with software count cache flush Spectre v2 mitigation support for Power9 DD2.3, 
and additional Spectre/Meltdown related patches for Power9.

  [Fix]
  List of upstream patches identified by IBM in comment #4, #5, and #8.

  [Test]
  Pre-req: requires Power9 DD2.3 hardware.
  A test kernel is available in PPA ppa:ubuntu-power-triage/lp1822870 and the 
kernel was tested by IBM. Please see comment #11 and #14 for details.

  [REGRESSION POTENTIAL]
  The patches are isolated to the ppc64el architecture and does not impact 
generic code. ppc64el test kernel was tested by IBM and no regressions were 
reported.

  [OTHER INFO]
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs

[Kernel-packages] [Bug 1826911] [NEW] hns: fix socket accounting

2019-04-29 Thread dann frazier

Public bug reported:

[Impact]
It is possible for a socket to use more memory than permitted on systems using 
the hns network driver.

[Fix]
b1ccd4c0ab6ef net: hns: fix skb->truesize underestimation

[Test Case]
Regression tested only.

[Regression Risk]
Trivial fix local to a single driver only used on ARM servers based on the 
Hi1616 SoC.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  hns: fix socket accounting

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

Bug description:
  [Impact]
  It is possible for a socket to use more memory than permitted on systems 
using the hns network driver.

  [Fix]
  b1ccd4c0ab6ef net: hns: fix skb->truesize underestimation

  [Test Case]
  Regression tested only.

  [Regression Risk]
  Trivial fix local to a single driver only used on ARM servers based on the 
Hi1616 SoC.

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

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

[Kernel-packages] [Bug 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue

2019-04-29 Thread Heikki Hannikainen

kernel.org bug ticket, showing similar crashes on 4.9 and 4.19 kernels:
https://bugzilla.kernel.org/show_bug.cgi?id=202669

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

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

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  
  After upgrading our server to this Kernel we experience frequent Kernel 
panics (Attachment).
  Every 3 hours. 
  Our machine has a throuput of about 600 Mbits/s 
  The Panics are around the area of ip6_expire_frag_queue.

__pskb_pull_tail
ip6_dst_lookup_tail
_decode_session6
__xfrm_decode_session
icmpv6_route_lookup
icmp6_send

  
  It seems similar to Bug Report in Debian.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488

  According to the bug finder of above bug it also occurred after using a 
Kernel with the change of
  rewrite ip6_expire_frag_queue()

  Intermediate solution. We disabled IPv6 on this machine to avoid further 
Panics.
  Please let me know what information is missing. The ubuntu-bug linux was 
send. And I hope it is attached to this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-145-generic 4.4.0-145.171
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Apr 14 11:40:11 2019
  InstallationDate: Installed on 2018-03-18 (391 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 21:04 seq
   crw-rw 1 root audio 116, 33 Apr 12 21:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1
  InstallationDate: Installed on 2018-03-18 (393 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-145-generic N/A
   linux-backports-modules-4.4.0-145-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-145-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (176 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd10/08/2012:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr1.2:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue

2019-04-29 Thread Heikki Hannikainen

** Attachment added: "5 kernel stack traces of crashes on 4.4.0-145 and -146, 
on 4 different hardware nodes"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+attachment/5260024/+files/hessu-ipv6_expire_frag_queue-crashes.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/1824687

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  
  After upgrading our server to this Kernel we experience frequent Kernel 
panics (Attachment).
  Every 3 hours. 
  Our machine has a throuput of about 600 Mbits/s 
  The Panics are around the area of ip6_expire_frag_queue.

__pskb_pull_tail
ip6_dst_lookup_tail
_decode_session6
__xfrm_decode_session
icmpv6_route_lookup
icmp6_send

  
  It seems similar to Bug Report in Debian.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488

  According to the bug finder of above bug it also occurred after using a 
Kernel with the change of
  rewrite ip6_expire_frag_queue()

  Intermediate solution. We disabled IPv6 on this machine to avoid further 
Panics.
  Please let me know what information is missing. The ubuntu-bug linux was 
send. And I hope it is attached to this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-145-generic 4.4.0-145.171
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Apr 14 11:40:11 2019
  InstallationDate: Installed on 2018-03-18 (391 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 21:04 seq
   crw-rw 1 root audio 116, 33 Apr 12 21:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1
  InstallationDate: Installed on 2018-03-18 (393 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-145-generic N/A
   linux-backports-modules-4.4.0-145-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-145-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (176 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd10/08/2012:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr1.2:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1826358] Re: linux: 4.15.0-49.53 -proposed tracker

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

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

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

** 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
  
  backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe)
  derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 
1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 
1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), 
bug 1826348 (linux-oracle), bug 1826350 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 29. April 2019 16: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
-   snap-release-to-beta: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=armhf:channel=18/beta'
-   snap-release-to-edge: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=armhf:channel=18/edge'
+   snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.15.0-49.53 -proposed tracker

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

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

  backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe)
  derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 
1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 
1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), 
bug 1826348 (linux-oracle), bug 1826350 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 29. April 2019 16: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
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826165] Re: linux-azure: 4.18.0-1017.17~18.04.1 -proposed tracker

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

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

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => 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
  
  derivatives: bug 1826164 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826166
  phase: Testing
  phase-changed: Monday, 29. April 2019 16: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
-   snap-release-to-beta: 'Pending -- snap azure-kernel not in expected 
channel(s):
- arch=amd64:channel=18/beta'
-   snap-release-to-edge: 'Pending -- snap azure-kernel not in expected 
channel(s):
- arch=amd64:channel=18/edge'
+   snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected 
channel(s):
+ arch=amd64:channel=18/candidate:rev=54'
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1017.17~18.04.1 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

  derivatives: bug 1826164 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826166
  phase: Testing
  phase-changed: Monday, 29. April 2019 16: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
snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected 
channel(s):
  arch=amd64:channel=18/candidate:rev=54'
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue

2019-04-29 Thread Heikki Hannikainen

I have had this crash, with the ip6_expire_frag_queue stack trace, more
than 18 times since 2019-04-16 on more than 10 different servers in 8
different countries.  There have been some more crashes, but from these
ones the panic dump managed to go out to a remote syslog server where
it's easy to grep. Crash count by kernel version; these are on both
trusty and xenial:

2 crashes: 4.4.0-144-generic #170~14.04.1-Ubuntu
8 crashes: 4.4.0-145-generic #171-Ubuntu
8 crashes: 4.4.0-146-generic #172-Ubuntu

Downgrading to 4.4.0-143 now, as that build does not seem to have the
"ipv6: frags: rewrite ip6_expire_frag_queue()" change; it first appears
in 4.4.0-144-generic image.  I think by tomorrow it's clear whether that
kernel is stable as we're now having multiple crashes per day (last
crash 50 minutes ago).

These are routers running NAT & firewall & some applications, with
substantial IPv6 traffic.

Interestingly the crashes only happen on bare hardware. We have a much
larger number of VMs doing the same thing, most of them now running 
4.4.0-146, and none of them have crashed like this.  The hardware instances
do have a larger number of CPU cores, the VMs only have 2 or 4.

I am also seeing crashes on 4.15.0-48-generic hwe kernel running on xenial,
but no stack trace to show yet.

Attaching kernel stack trace file containing several crashes on various
servers (hessu-ipv6_expire_frag_queue-crashes.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/1824687

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  
  After upgrading our server to this Kernel we experience frequent Kernel 
panics (Attachment).
  Every 3 hours. 
  Our machine has a throuput of about 600 Mbits/s 
  The Panics are around the area of ip6_expire_frag_queue.

__pskb_pull_tail
ip6_dst_lookup_tail
_decode_session6
__xfrm_decode_session
icmpv6_route_lookup
icmp6_send

  
  It seems similar to Bug Report in Debian.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488

  According to the bug finder of above bug it also occurred after using a 
Kernel with the change of
  rewrite ip6_expire_frag_queue()

  Intermediate solution. We disabled IPv6 on this machine to avoid further 
Panics.
  Please let me know what information is missing. The ubuntu-bug linux was 
send. And I hope it is attached to this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-145-generic 4.4.0-145.171
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Apr 14 11:40:11 2019
  InstallationDate: Installed on 2018-03-18 (391 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 21:04 seq
   crw-rw 1 root audio 116, 33 Apr 12 21:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1
  InstallationDate: Installed on 2018-03-18 (393 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-145-generic N/A
   linux-backports-modules-4.4.0-145-generic  N/A
   linux-firmware 1.157

[Kernel-packages] [Bug 1826145] Re: linux-kvm: 5.0.0-1005.5 -proposed tracker

** 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: 1826150
- phase: Testing
- phase-changed: Monday, 29. April 2019 15:36 UTC
+ phase: Signoff
+ phase-changed: Monday, 29. April 2019 17:06 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

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

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

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: 1826150
  phase: Signoff
  phase-changed: Monday, 29. April 2019 17:06 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

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

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

[Kernel-packages] [Bug 1826358] Re: linux: 4.15.0-49.53 -proposed tracker

** 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
  
  backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe)
  derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 
1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 
1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), 
bug 1826348 (linux-oracle), bug 1826350 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 29. April 2019 16: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
-   snap-release-to-beta: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=18/beta
- arch=armhf:channel=18/beta arch=i386:channel=18/beta'
-   snap-release-to-edge: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=18/edge
- arch=armhf:channel=18/edge arch=i386:channel=18/edge'
+   snap-release-to-beta: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=armhf:channel=18/beta'
+   snap-release-to-edge: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=armhf:channel=18/edge'
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.15.0-49.53 -proposed tracker

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

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

  backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe)
  derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 
1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 
1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), 
bug 1826348 (linux-oracle), bug 1826350 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 29. April 2019 16: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
snap-release-to-beta: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=armhf:channel=18/beta'
snap-release-to-edge: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=armhf:channel=18/edge'
verification-testing: Ongoing -- testing in progress

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

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

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

2019-04-29 Thread you

I did read everything. tlc did not help (or maybe not so much). I'm
usually using my battery from 80/90% to 15/20% for 1h30/2h on linux.

I didnt try since a some time but as I remember I can reach 3h/3h30 on
windows.

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

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

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 595047]

2019-04-29 Thread mpartap

Can 'someone' please open a bounty on creation of a VM test case, f.e. with 
`vagrant` or `phoronix test suite`?
Basically, a way to reproduce and quantify the perceived/actual performance 
difference between
> Linux 2.6.17 Released 17 June, 2006
and
> Linux 5.0 Released Sun, 3 Mar 2019 
…

(In reply to Alex Efros from comment #666)
> Not as bad as years ago […]
> And that's on powerful and modern enough system with
> kernel 4.19.27, CPU i7-2600K @ 4.5GHz, RAM 24GB, and HDD 3TB […]
> This is annoying, and I remember time before
> 12309 when rtorrent without any throttling won't make mplayer to freeze on
> less powerful hardware.

Oh yeah, this... i can clearly remember back then when on a then mid-
range machine with a lot of compiling (gentoo => 100% cpu �[U+1F923]�)
and filesystem work, VLC used to play an HD video stream even under
heavy load without any hiccups and micro-stuttering.. It was impressive
at the time.. and then.. it broke �[U+1F928]�

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

Title:
  Frequent swapping causes system to hang

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

Bug description:
  Periodically I notice my system slows to a near stand still, and the
  hard drive light is constantly going.  This seems to be a massive
  amount of disk i/o and it lasts for a long time (lets say 30 mins to
  put a number on it).  I installed and ran iotop (`iotop -a`) and it
  seems to point to jbd2.  From what I can see jbd2 is related to ext4
  journaling, but I cannot figure out how to kill this operation.  It
  might even be a red herring because I have also stopped the disk
  activity by kill either chromium or firefox.  I need to understand
  what else I can do to troubleshoot this.

  $ lsb_release -rd
  Description:  Ubuntu maverick (development branch)
  Release:  10.10

  Up-to-date as of 16th June 2010.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pgoodall   1372 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x5644 irq 44'
 Mixer name : 'Realtek ALC272X'
 Components : 'HDA:10ec0272,1025022c,0011'
 Controls  : 14
 Simple ctrls  : 8
  DistroRelease: Ubuntu 10.10
  Frequency: Once a day.
  HibernationDevice: RESUME=UUID=145f27a9-859a-4987-8132-ac878c832747
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
  MachineType: Acer AO531h
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic 
root=UUID=11f96f8b-5e04-4e20-a201-0fa5d0fc07fa ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
  Regression: Yes
  RelatedPackageVersions: linux-firmware 1.37
  Reproducible: No
  Tags: maverick ubuntu-une kconfig regression-potential needs-upstream-testing
  Uname: Linux 2.6.35-6-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 12/22/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3304
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3304:bd12/22/2009:svnAcer:pnAO531h:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: AO531h
  dmi.product.version: 1
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 336652]

2019-04-29 Thread mpartap

Can 'someone' please open a bounty on creation of a VM test case, f.e. with 
`vagrant` or `phoronix test suite`?
Basically, a way to reproduce and quantify the perceived/actual performance 
difference between
> Linux 2.6.17 Released 17 June, 2006
and
> Linux 5.0 Released Sun, 3 Mar 2019 
…

(In reply to Alex Efros from comment #666)
> Not as bad as years ago […]
> And that's on powerful and modern enough system with
> kernel 4.19.27, CPU i7-2600K @ 4.5GHz, RAM 24GB, and HDD 3TB […]
> This is annoying, and I remember time before
> 12309 when rtorrent without any throttling won't make mplayer to freeze on
> less powerful hardware.

Oh yeah, this... i can clearly remember back then when on a then mid-
range machine with a lot of compiling (gentoo => 100% cpu �[U+1F923]�)
and filesystem work, VLC used to play an HD video stream even under
heavy load without any hiccups and micro-stuttering.. It was impressive
at the time.. and then.. it broke �[U+1F928]�

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

Title:
  Poor system performance under I/O load

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

Bug description:
  This bug seems to particularly affect the Dell Latitude D420, D430 and
  (from the kernel.org bug) at least the D830 laptop models; but others
  have been reported.

  Under I/O load, which need not be excessive - running usb-creator or
  even just checking one's email - the system performs remarkably
  poorly, far less than other laptop users see.  It can often take
  minutes to open a window, and sometimes the screen isn't repainted.
  Certainly most applications are "dimmed" by Compiz under I/O.

  It also appears to massively negatively affect boot performance, with
  one core spending its entire time in I/O wait - something we don't see
  elsewhere.

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

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

[Kernel-packages] [Bug 1826165] Re: linux-azure: 4.18.0-1017.17~18.04.1 -proposed tracker

** 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 => In Progress

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

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

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

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

** Changed in: kernel-sru-workflow/automated-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
  
  derivatives: bug 1826164 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826166
- phase: Promote to Proposed
- phase-changed: Monday, 29. April 2019 11:41 UTC
+ phase: Testing
+ phase-changed: Monday, 29. April 2019 16:17 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
+   snap-release-to-beta: 'Pending -- snap azure-kernel not in expected 
channel(s):
+ arch=amd64:channel=18/beta'
+   snap-release-to-edge: 'Pending -- snap azure-kernel not in expected 
channel(s):
+ arch=amd64:channel=18/edge'
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1017.17~18.04.1 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

  derivatives: bug 1826164 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826166
  phase: Testing
  phase-changed: Monday, 29. April 2019 16: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
snap-release-to-beta: 'Pending -- snap azure-kernel not in expected 
channel(s):
  arch=amd64:channel=18/beta'
snap-release-to-edge: 'Pending -- snap azure-kernel not in expected 
channel(s):
  arch=amd64:channel=18/edge'
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working

Hello Frank, or anyone else affected,

Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

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

Title:
  Customize 'crashkernel' parameter is not properly working

Status in Ubuntu on IBM z Systems:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in makedumpfile source package in Cosmic:
  Fix Committed
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  SRU Justification:
  --

  [Impact]

   * While installing makedumpfile the "crashkernel=" argument is not
  properly set, hence dump is not triggered on reboot.

   * Means the triggering of dumpfiles is currently not possible using
  makedumpfile.

   * Dumpfiles are obviously only needed in rare cases, but if they are
  needed (e.g. in production environments) the situation is usually
  critical.

   * Hence fixing this is needed to allow post-mortem analysis of a
  dumps.

   * The provided shell code snippet provides a fixed sed statement that
  makes sure that the kernel parameter is propoerly set.

  [Test Case]

   * Create and boot a s390x (KVM virtual) machine

   * Install kdump-tools and makedumpfile
     Select 'yes' on question 'Should kdump-tools be enabled by default?' 
during installation

   * [ Reboot system ]

   * Look for crashkernel line in zipl boot-loader
     grep crashkernel /etc/zipl.conf
     crashkernel line is missing in case this bug still exists
     one or more lines like this should be given:
     parameters = root=UUID=5ed8f208-adce-4fad-b1a6-feb5e8732d89 
crashkernel=196M

   * One may further trigger a crash (for a full positiv test)
     sudo -s
     sysctl -w kernel.sysrq=1
     echo c > /proc/sysrq-trigger
     (in case this bug still exists the system will not come up again - check 
console in parallel)
 Finally dump files should be visible in /var/crash

  [Regression Potential]

   * The regression potential is very low, since:

   * it's limited to the zipl boot loader configuration file only
     and this means again it's on the s390x platform only (IBM Z)

   * kdump-tools and makedumpfile are not installed by default and only used in 
debug situations
     hence only system where the package(s) got manually installed get updated

   * The function is today broken anyway, hence it can actually only get
  better

   * I successfully verified this in disco.
  _

  Trying to use crashdump especially in a KVM machine.
  Installation looks fine and the reboot is triggered.
  But it does not work because the kernel does not have a 'crashkernel=' 
parameter.
  Nothing in /proc/cmdline:
  $ cat /proc/cmdline
  root=LABEL=cloudimg-rootfs

  Issue seems to be in adding the crashkernel line in this snippet:
  # Customize crashkernel= value according to architecture
  ARCH="$(arch)"
  DEF_PRESET="384M-:128M"
  case "$ARCH" in
     s390x)
    HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
    if test -z "$HAS_CRASHKERNEL"; then
   sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}" 
/etc/zipl.conf
   zipl
    fi
   CIO_IGNORE="$(cio_ignore -u -k)"
   sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
   sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}" 
$INITCONFFILE
  ;;
  esac

  (especially 1st sed stmt)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-s

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

Hello bugproxy, or anyone else affected,

Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

-- 
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:
  In Progress
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:
  New
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Fix Committed
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/+subscript

[Kernel-packages] [Bug 1811692] Re: udev coldplug will interrupt makedumpfile

Normally I should request a separate SRU bug for the 'backporting'
operation, but basically the test case here is fitting to check if the
backport works. So accepting those conditionally.

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

** Tags added: verification-needed-bionic

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

Title:
  udev coldplug will interrupt makedumpfile

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

Bug description:
  [Impact]
  During kdump on i386 systems, udev will restart kdump-tools, which will kill 
makedumpfile during dump capture, causing the system to reboot without 
capturing a dump.

  [Test case]
  After the fix, a dump could be captured on i386. Other arches were tested and 
worked just as fine.

  [Regression potential]
  Systems could fail to have a dump captured, but it was tested to not be the 
case.

  ===

  After introducing the udev rules to restart kdump-tools service when
  there is memory or cpu hotplug, it will be restarted during coldplug
  as well. This will cause the dump capture itself to be interrupted
  after a crash. When it is restarted and tries to dump again, it will
  find an existing dump file and will fail to dump.

  My proposed solution is to use a different systemd service for the
  real capture.

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

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

[Kernel-packages] [Bug 1811692] Please test proposed package

Hello Thadeu, or anyone else affected,

Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  udev coldplug will interrupt makedumpfile

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

Bug description:
  [Impact]
  During kdump on i386 systems, udev will restart kdump-tools, which will kill 
makedumpfile during dump capture, causing the system to reboot without 
capturing a dump.

  [Test case]
  After the fix, a dump could be captured on i386. Other arches were tested and 
worked just as fine.

  [Regression potential]
  Systems could fail to have a dump captured, but it was tested to not be the 
case.

  ===

  After introducing the udev rules to restart kdump-tools service when
  there is memory or cpu hotplug, it will be restarted during coldplug
  as well. This will cause the dump capture itself to be interrupted
  after a crash. When it is restarted and tries to dump again, it will
  find an existing dump file and will fail to dump.

  My proposed solution is to use a different systemd service for the
  real capture.

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

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

[Kernel-packages] [Bug 1826346] Re: linux-oracle: 4.15.0-1012.14~16.04.1 -proposed tracker

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

** 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: 1826348
  phase: Testing
  phase-changed: Monday, 29. April 2019 14:13 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
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1012.14~16.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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

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: 1826348
  phase: Testing
  phase-changed: Monday, 29. April 2019 14:13 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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826340] Re: linux-gcp: 4.15.0-1031.33 -proposed tracker

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

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => 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
  
  backports: bug 1826339 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 14:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1031
regression-testing: Ongoing -- testing in progress
-   snap-release-to-candidate: 'Pending -- snap gcp-kernel not in expected 
channel(s):
- arch=amd64:channel=18/candidate:rev=57'
+   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1031.33 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

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

  backports: bug 1826339 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 14:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1031
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

Hello bugproxy, or anyone else affected,

Accepted makedumpfile into cosmic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.10.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

-- 
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:
  In Progress
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:
  New
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Fix Committed
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-sys

[Kernel-packages] [Bug 1811692] Re: udev coldplug will interrupt makedumpfile

Hello Thadeu, or anyone else affected,

Accepted makedumpfile into cosmic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.10.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: makedumpfile (Ubuntu Cosmic)
   Status: New => Fix Committed

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

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

Title:
  udev coldplug will interrupt makedumpfile

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

Bug description:
  [Impact]
  During kdump on i386 systems, udev will restart kdump-tools, which will kill 
makedumpfile during dump capture, causing the system to reboot without 
capturing a dump.

  [Test case]
  After the fix, a dump could be captured on i386. Other arches were tested and 
worked just as fine.

  [Regression potential]
  Systems could fail to have a dump captured, but it was tested to not be the 
case.

  ===

  After introducing the udev rules to restart kdump-tools service when
  there is memory or cpu hotplug, it will be restarted during coldplug
  as well. This will cause the dump capture itself to be interrupted
  after a crash. When it is restarted and tries to dump again, it will
  find an existing dump file and will fail to dump.

  My proposed solution is to use a different systemd service for the
  real capture.

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

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

[Kernel-packages] [Bug 1826334] Re: linux-raspi2: 4.15.0-1035.37 -proposed tracker

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

** 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: 1826358
  phase: Ready for Testing
  phase-changed: Monday, 29. April 2019 15:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.15.0-1035.37 -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:
  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 snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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: 1826358
  phase: Ready for Testing
  phase-changed: Monday, 29. April 2019 15:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826343] Re: linux-kvm: 4.15.0-1033.33 -proposed tracker

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

** 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: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 14: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
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.15.0-1033.33 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  New

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: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 14: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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826125]

2019-04-29 Thread Lakshminarayana-vudum

Stan, any help here? I see hotplug events in dmesg.

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  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+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working

Hello Frank, or anyone else affected,

Accepted makedumpfile into cosmic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.10.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

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

Title:
  Customize 'crashkernel' parameter is not properly working

Status in Ubuntu on IBM z Systems:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in makedumpfile source package in Cosmic:
  Fix Committed
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  SRU Justification:
  --

  [Impact]

   * While installing makedumpfile the "crashkernel=" argument is not
  properly set, hence dump is not triggered on reboot.

   * Means the triggering of dumpfiles is currently not possible using
  makedumpfile.

   * Dumpfiles are obviously only needed in rare cases, but if they are
  needed (e.g. in production environments) the situation is usually
  critical.

   * Hence fixing this is needed to allow post-mortem analysis of a
  dumps.

   * The provided shell code snippet provides a fixed sed statement that
  makes sure that the kernel parameter is propoerly set.

  [Test Case]

   * Create and boot a s390x (KVM virtual) machine

   * Install kdump-tools and makedumpfile
     Select 'yes' on question 'Should kdump-tools be enabled by default?' 
during installation

   * [ Reboot system ]

   * Look for crashkernel line in zipl boot-loader
     grep crashkernel /etc/zipl.conf
     crashkernel line is missing in case this bug still exists
     one or more lines like this should be given:
     parameters = root=UUID=5ed8f208-adce-4fad-b1a6-feb5e8732d89 
crashkernel=196M

   * One may further trigger a crash (for a full positiv test)
     sudo -s
     sysctl -w kernel.sysrq=1
     echo c > /proc/sysrq-trigger
     (in case this bug still exists the system will not come up again - check 
console in parallel)
 Finally dump files should be visible in /var/crash

  [Regression Potential]

   * The regression potential is very low, since:

   * it's limited to the zipl boot loader configuration file only
     and this means again it's on the s390x platform only (IBM Z)

   * kdump-tools and makedumpfile are not installed by default and only used in 
debug situations
     hence only system where the package(s) got manually installed get updated

   * The function is today broken anyway, hence it can actually only get
  better

   * I successfully verified this in disco.
  _

  Trying to use crashdump especially in a KVM machine.
  Installation looks fine and the reboot is triggered.
  But it does not work because the kernel does not have a 'crashkernel=' 
parameter.
  Nothing in /proc/cmdline:
  $ cat /proc/cmdline
  root=LABEL=cloudimg-rootfs

  Issue seems to be in adding the crashkernel line in this snippet:
  # Customize crashkernel= value according to architecture
  ARCH="$(arch)"
  DEF_PRESET="384M-:128M"
  case "$ARCH" in
     s390x)
    HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
    if test -z "$HAS_CRASHKERNEL"; then
   sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}" 
/etc/zipl.conf
   zipl
    fi
   CIO_IGNORE="$(cio_ignore -u -k)"
   sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
   sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}" 
$INITCONFFILE
  ;;
  esac

  (especially 1st sed stmt)

To manage notifications about this bug go to:
https://bugs.laun

[Kernel-packages] [Bug 1826336] Re: linux-oem: 4.15.0-1037.42 -proposed tracker

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

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

** 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: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 14:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   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

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

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

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

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: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 14:09 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

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

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

[Kernel-packages] [Bug 1826348] Re: linux-oracle: 4.15.0-1012.14 -proposed tracker

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

** 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
  
  backports: bug 1826346 (xenial/linux-oracle)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 12:10 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
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1012.14 -proposed tracker

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

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

  backports: bug 1826346 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Testing
  phase-changed: Monday, 29. April 2019 12:10 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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1826338] Re: linux-aws: 4.15.0-1038.40 -proposed tracker

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

** 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
  
  backports: bug 1826337 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Testing
  phase-changed: Friday, 26. April 2019 18:41 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

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

Title:
  linux-aws: 4.15.0-1038.40 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

  backports: bug 1826337 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Testing
  phase-changed: Friday, 26. April 2019 18:41 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

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

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

[Kernel-packages] [Bug 1826166] Re: linux-azure: 4.18.0-1017.17 -proposed tracker

** 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 => In Progress

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

** 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
  
  backports: bug 1826165 (bionic/linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826171
- phase: Promote to Proposed
- phase-changed: Monday, 29. April 2019 11:37 UTC
+ phase: Testing
+ phase-changed: Monday, 29. April 2019 16:09 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
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1017.17 -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:
  Confirmed
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:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  New

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

  backports: bug 1826165 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826171
  phase: Testing
  phase-changed: Monday, 29. April 2019 16:09 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

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

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

[Kernel-packages] [Bug 1826335] Re: linux-snapdragon: 4.15.0-1052.56 -proposed tracker

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

** 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: 1826358
  phase: Promote to Proposed
  phase-changed: Monday, 29. April 2019 10:39 UTC
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
promote-to-proposed: Stalled -- packages are in the wrong component
+   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-snapdragon: 4.15.0-1052.56 -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 promote-to-proposed series:
  Incomplete
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 snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  New

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: 1826358
  phase: Promote to Proposed
  phase-changed: Monday, 29. April 2019 10:39 UTC
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
promote-to-proposed: Stalled -- packages are in the wrong component
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1812809] Re: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC