[Kernel-packages] [Bug 1990272] Re: PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0], AER UnsupReq
I am experiencing the same issue on a Thinkpad P1 Gen6. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990272 Title: PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0],AER UnsupReq Status in linux package in Ubuntu: Confirmed Bug description: My dmesg is getting spammed by these AER errors. The laptop (Lenovo X1 Extreme Gen 5, Intel Core i7-12700H) is otherwise working fine. The errors come in random waves of 60..160 back-to-back errors with an interval of 130..140 microseconds. Device [8086:51b0] is the PCI/thunderbolt bridge. [ 20.086628] pcieport :00:1d.0: AER: Uncorrected (Non-Fatal) error received: :00:1d.0 [ 20.086671] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ 20.086680] pcieport :00:1d.0: device [8086:51b0] error status/mask=0010/4000 [ 20.086688] pcieport :00:1d.0:[20] UnsupReq (First) [ 20.086694] pcieport :00:1d.0: AER: TLP Header: 3400 2052 [ 20.086810] thunderbolt :22:00.0: AER: can't recover (no error_detected callback) [ 20.086846] xhci_hcd :56:00.0: AER: can't recover (no error_detected callback) [ 20.086878] pcieport :00:1d.0: AER: device recovery failed [ 20.106033] pcieport :00:1d.0: AER: Multiple Uncorrected (Non-Fatal) error received: :00:1d.0 [ 20.106082] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ 20.106093] pcieport :00:1d.0: device [8086:51b0] error status/mask=0010/4000 [ 20.106101] pcieport :00:1d.0:[20] UnsupReq (First) [ 20.106108] pcieport :00:1d.0: AER: TLP Header: 3400 2052 [ 20.106219] thunderbolt :22:00.0: AER: can't recover (no error_detected callback) [ 20.106257] xhci_hcd :56:00.0: AER: can't recover (no error_detected callback) [ 20.106301] pcieport :00:1d.0: AER: device recovery failed Another wave was at 418s, 440s, 1168s, etc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: me 1827 F pulseaudio /dev/snd/controlC0: me 1827 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Sep 20 13:34:43 2022 InstallationDate: Installed on 2022-08-31 (19 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21DE001QMH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2022 dmi.bios.release: 1.8 dmi.bios.vendor: LENOVO dmi.bios.version: N3JET24W (1.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 21DE001QMH dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrN3JET24W(1.08):bd07/21/2022:br1.8:efr1.5:svnLENOVO:pn21DE001QMH:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001QMH:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5: dmi.product.family: ThinkPad X1 Extreme Gen 5 dmi.product.name: 21DE001QMH dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5 dmi.product.version: ThinkPad X1 Extreme Gen 5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990272/+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 2052411] Re: thunderbolt: interrupt for TX ring 0 is already enabled
linux-image-6.5.0-14-generic does not display this behaviour so this is clearly a regression. -- 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/2052411 Title: thunderbolt: interrupt for TX ring 0 is already enabled Status in linux-signed package in Ubuntu: New Bug description: After upgrading to linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1 I lost use of an HID device via thunderbolt (still working via USB). This coincided with the following dmesg trace. [26360.900981] [ cut here ] [26360.900984] thunderbolt :22:00.0: interrupt for TX ring 0 is already enabled [26360.901065] WARNING: CPU: 19 PID: 263006 at drivers/thunderbolt/nhi.c:146 ring_interrupt_active+0x270/0x350 [thunderbolt] [26360.901108] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xfrm_user xfrm_algo xt_addrtype br_netfilter ccm xt_CHECKSUM xt_MASQUERADE xt_conntrack snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_sof_probes snd_soc_hdac_hdmi cmac udp_diag ipt_REJECT nf_reject_ipv4 algif_hash snd_hda_codec_realtek nf_conntrack_netlink xt_tcpudp nft_ct snd_hda_codec_generic algif_skcipher nvidia_uvm(PO) nft_compat nft_masq nft_queue af_alg nft_chain_nat nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_tables nf_conntrack nfnetlink_queue nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge stp llc nfnetlink tcp_diag inet_diag overlay bnep snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof intel_uncore_ frequency intel_uncore_frequency_common [26360.901169] intel_tcc_cooling snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core x86_pkg_temp_thermal intel_powerclamp snd_soc_acpi_intel_match coretemp snd_soc_acpi soundwire_generic_allocation soundwire_bus nvidia_drm(PO) iwlmvm kvm_intel snd_soc_core snd_compress nvidia_modeset(PO) i915 snd_hda_codec_hdmi ac97_bus mac80211 snd_pcm_dmaengine kvm btusb crct10dif_pclmul polyval_clmulni btrtl polyval_generic uvcvideo ghash_clmulni_intel drm_buddy btbcm aesni_intel snd_hda_intel videobuf2_vmalloc hid_sensor_als btintel snd_hda_scodec_cs35l41_spi uvc ttm snd_intel_dspcfg crypto_simd btmtk videobuf2_memops mei_hdcp mei_pxp intel_rapl_msr libarc4 snd_intel_sdw_acpi cryptd videobuf2_v4l2 nvidia(PO) binfmt_misc irqbypass snd_usb_audio hid_sensor_trigger bluetooth iwlwifi snd_hda_codec thinkpad_acpi industrialio_triggered_buffer videodev drm_display_helper spi_nor kfifo_buf snd_usbmidi_lib snd_seq_midi snd_hda_core videobuf2_common rapl hid_sensor_iio_common snd_ump hid_magicmouse think_l mi snd_hda_scodec_cs35l41_i2c [26360.901228] snd_seq_midi_event ecdh_generic intel_cstate nls_iso8859_1 serio_raw cec snd_hda_scodec_cs35l41 processor_thermal_device_pci industrialio firmware_attributes_class wmi_bmof input_leds joydev apple_mfi_fastcharge mc snd_rawmidi mtd nvram ecc snd_hwdep rc_core mei_me processor_thermal_device snd_hda_cs_dsp_ctls cfg80211 snd_pcm snd_seq cs_dsp hid_multitouch processor_thermal_rfim mei snd_soc_cs35l41_lib processor_thermal_mbox drm_kms_helper snd_seq_device processor_thermal_rapl i2c_algo_bit snd_timer intel_rapl_common mac_hid snd soundcore serial_multi_instantiate ledtrig_audio int3403_thermal platform_profile int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel msr parport_pc ppdev drm lp parport efi_pstore ip_tables x_tables autofs4 hid_sensor_hub cdc_ncm cdc_ether usbnet r8152 mii usbhid hid_generic rtsx_pci_sdmmc i2c_i801 nvme spi_intel_pci crc32_pclmul psmouse thunderbolt i2c_smbus spi_intel nvme_core ucsi_acpi intel_lpss_pci rtsx_ pci typec_ucsi intel_lpss xhci_pci [26360.901294] nvme_common idma64 xhci_pci_renesas i2c_hid_acpi typec i2c_hid hid video pinctrl_tigerlake wmi [26360.901305] CPU: 19 PID: 263006 Comm: kworker/19:2 Tainted: P OE 6.5.0-15-generic #15~22.04.1-Ubuntu [26360.901309] Hardware name: LENOVO 21FV003CAU/21FV003CAU, BIOS N3ZET21W (1.08 ) 07/07/2023 [26360.901311] Workqueue: pm pm_runtime_work [26360.901317] RIP: 0010:ring_interrupt_active+0x270/0x350 [thunderbolt] [26360.901348] Code: 89 5d c8 44 89 45 d4 e8 8e da 38 cc 44 8b 45 d4 48 8b 4d c0 49 89 d9 48 8b 55 b8 48 89 c6 48 c7 c7 78 70 5e c0 e8 50 7e 97 cb <0f> 0b 4d 8b 7f 08 44 8b 5d c8 49 8b 77 18 45 84 ed 0f 85 d9 fe ff [26360.901351] RSP: 0018:b091a6213c48 EFLAGS: 00010046 [26360.901354] RAX: RBX: c05eb6db RCX: [26360.901357] RDX: RSI: RDI: [26360.901358] RBP: b091a6213c98 R08: R09: [26360.9
[Kernel-packages] [Bug 2052411] [NEW] thunderbolt: interrupt for TX ring 0 is already enabled
Public bug reported: After upgrading to linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1 I lost use of an HID device via thunderbolt (still working via USB). This coincided with the following dmesg trace. [26360.900981] [ cut here ] [26360.900984] thunderbolt :22:00.0: interrupt for TX ring 0 is already enabled [26360.901065] WARNING: CPU: 19 PID: 263006 at drivers/thunderbolt/nhi.c:146 ring_interrupt_active+0x270/0x350 [thunderbolt] [26360.901108] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xfrm_user xfrm_algo xt_addrtype br_netfilter ccm xt_CHECKSUM xt_MASQUERADE xt_conntrack snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_sof_probes snd_soc_hdac_hdmi cmac udp_diag ipt_REJECT nf_reject_ipv4 algif_hash snd_hda_codec_realtek nf_conntrack_netlink xt_tcpudp nft_ct snd_hda_codec_generic algif_skcipher nvidia_uvm(PO) nft_compat nft_masq nft_queue af_alg nft_chain_nat nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_tables nf_conntrack nfnetlink_queue nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge stp llc nfnetlink tcp_diag inet_diag overlay bnep snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof intel_uncore_fr equency intel_uncore_frequency_common [26360.901169] intel_tcc_cooling snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core x86_pkg_temp_thermal intel_powerclamp snd_soc_acpi_intel_match coretemp snd_soc_acpi soundwire_generic_allocation soundwire_bus nvidia_drm(PO) iwlmvm kvm_intel snd_soc_core snd_compress nvidia_modeset(PO) i915 snd_hda_codec_hdmi ac97_bus mac80211 snd_pcm_dmaengine kvm btusb crct10dif_pclmul polyval_clmulni btrtl polyval_generic uvcvideo ghash_clmulni_intel drm_buddy btbcm aesni_intel snd_hda_intel videobuf2_vmalloc hid_sensor_als btintel snd_hda_scodec_cs35l41_spi uvc ttm snd_intel_dspcfg crypto_simd btmtk videobuf2_memops mei_hdcp mei_pxp intel_rapl_msr libarc4 snd_intel_sdw_acpi cryptd videobuf2_v4l2 nvidia(PO) binfmt_misc irqbypass snd_usb_audio hid_sensor_trigger bluetooth iwlwifi snd_hda_codec thinkpad_acpi industrialio_triggered_buffer videodev drm_display_helper spi_nor kfifo_buf snd_usbmidi_lib snd_seq_midi snd_hda_core videobuf2_common rapl hid_sensor_iio_common snd_ump hid_magicmouse think_lmi snd_hda_scodec_cs35l41_i2c [26360.901228] snd_seq_midi_event ecdh_generic intel_cstate nls_iso8859_1 serio_raw cec snd_hda_scodec_cs35l41 processor_thermal_device_pci industrialio firmware_attributes_class wmi_bmof input_leds joydev apple_mfi_fastcharge mc snd_rawmidi mtd nvram ecc snd_hwdep rc_core mei_me processor_thermal_device snd_hda_cs_dsp_ctls cfg80211 snd_pcm snd_seq cs_dsp hid_multitouch processor_thermal_rfim mei snd_soc_cs35l41_lib processor_thermal_mbox drm_kms_helper snd_seq_device processor_thermal_rapl i2c_algo_bit snd_timer intel_rapl_common mac_hid snd soundcore serial_multi_instantiate ledtrig_audio int3403_thermal platform_profile int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel msr parport_pc ppdev drm lp parport efi_pstore ip_tables x_tables autofs4 hid_sensor_hub cdc_ncm cdc_ether usbnet r8152 mii usbhid hid_generic rtsx_pci_sdmmc i2c_i801 nvme spi_intel_pci crc32_pclmul psmouse thunderbolt i2c_smbus spi_intel nvme_core ucsi_acpi intel_lpss_pci rtsx_pc i typec_ucsi intel_lpss xhci_pci [26360.901294] nvme_common idma64 xhci_pci_renesas i2c_hid_acpi typec i2c_hid hid video pinctrl_tigerlake wmi [26360.901305] CPU: 19 PID: 263006 Comm: kworker/19:2 Tainted: P OE 6.5.0-15-generic #15~22.04.1-Ubuntu [26360.901309] Hardware name: LENOVO 21FV003CAU/21FV003CAU, BIOS N3ZET21W (1.08 ) 07/07/2023 [26360.901311] Workqueue: pm pm_runtime_work [26360.901317] RIP: 0010:ring_interrupt_active+0x270/0x350 [thunderbolt] [26360.901348] Code: 89 5d c8 44 89 45 d4 e8 8e da 38 cc 44 8b 45 d4 48 8b 4d c0 49 89 d9 48 8b 55 b8 48 89 c6 48 c7 c7 78 70 5e c0 e8 50 7e 97 cb <0f> 0b 4d 8b 7f 08 44 8b 5d c8 49 8b 77 18 45 84 ed 0f 85 d9 fe ff [26360.901351] RSP: 0018:b091a6213c48 EFLAGS: 00010046 [26360.901354] RAX: RBX: c05eb6db RCX: [26360.901357] RDX: RSI: RDI: [26360.901358] RBP: b091a6213c98 R08: R09: [26360.901360] R10: R11: R12: 0001 [26360.901361] R13: 0001 R14: 00038200 R15: 9763017d0240 [26360.901363] FS: () GS:976a3f6c() knlGS: [26360.901366] CS: 0010 DS: ES: CR0: 80050033 [26360.901368] CR2: 7ffc979f4d00 CR3: 00010fd6 CR4: 00752ee0 [26360.901370] PKRU: 55
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend
Also on 18.04.3 with 5.3.0-26-generic on a clevo p650re. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling and click-and-drag no longer works after resuming from suspend Status in Linux: Confirmed Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK 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:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+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 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Note that I'm not suggesting that it be altered mechanically, but rather than a warning be written that it may not be what is wanted (note also that this issue is not about nouveau drivers but NVidia-provided drivers). If I'd seen a warning like that on doing `ubuntu-drivers autoinstall`, this issue would probably not have been filed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to re
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
As an after thought. This could be mitigated by having the nvidia drivers' postinst check for nomodeset in /etc/defaults/grub and warn if it is present. It is already running grub-update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927) May 22 16:34:52 cube syste
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Yes, sorry. Removing nomodeset allowed boot to desktop and a functional and stable system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927) May 22 16:34:52 cube systemd[1]: Stopped NVIDIA Persistence Daemon. ``` This is a fresh install of 18.04.2 (less than
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Thank you so very much. That has fixed the problem. In the next couple of weeks when I can find some time, I'll look into the other issue that you've been managing and try it with a mainline kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927) May 22 16:34
[Kernel-packages] [Bug 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability
The reason I ask this is that launchpad has an unfortunate approach to issue management (these two that you have been communicating in are a welcome change - thanks) where bugs go stale for years or are dropped due to lack of engagement from maintainers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830029 Title: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability Status in linux package in Ubuntu: Incomplete Bug description: I am trying to use the nouveau drivers on a recent (today) install of 18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at all. What I am finding is that the sluggishness of the display is comparable to the case when nouveau drivers are disabled. The only real difference is in the amount of noise coming from the fan because of a slightly reduced CPU load due to Xorg. I don't even know where to start looking into this intelligently, but I would have expected that the drivers would have gotten to a usable state in the past 2 1/2 years since I last tried them on this machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 22 21:05:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540] NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540] InstallationDate: Installed on 2019-05-22 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:066d Acer, Inc Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65_P67RGRERA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830029/+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 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
re:nomodeset: That's odd unless the drivers on the live usb media are old; nomodeset is definitely needed to not lock up from the live usb on this machine. re:grubmenu: I'm not using UEFI, so AFAIU, shift should be the key (though I tried both). Is it edge triggered? If not, I've had the key held down from the moment the boot process is started at the boot medium option screen of my BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidi
[Kernel-packages] [Bug 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability
Please undo the incomplete. The action that was asked for was performed in the comment #2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830029 Title: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability Status in linux package in Ubuntu: Incomplete Bug description: I am trying to use the nouveau drivers on a recent (today) install of 18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at all. What I am finding is that the sluggishness of the display is comparable to the case when nouveau drivers are disabled. The only real difference is in the amount of noise coming from the fan because of a slightly reduced CPU load due to Xorg. I don't even know where to start looking into this intelligently, but I would have expected that the drivers would have gotten to a usable state in the past 2 1/2 years since I last tried them on this machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 22 21:05:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540] NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540] InstallationDate: Installed on 2019-05-22 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:066d Acer, Inc Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65_P67RGRERA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830029/+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 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
I will give that a go. The nomodeset option was set during istall, presumably because the live usb install media doesn't boot without it. I vaguely recall altering that option at the grub menu, but it was a long day yesterday, so I am not sure (as an aside, why does the grub menu not come up with shift or esc any more - I needed to alter the grub files to make it possible to see the menu at all, which is pretty unfriendly). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file c
[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
Ah, you mean nomodeset. I have tried that now with both 18.04 and 19.04 with success. Both live USBs are stable for at least 10 minutes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
What magic is required to get into safe graphic mode from the Disco live USB? (normal boot on that version fails in the same way) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
** Attachment added: "dmidecode.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262933/+files/dmidecode.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
acpi.tar.bz was not obtainable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
** Attachment added: "lspci output for working 16.04 system on same hardware" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262936/+files/lspci-16.04.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] [NEW] Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
Public bug reported: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
** Attachment added: "/proc/acpi for working 16.04 system on same hardware" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262938/+files/acpi-16.04.tar.bz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
** Attachment added: "dmesg from boot that results in hang" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262939/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
** Attachment added: "uname.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262932/+files/uname.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
** Attachment added: "uname for working 16.04 system on same hardware" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262935/+files/uname-16.04.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
lspci.txt is empty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
** Attachment added: "dmidecode output for working 16.04 system on same hardware" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262937/+files/dmidecode-16.04.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
** Attachment added: "lspci output with acpi=off noapic boot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262934/+files/lspci-acpi%3Doff-noapic.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic Status in linux package in Ubuntu: Confirmed Bug description: Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3 results in a hang shortly after the desktop is presented, unless acpi=off and noapic (or nolapic) are given as kernel boot parameters. The same installer runs without issue on other machines and the 16.04 installer runs without issue on the P650RE3. Without passing acpi=off and noapic, a desktop comes up and a terminal can be obtained, but keystrokes and mouse clicks are not responded to after a small number of seconds. The mouse pointer continues to move with trackpad input. With careful timing I was able to obtain, uname, dmidecode and (an empty) lspci output. I was not able to obtain any /proc/acpi information, but do have dmesg. These are all attached. With acpi=off and noapic, I can get lspci and dmidecode output, but obviously no /proc/acpi. In this case the lspci output is not impty and dmidecode is identical to the failing case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+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
