[Kernel-packages] [Bug 1756337] Re: kernel bug at fscache/operation.c
Due to https://bugs.launchpad.net/ubuntu/+source/apport/+bug/997020 I switched this to 'Confirmed'. ** 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/1756337 Title: kernel bug at fscache/operation.c Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Bug description: MAAS deployed Ubuntu 16.04 LTS hosts began suffering from either [577275.774627] FS-Cache: [577275.777530] FS-Cache: Assertion failed [577275.781945] FS-Cache: 6 == 5 is false [577275.786304] [ cut here ] [577275.791662] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/fs/fscache/operation.c:494! [577275.800740] invalid opcode: [#1] SMP [577275.805415] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache $ [577275.885578] ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipa$ [577275.925771] CPU: 52 PID: 39395 Comm: kworker/u161:1 Not tainted 4.10.0-19-generic #21-Ubuntu [577275.940896] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.6.0 10/31/2017 or [126530.552030] FS-Cache: [126530.554868] FS-Cache: Assertion failed [126530.559250] FS-Cache: 1 > 0 is false [126530.563472] [ cut here ] [126530.568822] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/fs/fscache/operation.c:68! [126530.577792] invalid opcode: [#1] SMP [126530.582464] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache $ [126530.662615] libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul $ [126530.700165] CPU: 6 PID: 13971 Comm: CPU 1/KVM Not tainted 4.10.0-19-generic #21-Ubuntu [126530.709227] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 01/26/2018 Possible solution here: https://patchwork.kernel.org/patch/10234815/ Using MAAS: MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1756337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814628] [NEW] divide error: 0000 with Ubuntu 18.04
Public bug reported: Got a host running lots of virtual machines crashing today with the following terminal output (if that's to any help): [3430458.298979] divide error: [#1] SMP PTI [3430458.304484] Modules linked in: cpuid vhost_net vhost tap nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink kvm_intel kvm irqbypass rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter 8021q garp mrp stp llc bonding ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas intel_cstate intel_rapl_perf ipmi_si mei_me ipmi_devintf lpc_ich mei shpchp ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi [3430458.389747] scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul mgag200 crc32_pclmul i2c_algo_bit ghash_clmulni_intel ttm pcbc mxm_wmi drm_kms_helper bnx2x aesni_intel syscopyarea sysfillrect aes_x86_64 sysimgblt fb_sys_fops crypto_simd glue_helper ptp cryptd drm pps_core ahci mdio libahci libcrc32c wmi [last unloaded: irqbypass] [3430458.440756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-43-generic #46-Ubuntu [3430458.450411] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 01/26/2018 [3430458.460008] RIP: 0010:update_group_capacity+0x19d/0x1f0 [3430458.467098] RSP: 0018:91043ec03bd8 EFLAGS: 00010247 [3430458.474207] RAX: 006314d6 RBX: 0001 RCX: 024d [3430458.483490] RDX: RSI: RDI: 00022880 [3430458.492769] RBP: 91043ec03c00 R08: 9104376dc940 R09: 1dcd6500 [3430458.502071] R10: 91043ec0 R11: 0001 R12: 910437625000 [3430458.511391] R13: 9104376dc940 R14: R15: 91043ec03c30 [3430458.520724] FS: () GS:91043ec0() knlGS: [3430458.531161] CS: 0010 DS: ES: CR0: 80050033 [3430458.538994] CR2: 00010960b008 CR3: 003f8300a002 CR4: 003626e0 [3430458.548416] DR0: DR1: DR2: [3430458.557858] DR3: DR6: fffe0ff0 DR7: 0400 [3430458.567298] Call Trace: [3430458.571507] [3430458.575253] find_busiest_group+0xff/0x9c0 [3430458.581327] load_balance+0x164/0x9c0 [3430458.586928] ? sched_clock+0x9/0x10 [3430458.592347] ? sched_clock_cpu+0x11/0xb0 [3430458.598249] rebalance_domains+0x245/0x2d0 [3430458.604372] run_rebalance_domains+0x139/0x1f0 [3430458.610901] __do_softirq+0xe4/0x2bb [3430458.616459] irq_exit+0xb8/0xc0 [3430458.621538] scheduler_ipi+0xea/0x130 [3430458.627201] smp_reschedule_interrupt+0x39/0xe0 [3430458.633860] reschedule_interrupt+0x84/0x90 [3430458.640138] [3430458.644096] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 [3430458.651289] RSP: 0018:a90100107e68 EFLAGS: 0246 ORIG_RAX: ff02 [3430458.661431] RAX: 91043ec22880 RBX: 000c2ffbd05252a7 RCX: 001f [3430458.671114] RDX: 000c2ffbd05252a7 RSI: ff1e5f04e459 RDI: [3430458.680819] RBP: a90100107ea8 R08: R09: 0d17 [3430458.690557] R10: a90100107e38 R11: 0eca R12: c900ff401f58 [3430458.700303] R13: 0004 R14: 9bb71d18 R15: [3430458.710075] ? cpuidle_enter_state+0x97/0x2f0 [3430458.716723] cpuidle_enter+0x17/0x20 [3430458.722455] call_cpuidle+0x23/0x40 [3430458.728041] do_idle+0x18c/0x1f0 [3430458.733312] cpu_startup_entry+0x73/0x80 [3430458.739293] start_secondary+0x1ab/0x200 [3430458.745229] secondary_startup_64+0xa5/0xb0 [3430458.751415] Code: 34 10 48 8b 96 38 0a 00 00 48 8b 86 30 0a 00 00 48 8b b6 a0 09 00 00 49 d1 e9 48 29 d6 ba 00 00 00 00 48 0f 48 f2 31 d2 44 01 ce <48> f7 f6 48 3d ff 03 00 00 77 0c ba 00 04 00 00 48 29 c2 48 0f [3430458.775397] RIP: update_group_capacity+0x19d/0x1f0 RSP: 91043ec03bd8 [3430458.784442] ---[ end trace c1ae6368b9740f8a ]--- [3430458.866540] Kernel panic - not syncing: Fatal exception in interrupt [3430458.866591] Kernel Offset: 0x1960 from 0x8100 (relocation range: 0x8000-0xbfff) [3430458.954898] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814628 Title: divide error: 000
[Kernel-packages] [Bug 1814628] Re: divide error: 0000 with Ubuntu 18.04
The host was inaccessible as it crashed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814628 Title: divide error: with Ubuntu 18.04 Status in linux package in Ubuntu: Incomplete Bug description: Got a host running lots of virtual machines crashing today with the following terminal output (if that's to any help): [3430458.298979] divide error: [#1] SMP PTI [3430458.304484] Modules linked in: cpuid vhost_net vhost tap nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink kvm_intel kvm irqbypass rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter 8021q garp mrp stp llc bonding ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas intel_cstate intel_rapl_perf ipmi_si mei_me ipmi_devintf lpc_ich mei shpchp ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi [3430458.389747] scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul mgag200 crc32_pclmul i2c_algo_bit ghash_clmulni_intel ttm pcbc mxm_wmi drm_kms_helper bnx2x aesni_intel syscopyarea sysfillrect aes_x86_64 sysimgblt fb_sys_fops crypto_simd glue_helper ptp cryptd drm pps_core ahci mdio libahci libcrc32c wmi [last unloaded: irqbypass] [3430458.440756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-43-generic #46-Ubuntu [3430458.450411] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 01/26/2018 [3430458.460008] RIP: 0010:update_group_capacity+0x19d/0x1f0 [3430458.467098] RSP: 0018:91043ec03bd8 EFLAGS: 00010247 [3430458.474207] RAX: 006314d6 RBX: 0001 RCX: 024d [3430458.483490] RDX: RSI: RDI: 00022880 [3430458.492769] RBP: 91043ec03c00 R08: 9104376dc940 R09: 1dcd6500 [3430458.502071] R10: 91043ec0 R11: 0001 R12: 910437625000 [3430458.511391] R13: 9104376dc940 R14: R15: 91043ec03c30 [3430458.520724] FS: () GS:91043ec0() knlGS: [3430458.531161] CS: 0010 DS: ES: CR0: 80050033 [3430458.538994] CR2: 00010960b008 CR3: 003f8300a002 CR4: 003626e0 [3430458.548416] DR0: DR1: DR2: [3430458.557858] DR3: DR6: fffe0ff0 DR7: 0400 [3430458.567298] Call Trace: [3430458.571507] [3430458.575253] find_busiest_group+0xff/0x9c0 [3430458.581327] load_balance+0x164/0x9c0 [3430458.586928] ? sched_clock+0x9/0x10 [3430458.592347] ? sched_clock_cpu+0x11/0xb0 [3430458.598249] rebalance_domains+0x245/0x2d0 [3430458.604372] run_rebalance_domains+0x139/0x1f0 [3430458.610901] __do_softirq+0xe4/0x2bb [3430458.616459] irq_exit+0xb8/0xc0 [3430458.621538] scheduler_ipi+0xea/0x130 [3430458.627201] smp_reschedule_interrupt+0x39/0xe0 [3430458.633860] reschedule_interrupt+0x84/0x90 [3430458.640138] [3430458.644096] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 [3430458.651289] RSP: 0018:a90100107e68 EFLAGS: 0246 ORIG_RAX: ff02 [3430458.661431] RAX: 91043ec22880 RBX: 000c2ffbd05252a7 RCX: 001f [3430458.671114] RDX: 000c2ffbd05252a7 RSI: ff1e5f04e459 RDI: [3430458.680819] RBP: a90100107ea8 R08: R09: 0d17 [3430458.690557] R10: a90100107e38 R11: 0eca R12: c900ff401f58 [3430458.700303] R13: 0004 R14: 9bb71d18 R15: [3430458.710075] ? cpuidle_enter_state+0x97/0x2f0 [3430458.716723] cpuidle_enter+0x17/0x20 [3430458.722455] call_cpuidle+0x23/0x40 [3430458.728041] do_idle+0x18c/0x1f0 [3430458.733312] cpu_startup_entry+0x73/0x80 [3430458.739293] start_secondary+0x1ab/0x200 [3430458.745229] secondary_startup_64+0xa5/0xb0 [3430458.751415] Code: 34 10 48 8b 96 38 0a 00 00 48 8b 86 30 0a 00 00 48 8b b6 a0 09 00 00 49 d1 e9 48 29 d6 ba 00 00 00 00 48 0f 48 f2 31 d2 44 01 ce <48> f7 f6 48 3d ff 03 00 00 77 0c ba 00 04 00 00 48 29 c2 48 0f [3430458.775397] RIP: update_group_capacity+0x19d/0x1f0 RSP: 91043ec03bd8 [3430458.784442] ---[ end trace c1ae6368b9740f8a ]--- [3430458.866540] Kernel panic - not syncing: Fatal exception in interrupt [3430458.866591] Kernel Offset: 0x1960 from 0x8100 (reloca
[Kernel-packages] [Bug 1814628] Re: divide error: 0000 with Ubuntu 18.04
We are running MAAS here and that server is one that was deployed a
month ago approximately.
1a)
[0.00] Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC
2019 (Ubuntu 4.15.0-45.48-generic 4.15.18)
[0.00] Command line:
BOOT_IMAGE=ubuntu/amd64/generic/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.223.0.5:5248/images/ubuntu/amd64/generic/bionic/daily/squashfs
ip=finer-panda:BOOTIF ip6=off overlayroot=tmpfs
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc
cloud-config-url=http://10.223.0.5:5240/MAAS/metadata/latest/by-id/yx6d6w/?op=get_preseed
apparmor=0 log_host=10.223.0.5 log_port=514 --- elevator=noop console=tty1
console=ttyS0,115200 initrd=ubuntu/amd64/generic/bionic/daily/boot-initrd
BOOTIF=01-f4-e9-d4-b6-5d-70
1b) Last check for them was a couple of months ago
1c) iDRAC says no.
2a) Say what? I tried starting it up and I got the shell appearing in the
console. Then it just shut itself down again before I had time to react to log
in. Could be a MAAS thing shutting it down?
2b) And what's that?
2c) Don't see any failures. First it boots up:
Ubuntu 18.04.1 LTS finer-panda ttyS0
finer-panda login: [ 50.049021] cloud-init[2188]: Cloud-init v.
18.4-0ubuntu1~18.04.1 running 'modules:config' at Fri, 08 Feb 2019 07:21:19
+. Up 48.36 seconds.
[ 51.015952] cloud-init[2270]: Powering node off.
ci-info: no authorized ssh keys fingerprints found for user ubuntu.
Then promptly after that:
[ 51.169438] cloud-init[2270]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running
'modules:final' at Fri, 08 Feb 2019 07:21:22 +. Up 50.67 seconds.
[ 51.169580] cloud-init[2270]: ci-info: no authorized ssh keys fingerprints
found for user ubuntu.
[ 51.169694] cloud-init[2270]: Cloud-init v. 18.4-0ubuntu1~18.04.1 finished
at Fri, 08 Feb 2019 07:21:23 +. Datasource DataSourceMAAS
[http://10.223.0.5:5240/MAs
Stopping Authorization Manager...
[ OK ] Stopped target Timers.
[ OK ] Stopped Daily apt upgrade and clean activ Stopping Accounts
Service...
[ OK ] Stopped target Host and Network Name Lookups.
Stopping Read required files in advance...
Stopping OpenBSD Secure Shell server...
Stopping LVM2 PV scan on device 8:2...
[ OK ] Unmounted /var/lib/lxcfs.
etc..
2d) This is the host running the dozens of virtual machines popping up
and shut down daily. Until this day and all the 32 exactly identical
hosts are still up and running...and have been for a month.
I'll try to dig out the info what causes it to shut down instead of
staying up.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1814628
Title:
divide error: with Ubuntu 18.04
Status in linux package in Ubuntu:
Incomplete
Bug description:
Got a host running lots of virtual machines crashing today with the
following terminal output (if that's to any help):
[3430458.298979] divide error: [#1] SMP PTI
[3430458.304484] Modules linked in: cpuid vhost_net vhost tap
nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink
kvm_intel kvm irqbypass rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace
sunrpc cachefiles fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp
bridge ebtable_filter ebtables ip6table_filter ip6_tables devlink
iptable_filter 8021q garp mrp stp llc bonding ipmi_ssif intel_rapl sb_edac
x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas intel_cstate
intel_rapl_perf ipmi_si mei_me ipmi_devintf lpc_ich mei shpchp ipmi_msghandler
acpi_power_meter mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core
iscsi_tcp libiscsi_tcp libiscsi
[3430458.389747] scsi_transport_iscsi ip_tables x_tables autofs4 btrfs
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul mgag200
crc32_pclmul i2c_algo_bit ghash_clmulni_intel ttm pcbc mxm_wmi drm_kms_helper
bnx2x aesni_intel syscopyarea sysfillrect aes_x86_64 sysimgblt fb_sys_fops
crypto_simd glue_helper ptp cryptd drm pps_core ahci mdio libahci libcrc32c wmi
[last unloaded: irqbypass]
[3430458.440756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-43-generic
#46-Ubuntu
[3430458.450411] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1
01/26/2018
[3430458.460008] RIP: 0010:update_group_capacity+0x19d/0x1f0
[3430458.467098] RSP: 0018:91043ec03bd8 EFLAGS: 00010247
[3430458.474207] RAX: 006314d6 RBX: 0001 RCX:
024d
[3430458.483490] RDX: RSI: RDI:
00022880
[3430458.492769] RBP: 91043ec03c00 R08: 910437
[Kernel-packages] [Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
still present in ubuntu 20.10 Linux lappy 5.8.0-20-generic #21-Ubuntu SMP Wed Sep 23 00:39:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [ 249.809259] nouveau :01:00.0: Direct firmware load for nouveau/nva5_fuc084 failed with error -2 [ 249.809305] nouveau :01:00.0: Direct firmware load for nouveau/nva5_fuc084d failed with error -2 [ 249.809310] nouveau :01:00.0: msvld: unable to load firmware data [ 249.809317] nouveau :01:00.0: msvld: init failed, -19 [ 249.809472] nouveau :01:00.0: Direct firmware load for nouveau/nva5_fuc084 failed with error -2 [ 249.809502] nouveau :01:00.0: Direct firmware load for nouveau/nva5_fuc084d failed with error -2 [ 249.809505] nouveau :01:00.0: msvld: unable to load firmware data [ 249.809511] nouveau :01:00.0: msvld: init failed, -19 [ 250.022979] nouveau :01:00.0: Direct firmware load for nouveau/nva5_fuc084 failed with error -2 [ 250.023001] nouveau :01:00.0: Direct firmware load for nouveau/nva5_fuc084d failed with error -2 [ 250.023004] nouveau :01:00.0: msvld: unable to load firmware data [ 250.023009] nouveau :01:00.0: msvld: init failed, -19 [ 250.023183] nouveau :01:00.0: Direct firmware load for nouveau/nva5_fuc084 failed with error -2 [ 250.023196] nouveau :01:00.0: Direct firmware load for nouveau/nva5_fuc084d failed with error -2 [ 250.023197] nouveau :01:00.0: msvld: unable to load firmware data [ 250.023200] 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 1559882] Re: Macbook Air resumes immediately after suspend
** Also affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1559882 Title: Macbook Air resumes immediately after suspend Status in linux-lts-vivid package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: New Bug description: When closing the lid on the computer, the machine suspends. Within 5 to 10 seconds, the machine resumes again with lid still closed. Opening and closing the lid again yields the same behavior again (suspend and resuming after a few seconds without opening the lid). This behaviour is the same when entering a sudo pm-suspend from the terminal, or using"Suspend" from the menu. There is one case where the behaviour described above is different. That is in the situation where machine is put into suspend for the first time after a complete reboot. In this case the machine suspends correctly and stays suspended as expected. The problem is consistent and can be reproduced as described any number of times. Disabling wi-fi (using the Broadcom 802.11 Linux STA proprietary driver) doesn't alter the behaviour described above. cat /proc/acpi/wakeup PEG0S3*disabled EC S4*disabled platform:PNP0C09:00 HDEFS3*disabled pci::00:1b.0 RP01S3*disabled pci::00:1c.0 RP02S3*disabled pci::00:1c.1 RP03S3*disabled pci::00:1c.2 ARPTS4*disabled pci::03:00.0 RP05S3*disabled pci::00:1c.4 RP06S3*disabled pci::00:1c.5 SPITS3*disabled platform:APP000D:00 XHC1S3*enabled pci::00:14.0 ADP1S4*disabled platform:ACPI0003:00 LID0S4*enabled platform:PNP0C0D:00 $ lsb_release -rd Description: Ubuntu 14.04.4 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-56-generic 3.19.0-56.62~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15 Uname: Linux 3.19.0-56-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 21 07:59:26 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-20 (91 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1559882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559882] Re: Macbook Air resumes immediately after suspend
On Macbook Air 7.2 (running Mate 16.04) closing lid suspends correctly after initial boot. Sometimes works for several cycles. Usually on second and subsequent cycles, the machine resumes again after a few seconds, while the lid is shut. From then on, this behaviour is consistent and does not change. Also same problem after manually placed into suspend from power menu. Workaraound: Disable XHC1 For example: echo XHC1 | sudo tee /proc/acpi/wakeup (toggles XHC1) This completely fixes the problem, and subsequent lid close/open works as it should. uname -r 4.4.0-18-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1559882 Title: Macbook Air resumes immediately after suspend Status in linux-lts-vivid package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: New Bug description: When closing the lid on the computer, the machine suspends. Within 5 to 10 seconds, the machine resumes again with lid still closed. Opening and closing the lid again yields the same behavior again (suspend and resuming after a few seconds without opening the lid). This behaviour is the same when entering a sudo pm-suspend from the terminal, or using"Suspend" from the menu. There is one case where the behaviour described above is different. That is in the situation where machine is put into suspend for the first time after a complete reboot. In this case the machine suspends correctly and stays suspended as expected. The problem is consistent and can be reproduced as described any number of times. Disabling wi-fi (using the Broadcom 802.11 Linux STA proprietary driver) doesn't alter the behaviour described above. cat /proc/acpi/wakeup PEG0S3*disabled EC S4*disabled platform:PNP0C09:00 HDEFS3*disabled pci::00:1b.0 RP01S3*disabled pci::00:1c.0 RP02S3*disabled pci::00:1c.1 RP03S3*disabled pci::00:1c.2 ARPTS4*disabled pci::03:00.0 RP05S3*disabled pci::00:1c.4 RP06S3*disabled pci::00:1c.5 SPITS3*disabled platform:APP000D:00 XHC1S3*enabled pci::00:14.0 ADP1S4*disabled platform:ACPI0003:00 LID0S4*enabled platform:PNP0C0D:00 $ lsb_release -rd Description: Ubuntu 14.04.4 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-56-generic 3.19.0-56.62~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15 Uname: Linux 3.19.0-56-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 21 07:59:26 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-20 (91 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1559882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457369] Re: kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel
Is there a workaround or anything I can run in 15.04 to fix this issue? My 15.04 install recently updated and now the HDMI audio output disappeared in sound devices and I have no audio at all (using a Gigabyte GA-Z87N-WIFI motherboard and Intel Core i5 4570S CPU). This is a pretty major issue for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1457369 Title: kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel Status in System76: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Fix Committed Bug description: Problem appears on multiple computers with exact same kernel update, so clearly the problem is within the kernel. 3.19.0-16 did work without any problems. Before sound worked great via HDMI, now the HDMI output is not visible in neither alsamixer nor pulseaudio. Audio via the headphone jack still works. The computers are Intel-NUC-Kit-D54250WYK: 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 09) Subsystem: Intel Corporation Device [8086:2054] Kernel driver in use: i915 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller [8086:0a0c] (rev 09) Subsystem: Intel Corporation Device [8086:2054] Kernel driver in use: snd_hda_inte dmesg gives: [3.178745] sound hdaudioC1D0: autoconfig: line_outs=1 (0x21/0x0/0x0/0x0/0x0) type:hp [3.178750] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.178753] sound hdaudioC1D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.178754] sound hdaudioC1D0:mono: mono_out=0x0 [3.178756] sound hdaudioC1D0:inputs: [3.178759] sound hdaudioC1D0: Mic=0x19 ... [3.215371] snd_hda_intel :00:03.0: Cannot turn on display power on i915 ... [3.297561] [drm] Initialized i915 1.6.0 20141121 for :00:02.0 on minor 0 ... [3.304357] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.304360] i915 :00:02.0: registered panic notifier --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: maarten1669 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 Lsusb: Bus 001 Device 008: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=6c65d9ee-31fe-4832-8907-f47ac02d6f83 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: WYLPT10H.86A.0038.2015.0410.1634 dmi.board.name: D54250WYK dmi.board.vendor: Intel Corporation dmi.board.version: H13922-302 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrWYLPT10H.86A.0038.2015.0410.1634:bd04/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD54250WYK:rvrH13922-302:cvn:ct3:cvr: --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: maarten1669 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 Lsusb: Bus 001 Device 008: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=6c65d9ee-31fe-4832-8907-f47ac02d6f83 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/10/2015 dmi.bios.vendor: In
[Kernel-packages] [Bug 1456285] Re: Intel 7260 problems on Thinkpad T440s
I am also having this problem on a Lenovo laptop running trusty (14.04.2 LTS) Now that the fix has been identified, will it be backported? What are the pros and cons of switching out the 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/1456285 Title: Intel 7260 problems on Thinkpad T440s Status in linux package in Ubuntu: Incomplete Bug description: Very intermittent and inconsistent wireless connections. Occasionally the indicator will show that the connection has been lost, but more often it seems that the indicator just shows low signal strength -- as it generally does even when the connection is working well. I'm pretty sure this is not an access-point problem because we have other devices using the same network without any problem. Here's some of the additional information that has been requested in other discussions of similar problems, although I don't fully understand what all these results mean. I have these three firmware files in /lib/firmware: [code] -rw-r--r-- 1 root root 683236 Nov 24 09:42 iwlwifi-7260-7.ucode -rw-r--r-- 1 root root 679780 Dec 1 09:16 iwlwifi-7260-8.ucode -rw-r--r-- 1 root root 680508 Dec 1 14:45 iwlwifi-7260-9.ucode [/code] dmesg | grep iwlwifi | grep firmware [code] [ 11.974201] iwlwifi :03:00.0: loaded firmware version 22.24.8.0 op_mode iwlmvm [/code] lspci -nn | grep 0280 [code] 03:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b2] (rev 83) [/code] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-52-generic 3.13.0-52.86 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: timh 2011 F pulseaudio timh 2801 F pulseaudio /dev/snd/controlC0: timh 2011 F pulseaudio timh 2801 F pulseaudio CurrentDesktop: XFCE Date: Mon May 18 12:05:48 2015 HibernationDevice: RESUME=UUID=799c429f-edb4-438c-bbc7-386342199d23 InstallationDate: Installed on 2014-03-12 (432 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: LENOVO 20ARCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-52-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-52-generic N/A linux-backports-modules-3.13.0-52-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2015-03-16 (63 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20ARCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20ARCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ARCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1437386] Re: Unable to boot LenovoThinkpad W541
I also have a w541 and I experienced the exact issue listed here when trying to install the latest Ubuntu 14.04 LTS or Kubuntu 14.04 LTS. My w541 has Core i7 4810HQ with 32GB or RAM + 240G SSD. After much research, I ended doing exactly one Arno Esser listed. Seems to be the only option at this time. I wanted to use LTS to avoid having to upgrade later, but I have no choicelooks like I have to use 15.04. I hope this gets address for the LTS too! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1437386 Title: Unable to boot LenovoThinkpad W541 Status in linux package in Ubuntu: Incomplete Bug description: I tried to boot my Lenovo Thinkpad W541 using a bootable USB(having Ubuntu 14.04 image). I could see the welcome screen where I can choose to try or install Ubuntu. Choosing either one causes a freeze. Initial boot screen shows the following error (which maybe the reason?): "mmc0 unknown controller version(3), You may experience problems" I cannot run "apport-collect" since this problem stops me from booting. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2803 F pulseaudio /dev/snd/controlC0: ubuntu 2803 F pulseaudio CasperVersion: 1.336ubuntu1 DistroRelease: Ubuntu 13.10 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20EGS01600 MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EGS01600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET72WW(2.20):bd02/26/2015:svnLENOVO:pn20EGS01600:pvrThinkPadW541:rvnLENOVO:rn20EGS01600:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20EGS01600 dmi.product.version: ThinkPad W541 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589195] Re: Machine saying "no bluetooth adaptors found" even though is has been working till few days ago.
@jsalisbury: Yes this issue started after an upgrade and there is a red Triangle with an exclamation mark inside on my task bar.It tells me the update information is outdated... and also informs me to update manually. When I initiate manual update it tell me my system is up-to-date. Kindly I also recently bought a new laptop 'Lenovo g50-70' and installed linux mint 17.3 and is having issues with wifi and bluetooth, I want to return it and get another one coz its still under warranty, can you advice me on a computer model that will work well with mint without issues because it seems that everyone with lenovo and linux have issues. 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/1589195 Title: Machine saying "no bluetooth adaptors found" even though is has been working till few days ago. Status in linux package in Ubuntu: Incomplete Bug description: T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 3 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 3.13 S: Manufacturer=Linux 3.13.0-87-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1d.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 8 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0020 Rev= 0.00 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 3 B: Alloc= 0/800 us ( 0%), #Int= 1, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 3.13 S: Manufacturer=Linux 3.13.0-87-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1a.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 6 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0020 Rev= 0.00 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 19 Spd=12 MxCh= 0 D: Ver= 1.01 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=147e ProdID=2016 Rev= 0.02 S: Manufacturer=UPEK S: Product=Biometric Coprocessor C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 4 Ivl=20ms tony@tony-ThinkPad-T410:~$ ubuntu-bug linux tony@tony-ThinkPad-T410:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-87-generic 3.13.0-87.133 ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39 Uname: Linux 3.13.0-87-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 2215 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 5 08:46:15 2016 HibernationDevice: RESUME=UUID=09a23d02-daef-4fd6-9db4-bff9e7f69b6c InstallationDate: Installed on 2014-06-27 (708 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 019: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 25U ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic root=UUID=d5cfd6a7-f53e-4c84-876a-bce38ae571d0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-87-generic N/A linux-backports-modules-3.13.0-87-generic N/A linux-firmware 1.127.22 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 25U dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1589195] [NEW] Machine saying "no bluetooth adaptors found" even though is has been working till few days ago.
Public bug reported: T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 3 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 3.13 S: Manufacturer=Linux 3.13.0-87-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1d.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 8 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0020 Rev= 0.00 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 3 B: Alloc= 0/800 us ( 0%), #Int= 1, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 3.13 S: Manufacturer=Linux 3.13.0-87-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1a.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 6 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0020 Rev= 0.00 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 19 Spd=12 MxCh= 0 D: Ver= 1.01 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=147e ProdID=2016 Rev= 0.02 S: Manufacturer=UPEK S: Product=Biometric Coprocessor C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 4 Ivl=20ms tony@tony-ThinkPad-T410:~$ ubuntu-bug linux tony@tony-ThinkPad-T410:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-87-generic 3.13.0-87.133 ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39 Uname: Linux 3.13.0-87-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 2215 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 5 08:46:15 2016 HibernationDevice: RESUME=UUID=09a23d02-daef-4fd6-9db4-bff9e7f69b6c InstallationDate: Installed on 2014-06-27 (708 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 019: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 25U ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic root=UUID=d5cfd6a7-f53e-4c84-876a-bce38ae571d0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-87-generic N/A linux-backports-modules-3.13.0-87-generic N/A linux-firmware 1.127.22 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 25U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn25U:pvrThinkPadT410:rvnLENOVO:rn25U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 25U dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589195 Title: Machine saying "no bluetooth adaptors found" even though is has been working till few days ago. Status in linux package in Ubuntu: Confirmed Bug description: T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 3 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 3.13 S: Manufacturer=Linux 3.13.0-87-generic ehci_hcd S: Product=EHCI Host Controller
[Kernel-packages] [Bug 88863] Re: Toshiba America Info Systems SD TypA Controller unsupported
This is affecting me. Toshiba Qosmio X505 Ubuntu 13.04 Linux 3.8.0-29-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/88863 Title: Toshiba America Info Systems SD TypA Controller unsupported Status in “linux” package in Ubuntu: Expired Bug description: Binary package hint: linux-source-2.6.17 As per lspci the PCI based SD card reader in Toshiba laptops is unsupported: 02:06.0 System peripheral: Toshiba America Info Systems SD TypA Controller (rev 03) This appears to be a well known issue but couldn't find it logged anywhere. There is another revisions affected: :02:0d.0 System peripheral: Toshiba America Info Systems SD TypA Controller (rev 05) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/88863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775131] Re: Ubuntu 18.04 networking issue (connection drops after approx. 15 minutes)
I second that. Seeing this on 20.04 for some reason. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775131 Title: Ubuntu 18.04 networking issue (connection drops after approx. 15 minutes) Status in linux package in Ubuntu: Confirmed Bug description: I'm currently troubleshooting some network issues on Ubuntu 18.04 LTS Bionic. After checking a few logs I noticed that the networkd-dispatcher is generating errors. I'm unsure if this is a bug but I'd like to report it over here just to be sure: ``` Jun 04 18:14:21 [servername] systemd-networkd-wait-online[2079]: managing: br2 Jun 04 18:14:22 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 7 seen, reloading interface list Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 8 seen, reloading interface list Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: ERROR:Unknown interface index 8 seen even after reload Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 8 seen, reloading interface list Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: ERROR:Unknown interface index 8 seen even after reload ``` These issues occur consistently on several servers. The problem is that I lose the connection specifically towards the internet after approx. 15 minutes. Internal facing interfaces (same hardware and driver) seem to behave differently and remain properly connected to the internal network. These network-dispatcher errors seem to occur simultanously when the connection on the external interface permanently drops. The physical network links still appears to be online when the connection is lost. I'm still also able to ping the default gateway from my provider to access the Internet. But all IP addresses beyond this gateway on the Internet seem to be unreachable. I have disabled TCP offloading and firewalls to eliminate any influences. But that didn't work. The ARP table shows that my gateway is a STALE record after the connection drops. So it seems related to the ARP-table or something likewise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775131/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 or 151 (but 4.4.0-143 works)
Another update to 4.4.0-154, still the same, screen still blank after booting, 143 still works. ** Summary changed: - [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 or 151 (but 4.4.0-143 works) + [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 or 151 or 154 (but 4.4.0-143 works) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 or 151 or 154 (but 4.4.0-143 works) Status in linux package in Ubuntu: Confirmed Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836521] Re: Mainline kernel build failure - 5.2, 5.1.17
** Package changed: ubuntu => linux (Ubuntu) ** Summary changed: - Mainline kernel build failure - 5.2, 5.1.17 + Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836521 Title: Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18 Status in linux package in Ubuntu: New Bug description: The mainline kernel builds on kernels.ubuntu.com are in failed state for the latest kernel versions. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.17/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.18/ Build seems to have failed for i386 and amd64 but succeeded for other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836521] Re: Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.amd64 ** 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/1836521 Title: Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18 Status in linux package in Ubuntu: Confirmed Bug description: The mainline kernel builds on kernels.ubuntu.com are in failed state for the latest kernel versions. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.17/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.18/ Build seems to have failed for i386 and amd64 but succeeded for other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145
Please not that Launchpad has automatically assigned this bug to mutter, but mutter is not installed on the notebook in question, so I have added linux ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145
Sorry I cannot collect log files for the kernel giving the bug. If I can collect any useful information using the kernel that does work, please let me know ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** 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/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Incomplete Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145
Sorry I cannot collect log files for the kernel giving the bug. If I can collect any useful information using the kernel that does work, please let me know ** Changed in: mutter (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145
Attached is a syslog for the boot of 4.4.0-145 from start up to shut down in the way described above. ** Attachment added: "Syslog from boot of 4.4.0-145" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255939/+files/syslog4.4.0-145 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145
Attached is Xorg log for the boot of 4.4.0-145 ** Attachment added: "Xorg log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255955/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 (but 4.4.0-143 works)
Another update to 4.4.0-148, still the same, screen still blank after booting, ** Summary changed: - [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 (but 4.4.0-143 works) + [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 (but 4.4.0-143 works) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 (but 4.4.0-143 works) Status in linux package in Ubuntu: Confirmed Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot
Tested the latest OEM kernel from -proposed on a Dell Edge Gateway 3000 running Ubuntu Server 18.04 LTS: # rmadison linux-image-oem | grep bionic-proposed linux-image-oem | 4.15.0.1035.40 | bionic-proposed | amd64 # dpkg -l | grep linux-image-oem ii linux-image-oem 4.15.0.1035.40 amd64OEM Linux kernel image Cold booted (x5) the system and instead of seeing "TPM error (2314)...selftest" messages, I see the following (expected) messages: Mar 28 18:35:01 1K5JB02 kernel: ACPI: TPM2 0x76D537C8 34 (v03 Tpm2Tabl 0001 AMI ) Mar 28 18:35:01 1K5JB02 kernel: tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) Mar 28 18:35:01 1K5JB02 kernel: tpm tpm0: A TPM error (2314) occurred attempting the self test Verified that the TPM is operational by running tpm2_listpcrs (version 3.1.3 built from source) using the in-kernel resource manager: admin@1K5JB02:~$ sudo -i root@1K5JB02:~# export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH root@1K5JB02:~# export TPM2TOOLS_TCTI_NAME=device TPM2TOOLS_DEVICE_FILE=/dev/tpmrm0 root@1K5JB02:~# tpm2_startup --clear root@1K5JB02:~# tpm2_listpcrs Bank/Algorithm: TPM_ALG_SHA1(0x0004) PCR_00: 51 3f 1d 55 df 26 29 a2 42 ac 0b bf ae 7d 76 54 ef 91 24 d3 . . . ** 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/1762672 Title: TPM intermittently fails after cold-boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold boots. The problem seems to be that the TPM gets into a state where the partial self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to completion), but instead returns TPM_RC_TESTING (meaning some tests are still running in the background). A reboot can sometimes restore TPM functionality. This bug was originally reported on a Dell XPS 13, but has also recently been reported on a Dell Edge Gateway 3000. The bug has been confirmed to be fixed in the current development release (19.04/Cosmic). [Test Case] Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop or Server and grep for the following error log message: "tpm tpm0: A TPM error (2314) occurred continue selftest" Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools should produce errors. As this bug is due to a race condition, ideally this test case would be run multiple times (20+ cold boots). Once the patch is installed the following error message may still be present in the syslog, however attempts to use the TPM should work: "tpm tpm0: A TPM error (2314) occurred attempting the self test" [Regression Potential] The chance of regression is low, as this patch was written by a well respected kernel developer with deep TPM experience. The patch is also being cherry-picked from the upstream stable and LTS kernels, and as mentioned, has already landed in Disco. [Original Description] After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently fail on cold boot. The following log messages could be observed in syslog: [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest [3.423100] tpm tpm0: TPM self test failed [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) Discussion https://lkml.org/lkml/2017/12/6/284 Fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot
I just ran an additional five cycles of the testing described in my previous comment with no failures. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM intermittently fails after cold-boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold boots. The problem seems to be that the TPM gets into a state where the partial self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to completion), but instead returns TPM_RC_TESTING (meaning some tests are still running in the background). A reboot can sometimes restore TPM functionality. This bug was originally reported on a Dell XPS 13, but has also recently been reported on a Dell Edge Gateway 3000. The bug has been confirmed to be fixed in the current development release (19.04/Cosmic). [Test Case] Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop or Server and grep for the following error log message: "tpm tpm0: A TPM error (2314) occurred continue selftest" Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools should produce errors. As this bug is due to a race condition, ideally this test case would be run multiple times (20+ cold boots). Once the patch is installed the following error message may still be present in the syslog, however attempts to use the TPM should work: "tpm tpm0: A TPM error (2314) occurred attempting the self test" [Regression Potential] The chance of regression is low, as this patch was written by a well respected kernel developer with deep TPM experience. The patch is also being cherry-picked from the upstream stable and LTS kernels, and as mentioned, has already landed in Disco. [Original Description] After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently fail on cold boot. The following log messages could be observed in syslog: [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest [3.423100] tpm tpm0: TPM self test failed [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) Discussion https://lkml.org/lkml/2017/12/6/284 Fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 (but 4.4.0-143 works)
Another update to 4.4.0-150, still the same, screen still blank after booting, ** Summary changed: - [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 (but 4.4.0-143 works) + [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 (but 4.4.0-143 works) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 (but 4.4.0-143 works) Status in linux package in Ubuntu: Confirmed Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but 4.4.0-143 works)
An update with 4.4.0-146 has been installed and there is no fix in it. The screen is still blank. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but 4.4.0-143 works) Status in linux package in Ubuntu: Confirmed Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 (but 4.4.0-143 works)
** Summary changed: - [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but 4.4.0-143 works) + [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 (but 4.4.0-143 works) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 (but 4.4.0-143 works) Status in linux package in Ubuntu: Confirmed Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
I am seeing this issue with the stock kernel in Ubuntu 20.04 on a Dell Venue Pro 7140 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in HWE Next: Confirmed Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT is set to Y, then it will make the legacy intel soc driver fail, and moreover the current sof driver can't support broadwell well, as a result, many broadwell computers with I2S codec can't support sound anymore. [Fix] Intel submitted a patch, it will make those two kconfig options exclusive, and the legacy soc's option has higher priority, if both of them are enabled, sof's option will be disabled. [Test Case] Build the kernel and check the debian/build/$buidling_dir/.config, the SND_SOC_SOF_BROADWELL_SUPPORT is disabled. [Regression Risk] Low, so far, the sof driver can't support broadwell machine well, so there is no machine use this driver yet. Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.90
[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
vanvugt: Well, I ran into a little issue. I went ahead and did a reinstall of ubuntu (at the point when I submitted my original bug, I was running PopOS). Before ANY updates, the trackpad works as it should until I launch software center (or even dmesg -w). The instant I run one of those, the track pad stops working. (kernel 5.4.0-26-generic). This activity is the same in Wayland and Xorg. After I did an update to bring it to the latest updates (kernel 5.4.0.29-generic + whatever else needed to be updated from the current ISO downloadable from Ubuntu (I downloaded it this morning to reinstall)) the trackpad works at the login screen as it should (clicks and everything), but once the full desktop is brought up it stops working. It will actually work for a few seconds until the desktop is done loading. kaihengfeng: Ok, this was interesting. I downloaded the tool and ran it, the first interesting thing is that there are 4 entries listed for the input, 3 of which are listed for Synaptics pad - /dev/hidraw0: Synaptics T Pad V 01.31 /dev/hidraw1: Synaptics T Pad V 01.31 /dev/hidraw2: SYNA7500:00 06CB:780E /dev/hidraw3: Synaptics T Pad V 01.31 hidraw0 gives data feed back as I move my finger over the trackpad, clicking the buttons show data scrolling similar to as I move my finger on the trackpad hidraw1 give basic info, but no data feed back as I click or move my finger on the trackpad - this appears to be the hid interface of the keyboard, as I press keys it shows what key I press hidraw2 Is the touch screen of the tablet portion, it gives feed back as I move my finger on the screen hidraw3 I have NO idea what this is, keypresses do nothing, trackpad interaction does nothing, touch screen does nothing, buttons on the side of the screen (volume up/down) do not trigger any feedback hidraw0 is definitely the trackpad input; I wonder if somehow when the desktop pulls up its changing what it thinks it should use for the trackpad from hidraw0 to hidraw3? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh
[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
I assume you mean output from hid-recorder - I'll attach the 4 files one at a time: This one contains hidraw0 which is the touchpad input - data in it includes me moving my finger on the touch pad. ** Attachment added: "hidraw0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370364/+files/hidraw0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git202
[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
This is hidraw2 which is the touch screen, I let it record me touching and moving my finger on the screen. ** Attachment added: "hidraw2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370366/+files/hidraw2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To mana
[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
This last one is hidraw3 - I have NO CLUE what this one is. ** Attachment added: "hidraw3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370367/+files/hidraw3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://
[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
This one is hidraw1, it is the keyboard (see sample keypresses in the output) ** Attachment added: "hidraw1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370365/+files/hidraw1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this b
[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
No change. Still stops working after a few seconds once the full desktop is active. Also I notice once it stops working at that point, if I log out the trackpad continues to not work at the logon screen. Rebooting the system brings back trackpad functionality until I log back in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xs
[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
Gave it a go - similar results to what happens when I first power it up and log in - the trackpad controls the pointer for a few seconds then stops once the desktop (I assume) is done loading. Is there any kind of command to find out what devices X and/or gnome is responding to? It almost feels like it might be switching from (I know this is not right, but just using it as reference) hidraw0 to hidraw3 ignoring hidraw0? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video
[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
Any other suggestions for what I should try? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kern
[Kernel-packages] [Bug 1868894] [NEW] [uc18] docker overlayfs* seems broken
Public bug reported: A customer recently reported that 'sudo docker run hello-world' fails on a pi3 or pi4 running UC18. Looking at the journal, the failure appears to be caused by an apparmor denial related docker's overlay2 storage driver. I've tried both the unified and the Pi3 specific UC18 images and both fail with the same error. The same command works fine on other devices running UC18 (I've tested multipass+macOS, and dragonboard), and also works on a Pi3b running our standard UC16 image. Here are the details from the UC18 image. $ snap list core16-2.43.3 8691stablecanonical✓ core core18 202001241673stablecanonical✓ base docker 18.09.9 427 stablecanonical✓ - pi 18-127 18-pi canonical✓ gadget pi-kernel 5.3.0-1019.21~18.04.1 104 18-pi canonical✓ kernel snapd 2.43.3 6438stablecanonical✓ snapd And here's the apparmor denial: Mar 24 19:38:55 localhost sudo[3095]: awe : TTY=pts/0 ; PWD=/home/awe ; USER=root ; COMMAND=/snap/bin/docker run hello-world Mar 24 19:39:02 localhost audit[2932]: AVC apparmor="DENIED" operation="open" profile="snap.docker.dockerd" name="/system-data/var/snap/docker/common/var-lib-docker/overlay2/afce643d5ac2c31f46b8c867c35abea776166c6da199fab370c30af17d314fd7-init/diff/.dockerenv" pid=2932 comm="dockerd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 I've been told this may end up being something that gets worked around in snapd, however as this looks like a regression, I'm erring on the side of caution and filing this bug anyways. Please let me know if there's anything else I can provide. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1868894 Title: [uc18] docker overlayfs* seems broken Status in linux-raspi2 package in Ubuntu: New Bug description: A customer recently reported that 'sudo docker run hello-world' fails on a pi3 or pi4 running UC18. Looking at the journal, the failure appears to be caused by an apparmor denial related docker's overlay2 storage driver. I've tried both the unified and the Pi3 specific UC18 images and both fail with the same error. The same command works fine on other devices running UC18 (I've tested multipass+macOS, and dragonboard), and also works on a Pi3b running our standard UC16 image. Here are the details from the UC18 image. $ snap list core 16-2.43.3 8691stablecanonical✓ core core18202001241673stablecanonical✓ base docker18.09.9 427 stablecanonical✓ - pi18-127 18-pi canonical✓ gadget pi-kernel 5.3.0-1019.21~18.04.1 104 18-pi canonical✓ kernel snapd 2.43.3 6438stablecanonical✓ snapd And here's the apparmor denial: Mar 24 19:38:55 localhost sudo[3095]: awe : TTY=pts/0 ; PWD=/home/awe ; USER=root ; COMMAND=/snap/bin/docker run hello-world Mar 24 19:39:02 localhost audit[2932]: AVC apparmor="DENIED" operation="open" profile="snap.docker.dockerd" name="/system-data/var/snap/docker/common/var-lib-docker/overlay2/afce643d5ac2c31f46b8c867c35abea776166c6da199fab370c30af17d314fd7-init/diff/.dockerenv" pid=2932 comm="dockerd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 I've been told this may end up being something that gets worked around in snapd, however as this looks like a regression, I'm erring on the side of caution and filing this bug anyways. Please let me know if there's anything else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1868894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806396] Re: lis3lv02d: unknown sensor type 0x0
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1806396 Title: lis3lv02d: unknown sensor type 0x0 Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: Hello, dmesg: [ 15.684425] lis3lv02d: unknown sensor type 0x0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:22:33 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827967] Re: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor
** Changed in: linux (Ubuntu) Assignee: Hui Wang (hui.wang) => tony curtis (tonyc433) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827967 Title: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] In our OEM projects, we often meet this issues, there is no any monitor plugged, but in the gnome-sound-setting, there are 4 hdmi/dp audio devices. [Fix] We check the eld_valid when reporting the hdmi/dp jack event [Test Case] On the problematic machines, we do s3 test without plugging monitor, there is no hdmi audio device in the sound-setting. On the machines without this problem, we do s3 test, pluggin/unplugging monitor test, the hdmi audio work well as before. [Regression Risk] Low. We have done many tests on machines with or without this problem, there is no regression so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 (but 4.4.0-143 works)
Another update to 4.4.0-151, still the same, screen still blank after booting, 143 still works. ** Summary changed: - [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 (but 4.4.0-143 works) + [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 or 151 (but 4.4.0-143 works) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 or 151 (but 4.4.0-143 works) Status in linux package in Ubuntu: Confirmed Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836396] Re: Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues
snappy-hwe-snaps is a project used to track work related to system stack snaps published by Canonical. Your bug most likely has to do with the bluez (or related) Debian package from the Ubuntu archive. ** Project changed: snappy-hwe-snaps => bluez ** Project changed: bluez => bluez (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1836396 Title: Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues Status in bluez package in Ubuntu: New Bug description: I'm using Ubuntu 19.04 on a Dell Inspiron Laptop that has Bluetooth enabled (visible, discoverable). Just bought a Tracfone MyFlip which uses KaiOS. Ideally, I should be able to transfer files back & forth. In fact, if a "send" a file from laptop to phone, I have no issues and the file appears. Means Bluetooth is more or less working ... devices are paired and some functionality. But if I try to send a file from phone to laptop - that does not work. There are messages on my phone, first: "File Transfer is Ready to Start". Then about 2 seconds latter: "File Transfer Fail." FYI: on KaiOS, via Files App... "Share" via "Bluetooth" and comes up with a list of paired devices, where my laptop is identified correctly. With laptop-->phone, phone bluetooth app displays messages and asks if OK to receive file. With phone-->laptop, no messages, nothing happens. Been knocking my head on this for two days now without resolution, so reaching out to community for help. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1836396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626731] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!
For anyone who is still having this problem, hopefully this will help you get your webcam working. I was able to get my webcam working and I am using a Dell Precision 7510 Laptop running Ubuntu 18.04.3. 1.) I issued "$dmesg | grep -i camera" in a terminal window and received "uvcvideo 1-11:1.0: Entity type for entity Camera 1 was not initialized!" which landed me here at this website (FYI I am still receiving that message and my camera works... as laurent.pinchart +bugzilla-kernel pointed out already it is a harmless warning). 2) I did a search for "ubuntu uvcvideo" in google and landed on "https://help.ubuntu.com/community/UVC"; which then pointed me to "https://www.berlios.de/software/linux-uvc/#download"; which then pointed me to "http://www.ideasonboard.org/uvc/";. 3) From "http://www.ideasonboard.org/uvc/";, if you scroll down to the bottom of it you will see a Downlaod section. Navigate to the "https://www.linuxtv.org/wiki/index.php/How_to_Obtain"; webpage and follow the "Basic" User's Approach instructions. 4) You may be asked to install pre-requisites during the build process. I had to issue the following command "$sudo apt install libproc- processtable-perl". 5) Once build is complete, run "$sudo make install". 6) I installed uvcdynctrl as floe suggested. I don't know if this helped or not sorry... 7) I then found and example file to test if the camera was working from "https://linuxtv.org/downloads/v4l-dvb-apis/uapi/v4l/v4l2grab.c.html";. I saved this file and tried to compile it "$gcc -o v4l2grab v4l2grab.c" and received an error that it couldn't find the libv4l2.h header file. So i searched for it using $sudo find / -name "libv4l2.h" and didn't find it. This led me to believe that I didn't have the v4l2 development library installed so I installed it $sudo apt install libv4l-dev. 8) I searched again and found it! I then set C include environment path variable to point to the directory containing the header file $export C_INCLUDE_PATH=/usr/include/ and changed #include "../libv4l/include/libv4l2.h" to just #include "libv4l2.h" 9) Tried to recompile and got a linking error, so I issued $gcc -o v4l2grab v4l2grab.c -lv4l1 -lv4l2 and waula, it compiled. Changed its permssions to be executable $chmod +755 v4l2grab (using octal format where 7 in binary is 111 corresponding to rwx for owner and 5 or 110 rw- for group and other) and ran it ./v4l2grab where then I saw the .ppm files in the directory where the executable was ran from, but this was not good enough I want live feed. 10) I then installed v4l-utils and ran $v4l2-ctl -d /dev/video0 --list- formats-ext. This gave me the parameters that are compatible with my webcam for video capture (width=1280, height=720, format=MJPG, and device index=0). 11) As a final death blow I ran the following v4l2-ctl -V --set-fmt-video=width=1280,height=720,pixelformat=MJPG --stream-mmap --stream-count=-1 --stream-to=test.jpg -d /dev/video0 but only got a single image. I think you need to incude OpenCV. Anyways, I hope this helps you atleast get images off of the webcam. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626731 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-14-generic 4.8.0-14.15 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2032 F...m pulseaudio /dev/snd/controlC0: caravena 2032 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 22 17:20:51 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (424 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-14-generic N/A linux-backports-modules-4.8.0-14-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bi
[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting
Just did a fresh upgrade of Ubuntu Mate from Xenial to Bionic. The guest packages were installed on the Xenial system prior to upgrade. During the upgrade the guest packages were upgraded, NOT removed. However, on the upgraded system the virtualbox-guest-utils.service was NOT started but could be started manually. Thus the original bug reported on this number still applies, although all the other issues found on the way seem to have been addressed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1753430 Title: virtualbox-guest-utils.service not starting Status in dkms package in Ubuntu: Fix Released Bug description: I am trialing various flavours of Ubuntu in Virtualbox virtual machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate. All version 18.04, running on Kubuntu 17.10 host. All set up identically as far as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and virtualbox-guest-x11 installed in each guest. All work fine except that shared folders does not work in 2 of the VMs. It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate. On investigation it appears that the virtualbox-guest-utils.service is not started automatically on the two versions not working. If I start it manually everything is OK. Here is the status - systemctl status virtualbox-guest-utils.service ● virtualbox-guest-utils.service - Virtualbox guest utils Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; enabled; vendor preset: enabled) Active: inactive (dead) Looking in journalctl there are no messages showing that the service tried to start and failed. There is nothing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virtualbox-guest-utils 5.2.8-dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic i686 ApportVersion: 2.20.8-0ubuntu10 Architecture: i386 CurrentDesktop: LXDE Date: Mon Mar 5 09:53:02 2018 InstallationDate: Installed on 2012-10-23 (1958 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: virtualbox UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1753430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Bug still present in 4.15.0-38-generic on HP Notebook - 15-ba047na. $ uname -r 4.15.0-38-generic $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1583.409 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.78 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Systems with acpi-lpss can't do S3/S4 on Bionic. [Test] Users confirmed these patches work for them. [Fix] Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system sleep handling) applies quirks for both runtime and system suspend. This causes problems for some systems, so avoid using quirks on S3 and S4. [Regression Potential] Low. These patches are in upstream stable, and it brings back driver's old behavior. ===Original Bug Report=== I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : ker
[Kernel-packages] [Bug 1800859] [NEW] Fail to wake from suspend in Ubuntu 18.10
Public bug reported: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description:Ubuntu 18.10 Release:18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 10 PASIDCtl: Enable+ Exec- Priv- Kernel driver in use: amdgpu Kernel modules: amdgpu 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio [1002:9840] Subsystem: Hewlett-Packard Company Kabini HDMI/DP Audio [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSE
[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10
/var/log/kern.log (Correct suspend) --- Oct 31 14:49:13 g0wfv kernel: [ 1526.582399] atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0). Oct 31 14:49:13 g0wfv kernel: [ 1526.582406] atkbd serio0: Use 'setkeycodes e058 ' to make it known. Oct 31 14:49:13 g0wfv kernel: [ 1526.591522] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0). Oct 31 14:49:13 g0wfv kernel: [ 1526.591529] atkbd serio0: Use 'setkeycodes e058 ' to make it known. Oct 31 14:49:13 g0wfv kernel: [ 1526.929334] wlo1: deauthenticating from c0:ff:d4:71:dd:c8 by local choice (Reason: 3=DEAUTH_LEAVING) Oct 31 14:49:17 g0wfv kernel: [ 1530.941539] PM: suspend entry (deep) Oct 31 14:49:17 g0wfv kernel: [ 1530.941544] PM: Syncing filesystems ... done. Oct 31 14:49:23 g0wfv kernel: [ 1531.403144] Freezing user space processes ... (elapsed 0.003 seconds) done. Oct 31 14:49:23 g0wfv kernel: [ 1531.406255] OOM killer disabled. Oct 31 14:49:23 g0wfv kernel: [ 1531.406256] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Oct 31 14:49:23 g0wfv kernel: [ 1531.408315] Suspending console(s) (use no_console_suspend to debug) Oct 31 14:49:23 g0wfv kernel: [ 1531.425977] sd 0:0:0:0: [sda] Synchronizing SCSI cache Oct 31 14:49:23 g0wfv kernel: [ 1531.607574] sd 0:0:0:0: [sda] Stopping disk Oct 31 14:49:23 g0wfv kernel: [ 1532.762024] ACPI: EC: interrupt blocked Oct 31 14:49:23 g0wfv kernel: [ 1532.781877] pci_raw_set_power_state: 31 callbacks suppressed Oct 31 14:49:23 g0wfv kernel: [ 1532.781885] snd_hda_intel :00:09.2: Refused to change power state, currently in D0 Oct 31 14:49:23 g0wfv kernel: [ 1532.801924] ACPI: Preparing to enter system sleep state S3 Oct 31 14:49:23 g0wfv kernel: [ 1532.810201] ACPI: EC: event blocked Oct 31 14:49:23 g0wfv kernel: [ 1532.810203] ACPI: EC: EC stopped Oct 31 14:49:23 g0wfv kernel: [ 1532.810204] PM: Saving platform NVS memory Oct 31 14:49:23 g0wfv kernel: [ 1532.810283] Disabling non-boot CPUs ... Oct 31 14:49:23 g0wfv kernel: [ 1532.826448] IRQ 37: no longer affine to CPU1 Oct 31 14:49:23 g0wfv kernel: [ 1532.827561] smpboot: CPU 1 is now offline Oct 31 14:49:23 g0wfv kernel: [ 1532.850783] IRQ 35: no longer affine to CPU2 Oct 31 14:49:23 g0wfv kernel: [ 1532.851832] smpboot: CPU 2 is now offline Oct 31 14:49:23 g0wfv kernel: [ 1532.882702] IRQ 18: no longer affine to CPU3 Oct 31 14:49:23 g0wfv kernel: [ 1532.882725] IRQ 28: no longer affine to CPU3 Oct 31 14:49:23 g0wfv kernel: [ 1532.882731] IRQ 29: no longer affine to CPU3 Oct 31 14:49:23 g0wfv kernel: [ 1532.882740] IRQ 33: no longer affine to CPU3 Oct 31 14:49:23 g0wfv kernel: [ 1532.883787] smpboot: CPU 3 is now offline Oct 31 14:49:23 g0wfv kernel: [ 1532.888683] ACPI: Low-level resume complete Oct 31 14:49:23 g0wfv kernel: [ 1532.888725] ACPI: EC: EC started Oct 31 14:49:23 g0wfv kernel: [ 1532.888726] PM: Restoring platform NVS memory Oct 31 14:49:23 g0wfv kernel: [ 1532.26] LVT offset 0 assigned for vector 0x400 Oct 31 14:49:23 g0wfv kernel: [ 1532.889090] Enabling non-boot CPUs ... Oct 31 14:49:23 g0wfv kernel: [ 1532.889171] x86: Booting SMP configuration: Oct 31 14:49:23 g0wfv kernel: [ 1532.889172] smpboot: Booting Node 0 Processor 1 APIC 0x11 Oct 31 14:49:23 g0wfv kernel: [ 1532.891503] cache: parent cpu1 should not be sleeping Oct 31 14:49:23 g0wfv kernel: [ 1532.891594] microcode: CPU1: patch_level=0x06006115 Oct 31 14:49:23 g0wfv kernel: [ 1532.891750] CPU1 is up Oct 31 14:49:23 g0wfv kernel: [ 1532.891813] smpboot: Booting Node 0 Processor 2 APIC 0x12 Oct 31 14:49:23 g0wfv kernel: [ 1532.894309] cache: parent cpu2 should not be sleeping Oct 31 14:49:23 g0wfv kernel: [ 1532.894431] microcode: CPU2: patch_level=0x06006115 Oct 31 14:49:23 g0wfv kernel: [ 1532.894666] CPU2 is up Oct 31 14:49:23 g0wfv kernel: [ 1532.894686] smpboot: Booting Node 0 Processor 3 APIC 0x13 Oct 31 14:49:23 g0wfv kernel: [ 1532.897085] cache: parent cpu3 should not be sleeping Oct 31 14:49:23 g0wfv kernel: [ 1532.897192] microcode: CPU3: patch_level=0x06006115 Oct 31 14:49:23 g0wfv kernel: [ 1532.897635] CPU3 is up Oct 31 14:49:23 g0wfv kernel: [ 1532.898310] ACPI: Waking up from system sleep state S3 Oct 31 14:49:23 g0wfv kernel: [ 1532.925268] ACPI: EC: interrupt unblocked Oct 31 14:49:23 g0wfv kernel: [ 1532.965438] ACPI: EC: event unblocked Oct 31 14:49:23 g0wfv kernel: [ 1532.966134] [drm] PCIE GART of 1024M enabled (table at 0x00F4). Oct 31 14:49:23 g0wfv kernel: [ 1532.966918] sd 0:0:0:0: [sda] Starting disk Oct 31 14:49:23 g0wfv kernel: [ 1532.998225] [drm] UVD initialized successfully. Oct 31 14:49:23 g0wfv kernel: [ 1533.198643] [drm] VCE initialized successfully. Oct 31 14:49:23 g0wfv kernel: [ 1533.200161] r8169 :01:00.0 enp1s0: link down Oct 31 14:49:23 g0wfv kernel: [ 1533.222588] usb 1-1.4: reset full-speed USB device number 3 using ehci-pci Oct 31 14:49:23 g0wfv kernel: [ 1533.770442] ata2: SATA link
[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10
apport information ** Tags added: apport-collected ** Description changed: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 10 PASIDCtl: Enable+ Exec- Priv- Kernel driver in use: amdgpu Kernel modules: amdgpu 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio [1002:9840] Subsystem: Hewlett-Packard Company Kabini HDMI/DP Audio [103c:81f9] Control: I/O+ Me
[Kernel-packages] [Bug 1800859] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207565/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-,
[Kernel-packages] [Bug 1800859] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207568/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Widt
[Kernel-packages] [Bug 1800859] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207564/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width:
[Kernel-packages] [Bug 1800859] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207567/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Widt
[Kernel-packages] [Bug 1800859] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207569/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, M
[Kernel-packages] [Bug 1800859] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207566/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PAS
[Kernel-packages] [Bug 1800859] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207571/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, M
[Kernel-packages] [Bug 1800859] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207570/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap:
[Kernel-packages] [Bug 1800859] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207577/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max
[Kernel-packages] [Bug 1800859] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207574/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max P
[Kernel-packages] [Bug 1800859] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207572/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Pr
[Kernel-packages] [Bug 1800859] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207575/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Wi
[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10
I'm waiting for it to fail again before posting more info. Once it does I will try the upstream kernel. But to answer the question, this was happening in 18.04 (kernel version 4.15.0-38-generic) prior to upgrade, and has failed once since upgrade to 18.10 earlier this afternoon. (But as luck would have it, it won't fail on demand for me now!) Last time I can remember this particular system resuming from suspend reliably was probably just prior to install of 18.04 from new - previously it was running 18.04 upgraded from 17.10 (and earlier!) I'll keep an eye on it and report back. Annoyingly, for now though, it seems to be resuming OK! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 C
[Kernel-packages] [Bug 1800859] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207573/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, M
[Kernel-packages] [Bug 1800859] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1800859/+attachment/5207576/+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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Wi
[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10
Failed wake after suspend ... Oct 31 15:55:08 g0wfv kernel: [ 3212.930714] atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0). Oct 31 15:55:08 g0wfv kernel: [ 3212.930721] atkbd serio0: Use 'setkeycodes e058 ' to make it known. Oct 31 15:55:08 g0wfv kernel: [ 3212.940557] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0). Oct 31 15:55:08 g0wfv kernel: [ 3212.940564] atkbd serio0: Use 'setkeycodes e058 ' to make it known. Oct 31 15:55:09 g0wfv kernel: [ 3213.238559] wlo1: deauthenticating from c0:ff:d4:71:dd:c8 by local choice (Reason: 3=DEAUTH_LEAVING) Oct 31 15:55:12 g0wfv kernel: [ 3216.833285] PM: suspend entry (deep) Oct 31 18:04:32 g0wfv kernel: [ 3216.833293] PM: Syncing filesystems ... done. Oct 31 18:04:32 g0wfv kernel: [ 3217.556685] Freezing user space processes ... (elapsed 0.003 seconds) done. Oct 31 18:04:32 g0wfv kernel: [ 3217.560474] OOM killer disabled. Oct 31 18:04:32 g0wfv kernel: [ 3217.560476] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done. Oct 31 18:04:32 g0wfv kernel: [ 3217.562636] Suspending console(s) (use no_console_suspend to debug) Oct 31 18:04:32 g0wfv kernel: [ 3217.583712] sd 0:0:0:0: [sda] Synchronizing SCSI cache Oct 31 18:04:32 g0wfv kernel: [ 3217.791855] sd 0:0:0:0: [sda] Stopping disk Oct 31 18:04:32 g0wfv kernel: [ 3218.954069] ACPI: EC: interrupt blocked Oct 31 18:04:32 g0wfv kernel: [ 3218.974774] snd_hda_intel :00:09.2: Refused to change power state, currently in D0 Oct 31 18:04:32 g0wfv kernel: [ 3218.994804] ACPI: Preparing to enter system sleep state S3 Oct 31 18:04:32 g0wfv kernel: [ 3219.002312] ACPI: EC: event blocked Oct 31 18:04:32 g0wfv kernel: [ 3219.002314] ACPI: EC: EC stopped Oct 31 18:04:32 g0wfv kernel: [ 3219.002315] PM: Saving platform NVS memory Oct 31 18:04:32 g0wfv kernel: [ 3219.002397] Disabling non-boot CPUs ... Oct 31 18:04:32 g0wfv kernel: [ 3219.016440] smpboot: CPU 1 is now offline Oct 31 18:04:32 g0wfv kernel: [ 3219.040670] smpboot: CPU 2 is now offline Oct 31 18:04:32 g0wfv kernel: [ 3219.072570] smpboot: CPU 3 is now offline Oct 31 18:04:32 g0wfv kernel: [ 3219.075473] ACPI: Low-level resume complete Oct 31 18:04:32 g0wfv kernel: [ 3219.075557] ACPI: EC: EC started Oct 31 18:04:32 g0wfv kernel: [ 3219.075558] PM: Restoring platform NVS memory Oct 31 18:04:32 g0wfv kernel: [ 3219.075659] LVT offset 0 assigned for vector 0x400 Oct 31 18:04:32 g0wfv kernel: [ 3219.075942] Enabling non-boot CPUs ... Oct 31 18:04:32 g0wfv kernel: [ 3219.076051] x86: Booting SMP configuration: Oct 31 18:04:32 g0wfv kernel: [ 3219.076052] smpboot: Booting Node 0 Processor 1 APIC 0x11 Oct 31 18:04:32 g0wfv kernel: [ 3219.078382] cache: parent cpu1 should not be sleeping Oct 31 18:04:32 g0wfv kernel: [ 3219.078473] microcode: CPU1: patch_level=0x06006115 Oct 31 18:04:32 g0wfv kernel: [ 3219.078630] CPU1 is up Oct 31 18:04:32 g0wfv kernel: [ 3219.078664] smpboot: Booting Node 0 Processor 2 APIC 0x12 Oct 31 18:04:32 g0wfv kernel: [ 3219.081154] cache: parent cpu2 should not be sleeping Oct 31 18:04:32 g0wfv kernel: [ 3219.081262] microcode: CPU2: patch_level=0x06006115 Oct 31 18:04:32 g0wfv kernel: [ 3219.081655] CPU2 is up Oct 31 18:04:32 g0wfv kernel: [ 3219.081721] smpboot: Booting Node 0 Processor 3 APIC 0x13 Oct 31 18:04:32 g0wfv kernel: [ 3219.084110] cache: parent cpu3 should not be sleeping Oct 31 18:04:32 g0wfv kernel: [ 3219.084209] microcode: CPU3: patch_level=0x06006115 Oct 31 18:04:32 g0wfv kernel: [ 3219.084643] CPU3 is up Oct 31 18:04:32 g0wfv kernel: [ 3219.085315] ACPI: Waking up from system sleep state S3 Oct 31 18:04:32 g0wfv kernel: [ 3219.112587] ACPI: EC: interrupt unblocked Oct 31 18:04:32 g0wfv kernel: [ 3219.158205] ACPI: EC: event unblocked Oct 31 18:04:32 g0wfv kernel: [ 3219.158986] [drm] PCIE GART of 1024M enabled (table at 0x00F4). Oct 31 18:04:32 g0wfv kernel: [ 3219.159425] sd 0:0:0:0: [sda] Starting disk Oct 31 18:04:32 g0wfv kernel: [ 3219.191933] [drm] UVD initialized successfully. Oct 31 18:04:32 g0wfv kernel: [ 3219.391445] [drm] VCE initialized successfully. Oct 31 18:04:32 g0wfv kernel: [ 3219.392666] r8169 :01:00.0 enp1s0: link down Oct 31 18:04:32 g0wfv kernel: [ 3219.392717] amdgpu :00:01.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x0001f1cf4040 flags=0x0050] Oct 31 18:04:32 g0wfv kernel: [ 3219.392720] amdgpu :00:01.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x0001f175c560 flags=0x0070] Oct 31 18:04:32 g0wfv kernel: [ 3219.392722] amdgpu :00:01.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x0001f175c570 flags=0x0070] Oct 31 18:04:32 g0wfv kernel: [ 3219.392725] amdgpu :00:01.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x0001f175c570 flags=0x0070] Oct 31 18:04:32 g0wfv kernel: [ 3219.415471] usb 1-1.4: reset full-speed USB device number 3 using ehci-pci Oct 31 18:04:32 g0wfv kernel: [ 3
[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10
Unable to boot 4.19 upstream kernel (invalid signature) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 10 PASIDCtl: Enable+ Exec- Priv- Kernel driver in
[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10
That would be a good idea (silly me!) Booted into 14.9 ... just testing as we speak! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 10 PASIDCtl: Enable+ Ex
[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10
This one failed to suspend properly on 14.9 ... Nov 1 08:30:24 g0wfv kernel: [ 282.955728] atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0). Nov 1 08:30:24 g0wfv kernel: [ 282.955736] atkbd serio0: Use 'setkeycodes e058 ' to make it known. Nov 1 08:30:24 g0wfv kernel: [ 282.964593] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0). Nov 1 08:30:24 g0wfv kernel: [ 282.964600] atkbd serio0: Use 'setkeycodes e058 ' to make it known. Nov 1 08:30:24 g0wfv kernel: [ 283.290474] wlo1: deauthenticating from c0:ff:d4:71:dd:c8 by local choice (Reason: 3=DEAUTH_LEAVING) Nov 1 08:30:28 g0wfv kernel: [ 287.130650] PM: suspend entry (deep) Nov 1 09:13:18 g0wfv kernel: [0.00] Linux version 4.19.0-041900-generic (kernel@tangerine) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #201810221809 SMP Mon Oct 22 22:11:45 UTC 2018 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-,
[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10
The above failure was exactly what I was originally experiencing in 18.04 with 4.15.0-38-generic; The only way to recover is to power off and back on. The AMDGPU failure seems to be another (sporadic) issue - it's the first time I've seen it fail this way ... More watching and testing required! ** Tags added: kernel-bug-exists-upstream ** 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/1800859 Title: Fail to wake from suspend in Ubuntu 18.10 Status in linux package in Ubuntu: Confirmed Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI)
[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10
Another failure to suspend on 4.19 (booted into 4.18 on restart) ... Nov 1 10:42:56 g0wfv kernel: [ 4694.900806] atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0). Nov 1 10:42:56 g0wfv kernel: [ 4694.900852] atkbd serio0: Use 'setkeycodes e058 ' to make it known. Nov 1 10:42:56 g0wfv kernel: [ 4694.909888] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0). Nov 1 10:42:56 g0wfv kernel: [ 4694.909892] atkbd serio0: Use 'setkeycodes e058 ' to make it known. Nov 1 10:42:56 g0wfv kernel: [ 4695.122164] wlo1: deauthenticating from c0:ff:d4:71:dd:c8 by local choice (Reason: 3=DEAUTH_LEAVING) Nov 1 10:43:00 g0wfv kernel: [ 4699.048317] PM: suspend entry (deep) Nov 1 12:13:08 g0wfv kernel: [0.00] Linux version 4.18.0-10-generic (buildd@lgw01-amd64-060) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 (Ubuntu 4.18.0-10.11-generic 4.18.12) ** Summary changed: - Fail to wake from suspend in Ubuntu 18.10 + Fail to suspend properly in Ubuntu 18.10 (Also occurred in 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/1800859 Title: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04) Status in linux package in Ubuntu: Confirmed Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- Fat
[Kernel-packages] [Bug 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)
And just for completeness, another failure on 4.18.0-10-generic ... Nov 1 13:27:49 g0wfv kernel: [ 4547.133172] atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0). Nov 1 13:27:49 g0wfv kernel: [ 4547.133179] atkbd serio0: Use 'setkeycodes e058 ' to make it known. Nov 1 13:27:49 g0wfv kernel: [ 4547.142204] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0). Nov 1 13:27:49 g0wfv kernel: [ 4547.142210] atkbd serio0: Use 'setkeycodes e058 ' to make it known. Nov 1 13:27:49 g0wfv kernel: [ 4547.387163] wlo1: deauthenticating from c0:ff:d4:71:dd:c8 by local choice (Reason: 3=DEAUTH_LEAVING) Nov 1 13:27:53 g0wfv kernel: [ 4551.104328] PM: suspend entry (deep) Nov 1 14:25:43 g0wfv kernel: [0.00] Linux version 4.18.0-10-generic (buildd@lgw01-amd64-060) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 (Ubuntu 4.18.0-10.11-generic 4.18.12) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800859 Title: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04) Status in linux package in Ubuntu: Confirmed Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported
[Kernel-packages] [Bug 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)
It seems to be behaving on 4.13.16-041316-generic (but I've not been about over the weekend to test a great deal!) Will keep an eye on it and report back this evening. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800859 Title: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04) Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (
[Kernel-packages] [Bug 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)
Yes, it suspends and resumes just fine on 4.13.16. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800859 Title: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04) Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 10 PASIDCtl: Enable+ Exec- Priv-
[Kernel-packages] [Bug 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)
4 days of running the 4.13 kernel and every time I close the lid on this laptop it's suspending and resuming without fail as it should. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800859 Title: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04) Status in linux package in Ubuntu: Incomplete Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap:
[Kernel-packages] [Bug 1762672] Re: TPM on Dell XPS 13 stopped working after upgrade to 18.04
@Tyler I've tested your kernel on a Dell Edge Gateway 3000 which was showing the same TPM selftest log messages as originally described in this bug. When cold-booted with your kernel I only see the following messages now: 14:57:44 [0.00] ACPI: TPM2 0x76D537C8 34 (v03 Tpm2Tabl 0001 AMI ) 14:57:44 [2.703384] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) 14:57:44 [2.714914] tpm tpm0: A TPM error (2314) occurred attempting the self test I was able to verify that the TPM is operational by running the following tpm2-tools commands: $ sudo tpm2_startup -T device --clear $ tpm2_nvlist (produces valid output) Note - in this case, the system is using the in-kernel resource manager, which it appears doesn't initialize the TPM, hence the need for using tpm2_startup to initialize the TPM. The version of tpm2-tools used is 2.1.0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM on Dell XPS 13 stopped working after upgrade to 18.04 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest [3.423100] tpm tpm0: TPM self test failed [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) Discussion https://lkml.org/lkml/2017/12/6/284 Fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: baz2268 F pulseaudio CurrentDesktop: XFCE Date: Tue Apr 10 11:41:57 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/cryptswap1 InstallationDate: Installed on 2018-03-01 (39 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.1 dmi.board.name: 02PG84 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762672] Re: TPM on Dell XPS 13 stopped working after upgrade to 18.04
I've run 10 cold boots on the gateway mentioned in my previous comment, and in each case after issuing a tpm2_startup clear command, I've been able to query the NVLIST of the TPM. So the back-ported patch appears to be working as advertised. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM on Dell XPS 13 stopped working after upgrade to 18.04 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest [3.423100] tpm tpm0: TPM self test failed [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) Discussion https://lkml.org/lkml/2017/12/6/284 Fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: baz2268 F pulseaudio CurrentDesktop: XFCE Date: Tue Apr 10 11:41:57 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/cryptswap1 InstallationDate: Installed on 2018-03-01 (39 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.1 dmi.board.name: 02PG84 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot
** Summary changed: - TPM on Dell XPS 13 stopped working after upgrade to 18.04 + TPM intermittently fails after cold-boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM intermittently fails after cold-boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest [3.423100] tpm tpm0: TPM self test failed [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) Discussion https://lkml.org/lkml/2017/12/6/284 Fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: baz2268 F pulseaudio CurrentDesktop: XFCE Date: Tue Apr 10 11:41:57 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/cryptswap1 InstallationDate: Installed on 2018-03-01 (39 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.1 dmi.board.name: 02PG84 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot
** Description changed: - [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) - [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest - [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest - [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest - [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest - [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest - [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest - [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest - [3.423100] tpm tpm0: TPM self test failed - [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) + [Impact] + On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold boots. The problem seems to be that the TPM gets into a state where the partial self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to completion), but instead returns TPM_RC_TESTING (meaning some tests are still running in the background). A reboot can sometimes restore TPM functionality. + + This bug was originally reported on a Dell XPS 13, but has also recently + been reported on a Dell Edge Gateway 3000. + + The bug has been confirmed to be fixed in the current development + release (19.04/Cosmic). + + [Test Case] + Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop or Server and grep for the following error log message: + + "tpm tpm0: A TPM error (2314) occurred continue selftest" + + Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools + should produce errors. + + As this bug is due to a race condition, ideally this test case would be + run multiple times (20+ cold boots). + + Once the patch is installed the following error message may still be + present in the syslog, however attempts to use the TPM should work: + + "tpm tpm0: A TPM error (2314) occurred attempting the self test" + + [Regression Potential] + The chance of regression is low, as this patch was written by a well respected kernel developer with deep TPM experience. The patch is also being cherry-picked from the upstream stable and LTS kernels, and as mentioned, has already landed in Disco. + + [Original Description] + After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently fail on cold boot. The following log messages could be observed in syslog: + + [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) + [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest + [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest + [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest + [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest + [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest + [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest + [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest + [3.423100] tpm tpm0: TPM self test failed + [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) Discussion https://lkml.org/lkml/2017/12/6/284 Fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6 - - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: linux-image-generic 4.15.0.13.14 - ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 - Uname: Linux 4.15.0-13-generic x86_64 - ApportVersion: 2.20.9-0ubuntu2 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: baz2268 F pulseaudio - CurrentDesktop: XFCE - Date: Tue Apr 10 11:41:57 2018 - EcryptfsInUse: Yes - HibernationDevice: RESUME=/dev/mapper/cryptswap1 - InstallationDate: Installed on 2018-03-01 (39 days ago) - InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) - MachineType: Dell Inc. XPS 13 9360 - ProcFB: 0 inteldrmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1 - RelatedPackageVersions: - linux-restricted-modules-4.15.0-13-generic N/A - linux-backports-modules-4.15.0-13-generic N/A - linux-firmware 1.173 - SourcePackage: linux - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 01/25/2018 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 2.5.1 - dmi.board.name: 02PG84 - dmi.board.vendor: Dell Inc. - dmi.board.version: A00 - dmi.chassis.type: 9 - dmi.chassis.vendor: Dell Inc. - dmi.modalias: dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr: - dmi.product.family: XPS - dmi.product.name: XPS 13 9360 - dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of K
[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot
@Khaled Just curious as to why this is now FixCommitted? Has Tyler's back-port landed in git for the next OEM and/or mainline kernel SRU release? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM intermittently fails after cold-boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold boots. The problem seems to be that the TPM gets into a state where the partial self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to completion), but instead returns TPM_RC_TESTING (meaning some tests are still running in the background). A reboot can sometimes restore TPM functionality. This bug was originally reported on a Dell XPS 13, but has also recently been reported on a Dell Edge Gateway 3000. The bug has been confirmed to be fixed in the current development release (19.04/Cosmic). [Test Case] Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop or Server and grep for the following error log message: "tpm tpm0: A TPM error (2314) occurred continue selftest" Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools should produce errors. As this bug is due to a race condition, ideally this test case would be run multiple times (20+ cold boots). Once the patch is installed the following error message may still be present in the syslog, however attempts to use the TPM should work: "tpm tpm0: A TPM error (2314) occurred attempting the self test" [Regression Potential] The chance of regression is low, as this patch was written by a well respected kernel developer with deep TPM experience. The patch is also being cherry-picked from the upstream stable and LTS kernels, and as mentioned, has already landed in Disco. [Original Description] After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently fail on cold boot. The following log messages could be observed in syslog: [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest [3.423100] tpm tpm0: TPM self test failed [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) Discussion https://lkml.org/lkml/2017/12/6/284 Fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot
@Tyler So it looks like we landed this just in time for the new SRU cycle, which means we're looking at a tentative release to proposed on Mar 25. Does that sound right? If so, I may check with Anthony to see if there's a possibility that linux-oem could possibly re-spin and release earlier... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM intermittently fails after cold-boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold boots. The problem seems to be that the TPM gets into a state where the partial self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to completion), but instead returns TPM_RC_TESTING (meaning some tests are still running in the background). A reboot can sometimes restore TPM functionality. This bug was originally reported on a Dell XPS 13, but has also recently been reported on a Dell Edge Gateway 3000. The bug has been confirmed to be fixed in the current development release (19.04/Cosmic). [Test Case] Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop or Server and grep for the following error log message: "tpm tpm0: A TPM error (2314) occurred continue selftest" Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools should produce errors. As this bug is due to a race condition, ideally this test case would be run multiple times (20+ cold boots). Once the patch is installed the following error message may still be present in the syslog, however attempts to use the TPM should work: "tpm tpm0: A TPM error (2314) occurred attempting the self test" [Regression Potential] The chance of regression is low, as this patch was written by a well respected kernel developer with deep TPM experience. The patch is also being cherry-picked from the upstream stable and LTS kernels, and as mentioned, has already landed in Disco. [Original Description] After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently fail on cold boot. The following log messages could be observed in syslog: [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest [3.423100] tpm tpm0: TPM self test failed [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) Discussion https://lkml.org/lkml/2017/12/6/284 Fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
Applied the 'fix' from Comment #11 by vmc(vmclark) in Linux Mint 20. The error is no longer logged. Some boots on my HP laptop with a 5400RPM spinning Hard drive are slow but some are faster but some around the same time with lz4. Hard disk performance on my laptop is better with gzip than lz4. With lz4 the PC extremely lags when some apt packages are being set up and configured and some final configurations after most or all packages are installed, set up and configured but with gzip, the lag never occurs and PC is usable. Hard disk read benchmarks are better with gzip than with lz4. I think that lz4 is more suitable for an SSD than a spinning hard drive -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901880] [NEW] rtl88x2BU won't build in 20.10
Public bug reported: I have a USB wifi adapter, I installed rtl88x2BU and for every kernel update in 20.04 dkms built it automatically without any problems. Now I have updated to 20.10 I would expect this to happen but the build fails: Building module: cleaning build area... make -j4 KERNELRELEASE=5.8.0-26-generic KVER=5.8.0-26-generic src=/usr/src/rtl88x2bu-5.3.1...(bad exit status: 2) ERROR (dkms apport): binary package for rtl88x2bu: 5.3.1 not found Error! Bad return status for module build on kernel: 5.8.0-26-generic (x86_64) Consult /var/lib/dkms/rtl88x2bu/5.3.1/build/make.log for more information. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dkms 2.8.3-4 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 11:43:38 2020 InstallationDate: Installed on 2015-06-21 (1955 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to groovy on 2020-10-23 (4 days ago) ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1901880 Title: rtl88x2BU won't build in 20.10 Status in dkms package in Ubuntu: New Bug description: I have a USB wifi adapter, I installed rtl88x2BU and for every kernel update in 20.04 dkms built it automatically without any problems. Now I have updated to 20.10 I would expect this to happen but the build fails: Building module: cleaning build area... make -j4 KERNELRELEASE=5.8.0-26-generic KVER=5.8.0-26-generic src=/usr/src/rtl88x2bu-5.3.1...(bad exit status: 2) ERROR (dkms apport): binary package for rtl88x2bu: 5.3.1 not found Error! Bad return status for module build on kernel: 5.8.0-26-generic (x86_64) Consult /var/lib/dkms/rtl88x2bu/5.3.1/build/make.log for more information. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dkms 2.8.3-4 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 11:43:38 2020 InstallationDate: Installed on 2015-06-21 (1955 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to groovy on 2020-10-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1901880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901880] Re: rtl88x2BU won't build in 20.10
Here is the make log ** Attachment added: "Make log" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1901880/+attachment/5428455/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1901880 Title: rtl88x2BU won't build in 20.10 Status in dkms package in Ubuntu: New Bug description: I have a USB wifi adapter, I installed rtl88x2BU and for every kernel update in 20.04 dkms built it automatically without any problems. Now I have updated to 20.10 I would expect this to happen but the build fails: Building module: cleaning build area... make -j4 KERNELRELEASE=5.8.0-26-generic KVER=5.8.0-26-generic src=/usr/src/rtl88x2bu-5.3.1...(bad exit status: 2) ERROR (dkms apport): binary package for rtl88x2bu: 5.3.1 not found Error! Bad return status for module build on kernel: 5.8.0-26-generic (x86_64) Consult /var/lib/dkms/rtl88x2bu/5.3.1/build/make.log for more information. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dkms 2.8.3-4 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 11:43:38 2020 InstallationDate: Installed on 2015-06-21 (1955 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to groovy on 2020-10-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1901880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574612] Re: Random hangs
I have this same problem with the UI freezing up. It always occurs when I resize a window, although not every time I resize a window. The app running inside the window isn't always the same, it is more often a code editor or a web browser, or a zoom meeting. The result is that the UI freezes up completely, although audio continues running so if I am on a video call I can still talk to people, or if I am playing something with audio, I can continue to hear it. Something seems to be going on with the machine because after a few seconds the I hear the fan turning on. I'm running an up to date 20.04.1 LTS and the kernel is 5.4.0-58-generic. GNOME version is 3.36.8, windowing X11 and it's a 64-bit install. My laptop is Hewlett-Packard HP ZBook 17 G2/2255, BIOS M70 Ver. 01.12 09/23/2015 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574612 Title: Random hangs Status in linux package in Ubuntu: Triaged Bug description: System hangs randomly. This mostly occurs anywhere between 15 minutes and a few hours after boot. Couldn't figure out the trigger. Happened while viewing YouTube, using Spotify switching to Eclipse etc. SSH still works, so I can get to the machine if the lockup occurs. That's how I submitted the bug. All screens freeze though, while audio keeps on working (like music from Spotify or sound from a YouTube video). The only thing that seems to keep working UI-wise is the mouse pointer. Had memtest running for half an hour without problems. The issue occurs multiple times a day. Issue doesn't seem to be triggered if I remove linux-image-4.2.0-35-generic and go back to linux-image-4.2.0-16-generic. Did use the linux-image-4.2.0-16-generic kernel for a few days without issues. The kern.log contains some stacktraces with the method being 'schedule'. This is around the time the hang occurs. See extra debug information for more info. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic 4.2.0-35.40 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: serrie 1815 F pulseaudio /dev/snd/pcmC0D0c: serrie 1815 F...m pulseaudio /dev/snd/controlC0: serrie 1815 F pulseaudio Date: Mon Apr 25 13:56:48 2016 InstallationDate: Installed on 2016-04-12 (13 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: docker0 no wireless extensions. enp4s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=c15a8aa0-fb21-495c-bbc6-ea4f2018dc1f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.149.3 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2016-04-22 (3 days ago) dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: B150M-A D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd01/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150M-AD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892614] [NEW] RTL8723DE firmware bug: rtw_pci 0000:0d:00.0: failed to send h2c command
Public bug reported: WiFi (WLAN) Module: Realtek RTL8723DE (came with my HP laptop). Ubuntu 20.04 is the first Ubuntu release to have the module working out of the box. Network devices as output by 'inxi -N' Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 Device-2: Realtek RTL8723DE 802.11b/g/n PCIe Adapter driver: rtw_pci Device-3: Realtek 802.11n WLAN Adapter type: USB driver: btusb The error 'rtw_pci :0d:00.0: failed to send h2c command' is logged every time I use the module for internet access. The error is logged more frequently especially if I stream a video and other related tasks. The driver is stable but it may fail become unavailable unless a cold boot is performed. The attached log contains the error logged many times when I was streaming a video Today. According to https://askubuntu.com/questions/1217892/system-responds-with-failed-to- send-h2c-command-on-shutdown-what-does-that-me the error may be due to a firmware issue or the driver issue. The error does not occur if using the Realtek drivers obtained from Github in this link: https://github.com/lwfinger/rtw88 and the driver of the module is identified as rtw_8723de. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1949 F pulseaudio /dev/snd/controlC1: tony 1949 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 08:37:12 2020 InstallationDate: Installed on 2020-08-22 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15-bs1xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=7b47411f-1984-4025-9678-8f5fba5b2059 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8444 dmi.board.vendor: HP dmi.board.version: 67.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd12/06/2019:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn8444:rvr67.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs1xx dmi.product.sku: 4UL47EA#BH5 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "rtw_pci-errors.txt" https://bugs.launchpad.net/bugs/1892614/+attachment/5403756/+files/rtw_pci-errors.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/1892614 Title: RTL8723DE firmware bug: rtw_pci :0d:00.0: failed to send h2c command Status in linux package in Ubuntu: New Bug description: WiFi (WLAN) Module: Realtek RTL8723DE (came with my HP laptop). Ubuntu 20.04 is the first Ubuntu release to have the module working out of the box. Network devices as output by 'inxi -N' Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 Device-2: Realtek RTL8723DE 802.11b/g/n PCIe Adapter driver: rtw_pci Device-3: Realtek 802.11n WLAN Adapter type: USB driver: btusb The error 'rtw_pci :0d:00.0: failed to send h2c command' is logged every time I use the module for internet access. The error is logged more frequently especially if I stream a video and other related tasks. The driver is stable but it may fail become unavailable unless a cold boot is performed. The attached log contains the error logged many times when I was streaming a video Today. According to https://askubuntu.com/questions/1217892/system-responds-with-failed- to-send-h2c-command-on-shutdown-what-does-that-me the error may be due to a firmware issue or the driver issue. The error does not occur if using the Realtek drivers obtained from Github in this link: https://github.com/lwfinger/rtw88 and the driver of the module is identified as rtw_8723de. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse:
[Kernel-packages] [Bug 1892614] Re: RTL8723DE firmware bug: rtw_pci 0000:0d:00.0: failed to send h2c command
I tested Linux Kernel 5.8 which had the driver out of the box as rtw_8723de but the firmware bug is not present. The bug also does not occur when using the drivers from Larry Fingers rtw88 GitHub repository which comes with the rtw_8723de driver for the module. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892614 Title: RTL8723DE firmware bug: rtw_pci :0d:00.0: failed to send h2c command Status in linux package in Ubuntu: Incomplete Bug description: WiFi (WLAN) Module: Realtek RTL8723DE (came with my HP laptop). Ubuntu 20.04 is the first Ubuntu release to have the module working out of the box. Network devices as output by 'inxi -N' Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 Device-2: Realtek RTL8723DE 802.11b/g/n PCIe Adapter driver: rtw_pci Device-3: Realtek 802.11n WLAN Adapter type: USB driver: btusb The error 'rtw_pci :0d:00.0: failed to send h2c command' is logged every time I use the module for internet access. The error is logged more frequently especially if I stream a video and other related tasks. The driver is stable but it may fail become unavailable unless a cold boot is performed. The attached log contains the error logged many times when I was streaming a video Today. According to https://askubuntu.com/questions/1217892/system-responds-with-failed- to-send-h2c-command-on-shutdown-what-does-that-me the error may be due to a firmware issue or the driver issue. The error does not occur if using the Realtek drivers obtained from Github in this link: https://github.com/lwfinger/rtw88 and the driver of the module is identified as rtw_8723de. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1949 F pulseaudio /dev/snd/controlC1: tony 1949 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 08:37:12 2020 InstallationDate: Installed on 2020-08-22 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15-bs1xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=7b47411f-1984-4025-9678-8f5fba5b2059 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8444 dmi.board.vendor: HP dmi.board.version: 67.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd12/06/2019:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn8444:rvr67.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs1xx dmi.product.sku: 4UL47EA#BH5 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903286] [NEW] Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative
Public bug reported: Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 6 10:31:06 2020 ImageMediaBuild: 20201028 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903286 Title: Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative Status in bluez package in Ubuntu: New Bug description: Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 6 10:31:06 2020 ImageMediaBuild: 20201028 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903286/+subscriptions -- Mailing list: https://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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Hi, I implemented the fix detailed in the test case yesterday and the bug still existed. I've double checked again this morning and done a full-upgrade just to check nothing new was waiting and the bug still exists on this Mate 20.10 install. Yesterday after applying the fix I started getting random "System problem detected, report this?" popups but none so far today. Blueman Applet is set as a startup item and both blueman-applet and blueman-tray appear as running processes but running blueman-manager or blueman-adapters from the command line both fail with the message 'Blueman applet needs to be running' The Bluetooth panel item isnt shown. OS: Ubuntu MATE 20.10 aarch64 Host: Raspberry Pi 400 Rev 1.0 Kernel: 5.8.0-1007-raspi Tony On 11/11/2020 04:32, Launchpad Bug Tracker wrote: > This bug was fixed in the package bluez - 5.55-0ubuntu2 > > --- > bluez (5.55-0ubuntu2) hirsute; urgency=medium > >* Added patches from the Raspberry Pi Foundation > - d/p/raspi-bcm43xx-load-firmware.patch > - d/p/raspi-bcm43xx-3wire.patch > - d/p/raspi-cypress-305-bdaddr.patch >* These patches fix Bluetooth operation on the Pi 400 (LP: #1903048) > > -- Dave Jones Thu, 05 Nov 2020 13:39:07 > + > > ** Changed in: bluez (Ubuntu Hirsute) > Status: Fix Committed => Fix Released > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Hirsute: Fix Released Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: Bluetooth won't activate on the pi 400
Just to close the loop, I've just made fresh SD and USB boot disks from the latest current Mate 20.10 image and both don't have working Bluetooth, Ive updated both with the ppa and now both do work and I can use mouse and headphones with no problems. I have no idea why my original USB boot of Mate 20.10 didnt work after patching, there must be another problem with it as well, my apologies for any confusion caused by that. Martin and Alan have been nagging us 'ordinary' people to get involved and contribute where we can to help you out if possible, that's all I was trying to do. Thanks for the patch, hope you get it upstreamed, etc OK. Best wishes Tony -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I've just used a fresh image of Mate 20.10 and used -proposed and done a full update and reboot. My bluetooth mouse, headphones and external keyboard are working fine now with this build so this bug has been fixed for me. Thank you all for your efforts in getting it sorted Kind regards Tony -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Committed Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 or 151 or 154 (but 4.4.0-143 works)
Update to 4.4.0-164 has cured this bug. I can now boot with this kernel and log in OK. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 or 151 or 154 (but 4.4.0-143 works) Status in linux package in Ubuntu: Confirmed Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting
Slightly confused by this response and the move to "Fix released". The fix referred to fixes the compilation error. However there are two other problems - the service not starting even when the module compiled and the packages being uninstalled during the upgrade. Do I need to raise those as new bugs? You ask for an upgrade log. Please can you clarify which log you need. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1753430 Title: virtualbox-guest-utils.service not starting Status in dkms package in Ubuntu: Fix Released Bug description: I am trialing various flavours of Ubuntu in Virtualbox virtual machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate. All version 18.04, running on Kubuntu 17.10 host. All set up identically as far as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and virtualbox-guest-x11 installed in each guest. All work fine except that shared folders does not work in 2 of the VMs. It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate. On investigation it appears that the virtualbox-guest-utils.service is not started automatically on the two versions not working. If I start it manually everything is OK. Here is the status - systemctl status virtualbox-guest-utils.service ● virtualbox-guest-utils.service - Virtualbox guest utils Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; enabled; vendor preset: enabled) Active: inactive (dead) Looking in journalctl there are no messages showing that the service tried to start and failed. There is nothing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virtualbox-guest-utils 5.2.8-dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic i686 ApportVersion: 2.20.8-0ubuntu10 Architecture: i386 CurrentDesktop: LXDE Date: Mon Mar 5 09:53:02 2018 InstallationDate: Installed on 2012-10-23 (1958 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: virtualbox UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1753430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting
I thought virtualbox-hwe was a host package. My problem was when upgrading guest systems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1753430 Title: virtualbox-guest-utils.service not starting Status in dkms package in Ubuntu: Fix Released Bug description: I am trialing various flavours of Ubuntu in Virtualbox virtual machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate. All version 18.04, running on Kubuntu 17.10 host. All set up identically as far as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and virtualbox-guest-x11 installed in each guest. All work fine except that shared folders does not work in 2 of the VMs. It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate. On investigation it appears that the virtualbox-guest-utils.service is not started automatically on the two versions not working. If I start it manually everything is OK. Here is the status - systemctl status virtualbox-guest-utils.service ● virtualbox-guest-utils.service - Virtualbox guest utils Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; enabled; vendor preset: enabled) Active: inactive (dead) Looking in journalctl there are no messages showing that the service tried to start and failed. There is nothing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virtualbox-guest-utils 5.2.8-dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic i686 ApportVersion: 2.20.8-0ubuntu10 Architecture: i386 CurrentDesktop: LXDE Date: Mon Mar 5 09:53:02 2018 InstallationDate: Installed on 2012-10-23 (1958 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: virtualbox UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1753430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting
Had a look at your PPA and realised that you had got hwe versions of the guest packages as well as virtualbox-hwe. So, added your PPA to 16.04 Kubuntu guest and tried to upgrade to 18.04. However do-release-upgrade disabled the entry before it upgraded. In that case I don't know how to test this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1753430 Title: virtualbox-guest-utils.service not starting Status in dkms package in Ubuntu: Fix Released Bug description: I am trialing various flavours of Ubuntu in Virtualbox virtual machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate. All version 18.04, running on Kubuntu 17.10 host. All set up identically as far as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and virtualbox-guest-x11 installed in each guest. All work fine except that shared folders does not work in 2 of the VMs. It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate. On investigation it appears that the virtualbox-guest-utils.service is not started automatically on the two versions not working. If I start it manually everything is OK. Here is the status - systemctl status virtualbox-guest-utils.service ● virtualbox-guest-utils.service - Virtualbox guest utils Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; enabled; vendor preset: enabled) Active: inactive (dead) Looking in journalctl there are no messages showing that the service tried to start and failed. There is nothing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virtualbox-guest-utils 5.2.8-dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic i686 ApportVersion: 2.20.8-0ubuntu10 Architecture: i386 CurrentDesktop: LXDE Date: Mon Mar 5 09:53:02 2018 InstallationDate: Installed on 2012-10-23 (1958 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: virtualbox UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1753430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting
Regarding the original service not starting problem. If I do a clean 18.04 install everything works OK. (Apart from Lubuntu where I couldn't get the installer to work.) If I do a clean 17.10 install without the guest packages because of bug #1683043, upgrade to 18.04, install dpkg-dev, install the guest packages everything works. If I do a clean 16.04 install, add the guest packages, upgrade to 18.04 during which the guest packages are removed, re add the guest packages then Kubuntu, Ubuntu, Xubuntu work. For Lubuntu and Ubuntu Mate the virtualbox-guest-utils.service does not start automatically but can be started manually. This situation is a bit artificial as the packages shouldn't be removed during the upgrade. I suggest we revisit this problem when the upgrade package removal problem is resolved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1753430 Title: virtualbox-guest-utils.service not starting Status in dkms package in Ubuntu: Fix Released Bug description: I am trialing various flavours of Ubuntu in Virtualbox virtual machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate. All version 18.04, running on Kubuntu 17.10 host. All set up identically as far as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and virtualbox-guest-x11 installed in each guest. All work fine except that shared folders does not work in 2 of the VMs. It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate. On investigation it appears that the virtualbox-guest-utils.service is not started automatically on the two versions not working. If I start it manually everything is OK. Here is the status - systemctl status virtualbox-guest-utils.service ● virtualbox-guest-utils.service - Virtualbox guest utils Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; enabled; vendor preset: enabled) Active: inactive (dead) Looking in journalctl there are no messages showing that the service tried to start and failed. There is nothing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virtualbox-guest-utils 5.2.8-dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic i686 ApportVersion: 2.20.8-0ubuntu10 Architecture: i386 CurrentDesktop: LXDE Date: Mon Mar 5 09:53:02 2018 InstallationDate: Installed on 2012-10-23 (1958 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: virtualbox UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1753430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729244] [NEW] package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
Public bug reported: Attempting to install with nVidia GTX1060 graphics card ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-image-extra-4.4.0-98-generic: Purge NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: manager2337 F pulseaudio Date: Wed Nov 1 01:01:21 2017 DpkgTerminalLog: dpkg: error processing package linux-image-extra-4.4.0-98-generic (--purge): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal HibernationDevice: RESUME=UUID=a907603a-3713-4675-a0a6-27553415946e MachineType: empty empty ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=aad3d69b-99bb-47af-a94c-f6dd4926450f ro bootdegraded=y PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 'V1.06 ' dmi.board.asset.tag: empty dmi.board.name: S3992-E dmi.board.vendor: TYAN Computer Corporation dmi.board.version: empty dmi.chassis.asset.tag: empty dmi.chassis.type: 3 dmi.chassis.vendor: empty dmi.chassis.version: empty dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr'V1.06':bd06/09/2009:svnempty:pnempty:pvrempty:rvnTYANComputerCorporation:rnS3992-E:rvrempty:cvnempty:ct3:cvrempty: dmi.product.name: empty dmi.product.version: empty dmi.sys.vendor: empty ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729244 Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux package in Ubuntu: New Bug description: Attempting to install with nVidia GTX1060 graphics card ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-image-extra-4.4.0-98-generic: Purge NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: manager2337 F pulseaudio Date: Wed Nov 1 01:01:21 2017 DpkgTerminalLog: dpkg: error processing package linux-image-extra-4.4.0-98-generic (--purge): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal HibernationDevice: RESUME=UUID=a907603a-3713-4675-a0a6-27553415946e MachineType: empty empty ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=aad3d69b-99bb-47af-a94c-f6dd4926450f ro bootdegraded=y PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 'V1.06 ' dmi.board.asset.tag: empty dmi.board.name: S3992-E dmi.board.vendor: TYAN Computer Corporation dmi.board.version: empty dmi.chassis.asset.tag: empty dmi.chassis.type: 3 dmi.chassis.vendor: empty dmi.chassis.version: empty dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr'V1.06':bd06/09/2009:svnempty:pnempty:pvrempty:rvnTYANComputerCorporation:rnS3992-E:rvrempty:cvnempty:ct3:cvrempty: dmi.product.name: empty dmi.product.version: empty dmi.sys.vendor: empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729244/+subscriptions -- Mailing li
Re: [Kernel-packages] [Bug 1729244] Re: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a
On 01/11/17 14:29, Joseph Salisbury wrote: > You may need to run the following from a terminal: > > sudo apt-get install -f > sudo apt-get clean > sudo apt-get update > > Then re-install the package or updates. > > If that does not resolve your issue, please mark the bug as "Confirmed" Hi, Joseph. OK, that fixed the problem. Thanks, Tony. > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > -- Minke Informatics Limited, Registered in Scotland - Company No. SC419028 Registered Office: 3 Donview, Bridge of Alford, AB33 8QJ, Scotland (UK) tel. +44(0)19755 63548http://minke-informatics.co.uk mob. +44(0)7985 078324mailto:tony.tra...@minke-informatics.co.uk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729244 Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux package in Ubuntu: Incomplete Bug description: Attempting to install with nVidia GTX1060 graphics card ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-image-extra-4.4.0-98-generic: Purge NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: manager2337 F pulseaudio Date: Wed Nov 1 01:01:21 2017 DpkgTerminalLog: dpkg: error processing package linux-image-extra-4.4.0-98-generic (--purge): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal HibernationDevice: RESUME=UUID=a907603a-3713-4675-a0a6-27553415946e MachineType: empty empty ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=aad3d69b-99bb-47af-a94c-f6dd4926450f ro bootdegraded=y PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 'V1.06 ' dmi.board.asset.tag: empty dmi.board.name: S3992-E dmi.board.vendor: TYAN Computer Corporation dmi.board.version: empty dmi.chassis.asset.tag: empty dmi.chassis.type: 3 dmi.chassis.vendor: empty dmi.chassis.version: empty dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr'V1.06':bd06/09/2009:svnempty:pnempty:pvrempty:rvnTYANComputerCorporation:rnS3992-E:rvrempty:cvnempty:ct3:cvrempty: dmi.product.name: empty dmi.product.version: empty dmi.sys.vendor: empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
buzuk56's solution worked for me. I'm using Ryzen 5 1500X with Gigabyte GA-AB350-gaming-3. Thanks! So glad to have Ubuntu on this machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: [Impact] Gigabyte AM4 boards users cannot boot Ubuntu successfully. Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf "pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. [Test Case] All Gigabyte AM4 boards can reproduce the issue. With the patch, the issue is resolved, per comment #170. [Regression Potential] Regression Potential is low. It limits to rather new AMD platform which has pinctrl-amd. As the commit log says, use chained interrupt is not a good idea. Use regular interrupt is the correct way. I also test the patch on an AMD laptop, where its touchpad depends on pinctrl-amd. No regression found. Original bug report: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot
** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete ** Changed in: canonical-devices-system-image Status: Confirmed => Incomplete ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Selene Scriven (toykeeper) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1387949 Title: power cycling Emerson EM229 headset caused phone to reboot Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: While sanity testing krillin rtm image 139, I paired a bluetooth headset. I made a call with it, hung up, then turned the headset off. I noticed this caused the BT indicator icon to invert, which is a nice way to indicate whether something is connected. So, I turned the device back on, waited for the icon to invert, turned the device off, waited, and instead of inverting the icon... the phone rebooted. Not sure what exactly failed here, like which component, but it's definitely not good when a paired headset can cause the phone to spontaneously reboot. I don't see any relevant .crash files, and all I see in syslog from that time is this: Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: Activation (/ril_1) failed for connection '/310410695117999/context1' Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): deactivating device (reason 'none') [0] Oct 30 23:43:01 ubuntu-phablet kernel: [ 747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 (2014-10-31 05:43:01.704759580 UTC) Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.779813]mtk-tpd: TPD wake up Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816572]mtk-tpd: TPD wake up done Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816593] mag_context_obj ok--->hwm_obj->early_suspend=0 Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated service 'org.freedesktop.systemd1' Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com";] exiting on signal 15. Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com";] start Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103 Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on physical CPU 0 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup subsys cpu Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 (root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 28 11:57:42 UTC 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt
** Description changed: Connecting to the latest generation Apple BT keyboard ( the one with the USB port & no batteries ) fails on an Ubuntu Touch device, as when you press the "Connect" button on the device page, a dialog titled "Bluetooth Pairing Request" is displayed, with the following text: Please confirm that the PIN displayed on 'Magic Keyboard' matches this one: XX The dialog has "Cancel" and "Confirm PIN" buttons. The keyboard has no display on which a PIN could be displayed. When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X, ... ) to connect this keyboard all that's necessary is to click/press the 'Connect' button in the appropriate place, and the keyboard automatically connects, and is usable with no other actions required from the user. Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez 5.36-0ubuntu2~overlay1 installed. Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37 installed from silo 39. Note, after dismissing the dialog, subsequent attempts to connect may not re-display the PIN dialog, instead nothing happens. I've found that this requires power cycling the keyboard to clear and cause the PIN dialog to be displayed again. + + [bluetooth]# show + Controller B8:64:91:48:2B:1E + Name: Aquaris E4.5 Ubuntu Edition + Alias: Aquaris E4.5 Ubuntu Edition + Class: 0x1c020c + Powered: yes + Discoverable: no + Pairable: yes + UUID: Headset AG(1112--1000-8000-00805f9b34fb) + UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) + UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) + UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) + UUID: PnP Information (1200--1000-8000-00805f9b34fb) + UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) + UUID: Audio Source (110a--1000-8000-00805f9b34fb) + UUID: Audio Sink(110b--1000-8000-00805f9b34fb) + UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) + UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) + Modalias: usb:v1D6Bp0246d0525 + Discovering: no + + [bluetooth]# devices + Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3 + Device DE:76:E2:04:9D:6F BB-9D6F + Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03 + Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8 + Device 84:38:35:67:0C:3D ubuntu-0 + Device 04:69:F8:C2:A0:09 tony espy’s Keyboard + Device 00:21:3C:A0:14:A6 Jawbone ERA + Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7 + + Device info *before* pairing attempt: + + Device 04:69:F8:C2:A0:09 + Name: tony espy’s Keyboard + Alias: tony espy’s Keyboard + Class: 0x002540 + Icon: input-keyboard + Paired: no + Trusted: no + Blocked: no + Connected: no + LegacyPairing: no + Modalias: bluetooth:v004Cp0267d0066 + + No changes in any of the attributes after *after* the pairing attempt ( + output of info command is the same ). ** Attachment added: "syslog from krillin w/bluez debug enabled" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591778/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1551858 Title: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: Connecting to the latest generation Apple BT keyboard ( the one with the USB port & no batteries ) fails on an Ubuntu Touch device, as when you press the "Connect" button on the device page, a dialog titled "Bluetooth Pairing Request" is displayed, with the following text: Please confirm that the PIN displayed on 'Magic Keyboard' matches this one: XX The dialog has "Cancel" and "Confirm PIN" buttons. The keyboard has no display on which a PIN could be displayed. When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X, ... ) to connect this keyboard all that's necessary is to click/press the 'Connect' button in the appropriate place, and the keyboard automatically connects, and is usable with no other actions required from the user. Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez 5.36-0ubuntu2~overlay1 installed. Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37 installed from silo 39. Note, after dismissing the dialog, subsequent attempts to connect may not re-display the PIN dialog, instead nothing happens. I've found that this requires power cyc
[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt
Re-tested on krillin ( rc-proposed/bq-aquaris.en / 270 ), this time with bluez 5.37 installed from the silo. @Simon, how could this not be a system settings app failure? As I pointed out in my description, pairing this keyboard works fine with every other device I tried, including two Ubuntu desktop systems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1551858 Title: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: Connecting to the latest generation Apple BT keyboard ( the one with the USB port & no batteries ) fails on an Ubuntu Touch device, as when you press the "Connect" button on the device page, a dialog titled "Bluetooth Pairing Request" is displayed, with the following text: Please confirm that the PIN displayed on 'Magic Keyboard' matches this one: XX The dialog has "Cancel" and "Confirm PIN" buttons. The keyboard has no display on which a PIN could be displayed. When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X, ... ) to connect this keyboard all that's necessary is to click/press the 'Connect' button in the appropriate place, and the keyboard automatically connects, and is usable with no other actions required from the user. Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez 5.36-0ubuntu2~overlay1 installed. Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37 installed from silo 39. Note, after dismissing the dialog, subsequent attempts to connect may not re-display the PIN dialog, instead nothing happens. I've found that this requires power cycling the keyboard to clear and cause the PIN dialog to be displayed again. [bluetooth]# show Controller B8:64:91:48:2B:1E Name: Aquaris E4.5 Ubuntu Edition Alias: Aquaris E4.5 Ubuntu Edition Class: 0x1c020c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0525 Discovering: no [bluetooth]# devices Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3 Device DE:76:E2:04:9D:6F BB-9D6F Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03 Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8 Device 84:38:35:67:0C:3D ubuntu-0 Device 04:69:F8:C2:A0:09 tony espy’s Keyboard Device 00:21:3C:A0:14:A6 Jawbone ERA Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7 Device info *before* pairing attempt: Device 04:69:F8:C2:A0:09 Name: tony espy’s Keyboard Alias: tony espy’s Keyboard Class: 0x002540 Icon: input-keyboard Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no Modalias: bluetooth:v004Cp0267d0066 No changes in any of the attributes after *after* the pairing attempt ( output of info command is the same ). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
