[Kernel-packages] [Bug 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq
** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=200855 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/1733194 Title: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: When in AP mode after some time, get this BUG: Nov 18 23:21:31 bifrost kernel: [18345.860393] BUG: unable to handle kernel NULL pointer dereference at 0070 Nov 18 23:21:31 bifrost kernel: [18345.860552] IP: iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi] Nov 18 23:21:31 bifrost kernel: [18345.860644] PGD 0 Nov 18 23:21:31 bifrost kernel: [18345.860646] P4D 0 Nov 18 23:21:31 bifrost kernel: [18345.860682] Nov 18 23:21:31 bifrost kernel: [18345.860747] Oops: 0002 [#1] SMP Nov 18 23:21:31 bifrost kernel: [18345.860800] Modules linked in: nfnetlink_queue nfnetlink_log nfnetlink dummy ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo xt_policy xt_multiport ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter nls_iso8859_1 cmdlinepart intel_spi_platform intel_spi spi_nor mtd arc4 intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel bridge kvm stp llc iwlmvm irqbypass punit_atom_debug mac80211 intel_cstate snd_hda_codec_hdmi iwlwifi snd_hda_codec_realtek snd_hda_codec_generic cfg80211 btusb snd_hda_intel lpc_ich btrtl snd_hda_codec snd_intel_sst_acpi Nov 18 23:21:31 bifrost kernel: [18345.861897] mei_txe snd_hda_core mei snd_hwdep shpchp snd_intel_sst_core snd_soc_sst_atom_hifi2_platform hci_uart snd_soc_sst_match snd_soc_core btbcm serdev snd_compress btqca ac97_bus btintel snd_pcm_dmaengine snd_pcm dw_dmac dw_dmac_core snd_timer bluetooth snd soundcore mac_hid intel_int0002_vgpio ecdh_generic spi_pxa2xx_platform rfkill_gpio pwm_lpss_platform pwm_lpss 8250_dw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 drm_kms_helper crct10dif_pclmul igb syscopyarea sysfillrect crc32_pclmul sysimgblt fb_sys_fops dca ghash_clmulni_intel i2c_algo_bit cryptd ahci ptp drm pps_core libahci video Nov 18 23:21:31 bifrost kernel: [18345.862995] i2c_hid hid sdhci_acpi sdhci Nov 18 23:21:31 bifrost kernel: [18345.863068] CPU: 1 PID: 1202 Comm: kworker/1:2 Tainted: GW 4.13.0-16-generic #19-Ubuntu Nov 18 23:21:31 bifrost kernel: [18345.863203] Hardware name: NF541 NF541/NF541, BIOS BAR1NA02 02/25/2016 Nov 18 23:21:31 bifrost kernel: [18345.863326] Workqueue: events iwl_mvm_add_new_dqa_stream_wk [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.863428] task: 96862c1c5800 task.stack: a98a817c Nov 18 23:21:31 bifrost kernel: [18345.863539] RIP: 0010:iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi] Nov 18 23:21:31 bifrost kernel: [18345.863635] RSP: 0018:a98a817c3be0 EFLAGS: 00010246 Nov 18 23:21:31 bifrost kernel: [18345.863718] RAX: 09c4 RBX: 001f RCX: Nov 18 23:21:31 bifrost kernel: [18345.863824] RDX: RSI: 001f RDI: 2710 Nov 18 23:21:31 bifrost kernel: [18345.863932] RBP: a98a817c3c30 R08: 2710 R09: 0001 Nov 18 23:21:31 bifrost kernel: [18345.864039] R10: R11: 9686344ce010 R12: Nov 18 23:21:31 bifrost kernel: [18345.864145] R13: 96862c9d0018 R14: R15: Nov 18 23:21:31 bifrost kernel: [18345.864253] FS: () GS:96863fc8() knlGS: Nov 18 23:21:31 bifrost kernel: [18345.864373] CS: 0010 DS: ES: CR0: 80050033 Nov 18 23:21:31 bifrost kernel: [18345.864461] CR2: 0070 CR3: 00023068b000 CR4: 001006e0 Nov 18 23:21:31 bifrost kernel: [18345.864568] Call Trace: Nov 18 23:21:31 bifrost kernel: [18345.864633] iwl_mvm_enable_txq+0x212/0x3a0 [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.864732] iwl_mvm_add_new_dqa_stream_wk+0x7e8/0x15e0 [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.864843] ? iwl_mvm_add_new_dqa_stream_wk+0x7e8/0x15e0 [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.864945] ? __switch_to+0x211/0x520 Nov 18 23:21:31 bifrost kernel: [18345.865008] ? put_prev_entity+0x23/0xf0 Nov 18 23:21:31 bifrost kernel: [18345.865075] process_one_work+0x1e7/0x410 Nov 18 23:21:31 bifrost kernel: [18345.865143] worker_thread+
[Kernel-packages] [Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
confirmed in Ubuntu 18.10 daily build from 9 sept 2018 Linux cuttlefish 4.17.0-9-generic #10-Ubuntu SMP Wed Aug 22 13:33:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 9.595924] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [9.808153] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [9.811132] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready [9.918233] r8169 :03:00.0 enp3s0: link down [9.918344] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready [ 12.862862] r8169 :03:00.0 enp3s0: link up [ 12.862868] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready [ 14.868315] rfkill: input handler disabled [ 36.984425] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 36.984432] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 36.984433] nouveau :01:00.0: msvld: unable to load firmware data [ 36.984437] nouveau :01:00.0: msvld: init failed, -19 -- 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/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Status in linux package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Won't Fix Bug description: [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Hello, from time to time I find this annoying messages in dmesg in various Ubuntu versions (I believe since 16.04 or 16.10 up until now, including Bionic Beaver daily build). From time to time, the gdm3 crashes. The current HW/SW setup will be described below. I cannot replicate the situation, but it happens. See the excerpt from dmesg output below. [9.386558] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready [9.399079] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12 [9.399134] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13 [9.399208] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14 [9.399274] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15 [ 12.312741] r8169 :03:00.0 enp3s0: link up [ 12.312748] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready [ 13.439863] rfkill: input handler disabled [ 15.125569] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 136.559618] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 136.559619] nouveau :01:00.0: msvld: unable to load firmware data [ 136.559622] nouveau :01:00.0: msvld: init failed, -19 [ 1376.746130] lp: driver loaded but no devices found [ 1376.756790] st: Version 20160209, fixed bufsize 32768, s/g segs 256 [ 1381.398605] do_IRQ: 1.37 No irq handler for vector rr HW setup: Asrock Extreme 6 Z97 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 3563 MHz nVidia GK107 [GeForce GT 640] SW setup: Linux bionic 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@bionic:~# lsmod | grep nouveau nouveau 1716224 5 i2c_algo_bit 16384 1 nouveau ttm 106496 1 nouveau drm_kms_helper167936 1 nouveau mxm_wmi16384 1 nouveau drm 401408 8 nouveau,ttm,drm_kms_helper wmi24576 2 mxm_wmi,nouveau video 40960 1 nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
after suspend
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This upstream bug has been confirmed to affect Ubuntu users[1]. As
per the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
from system sleep. Frequency of the bug is described as once every
few days[2].
[1] E.g. this user confirms the bug & very specific workaround:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
[2] E.g. this log of crashes:
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23
This is a bug in blk-core.c. It is not specific to any one hardware
driver. Technically the suspend bug is triggered by the SCSI core -
which is used by *all SATA devices*.
The commit also includes a test which quickly and reliably proves the
existence of a horrifying bug.
I guess you might avoid this bug only if you have root on NVMe. The
other way to not hit the Xorg crash is if you don't use all your RAM,
so there's no pressure that leads to cold pages of Xorg being swapped.
Also, you won't reproduce the Xorg crash if you suspend+resume
immediately. (This frustrated my tests at one point, it only
triggered after left the system suspended over lunch :).
Fix: "block: do not use interruptible wait anywhere"
in kernel 4.17:
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428
in kernel 4.16.8:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6
lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-24.26#n856
I.e., this bug is still present in Ubuntu source package
linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details
(lspci-vnvn.log) of a system where this bug is known to happen.
Regards
Alan
WORKAROUND: Use kernel parameter:
scsi_mod.scan=sync
== Fix ==
1dc3039bc87a ("block: do not use interruptible wait anywhere")
== Regression Potential ==
Low. This patch has been sent to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788751] Re: linux-azure: 4.15.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- 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/1788751 Title: linux-azure: 4.15.0-1023.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790606] Re: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor E3800 Series PCI Express Root Port 4 /0/100/1c.3/0 ens3 network RTL8111
[Kernel-packages] [Bug 1790606] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185351/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Proces
[Kernel-packages] [Bug 1790606] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185356/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processo
[Kernel-packages] [Bug 1790606] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185352/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor
[Kernel-packages] [Bug 1790606] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185355/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor E380
[Kernel-packages] [Bug 1790606] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185350/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom
[Kernel-packages] [Bug 1790606] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185354/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor E3800 S
[Kernel-packages] [Bug 1790606] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185353/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor E3800 S
[Kernel-packages] [Bug 1790606] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185343/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Proc
[Kernel-packages] [Bug 1790606] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185346/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor E3800 Ser
[Kernel-packages] [Bug 1790606] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185342/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor E3800 Serie
[Kernel-packages] [Bug 1790606] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185341/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor
[Kernel-packages] [Bug 1790606] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185349/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Proces
[Kernel-packages] [Bug 1790606] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185345/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor E3800 Ser
[Kernel-packages] [Bug 1790606] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185344/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor E3
[Kernel-packages] [Bug 1790606] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185348/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 brid
[Kernel-packages] [Bug 1790606] Re: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17
apport information ** Tags added: apport-collected trusty ** Description changed: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor E3800 Series PCI Express Root Port 4 /0/100/1c.3/0 ens3 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller /0/100/1d bus Atom Processor Z36xxx/Z37xxx Series USB EHCI /0/100/1d/1 usb1 bus EHCI Host Controller /0/100/1f bridge Atom Processor Z36xxx/Z37xxx Series Power Control Unit /0/100/1f.3 bus Atom Processor E3800 Seri
[Kernel-packages] [Bug 1790606] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1790606/+attachment/5185347/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790606 Title: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17 Status in linux package in Ubuntu: Confirmed Bug description: On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed on a 18G deleted partition. Apparently, suspend/hibernate succeed partially only, so that it cannot resume. The latest kernel where suspend/hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend/hibernate does not work. It does not help: - to change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. - to enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. - to use Feng's fixed kernel. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). - /sys/power/ files seems to be alright: cat disk mem_sleep state [platform] shutdown reboot suspend test_resume s2idle [deep] freeze mem disk https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270 - busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend: s "yes" If anyone want additional information, just let me know. I don't know how to update BIOS on Acer Aspire ES1-512 from Linux: https://help.ubuntu.com/community/BIOSUpdate I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 ubuntu-bug linux says that the bug is about a non-installed package (?) lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 cat /proc/version Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018 debconf-show uswsusp uswsusp/RSA_passphrase_v: (password omitted) uswsusp/RSA_passphrase: (password omitted) uswsusp/compress: true uswsusp/image_size: 2147483647 uswsusp/max_loglevel: uswsusp/resume_offset: uswsusp/suspend_loglevel: uswsusp/early_writeout: true uswsusp/encrypt: false uswsusp/no_swap: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true uswsusp/shutdown_method: platform uswsusp/snapshot_device: uswsusp/create_RSA_key: false uswsusp/resume_device: /dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 bus Aspire ES1-512 /0/0 memory 64KiB BIOS /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7 memory 24KiB L1 cache /0/f memory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/1 usb2 bus xHCI Host Controller /0/100/14/1/3 bus USB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 generic USB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a generic Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0 wls2 network QCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Proces
[Kernel-packages] [Bug 1788351] Re: bind03 in ubuntu_ltp_syscalls failed with X/B
It seems that this issue has been addressed in commit:
https://github.com/linux-test-project/ltp/commit/21c27c11c3f2ded30b718ae3ec7a5b8763abf201
Will need to verify these across different kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788351
Title:
bind03 in ubuntu_ltp_syscalls failed with X/B
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is a new test. It has passed on Trusty but failed on X/B (I guess
in C as well)
<<>>
tag=bind03 stime=1534863126
cmdline="bind03"
contacts=""
analysis=exit
<<>>
tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
bind03.c:48: FAIL: expected EINVAL: EADDRINUSE
Summary:
passed 0
failed 1
skipped 0
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<>>
From the commit message of this test:
With 0fb44559ffd6 ("af_unix: move unix_mknod() out of bindlock")
the behavior of bind() for STREAM UNIX sockets changed in
case a socket that is already bound is passed to bind() again.
This testcase fails for the new behavior and passes for the
old one.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1032-kvm 4.4.0-1032.38
ProcVersionSignature: User Name 4.4.0-1032.38-kvm 4.4.140
Uname: Linux 4.4.0-1032-kvm x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Aug 22 07:33:43 2018
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1788351/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1607571] Re: [Dell Alienware 17 R3] No network devices after suspend and resume
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1607571 Title: [Dell Alienware 17 R3] No network devices after suspend and resume Status in linux package in Ubuntu: Expired Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790249] Re: desktop sharing won't start after upgrading to 18.04
Well, the remote support was setup under 16.04 so Desktop Sharing must have behaved properly then. Whether its behavior has changed between the setup and upgrading I don't know, but why would it? Anyway, I will boot back wen next I get a chance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790249 Title: desktop sharing won't start after upgrading to 18.04 Status in linux package in Ubuntu: Incomplete Bug description: First time destop sharing was started the system detected a problem which was reported -- so there should be some info for you there already. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:17:29 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker
4.15.0-1019.20~16.04.1 - gcp Regression test CMPL, RTB. Issue to note in gcp: libhugetlbfs - 1 failed , 1 killed by signal, 3 bad config ubuntu_kvm_unit_tests - failed due to no KVM support ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) quotactl01 failed (bug 1790028) Skipped / blacklisted: * ubuntu_ltp * ubuntu_nbd_smoke_test * ubuntu_seccomp * ubuntu_sysdig_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1788758 Title: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790825] Re: gicv3-ipi and gicv3-active failed on Bionic Moonshot ARM64 server
These two tests will be skipped with QEMU 3.0.0 built from source. # QEMU=/home/ubuntu/qemu-3.0.0/aarch64-softmmu/qemu-system-aarch64 ./run_tests.sh -v SKIP selftest-setup (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-vectors-kernel (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-vectors-user (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-smp (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP pci-test (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP pmu (qemu-system-aarch64: Unable to determine GIC version supported by host) TESTNAME=gicv2-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'ipi' PASS gicv2-ipi (3 tests) SKIP gicv3-ipi (qemu-system-aarch64: Userspace GICv3 is not supported with KVM) TESTNAME=gicv2-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'active' PASS gicv2-active (1 tests) SKIP gicv3-active (qemu-system-aarch64: Userspace GICv3 is not supported with KVM) SKIP psci (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP timer (qemu-system-aarch64: Unable to determine GIC version supported by host) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790825 Title: gicv3-ipi and gicv3-active failed on Bionic Moonshot ARM64 server Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: These two test will fail on a Moonshot node, with Bionic installed. $ sudo ./run_tests.sh -v SKIP selftest-setup (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-vectors-kernel (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-vectors-user (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-smp (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP pci-test (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP pmu (qemu-system-aarch64: Unable to determine GIC version supported by host) TESTNAME=gicv2-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'ipi' PASS gicv2-ipi (3 tests) TESTNAME=gicv3-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'ipi' FAIL gicv3-ipi TESTNAME=gicv2-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'active' PASS gicv2-active (1 tests) TESTNAME=gicv3-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'active' FAIL gicv3-active SKIP psci (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP timer (qemu-system-aarch64: Unable to determine GIC version supported by host) Further check with these two failed test case, they are complaining the same issue: root@ms10-35-mcdivittB0-kernel:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=gicv3-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'ipi' timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp -machine gic-version=3 -append ipi # -initrd /tmp/tmp.oWkFeTiIeQ qemu-system-aarch64: -smp -machine: Parameter 'cpus' expects a number root@ms10-35-mcdivittB0-kernel:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=gicv3-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'active' timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp -machine gic-version=3 -append active # -initrd /tmp/tmp.1X2ud5gyAh qemu-system-aarch64: -smp -machine: Parameter 'cpus' expects a number ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: User Name 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 5 08:09 seq crw-rw 1 root audio 116, 33 Sep 5 08:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' App
[Kernel-packages] [Bug 1788387] Re: After upgrading from 4.4.0 to 4.15.0 system doesn't boot - ACPI issue
Hi, yes I can try. The last good one is 4.4.154 and the first bad kernel is 4.13.0 (4.15 and 4.18 are confirmed problematic), I see the range between kernels is wide. How would I proceed to test? Bye -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788387 Title: After upgrading from 4.4.0 to 4.15.0 system doesn't boot - ACPI issue Status in linux package in Ubuntu: Confirmed Bug description: I'm using Xubuntu in an old system, I'm concerned because other users looking for a light OS for their old PC wouldn't be able to install or boot the 18.04 version and above. With kernel 4.4.0 the system boots without problem (xubuntu 16.04), after upgrading to kernel 4.15 the system doesn't boot anymore (18.04). This issue was present when testing kernel 4.13 too. The install crashes with an error: BIOS bug:8254 timer not connected to io-apic error on. Adding any of these commands to the boot allows the system to load properly: -acpi=off -pci=noacpi -acpi=noirq I attach the info related. Ubuntu 4.15.0-32.35-generic 4.15.18 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1509 F pulseaudio /dev/snd/controlC1: 1509 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ed42d246-f10a-403e-a009-8c6428ce1a88 InstallationDate: Installed on 2018-06-12 (70 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 248a:00da Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc Dimension C521 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=467ee8bd-241d-4d11-95d9-6d9268a1dca6 ro quiet splash pci=noacpi vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775487] Re: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports
I have the same, or at least similar issue as @Adam. I also have a Sandisk Ultra USB Flash Drive (but 64 GB). It is recognized and mounted by the operating system when I plug it in directly to my laptop's USB 3.0 ports. I also use a USB 3.0 4-port hub to allow connection of mouse, keyboard, (and ideally, flash drives). The laptop, mouse, keyboard and hub work well together. I presume mouse and keyboard use USB 2.0. However, when I connect the Flash Drive thru the USB hub, it isn't recognized. See outputs of "lsusb" below. (In fact, if I wait for 10-30min, sometimes it is recognized, suggesting that some system event triggers recognition. I'm alerted by the appearance of a mounted drive on the system. However, this recognition/mounting is usually temporary.) MY SYSTEM: OS: Ubuntu 18.04 LTS Linux Release: 4.15.0-33-generic Linux Version: #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 Laptop: Lenovo T580 Thinkpad (2 x USB 3.0 ports) USB Hub: Targus ACH124 4-Port Hub (USB 3.0) Drive: Sandisk Ultra USB Flash Drive (USB 3.0) Note that the same hub and flash drive worked well together on an older laptop (with USB 2.0 ports) using an older OS (Ubuntu 16.04). They also used to work well with the current laptop and OS, but not after suspend. I'm guessing that a kernel or OS update/patch changed this behaviour. There seem to be several reports of drives having difficulty being recognised under USB 3.0 protocols, suggesting the problem lies in the USB 3.0 implementation within the linux kernel. Some of these reports involve USB hubs, for example: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693842 https://www.reddit.com/r/archlinux/comments/678lri/usb_3_ports_no_longer_working/ Below are outputs from command "lsusb" under both scenarios. The flash drive appears as "SanDisk Corp. Ultra". The hub appears as "Genesys Logic, Inc. 4-port hub" OUTPUT OF "lsusb" - Flash Drive Connected thru Hub -- Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 06cb:009a Synaptics, Inc. Bus 001 Device 006: ID 04f2:b604 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 04f2:b613 Chicony Electronics Co., Ltd Bus 001 Device 018: ID 1bcf:0002 Sunplus Innovation Technology Inc. Bus 001 Device 017: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub OUTPUT OF "lsusb" - Flash Drive Connected Directly to Laptop Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Bus 002 Device 011: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 06cb:009a Synaptics, Inc. Bus 001 Device 006: ID 04f2:b604 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 04f2:b613 Chicony Electronics Co., Ltd Bus 001 Device 018: ID 1bcf:0002 Sunplus Innovation Technology Inc. Bus 001 Device 017: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775487 Title: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports Status in linux package in Ubuntu: Incomplete Bug description: I have a 128 GB Sandisk Ultra USB Flash Drive. It works when I plug it into a USB 2.0 port, or if I partially insert it into a USB 3.0 port (so the USB 3 pins don't make contact). Here's what lsusb says about it: Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra And dmesg from a successful connection: [ 1269.667097] usb 3-1.4: new high-speed USB device number 6 using xhci_hcd [ 1269.779871] usb 3-1.4: New USB device found, idVendor=0781, idProduct=5581 [ 1269.779875] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1269.779878] usb 3-1.4: Product: Ultra [ 1269.779880] usb 3-1.4: Manufacturer: SanDisk [ 1269.779883] usb 3-1.4: SerialNumber: 4C530001080228105161 [ 1269.780937] usb-storage 3-1.4:1.0: USB Mass Storage device detected [ 1269.781346] scsi host10: usb-storage 3-1.4:1.0 [ 1270.800187] scsi 10:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6 [ 1270.800733] sd 10:0:0:0: Attached scsi generic sg3 type 0 [ 1270.800919] sd 10:0:0:0: [sdd] 240254976 512-byte logical blocks: (123 GB/115 GiB) [ 1270.801887] sd 10:0:0:0: [sdd] Write Protect is off [ 1270.801891] sd 10:0:0:0: [sdd
[Kernel-packages] [Bug 1790028] Re: quotactl01 in ubuntu_ltp_syscalls test failed on B-gcp / X-KVM
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1790028 Title: quotactl01 in ubuntu_ltp_syscalls test failed on B-gcp / X-KVM Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: This issue did not happen on generic Bionic kernel. tag=quotactl01 stime=1535578406 cmdline="quotactl01" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:83: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s quotactl01.c:195: FAIL: quotactl failed to turn on quota for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for user: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for user quotactl01.c:206: PASS: quotactl succeeded to turn off quota for user quotactl01.c:195: FAIL: quotactl failed to turn on quota for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for group: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for group quotactl01.c:206: PASS: quotactl succeeded to turn off quota for group Summary: passed 4 failed 12 skipped 0 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788744] Re: linux: 4.15.0-34.37 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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/1788744 Title: linux: 4.15.0-34.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 (linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 1788761 (linux-hwe-edge) derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 (linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
** Summary changed: - Triple 4K monitor display failed (modesetting driver) + Triple 4K monitor display failed (modesetting driver limited to 8192x8192) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790390] Re: Xorg cannot exceed pipeline dimensions reported by kernel
*** This bug is a duplicate of bug 1714178 ***
https://bugs.launchpad.net/bugs/1714178
Actually Chris's comment explains everything:
https://bugs.freedesktop.org/show_bug.cgi?id=107840#c1
So the kernel is behaving correctly. And the modesetting driver is doing
its best. But it sounds like "its best" can possibly be improved.
** Package changed: linux (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => Medium
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Triaged
** Summary changed:
- Xorg cannot exceed pipeline dimensions reported by kernel
+ Modesetting driver cannot exceed pipeline dimensions reported by kernel
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=107840
Importance: Unknown
Status: Unknown
** Summary changed:
- Modesetting driver cannot exceed pipeline dimensions reported by kernel
+ Modesetting driver cannot exceed pipeline dimensions reported by kernel
(8192x8192)
** Summary changed:
- Modesetting driver cannot exceed pipeline dimensions reported by kernel
(8192x8192)
+ Modesetting driver cannot exceed pipeline dimensions reported by kernel
(8192x8192). The old intel driver could.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790390
Title:
Modesetting driver cannot exceed pipeline dimensions reported by
kernel (8192x8192). The old intel driver could.
Status in X.Org X server:
Unknown
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
The i915 driver in the Linux kernel misrepresents the max output of
certain, newer, GPUs.
The output should be 16384x16384 for newer models (on at least 7th and
8th gen Intel CPUs) but it is stuck in 8192x8192.
The problem lies in:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c
The conditional branch which is wrong is:
/* maximum framebuffer dimensions */
if (IS_GEN2(dev_priv)) {
dev->mode_config.max_width = 2048;
dev->mode_config.max_height = 2048;
} else if (IS_GEN3(dev_priv)) {
dev->mode_config.max_width = 4096;
dev->mode_config.max_height = 4096;
} else {
dev->mode_config.max_width = 8192;
dev->mode_config.max_height = 8192;
}
While I'm not certain which generations specifically allows the higher
output it is most certainly true of all iGPUs on the 7th and 8th
generation CPUs.
This is corroborated by Intel's own hardware pages, and can be proven
by running Wayland which ignores the limitation in the driver.
Bug is present both on all Ubuntu releases, including 18.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1790390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790390] Re: Xorg cannot exceed pipeline dimensions reported by kernel
*** This bug is a duplicate of bug 1714178 ***
https://bugs.launchpad.net/bugs/1714178
Is it possible you're confusing the max texture size for max framebuffer
size?
Can you share that link to "Intel's own hardware pages"?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790390
Title:
Modesetting driver cannot exceed pipeline dimensions reported by
kernel (8192x8192). The old intel driver could.
Status in X.Org X server:
Unknown
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
The i915 driver in the Linux kernel misrepresents the max output of
certain, newer, GPUs.
The output should be 16384x16384 for newer models (on at least 7th and
8th gen Intel CPUs) but it is stuck in 8192x8192.
The problem lies in:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c
The conditional branch which is wrong is:
/* maximum framebuffer dimensions */
if (IS_GEN2(dev_priv)) {
dev->mode_config.max_width = 2048;
dev->mode_config.max_height = 2048;
} else if (IS_GEN3(dev_priv)) {
dev->mode_config.max_width = 4096;
dev->mode_config.max_height = 4096;
} else {
dev->mode_config.max_width = 8192;
dev->mode_config.max_height = 8192;
}
While I'm not certain which generations specifically allows the higher
output it is most certainly true of all iGPUs on the 7th and 8th
generation CPUs.
This is corroborated by Intel's own hardware pages, and can be proven
by running Wayland which ignores the limitation in the driver.
Bug is present both on all Ubuntu releases, including 18.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1790390/+subscriptions
--
Mailing list: https://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 1790506] Re: Upgrading to 18.04.1 from 17.10
I have installed 16. 17, and 18.04 without any issues, multiple times without any issues. When I do the update to 18.04.1, that is when it will cycle through the dots then lock up. 18.04.1 works great n a different laptop. Sent from my Windows 10 phone From: Joseph Salisbury Sent: Wednesday, September 5, 2018 9:41 AM To: horn.jt.li...@gmail.com Subject: [Bug 1790506] Re: Upgrading to 18.04.1 from 17.10 Are you able to boot any kernels that previously worked? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1790506 Title: Upgrading to 18.04.1 from 17.10 Status in linux package in Ubuntu: Incomplete Bug description: I have a HP Mini 210-1170NR that I have been using since Ubuntu 14 I believe. I have at it at 16 and currently (recently re-install 17.10 because of the possible "bug" in upgrading to 18.10.1 or even a fresh install of 18.10.1 on this same system. I believe I do remembering upgrading to 18.10 with success, but when it tries to go to 18.10.1 that is where the issue occurs. Through at least 3 attempts to upgrade my laptop to 18.10.1 it will go through the upgrade with out any errors or warnings until it does the last reboot into the updated version. It will bring up the screen that just has Ubuntu on it with the row of dots, it will go through at least one cycle of changing the colors of the dots, it will display the mouse pointer, which will not move when the mouse is moved, there will be some activity on the drive (the drive light will flash for about 5 minutes, but not sure of the exact time) then even it will not flash anymore. The screen will go blank after no activity, but moving the mouse or clicking on keys will not cause the screen to turn the display back on. Since the information gathered here is more for a working system and not the system that is having issues, and I seem to be able to re-create the issue at will, I will try and proceed with the upgrade to 18.10.1 and see if it "works" this time. What I can use from you is maybe an iso or instructions to possibly gather additional information that could be used to determine why it is not completing the update process. Any assistants you can provide will be gratefully appreciated. This is an old windows system that I put Ubuntu on and it could be I go back to 16.. and leave it there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-46-generic 4.13.0-46.51 ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 1317 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 09:08:40 2018 HibernationDevice: RESUME=UUID=393e2e20-215e-4082-bca5-cc6f1a2f5b85 InstallationDate: Installed on 2018-09-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Hewlett-Packard HP Mini 210-1100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-46-generic N/A linux-backports-modules-4.13.0-46-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3660 dmi.board.vendor: Hewlett-Packard dmi.board.version: 48.26 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd03/18/2011:svnHewlett-Packard:pnHPMini210-1100:pvr049111202B030:rvnHewlett-Packard:rn3660:rvr48.26:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Mini 210-1100 dmi.product.version: 049111202B030 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790506/+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/1790506 Title: Upgrading to 18.04.1 from 17.10 Status in linux package in Ubuntu: Incomplete Bug description: I have a HP Mini 210-1170NR that I have been using since Ubuntu 14 I believe. I have at it at 16 and currently (recently re-in
[Kernel-packages] [Bug 1790390] 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 1790390
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/1790390
Title:
Xorg cannot exceed pipeline dimensions reported by kernel
Status in linux package in Ubuntu:
Incomplete
Bug description:
The i915 driver in the Linux kernel misrepresents the max output of
certain, newer, GPUs.
The output should be 16384x16384 for newer models (on at least 7th and
8th gen Intel CPUs) but it is stuck in 8192x8192.
The problem lies in:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c
The conditional branch which is wrong is:
/* maximum framebuffer dimensions */
if (IS_GEN2(dev_priv)) {
dev->mode_config.max_width = 2048;
dev->mode_config.max_height = 2048;
} else if (IS_GEN3(dev_priv)) {
dev->mode_config.max_width = 4096;
dev->mode_config.max_height = 4096;
} else {
dev->mode_config.max_width = 8192;
dev->mode_config.max_height = 8192;
}
While I'm not certain which generations specifically allows the higher
output it is most certainly true of all iGPUs on the 7th and 8th
generation CPUs.
This is corroborated by Intel's own hardware pages, and can be proven
by running Wayland which ignores the limitation in the driver.
Bug is present both on all Ubuntu releases, including 18.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767932] Re: nvidia-390 causes kernel hang
I had this exact problem today (same message in `dmesg`) which I found while investigating a hang of anything CUDA-related, appearing out of nowhere after my setup had been working for a while. I was able to fix it by adding `acpi=ht` (or `acpi=off`) to my GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, running `sudo update- grub`, and rebooting. I've got two nVidia 1080tis in this box, and I'm using the nvidia-396 driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767932 Title: nvidia-390 causes kernel hang Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Here is the hung task: Apr 30 15:21:50 michael-desktop-ubuntu kernel: INFO: task nvidia-modeset:243 blocked for more than 120 seconds. Apr 30 15:21:50 michael-desktop-ubuntu kernel: Tainted: P IOE 4.15.0-20-generic #21-Ubuntu Apr 30 15:21:50 michael-desktop-ubuntu kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 30 15:21:50 michael-desktop-ubuntu kernel: nvidia-modeset D0 243 2 0x8000 Apr 30 15:21:50 michael-desktop-ubuntu kernel: Call Trace: Apr 30 15:21:50 michael-desktop-ubuntu kernel: __schedule+0x297/0x8b0 Apr 30 15:21:50 michael-desktop-ubuntu kernel: schedule+0x2c/0x80 Apr 30 15:21:50 michael-desktop-ubuntu kernel: schedule_timeout+0x1cf/0x350 Apr 30 15:21:50 michael-desktop-ubuntu kernel: ? schedule_timeout+0x1cf/0x350 Apr 30 15:21:50 michael-desktop-ubuntu kernel: ? __slab_free+0x14d/0x2c0 Apr 30 15:21:50 michael-desktop-ubuntu kernel: __down+0x91/0xe0 Apr 30 15:21:50 michael-desktop-ubuntu kernel: down+0x41/0x50 Apr 30 15:21:50 michael-desktop-ubuntu kernel: ? down+0x41/0x50 Apr 30 15:21:50 michael-desktop-ubuntu kernel: nvkms_kthread_q_callback+0x65/0xe0 [nvidia_modeset] Apr 30 15:21:50 michael-desktop-ubuntu kernel: _main_loop+0x76/0x140 [nvidia] Apr 30 15:21:50 michael-desktop-ubuntu kernel: kthread+0x121/0x140 Apr 30 15:21:50 michael-desktop-ubuntu kernel: ? _raw_q_schedule+0x80/0x80 [nvidia] Apr 30 15:21:50 michael-desktop-ubuntu kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Apr 30 15:21:50 michael-desktop-ubuntu kernel: ret_from_fork+0x35/0x40 uname: Linux michael-desktop-ubuntu 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Drivers: ii libnvidia-cfg1-390:amd64 390.48-0ubuntu3 amd64NVIDIA binary OpenGL/GLX configuration library ii libnvidia-common-390 390.48-0ubuntu3 all Shared files used by the NVIDIA libraries ii libnvidia-compute-390:amd64390.48-0ubuntu3 amd64NVIDIA libcompute package ii libnvidia-compute-390:i386 390.48-0ubuntu3 i386 NVIDIA libcompute package ii libnvidia-decode-390:amd64 390.48-0ubuntu3 amd64NVIDIA Video Decoding runtime libraries ii libnvidia-decode-390:i386 390.48-0ubuntu3 i386 NVIDIA Video Decoding runtime libraries ii libnvidia-encode-390:amd64 390.48-0ubuntu3 amd64NVENC Video Encoding runtime library ii libnvidia-encode-390:i386 390.48-0ubuntu3 i386 NVENC Video Encoding runtime library ii libnvidia-fbc1-390:amd64 390.48-0ubuntu3 amd64NVIDIA OpenGL-based Framebuffer Capture runtime library ii libnvidia-fbc1-390:i386390.48-0ubuntu3 i386 NVIDIA OpenGL-based Framebuffer Capture runtime library ii libnvidia-gl-390:amd64 390.48-0ubuntu3 amd64NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD ii libnvidia-gl-390:i386 390.48-0ubuntu3 i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD ii libnvidia-ifr1-390:amd64 390.48-0ubuntu3 amd64NVIDIA OpenGL-based Inband Frame Readback runtime library ii libnvidia-ifr1-390:i386390.48-0ubuntu3 i386 NVIDIA OpenGL-based Inband Frame Readback runtime library ii nvidia-compute-utils-390 390.48-0ubuntu3 amd64NVIDIA compute utilities ii nvidia-dkms-390390.48-0ubuntu3 amd64NVIDIA DKMS package ii nvidia-driver-390 390.48-0ubuntu3
[Kernel-packages] [Bug 1790991] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790991
Title:
package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to
install/upgrade: installed linux-image-4.15.0-30-generic package pre-
removal script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Confirmed
Bug description:
Impossible to boot the operating system since it wasn't able to detect
2 external USB drives that should be unmounted, maybe was caused by a
false unmount of those devices
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-30-generic 4.15.0-30.32
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-33-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: antonio 883 F pulseaudio
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xd540 irq 31'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,104313f3,00100302
HDA:80862804,80860101,0010'
Controls : 26
Simple ctrls : 9
Date: Wed Sep 5 15:37:19 2018
ErrorMessage: installed linux-image-4.15.0-30-generic package pre-removal
script subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-09 (88 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: ASUSTeK Computer Inc. K52F
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=UUID=44bcc84e-8292-4053-a854-a6997dcfc6af ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to
install/upgrade: installed linux-image-4.15.0-30-generic package pre-removal
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/12/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52F.218
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K52F
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.:bvrK52F.218:bd07/12/2011:svnASUSTeKComputerInc.:pnK52F:pvr1.0:rvnASUSTeKComputerInc.:rnK52F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K52F
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/1790991/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790390] Re: Xorg cannot exceed pipeline dimensions reported by kernel
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790390
Title:
Xorg cannot exceed pipeline dimensions reported by kernel
Status in linux package in Ubuntu:
Incomplete
Bug description:
The i915 driver in the Linux kernel misrepresents the max output of
certain, newer, GPUs.
The output should be 16384x16384 for newer models (on at least 7th and
8th gen Intel CPUs) but it is stuck in 8192x8192.
The problem lies in:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c
The conditional branch which is wrong is:
/* maximum framebuffer dimensions */
if (IS_GEN2(dev_priv)) {
dev->mode_config.max_width = 2048;
dev->mode_config.max_height = 2048;
} else if (IS_GEN3(dev_priv)) {
dev->mode_config.max_width = 4096;
dev->mode_config.max_height = 4096;
} else {
dev->mode_config.max_width = 8192;
dev->mode_config.max_height = 8192;
}
While I'm not certain which generations specifically allows the higher
output it is most certainly true of all iGPUs on the 7th and 8th
generation CPUs.
This is corroborated by Intel's own hardware pages, and can be proven
by running Wayland which ignores the limitation in the driver.
Bug is present both on all Ubuntu releases, including 18.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790390] [NEW] Xorg cannot exceed pipeline dimensions reported by kernel
You have been subscribed to a public bug:
The i915 driver in the Linux kernel misrepresents the max output of
certain, newer, GPUs.
The output should be 16384x16384 for newer models (on at least 7th and
8th gen Intel CPUs) but it is stuck in 8192x8192.
The problem lies in:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c
The conditional branch which is wrong is:
/* maximum framebuffer dimensions */
if (IS_GEN2(dev_priv)) {
dev->mode_config.max_width = 2048;
dev->mode_config.max_height = 2048;
} else if (IS_GEN3(dev_priv)) {
dev->mode_config.max_width = 4096;
dev->mode_config.max_height = 4096;
} else {
dev->mode_config.max_width = 8192;
dev->mode_config.max_height = 8192;
}
While I'm not certain which generations specifically allows the higher
output it is most certainly true of all iGPUs on the 7th and 8th
generation CPUs.
This is corroborated by Intel's own hardware pages, and can be proven by
running Wayland which ignores the limitation in the driver.
Bug is present both on all Ubuntu releases, including 18.04.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Xorg cannot exceed pipeline dimensions reported by kernel
https://bugs.launchpad.net/bugs/1790390
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 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
@Zhanglei Could you try these 2 patches? https://patchwork.freedesktop.org/patch/246810/ https://patchwork.freedesktop.org/patch/246811/ I think these 2 patches will fix the issue that dual GPU install on UEFI boot mode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790991] [NEW] package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to install/upgrade: installed linux-image-4.15.0-30-generic package pre-removal script subprocess return
Public bug reported:
Impossible to boot the operating system since it wasn't able to detect 2
external USB drives that should be unmounted, maybe was caused by a
false unmount of those devices
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-30-generic 4.15.0-30.32
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-33-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: antonio 883 F pulseaudio
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xd540 irq 31'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,104313f3,00100302
HDA:80862804,80860101,0010'
Controls : 26
Simple ctrls : 9
Date: Wed Sep 5 15:37:19 2018
ErrorMessage: installed linux-image-4.15.0-30-generic package pre-removal
script subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-09 (88 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: ASUSTeK Computer Inc. K52F
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=UUID=44bcc84e-8292-4053-a854-a6997dcfc6af ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to
install/upgrade: installed linux-image-4.15.0-30-generic package pre-removal
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/12/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52F.218
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K52F
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.:bvrK52F.218:bd07/12/2011:svnASUSTeKComputerInc.:pnK52F:pvr1.0:rvnASUSTeKComputerInc.:rnK52F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K52F
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package 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/1790991
Title:
package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to
install/upgrade: installed linux-image-4.15.0-30-generic package pre-
removal script subprocess returned error exit status 1
Status in linux package in Ubuntu:
New
Bug description:
Impossible to boot the operating system since it wasn't able to detect
2 external USB drives that should be unmounted, maybe was caused by a
false unmount of those devices
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-30-generic 4.15.0-30.32
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-33-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: antonio 883 F pulseaudio
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xd540 irq 31'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,104313f3,00100302
HDA:80862804,80860101,0010'
Controls : 26
Simple ctrls : 9
Date: Wed Sep 5 15:37:19 2018
ErrorMessage: installed linux-image-4.15.0-30-generic package pre-removal
script subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-09 (88 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: ASUSTeK Computer Inc. K52F
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=UUID=44bcc84e-8292-4053-a854-a6997dcfc6af ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or no
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
Dann, For the wanland issues, I understood it as comments in #15, that is: Blur screen for GDM login was caused by wayland, it can be fix by force to use Xorg in /etc/gdm3/customer.conf to uncoment WaylandEnable=false Is this right for your wanland issues on D05? In 18.04, we found 2 issues on Huawei X86 server. One is screen blur during d-i install on UEFI model in Language selection screen, but it works for legacy bios model. The other is after start GUI (x-window or Ubuntu desktop). After we sucessfully installed 18.04 in legacy bios model on X86 Huawei server, I tried to start X-windows via apt-get install ubuntu-dekstop and reboot, we would get this blur screen again. This seems caused by this wanyland and can be fixed by this "WaylandEnable=false". As I know, this wayland issues have been happened for D05 but I don't think D05 have above issues during install. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-390 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-390/390.77-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773113] Re: nvidia-390 does not show GUI
I've managed to get it working, the last thing I did was creating this file $ cat /etc/modprobe.d/zz-nvidia.conf options nvidia_390_drm modeset=1 options nvidia_drm modeset=1 But I'm not sure this is the only thing required. AFAIU, only one of these lines is correct but it works with both of them present and I'm really tired of restarting everything to figure out which one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1773113 Title: nvidia-390 does not show GUI Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I know this bug is a duplicate, I am opening it because it seems that for # #1752053 it is marked as "Fix Released" although many people are still affected and complaining about it and nobody can or will change that status. So it is an attempt to raise more attention, as HDMI currently isn't usable for me on Ubuntu 18.04 (it affected me on 16.04 as well). Put in short, after Nvidia drivers are installed and I switch from Nvidia card to the intel one, the GUI can't be opened anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1773113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787898] Re: [18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"
http://kernel.ubuntu.com/~ksouza/lp1787898/linux-
headers-4.15.0-34-generic_4.15.0-34.37~lp1787898_s390x.deb
does not contain s390 builds of tools:
$ arch
s390x
$ usr/src/linux-headers-4.15.0-34-generic/scripts/basic/fixdep
warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
/lib64/ld-linux-x86-64.so.2: No such file or directory
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787898
Title:
[18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"
Status in Ubuntu on IBM z Systems:
Fix Committed
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:
SRU Justification
Impact: To boot an IBM Secure Service Container Appliance in an s390
LPAR. we need to be able to send the Open for Business (OFB) message
to signal that the appliance is up and running.
Fix: Set CONFIG_SCLP_OFB=y.
Regression Potential: The option enables only a few pieces of
architecture-specific code, so the potential impact is limited.
---
For successfully booting an IBM Secure Service Container Appliance in an s390
LPAR, we need to be able to send the OFB (Open for Business) message to the
Support Element to signal when the Appliance is fully up and running.
Basic support for OFB was added to the kernel with the following commit
https://github.com/projectacrn/acrn-kernel/commit/c6f70d3b8a32fdec60d3f78cb59423f056f16688
The kernel config option CONFIG_SCLP_OFB need to be set
This update is mandatory for 18.04 , but need to be requested first
for 18.10
$ git grep SCLP_OFB
debian.master/config/annotations:CONFIG_SCLP_OFB
policy<{'s390x': 'n'}>
debian.master/config/config.common.ubuntu:# CONFIG_SCLP_OFB is not set
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1787898/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787240] Re: [Bionic] i2c: xlp9xx: Fix case where SSIF read transaction completes early
-- proposed verification --
ubuntu@helo:~$ uname -a
Linux helo 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:22:18 UTC 2018
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@helo:~$
Ran the test:
for i in {1..200}; do sudo ipmitool sel list ; sudo ipmitool sensor list ; sudo
ipmitool sdr list ; sudo ipmitool sel list ; done
Test ran for more than 8hrs and did not produce any errors in dmesg.
** 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/1787240
Title:
[Bionic] i2c: xlp9xx: Fix case where SSIF read transaction completes
early
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
i2c: xlp9xx: Fix case where SSIF read transaction completes early
During ipmi stress tests we see occasional failure of transactions
at the boot time. This happens in the case of a I2C_M_RECV_LEN
transactions, when the read transfer completes (with the initial
read length of 34) before the driver gets a chance to handle interrupts.
[Test]
Use ipmitool to generate a lot of data read, run multiple instances of the
following test:
for i in {1..200}; do sudo ipmitool sel list ; sudo ipmitool sensor list ;
sudo ipmitool sdr list ; sudo ipmitool sel list ; done
[Fix]
Following upstream patch fixes this issue:
commit 5eb173f5c8f3a3cdc47b3952c368f10a28c81ab8
Author: George Cherian
Date: Wed Aug 8 23:36:48 2018 -0700
i2c: xlp9xx: Fix case where SSIF read transaction completes early
[Regression Risk]
The fix is to the i2c-xlp9xx driver, and does not impact any platform code.
Risk of regression is low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787240/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I know it's kind of rude just to "+1" on an issue. But whoever is responsible for these NVidia drivers deserved it. So, +1. Issue is not fixed. Blank screen on upgrade from 16.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790602] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2018-09-05 17:50 EDT---
I recreated on the old kernel:
user@deb3qwsp1:~$ cat /proc/version
Linux version 4.15.0-33-generic (buildd@bos02-ppc64el-007) (gcc version 7.3.0
(Ubuntu 7.3.0-16ubuntu3)) #36-Ubuntu SMP Wed Aug 15 13:42:39 UTC 2018
user@deb3qwsp1:~$ for i in `seq 1 6`; do sudo cpupower idle-set -d $i; done
Idlestate 1 disabled on CPU 0
Idlestate 1 disabled on CPU 1
Idlestate 1 disabled on CPU 2
user@deb3qwsp1:~$ cpupower monitor sleep 30
sleep took 30.02607 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop | stop
0| 0| 0| 87.88| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00
0| 0| 1| 87.95| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00
0| 0| 2| 88.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00
0| 0| 3| 87.97| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00
And I booted the new kernel:
user@deb3qwsp1:~$ cat /proc/version
Linux version 4.15.0-35-generic (kamal@kathleen) (gcc version 7.3.0 (Ubuntu
7.3.0-16ubuntu3)) #38 SMP Wed Sep 5 15:07:24 UTC 2018
But looks like cpupower is part of linux-tools-4.15.0-35-generic and
just the linux-tools-common and linux-tools-hosts is available.
Can you please upload the linux-
tools-4.15.0-35-generic_4.15.0-35.38_ppc64el.deb and I can finish the
verification?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790602
Title:
Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next
state disabled (performance)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
Triaged
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-09-04
00:50:14 ==
The CPUs remain in snooze state on an idle system when only the
shallow states disabled resulting in increased power consumption.
The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze
to deeper idle state") introduced a timeout for the snooze idle state so that
it could be eventually be promoted to a deeper idlestate. The snooze
timeout value is static and set to the target residency of the next idle
state, which would train the cpuidle governor to pick the next idle state
eventually.
The unfortunate side-effect of this is that if the next idle state(s) is
disabled, the CPU will forever remain in snooze, despite the fact that the
system is completely idle, and other deeper idle states are available.
This patch fixes the issue by dynamically setting the snooze timeout to the
target residency of the next enabled state on the device.
Before Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01297 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 96.41| 0.00| 0.00
0| 8| 1| 96.43| 0.00| 0.00
0| 8| 2| 96.47| 0.00| 0.00
0| 8| 3| 96.35| 0.00| 0.00
0| 8| 4| 96.37| 0.00| 0.00
0| 8| 5| 96.37| 0.00| 0.00
0| 8| 6| 96.47| 0.00| 0.00
0| 8| 7| 96.47| 0.00| 0.00
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1, stop2)
disabled:
$ cpupower monitor sleep 30
sleep took 30.05033 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 16| 0| 89.79| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 1| 90.12| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 2| 90.21| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 3| 90.29| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
After Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01200 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 16.58| 0.00| 77.21
0| 8| 1| 18.42| 0.00| 75.38
0| 8| 2| 4.70| 0.00| 94.09
0| 8| 3| 17.06| 0.00| 81.73
0| 8| 4| 3.06| 0.00| 95.73
0| 8| 5| 7.00| 0.00| 96.80
0| 8| 6| 1.00| 0.00| 98.79
0| 8| 7| 5.62| 0.00| 94.17
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1,
stop2) disabled:
$ cpupower monitor sleep 30
sleep took 30.02110 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 0| 0| 0.69| 0.00
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
I built Xenial, Bionic and Cosmic test kernels with commit 0522236d4f9c5ab2e79889cb020d1acbe5da416e . The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1790832 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: * If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. * If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777279] Re: Resume from suspend to RAM fails with nvidia-graphics-drivers-390
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1777279 Title: Resume from suspend to RAM fails with nvidia-graphics-drivers-390 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After suspending to RAM when resuming only black screen is visible with frozen mouse cursor. Can't switch to console and reset is required. When trying to suspend to RAM with pm-suspend command system doesn't suspend at all, you can find pm-suspend.log file attached. With default nouveau drivers system resumes fine however hangs forever on shutdown. My specs: AMD Ryzen 5 1600 Kingston Predator DDR4 8GB Gigabyte GA-AB350N-Gaming WIFI MSI GeForce GTX 1060 AERO ITX SSD Crucial MX500 500GB ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaroslaw 1386 F pulseaudio /dev/snd/controlC1: jaroslaw 1386 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Jun 16 21:38:21 2018 InstallationDate: Installed on 2018-05-16 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=b5a92bcf-517e-4b97-ab26-84dbab8247c5 ro quiet splash resume=/dev/sda2 resume_offset=19075072 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1777279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787197] Re: Touchpad doesn't work well after upgrade to 18.04
I installed the linux-image-etc file for 4.18, then the linux-headers file installation says "no space left on device". Before, I had removed every file of previous kernels and installations, I only have 4.15.34 files in /boot. I wanted to increase the size of the boot partition because that's an issue on every linux update, but as my disk is encrypted, that's a lot of work. Sorry. On Ubuntu until 16.04, I could update by removing old kernels from /boot. Now, the files seem to have gotten to big for even keeping the active 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/1787197 Title: Touchpad doesn't work well after upgrade to 18.04 Status in linux package in Ubuntu: Incomplete Bug description: I upgraded my laptop (Dell XPS 13, older version) to 18.04. Now the touchpad doesn't work, unless I hit it very hard. How do I increase the sensitivity of the touchpad so I can use it like I've always done? It always worked well, until the upgrade. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christine 3495 F pulseaudio /dev/snd/controlC0: christine 3495 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1212abb0-90f7-4f0a-94bf-0d790e8b3593 InstallationDate: Installed on 2015-12-13 (975 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: MSI MS-7881 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic.efi.signed root=UUID=eea1d4c7-5f21-40a5-b73d-fed6b0a48f69 ro noprompt persistent quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.20 RfKill: Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 10/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99S XPOWER AC (MS-7881) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd10/30/2015:svnMSI:pnMS-7881:pvr1.0:rvnMSI:rnX99SXPOWERAC(MS-7881):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7881 dmi.product.version: 1.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christine 3495 F pulseaudio /dev/snd/controlC0: christine 3495 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1212abb0-90f7-4f0a-94bf-0d790e8b3593 InstallationDate: Installed on 2015-12-13 (975 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: MSI MS-7881 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic.efi.signed root=UUID=eea1d4c7-5f21-40a5-b73d-fed6b0a48f69 ro noprompt persistent quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.20 RfKill: Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 10/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99S XPOWER AC (MS-7881) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd10/30/2015:svnMSI:pnMS-7881:pvr1.0:rvnMSI:rnX99SXPOWERAC(MS-7881):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7881 dmi.product.version: 1.0 dmi.sys.vendor: MSI --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/s
[Kernel-packages] [Bug 1789519] Re: Low Memory corruption logged in syslog
** Attachment added: "Makefile" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789519/+attachment/5185076/+files/Makefile -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789519 Title: Low Memory corruption logged in syslog Status in linux package in Ubuntu: Confirmed Bug description: Dell Inspiron 3847 Desktop running Ubuntu 18.04.1 LTS kernel: 4.15.0-33-generic Corrupted low memory messages logged in syslog Can be reproduced with script: #!/bin/bash # log to syslog... logger -st low_mem_corruption.sh "Checking for low memory corruption with kernel $(uname -rv)..." # this will cause syslog messages on affected kernels... cat /proc/i8k logger -st low_mem_corruption.sh "Please wait for 90 secs to ensure low memory test has completed..." # sleep for 1.5 mins - enough time for mem check every 60 secs... sleep 90 logger -st low_mem_corruption.sh "Check for low memory corruption done! Was anything logged in syslog?" Kernels tested: Kernel 4.15.0-29-generic - fine Kernel 4.15.0-30-generic - fine Kernel 4.15.0-30-generic - Never installed, do not know - did it exist? Kernel 4.15.0-32-generic - Low Memory corruption! Kernel 4.15.0-33-generic - Low Memory corruption! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bossman1316 F pulseaudio /dev/snd/pcmC1D0p: bossman1316 F...m pulseaudio /dev/snd/controlC1: bossman1316 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 16:56:01 2018 HibernationDevice: RESUME=UUID=1c065a24-2acf-43dc-bf3d-1382f3bbf0ac InstallationDate: Installed on 2018-05-12 (108 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3847 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=a5dec663-366e-4ecc-a17a-ce4219c54897 ro quiet loglevel=3 splash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 088DT1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/10/2018:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 3847 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789519] Re: Low Memory corruption logged in syslog
** Attachment added: "dell-smm-hwmon.c" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789519/+attachment/5185075/+files/dell-smm-hwmon.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789519 Title: Low Memory corruption logged in syslog Status in linux package in Ubuntu: Confirmed Bug description: Dell Inspiron 3847 Desktop running Ubuntu 18.04.1 LTS kernel: 4.15.0-33-generic Corrupted low memory messages logged in syslog Can be reproduced with script: #!/bin/bash # log to syslog... logger -st low_mem_corruption.sh "Checking for low memory corruption with kernel $(uname -rv)..." # this will cause syslog messages on affected kernels... cat /proc/i8k logger -st low_mem_corruption.sh "Please wait for 90 secs to ensure low memory test has completed..." # sleep for 1.5 mins - enough time for mem check every 60 secs... sleep 90 logger -st low_mem_corruption.sh "Check for low memory corruption done! Was anything logged in syslog?" Kernels tested: Kernel 4.15.0-29-generic - fine Kernel 4.15.0-30-generic - fine Kernel 4.15.0-30-generic - Never installed, do not know - did it exist? Kernel 4.15.0-32-generic - Low Memory corruption! Kernel 4.15.0-33-generic - Low Memory corruption! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bossman1316 F pulseaudio /dev/snd/pcmC1D0p: bossman1316 F...m pulseaudio /dev/snd/controlC1: bossman1316 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 16:56:01 2018 HibernationDevice: RESUME=UUID=1c065a24-2acf-43dc-bf3d-1382f3bbf0ac InstallationDate: Installed on 2018-05-12 (108 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3847 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=a5dec663-366e-4ecc-a17a-ce4219c54897 ro quiet loglevel=3 splash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 088DT1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/10/2018:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 3847 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789519] Re: Low Memory corruption logged in syslog
** Attachment added: "low_mem_corruption.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789519/+attachment/5185077/+files/low_mem_corruption.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789519 Title: Low Memory corruption logged in syslog Status in linux package in Ubuntu: Confirmed Bug description: Dell Inspiron 3847 Desktop running Ubuntu 18.04.1 LTS kernel: 4.15.0-33-generic Corrupted low memory messages logged in syslog Can be reproduced with script: #!/bin/bash # log to syslog... logger -st low_mem_corruption.sh "Checking for low memory corruption with kernel $(uname -rv)..." # this will cause syslog messages on affected kernels... cat /proc/i8k logger -st low_mem_corruption.sh "Please wait for 90 secs to ensure low memory test has completed..." # sleep for 1.5 mins - enough time for mem check every 60 secs... sleep 90 logger -st low_mem_corruption.sh "Check for low memory corruption done! Was anything logged in syslog?" Kernels tested: Kernel 4.15.0-29-generic - fine Kernel 4.15.0-30-generic - fine Kernel 4.15.0-30-generic - Never installed, do not know - did it exist? Kernel 4.15.0-32-generic - Low Memory corruption! Kernel 4.15.0-33-generic - Low Memory corruption! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bossman1316 F pulseaudio /dev/snd/pcmC1D0p: bossman1316 F...m pulseaudio /dev/snd/controlC1: bossman1316 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 16:56:01 2018 HibernationDevice: RESUME=UUID=1c065a24-2acf-43dc-bf3d-1382f3bbf0ac InstallationDate: Installed on 2018-05-12 (108 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3847 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=a5dec663-366e-4ecc-a17a-ce4219c54897 ro quiet loglevel=3 splash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 088DT1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/10/2018:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 3847 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789519] Re: Low Memory corruption logged in syslog
Since I reported this issue I have tried to debug this problem and found that the function call to 'i8k_get_fn_status' in the kernel module 'dell-smm-hwmon' (code at https://github.com/torvalds/linux/blob/master/drivers/hwmon/dell-smm-hwmon.c) is what causes low memory corruption on Dell Inspiron 3847. This affects the procfs '/proc/i8k' interface only when kernel compiled with 'CONFIG_I8K' I have downloaded kernel module from https://github.com/torvalds/linux/blob/master/drivers/hwmon/dell-smm-hwmon.c and modified/compiled to debug/test this issue with possible fixes. A possible fix involves disallowing 'i8k_get_fn_status' calls for affected machines using a blacklist. I have attached modified kernel module code and makefile used as well as script and script output to check problem once modified module is loaded. Attachments: dell-smm-hwmon.c Makefile low_mem_corruption.sh script_output.txt I suspect this issue may affect other Dell machines (not just Inspiron 3847) ?? (see https://bugs.launchpad.net/i8kutils/+bug/1179282/comments/41) During the process of figuring out the likely problem I have found that the Dell SMM/BIOS seems to be buggy on various machines! Testing of modified module has been done under Ubuntu 18.04.1 LTS 4.15.0-29-generic, and 4.15.0-33-generic kernels and Linux Mint Tara 19 (4.15.0-29-generic, 4.15.0-33-generic kernels) and Linux Mint Tara 17.3 (4.4.0-134-generic, old 3.19.0-32-generic kernel) Output of tests in in attached file 'script_output.txt'. The low memory corruption problem can be reproduced on the Dell Inspiron 3847 running: Ubuntu 18.04.1 LTS, 4.15.0-32-generic Ubuntu 18.04.1 LTS, 4.15.0-33-generic Ubuntu 18.04.1 LTS, 4.19-rc1 upstream kernel (4.19.0-041900rc1) Linux Mint 19 Tara, 4.15.0-32-generic Linux Mint 19 Tara, 4.15.0-33-generic Linux Mint 17.3, OLD 3.19.0-32-generic kernel Linux Mint 17.3, 4.4.0-134-generic kernel Low memory corruption problem DOES NOT OCCUR on: Ubuntu 18.04.1 LTS, 4.15.0-29-generic Ubuntu 18.04.1 LTS, 4.15.0-30-generic Linux Mint 19 Tara, 4.15.0-29-generic I have no idea why there is different behaviour running under the different kernels noted above. Does this imply the problem may be in changes to the kernel? I am new to kernel modules and this is my first attempt at debugging one but I hope the info here is useful in fixing the problem and can be passed on to the maintainer. from https://github.com/torvalds/linux/blob/master/MAINTAINERS DELL LAPTOP SMM DRIVER M: Pali Rohár S: Maintained F: drivers/hwmon/dell-smm-hwmon.c ** Attachment added: "script_output.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789519/+attachment/5185074/+files/script_output.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789519 Title: Low Memory corruption logged in syslog Status in linux package in Ubuntu: Confirmed Bug description: Dell Inspiron 3847 Desktop running Ubuntu 18.04.1 LTS kernel: 4.15.0-33-generic Corrupted low memory messages logged in syslog Can be reproduced with script: #!/bin/bash # log to syslog... logger -st low_mem_corruption.sh "Checking for low memory corruption with kernel $(uname -rv)..." # this will cause syslog messages on affected kernels... cat /proc/i8k logger -st low_mem_corruption.sh "Please wait for 90 secs to ensure low memory test has completed..." # sleep for 1.5 mins - enough time for mem check every 60 secs... sleep 90 logger -st low_mem_corruption.sh "Check for low memory corruption done! Was anything logged in syslog?" Kernels tested: Kernel 4.15.0-29-generic - fine Kernel 4.15.0-30-generic - fine Kernel 4.15.0-30-generic - Never installed, do not know - did it exist? Kernel 4.15.0-32-generic - Low Memory corruption! Kernel 4.15.0-33-generic - Low Memory corruption! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bossman1316 F pulseaudio /dev/snd/pcmC1D0p: bossman1316 F...m pulseaudio /dev/snd/controlC1: bossman1316 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 16:56:01 2018 HibernationDevice: RESUME=UUID=1c065a24-2acf-43dc-bf3d-1382f3bbf0ac InstallationDate: Installed on 2018-05-12 (108 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3847 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB:
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Also affects: linux (Ubuntu Cosmic) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790835] Re: Ubuntu18.10 - crypto/vmx: Fix sleep-in-atomic bugs
*** This bug is a duplicate of bug 1790832 *** https://bugs.launchpad.net/bugs/1790832 ** This bug has been marked a duplicate of bug 1790832 crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.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/1790835 Title: Ubuntu18.10 - crypto/vmx: Fix sleep-in-atomic bugs Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: == Comment: #0 - Paulo Flabiano Smorigo - 2018-09-04 15:07:23 == Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790835] Re: Ubuntu18.10 - crypto/vmx: Fix sleep-in-atomic bugs
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790835 Title: Ubuntu18.10 - crypto/vmx: Fix sleep-in-atomic bugs Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: == Comment: #0 - Paulo Flabiano Smorigo - 2018-09-04 15:07:23 == Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 952080] Re: laptop immediately resumes after sending to standby
Launchpad has imported 93 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=43081. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-04-09T21:52:45+00:00 benshalom wrote: Suspending my Dell XPS 1340 laptop, using ubuntu precise, with kernels 3.2.0-22 and 3.4.0-0340400rc2.201204072235 results in immediate resume. This did not happen in 3.0.0-17. Please let me know what log files etc. I should post here in order to solve this. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/952080/comments/31 On 2012-04-09T21:54:36+00:00 benshalom wrote: A link to a downstream report made by another user: https://bugs.launchpad.net/linux/+bug/952080 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/952080/comments/32 On 2012-04-10T02:33:48+00:00 lenb wrote: 3.0.0-17 worked 3.2.0-22 (and later) fail Can you try some releases between (eg. 3.1) to bisect where the problem may have first come about? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/952080/comments/33 On 2012-04-10T03:34:55+00:00 benshalom wrote: Unfortunately the kernels from 3.1 series which are available to my distribution will not boot at all. The messages scroll fast, but I can read that this is a problem with the old OHCI-USB module. Is there any other information I can send? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/952080/comments/34 On 2012-04-10T23:03:15+00:00 benshalom wrote: The data from kernels 3.1 is unobtainable, because they do not boot. Does that mean that this bug will be incomplete forever? The problem is very real. I am willing to help in any way I can. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/952080/comments/35 On 2012-04-23T08:17:16+00:00 tianyu.lan wrote: Did you try all rc versions of the 3.1 kernel? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/952080/comments/37 On 2012-04-23T11:49:11+00:00 benshalom wrote: 3,1,0, 3.1.5 and 3.1.10 all fail to boot, so I cannot check if this issue exist in them. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/952080/comments/38 On 2012-04-24T03:01:58+00:00 lenb wrote: please show the output from cat /proc/acpi/wakeup for failing and working kernels Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/952080/comments/39 On 2012-04-24T03:57:05+00:00 benshalom wrote: Failing kernel: yotam@aku:~$ uname -a Linux aku 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux yotam@aku:~$ cat /proc/acpi/wakeup Device S-state Status Sysfs node PCI0 S5*disabled no-bus:pci:00 USB0 S3*enabled pci::00:04.0 USB1 S3*enabled pci::00:04.1 USB2 S3*enabled pci::00:06.0 USB3 S3*enabled pci::00:06.1 MAC0 S5*disabled pci::00:0a.0 AZA S5*disabled pci::00:08.0 P2P0 S5*disabled pci::00:09.0 XVR0 S5*disabled pci::00:0c.0 XVR1 S5*disabled XVR2 S5*disabled XVR3 S5*disabled pci::00:15.0 XVR4 S5*disabled pci::00:16.0 XVR5 S5*disabled pci::00:17.0 XVR6 S5*disabled pci::00:18.0 LID S3*enabled Working Kernel: yotam@aku:~$ uname -a Linux aku 3.0.0-19-generic #33-Ubuntu SMP Thu Apr 19 19:05:14 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux yotam@aku:~$ cat /proc/acpi/wakeup Device S-state Status Sysfs node PCI0 S5*disabled no-bus:pci:00 USB0 S3*disabled pci::00:04.0 USB1 S3*disabled pci::00:04.1 USB2 S3*disabled pci::00:06.0 USB3 S3*disabled pci::00:06.1 MAC0 S5*disabled pci::00:0a.0 AZA S5*disabled pci::00:08.0 P2P0 S5*disabled pci::00:09.0 XVR0 S5*disabled pci::00:0c.0 XVR1 S5*disabled XVR2 S5*disabled XVR3 S5*disabled pci::00:15.0 XVR4 S5*disabled pci::00:16.0 XVR5 S5*disabled pci::00:17.0 XVR6 S5*disabled pci::00:18.0 LID S3*enabled Reply at: https://bugs.launchp
[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
** Changed in: linux (Ubuntu)
Status: Fix Committed => 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/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
after suspend
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This upstream bug has been confirmed to affect Ubuntu users[1]. As
per the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
from system sleep. Frequency of the bug is described as once every
few days[2].
[1] E.g. this user confirms the bug & very specific workaround:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
[2] E.g. this log of crashes:
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23
This is a bug in blk-core.c. It is not specific to any one hardware
driver. Technically the suspend bug is triggered by the SCSI core -
which is used by *all SATA devices*.
The commit also includes a test which quickly and reliably proves the
existence of a horrifying bug.
I guess you might avoid this bug only if you have root on NVMe. The
other way to not hit the Xorg crash is if you don't use all your RAM,
so there's no pressure that leads to cold pages of Xorg being swapped.
Also, you won't reproduce the Xorg crash if you suspend+resume
immediately. (This frustrated my tests at one point, it only
triggered after left the system suspended over lunch :).
Fix: "block: do not use interruptible wait anywhere"
in kernel 4.17:
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428
in kernel 4.16.8:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6
lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-24.26#n856
I.e., this bug is still present in Ubuntu source package
linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details
(lspci-vnvn.log) of a system where this bug is known to happen.
Regards
Alan
WORKAROUND: Use kernel parameter:
scsi_mod.scan=sync
== Fix ==
1dc3039bc87a ("block: do not use interruptible wait anywhere")
== Regression Potential ==
Low. This patch has been sent to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
This is definitely reproducible on a D05 (arm64) with 18.04 running wayland, and the symptoms look identical. I re-tested with the 18.04.1 ISO and confirmed. ** Attachment added: "arm64-hisilicon-d05-18.04-blurry-syslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5185036/+files/arm64-hisilicon-d05-18.04-blurry-syslog.txt ** No longer affects: install-package (Ubuntu 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/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790135] Re: [drm:i915_gem_init_stolen [i915]] *ERROR* conflict detected with stolen region: [0x000000007c000000 - 0x0000000080000000]
** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Attachment added: "4.19 kernel dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790135/+attachment/5185043/+files/dmesg4.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790135 Title: [drm:i915_gem_init_stolen [i915]] *ERROR* conflict detected with stolen region: [0x7c00 - 0x8000] Status in linux package in Ubuntu: Confirmed Bug description: intel g41 error, It has been going on for 4 years. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 31 16:10:34 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions 4 Series Chipset Integrated Graphics Controller [1734:114c] InstallationDate: Installed on 2018-08-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ARCELIK AS 1YA-ARCELIK 5440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=2a7f9b0a-cc5a-44f3-8ef5-4b344566f438 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.02.3041.A1 dmi.board.name: D3041-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3041-A1 dmi.chassis.asset.tag: 93742010006534 dmi.chassis.type: 6 dmi.chassis.vendor: ARCELIK AS dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00R1.02.3041.A1:bd11/09/2010:svnARCELIKAS:pn1YA-ARCELIK5440:pvrV102:rvnFUJITSU:rnD3041-A1:rvrS26361-D3041-A1:cvnARCELIKAS:ct6:cvr: dmi.product.name: 1YA-ARCELIK 5440 dmi.product.version: V102 dmi.sys.vendor: ARCELIK AS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790778] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 16.04
*** This bug is a duplicate of bug 1790832 *** https://bugs.launchpad.net/bugs/1790832 ** This bug has been marked a duplicate of bug 1790832 crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.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/1790778 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 16.04 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Paulo Flabiano Smorigo - 2018-09-04 15:02:20 == Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790905] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790905 Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: installed linux-image-4.15.0-33-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: I don't know what happen after I updated Ubuntu. Now my speakers are not working. It shows dummy output in Sound Setting. I tried to search on net but none of the solution worked for me. Please help ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: linux-generic:amd64: Remove linux-image-generic:amd64: Remove linux-image-4.15.0-33-generic:amd64: Remove linux-image-unsigned-4.15.0-33-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Sep 5 21:35:12 2018 ErrorMessage: installed linux-image-4.15.0-33-generic package pre-removal script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=a8ac24cf-125b-48f3-9d3d-8625a57a061c InstallationDate: Installed on 2018-07-18 (48 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210f Acer, Inc Bus 001 Device 002: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80XL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=d45cd3c9-bc33-4ff7-8960-736eb1e90811 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.3 SourcePackage: linux Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: installed linux-image-4.15.0-33-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN40WW:bd04/13/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80XL dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786981] Re: [Bionic] i2c: xlp9xx: Add SMBAlert support
-- proposed testing -- ubuntu@helo:~$ uname -a Linux helo 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:22:18 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@helo:~$ ubuntu@helo:~$ dmesg | grep -i smbalert [ 36.572195] i2c i2c-0: supports SMBALERT# ubuntu@helo:~$ ** 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/1786981 Title: [Bionic] i2c: xlp9xx: Add SMBAlert support Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [IMPACT] Add support for SMBAlert to the ThunderX2 i2c driver [TEST] $ dmesg | grep -i smbalert [ 36.993477] i2c i2c-0: supports SMBALERT# [FIX] 40f4e372cba8 i2c: xlp9xx: Add support for SMBAlert [REGRESSION POTENTIAL] The patch enables SMBus Alert mechanism to i2c-xlp9xx driver. The patch is limited to the i2c driver and does not impact any platform code. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790905] Re: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: installed linux-image-4.15.0-33-generic package pre-removal script subprocess returned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790905 Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: installed linux-image-4.15.0-33-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: I don't know what happen after I updated Ubuntu. Now my speakers are not working. It shows dummy output in Sound Setting. I tried to search on net but none of the solution worked for me. Please help ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: linux-generic:amd64: Remove linux-image-generic:amd64: Remove linux-image-4.15.0-33-generic:amd64: Remove linux-image-unsigned-4.15.0-33-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Sep 5 21:35:12 2018 ErrorMessage: installed linux-image-4.15.0-33-generic package pre-removal script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=a8ac24cf-125b-48f3-9d3d-8625a57a061c InstallationDate: Installed on 2018-07-18 (48 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210f Acer, Inc Bus 001 Device 002: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80XL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=d45cd3c9-bc33-4ff7-8960-736eb1e90811 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.3 SourcePackage: linux Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: installed linux-image-4.15.0-33-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN40WW:bd04/13/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80XL dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790905] [NEW] package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: installed linux-image-4.15.0-33-generic package pre-removal script subprocess return
Public bug reported: I don't know what happen after I updated Ubuntu. Now my speakers are not working. It shows dummy output in Sound Setting. I tried to search on net but none of the solution worked for me. Please help ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: linux-generic:amd64: Remove linux-image-generic:amd64: Remove linux-image-4.15.0-33-generic:amd64: Remove linux-image-unsigned-4.15.0-33-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Sep 5 21:35:12 2018 ErrorMessage: installed linux-image-4.15.0-33-generic package pre-removal script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=a8ac24cf-125b-48f3-9d3d-8625a57a061c InstallationDate: Installed on 2018-07-18 (48 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210f Acer, Inc Bus 001 Device 002: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80XL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=d45cd3c9-bc33-4ff7-8960-736eb1e90811 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.3 SourcePackage: linux Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: installed linux-image-4.15.0-33-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN40WW:bd04/13/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80XL dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1790905 Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: installed linux-image-4.15.0-33-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: I don't know what happen after I updated Ubuntu. Now my speakers are not working. It shows dummy output in Sound Setting. I tried to search on net but none of the solution worked for me. Please help ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: linux-generic:amd64: Remove linux-image-generic:amd64: Remove linux-image-4.15.0-33-generic:amd64: Remove linux-image-unsigned-4.15.0-33-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Sep 5 21:35:12 2018 ErrorMessage: installed linux-image-4.15.0-33-generic package pre-removal script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=a8ac24cf-125b-48f3-9d3d-8625a57a061c InstallationDate: Installed on 2018-07-18 (48 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210f Acer, Inc Bus 001 Device 002: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80XL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=d45cd3c9-bc33-4ff7-8960-736eb1e90811 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Pyt
[Kernel-packages] [Bug 1790181] Re: /proc/diskstats shows weird values
I noticed the bug only after I installed munin recently. I don't know how long it may have existed before. I will test the mainline kernel as soon as I can but since the machine is used in production and can't be rebooted at will so testing probably be 2 weeks out. Thanks for your reply. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Incomplete Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787469] Re: [Bionic] integrate upstream fix for Cavium zram driver
-- proposed verification for bionic -- ubuntu@anuchin:~$ uname -a Linux anuchin 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:22:18 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@anuchin:~$ ubuntu@anuchin:~$ sudo bash root@anuchin:~# modprobe zram root@anuchin:~# echo 1 > /sys/block/zram0/reset root@anuchin:~# echo deflate > /sys/block/zram0/comp_algorithm root@anuchin:~# echo 128M > /sys/block/zram0/disksize root@anuchin:~# mkfs.ext4 -F /dev/zram0 mke2fs 1.44.1 (24-Mar-2018) Discarding device blocks: done Creating filesystem with 32768 4k blocks and 32768 inodes Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done root@anuchin:~# ** 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/1787469 Title: [Bionic] integrate upstream fix for Cavium zram driver Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Revert Sauce patches and integrate upstream fix for thunderx_zip hang. [Test] ubuntu@anuchin:~$ uname -a Linux anuchin 4.15.0-33-generic #36~lp1787469+build.1 SMP Thu Aug 16 19:43:58 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@anuchin:~$ sudo bash root@anuchin:~# modprobe zram root@anuchin:~# echo 1 > /sys/block/zram0/reset root@anuchin:~# echo deflate > /sys/block/zram0/comp_algorithm root@anuchin:~# echo 128M > /sys/block/zram0/disksize root@anuchin:~# mkfs.ext4 -F /dev/zram0 mke2fs 1.44.1 (24-Mar-2018) Discarding device blocks: done Creating filesystem with 32768 4k blocks and 32768 inodes Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done root@anuchin:~# [Fix] e7a9b05ca4c7 crypto: cavium - Fix smp_processor_id() warnings 1cc7e01ff977 crypto: cavium - Fix statistics pending request value a40c88045506 crypto: cavium - Prevent division by zero c782a8c43e94 crypto: cavium - Limit result reading attempts 37ff02acaa3d crypto: cavium - Fix fallout from CONFIG_VMAP_STACK [Regression Potential] These patches are limited to Cavium zip_crypto zram driver, and does not touch any other platform code. Also, these changes are limited to the ThunderX systems. Regression potential low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Changed in: ubuntu-power-systems 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/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790602] Re: Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance)
http://kernel.ubuntu.com/~kamal/lp1790636-lp1790602-ppc/
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
* If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
* If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.
Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790602
Title:
Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next
state disabled (performance)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
Triaged
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-09-04
00:50:14 ==
The CPUs remain in snooze state on an idle system when only the
shallow states disabled resulting in increased power consumption.
The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze
to deeper idle state") introduced a timeout for the snooze idle state so that
it could be eventually be promoted to a deeper idlestate. The snooze
timeout value is static and set to the target residency of the next idle
state, which would train the cpuidle governor to pick the next idle state
eventually.
The unfortunate side-effect of this is that if the next idle state(s) is
disabled, the CPU will forever remain in snooze, despite the fact that the
system is completely idle, and other deeper idle states are available.
This patch fixes the issue by dynamically setting the snooze timeout to the
target residency of the next enabled state on the device.
Before Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01297 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 96.41| 0.00| 0.00
0| 8| 1| 96.43| 0.00| 0.00
0| 8| 2| 96.47| 0.00| 0.00
0| 8| 3| 96.35| 0.00| 0.00
0| 8| 4| 96.37| 0.00| 0.00
0| 8| 5| 96.37| 0.00| 0.00
0| 8| 6| 96.47| 0.00| 0.00
0| 8| 7| 96.47| 0.00| 0.00
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1, stop2)
disabled:
$ cpupower monitor sleep 30
sleep took 30.05033 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 16| 0| 89.79| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 1| 90.12| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 2| 90.21| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 3| 90.29| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
After Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01200 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 16.58| 0.00| 77.21
0| 8| 1| 18.42| 0.00| 75.38
0| 8| 2| 4.70| 0.00| 94.09
0| 8| 3| 17.06| 0.00| 81.73
0| 8| 4| 3.06| 0.00| 95.73
0| 8| 5| 7.00| 0.00| 96.80
0| 8| 6| 1.00| 0.00| 98.79
0| 8| 7| 5.62| 0.00| 94.17
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1,
stop2) disabled:
$ cpupower monitor sleep 30
sleep took 30.02110 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 0| 0| 0.69| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 9.39|
89.70
0| 0| 1| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.05|
93.21
0| 0| 2| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
89.93
0| 0| 3| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
93.26
This fix (commit 0a4ec6aa035a "cpuidle: powernv: Fix promotion from snooze
if next state disabled") is in the -next branch of the powerpc tree and
upstream:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/cpuidle/cpuidle-powernv.c?id=0a4ec6aa035a52c422eceb2ed51ed88392a3d6c2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790602/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.ne
[Kernel-packages] [Bug 1790636] Re: Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered
http://kernel.ubuntu.com/~kamal/lp1790636-lp1790602-ppc/ Can you test this kernel and see if it resolves this bug? Note about installing test kernels: * If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. * If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790636 Title: Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Michael Ranweiler - 2018-09-04 01:38:39 == Problem: --- Kernel panics and Hardlockup messages when kernel crash was triggered to test kdump. There are two patches for a problem during a kernel crash: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de6e5d38417e6cdb005843db420a2974993d36ff And: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0beffc4f4c658fde86d52c837e784326e9cc875 Only the first was marked for stable (and is currently present in 18.04.1), but both should really be included to fix the problems in the commit log. Can you include the second one, too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
** Attachment removed: "arm64-hisilicon-d05-18.04-blurry-screenshot.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5183108/+files/arm64-hisilicon-d05-18.04-blurry-screenshot.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790602] Re: Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu Bionic)
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/1790602
Title:
Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next
state disabled (performance)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
Triaged
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-09-04
00:50:14 ==
The CPUs remain in snooze state on an idle system when only the
shallow states disabled resulting in increased power consumption.
The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze
to deeper idle state") introduced a timeout for the snooze idle state so that
it could be eventually be promoted to a deeper idlestate. The snooze
timeout value is static and set to the target residency of the next idle
state, which would train the cpuidle governor to pick the next idle state
eventually.
The unfortunate side-effect of this is that if the next idle state(s) is
disabled, the CPU will forever remain in snooze, despite the fact that the
system is completely idle, and other deeper idle states are available.
This patch fixes the issue by dynamically setting the snooze timeout to the
target residency of the next enabled state on the device.
Before Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01297 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 96.41| 0.00| 0.00
0| 8| 1| 96.43| 0.00| 0.00
0| 8| 2| 96.47| 0.00| 0.00
0| 8| 3| 96.35| 0.00| 0.00
0| 8| 4| 96.37| 0.00| 0.00
0| 8| 5| 96.37| 0.00| 0.00
0| 8| 6| 96.47| 0.00| 0.00
0| 8| 7| 96.47| 0.00| 0.00
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1, stop2)
disabled:
$ cpupower monitor sleep 30
sleep took 30.05033 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 16| 0| 89.79| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 1| 90.12| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 2| 90.21| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 3| 90.29| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
After Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01200 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 16.58| 0.00| 77.21
0| 8| 1| 18.42| 0.00| 75.38
0| 8| 2| 4.70| 0.00| 94.09
0| 8| 3| 17.06| 0.00| 81.73
0| 8| 4| 3.06| 0.00| 95.73
0| 8| 5| 7.00| 0.00| 96.80
0| 8| 6| 1.00| 0.00| 98.79
0| 8| 7| 5.62| 0.00| 94.17
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1,
stop2) disabled:
$ cpupower monitor sleep 30
sleep took 30.02110 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 0| 0| 0.69| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 9.39|
89.70
0| 0| 1| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.05|
93.21
0| 0| 2| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
89.93
0| 0| 3| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
93.26
This fix (commit 0a4ec6aa035a "cpuidle: powernv: Fix promotion from snooze
if next state disabled") is in the -next branch of the powerpc tree and
upstream:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/cpuidle/cpuidle-powernv.c?id=0a4ec6aa035a52c422eceb2ed51ed88392a3d6c2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790602/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790888] Re: touchpad not detected/ not working
status of the bug '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/1790888 Title: touchpad not detected/ not working Status in linux package in Ubuntu: Incomplete Bug description: docs attached --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-04 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: bionic Uname: Linux 4.18.5-041805-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790636] Re: Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) 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/1790636 Title: Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Michael Ranweiler - 2018-09-04 01:38:39 == Problem: --- Kernel panics and Hardlockup messages when kernel crash was triggered to test kdump. There are two patches for a problem during a kernel crash: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de6e5d38417e6cdb005843db420a2974993d36ff And: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0beffc4f4c658fde86d52c837e784326e9cc875 Only the first was marked for stable (and is currently present in 18.04.1), but both should really be included to fix the problems in the commit log. Can you include the second one, too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790888] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1790888/+attachment/5184992/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790888 Title: touchpad not detected/ not working Status in linux package in Ubuntu: Incomplete Bug description: docs attached --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-04 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: bionic Uname: Linux 4.18.5-041805-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790888] Re: touchpad not detected/ not working
apport information ** Tags added: apport-collected bionic ** Description changed: docs attached + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-09-04 (1 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + Tags: bionic + Uname: Linux 4.18.5-041805-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1790888/+attachment/5184991/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790888 Title: touchpad not detected/ not working Status in linux package in Ubuntu: Incomplete Bug description: docs attached --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-04 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: bionic Uname: Linux 4.18.5-041805-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790602] Re: Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance)
The patch is available in linux-stable, and could be fwd ported from
4.14, or backported from 4.17 to bionic.
-- linux-4.14.y --
3b185e667b52 cpuidle: powernv: Fix promotion from snooze if next state disabled
-- linux-4.17.y --
6de015f7f962 cpuidle: powernv: Fix promotion from snooze if next state disabled
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790602
Title:
Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next
state disabled (performance)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-09-04
00:50:14 ==
The CPUs remain in snooze state on an idle system when only the
shallow states disabled resulting in increased power consumption.
The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze
to deeper idle state") introduced a timeout for the snooze idle state so that
it could be eventually be promoted to a deeper idlestate. The snooze
timeout value is static and set to the target residency of the next idle
state, which would train the cpuidle governor to pick the next idle state
eventually.
The unfortunate side-effect of this is that if the next idle state(s) is
disabled, the CPU will forever remain in snooze, despite the fact that the
system is completely idle, and other deeper idle states are available.
This patch fixes the issue by dynamically setting the snooze timeout to the
target residency of the next enabled state on the device.
Before Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01297 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 96.41| 0.00| 0.00
0| 8| 1| 96.43| 0.00| 0.00
0| 8| 2| 96.47| 0.00| 0.00
0| 8| 3| 96.35| 0.00| 0.00
0| 8| 4| 96.37| 0.00| 0.00
0| 8| 5| 96.37| 0.00| 0.00
0| 8| 6| 96.47| 0.00| 0.00
0| 8| 7| 96.47| 0.00| 0.00
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1, stop2)
disabled:
$ cpupower monitor sleep 30
sleep took 30.05033 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 16| 0| 89.79| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 1| 90.12| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 2| 90.21| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 3| 90.29| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
After Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01200 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 16.58| 0.00| 77.21
0| 8| 1| 18.42| 0.00| 75.38
0| 8| 2| 4.70| 0.00| 94.09
0| 8| 3| 17.06| 0.00| 81.73
0| 8| 4| 3.06| 0.00| 95.73
0| 8| 5| 7.00| 0.00| 96.80
0| 8| 6| 1.00| 0.00| 98.79
0| 8| 7| 5.62| 0.00| 94.17
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1,
stop2) disabled:
$ cpupower monitor sleep 30
sleep took 30.02110 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 0| 0| 0.69| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 9.39|
89.70
0| 0| 1| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.05|
93.21
0| 0| 2| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
89.93
0| 0| 3| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
93.26
This fix (commit 0a4ec6aa035a "cpuidle: powernv: Fix promotion from snooze
if next state disabled") is in the -next branch of the powerpc tree and
upstream:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/cpuidle/cpuidle-powernv.c?id=0a4ec6aa035a52c422eceb2ed51ed88392a3d6c2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790602/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790888] Re: touchpad not detected/ not working
** Attachment added: "xlog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+attachment/5184990/+files/Xorg.0.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790888 Title: touchpad not detected/ not working Status in linux package in Ubuntu: Incomplete Bug description: docs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790888] Re: touchpad not detected/ not working
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+attachment/5184989/+files/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/1790888 Title: touchpad not detected/ not working Status in linux package in Ubuntu: Incomplete Bug description: docs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790888] 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 1790888 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/1790888 Title: touchpad not detected/ not working Status in linux package in Ubuntu: Incomplete Bug description: docs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790888] [NEW] touchpad not detected/ not working
Public bug reported: docs attached ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: touchpad ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1790888/+attachment/5184988/+files/devices ** Tags added: touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790888 Title: touchpad not detected/ not working Status in linux package in Ubuntu: Incomplete Bug description: docs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790888] Re: touchpad not detected/ not working
thanks for registration -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790888 Title: touchpad not detected/ not working Status in linux package in Ubuntu: Incomplete Bug description: docs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.
Upgrading the BIOS to 1.6 does indeed seem to fix the problem. At least it is now allowing me to boot into live mode. It's taking a while, but is has gone past the kernel panic I was seeing earlier. For those having trouble with the DC580 on BIOS V1.3, it should fix the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772038 Title: ubuntu/xubuntu 18.04 kernel crash during install. Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I've been trying to install ubuntu 18.04, but the system crashes with a kernel panic and thus won't run. So how do I report this bug? The system passes all memory tests and runs 17.10 with no problems, but will not run 18.04 There is very little data gathering that I can do, as the system will not boot, not even into text mode. PS. This back door way of creating a bug report is very poor when dealing with systems that don't run. The steps required to reproduce this bug are: 1) download Ubuntu and/or Xubuntu 2) burn the installation image to a dvd 3) insert dvd into target computer 4) power on target computer 5) wait a couple of seconds 6) Stare at frozen screen saying Kernel panic 7) Go back to step 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789653] Re: regression with EXT4 file systems and meta_bg flag
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789653
Title:
regression with EXT4 file systems and meta_bg flag
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Bug description:
== SRU Justification ==
A regression was introduced where ext4_check_descriptors() was getting
called before s_gdb_count was initialized. This regression was
introduced to Xenial in 4.4.0-134. This is fixed by mainline commit
44de022c4382.
Commit 44de022c4382 was also cc'd to upstream stable. However, it has
not made it's way into Xenial via stable updates as of yet.
== Fix ==
44de022c4382 ("ext4: fix false negatives *and* false positives in
ext4_check_descriptors()")
== Regression Potential ==
Low. This commit has been cc'd upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Hello,
In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
partitions in ext4 with flag meta_bg :
kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap
for group 0 overlaps block group descriptors
kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!
Go back with the kernel 4.4.0-133-generic and all partitions mount
correctly.
It looks like this:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd
The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: N/A
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
InstallationDate: Installed on 2017-04-28 (488 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
RelatedPackageVersions:
linux-restricted-modules-4.4.0-134-generic N/A
linux-backports-modules-4.4.0-134-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.4.0-134-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: N/A
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
InstallationDate: Installed on 2017-04-28 (488 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
ProcVersionSignature: Ubuntu 4.4.0-134.160-g
[Kernel-packages] [Bug 1790354] Re: Display refresh rate is not stored
Alas, I can't do that. I don't even have the disk space, neither the expertise. Does the kernel actually store the value, I wonder? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790354 Title: Display refresh rate is not stored Status in linux package in Ubuntu: Incomplete Bug description: After upgrade from 16.04 to 18.04, I cannot store the manual refresh rate any longer. When I go to the display settings, advanced, and store e.g. 25,00 Hz, 'Apply', go elsewhere and back to advanced display settings, it has fallen back to 'Auto'. i tried a number of times, including reboots, but it used to come back as 'Auto'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790636] Re: Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered
The bug description says that the 1st patch is in bionic (18.04.1) but I was not able to find that commit in bionic (master and master-next). The two patches are in 4.17 and 4.18 stable trees. -- linux-4.17.y -- ab830707c443 powerpc: smp_send_stop do not offline stopped CPUs -- linux-4.18.y -- c0beffc4f4c6 powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790636 Title: Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Michael Ranweiler - 2018-09-04 01:38:39 == Problem: --- Kernel panics and Hardlockup messages when kernel crash was triggered to test kdump. There are two patches for a problem during a kernel crash: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de6e5d38417e6cdb005843db420a2974993d36ff And: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0beffc4f4c658fde86d52c837e784326e9cc875 Only the first was marked for stable (and is currently present in 18.04.1), but both should really be included to fix the problems in the commit log. Can you include the second one, too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785675] Re: Security fix: check if IOMMU page is contained in the pinned physical page
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1785675
Title:
Security fix: check if IOMMU page is contained in the pinned physical
page
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is requesting commit 76fa4975f3ed in powerpc as a security fix.
This commit Fixes: 121f80ba68f1. Commit 76fa4975f3ed also requires
mainline commit 1463edca6734 as a prereq.
Both these commits have already been cc'd to upstream stable, but they
have not landed in Bionic as of yet.
== Fixes ==
1463edca6734 ("vfio/spapr: Use IOMMU pageshift rather than pagesize")
76fa4975f3ed ("KVM: PPC: Check if IOMMU page is contained in the pinned
physical page")
== Regression Potential ==
Low. These commits have also been sent to upstream stable, so have had
additional upstream review.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-08-06
12:27:59 ==
Please, add the following security fix to the distro kernel:
76fa4975f3ed KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
Also already available in the 4.14 stable tree:
58113603a4ea KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
And in the 4.17 stable tree:
970e28cb2c7a KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1785675/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789131] Re: Probable regression with EXT3 file systems and CVE-2018-1093 patches
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789131
Title:
Probable regression with EXT3 file systems and CVE-2018-1093 patches
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Committed
Bug description:
== SRU Justification ==
Mainline commit 7dac4a1726a9 introduced a regression in v4.17-rc1, which
made it's way into Trusty via upstream stable updates. This regression
is resolved by mainline commit 22be37acce25. This commit has been cc'd
to upstream stable, but has not made it's way into Trusty as of yet.
== Fix ==
22be37acce25 ("ext4: fix bitmap position validation")
== Regression Potential ==
Low. This commit has been cc'd to upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
A customer reported on all of their ext3 and none of their ext4
systems that the file system was in read-only mode, I believe after
rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
of tune2fs -l for one of the file systems:
tune2fs 1.42.12 (29-Aug-2014)
Last mounted on: /
Filesystem UUID: 748f503a-443d-4769-8dd2-45ff46b48555
Filesystem magic number: 0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options:(none)
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 1966080
Block count: 7863296
Reserved block count: 393164
Free blocks: 4568472
Free inodes: 1440187
First block: 0
Block size: 4096
Fragment size:4096
Reserved GDT blocks: 1022
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
RAID stride: 128
RAID stripe width:512
Filesystem created: Thu Feb 25 21:54:24 2016
Last mount time: Fri Aug 24 07:40:51 2018
Last write time: Fri Aug 24 07:40:51 2018
Mount count: 1
Maximum mount count: 25
Last checked: Fri Aug 24 07:38:54 2018
Check interval: 15552000 (6 months)
Next check after: Wed Feb 20 07:38:54 2019
Lifetime writes: 7381 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode:8
Default directory hash: half_md4
Directory Hash Seed: d6564a54-cd2a-4804-ad94-1e4e0e47933a
Journal backup: inode blocks
FS Error count: 210
First error time: Fri Aug 24 07:40:51 2018
First error function: ext4_validate_block_bitmap
First error line #: 376
First error inode #: 0
First error block #: 0
Last error time: Sun Aug 26 19:35:16 2018
Last error function: ext4_remount
Last error line #:4833
Last error inode #: 0
Last error block #: 0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789131/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790390] Re: Intel i915 GPU driver has wrong max resolution output for certain models
Update. This is a functional regression as a result of switching to
modesetting.
Source: https://bugs.freedesktop.org/show_bug.cgi?id=107840#c1
** Package changed: linux-signed-oem (Ubuntu) => xorg (Ubuntu)
** Tags removed: kernel-bug
** Summary changed:
- Intel i915 GPU driver has wrong max resolution output for certain models
+ Xorg cannot exceed pipeline dimensions reported by kernel
** Bug watch added: freedesktop.org Bugzilla #107840
https://bugs.freedesktop.org/show_bug.cgi?id=107840
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1790390
Title:
Xorg cannot exceed pipeline dimensions reported by kernel
Status in xorg package in Ubuntu:
New
Bug description:
The i915 driver in the Linux kernel misrepresents the max output of
certain, newer, GPUs.
The output should be 16384x16384 for newer models (on at least 7th and
8th gen Intel CPUs) but it is stuck in 8192x8192.
The problem lies in:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c
The conditional branch which is wrong is:
/* maximum framebuffer dimensions */
if (IS_GEN2(dev_priv)) {
dev->mode_config.max_width = 2048;
dev->mode_config.max_height = 2048;
} else if (IS_GEN3(dev_priv)) {
dev->mode_config.max_width = 4096;
dev->mode_config.max_height = 4096;
} else {
dev->mode_config.max_width = 8192;
dev->mode_config.max_height = 8192;
}
While I'm not certain which generations specifically allows the higher
output it is most certainly true of all iGPUs on the 7th and 8th
generation CPUs.
This is corroborated by Intel's own hardware pages, and can be proven
by running Wayland which ignores the limitation in the driver.
Bug is present both on all Ubuntu releases, including 18.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1790390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789934] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-09-05 10:16 EDT--- You are right. These 2 git commits were missing e82f2e31f5597a3de44bd27b7427f577f637c552 net/smc: optimize consumer cursor updates 684b89bc39ce4f204b1a2b180f39f2eb36a6b695 s390/ism: add device driver for internal shared memory -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789934 Title: [18.10 FEAT] Add kernel config options for SMC-R/D Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Add folliowing options for SMC-R/D CONFIG_SMC=m CONFIG_SMC_DIAG=m CONFIG_ISM=m Already provided CONFIG_HAVE_PNETID with bugzilla https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1789934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790506] Re: Upgrading to 18.04.1 from 17.10
Are you able to boot any kernels that previously worked? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790506 Title: Upgrading to 18.04.1 from 17.10 Status in linux package in Ubuntu: Incomplete Bug description: I have a HP Mini 210-1170NR that I have been using since Ubuntu 14 I believe. I have at it at 16 and currently (recently re-install 17.10 because of the possible "bug" in upgrading to 18.10.1 or even a fresh install of 18.10.1 on this same system. I believe I do remembering upgrading to 18.10 with success, but when it tries to go to 18.10.1 that is where the issue occurs. Through at least 3 attempts to upgrade my laptop to 18.10.1 it will go through the upgrade with out any errors or warnings until it does the last reboot into the updated version. It will bring up the screen that just has Ubuntu on it with the row of dots, it will go through at least one cycle of changing the colors of the dots, it will display the mouse pointer, which will not move when the mouse is moved, there will be some activity on the drive (the drive light will flash for about 5 minutes, but not sure of the exact time) then even it will not flash anymore. The screen will go blank after no activity, but moving the mouse or clicking on keys will not cause the screen to turn the display back on. Since the information gathered here is more for a working system and not the system that is having issues, and I seem to be able to re-create the issue at will, I will try and proceed with the upgrade to 18.10.1 and see if it "works" this time. What I can use from you is maybe an iso or instructions to possibly gather additional information that could be used to determine why it is not completing the update process. Any assistants you can provide will be gratefully appreciated. This is an old windows system that I put Ubuntu on and it could be I go back to 16.. and leave it there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-46-generic 4.13.0-46.51 ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 1317 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 09:08:40 2018 HibernationDevice: RESUME=UUID=393e2e20-215e-4082-bca5-cc6f1a2f5b85 InstallationDate: Installed on 2018-09-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Hewlett-Packard HP Mini 210-1100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-46-generic N/A linux-backports-modules-4.13.0-46-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3660 dmi.board.vendor: Hewlett-Packard dmi.board.version: 48.26 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd03/18/2011:svnHewlett-Packard:pnHPMini210-1100:pvr049111202B030:rvnHewlett-Packard:rn3660:rvr48.26:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Mini 210-1100 dmi.product.version: 049111202B030 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
