[Kernel-packages] [Bug 1766614] Re: linux-aws: 4.4.0-1056.65 -proposed tracker
4.4.0-1056.65 - aws Regression test CMPL. Issue to note in x86_64 (aws): libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 1, bad config 3, only spotted on t2.small, passed on the rest ubuntu_kvm_unit_tests - test skipped due to no KVM support ubuntu_lxc - lxc-test-ubunut failed (Failed to start networking in ubuntu-cloud container), only spotted on t2.small, passed on the rest ubuntu_qrt_apparmor - longpath test failed with permission denied (bug 1768784) Skipped / blacklisted: * ubuntu_ltp * ubuntu_seccomp * ubuntu_sysdig_smoke_test * ubuntu_zram_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1766614 Title: linux-aws: 4.4.0-1056.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1766604 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766614/+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 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush
Hi Breno, Sorry for the late reply. Regarding Xenial, we updated the kernel to a later upstream stable version since you posted the patches. 4.4.0-123.147 from -proposed should be in sync with 4.4.128 now and your patches don't apply cleanly any longer. When updating to 4.4.117 we reverted a bunch of SAUCE rfi-flush patches and replaced them with the upstream versions. Is there a possibility that your patches are no longer required with those updates? Thanks ...Juerg -- 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/1744173 Title: artful: rfi-flush: Switch to new linear fallback flush Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Bug description: Change flush from congruence-first with dependencies to linear with no dependencies, which increases flush performance by 8x on P8, and 3x on P9 (as measured with null syscall loop, which will have the flush area in the L2). The flush also becomes simpler and more adaptable to different cache geometries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+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 1769733] Re: Third screen not working displayport amd ryzen 5 2400g apu
I will try to test the latest kernel and see if that will fix it. Also I will add in the logs. I'll do that in 8~10 hours from now. -- 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/1769733 Title: Third screen not working displayport amd ryzen 5 2400g apu Status in linux package in Ubuntu: Incomplete Bug description: All relevant information can be found in this post: https://askubuntu.com/questions/1033287/cant-get-my-third-screen-working-ubuntu-18-04-amd-ryzen-5-2400g All errors and tries have been posted in that post. the problem is reletaed to the drivers regarding the amd ryzen 5 2400g APU, not all three of my screens turn on. only the dvi-d port and gdmi port give me output but the display port gives me a blank screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 21:52:25 2018 InstallationDate: Installed on 2018-05-06 (0 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/1769733/+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 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
confirmed in xubuntu 18.04 Linux bart 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [261304.111515] nouveau :04:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 [261304.111529] nouveau :04:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 [261304.111532] nouveau :04:00.0: msvld: unable to load firmware data [261304.111538] nouveau :04:00.0: msvld: init failed, -19 [340065.706109] perf: interrupt took too long (9727 > 9721), lowering kernel.perf_event_max_sample_rate to 20500 [348688.301567] nouveau :04:00.0: fb: trapped read at 01008bc04c on channel -1 [3fee unknown] engine 06 [BAR] client 08 [PFIFO_READ] subclient 01 [IN] reason 0002 [PAGE_NOT_PRESENT] [348698.597698] nouveau :04:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 [348698.597714] nouveau :04:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 [348698.597717] nouveau :04:00.0: msvld: unable to load firmware data [348698.597723] nouveau :04:00.0: msvld: init failed, -19 Elvis -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Status in linux package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Won't Fix Bug description: [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Hello, from time to time I find this annoying messages in dmesg in various Ubuntu versions (I believe since 16.04 or 16.10 up until now, including Bionic Beaver daily build). From time to time, the gdm3 crashes. The current HW/SW setup will be described below. I cannot replicate the situation, but it happens. See the excerpt from dmesg output below. [9.386558] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready [9.399079] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12 [9.399134] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13 [9.399208] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14 [9.399274] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15 [ 12.312741] r8169 :03:00.0 enp3s0: link up [ 12.312748] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready [ 13.439863] rfkill: input handler disabled [ 15.125569] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 136.559618] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 136.559619] nouveau :01:00.0: msvld: unable to load firmware data [ 136.559622] nouveau :01:00.0: msvld: init failed, -19 [ 1376.746130] lp: driver loaded but no devices found [ 1376.756790] st: Version 20160209, fixed bufsize 32768, s/g segs 256 [ 1381.398605] do_IRQ: 1.37 No irq handler for vector rr HW setup: Asrock Extreme 6 Z97 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 3563 MHz nVidia GK107 [GeForce GT 640] SW setup: Linux bionic 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@bionic:~# lsmod | grep nouveau nouveau 1716224 5 i2c_algo_bit 16384 1 nouveau ttm 106496 1 nouveau drm_kms_helper167936 1 nouveau mxm_wmi16384 1 nouveau drm 401408 8 nouveau,ttm,drm_kms_helper wmi24576 2 mxm_wmi,nouveau video 40960 1 nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+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 1766610] Re: linux-kvm: 4.4.0-1022.27 -proposed tracker
bug 1768784 is a test case issue, giving this a green light. ** Tags added: regression-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1766610 Title: linux-kvm: 4.4.0-1022.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1766604 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766610/+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
Re: [Kernel-packages] [Bug 1710548] Re: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 Webcam/Zoneminder/Startech
Hi, It looks like someone attempted a fix, but it was beset by a typo. I fixed the typo and compiled the kernel and the issue was resolved. I detailed the typo in the original thread. Can you run this up the flagpole for me? I don't know how to get in touch with the devs. Thank you, -Jeff On Sunday, March 25, 2018, 9:36:06 PM PDT, Kai-Heng Feng wrote: This was my attempt to send a quirk patch: https://lkml.org/lkml/2017/9/6/516 -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1710548 Title: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 Webcam/Zoneminder/Startech Status in linux package in Ubuntu: Confirmed Bug description: Building zoneminder server. I think I stumbled on a kernel bug. The suggestion is that the popular Renesas / NEC - µPD720202 may need "quirk" in the kernel. Wiped the drive. Loaded 17.04 Server Now getting 100's of messages in DMESG complaining of thousands of errors: [96415.044917] handle_tx_event: 516 callbacks suppressed [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Messages suggest "quirk" is the solution. a)Researched usb 3.0 "quirk' b)Discovered it's really a "thing" c)Couldn't find recipe for patching kernel for NEC/Renasas "quirk" fix. [EDIT]: Note C920 webcam is USB 2.0. Note DMESG errors disappear when cam is plug into motherboard USB 2.0 ports. Anecdotes suggest Nec/Renasas firmware is to blame. a) Kernel indicates 2024 firmaware b) Startech website has 2026 firmware. c) SIDEBAR: WindowCentric GUI instructions do not translate between ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing runfile for effective firmware update of all 4 controllers. Yes, for the 4 channel controller, count them: 4 update iterations. d) Firmware updated. Rebooted with new Startech/Nec/Renases 2026 firmware. SAME OLD PLETHORA OF ERRORS I give up. It may well be worth noting that there are no errors from DMESG until some seconds after the first webcam is attached to the Startech, while zoneminder is running. I think the file attached represents DMESG immediately before the errors start going nuts. My theory is that ZM does lazy polls on missing cams but once it gets a hold of the cam and sucking data the quirk bug surfaces. ProblemType: Bug DistroRelease: Ubuntu 17.04,17.10,18.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36 also in 4.13 and 4.15 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jeff 12776 F pulseaudio /dev/snd/controlC3: jeff 12776 F pulseaudio /dev/snd/controlC2: jeff 12776 F pulseaudio /dev/snd/controlC1: jeff 12776 F pulseaudio Date: Sun Aug 13 16:48:41 2017 MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware 1.164.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2a dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+subscriptions -- 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/1710548 Title: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logit
[Kernel-packages] [Bug 1758496] Re: Backlight does not work on a MacBookAir3, 2
Please file an upstream bug at https://bugzilla.kernel.org/ Product: ACPI Component: Power-Video -- 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/1758496 Title: Backlight does not work on a MacBookAir3,2 Status in linux package in Ubuntu: Incomplete Bug description: Backlight control does not work and there are no entries in /sys/class/backlight. When I boot my system with the option GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=vendor" I can change the brightness with the command xrandr on a terminal. I attach all the system information about this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: victor 2932 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 07:22:05 2018 InstallationDate: Installed on 2018-03-04 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Apple Inc. MacBookAir3,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=dd2bcce2-7d14-4df7-b7c8-6aea4fbb9c13 ro acpi_backlight=vendor RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA31.88Z.0061.B01.1011181342 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-942C5DF58193131B dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir3,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942C5DF58193131B dmi.modalias: dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B01.1011181342:bd11/18/10:svnAppleInc.:pnMacBookAir3,2:pvr1.0:rvnAppleInc.:rnMac-942C5DF58193131B:rvrMacBookAir3,2:cvnAppleInc.:ct10:cvrMac-942C5DF58193131B: dmi.product.family: MacBook dmi.product.name: MacBookAir3,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758496/+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 1763429] Re: Lenovo Yoga 720 does not shutdown with wifi enabled
Can you try latest firmware in [1]? [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/ -- 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/1763429 Title: Lenovo Yoga 720 does not shutdown with wifi enabled Status in linux package in Ubuntu: Incomplete Bug description: Whenever I try to shutdown or reboot the system while the internal wifi card is enabled, the systems hangs (system does not switch to command line mode, only possible to reboot using Syrq-Key+B, even Sysrq+O does not work). When I disable the wifi card using network manager before shutting down it works fine. The system runs in UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe1448 F pulseaudio CurrentDesktop: XFCE Date: Thu Apr 12 17:36:34 2018 InstallationDate: Installed on 2018-04-09 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=3ba7e23d-37e2-4bef-b60a-c7509a7b487c ro reboot=cold 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN22WW(V1.07) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN22WW(V1.07):bd06/22/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763429/+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 1205791] Re: Dell Vostro V131: special keys not working
Whoopie, Will you make a pull request to systemd? -- 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/1205791 Title: Dell Vostro V131: special keys not working Status in udev: New Status in linux package in Ubuntu: Confirmed Bug description: Bug filed, following conversation on IRC at: http://irclogs.ubuntu.com/2013/07/28/%23ubuntu-devel.html#t07:45 I own a Dell Vostro V131. This model has 3 special hotkeys (quick launch keys: http://www.notebookcheck.net/fileadmin/_migrated/pics/v131tastatur_01.jpg There are documented in page 1 of the manual: ftp://ftp.dell.com/Manuals/all- products/esuprt_laptop/esuprt_vostro_notebook/vostro-v131_Setup %20Guide_en-us.pdf as being: 1. "Windows mobility center" (this hotkey generates [Mod]+[x]) 2. "Dell support center" 3. "Dell instant launch manager" This was previous raised at: http://www.mail-archive.com/platform-driver-x86@vger.kernel.org/msg03124.html http://www.mail-archive.com/platform-driver-x86@vger.kernel.org/msg0.html The "Dell support center" key generates keycode 0xEE, but misses release event. I got it working with an udev "keyboard force release" quirk, see attached patch in the '' email. However, the "Dell instant launch manager" key doesn't generate anything, neither through dell-wmi nor i8042. It's the rightmost button in the right upper corner of the keyboard. The ACPI interrupt- count appears to increment, as seen with: http://www.mail-archive.com/platform-driver-x86@vger.kernel.org/msg03126.html watch -n 0,1 cat /proc/interrupts To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/1205791/+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 1710548] Re: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 Webcam/Zoneminder/Startech
Yeah it's a typo. -- 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/1710548 Title: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 Webcam/Zoneminder/Startech Status in linux package in Ubuntu: Confirmed Bug description: Building zoneminder server. I think I stumbled on a kernel bug. The suggestion is that the popular Renesas / NEC - µPD720202 may need "quirk" in the kernel. Wiped the drive. Loaded 17.04 Server Now getting 100's of messages in DMESG complaining of thousands of errors: [96415.044917] handle_tx_event: 516 callbacks suppressed [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Messages suggest "quirk" is the solution. a)Researched usb 3.0 "quirk' b)Discovered it's really a "thing" c)Couldn't find recipe for patching kernel for NEC/Renasas "quirk" fix. [EDIT]: Note C920 webcam is USB 2.0. Note DMESG errors disappear when cam is plug into motherboard USB 2.0 ports. Anecdotes suggest Nec/Renasas firmware is to blame. a) Kernel indicates 2024 firmaware b) Startech website has 2026 firmware. c) SIDEBAR: WindowCentric GUI instructions do not translate between ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing runfile for effective firmware update of all 4 controllers. Yes, for the 4 channel controller, count them: 4 update iterations. d) Firmware updated. Rebooted with new Startech/Nec/Renases 2026 firmware. SAME OLD PLETHORA OF ERRORS I give up. It may well be worth noting that there are no errors from DMESG until some seconds after the first webcam is attached to the Startech, while zoneminder is running. I think the file attached represents DMESG immediately before the errors start going nuts. My theory is that ZM does lazy polls on missing cams but once it gets a hold of the cam and sucking data the quirk bug surfaces. ProblemType: Bug DistroRelease: Ubuntu 17.04,17.10,18.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36 also in 4.13 and 4.15 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeff 12776 F pulseaudio /dev/snd/controlC3: jeff 12776 F pulseaudio /dev/snd/controlC2: jeff 12776 F pulseaudio /dev/snd/controlC1: jeff 12776 F pulseaudio Date: Sun Aug 13 16:48:41 2017 MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware 1.164.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2a dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+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 1769816] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135862/+files/WifiSyslog.txt ** 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/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1761693] Re: Wifi realtek 8822be BUG <=18.04
Please file an upstream bug at https://bugzilla.kernel.org/ Product: Drivers Component: network-wireless -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761693 Title: Wifi realtek 8822be BUG <=18.04 Status in linux package in Ubuntu: Confirmed Bug description: I am a regular linux user and i have bought last week a new computer that comes with the realtek 8822be wireless chipset. While using Ubuntu 16.04(Kernel version updated to 4.14 where we started to have support to this chipset) or both 18.04 beta 1 and final version i found a problem: 1º when i boot all this versions with the kernel version >= 4.14, i found out that the driver is instaled and she is detected in the network manager.Anyway, when i used she won´t work and in few secconds later will shutdown. When i go to the wifi settings i can´t find networks! 2º I use modprobe so that i can manipulate my drivers/modules and i can start to work with my wifi card: -> modprobe -rv r8822be -> modprobe -v r8822be aspm=0 The problem is that when i connect to a 5ghz frequency router, i have very slow download speed 8 mbps max (Usually my speed is approximately 200/210 mbps in wifi mode).In the outher hand when i connect to a 2.4ghz frequency router it works fine! Thanks Best regards --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teste 1285 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=9fdace6b-915c-4770-8261-aa8dcaa735b1 InstallationDate: Installed on 2018-04-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: ASUSTeK COMPUTER INC. X411UN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=1d0c4a1b-32fe-43b2-ae21-2b0d9101e5fc ro 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 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/04/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X411UN.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X411UN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX411UN.300:bd08/04/2017:svnASUSTeKCOMPUTERINC.:pnX411UN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX411UN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X411UN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761693/+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 1769816] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135851/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135858/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135860/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135855/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135852/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135861/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135857/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135854/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] HookError_generic.txt
apport information ** Attachment added: "HookError_generic.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135853/+files/HookError_generic.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135856/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135859/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrewm2561 F pulseaudio /dev/snd/controlC0: andrewm2561 F pulseaudio DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 InstallationDate: Installed on 2016-09-10 (604 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: TOSHIBA Satellite P50-A NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.157.17 Tags: sylvia sylvia Uname: Linux 4.15.0-15-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P50-A dmi.product.version: PSPMHA-01D00L dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] Re: bootup low resolution can't unlock crypt volume
apport information ** Tags added: apport-collected sylvia ** Description changed: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx + --- + ApportVersion: 2.20.1-0ubuntu2.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: andrewm2561 F pulseaudio + /dev/snd/controlC0: andrewm2561 F pulseaudio + DistroRelease: Linux 18.3 + HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409 + InstallationDate: Installed on 2016-09-10 (604 days ago) + InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 + MachineType: TOSHIBA Satellite P50-A + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_AU:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_AU.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/mint--vg-root ro quiet splash + ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.15.0-15-generic N/A + linux-backports-modules-4.15.0-15-generic N/A + linux-firmware 1.157.17 + Tags: sylvia sylvia + Uname: Linux 4.15.0-15-generic x86_64 + UnreportableReason: The report belongs to a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: False + dmi.bios.date: 09/19/2014 + dmi.bios.vendor: TOSHIBA + dmi.bios.version: 1.90 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: VG10S + dmi.board.vendor: TOSHIBA + dmi.board.version: To be filled by O.E.M. + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: TOSHIBA + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: + dmi.product.family: PEGA Family + dmi.product.name: Satellite P50-A + dmi.product.version: PSPMHA-01D00L + dmi.sys.vendor: TOSHIBA ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1769816/+attachment/5135850/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Confirmed Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx --- Appo
[Kernel-packages] [Bug 1769816] Re: bootup low resolution can't unlock crypt volume
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+attachment/5135848/+files/version.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/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Incomplete Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1765213] Re: e1000e hang bug, locks up host
Does this also happen to Bionic? Also can you try latest mainline kernel (v4.17-rc3)? -- 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/1765213 Title: e1000e hang bug, locks up host Status in linux package in Ubuntu: Incomplete Bug description: I have a rough switch in my home network that sometimes floods the network with PAUSE frames. https://en.wikipedia.org/wiki/Ethernet_flow_control#Pause_frame This has the effect that it locks up many nodes in my home-network, even after I restarted the rough switch. Only way to recover is to physically reboot the nodes affected aswell. $ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 Host helium === Linux helium 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux nothing in the kernlog, likely that disk was unable to flush before total lock-up last entry in syslog (which is crowded on this host) is Apr 18 13:43:52, follwed by a bunch of \0 bytes $ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: on (auto) Cannot get wake-on-lan settings: Operation not permitted Current message level: 0x0007 (7) drv probe link Link detected: yes $ ethtool -i eth0 driver: e1000e version: 3.2.6-k firmware-version: 0.8-4 expansion-rom-version: bus-info: :00:1f.6 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no Host lithium Linux lithium 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Apr 18 13:54:29 lithium kernel: [234281.728575] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Apr 18 13:54:29 lithium kernel: [234281.728595] [ cut here ] Apr 18 13:54:29 lithium kernel: [234281.728602] WARNING: CPU: 2 PID: 16114 at /build/linux-cg_do7/linux-4.13.0/net/sched/sch_generic.c:316 dev_watchdog+0x224/0x230 Apr 18 13:54:29 lithium kernel: [234281.728603] Modules linked in: binfmt_misc nls_iso8859_1 wmi_bmof intel_rapl snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclam p snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel kvm_intel snd_hda_codec kvm snd_hda_core snd_hwdep snd_pcm snd_timer irqbypass snd intel_cstate intel_rapl_p erf soundcore nvidia_uvm(POE) hci_uart btbcm serdev shpchp btqca btintel bluetooth mac_hid ecdh_generic mei_me intel_lpss_acpi acpi_pad intel_lpss mei wmi acpi_als kfif o_buf industrialio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi coretemp ip_tables x_tables autofs4 btrfs raid10 raid456 asy nc_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nvidia_drm(POE) crct10dif_pclmul crc32_pclmul nvidia_modeset (POE) Apr 18 13:54:29 lithium kernel: [234281.728635] ghash_clmulni_intel pcbc i915 e1000e aesni_intel ptp pps_core aes_x86_64 crypto_simd glue_helper cryptd nvidia(POE) i2c _algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci ipmi_devintf ipmi_msghandler video i2c_hid hid Apr 18 13:54:29 lithium kernel: [234281.728648] CPU: 2 PID: 16114 Comm: kworker/2:0 Tainted: P U W OE 4.13.0-38-generic #43-Ubuntu Apr 18 13:54:29 lithium kernel: [234281.728648] Hardware name: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming K3/Z370 AORUS Gaming K3-CF, BIOS F3 09/22/2017 Apr 18 13:54:29 lithium kernel: [234281.728836] Workqueue: events os_execute_work_item [nvidia] Apr 18 13:54:29 lithium kernel: [234281.728838] task: 9a9e6e8aaf80 task.stack: b1ce9077c000 Apr 18 13:54:29 lithium kernel: [234281.728841] RIP: 0010:dev_watchdog+0x224/0x230 Apr 18 13:54:29 lithium kernel: [234281.728842] RSP: :9a9e7f503e50 EFLAGS: 00010282 Apr 18 13:54:29 lithium kernel: [234281.728842] RAX: 003a RBX: RCX: Apr 18 13:54:29 lithium kernel: [234281.728843] RDX: RSI: 9a9e7f516578 RDI: 9a9e7f516578 Apr 18 13:54:29 lithium kernel: [234281
[Kernel-packages] [Bug 1761105] Re: Ethernet Cable Unplugged/Connecting on Lenovo Thinkpad T430
This should be fixed by 4.13.0-40.45. -- 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/1761105 Title: Ethernet Cable Unplugged/Connecting on Lenovo Thinkpad T430 Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After the kernel update, Ethernet is not working on Lenovo Thinkpad T430. Looping on Unplugged/connecting as if cable fault. Tested cables and switch. Reverting back to Kernel 4.13.0-37-generic solves the problem completely. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sharif 3235 F pulseaudio /dev/snd/controlC1: sharif 3235 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 4 10:35:32 2018 MachineType: LENOVO 2349NL4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=8496cc43-27ca-48ea-ad12-21119c1e7263 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB4WW (2.74 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349NL4 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB4WW(2.74):bd09/25/2017:svnLENOVO:pn2349NL4:pvrThinkPadT430:rvnLENOVO:rn2349NL4:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349NL4 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761105/+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 1769816] Re: bootup low resolution can't unlock crypt volume
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+attachment/5135849/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Incomplete Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1737423] Re: With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video memory misdetected as 512 Mb : result was kernel panic in worst case and memory crash in best
Can you try v4.17-rc3? -- 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/1737423 Title: With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video memory misdetected as 512 Mb : result was kernel panic in worst case and memory crash in best case Status in linux package in Ubuntu: Confirmed Bug description: Under XP card detected as PCI\VEN_10DE&DEV_0221&SUBSYS_&REV_A1\4&3A321F38&0&48F0 PCI\VEN_10DE&DEV_0221&SUBSYS_&REV_A1\4&3A321F38&0&48F0 PCI\VEN_10DE&DEV_0221&SUBSYS_&REV_A1 PCI\VEN_10DE&DEV_0221&CC_03 memory range 9400 94FF memory range C000 DFFF memory range 9200 92FF IRQ 09 IO range 03B0 03BB IO range 03C0 03DF memory range 000A 000B Processeur graphique :GeForce 6200 Version du pilote : 307.83 Prise en charge DirectX : 9.0c Horloge principale : 300 MHz Débit de données mémoire :1064 MHz Interface de mémoire :64 bits Mémoire : 256 Mo Type de mémoire : DDR2 Version BIOS vidéo : 5.44.A2.10.26 IRQ : 9 Bus : PCI correctly detected as 256Mb and working Under linux file /var/log/Xorg.0.log contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @ 0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @ 0x/131072 card bad detection ... 0xc000/536870912 correct adress, wrong size 536870912 soit 512Mo output of: sudo lshw -C display; lsb_release -a; uname -a is jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a [sudo] password for jean: *-display description: Display controller produit: 82865G Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 02 bits: 32 bits horloge: 33MHz fonctionnalités: pm bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:16 mémoire:a000-a7ff mémoire:9000-9007 portE/S:1800(taille=8) *-display description: VGA compatible controller produit: NV44A [GeForce 6200] fabriquant: NVIDIA Corporation identifiant matériel: 9 information bus: pci@:03:09.0 version: a1 bits: 32 bits horloge: 66MHz fonctionnalités: pm vga_controller bus_master cap_list rom configuration: driver=nouveau latency=40 maxlatency=1 mingnt=5 ressources: irq:21 mémoire:9400-94ff mémoire:c000-dfff mémoire:9200-92ff mémoire:e000-e001 No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename:trusty Linux jean-Soisy 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 11:56:31 UTC 2017 i686 i686 i686 GNU/Linux Attempted to find where the memory size detection lies in the code, but was too far in the labyrinth for me. Regards Jean COLIN --- ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jean 2206 F pulseaudio /dev/snd/controlC0: jean 2206 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2ae1454f-4490-4a9a-aea5-55daa49c243c InstallationDate: Installed on 2015-08-08 (985 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820) MachineType: IBM 8429RG7 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-144-generic root=UUID=0f7280ad-8482-48be-9433-13ca09f7304a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-144-generic N/A linux-backports-modules-3.13.0-144-generic N/A linux-firmware 1.127.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-144-generic i686 UpgradeStatus: Upgraded to trusty on 2015-08-08 (985 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/06/2005 dmi.bios.vendor: IBM dmi.bios.version: 2AKT51AUS dmi.board.name: IBM dmi.board.vendor: IBM dmi.chassis.asset.tag: dmi.chassis.type: 4 dmi.chassis.vendor: IBM dmi.modalias: dmi:bvnIBM:bvr2AKT51AUS:bd07/06/2005:svnIBM:pn8429RG7:pvr:rvnIBM:rnIBM:rvr:cvnIBM:ct4:cvr: dmi.product.name: 8429RG7 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737423/+su
[Kernel-packages] [Bug 1769816] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1769816 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Incomplete Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 1769816] [NEW] bootup low resolution can't unlock crypt volume
Public bug reported: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769816 Title: bootup low resolution can't unlock crypt volume Status in linux package in Ubuntu: Incomplete Bug description: linux-headers-4.15.0-20 On boot, the screen for entering cryptsetup pass phrase looks like vga size and I cannot enter the pass phrase to unlock FDE Booting older kernel works fine. Revert to older kernel for boot with older kernel, have the following inxi details: System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) Desktop: Cinnamon 3.6.7 Distro: Linux Mint 18.3 Sylvia Machine: System: TOSHIBA (portable) product: Satellite P50-A v: PSPMHA-01D00L serial: XXM Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 1.90 date: 09/19/2014 CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK107M [GeForce GT 745M] Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) FAILED: nouveau tty size: 200x60 Advanced Data: N/A for root Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769816/+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 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound
Emmanuel,
This quirk should apply to your webcam:
static const struct usb_device_id usb_interface_quirk_list[] = {
/* Logitech UVC Cameras */
{ USB_VENDOR_AND_INTERFACE_INFO(0x046d, USB_CLASS_VIDEO, 1, 0),
.driver_info = USB_QUIRK_RESET_RESUME },
{ } /* terminating entry must be last */
};
--
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/843431
Title:
Logitech camera microphone does not work / makes "chipmunk" sound
Status in Linux:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Oneiric:
Fix Released
Status in linux package in Debian:
New
Bug description:
Did not know which application to log so feel free to let me know and
I'll upload the correct log. In Natty, this mic worked great. Now,
in the sound control panel, the mic does not show any input level at
all and sound recorder does not record any sound.
edit: I can also confirm the same behavior as Alex Popovskiy. It
either works but plays too fast (high pitch) or it doesn't work at
all.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.91-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Sep 6 20:31:13 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: alex 1594 F pulseaudio
/dev/snd/controlC0: alex 1594 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xf9ef4000 irq 16'
Mixer name : 'VIA VT1708S'
Components : 'HDA:11060397,18490397,0010'
Controls : 36
Simple ctrls : 20
Card1.Amixer.info:
Card hw:1 'U0x46d0x809'/'USB Device 0x46d:0x809 at usb-:00:13.2-6, high
speed'
Mixer name : 'USB Mixer'
Components : 'USB046d:0809'
Controls : 2
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
Capture channels: Mono
Limits: Capture 0 - 6400
Mono: Capture 6400 [100%] [31.00dB] [on]
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=8ccfea11-7ba8-42e2-bc75-a37e20a8c83c
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic
root=UUID=3c8a3aec-07c0-47ad-bab8-0365abb68a42 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
RelatedPackageVersions:
linux-restricted-modules-3.0.0-10-generic N/A
linux-backports-modules-3.0.0-10-generic N/A
linux-firmware1.60
Tags: oneiric running-unity
Uname: Linux 3.0.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/07/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.70
dmi.board.name: M3A770DE
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd09/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A770DE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/843431/+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 1744510] Re: RF mouse (with USB dongle) doesn't work after reboot until I unplug it and plug it back in
Does the mouse movement work again after you click its button? -- 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/1744510 Title: RF mouse (with USB dongle) doesn't work after reboot until I unplug it and plug it back in Status in linux package in Ubuntu: Confirmed Bug description: My wireless mouse doesn't work after I reboot until I unplug its USB dongle and plug it back in. I don't see anything in Xorg.0.log which obviously explains this problem. It looks like the mouse is added to the X server configuration on startup without any problems, at least unless I'm misreading the log, and then the second time it's added, when I unplug it and plug it back in, it looks like the same thing happens in the log, but then the mouse works. This was a problem in 17.04 as well, i.e., it isn't new in 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 20 18:31:15 2018 DistUpgraded: 2018-01-20 12:11:24,767 ERROR Cache can not be locked (E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?) DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:1131] InstallationDate: Installed on 2016-01-16 (735 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Predator G6-710 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2018-01-20 (0 days ago) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jan 20 17:16:47 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744510/+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 1769480] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1769480 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769480 Title: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: how to reproduce: dd the iso to an usb drive and boot from it. List all wifi devices in live-mode and connect to one of it. Use the web for some minutes. Open up the wifi on the top right again and list the available networks - it dont show any others any more. Just the one you are connected to. How to overcome the bug: put the computer into airplane mode and go away from airplane mode again. Or: disconnect the usb wifi device and connect it again. Does this bug exist also on installed 18.04 and updated to last (apt update, apt upgrade, apt dist-upgrade)? Yes What wifi device is been used: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' usbcore: registered new interface driver rt2800usb ... ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 uname -a Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769480/+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 1751398] Re: Brightness keys do nothing, stuck on full brightness
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751398 Title: Brightness keys do nothing, stuck on full brightness Status in linux package in Ubuntu: Expired Bug description: Brightness keys do nothing, stuck on full brightness ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: forge 1895 F pulseaudio CurrentDesktop: Unity Date: Fri Feb 23 19:47:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-23 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: LENOVO 80R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=85451546-daae-4935-b12f-494e677b1dac ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2018-02-23 (0 days ago) dmi.bios.date: 12/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Flex 3-1480 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Flex 3-1480 dmi.modalias: dmi:bvnLENOVO:bvrD3CN29WW:bd12/23/2015:svnLENOVO:pn80R3:pvrFlex3-1480:rvnLENOVO:rnFlex3-1480:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrFlex3-1480: dmi.product.name: 80R3 dmi.product.version: Flex 3-1480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751398/+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 1754353] Re: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40 failed to install/upgrade: unable to open '/lib/modules/4.13.0-36-generic/kernel/drivers/net/ethernet/qlogi
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754353 Title: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40 failed to install/upgrade: unable to open '/lib/modules/4.13.0-36-generic/kernel/drivers/net/ethernet/qlogic/qla3xxx.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Expired Bug description: Failed as soon as I logged in. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1468 F pulseaudio andy 1969 F pulseaudio /dev/snd/controlC1: gdm1468 F pulseaudio andy 1969 F pulseaudio Date: Sat Mar 3 14:17:51 2018 DuplicateSignature: package:linux-image-extra-4.13.0-36-generic:4.13.0-36.40 Unpacking linux-image-extra-4.13.0-36-generic (4.13.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-NH787j/1-linux-image-extra-4.13.0-36-generic_4.13.0-36.40_amd64.deb (--unpack): unable to open '/lib/modules/4.13.0-36-generic/kernel/drivers/net/ethernet/qlogic/qla3xxx.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.13.0-36-generic/kernel/drivers/net/ethernet/qlogic/qla3xxx.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-02-03 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: lono wireless extensions. enp0s10 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 058f:6363 Alcor Micro Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer Aspire X3300 ProcFB: 0 nouveaufb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=c2dc0381-491b-4ee2-a364-b421983b761c 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. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7.2 RfKill: SourcePackage: linux Title: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40 failed to install/upgrade: unable to open '/lib/modules/4.13.0-36-generic/kernel/drivers/net/ethernet/qlogic/qla3xxx.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2009 dmi.bios.vendor: AMI dmi.bios.version: P01-A1 dmi.board.name: WMCP78M dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAMI:bvrP01-A1:bd04/30/2009:svnAcer:pnAspireX3300:pvr:rvnAcer:rnWMCP78M:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X3300 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754353/+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 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769480 Title: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Confirmed Bug description: how to reproduce: dd the iso to an usb drive and boot from it. List all wifi devices in live-mode and connect to one of it. Use the web for some minutes. Open up the wifi on the top right again and list the available networks - it dont show any others any more. Just the one you are connected to. How to overcome the bug: put the computer into airplane mode and go away from airplane mode again. Or: disconnect the usb wifi device and connect it again. Does this bug exist also on installed 18.04 and updated to last (apt update, apt upgrade, apt dist-upgrade)? Yes What wifi device is been used: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' usbcore: registered new interface driver rt2800usb ... ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 uname -a Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769480/+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 1750038] Re: user space process hung in 'D' state waiting for disk io to complete
** Description changed:
+ == SRU Justification ==
+
+ [Impact]
+ Occasionally an application gets stuck in "D" state on NFS reads/sync and
close system calls. All the subsequent operations on the NFS mounts are stuck
and reboot is required to rectify the situation.
+
+ [Fix]
+ Use GPF_NOIO in some allocations in writeback to avoid a deadlock. This is
upstream in:
+ ae97aa524ef4 ("NFS: Use GFP_NOIO for two allocations in writeback")
+
+ [Testcase]
+ See Test scenario in previous description.
+
+ A test kernel with this patch was tested heavily (>100hrs of test suite)
+ without issue.
+
+ [Regression Potential]
+ This changes memory allocation in NFS to use a different policy. This could
potentially affect NFS.
+
+ However, the patch is already in Artful and Bionic without issue.
+
+ The patch does not apply to Trusty.
+
+ == Previous Description ==
+
Using Ubuntu Xenial user reports processes hang in D state waiting for
disk io.
Ocassionally one of the applications gets into "D" state on NFS
reads/sync and close system calls. based on the kernel backtraces seems
to be stuck in kmalloc allocation during cleanup of dirty NFS pages.
All the subsequent operations on the NFS mounts are stuck and reboot is
required to rectify the situation.
[Test scenario]
- 1) Applications running in Docker environment
- 2) Application have cgroup limits --cpu-shares --memory -shm-limit
- 3) python and C++ based applications (torch and caffe)
- 4) Applications read big lmdb files and write results to NFS shares
- 5) use NFS v3 , hard and fscache is enabled
- 6) now swap space is configured
+ 1) Applications running in Docker environment
+ 2) Application have cgroup limits --cpu-shares --memory -shm-limit
+ 3) python and C++ based applications (torch and caffe)
+ 4) Applications read big lmdb files and write results to NFS shares
+ 5) use NFS v3 , hard and fscache is enabled
+ 6) now swap space is configured
This prevents all other I/O activity on that mount to hang.
we are running into this issue more frequently and identified few
applications causing this problem.
As updated in the description, the problem seems to be happening when
exercising the stack
try_to_free_mem_cgroup_pages+0xba/0x1a0
we see this with docker containers with cgroup option --memory
.
whenever there is a deadlock, we see that the process that is hung has
reached the maximum cgroup limit, multiple times and typically cleans up
dirty data and caches to bring the usage under the limit.
This reclaim path happens many times and finally we hit probably a race
get into deadlock
** Changed in: linux (Ubuntu)
Assignee: Dragan S. (dragan-s) => Daniel Axtens (daxtens)
--
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/1750038
Title:
user space process hung in 'D' state waiting for disk io to complete
Status in linux package in Ubuntu:
Incomplete
Bug description:
== SRU Justification ==
[Impact]
Occasionally an application gets stuck in "D" state on NFS reads/sync and
close system calls. All the subsequent operations on the NFS mounts are stuck
and reboot is required to rectify the situation.
[Fix]
Use GPF_NOIO in some allocations in writeback to avoid a deadlock. This is
upstream in:
ae97aa524ef4 ("NFS: Use GFP_NOIO for two allocations in writeback")
[Testcase]
See Test scenario in previous description.
A test kernel with this patch was tested heavily (>100hrs of test
suite) without issue.
[Regression Potential]
This changes memory allocation in NFS to use a different policy. This could
potentially affect NFS.
However, the patch is already in Artful and Bionic without issue.
The patch does not apply to Trusty.
== Previous Description ==
Using Ubuntu Xenial user reports processes hang in D state waiting for
disk io.
Ocassionally one of the applications gets into "D" state on NFS
reads/sync and close system calls. based on the kernel backtraces
seems to be stuck in kmalloc allocation during cleanup of dirty NFS
pages.
All the subsequent operations on the NFS mounts are stuck and reboot
is required to rectify the situation.
[Test scenario]
1) Applications running in Docker environment
2) Application have cgroup limits --cpu-shares --memory -shm-limit
3) python and C++ based applications (torch and caffe)
4) Applications read big lmdb files and write results to NFS shares
5) use NFS v3 , hard and fscache is enabled
6) now swap space is configured
This prevents all other I/O activity on that mount to hang.
we are running into this issue more frequently and identified few
applications causing this problem.
As updated in the description, the problem seems to be happening when
exercising the stack
try_to_free_mem_cgroup_pages+0xba/0x1a0
we see this with docker containe
[Kernel-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04
This is the debdiff for cosmic. Backported the 2 patches to 1.1.6-1. thanks. ** Patch added: "alsa-lib_1.1.6-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1768830/+attachment/5135786/+files/alsa-lib_1.1.6-1ubuntu1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1768830 Title: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04 Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Bionic: New Bug description: Steps: 1. Install the ubuntu 18.04 on the machine of Lenovo P520. 2. Login system. 3. Plug in an external headset to record and playback in front and rear panel. Expected result: Output and input audio should work in front and rear panel. Actual result: Front panel audio doesn't work at all. Just output audio working, input audio does't work in rear panel. SRU Document: [Impact] We have several Lenovo machines like Lenovo P520 which have 2 analogue audio codecs on them, the internal speaker and front headset are connected to the 1st codec, the Rear mic, Line in and Line out are connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa- lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and front headset) on the 1st codec can work. To make all audio devices work on this machine, upstream provided 3 patches for kernel audio driver and 5 patches for alsa-lib. The kernel patches are already in the linux-4.12, so this is not a problem anymore under 18.04 since we use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to backport them to v1.1.3-5, the 5 patches are list as below: 2b9b3f01 ucm: Assure the user input card name not to exceed max size of card long name (it is in the alsa-lib v1.1.4) 4b9297e6 ucm: Load device-specific configuration file based on the card long name (it is in the alsa-lib v1.1.4) b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the alsa-lib v1.1.6) 181f8e25 ucm: adding the folder of card_long_name when finding verb conf file (it is in the alsa-lib v1.1.6+) 81db276f conf/ucm: increase the input volume for LineIn (it is in the alsa-lib v1.1.6+) Some explanation for these 5 patches, to make the audio work, the alsa-lib needs to add an audio configuration file and verb conf file for lenovo machines with dual codecs, these two files are put in a folder named by card_long_name, and the name of configuration file itself is also named by card_long_name, this is implemented by the patches of NO. 3rd and 5th. But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with card_long_name, it only support searching with card_name, So we need to backport 3 patches to let alsa-lib v1.1.3-5 support to search with card_long_name, these 3 patches are No. 1st, 2nd and 4th. [Test Case] On the Lenovo machines with dual codecs (p520), I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can find the conf file and can parse the conf file successfully, and I tested the internal speaker, front headset, rear mic, line out and line in, all audio devices work well. On a HP and Dell machines without dual codecs, I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can't find conf file by card_long_name and card_name, the pulseaudio will drive the sound card as before, so all audio functions worked well as before. [Regression Potential] After adding these 5 patches, there 2 two changes introduced into the alsa-lib v1.1.3-5ubuntu1: 1) before: only have folder and conf files named by card_name; after: has one folder and conf file named by card_long_name, this folder and conf file will not affect others, 2) before: the ucm parser will search the conf file/folder by card_name only; after: the ucm parser will search the conf file/foler by card_long_name first, if it fails, it will fallback to use card_name to search again. So this change is compatible with old version. There is no regression since there is only one folder named by card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with dual codecs, it will find the conf file by card_long_name, if it runs on other machines, the search by card_long_name will definitely fail and fall back to search by card_name, then it will be same as before. So the objective of these 5 patches is to let lenovo machines with dual codecs find the conf file by card_long_name, let other machines fail to search by card_long_name, then fallback to original searching method - search by card_name. [Other Info] Since I could not find the alsa-lib repository in canonical, I just generated the debdiff with "apt-get source ...". To man
[Kernel-packages] [Bug 1769800] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ["Unable to get on D-Bus"]
** Summary changed: - package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 + package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ["Unable to get on D-Bus"] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769800 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ["Unable to get on D-Bus"] Status in bluez package in Ubuntu: New Bug description: error occurred at initial boot-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 7 18:10:42 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-05 (91 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision M2400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=bfcb572e-5cce-49d0-8b64-5ca3d710e894 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U698R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/08/2009:svnDellInc.:pnPrecisionM2400:pvr:rvnDellInc.:rn0U698R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M2400 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:22:5F:B6:8C:FB ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:607 acl:0 sco:0 events:39 errors:0 TX bytes:3303 acl:0 sco:0 commands:39 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769800/+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 1769800] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769800 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ["Unable to get on D-Bus"] Status in bluez package in Ubuntu: New Bug description: error occurred at initial boot-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 7 18:10:42 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-05 (91 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision M2400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=bfcb572e-5cce-49d0-8b64-5ca3d710e894 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U698R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/08/2009:svnDellInc.:pnPrecisionM2400:pvr:rvnDellInc.:rn0U698R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M2400 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:22:5F:B6:8C:FB ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:607 acl:0 sco:0 events:39 errors:0 TX bytes:3303 acl:0 sco:0 commands:39 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769800/+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 1769800] [NEW] package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: error occurred at initial boot-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 7 18:10:42 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-05 (91 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision M2400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=bfcb572e-5cce-49d0-8b64-5ca3d710e894 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U698R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/08/2009:svnDellInc.:pnPrecisionM2400:pvr:rvnDellInc.:rn0U698R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M2400 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:22:5F:B6:8C:FB ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:607 acl:0 sco:0 events:39 errors:0 TX bytes:3303 acl:0 sco:0 commands:39 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769800 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: error occurred at initial boot-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 7 18:10:42 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-05 (91 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision M2400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=bfcb572e-5cce-49d0-8b64-5ca3d710e894 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U698R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/08/2009:svnDellInc.:pnPrecisionM2400:pvr:rvnDellInc.:rn0U698R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M2400 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:22:5F:B6:8C:FB ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:607 acl:0 sco:0 events:39 errors:0 TX bytes:3303 acl:0 sco:0 commands:39 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769792] [NEW] Keyboard and Touchpad do not work after suspend/resume
Public bug reported: My laptop is a Toshiba Satellite C850D with updated 18.04 installed. When resuming from suspend, I have no keyboard and touchpad. dmesg shows "i8042: Can't reactivate KBD port" This looks like a recurring problem, and is just like these: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142118 Here's the dmesg output from before and after suspending. https://paste.ubuntu.com/p/rsFX9Yw7Xh/ This post also talks about this bit failing for a lot of people! http://lightrush.ndoytchev.com/random-1/i8042quirkoptions Some of the function keys work, such as changing the screen brightness, but the key (fn+F5) does not turn the touchpad back on. I have not yet tried any of the suggested options, as results have been mixed, but I will. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 22:01:26 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (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-signed in Ubuntu. https://bugs.launchpad.net/bugs/1769792 Title: Keyboard and Touchpad do not work after suspend/resume Status in linux-signed package in Ubuntu: New Bug description: My laptop is a Toshiba Satellite C850D with updated 18.04 installed. When resuming from suspend, I have no keyboard and touchpad. dmesg shows "i8042: Can't reactivate KBD port" This looks like a recurring problem, and is just like these: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142118 Here's the dmesg output from before and after suspending. https://paste.ubuntu.com/p/rsFX9Yw7Xh/ This post also talks about this bit failing for a lot of people! http://lightrush.ndoytchev.com/random-1/i8042quirkoptions Some of the function keys work, such as changing the screen brightness, but the key (fn+F5) does not turn the touchpad back on. I have not yet tried any of the suggested options, as results have been mixed, but I will. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 22:01:26 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1769792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769557] Re: SD Card Realtek RTL8411 not working
tagged: 'kernel-bug-exists-upstream'. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769557 Title: SD Card Realtek RTL8411 not working Status in linux package in Ubuntu: Confirmed Bug description: Hi to everyone I've been trying to solve this problem for weeks now and nothing has helped me yet. I'm running Ubuntu 18.04 in a Asus X450CC with a Realtek RTL8411 Express Card Reader. Nothing makes it work, even the USB external card reader doesn't work (this one erases the whole information from the SD card). Here is the output from lspci -v 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor DRAM Controller Flags: bus master, fast devsel, latency 0 Capabilities: Kernel driver in use: ivb_uncore 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 16 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: f600-f70f Prefetchable memory behind bridge: e000-f1ff Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at f740 (64-bit, non-prefetchable) [size=4M] Memory at d000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. 7 Series/C210 Series Chipset Family USB xHCI Host Controller Flags: bus master, medium devsel, latency 0, IRQ 26 Memory at f7a0 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) Subsystem: ASUSTeK Computer Inc. 7 Series/C216 Chipset Family MEI Controller Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f7a1a000 (64-bit, non-prefetchable) [size=16] Capabilities: Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. 7 Series/C216 Chipset Family USB Enhanced Host Controller Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at f7a18000 (32-bit, non-prefetchable) [size=1K] Capabilities: Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) Subsystem: ASUSTeK Computer Inc. 7 Series/C216 Chipset Family High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at f7a1 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 16 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 17 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: f790-f79f Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 4 (rev c4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 19 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: f780-f78f Prefetchable memory behind bridge: f210-f21f Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. 7 Series/C216 Chipset Family USB Enhanced Host Controller Fl
[Kernel-packages] [Bug 1769557] Re: SD Card Realtek RTL8411 not working
Hi! No, i've installed Ubuntu 16.04.1 and since then upgraded it untill 18.04, but it has never read an SD card. Doing what you said nothing changed. Thank for your comment! ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: Hi to everyone - I've been trying to solve this problem for weeks now and nothing has helped me yet. I'm running Ubuntu 18.04 in a Asus X450CC with a Realtek RTL8411 Express Card Reader. Nothing makes it work, even the USB external card reader doesn't work (this one erases the whole information from the SD card). + I've been trying to solve this problem for weeks now and nothing has helped me yet. I'm running Ubuntu 18.04 in a Asus X450CC with a Realtek RTL8411 Express Card Reader. Nothing makes it work, even the USB external card reader doesn't work (this one erases the whole information from the SD card). Here is the output from lspci -v 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) - Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor DRAM Controller - Flags: bus master, fast devsel, latency 0 - Capabilities: - Kernel driver in use: ivb_uncore + Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor DRAM Controller + Flags: bus master, fast devsel, latency 0 + Capabilities: + Kernel driver in use: ivb_uncore 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) (prog-if 00 [Normal decode]) - Flags: bus master, fast devsel, latency 0, IRQ 16 - Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 - I/O behind bridge: e000-efff - Memory behind bridge: f600-f70f - Prefetchable memory behind bridge: e000-f1ff - Capabilities: - Kernel driver in use: pcieport - Kernel modules: shpchp + Flags: bus master, fast devsel, latency 0, IRQ 16 + Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 + I/O behind bridge: e000-efff + Memory behind bridge: f600-f70f + Prefetchable memory behind bridge: e000-f1ff + Capabilities: + Kernel driver in use: pcieport + Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) - Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller - Flags: bus master, fast devsel, latency 0, IRQ 30 - Memory at f740 (64-bit, non-prefetchable) [size=4M] - Memory at d000 (64-bit, prefetchable) [size=256M] - I/O ports at f000 [size=64] - [virtual] Expansion ROM at 000c [disabled] [size=128K] - Capabilities: - Kernel driver in use: i915 - Kernel modules: i915 + Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller + Flags: bus master, fast devsel, latency 0, IRQ 30 + Memory at f740 (64-bit, non-prefetchable) [size=4M] + Memory at d000 (64-bit, prefetchable) [size=256M] + I/O ports at f000 [size=64] + [virtual] Expansion ROM at 000c [disabled] [size=128K] + Capabilities: + Kernel driver in use: i915 + Kernel modules: i915 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI]) - Subsystem: ASUSTeK Computer Inc. 7 Series/C210 Series Chipset Family USB xHCI Host Controller - Flags: bus master, medium devsel, latency 0, IRQ 26 - Memory at f7a0 (64-bit, non-prefetchable) [size=64K] - Capabilities: - Kernel driver in use: xhci_hcd + Subsystem: ASUSTeK Computer Inc. 7 Series/C210 Series Chipset Family USB xHCI Host Controller + Flags: bus master, medium devsel, latency 0, IRQ 26 + Memory at f7a0 (64-bit, non-prefetchable) [size=64K] + Capabilities: + Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) - Subsystem: ASUSTeK Computer Inc. 7 Series/C216 Chipset Family MEI Controller - Flags: bus master, fast devsel, latency 0, IRQ 31 - Memory at f7a1a000 (64-bit, non-prefetchable) [size=16] - Capabilities: - Kernel driver in use: mei_me - Kernel modules: mei_me + Subsystem: ASUSTeK Computer Inc. 7 Series/C216 Chipset Family MEI Controller + Flags: bus master, fast devsel, latency 0, IRQ 31 + Memory at f7a1a000 (64-bit, non-prefetchable) [size=16] + Capabilities: + Kernel driver in use: mei_me + Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI]) - Subsystem: ASUSTeK Computer Inc. 7 Series/C216 Chipset Family USB Enhanced Host Controller - Flags: bus master, medium devsel, latency 0, IRQ 16 - Memory at f7a18000 (32-bit, no
[Kernel-packages] [Bug 1769236] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135726/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.
[Kernel-packages] [Bug 1769236] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135721/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sy
[Kernel-packages] [Bug 1769236] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135728/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.
[Kernel-packages] [Bug 1769236] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135720/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To
[Kernel-packages] [Bug 1769236] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135730/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP
[Kernel-packages] [Bug 1769236] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135727/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dm
[Kernel-packages] [Bug 1769236] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135732/+files/WifiSyslog.txt ** 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/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre La
[Kernel-packages] [Bug 1769236] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135729/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.vend
[Kernel-packages] [Bug 1769236] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135731/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP
[Kernel-packages] [Bug 1769236] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135722/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor
[Kernel-packages] [Bug 1769236] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135724/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.
[Kernel-packages] [Bug 1769236] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135723/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP T
[Kernel-packages] [Bug 1769236] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135725/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfi
[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value
apport information ** Tags added: apport-collected ** Description changed: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gjditchf 1190 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-04-28 (10 days ago) + InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:0a2b Intel Corp. + Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. + Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: HP HP Spectre Laptop 13-af0xx + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 + Tags: bionic + Uname: Linux 4.15.0-20-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/13/2017 + dmi.bios.vendor: Insyde + dmi.bios.version: F.06 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: 83A2 + dmi.board.vendor: HP + dmi.board.version: 55.24 + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: + dmi.product.family: 103C_5335KV HP Spectre + dmi.product.name: HP Spectre Laptop 13-af0xx + dmi.product.version: Type1ProductConfigId + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1769236/+attachment/5135719/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at mini
[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value
This was a fresh install, not an upgrade. I have applied all updates made available since the installation, but performance has not changed. I have not installed any other linux on this laptop. For comparison purposes, I booted it from a 17.04 (Artful) live USB, which has kernel 4.13.0-16. It doesn't feel faster, but of course there are many factors involved ... When running Artful, /proc/cpuinfo displays "cpu MHz : 2000.000" for all 8 CPU's, and never varies. When running c-ray, all 8 CPUs are 50%--75% used, but the fans never spin up. "cpupower frequency-info" reports "current CPU frequency: 400 MHz (asserted by call to kernel)", which contradicts /proc/cpuinfo. I will try an upstream kernel tomorrow. -- 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/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Incomplete Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.
[Kernel-packages] [Bug 1760545] Re: [18.04] GLK hang after a while
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760545 Title: [18.04] GLK hang after a while Status in intel: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: SRU Justification Impact: i915 lacks information about the glk_dmc_ver1_04.bin firmware file in modinfo, so it is not included in the initrd along with the i915 driver. Thus the firmware does not get loaded. Loading the firmware is said to prevent a hang. Fix: Add a MODULE_FIRMWARE statement for the firmware. Test Case: Without the firmware there will be a "Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2" line in dmesg. With the firmware there is no such message. Regression Potential: Minimal. Will only be loaded by i915 for specific hardware, and loading the firmware is known to fix a hang. --- Description: Platform information: Label: GLK02SDP Processor: Silver N5000 Bios: GELKRVPA.X64.0083.B30.1801162142 OS: Ubuntu 18.04 Kernel: 4.15.0-10-generic Details: Power on, and enter into the system; After a period, sometimes about 20 minutes, sometimes 1 hour, the machine will hang. We can only power it off manually, then power on to enter into OS again. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1760545/+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 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
Still happening on 4.16.6 kernel for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+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 1728238] Re: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load
And to clarify when I ran: sudo update-initramfs -u -v -k all|grep kbl The first round of firmware files is for 4.15.0-21-generic while the second listing is for your patched kernel. Notice the added GuC entry. As you can see the GuC firmware loads when running your patched kernel. Thank you for building the test kernel :) -- 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/1728238 Title: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load Status in initramfs-tools: New Status in linux package in Ubuntu: Confirmed Bug description: The i915 Kabylake GuC firmware is failing to load on boot, and generating dmesg errors. The Kabylake HuC firmware succeeds. All files exist. I've also verified the Kabylake GuC firmware matches the correct file size and md5 listed on 01.org. I then ran update-initramfs verbosely, and see that only /lib/firmware/i915/skl_guc_ver6_1.bin is being added. /lib/firmware/i915/bxt_guc_ver8_7.bin and /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored. I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and initramfs-tools 0.125ubuntu12. Perhaps Broxton systems might have the same issue? Output and logs: - ls -al /lib/firmware/i915/kbl_* -rw-r--r-- 1 root root 8616 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1_01.bin lrwxrwxrwx 1 root root 19 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin -rw-r--r-- 1 root root 142656 Oct 20 21:12 /lib/firmware/i915/kbl_guc_ver9_14.bin -rw-r--r-- 1 root root 218688 Aug 17 11:09 /lib/firmware/i915/kbl_huc_ver02_00_1810.bin sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: FAIL load: NONE version wanted: 9.14 version found: 0.0 header: offset is 0; size = 0 uCode: offset is 0; size = 0 RSA: offset is 0; size = 0 GuC status 0x0001: Bootrom status = 0x0 uKernel status = 0x0 MIA Core status = 0x0 Scratch registers: 0: 0x0 1: 0x0 2: 0x0 3: 0x0 4: 0x0 5: 0x0 6: 0x0 7: 0x0 8: 0x0 9: 0x0 10: 0x0 11: 0x0 12: 0x0 13: 0x0 14: 0x0 15: 0x0 sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status HuC firmware status: path: i915/kbl_huc_ver02_00_1810.bin fetch: SUCCESS load: SUCCESS version wanted: 2.0 version found: 2.0 header: offset is 0; size = 128 uCode: offset is 128; size = 218304 RSA: offset is 218432; size = 256 HuC status 0x6000: dmesg [1.052879] hidraw: raw HID events driver (C) Jiri Kosina [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002) [1.082308] nvme nvme0: pci function :3c:00.0 [1.095073] Setting dangerous option enable_guc_loading - tainting kernel [1.095075] Setting dangerous option enable_guc_submission - tainting kernel [1.097867] [drm] Memory usable by graphics device = 4078M [1.097869] checking generic (9000 1fb) vs hw (9000 1000) [1.097869] fb: switching to inteldrmfb from EFI VGA [1.097899] Console: switching to colour dummy device 80x25 [1.098049] [drm] Replacing VGA console driver [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.104157] [drm] Driver supports precise vblank timestamp query. [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd [1.298572] nvme0n1: p1 p2 [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.433243] usb 1-1: Product: USB+PS2 Keyboard [1.433244] usb 1-1: Manufacturer: Generic [1.446460] usbcore: registered new interface driver usbhid [1.446461] usbhid: USB HID core driver [1.448067] input: Generic USB+PS2 Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7 [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0 [1.508541] input: Generic USB+PS2 Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8 [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1 [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b [1.695656] usb 1-2: New USB device strings: Mfr=1
[Kernel-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load
@jsalisbury This does indeed fix the issue: ~$ sudo update-initramfs -u -v -k all|grep kbl Adding firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin Adding firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin /usr/sbin/iucode_tool: system has processor(s) with signature 0x000806e9 /usr/sbin/iucode_tool: Writing selected microcodes to: /var/tmp/mkinitramfs-EFW_1VBI8FyxJM /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable Adding firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin Adding firmware /lib/firmware/i915/kbl_guc_ver9_14.bin Adding firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin /usr/sbin/iucode_tool: system has processor(s) with signature 0x000806e9 /usr/sbin/iucode_tool: Writing selected microcodes to: /var/tmp/mkinitramfs-EFW_LmLiZccZZr /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable ~$ uname -a Linux 4.15.0-20-generic #21~lp1728238 SMP Mon May 7 16:50:25 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ~$ sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status GuC firmware: i915/kbl_guc_ver9_14.bin status: fetch SUCCESS, load SUCCESS version: wanted 9.14, found 9.14 header: offset 0, size 128 uCode: offset 128, size 142272 RSA: offset 142400, size 256 GuC status 0x800330ed: Bootrom status = 0x76 uKernel status = 0x30 MIA Core status = 0x3 Scratch registers: 0: 0xf000 1: 0x0 2: 0x0 3: 0x5f5e100 4: 0x600 5: 0xcdfd3 6: 0x0 7: 0x8 8: 0x3 9: 0x70240 10: 0x0 11: 0x0 12: 0x0 13: 0x0 14: 0x0 15: 0x0 ~$ sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status HuC firmware: i915/kbl_huc_ver02_00_1810.bin status: fetch SUCCESS, load SUCCESS version: wanted 2.0, found 2.0 header: offset 0, size 128 uCode: offset 128, size 218304 RSA: offset 218432, size 256 HuC status 0x6080: -- 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/1728238 Title: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load Status in initramfs-tools: New Status in linux package in Ubuntu: Confirmed Bug description: The i915 Kabylake GuC firmware is failing to load on boot, and generating dmesg errors. The Kabylake HuC firmware succeeds. All files exist. I've also verified the Kabylake GuC firmware matches the correct file size and md5 listed on 01.org. I then ran update-initramfs verbosely, and see that only /lib/firmware/i915/skl_guc_ver6_1.bin is being added. /lib/firmware/i915/bxt_guc_ver8_7.bin and /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored. I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and initramfs-tools 0.125ubuntu12. Perhaps Broxton systems might have the same issue? Output and logs: - ls -al /lib/firmware/i915/kbl_* -rw-r--r-- 1 root root 8616 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1_01.bin lrwxrwxrwx 1 root root 19 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin -rw-r--r-- 1 root root 142656 Oct 20 21:12 /lib/firmware/i915/kbl_guc_ver9_14.bin -rw-r--r-- 1 root root 218688 Aug 17 11:09 /lib/firmware/i915/kbl_huc_ver02_00_1810.bin sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: FAIL load: NONE version wanted: 9.14 version found: 0.0 header: offset is 0; size = 0 uCode: offset is 0; size = 0 RSA: offset is 0; size = 0 GuC status 0x0001: Bootrom status = 0x0 uKernel status = 0x0 MIA Core status = 0x0 Scratch registers: 0: 0x0 1: 0x0 2: 0x0 3: 0x0
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Ok, I guess this is embarrassing, but as I was trying James' workaround in #92 , I started thinking that somehow the signal was weak or intermittent. A few minutes later, Solaar (the GUI that displays status of Logitech wireless devices) tells me that the battery level in the mouse was down to 5%. I replaced the only battery it takes (I have the M215), and the middle button started working just fine. It's been rock solid for a few days.Running Bionic now. (as an aside, it seems like the battery reporting capabilities are not too good: new batteries show 90% charge, and this one "dropped" from 90% to 5% instantly. But the battery was very likely almost empty for quite some time) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersi
[Kernel-packages] [Bug 1769027] Re: perf record crash: refcount_inc assertion failed
Confirmed that the updated perf binary doesn't crash with the cgroups argument. -- 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/1769027 Title: perf record crash: refcount_inc assertion failed Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: On linux-hwe-tools-4.13.0-39 in xenial: Trying to run perf record ... --cgroup=mycgroup causes an immediate assertion failure: refcount_inc: Assertion `!(!refcount_inc_not_zero(r))' failed. Confirmed fixed by patching my linux-tools package with this upstream commit (on top of the commit in bug #1767204): https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git/commit/tools/perf/util/cgroup.c?id=cd8dd032f61abeb08d2c03bab4968a9de231a1be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769027/+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 1768442] Re: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: Unterprozess installed linux-image-4.15.0-20-generic package pre-removal script gab de
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1768442 Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: Unterprozess installed linux-image-4.15.0-20-generic package pre-removal script gab den Fehler-Ausgangsstatus 1 zurück Status in linux-signed package in Ubuntu: Confirmed Bug description: Crash happened on regular apt full-upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon Apr 30 15:55:19 2018 ErrorMessage: Unterprozess installed linux-image-4.15.0-20-generic package pre-removal script gab den Fehler-Ausgangsstatus 1 zurück InstallationDate: Installed on 2018-04-30 (1 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: Unterprozess installed linux-image-4.15.0-20-generic package pre-removal script gab den Fehler-Ausgangsstatus 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1768442/+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 1728238] Re: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load
@mtvoid Thank you for clearing that up. I was not aware that Broxton was Atom. For some reason I thought it was an earlier generation x64 Core architecture. @jsalisbury I am running Bionic. I've never tested a kernel before, but am willing to do so. -- 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/1728238 Title: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load Status in initramfs-tools: New Status in linux package in Ubuntu: Confirmed Bug description: The i915 Kabylake GuC firmware is failing to load on boot, and generating dmesg errors. The Kabylake HuC firmware succeeds. All files exist. I've also verified the Kabylake GuC firmware matches the correct file size and md5 listed on 01.org. I then ran update-initramfs verbosely, and see that only /lib/firmware/i915/skl_guc_ver6_1.bin is being added. /lib/firmware/i915/bxt_guc_ver8_7.bin and /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored. I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and initramfs-tools 0.125ubuntu12. Perhaps Broxton systems might have the same issue? Output and logs: - ls -al /lib/firmware/i915/kbl_* -rw-r--r-- 1 root root 8616 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1_01.bin lrwxrwxrwx 1 root root 19 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin -rw-r--r-- 1 root root 142656 Oct 20 21:12 /lib/firmware/i915/kbl_guc_ver9_14.bin -rw-r--r-- 1 root root 218688 Aug 17 11:09 /lib/firmware/i915/kbl_huc_ver02_00_1810.bin sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: FAIL load: NONE version wanted: 9.14 version found: 0.0 header: offset is 0; size = 0 uCode: offset is 0; size = 0 RSA: offset is 0; size = 0 GuC status 0x0001: Bootrom status = 0x0 uKernel status = 0x0 MIA Core status = 0x0 Scratch registers: 0: 0x0 1: 0x0 2: 0x0 3: 0x0 4: 0x0 5: 0x0 6: 0x0 7: 0x0 8: 0x0 9: 0x0 10: 0x0 11: 0x0 12: 0x0 13: 0x0 14: 0x0 15: 0x0 sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status HuC firmware status: path: i915/kbl_huc_ver02_00_1810.bin fetch: SUCCESS load: SUCCESS version wanted: 2.0 version found: 2.0 header: offset is 0; size = 128 uCode: offset is 128; size = 218304 RSA: offset is 218432; size = 256 HuC status 0x6000: dmesg [1.052879] hidraw: raw HID events driver (C) Jiri Kosina [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002) [1.082308] nvme nvme0: pci function :3c:00.0 [1.095073] Setting dangerous option enable_guc_loading - tainting kernel [1.095075] Setting dangerous option enable_guc_submission - tainting kernel [1.097867] [drm] Memory usable by graphics device = 4078M [1.097869] checking generic (9000 1fb) vs hw (9000 1000) [1.097869] fb: switching to inteldrmfb from EFI VGA [1.097899] Console: switching to colour dummy device 80x25 [1.098049] [drm] Replacing VGA console driver [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.104157] [drm] Driver supports precise vblank timestamp query. [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd [1.298572] nvme0n1: p1 p2 [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.433243] usb 1-1: Product: USB+PS2 Keyboard [1.433244] usb 1-1: Manufacturer: Generic [1.446460] usbcore: registered new interface driver usbhid [1.446461] usbhid: USB HID core driver [1.448067] input: Generic USB+PS2 Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7 [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0 [1.508541] input: Generic USB+PS2 Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8 [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1 [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.695657] usb 1-2: Product: USB Receive
[Kernel-packages] [Bug 1769733] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1769733 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769733 Title: Third screen not working displayport amd ryzen 5 2400g apu Status in linux package in Ubuntu: Incomplete Bug description: All relevant information can be found in this post: https://askubuntu.com/questions/1033287/cant-get-my-third-screen-working-ubuntu-18-04-amd-ryzen-5-2400g All errors and tries have been posted in that post. the problem is reletaed to the drivers regarding the amd ryzen 5 2400g APU, not all three of my screens turn on. only the dvi-d port and gdmi port give me output but the display port gives me a blank screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 21:52:25 2018 InstallationDate: Installed on 2018-05-06 (0 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/1769733/+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 1769721] Re: [ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092167.html
** Description changed:
- As submitted upstream in this email: http://mailman.alsa-
- project.org/pipermail/alsa-devel/2018-May/135685.html
- This adds support for the P950ER, which has the same required fixup as
- the P950HR, but has a different PCI ID.
+ == SRU Justification ==
+ This request is to add a sound quirk requested by System76. This adds
+ support for the P950ER, which has the same required fixup as the P950HR,
+ but has a different PCI ID.
- Signed-off-by: Jeremy Soller
- ---
- sound/pci/hda/patch_realtek.c | 1 +
- 1 file changed, 1 insertion(+)
+ The patch was already submitted upstream in this email:
+ http://mailman.alsa-project.org/pipermail/alsa-devel/2018-May/135685.html
- diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
- index 2dd34dd77447..01a6643fc7d4 100644
- --- a/sound/pci/hda/patch_realtek.c
- +++ b/sound/pci/hda/patch_realtek.c
- @@ -2363,6 +2363,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = {
- SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
- SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
- SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR",
ALC1220_FIXUP_CLEVO_P950),
- + SND_PCI_QUIRK(0x1558, 0x95e2, "Clevo P950ER",
ALC1220_FIXUP_CLEVO_P950),
- SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
- SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
- SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530",
ALC882_FIXUP_LENOVO_Y530),
+ However, the patch has not landed in mainline as of yet, so it is being
+ requested as SAUCE.
+
+ == Fix ==
+ UBUNTU: SAUCE: ALSA: hda/realtek - Clevo P950ER ALC1220 Fixup
+
+ == Regression Potential ==
+ Low. Limited to a new sound quirk.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
--
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/1769721
Title:
[ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
This request is to add a sound quirk requested by System76. This adds
support for the P950ER, which has the same required fixup as the P950HR,
but has a different PCI ID.
The patch was already submitted upstream in this email:
http://mailman.alsa-project.org/pipermail/alsa-devel/2018-May/135685.html
However, the patch has not landed in mainline as of yet, so it is being
requested as SAUCE.
== Fix ==
UBUNTU: SAUCE: ALSA: hda/realtek - Clevo P950ER ALC1220 Fixup
== Regression Potential ==
Low. Limited to a new sound quirk.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769721/+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 1769733] Re: Third screen not working displayport amd ryzen 5 2400g apu
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc4 ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => 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/1769733 Title: Third screen not working displayport amd ryzen 5 2400g apu Status in linux package in Ubuntu: Incomplete Bug description: All relevant information can be found in this post: https://askubuntu.com/questions/1033287/cant-get-my-third-screen-working-ubuntu-18-04-amd-ryzen-5-2400g All errors and tries have been posted in that post. the problem is reletaed to the drivers regarding the amd ryzen 5 2400g APU, not all three of my screens turn on. only the dvi-d port and gdmi port give me output but the display port gives me a blank screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 21:52:25 2018 InstallationDate: Installed on 2018-05-06 (0 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/1769733/+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 1769721] Re: [ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Thanks, I appreciate the help in getting it into Ubuntu! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769721 Title: [ALSA] [PATCH] Clevo P950ER ALC1220 Fixup Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == SRU Justification == This request is to add a sound quirk requested by System76. This adds support for the P950ER, which has the same required fixup as the P950HR, but has a different PCI ID. The patch was already submitted upstream in this email: http://mailman.alsa-project.org/pipermail/alsa-devel/2018-May/135685.html However, the patch has not landed in mainline as of yet, so it is being requested as SAUCE. == Fix == UBUNTU: SAUCE: ALSA: hda/realtek - Clevo P950ER ALC1220 Fixup == Regression Potential == Low. Limited to a new sound quirk. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769721/+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 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation
Artful SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092160.html
Xenial SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092161.html
** Description changed:
+ == SRU Justification ==
+ IBM reported this bug due to a regression introduced by mainline commit
+ 94232a4332de. IBM has requested this SAUCE backport to resolve this
+ regression in Artful and Xenial.
+
+ With Bionic and v4.15, the rwlock code has been rewritten. See upstream
gitcommit:
+ eb3b7b848fb3 ("s390/rwlock: introduce rwlock wait queueing").
+
+ Since the upstream code has been rewritten there also won't be an upstream
+ git commit id available which contains the attached fix.
+
+ == Fix ==
+ UBUNTU: SAUCE: (no-up) s390: fix rwlock implementation
+
+ == Regression Potential ==
+ Low. The backport was written and tested by IBM. It is specific to s390.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
Description: kernel: fix rwlock implementation
Symptom: Kernel hangs, due to deadlock on an rwlock.
Problem: With upstream commit 94232a4332de ("s390/rwlock: improve writer
- fairness") rwlock writer fairness was supposed to be
- implemented. If a writer tries to take an rwlock it sets
- unconditionally the writer bit within the lock word and waits
- until all readers have released the lock. This however can lead
- to a deadlock since rwlocks can be taken recursively by readers.
- If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to
- write-lock the lock, then CPU 1 sets the writer bit and
- afterwards busy waits for CPU 0 to release the lock. If now CPU 0
- tries to read-lock the lock again (recursively) it will also
busy
- wait until CPU 1 removes the writer bit, which will never
happen,
- since it waits for the first reader on CPU 0 to release the
lock.
+ fairness") rwlock writer fairness was supposed to be
+ implemented. If a writer tries to take an rwlock it sets
+ unconditionally the writer bit within the lock word and waits
+ until all readers have released the lock. This however can lead
+ to a deadlock since rwlocks can be taken recursively by readers.
+ If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to
+ write-lock the lock, then CPU 1 sets the writer bit and
+ afterwards busy waits for CPU 0 to release the lock. If now CPU 0
+ tries to read-lock the lock again (recursively) it will also
busy
+ wait until CPU 1 removes the writer bit, which will never
happen,
+ since it waits for the first reader on CPU 0 to release the
lock.
Solution: Revert the rwlock writer fairness semantics again.
--
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/1761674
Title:
[Ubuntu 16.04] kernel: fix rwlock implementation
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
IBM reported this bug due to a regression introduced by mainline commit
94232a4332de. IBM has requested this SAUCE backport to resolve this
regression in Artful and Xenial.
With Bionic and v4.15, the rwlock code has been rewritten. See upstream
gitcommit:
eb3b7b848fb3 ("s390/rwlock: introduce rwlock wait queueing").
Since the upstream code has been rewritten there also won't be an upstream
git commit id available which contains the attached fix.
== Fix ==
UBUNTU: SAUCE: (no-up) s390: fix rwlock implementation
== Regression Potential ==
Low. The backport was written and tested by IBM. It is specific to s390.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Description: kernel: fix rwlock implementation
Symptom: Kernel hangs, due to deadlock on an rwlock.
Problem: With upstream commit 94232a4332de ("s390/rwlock: improve writer
fairness") rwlock writer fairness was supposed to be
implemented. If a writer tries to take an rwlock it sets
unconditionally the writer bit within the lock word and waits
until all readers have released the lock. This however can lead
to a deadlock since rwlocks can be taken recursively by readers.
If e.g. CPU 0 holds the lock as a r
[Kernel-packages] [Bug 1769721] Re: [ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Thanks for testing and sorry for the typo. I'll submit and SRU request
for this 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/1769721
Title:
[ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
As submitted upstream in this email: http://mailman.alsa-
project.org/pipermail/alsa-devel/2018-May/135685.html
This adds support for the P950ER, which has the same required fixup as
the P950HR, but has a different PCI ID.
Signed-off-by: Jeremy Soller
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 2dd34dd77447..01a6643fc7d4 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -2363,6 +2363,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = {
SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR",
ALC1220_FIXUP_CLEVO_P950),
+ SND_PCI_QUIRK(0x1558, 0x95e2, "Clevo P950ER",
ALC1220_FIXUP_CLEVO_P950),
SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530",
ALC882_FIXUP_LENOVO_Y530),
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769721/+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 1769730] Re: Some PCIe errors not surfaced through rasdaemon
** Description changed: [Impact] The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe errors to the AER (Advanced Error Reporting) driver, which surfaces them to userspace. However, we're currently only reporting "recoverable" errors and not errors of other types (e.g. correctable), thus hiding signs of faulty hardware from the user. [Test Case] $ sudo apt install rasdaemon # On a system that supports ACPI EINJ (dmesg | grep "ACPI: EINJ"), use the attached script to inject a correctable PCIe error. $ sudo ras-mc-ctl --errors # There should be an entry for the injected error, as shown below: No Memory errors. PCIe AER events: 1 2018-05-07 17:55:46 + Fatal error: Receiver Error No Extlog errors. No MCE errors. [Regression Risk] + Above test was ran on x86 & ARM platforms to mitigate regression risk. ** Attachment added: "einj-aer.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769730/+attachment/5135673/+files/einj-aer.sh -- 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/1769730 Title: Some PCIe errors not surfaced through rasdaemon Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe errors to the AER (Advanced Error Reporting) driver, which surfaces them to userspace. However, we're currently only reporting "recoverable" errors and not errors of other types (e.g. correctable), thus hiding signs of faulty hardware from the user. [Test Case] $ sudo apt install rasdaemon # On a system that supports ACPI EINJ (dmesg | grep "ACPI: EINJ"), use the attached script to inject a correctable PCIe error. $ sudo ras-mc-ctl --errors # There should be an entry for the injected error, as shown below: No Memory errors. PCIe AER events: 1 2018-05-07 17:55:46 + Fatal error: Receiver Error No Extlog errors. No MCE errors. [Regression Risk] Above test was ran on x86 & ARM platforms to mitigate regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769730/+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 1769027] Re: perf record crash: refcount_inc assertion failed
I'm going to mark bug 1767204 as a duplicate of this bug. I'll include the commit in that bug and the commit in this bug in a single SRU request once testing is complete. -- 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/1769027 Title: perf record crash: refcount_inc assertion failed Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: On linux-hwe-tools-4.13.0-39 in xenial: Trying to run perf record ... --cgroup=mycgroup causes an immediate assertion failure: refcount_inc: Assertion `!(!refcount_inc_not_zero(r))' failed. Confirmed fixed by patching my linux-tools package with this upstream commit (on top of the commit in bug #1767204): https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git/commit/tools/perf/util/cgroup.c?id=cd8dd032f61abeb08d2c03bab4968a9de231a1be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769027/+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 1769721] Re: [ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
By the way, I installed the kernel from
http://kernel.ubuntu.com/~jsalisbury/lp1769721/, since the above link
had a 0 instead of a 9.
--
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/1769721
Title:
[ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
As submitted upstream in this email: http://mailman.alsa-
project.org/pipermail/alsa-devel/2018-May/135685.html
This adds support for the P950ER, which has the same required fixup as
the P950HR, but has a different PCI ID.
Signed-off-by: Jeremy Soller
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 2dd34dd77447..01a6643fc7d4 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -2363,6 +2363,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = {
SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR",
ALC1220_FIXUP_CLEVO_P950),
+ SND_PCI_QUIRK(0x1558, 0x95e2, "Clevo P950ER",
ALC1220_FIXUP_CLEVO_P950),
SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530",
ALC882_FIXUP_LENOVO_Y530),
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769721/+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 1767204] Re: perf record crash due to swapped xyarray function signatures
*** This bug is a duplicate of bug 1769027 *** https://bugs.launchpad.net/bugs/1769027 ** This bug has been marked a duplicate of bug 1769027 perf record crash: refcount_inc assertion failed -- 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/1767204 Title: perf record crash due to swapped xyarray function signatures Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: Crash happens on 16.04 with kernel 4.13.0-39. Please backport this upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/patch/?id=3d8bba9535ac6e79453c769dd0c8ea852a51ad60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767204/+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 1769721] Re: [ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
The audio, which does not work with the current Ubuntu kernel, now works
as expected!
--
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/1769721
Title:
[ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
As submitted upstream in this email: http://mailman.alsa-
project.org/pipermail/alsa-devel/2018-May/135685.html
This adds support for the P950ER, which has the same required fixup as
the P950HR, but has a different PCI ID.
Signed-off-by: Jeremy Soller
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 2dd34dd77447..01a6643fc7d4 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -2363,6 +2363,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = {
SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR",
ALC1220_FIXUP_CLEVO_P950),
+ SND_PCI_QUIRK(0x1558, 0x95e2, "Clevo P950ER",
ALC1220_FIXUP_CLEVO_P950),
SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530",
ALC882_FIXUP_LENOVO_Y530),
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769721/+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 1764982] Re: [bionic] machine stuck and bonding not working well when nvmet_rdma module is loaded
SRU request submitted for Bionic:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092158.html
** Description changed:
- Hi
+
+ == SRU Justification ==
+ This bug causes the machine to get stuck and bonding to not work when
+ the nvmet_rdma module is loaded.
+
+ Both of these commits are in mainline as of v4.17-rc1.
+
+ == Fixes ==
+ a3dd7d0022c3 ("nvmet-rdma: Don't flush system_wq by default during
remove_one")
+ 9bad0404ecd7 ("nvme-rdma: Don't flush delete_wq by default during remove_one")
+
+ == Regression Potential ==
+ Low. Limited to nvme driver and tested by Mellanox.
+
+ == Test Case ==
+ A test kernel was built with these patches and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
+ == Original Bug Description ==
+
+ Hi
Machine stuck after unregistering bonding interface when the nvmet_rdma
module is loading.
scenario:
-
- # modprobe nvmet_rdma
- # modprobe -r bonding
- # modprobe bonding -v mode=1 miimon=100 fail_over_mac=0
- # ifdown eth4
- # ifdown eth5
- # ip addr add 15.209.12.173/8 dev bond0
- # ip link set bond0 up
- # echo +eth5 > /sys/class/net/bond0/bonding/slaves
- # echo +eth4 > /sys/class/net/bond0/bonding/slaves
- # echo -eth4 > /sys/class/net/bond0/bonding/slaves
- # echo -eth5 > /sys/class/net/bond0/bonding/slaves
- # echo -bond0 > /sys/class/net/bonding_masters
-
+ # modprobe nvmet_rdma
+ # modprobe -r bonding
+ # modprobe bonding -v mode=1 miimon=100 fail_over_mac=0
+ # ifdown eth4
+ # ifdown eth5
+ # ip addr add 15.209.12.173/8 dev bond0
+ # ip link set bond0 up
+ # echo +eth5 > /sys/class/net/bond0/bonding/slaves
+ # echo +eth4 > /sys/class/net/bond0/bonding/slaves
+ # echo -eth4 > /sys/class/net/bond0/bonding/slaves
+ # echo -eth5 > /sys/class/net/bond0/bonding/slaves
+ # echo -bond0 > /sys/class/net/bonding_masters
dmesg:
kernel: [78348.225556] bond0 (unregistering): Released all slaves
kernel: [78358.339631] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78368.419621] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78378.499615] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78388.579625] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78398.659613] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78408.739655] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78418.819634] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78428.899642] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78438.979614] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78449.059619] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78459.139626] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78469.219623] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78479.299619] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78489.379620] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78499.459623] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78509.539631] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78519.619629] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
-
The following upstream commits that fix this issue
-
commit a3dd7d0022c347207ae931c753a6dc3e6e8fcbc1
Author: Max Gurtovoy
Date: Wed Feb 28 13:12:38 2018 +0200
- nvmet-rdma: Don't flush system_wq by default during remove_one
+ nvmet-rdma: Don't flush system_wq by default during remove_one
- The .remove_one function is called for any ib_device removal.
- In case the removed device has no reference in our driver, there
- is no need to flush the system work queue.
+ The .remove_one function is called for any ib_device removal.
+ In case the removed device has no reference in our driver, there
+ is no need to flush the system work queue.
- Reviewed-by: Israel Rukshin
- Signed-off-by: Max Gurtovoy
- Reviewed-by: Sagi Grimberg
- Signed-off-by: Keith Busch
- Signed-off-by: Jens Axboe
+ Reviewed-by: Israel Rukshin
+ Signed-off-by: Max Gurtovoy
+ Reviewed-by: Sagi Grimberg
+ Signed-off-by: Keith Busch
+ Signed-off-by: Jens Axboe
diff --git a/drivers/nvme/target/rdma.c b/drivers/nvme/target/rdma.c
index aa8068f..a59263d 100644
--- a/drivers/nvme/target/rdma.c
+++ b/drivers/nvme/target/rdma.c
@@ -1469,8 +1469,25 @@ static struct nvmet_fabrics_ops nvmet_rdma_ops = {
- static void nvmet_rdma_remove_one(struct ib_device *ib_de
[Kernel-packages] [Bug 1760545] Re: [18.04] GLK hang after a while
Attached is the patch (or commit b607990c76ceda0a7a7ceacabab174cdc8b9beee). ** Patch added: "0001-drm-i915-glk-Add-MODULE_FIRMWARE-for-Geminilake.patch" https://bugs.launchpad.net/intel/+bug/1760545/+attachment/5135659/+files/0001-drm-i915-glk-Add-MODULE_FIRMWARE-for-Geminilake.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/1760545 Title: [18.04] GLK hang after a while Status in intel: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: SRU Justification Impact: i915 lacks information about the glk_dmc_ver1_04.bin firmware file in modinfo, so it is not included in the initrd along with the i915 driver. Thus the firmware does not get loaded. Loading the firmware is said to prevent a hang. Fix: Add a MODULE_FIRMWARE statement for the firmware. Test Case: Without the firmware there will be a "Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2" line in dmesg. With the firmware there is no such message. Regression Potential: Minimal. Will only be loaded by i915 for specific hardware, and loading the firmware is known to fix a hang. --- Description: Platform information: Label: GLK02SDP Processor: Silver N5000 Bios: GELKRVPA.X64.0083.B30.1801162142 OS: Ubuntu 18.04 Kernel: 4.15.0-10-generic Details: Power on, and enter into the system; After a period, sometimes about 20 minutes, sometimes 1 hour, the machine will hang. We can only power it off manually, then power on to enter into OS again. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1760545/+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 1760545] Re: [18.04] GLK hang after a while
A mainline patch is available now in v4.17-rc4. It is probably best to back port commit b607990c76ceda0a7a7ceacabab174cdc8b9beee for Ubuntu 4.15 and Ubuntu 4.16 (if released) as the mainline 'Cc: stable' tag is stalled. The patch/commit fixes the bug as documented above: ubuntu@ubuntu:~$ dmesg | egrep 'Linux version|DMI:|i915' [0.00] Linux version 4.17.0-041700rc4-generic (kernel@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #201805070430 SMP Mon May 7 04:31:46 UTC 2018 [0.00] DMI: Intel Corporation NUC7CJYS/NUC7JYB, BIOS JYGLKCPX.86A.0024.2017.1229.1454 12/29/2017 [2.489175] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [2.489705] [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4) [2.493790] [drm] Initialized i915 1.6.0 20180308 for :00:02.0 on minor 0 [2.567821] i915 :00:02.0: fb0: inteldrmfb frame buffer device ubuntu@ubuntu:~$ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760545 Title: [18.04] GLK hang after a while Status in intel: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: SRU Justification Impact: i915 lacks information about the glk_dmc_ver1_04.bin firmware file in modinfo, so it is not included in the initrd along with the i915 driver. Thus the firmware does not get loaded. Loading the firmware is said to prevent a hang. Fix: Add a MODULE_FIRMWARE statement for the firmware. Test Case: Without the firmware there will be a "Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2" line in dmesg. With the firmware there is no such message. Regression Potential: Minimal. Will only be loaded by i915 for specific hardware, and loading the firmware is known to fix a hang. --- Description: Platform information: Label: GLK02SDP Processor: Silver N5000 Bios: GELKRVPA.X64.0083.B30.1801162142 OS: Ubuntu 18.04 Kernel: 4.15.0-10-generic Details: Power on, and enter into the system; After a period, sometimes about 20 minutes, sometimes 1 hour, the machine will hang. We can only power it off manually, then power on to enter into OS again. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1760545/+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 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5
V3 SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092153.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/1746474
Title:
unregister_netdevice: waiting for eth0 to become free. Usage count = 5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
Commit 52df157f17e5 introduced a regression in v4.13-rc1. This regression
causes a stack trace to occur when tearing down an LXD container. The process
hangs with the following message:
"unregister_netdevice: waiting for eth0 to become free. Usage count =
5"
This regression is fixed by commit 510c321b5571, which is in mainline as of
v4.16-rc7. The fix is needed in Artful and Bionic. However, Artful needs
a prereq commit, so it's SRU request will be sent separately.
== Fix ==
510c321b5571 ("xfrm: reuse uncached_list to track xdsts")
== Regression Potential ==
Low. This commit is to fix a current regression.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
This occurs when tearing down an LXD container.
LXD monitor process hangs with the following stack:
$ sudo cat /proc/27043/stack
[] msleep+0x2e/0x40
[] netdev_run_todo+0x11f/0x310
[] rtnetlink_rcv+0x2d/0x30
[] netlink_unicast+0x18c/0x240
[] netlink_sendmsg+0x2dd/0x3c0
[] sock_sendmsg+0x38/0x50
[] ___sys_sendmsg+0x2e3/0x2f0
[] __sys_sendmsg+0x54/0x90
[] SyS_sendmsg+0x12/0x20
[] do_syscall_64+0x5b/0xc0
[] entry_SYSCALL64_slow_path+0x8/0x8
[] 0x
Issue submitted to LXD as well ([1]), though as indicated there, it
seems to be a kernel bug.
[1] https://github.com/lxc/lxd/issues/4208
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Jan 31 11:42:59 2018
InstallationDate: Installed on 2016-11-09 (447 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+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 1769721] Re: [ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Thanks, I am looking at it now.
--
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/1769721
Title:
[ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
As submitted upstream in this email: http://mailman.alsa-
project.org/pipermail/alsa-devel/2018-May/135685.html
This adds support for the P950ER, which has the same required fixup as
the P950HR, but has a different PCI ID.
Signed-off-by: Jeremy Soller
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 2dd34dd77447..01a6643fc7d4 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -2363,6 +2363,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = {
SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR",
ALC1220_FIXUP_CLEVO_P950),
+ SND_PCI_QUIRK(0x1558, 0x95e2, "Clevo P950ER",
ALC1220_FIXUP_CLEVO_P950),
SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530",
ALC882_FIXUP_LENOVO_Y530),
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769721/+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 1769721] Re: [ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
I built a Bionic test kernel with your patch.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1760721
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-image-unsigned, linux-modules and linux-modules-extra .deb packages.
Thanks in advance!
--
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/1769721
Title:
[ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
As submitted upstream in this email: http://mailman.alsa-
project.org/pipermail/alsa-devel/2018-May/135685.html
This adds support for the P950ER, which has the same required fixup as
the P950HR, but has a different PCI ID.
Signed-off-by: Jeremy Soller
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 2dd34dd77447..01a6643fc7d4 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -2363,6 +2363,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = {
SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR",
ALC1220_FIXUP_CLEVO_P950),
+ SND_PCI_QUIRK(0x1558, 0x95e2, "Clevo P950ER",
ALC1220_FIXUP_CLEVO_P950),
SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530",
ALC882_FIXUP_LENOVO_Y530),
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769721/+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 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel
** Attachment removed: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134463/+files/file_166588.txt ** Attachment removed: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5133956/+files/file_166588.txt ** Attachment removed: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132693/+files/file_166588.txt ** Attachment removed: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132675/+files/file_166588.txt ** Attachment removed: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132349/+files/file_166588.txt ** Attachment removed: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132345/+files/file_166588.txt ** Attachment removed: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5127947/+files/file_166588.txt ** Attachment removed: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5127895/+files/file_166588.txt ** Attachment removed: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134462/+files/qla2xxx-10.00.00.04-k.tgz ** Attachment removed: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5133955/+files/qla2xxx-10.00.00.04-k.tgz ** Attachment removed: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132692/+files/qla2xxx-10.00.00.04-k.tgz ** Attachment removed: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132674/+files/qla2xxx-10.00.00.04-k.tgz ** Attachment removed: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132344/+files/qla2xxx-10.00.00.04-k.tgz ** Attachment removed: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5127946/+files/qla2xxx-10.00.00.04-k.tgz ** Attachment removed: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5127894/+files/qla2xxx-10.00.00.04-k.tgz ** Attachment removed: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5127830/+files/qla2xxx-10.00.00.04-k.tgz ** Attachment removed: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134461/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt ** Attachment removed: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5133954/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt ** Attachment removed: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132691/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt ** Attachment removed: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132673/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt ** Attachment removed: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132343/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt ** Attachment removed: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5127945/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt ** Attachment removed: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5127893/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt ** Attachment removed: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5127829/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt ** Attachment removed: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5127714/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16
[Kernel-packages] [Bug 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush
Hello Joseph, Any update on this bug? -- 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/1744173 Title: artful: rfi-flush: Switch to new linear fallback flush Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Bug description: Change flush from congruence-first with dependencies to linear with no dependencies, which increases flush performance by 8x on P8, and 3x on P9 (as measured with null syscall loop, which will have the flush area in the L2). The flush also becomes simpler and more adaptable to different cache geometries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+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 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel
** Attachment removed: "dmesg log_boslcp3_latest for may1 run" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135514/+files/dmesg_boslcp3_may3 ** Attachment removed: "dmesg log_boslcp3_latest for may1 run" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134466/+files/dmesg_boslcp3_may3 ** Attachment removed: "dmesg log_boslcp3_latest for may1 run" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134384/+files/dmesg_boslcp3_may3 ** Attachment removed: "dmesg log_boslcp3_latest for may1 run" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134081/+files/dmesg_boslcp3_may3 ** Attachment removed: "dmesg log_boslcp3_latest for may1 run" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134054/+files/dmesg_boslcp3_may3 ** Attachment removed: "dmesg log_boslcp3_latest for may1 run" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5133959/+files/dmesg_boslcp3_may3 ** Attachment removed: "dmesg log_boslcp3_latest for may1 run" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132801/+files/dmesg_boslcp3_may3 ** Attachment removed: "boslcp3 host console tee logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135513/+files/boslcp3-host-may1.txt ** Attachment removed: "boslcp3 host console tee logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134465/+files/boslcp3-host-may1.txt ** Attachment removed: "boslcp3 host console tee logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134383/+files/boslcp3-host-may1.txt ** Attachment removed: "boslcp3 host console tee logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134080/+files/boslcp3-host-may1.txt ** Attachment removed: "boslcp3 host console tee logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5133958/+files/boslcp3-host-may1.txt ** Attachment removed: "boslcp3 host console tee logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132800/+files/boslcp3-host-may1.txt ** Attachment removed: "boslcp3 host console tee logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132695/+files/boslcp3-host-may1.txt ** Attachment removed: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135512/+files/dmesg ** Attachment removed: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134464/+files/dmesg ** Attachment removed: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134378/+files/dmesg ** Attachment removed: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134079/+files/dmesg ** Attachment removed: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5133957/+files/dmesg ** Attachment removed: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132694/+files/dmesg ** Attachment removed: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132676/+files/dmesg ** Attachment removed: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132350/+files/dmesg -- 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/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4
[Kernel-packages] [Bug 1769733] [NEW] Third screen not working displayport amd ryzen 5 2400g apu
Public bug reported: All relevant information can be found in this post: https://askubuntu.com/questions/1033287/cant-get-my-third-screen-working-ubuntu-18-04-amd-ryzen-5-2400g All errors and tries have been posted in that post. the problem is reletaed to the drivers regarding the amd ryzen 5 2400g APU, not all three of my screens turn on. only the dvi-d port and gdmi port give me output but the display port gives me a blank screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 21:52:25 2018 InstallationDate: Installed on 2018-05-06 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (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-signed in Ubuntu. https://bugs.launchpad.net/bugs/1769733 Title: Third screen not working displayport amd ryzen 5 2400g apu Status in linux-signed package in Ubuntu: New Bug description: All relevant information can be found in this post: https://askubuntu.com/questions/1033287/cant-get-my-third-screen-working-ubuntu-18-04-amd-ryzen-5-2400g All errors and tries have been posted in that post. the problem is reletaed to the drivers regarding the amd ryzen 5 2400g APU, not all three of my screens turn on. only the dvi-d port and gdmi port give me output but the display port gives me a blank screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 21:52:25 2018 InstallationDate: Installed on 2018-05-06 (0 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-signed/+bug/1769733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'
First of all, I do not use Ubuntu, I use Debian, but I thought it would be a nice input anyway, feel free to delete this if this don't help. I had the same problem the first reboot I did after a system update to: Linux version 4.9.0-6-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.88-1 (2018-04-29) Boot got stuck everytime at random: crng init, varying from 1min to 20min. A friend told me it was because the random pool was being populated everytime I booted and for some reason it was taking too long. I installed the havenge package (deb free repo) that contains an alternative algorithm to populate de RNG seeds. Apparently the problem is now solved, as my system is now booting in 13s. Hopefully this will be of some help. Anyway, if installing havenge does not work, you could purge it afterwards and no harm done... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685794 Title: Boot delayed for about 90 seconds until 'random: crng init done' Status in linux package in Ubuntu: Confirmed Bug description: Shortened dmesg output, notice the unnaturally long delay before crng init finishes: [8.533630] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [8.542239] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card1/input18 [8.542313] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card1/input19 [8.542382] input: HDA Intel PCH Dock Line Out as /devices/pci:00/:00:1b.0/sound/card1/input20 [8.542449] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card1/input21 [8.544240] cdc_ether 2-6:2.0 usb0: register 'cdc_ether' at usb-:00:14.0-6, CDC Ethernet Device, 02:1e:10:1f:00:00 [8.544271] usbcore: registered new interface driver cdc_ether [8.637660] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [8.654022] input: HP WMI hotkeys as /devices/virtual/input/input22 [8.688226] cdc_ether 2-6:2.0 enp0s20u6c2: renamed from usb0 [8.713288] iwlwifi :02:00.0 wlo1: renamed from wlan0 [9.804308] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input23 [ 98.327857] random: crng init done [ 98.330072] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 98.330073] Bluetooth: BNEP filters: protocol multicast [ 98.330077] Bluetooth: BNEP socket layer initialized [ 98.443281] kauditd_printk_skb: 90 callbacks suppressed [ 98.492927] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 98.681030] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 98.685672] IPv6: ADDRCONF(NETDEV_UP): enp0s20u6c2: link is not ready [ 98.685789] cdc_ether 2-6:2.0 enp0s20u6c2: kevent 12 may have been dropped [ 98.688384] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready [ 98.690915] iwlwifi :02:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Apr 24 14:58:33 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-18 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=9fb9fc1d-15a4-4e98-a2ae-bf572e0900d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: USH452L0B1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCV
[Kernel-packages] [Bug 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel
** Attachment removed: "fuller version of previous boslcp6 log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135531/+files/kern-boslcp6-before-and-after-bz166588-patch-fuller.log ** Attachment removed: "Logs from crashes after SAN bring-up of boslcp6 and subsequent logs of success boot after install of bz166588 patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135530/+files/kern-boslcp6-before-and-after-bz166588-patch.log ** Attachment removed: "fuller version of previous boslcp6 log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135527/+files/kern-boslcp6-before-and-after-bz166588-patch-fuller.log ** Attachment removed: "Logs from crashes after SAN bring-up of boslcp6 and subsequent logs of success boot after install of bz166588 patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135526/+files/kern-boslcp6-before-and-after-bz166588-patch.log ** Attachment removed: "boslcp3_host_reboot_consolelogs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135525/+files/boslcp3_reboot_console_logs.txt ** Attachment removed: "boslcp3_host_reboot_consolelogs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134496/+files/boslcp3_reboot_console_logs.txt ** Attachment removed: "boslcp3_host_reboot_consolelogs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134474/+files/boslcp3_reboot_console_logs.txt ** Attachment removed: "boslcp3_host_reboot_consolelogs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134387/+files/boslcp3_reboot_console_logs.txt ** Attachment removed: "boslcp3_host_reboot_consolelogs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134085/+files/boslcp3_reboot_console_logs.txt ** Attachment removed: "boslcp3_host_reboot_consolelogs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134057/+files/boslcp3_reboot_console_logs.txt ** Attachment removed: "boslcp3_host_reboot_consolelogs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5133969/+files/boslcp3_reboot_console_logs.txt ** Attachment removed: "/var/log/syslog1.file boslcp3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135524/+files/syslog.1 ** Attachment removed: "/var/log/syslog1.file boslcp3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134495/+files/syslog.1 ** Attachment removed: "/var/log/syslog1.file boslcp3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134473/+files/syslog.1 ** Attachment removed: "/var/log/syslog1.file boslcp3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134386/+files/syslog.1 ** Attachment removed: "/var/log/syslog1.file boslcp3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134084/+files/syslog.1 ** Attachment removed: "/var/log/syslog1.file boslcp3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134056/+files/syslog.1 ** Attachment removed: "/var/log/syslog1.file boslcp3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132814/+files/syslog.1 ** Attachment removed: "/var/log/syslog boslcp3 host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135523/+files/syslog ** Attachment removed: "/var/log/syslog boslcp3 host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134472/+files/syslog ** Attachment removed: "/var/log/syslog boslcp3 host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134385/+files/syslog ** Attachment removed: "/var/log/syslog boslcp3 host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134082/+files/syslog ** Attachment removed: "/var/log/syslog boslcp3 host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134055/+files/syslog ** Attachment removed: "/var/log/syslog boslcp3 host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5133960/+files/syslog ** Attachment removed: "/var/log/syslog boslcp3 host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5132802/+files/syslog ** Attachment removed: "fuller version of previous boslcp6 log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5135440/+files/kern-boslcp6-before-and-after-bz166588-patch-fuller.log ** Attachment removed: "fuller version of previous boslcp6 log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762844/+attachment/5134610/+files/kern-boslcp6-before-and-after-bz166588-patch-fuller.log ** Attachment removed: "Logs from crashes after SAN bring-up of boslcp6 and subsequent logs of success boot after install of bz
[Kernel-packages] [Bug 1769730] [NEW] Some PCIe errors not surfaced through rasdaemon
Public bug reported: [Impact] The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe errors to the AER (Advanced Error Reporting) driver, which surfaces them to userspace. However, we're currently only reporting "recoverable" errors and not errors of other types (e.g. correctable), thus hiding signs of faulty hardware from the user. [Test Case] $ sudo apt install rasdaemon # On a system that supports ACPI EINJ (dmesg | grep "ACPI: EINJ"), use the attached script to inject a correctable PCIe error. $ sudo ras-mc-ctl --errors # There should be an entry for the injected error, as shown below: No Memory errors. PCIe AER events: 1 2018-05-07 17:55:46 + Fatal error: Receiver Error No Extlog errors. No MCE errors. [Regression Risk] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- 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/1769730 Title: Some PCIe errors not surfaced through rasdaemon Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe errors to the AER (Advanced Error Reporting) driver, which surfaces them to userspace. However, we're currently only reporting "recoverable" errors and not errors of other types (e.g. correctable), thus hiding signs of faulty hardware from the user. [Test Case] $ sudo apt install rasdaemon # On a system that supports ACPI EINJ (dmesg | grep "ACPI: EINJ"), use the attached script to inject a correctable PCIe error. $ sudo ras-mc-ctl --errors # There should be an entry for the injected error, as shown below: No Memory errors. PCIe AER events: 1 2018-05-07 17:55:46 + Fatal error: Receiver Error No Extlog errors. No MCE errors. [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769730/+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 1769696] Re: [SRU][Bionic] fix false positives in W+X checking
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) 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/1769696 Title: [SRU][Bionic] fix false positives in W+X checking Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1768115] summary of crash data migrating from boslcp5 to boslcp6
--- Comment (attachment only) From mdr...@us.ibm.com 2018-05-07 14:51 EDT--- ** Attachment added: "summary of crash data migrating from boslcp5 to boslcp6" https://bugs.launchpad.net/bugs/1768115/+attachment/5135574/+files/boslcp3g1-migtest2-fail-on-lcp6-instrumented-fuller -- 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/1768115 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160. Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: Problem Description: Migration Guest running with IO stress crashed@security_file_permission+0xf4/0x160 after couple of migrations. Steps to re-create: Source host - boslcp3 Destination host - boslcp4 1.boslcp3 & boslcp4 installed with latest kernel root@boslcp3:~# uname -a Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# root@boslcp4:~# uname -a Linux boslcp4 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# 2. Installed guest boslcp3g1 with kernel and started LTP run from boslcp3 host root@boslcp3g1:~# uname -a Linux boslcp3g1 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux 3. Started migrating boslcp3g1 guest from source to destination & viceversa. 4. After couple of migrations it crashed at boslcp4 & enters into xmon 8:mon> t [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110 [c004f8a23e30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 71f1779fe280 SP (7fffe99ece50) is in userspace 8:mon> S msr= 80001033 sprg0 = pvr= 004e1202 sprg1 = c7a85800 dec= 591e3e03 sprg2 = c7a85800 sp = c004f8a234a0 sprg3 = 00010008 toc= c16eae00 dar = 023c srr0 = c00c355c srr1 = 80001033 dsisr = 4000 dscr = ppr = 0010 pir= 0011 amr= uamor = dpdes = tir = cir= fscr = 05000180 tar = pspb = mmcr0 = 8000 mmcr1 = mmcr2 = pmc1 = pmc2 = pmc3 = pmc4 = mmcra = siar = pmc5 = 026c sdar = sier = pmc6 = 0861 ebbhr = ebbrr = bescr = iamr = 4000 pidr = 0034 tidr = cpu 0x8: Vector: 700 (Program Check) at [c004f8a23220] pc: c00e4854: xmon_core+0x1f24/0x3520 lr: c00e4850: xmon_core+0x1f20/0x3520 sp: c004f8a234a0 msr: 80041033 current = 0xc004f89faf00 paca= 0xc7a85800 softe: 0irq_happened: 0x01 pid = 24028, comm = top Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.17) cpu 0x8: Exception 700 (Program Check) in xmon, returning to main loop [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110 [c004f8a23e30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 71f1779fe280 SP (7fffe99ece50) is in userspace 8:mon> r R00 = c043b7fc R16 = R01 = c004f8a23c90 R17 = ff70 R02 = c16eae00 R18 = 0a51b4bebfc8 R03 = c00279557200 R19 = 7fffe99edbb0 R04 = c003242499c0 R20 = 0a51b4c04db0 R05 = 0002 R21 = 0a51b4c20e90 R06 = 0004 R22 = 00040f00 R07 = ff81 R23 = 0a51b4c06560 R08 = ff80 R24 = ff80 R09 = R25 = 0a51b4bec2b8 R10 = R26 = 71f177bb0b20 R11 = R27 = R12 = 2000 R28 = c00279557200 R13 = c7a85800 R29 = c004c7734210 R14 = R30 = R15 = R31 = c
[Kernel-packages] [Bug 1768115] summary of crash data migrating from boslcp6 to boslcp5
--- Comment (attachment only) From mdr...@us.ibm.com 2018-05-07 14:50 EDT--- ** Attachment added: "summary of crash data migrating from boslcp6 to boslcp5" https://bugs.launchpad.net/bugs/1768115/+attachment/5135573/+files/boslcp3g1-migtest-fail-on-lcp5-instrumented-fuller -- 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/1768115 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160. Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: Problem Description: Migration Guest running with IO stress crashed@security_file_permission+0xf4/0x160 after couple of migrations. Steps to re-create: Source host - boslcp3 Destination host - boslcp4 1.boslcp3 & boslcp4 installed with latest kernel root@boslcp3:~# uname -a Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# root@boslcp4:~# uname -a Linux boslcp4 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# 2. Installed guest boslcp3g1 with kernel and started LTP run from boslcp3 host root@boslcp3g1:~# uname -a Linux boslcp3g1 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux 3. Started migrating boslcp3g1 guest from source to destination & viceversa. 4. After couple of migrations it crashed at boslcp4 & enters into xmon 8:mon> t [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110 [c004f8a23e30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 71f1779fe280 SP (7fffe99ece50) is in userspace 8:mon> S msr= 80001033 sprg0 = pvr= 004e1202 sprg1 = c7a85800 dec= 591e3e03 sprg2 = c7a85800 sp = c004f8a234a0 sprg3 = 00010008 toc= c16eae00 dar = 023c srr0 = c00c355c srr1 = 80001033 dsisr = 4000 dscr = ppr = 0010 pir= 0011 amr= uamor = dpdes = tir = cir= fscr = 05000180 tar = pspb = mmcr0 = 8000 mmcr1 = mmcr2 = pmc1 = pmc2 = pmc3 = pmc4 = mmcra = siar = pmc5 = 026c sdar = sier = pmc6 = 0861 ebbhr = ebbrr = bescr = iamr = 4000 pidr = 0034 tidr = cpu 0x8: Vector: 700 (Program Check) at [c004f8a23220] pc: c00e4854: xmon_core+0x1f24/0x3520 lr: c00e4850: xmon_core+0x1f20/0x3520 sp: c004f8a234a0 msr: 80041033 current = 0xc004f89faf00 paca= 0xc7a85800 softe: 0irq_happened: 0x01 pid = 24028, comm = top Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.17) cpu 0x8: Exception 700 (Program Check) in xmon, returning to main loop [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110 [c004f8a23e30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 71f1779fe280 SP (7fffe99ece50) is in userspace 8:mon> r R00 = c043b7fc R16 = R01 = c004f8a23c90 R17 = ff70 R02 = c16eae00 R18 = 0a51b4bebfc8 R03 = c00279557200 R19 = 7fffe99edbb0 R04 = c003242499c0 R20 = 0a51b4c04db0 R05 = 0002 R21 = 0a51b4c20e90 R06 = 0004 R22 = 00040f00 R07 = ff81 R23 = 0a51b4c06560 R08 = ff80 R24 = ff80 R09 = R25 = 0a51b4bec2b8 R10 = R26 = 71f177bb0b20 R11 = R27 = R12 = 2000 R28 = c00279557200 R13 = c7a85800 R29 = c004c7734210 R14 = R30 = R15 = R31 = c0
[Kernel-packages] [Bug 1768115] Comment bridged from LTC Bugzilla
--- Comment From mdr...@us.ibm.com 2018-05-07 14:48 EDT--- The RCU connection is possibly a red herring. I tested the above theory about RCU timeouts/warning being a trigger by modifying QEMU to allow guest timebase to be advanced artificially to trigger RCU timeouts/warnings in rapid succession and ran this for 8 hours using the same workload without seeing a crash. It seems migration is a necessary component to reproduce this. I did further tests to capture the guest memory state before/after migration to see if there's possibly an issue with dirty-page tracking or something similar that could explain the crashes, and have data from 2 crashes that show a roughly 24 bytes difference between source/target after migration within the first 100MB of guest physical address range. I have more details in the summaries/logs I'm attaching, but one example is below (from "migtest" log): root@boslcp5:~/dumps-cmp# xxd -s 0x013e -l 128 0-2.boslcp5 013e: 013e0010: 013e0020: 013e0030: 013e0040: 013e0050: 013e0060: 013e0070: root@boslcp5:~/dumps-cmp# xxd -s 0x013e -l 128 0-2.boslcp6 013e: 3403 0100 0002 2f62 6c61 7374 2f76 4.../blast/v 013e0010: 6463 3400 dc4. 013e0020: 013e0030: 013e0040: 013e0050: 013e0060: 013e0070: "blast" is part of the LTP IO test suite running in the guest. It seems some data structure related to it is present in the source guest memory, but not on the target side. Part of the structure seems to be a trigger buffer, but the preceding value might be a point or something else and may explain the crashes if that ends up being zero'd on the target side. The other summary/log I'm attaching has almost an identical inconsistent between source/target from another guest using same workload and hitting a crash: root@boslcp5:~/dumps-cmp-migtest2# xxd -s 38273024 -l 128 0-2.boslcp5 0248: c000 0100 2f62 6c61 7374 2f76 /blast/v 02480010: 6462 3400 db4. 02480020: 02480030: 02480040: 02480050: 02480060: 02480070: root@boslcp5:~/dumps-cmp-migtest2# xxd -s 38273024 -l 128 0-2.boslcp6 0248: 02480010: 02480020: 02480030: 02480040: 02480050: 02480060: 02480070: It seems highly likely there's an issue related to dirty bitmap tracking at play here. Could use some help from kernel folks on figuring out where that might lie. Crashed guests are still live ATM so let me know if there's anything I should try to gather. -- 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/1768115 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160. Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: Problem Description: Migration Guest running with IO stress crashed@security_file_permission+0xf4/0x160 after couple of migrations. Steps to re-create: Source host - boslcp3 Destination host - boslcp4 1.boslcp3 & boslcp4 installed with latest kernel root@boslcp3:~# uname -a Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# root@boslcp4:~# uname -a
Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs
Just to make sure you got the latest, the 4.17.x kernel did not work well enoguh to leave it running, it broke kernel-nfs-server among other things. I am pressenting running 4.15.0-21 and with this kernel I would still get these hangs except that I discovered disabling certain hardware offload functions stops it, so presently in my /etc/rc.local file on the affected servers I have: /sbin/ethtool -K eno1 gso off gro off tso off With this in place no hangs, slight performance penalty but no hangs. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Mon, 7 May 2018, Joseph Salisbury wrote: > Date: Mon, 07 May 2018 18:26:12 - > From: Joseph Salisbury > Reply-To: Bug 1766377 <1766...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs > > ** Tags removed: kernel-key > ** Tags added: kernel-da-key > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1766377 > > Title: > Ethernet E1000 Controller Hangs > > Status in linux package in Ubuntu: > Incomplete > Status in linux source package in Bionic: > Incomplete > > Bug description: > With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic > hanging of the LAN connection. This is happening on an Asus X99-DELUX > motherboard, controller specifications: > Intel® I218V, 1 x Gigabit LAN Controller(s) > Intel® I211-AT, 1 x Gigabit LAN > Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) > appliance > Support Teaming Technology > ASUS Turbo LAN Utility > The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM. > This machine has a number of Qemu/KVM virtual guests and is using a software > bridge to share the interface. > This did not happen with 17.10 and 4.13.0 kernel. It is happening on > multiple machines here. > Here are the messages from dmesg: > 1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: > TDH > TDT <2d> > next_to_use <2d> > next_to_clean > buffer_info[next_to_clean]: > time_stamp <13c8d0008> > next_to_watch > jiffies <13c8d0880> > next_to_watch.status <0> > MAC Status <80083> > PHY Status <796d> > PHY 1000BASE-T Status <3c00> > PHY Extended Status<3000> > PCI Status <10> > [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: > TDH > TDT <2d> > next_to_use <2d> > next_to_clean > buffer_info[next_to_clean]: > time_stamp <13c8d0008> > next_to_watch > jiffies <13c8d1040> > next_to_watch.status <0> > MAC Status <80083> > PHY Status <796d> > PHY 1000BASE-T Status <3c00> > PHY Extended Status<3000> > PCI Status <10> > [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly > [1016202.413701] bridge0: port 1(eno1) entered disabled state > [1016202.413732] bridge0: topology change detected, propagating > [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow > Control: Rx/Tx > [1016206.666708] bridge0: port 1(eno1) entered blocking state > [1016206.666712] bridge0: port 1(eno1) entered listening state > [1016216.750911] bridge0: port 1(eno1) entered learning state > [1016232.110291] bridge0: port 1(eno1) entered forwarding state > [1016232.110294] bridge0: topology change detected, sending tcn bpdu > [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for > regulatory database > [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' > [1017834.414792] platform regulatory.0: Direct firmware load for > regulatory.db failed with error -2 > [1017834.414794] cfg80211: failed to load regulatory.db > If there is any other information I can provide to aid in resolution, please > contact me, nan...@eskimo.com. Thank you! > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16 > ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 > Uname: Linux 4.15
[Kernel-packages] [Bug 1769721] Re: [ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
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/1769721
Title:
[ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
As submitted upstream in this email: http://mailman.alsa-
project.org/pipermail/alsa-devel/2018-May/135685.html
This adds support for the P950ER, which has the same required fixup as
the P950HR, but has a different PCI ID.
Signed-off-by: Jeremy Soller
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 2dd34dd77447..01a6643fc7d4 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -2363,6 +2363,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = {
SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR",
ALC1220_FIXUP_CLEVO_P950),
+ SND_PCI_QUIRK(0x1558, 0x95e2, "Clevo P950ER",
ALC1220_FIXUP_CLEVO_P950),
SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530",
ALC882_FIXUP_LENOVO_Y530),
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769721/+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 1769721] [NEW] [ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Public bug reported:
As submitted upstream in this email: http://mailman.alsa-
project.org/pipermail/alsa-devel/2018-May/135685.html
This adds support for the P950ER, which has the same required fixup as
the P950HR, but has a different PCI ID.
Signed-off-by: Jeremy Soller
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 2dd34dd77447..01a6643fc7d4 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -2363,6 +2363,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = {
SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR", ALC1220_FIXUP_CLEVO_P950),
+ SND_PCI_QUIRK(0x1558, 0x95e2, "Clevo P950ER", ALC1220_FIXUP_CLEVO_P950),
SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530", ALC882_FIXUP_LENOVO_Y530),
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Affects: linux (Ubuntu Cosmic)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Description changed:
+ As submitted upstream in this email: http://mailman.alsa-
+ project.org/pipermail/alsa-devel/2018-May/135685.html
+
This adds support for the P950ER, which has the same required fixup as
the P950HR, but has a different PCI ID.
Signed-off-by: Jeremy Soller
---
- sound/pci/hda/patch_realtek.c | 1 +
- 1 file changed, 1 insertion(+)
+ sound/pci/hda/patch_realtek.c | 1 +
+ 1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 2dd34dd77447..01a6643fc7d4 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -2363,6 +2363,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = {
- SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
- SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
- SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR",
ALC1220_FIXUP_CLEVO_P950),
+ SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
+ SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
+ SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR",
ALC1220_FIXUP_CLEVO_P950),
+ SND_PCI_QUIRK(0x1558, 0x95e2, "Clevo P950ER",
ALC1220_FIXUP_CLEVO_P950),
- SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
- SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
- SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530",
ALC882_FIXUP_LENOVO_Y530),
+ SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
+ SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
+ SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530",
ALC882_FIXUP_LENOVO_Y530),
--
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/1769721
Title:
[ALSA] [PATCH] Clevo P950ER ALC1220 Fixup
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
As submitted upstream in this email: http://mailman.alsa-
project.org/pipermail/alsa-devel/2018-May/135685.html
This adds support for the P950ER, which has the same required fixup as
the P950HR, but has a different PCI ID.
Signed-off-by: Jeremy Soller
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 2dd34dd77447..01a6643fc7d4 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -2363,6 +2363,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = {
SND_PCI_QUIRK_VENDOR(0x1462, "MSI", ALC882_FIXUP_GPIO3),
SND_PCI_QUIRK(0x147b, 0x107a, "Abit AW9D-MAX",
ALC882_FIXUP_ABIT_AW9D_MAX),
SND_PCI_QUIRK(0x1558, 0x9501, "Clevo P950HR",
ALC1220_FIXUP_CLEVO_P950),
+ SND_PCI_QUIRK(0x1558, 0x95e2, "Clevo P950ER",
ALC1220_FIXUP_CLEVO_P950),
SND_PCI_QUIRK_VENDOR(0x1558, "Clevo laptop", ALC882_FIXUP_EAPD),
SND_PCI_QUIRK(0x161f, 0x2054, "Medion laptop", ALC883_FIXUP_EAPD),
SND_PCI_QUIRK(0x17aa, 0x3a0d, "Lenovo Y530",
ALC882_FIXUP_LENOVO_Y530),
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769721/+subscripti
[Kernel-packages] [Bug 1769723] [NEW] Bionic update to v4.15.18 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.15.18 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.15.18 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1769723 Title: Bionic update to v4.15.18 stable release Status in linux package in Ubuntu: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.15.18 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.15.18 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769723/+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
