[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats
I found a $HOME with 10gb space, so finally a virtual machine test
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
host: Fedora 28 x86_64 4.18.14-200
virtual machine Type: Linux Version: Ubuntu (32 bit)
Virtual Box version: 5.2.18 r124319 (Qt5.11.1)
guiverc@hp-vb-8200:~$ screenfetch -n
guiverc@hp-vb-8200
OS: Ubuntu 18.04 bionic
Kernel: i686 Linux 4.18.0-10-generic
Uptime: 1m
Packages: 1614
Shell: bash 4.4.19
Resolution: 1504x798
DE: XFCE
WM: Xfwm4
WM Theme: Greybird
GTK Theme: Greybird [GTK2]
Icon Theme: elementary-xfce-darker
Font: Noto Sans 9
CPU: Intel Core i5-2400 @ 3.093GHz
GPU: llvmpipe (LLVM 6.0, 256 bits)
RAM: 206MiB / 2012MiB
guiverc@hp-vb-8200:~$ apt-cache policy linux-image-4.18.0-10-generic
linux-image-4.18.0-10-generic:
Installed: 4.18.0-10.11
Candidate: 4.18.0-10.11
Version table:
*** 4.18.0-10.11 500
500 http://ppa.launchpad.net/canonical-kernel-team/unstable/ubuntu
cosmic/main i386 Packages
100 /var/lib/dpkg/status
guiverc@hp-vb-8200:~$
YEAH I installed XUBUNTU again sorry. Don't have a brain injury : you
can't hold things in your head, however I got x86 right at least this
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/1794922
Title:
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
" repeats
Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Unknown
Bug description:
-- Background --
Testing the x86 (32bit) ISO image on various machines.
After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 &
hp dx6120), however
-- Issue --
dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.
switching to messages, it's just the following repeating
// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048
of device mask "
// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048
of device mask "
NOTE: I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've
manually typed it; so typo's could have been made.
A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -
---
guiverc: lyorian:
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
seems like it's a usb issue of some kind with 4.18
---
This fits because whilst I do my testing mostly on d610 & t43 (no
issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
issues. My last test was also long enough ago to be on 4.17 kernel.
I'll add `lshw` files for the two failed systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+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 1680421] Re: Computer suspends/sleeps before login
This bug is still present on Ubuntu 18.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680421 Title: Computer suspends/sleeps before login Status in systemd: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: I am not able to login into the system because it sleeps in the boot process. To fix this, I need to edit (in recovery mode) the /etc/systemd/logind.conf to replace the following options: HandleLidSwitch=ignore HandleLidSwitchDocked=ignore This behaviour started in Ubuntu 14.10. Some other users have this issue too: http://askubuntu.com/questions/829998/ubuntu-16-04-usually-suspends-before-login-and-while-logout ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic i686 ApportVersion: 2.20.4-0ubuntu3 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 6 08:25:20 2017 InstallationDate: Installed on 2017-04-06 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta i386 (20170405) MachineType: Positivo Positivo Mobile PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic root=UUID=f7649356-2952-4c27-9279-c3ab658730ad ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2006 dmi.bios.vendor: Phoenix dmi.bios.version: 4.06CJ15 dmi.board.name: M5X0V dmi.board.vendor: CLEVO Co. dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd06/08/2006:svnPositivo:pnPositivoMobile:pvrVT6198:rvnCLEVOCo.:rnM5X0V:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Positivo Mobile dmi.product.version: VT6198 dmi.sys.vendor: Positivo mtime.conffile..etc.systemd.logind.conf: 2017-04-06T08:15:16.198796 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1680421/+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 1786192] Re: kernel trace
[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/1786192 Title: kernel trace Status in linux package in Ubuntu: Expired Bug description: [ 157.511000] [ cut here ] [ 157.511004] vblank wait timed out on crtc 1 [ 157.511092] WARNING: CPU: 0 PID: 1149 at /build/linux-WHbi0x/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x1a1/0x1b0 [drm] [ 157.511094] Modules linked in: option usb_wwan usbserial huawei_cdc_ncm cdc_wdm cdc_ncm usbnet mii ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 snd_hda_codec_hdmi xt_hl snd_hda_codec_realtek ip6t_rt snd_hda_codec_generic snd_hda_intel nf_conntrack_ipv6 nf_defrag_ipv6 snd_hda_codec ipt_REJECT snd_hda_core nf_reject_ipv4 snd_hwdep nf_log_ipv4 snd_pcm nf_log_common xt_LOG snd_seq_midi snd_seq_midi_event snd_rawmidi arc4 pcmcia coretemp xt_limit iwl4965 joydev xt_tcpudp iwlegacy snd_seq acer_wmi snd_seq_device input_leds serio_raw wmi_bmof yenta_socket sparse_keymap pcmcia_rsrc mac80211 tifm_7xx1 xt_addrtype snd_timer pcmcia_core tifm_core snd lpc_ich cfg80211 soundcore shpchp nsc_ircc(CE) irda(CE) nf_conntrack_ipv4 nf_defrag_ipv4 mac_hid xt_conntrack ip6table_filter sch_fq_codel ip6_tables nf_conntrack_netbios_ns [ 157.511145] nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack libcrc32c iptable_filter parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt firewire_ohci fb_sys_fops tg3 ahci sdhci_pci firewire_core psmouse drm libahci sdhci ptp pata_acpi crc_itu_t pps_core wmi video uas usb_storage [ 157.511176] CPU: 0 PID: 1149 Comm: gnome-shell Tainted: GWC E 4.15.0-30-generic #32-Ubuntu [ 157.511181] Hardware name: AcerTravelMate 5320 /Columbia , BIOS V1.22 10/22/2007 [ 157.511200] EIP: drm_wait_one_vblank+0x1a1/0x1b0 [drm] [ 157.511202] EFLAGS: 00010292 CPU: 0 [ 157.511204] EAX: 001f EBX: f4e2c000 ECX: f63e9630 EDX: 0007 [ 157.511205] ESI: 0001 EDI: EBP: f0713b74 ESP: f0713b3c [ 157.511207] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 157.511209] CR0: 80050033 CR2: b5a91a90 CR3: 30655f00 CR4: 06f0 [ 157.511211] Call Trace: [ 157.511222] ? wait_woken+0x70/0x70 [ 157.511277] intel_get_load_detect_pipe+0x5eb/0x650 [i915] [ 157.511318] intel_tv_detect+0x113/0x4b0 [i915] [ 157.511360] ? intel_tv_get_modes+0x1f0/0x1f0 [i915] [ 157.511376] drm_helper_probe_detect+0x45/0x80 [drm_kms_helper] [ 157.511386] drm_helper_probe_single_connector_modes+0xbc/0x640 [drm_kms_helper] [ 157.511397] ? drm_helper_probe_detect+0x80/0x80 [drm_kms_helper] [ 157.511417] drm_mode_getconnector+0x11e/0x2c0 [drm] [ 157.511438] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [ 157.511454] drm_ioctl_kernel+0x56/0xb0 [drm] [ 157.511471] drm_ioctl+0x2c4/0x370 [drm] [ 157.511490] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [ 157.511497] ? kmap_atomic_prot+0xe0/0x100 [ 157.511500] ? __kunmap_atomic+0x73/0x90 [ 157.511505] ? handle_mm_fault+0xc35/0xe80 [ 157.511522] ? drm_version+0x80/0x80 [drm] [ 157.511527] do_vfs_ioctl+0x93/0x6b0 [ 157.511532] SyS_ioctl+0x58/0x70 [ 157.511536] do_fast_syscall_32+0x7f/0x1e0 [ 157.511542] entry_SYSENTER_32+0x4e/0x7c [ 157.511545] EIP: 0xb7f60d09 [ 157.511546] EFLAGS: 00200292 CPU: 0 [ 157.511548] EAX: ffda EBX: 000b ECX: c05064a7 EDX: bfe159a8 [ 157.511550] ESI: 0001 EDI: c05064a7 EBP: 000b ESP: bfe15928 [ 157.511552] DS: 007b ES: 007b FS: GS: 0033 SS: 007b [ 157.511553] Code: 00 00 00 e9 e4 fe ff ff e8 bd 48 a2 cc 8b 45 d0 8d 55 dc e8 f2 65 a6 cc 85 ff 0f 85 ee fe ff ff 56 68 48 a2 66 f8 e8 2f 46 a2 cc <0f> 0b 58 5a e9 da fe ff ff 8d b6 00 00 00 00 66 66 66 66 90 55 [ 157.511597] ---[ end trace ecf18bbc5fa1e893 ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: plymouth 0.9.3-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Aug 9 10:31:18 2018 DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1: InstallationDate: Installed on 2015-04-29 (1197 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120426-19:21 MachineType: Acer TravelMate 5320 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=8d92a94a-114e-4010-9
[Kernel-packages] [Bug 1783538] Re: System crashed after running xrandr
[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/1783538 Title: System crashed after running xrandr Status in linux package in Ubuntu: Expired Bug description: Jul 25 13:45:51 naamaG kernel: [310183.206113] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Jul 25 13:45:51 naamaG kernel: [310183.270735] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun Jul 25 13:45:51 naamaG kernel: [310183.279137] [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) Jul 25 13:45:51 naamaG kernel: [310183.279210] [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 8cf8326d45b0, found 8cf8326d4518) Jul 25 13:45:51 naamaG kernel: [310183.279272] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) Jul 25 13:45:51 naamaG kernel: [310183.279329] [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) Jul 25 13:45:51 naamaG kernel: [310183.279382] [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Jul 25 13:45:51 naamaG kernel: [310183.279386] pipe state doesn't match! Jul 25 13:45:51 naamaG kernel: [310183.279442] [ cut here ] Jul 25 13:45:51 naamaG kernel: [310183.279505] WARNING: CPU: 2 PID: 1207 at /build/linux-KPInqg/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12277 intel_atomic_commit_tail+0xddb/0xfb0 [i915] Jul 25 13:45:51 naamaG kernel: [310183.279507] Modules linked in: nfnetlink_queue nfnetlink_log sctp ccm veth xt_nat xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc overlay bnep nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp arc4 coretemp wmi_bmof kvm snd_hda_codec_hdmi irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd snd_hda_codec_realtek glue_helper snd_hda_codec_generic cryptd iwlmvm intel_cstate uvcvideo mac80211 intel_rapl_perf videobuf2_vmalloc snd_seq_midi videobuf2_memops snd_seq_midi_event videobuf2_v4l2 snd_hda_intel videobuf2_core snd_hda_codec snd_rawmidi Jul 25 13:45:51 naamaG kernel: [310183.279581] iwlwifi input_leds joydev rtsx_pci_ms videodev snd_hda_core hci_uart media thinkpad_acpi snd_hwdep serio_raw memstick serdev btusb snd_seq snd_pcm btrtl btqca nvram btbcm cfg80211 snd_seq_device btintel snd_timer bluetooth snd mei_me mei shpchp intel_pch_thermal wmi ecdh_generic soundcore intel_lpss_acpi intel_lpss mac_hid tpm_crb acpi_pad parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect rtsx_pci_sdmmc sysimgblt e1000e fb_sys_fops psmouse drm ptp nvme pps_core nvme_core rtsx_pci i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel Jul 25 13:45:51 naamaG kernel: [310183.279663] CPU: 2 PID: 1207 Comm: Xorg Not tainted 4.13.0-46-generic #51-Ubuntu Jul 25 13:45:51 naamaG kernel: [310183.279665] Hardware name: LENOVO 20J60018IV/20J60018IV, BIOS R0FET34W (1.14 ) 06/30/2017 Jul 25 13:45:51 naamaG kernel: [310183.279668] task: 8cf83581 task.stack: 9ecc02c48000 Jul 25 13:45:51 naamaG kernel: [310183.279724] RIP: 0010:intel_atomic_commit_tail+0xddb/0xfb0 [i915] Jul 25 13:45:51 naamaG kernel: [310183.279727] RSP: 0018:9ecc02c4ba90 EFLAGS: 00010286 Jul 25 13:45:51 naamaG kernel: [310183.279731] RAX: 0019 RBX: 8cf8326d0310 RCX: 0006 Jul 25 13:45:51 naamaG kernel: [310183.279733] RDX: RSI: 0082 RDI: 8cf852496570 Jul 25 13:45:51 naamaG kernel: [310183.279735] RBP: 9ecc02c4bb48 R08: 0001 R09: 3b77 Jul 25 13:45:51 naamaG kernel: [310183.279738] R10: 0001 R11: R12: 8cf438d2c000 Jul 25 13:45:51 naamaG kernel: [310183.279740] R13: 8cf833d5 R14: 8cf438d2f000 R15: 8cf8326d0308 Jul 25 13:45:51 naamaG kernel: [310183.279744] FS: 7fb6cf9b4500() GS:8cf85248() knlGS: Jul 25 13:45:51 naamaG kernel: [310183.279746] CS: 0010 DS: ES: CR0: 80050033 Jul 25 13:45:51 naamaG kernel: [310183.279749] CR2: 374f263f6ab8 CR3: 00043a574002 CR4: 003606e0 Jul 25 13:45:51 naamaG kernel: [310183.279751] Call Trace: Jul 25 13:45:51 naamaG kernel: [310183.279761] ? wait_woken+0x80/0x80 Jul 25 13:45:51 naamaG kernel: [310183.
[Kernel-packages] [Bug 1787598] Re: Errors During Startup
[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/1787598 Title: Errors During Startup Status in linux package in Ubuntu: Expired Bug description: Could not find/ resolve named package element- dspkginit-381 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 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1942 F pulseaudio /dev/snd/controlC0: user 1942 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Aug 17 18:51:33 2018 InstallationDate: Installed on 2018-07-30 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 003: ID 0bda:5776 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=d098e794-9e32-435b-9443-206c01202ee6 ro quiet splash 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2212 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.28 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.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787598/+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 1787529] Re: login causes watchdog cpu lockup
[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/1787529 Title: login causes watchdog cpu lockup Status in linux package in Ubuntu: Expired Bug description: Immediately after login watchdog soft-lock cpu (x) occurs. Attempted different desktop environment, reinstalling and reconfiguring lightdm, logging in from shell and updating. Nothing that I've tried has able to get me logged into a desktop environment since I get a CPU lockup before then. Attempting to shutdown from shell also results in unexpected behavior. 'sudo shutdown -a now' results in a black screen and unresponsive keyboard, I'm forced to hardboot. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Aug 17 01:35:44 2018 InstallationDate: Installed on 2018-08-17 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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/1787529/+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 1787743] Re: Slow USB mouse input on linux-lowlatency
[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/1787743 Title: Slow USB mouse input on linux-lowlatency Status in linux package in Ubuntu: Expired Bug description: USB mouse input is very slow and "laggy" onscreen after switching over from the generic 'linux' kernel to 'linux-lowlatency.' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-lowlatency 4.15.0.32.34 ProcVersionSignature: Ubuntu 4.15.0-32.35-lowlatency 4.15.18 Uname: Linux 4.15.0-32-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jeb1710 F pulseaudio /dev/snd/controlC1: jeb1710 F pulseaudio /dev/snd/controlC0: jeb1710 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 12:41:52 2018 InstallationDate: Installed on 2018-08-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: BIOSTAR Group A880G+ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-lowlatency root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-lowlatency N/A linux-backports-modules-4.15.0-32-lowlatency N/A linux-firmware1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A880G+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A880G+ dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787743/+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 1787473] Re: PDFs Don't Print from Document Viewer
[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/1787473 Title: PDFs Don't Print from Document Viewer Status in linux package in Ubuntu: Expired Bug description: After upgrading from Ubuntu 16.04 to 18.04 (via CLI) I'm unable to print PDF documents from the Document Viewer application. When I try to print a PDF from Document Viewer, the PDF stays in the printer queue with status = "Processing". Steps to reproduce: - Open PDF using Document Viewer - press ctrl-P - print dialog opens - choose desired printer, pages-to-print, etc. - click Print Expected: - document prints Actual: - document sits in printer queue with status = "processing" Workaround 1) Open the PDF file using a web browser, and print successfully from the browser. Workaround 2) From Document Viewer, choose "Preview", and from the print-preview click the printer icon to print the preview. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michelle 3174 F pulseaudio /dev/snd/controlC0: michelle 3174 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2f8fccbc-e235-4e8b-9ea2-c30c8b90e7b1 InstallationDate: Installed on 2016-10-18 (666 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. G551JM Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash pcie_aspm=force acpi_os=Windows acpi_backlight=native vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-15 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G551JM.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G551JM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG551JM.204:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnG551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G551JM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787473/+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 1799011] [NEW] package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es d
Public bug reported: congiguration of nvidia-settings failed, then i tried to reinstal nvidia driver but i had problems ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-compute-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Oct 20 17:55:16 2018 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 ErrorMessage: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es distinto de otras instancias del paquetes libnvidia-compute-390:i386 InstallationDate: Installed on 2018-09-16 (34 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es distinto de otras instancias del paquetes libnvidia-compute-390:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1799011 Title: package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es distinto de otras instancias del paquetes libnvidia-compute-390:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: congiguration of nvidia-settings failed, then i tried to reinstal nvidia driver but i had problems ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-compute-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Oct 20 17:55:16 2018 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 ErrorMessage: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es distinto de otras instancias del paquetes libnvidia-compute-390:i386 InstallationDate: Installed on 2018-09-16 (34 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es distinto de otras instancias del paquetes libnvidia-compute-390:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799011/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
I am failing to boot from this new kernel. Downloaded the amd64 build files, 'sudo dpkg -i ' on each of them, but upon trying to boot from the new entries, it stops with "you need to load the kernel first". I really need some help figuring out my mistake here. I did my homework but no solutions yet. First time doing this. -- 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me, although it seems to happen more often when I'm running Xfce (Xubuntu) on a recent kernel (4.17+). Xfce's default image viewer seems to be connected to it, as well. Most of the time I was having multiple instances of it when everything froze. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.typ
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
This is the bug report opened for Arch Linux [TASK FS#59483]: https://bugs.archlinux.org/task/59483?string=freeze&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= The OP reports 4.17.10-1 being the problematic kernel version. What I can say for sure is that this problem did not exist in kernel versions 4.16 and older. Yes, I can try the newest kernel, however these freezes are random and I don't know how to trigger them. I will take some time to experiment with it. -- 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me, although it seems to happen more often when I'm running Xfce (Xubuntu) on a recent kernel (4.17+). Xfce's default image viewer seems to be connected to it, as well. Most of the time I was having multiple instances of it when everything froze. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system
Same problem on Dell Inspiron 7577 with Ubuntu 18.10 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.10 Release:18.10 Codename: cosmic $ uname -a Linux Dell7577Linux 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 27c6:5301 Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 042: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset] Bus 001 Device 041: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 007: ID 0bda:5652 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Would be really nice if I could use the Goodix Fingerprint sensor GF3208 like I use it in Windows 10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: The Goodix GF3208 is not being recognised by the system (Dell Inspiron 15 7577). What's worse is that it isn't even showing the manufacturer vendor id information when doing: $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5301 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note that the vendor id 27c6 should at least say "Shenzhen Huiding Technology Co., Ltd." as per https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings /vendor-prefixes.txt Will/has support been made for the Goodix GF3208 Fingerprint reader/scanner? Thanks in advance, Haz ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 7 04:03:25 2017 InstallationDate: Installed on 2017-10-01 (5 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Bug still present Thinkpad X240 Ubuntu 18.04 – 4.15.0-36 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Systems with acpi-lpss can't do S3/S4 on Bionic. [Test] Users confirmed these patches work for them. [Fix] Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system sleep handling) applies quirks for both runtime and system suspend. This causes problems for some systems, so avoid using quirks on S3 and S4. [Regression Potential] Low. These patches are in upstream stable, and it brings back driver's old behavior. ===Original Bug Report=== I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798979] Re: Hama "Slim" USB 3.0 Multi Card Reader doesn't work
> Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? As said in the description, it started happening after upgrading from Kubuntu 18.04 to 18.10. 18.04 has kernel 4.15. > Would it be possible for you to test the latest upstream kernel? The problem reproduces with kernel 4.19 rc8. The is the dmesg lines that start appearing when the problem happens: [ 136.161611] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 136.161615] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 136.293090] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 166.865743] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 166.865747] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 167.001317] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- 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/1798979 Title: Hama "Slim" USB 3.0 Multi Card Reader doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I have problems with Hama "Slim" USB 3.0 Multi Card Reader (model number 00114837, https://www.hama.com/00114837/hama-slim-usb-30-multi- card-reader-black) attached to a USB 3.0. After attaching the reader (or booting the system) the device works for some time, about a minute or so. It's blue power led is on. Then CPU load goes up to 30-50% and the power led on the reader starts turning off and on with a several seconds interval. It looks like the device is being repeatedly reinitialized. dmesg shows these lines while this is happening: [ 147.251654] xhci_hcd :05:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 147.447251] xhci_hcd :05:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? [ 220.546280] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 220.546283] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 220.685727] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 251.266583] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 251.266584] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 251.398028] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 284.045003] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 284.045006] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 284.180500] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 314.761869] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 314.761873] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 314.893338] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd and so on. No cards are inserted in the device and no user activity on the system, the problem starts happening "on its own". I tried plugging the device in a different USB 3.0 slot, it doesn't help. The device worked on the same system in Kubuntu 18.04, linux kernel 4.15. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-generic 4.18.0.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lastique 3112 F pulseaudio /dev/snd/controlC1: lastique 3112 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 20 19:31:35 2018 InstallationDate: Installed on 2015-05-01 (1267 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductNa
[Kernel-packages] [Bug 1797772] Re: ideapad_laptop disables WiFi/BT radios on Lenovo Y530
It was a clean install of 18.10. The mainline module doesn't have
support for this device as yet. Since the blacklist the user has gone
quite so additional testing is not possible
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797772
Title:
ideapad_laptop disables WiFi/BT radios on Lenovo Y530
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've been working with a user that has a Lenovo Legion Y530-15ICH
where booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios
being disabled by the platform driver "ideapad-laptop".
Unloading or blacklisting the module solves the issue but disables
other platform ACPI interfaces:
$ sudo tee /etc/modprobe.d/ideapad.conf <<< "blacklist ideapad_laptop"
The system has the most recent firmware:
[0.00] DMI: LENOVO 81FV/LNVNB161216, BIOS 8JCN44WW 08/13/2018
The wifi device is:
00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560
[Jefferson Peak] [8086:a370] (rev 10)
Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:0034]
Kernel driver in use: iwlwifi
We investigated the issue extensively and built the module with
additional logic without solving the issue. It is well-known that some
Lenovo models do not have a separate hardware radio kill switch (this
model uses hot-keys Fn + F7 for 'Airplane mode') and need to use a DMI
match to disable the rfkill logic.
We used dmidecode to get the correct Version string:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 81FV
Version: Lenovo Legion Y530-15ICH
Serial Number: PF18CD10
UUID: A44F71C1-5E3D-11E8-9379-8C16458E3F9D
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
Family: Legion Y530-15ICH
and added it to no_hw_rfkill_list[]:
{
.ident = "Lenovo Legion Y530-15ICH",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion Y530-15ICH"),
},
},
However, rfkill was still listing the platform devices "ideapad_wlan"
and "ideapad_bluetooth":
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: ideapad_bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
/sys/class/rfkill/rfkill0/hard=1
/sys/class/rfkill/rfkill0/index=0
/sys/class/rfkill/rfkill0/name=ideapad_wlan
/sys/class/rfkill/rfkill0/persistent=1
/sys/class/rfkill/rfkill0/soft=0
/sys/class/rfkill/rfkill0/state=2
/sys/class/rfkill/rfkill0/type=wlan
/sys/class/rfkill/rfkill0/uevent=RFKILL_NAME=ideapad_wlan RFKILL_TYPE=wlan
RFKILL_STATE=2
/sys/class/rfkill/rfkill1/hard=1
/sys/class/rfkill/rfkill1/index=1
/sys/class/rfkill/rfkill1/name=ideapad_bluetooth
/sys/class/rfkill/rfkill1/persistent=1
/sys/class/rfkill/rfkill1/soft=1
/sys/class/rfkill/rfkill1/state=2
/sys/class/rfkill/rfkill1/type=bluetooth
/sys/class/rfkill/rfkill1/uevent=RFKILL_NAME=ideapad_bluetooth
RFKILL_TYPE=bluetooth RFKILL_STATE=2
/sys/class/rfkill/rfkill3/hard=0
/sys/class/rfkill/rfkill3/index=3
/sys/class/rfkill/rfkill3/name=phy0
/sys/class/rfkill/rfkill3/persistent=0
/sys/class/rfkill/rfkill3/soft=0
/sys/class/rfkill/rfkill3/state=1
/sys/class/rfkill/rfkill3/type=wlan
/sys/class/rfkill/rfkill3/uevent=RFKILL_NAME=phy0 RFKILL_TYPE=wlan
RFKILL_STATE=1
/sys/class/rfkill/rfkill4/hard=0
/sys/class/rfkill/rfkill4/index=4
/sys/class/rfkill/rfkill4/name=hci0
/sys/class/rfkill/rfkill4/persistent=0
/sys/class/rfkill/rfkill4/soft=1
/sys/class/rfkill/rfkill4/state=0
/sys/class/rfkill/rfkill4/type=bluetooth
/sys/class/rfkill/rfkill4/uevent=RFKILL_NAME=hci0 RFKILL_TYPE=bluetooth
RFKILL_STATE=0
We then added printk(KERN_NOTICE ... in the module's
platform_driver.probe function ideapad_acpi_add() both at entry and
later to report the DMI and status of the hardware switch control
flag:
diff -u
/home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
./ideapad-laptop.c
--- /home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
2018-10-14 01:46:49.506088219 +0100
+++ ./ideapad-laptop.c 2018-10-14 06:19:48.843813865 +0100
@@ -1147,6 +1147,13 @@
},
},
{
+ .ident = "Lenovo Legion Y530-15ICH",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion
Y530-15ICH"),
+ },
+ },
+ {
.ident = "Lenovo Legion Y720-15IKB",
.matches = {
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me, although it seems to happen more often when I'm running Xfce (Xubuntu) on a recent kernel (4.17+). Xfce's default image viewer seems to be connected to it, as well. Most of the time I was having multiple instances of it when everything froze. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798979] Re: Hama "Slim" USB 3.0 Multi Card Reader doesn't work
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798979 Title: Hama "Slim" USB 3.0 Multi Card Reader doesn't work Status in linux package in Ubuntu: Incomplete Bug description: I have problems with Hama "Slim" USB 3.0 Multi Card Reader (model number 00114837, https://www.hama.com/00114837/hama-slim-usb-30-multi- card-reader-black) attached to a USB 3.0. After attaching the reader (or booting the system) the device works for some time, about a minute or so. It's blue power led is on. Then CPU load goes up to 30-50% and the power led on the reader starts turning off and on with a several seconds interval. It looks like the device is being repeatedly reinitialized. dmesg shows these lines while this is happening: [ 147.251654] xhci_hcd :05:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 147.447251] xhci_hcd :05:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? [ 220.546280] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 220.546283] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 220.685727] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 251.266583] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 251.266584] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 251.398028] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 284.045003] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 284.045006] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 284.180500] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 314.761869] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 314.761873] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 314.893338] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd and so on. No cards are inserted in the device and no user activity on the system, the problem starts happening "on its own". I tried plugging the device in a different USB 3.0 slot, it doesn't help. The device worked on the same system in Kubuntu 18.04, linux kernel 4.15. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-generic 4.18.0.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lastique 3112 F pulseaudio /dev/snd/controlC1: lastique 3112 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 20 19:31:35 2018 InstallationDate: Installed on 2015-05-01 (1267 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System
[Kernel-packages] [Bug 1798982] [NEW] Kubuntu 18.10 scaling problem
Public bug reported: Hi, I installed Kubuntu 18.10. My notebook has a fullHD display so DPI scaling was needed. I set scaling to 1.2 but the ui of firefox and chromium browsers were still small. Then I set it to 1.3 and chromium looked OK but firefox still had small elements. I think Kubuntu is the best linux desktop in dpiScaling point of view but there could be some improvements for better out of the box experience. All the settings should work fine for/with the desktop's default applications because everybody has a HD display nowadays. Beside that it would be more comfortable if it shouldn't be needed to set the size of the panel and statusbar icons separately (by hacking configs). These things are very important for a good user experience. Thanks. ** Affects: plasma-desktop (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, I installed Kubuntu 18.10. My notebook has a fullHD display so DPI scaling was needed. I set scaling to 1.2 but the ui of firefox and chromium browsers were still small. Then I set it to 1.3 and chromium looked OK but firefox still had small elements. I think Kubuntu is the best linux desktop in dpiScaling point of view but there could be some improvements for better out of the box experience. All the settings should work fine for/with the desktop's default applications because everybody has a HD display nowadays. Beside that it would be more comfortable if it shouldn't be needed to - set the size of the panel and statusbar icons separately. + set the size of the panel and statusbar icons separately (by hacking + configs). These things are very important for a good user experience. Thanks. ** Package changed: linux (Ubuntu) => plasma-desktop (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798982 Title: Kubuntu 18.10 scaling problem Status in plasma-desktop package in Ubuntu: New Bug description: Hi, I installed Kubuntu 18.10. My notebook has a fullHD display so DPI scaling was needed. I set scaling to 1.2 but the ui of firefox and chromium browsers were still small. Then I set it to 1.3 and chromium looked OK but firefox still had small elements. I think Kubuntu is the best linux desktop in dpiScaling point of view but there could be some improvements for better out of the box experience. All the settings should work fine for/with the desktop's default applications because everybody has a HD display nowadays. Beside that it would be more comfortable if it shouldn't be needed to set the size of the panel and statusbar icons separately (by hacking configs). These things are very important for a good user experience. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1798982/+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 1798979] 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/1798979 Title: Hama "Slim" USB 3.0 Multi Card Reader doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I have problems with Hama "Slim" USB 3.0 Multi Card Reader (model number 00114837, https://www.hama.com/00114837/hama-slim-usb-30-multi- card-reader-black) attached to a USB 3.0. After attaching the reader (or booting the system) the device works for some time, about a minute or so. It's blue power led is on. Then CPU load goes up to 30-50% and the power led on the reader starts turning off and on with a several seconds interval. It looks like the device is being repeatedly reinitialized. dmesg shows these lines while this is happening: [ 147.251654] xhci_hcd :05:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 147.447251] xhci_hcd :05:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? [ 220.546280] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 220.546283] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 220.685727] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 251.266583] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 251.266584] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 251.398028] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 284.045003] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 284.045006] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 284.180500] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 314.761869] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 314.761873] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 314.893338] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd and so on. No cards are inserted in the device and no user activity on the system, the problem starts happening "on its own". I tried plugging the device in a different USB 3.0 slot, it doesn't help. The device worked on the same system in Kubuntu 18.04, linux kernel 4.15. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-generic 4.18.0.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lastique 3112 F pulseaudio /dev/snd/controlC1: lastique 3112 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 20 19:31:35 2018 InstallationDate: Installed on 2015-05-01 (1267 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798979/+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 1798979] [NEW] Hama "Slim" USB 3.0 Multi Card Reader doesn't work
Public bug reported: I have problems with Hama "Slim" USB 3.0 Multi Card Reader (model number 00114837, https://www.hama.com/00114837/hama-slim-usb-30-multi-card- reader-black) attached to a USB 3.0. After attaching the reader (or booting the system) the device works for some time, about a minute or so. It's blue power led is on. Then CPU load goes up to 30-50% and the power led on the reader starts turning off and on with a several seconds interval. It looks like the device is being repeatedly reinitialized. dmesg shows these lines while this is happening: [ 147.251654] xhci_hcd :05:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 147.447251] xhci_hcd :05:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? [ 220.546280] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 220.546283] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 220.685727] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 251.266583] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 251.266584] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 251.398028] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 284.045003] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 284.045006] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 284.180500] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 314.761869] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 314.761873] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 314.893338] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd and so on. No cards are inserted in the device and no user activity on the system, the problem starts happening "on its own". I tried plugging the device in a different USB 3.0 slot, it doesn't help. The device worked on the same system in Kubuntu 18.04, linux kernel 4.15. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-generic 4.18.0.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lastique 3112 F pulseaudio /dev/snd/controlC1: lastique 3112 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 20 19:31:35 2018 InstallationDate: Installed on 2015-05-01 (1267 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1798979 Title: Hama "Slim" USB 3.0 Multi Card Reader doesn't work Status in linux package in Ubuntu: New Bug description: I have problems with Hama "Slim" USB 3.0 Multi Card Reader (model number 00114837, https://www.hama.com/00114837/hama-slim-usb-30-multi- card-reader-black) attached to a USB 3.0. After attaching the reader (or booting the system) the device works for some time, about a minute or so. It's blue power led is on. Then CPU load goes up to 30-50% and the power led on the reader starts turning off and on with a several seconds interval. It looks like the device is being repeatedly reinitialized. dmesg shows these lines while this is happening: [ 147.251654] xhci_hcd :05:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 147.447251] xhci_hcd :05:00.0: WARN Event TRB for slot 1 ep 4
[Kernel-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
I have Bluettooth Logitec M535 mouse and have the same problem. It will pair and I can use the mouse. But as soon as I suspend the laptop, or power it off it won't work anymore. I need to go delete the mouse from the list of paired devices, turn off bluetooth, turn it on again and pair again so or it won't connect at all. What solved the problem was this suggestions https://ubuntuforums.org/showthread.php?t=2390542 from ivavis. Following the instructions to add the mouse from the bluez console solved the problem. -- 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/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1798615] Re: suspend does not lock in 18.04
I believe this bug affects security, given that it is a failure of Ubuntu to perform a "Session Lock". E.g. this is from NIST Special Publication 800-53 (Rev. 4): https://nvd.nist.gov/800-53/Rev4/control/AC-11 The information system: a. Prevents further access to the system by initiating a session lock after [Assignment: organization-defined time period] of inactivity or upon receiving a request from a user; and b. Retains the session lock until the user reestablishes access using established identification and authentication procedures. The name has been changed from "Session Lock" to "Device Lock" in Rev 5 (draft, 2017), but it's still listed there for the sake of best practices. -- 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/1798615 Title: suspend does not lock in 18.04 Status in linux package in Ubuntu: Incomplete Bug description: To reproduce from the command-line (this is ubuntu 18.04): % gsettings set org.gnome.desktop.screensaver ubuntu-lock-on-suspend true % gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend true % systemctl suspend Now the monitors go black and report "no signal" (good), and it will stay that way for hours (good) ... but if I tap "shift" key a few times, Ubuntu 18.04 comes back without asking my password. (I expected rather that the system would be locked, i.e. I should see a dialog box that would require a password before anything else!) Same thing if I suspend by using the upper-right-of-screen "power" icon (click-and-hold, then click on the suspend icon). Same thing if I let 20 minutes go by. (A msg comes up ~~ "system will suspend soon...", and it does suspend, but doesn't lock). I have left the ubuntu-lock-on-suspend setting at "true" through several re-boots, but it still doesn't take effect. I get the same behavior whether ubuntu-lock-on-suspend is set to "true" or "false". Other info: % wmctrl -m Name: GNOME Shell Class: N/A PID: N/A Window manager's "showing the desktop" mode: N/A % lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic % uname -a Linux ucbvax 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I just upgraded from 16.04 a couple of weeks ago. I think (90%) it was locking in 16.04, but now not locking in 18.04. If I click on the upper-right-of-screen padlock icon, then the system does lock (password required). While it's locked in that way, I can click on the upper-right-of- screen "suspend" (from drop-down), and then my system is both suspended and locked. But the question is ... How can I make my system lock (automatically) every time a "suspend" happens? (Or even "every time kbd and mouse are idle for 15 minutes"?) Please advise. thanks --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 7633 F pulseaudio /dev/snd/controlC1: ubuntu 7633 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp2s0no wireless extensions. enp7s5no wireless extensions. lono wireless extensions. 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. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity 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 RfKill: Tags: bionic 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: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx 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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A99X
[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Same problem here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'
Again Debian stretch with backports (kernel 4.18) on an Asus B53F with another wireless card and without that broadcom-sta-dkms package. Installing rng-tools solves the problem. Apparently it also affects a Latitude E6410, but does not affect an E4310 and an E5450 (none of them has broadcom-sta-dkms installed). -- 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/1685794 Title: Boot delayed for about 90 seconds until 'random: crng init done' Status in linux package in Ubuntu: Confirmed Status in broadcom-sta package in Debian: Unknown Bug description: Shortened dmesg output, notice the unnaturally long delay before crng init finishes: [8.533630] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [8.542239] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card1/input18 [8.542313] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card1/input19 [8.542382] input: HDA Intel PCH Dock Line Out as /devices/pci:00/:00:1b.0/sound/card1/input20 [8.542449] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card1/input21 [8.544240] cdc_ether 2-6:2.0 usb0: register 'cdc_ether' at usb-:00:14.0-6, CDC Ethernet Device, 02:1e:10:1f:00:00 [8.544271] usbcore: registered new interface driver cdc_ether [8.637660] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [8.654022] input: HP WMI hotkeys as /devices/virtual/input/input22 [8.688226] cdc_ether 2-6:2.0 enp0s20u6c2: renamed from usb0 [8.713288] iwlwifi :02:00.0 wlo1: renamed from wlan0 [9.804308] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input23 [ 98.327857] random: crng init done [ 98.330072] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 98.330073] Bluetooth: BNEP filters: protocol multicast [ 98.330077] Bluetooth: BNEP socket layer initialized [ 98.443281] kauditd_printk_skb: 90 callbacks suppressed [ 98.492927] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 98.681030] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 98.685672] IPv6: ADDRCONF(NETDEV_UP): enp0s20u6c2: link is not ready [ 98.685789] cdc_ether 2-6:2.0 enp0s20u6c2: kevent 12 may have been dropped [ 98.688384] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready [ 98.690915] iwlwifi :02:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Apr 24 14:58:33 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-18 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=9fb9fc1d-15a4-4e98-a2ae-bf572e0900d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: USH452L0B1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+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 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
I also could't see grub or the recover mode to test something from there. -- 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/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] Status in linux package in Ubuntu: Incomplete Bug description: Dell XPS 15 9570 ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2250 F pulseaudio Date: Fri Oct 12 08:54:08 2018 Failure: oops InstallationDate: Installed on 2018-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+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 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
Joseph, do you have any suggestion on how I can I apply the upstream kernel once the system freezes right after the login? Is it possible to apply it from the live USB? -- 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/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] Status in linux package in Ubuntu: Incomplete Bug description: Dell XPS 15 9570 ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2250 F pulseaudio Date: Fri Oct 12 08:54:08 2018 Failure: oops InstallationDate: Installed on 2018-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+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 1798961] 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Confirmed Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me, although it seems to happen more often when I'm running Xfce (Xubuntu) on a recent kernel (4.17+). Xfce's default image viewer seems to be connected to it, as well. Most of the time I was having multiple instances of it when everything froze. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798961] [NEW] Random unrecoverable freezes on Ubuntu 18.10
Public bug reported: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me, although it seems to happen more often when I'm running Xfce (Xubuntu) on a recent kernel (4.17+). Xfce's default image viewer seems to be connected to it, as well. Most of the time I was having multiple instances of it when everything froze. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "system hardware information" https://bugs.launchpad.net/bugs/1798961/+attachment/5203301/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: New Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me, although it seems to happen more often when I'm running Xfce (Xubuntu) on a recent kernel (4.17+). Xfce's default image viewer seems to be connected to it, as well. Most of the time I was having multiple instances of it when everything froze. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:b
[Kernel-packages] [Bug 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
I have the same issue after upgrading it from 18.04.1 and also after a clean install. I can't do mutch with the computer because it is freezing after the login. The trackpad also freezes about 10s after the login. -- 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/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] Status in linux package in Ubuntu: Incomplete Bug description: Dell XPS 15 9570 ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2250 F pulseaudio Date: Fri Oct 12 08:54:08 2018 Failure: oops InstallationDate: Installed on 2018-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+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 1521173] Re: AER: Corrected error received: id=00e0
This is also present in later distro versions, right up to Cosmic. In my case it manifests on Supermicro and Intel 7500/5500/5520/X58 - based servers when Qlogic QLE2562 fibre optic cards are used - and _ONLY_ with Qlogic cards, nothing else seems to trigger it As with the wifi cards on laptops, a S3 cycle stops it. -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1798880] Re: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
lenge@hp-15:~$ cat /proc/version Linux version 4.19.0-041900rc8-generic (kernel@kathleen) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #201810150631 SMP Mon Oct 15 06:33:11 UTC 2018 It has same question: [7.132836] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [7.132840] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [7.132843] pcieport :00:1c.5: device [8086:a115] error status/mask=0001/2000 [7.132845] pcieport :00:1c.5:[ 0] RxErr -- 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/1798880 Title: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Status in linux package in Ubuntu: Confirmed Bug description: [ 1276.702446] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 1276.702457] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 1276.702466] pcieport :00:1c.5: device [8086:a115] error status/mask=0001/2000 [ 1276.702472] pcieport :00:1c.5:[ 0] Receiver Error (First) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lenge 2188 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 02:43:17 2018 MachineType: HP OMEN by HP Laptop ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=403be5e5-0af1-478d-a476-d3ba180f4c3c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.46:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1DE85PA#AB2 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798880/+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 1798880] Re: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- 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/1798880 Title: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Status in linux package in Ubuntu: Confirmed Bug description: [ 1276.702446] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 1276.702457] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 1276.702466] pcieport :00:1c.5: device [8086:a115] error status/mask=0001/2000 [ 1276.702472] pcieport :00:1c.5:[ 0] Receiver Error (First) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lenge 2188 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 02:43:17 2018 MachineType: HP OMEN by HP Laptop ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=403be5e5-0af1-478d-a476-d3ba180f4c3c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.46:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1DE85PA#AB2 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798880/+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 1798948] [NEW] Suspend to RAM on lid close does not work
Public bug reported: Upgraded to 18.10, installed NVIDIA-384 meta package for latest NVIDIA drivers. Closing the lid does not suspend the machine. journalctl: ... Okt 20 12:27:53 mbpr15a systemd-logind[1185]: Lid closed. Okt 20 12:27:53 mbpr15a /usr/lib/gdm3/gdm-x-session[2297]: (EE) event8 - bcm5974: libinput bug: 3: invalid tap event TAP_EVENT_RELEASE in state TAP_STATE_TAPPED Okt 20 12:27:53 mbpr15a gnome-shell[2461]: setup_framebuffers: assertion 'width > 0' failed Okt 20 12:27:57 mbpr15a systemd-logind[1185]: Lid opened. Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed ... the machine is set so that lid close should trigger suspend. cmd-L suspend OK ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-384 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 12:29:14 2018 InstallationDate: Installed on 2018-04-28 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1798948 Title: Suspend to RAM on lid close does not work Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Upgraded to 18.10, installed NVIDIA-384 meta package for latest NVIDIA drivers. Closing the lid does not suspend the machine. journalctl: ... Okt 20 12:27:53 mbpr15a systemd-logind[1185]: Lid closed. Okt 20 12:27:53 mbpr15a /usr/lib/gdm3/gdm-x-session[2297]: (EE) event8 - bcm5974: libinput bug: 3: invalid tap event TAP_EVENT_RELEASE in state TAP_STATE_TAPPED Okt 20 12:27:53 mbpr15a gnome-shell[2461]: setup_framebuffers: assertion 'width > 0' failed Okt 20 12:27:57 mbpr15a systemd-logind[1185]: Lid opened. Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed Okt 20 12:27:57 mbpr15a gnome-shell[1723]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed ... the machine is set so that lid close should trigger suspend. cmd-L suspend OK ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-384 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 12:29:14 2018 InstallationDate: Installed on 2018-04-28 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1798948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Yes this is exactly the problem I have. Every-time I install the Nvidia- drivers the machine won't boot up it hangs and displays "Failed to connect to lvmetad. Falling back to device scanning. /dev/mapper/ubuntu--vg--root" I even tried installing earlier drivers -340 or 361 . The problem persists. The only time it boots up is when I purge the Nvidia drivers. This started soon after I upgraded to 18.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
temporary solution.. create and edit: /lib/systemd/system-sleep/restore_connection ... #!/bin/sh sleep 5 case $1/$2 in post/*) sudo systemctl restart network-manager.service modprobe -r sky2 modprobe sky2 ;; esac ...give executable rights. chmod +x /lib/systemd/system-sleep/restore_connection but we must finally fix it !!! :-) -- 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/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] sky2 ethernet stops working after system resume from suspend. [Fix] Increase the PCI D3 delay can workaround the issue. [Test] User responded that the D3 delay increase can solve the issue. [Regression Potential] Low. It only affects one device. The fix only increase the delay timer, without any functional change. ===Original Bug Report=== After resuming from sleep using the lid-open event, OFTEN (60% replicable, usually after 2nd or later resume) the NIC is not functional, and reloading the sky2 module does not help. Relevant parts from dmesg: [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 ... [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error And after reloading the module: [ 1421.781480] sky2: driver version 1.30 [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003) [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff [ 1421.782292] sky2: probe of :04:00.0 failed with error -95 Possibly relevant: [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID. Replicability: When it happens once, further suspend-resume cycles (tried ~5) don't fix it. Reboot fixes the NIC, and it often survives first resume after that, but 1-2 suspend-resume cycles later the issue WILL occur again. Per-boot chance of encountering the issue - so far 2/5. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-12-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sat Mar 24 09:54:10 2018 HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1 InstallationDate: Installed on 2018-03-21 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d consoleblank=300 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firm
[Kernel-packages] [Bug 1760073] Re: No network from suspend resume
*** This bug is a duplicate of bug 1752772 *** https://bugs.launchpad.net/bugs/1752772 all new 4.15.0-X.X kernels have this error :-( but I use this script and it's OK but we must finally fix it . create and edit: /lib/systemd/system-sleep/restore_connection ... #!/bin/sh sleep 5 case $1/$2 in post/*) sudo systemctl restart network-manager.service modprobe -r sky2 modprobe sky2 ;; esac ...give executable rights. chmod +x /lib/systemd/system-sleep/restore_connection -- 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/1760073 Title: No network from suspend resume Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Following a resume from suspend - no network available on machine. Originally reported when using 4.15.0-10-generic, recent update to kernel 4.15.0-15-generic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.25.2-0ubuntu1 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: XFCE Date: Fri Mar 30 11:53:22 2018 InstallationDate: Installed on 2018-03-08 (21 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-08 (23 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Tags: bionic third-party-packages Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-08 (23 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Tags: bionic third-party-packages Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-08 (23 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1760073/+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 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
all new 4.15.0-X.X kernels have this error :-( -- 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/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] sky2 ethernet stops working after system resume from suspend. [Fix] Increase the PCI D3 delay can workaround the issue. [Test] User responded that the D3 delay increase can solve the issue. [Regression Potential] Low. It only affects one device. The fix only increase the delay timer, without any functional change. ===Original Bug Report=== After resuming from sleep using the lid-open event, OFTEN (60% replicable, usually after 2nd or later resume) the NIC is not functional, and reloading the sky2 module does not help. Relevant parts from dmesg: [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 ... [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error And after reloading the module: [ 1421.781480] sky2: driver version 1.30 [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003) [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff [ 1421.782292] sky2: probe of :04:00.0 failed with error -95 Possibly relevant: [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID. Replicability: When it happens once, further suspend-resume cycles (tried ~5) don't fix it. Reboot fixes the NIC, and it often survives first resume after that, but 1-2 suspend-resume cycles later the issue WILL occur again. Per-boot chance of encountering the issue - so far 2/5. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-12-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sat Mar 24 09:54:10 2018 HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1 InstallationDate: Installed on 2018-03-21 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d consoleblank=300 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.11 - 067 - 1566 dmi.board.name: S11D dmi.b
[Kernel-packages] [Bug 1798940] 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/1798940 Title: PKCS#7 signature not signed with a trusted key Status in linux package in Ubuntu: Confirmed Bug description: executing: '"/lib/modules/4.18.0-10-generic/build/scripts/sign-file" "sha512" "/var/lib/shim-signed/mok/MOK.priv" "/var/lib/shim-signed/mok/MOK.der" "./kernel/nvidia.ko"'... ... executing: '"/lib/modules/4.18.0-10-generic/build/scripts/sign-file" "sha512" "/var/lib/shim-signed/mok/MOK.priv" "/var/lib/shim-signed/mok/MOK.der" "./kernel/nvidia-uvm.ko"'... nvidia drivers had been signed at install, and lenge@hp-15:/lenge/linux$ mokutil --test-key /var/lib/shim-signed/mok/MOK.der /var/lib/shim-signed/mok/MOK.der is already enrolled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lenge 2130 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 15:55:57 2018 MachineType: HP OMEN by HP Laptop ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=403be5e5-0af1-478d-a476-d3ba180f4c3c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.46:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1DE85PA#AB2 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798940/+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 1798940] [NEW] PKCS#7 signature not signed with a trusted key
Public bug reported: executing: '"/lib/modules/4.18.0-10-generic/build/scripts/sign-file" "sha512" "/var/lib/shim-signed/mok/MOK.priv" "/var/lib/shim-signed/mok/MOK.der" "./kernel/nvidia.ko"'... ... executing: '"/lib/modules/4.18.0-10-generic/build/scripts/sign-file" "sha512" "/var/lib/shim-signed/mok/MOK.priv" "/var/lib/shim-signed/mok/MOK.der" "./kernel/nvidia-uvm.ko"'... nvidia drivers had been signed at install, and lenge@hp-15:/lenge/linux$ mokutil --test-key /var/lib/shim-signed/mok/MOK.der /var/lib/shim-signed/mok/MOK.der is already enrolled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lenge 2130 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 15:55:57 2018 MachineType: HP OMEN by HP Laptop ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=403be5e5-0af1-478d-a476-d3ba180f4c3c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.46:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1DE85PA#AB2 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1798940 Title: PKCS#7 signature not signed with a trusted key Status in linux package in Ubuntu: New Bug description: executing: '"/lib/modules/4.18.0-10-generic/build/scripts/sign-file" "sha512" "/var/lib/shim-signed/mok/MOK.priv" "/var/lib/shim-signed/mok/MOK.der" "./kernel/nvidia.ko"'... ... executing: '"/lib/modules/4.18.0-10-generic/build/scripts/sign-file" "sha512" "/var/lib/shim-signed/mok/MOK.priv" "/var/lib/shim-signed/mok/MOK.der" "./kernel/nvidia-uvm.ko"'... nvidia drivers had been signed at install, and lenge@hp-15:/lenge/linux$ mokutil --test-key /var/lib/shim-signed/mok/MOK.der /var/lib/shim-signed/mok/MOK.der is already enrolled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lenge 2130 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 15:55:57 2018 MachineType: HP OMEN by HP Laptop ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=403be5e5-0af1-478d-a476-d3ba180f4c3c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.46:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1DE85PA#AB2 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798940/+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
I have the same problem on my old Dell Latitude E6400. Workaround at post #55 fixes the problem until next reboot. -- 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
