[Kernel-packages] [Bug 1793369] Re: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc/sysrq-trigger
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1810 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793369 Title: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc /sysrq-trigger Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in linux source package in Cosmic: Invalid Status in systemd source package in Cosmic: Won't Fix Bug description: == Comment: #0 - Praveen K. Pandey - 2018-09-19 04:49:39 == ---Problem Description--- [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] : Sysrq trigger disabled when writing to /proc/sysrq-trigger while testing kdump trying trigger kdump panic via /proc/sysrq-trigger it failed as : SysRq : This sysrq operation is disabled LOG: root@test:~# cat /proc/sys/kernel/sysrq 176 root@test:~# echo c > /proc/sysrq-trigger root@test:~# dmesg [ 380.340051] mlx5_core :01:00.1 enp1s0f1: Self test out: status flags(0x2) [ 389.404239] sysrq: SysRq : This sysrq operation is disabled. root@test~# cat /boot/config-4.18.0-7-generic | grep CONFIG_MAGIC_SYSRQ CONFIG_MAGIC_SYSRQ=y CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6 CONFIG_MAGIC_SYSRQ_SERIAL=y root@test:~# cat /etc/sysctl.conf | grep kernel.sysrq #kernel.sysrq=438 root@test:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-7-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-7-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=c0302064-c5a3-49a7-8bd4-402283e6fcbe ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@test:~# Regards Praveen == Comment: #2 - Praveen K. Pandey - 2018-09-19 05:16:11 == when i enable in /etc/sysctl.conf it works . i append below value in sysctl.conf echo "kernel.sysrq = 1" >> /etc/sysctl.conf I think this is should be enable by default in ubuntu 18.10 as earlier ubuntu distro it has , not sure why it got removed as kdump mechanism require this . Praveen Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1793369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769792] Re: Keyboard and Touchpad do not work after suspend/resume
If I'm not wrong bisection has been done by Guido Aulisi on https://bugzilla.redhat.com/show_bug.cgi?id=1436636, Comment 4. In any case, right now I can't try the bisection. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769792 Title: Keyboard and Touchpad do not work after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: My laptop is a Toshiba Satellite C850D with updated 18.04 installed. When resuming from suspend, I have no keyboard and touchpad. dmesg shows "i8042: Can't reactivate KBD port" This looks like a recurring problem, and is just like these: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142118 Here's the dmesg output from before and after suspending. https://paste.ubuntu.com/p/rsFX9Yw7Xh/ This post also talks about this bit failing for a lot of people! http://lightrush.ndoytchev.com/random-1/i8042quirkoptions Some of the function keys work, such as changing the screen brightness, but the key (fn+F5) does not turn the touchpad back on. I have not yet tried any of the suggested options, as results have been mixed, but I will. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 22:01:26 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a
** Package changed: ubuntu => linux-signed-hwe (Ubuntu) ** Package changed: linux-signed-hwe (Ubuntu) => linux-signed (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1793997 Title: iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a Status in linux-signed package in Ubuntu: New Bug description: Every few days iwlwifi decides to stop working. Only recourse is restart. From syslog: Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi transaction failed, dumping registers Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi device config registers: Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: : 08b18086 0010 028000bb 0004 Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 0020: 40708086 00c8 0100 Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi device memory mapped registers: Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: : Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 0020: Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi device AER capability structure: Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: : 14010001 0010 00462031 3141 2000 0014 4001 Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 0020: 000f ec100460 Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi parent port (:00:1c.3) config registers: Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: : 8c168086 0017 060400d5 00810010 00040400 20f0 Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 0020: ec10ec10 0001fff1 0040 00100405 Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here ] Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at /build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi] Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4 vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt intel_rapl x86_pkg_temp_thermal Sep 24 11:42:10 bonobo kernel: [109525.538898] intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4 intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables Sep 24 11:42:10 bonobo kernel: [109525.538952] x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm rtsx_pci psmouse ahci r8169 libahci ipmi_devintf mii ipmi_msghandler video wmi Sep 24 11:42:10 bonobo kernel: [109525.538982] CPU: 5 PID: 0 Comm: swapper/5 Tainted: P OE4.15.0-34-generic #37-Ubuntu
[Kernel-packages] [Bug 1793997] [NEW] iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a
You have been subscribed to a public bug:
Every few days iwlwifi decides to stop working. Only recourse is
restart.
>From syslog:
Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi
transaction failed, dumping registers
Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi
device config registers:
Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: :
08b18086 0010 028000bb 0004
Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 0020:
40708086 00c8 0100
Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi
device memory mapped registers:
Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: :
Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 0020:
Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi
device AER capability structure:
Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: :
14010001 0010 00462031 3141 2000 0014 4001
Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 0020:
000f ec100460
Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi
parent port (:00:1c.3) config registers:
Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: :
8c168086 0017 060400d5 00810010 00040400 20f0
Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 0020:
ec10ec10 0001fff1 0040 00100405
Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here
]
Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware
access (CSR_GP_CNTRL 0x)
Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at
/build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973
iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi]
Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in:
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub
vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel
tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4
vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables
devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt
intel_rapl x86_pkg_temp_thermal
Sep 24 11:42:10 bonobo kernel: [109525.538898] intel_powerclamp coretemp
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4
intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel
snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm
btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo
intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm
mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi
snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev
snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid
ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp
parport ip_tables
Sep 24 11:42:10 bonobo kernel: [109525.538952] x_tables autofs4 btrfs xor
zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid
nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper
syscopyarea sysfillrect sysimgblt fb_sys_fops drm rtsx_pci psmouse ahci r8169
libahci ipmi_devintf mii ipmi_msghandler video wmi
Sep 24 11:42:10 bonobo kernel: [109525.538982] CPU: 5 PID: 0 Comm: swapper/5
Tainted: P OE4.15.0-34-generic #37-Ubuntu
Sep 24 11:42:10 bonobo kernel: [109525.538983] Hardware name: System76, Inc.
Bonobo WS /Bonobo WS , BIOS
4.6.5 05/15/2015
Sep 24 11:42:10 bonobo kernel: [109525.538993] RIP:
0010:iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi]
Sep 24 11:42:10 bonobo kernel: [109525.538995] RSP: 0018:89ce6ed43dc8
EFLAGS: 00010086
Sep 24 11:42:10 bonobo kernel: [109525.538997] RAX: RBX:
89ce442c0018 RCX: 0006
Sep 24 11:42:10 b
[Kernel-packages] [Bug 1782888] Re: trackpad not recognised by kernel
[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/1782888 Title: trackpad not recognised by kernel Status in linux package in Ubuntu: Expired Bug description: This is a new laptop with reference TongFang GI5CN5E The UK supplier is unable to give me any further details about the trackpad, but they agree that there is a problem with the Linux kernel. There is no response from the trackpad. An external mouse works fine. Further details: Linux Mint 19 (Ubuntu 18.04 - bionic) ubuntu-bug linux command did not work: *** Problem in linux-image-4.15.0-29-generic The problem cannot be reported: This is not an official Linux package. Please remove any third party package and try again. I attempted to attach various diagnostic files as per the instructions for reporting this bug but as this system is not confirming what has been attached I also attached (I hope) a file with all 4 reports. Sorry if this is noise... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 2775 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=8d3430b5-51a5-4052-877b-d840f6ea53d7 InstallationDate: Installed on 2018-07-01 (19 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: PC Specialist LTD Vyper NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.01 dmi.board.asset.tag: Standard dmi.board.name: GI5CN5E dmi.board.vendor: Tong Fang dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: Standard dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.01:bd04/09/2018:svnPCSpecialistLTD:pnVyper:pvrStandard:rvnTongFang:rnGI5CN5E:rvrStandard:cvnStandard:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: Vyper dmi.product.version: Standard dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790249] Re: desktop sharing won't start after upgrading to 18.04
system won't give me a chance to boot back to the prior kernel as you can see from attached photo. After all that unreadable stuff scrolling past, it goes straight to the home screen (with automatic login). ** Attachment added: "DSCN0348.JPG" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790249/+attachment/5192198/+files/DSCN0348.JPG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790249 Title: desktop sharing won't start after upgrading to 18.04 Status in linux package in Ubuntu: Incomplete Bug description: First time destop sharing was started the system detected a problem which was reported -- so there should be some info for you there already. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:17:29 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793998] 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/1793998 Title: O2 Micro SD Controller Not Functional Status in linux package in Ubuntu: Confirmed Bug description: Upon attempting to use my SD card reader in my Thinkpad W541, I am no longer able to read cards. Ubuntu 17.10 worked OK, but 18.04 does not. I have since done a fresh install and it still does not work. I have tried some workarounds including: sudo rmmod sdhci sdhci_pci sdhci_acpi sudo modprobe sdhci debug_quirks2="0x4" sudo modprobe sdhci_pci including: "0x1", and "0x8000", but none of these are working. I still cannot get my SD card reader from O2 Micro to work. The logs I am getting when inserting an SD card are the following: 7:26:36 PM kernel: mmc0: sdhci: 7:26:36 PM kernel: mmc0: sdhci: ADMA Err: 0x | ADMA Ptr: 0x 7:26:36 PM kernel: mmc0: sdhci: Host ctl2: 0x 7:26:36 PM kernel: mmc0: sdhci: Resp[2]: 0x | Resp[3]: 0x 7:26:36 PM kernel: mmc0: sdhci: Resp[0]: 0x | Resp[1]: 0x 7:26:36 PM kernel: mmc0: sdhci: Cmd: 0x341a | Max curr: 0x005800c8 7:26:36 PM kernel: mmc0: sdhci: Caps: 0x25fec8bf | Caps_1: 0x10002078 7:26:36 PM kernel: mmc0: sdhci: AC12 err: 0x | Slot int: 0x 7:26:36 PM kernel: mmc0: sdhci: Int enab: 0x00ff0083 | Sig enab: 0x00ff0083 7:26:36 PM kernel: mmc0: sdhci: Timeout: 0x | Int stat: 0x 7:26:36 PM kernel: mmc0: sdhci: Wake-up: 0x | Clock:0xfa07 7:26:36 PM kernel: mmc0: sdhci: Power: 0x000f | Blk gap: 0x 7:26:36 PM kernel: mmc0: sdhci: Present: 0x01ff0001 | Host ctl: 0x0001 7:26:36 PM kernel: mmc0: sdhci: Argument: 0x0c00 | Trn mode: 0x 7:26:36 PM kernel: mmc0: sdhci: Blk size: 0x | Blk cnt: 0x 7:26:36 PM kernel: mmc0: sdhci: Sys addr: 0x | Version: 0x0603 7:26:36 PM kernel: mmc0: sdhci: SDHCI REGISTER DUMP === 7:26:36 PM kernel: mmc0: Timeout waiting for hardware cmd interrupt. 7:26:23 PM kernel: mmc0: Unknown controller version (3). You may experience problems. Any help is welcome, but I am submitting this as a bug, because it seems to be affecting all of my laptops with O2 Micro's as well, not just my Thinkpad W541 I am writing this on right now. Output of lspci -v: 02:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01) (prog-if 01) Subsystem: Lenovo SD/MMC Card Reader Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at b4901000 (32-bit, non-prefetchable) [size=4K] Memory at b490 (32-bit, non-prefetchable) [size=2K] Capabilities: [6c] Power Management version 3 Capabilities: [48] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [200] Advanced Error Reporting Capabilities: [230] Latency Tolerance Reporting Kernel driver in use: sdhci-pci Kernel modules: sdhci_pci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1449 F pulseaudio /dev/snd/pcmC1D0c: michael1449 F...m pulseaudio /dev/snd/pcmC1D0p: michael1449 F...m pulseaudio /dev/snd/controlC1: michael1449 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sun Sep 23 19:43:46 2018 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20EFCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=37e56de6-bb7b-4246-8524-093c50e55296 ro quiet splash nouveau.runpm=0 sdhci.debug_quirks2=0x4 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GNET88WW (2.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.versio
[Kernel-packages] [Bug 1793998] [NEW] O2 Micro SD Controller Not Functional
Public bug reported: Upon attempting to use my SD card reader in my Thinkpad W541, I am no longer able to read cards. Ubuntu 17.10 worked OK, but 18.04 does not. I have since done a fresh install and it still does not work. I have tried some workarounds including: sudo rmmod sdhci sdhci_pci sdhci_acpi sudo modprobe sdhci debug_quirks2="0x4" sudo modprobe sdhci_pci including: "0x1", and "0x8000", but none of these are working. I still cannot get my SD card reader from O2 Micro to work. The logs I am getting when inserting an SD card are the following: 7:26:36 PM kernel: mmc0: sdhci: 7:26:36 PM kernel: mmc0: sdhci: ADMA Err: 0x | ADMA Ptr: 0x 7:26:36 PM kernel: mmc0: sdhci: Host ctl2: 0x 7:26:36 PM kernel: mmc0: sdhci: Resp[2]: 0x | Resp[3]: 0x 7:26:36 PM kernel: mmc0: sdhci: Resp[0]: 0x | Resp[1]: 0x 7:26:36 PM kernel: mmc0: sdhci: Cmd: 0x341a | Max curr: 0x005800c8 7:26:36 PM kernel: mmc0: sdhci: Caps: 0x25fec8bf | Caps_1: 0x10002078 7:26:36 PM kernel: mmc0: sdhci: AC12 err: 0x | Slot int: 0x 7:26:36 PM kernel: mmc0: sdhci: Int enab: 0x00ff0083 | Sig enab: 0x00ff0083 7:26:36 PM kernel: mmc0: sdhci: Timeout: 0x | Int stat: 0x 7:26:36 PM kernel: mmc0: sdhci: Wake-up: 0x | Clock:0xfa07 7:26:36 PM kernel: mmc0: sdhci: Power: 0x000f | Blk gap: 0x 7:26:36 PM kernel: mmc0: sdhci: Present: 0x01ff0001 | Host ctl: 0x0001 7:26:36 PM kernel: mmc0: sdhci: Argument: 0x0c00 | Trn mode: 0x 7:26:36 PM kernel: mmc0: sdhci: Blk size: 0x | Blk cnt: 0x 7:26:36 PM kernel: mmc0: sdhci: Sys addr: 0x | Version: 0x0603 7:26:36 PM kernel: mmc0: sdhci: SDHCI REGISTER DUMP === 7:26:36 PM kernel: mmc0: Timeout waiting for hardware cmd interrupt. 7:26:23 PM kernel: mmc0: Unknown controller version (3). You may experience problems. Any help is welcome, but I am submitting this as a bug, because it seems to be affecting all of my laptops with O2 Micro's as well, not just my Thinkpad W541 I am writing this on right now. Output of lspci -v: 02:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01) (prog-if 01) Subsystem: Lenovo SD/MMC Card Reader Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at b4901000 (32-bit, non-prefetchable) [size=4K] Memory at b490 (32-bit, non-prefetchable) [size=2K] Capabilities: [6c] Power Management version 3 Capabilities: [48] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [200] Advanced Error Reporting Capabilities: [230] Latency Tolerance Reporting Kernel driver in use: sdhci-pci Kernel modules: sdhci_pci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1449 F pulseaudio /dev/snd/pcmC1D0c: michael1449 F...m pulseaudio /dev/snd/pcmC1D0p: michael1449 F...m pulseaudio /dev/snd/controlC1: michael1449 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sun Sep 23 19:43:46 2018 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20EFCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=37e56de6-bb7b-4246-8524-093c50e55296 ro quiet splash nouveau.runpm=0 sdhci.debug_quirks2=0x4 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GNET88WW (2.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20EFCTO1WW:pvrThinkPadW541:rvnLENOVO:rn20EFCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W541 dmi.product.name: 20EFCTO1WW dmi.product.version: ThinkPad W541 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided
[Kernel-packages] [Bug 1793988] 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/1793988 Title: Onscreen keyboard not appearing. Status in linux package in Ubuntu: Confirmed Bug description: Virtual/onscreen keyboard is missing in action. Changes in the Settings do not seem to be altered as they should. lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-35-generic 4.15.0-35.38 ProcVersionSignature: Ubuntu 4.15.0-35.38-generic 4.15.18 Uname: Linux 4.15.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jd 2192 F pulseaudio /dev/snd/controlC0: jd 2192 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 23 17:54:30 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=772f4c39-46bc-4bc3-b1ca-5ce6eed50654 InstallationDate: Installed on 2017-10-26 (331 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: LENOVO 9960ALU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-35-generic root=UUID=61a4594d-c2f3-400f-93b0-5d2fe799864c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-35-generic N/A linux-backports-modules-4.15.0-35-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-27 (149 days ago) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NONE dmi.chassis.asset.tag: � dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn9960ALU:pvrThinkCentreM58:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.family: NONE dmi.product.name: 9960ALU dmi.product.version: ThinkCentre M58 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793988] [NEW] Onscreen keyboard not appearing.
Public bug reported: Virtual/onscreen keyboard is missing in action. Changes in the Settings do not seem to be altered as they should. lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-35-generic 4.15.0-35.38 ProcVersionSignature: Ubuntu 4.15.0-35.38-generic 4.15.18 Uname: Linux 4.15.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jd 2192 F pulseaudio /dev/snd/controlC0: jd 2192 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 23 17:54:30 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=772f4c39-46bc-4bc3-b1ca-5ce6eed50654 InstallationDate: Installed on 2017-10-26 (331 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: LENOVO 9960ALU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-35-generic root=UUID=61a4594d-c2f3-400f-93b0-5d2fe799864c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-35-generic N/A linux-backports-modules-4.15.0-35-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-27 (149 days ago) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NONE dmi.chassis.asset.tag: � dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn9960ALU:pvrThinkCentreM58:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.family: NONE dmi.product.name: 9960ALU dmi.product.version: ThinkCentre M58 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793988 Title: Onscreen keyboard not appearing. Status in linux package in Ubuntu: New Bug description: Virtual/onscreen keyboard is missing in action. Changes in the Settings do not seem to be altered as they should. lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-35-generic 4.15.0-35.38 ProcVersionSignature: Ubuntu 4.15.0-35.38-generic 4.15.18 Uname: Linux 4.15.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jd 2192 F pulseaudio /dev/snd/controlC0: jd 2192 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 23 17:54:30 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=772f4c39-46bc-4bc3-b1ca-5ce6eed50654 InstallationDate: Installed on 2017-10-26 (331 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: LENOVO 9960ALU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-35-generic root=UUID=61a4594d-c2f3-400f-93b0-5d2fe799864c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-35-generic N/A linux-backports-modules-4.15.0-35-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-27 (149 days ago) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NONE dmi.chassis.asset.tag: � dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn9960ALU:pvrThinkCentreM58:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.family: NONE dmi.product.name: 9960ALU dmi.product.version: ThinkCentre M58 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
why is this still not fixed, it is quite a showstopper on dell systems -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
modprobe -r elan_i2c modprobe elan_i2c is a workaround. But Touchpad still freezes after some time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
After some time the Touchpad now stops working and is not usable. External Mouse works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793976] [NEW] kvm kernel missing nbd module
Public bug reported: The "nbd" module is missing from linux-modules-XXX-kvm in bionic root@ubuntu:~# /sbin/modprobe nbd max_part=16 modprobe: FATAL: Module nbd not found in directory /lib/modules/4.15.0-1021-kvm root@ubuntu:~# uname -a Linux ubuntu 4.15.0-1021-kvm #21-Ubuntu SMP Tue Aug 28 09:57:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# dpkg-query -l | grep linux-modules ii linux-modules-4.15.0-1019-kvm 4.15.0-1019.19 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-1021-kvm 4.15.0-1021.21 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-34-generic 4.15.0-34.37 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-extra-4.15.0-34-generic 4.15.0-34.37 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP nbd exists for the generic kernel, but not kvm. root@ubuntu:~# find /lib/modules -name '*nbd*' /lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko root@ubuntu:~# dpkg-query -S /lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko linux-modules-4.15.0-34-generic: /lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko In fact, there are many more modules in the generic kernel: root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-1021-kvm | wc -l 514 root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-34-generic | wc -l 1285 I checked if there is a linux-modules-extra for kvm and this kernel version, but there is not - only for azure. root@ubuntu:~# apt-cache search linux-modules-extra-4.15.0-1021 linux-modules-extra-4.15.0-1021-azure - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP root@ubuntu:~# There is a "linux-image-extra-virtual" package, but it's empty: root@ubuntu:~# dpkg-query -L linux-image-extra-virtual /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-image-extra-virtual /usr/share/doc/linux-image-extra-virtual/copyright /usr/share/doc/linux-image-extra-virtual/changelog.gz As a workaround, I expect I can use the generic kernel - but this won't be optimised for kvm. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-4.15.0-1021-kvm 4.15.0-1021.21 ProcVersionSignature: Ubuntu 4.15.0-1021.21-kvm 4.15.18 Uname: Linux 4.15.0-1021-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sun Sep 23 19:43:56 2018 Dependencies: InstallationDate: Installed on 2018-06-15 (100 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_GB.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1793976 Title: kvm kernel missing nbd module Status in linux-kvm package in Ubuntu: New Bug description: The "nbd" module is missing from linux-modules-XXX-kvm in bionic root@ubuntu:~# /sbin/modprobe nbd max_part=16 modprobe: FATAL: Module nbd not found in directory /lib/modules/4.15.0-1021-kvm root@ubuntu:~# uname -a Linux ubuntu 4.15.0-1021-kvm #21-Ubuntu SMP Tue Aug 28 09:57:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# dpkg-query -l | grep linux-modules ii linux-modules-4.15.0-1019-kvm 4.15.0-1019.19 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-1021-kvm 4.15.0-1021.21 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-34-generic 4.15.0-34.37 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-extra-4.15.0-34-generic 4.15.0-34.37 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP nbd exists for the generic kernel, but not kvm. root@ubuntu:~# find /lib/modules -name '*nbd*' /lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko root@ubuntu:~# dpkg-query -S /lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko linux-modules-4.15.0-34-generic: /lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko In fact, there are many more modules in the generic kernel: root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-1021-kvm | wc -l 514 root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-34-generic | wc -l 1285 I checked if there is a linux-modules-extra for kvm and this kernel version, but there is not - o
[Kernel-packages] [Bug 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image
To be clear, this should have been "it works in rc4". I didn't have time to test in which version the fix was 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/1791372 Title: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image Status in acpid package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Repro: 1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully updated -> Keyboard backlight should come on or change but doesn't. The gnome-shell pop-up icon for the keyboard backlight appears for both keys, but the icon's "progress" bar is not visible. Kernel version is linux-image-4.17.0-9-generic This is the same in X and Wayland session. In case it matters, Nvidia binary drivers are installed but Nvidia is switched off via Prime setting in nvidia-settings. Running with Intel drivers The keyboard backlight works perfectly when booting from the 18.04.1 desktop live image. When turning on light with 18.04.1, it is off again after rebooting into 18.10. (However 18.04.1 seems to freeze when shutting down from menu, I have to hard-shut it off). Most other important Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound) except for the airplane mode key. However the airplane mode key only fails in gnome-shell but works on the console (this is filed as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367) (Not working are a key that seems to mean "display off" and another of unclear purpose that never worked on any laptop I ever saw, maybe "presentation mode" as it seems to depict a flip chart or projection screen). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: angela16196 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 22:08:12 2018 InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD 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/acpid/+bug/1791372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
Looks like it got solved at least for me on recent Ubuntu 18.10 with the official kernel. Looks like now hotplugging Dell TB16 dock works fine on Precision 5520. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw&sh=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dm
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I do not know Linux kernel process, but i would like to know if and when this fix will appear by defautl into Ubuntu doing a sudo apt upgrade ? Thanks and sorry for such basic question. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 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 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Yes, it still need "ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2" -- 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: New 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 1793960] 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/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793960] [NEW] Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
Public bug reported: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic elan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Robert, There are some patches pending upstream to fix the "incomplete report" errors in the mean time these can be safely ignored. As for you needing to do a 2-finger-click to get a right click, that means that libinput is configured for clickfinger behavior rather then click areas. To change this run gnome-tweaks and go to: "Keyboard & Mouse" then under "Mouse Click Emulation" select "Area" that should give you a right click at the bottom right area of the touchpad. Regards, Hans -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags added: patch -- You 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 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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I installed the packages from -proposed as per the instructions and had two issues: 1. Steam fails to launch with NVIDIA due to a "glXChooseVisual failed" error, which some cursory Googling suggests is due to a lack of 32-bit libraries—perhaps this is expected. 2. After switching from NVIDIA to Intel and logging out, the first attempt to log in again would seem to fail and just return me to the login screen. A second attempt would then succeed and take me to the desktop. This didn't happen when switching in the other direction. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage
@lou (louvee) I did try to ask on the kernel mail list (here https://lkml.org/lkml/2018/9/10/296 ), but got no replies, however the good news is, for me anyway, that I'm still successfully using my own kernel(4.18.9) patch(le9d.patch) , in Qubes OS (both in dom0 and VM kernels). Here's a copy of it, if you want to give it a test. ** Patch added: "le9d.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+attachment/5191960/+files/le9d.patch -- You 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 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 1752772] Re: r8169 ethernet card don't work after returning from suspension
I can confirm that the fix from DiegoRivera #102 is also functional. Look here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/102 The issue with the r8169 driver exists on other distributions ans kernel versions also. I use Debian with kernel 4.16.0-2-amd64 18:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Subsystem: Micro-Star International Co., Ltd. [MSI] RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Flags: bus master, fast devsel, latency 0, IRQ 73 I/O ports at f000 [size=256] Memory at f7604000 (64-bit, non-prefetchable) [size=4K] Memory at f760 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] L1 PM Substates Kernel driver in use: r8169 Kernel modules: r8169 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By
[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage
Update: I'd commented in detail about this bug (post 77,78). I run the live versions of Linux on a 4GB Core-i5 laptop (and another 4GB pentium laptop also.) Just wanted to add: I've added 4Gb of RAM to the Core-i5 laptop for 8Gb total now. This helps a lot, but it's not a cure. With Fedora 28, the system will still cease up with maybe 2 dozen (or less depending on what's happening (video, etc) ) FF tabs opened/active. I came back here to note that, I'm currently using a Live Debian Stretch (9.5). There are obviously significant differences in the way these variants of Linux manage memory. Why? Because under the same system conditions (Gnome, same s/w programs installed and/or running), I can open WAY more tabs in FF on Debian; open more simultaneous programs, without fear of a sudden system heart- attack. In fact, it is much harder for me to cause the system freeze in Debian, even with approaching 50 tabs opened in FF developer 63... I understand there are underlying Fedora vs Debian system differences like: systemd vs init, and Wayland vs Xorg, Gnome versions (3.28.1 vs 3.22.5) and kernel revisions (4.16.3-301.fc28.x86_64 vs 4.9.110-1 (2018-07-05) ), but in all, I find Debian WA more forgiving, and more manageable, ESPECIALLY in light of this FATAL flaw, AND the known Gnome memory leak bug which can easily be remediated for in Debian by restarting Gnome (via Alt-F2, r) to free back up that memory. (The only way to accomplish this in Fedora is to actually log out of your session because of Wayland limitations.) Anyway, I jut thought it's another data point to add to the mystery. I still have to keep resource monitor opened even in Stretch, just in case, but I only crashed Stretch once over the past 3 months or so when I was in the 80's (mem % used) and let a video play for 2 hrs without checking up. Normally anyway, that percentage isn't rising above the 70's in my typical "working" environment. Finally, I'd like to mention to those asking for logs, etc., for this issue, realize that WHEN this issue occurs, it *is* essentially a heart- attack for the system. There is no recourse, and no way to gather logs. EVERYTHING ceases up- usually never to come back. A hard power-cycle is the only recourse, and NO logs which would shed light on the issue are written. EVERYTHING stops- including log writing. This is the reality. I *do* have a few logs from and old (non-live) Jesse 8.7.1 install-- for a few times when, the system did revive, after hours-- and there's nothing in there that would shed light on the issue. The (very) few (interesting/odd) entries in the log that I've researched pointed to no other instances/causes of this same issue. It would be nice after 11 or 12 years of this issue, if someone higher up and more knowledgeable in the development "food chain" would would simply replicate the issue, it's not really that hard to do so at all. It honestly is a show-stopper. Ciao. -- You 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 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 1793934] Re: Black Screen After A Few Minutes
** Description changed: Edit 1: - added "installing mainline linux kernel v4.3.6-wily/" to things I tried I first encountered the issue on Kubuntu 18.04 when I removed my 2nd monitor, the screen went black after 5-30 seconds. I tried: - disconnecting the 1st instead of the 2nd monitor - using Ubuntu 18.04 (not Kubuntu) - using Wayland - installing the latest mainline linux kernel 4.19rc4 - installing mainline linux kernel v4.3.6-wily/ The only things that worked so far are: - Having both Monitors connected - nomodeset or recovery mode - using Ubuntu Gnome 16.04 - login via tty/terminal When the PC was turned off for a while, I have to wait for a few minutes or start lots of applications for the black screen to occur. If the PC was restarted several times due to this bug, a blank screen may occur as soon as I see the login screen. The issue also occurs during installation when autodetecting the keyboard type or after selecting the installation type (Minimal Installation or Normal Installation etc.) My Hardware: - ASRock H87 Pro4 - Intel i5-4570 - AMD Radeon R9 390 - 1st Monitor connected via DisplayPort to HDMI adapter cable (or DVI-D) - 2nd Monitor connected via DVI-D cable - - Windows 10 is installed on a separate SSD + - Windows 10 is installed on a separate SSD and is working just fine (Although Windows 10 is doing some kind of boot repair when switching from Ubuntu to Windows) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2031 F pulseaudio /dev/snd/controlC1: ubuntu 2031 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 23 06:03:27 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- nomodeset keyboard-configuration/layoutcode=de RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H87 Pro4 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.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4: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: To Be Filled By O.E.M. ** Description changed: Edit 1: - added "installing mainline linux kernel v4.3.6-wily/" to things I tried - I first encountered the issue on Kubuntu 18.04 when I removed my 2nd monitor, the screen went black after 5-30 seconds. I tried: + I first encountered the issue on Kubuntu 18.04 when I removed my 2nd monitor, the screen went black after 5-30 seconds, forcing me to shutdown the PC by pressing the power button. I tried the following to resolve the black screen issue: - disconnecting the 1st instead of the 2nd monitor - using Ubuntu 18.04 (not Kubuntu) - using Wayland - installing the latest mainline linux kernel 4.19rc4 - installing mainline linux kernel v4.3.6-wily/ The only things that worked so far are: - Having both Monitors connected - nomodeset or recovery mode - using Ubuntu Gnome 16.04 - login via tty/terminal When the PC was turned off for a while, I have to wait for a few minutes or start lots of applications for the black screen to occur. If the PC was restarted several times due to this bug, a blank screen may occur as soon as I see the login screen. The issue also occurs during installation when autodetecting the keyboard type or after selecting the installation type (Minimal Installation or Normal Installation etc.) My Hardware: - ASRock H87 Pro4 - Intel i5-4570 - AMD Radeon R9 390 - 1st Monitor connected via DisplayPort to HDMI adapter cable (or DVI-D) - 2nd Monitor connected via DVI-D cable - Windows 10 is installed on a separate SS
[Kernel-packages] [Bug 1793934] Re: Black Screen After A Few Minutes
** Description changed: Edit 1: - added "installing mainline linux kernel v4.3.6-wily/" to things I tried - I first encountered the issue on Kubuntu 18.04 when I removed my 2nd monitor, the screen went black after 5-30 seconds. I tried: - disconnecting the 1st instead of the 2nd monitor - using Ubuntu 18.04 (not Kubuntu) - using Wayland - installing the latest mainline linux kernel 4.19rc4 - installing mainline linux kernel v4.3.6-wily/ The only things that worked so far are: - Having both Monitors connected - nomodeset or recovery mode - using Ubuntu Gnome 16.04 - login via tty/terminal When the PC was turned off for a while, I have to wait for a few minutes or start lots of applications for the black screen to occur. If the PC was restarted several times due to this bug, a blank screen may occur as soon as I see the login screen. The issue also occurs during installation when autodetecting the keyboard type or after selecting the installation type (Minimal Installation or Normal Installation etc.) My Hardware: - ASRock H87 Pro4 - Intel i5-4570 - AMD Radeon R9 390 - 1st Monitor connected via DisplayPort to HDMI adapter cable (or DVI-D) - 2nd Monitor connected via DVI-D cable + - Windows 10 is installed on a separate SSD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2031 F pulseaudio /dev/snd/controlC1: ubuntu 2031 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 23 06:03:27 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- nomodeset keyboard-configuration/layoutcode=de RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H87 Pro4 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.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4: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: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793934 Title: Black Screen After A Few Minutes Status in linux package in Ubuntu: Confirmed Bug description: Edit 1: - added "installing mainline linux kernel v4.3.6-wily/" to things I tried I first encountered the issue on Kubuntu 18.04 when I removed my 2nd monitor, the screen went black after 5-30 seconds. I tried: - disconnecting the 1st instead of the 2nd monitor - using Ubuntu 18.04 (not Kubuntu) - using Wayland - installing the latest mainline linux kernel 4.19rc4 - installing mainline linux kernel v4.3.6-wily/ The only things that worked so far are: - Having both Monitors connected - nomodeset or recovery mode - using Ubuntu Gnome 16.04 - login via tty/terminal When the PC was turned off for a while, I have to wait for a few minutes or start lots of applications for the black screen to occur. If the PC was restarted several times due to this bug, a blank screen may occur as soon as I see the login screen. The issue also occurs during installation when autodetecting the keyboard type or after selecting the installation type (Minimal Installation or Normal Installation etc.) My Hardware: - ASRock H87 Pro4 - Intel i5-4570 - AMD Radeon R9 390 - 1st Monitor connected via DisplayPort to HDMI adapter cable (or DVI-D) - 2nd Monitor connected via DVI-D cable - Windows 10 is installed on a separate SSD and is working just fine (Although Windows 10 is doing some kind of boot repair when switching from Ubuntu to Windows) ProblemType: Bug DistroRelease: Ubuntu
[Kernel-packages] [Bug 1793934] Re: Black Screen After A Few Minutes
** Description changed: + Edit 1: + - added "installing mainline linux kernel v4.3.6-wily/" to things I tried + + I first encountered the issue on Kubuntu 18.04 when I removed my 2nd monitor, the screen went black after 5-30 seconds. I tried: - disconnecting the 1st instead of the 2nd monitor - using Ubuntu 18.04 (not Kubuntu) - using Wayland - installing the latest mainline linux kernel 4.19rc4 + - installing mainline linux kernel v4.3.6-wily/ The only things that worked so far are: - Having both Monitors connected - nomodeset or recovery mode - using Ubuntu Gnome 16.04 - - loggin via tty/terminal + - login via tty/terminal When the PC was turned off for a while, I have to wait for a few minutes or start lots of applications for the black screen to occur. If the PC was restarted several times due to this bug, a blank screen may occur as soon as I see the login screen. The issue also occurs during installation when autodetecting the keyboard type or after selecting the installation type (Minimal Installation or Normal Installation etc.) My Hardware: - ASRock H87 Pro4 - Intel i5-4570 - AMD Radeon R9 390 - 1st Monitor connected via DisplayPort to HDMI adapter cable (or DVI-D) - 2nd Monitor connected via DVI-D cable - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2031 F pulseaudio /dev/snd/controlC1: ubuntu 2031 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 23 06:03:27 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- nomodeset keyboard-configuration/layoutcode=de RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H87 Pro4 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.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4: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: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793934 Title: Black Screen After A Few Minutes Status in linux package in Ubuntu: Confirmed Bug description: Edit 1: - added "installing mainline linux kernel v4.3.6-wily/" to things I tried I first encountered the issue on Kubuntu 18.04 when I removed my 2nd monitor, the screen went black after 5-30 seconds. I tried: - disconnecting the 1st instead of the 2nd monitor - using Ubuntu 18.04 (not Kubuntu) - using Wayland - installing the latest mainline linux kernel 4.19rc4 - installing mainline linux kernel v4.3.6-wily/ The only things that worked so far are: - Having both Monitors connected - nomodeset or recovery mode - using Ubuntu Gnome 16.04 - login via tty/terminal When the PC was turned off for a while, I have to wait for a few minutes or start lots of applications for the black screen to occur. If the PC was restarted several times due to this bug, a blank screen may occur as soon as I see the login screen. The issue also occurs during installation when autodetecting the keyboard type or after selecting the installation type (Minimal Installation or Normal Installation etc.) My Hardware: - ASRock H87 Pro4 - Intel i5-4570 - AMD Radeon R9 390 - 1st Monitor connected via DisplayPort to HDMI adapter cable (or DVI-D) - 2nd Monitor connected via DVI-D cable - Windows 10 is installed on a separate SSD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux
[Kernel-packages] [Bug 1793934] 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/1793934 Title: Black Screen After A Few Minutes Status in linux package in Ubuntu: Confirmed Bug description: I first encountered the issue on Kubuntu 18.04 when I removed my 2nd monitor, the screen went black after 5-30 seconds. I tried: - disconnecting the 1st instead of the 2nd monitor - using Ubuntu 18.04 (not Kubuntu) - using Wayland - installing the latest mainline linux kernel 4.19rc4 The only things that worked so far are: - Having both Monitors connected - nomodeset or recovery mode - using Ubuntu Gnome 16.04 - loggin via tty/terminal When the PC was turned off for a while, I have to wait for a few minutes or start lots of applications for the black screen to occur. If the PC was restarted several times due to this bug, a blank screen may occur as soon as I see the login screen. The issue also occurs during installation when autodetecting the keyboard type or after selecting the installation type (Minimal Installation or Normal Installation etc.) My Hardware: - ASRock H87 Pro4 - Intel i5-4570 - AMD Radeon R9 390 - 1st Monitor connected via DisplayPort to HDMI adapter cable (or DVI-D) - 2nd Monitor connected via DVI-D cable ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2031 F pulseaudio /dev/snd/controlC1: ubuntu 2031 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 23 06:03:27 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- nomodeset keyboard-configuration/layoutcode=de RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H87 Pro4 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.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
