[Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade
Do you have anything connected to your thunderbolt/USB type-c port? -- 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/1738224 Title: Suspend broken after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: My machine (XPS 13 9360) won't go into suspend properly after upgrading from linux-image-4.13.0-17-generic to linux- image-4.13.0-19-generic. This affects both suspend through lid close and "systemctl suspend". Screen goes off, power led remains lit. Then after some time the screen comes back on, is stuck and lets me wait for a few before becoming responsive again. Booting back into 4.13.0-17 resolved the issue. --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeffrey1963 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5 InstallationDate: Installed on 2017-10-18 (56 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful wayland-session Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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 1738224] Re: Suspend broken after kernel upgrade
This commit might cause your issue: http://kernel.ubuntu.com/git/ubuntu /ubuntu-artful.git/commit/?id=56aa325de02d0448345358cb1b851a4c1e94f758 Return to s2idle should solve the issue. # echo s2idle > /sys/power/mem_sleep -- 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/1738224 Title: Suspend broken after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: My machine (XPS 13 9360) won't go into suspend properly after upgrading from linux-image-4.13.0-17-generic to linux- image-4.13.0-19-generic. This affects both suspend through lid close and "systemctl suspend". Screen goes off, power led remains lit. Then after some time the screen comes back on, is stuck and lets me wait for a few before becoming responsive again. Booting back into 4.13.0-17 resolved the issue. --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeffrey1963 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5 InstallationDate: Installed on 2017-10-18 (56 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful wayland-session Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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 1738523] [NEW] External HDMI monitor failed to show screen on Lenovo X1 series
Public bug reported: Test machine: Raven3-1 Image: sutton-wilkes-xenial-amd64-20171016-3 CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) BIOS: N25ET09W (0.09 ) Steps: 1. Install image on Raven3-1 2. Login system 3. Connect an external monitor 4. Try to switch display modes in mirrored, extended, displayed on external or internal. Expected result: Video signal can be mirrored, extended, displayed on external or internal. Actual result: Internal and mirror modes works. ** 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/1738523 Title: External HDMI monitor failed to show screen on Lenovo X1 series Status in linux package in Ubuntu: New Bug description: Test machine: Raven3-1 Image: sutton-wilkes-xenial-amd64-20171016-3 CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) BIOS: N25ET09W (0.09 ) Steps: 1. Install image on Raven3-1 2. Login system 3. Connect an external monitor 4. Try to switch display modes in mirrored, extended, displayed on external or internal. Expected result: Video signal can be mirrored, extended, displayed on external or internal. Actual result: Internal and mirror modes works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738523/+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 1738523] Re: External HDMI monitor failed to show screen on Lenovo X1 series
** Tags added: originate-from-1725109 sutton -- 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/1738523 Title: External HDMI monitor failed to show screen on Lenovo X1 series Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Thinkpad X1 yoga: CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Steps: 1, Connect an external monitor 2, Try to switch display modes in mirrored, extended, displayed on external or internal. [Impact] External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon [Fix] Add a workaround to bypass this TMDS_OE writing on identified laptop models. [Test Case] Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output OK. [Regression Potential] Low, it limits to ThinkPad specific laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1738523/+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 1738523] Re: External HDMI monitor failed to show screen on Lenovo X1 series
** Description changed: - Test machine: Raven3-1 - Image: sutton-wilkes-xenial-amd64-20171016-3 + Thinkpad X1 yoga: CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) - BIOS: N25ET09W (0.09 ) Steps: - 1. Install image on Raven3-1 - 2. Login system - 3. Connect an external monitor - 4. Try to switch display modes in mirrored, extended, displayed on external or internal. + 1, Connect an external monitor + 2, Try to switch display modes in mirrored, extended, displayed on external or internal. - Expected result: - Video signal can be mirrored, extended, displayed on external or internal. + [Impact] + External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon - Actual result: - Internal and mirror modes works. + [Fix] + Add a workaround to bypass this TMDS_OE writing on identified laptop models. + + [Test Case] + Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output + OK. + + [Regression Potential] + Low, it limits to ThinkPad specific laptops. -- 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/1738523 Title: External HDMI monitor failed to show screen on Lenovo X1 series Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Thinkpad X1 yoga: CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Steps: 1, Connect an external monitor 2, Try to switch display modes in mirrored, extended, displayed on external or internal. [Impact] External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon [Fix] Add a workaround to bypass this TMDS_OE writing on identified laptop models. [Test Case] Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output OK. [Regression Potential] Low, it limits to ThinkPad specific laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1738523/+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 1738523] 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 1738523 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/1738523 Title: External HDMI monitor failed to show screen on Lenovo X1 series Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Thinkpad X1 yoga: CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Steps: 1, Connect an external monitor 2, Try to switch display modes in mirrored, extended, displayed on external or internal. [Impact] External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon [Fix] Add a workaround to bypass this TMDS_OE writing on identified laptop models. [Test Case] Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output OK. [Regression Potential] Low, it limits to ThinkPad specific laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1738523/+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 1730958] Re: nuvoton-cir not working after boot
277edbabf6fece057b14fb6db5e3a34e00f42f42 is the first bad commit Hope this helps. -- 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/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Incomplete Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 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.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad
[Kernel-packages] [Bug 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34
As original poster, if I didn't continue to post oom dumps, perhaps things started to peter out on 4.8.0-39 or later. What was particular about the load that triggered this bug was heavy IO putting cache pressure on ext4 on a system where there's zero locality of reference in anything read from or written to disk (ssd backed storage). In any case, by May these data storage servers that had been triggering this issue had been decommissioned and IO strategy had changed. Now writes are written to a raw block device before being flushed to filesystem periodically using O_DSYNC, taking ext4 disk cache out of the equation. The HWE kernel is now 4.10, and judging by the edge packages soon to be 4.13, so maybe its been fixed in that time. However I'm no longer able to confirm or deny that, as there's no possible way for me to reproduce it anyway. As per Rasmus' comment, its something that only happened on production workloads. -- 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/1666260 Title: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34 Status in linux package in Ubuntu: Confirmed Bug description: Same as #1655842 - Started seeing oom-killer on multiple servers upgraded to 4.4.0-59. Unlike #1655842, also seeing the same oom-killer on multiple servers updated to 4.8.0-34. First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to 4.4.0-63. I am seeing an even more pronounced change in the memory usage, so I can only assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59 and 4.8.0-34. Either because #1655842 is not fixed, or it is only fixed for certain kinds of workloads. These are the changes I'm seeing in our memory graphs between 4.4.0-59 and 4.4.0-63/4.8.0-34. The symptoms I'm seeing are: Upgrading 4.4.0-57 -> 4.4.0-59: - /proc/meminfo:Buffers: Up from 9GB to 15GB - /proc/meminfo:Cached: Up from 5GB to 10GB - /proc/meminfo:SReclaimable: Down from 15GB to 5GB - /proc/meminfo:SUnreclaim: Staying at 50MB Upgrading 4.4.0-57 -> 4.4.0-63: - /proc/meminfo:Buffers: Up from 9GB to 26GB - /proc/meminfo:Cached: Down from 5GB to 300MB - /proc/meminfo:SReclaimable: Down from 15GB to 2GB - /proc/meminfo:SUnreclaim: Down from 50MB to 30MB Upgrading 4.4.0-57 -> 4.8.0-34: - /proc/meminfo:Buffers: Up from 9GB to 14GB - /proc/meminfo:Cached: Down from 5GB to 2GB - /proc/meminfo:SReclaimable: Down from 15GB to 14GB - /proc/meminfo:SUnreclaim: Staying at 50MB Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of not causing OOMs. Downgrading to 4.4.0-57 also works. Will also note that I haven't had a definitive OOM in 4.4.0-63. But the shift in memory usage is far too much from what I expect to be normal on these particular servers where I'm experiencing crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-63-generic 4.4.0-63.84 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' Date: Mon Feb 20 16:15:56 2017 InstallationDate: Installed on 2012-06-04 (1721 days ago) InstallationMedia: IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: System manufacturer System Product Name PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-63-generic N/A linux-backports-modules-4.4.0-63-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1106:bd10/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.
[Kernel-packages] [Bug 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34
Servers are now running on 4.10 kernels, so I guess no one cares about 4.8 anymore. -- 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/1666260 Title: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34 Status in linux package in Ubuntu: Confirmed Bug description: Same as #1655842 - Started seeing oom-killer on multiple servers upgraded to 4.4.0-59. Unlike #1655842, also seeing the same oom-killer on multiple servers updated to 4.8.0-34. First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to 4.4.0-63. I am seeing an even more pronounced change in the memory usage, so I can only assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59 and 4.8.0-34. Either because #1655842 is not fixed, or it is only fixed for certain kinds of workloads. These are the changes I'm seeing in our memory graphs between 4.4.0-59 and 4.4.0-63/4.8.0-34. The symptoms I'm seeing are: Upgrading 4.4.0-57 -> 4.4.0-59: - /proc/meminfo:Buffers: Up from 9GB to 15GB - /proc/meminfo:Cached: Up from 5GB to 10GB - /proc/meminfo:SReclaimable: Down from 15GB to 5GB - /proc/meminfo:SUnreclaim: Staying at 50MB Upgrading 4.4.0-57 -> 4.4.0-63: - /proc/meminfo:Buffers: Up from 9GB to 26GB - /proc/meminfo:Cached: Down from 5GB to 300MB - /proc/meminfo:SReclaimable: Down from 15GB to 2GB - /proc/meminfo:SUnreclaim: Down from 50MB to 30MB Upgrading 4.4.0-57 -> 4.8.0-34: - /proc/meminfo:Buffers: Up from 9GB to 14GB - /proc/meminfo:Cached: Down from 5GB to 2GB - /proc/meminfo:SReclaimable: Down from 15GB to 14GB - /proc/meminfo:SUnreclaim: Staying at 50MB Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of not causing OOMs. Downgrading to 4.4.0-57 also works. Will also note that I haven't had a definitive OOM in 4.4.0-63. But the shift in memory usage is far too much from what I expect to be normal on these particular servers where I'm experiencing crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-63-generic 4.4.0-63.84 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' Date: Mon Feb 20 16:15:56 2017 InstallationDate: Installed on 2012-06-04 (1721 days ago) InstallationMedia: IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: System manufacturer System Product Name PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-63-generic N/A linux-backports-modules-4.4.0-63-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1106:bd10/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+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 1738534] [NEW] Processor turbo dsiabled/throttled after suspend
Public bug reported: After suspending/resuming my laptop on battery power, I noticed choppy video playback. I've narrowed it down to the CPU being locked to lower frequencies after suspend/resume (only on battery). Plugging the laptop back in does not restore the normal performance, nor does suspend/resume after plugging it back in. The performance doesn't drop until after the suspend/resume, I'm not sure if it is _supposed_ to throttle when on battery, but either way the behaviour is wrong. Doing a full shutdown and restart restores the performance to normal. Prior to a suspend/resume cycle, cpupower reports: $ sudo 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: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.26 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has no effect) and turbo is disabled: $ sudo 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: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 1.80 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 950 MHz (asserted by call to kernel) boost state support: Supported: no Active: no 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Trying to re-enable turbo mode by setting the no_turbo intel_pstate /sys/ entry back to 0 is rejected: $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo 0 tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted However, these two commands *do* work around the problem, forcing turbo mode back on and then restoring the normal frequency range: sudo x86_energy_perf_policy --turbo-enable 1 sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz I also see this error in dmesg after some resumes (but the above problem sometimes happens without this error message): Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by BIOS or unavailable on processor ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 11:18:12 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 001 Device 004: ID 2232:1024 Silicon Motion Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-19-generic root=UUID=7352de8c-0017-44e1-81fb-0145ad9c1185 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900
[Kernel-packages] [Bug 1738534] Re: Processor turbo dsiabled/throttled after suspend
Just tried another scenario. If I do the full power cycle while on battery power, then it boots up with turbo disabled and frequency locked. This command then seems to work (cpupower then reports turbo is active/supported): sudo x86_energy_perf_policy --turbo-enable 1 But this command has no effect: sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz (Where, int he previous scenario, it did work.) -- 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/1738534 Title: Processor turbo dsiabled/throttled after suspend Status in linux package in Ubuntu: New Bug description: After suspending/resuming my laptop on battery power, I noticed choppy video playback. I've narrowed it down to the CPU being locked to lower frequencies after suspend/resume (only on battery). Plugging the laptop back in does not restore the normal performance, nor does suspend/resume after plugging it back in. The performance doesn't drop until after the suspend/resume, I'm not sure if it is _supposed_ to throttle when on battery, but either way the behaviour is wrong. Doing a full shutdown and restart restores the performance to normal. Prior to a suspend/resume cycle, cpupower reports: $ sudo 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: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.26 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has no effect) and turbo is disabled: $ sudo 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: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 1.80 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 950 MHz (asserted by call to kernel) boost state support: Supported: no Active: no 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Trying to re-enable turbo mode by setting the no_turbo intel_pstate /sys/ entry back to 0 is rejected: $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo 0 tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted However, these two commands *do* work around the problem, forcing turbo mode back on and then restoring the normal frequency range: sudo x86_energy_perf_policy --turbo-enable 1 sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz I also see this error in dmesg after some resumes (but the above problem sometimes happens without this error message): Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by BIOS or unavailable on processor ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 11:18:12 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 001 Device 004: ID 2232:1024 Silicon Motion Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-19-generic root=UUID
[Kernel-packages] [Bug 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34
** Tags added: kernel-fixed-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/1666260 Title: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34 Status in linux package in Ubuntu: Confirmed Bug description: Same as #1655842 - Started seeing oom-killer on multiple servers upgraded to 4.4.0-59. Unlike #1655842, also seeing the same oom-killer on multiple servers updated to 4.8.0-34. First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to 4.4.0-63. I am seeing an even more pronounced change in the memory usage, so I can only assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59 and 4.8.0-34. Either because #1655842 is not fixed, or it is only fixed for certain kinds of workloads. These are the changes I'm seeing in our memory graphs between 4.4.0-59 and 4.4.0-63/4.8.0-34. The symptoms I'm seeing are: Upgrading 4.4.0-57 -> 4.4.0-59: - /proc/meminfo:Buffers: Up from 9GB to 15GB - /proc/meminfo:Cached: Up from 5GB to 10GB - /proc/meminfo:SReclaimable: Down from 15GB to 5GB - /proc/meminfo:SUnreclaim: Staying at 50MB Upgrading 4.4.0-57 -> 4.4.0-63: - /proc/meminfo:Buffers: Up from 9GB to 26GB - /proc/meminfo:Cached: Down from 5GB to 300MB - /proc/meminfo:SReclaimable: Down from 15GB to 2GB - /proc/meminfo:SUnreclaim: Down from 50MB to 30MB Upgrading 4.4.0-57 -> 4.8.0-34: - /proc/meminfo:Buffers: Up from 9GB to 14GB - /proc/meminfo:Cached: Down from 5GB to 2GB - /proc/meminfo:SReclaimable: Down from 15GB to 14GB - /proc/meminfo:SUnreclaim: Staying at 50MB Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of not causing OOMs. Downgrading to 4.4.0-57 also works. Will also note that I haven't had a definitive OOM in 4.4.0-63. But the shift in memory usage is far too much from what I expect to be normal on these particular servers where I'm experiencing crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-63-generic 4.4.0-63.84 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' Date: Mon Feb 20 16:15:56 2017 InstallationDate: Installed on 2012-06-04 (1721 days ago) InstallationMedia: IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: System manufacturer System Product Name PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-63-generic N/A linux-backports-modules-4.4.0-63-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1106:bd10/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+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 1738534] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738534 Title: Processor turbo dsiabled/throttled after suspend Status in linux package in Ubuntu: Confirmed Bug description: After suspending/resuming my laptop on battery power, I noticed choppy video playback. I've narrowed it down to the CPU being locked to lower frequencies after suspend/resume (only on battery). Plugging the laptop back in does not restore the normal performance, nor does suspend/resume after plugging it back in. The performance doesn't drop until after the suspend/resume, I'm not sure if it is _supposed_ to throttle when on battery, but either way the behaviour is wrong. Doing a full shutdown and restart restores the performance to normal. Prior to a suspend/resume cycle, cpupower reports: $ sudo 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: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.26 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has no effect) and turbo is disabled: $ sudo 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: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 1.80 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 950 MHz (asserted by call to kernel) boost state support: Supported: no Active: no 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Trying to re-enable turbo mode by setting the no_turbo intel_pstate /sys/ entry back to 0 is rejected: $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo 0 tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted However, these two commands *do* work around the problem, forcing turbo mode back on and then restoring the normal frequency range: sudo x86_energy_perf_policy --turbo-enable 1 sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz I also see this error in dmesg after some resumes (but the above problem sometimes happens without this error message): Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by BIOS or unavailable on processor ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 11:18:12 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 001 Device 004: ID 2232:1024 Silicon Motion Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-19-generic root=UUID=7352de8c-0017-44e1-81fb-0145ad9c1185 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeSt
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Lenovo z50-70 (20354) corrrupted bios, can modify only date and time. Lastest version of bios allready installed. I've only tried ubuntu 17.10. My luck is I've installed grub2, so from usb I can load conf and boot all my operative systems. No way to do something for rewrite from the laptop. So, if you can boot the uefi live usb, another workaround is take the disk and install grub (if you haven't one installed yet), and when you boot the usb press 'c' key and load the config file for grub. If anyone have a sane bios image, please dump it and public it, so I'll try to reflash the image on my bios. Regards, Igor -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 The bug also affects Acer Aspire E5-771G. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-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/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680421] Re: Computer suspends/sleeps before login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680421 Title: Computer suspends/sleeps before login Status in systemd: Confirmed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I am not able to login into the system because it sleeps in the boot process. To fix this, I need to edit (in recovery mode) the /etc/systemd/logind.conf to replace the following options: HandleLidSwitch=ignore HandleLidSwitchDocked=ignore This behaviour started in Ubuntu 14.10. Some other users have this issue too: http://askubuntu.com/questions/829998/ubuntu-16-04-usually-suspends-before-login-and-while-logout ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic i686 ApportVersion: 2.20.4-0ubuntu3 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 6 08:25:20 2017 InstallationDate: Installed on 2017-04-06 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta i386 (20170405) MachineType: Positivo Positivo Mobile PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic root=UUID=f7649356-2952-4c27-9279-c3ab658730ad ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2006 dmi.bios.vendor: Phoenix dmi.bios.version: 4.06CJ15 dmi.board.name: M5X0V dmi.board.vendor: CLEVO Co. dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd06/08/2006:svnPositivo:pnPositivoMobile:pvrVT6198:rvnCLEVOCo.:rnM5X0V:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Positivo Mobile dmi.product.version: VT6198 dmi.sys.vendor: Positivo mtime.conffile..etc.systemd.logind.conf: 2017-04-06T08:15:16.198796 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1680421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738554] [NEW] linux: 4.14.0-12.14 -proposed tracker
Public bug reported: This bug is for tracking the 4.14.0-12.14 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 kernel-phase-changed:Saturday, 16. December 2017 16:32 UTC kernel-phase:Packaging -- swm properties -- phase: Packaging ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-development-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-development-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-development-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New => In Progress ** Changed in: kernel-development-workflow Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-development-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** 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.
[Kernel-packages] [Bug 1734901] Re: linux: 4.14.0-10.12 -proposed tracker
*** This bug is a duplicate of bug 1738554 *** https://bugs.launchpad.net/bugs/1738554 ** This bug is no longer a duplicate of bug 1736168 linux: 4.14.0-11.13 -proposed tracker ** This bug has been marked a duplicate of bug 1738554 linux: 4.14.0-12.14 -proposed tracker -- 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/1734901 Title: linux: 4.14.0-10.12 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-10.12 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 kernel-phase-changed:Tuesday, 28. November 2017 15:01 UTC kernel-phase:Packaging -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1734901/+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 1734728] Re: linux: 4.14.0-9.11 -proposed tracker
*** This bug is a duplicate of bug 1738554 *** https://bugs.launchpad.net/bugs/1738554 ** This bug is no longer a duplicate of bug 1736168 linux: 4.14.0-11.13 -proposed tracker ** This bug has been marked a duplicate of bug 1738554 linux: 4.14.0-12.14 -proposed tracker -- 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/1734728 Title: linux: 4.14.0-9.11 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-9.11 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 kernel-phase:Packaging kernel-phase-changed:Monday, 27. November 2017 18:00 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1734728/+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 1734695] Re: linux: 4.14.0-8.10 -proposed tracker
*** This bug is a duplicate of bug 1738554 *** https://bugs.launchpad.net/bugs/1738554 ** This bug is no longer a duplicate of bug 1736168 linux: 4.14.0-11.13 -proposed tracker ** This bug has been marked a duplicate of bug 1738554 linux: 4.14.0-12.14 -proposed tracker -- 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/1734695 Title: linux: 4.14.0-8.10 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-8.10 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 kernel-phase:Packaging kernel-phase-changed:Monday, 27. November 2017 14:00 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1734695/+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 1736168] Re: linux: 4.14.0-11.13 -proposed tracker
*** This bug is a duplicate of bug 1738554 *** https://bugs.launchpad.net/bugs/1738554 ** This bug has been marked a duplicate of bug 1738554 linux: 4.14.0-12.14 -proposed tracker -- 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/1736168 Title: linux: 4.14.0-11.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-11.13 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 -- 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-development-workflow/+bug/1736168/+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 1738554] Re: linux: 4.14.0-12.14 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the 4.14.0-12.14 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 + + kernel-phase-changed:Saturday, 16. December 2017 16:32 UTC + kernel-phase:Packaging ** Description changed: This bug is for tracking the 4.14.0-12.14 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 kernel-phase-changed:Saturday, 16. December 2017 16:32 UTC kernel-phase:Packaging + + -- swm properties -- + phase: Packaging -- 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/1738554 Title: linux: 4.14.0-12.14 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-12.14 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 kernel-phase-changed:Saturday, 16. December 2017 16:32 UTC kernel-phase:Packaging -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1738554/+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 1215411] Re: libcpupower.so is not installed from linux-tools
** Tags added: bionic -- 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/1215411 Title: libcpupower.so is not installed from linux-tools Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+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 1215411] Re: libcpupower.so is not installed from linux-tools
I had some discussion about this on kernel-team mailing list in September, and provided a patch which addresses Juerg Haefliger’s review: https://lists.ubuntu.com/archives/kernel-team/2017-September/086839.html However there has been no action since then :( Attaching the new version of the patch here as well. Also subscribing Juerg in case he can help us here. ** Patch added: "0001-UBUNTU-Add-new-libcpupower-1-dev-packages-for-compat.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+attachment/5023487/+files/0001-UBUNTU-Add-new-libcpupower-1-dev-packages-for-compat.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/1215411 Title: libcpupower.so is not installed from linux-tools Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+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 1738560] [NEW] touch pad stopped working after upgrade to artful 17.10
Public bug reported: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: artful ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1738560/+attachment/5023488/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Incomplete Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] 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 1738560 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: artful -- 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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Incomplete Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation
** Description changed: [Impact] console-setup continuously tries to open /dev/tty[1-6] on s390x, when such consoles do not exist on s390x. This can be seen on boot in the output from the initramfs, and during the installer. - [Cuase] + [Cause] It seems to me that the postinst of the console-setup is incorrect for s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR, z/VM, KVM) [Solution] I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it to... "guess". Usually it should be slcp, but that depends on which consoles are configured/activated in the given KVM. [Testcase] On boot, scroll all the messages and makesure there are no error messages about inability to open /dev/tty* [Original Bug Report] During the installation (z/VM guest and KVM virtual machine) of Ubuntu Server 16.04.1 (and 16.04.2) repeating messages of the form: " Select and install software ... 10% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 20% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 30%... 40% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 50% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 60% can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 90% The system is going down NOW Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system reboot 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 00 Storage cleared - system reset. 00 zIPL .. " They start to occur when the software gets installed: "Select and install software ... 10% can't open /dev/tty4: No such device or address" And only stop with the final system reboot at the end of the installation. ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1704929 Title: Repeating "can't open /dev/ttyX: No such device or address" messages during installation Status in Ubuntu on IBM z Systems: Confirmed Status in console-setup package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: [Impact] console-setup continuously tries to open /dev/tty[1-6] on s390x, when such consoles do not exist on s390x. This can be seen on boot in the output from the initramfs, and during the installer. [Cause] It seems to me that the postinst of the console-setup is incorrect for s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR, z/VM, KVM) [Solution] I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it to... "guess". Usually it should be slcp, but that depends on which consoles are configured/activated in the given KVM. [Testcase] On boot, scroll all the messages and makesure there are no error messages about inability to open /dev/tty* [Original Bug Report] During the installation (z/VM guest and KVM virtual machine) of Ubuntu Server 16.04.1 (and 16.04.2) repeating messages of the form: " Select and install software ... 10% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such d
[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10
apport information ** Tags added: apport-collected ** Description changed: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 + --- + ApportVersion: 2.20.7-0ubuntu3.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: pang 1303 F pulseaudio + CurrentDesktop: GNOME + DistroRelease: Ubuntu 17.10 + HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df + InstallationDate: Installed on 2017-12-16 (0 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + MachineType: Micro-Star International Co., Ltd. GP62M 7RD + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=es_ES.UTF-8 + SHELL=/usr/bin/fish + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-19-generic N/A + linux-backports-modules-4.13.0-19-generic N/A + linux-firmware 1.169.1 + Tags: artful + Uname: Linux 4.13.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/07/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: E16J9IMS.307 + dmi.board.asset.tag: Default string + dmi.board.name: MS-16J9 + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: REV:1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: + dmi.product.family: G + dmi.product.name: GP62M 7RD + dmi.product.version: REV:1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023489/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:c
[Kernel-packages] [Bug 1738560] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023500/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023498/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023496/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023491/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023497/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023495/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023493/+files/JournalErrors.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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023499/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023501/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023490/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023503/+files/WifiSyslog.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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] Re: touch pad stopped working after upgrade to artful 17.10
I booted with a 16.10 usb disk, the touchpad works, the output of xinput.list is: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ BisonCam, NB Pro id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] ↳ MSI WMI hotkeys id=14 [slave keyboard (3)] -- 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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023492/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023502/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1738560/+attachment/5023494/+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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] Re: touch pad stopped working after upgrade to artful 17.10
Installed apport, run apport-collect 1738560, changed status to 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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738560] Re: touch pad stopped working after upgrade to artful 17.10
However, if I run xinput list within 17.10 I get: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB Optical Mouse id=7[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=8[slave keyboard (3)] ** 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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Also affects Lenovo Flex 3-1120 with BIOS C0CN31WW (v 4.5). Problem presented after installing latest system updates for Ubuntu 17.10. Symptoms are exactly the same; BIOS can be entered from system hotkey F12, but changes to BIOS settings cannot be saved. -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 The bug also affects Acer Aspire E5-771G. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-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/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported
The latest firmware is not included in the linux-firmware package on artful. Is this intended? I see that it is only included in the latest LTS and bionic. -- 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/1520343 Title: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported Status in HWE Next: New Status in OEM Priority Project: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: --- STATUS 2016-03-17: == WARNING: You need at least kernel 4.5.0 for the following new fix to work, else refer to the old method described in post #22 == The support for this card has now been merged to https://github.com/kvalo/ath10k-firmware. The repository now contains the required board.bin, board-2.bin and firmware-4.bin files for the card to initialize and connect to a bgn-access point (5GHz (ac- protocol) is still untested, feel free to modify this if you can confirm it works). Here are the new commands to get you online: sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/ sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true Reboot or reload the ath10k_pci module and you should be able to connect! --- STATUS 2015-12-22: Currently there is a fix for this problem in post #22 (originally post #19, but reposted due to command typos!) which seems to have fixed the issue for many. This bug is unique to revision 32 of the card [168c:003e], fixes for older revisions don't seem to work. There are a couple of issues regarding the fix for some people (not all): 1. Wireless works, but network throughput stops some time after connecting to access point 2. Bluetooth communications take a noticeable performance hit when transferring something over WiFi --- Original description: I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card doesn't work in it or 16.04. The card has the device id 168c:003e as many other cards, for example the Qualcomm Atheros Killer (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a newer revision number (32) and the suggested fixes work only partially and the wireless is unusable. The computer has just been released this summer and is Intel Skylake -based. I've tried the patch from bug 1383184, which has a fix for the card revision 20: Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch files: board.bin firmware-4.bin notice_ath10k_firmware-4.txt ath10k_pci succeeds in loading the firmware, but it seems that the firmware is not working correctly: dmesg | grep ath [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [5.678420] ath10k_pci :07:00.0: Direct firmware load for ath10k/cal-pci-:07:00.0.bin failed with error -2 [5.678773] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2 [5.678781] ath10k_pci :07:00.0: failed to load spec board file, falling back to generic: -2 [5.679445] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32 [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [8.200607] ath: EEPROM regdomain: 0x6c [8.200614] ath: EEPROM indicates we should expect a direct regpair map [8.200619] ath: Country alpha2 being used: 00 [8.200621] ath: Regpair used: 0x6c [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0 [ 13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 16.461416] ath10k_pci :07:00.0: could not suspend target (-11) [ 24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -1
[Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade
kai-Heng, on both occasions (suspend working and broken on latest kernel) I had nothing connected to my USB-C port. I'll test s2idle later and get back to you. -- 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/1738224 Title: Suspend broken after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: My machine (XPS 13 9360) won't go into suspend properly after upgrading from linux-image-4.13.0-17-generic to linux- image-4.13.0-19-generic. This affects both suspend through lid close and "systemctl suspend". Screen goes off, power led remains lit. Then after some time the screen comes back on, is stuck and lets me wait for a few before becoming responsive again. Booting back into 4.13.0-17 resolved the issue. --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeffrey1963 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5 InstallationDate: Installed on 2017-10-18 (56 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful wayland-session Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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 1738224] Re: Suspend broken after kernel upgrade
That particular commit actually breaks proper s2idle. Because of it S3 should be used instead on 9360. It was intentionally broken because of some reported regression by one guy with an nvme SSD of a particular vendor. Can you please check which SSD you have? Nvme info command on it can be helpful. On Sat, Dec 16, 2017, 16:05 Jeffrey Bouter <1738...@bugs.launchpad.net> wrote: > kai-Heng, on both occasions (suspend working and broken on latest > kernel) I had nothing connected to my USB-C port. I'll test s2idle later > and get back to you. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1738224 > > Title: > Suspend broken after kernel upgrade > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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/1738224 Title: Suspend broken after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: My machine (XPS 13 9360) won't go into suspend properly after upgrading from linux-image-4.13.0-17-generic to linux- image-4.13.0-19-generic. This affects both suspend through lid close and "systemctl suspend". Screen goes off, power led remains lit. Then after some time the screen comes back on, is stuck and lets me wait for a few before becoming responsive again. Booting back into 4.13.0-17 resolved the issue. --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeffrey1963 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5 InstallationDate: Installed on 2017-10-18 (56 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful wayland-session Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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
This computer is installed in a secondary house, and it is not planned to use it before March 2010 Was fresh install Will run command apport-collect 1737423 but in some month Will test the kernel you indicate, but in some month ** 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/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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737423/+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 1738224] Re: Suspend broken after kernel upgrade
Mario, THNSN5512GPUK NVMe TOSHIBA 512GB would be the model -- 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/1738224 Title: Suspend broken after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: My machine (XPS 13 9360) won't go into suspend properly after upgrading from linux-image-4.13.0-17-generic to linux- image-4.13.0-19-generic. This affects both suspend through lid close and "systemctl suspend". Screen goes off, power led remains lit. Then after some time the screen comes back on, is stuck and lets me wait for a few before becoming responsive again. Booting back into 4.13.0-17 resolved the issue. --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeffrey1963 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5 InstallationDate: Installed on 2017-10-18 (56 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful wayland-session Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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 1738224] Re: Suspend broken after kernel upgrade
Kai-Heng, A cat on /sys/power/mem_sleep already shows: [s2idle] deep -- 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/1738224 Title: Suspend broken after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: My machine (XPS 13 9360) won't go into suspend properly after upgrading from linux-image-4.13.0-17-generic to linux- image-4.13.0-19-generic. This affects both suspend through lid close and "systemctl suspend". Screen goes off, power led remains lit. Then after some time the screen comes back on, is stuck and lets me wait for a few before becoming responsive again. Booting back into 4.13.0-17 resolved the issue. --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeffrey1963 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5 InstallationDate: Installed on 2017-10-18 (56 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful wayland-session Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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 1738224] Re: Suspend broken after kernel upgrade
Did you manually set s2idle? That policy shouldn't have been picked unless you were on 4.14. On Sat, Dec 16, 2017, 17:55 Jeffrey Bouter <1738...@bugs.launchpad.net> wrote: > Kai-Heng, > > A cat on /sys/power/mem_sleep already shows: > > [s2idle] deep > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1738224 > > Title: > Suspend broken after kernel upgrade > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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/1738224 Title: Suspend broken after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: My machine (XPS 13 9360) won't go into suspend properly after upgrading from linux-image-4.13.0-17-generic to linux- image-4.13.0-19-generic. This affects both suspend through lid close and "systemctl suspend". Screen goes off, power led remains lit. Then after some time the screen comes back on, is stuck and lets me wait for a few before becoming responsive again. Booting back into 4.13.0-17 resolved the issue. --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeffrey1963 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5 InstallationDate: Installed on 2017-10-18 (56 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful wayland-session Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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 332467] lovely things
*** This bug is a duplicate of bug 252900 *** https://bugs.launchpad.net/bugs/252900 I've seen a few things that might interest you , just glimpse here http://www.kupiopal.ru/ahlgx.php?UE8zMzI0NjdAYnVHUy5MYXVuY2hwYWQubmVU - Un gâteau sec si il existe un petit dénombrement qui réclame l'autorisation de s'avérer être placé sur le disque dur de votre poste informatique . Une fois que vous êtes à l'unisson , le liste est boniment et le cookie favorise analyser le trafic Web ou vous permet de connaitre quand vous venez visiter une page particulier . Les cookies permettent aux applications Web de vous vous apporter des réponses comme qu'individu . L'application Web peut roder ses procédés à vos besoins , goûts et dégoût en rassemblant ainsi qu'en mémorisant vos réponses sur vos choix . -- 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/332467 Title: package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to install/upgrade: unable to make backup link of `./boot/vmlinuz-2.6.27-7-generic' before installing new version: Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: Automated bug report information should be attached. Fresh install using wubi. Applied 259 updates after opening OpenOffice.org twice and file browsing but no other system usage. ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 8.10 ErrorMessage: unable to make backup link of `./boot/vmlinuz-2.6.27-7-generic' before installing new version: Operation not permitted LsUsb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse Plus] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux-image-2.6.27-7-generic 2.6.27-7.14 ProcCmdLine: User Name=UUID=1542-16FE loop=/hostname/disks/home/username.disk ro ROOTFLAGS=sync quiet splash ProcVersionSignature: Ubuntu 2.6.27-7.14-generic SourcePackage: linux Title: package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to install/upgrade: unable to make backup link of `./boot/vmlinuz-2.6.27-7-generic' before installing new version: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/332467/+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 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen
** Changed in: linux
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/1724639
Title:
Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in openSUSE:
Unknown
Bug description:
Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
the install went smoothly. When the system is rebooted, however,
switching to graphics mode results in the below described screen
corruption:-
Left Hand Side 80% of screen black with a blue of white pixels and some blue
lines at the top
Right Hand Side 20% of screen OK.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.13.0-16-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.20.7-0ubuntu3
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ian 918 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,144dca00,0011'
Controls : 25
Simple ctrls : 12
CurrentDesktop: LXDE
Date: Wed Oct 18 18:30:15 2017
HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
InstallationDate: Installed on 2017-10-18 (0 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.13.0-16-generic N/A
linux-backports-modules-4.13.0-16-generic N/A
linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 07CA.M002.20090414.KTW
dmi.board.name: NC10
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: NC10
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1724639/+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 1724164] Re: BUG: unable to handle kernel paging request at 34025020
[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/1724164 Title: BUG: unable to handle kernel paging request at 34025020 Status in linux package in Ubuntu: Expired Bug description: Just booted computer. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: charlie2393 F pulseaudio Date: Tue Oct 17 09:16:04 2017 DuplicateSignature: BUG: unable to handle kernel paging request at location EIP: vfs_read+0xa8/0x140 SS:ESP: 0068:f4691f4c Failure: oops InstallationDate: Installed on 2017-07-28 (80 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170725.1) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: NOVATECH LTD PERSONAL COMPUTER ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=650586f6-4f8f-4d72-853f-15154b747716 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: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel paging request at 34025020 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: xxx-xxx dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: PERSONAL COMPUTER dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724164/+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 1724242] Re: BUG: unable to handle kernel NULL pointer dereference at (null)
[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/1724242 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Expired Bug description: This happened completely random while using the desktop. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raony 2597 F pulseaudio Date: Tue Oct 17 13:54:12 2017 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: timecounter_read+0x13/0x60 RSP: 9db6c3c23de0 Failure: oops HibernationDevice: RESUME=UUID=c691d0d6-cb77-4e0a-a159-1b91f7144028 InstallationDate: Installed on 2017-09-27 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20F9006JUK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=b49f6369-36d7-41d6-a0f4-6376bf56e3be 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: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET45W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F9006JUK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET45W(1.13):bd06/02/2016:svnLENOVO:pn20F9006JUK:pvrThinkPadT460s:rvnLENOVO:rn20F9006JUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20F9006JUK dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724242/+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 1723032] Re: Copying data from SATA SSD to NVMe SSD causes kernel bug
[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/1723032 Title: Copying data from SATA SSD to NVMe SSD causes kernel bug Status in linux package in Ubuntu: Expired Bug description: I'm trying to move my Ubuntu Server installation to a new NVMe SSD (Samsung EVO 960 500GB) using dd: sudo dd if=/dev/sda3 of=/dev/nvme0n1p3 bs=1M conv=fsync status=progress The first two partitions, EFI System and the Linux root fs, copy fine but copying the third partition causes the dd command to hang after a few seconds. If I kill the dd command the whole system freezes. Running Ubuntu Desktop 17.4 live image on a USB-connected SD-card My SATA SSD is partitioned as follows: Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 75902613-8162-4C99-A7CF-1642374BEDBB DeviceStart End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 59643903 58593280 28G Linux filesystem /dev/sda3 59643904 250068991 190425088 90.8G Linux LVM dmesg output: [ 140.327890] [ cut here ] [ 140.327914] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/drivers/nvme/host/pci.c:566! [ 140.327940] invalid opcode: [#1] SMP [ 140.327953] Modules linked in: bnep snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec crct10dif_pclmul crc32_pclmul snd_hda_core snd_hwdep ghash_clmulni_intel snd_pcm pcbc aesni_intel snd_seq_midi snd_seq_midi_event aes_x86_64 snd_rawmidi crypto_simd glue_helper cryptd intel_cstate snd_seq intel_rapl_perf snd_seq_device input_leds joydev snd_timer serio_raw snd hci_uart soundcore btbcm btqca btintel bluetooth mei_me mei intel_lpss_acpi intel_lpss mac_hid acpi_pad shpchp intel_pch_thermal parport_pc ppdev lp parport ip_tables x_tables autofs4 aufs nls_utf8 isofs btrfs xor raid6_pq nls_iso8859_1 dm_mirror dm_region_hash dm_log uas usb_storage hid_generic usbhid i915 i2c_algo_bit [ 140.328186] drm_kms_helper syscopyarea e1000e psmouse ptp pps_core nvme sysfillrect sysimgblt nvme_core fb_sys_fops ahci drm libahci wmi i2c_hid pinctrl_sunrisepoint video pinctrl_intel hid fjes [ 140.328243] CPU: 1 PID: 170 Comm: kworker/u4:3 Not tainted 4.10.0-19-generic #21-Ubuntu [ 140.328267] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.22.0 for D3417-B1x07/26/2017 [ 140.328302] Workqueue: writeback wb_workfn (flush-259:0) [ 140.328320] task: 8a80a84eab00 task.stack: 968380aac000 [ 140.328341] RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme] [ 140.328358] RSP: 0018:968380aaf670 EFLAGS: 00010286 [ 140.328375] RAX: 0078 RBX: f200 RCX: 1000 [ 140.328397] RDX: 0010 RSI: 0200 RDI: 0246 [ 140.328418] RBP: 968380aaf748 R08: 8a80a1d66000 R09: f200 [ 140.328440] R10: 1000 R11: 8a7fbcdf R12: a4dfa000 [ 140.328461] R13: 0002f400 R14: 8a80a1d66000 R15: 0200 [ 140.328483] FS: () GS:8a80ae50() knlGS: [ 140.328508] CS: 0010 DS: ES: CR0: 80050033 [ 140.328526] CR2: 7f0422b5f2b5 CR3: 4ba09000 CR4: 002406e0 [ 140.328547] Call Trace: [ 140.328560] blk_mq_try_issue_directly+0x7e/0x100 [ 140.328576] blk_mq_make_request+0x3cf/0x4e0 [ 140.328592] generic_make_request+0xf2/0x1d0 [ 140.328607] submit_bio+0x73/0x150 [ 140.328619] ? __percpu_counter_add+0x4f/0x60 [ 140.328635] submit_bh_wbc+0x152/0x180 [ 140.328648] __block_write_full_page+0x176/0x360 [ 140.328664] ? I_BDEV+0x20/0x20 [ 140.328676] ? I_BDEV+0x20/0x20 [ 140.328688] block_write_full_page+0x13b/0x160 [ 140.328702] blkdev_writepage+0x18/0x20 [ 140.328716] __writepage+0x13/0x30 [ 140.328728] write_cache_pages+0x205/0x530 [ 140.328742] ? wb_position_ratio+0x1f0/0x1f0 [ 140.328757] generic_writepages+0x56/0x90 [ 140.328771] ? delayacct_end+0x56/0x60 [ 140.328784] ? __delayacct_blkio_end+0x30/0x50 [ 140.328799] blkdev_writepages+0x2f/0x40 [ 140.328813] do_writepages+0x1e/0x30 [ 140.328826] __writeback_single_inode+0x45/0x320 [ 140.328842] ? wake_up_q+0x80/0x80 [ 140.328855] writeback_sb_inodes+0x266/0x5f0 [ 140.328870] __writeback_inodes_wb+0x92/0xc0 [ 140.328884] wb_writeback+0x268/0x300 [ 140.328897] wb_workfn+0x234/0x410 [ 140.328910] pro
[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10
I just went through the info from apport: wow, do you really collect and publish in the open that much info? It doesn't have passwords, but it potentially has emails, paths, wireless networks IDs, attack vectors etc. And it's irrevertible, I cannot hide that data from the internet bots now. I think that's illegal in Europe, isn't it? You should at least change the text of the ubuntu bot, something like: "the information you provide might contain this and that info and will be published to anyone and for ever, by running the command you accept these terms, blah blah", but I think it's better to actually display that message when running apport. -- 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/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1638862] Re: [Dell Latitude E5460] bluetooth is not supported on 16.04.1.
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1638862 Title: [Dell Latitude E5460] bluetooth is not supported on 16.04.1. Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Dell Latitude E5460 (CID 201507-18776) Ubuntu 16.04.1 (updated to kernel 4.4.0-45-generic) [Steps to reproduce] 1. Install Ubuntu 16.04.1 via Live USB. 2. On desktop, open the terminal to issue the command to check the status[1]. 3. Open Bluetooth setup window. 4. Update the system and do the same steps from 1~3. [Expected Result] Bluetooth setup window is ready for you to setup bluetooth devices. [Actual Result] The bluetooth setup window shows "Bluetooth is disabled". [1] ubuntu@201507-18776:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 2: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1523 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 3 17:56:50 2016 HibernationDevice: RESUME=UUID=e104534d-b5db-4ef1-9955-2b8178924bcb InstallationDate: Installed on 2016-11-02 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=a02ea97e-ff66-470f-aa17-74a60670faa1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd01/10/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Latest drm-intel-next 4.15 hasn't the touchpad working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
