[Kernel-packages] [Bug 1788563] Re: L1TF mitigation not effective
Yes, the bionic test kernel resolves this issue. Verified by looking at dmesg as well as https://github.com/speed47/spectre-meltdown-checker -- 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/1788563 Title: L1TF mitigation not effective Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: Lenovo Thinkpad W530 system with 32 GB RAM dmesg | grep -i l1tf [0.038386] L1TF: System has more than MAX_PA/2 memory. L1TF mitigation not effective. [ 2652.469669] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details. Related: https://bugzilla.opensuse.org/show_bug.cgi?id=1105536 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.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pgera 2809 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Aug 23 03:38:40 2018 InstallationDate: Installed on 2018-08-11 (12 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 24382LU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=e2607c8a-4bd1-49fe-ad07-83046492fac5 ro quiet splash vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 24382LU dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:svnLENOVO:pn24382LU:pvrThinkPadW530:rvnLENOVO:rn24382LU:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 24382LU dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
nvidia-prime 0.8.8.1, everything else updated. After selecting intel and rebooting NVidia drivers still loaded. ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1055475] Re: [Apple Inc. MacBookPro5, 4] suspend/resume failure [non-free: wl]
Launchpad has imported 2 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=49431. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-10-24T13:13:58+00:00 mario.vukelic wrote: [1.] One line summary of the problem (downstream bug title) [Apple Inc. MacBookPro5,4] suspend/resume failure [non-free: wl] [2.] Full description of the downstream problem/report: (Downstream report URL: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1055475) Note: When the problem occurred and the apport bug report was created, the non-free wl module was loaded (compiled from bcmwl-kernel-source) to enable the Broadcom wifi. However, the same problem happens after removing the wl module and rebooting. On this machine, suspend/resume has worked in released Ubuntu versions since its purchase mid-2009, when IIRC it received a development version install of Karmic (9.10). Hibernate/resume worked just as reliably. The latest fresh install was Oneiric (11.10), later upgraded to Precise (12.04) after release. The machine usually ran the proprietary NVidia graphics drivers, therefore I am unsure if suspend/hibernate/resume also worked with the nouveau drivers (however I seem to remember so). Recently I performed a reinstall with 12.04.1 (using the BIOS image, not the EFI image) and immediately upgraded to Quantal. (For some reason I could not make Quantal CDs boot). The machine is now using the nouveau drivers because currently the backlight adjustment does not work with NVidia drivers. In Quantal with nouveau, resume from suspend never worked for me. When going into suspended state all at first appears fine. However, the machine does not resume properly. When trying to resume, the fan and optical drive starts, however the screen remains black and I can't tell if its responsive. I pressed the power button for 5 seconds and the machine rebooted fine. After logging in, an apport prompt appeared, from which I created this bug report. Resume works correctly with the proprietary nvidia-current drivers. I don't know about hibernate since due to using an encrypted home directory it is not available anymore. [3.] Keywords amd64 resume suspend nouveau [4.] Kernel version (from /proc/version): Linux version 3.6.1-030601-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201210071322 SMP Sun Oct 7 17:23:28 UTC 2012 [5.] Output of Oops.. message None that I know of, but the automated Ubuntu report says "ProblemType: KernelOops" [6.] A small shell script or example program which triggers the problem (if possible) None. Reproducible by suspending and resuming the machine. [7.] Environment (lsb_release -rd) Description:Ubuntu 12.10 Release:12.10 [7.1.] Software (add the output of the ver_linux script here) Linux chronic 3.6.1-030601-generic #201210071322 SMP Sun Oct 7 17:23:28 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Gnu C 4.7 Gnu make 3.81 binutils 2.22.90.20120924 util-linux 2.20.1 mount support module-init-tools 3.16 e2fsprogs 1.42.5 pcmciautils018 PPP2.4.5 Linux C Library2.15 Dynamic linker (ldd) 2.15 Procps 3.3.3 Net-tools 1.60 Kbd1.15.3 Sh-utils 8.13 Modules Loaded msr michael_mic arc4 dm_crypt snd_hda_codec_cirrus joydev applesmc input_polldev coretemp kvm_intel kvm lib80211_crypt_tkip snd_hda_intel microcode snd_hda_codec snd_hwdep snd_pcm wl snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq lib80211 snd_timer shpchp snd_seq_device snd uvcvideo videobuf2_core videodev videobuf2_vmalloc soundcore videobuf2_memops snd_page_alloc bcm5974 apple_gmux apple_bl mac_hid i2c_nforce2 bnep rfcomm bluetooth parport_pc ppdev lp binfmt_misc parport hid_apple hid_generic usbhid hid usb_storage uas firewire_ohci nouveau firewire_core crc_itu_t ttm drm_kms_helper drm i2c_algo_bit mxm_wmi video wmi forcedeth [7.2.] Processor information (from /proc/cpuinfo): processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz stepping: 10 microcode : 0xa07 cpu MHz : 798.000 cache size : 3072 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf
[Kernel-packages] [Bug 1787309] Re: zed not sending mail on scrub finish
The 7.5 and 4.15 kernel was causing a crash under load when only zfs io was happening and then did something to cause ext4 root file system i/o. The system locked up so hard that the console keyboard cap lock did not even work. I have downgraded to 4.13 which solves the system lockup and the mail for for scrub starting working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1787309 Title: zed not sending mail on scrub finish Status in zfs-linux package in Ubuntu: New Bug description: ZED should be sending email when scrub finishes but I do not get any email. I did update modify the zed.rc file to end the email by setting the following ZED_EMAIL_ADDR="root" ZED_EMAIL_PROG="mail" ZED_NOTIFY_VERBOSE=1 I tested to verify mail work. I did the following: echo testing | mail -s testit root I did get the mail so the mail system work. I also check syslog to see verify that zed saw the event. Aug 15 22:45:56 mike-think systemd[1]: Started ZFS Event Daemon (zed). Aug 15 22:45:56 mike-think zed[5576]: ZFS Event Daemon 0.6.5.6-0ubuntu23 (PID 5576) Aug 15 22:45:56 mike-think zed[5576]: Processing events since eid=7 Aug 15 22:48:38 mike-think zed: eid=8 class=history_event pool=lxc Aug 15 22:48:38 mike-think zed: eid=9 class=scrub_finish pool=lxc mike@mike-think:/var/log$ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 mike@mike-think:/var/log$ mike@mike-think:/var/log$ apt-cache policy zfs-zed zfs-zed: Installed: 0.6.5.6-0ubuntu23 Candidate: 0.6.5.6-0ubuntu23 Version table: *** 0.6.5.6-0ubuntu23 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages mike@mike-think:/var/log$ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfs-zed 0.6.5.6-0ubuntu23 ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Aug 15 22:50:27 2018 InstallationDate: Installed on 2016-07-24 (752 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.zfs.zed.d.zed.rc: 2018-08-15T22:44:06.422894 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1787309/+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 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image
Added acpid as affected because there is a file /etc/acpi/asus-keyboard- backlight.sh so I suppose it will be involved ** Also affects: acpid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791372 Title: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image Status in acpid package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Repro: 1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully updated -> Keyboard backlight should come on or change but doesn't. The gnome-shell pop-up icon for the keyboard backlight appears for both keys, but the icon's "progress" bar is not visible. Kernel version is linux-image-4.17.0-9-generic This is the same in X and Wayland session. In case it matters, Nvidia binary drivers are installed but Nvidia is switched off via Prime setting in nvidia-settings. Running with Intel drivers The keyboard backlight works perfectly when booting from the 18.04.1 desktop live image. When turning on light with 18.04.1, it is off again after rebooting into 18.10. (However 18.04.1 seems to freeze when shutting down from menu, I have to hard-shut it off). Most other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for the airplane mode key. However the airplane mode key only fails in gnome-shell but works on the console (this is filed as https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1791367) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: angela16196 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 22:08:12 2018 InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1791372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
The situation is incredible, in that there doesn't (seem) to be a concrete sure fire solution to this. If there's a BIOS option, which can fix it, it should damn well be put MANDATORY in all BIOS - not an option, locked in. System stability should not be this unreliable.Especially now they're on 2xxx series processors. This huge job log is neatly a year old now, it's crazy. It should be fixed on the processor itself or the BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8
[Kernel-packages] [Bug 1690085]
Haven't had a single lockup after update to Kernel 4.15 and setting the BIOS to typical idle current setting. Have run the PC for few days and no issues nor any lock up under heavy CPU use.This is a ASUS B350M board with latest BIOS on Ryzen 1700. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1690085]
I erred earlier in suggesting that this bug should be closed with "fixed". Rather, this bug should should be closed with "notabug" because there appears to be no evidence to suggest that it is actually a kernel bug, compared to considerable evidence suggesting it is not. Meanwhile, I personally appreciate the slow trickle of comments along the lines of confirming that the typical current bios fix is effective, compared to the absence of comments that the bug persists even with this option enabled. My current uptime with typical current enabled is 136 days, compared to only a few days without 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release
[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
?? How do we go about working with someone to get this issue with the Intel i219-v ethernet controller fixed on Ubuntu 18.04? The issue has existing since day one of the install and continues to this day. Ethernet/Internet connectivity should be 100% staple on any OS. -- 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/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+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 1791389] Re: usb 3-4: device descriptor read/64, error -110
Launchpad has imported 5 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=201037. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-09-07T11:39:30+00:00 caravena wrote: Created attachment 278363 dmesg 4.18.5-gnu Hello, dmesg: [7.008154] usb 3-1: device descriptor read/64, error -110 Best regards, -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791389/comments/0 On 2018-09-07T11:45:28+00:00 caravena wrote: Created attachment 278365 # lspci -vvnn Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791389/comments/1 On 2018-09-07T11:51:34+00:00 greg wrote: On Fri, Sep 07, 2018 at 11:39:30AM +, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=201037 > > Bug ID: 201037 >Summary: usb 3-1: device descriptor read/64, error -110 >Product: Drivers >Version: 2.5 > Kernel Version: 4.18.5-gnu All USB bugs should be sent to the linux-...@vger.kernel.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791389/comments/2 On 2018-09-07T15:30:23+00:00 caravena wrote: Hello Greg Kroah-Hartman, https://marc.info/?l=linux-usb=153633276313388=2 Best regards, -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791389/comments/3 On 2018-09-07T23:46:59+00:00 caravena wrote: Hello, Report in launchpad.net https://bugs.launchpad.net/bugs/1791389 Best regards, -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791389/comments/6 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- 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/1791389 Title: usb 3-4: device descriptor read/64, error -110 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [7.776138] usb 3-4: device descriptor read/64, error -110 [8.048909] usb 3-4: New USB device found, idVendor=0cf3, idProduct=9271, bcdDevice= 1.08 [8.048917] usb 3-4: New USB device strings: Mfr=16, Product=32, SerialNumber=48 [8.048922] usb 3-4: Product: USB2.0 WLAN [8.048927] usb 3-4: Manufacturer: ATHEROS [8.048939] usb 3-4: SerialNumber: 12345 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2485 F pulseaudio /dev/snd/pcmC0D0p: caravena 2485 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 20:39:28 2018 InstallationDate: Installed on 2017-10-13 (329 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-7-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
[Kernel-packages] [Bug 1055475] Re: [Apple Inc. MacBookPro5, 4] suspend/resume failure [non-free: wl]
This was resolved somewhere along the way long ago ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1055475 Title: [Apple Inc. MacBookPro5,4] suspend/resume failure [non-free: wl] Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: Note: When the problem occurred and the apport bug report was created, the non-free wl module was loaded (compiled from bcmwl-kernel-source) to enable the Broadcom wifi. However, the same problem happens after removing the wl module and rebooting. On this machine, suspend/resume has worked in released Ubuntu versions since its purchase mid-2009, when IIRC it received a development version install of Karmic (9.10). Hibernate/resume worked just as reliably. The latest fresh install was Oneiric (11.10), later upgraded to Precise (12.04) after release. The machine usually ran the proprietary NVidia graphics drivers, therefore I am unsure if suspend/hibernate/resume also worked with the nouveau drivers (however I seem to remember so). I now performed a reinstall with 12.04.1 (using the BIOS image, not the EFI image) and immediately upgraded to Quantal. (For some reason I could not make Quantal CDs boot). The machine is now using the nouveau drivers because currently the backlight adjustment does not work with NVidia drivers. In Quantal with nouveau, resume from suspend never worked for me. When going into suspended state all at first appears fine. However, the machine does not resume properly. When trying to resume, the fan and optical drive starts, however the screen remains black and I can't tell if its responsive. I pressed the power button for 5 seconds and the machine rebooted fine. After logging in, an apport prompt appeared, from which I created this bug report. I don't know about hibernate since due to using an encrypted home directory it is not available anymore. WORKAROUND: Resume works correctly with the proprietary nvidia-current drivers. ProblemType: KernelOops DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-15-generic 3.5.0-15.22 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 2337 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 24 09:05:58 2012 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=58df2950-5d89-42a8-a44c-3bf5410313aa InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) InterpreterPath: /usr/bin/python3.2mu MachineType: Apple Inc. MacBookPro5,4 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=1f4ef214-a70d-44ac-8515-2d4234f32e38 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-3.5.0-15-generic N/A linux-backports-modules-3.5.0-15-generic N/A linux-firmware1.93 RfKill: 0: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [Apple Inc. MacBookPro5,4] suspend/resume failure [non-free: wl] UpgradeStatus: Upgraded to quantal on 2012-09-15 (8 days ago) UserGroups: dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP53.88Z.00AC.B03.0906151647 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22587A1 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro5,4 dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22587A1 dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,4:pvr1.0:rvnAppleInc.:rnMac-F22587A1:rvrMacBookPro5,4:cvnAppleInc.:ct10:cvrMac-F22587A1: dmi.product.name: MacBookPro5,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1055475/+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 1791389] Re: usb 3-4: device descriptor read/64, error -110
** Bug watch added: Linux Kernel Bug Tracker #201037 https://bugzilla.kernel.org/show_bug.cgi?id=201037 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=201037 Importance: Unknown Status: Unknown ** Description changed: Hello, dmesg: [7.776138] usb 3-4: device descriptor read/64, error -110 [8.048909] usb 3-4: New USB device found, idVendor=0cf3, idProduct=9271, bcdDevice= 1.08 [8.048917] usb 3-4: New USB device strings: Mfr=16, Product=32, SerialNumber=48 [8.048922] usb 3-4: Product: USB2.0 WLAN [8.048927] usb 3-4: Manufacturer: ATHEROS [8.048939] usb 3-4: SerialNumber: 12345 - - -- - - https://bugzilla.kernel.org/show_bug.cgi?id=201037 - - -- Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: caravena 2485 F pulseaudio - /dev/snd/pcmC0D0p: caravena 2485 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: caravena 2485 F pulseaudio + /dev/snd/pcmC0D0p: caravena 2485 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 20:39:28 2018 InstallationDate: Installed on 2017-10-13 (329 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-7-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: - linux-restricted-modules-4.18.0-7-generic N/A - linux-backports-modules-4.18.0-7-generic N/A - linux-firmware1.175 + linux-restricted-modules-4.18.0-7-generic N/A + linux-backports-modules-4.18.0-7-generic N/A + linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. -- 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/1791389 Title: usb 3-4: device descriptor read/64, error -110 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [7.776138] usb 3-4: device descriptor read/64, error -110 [8.048909] usb 3-4: New USB device found, idVendor=0cf3, idProduct=9271, bcdDevice= 1.08 [8.048917] usb 3-4: New USB device strings: Mfr=16, Product=32, SerialNumber=48 [8.048922] usb 3-4: Product: USB2.0 WLAN [8.048927] usb 3-4: Manufacturer: ATHEROS [8.048939] usb 3-4: SerialNumber: 12345 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2485 F pulseaudio /dev/snd/pcmC0D0p: caravena 2485 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 20:39:28 2018 InstallationDate: Installed on 2017-10-13 (329 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-7-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux
[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
you can find the missing logfile as attachment: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+attachment/5186052/+files/apport.linux-image-4.15.0-33-generic.s5j_wb2y.apport ** 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/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in linux package in Ubuntu: Confirmed Bug description: my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+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 1790688] Re: x86/pti: 32-bit x86 systems support already available.
** Summary changed:
- x86/pti: 32-Bit x86 systems support already available.
+ x86/pti: 32-bit x86 systems support already available.
** Description changed:
Hello.
- Linux kernel v4.19 release candidate [1], finally have kernel page-table
- isolation ('PTI', previously known as 'KAISER') support for x86_32
- architecture. As we know, 'PTI' provides protection against attack,
- known as the "Meltdown" (CVE-2017-5754), that breaks isolation between
- user applications and the operating system etc. However, kernel page-
- table isolation wasn't available on 32-Bit x86 systems. Until now.
+ This is a very good news: 'PTI' support for x86-32 architecture is
+ available. Linux kernel v4.19 release candidate, finally have Kernel
+ Page-Table Isolation ('PTI', previously known as 'KAISER') support. As
+ we know, 'PTI' provides protection against attack, known as the
+ "Meltdown" (CVE-2017-5754), that breaks isolation between user
+ applications and the operating system etc. However, this protection -
+ needed for "Meltdown" mitigation - wasn't available on 32-bit x86
+ systems. Until now.
So, I would like to ask a question: are there any plans to backport
- kernel page-table isolation patches for Linux kernels available in
- "Trusty"/14.04, "Xenial"/16.04 and "Bionic"/18.04 releases etc.? I mean
- x86_32 bit architecture, of course. I'm asking, because it seems, that
- pretty much no developers run 32-bit any more. However, there still are
- many 32-bit users out there.
+ Kernel Page-Table Isolation patches for Linux kernels available in
+ "Trusty"/14.04, "Xenial"/16.04 and "Bionic"/18.04 releases etc.? I'm
+ asking, because it seems, that pretty much no developers run 32-bit any
+ more. However, there still are many 32-bit users out there.
- For more informations about how 'PTI' was implementing on 32-Bit x86
- architecture, plase check - for example - commit '7757d607c6b31'
- ("x86/pti: Allow CONFIG_PAGE_TABLE_ISOLATION for x86_32"). Here are
- messages about 'PTI' support (PATCH v7, v8) for x86_32 [1]. Next, 'PTI'
- fixes for x86-32 [2] and more patches related to 'x86/mm/pti' [3]. There
- is also a short report for the first half of the 4.19 kernel merge
- window [4].
+ For more informations about how 'PTI' was implemented, created for 32
+ bit x86 architecture, please check - for example - commit
+ '7757d607c6b31' ("x86/pti: Allow CONFIG_PAGE_TABLE_ISOLATION for
+ x86_32") and these messages on lkml mailing list and lwn.net website
+ (which contains summary of the first half of the 4.19 kernel merge
+ window):
- I'm sorry for such a long message, but I'm very happy that 'PTI' support
- is already available for x86_32 architecture and I hope, that it will be
- backported to all Ubuntu LTS releases etc.
+ ✗ http://lkml.iu.edu/hypermail/linux/kernel/1807.2/02790.html ('PTI' on
x86-32; PATCH v.8)
+ ✗ https://lwn.net/Articles/762566/ (See "Architecture-specific" changes)
+
+ I would like to send a big "Thank You" to Mr Joerg Roedel (and Others,
+ of course) for his amazing work - a whole raft of measures and patches
+ to make this possible - to enable 'PTI' mitigation on x86-32
+ architecture etc.
Thanks, best regards.
- __
-
- [1] http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03578.html (please see
every next patches etc.)
- http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03181.html
- http://lkml.iu.edu/hypermail/linux/kernel/1807.2/02790.html
- [2] http://lkml.iu.edu/hypermail/linux/kernel/1808.0/05516.html
- [3] http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03161.html
- [4] https://lwn.net/Articles/762566/ (See "Architecture-specific" changes)
--
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/1790688
Title:
x86/pti: 32-bit x86 systems support already available.
Status in linux package in Ubuntu:
Triaged
Bug description:
Hello.
This is a very good news: 'PTI' support for x86-32 architecture is
available. Linux kernel v4.19 release candidate, finally have Kernel
Page-Table Isolation ('PTI', previously known as 'KAISER') support. As
we know, 'PTI' provides protection against attack, known as the
"Meltdown" (CVE-2017-5754), that breaks isolation between user
applications and the operating system etc. However, this protection -
needed for "Meltdown" mitigation - wasn't available on 32-bit x86
systems. Until now.
So, I would like to ask a question: are there any plans to backport
Kernel Page-Table Isolation patches for Linux kernels available in
"Trusty"/14.04, "Xenial"/16.04 and "Bionic"/18.04 releases etc.? I'm
asking, because it seems, that pretty much no developers run 32-bit
any more. However, there still are many 32-bit users out there.
For more informations about how 'PTI' was implemented, created for 32
bit x86 architecture, please check - for example - commit
'7757d607c6b31' ("x86/pti: Allow
[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)
@softrabbit - I have a machine with an Intel Celeron N2840 that oddly was never affected by the Suspend bug described in this report. My HP Pavilion with N3540 and another I tested with an N2830 (using a Live USB of 18.04) were both affected but curiously not the N2840 machine. I have started a thread regarding some of the Suspend issues on 18.04 that I found along the way whilst trying to figure out what was wrong with my machine. If you wish to discuss further please post here: https://ubuntuforums.org/showthread.php?t=2395562 -- 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 Committed 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 1761999] Re: general protection fault: 0000 [#1] SMP NOPTI
The logs have been anonymised. Problem started around the time 00:50 ** Attachment added: "paste1.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761999/+attachment/5186535/+files/paste1.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/1761999 Title: general protection fault: [#1] SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Filebot tried to write to network storage, chrashed nautilus and the system ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 15:55:03 2018 Failure: oops HibernationDevice: RESUME=UUID=16b94b21-aecc-4d2e-93f5-13640ea3517b InstallationDate: Installed on 2014-04-20 (1448 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-790XT-USB3 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic root=UUID=2e3a0b23-1dde-4570-aa78-bd8253bbd52a 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 RfKill: SourcePackage: linux Title: general protection fault: [#1] SMP NOPTI UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-790XT-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-790XT-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761999/+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 1761999] Re: general protection fault: 0000 [#1] SMP NOPTI
I had an ugly instance of this problem on an EPYC processor. Not sure what it was related to. It all started with errors during package upgrades. sudo apt-get update >> success sudo apt-get upgrade >> segmentation fault The upgrade left several packages in a half-installed state (attach Part 1), and basic os command started to crash (attach Part 2). In the syslog I had "general protection fault: [#1] SMP NOPTI" with multiple processes, see a detail failure log in attach Part 3 and Part 4. Attach Part 5 lists numerous processes that had the same failure as Part 4. The system load started to climb, from idle, progressively by about 1 point per 3-5 min, until levels like 20-30, at this point it was very difficult to enter and reboot the system. I tried and managed to have it respond with reboot -f but it had the problem still and system did not come up correctly, until we performed a physical shutdown and restart. From then the system seems clean. I corrected the packages by reinstallation, and so far no problem. Very frightening! Can it be related to some problem between Ubuntu and the Ryzen/EPYC technology? Please comment if you think this is a completely different bug. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761999 Title: general protection fault: [#1] SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Filebot tried to write to network storage, chrashed nautilus and the system ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 15:55:03 2018 Failure: oops HibernationDevice: RESUME=UUID=16b94b21-aecc-4d2e-93f5-13640ea3517b InstallationDate: Installed on 2014-04-20 (1448 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-790XT-USB3 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic root=UUID=2e3a0b23-1dde-4570-aa78-bd8253bbd52a 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 RfKill: SourcePackage: linux Title: general protection fault: [#1] SMP NOPTI UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-790XT-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-790XT-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761999/+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 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
Ok, you didn't actually read my log output and assume things. The log message disappears completely WHEN my Bluetooth starts working. The actual opposite of your argument. I.e., the message only appears when my machine is "unhealthy". The message does not occur concurrently at all. Regardless, I can redo my test say 3 times before/after suspend/reboot/logout and if the same pattern occurs it is not a coincident for sure. The message will then be related to the issues (already) reported in several other bug reports. The coder behind this message is arguing, from what i can surmise, that this is an error that is not handled, not that it is a superfluous debug statement as seen in statements above: https://www.spinics.net/lists /linux-bluetooth/msg75270.html -- 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/1748565 Title: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f) Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-9-generic 4.15.0-9.10 ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2 Uname: Linux 4.15.0-9-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1811 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Feb 9 20:35:29 2018 InstallationDate: Installed on 2017-10-13 (119 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-9-generic N/A linux-backports-modules-4.15.0-9-generic N/A linux-firmware1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1748565/+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 1791427] 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version:
[Kernel-packages] [Bug 1775945] Re: Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid
Hi Joseph, I've been on 4.15.18 upstream stable for three weeks now, and the problem seems to be gone. When will the Ubuntu kernel have the fixes incorporated so that I can I switch back from the upstream stable kernel? Regards, Pieter -- 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/1775945 Title: Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid Status in linux package in Ubuntu: Confirmed Bug description: I was running ubuntu 17.10 for months with no issues. After upgrading to 18.04, closing the lid regularly (but not always) results in either: 1. The display staying on with a frozen lock-screen, or 2. The display powered off, but the notebook still powered on. In both cases the notebook does not respond. A five-second press of the power button to hard-reboot the computer is the only means of recovery. After powering the notebook back on, there are no files in /var/crash. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 00:00:48 2018 InstallationDate: Installed on 2018-06-02 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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/1775945/+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 1791427] [NEW] Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Public bug reported: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-Discussion/X1 -Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-Suspend- to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET55W(1.30):bd08/31/2018:svnLENOVO:pn20KH006KPB:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH006KPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH006KPB dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1756105] Re: X1 Carbon 6th gen S0i3 sleep broken
Not a fix for S0i3, but the latest X1 6th Gen BIOS (1.30) now has a power option to enable S3 without having to patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756105 Title: X1 Carbon 6th gen S0i3 sleep broken Status in linux package in Ubuntu: Confirmed Bug description: Recent kernel claims S0i3 patch, but this mode is not currently engage "out of the box" on latest patch levels of 18.04. Sleep consumes 2-3 watts instead of 0.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756105/+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 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq
I suffer from this bug too, with this card in access point mode: 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] And kernel 4.15.0-33-generic on Ubuntu 16.04 Xenial, though I encountered it with previous versions too, and I think with 4.4 kernels too. It seems to happen when the load on the network is high. But luckily, according to https://www.spinics.net/lists/linux- wireless/msg169581.html it seems to be fixed in Intel by https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport- iwlwifi.git/commit/?id=b8e2a319df8cc60626ab7dcabbbab64ff56be41e in their release/core35. I think the resulting bug is probably in iwlwifi.ko (linux-image-extra package) (I don't think it is in iwlwifi.ucode). Is there any way to track which release/coreXX is in a kernel version? -- 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/1733194 Title: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: When in AP mode after some time, get this BUG: Nov 18 23:21:31 bifrost kernel: [18345.860393] BUG: unable to handle kernel NULL pointer dereference at 0070 Nov 18 23:21:31 bifrost kernel: [18345.860552] IP: iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi] Nov 18 23:21:31 bifrost kernel: [18345.860644] PGD 0 Nov 18 23:21:31 bifrost kernel: [18345.860646] P4D 0 Nov 18 23:21:31 bifrost kernel: [18345.860682] Nov 18 23:21:31 bifrost kernel: [18345.860747] Oops: 0002 [#1] SMP Nov 18 23:21:31 bifrost kernel: [18345.860800] Modules linked in: nfnetlink_queue nfnetlink_log nfnetlink dummy ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo xt_policy xt_multiport ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter nls_iso8859_1 cmdlinepart intel_spi_platform intel_spi spi_nor mtd arc4 intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel bridge kvm stp llc iwlmvm irqbypass punit_atom_debug mac80211 intel_cstate snd_hda_codec_hdmi iwlwifi snd_hda_codec_realtek snd_hda_codec_generic cfg80211 btusb snd_hda_intel lpc_ich btrtl snd_hda_codec snd_intel_sst_acpi Nov 18 23:21:31 bifrost kernel: [18345.861897] mei_txe snd_hda_core mei snd_hwdep shpchp snd_intel_sst_core snd_soc_sst_atom_hifi2_platform hci_uart snd_soc_sst_match snd_soc_core btbcm serdev snd_compress btqca ac97_bus btintel snd_pcm_dmaengine snd_pcm dw_dmac dw_dmac_core snd_timer bluetooth snd soundcore mac_hid intel_int0002_vgpio ecdh_generic spi_pxa2xx_platform rfkill_gpio pwm_lpss_platform pwm_lpss 8250_dw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 drm_kms_helper crct10dif_pclmul igb syscopyarea sysfillrect crc32_pclmul sysimgblt fb_sys_fops dca ghash_clmulni_intel i2c_algo_bit cryptd ahci ptp drm pps_core libahci video Nov 18 23:21:31 bifrost kernel: [18345.862995] i2c_hid hid sdhci_acpi sdhci Nov 18 23:21:31 bifrost kernel: [18345.863068] CPU: 1 PID: 1202 Comm: kworker/1:2 Tainted: GW 4.13.0-16-generic #19-Ubuntu Nov 18 23:21:31 bifrost kernel: [18345.863203] Hardware name: NF541 NF541/NF541, BIOS BAR1NA02 02/25/2016 Nov 18 23:21:31 bifrost kernel: [18345.863326] Workqueue: events iwl_mvm_add_new_dqa_stream_wk [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.863428] task: 96862c1c5800 task.stack: a98a817c Nov 18 23:21:31 bifrost kernel: [18345.863539] RIP: 0010:iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi] Nov 18 23:21:31 bifrost kernel: [18345.863635] RSP: 0018:a98a817c3be0 EFLAGS: 00010246 Nov 18 23:21:31 bifrost kernel: [18345.863718] RAX: 09c4 RBX: 001f RCX: Nov 18 23:21:31 bifrost kernel: [18345.863824] RDX: RSI: 001f RDI: 2710 Nov 18 23:21:31 bifrost kernel: [18345.863932] RBP: a98a817c3c30 R08: 2710 R09: 0001 Nov 18 23:21:31 bifrost kernel: [18345.864039] R10: R11: 9686344ce010 R12: Nov 18 23:21:31 bifrost kernel: [18345.864145] R13: 96862c9d0018 R14: R15: Nov 18 23:21:31 bifrost kernel: [18345.864253] FS: () GS:96863fc8() knlGS: Nov 18 23:21:31 bifrost kernel: [18345.864373] CS: 0010 DS: ES: CR0:
[Kernel-packages] [Bug 1790594] Re: The system is not able to detect the touchsreen
And when you installed the system you need to add this file
https://github.com/hirotakaster/baytail-bootia32.efi and boot ino that.
--
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/1790594
Title:
The system is not able to detect the touchsreen
Status in linux package in Ubuntu:
Incomplete
Bug description:
I' m using a tablet that is sold with Windows 10.
The firmware extracted from the special driver are already available here
https://github.com/onitake/gsl-firmware/tree/master/firmware/trekstor/surftab7old.
(I discovered that the Mediacom drivers are the same as those for TrekStor, a
company that also works with Mediacom.Mediacom Winpad 7.0 W700 corresponds at
SurfTab wintron 7.0 ST70416-6).
That repository states that i need to recompile the kernel.
I don' t know how here
https://unix.stackexchange.com/questions/466571/recompile-a-kernel-including-a-firmware?noredirect=1#comment850048_466571
there is my question about this problem.
It would be nice if the linux-kernel would support the tablet touchscreen by
default.
My kernel is 4.15.0-33-generic.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-33-generic 4.15.0-33.36
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-33-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: bytcrrt5651 [bytcr-rt5651], device 0: 3 []
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vegito 1554 F pulseaudio
/dev/snd/controlC0: vegito 1554 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
Mixer name : ''
Components : ''
Controls : 11
Simple ctrls : 1
Card1.Amixer.info:
Card hw:1 'bytcrrt5651'/'bytcr-rt5651'
Mixer name : ''
Components : ''
Controls : 243
Simple ctrls : 213
CurrentDesktop: LXDE
Date: Tue Sep 4 09:57:45 2018
HibernationDevice: RESUME=UUID=f8f953f2-ceb9-4989-9564-a4ba2fed3fd4
InstallationDate: Installed on 2018-08-21 (13 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MEDIACOM WinPad 7 W10 - WPW700
PciMultimedia:
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-33-generic N/A
linux-backports-modules-4.15.0-33-generic N/A
linux-firmware 1.173.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: r8723bs
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: MC.G.WI71C.MGBMRBA03
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name
dmi.board.vendor: Type2 - Board Manufacturer
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDECorp.:bvrMC.G.WI71C.MGBMRBA03:bd11/16/2015:svnMEDIACOM:pnWinPad7W10-WPW700:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Type1 - Family
dmi.product.name: WinPad 7 W10 - WPW700
dmi.product.version: Type1 - TBD by OEM
dmi.sys.vendor: MEDIACOM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790594/+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 1790594] Re: The system is not able to detect the touchsreen
And the silead_dmi.c that i attached.
BUT using dmesg | grep silead it seems that is using the backup firmware
which is the same but with the different name.
And i can' t use the photocamera and the speakers .
--
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/1790594
Title:
The system is not able to detect the touchsreen
Status in linux package in Ubuntu:
Incomplete
Bug description:
I' m using a tablet that is sold with Windows 10.
The firmware extracted from the special driver are already available here
https://github.com/onitake/gsl-firmware/tree/master/firmware/trekstor/surftab7old.
(I discovered that the Mediacom drivers are the same as those for TrekStor, a
company that also works with Mediacom.Mediacom Winpad 7.0 W700 corresponds at
SurfTab wintron 7.0 ST70416-6).
That repository states that i need to recompile the kernel.
I don' t know how here
https://unix.stackexchange.com/questions/466571/recompile-a-kernel-including-a-firmware?noredirect=1#comment850048_466571
there is my question about this problem.
It would be nice if the linux-kernel would support the tablet touchscreen by
default.
My kernel is 4.15.0-33-generic.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-33-generic 4.15.0-33.36
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-33-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: bytcrrt5651 [bytcr-rt5651], device 0: 3 []
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vegito 1554 F pulseaudio
/dev/snd/controlC0: vegito 1554 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
Mixer name : ''
Components : ''
Controls : 11
Simple ctrls : 1
Card1.Amixer.info:
Card hw:1 'bytcrrt5651'/'bytcr-rt5651'
Mixer name : ''
Components : ''
Controls : 243
Simple ctrls : 213
CurrentDesktop: LXDE
Date: Tue Sep 4 09:57:45 2018
HibernationDevice: RESUME=UUID=f8f953f2-ceb9-4989-9564-a4ba2fed3fd4
InstallationDate: Installed on 2018-08-21 (13 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MEDIACOM WinPad 7 W10 - WPW700
PciMultimedia:
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-33-generic N/A
linux-backports-modules-4.15.0-33-generic N/A
linux-firmware 1.173.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: r8723bs
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: MC.G.WI71C.MGBMRBA03
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name
dmi.board.vendor: Type2 - Board Manufacturer
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDECorp.:bvrMC.G.WI71C.MGBMRBA03:bd11/16/2015:svnMEDIACOM:pnWinPad7W10-WPW700:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Type1 - Family
dmi.product.name: WinPad 7 W10 - WPW700
dmi.product.version: Type1 - TBD by OEM
dmi.sys.vendor: MEDIACOM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790594/+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 1779817] Re: r8169 no internet after suspending
I've found these discussion, installed latest r8169 driver and at last internet begins to restore after suspending! Before that nothing help, including "modprobe -r r8169" and restart NetworkManager. I'm happy! ))) -- 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/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: ===SRU Justification=== [Impact] r8169 failed to establish connection after the fix for LP: #1752772 landed. [Fix] Accepts BIOS WoL settings again, and disables MSI-X for certain chip revisions. [Test] Users confirmed the fix worked for them. [Regression Potential] Low. This brings back the old behavior for both WoL and MSI. ===Original Bug Report=== When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+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 1790594] Re: The system is not able to detect the touchsreen
Thanks to owner of the repository we found the solution adding this to the
drivers/platform/x86/silead_dmi.c:
First this section
but is optional if i understood right the important things is to have a DMI
match:
static const struct property_entry mediacom_w700_props[] = {
PROPERTY_ENTRY_U32("touchscreen-size-x", 884),
PROPERTY_ENTRY_U32("touchscreen-size-y", 632),
PROPERTY_ENTRY_STRING("firmware-name",
"gsl1686-surftab-wintron70-st70416-6.fw"),
PROPERTY_ENTRY_U32("silead,max-fingers", 10),
PROPERTY_ENTRY_BOOL("silead,home-button"),
{ }
};
The the DMI_MARTCH section:
{
/* Mediacom WinPad 7.0 W700 */
.driver_data = (void *)_wintron70_st70416_6_data,
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "MEDIACOM"),
DMI_MATCH(DMI_PRODUCT_NAME, "WinPad 7 W10 - WPW700"),
},
},
--
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/1790594
Title:
The system is not able to detect the touchsreen
Status in linux package in Ubuntu:
Incomplete
Bug description:
I' m using a tablet that is sold with Windows 10.
The firmware extracted from the special driver are already available here
https://github.com/onitake/gsl-firmware/tree/master/firmware/trekstor/surftab7old.
(I discovered that the Mediacom drivers are the same as those for TrekStor, a
company that also works with Mediacom.Mediacom Winpad 7.0 W700 corresponds at
SurfTab wintron 7.0 ST70416-6).
That repository states that i need to recompile the kernel.
I don' t know how here
https://unix.stackexchange.com/questions/466571/recompile-a-kernel-including-a-firmware?noredirect=1#comment850048_466571
there is my question about this problem.
It would be nice if the linux-kernel would support the tablet touchscreen by
default.
My kernel is 4.15.0-33-generic.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-33-generic 4.15.0-33.36
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-33-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: bytcrrt5651 [bytcr-rt5651], device 0: 3 []
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vegito 1554 F pulseaudio
/dev/snd/controlC0: vegito 1554 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
Mixer name : ''
Components : ''
Controls : 11
Simple ctrls : 1
Card1.Amixer.info:
Card hw:1 'bytcrrt5651'/'bytcr-rt5651'
Mixer name : ''
Components : ''
Controls : 243
Simple ctrls : 213
CurrentDesktop: LXDE
Date: Tue Sep 4 09:57:45 2018
HibernationDevice: RESUME=UUID=f8f953f2-ceb9-4989-9564-a4ba2fed3fd4
InstallationDate: Installed on 2018-08-21 (13 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MEDIACOM WinPad 7 W10 - WPW700
PciMultimedia:
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-33-generic N/A
linux-backports-modules-4.15.0-33-generic N/A
linux-firmware 1.173.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: r8723bs
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: MC.G.WI71C.MGBMRBA03
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name
dmi.board.vendor: Type2 - Board Manufacturer
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDECorp.:bvrMC.G.WI71C.MGBMRBA03:bd11/16/2015:svnMEDIACOM:pnWinPad7W10-WPW700:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Type1 - Family
dmi.product.name: WinPad 7 W10 - WPW700
dmi.product.version: Type1 - TBD by OEM
dmi.sys.vendor:
[Kernel-packages] [Bug 1790594] Re: The system is not able to detect the touchsreen
And you must have the firmware in
/lib/firmware/silead/.fw.
So you can add the firmware to the official kernel?
https://github.com/onitake/gsl-firmware/tree/master/firmware/linux
** Attachment added: "silead_dmi.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790594/+attachment/5186445/+files/silead_dmi.c
--
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/1790594
Title:
The system is not able to detect the touchsreen
Status in linux package in Ubuntu:
Incomplete
Bug description:
I' m using a tablet that is sold with Windows 10.
The firmware extracted from the special driver are already available here
https://github.com/onitake/gsl-firmware/tree/master/firmware/trekstor/surftab7old.
(I discovered that the Mediacom drivers are the same as those for TrekStor, a
company that also works with Mediacom.Mediacom Winpad 7.0 W700 corresponds at
SurfTab wintron 7.0 ST70416-6).
That repository states that i need to recompile the kernel.
I don' t know how here
https://unix.stackexchange.com/questions/466571/recompile-a-kernel-including-a-firmware?noredirect=1#comment850048_466571
there is my question about this problem.
It would be nice if the linux-kernel would support the tablet touchscreen by
default.
My kernel is 4.15.0-33-generic.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-33-generic 4.15.0-33.36
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-33-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: bytcrrt5651 [bytcr-rt5651], device 0: 3 []
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vegito 1554 F pulseaudio
/dev/snd/controlC0: vegito 1554 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
Mixer name : ''
Components : ''
Controls : 11
Simple ctrls : 1
Card1.Amixer.info:
Card hw:1 'bytcrrt5651'/'bytcr-rt5651'
Mixer name : ''
Components : ''
Controls : 243
Simple ctrls : 213
CurrentDesktop: LXDE
Date: Tue Sep 4 09:57:45 2018
HibernationDevice: RESUME=UUID=f8f953f2-ceb9-4989-9564-a4ba2fed3fd4
InstallationDate: Installed on 2018-08-21 (13 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MEDIACOM WinPad 7 W10 - WPW700
PciMultimedia:
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-33-generic N/A
linux-backports-modules-4.15.0-33-generic N/A
linux-firmware 1.173.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: r8723bs
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: MC.G.WI71C.MGBMRBA03
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name
dmi.board.vendor: Type2 - Board Manufacturer
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDECorp.:bvrMC.G.WI71C.MGBMRBA03:bd11/16/2015:svnMEDIACOM:pnWinPad7W10-WPW700:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Type1 - Family
dmi.product.name: WinPad 7 W10 - WPW700
dmi.product.version: Type1 - TBD by OEM
dmi.sys.vendor: MEDIACOM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790594/+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 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows
"It turned out that the power limits in Windows are broken, and the ones in Linux are correct, so this bug is in fact Invalid." Where do I find that? -- 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/1763144 Title: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows Status in linux package in Ubuntu: Invalid Bug description: A ThinkPad T480s under windows has a power limit of 44W, both short and long term, with a thermal maximum of about 93C or so. Under Linux, the power limits are 44W and 15W (short) or so, and the thermal limit is 80C, causing a significant performance loss. Looking at MSR and MCHBAR values, we can see that the values are correctly at 44W in the MSR, but the MCHBAR is set to a lower value: $ sudo rdmsr -a 0x610 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0 0x0042816000dd8078 Setting the MCHBAR to the same value as the MSR register solves the problem. At some point intel-rapl seems to reduce overall frequency to 600 MHz, though. The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24 -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting in performance comparative to Windows. Most of the analysis is based on the analysis in https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/ This applies to all bionic kernels I have tested so far, including Ubuntu 4.15.0-13.14-generic 4.15.10 --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: jak5881 F...m pulseaudio /dev/snd/controlC2: jak5881 F pulseaudio /dev/snd/controlC1: jak5881 F pulseaudio /dev/snd/controlC0: jak5881 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-14 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET31W (1.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 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:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+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 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image
** Tags added: regression-update ** Description changed: Repro: 1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully updated -> Keyboard backlight should come on or change but doesn't. The gnome- - shell icon for the keyboard backlight appears for both keys, but the - icon's "progress" bar is not visible. + shell pop-up icon for the keyboard backlight appears for both keys, but + the icon's "progress" bar is not visible. Kernel version is linux-image-4.17.0-9-generic This is the same in X and Wayland session. In case it matters, Nvidia binary drivers are installed but Nvidia is switched off via Prime setting in nvidia-settings. Running with Intel drivers The keyboard backlight works perfectly when booting from the 18.04.1 desktop live image. When turning on light with 18.04.1, it is off again after rebooting into 18.10. (However 18.04.1 seems to freeze when shutting down from menu, I have to hard-shut it off). Most other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for the airplane mode key. However the airplane mode key only fails in gnome-shell but works on the console (this is filed as https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1791367) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: angela16196 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 22:08:12 2018 InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791372 Title: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image Status in linux package in Ubuntu: Confirmed Bug description: Repro: 1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully updated -> Keyboard backlight should come on or change but doesn't. The gnome-shell pop-up icon for the keyboard backlight appears for both keys, but the icon's "progress" bar is not visible. Kernel version is linux-image-4.17.0-9-generic This is the same in X and Wayland session. In case it matters, Nvidia binary drivers are installed but Nvidia is switched off via Prime setting in nvidia-settings. Running with Intel drivers The keyboard backlight works perfectly when booting from the 18.04.1 desktop live image. When turning on light with 18.04.1, it is off again after rebooting into 18.10. (However 18.04.1 seems to freeze when shutting down from menu, I have to hard-shut it off). Most other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for the airplane mode key. However the airplane mode key only fails in gnome-shell but works on the console (this is filed as https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1791367) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname:
[Kernel-packages] [Bug 1790515] Re: black screen on ubuntu GTX 1050 eGPU
please try the latest 396 from ubuntu graphics ppa -- 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/1790515 Title: black screen on ubuntu GTX 1050 eGPU Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I'm using a laptop lenovo thinkpad T410 with intel graphics and egpu + GTX 1050. (using expresscard or mini pcie both failed) When I install the 390 driver my graphical display fails. I know that egpu is not the best solution but for some people it works. I tried: 390, 396, 384 nvidia drivers from ppa and from NVIDIA (.run) Ubuntu and Xubuntu (18, 17, 16) using gdm3 and lightgdm blacklist nouveau and everything similar Sometimes Ubuntu 18.04 freeze using live usb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790515/+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
