[Kernel-packages] [Bug 1807264] Re: Ubuntu 18.04 Video Crash on Suspend/Hibernate
Please try mainline kernel. Also, what's the last working kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807264 Title: Ubuntu 18.04 Video Crash on Suspend/Hibernate Status in linux package in Ubuntu: Confirmed Bug description: After updating to 18.04 when the system automatically suspends/hibernates after non-use, the screen goes black, but will not wake up by taping the space bar, nor does it display the hibernation screen. Additionally, I'm using two screens the laptop and an external monitor connected with the Mini Display port. When required to come out of suspend, each screen behaves differently. The laptop screen flashes while the external monitor may show any of these: 1) background screen image with no tool bars or menu; 2) remains black; or 3) shows a gray image. The only way to recover is to reboot, either by holding the power button or Ctrl-F1 to log back into the system and use the reboot command; only the external monitor will recover to a terminal screen. Upgrading the kernel from 4.15 thru 4.19 does not change the suspend/hibernation issue. It seems to be video related issue, since HDMI port reacts differently than the Mini Display port, in that device settings do not operate the same and changing the settings can cause the same type of screen crash. Additionally, trying NVIDIA drivers will help with the suspend/hibernation problem and allows the hibernation screen to show, but is not a cure. Sometimes the NVIDIA drivers will allow it to come back from hibernation and sometimes not. My suspicion is that the drivers are not correct for the Intel video card. I am also flummoxed by the fact that I cannot control suspend/hibernation. There is no obvious way to keep the system from suspending. Screen lock is OFF. Automatic suspend is OFF. Power button suspend is OFF. There needs to be more control; the ability to eliminate any and all suspend operations is a must! With this type of control, I could have kept if from suspending until a fix is generated. Reports are as follows: - lspci: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:04.0 Signal processing controller: Intel Corporation Haswell-ULT Thermal Subsystem (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 00:1f.6 Signal processing controller: Intel Corporation 8 Series Thermal (rev 04) 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) - ubuntu-bug linux: Problem in linux-image-4.19.17-041907-generic cannot be reported, this report is about a package that is not installed - cat /proc/version_signature > version.log: cat: /proc/version_signature: No such file or directory - sudo lspci -vnvn > lspci-vnvn.log: (no response) - lsb_release -rd: Ubuntu 18.04 LTS - apt-cache policy pkgname: N: Unable to locate package pkgname - sudo lshw -C display; uname -a; lsb_release -a; sudo dmidecode -t 1: *-display description: VGA compatible controller product: Haswell-ULT Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:42 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) memory:c-d Linux tablet3 4.19.7-041907-generic #201812052010 SMP Wed Dec 5 20:11:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-10-31 (1497 days ago) Inst
[Kernel-packages] [Bug 1819028] Re: Intel 9260 WiFi adapter doesn't work on B450 motherboard
Please attach 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/1819028 Title: Intel 9260 WiFi adapter doesn't work on B450 motherboard Status in linux package in Ubuntu: Incomplete Bug description: Hi, I know this has been a well discussed issue on Linux forums, but I am having extreme issues maintaining the built-in Intel WiFi in my motherboard, it resets everytime I update my distros (Ubuntu 18.04 and Linux Mint Cinnamon 18.3). My best fix for it is following the guide at [https://askubuntu.com/questions/1038242/no-wifi-option-on- ubuntu-18-04-and-16-04]. I am wanting to know if there is a way to make this process more streamlined for users as this affects many and is a hassle to maintain properly. I know this has been addressed before with Ryzen CPUs but this shouldn't have to be necessary if the driver is baked into the kernel as this is quite frustrating for any user to go through, as it requires what is causing the problem to fix - a network connection. I don't mind if it's simpler to have a on/off feature like the Nvidia drivers have, as that is still a lot simpler than writing out a paragraphs of code. TL;DR I'm asking if changes could be added so that instead of needing a network connection (something that you can't have if the driver isn't built into/available through the distro) and writing a dissertation of code, they have a driver automatically work or a switch option like Broadcom and Nvidia have in this photo [https://linuxhint.com/wp-content/uploads/2017/11/driver-manager-1.png] I was referred here by the Linux Mint forum, please refer to the page in case any questions have already been answered there [https://forums.linuxmint.com/viewtopic.php?f=49&t=289358&e=1&view=unread#unread] My system is a AMD Ryzen 2700x B450 with built-in Intel 9260 WiFi, Linux Mint 18.3/Ubuntu 18.04 dual boot. Thanks, Bionicle159 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808886] Re: Microcode SW error detected. Restarting 0x0.
I think it's the same one as LP: #1808389. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1808886 Title: Microcode SW error detected. Restarting 0x0. Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: intel-microcode: Installed: 3.20180807a.0ubuntu0.18.04.1 Candidate: 3.20180807a.0ubuntu0.18.04.1 Version table: *** 3.20180807a.0ubuntu0.18.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.20180312.0~ubuntu18.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Version: Ubuntu 4.15.0-42.45-generic 4.15.18 Error: [ 3136.084499] rtsx_pci :06:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1 [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 source:0x [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: id=00e8 [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Transmitter ID) [ 3136.085694] pcieport :00:1d.0: device [8086:a335] error status/mask=1101/2000 [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First) [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6 [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0 [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0 [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2 [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1 [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2 [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1 [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2 [ 3166.625860] iwlwifi :00:14.3: 0x | data3 [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1 [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2 [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0 [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1 [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2 [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3 [ 3166.625944] iwlwifi :00:14.3: 0x | isr4 [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7 [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1 [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2 [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1 [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2 [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1 [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2 [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3 [ 3166.626194] iwlwifi :00:14.3: 0x0022 | umac major [ 3166.626199] iwlwi
[Kernel-packages] [Bug 1820948] Re: i40e xps management broken when > 64 queues/cpus
It's been reported by an external reporter and reproduced internally. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820948 Title: i40e xps management broken when > 64 queues/cpus Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: [Impact] Transmit packet steering (xps) settings don't work when the number of queues (cpus) is higher than 64. This is currently still an issue on the 4.15 kernel (Xenial -hwe and Bionic kernels). It was fixed in Intel's i40e driver version 2.7.11 and in 4.16-rc1 mainline Linux (i.e. Cosmic, Disco have fix). Fix - The following commit fixes this issue (as identified by Lihong Yang in discussion with Intel i40e team): "i40e: Fix the number of queues available to be mapped for use" Commit: bc6d33c8d93f520e97a8c6330b8910053d4f [Test Case] 1. Kernel version: Bionic/Xenial -hwe: any 4.15 kernel i40e driver version: 2.1.14-k Any system with > 64 CPUs 2. For any queue 0 - 63, you can read/set tx xps: echo > /sys/class/net/eth2/queues/tx-63/xps_cpus echo $? 0 cat /sys/class/net/eth2/queues/tx-63/xps_cpus 00,, But for any queue number > 63, we see this error: echo > /sys/class/net/eth2/queues/tx-64/xps_cpus echo: write error: Invalid argument cat /sys/class/net/eth2/queues/tx-64/xps_cpus cat: /sys/class/net/eth2/queues/tx-64/xps_cpus: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820948] [NEW] i40e xps management broken when > 64 queues/cpus
Public bug reported: [Impact] Transmit packet steering (xps) settings don't work when the number of queues (cpus) is higher than 64. This is currently still an issue on the 4.15 kernel (Xenial -hwe and Bionic kernels). It was fixed in Intel's i40e driver version 2.7.11 and in 4.16-rc1 mainline Linux (i.e. Cosmic, Disco have fix). Fix - The following commit fixes this issue (as identified by Lihong Yang in discussion with Intel i40e team): "i40e: Fix the number of queues available to be mapped for use" Commit: bc6d33c8d93f520e97a8c6330b8910053d4f [Test Case] 1. Kernel version: Bionic/Xenial -hwe: any 4.15 kernel i40e driver version: 2.1.14-k Any system with > 64 CPUs 2. For any queue 0 - 63, you can read/set tx xps: echo > /sys/class/net/eth2/queues/tx-63/xps_cpus echo $? 0 cat /sys/class/net/eth2/queues/tx-63/xps_cpus 00,, But for any queue number > 63, we see this error: echo > /sys/class/net/eth2/queues/tx-64/xps_cpus echo: write error: Invalid argument cat /sys/class/net/eth2/queues/tx-64/xps_cpus cat: /sys/class/net/eth2/queues/tx-64/xps_cpus: Invalid argument ** Affects: linux (Ubuntu) Importance: High Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: High Assignee: Nivedita Singhvi (niveditasinghvi) Status: Confirmed ** Tags: bionic ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Nivedita Singhvi (niveditasinghvi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820948 Title: i40e xps management broken when > 64 queues/cpus Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: [Impact] Transmit packet steering (xps) settings don't work when the number of queues (cpus) is higher than 64. This is currently still an issue on the 4.15 kernel (Xenial -hwe and Bionic kernels). It was fixed in Intel's i40e driver version 2.7.11 and in 4.16-rc1 mainline Linux (i.e. Cosmic, Disco have fix). Fix - The following commit fixes this issue (as identified by Lihong Yang in discussion with Intel i40e team): "i40e: Fix the number of queues available to be mapped for use" Commit: bc6d33c8d93f520e97a8c6330b8910053d4f [Test Case] 1. Kernel version: Bionic/Xenial -hwe: any 4.15 kernel i40e driver version: 2.1.14-k Any system with > 64 CPUs 2. For any queue 0 - 63, you can read/set tx xps: echo > /sys/class/net/eth2/queues/tx-63/xps_cpus echo $? 0 cat /sys/class/net/eth2/queues/tx-63/xps_cpus 00,, But for any queue number > 63, we see this error: echo > /sys/class/net/eth2/queues/tx-64/xps_cpus echo: write error: Invalid argument cat /sys/class/net/eth2/queues/tx-64/xps_cpus cat: /sys/class/net/eth2/queues/tx-64/xps_cpus: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818162] Re: arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout
= cosmic verification = After running cert: ubuntu@d06-4:~$ cat /proc/version Linux version 4.18.0-17-generic (buildd@bos02-arm64-075) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:57 UTC 2019 ubuntu@d06-4:~$ dmesg | grep CMD_SYNC ** 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/1818162 Title: arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] During heavy load, the following message may appear on the console of a HiSilicon D06 system: arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout This is due to a bug that can also impact system performance, as the CPU is blocked until the timeout occurs. [Test Case] The Ubuntu server certification test suite hits this pretty reliably during the stress-ng tests, although I haven't narrowed it down to exactly which test yet. [Fix] 0f02477d16980 iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout [Regression Risk] Limited to arm64 systems. This change has been upstream since 4.20 w/o any noticed regressions (based on lack of Fixes: commits). Regressions could manifest as a performance hit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Bug watch added: Linux Kernel Bug Tracker #202971 https://bugzilla.kernel.org/show_bug.cgi?id=202971 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 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 Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786752] Re: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)
We have upgraded to kernel v4.20.15 and its going to be more than a week, we are not seeing any more call traces in this kernel logs. We will watch for few more days and i will report back here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786752 Title: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from 14.04 to 18.04, we see very frequent warnings about negative refcnts in dst_release: [ 3117.882227] WARNING: CPU: 6 PID: 0 at /build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial ipmi_si [ 3117.882265] irqbypass intel_cstate mei_me mei ioatdma acpi_pad intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel nf_conntrack iptable_filter ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 ttm crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp hid mxm_wmi cryptd [ 3117.882309] drm libahci megaraid_sas pps_core mdio wmi [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW 4.15.0-30-generic #32-Ubuntu [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS SE5C610.86B.01.01.0022.062820171903 06/28/2017 [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246 [ 3117.882322] RAX: RBX: 90de4000 RCX: 1924 [ 3117.882323] RDX: RSI: 88d749ae6400 RDI: 88d655e96600 [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 0018 [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 88d655e96600 [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 88d7493dc000 [ 3117.882327] FS: () GS:88d77f38() knlGS: [ 3117.882327] CS: 0010 DS: ES: CR0: 80050033 [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 003606e0 [ 3117.882329] DR0: DR1: DR2: [ 3117.882330] DR3: DR6: fffe0ff0 DR7: 0400 [ 3117.882331] Call Trace: [ 3117.882332] [ 3117.882337] ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4] [ 3117.882339] nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4] [ 3117.882342] iptable_nat_ipv4_out+0x15/0x20 [iptable_nat] [ 3117.882347] nf_hook_slow+0x48/0xc0 [ 3117.882353] ip_output+0xd2/0xe0 [ 3117.882355] ? ip_fragment.constprop.44+0x80/0x80 [ 3117.882357] ip_forward_finish+0x49/0x70 [ 3117.882359] ip_forward+0x366/0x440 [ 3117.882361] ? ip_frag_mem+0x20/0x20 [ 3117.882362] ip_rcv_finish+0x129/0x430 [ 3117.882364] ip_rcv+0x28f/0x3a0 [ 3117.882366] ? inet_del_offload+0x40/0x40 [ 3117.882372] __netif_receive_skb_core+0x432/0xb40 [ 3117.882379] ? handle_edge_irq+0x7c/0x190 [ 3117.882384] ? irq_exit+0x67/0xc0 [ 3117.882391] ? do_IRQ+0x82/0xd0 [ 3117.882393] __netif_receive_skb+0x18/0x60 [ 3117.882395] ? __netif_receive_skb+0x18/0x60 [ 3117.882397] netif_receive_skb_internal+0x37/0xd0 [ 3117.882398] napi_gro_receive+0xc5/0xf0 [ 3117.882407] ixgbe_clean_rx_irq+0x446/0xe30 [ixgbe] [ 3117.882411] ixgbe_poll+0x256/0x710 [ixgbe] [ 3117.882413] ? do_IRQ+0x82/0xd0 [ 3117.882415] net_rx_action+0x140/0x3a0 [ 3117.882418] __do_softirq+0xdf/0x2b2 [ 3117.882419] irq_exit+0xb6/0xc0 [ 3117.882421] do_IRQ+0x82/0xd0 [ 3117.882423] common_interrupt+0x84/0x84 [
[Kernel-packages] [Bug 1776563]
to revive touchpad after 1.13 do: sudo modprobe -r i2c_hid sudo modprobe i2c_hid as for the wireless problem i ve opened a back report here: https://bugzilla.kernel.org/show_bug.cgi?id=202971 please get into the cc list if you have problems with the wireless -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 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 Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812163] Re: package linux-firmware 1.173.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1812163 Title: package linux-firmware 1.173.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux-firmware package in Ubuntu: Expired Bug description: ackage linux-firmware 1.173.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.3 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 Date: Thu Jan 17 00:53:58 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DpkgHistoryLog: Start-Date: 2019-01-17 00:53:03 Requested-By: yiannis (1001) Upgrade: gvfs-backends:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-bin:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gnome-software-plugin-snap:amd64 (3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), gnome-software:amd64 (3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), gvfs-libs:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-fuse:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), ubuntu-software:amd64 (3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), gvfs:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-common:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gnome-software-common:amd64 (3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), gvfs-daemons:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2) DuplicateSignature: package:linux-firmware:1.173.3 Processing triggers for hicolor-icon-theme (0.17-2) ... dpkg: error processing package linux-firmware (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2013-02-22 (2155 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: linux-firmware Title: package linux-firmware 1.173.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1812163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] Re: Unable to get right-click working on ThinkPad T480s
** Changed in: libinput Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in libinput: Fix Released Status in Linux: Unknown Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Triaged Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260
** Changed in: linux (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809483 Title: iwlwifi not working with Intel AC 9260 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: [ 22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 9260, REV=0x324 [ 22.208574] [ cut here ] [ 22.208575] kernel BUG at /build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425! [ 22.208578] invalid opcode: [#1] SMP NOPTI [ 22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi irqbypass uvcvideo mxm_wmi intel_wmi_thunderb olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) aesni_intel aes_x86_64 crypto_simd [ 22.208598] cryptd glue_helper drm_kms_helper syscopyarea sysfillrect input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci ipmi_msghandler video mac_hid [ 22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P OE 4.15.0-43-generic #46-Ubuntu [ 22.208605] Hardware name: Notebook P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018 [ 22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi] [ 22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286 [ 22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: e4b2e1c6ab60 [ 22.208612] RDX: 99b9b38b61a8 RSI: RDI: 99b9b8280078 [ 22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 007690c8 [ 22.208614] R10: R11: 99b9b8280050 R12: 99b9b828 [ 22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 99b9b38b61d0 [ 22.208615] FS: 7fb8c9ec9540() GS:99b9be30() knlGS: [ 22.208616] CS: 0010 DS: ES: CR0: 80050033 [ 22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 003606e0 [ 22.208618] DR0: DR1: DR2: [ 22.208619] DR3: DR6: fffe0ff0 DR7: 0400 [ 22.208619] Call Trace: [ 22.208623] _iwl_pcie_rx_init+0x252/0x710 [iwlwifi] [ 22.208626] iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi] [ 22.208631] ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm] [ 22.208635] iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi] [ 22.208639] iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm] [ 22.208640] ? 0xc198e000 [ 22.208644] iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm] [ 22.208647] ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm] [ 22.208650] ? iwl_wait_init_complete+0x20/0x20 [iwlmvm] [ 22.208654] iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm] [ 22.208657] ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm] [ 22.208660] _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi] [ 22.208663] iwl_opmode_register+0x75/0xe0 [iwlwifi] [ 22.208664] ? 0xc19e8000 [ 22.208668] iwl_mvm_init+0x38/0x1000 [iwlmvm] [ 22.208671] do_one_initcall+0x52/0x19f [ 22.208672] ? _cond_resched+0x19/0x40 [ 22.208674] ? kmem_cache_alloc_trace+0xa6/0x1b0 [ 22.208676] ? do_init_module+0x27/0x209 [ 22.208678] do_init_module+0x5f/0x209 [ 22.208679] load_module+0x191e/0x1f10 [ 22.208681] ? ima_post_read_file+0x96/0xa0 [ 22.208682] SYSC_finit_module+0xfc/0x120 [ 22.208683] ? SYSC_finit_module+0xfc/0x120 [ 22.208685] SyS_finit_module+0xe/0x10 [ 22.208686] do_syscall_64+0x73/0x130 [ 22.208688] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 22.208689] RIP: 0033:0x7fb8c99ef839 [ 22.208690] RSP: 002b:7ffecf171ea8 EFLAGS: 0246 ORIG_RAX: 0139 [ 22.208691] RAX: ffda RBX: 55c40d7462f0 RCX: 7fb8c99ef839 [ 22.208691] RDX: RSI: 55c40c09cd2e RDI: 0001 [ 22.2086
[Kernel-packages] [Bug 1819698] Re: linux-gcp: 4.15.0-1029.31 -proposed tracker
** Summary changed: - linux-gcp: 4.15.0-1029.30 -proposed tracker + linux-gcp: 4.15.0-1029.31 -proposed tracker -- 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/1819698 Title: linux-gcp: 4.15.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New 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 1819695 (xenial/linux-gcp) -- swm properties -- kernel-stable-master-bug: 1819716 phase: Packaging phase-changed: Monday, 18. March 2019 03:31 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] Re: Unable to get right-click working on ThinkPad T480s
** Bug watch added: gitlab.freedesktop.org/libinput/libinput/issues #177 https://gitlab.freedesktop.org/libinput/libinput/issues/177 ** Also affects: libinput via https://gitlab.freedesktop.org/libinput/libinput/issues/177 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in libinput: Unknown Status in Linux: Unknown Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Triaged Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820930] Re: some codecs stop working after S3
** Description changed: - need to cat /proc/asound/cardX/codecX to trigger it work again. + + To fix this bug, B/OEM-B/C needs only 1 patch, while v5.0-rc1 introduced + a new patch which affect this issue, so the DISCO needs 2 patches. + + [Impact] + After S3, some codecs (alc236, alc255, alc891 and some HDMI codec) stop + working, they can't detect jack plugging/unplugging or the audio device + can't show up in the gnome-sound-setting + + [Fix] + After S3, if it runs runtime_resume(), the codec works again. We change + the driver to let system_resume() trigger runtime_resume() + + [Test Case] + This issue is reported from OEM project, some codecs can't detect + jack pluggin/unplugging, some codecs can't show up in the UI, after + applying this patch, all related bugs are fixed. + + [Regression Potential] + Low. have tested on many machines (with this issue or without this issue), + all worked well. ** Tags added: originate-from-1817519 somerville ** Tags added: originate-from-1811173 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820930 Title: some codecs stop working after S3 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: To fix this bug, B/OEM-B/C needs only 1 patch, while v5.0-rc1 introduced a new patch which affect this issue, so the DISCO needs 2 patches. [Impact] After S3, some codecs (alc236, alc255, alc891 and some HDMI codec) stop working, they can't detect jack plugging/unplugging or the audio device can't show up in the gnome-sound-setting [Fix] After S3, if it runs runtime_resume(), the codec works again. We change the driver to let system_resume() trigger runtime_resume() [Test Case] This issue is reported from OEM project, some codecs can't detect jack pluggin/unplugging, some codecs can't show up in the UI, after applying this patch, all related bugs are fixed. [Regression Potential] Low. have tested on many machines (with this issue or without this issue), all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1820930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820930] 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 1820930 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/1820930 Title: some codecs stop working after S3 Status in linux package in Ubuntu: Incomplete Bug description: need to cat /proc/asound/cardX/codecX to trigger it work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814982] Re: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
Note: if the point release installers will pick up the 4.18 series kernel with the fix then I think a fix for cosmic will suffice vs. bionic also given the results. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814982 Title: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] The Ubuntu kernel is not currently bootable on various arm64 laptops (HP Envy x2, Asus NovaGo, Lenovo Miix 630, Lenovo Yoga C630, Samsung ...) because of EFI memory permissions/restrictions. The reason is explained in the commit supplied below. [Test Case] Install and boot Ubuntu on one of the above arm64 laptops. [Fix] Committed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e46c2a956215482418d7b315749fb1b6c6bc224 [Regression Risk] This commit adds support for an optional kernel command line parameter so there is minimal to no risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814982] Re: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
bionic linux-image-4.15.0-47-generic: - Tested with and without efi=novamap and didn't get past the EFI stub messages. cosmic linux-image-4.18.0-17-generic: - Tested with efi=novamap and the kernel booted and got quite far but then went blank, as expected but this is a good start; without efi=novamap it didn't get past the EFI stub messages. disco linux-image-5.0.0-8.9-generic: - Tested this one for fun, oddly this kernel did worse than 4.18 and didn't get past the kernel stubs either! ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic ** 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/1814982 Title: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] The Ubuntu kernel is not currently bootable on various arm64 laptops (HP Envy x2, Asus NovaGo, Lenovo Miix 630, Lenovo Yoga C630, Samsung ...) because of EFI memory permissions/restrictions. The reason is explained in the commit supplied below. [Test Case] Install and boot Ubuntu on one of the above arm64 laptops. [Fix] Committed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e46c2a956215482418d7b315749fb1b6c6bc224 [Regression Risk] This commit adds support for an optional kernel command line parameter so there is minimal to no risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820930] [NEW] some codecs stop working after S3
Public bug reported: need to cat /proc/asound/cardX/codecX to trigger it work again. ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820930 Title: some codecs stop working after S3 Status in linux package in Ubuntu: New Bug description: need to cat /proc/asound/cardX/codecX to trigger it work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.10.2 --- mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172) mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium * New upstream bugfix release. (LP: #1811225) - add missing gpu-id's. (LP: #1789924) * Cherry-picked from disco: Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev because GL/glcorearb.h and GL/glext.h started to depend on this header too (Closes: #914167). -- Timo Aaltonen Fri, 08 Feb 2019 19:12:58 +0200 ** Changed in: mesa (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Released Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.10.2 --- mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172) mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium * New upstream bugfix release. (LP: #1811225) - add missing gpu-id's. (LP: #1789924) * Cherry-picked from disco: Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev because GL/glcorearb.h and GL/glext.h started to depend on this header too (Closes: #914167). -- Timo Aaltonen Fri, 08 Feb 2019 19:12:58 +0200 ** Changed in: mesa (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.04.2 --- mesa (18.2.8-0ubuntu0~18.04.2) bionic; urgency=medium * Backport to bionic. mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172) mesa (18.2.8-0ubuntu0~18.04.1) bionic; urgency=medium * Backport to bionic. * intel-whl-aml-cfl-ids.diff: Dropped, upstream. mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium * New upstream bugfix release. (LP: #1811225) - add missing gpu-id's. (LP: #1789924) * Cherry-picked from disco: Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev because GL/glcorearb.h and GL/glext.h started to depend on this header too (Closes: #914167). -- Timo Aaltonen Sat, 09 Feb 2019 00:02:44 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.04.2 --- mesa (18.2.8-0ubuntu0~18.04.2) bionic; urgency=medium * Backport to bionic. mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172) mesa (18.2.8-0ubuntu0~18.04.1) bionic; urgency=medium * Backport to bionic. * intel-whl-aml-cfl-ids.diff: Dropped, upstream. mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium * New upstream bugfix release. (LP: #1811225) - add missing gpu-id's. (LP: #1789924) * Cherry-picked from disco: Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev because GL/glcorearb.h and GL/glext.h started to depend on this header too (Closes: #914167). -- Timo Aaltonen Sat, 09 Feb 2019 00:02:44 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
5.1 kernel cursor tearing at x-axis=0, however, take with a grain of salt as I don't have the newest Mesa, vulkin, etc. Perhaps someone can hack a HP or Lenovo bios and see what the differences are, as they have the same main board as us [metapod_rr]? Or just hack those bioses to work in these. Can't see why not, same board, same insyde crap bios? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 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 Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Distro I'm running is Fedora 29 on an A315-41. Now under 4.19 kernel, no ivrs args needed, Touchpad works, secure boot, WiFi, etc. works. Overall, the most stable this laptop has ever been. Kernel 4.20, softlocks immediately upon boot, need to add ivrs args back and acpi goes to physical flat. Touchpad still works. Now for living on the edge, vanilla mainline git 5.1x, still need ivrs args, touchpad does not work, and cursor tearing in middle half of screen. Ugh. This is more of a regression than 4.20 was. I had Debian Working with backported 4.18 and updated amd firmware blobs, I could never get Ubuntu to work at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 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 Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
After update to 1.13 my touchpad doesn't work in Linux. Not recommending -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 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 Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Soft lockups now occurs even with ivrs_table arguments in place. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 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 Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Manjaro 5.0.2 kernel can start without exotics with 1.13 bios. Wi-Fi firmware(ath10k), however, dies right after getting into DE. Interestingly - vulkan bugs with Vega 8 went away with this update. Hibernation works (but unbelievable slow and artifacting while processing). TurboBoost after hibernation works. WI-FI ressurected after waking up from hibernation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 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 Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
A315-41-RX8R here. With 1.13 still cannot boot into manjaro default 4.20 kernel without ivrs_table\noapic tricks. CPU soft lockup -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 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 Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820366] Re: network install of xenial 16.04 fails with linux-generic package error
Is downgrading to linux-image-4.4.0-142-generic a viable workaround in the meantime? We're also a full netinstall shop, and this bug is blocking all U16 deployments. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820366 Title: network install of xenial 16.04 fails with linux-generic package error Status in linux package in Ubuntu: Confirmed Bug description: network installing xenial ubuntu is failing for myself and other people (as seen on the #ubuntu irc channel). I had this issue both with and without preseed. I am using the latest netboot kernel and initrd files from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer- amd64/current/images/netboot/ ( I re-downloaded and checked the file digest). The latest version available from the above URL is 4.4.0-142 and the installer fails while installing 4.4.0-143. The following error messages seen during installation: Mar 16 01:20:12 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 16 01:20:12 in-target: linux-update-symlinks: not found Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: subprocess installed post-installation script returned error exit status 127 Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-modules-extra-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up intel-microcode (3.20180807a.0ubuntu0.16.04.1) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: intel-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up amd64-microcode (3.20180524.1~ubuntu0.16.04.2) ...^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: amd64-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-image-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-modules-extra-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-modules-extra-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M After having these issue with a preseed file, I started a PXE install without any preseed ( therefore answering the standard installer questions manually) but I still had the same error. I was told in the #ubuntu irc channel to set : d-i base-installer/kernel/image string linux-image-4.4.0-142-generic in my preseed file. This worked and the installer completed correctly without any failures. Previously my preseed file container: d-i base-installer/kernel/image string linux-generic but as I said above, even without a preseed file the error occured. One thought - shouldn't a 4.4.0-143 netboot kernel / initrd be
[Kernel-packages] [Bug 1168819] Re: 168c:0032 [Asus G75VX] Slow wireless with AR9485 ath9k
** No longer affects: linux (Ubuntu) ** Project changed: linux => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Medium => Undecided ** Changed in: linux (Ubuntu) Status: Fix Released => New ** Changed in: linux (Ubuntu) Remote watch: Linux Kernel Bug Tracker #49201 => None ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1168819 Title: 168c:0032 [Asus G75VX] Slow wireless with AR9485 ath9k Status in linux package in Ubuntu: Invalid Bug description: With the latest raring kernel image (linux-signed-image-3.8.0-18-generic) my wireless connection becomes very slow after a few minutes (ping to my AP increases from < 1ms to ~ 900ms). Kernel 3.8.0.17.27 is still fine, other wireless devices continue to work fine if the problem occurs. HW is AR9485 (ath9k) 1x1 802.11n in Asus G75VX laptop, AP is Asus RT-AC66U. ~ --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: #RESUME=UUID=8c98d3e1-50af-4c74-820b-e3f29cefc50c #RESUME=/dev/mapper/cryptswap1 InstallationDate: Installed on 2013-03-27 (17 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) MachineType: ASUSTeK COMPUTER INC. G75VX MarkForUpload: True NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=93525b3d-45ae-49d5-be79-e00da8ca123b ro bootchart=disable ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 RelatedPackageVersions: linux-restricted-modules-3.8.0-17-generic N/A linux-backports-modules-3.8.0-17-generic N/A linux-firmware1.105 Tags: raring Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-06 (8 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video dmi.bios.date: 02/27/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VX.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VX.206:bd02/27/2013:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VX 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/1168819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
** Tags added: cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
New
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
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.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
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/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1168819] [NEW] 168c:0032 [Asus G75VX] Slow wireless with AR9485 ath9k
You have been subscribed to a public bug: With the latest raring kernel image (linux-signed-image-3.8.0-18-generic) my wireless connection becomes very slow after a few minutes (ping to my AP increases from < 1ms to ~ 900ms). Kernel 3.8.0.17.27 is still fine, other wireless devices continue to work fine if the problem occurs. HW is AR9485 (ath9k) 1x1 802.11n in Asus G75VX laptop, AP is Asus RT-AC66U. ~ --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: #RESUME=UUID=8c98d3e1-50af-4c74-820b-e3f29cefc50c #RESUME=/dev/mapper/cryptswap1 InstallationDate: Installed on 2013-03-27 (17 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) MachineType: ASUSTeK COMPUTER INC. G75VX MarkForUpload: True NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=93525b3d-45ae-49d5-be79-e00da8ca123b ro bootchart=disable ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 RelatedPackageVersions: linux-restricted-modules-3.8.0-17-generic N/A linux-backports-modules-3.8.0-17-generic N/A linux-firmware1.105 Tags: raring Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-06 (8 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video dmi.bios.date: 02/27/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VX.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VX.206:bd02/27/2013:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected latest-bios-206 needs-bisect needs-upstream-testing needs-wifi-debug raring regression-release third-party-packages -- 168c:0032 [Asus G75VX] Slow wireless with AR9485 ath9k https://bugs.launchpad.net/bugs/1168819 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Just for the record - 18.10 with 4.18.0-16-generic has this bug as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
New
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
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.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
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/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818747] Re: Crash in nvme_irq_check() when using threaded interrupts
** 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/1818747 Title: Crash in nvme_irq_check() when using threaded interrupts Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] kernel crashes under load w/ nvme.use_threaded_interrupts=1 [Test Case] Boot w/ nvme.use_threaded_interrupts=1 sudo fio -name=randread -numjobs=8 -filename=/dev/nvme0n1 -rw=randread -ioengine=libaio -direct=1 -iodepth=64 -sync=0 -norandommap -group_reporting -runtime=300 -time_based -bs=4k [ 284.756476] CPU: 0 PID: 1047 Comm: irq/97-nvme0q1 Not tainted 4.18.0-15-generic #16~18.04.1-Ubuntu [ 284.765420] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.13.01 02/14/2019 [ 284.773930] pstate: 00400089 (nzcv daIf +PAN -UAO) [ 284.778711] pc : nvme_irq_check+0x30/0x48 [nvme] [ 284.783319] lr : __handle_irq_event_percpu+0x68/0x228 [ 284.788356] sp : 08003e70 [Fix] dcca166272722 nvme-pci: fix out of bounds access in nvme_cqe_pending [Regression Risk] Restricted to systems w/ NVMe. There are no upstream patches marked as Fixing the upstream change, which suggests it is not yet know to introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820685] Re: Wrong resolution during boot
After some reading on internet I decided yesterday to install the nvidia diverse in package nvidia-driver-390. This resulted in a non-working graphic display. So I had to restore my installed packages and remove the nvidia-driver-390 package. When rebooting the initial screen showed the expected graphic resolution instead of a terminal like screen. I still don't quite understand what happened. nvidia-settings? or graphic card which has gotten wrong commands from previous installed driver? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820685 Title: Wrong resolution during boot Status in linux package in Ubuntu: Incomplete Bug description: When booting the startup screen is in low resolution while before it was in high resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 18:04:57 2019 DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b] InstallationDate: Installed on 2018-01-04 (437 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK COMPUTER INC. CM6870 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago) dmi.bios.date: 12/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6870 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: CM6870 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Sep 26 20:09:04 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
For me on a DELL Latitude E5550 it seems the issue is solved since update to 4.18.0-16-generic (kubuntu). Running for a week now with several suspend/resume cycles - no more frost. Spring is coming :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819028] Re: Intel 9260 WiFi adapter doesn't work on B450 motherboard
Sorry for the late replies, I've got a lot on at college and won't be able to give snappy responses. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819028 Title: Intel 9260 WiFi adapter doesn't work on B450 motherboard Status in linux package in Ubuntu: Incomplete Bug description: Hi, I know this has been a well discussed issue on Linux forums, but I am having extreme issues maintaining the built-in Intel WiFi in my motherboard, it resets everytime I update my distros (Ubuntu 18.04 and Linux Mint Cinnamon 18.3). My best fix for it is following the guide at [https://askubuntu.com/questions/1038242/no-wifi-option-on- ubuntu-18-04-and-16-04]. I am wanting to know if there is a way to make this process more streamlined for users as this affects many and is a hassle to maintain properly. I know this has been addressed before with Ryzen CPUs but this shouldn't have to be necessary if the driver is baked into the kernel as this is quite frustrating for any user to go through, as it requires what is causing the problem to fix - a network connection. I don't mind if it's simpler to have a on/off feature like the Nvidia drivers have, as that is still a lot simpler than writing out a paragraphs of code. TL;DR I'm asking if changes could be added so that instead of needing a network connection (something that you can't have if the driver isn't built into/available through the distro) and writing a dissertation of code, they have a driver automatically work or a switch option like Broadcom and Nvidia have in this photo [https://linuxhint.com/wp-content/uploads/2017/11/driver-manager-1.png] I was referred here by the Linux Mint forum, please refer to the page in case any questions have already been answered there [https://forums.linuxmint.com/viewtopic.php?f=49&t=289358&e=1&view=unread#unread] My system is a AMD Ryzen 2700x B450 with built-in Intel 9260 WiFi, Linux Mint 18.3/Ubuntu 18.04 dual boot. Thanks, Bionicle159 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819028] Re: Intel 9260 WiFi adapter doesn't work on B450 motherboard
Kai-Heng Feng, I don't believe I've tried that, from the article you attached I'm not sure what going to a previous version would do to help as I have had this issue on several kernels since December 2018. I think the device team needs to modify the Intel driver for AMD B450 integrated WiFi compatibility, whether as an extended pci-e device or something a part of the chipset. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819028 Title: Intel 9260 WiFi adapter doesn't work on B450 motherboard Status in linux package in Ubuntu: Incomplete Bug description: Hi, I know this has been a well discussed issue on Linux forums, but I am having extreme issues maintaining the built-in Intel WiFi in my motherboard, it resets everytime I update my distros (Ubuntu 18.04 and Linux Mint Cinnamon 18.3). My best fix for it is following the guide at [https://askubuntu.com/questions/1038242/no-wifi-option-on- ubuntu-18-04-and-16-04]. I am wanting to know if there is a way to make this process more streamlined for users as this affects many and is a hassle to maintain properly. I know this has been addressed before with Ryzen CPUs but this shouldn't have to be necessary if the driver is baked into the kernel as this is quite frustrating for any user to go through, as it requires what is causing the problem to fix - a network connection. I don't mind if it's simpler to have a on/off feature like the Nvidia drivers have, as that is still a lot simpler than writing out a paragraphs of code. TL;DR I'm asking if changes could be added so that instead of needing a network connection (something that you can't have if the driver isn't built into/available through the distro) and writing a dissertation of code, they have a driver automatically work or a switch option like Broadcom and Nvidia have in this photo [https://linuxhint.com/wp-content/uploads/2017/11/driver-manager-1.png] I was referred here by the Linux Mint forum, please refer to the page in case any questions have already been answered there [https://forums.linuxmint.com/viewtopic.php?f=49&t=289358&e=1&view=unread#unread] My system is a AMD Ryzen 2700x B450 with built-in Intel 9260 WiFi, Linux Mint 18.3/Ubuntu 18.04 dual boot. Thanks, Bionicle159 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808886] Re: Microcode SW error detected. Restarting 0x0.
I still have this bug. Can someone say me, what can i do to fix him? I wanna use ubuntu on my notebook -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1808886 Title: Microcode SW error detected. Restarting 0x0. Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: intel-microcode: Installed: 3.20180807a.0ubuntu0.18.04.1 Candidate: 3.20180807a.0ubuntu0.18.04.1 Version table: *** 3.20180807a.0ubuntu0.18.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.20180312.0~ubuntu18.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Version: Ubuntu 4.15.0-42.45-generic 4.15.18 Error: [ 3136.084499] rtsx_pci :06:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1 [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 source:0x [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: id=00e8 [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Transmitter ID) [ 3136.085694] pcieport :00:1d.0: device [8086:a335] error status/mask=1101/2000 [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First) [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6 [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0 [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0 [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2 [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1 [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2 [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1 [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2 [ 3166.625860] iwlwifi :00:14.3: 0x | data3 [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1 [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2 [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0 [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1 [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2 [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3 [ 3166.625944] iwlwifi :00:14.3: 0x | isr4 [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7 [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1 [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2 [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1 [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2 [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1 [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2 [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3 [ 3166.626194] iwlwifi
[Kernel-packages] [Bug 1801305] Re: Restore request-based mode to xen-blkfront for AWS kernels
Upon closer inspection, it looks like we probably do want to keep the PM patches, so I've only dropped "UBUNTU: SAUCE: xen-blkfront: resurrect request-based mode." -- 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/1801305 Title: Restore request-based mode to xen-blkfront for AWS kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux-aws source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-aws source package in Cosmic: Fix Released Status in linux source package in Disco: Triaged Status in linux-aws source package in Disco: Fix Released Bug description: In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. For X this needs a small patch from upstream for error handling. For B/C this patchset is bigger as it includes the suspend/resume patches already in X, and a new fixup. These are desirable as the request mode patch assumes their presence. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1801305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818747] Re: Crash in nvme_irq_check() when using threaded interrupts
** 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/1818747 Title: Crash in nvme_irq_check() when using threaded interrupts Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] kernel crashes under load w/ nvme.use_threaded_interrupts=1 [Test Case] Boot w/ nvme.use_threaded_interrupts=1 sudo fio -name=randread -numjobs=8 -filename=/dev/nvme0n1 -rw=randread -ioengine=libaio -direct=1 -iodepth=64 -sync=0 -norandommap -group_reporting -runtime=300 -time_based -bs=4k [ 284.756476] CPU: 0 PID: 1047 Comm: irq/97-nvme0q1 Not tainted 4.18.0-15-generic #16~18.04.1-Ubuntu [ 284.765420] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.13.01 02/14/2019 [ 284.773930] pstate: 00400089 (nzcv daIf +PAN -UAO) [ 284.778711] pc : nvme_irq_check+0x30/0x48 [nvme] [ 284.783319] lr : __handle_irq_event_percpu+0x68/0x228 [ 284.788356] sp : 08003e70 [Fix] dcca166272722 nvme-pci: fix out of bounds access in nvme_cqe_pending [Regression Risk] Restricted to systems w/ NVMe. There are no upstream patches marked as Fixing the upstream change, which suggests it is not yet know to introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
18.04 didn't exhibit the problem for me (HP Elitebook 820 G3), but I have had it since the upgrade to 18.10. -- 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 1801305] Re: Restore request-based mode to xen-blkfront for AWS kernels
Adding a note that we must drop these patches for 5.0 (disco). The single queue IO schedulers are gone; blk-mq is the only game in town. For reference, this seems to be one of the key commits: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a1ce35fa49852db60fc6e268038530be533c5b15 I don't know if some of the patches are still useful or not. I'm going to drop them all; we can add some of them back if still needed. -- 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/1801305 Title: Restore request-based mode to xen-blkfront for AWS kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux-aws source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-aws source package in Cosmic: Fix Released Status in linux source package in Disco: Triaged Status in linux-aws source package in Disco: Fix Released Bug description: In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. For X this needs a small patch from upstream for error handling. For B/C this patchset is bigger as it includes the suspend/resume patches already in X, and a new fixup. These are desirable as the request mode patch assumes their presence. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1801305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817784] Re: libsas disks can have non-unique by-path names
cosmic verification: ubuntu@d06-1:~$ cat /proc/version Linux version 4.18.0-17-generic (buildd@bos02-arm64-075) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:57 UTC 2019 ubuntu@d06-1:~$ ls -l /dev/disk/by-path total 0 lrwxrwxrwx 1 root root 9 Mar 19 18:09 pci-:74:02.0-sas-exp0x500e004aaa1f-phy5-lun-0 -> ../../sdb lrwxrwxrwx 1 root root 10 Mar 19 18:09 pci-:74:02.0-sas-exp0x500e004aaa1f-phy5-lun-0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Mar 19 18:11 pci-:74:02.0-sas-exp0x500e004aaa1f-phy5-lun-0-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 9 Mar 19 18:09 pci-:74:02.0-sas-exp0x500e004aaa1f-phy8-lun-0 -> ../../sdc lrwxrwxrwx 1 root root 9 Mar 19 18:09 pci-:7a:01.0-usb-0:1.3:1.0-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Mar 19 18:09 pci-:7a:01.0-usb-0:1.3:1.0-scsi-0:0:0:0-part1 -> ../../sda1 bionic verification: ubuntu@d06-1:~$ cat /proc/version Linux version 4.15.0-47-generic (buildd@bos02-arm64-022) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #50-Ubuntu SMP Wed Mar 13 10:42:02 UTC 2019 ubuntu@d06-1:~$ ls -l /dev/disk/by-path total 0 lrwxrwxrwx 1 root root 9 Mar 19 18:39 pci-:74:02.0-sas-exp0x500e004aaa1f-phy5-lun-0 -> ../../sda lrwxrwxrwx 1 root root 10 Mar 19 18:39 pci-:74:02.0-sas-exp0x500e004aaa1f-phy5-lun-0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Mar 19 18:41 pci-:74:02.0-sas-exp0x500e004aaa1f-phy5-lun-0-part2 -> ../../sda2 lrwxrwxrwx 1 root root 9 Mar 19 18:39 pci-:74:02.0-sas-exp0x500e004aaa1f-phy8-lun-0 -> ../../sdb lrwxrwxrwx 1 root root 9 Mar 19 18:39 pci-:7a:01.0-usb-0:1.3:1.0-scsi-0:0:0:0 -> ../../sdc lrwxrwxrwx 1 root root 10 Mar 19 18:39 pci-:7a:01.0-usb-0:1.3:1.0-scsi-0:0:0:0-part1 -> ../../sdc1 ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic 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/1817784 Title: libsas disks can have non-unique by-path names Status in linux package in Ubuntu: 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: [Impact] Multiple disks in a system can end up having the same BY_PATH name, making the corresponding symlinks in /dev/disk/by-path non-unique. This can result in a user performing an operation on the wrong disk, possibly resulting in data loss. [Test Case] $ ls -l /dev/disk/by-path/ total 0 lrwxrwxrwx 1 root root 9 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0 -> ../../sdb lrwxrwxrwx 1 root root 10 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part3 -> ../../sdc3 Notice that there is no symlink for /dev/sdc. [Fix] ffeafdd2bf0b2 scsi: libsas: Fix rphy phy_identifier for PHYs with end devices attached [Regression Risk] This may change the by-path symlinks for disks on the system. While the new name would be the correct one - users maybe relying on the incorrect version. This could result in an unbootable system, requiring manual intervention to repair. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812123] Re: Upstream Commits Needed for DPDK on Azure
I believe these fixes from testing the scenario of rescinding/revoking
the VF while DPDK is active, which is a scenario triggered by a host
networking driver update.
--
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/1812123
Title:
Upstream Commits Needed for DPDK on Azure
Status in linux-azure package in Ubuntu:
Confirmed
Status in linux-azure source package in Bionic:
New
Status in linux-azure source package in Cosmic:
In Progress
Bug description:
The following two patches are related to multi-queue. They are needed
in the linux-azure kernels for DPDK to work properly on Azure.
b5679cebf780 ("vmbus: fix subchannel removal")
5e3c420dcca5 ("uio_hv_generic: set callbacks on open")
Both commits have also been cc'd to upstream stable. Commit 5e3c420dcca5 is
in mainline as of v4.20. Commit b5679cebf780 is still in linux-next.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1812123/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819662] Re: linux-lts-trusty: 3.13.0-168.218~precise1 -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 -- kernel-stable-master-bug: 1819663 phase: Packaging phase-changed: Tuesday, 19. March 2019 16:07 UTC reason: - prepare-package: Pending -- version not specified - prepare-package-meta: Pending -- version not specified - prepare-package-signed: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1819662 Title: linux-lts-trusty: 3.13.0-168.218~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- kernel-stable-master-bug: 1819663 phase: Packaging phase-changed: Tuesday, 19. March 2019 16:07 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820878] Re: linux-aws: 5.0.0-1001.1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 + phase: Packaging + phase-changed: Tuesday, 19. March 2019 17:31 UTC + reason: + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1820878 Title: linux-aws: 5.0.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 phase: Packaging phase-changed: Tuesday, 19. March 2019 17:31 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819662] Re: linux-lts-trusty: 3.13.0-168.218~precise1 -proposed tracker
** Summary changed: - linux-lts-trusty: -proposed tracker + linux-lts-trusty: 3.13.0-168.218~precise1 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1819662 Title: linux-lts-trusty: 3.13.0-168.218~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- kernel-stable-master-bug: 1819663 phase: Packaging phase-changed: Tuesday, 19. March 2019 16:07 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1818170] Re: xenial linux 4.4.0-143.169 ADT test failure [/proc/timer_list: Permission denied]
On Tue, Mar 19, 2019 at 09:46:38AM -, kenn wrote: > I have that bug, i/o screenlet won't run because of insufficient > permission. Will it be fixed in the 4.4.0-143 kernel? This was an intentional change: https://marc.info/?l=git-commits-head&m=151163650225215&w=2 https://lkml.org/lkml/2018/12/20/346 The file /proc/timer_list may be removed in the future: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=844056fd74ebdd826bd23a7d989597e15f478acb Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818170 Title: xenial linux 4.4.0-143.169 ADT test failure [/proc/timer_list: Permission denied] Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20190228_103241_6fdc6@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190226_190740_8dbe6@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20190226_183159_8dbe6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20190226_174407_8dbe6@/log.gz Test suite: ubuntu_qrt_kernel_security.test-kernel-security.py Test case: test_095_kernel_symbols_missing_proc_time_list 16:57:44 ERROR| [stderr] test_095_kernel_symbols_missing_proc_time_list (__main__.KernelSecurityTest) 16:57:44 ERROR| [stderr] kernel addresses in /proc/timer_list are zeroed out ... FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1818170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819759] Re: linux: 5.0.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- backports: null - derivatives: bug 1820605 (linux-azure) + derivatives: bug 1820878 (linux-aws) phase: Testing phase-changed: Thursday, 14. March 2019 14:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - backports: - derivatives: bug 1820878 (linux-aws) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819759 Title: linux: 5.0.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- backports: null derivatives: bug 1820878 (linux-aws) phase: Testing phase-changed: Thursday, 14. March 2019 14:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
I can confirm adding d-i base-installer/kernel/image string linux- image-4.4.0-142-generic does not work the install will ignore this option and proceed with the install of 143 fresh netinstall of 16.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in Blue Linux: New Status in linux-base package in Ubuntu: Confirmed Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818162] Re: arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout
= bionic verification = After running cert: ubuntu@d06-4:~$ cat /proc/version Linux version 4.15.0-47-generic (buildd@bos02-arm64-022) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #50-Ubuntu SMP Wed Mar 13 10:42:02 UTC 2019 ubuntu@d06-4:~$ dmesg | grep CMD_SYNC ubuntu@d06-4:~$ ** 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/1818162 Title: arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] During heavy load, the following message may appear on the console of a HiSilicon D06 system: arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout This is due to a bug that can also impact system performance, as the CPU is blocked until the timeout occurs. [Test Case] The Ubuntu server certification test suite hits this pretty reliably during the stress-ng tests, although I haven't narrowed it down to exactly which test yet. [Fix] 0f02477d16980 iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout [Regression Risk] Limited to arm64 systems. This change has been upstream since 4.20 w/o any noticed regressions (based on lack of Fixes: commits). Regressions could manifest as a performance hit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] Re: Unable to get right-click working on ThinkPad T480s
Can we backport to 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/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in Linux: Unknown Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Triaged Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820366] Re: network install of xenial 16.04 fails with linux-generic package error
@Derek Gibson I have no issue using the HWE mini.iso to accomplish the same thing ... I'd just rather not start building "standard 16.04 workstations" that are using the HWE kernel ... Though give it another day or so and that might not look too bad anymore @rcgop ... Yes, there are whole other discussions ongoing regarding breakages in NVIDIA drivers, virtualbox, etc ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820366 Title: network install of xenial 16.04 fails with linux-generic package error Status in linux package in Ubuntu: Confirmed Bug description: network installing xenial ubuntu is failing for myself and other people (as seen on the #ubuntu irc channel). I had this issue both with and without preseed. I am using the latest netboot kernel and initrd files from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer- amd64/current/images/netboot/ ( I re-downloaded and checked the file digest). The latest version available from the above URL is 4.4.0-142 and the installer fails while installing 4.4.0-143. The following error messages seen during installation: Mar 16 01:20:12 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 16 01:20:12 in-target: linux-update-symlinks: not found Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: subprocess installed post-installation script returned error exit status 127 Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-modules-extra-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up intel-microcode (3.20180807a.0ubuntu0.16.04.1) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: intel-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up amd64-microcode (3.20180524.1~ubuntu0.16.04.2) ...^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: amd64-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-image-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-modules-extra-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-modules-extra-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M After having these issue with a preseed file, I started a PXE install without any preseed ( therefore answering the standard installer questions manually) but I still had the same error. I was told in the #ubuntu irc channel to set : d-i base-installer/kernel/image string linux-image-4.4.0-142-generic in my preseed file. This worked and the installer completed correctly without any failures. Previously m
[Kernel-packages] [Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
I have verified this issue still exists in kernel version 4.18.0-10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819924 Title: System hangs when hot-plugging dual monitor dock Status in linux package in Ubuntu: Confirmed Bug description: When plugging in my Cable Matters USB-C Dual 4K DisplayPort Docking Station into my system, after it has already booted, the system hangs with a kernel OOPS. This is always repeatable. Steps to reproduce: 1. Ensure docking station is unplugged or shut-off. 2. Boot up computer. 3. Turn-on docking station and plug into to system. If the docking station is plugged in before the system boots, it works fine. It can even be unpluged and hot-plugged without issue at that point. This kernel Oops occurs when the system hangs: BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 SMP NOPTI CPU: 3 PID: 84 Comm: kworker/3:1 Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 Workqueue: events_long drm_dp_mst_link_probe_work [drm_kms_helper] RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 8e df ff ff 31 c0 65 48 8b 14 25 00 5c 01 00 48 0f b1 13 74 08 48 89 df e8 b4 ff ff ff 5b 5d c3 90 0f 1f 44 RSP: 0018:b6c0c1efbd78 EFLAGS: 00010246 RAX: RBX: 0320 RCX: 8ed7cfb5c800 RDX: 8ed7d383 RSI: 0202 RDI: 0320 RBP: b6c0c1efbd80 R08: 0201 R09: R10: R11: 8ed7df6e1ac8 R12: R13: 8ed7cfb5c468 R14: 8ed7d3b33f60 R15: FS: () GS:8ed7df6c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0320 CR3: 0003b5d6e000 CR4: 003406a0 Call Trace: drm_dp_mst_wait_tx_reply+0x155/0x1f0 [drm_kms_helper] ? wait_woken+0x80/0x80 drm_dp_send_enum_path_resources.isra.24+0x69/0xf0 [drm_kms_helper] drm_dp_check_and_send_link_address+0xa1/0xd0 [drm_kms_helper] drm_dp_mst_link_probe_work+0x4f/0x80 [drm_kms_helper] process_one_work+0x20f/0x410 worker_thread+0x34/0x400 kthread+0x120/0x140 ? pwq_unbound_release_workfn+0xd0/0xd0 ? kthread_bind+0x40/0x40 ret_from_fork+0x22/0x40 Modules linked in: snd_usb_audio snd_usbmidi_lib usbhid cdc_ether uas usbnet usb_storage r8152 rfcomm binfmt_misc ccm cmac bnep btusb btrtl btbcm btintel bluetooth ecdh_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media evdi(OE) nfc arc4 joydev nls_iso8859_1 snd_hda_codec_conexant snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep kvm_amd ccp kvm irqbypass snd_pcm crct10dif_pclmul iwlmvm crc32_pclmul ghash_clmulni_intel pcbc snd_seq_midi snd_seq_midi_event mac80211 snd_rawmidi snd_seq snd_seq_device snd_timer iwlwifi aesni_intel snd hp_wmi aes_x86_64 crypto_simd cryptd input_leds glue_helper wmi_bmof serio_raw sparse_keymap hid_multitouch k10temp soundcore cfg80211 ipmi_devintf ipmi_msghandler ucsi_acpi typec_ucsi typec mac_hid hp_wireless sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic amdkfd amd_iommu_v2 amdgpu chash gpu_sched i2c_algo_bit ttm nvme drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm ahci libahci r8169 nvme_core i2c_piix4 mii i2c_hid wmi hid video CR2: 0320 ---[ end trace 3aa69f7fb354f0c1 ]--- BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 RIP: 0010:queue_work_on+0x1b/0x40 Code: SMP NOPTI CPU: 0 PID: 974 Comm: Xorg Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 58 66 66 2e 0f 01 01 e8 69 1f 84 00 27 fe ff 00 0f 0b e9 00 b5 fc ff 00 ff 0f 1f 00 44 00 00 0f 55 48 89 e5 1f 44 00 53 00 55 48 9c 89 e5 53 58 0f 1f 48 44 00 00 48 89 fb e8 89 c3 fa 8e 66 0f 1f df 44 00 00 ff 48 0f ba 2a ff 31 c0 00 65 48 8b 73 11 31 c9 14 25 00 48 89 df 57 5c 01 00 9d 0f 1f 44 00 00 89 48 0f b1 c8 RSP: 0018:b6c0c2063c98 EFLAGS: 00010002 13 RAX: 0202 RBX: 0202 RCX: 74 08 48 89 RDX: 03a8 RSI: 8ed7df019000 RDI: 2000 df e8 b4 RBP: b6c0c2063ca0 R08: 00027080 R09: a25d9e13 R10: fa628ed74840 R11: 0036 R12: 8ed7cfb5c5e6 R13: 8ed7801fa800 R14: 0001 R15: 8ed7d3b33f60 FS: () GS:8ed7df6c
[Kernel-packages] [Bug 1820878] [NEW] linux-aws: 5.0.0-1001.1 -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-aws (Ubuntu Disco) Importance: Medium Status: Confirmed ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.03.15-1 kernel-sru-derivative-of-1819759 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Disco) Importance: Undecided Status: New ** Tags added: disco ** Changed in: linux-aws (Ubuntu Disco) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-aws (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Tags added: kernel-sru-cycle-d2019.03.15-1 ** Tags added: kernel-sru-derivative-of-1819759 ** Summary changed: - linux-aws: -proposed tracker + linux-aws: 5.0.0-1001.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) -- 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/1820878 Title: linux-aws: 5.0.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status
[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-hwe-18.04 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Confirmed Status in xorg-hwe-18.04 package in Ubuntu: Confirmed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e 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 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/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819759] Re: linux: 5.0.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- backports: null derivatives: bug 1820605 (linux-azure) phase: Testing phase-changed: Thursday, 14. March 2019 14:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress + backports: + derivatives: bug 1820878 (linux-aws) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819759 Title: linux: 5.0.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- backports: null derivatives: bug 1820605 (linux-azure) phase: Testing phase-changed: Thursday, 14. March 2019 14:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress backports: derivatives: bug 1820878 (linux-aws) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1820687] Re: Sound issue, or rather, lack of sound
I am not sure I know what a cold boot is but that partition is not gone yet. I can try once I know what it is. This is on an older Dell Dimension 8400 tower. Dual booting with Win 7 and separate drive with Win XP. This machine is what I use as a hobby for some gaming my laptop with dual boot Win 10, Linux Cinnamon 18.3 and Ubuntu Bionic Beaver won't do with ease. Laptop heats now and shuts down. Off topic but let me know and I'll try it. Thanks for your help and efforts. On Monday, March 18, 2019, 11:10:46 PM PDT, Kai-Heng Feng wrote: Does a cold boot help? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1820687 Title: Sound issue, or rather, lack of sound Status in linux package in Ubuntu: Incomplete Bug description: Linux Mint 18.3 update Kernel 4.4.0-143-generic up-heaved my Alsa mixer/pulse-audio or something to disable sound, made the mixer and configurations useless and grayed out/inoperable. I have gone through this some time ago and forgotten how to remedy but the next thing, besides what I have tried futilely, will be to rollback the new kernel to its predecessor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820687/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820687 Title: Sound issue, or rather, lack of sound Status in linux package in Ubuntu: Incomplete Bug description: Linux Mint 18.3 update Kernel 4.4.0-143-generic up-heaved my Alsa mixer/pulse-audio or something to disable sound, made the mixer and configurations useless and grayed out/inoperable. I have gone through this some time ago and forgotten how to remedy but the next thing, besides what I have tried futilely, will be to rollback the new kernel to its predecessor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
@ Lunatine (lunatine-lunatine) The suggested work around does work for us. This helps relieve some pressure until the package can be fixed. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in Blue Linux: New Status in linux-base package in Ubuntu: Confirmed Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819662] Re: linux-lts-trusty: -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 -- kernel-stable-master-bug: 1819663 - phase: Ready for Packaging - phase-changed: Friday, 15. March 2019 08:44 UTC + phase: Packaging + phase-changed: Tuesday, 19. March 2019 16:07 UTC reason: prepare-package: Pending -- version not specified + prepare-package-meta: Pending -- version not specified + prepare-package-signed: Pending -- version not specified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1819662 Title: linux-lts-trusty: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- kernel-stable-master-bug: 1819663 phase: Packaging phase-changed: Tuesday, 19. March 2019 16:07 UTC reason: prepare-package: Pending -- version not specified prepare-package-meta: Pending -- version not specified prepare-package-signed: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819713] Re: linux-azure: 4.15.0-1041.45 -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 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 - phase: Ready for Promote to Proposed - phase-changed: Friday, 15. March 2019 18:36 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 19. March 2019 16:06 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages copies requested -- 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/1819713 Title: linux-azure: 4.15.0-1041.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in 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 backports: bug 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 16:06 UTC reason: promote-to-proposed: Ongoing -- packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819711] Re: linux-azure: 4.15.0-1041.45~14.04.1 -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: 1819713 - phase: Ready for Promote to Proposed - phase-changed: Monday, 18. March 2019 20:33 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 19. March 2019 16:02 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review 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/1819711 Title: linux-azure: 4.15.0-1041.45~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: 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: 1819713 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 16:02 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
Same problem here. "d-i base-installer/kernel/image string linux-image-4.4.0-142-generic" did not work for us. The installer continued to fetch 4.4.0-143. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in Blue Linux: New Status in linux-base package in Ubuntu: Confirmed Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819713] Re: linux-azure: 4.15.0-1041.45 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819713 Title: linux-azure: 4.15.0-1041.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in 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 backports: bug 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Ready for Promote to Proposed phase-changed: Friday, 15. March 2019 18:36 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766728] Re: update linux-base on xenial and earlier
Ditto. Netinstalls are broken and the installer ignored the suggested workaround in our kickstart: preseed d-i base-installer/kernel/image string linux- image-4.4.0-142-generic See also: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1820755 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820366 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1766728 Title: update linux-base on xenial and earlier Status in linux-base package in Ubuntu: Confirmed Status in linux-base source package in Precise: In Progress Status in linux-base source package in Trusty: Fix Released Status in linux-base source package in Xenial: Fix Released Status in linux-base source package in Artful: Invalid Bug description: [Impact] After some changes on linux package on bionic, linux-azure-edge and linux-hwe-edge, which are based on that package, now require a linux- base that provides linux-update-symlinks and linux-check-removal. Using the latest version also means translations will be present. [Test Case] Installing the latest linux-azure-edge will fail the config stage because maintainer scripts call into non-existing linux-update- symlinks and linux-check-removal. Test result: It works with xenial kernels and fixes the problem with hwe-edge. [Regression Potential] New functions on perl module are tested during build time. It could break symlinks creation for other kernels. perf bash completion is not distributed, so does not conflict with linux-tools-common. Older kernels still have their links working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1766728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819711] Re: linux-azure: 4.15.0-1041.45~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819711 Title: linux-azure: 4.15.0-1041.45~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: 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: 1819713 phase: Ready for Promote to Proposed phase-changed: Monday, 18. March 2019 20:33 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820366] Re: network install of xenial 16.04 fails with linux-generic package error
@Ken Stone I had the same issue, using the 142 kernel, successful install but when the system restarts post install, no network modules I have just successfully tested using the HWE kernel d-i base-installer/kernel/image string linux-image-generic-hwe-16.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820366 Title: network install of xenial 16.04 fails with linux-generic package error Status in linux package in Ubuntu: Confirmed Bug description: network installing xenial ubuntu is failing for myself and other people (as seen on the #ubuntu irc channel). I had this issue both with and without preseed. I am using the latest netboot kernel and initrd files from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer- amd64/current/images/netboot/ ( I re-downloaded and checked the file digest). The latest version available from the above URL is 4.4.0-142 and the installer fails while installing 4.4.0-143. The following error messages seen during installation: Mar 16 01:20:12 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 16 01:20:12 in-target: linux-update-symlinks: not found Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: subprocess installed post-installation script returned error exit status 127 Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-modules-extra-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up intel-microcode (3.20180807a.0ubuntu0.16.04.1) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: intel-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up amd64-microcode (3.20180524.1~ubuntu0.16.04.2) ...^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: amd64-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-image-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-modules-extra-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-modules-extra-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M After having these issue with a preseed file, I started a PXE install without any preseed ( therefore answering the standard installer questions manually) but I still had the same error. I was told in the #ubuntu irc channel to set : d-i base-installer/kernel/image string linux-image-4.4.0-142-generic in my preseed file. This worked and the installer completed correctly without any failures. Previously my preseed file container: d-i base-installer/kernel/image string linux-generic but as I said above, even without a pres
[Kernel-packages] [Bug 1819713] Re: linux-azure: 4.15.0-1041.45 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819713 Title: linux-azure: 4.15.0-1041.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in 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 backports: bug 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Ready for Promote to Proposed phase-changed: Friday, 15. March 2019 18:36 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820366] Re: network install of xenial 16.04 fails with linux-generic package error
We deploy Ubuntu exclusively via netinstall so this has brought deployments across our entire organization to a standstill. Adding preseed d-i base-installer/kernel/image string linux- image-4.4.0-142-generic to our kickstart did not help; the installer continued to fetch the 4.4.0-143 packages. Bonus failure: since the kernel post-install script dies early, it breaks DKMS, which in turn breaks the nVidia driver on machines set to auto-upgrade. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820366 Title: network install of xenial 16.04 fails with linux-generic package error Status in linux package in Ubuntu: Confirmed Bug description: network installing xenial ubuntu is failing for myself and other people (as seen on the #ubuntu irc channel). I had this issue both with and without preseed. I am using the latest netboot kernel and initrd files from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer- amd64/current/images/netboot/ ( I re-downloaded and checked the file digest). The latest version available from the above URL is 4.4.0-142 and the installer fails while installing 4.4.0-143. The following error messages seen during installation: Mar 16 01:20:12 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 16 01:20:12 in-target: linux-update-symlinks: not found Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: subprocess installed post-installation script returned error exit status 127 Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-modules-extra-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up intel-microcode (3.20180807a.0ubuntu0.16.04.1) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: intel-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up amd64-microcode (3.20180524.1~ubuntu0.16.04.2) ...^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: amd64-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-image-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-modules-extra-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-modules-extra-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M After having these issue with a preseed file, I started a PXE install without any preseed ( therefore answering the standard installer questions manually) but I still had the same error. I was told in the #ubuntu irc channel to set : d-i base-installer/kernel/image string linux-image-4.4.0-142-generic in my preseed file. This worked and t
[Kernel-packages] [Bug 1819662] Re: linux-lts-trusty: 3.13.0-167.217~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1819662 Title: linux-lts-trusty: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- kernel-stable-master-bug: 1819663 phase: Ready for Packaging phase-changed: Friday, 15. March 2019 08:44 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820366] Re: network install of xenial 16.04 fails with linux-generic package error
Has anyone found another work around for this issue yet ? I can add the preseed to my kickstart file and get a system to come up with the 142 kernel but unfortunately it also has no network interfaces as Stian saw -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820366 Title: network install of xenial 16.04 fails with linux-generic package error Status in linux package in Ubuntu: Confirmed Bug description: network installing xenial ubuntu is failing for myself and other people (as seen on the #ubuntu irc channel). I had this issue both with and without preseed. I am using the latest netboot kernel and initrd files from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer- amd64/current/images/netboot/ ( I re-downloaded and checked the file digest). The latest version available from the above URL is 4.4.0-142 and the installer fails while installing 4.4.0-143. The following error messages seen during installation: Mar 16 01:20:12 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 16 01:20:12 in-target: linux-update-symlinks: not found Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: subprocess installed post-installation script returned error exit status 127 Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-modules-extra-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up intel-microcode (3.20180807a.0ubuntu0.16.04.1) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: intel-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up amd64-microcode (3.20180524.1~ubuntu0.16.04.2) ...^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: amd64-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-image-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-modules-extra-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-modules-extra-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M After having these issue with a preseed file, I started a PXE install without any preseed ( therefore answering the standard installer questions manually) but I still had the same error. I was told in the #ubuntu irc channel to set : d-i base-installer/kernel/image string linux-image-4.4.0-142-generic in my preseed file. This worked and the installer completed correctly without any failures. Previously my preseed file container: d-i base-installer/kernel/image string linux-generic but as I said above, even without a preseed file the error occured. One though
[Kernel-packages] [Bug 1820872] 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 1820872 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1820872 Title: Xenial: Sync to upstream v4.9 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: == SRU Justification == Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the Spectre-related areas. == Regression Potential == Low. These are cosmetic cleanups (non-functional changes) and backports of low-risk commits that have been in upstream stable for quite a while already. == Fix == Backport the relevant commits. == Test Case == TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820872] [NEW] Xenial: Sync to upstream v4.9
Public bug reported: == SRU Justification == Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the Spectre-related areas. == Regression Potential == Low. These are cosmetic cleanups (non-functional changes) and backports of low-risk commits that have been in upstream stable for quite a while already. == Fix == Backport the relevant commits. == Test Case == TBD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Confirmed ** Description changed: == SRU Justification == Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the Spectre-related areas. - == Regression potiential == + == Regression Potential == Low. These are cosmetic cleanups (non-functional changes) and backports of low-risk commits that have been in upstream stable for quite a while already. == Fix == Backport the relevant commits. - == Test case == + == Test Case == TBD. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820872 Title: Xenial: Sync to upstream v4.9 Status in linux package in Ubuntu: New Status in linux source package in Xenial: Confirmed Bug description: == SRU Justification == Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the Spectre-related areas. == Regression Potential == Low. These are cosmetic cleanups (non-functional changes) and backports of low-risk commits that have been in upstream stable for quite a while already. == Fix == Backport the relevant commits. == Test Case == TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788432] Re: 4.15 s390x kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
** Description changed: + [SRU Justification] + + == Impact == + Several helper functions in the s390x code which handle accessing sysfs attributes were missing protection against races. Concurrent access would be able to trigger kernel bugs. + + == Fix == + The following two upstream commits (from v5.0 upstream) will fix the issue: + + 78b1a52e05c9 virtio/s390: fix race in ccw_io_helper() + 2448a299ec41 virtio/s390: avoid race on vcdev->config + + == Testcase == + see below + + == Risk of Regression == + Changes are isolated to architecture code and are verified by running the stress testing, so overall should be low. + + uname -a Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux and same for 4.15.0-29-generic and 4.17.0-8-generic Steps to reproduce this bug: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make clean make And run with: ./stress-ng --sysfs 0 -t 60 .. wait a few seconds and then: [ 119.445891] [ cut here ] [ 119.445898] kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP [ 119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk [ 119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P DO 4.15.0-33-generic #36-Ubuntu [ 119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 119.446170] Krnl PSW : 12d313d3 405835bc (virtblk_cache_type_show+0x82/0x88 [virtio_blk]) [ 119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 6545 [ 119.446196]03ff800058da 6546 6bf537c0 6b60a100 [ 119.446198] 00690648 7cc3de40 7a74b000 [ 119.446202]03ff80008210 03ff800058da 7ac1bce8 [ 119.446210] Krnl Code: 03ff80005912: ebbff0a80004 lmg %r11,%r15,168(%r15) [ 119.446210]03ff80005918: c0f40560 brcl 15,3ff800063d8 [ 119.446210] #03ff8000591e: a7f40001 brc 15,3ff80005920 [ 119.446210] >03ff80005922: 0707 bcr 0,%r7 [ 119.446210]03ff80005924: 0707 bcr 0,%r7 [ 119.446210]03ff80005926: 0707 bcr 0,%r7 [ 119.446210]03ff80005928: c004 brcl 0,3ff80005928 [ 119.446210]03ff8000592e: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 119.446226] Call Trace: [ 119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 [virtio_blk]) [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 [ 119.446279] Last Breaking-Event-Address: [ 119.446281] [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 [virtio_blk] [ 119.446283] [ 119.446284] ---[ end trace 2c2403d726047e4a ]--- For 4.17.0-8-generic: [ 25.170715] kernel BUG at drivers/block/virtio_blk.c:574! [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP [ 25.170797] Modules linked in: lttng_statedump(OE) lttng_clock(OE) lttng_lib_ring_buffer(OE) binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm nfsd ib_core auth_rpcgss iscsi_tcp nfs_acl lockd grace libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net virtio_blk crc32_vx_s390 [ 25.170835] CPU: 0 PID: 5590 Comm: stress-ng-sysfs Tainted: P OE 4.17.0-8-generic #9-Ubuntu [ 25.170837] Hardware name: IBM 2964 N63 400 (KVM/Linux) [
[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)
Submitted SRU request -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779756 Title: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] The i40e driver can get stalled on tx timeouts. This can happen when DCB is enabled on the connected switch. This can also trigger a second situation when a tx timeout occurs before the recovery of a previous timeout has completed due to CPU load, which is not handled correctly. This leads to networking delays, drops and application timeouts and hangs. Note that the first tx timeout cause is just one of the ways to end up in the second situation. This issue was seen on a heavily loaded Kafka broker node running the 4.15.0-38-generic kernel on Xenial. Symptoms include messages in the kernel log of the form: --- [4733544.982116] i40e :18:00.1 eno2: tx_timeout: VSI_seid: 390, Q 6, NTC: 0x1a0, HWB: 0x66, NTU: 0x66, TAIL: 0x66, INT: 0x0 [4733544.982119] i40e :18:00.1 eno2: tx_timeout recovery level 1, hung_queue 6 With the test kernel provided in this LP bug which had these two commits compiled in, the problem has not been seen again, and has been running successfully for several months: "i40e: Fix for Tx timeouts when interface is brought up if DCB is enabled" Commit: fa38e30ac73fbb01d7e5d0fd1b12d412fa3ac3ee "i40e: prevent overlapping tx_timeout recover" Commit: d5585b7b6846a6d0f9517afe57be3843150719da * The first commit is already in Disco, Cosmic * The second commit is already in Disco * Bionic needs both patches and Cosmic needs the second [Test Case] * We are considering the case of both issues above occurring. * Seen by reporter on a Kafka broker node with heavy traffic. * Not easy to reproduce as it requires something like the following example environment and heavy load: Kernel: 4.15.0-38-generic Network driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 NIC: Intel 40Gb XL710 DCB enabled [Regression Potential] Low, as the first only impacts i40e DCB environment, and has been running for several months in production-load testing successfully. --- Original Description Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13 to the Kernel 4.15.0-24-generic. On a "Dell PowerEdge R330" server with a network adapter "Intel Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network card no longer works and permanently displays these three lines : [ 98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1 [ 98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, hung_queue 8 [ 98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819653] Re: linux-aws: 4.4.0-1078.88 -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: 1819660 phase: Testing phase-changed: Tuesday, 19. March 2019 13:31 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 not in beta channel snap-release-to-edge: Pending -- snap not in edge channel 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/1819653 Title: linux-aws: 4.4.0-1078.88 -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 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 verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1819660 phase: Testing phase-changed: Tuesday, 19. March 2019 13:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788432] Re: 4.15 s390x kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
Just checked and Disco 5.0.0-7.8 is now released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788432 Title: 4.15 s390x kernel BUG at /build/linux- Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Triaged Bug description: uname -a Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux and same for 4.15.0-29-generic and 4.17.0-8-generic Steps to reproduce this bug: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make clean make And run with: ./stress-ng --sysfs 0 -t 60 .. wait a few seconds and then: [ 119.445891] [ cut here ] [ 119.445898] kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP [ 119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk [ 119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P DO 4.15.0-33-generic #36-Ubuntu [ 119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 119.446170] Krnl PSW : 12d313d3 405835bc (virtblk_cache_type_show+0x82/0x88 [virtio_blk]) [ 119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 6545 [ 119.446196]03ff800058da 6546 6bf537c0 6b60a100 [ 119.446198] 00690648 7cc3de40 7a74b000 [ 119.446202]03ff80008210 03ff800058da 7ac1bce8 [ 119.446210] Krnl Code: 03ff80005912: ebbff0a80004 lmg %r11,%r15,168(%r15) [ 119.446210]03ff80005918: c0f40560 brcl 15,3ff800063d8 [ 119.446210] #03ff8000591e: a7f40001 brc 15,3ff80005920 [ 119.446210] >03ff80005922: 0707 bcr 0,%r7 [ 119.446210]03ff80005924: 0707 bcr 0,%r7 [ 119.446210]03ff80005926: 0707 bcr 0,%r7 [ 119.446210]03ff80005928: c004 brcl 0,3ff80005928 [ 119.446210]03ff8000592e: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 119.446226] Call Trace: [ 119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 [virtio_blk]) [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 [ 119.446279] Last Breaking-Event-Address: [ 119.446281] [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 [virtio_blk] [ 119.446283] [ 119.446284] ---[ end trace 2c2403d726047e4a ]--- For 4.17.0-8-generic: [ 25.170715] kernel BUG at drivers/block/virtio_blk.c:574! [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP [ 25.170797] Modules linked in: lttng_statedump(OE) lttng_clock(OE) lttng_lib_ring_buffer(OE) binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm nfsd ib_core auth_rpcgss iscsi_tcp nfs_acl lockd grace libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net virtio_blk crc32_vx
[Kernel-packages] [Bug 1819694] Re: linux-aws: 4.15.0-1035.37 -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/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** 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 1819693 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 - phase: Promote to Proposed - phase-changed: Tuesday, 19. March 2019 13:34 UTC + phase: Testing + phase-changed: Tuesday, 19. March 2019 14:32 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: Pending -- snap not in 18/beta channel + snap-release-to-edge: Pending -- snap not in 18/edge channel + 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/1819694 Title: linux-aws: 4.15.0-1035.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow 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 1819693 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Tuesday, 19. March 2019 14:32 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 snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819655] Re: linux-kvm: 4.4.0-1042.48 -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: 1819660 phase: Testing phase-changed: Tuesday, 19. March 2019 12:33 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/1819655 Title: linux-kvm: 4.4.0-1042.48 -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 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: 1819660 phase: Testing phase-changed: Tuesday, 19. March 2019 12:33 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/1819655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819653] Re: linux-aws: 4.4.0-1078.88 -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/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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819660 - phase: Promote to Proposed - phase-changed: Tuesday, 19. March 2019 11:34 UTC + phase: Testing + phase-changed: Tuesday, 19. March 2019 13:31 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 not in beta channel + snap-release-to-edge: Pending -- snap not in edge channel + 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/1819653 Title: linux-aws: 4.4.0-1078.88 -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: 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 verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1819660 phase: Testing phase-changed: Tuesday, 19. March 2019 13:31 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 not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819694] Re: linux-aws: 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 backports: bug 1819693 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 - phase: Ready for Promote to Proposed - phase-changed: Monday, 18. March 2019 21:05 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 19. March 2019 13:34 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1819694 Title: linux-aws: 4.15.0-1035.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New 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 1819693 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 13:34 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819653] Re: linux-aws: 4.4.0-1078.88 -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: 1819660 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 11:34 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1819653 Title: linux-aws: 4.4.0-1078.88 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1819660 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 11:34 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819655] Re: linux-kvm: 4.4.0-1042.48 -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/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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819660 - phase: Promote to Proposed - phase-changed: Tuesday, 19. March 2019 10:33 UTC + phase: Testing + phase-changed: Tuesday, 19. March 2019 12:33 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- 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/1819655 Title: linux-kvm: 4.4.0-1042.48 -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 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: 1819660 phase: Testing phase-changed: Tuesday, 19. March 2019 12:33 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/1819655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819694] Re: linux-aws: 4.15.0-1035.37 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1819694 Title: linux-aws: 4.15.0-1035.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New 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 1819693 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Ready for Promote to Proposed phase-changed: Monday, 18. March 2019 21:05 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819694] Re: linux-aws: 4.15.0-1035.37 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1819694 Title: linux-aws: 4.15.0-1035.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New 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 1819693 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Ready for Promote to Proposed phase-changed: Monday, 18. March 2019 21:05 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819653] Re: linux-aws: 4.4.0-1078.88 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1819653 Title: linux-aws: 4.4.0-1078.88 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1819660 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 11:34 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819653] Re: linux-aws: 4.4.0-1078.88 -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: 1819660 - phase: Ready for Promote to Proposed - phase-changed: Monday, 18. March 2019 14:37 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 19. March 2019 11:34 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review 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/1819653 Title: linux-aws: 4.4.0-1078.88 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1819660 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 11:34 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804149] Re: Kernel panic, Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi]
Can you please test the test kernel at: https://kernel.ubuntu.com/~juergh/lp1804149/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804149 Title: Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Michael Finnegan - 2018-11-19 14:14:40 == ---Problem Description--- Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] ---uname output--- Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) ---Debugger--- A debugger is not configured Contact Information = Michael Finnegan/finne...@us.ibm.com Stack trace output: dmesg.201811161956 [1363037.322472] Unable to handle kernel pointer dereference in virtual kernel address space [1363037.322481] Failing address: TEID: 0483 [1363037.322483] Fault in home space mode while using kernel ASCE. [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d [1363037.322524] Oops: 0004 ilc:3 [#1] SMP [1363037.322529] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 4.15.0-36-generic #39-Ubuntu [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0) [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi] [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 (__iscsi_get_task+0x6/0x18 [libiscsi]) [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [1363037.322589] Krnl GPRS: 02923ce0 0400 [1363037.322591]03ff80277640 0008 788efc00 03ff802777cc [1363037.322592]03ff8027769c 78ce8310 [1363037.322594]f3689800 78ce83a2 03ff80272e8e 02923c90 [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6 brcl 15,3ff80272010 03ff8027262a: c0f4377b brcl 15,3ff80279520 #03ff80272630: c004 brcl 0,3ff80272630 >03ff80272636: eb012078006a asi 120(%r2),1 03ff8027263c: c0f43772 brcl 15,3ff80279520 03ff80272642: 0707 bcr 0,%r7 03ff80272644: 0707 bcr 0,%r7 03ff80272646: 0707 bcr 0,%r7 [1363037.322618] Call Trace: [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi]) [1363037.322625] [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi] [1363037.322636] [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi] [1363037.322642] [<001918f2>] process_one_work+0x262/0x4d8 [1363037.322644] [<00191bc0>] worker_thread+0x58/0x4e8 [1363037.322648] [<00198d24>] kthread+0x14c/0x168 [1363037.322652] [<008e3eb2>] kernel_thread_starter+0xa/0x10 [1363037.322654] [<008e3ea8>] kernel_thread_starter+0x0/0x10 [1363037.322655] Last Breaking-Event-Address: [1363037.322657] [<03ff80272e88>] iscsi_xmit_task+0x48/0x138 [libiscsi] [1363037.322658] [1363037.322660] Kernel panic - not syncing: Fatal exception in interrupt Oops output: Oops: 0004 ilc:3 [#1] SMP *Additional Instructions for Michael Finnegan/finne...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819653] Re: linux-aws: 4.4.0-1078.88 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1819653 Title: linux-aws: 4.4.0-1078.88 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1819660 phase: Ready for Promote to Proposed phase-changed: Monday, 18. March 2019 14:37 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819703] Re: linux-oracle: 4.15.0-1010.12~16.04.1 -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 -- kernel-stable-master-bug: 1819704 - phase: Ready for Packaging - phase-changed: Monday, 18. March 2019 16:33 UTC + phase: Packaging + phase-changed: Tuesday, 19. March 2019 11:05 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- 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/1819703 Title: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-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 -- kernel-stable-master-bug: 1819704 phase: Packaging phase-changed: Tuesday, 19. March 2019 11:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819655] Re: linux-kvm: 4.4.0-1042.48 -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: 1819660 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 10:33 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1819655 Title: linux-kvm: 4.4.0-1042.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1819660 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 10:33 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
As a temporary measure, the installation failure error was avoided by putting 4.4.0-142 kernel on preseed.cfg d-i base-installer/kernel/image string linux-image-4.4.0-142-generic After installing this version 4.04-142, we update the linux-base to 4.5ubuntu1 version at POST stage and upgrade it to 4.4.0-143. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in Blue Linux: New Status in linux-base package in Ubuntu: Confirmed Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260
** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809483 Title: iwlwifi not working with Intel AC 9260 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: New Status in linux source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: [ 22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 9260, REV=0x324 [ 22.208574] [ cut here ] [ 22.208575] kernel BUG at /build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425! [ 22.208578] invalid opcode: [#1] SMP NOPTI [ 22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi irqbypass uvcvideo mxm_wmi intel_wmi_thunderb olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) aesni_intel aes_x86_64 crypto_simd [ 22.208598] cryptd glue_helper drm_kms_helper syscopyarea sysfillrect input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci ipmi_msghandler video mac_hid [ 22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P OE 4.15.0-43-generic #46-Ubuntu [ 22.208605] Hardware name: Notebook P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018 [ 22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi] [ 22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286 [ 22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: e4b2e1c6ab60 [ 22.208612] RDX: 99b9b38b61a8 RSI: RDI: 99b9b8280078 [ 22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 007690c8 [ 22.208614] R10: R11: 99b9b8280050 R12: 99b9b828 [ 22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 99b9b38b61d0 [ 22.208615] FS: 7fb8c9ec9540() GS:99b9be30() knlGS: [ 22.208616] CS: 0010 DS: ES: CR0: 80050033 [ 22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 003606e0 [ 22.208618] DR0: DR1: DR2: [ 22.208619] DR3: DR6: fffe0ff0 DR7: 0400 [ 22.208619] Call Trace: [ 22.208623] _iwl_pcie_rx_init+0x252/0x710 [iwlwifi] [ 22.208626] iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi] [ 22.208631] ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm] [ 22.208635] iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi] [ 22.208639] iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm] [ 22.208640] ? 0xc198e000 [ 22.208644] iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm] [ 22.208647] ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm] [ 22.208650] ? iwl_wait_init_complete+0x20/0x20 [iwlmvm] [ 22.208654] iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm] [ 22.208657] ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm] [ 22.208660] _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi] [ 22.208663] iwl_opmode_register+0x75/0xe0 [iwlwifi] [ 22.208664] ? 0xc19e8000 [ 22.208668] iwl_mvm_init+0x38/0x1000 [iwlmvm] [ 22.208671] do_one_initcall+0x52/0x19f [ 22.208672] ? _cond_resched+0x19/0x40 [ 22.208674] ? kmem_cache_alloc_trace+0xa6/0x1b0 [ 22.208676] ? do_init_module+0x27/0x209 [ 22.208678] do_init_module+0x5f/0x209 [ 22.208679] load_module+0x191e/0x1f10 [ 22.208681] ? ima_post_read_file+0x96/0xa0 [ 22.208682] SYSC_finit_module+0xfc/0x120 [ 22.208683] ? SYSC_finit_module+0xfc/0x120 [ 22.208685] SyS_finit_module+0xe/0x10 [ 22.208686] do_syscall_64+0x73/0x130 [ 22.208688] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 22.208689] RIP: 0033:0x7fb8c99ef839 [ 22.208690] RSP: 002b:7ffecf171ea8 EFLAGS: 0246 ORIG_RAX: 0139 [ 22.208691] RAX: ffda RBX: 55c40d7462f0 RCX: 7fb8c99ef839 [ 22.208691] RDX: RSI: 55c40c09cd2e RDI: 0001 [ 22.208692] RBP: 000
[Kernel-packages] [Bug 1813783] Re: Unable to toggle Touchpad by keyboard shortcut
Yes, the error only appears when pressing Function button only. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813783 Title: Unable to toggle Touchpad by keyboard shortcut Status in linux package in Ubuntu: Confirmed Bug description: Pressing Fn+F5 button should toggle the onboard touchpad. This seems not to work and might be related to the following bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931 After pressing Fn+F5 shows the following: $ dmesg ... [ 248.412826] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0). [ 248.412833] atkbd serio0: Use 'setkeycodes e078 ' to make it known. [ 250.261108] atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0). [ 250.261110] atkbd serio0: Use 'setkeycodes e078 ' to make it known. I've added the mentioned kernel parameters as described in https://wiki.ubuntu.com/DebuggingACPI (adding acpi=off) and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931/comments/21 (i8042.nomux=1) but the problem still exists. Touchpad also has a little dot in the upper left side which I assume also is for toggling on/off the touchpad. This is also unresponsive. How reproducible: Always Steps to Reproduce: Press Fn+F5 Actual results: Touchpad is not working Expected results: Touchpad should toggle on/off, making it able to use the touchpad. Extra info: Bios is up to date. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ inxi -F System:Host: CarogaLaptopLinux Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Machine: Device: laptop System: Standard product: Standard v: Standard serial: N/A Mobo: Standard model: Standard v: Standard serial: N/A UEFI: American Megatrends v: N.0.05 date: 04/14/2018 BatteryBAT0: charge: 42.2 Wh 90.2% condition: 46.7/46.7 Wh (100%) CPU: 6 core Intel Core i7-8750H (-MT-MCP-) cache: 9216 KB clock speeds: max: 4100 MHz 1: 1541 MHz 2: 2043 MHz 3: 2069 MHz 4: 2345 MHz 5: 2241 MHz 6: 2111 MHz 7: 2080 MHz 8: 2047 MHz 9: 2035 MHz 10: 2388 MHz 11: 1879 MHz 12: 2175 MHz Graphics: Card-1: Intel Device 3e9b Card-2: NVIDIA GP106M [GeForce GTX 1060 Mobile] Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@144.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics (Coffeelake 3x8 GT2) version: 4.5 Mesa 18.0.5 Audio: Card Intel Device a348 driver: snd_hda_intel Sound: ALSA v: k4.15.0-43-generic Network: Card-1: Intel Device a370 driver: iwlwifi IF: wlo1 state: up speed: N/A duplex: N/A mac: 94:b8:6d:fc:16:24 Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: enp4s0 state: down mac: b0:25:aa:29:17:57 Drives:HDD Total Size: 500.1GB (25.6% used) ID-1: /dev/nvme0n1 model: WDS500G2X0C size: 500.1GB ID-2: /dev/nvme1n1 model: WDS500G2X0C size: 500.1GB Partition: ID-1: / size: 398G used: 61G (17%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: swap-1 size: 65.53GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p1 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 55.0C mobo: 54.0C Fan Speeds (in rpm): cpu: N/A Info: Processes: 387 Uptime: 16 min Memory: 3855.5/32027.2MB Client: Shell (zsh) inxi: 2.3.56 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/pcmC0D0p: caroga 3523 F...m pulseaudio /dev/snd/controlC0: caroga 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 16:04:41 2019 HibernationDevice: RESUME=UUID=8cafe715-f523-4099-8dd8-7f80c5de58d4 InstallationDate: Installed on 2018-08-17 (164 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Standard Standard ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=e177b84e-a10b-4a4e-8d1c-8eeafbb021ba ro quiet splash i8042.nomux=1 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.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2018 dmi.bios.vendor: American Me
[Kernel-packages] [Bug 1819703] Re: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker
** Summary changed: - linux-oracle: -proposed tracker + linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- 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/1819703 Title: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-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 -- kernel-stable-master-bug: 1819704 phase: Ready for Packaging phase-changed: Monday, 18. March 2019 16:33 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819655] Re: linux-kvm: 4.4.0-1042.48 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1819655 Title: linux-kvm: 4.4.0-1042.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1819660 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 10:33 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260 on kernel 4.15
** Tags added: originate-from-1820564 somerville ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Summary changed: - iwlwifi not working with Intel AC 9260 on kernel 4.15 + iwlwifi not working with Intel AC 9260 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809483 Title: iwlwifi not working with Intel AC 9260 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: New 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: Confirmed Bug description: [ 22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 9260, REV=0x324 [ 22.208574] [ cut here ] [ 22.208575] kernel BUG at /build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425! [ 22.208578] invalid opcode: [#1] SMP NOPTI [ 22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi irqbypass uvcvideo mxm_wmi intel_wmi_thunderb olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) aesni_intel aes_x86_64 crypto_simd [ 22.208598] cryptd glue_helper drm_kms_helper syscopyarea sysfillrect input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci ipmi_msghandler video mac_hid [ 22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P OE 4.15.0-43-generic #46-Ubuntu [ 22.208605] Hardware name: Notebook P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018 [ 22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi] [ 22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286 [ 22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: e4b2e1c6ab60 [ 22.208612] RDX: 99b9b38b61a8 RSI: RDI: 99b9b8280078 [ 22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 007690c8 [ 22.208614] R10: R11: 99b9b8280050 R12: 99b9b828 [ 22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 99b9b38b61d0 [ 22.208615] FS: 7fb8c9ec9540() GS:99b9be30() knlGS: [ 22.208616] CS: 0010 DS: ES: CR0: 80050033 [ 22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 003606e0 [ 22.208618] DR0: DR1: DR2: [ 22.208619] DR3: DR6: fffe0ff0 DR7: 0400 [ 22.208619] Call Trace: [ 22.208623] _iwl_pcie_rx_init+0x252/0x710 [iwlwifi] [ 22.208626] iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi] [ 22.208631] ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm] [ 22.208635] iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi] [ 22.208639] iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm] [ 22.208640] ? 0xc198e000 [ 22.208644] iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm] [ 22.208647] ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm] [ 22.208650] ? iwl_wait_init_complete+0x20/0x20 [iwlmvm] [ 22.208654] iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm] [ 22.208657] ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm] [ 22.208660] _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi] [ 22.208663] iwl_opmode_register+0x75/0xe0 [iwlwifi] [ 22.208664] ? 0xc19e8000 [ 22.208668] iwl_mvm_init+0x38/0x1000 [iwlmvm] [ 22.208671] do_one_initcall+0x52/0x19f [ 22.208672] ? _cond_resched+0x19/0x40 [ 22.208674] ? kmem_cache_alloc_trace+0xa6/0x1b0 [ 22.208676] ? do_init_module+0x27/0x209 [ 22.208678] do_init_module+0x5f/0x209 [ 22.208679] load_module+0x191e/0x1f10 [ 22.208681] ? ima_post_read_file+0x96/0xa0 [ 22.208682] SYSC_finit_mod
[Kernel-packages] [Bug 1819655] Re: linux-kvm: 4.4.0-1042.48 -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: 1819660 - phase: Ready for Promote to Proposed - phase-changed: Monday, 18. March 2019 13:00 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 19. March 2019 10:33 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review 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/1819655 Title: linux-kvm: 4.4.0-1042.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1819660 phase: Promote to Proposed phase-changed: Tuesday, 19. March 2019 10:33 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
