[Kernel-packages] [Bug 1821564] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI: 7ffe93a35cd0 RDI: 0008 6.485518] RBP: 7ffe93a35cd0 R08: R09: 6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 6.485518] R13: 5598b029e880 R14:
[Kernel-packages] [Bug 1821564] [NEW] b44 Ethernet driver null pointer during initialization
Public bug reported: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI: 7ffe93a35cd0 RDI: 0008 6.485518] RBP: 7ffe93a35cd0 R08: R09: 6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 6.485518] R13: 5598b029e880 R14: 7ffe93a35e7c R15: 6.485518] Modules linked in: arc4 b43 cordic snd_hda_codec_hdmi ttm bcma dell_laptop snd_hda_codec_idt snd_hda_codec_generic dell_smm_hwmon drm_kms_helper dell_wmi ledtrig_audio snd_hda_intel kvm mac80211 dell_smbios dcdbas drm joydev snd_hda_codec r852 irqbypass input_leds sm_common sparse_keymap wmi_bmof dell_wmi_descriptor snd_hda_core i2c_algo_bit snd_hwdep cfg80211 serio_raw snd_pcm nand fb_sys_fops snd_timer r592 syscopyarea nand_ecc snd nand_bch sysfillrect soundcore sysimgblt bch memstick mtd mac
[Kernel-packages] [Bug 1788432] Re: 4.15 s390x kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788432 Title: 4.15 s390x kernel BUG at /build/linux- Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [SRU Justification] == Impact == Several helper functions in the s390x code which handle accessing sysfs attributes were missing protection against races. Concurrent access would be able to trigger kernel bugs. == Fix == The following two upstream commits (from v5.0 upstream) will fix the issue: 78b1a52e05c9 virtio/s390: fix race in ccw_io_helper() 2448a299ec41 virtio/s390: avoid race on vcdev->config == Testcase == see below == Risk of Regression == Changes are isolated to architecture code and are verified by running the stress testing, so overall should be low. uname -a Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux and same for 4.15.0-29-generic and 4.17.0-8-generic Steps to reproduce this bug: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make clean make And run with: ./stress-ng --sysfs 0 -t 60 .. wait a few seconds and then: [ 119.445891] [ cut here ] [ 119.445898] kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP [ 119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk [ 119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P DO 4.15.0-33-generic #36-Ubuntu [ 119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 119.446170] Krnl PSW : 12d313d3 405835bc (virtblk_cache_type_show+0x82/0x88 [virtio_blk]) [ 119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 6545 [ 119.446196]03ff800058da 6546 6bf537c0 6b60a100 [ 119.446198] 00690648 7cc3de40 7a74b000 [ 119.446202]03ff80008210 03ff800058da 7ac1bce8 [ 119.446210] Krnl Code: 03ff80005912: ebbff0a80004 lmg %r11,%r15,168(%r15) [ 119.446210]03ff80005918: c0f40560 brcl 15,3ff800063d8 [ 119.446210] #03ff8000591e: a7f40001 brc 15,3ff80005920 [ 119.446210] >03ff80005922: 0707 bcr 0,%r7 [ 119.446210]03ff80005924: 0707 bcr 0,%r7 [ 119.446210]03ff80005926: 0707 bcr 0,%r7 [ 119.446210]03ff80005928: c004 brcl 0,3ff80005928 [ 119.446210]03ff8000592e: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 119.446226] Call Trace: [ 119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 [virtio_blk]) [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 [ 119.446279] Last Breaking-Event-Address: [ 119.446281] [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 [virtio_blk] [ 119.446283] [ 119.446284] ---[ end trace 2c2403d726047e4a ]--- For 4.17.0-8-generic: [ 25.170715] kernel BUG at drivers/block/virtio_blk.c:574! [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP [ 25.170797] Modules linked in: lttng_statedump(OE) lttng_clock(OE) lttng_lib_ring_buffer(OE) binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha
[Kernel-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
Thanks. Confirm, the tlp not installed. Mouse: Acer MT1BF One more thing, the use of bluetoothctl is not resolving issue. -- 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/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821371] Re: [nouveau] Black screen with some icons flashing on start-up
Please file an upstream bug at https://bugs.freedesktop.org/ Product: xorg Component: DRM/nouveau -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821371 Title: [nouveau] Black screen with some icons flashing on start-up Status in linux package in Ubuntu: Confirmed Bug description: when i start , i can't have ubuntu , but black screen with some icones flashing , my arrow of the mouse can move but do nothing , i'm french so excuse me for my language ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_36_39_generic_48 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Fri Mar 22 16:34:18 2019 DistUpgraded: 2018-07-23 08:19:08,090 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 740] [1458:368d] InstallationDate: Installed on 2017-05-19 (672 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Olidata S.p.A. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4bf32425-67a7-4926-91a8-f1fb1b97baaf ro splash quiet plymouth:debug=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-23 (242 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B85M DASH/OL R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/23/2015:svnOlidataS.p.A.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85MDASH/OLR2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jul 22 08:14:02 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver MOUSE, id 9 inputLogitech USB Receiver KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid
I don't find any suspend related message from log in #17. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Triaged Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820990] Re: [SRU][B/B-OEM/C/D] Fix AMD IOMMU NULL dereference
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-oem (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Disco) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820990 Title: [SRU][B/B-OEM/C/D] Fix AMD IOMMU NULL dereference Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Bug description: [Impact] When no acpi hid match the device, there will be a NULL dereference in amd iommu. It will make system hang. [Fix] Check NULL pointer before using it. [Test] Tested on several AMD platforms, bugs are fixed with this patch. [Regression Potential] Low, upstream fix, Verified on several platforms. It should be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1820990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821383] Re: synaptics touchpoint fails after resume
Please attach `dmesg` right after 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/1821383
Title:
synaptics touchpoint fails after resume
Status in linux package in Ubuntu:
Confirmed
Bug description:
To workaround bug #924648 I've installed the following:
$ cat /etc/udev/rules.d/10-trackpoint.rules
ACTION=="add|change",
SUBSYSTEM=="input",
ATTR{name}=="TPPS/2 IBM TrackPoint",
ATTR{device/sensitivity}="250",
ATTR{device/speed}="250",
While this works I now sometimes get a broken pointer after suspend.
dmesg shows this at resume:
[353671.884852] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e,
buttons: 3/3
[353672.381746] psmouse serio2: Failed to deactivate mouse on
synaptics-pt/serio0
[353672.845761] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0
After some time it resets and the pointer is back. Most of the time
just this is shown:
[353852.538962] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e,
buttons: 3/3
[353852.735990] input: TPPS/2 IBM TrackPoint as
/devices/platform/i8042/serio1/serio2/input/input52
But I did get a timeout call trace once:
[ 5676.512616] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0
[ 5677.453153] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e,
buttons: 3/3
[ 5677.643970] input: TPPS/2 IBM TrackPoint as
/devices/platform/i8042/serio1/serio2/input/input21
[ 5800.035392] INFO: task kworker/0:2:9739 blocked for more than 120 seconds.
[ 5800.035402] Tainted: G OE4.15.0-45-generic #48-Ubuntu
[ 5800.035406] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 5800.035410] kworker/0:2 D0 9739 2 0x8000
[ 5800.035424] Workqueue: events_long serio_handle_event
[ 5800.035427] Call Trace:
[ 5800.035439] __schedule+0x291/0x8a0
[ 5800.035445] ? schedule_timeout+0x165/0x350
[ 5800.035453] schedule+0x2c/0x80
[ 5800.035460] __kernfs_remove.part.12+0x175/0x1f0
[ 5800.035467] ? wait_woken+0x80/0x80
[ 5800.035474] kernfs_remove_by_name_ns+0x54/0xa0
[ 5800.035479] remove_files.isra.1+0x35/0x70
[ 5800.035484] sysfs_remove_group+0x44/0x90
[ 5800.035488] sysfs_remove_groups+0x2e/0x50
[ 5800.035493] device_remove_groups+0x12/0x20
[ 5800.035508] trackpoint_disconnect+0x44/0x70 [psmouse]
[ 5800.035517] psmouse_disconnect+0xfe/0x190 [psmouse]
[ 5800.035525] serio_disconnect_driver+0x36/0x50
[ 5800.035531] serio_driver_remove+0x15/0x20
[ 5800.035539] device_release_driver_internal+0x15b/0x240
[ 5800.035544] device_release_driver+0x12/0x20
[ 5800.035548] serio_disconnect_port+0x98/0xb0
[ 5800.035553] serio_handle_event+0x18e/0x250
[ 5800.035559] process_one_work+0x1de/0x410
[ 5800.035565] worker_thread+0x32/0x410
[ 5800.035572] kthread+0x121/0x140
[ 5800.035576] ? process_one_work+0x410/0x410
[ 5800.035582] ? kthread_create_worker_on_cpu+0x70/0x70
[ 5800.035589] ? do_syscall_64+0x73/0x130
[ 5800.035594] ? SyS_exit+0x17/0x20
[ 5800.035600] ret_from_fork+0x35/0x40
[ 5858.636930] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e,
buttons: 3/3
[ 5858.872453] input: TPPS/2 IBM TrackPoint as
/devices/platform/i8042/serio1/serio2/input/input22
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pedrocr 26606 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Mar 22 18:20:56 2019
InstallationDate: Installed on 2018-05-31 (295 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc.
Bus 001 Device 003: ID 5986:0706 Acer, Inc
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FAS5TS00
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=UUID=0206141b-5758-4895-bbbd-8022b1e78519 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-45-generic N/A
linux-backports-modules-4.15.0-45-generic N/A
linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1CET66W (1.34 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FAS5TS00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.cha
[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)
No, I am 100% sure it worked with kernel 4.15.0-42 and with the nvidia proprietary driver nvidia-415 before the version .27 Also always worked fine without any nvidia driver, specially for the upstream kernel. I test this since more than one year... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819915 Title: s2disk freezes at saving image to disk (hibernation) Status in linux package in Ubuntu: Confirmed Bug description: This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1 hibernation was working flawlessly on my machine. (with kernel 4.15-46! not a kernel issue then?) Another thing that got updated recently was nvidia drivers which were known to cause hibernation issues, but those were on restoring the snapshot. http://imgur.com/gallery/jOyHEcL --> I get stuck on this screen after running hibernate or pm-hibernate. (sys-req REISUB combination works there and is the only good way to restart I found) SPECS Laptop Dell Inspiron 7567 A30P Intel Core i7-7700HQ 1x 16 GB DDR4 1 TB HDD + 256 GB SSD Nvidia GeForce GTX 1050 Ti FHD display Intel Dual Band Wireless AC 3165 1x1 Motherboard: Intel HM175 Graphics adapter: NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, Core: 1620 MHz, Memory: 1752 MHz, GDDR5, 21.21.13.7320 (ForceWare 373.20), Nvidia Optimus nvidia driver: 415.27 INFO # uname -a Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # free -m totalusedfree shared buff/cache available Mem: 1590629258742 1614238 12485 Swap: 16333 0 16333 # cat /etc/fstab | grep swap # swap was on /dev/sda8 during installation UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw 0 0 n root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernate root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hiber root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep s2disk root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernation I could find nothing scrolling up on syslog about the hibernation process or with grep An interesting Note is that if I run hibernate just after I boot, it works and resumes perfectly! But after some system usage it randomly has that problem if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 once. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: matheus 25949 F...m pulseaudio /dev/snd/pcmC0D0p: matheus 25949 F...m pulseaudio /dev/snd/controlC0: matheus 25949 F pulseaudio /dev/snd/seq:matheus4986 f qsynth CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06 InstallationDate: Installed on 2018-05-10 (308 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 15 7000 Gaming NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug no_console_suspend systemd.log_level=info nvidia-drm.modeset=0 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)
Isn't there a way to extract logs from s2disk or uswsusp??? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819915 Title: s2disk freezes at saving image to disk (hibernation) Status in linux package in Ubuntu: Confirmed Bug description: This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1 hibernation was working flawlessly on my machine. (with kernel 4.15-46! not a kernel issue then?) Another thing that got updated recently was nvidia drivers which were known to cause hibernation issues, but those were on restoring the snapshot. http://imgur.com/gallery/jOyHEcL --> I get stuck on this screen after running hibernate or pm-hibernate. (sys-req REISUB combination works there and is the only good way to restart I found) SPECS Laptop Dell Inspiron 7567 A30P Intel Core i7-7700HQ 1x 16 GB DDR4 1 TB HDD + 256 GB SSD Nvidia GeForce GTX 1050 Ti FHD display Intel Dual Band Wireless AC 3165 1x1 Motherboard: Intel HM175 Graphics adapter: NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, Core: 1620 MHz, Memory: 1752 MHz, GDDR5, 21.21.13.7320 (ForceWare 373.20), Nvidia Optimus nvidia driver: 415.27 INFO # uname -a Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # free -m totalusedfree shared buff/cache available Mem: 1590629258742 1614238 12485 Swap: 16333 0 16333 # cat /etc/fstab | grep swap # swap was on /dev/sda8 during installation UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw 0 0 n root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernate root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hiber root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep s2disk root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernation I could find nothing scrolling up on syslog about the hibernation process or with grep An interesting Note is that if I run hibernate just after I boot, it works and resumes perfectly! But after some system usage it randomly has that problem if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 once. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: matheus 25949 F...m pulseaudio /dev/snd/pcmC0D0p: matheus 25949 F...m pulseaudio /dev/snd/controlC0: matheus 25949 F pulseaudio /dev/snd/seq:matheus4986 f qsynth CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06 InstallationDate: Installed on 2018-05-10 (308 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 15 7000 Gaming NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug no_console_suspend systemd.log_level=info nvidia-drm.modeset=0 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)
With the recomended nvidia driver and low ram usage, the system sucessfully hibernates, but then fails to resume and I get the login screen instead. With high ram usage it hangs trying to save the image to disk. That's a new behaviour to 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/1819915 Title: s2disk freezes at saving image to disk (hibernation) Status in linux package in Ubuntu: Confirmed Bug description: This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1 hibernation was working flawlessly on my machine. (with kernel 4.15-46! not a kernel issue then?) Another thing that got updated recently was nvidia drivers which were known to cause hibernation issues, but those were on restoring the snapshot. http://imgur.com/gallery/jOyHEcL --> I get stuck on this screen after running hibernate or pm-hibernate. (sys-req REISUB combination works there and is the only good way to restart I found) SPECS Laptop Dell Inspiron 7567 A30P Intel Core i7-7700HQ 1x 16 GB DDR4 1 TB HDD + 256 GB SSD Nvidia GeForce GTX 1050 Ti FHD display Intel Dual Band Wireless AC 3165 1x1 Motherboard: Intel HM175 Graphics adapter: NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, Core: 1620 MHz, Memory: 1752 MHz, GDDR5, 21.21.13.7320 (ForceWare 373.20), Nvidia Optimus nvidia driver: 415.27 INFO # uname -a Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # free -m totalusedfree shared buff/cache available Mem: 1590629258742 1614238 12485 Swap: 16333 0 16333 # cat /etc/fstab | grep swap # swap was on /dev/sda8 during installation UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw 0 0 n root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernate root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hiber root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep s2disk root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernation I could find nothing scrolling up on syslog about the hibernation process or with grep An interesting Note is that if I run hibernate just after I boot, it works and resumes perfectly! But after some system usage it randomly has that problem if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 once. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: matheus 25949 F...m pulseaudio /dev/snd/pcmC0D0p: matheus 25949 F...m pulseaudio /dev/snd/controlC0: matheus 25949 F pulseaudio /dev/snd/seq:matheus4986 f qsynth CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06 InstallationDate: Installed on 2018-05-10 (308 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 15 7000 Gaming NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug no_console_suspend systemd.log_level=info nvidia-drm.modeset=0 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-p
[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)
Maybe try older kernel releases from Artful (4.13) or Zesty (4.10). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819915 Title: s2disk freezes at saving image to disk (hibernation) Status in linux package in Ubuntu: Confirmed Bug description: This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1 hibernation was working flawlessly on my machine. (with kernel 4.15-46! not a kernel issue then?) Another thing that got updated recently was nvidia drivers which were known to cause hibernation issues, but those were on restoring the snapshot. http://imgur.com/gallery/jOyHEcL --> I get stuck on this screen after running hibernate or pm-hibernate. (sys-req REISUB combination works there and is the only good way to restart I found) SPECS Laptop Dell Inspiron 7567 A30P Intel Core i7-7700HQ 1x 16 GB DDR4 1 TB HDD + 256 GB SSD Nvidia GeForce GTX 1050 Ti FHD display Intel Dual Band Wireless AC 3165 1x1 Motherboard: Intel HM175 Graphics adapter: NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, Core: 1620 MHz, Memory: 1752 MHz, GDDR5, 21.21.13.7320 (ForceWare 373.20), Nvidia Optimus nvidia driver: 415.27 INFO # uname -a Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # free -m totalusedfree shared buff/cache available Mem: 1590629258742 1614238 12485 Swap: 16333 0 16333 # cat /etc/fstab | grep swap # swap was on /dev/sda8 during installation UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw 0 0 n root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernate root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hiber root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep s2disk root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernation I could find nothing scrolling up on syslog about the hibernation process or with grep An interesting Note is that if I run hibernate just after I boot, it works and resumes perfectly! But after some system usage it randomly has that problem if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 once. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: matheus 25949 F...m pulseaudio /dev/snd/pcmC0D0p: matheus 25949 F...m pulseaudio /dev/snd/controlC0: matheus 25949 F pulseaudio /dev/snd/seq:matheus4986 f qsynth CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06 InstallationDate: Installed on 2018-05-10 (308 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 15 7000 Gaming NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug no_console_suspend systemd.log_level=info nvidia-drm.modeset=0 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809586] Re: [ 14.259626] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vddl not found, using dummy regulator
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809586 Title: [ 14.259626] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vddl not found, using dummy regulator Status in linux package in Ubuntu: Expired Bug description: Missing i2c-HTIX5288 driver. Touch does work OK but sometimes it freezes at random times. When using a mouse the mouse works fine. Ubuntu 18.04 Kernel 4.18.0-13 Dual-Core Intel® Celeron® N4000 CPU @ 1.10GHz ~$ dmesg [ 14.259578] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vdd not found, using dummy regulator [ 14.259622] i2c_hid i2c-HTIX5288:00: Linked as a consumer to regulator.0 [ 14.259626] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vddl not found, using dummy regulator [ 14.296078] ahci :00:12.0: port does not support device sleep [ 14.421143] input: HTIX5288:00 0911:5288 Mouse as /devices/pci:00/:00:17.3/i2c_designware.7/i2c-12/i2c-HTIX5288:00/0018:0911:5288.0002/input/input17 [ 14.421507] input: HTIX5288:00 0911:5288 Touchpad as /devices/pci:00/:00:17.3/i2c_designware.7/i2c-12/i2c-HTIX5288:00/0018:0911:5288.0002/input/input18 [ 14.421715] hid-generic 0018:0911:5288.0002: input,hidraw1: I2C HID v1.00 Mouse [HTIX5288:00 0911:5288] on i2c-HTIX5288:00 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: juno 1113 F pulseaudio /dev/snd/controlC0: juno 1113 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-12-23 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Default string Default string Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=161d8da2-6b65-4a94-b327-82974d663e77 ro quiet splash acpi_osi=Linux i8042.nopnp vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL5-BIOS-4G-V3-002-A dmi.board.asset.tag: Default string dmi.board.name: Gemini II dmi.board.vendor: PC Specialist LTD dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL5-BIOS-4G-V3-002-A:bd11/28/2018:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnPCSpecialistLTD:rnGeminiII:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798705] Re: Incomplete linking with boost_regex
** Also affects: gce-compute-image-packages (Ubuntu) Importance: Undecided Status: New ** Changed in: gce-compute-image-packages (Ubuntu) Assignee: (unassigned) => Daniel Axtens (daxtens) ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798705 Title: Incomplete linking with boost_regex Status in gce-compute-image-packages package in Ubuntu: New Bug description: SRU Justification = [Impact] oslogin fails on Xenial and Trusty. In auth.log we see: Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: cannot open shared object file: No such file or directory Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: pam_oslogin_login.so Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: cannot open shared object file: No such file or directory Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: pam_oslogin_admin.so The error message is a bit deceptive - PAM tries to load the module from the correct location, fails, and then tries the other location where it is missing. It then reports the missing error rather than the real error. symlink the module into both paths leads to a much more useful error message: Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: undefined symbol: _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE Oct 18 06:45:12 dja-202158 sshd[16554]: PAM adding faulty module: pam_oslogin_login.so Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: undefined symbol: _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE [Test case] - set up GCE VM - turn on oslogin - attempt to log in [Fix] debian/patches/0002-Set-LDFLAGS-at-the-end-of-the-c-command-line-right-b.patch re-orders the link flags to link boost_regex for oslogin. However, this didn't change the flags for PAM module linking. So fix that too. [Regression Potential] - fixes a regression - limited to oslogin, and how it is linked. [Other Notes] We still see a scary list of warnings when building, but they don't seem to have an impact on the common path: dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail13put_mem_blockEPv used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail14verify_optionsEjNS_15regex_constants12_match_flagsE used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZNK5boost9re_detail31cpp_regex_traits_implementationIcE17transform_primaryEPKcS4_ used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost13match_resultsIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISB_12maybe_assignERKSF_ used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost11basic_regexIcNS_12regex_traitsIcNS_16cpp_regex_traitsIcE9do_assignEPKcS7_j used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail19raise_runtime_errorERKSt13runtime_error used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZNK5boost9re_detail31cpp_regex_traits_implementationIcE9transformEP
[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)
I don't think that's the issue. The nvidia problem I was used to is being unable to resume. I also tested with the nvidia drivers disabled and this issue still persists. Something I noticed is that I was not on the recommended version of nvidia drivers which is 415 and I just changed that now upgrading to 418. Still exactly the same issue. Tested with various DE's and even out DE's running. Do you have any other guess? Is there a better way to find out what's wrong? To see dmesg while it is trying to hibernate maybe? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819915 Title: s2disk freezes at saving image to disk (hibernation) Status in linux package in Ubuntu: Confirmed Bug description: This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1 hibernation was working flawlessly on my machine. (with kernel 4.15-46! not a kernel issue then?) Another thing that got updated recently was nvidia drivers which were known to cause hibernation issues, but those were on restoring the snapshot. http://imgur.com/gallery/jOyHEcL --> I get stuck on this screen after running hibernate or pm-hibernate. (sys-req REISUB combination works there and is the only good way to restart I found) SPECS Laptop Dell Inspiron 7567 A30P Intel Core i7-7700HQ 1x 16 GB DDR4 1 TB HDD + 256 GB SSD Nvidia GeForce GTX 1050 Ti FHD display Intel Dual Band Wireless AC 3165 1x1 Motherboard: Intel HM175 Graphics adapter: NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, Core: 1620 MHz, Memory: 1752 MHz, GDDR5, 21.21.13.7320 (ForceWare 373.20), Nvidia Optimus nvidia driver: 415.27 INFO # uname -a Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # free -m totalusedfree shared buff/cache available Mem: 1590629258742 1614238 12485 Swap: 16333 0 16333 # cat /etc/fstab | grep swap # swap was on /dev/sda8 during installation UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw 0 0 n root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernate root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hiber root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep s2disk root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernation I could find nothing scrolling up on syslog about the hibernation process or with grep An interesting Note is that if I run hibernate just after I boot, it works and resumes perfectly! But after some system usage it randomly has that problem if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 once. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: matheus 25949 F...m pulseaudio /dev/snd/pcmC0D0p: matheus 25949 F...m pulseaudio /dev/snd/controlC0: matheus 25949 F pulseaudio /dev/snd/seq:matheus4986 f qsynth CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06 InstallationDate: Installed on 2018-05-10 (308 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 15 7000 Gaming NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug no_console_suspend systemd.log_level=info nvidia-drm.modeset=0 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: In
[Kernel-packages] [Bug 1821466] Re: Kernel 4.4.0-143 faulty
Hello, can you attach the error log mentioned in your screenshot, "/var/log/vbox-setup.log"? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821466 Title: Kernel 4.4.0-143 faulty Status in linux package in Ubuntu: Incomplete Bug description: Since kernel update to 4.4.0-143, Oracle Virtualbox machines does not run anymore: http://cb3hn.dyndns.tv/tmp/virtualbox_5.2.26.png http://cb3hn.dyndns.tv/tmp/vboxconfig.png Regards... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821537] Re: Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16
Series tracked for Cosmic, as per Seth's comment: USB_XHCI_DBGCAP has been enabled since cosmic. I've now enabled CONFIG_EARLY_PRINTK_USB_XDBC as well in disco. ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821537 Title: Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16 Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Confirmed Bug description: Since kernel 4.13 Linux supports an USB debug console with passive USB 3.x host-to-host cables aka "USB 3.0 super-speed A-to-A debugging cable". Beginning with kernel 4.16 a serial port (/dev/ttyDbC) has been added (https://www.kernel.org/doc/html/v4.16/driver-api/usb/usb3-debug-port.html#serial-tty). I suggest to enable USB DbC by enabling the kernel options "CONFIG_EARLY_PRINTK_USB_XDBC=Y" and "USB_XHCI_DBGCAP=Y" in Ubuntu kernels >= 4.16 for Bionic HWE and newer ubuntu versions. It would also be great to get feedback about line speed from others as USB_XHCI_DBGCAP serial ports could be used for network connections via tun/tap devices or PPP/SLIP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
(In reply to JerryD from comment #578) > $ sudo rdmsr -a 0xc0011020 > 68000 > > This is on: > > cpu family: 23 > model : 17 > model name: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx > stepping : 0 > microcode : 0x8101007 You're showing me the MSR output for erratum 1033 but your CPU is not affected. > Has your patch been applied to kernel yet? No it hasn't - I'm still waiting for someone to test it and confirm that it fixes the issue on their boxes. And by issue I don't mean erratum 1033 - that is a red herring anyway - but the lockups people are reporting on some broken BIOSes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zap
[Kernel-packages] [Bug 1690085]
(In reply to Borislav Petkov from comment #571) > (In reply to Lars Viklund from comment #570) > > rdmsr yields 68010, which has bit 4 set. > > Looks like your BIOS applies the fix. Now, does the patch in comment #526 > fix your freezes? Hi Boris, on my laptop with its latest BIOS I get: $ sudo rdmsr -a 0xc0011020 68000 This is on: cpu family : 23 model : 17 model name : AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx stepping: 0 microcode : 0x8101007 Booting with: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.20.16-200.fc29.x86_64 root=/dev/mapper/fedora-root ro resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8 idle=nomwait iommu=pt processor.max_cstate=1 Has your patch been applied to kernel yet? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks ---
[Kernel-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-hwe (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821533 Title: failure to detect and use Intel 620 graphics pci id 3ea0 Status in linux-hwe package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb install (also 18.10, also 19.04 daily) leads to black screen. Adding "nomodeset" to kernel boot parameter gives 800x600 video only and permits installing OS to disk. Applying updates and hardware enablement packages does not solve problem: the system will still only boot with nomodeset kernel option, and X is limited to using fbdev module at 800x600 resolution. The "modesetting" driver appears to be loaded and then unloaded during X startup. Trying to force intel module from xserver-xorg-video-intel by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does not help. The PCI id for the graphics device appears to be 3ea0 and the place where that might be relevant is the i915 module. This problem occurs with every other Linux release I have tried including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest. The one open source OS that I have found where it might be fixed is DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have verified that the patch referenced in that bug report does make DragonFlyBSD boot past the video problem which I think is the same problem I experience with every Linux OS I have tried including Ubuntu. guest@guest-ZenBook-UX431FA:~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev" ii linux-generic-hwe-18.044.18.0.16.66 amd64Complete Generic Linux kernel and headers ii linux-headers-generic-hwe-18.044.18.0.16.66 amd64Generic Linux kernel headers ii linux-image-generic-hwe-18.04 4.18.0.16.66 amd64Generic Linux kernel image ii linux-signed-generic-hwe-18.04 4.18.0.16.66 amd64Complete Signed Generic Linux kernel and headers (dummy transitional package) ii xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1 amd64X.Org X server -- fbdev display driver Expected result: Video at 1920x1080 Actual result: Video limited to 800x600 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 10:36:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:17d1] InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431FA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18
[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Please try live booting 19.04: http://cdimages.ubuntu.com/daily-live/current/ and tell us if audio works there. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
** Tags added: bionic ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821371] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821371 Title: [nouveau] Black screen with some icons flashing on start-up Status in linux package in Ubuntu: Confirmed Bug description: when i start , i can't have ubuntu , but black screen with some icones flashing , my arrow of the mouse can move but do nothing , i'm french so excuse me for my language ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_36_39_generic_48 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Fri Mar 22 16:34:18 2019 DistUpgraded: 2018-07-23 08:19:08,090 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 740] [1458:368d] InstallationDate: Installed on 2017-05-19 (672 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Olidata S.p.A. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4bf32425-67a7-4926-91a8-f1fb1b97baaf ro splash quiet plymouth:debug=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-23 (242 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B85M DASH/OL R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/23/2015:svnOlidataS.p.A.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85MDASH/OLR2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jul 22 08:14:02 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver MOUSE, id 9 inputLogitech USB Receiver KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821371] Re: starting
It appears Xorg can't open the GPU device: [ 125.196] (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 [ 125.196] (EE) open /dev/dri/card0: No such file or directory [ 125.196] (WW) Falling back to old probe method for modesetting [ 125.196] (EE) open /dev/dri/card0: No such file or directory which may or may not be related to this kernel error: [ 75.351253] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 75.351261] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 75.351263] nouveau :01:00.0: msvld: unable to load firmware data [ 75.351266] nouveau :01:00.0: msvld: init failed, -19 ** Tags added: nouveau ** Summary changed: - starting + [nouveau] Black screen with some icons flashing on start-up ** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu) ** Package changed: xserver-xorg-video-nouveau (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821371 Title: [nouveau] Black screen with some icons flashing on start-up Status in linux package in Ubuntu: Confirmed Bug description: when i start , i can't have ubuntu , but black screen with some icones flashing , my arrow of the mouse can move but do nothing , i'm french so excuse me for my language ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_36_39_generic_48 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Fri Mar 22 16:34:18 2019 DistUpgraded: 2018-07-23 08:19:08,090 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 740] [1458:368d] InstallationDate: Installed on 2017-05-19 (672 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Olidata S.p.A. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4bf32425-67a7-4926-91a8-f1fb1b97baaf ro splash quiet plymouth:debug=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-23 (242 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B85M DASH/OL R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/23/2015:svnOlidataS.p.A.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85MDASH/OLR2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jul 22 08:14:02 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver MOUSE, id 9 inputLogitech USB Receiver KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821371] [NEW] [nouveau] Black screen with some icons flashing on start-up
You have been subscribed to a public bug: when i start , i can't have ubuntu , but black screen with some icones flashing , my arrow of the mouse can move but do nothing , i'm french so excuse me for my language ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_36_39_generic_48 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Fri Mar 22 16:34:18 2019 DistUpgraded: 2018-07-23 08:19:08,090 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 740] [1458:368d] InstallationDate: Installed on 2017-05-19 (672 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Olidata S.p.A. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4bf32425-67a7-4926-91a8-f1fb1b97baaf ro splash quiet plymouth:debug=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-23 (242 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B85M DASH/OL R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/23/2015:svnOlidataS.p.A.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85MDASH/OLR2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jul 22 08:14:02 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver MOUSE, id 9 inputLogitech USB Receiver KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic nouveau ubuntu -- [nouveau] Black screen with some icons flashing on start-up https://bugs.launchpad.net/bugs/1821371 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Created attachment 281993 attachment-495-0.html Yep still get hard lock if I don't add both missing IVRS table data for 0:00.2 and 0:14.0 . But, I no longer require i8042.nopnp to get touchpad working, but it does complain about an AUX port being disabled and if it's incorrect it says to use i8042.nopnp. tested with Git freedesktop.org/~agd5f/linux amd-staging-drm-next. On Thu, Mar 21, 2019, 14:32 wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=200087 > > --- Comment #125 from siyia (eutychio...@gmail.com) --- > your fan runs at 100% because you use pci=noacpi > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792045] Re: Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04
Hello again! I apologize for never updating this bug report again. Right after my last response I had a series of bad life events one after another for a few months that kept me away. I'm happy to report that this no longer seems like an issue for me in Ubuntu 18.04. USB speeds are maxing out the devices I've tested. Please close this submission. ** 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/1792045 Title: Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04 Status in linux package in Ubuntu: Fix Released Bug description: I cannot get my external 8TB sata hard drive (attached via USB 3) to write faster than about 10 megabytes per second under Ubuntu 18.04. I have another that writes at the expected full speed or close enough (100+ MBps). I have tried: * Changing the enclosure from the stock to a new one * Using usb-storage "quirks" options in modprobe conf files to work around any UAS incompatibilities with the bridge (many reports of the drive working at full performance when disabling UAS, no such luck for me) * Checking the disk for errors * Updating the kernel to the most recent mainline (4.18.6 at the time) * Checking UEFI settings (I'm already on the most recent revision of the firmware) * Applying all available updates * Changing USB ports * Checking dmesg for any obvious errors (dead end, I googled everything) Again, a different external 3TB USB 3 drive does not have any write speed issues at all, so it's not the computer (Intel NUC7PJYH). However, the very same drive in both of the enclosures I have used works *perfectly* in Ubuntu 16.04 on kernel 4.15.0-34 in both a live session and installed. I am not sure what the difference is between the two LTS versions that is causing this, but unfortunately I think I've reached the end of my know-how on this. Thank you for your time, and please let me know what other information I can provide. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Sep 11 18:33:46 2018 InstallationDate: Installed on 2018-09-06 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 1997:2433 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7PJYH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=b40fd1a1-0de5-40bb-b598-7f4cd53daee1 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/21/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0044.2018.0821.1915 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67969-401 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0044.2018.0821.1915:bd08/21/2018:svnIntelCorporation:pnNUC7PJYH:pvrJ67992-401:rvnIntelCorporation:rnNUC7JYB:rvrJ67969-401:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC7PJYH dmi.product.version: J67992-401 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage
The editing of overcommits makes chromium crash. So I don't know -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: When DMA is disabled system freeze on high memory usage Status in linux package in Ubuntu: Incomplete Status in linux package in Arch Linux: New Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821537] Re: Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16
@ubuntu-kernel-bot: Missing things can't be logged. ;-) @all: Don't use simple A-to-A USB cables for USB 3.x slave devices as they can fry your hardware. See cable specs in section 5.5.2 of the USB 3.0 specification (https://i.stack.imgur.com/YwsX3.png). ** 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/1821537 Title: Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 4.13 Linux supports an USB debug console with passive USB 3.x host-to-host cables aka "USB 3.0 super-speed A-to-A debugging cable". Beginning with kernel 4.16 a serial port (/dev/ttyDbC) has been added (https://www.kernel.org/doc/html/v4.16/driver-api/usb/usb3-debug-port.html#serial-tty). I suggest to enable USB DbC by enabling the kernel options "CONFIG_EARLY_PRINTK_USB_XDBC=Y" and "USB_XHCI_DBGCAP=Y" in Ubuntu kernels >= 4.16 for Bionic HWE and newer ubuntu versions. It would also be great to get feedback about line speed from others as USB_XHCI_DBGCAP serial ports could be used for network connections via tun/tap devices or PPP/SLIP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage
So as a conclusion for my old 2Gb laptop, I've set zram to twice of amount of physical RAM (/usr/bin/init-zram-swapping), and have added this parameters to /etc/sysctl.d/99-sysctl.conf: vm.min_free_kbytes=128000 vm.overcommit_memory=2 vm.overcommit_ratio=90 And seems it work for me. And I have to say that I don't have physical swap and have /tmp and /var/tmp mounted to ram disk. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: When DMA is disabled system freeze on high memory usage Status in linux package in Ubuntu: Incomplete Status in linux package in Arch Linux: New Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821537] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1821537 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821537 Title: Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16 Status in linux package in Ubuntu: Incomplete Bug description: Since kernel 4.13 Linux supports an USB debug console with passive USB 3.x host-to-host cables aka "USB 3.0 super-speed A-to-A debugging cable". Beginning with kernel 4.16 a serial port (/dev/ttyDbC) has been added (https://www.kernel.org/doc/html/v4.16/driver-api/usb/usb3-debug-port.html#serial-tty). I suggest to enable USB DbC by enabling the kernel options "CONFIG_EARLY_PRINTK_USB_XDBC=Y" and "USB_XHCI_DBGCAP=Y" in Ubuntu kernels >= 4.16 for Bionic HWE and newer ubuntu versions. It would also be great to get feedback about line speed from others as USB_XHCI_DBGCAP serial ports could be used for network connections via tun/tap devices or PPP/SLIP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821537] [NEW] Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16
Public bug reported: Since kernel 4.13 Linux supports an USB debug console with passive USB 3.x host-to-host cables aka "USB 3.0 super-speed A-to-A debugging cable". Beginning with kernel 4.16 a serial port (/dev/ttyDbC) has been added (https://www.kernel.org/doc/html/v4.16/driver-api/usb/usb3-debug-port.html#serial-tty). I suggest to enable USB DbC by enabling the kernel options "CONFIG_EARLY_PRINTK_USB_XDBC=Y" and "USB_XHCI_DBGCAP=Y" in Ubuntu kernels >= 4.16 for Bionic HWE and newer ubuntu versions. It would also be great to get feedback about line speed from others as USB_XHCI_DBGCAP serial ports could be used for network connections via tun/tap devices or PPP/SLIP. ** 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/1821537 Title: Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16 Status in linux package in Ubuntu: New Bug description: Since kernel 4.13 Linux supports an USB debug console with passive USB 3.x host-to-host cables aka "USB 3.0 super-speed A-to-A debugging cable". Beginning with kernel 4.16 a serial port (/dev/ttyDbC) has been added (https://www.kernel.org/doc/html/v4.16/driver-api/usb/usb3-debug-port.html#serial-tty). I suggest to enable USB DbC by enabling the kernel options "CONFIG_EARLY_PRINTK_USB_XDBC=Y" and "USB_XHCI_DBGCAP=Y" in Ubuntu kernels >= 4.16 for Bionic HWE and newer ubuntu versions. It would also be great to get feedback about line speed from others as USB_XHCI_DBGCAP serial ports could be used for network connections via tun/tap devices or PPP/SLIP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage
I've tried to set vm.min_free_kbytes to 6% of my total physical RAM, divided by
the number of cores as it is said there
https://askubuntu.com/questions/41778/computer-freezing-on-almost-full-ram-possibly-disk-cache-problem,
but I decided to keep vm.swapiness at its default (60), because I was going to
tune up zram.
And then I had installed zram-config package, opened
/usr/bin/init-zram-swapping file with my text editor and had changed this string
mem=$(((totalmem / 2 / ${NRDEVICES}) * 1024))
to this:
mem=$(((totalmem / 2 / ${NRDEVICES}) * 5 * 1024))
Then I had rebooted and tested this all with "stress -m 4 --vm-bytes=1G".
This all was happening on my one core 2Gb x86 Lubuntu 16.04 notebook. Seems it
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/159356
Title:
When DMA is disabled system freeze on high memory usage
Status in linux package in Ubuntu:
Incomplete
Status in linux package in Arch Linux:
New
Bug description:
I run a batch matlab job server here at my lab, running Dapper 6.06 (for the
LTS). One of the users has submitted a very memory-consuming job, which
successfully crashes the server. Upon closer inspection, the crash happens like
this:
1. I run matlab with the given file (as an ordinary, unpriveleged user)
2. RAM usage quickly fills up
3. Once the RAM meter hits 100%, the system freezes: All SSH connections
freeze up, and while switching VTs directly on the machine works, no new
processes run - so one can't log in, or do anything if he is logged in.
(Sometimes typing doesn't work at all)
Note that the swap - while 7 gigs of it are available - is never used.
(The machine has 7 gigs of RAM as well)
I've tried the same on my Gutsy 32-bit box, and there was no system
freezeup - matlab simply notified that the system was out of memory.
However, it did this once memory was 100% in use - and still, swap
didn't get used at all! (Though it is mounted correctly and shows up
in "top" and "free").
So first thing's first - I'd like to eliminate the crash issue. I
suppose I could switch the server to 32-bit, but I think that would be
a performance loss, considering that it does a lot of heavy
computation. There is no reason, however, that this should happen on a
64-bit machine anyway. Why does it?
WORKAROUND: Enabling DMA in the BIOS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
I was experiencing a situation with moby dockerd entering a state similar to comment 0 here, running kubernetes and linux kernel 4.15.0-1037-azure. This was an 8 node cluster. Observed with combinations: kubernetes 1.11.5 + moby runtime 3.0.1 + Ubuntu 16.04.5 kubernetes 1.11.7 + moby runtime 3.0.4 + Ubuntu 16.04.10 The longest window between outages prior was 4 days, with the shortest being less than a day. I have observed 2 weeks of uptime on 8 nodes without observation of the original symptoms since upgrading the kubernetes node kernel to 4.15.0-1040-azure. I am confident the kernel patch has resolved our problem. Ref https://github.com/moby/moby/issues/38750 and https://github.com/Azure/AKS/issues/838, both closed. ** Bug watch added: github.com/moby/moby/issues #38750 https://github.com/moby/moby/issues/38750 ** Bug watch added: github.com/Azure/AKS/issues #838 https://github.com/Azure/AKS/issues/838 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-azure source package in Cosmic: Fix Released Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev&id=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist,
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
As Marius mentioned we already deployed this patch on several instances and now we are monitoring them to see if this still happens. At least 2 of them were affected by the bug before patching so we had to reboot them. If the above information (previous post) is correct and considering the time until this might reproduce or not, I think you might want to include this fix into existing release cycle. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-azure source package in Cosmic: Fix Released Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev&id=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
@mfo Just to confirm that we installed the right proposed version of the kernel as this doesn't have any steps to reproduce. It only reproduces randomly after a certain amount of time. These are the steps we followed to install echo 'deb http://archive.ubuntu.com/ubuntu/ xenial-proposed restricted main multiverse universe' > /etc/apt/sources.list.d/kernel.list echo -e "Package: *\nPin: release a=xenial-proposed\nPin-Priority: 400" > /etc/apt/preferences.d/proposed-updates apt-get -t xenial-proposed install -y linux-image-unsigned-4.15.0-47-generic reboot Installed packages dpkg -l | grep -i 4.15.0-47 ii linux-image-unsigned-4.15.0-47-generic 4.15.0-47.50~16.04.1 amd64Linux kernel image for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-47-generic4.15.0-47.50~16.04.1 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP dpkg -l | grep -i hwe ii linux-generic-hwe-16.044.15.0.45.66 amd64Complete Generic Linux kernel and headers ii linux-headers-generic-hwe-16.044.15.0.45.66 amd64Generic Linux kernel headers ii linux-image-generic-hwe-16.04 4.15.0.45.66 amd64Generic Linux kernel image uname -a Linux myhostname 4.15.0-47-generic #50~16.04.1-Ubuntu SMP Fri Mar 15 16:06:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-azure source package in Cosmic: Fix Released Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else).
[Kernel-packages] [Bug 1757445] Re: Suspend does not always resume
It hung again yesterday (S 23 Mar 2019). It used to hang multiple times daily. Anyhow, the laptop was unresponsive. The disk activity light continued as normal, though. However, it did allow me to SSH into it, but hung completely when I tried to open gnome-control-center. That suggests that the X server was hung. I will try to collect some details the next time it hangs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757445 Title: Suspend does not always resume Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Dell XPS 13 9350 on AC power left running overnight, suspends after a given timeout. When coming back the next morning sometimes the laptop resumes to an aubergine desktop (just the screen, no GDM) and cursor and sits there forever. Sometimes it resumes to a black screen and cursor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 21 14:15:04 2018 InstallationDate: Installed on 2018-02-13 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819028] Re: Intel 9260 WiFi adapter doesn't work on B450 motherboard
If latest kernel and latest firmware don't work, Please file an upstream bug at https://bugzilla.kernel.org/ Product: Drivers Component: network-wireless -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819028 Title: Intel 9260 WiFi adapter doesn't work on B450 motherboard Status in linux package in Ubuntu: Confirmed Bug description: Hi, I know this has been a well discussed issue on Linux forums, but I am having extreme issues maintaining the built-in Intel WiFi in my motherboard, it resets everytime I update my distros (Ubuntu 18.04 and Linux Mint Cinnamon 18.3). My best fix for it is following the guide at [https://askubuntu.com/questions/1038242/no-wifi-option-on- ubuntu-18-04-and-16-04]. I am wanting to know if there is a way to make this process more streamlined for users as this affects many and is a hassle to maintain properly. I know this has been addressed before with Ryzen CPUs but this shouldn't have to be necessary if the driver is baked into the kernel as this is quite frustrating for any user to go through, as it requires what is causing the problem to fix - a network connection. I don't mind if it's simpler to have a on/off feature like the Nvidia drivers have, as that is still a lot simpler than writing out a paragraphs of code. TL;DR I'm asking if changes could be added so that instead of needing a network connection (something that you can't have if the driver isn't built into/available through the distro) and writing a dissertation of code, they have a driver automatically work or a switch option like Broadcom and Nvidia have in this photo [https://linuxhint.com/wp-content/uploads/2017/11/driver-manager-1.png] I was referred here by the Linux Mint forum, please refer to the page in case any questions have already been answered there [https://forums.linuxmint.com/viewtopic.php?f=49&t=289358&e=1&view=unread#unread] My system is a AMD Ryzen 2700x B450 with built-in Intel 9260 WiFi, Linux Mint 18.3/Ubuntu 18.04 dual boot. Thanks, Bionicle159 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amir 2179 F pulseaudio /dev/snd/controlC1: amir 2179 F pulseaudio /dev/snd/controlC2: amir 2179 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b InstallationDate: Installed on 2018-08-22 (210 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Micro-Star International Co., Ltd. MS-7B85 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=4c3c212e-59c3-4de8-a1a2-24acc6e040d6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 GAMING PRO CARBON AC (MS-7B85) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd08/06/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B85:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450GAMINGPROCARBONAC(MS-7B85):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B85 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amir 2179 F pulseaudio /dev/snd/controlC1: amir 2179 F pulseaudio /dev/snd/controlC2: amir 2179 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b InstallationDate: Installed on 2018-08-22 (210 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Micro-Star International Co., Ltd. MS-7B85 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (no
[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed
Hi Tyler, We did a kernel bisecting and we fount that the mentioned commit is the root cause of this big, if bionic contain this commit, so the bug also in bionic release. yours, Talat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801574 Title: [cosmic] ipoib ping with large message size failed Status in linux package in Ubuntu: Confirmed Bug description: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please check with the canonical kernel team why they revert that commit? To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 2044 MTU (default) and run command [2]. Is there open Launchpad on it? [1] commit 77a24c313d21e3765b04d90521e9228a9bb6e332 Author: Tyler Hicks Date: Fri Aug 3 21:53:15 2018 + Revert "net: increase fragment memory usage limits" This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It made denial of service attacks on the IP fragment handling easier to carry out. CVE-2018-5391 Signed-off-by: Tyler Hicks Signed-off-by: Stefan Bader [2] ping 13.194.22.1 -I 13.194.23.1 -s 65507 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)
So maybe it's caused by Nvidia driver update? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819915 Title: s2disk freezes at saving image to disk (hibernation) Status in linux package in Ubuntu: Confirmed Bug description: This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1 hibernation was working flawlessly on my machine. (with kernel 4.15-46! not a kernel issue then?) Another thing that got updated recently was nvidia drivers which were known to cause hibernation issues, but those were on restoring the snapshot. http://imgur.com/gallery/jOyHEcL --> I get stuck on this screen after running hibernate or pm-hibernate. (sys-req REISUB combination works there and is the only good way to restart I found) SPECS Laptop Dell Inspiron 7567 A30P Intel Core i7-7700HQ 1x 16 GB DDR4 1 TB HDD + 256 GB SSD Nvidia GeForce GTX 1050 Ti FHD display Intel Dual Band Wireless AC 3165 1x1 Motherboard: Intel HM175 Graphics adapter: NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, Core: 1620 MHz, Memory: 1752 MHz, GDDR5, 21.21.13.7320 (ForceWare 373.20), Nvidia Optimus nvidia driver: 415.27 INFO # uname -a Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # free -m totalusedfree shared buff/cache available Mem: 1590629258742 1614238 12485 Swap: 16333 0 16333 # cat /etc/fstab | grep swap # swap was on /dev/sda8 during installation UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw 0 0 n root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernate root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hiber root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep s2disk root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernation I could find nothing scrolling up on syslog about the hibernation process or with grep An interesting Note is that if I run hibernate just after I boot, it works and resumes perfectly! But after some system usage it randomly has that problem if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 once. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: matheus 25949 F...m pulseaudio /dev/snd/pcmC0D0p: matheus 25949 F...m pulseaudio /dev/snd/controlC0: matheus 25949 F pulseaudio /dev/snd/seq:matheus4986 f qsynth CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06 InstallationDate: Installed on 2018-05-10 (308 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 15 7000 Gaming NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug no_console_suspend systemd.log_level=info nvidia-drm.modeset=0 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
