[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume
BTW, when it "worked fine", did it boot with Linux 4.10 instead of 4.11? -- 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/1708043 Title: Lenovo X1 Carbon Gen5 fails to resume Status in linux package in Ubuntu: Confirmed Bug description: Last week it worked fine, this week however if I open the lid for it to resume the power light flashes for a bit, then comes on solid, the but screen stays blank and the machine is unresponsive. I have to power it off / on again in order to use it. It might be related to the APST issue with Samsung NVMe SSDs, I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dean 1652 F...m pulseaudio /dev/snd/controlC0: dean 1652 F pulseaudio CurrentDesktop: GNOME Date: Tue Aug 1 17:39:20 2017 HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nvme_core.default_ps_max_latency_us=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET37W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW 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:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1708043 Title: Lenovo X1 Carbon Gen5 fails to resume Status in linux package in Ubuntu: Confirmed Bug description: Last week it worked fine, this week however if I open the lid for it to resume the power light flashes for a bit, then comes on solid, the but screen stays blank and the machine is unresponsive. I have to power it off / on again in order to use it. It might be related to the APST issue with Samsung NVMe SSDs, I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dean 1652 F...m pulseaudio /dev/snd/controlC0: dean 1652 F pulseaudio CurrentDesktop: GNOME Date: Tue Aug 1 17:39:20 2017 HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nvme_core.default_ps_max_latency_us=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET37W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW 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:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1694787] Re: Dell Precision 5520 crashing after connecting to ethernet
Which dongle do you use? Is it a Dell one? ** Changed in: linux (Ubuntu) Status: Expired => 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/1694787 Title: Dell Precision 5520 crashing after connecting to ethernet Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell Precision 5520 that came pre-installed with Ubuntu 16.04. I use it at home on wireless exclusively. When I take it to work, I plug it into ethernet via the ethernet dongle. Without fail, almost an hour later, all networking stops working. I can ping neither domains not IPs, even on my local network. If I try to run `sudo service networking restart` or `sudo service network-manager restart` then Gnome-Shell hangs. If I switch to an Fn terminal, I can run some commands, but eventually all sudo commands there hang too. Holding down ctrl+alt+del says "ctrl+alt+del pressed 7 times in 2 seconds, rebooting immediately", but after 15 minutes, it still doesn't reboot, forcing me to do a hard reboot. Afterwards, the laptop works fine until the next day, when it all happens again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2444 F pulseaudio CurrentDesktop: GNOME Date: Wed May 31 14:14:09 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-03-09 (82 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=b3c434bc-85ba-4b42-a137-374a088e6c0f ro acpi_rev_override quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-78-generic N/A linux-backports-modules-4.4.0-78-generic N/A linux-firmware1.157.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.2 dmi.board.name: 0GPNW9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.2:bd12/28/2016:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0GPNW9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694787/+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 1705921] Re: Wifi isn't identified for Ampak AP6212
Oops, it should be "0x1E" instead. Sorry. -- 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/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+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 1705921] Re: Wifi isn't identified for Ampak AP6212
I still get only the silly Audio Port error. Is there a way I can tell dmesg to ignore it? On Wed, Aug 2, 2017 at 10:31 AM Kai-Heng Feng wrote: > Oops, it should be "0x1E" instead. Sorry. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1705921 > > Title: > Wifi isn't identified for Ampak AP6212 > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak > AP6212 card (neither for wifi nor for bluetooth). Here is the output of > dmesg |less: > file.io/PkdSHh > --- > ApportVersion: 2.20.1-0ubuntu2.9 > Architecture: i386 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', > '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CRDA: >country IL: DFS-ETSI > (2402 - 2482 @ 40), (N/A, 20), (N/A) > (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR > (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS > CurrentDesktop: XFCE > DistroRelease: Ubuntu 16.04 > HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 > InstallationDate: Installed on 2017-04-06 (108 days ago) > InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 > (20160719) > MachineType: Insyde BayTrail > Package: linux (not installed) > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic > root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 > RelatedPackageVersions: >linux-restricted-modules-4.10.0-27-generic N/A >linux-backports-modules-4.10.0-27-generic N/A >linux-firmware 1.157.11 > RfKill: >1: phy1: Wireless LAN > Soft blocked: no > Hard blocked: no > Tags: xenial > Uname: Linux 4.10.0-27-generic i686 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 10/29/2014 > dmi.bios.vendor: INSYDE Corp. > dmi.bios.version: DSO.00 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: Type2 - Board Product Name > dmi.board.vendor: Type2 - Board Manufacturer > dmi.board.version: Type2 - Board Version > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Chassis Manufacturer > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: > dmi.product.name: BayTrail > dmi.product.version: Type1 - TBD by OEM > dmi.sys.vendor: Insyde > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+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/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1699772] Re: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing
** Changed in: linux (Ubuntu) Status: Fix Released => 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/1699772 Title: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux- image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in commons-daemon package in Ubuntu: Confirmed Status in eclipse package in Ubuntu: Confirmed Status in imagej package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in octave package in Ubuntu: Confirmed Status in python-jpype package in Ubuntu: Confirmed Status in rustc package in Ubuntu: Confirmed Status in scilab package in Ubuntu: Confirmed Status in linux package in Debian: Confirmed Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+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 1654068] Comment bridged from LTC Bugzilla
--- Comment From hasri...@in.ibm.com 2017-08-02 04:45 EDT--- Issue is still observed on Ubuntu 17.10 as well, 4.11 kernel # uname -a Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux [ 493.883642] kdump-tools[1132]: The kernel version is not supported. [ 493.883861] kdump-tools[1132]: The makedumpfile operation may be incomplete. [ 493.884133] kdump-tools[1132]: The dumpfile is saved to /var/crash/201708020409/dump-incomplete. [ 493.884379] kdump-tools[1132]: makedumpfile Completed. [ 493.935115] kdump-tools[1132]: * kdump-tools: saved vmcore in /var/crash/201708020409 [ 494.123081] kdump-tools[1132]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201708020409/dmesg.201708020409 [ 494.186862] kdump-tools[1132]: The kernel version is not supported. [ 494.187237] kdump-tools[1132]: The makedumpfile operation may be incomplete. [ 494.187536] kdump-tools[1132]: The dmesg log is saved to /var/crash/201708020409/dmesg.201708020409. [ 494.187785] kdump-tools[1132]: makedumpfile Completed. [ 494.188064] kdump-tools[1132]: * kdump-tools: saved dmesg content in /var/crash/201708020409 [ 494.210743] kdump-tools[1132]: Wed, 02 Aug 2017 04:17:14 -0400 [ 494.274866] kdump-tools[1132]: Failed to read reboot parameter file: No such file or directory [ 494.275209] kdump-tools[1132]: Rebooting. Thanks, Harish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1654068 Title: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Yakkety: Confirmed Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-25 23:00:37 == ---Problem Description--- Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. ---Steps to Reproduce--- 1. Configure fadump. 2. Trigger crash. Logs = root@alp9:/home/ubuntu# service kdump status ? kdump.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) root@alp9:/home/ubuntu# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-32-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-32-generic current state:ready to fadump [-1;-1f[3.187917] kdump-tools[1049]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201612220208/dump-incomplete Copying data : [100.0 %] | [5.711820] kdump-tools[1049]: The kernel version is not supported. [5.712201] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.712515] kdump-tools[1049]: The dumpfile is saved to /var/crash/201612220208/dump-incomplete. [5.712849] kdump-tools[1049]: makedumpfile Completed. [5.720901] kdump-tools[1049]: * kdump-tools: saved vmcore in /var/crash/201612220208 [5.916826] kdump-tools[1049]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201612220208/dmesg.201612220208 [5.941113] kdump-tools[1049]: The kernel version is not supported. [5.941612] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.941969] kdump-tools[1049]: The dmesg log is saved to /var/crash/201612220208/dmesg.201612220208. [5.942340] kdump-tools[1049]: makedumpfile Completed. [5.942648] kdump-tools[1049]: * kdump-tools: saved dmesg content in /var/crash/201612220208 [5.994508] kdump-tools[1049]: Thu, 22 Dec 2016 02:08:35 -0500 [6.018241] kdump-tools[1049]: Rebooting. [6.025884] reboot: Restarting system == Comment: #3 - Hari Krishna Bathini - 2017-01-04 07:14:19 == Canonical, Please pick the latest version of makedumpfile (v1.6.1) which officially supports 4.8 kernels. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1654068/+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 1708120] [NEW] Lenovo Yoga 910 Sensors
Public bug reported: Rotation and light sensors don't function in the current 4.11.0-10 Artful kernel. After applying the patch at https://patchwork.kernel.org/patch/9842347/, the sensors function correctly and brightness and screen rotation work as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1521 F pulseaudio CurrentDesktop: GNOME Date: Wed Aug 2 11:02:28 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 138a:0094 Validity Sensors, Inc. Bus 001 Device 002: ID 5986:2104 Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80VF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=fc5e4cce-4a17-4d07-980b-c8ee385a945e ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2JCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Agera dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 910-13IKB dmi.modalias: dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB: dmi.product.name: 80VF dmi.product.version: Lenovo YOGA 910-13IKB dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1708120 Title: Lenovo Yoga 910 Sensors Status in linux package in Ubuntu: New Bug description: Rotation and light sensors don't function in the current 4.11.0-10 Artful kernel. After applying the patch at https://patchwork.kernel.org/patch/9842347/, the sensors function correctly and brightness and screen rotation work as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1521 F pulseaudio CurrentDesktop: GNOME Date: Wed Aug 2 11:02:28 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 138a:0094 Validity Sensors, Inc. Bus 001 Device 002: ID 5986:2104 Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80VF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=fc5e4cce-4a17-4d07-980b-c8ee385a945e ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2JCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Agera dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 910-13IKB dmi.modalias: dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB: dmi.product.name: 80VF dmi.product.version: Lenovo YOGA 910-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packag
[Kernel-packages] [Bug 1708120] Re: Lenovo Yoga 910 Sensors
** Patch added: "HID-Add-quirk-for-Lenovo-Yoga-910-with-ITE-Chips.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708120/+attachment/4925770/+files/HID-Add-quirk-for-Lenovo-Yoga-910-with-ITE-Chips.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/1708120 Title: Lenovo Yoga 910 Sensors Status in linux package in Ubuntu: New Bug description: Rotation and light sensors don't function in the current 4.11.0-10 Artful kernel. After applying the patch at https://patchwork.kernel.org/patch/9842347/, the sensors function correctly and brightness and screen rotation work as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1521 F pulseaudio CurrentDesktop: GNOME Date: Wed Aug 2 11:02:28 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 138a:0094 Validity Sensors, Inc. Bus 001 Device 002: ID 5986:2104 Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80VF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=fc5e4cce-4a17-4d07-980b-c8ee385a945e ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2JCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Agera dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 910-13IKB dmi.modalias: dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB: dmi.product.name: 80VF dmi.product.version: Lenovo YOGA 910-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708120/+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 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Just installed the new BIOS 310 update for OS 'Others'. I can't try the microphone jack at the moment, but the headphone jack still doesn't work and the area around usb ports and audio jacks on the right side of my laptop is again pretty hot. I applied the hdajackretask headphones fix (override pin 0x16 to headpohne), but after that the rear left and the rear right speaker doesn't work - so I restored the original settings. ELAN touchpad remains completely dead: [4.629104] hid-multitouch 0018:04F3:3043.0007: Ignoring the extra HID_DG_INPUTMODE [4.629142] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input16 [4.629305] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 -- 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/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I:
[Kernel-packages] [Bug 1708120] 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/1708120 Title: Lenovo Yoga 910 Sensors Status in linux package in Ubuntu: Confirmed Bug description: Rotation and light sensors don't function in the current 4.11.0-10 Artful kernel. After applying the patch at https://patchwork.kernel.org/patch/9842347/, the sensors function correctly and brightness and screen rotation work as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1521 F pulseaudio CurrentDesktop: GNOME Date: Wed Aug 2 11:02:28 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 138a:0094 Validity Sensors, Inc. Bus 001 Device 002: ID 5986:2104 Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80VF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=fc5e4cce-4a17-4d07-980b-c8ee385a945e ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2JCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Agera dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 910-13IKB dmi.modalias: dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB: dmi.product.name: 80VF dmi.product.version: Lenovo YOGA 910-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708120/+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 1654068] Re: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful.
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1654068 Title: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Yakkety: Confirmed Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-25 23:00:37 == ---Problem Description--- Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. ---Steps to Reproduce--- 1. Configure fadump. 2. Trigger crash. Logs = root@alp9:/home/ubuntu# service kdump status ? kdump.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) root@alp9:/home/ubuntu# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-32-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-32-generic current state:ready to fadump [-1;-1f[3.187917] kdump-tools[1049]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201612220208/dump-incomplete Copying data : [100.0 %] | [5.711820] kdump-tools[1049]: The kernel version is not supported. [5.712201] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.712515] kdump-tools[1049]: The dumpfile is saved to /var/crash/201612220208/dump-incomplete. [5.712849] kdump-tools[1049]: makedumpfile Completed. [5.720901] kdump-tools[1049]: * kdump-tools: saved vmcore in /var/crash/201612220208 [5.916826] kdump-tools[1049]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201612220208/dmesg.201612220208 [5.941113] kdump-tools[1049]: The kernel version is not supported. [5.941612] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.941969] kdump-tools[1049]: The dmesg log is saved to /var/crash/201612220208/dmesg.201612220208. [5.942340] kdump-tools[1049]: makedumpfile Completed. [5.942648] kdump-tools[1049]: * kdump-tools: saved dmesg content in /var/crash/201612220208 [5.994508] kdump-tools[1049]: Thu, 22 Dec 2016 02:08:35 -0500 [6.018241] kdump-tools[1049]: Rebooting. [6.025884] reboot: Restarting system == Comment: #3 - Hari Krishna Bathini - 2017-01-04 07:14:19 == Canonical, Please pick the latest version of makedumpfile (v1.6.1) which officially supports 4.8 kernels. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1654068/+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 1702910] Re: System freeze after in6_dev_finish_destroy errors
We've successfully reproduced the error on a newly built instance. We'll proceed to run the mainline kernel on the same instance. Worth noting that it took 441529 seconds (5.1 days) since boot for this to manifest in this case. On our previous instance the time to failure was in the order of a hours to days. [441529.300238] [ cut here ] [441529.300288] WARNING: CPU: 1 PID: 10409 at /build/linux-lts-xenial-N0BD4p/linux-lts-xenial-4.4.0/net/ipv6/addrconf_core.c:159 in6_dev_finish_destroy+0x6b/0xb0() [441529.300359] CPU: 1 PID: 10409 Comm: kworker/u4:0 Not tainted 4.4.0-87-generic #110~14.04.1-Ubuntu [441529.300361] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/17/2015 [441529.300374] Workqueue: netns cleanup_net [441529.300376] 880088ddbbb8 813de2dc [441529.300378] 81d7aa60 880088ddbbf0 8107ea46 880139e5a400 [441529.300380] 0006 880088ddbcc0 [441529.300382] Call Trace: [441529.300398] [] dump_stack+0x63/0x87 [441529.300413] [] warn_slowpath_common+0x86/0xc0 [441529.300415] [] warn_slowpath_null+0x1a/0x20 [441529.300417] [] in6_dev_finish_destroy+0x6b/0xb0 [441529.300421] [] ip6_route_dev_notify+0x110/0x130 [441529.300425] [] notifier_call_chain+0x49/0x70 [441529.300427] [] raw_notifier_call_chain+0x16/0x20 [441529.300429] [] call_netdevice_notifiers_info+0x35/0x60 [441529.300432] [] netdev_run_todo+0x157/0x300 [441529.300436] [] ? rollback_registered_many+0x22e/0x2e0 [441529.300440] [] rtnl_unlock+0xe/0x10 [441529.300442] [] default_device_exit_batch+0x138/0x150 [441529.300452] [] ? __wake_up_sync+0x20/0x20 [441529.300454] [] ops_exit_list.isra.4+0x52/0x60 [441529.300456] [] cleanup_net+0x1b3/0x280 [441529.300461] [] process_one_work+0x150/0x3f0 [441529.300463] [] worker_thread+0x11a/0x470 [441529.300471] [] ? __schedule+0x359/0x980 [441529.300473] [] ? rescuer_thread+0x310/0x310 [441529.300475] [] kthread+0xd6/0xf0 [441529.300477] [] ? do_exit+0x655/0xae0 [441529.300479] [] ? kthread_park+0x60/0x60 [441529.300481] [] ret_from_fork+0x3f/0x70 [441529.300483] [] ? kthread_park+0x60/0x60 [441529.300484] ---[ end trace 5e09761f8674a0af ]--- [441529.300485] [ cut here ] [441529.300487] WARNING: CPU: 1 PID: 10409 at /build/linux-lts-xenial-N0BD4p/linux-lts-xenial-4.4.0/net/ipv6/addrconf_core.c:160 in6_dev_finish_destroy+0xa4/0xb0() [441529.300510] CPU: 1 PID: 10409 Comm: kworker/u4:0 Tainted: GW 4.4.0-87-generic #110~14.04.1-Ubuntu [441529.300511] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/17/2015 [441529.300513] Workqueue: netns cleanup_net [441529.300514] 880088ddbbb8 813de2dc [441529.300515] 81d7aa60 880088ddbbf0 8107ea46 880139e5a400 [441529.300517] 0006 880088ddbcc0 [441529.300518] Call Trace: [441529.300520] [] dump_stack+0x63/0x87 [441529.300522] [] warn_slowpath_common+0x86/0xc0 [441529.300524] [] warn_slowpath_null+0x1a/0x20 [441529.300526] [] in6_dev_finish_destroy+0xa4/0xb0 [441529.300528] [] ip6_route_dev_notify+0x110/0x130 [441529.300529] [] notifier_call_chain+0x49/0x70 [441529.300531] [] raw_notifier_call_chain+0x16/0x20 [441529.300533] [] call_netdevice_notifiers_info+0x35/0x60 [441529.300535] [] netdev_run_todo+0x157/0x300 [441529.300538] [] ? rollback_registered_many+0x22e/0x2e0 [441529.300540] [] rtnl_unlock+0xe/0x10 [441529.300543] [] default_device_exit_batch+0x138/0x150 [441529.300546] [] ? __wake_up_sync+0x20/0x20 [441529.300549] [] ops_exit_list.isra.4+0x52/0x60 [441529.300552] [] cleanup_net+0x1b3/0x280 [441529.300555] [] process_one_work+0x150/0x3f0 [441529.300558] [] worker_thread+0x11a/0x470 [441529.300561] [] ? __schedule+0x359/0x980 [441529.300563] [] ? rescuer_thread+0x310/0x310 [441529.300564] [] kthread+0xd6/0xf0 [441529.300566] [] ? do_exit+0x655/0xae0 [441529.300568] [] ? kthread_park+0x60/0x60 [441529.300570] [] ret_from_fork+0x3f/0x70 [441529.300571] [] ? kthread_park+0x60/0x60 [441529.300573] ---[ end trace 5e09761f8674a0b0 ]--- [441529.300775] PGD b97cd067 PUD b97ad067 PMD 0 [441529.300877] Oops: [#1] SMP [441529.301242] CPU: 1 PID: 10409 Comm: kworker/u4:0 Tainted: GW 4.4.0-87-generic #110~14.04.1-Ubuntu [441529.301281] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/17/2015 [441529.302097] Workqueue: netns cleanup_net [441529.302114] task: 880057de0e00 ti: 880088dd8000 task.ti: 880088dd8000 [441529.302143] RIP: 0010:[] [] in6_dev_finish_destroy+0x2d/0xb0 [441529.328032] RSP: 0018:880088ddbc10 EFLAGS: 00010246 [441529.328064] RAX: 0024 RBX: 880139e5a400 RCX: 0006 [441529.328092] RD
[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
Same issue when powering off my computer: Linux acer-veriton 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Aug 2 11:30:23 acer-veriton systemd[1]: Stopping LSB: VirtualBox Linux kernel module... Aug 2 11:30:23 acer-veriton kernel: [10362.177603] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Aug 2 11:30:23 acer-veriton kernel: [10362.177606] ecryptfs_readpage: Error decrypting page; rc = [-4] Aug 2 11:30:23 acer-veriton kernel: [10362.178488] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-4] Aug 2 11:30:23 acer-veriton kernel: [10362.178491] ecryptfs_write_end: Error encrypting page (upper index [0x0012]) Aug 2 11:30:23 acer-veriton systemd[1]: Stopping crash report submission daemon... Aug 2 11:30:23 acer-veriton kernel: [10362.212362] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Aug 2 11:30:23 acer-veriton kernel: [10362.212365] ecryptfs_write_begin: Error decrypting page at index [0]; rc = [-4] Aug 2 11:30:23 acer-veriton rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1063" x-info="http://www.rsyslog.com";] exiting on signal 15. -- 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/1585434 Title: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Status in linux package in Ubuntu: Confirmed Bug description: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] ecryptfs_readpage: Error decrypting page; rc = [-4] I dont' have this issue showing in dmesg when using 3.19 kernel, only with later kernels. Is it related to selecting encrypted home on install or something? I don't notice any issues with performance because of it or have any other error messages. I am using default ubuntu xenial 16.04 with unity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cooloutac 2054 F pulseaudio /dev/snd/pcmC0D0p: cooloutac 2054 F...m pulseaudio /dev/snd/controlC0: cooloutac 2054 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 22:38:44 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1 InstallationDate: Installed on 2016-05-20 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 7100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585434/+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 1654068] Re: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful.
However, the message is mostly cosmetic in its nature. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1654068 Title: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Yakkety: Confirmed Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-25 23:00:37 == ---Problem Description--- Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. ---Steps to Reproduce--- 1. Configure fadump. 2. Trigger crash. Logs = root@alp9:/home/ubuntu# service kdump status ? kdump.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) root@alp9:/home/ubuntu# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-32-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-32-generic current state:ready to fadump [-1;-1f[3.187917] kdump-tools[1049]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201612220208/dump-incomplete Copying data : [100.0 %] | [5.711820] kdump-tools[1049]: The kernel version is not supported. [5.712201] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.712515] kdump-tools[1049]: The dumpfile is saved to /var/crash/201612220208/dump-incomplete. [5.712849] kdump-tools[1049]: makedumpfile Completed. [5.720901] kdump-tools[1049]: * kdump-tools: saved vmcore in /var/crash/201612220208 [5.916826] kdump-tools[1049]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201612220208/dmesg.201612220208 [5.941113] kdump-tools[1049]: The kernel version is not supported. [5.941612] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.941969] kdump-tools[1049]: The dmesg log is saved to /var/crash/201612220208/dmesg.201612220208. [5.942340] kdump-tools[1049]: makedumpfile Completed. [5.942648] kdump-tools[1049]: * kdump-tools: saved dmesg content in /var/crash/201612220208 [5.994508] kdump-tools[1049]: Thu, 22 Dec 2016 02:08:35 -0500 [6.018241] kdump-tools[1049]: Rebooting. [6.025884] reboot: Restarting system == Comment: #3 - Hari Krishna Bathini - 2017-01-04 07:14:19 == Canonical, Please pick the latest version of makedumpfile (v1.6.1) which officially supports 4.8 kernels. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1654068/+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 1707887] Re: Failed to build libhugetlbfs-2.20 from source on 4.4 / 3.13 Trusty ARM64
More debug shows that it will acquire the following status from the libhugetlbfs-2.20/Makefile CC64 = $(CC) ELF64 = aarch64elf TMPLIB64 = lib64 CUSTOM_LDSCRIPTS = no And in libhugetlbfs-2.20/test/Makefile the linkhuge_rw will be built since: ifdef ELF64 ifeq ($(CUSTOM_LDSCRIPTS),yes) TESTS += $(LDSCRIPT_TESTS) $(HUGELINK_TESTS) $(HUGELINK_TESTS:%=xB.%) \ $(HUGELINK_TESTS:%=xBDT.%) else TESTS += $(LDSCRIPT_TESTS) $(HUGELINK_TESTS) $(HUGELINK_RW_TESTS) endif >From here it will pass the ELF64 check, but go to the else as the >CUSTOM_LDSCRIPTS is "no". This explains why it's not being built for amd64 -- 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/1707887 Title: Failed to build libhugetlbfs-2.20 from source on 4.4 / 3.13 Trusty ARM64 Status in linux package in Ubuntu: Incomplete Bug description: It will fail to build libhugetlbfs verison 2.20 for SRU regression- test on 3.13 ARM64 It's ok on 4.10 / 4.4 ARM64, but not 4.4.0-88.111~14.04.1 and 3.13.0-126.175 ARM64 Looks like it's failing with: LD64 (hugelink_rw test) obj64/linkhuge_rw /usr/bin/ld: final link failed: File truncated This is not a regression. As this issue has been seen before. Complete make log: $ make VERSION version string: 2.20 CC64 obj64/elflink.o AS64 obj64/sys-aarch64elf.o CC64 obj64/hugeutils.o CC64 obj64/version.o CC64 obj64/init.o CC64 obj64/morecore.o CC64 obj64/debug.o CC64 obj64/alloc.o CC64 obj64/shm.o CC64 obj64/kernel-features.o LD64 (shared) obj64/libhugetlbfs.so AR64 obj64/libhugetlbfs.a CC64 obj64/init_privutils.o LD64 (shared) obj64/libhugetlbfs_privutils.so CCHOST obj/init_privutils.o CCHOST obj/debug.o CCHOST obj/hugeutils.o CCHOST obj/kernel-features.o ARHOST obj/libhugetlbfs_privutils.a CC64 obj64/gethugepagesize.o CC64 obj64/testutils.o CC64 obj64/libtestutils.o LD64 (lib test) obj64/gethugepagesize CC64 obj64/test_root.o LD64 (lib test) obj64/test_root CC64 obj64/find_path.o LD64 (lib test) obj64/find_path CC64 obj64/unlinked_fd.o LD64 (lib test) obj64/unlinked_fd CC64 obj64/misalign.o LD64 (lib test) obj64/misalign CC64 obj64/readback.o LD64 (lib test) obj64/readback CC64 obj64/truncate.o LD64 (lib test) obj64/truncate CC64 obj64/shared.o LD64 (lib test) obj64/shared CC64 obj64/private.o LD64 (lib test) obj64/private CC64 obj64/fork-cow.o LD64 (lib test) obj64/fork-cow CC64 obj64/empty_mounts.o LD64 (lib test) obj64/empty_mounts CC64 obj64/large_mounts.o LD64 (lib test) obj64/large_mounts CC64 obj64/meminfo_nohuge.o LD64 (lib test) obj64/meminfo_nohuge CC64 obj64/ptrace-write-hugepage.o LD64 (lib test) obj64/ptrace-write-hugepage CC64 obj64/icache-hygiene.o icache-hygiene.c: In function ‘test_once’: icache-hygiene.c:158:11: warning: ignoring return value of ‘ftruncate’, declared with attribute warn_unused_result [-Wunused-result] ftruncate(fd, 0); ^ icache-hygiene.c:162:12: warning: ignoring return value of ‘ftruncate’, declared with attribute warn_unused_result [-Wunused-result] ftruncate(fd, 0); ^ icache-hygiene.c:171:11: warning: ignoring return value of ‘ftruncate’, declared with attribute warn_unused_result [-Wunused-result] ftruncate(fd, hpage_size); ^ icache-hygiene.c:177:11: warning: ignoring return value of ‘ftruncate’, declared with attribute warn_unused_result [-Wunused-result] ftruncate(fd, 0); ^ LD64 (lib test) obj64/icache-hygiene CC64 obj64/slbpacaflush.o LD64 (lib test) obj64/slbpacaflush CC64 obj64/chunk-overcommit.o LD64 (lib test) obj64/chunk-overcommit CC64 obj64/mprotect.o LD64 (lib test) obj64/mprotect CC64 obj64/alloc-instantiate-race.o alloc-instantiate-race.c: In function ‘thread_racer’: alloc-instantiate-race.c:114:6: warning: variable ‘rc’ set but not used [-Wunused-but-set-variable] int rc; ^ LD64 (lib test) obj64/alloc-instantiate-race CC64 obj64/mlock.o LD64 (lib test) obj64/mlock CC64 obj64/truncate_reserve_wraparound.o LD64 (lib test) obj64/truncate_reserve_wraparound CC64 obj64/truncate_sigbus_versus_oom.o LD64 (lib test) obj64/truncate_sigbus_versus_oom CC64 obj64/map_high_truncate_2.o LD64 (lib test) obj64/map_high_truncate_2 CC64 obj64/truncate_above_4GB.o LD64 (lib test) obj64/truncate_above_4GB CC64 obj64
[Kernel-packages] [Bug 1654068] Re: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful.
** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1654068 Title: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Yakkety: Confirmed Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-25 23:00:37 == ---Problem Description--- Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. ---Steps to Reproduce--- 1. Configure fadump. 2. Trigger crash. Logs = root@alp9:/home/ubuntu# service kdump status ? kdump.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) root@alp9:/home/ubuntu# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-32-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-32-generic current state:ready to fadump [-1;-1f[3.187917] kdump-tools[1049]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201612220208/dump-incomplete Copying data : [100.0 %] | [5.711820] kdump-tools[1049]: The kernel version is not supported. [5.712201] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.712515] kdump-tools[1049]: The dumpfile is saved to /var/crash/201612220208/dump-incomplete. [5.712849] kdump-tools[1049]: makedumpfile Completed. [5.720901] kdump-tools[1049]: * kdump-tools: saved vmcore in /var/crash/201612220208 [5.916826] kdump-tools[1049]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201612220208/dmesg.201612220208 [5.941113] kdump-tools[1049]: The kernel version is not supported. [5.941612] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.941969] kdump-tools[1049]: The dmesg log is saved to /var/crash/201612220208/dmesg.201612220208. [5.942340] kdump-tools[1049]: makedumpfile Completed. [5.942648] kdump-tools[1049]: * kdump-tools: saved dmesg content in /var/crash/201612220208 [5.994508] kdump-tools[1049]: Thu, 22 Dec 2016 02:08:35 -0500 [6.018241] kdump-tools[1049]: Rebooting. [6.025884] reboot: Restarting system == Comment: #3 - Hari Krishna Bathini - 2017-01-04 07:14:19 == Canonical, Please pick the latest version of makedumpfile (v1.6.1) which officially supports 4.8 kernels. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1654068/+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 1707610] Re: fanctl does not stop setup on first match
** Changed in: ubuntu-fan (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-fan (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-fan (Ubuntu) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1707610 Title: fanctl does not stop setup on first match Status in ubuntu-fan package in Ubuntu: In Progress Status in ubuntu-fan source package in Xenial: New Status in ubuntu-fan source package in Zesty: New Bug description: SRU Justification (Zesty/Xenial) Impact: When /etc/network/fan contains two entries for the same mapping (for example on mapping for the generic network mapping and one for a specific interface) it will try to set up the same Fan bridge twice. Fix: Add a break which exits the setup loop once there has been one successful run. Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, and host has for example a 192.168.1.0/24 address. Then trying to use fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8 would show an error now and with the fix applied work ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+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 1707610] Re: fanctl does not stop setup on first match
We actually only want to bring up enabled Fan Networks, fanatic is indicating this via its use of --auto. Use this to modify the config scanner. Does the attached (untested) patch help. ** Patch added: "0001-fanctl-only-bring-up-enabled-Fan-Networks-in-auto-mo.patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+attachment/4925799/+files/0001-fanctl-only-bring-up-enabled-Fan-Networks-in-auto-mo.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1707610 Title: fanctl does not stop setup on first match Status in ubuntu-fan package in Ubuntu: In Progress Status in ubuntu-fan source package in Xenial: New Status in ubuntu-fan source package in Zesty: New Bug description: SRU Justification (Zesty/Xenial) Impact: When /etc/network/fan contains two entries for the same mapping (for example on mapping for the generic network mapping and one for a specific interface) it will try to set up the same Fan bridge twice. Fix: Add a break which exits the setup loop once there has been one successful run. Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, and host has for example a 192.168.1.0/24 address. Then trying to use fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8 would show an error now and with the fix applied work ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+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 1707610] Re: fanctl does not stop setup on first match
This is occuring because fanatic is trying to bring up the newly configured Fan Network as if it had been brought up automatically. This is done to bring the system into a state that is equivalent to having had the configuration for this Fan Network at boot time. However it does it using an interface which appear to fanctl as a user "who knows what they are doing", and it brings up all matching prefixes; in this case a prefix which is purely in the file as an example/preferred configuration. ** Also affects: ubuntu-fan (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1707610 Title: fanctl does not stop setup on first match Status in ubuntu-fan package in Ubuntu: In Progress Status in ubuntu-fan source package in Xenial: New Status in ubuntu-fan source package in Zesty: New Bug description: SRU Justification (Zesty/Xenial) Impact: When /etc/network/fan contains two entries for the same mapping (for example on mapping for the generic network mapping and one for a specific interface) it will try to set up the same Fan bridge twice. Fix: Add a break which exits the setup loop once there has been one successful run. Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, and host has for example a 192.168.1.0/24 address. Then trying to use fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8 would show an error now and with the fix applied work ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+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 1708130] [NEW] ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests
You have been subscribed to a public bug: == Comment: #0 - INDIRA P. JOGA - 2017-07-07 03:56:54 == Description: -- Started Leaf IO and BASE(without smt tests)and then tried to change the SMT value manually where it hangs UBUNTU BUILD: 4.10.0-26-generic Steps to re-create: -- > Installed latest Ubuntu160403 kernel on system lotkvm 4.10.0-26-generic > Leaf microcode: KMIPP113 > Started Leaf IO and BASE tests(without smt tests). root@lotkvm:/home# show.report.py HOSTNAMEKERNEL VERSION DISTRO INFO ---- lotkvm 4.10.0-26-genericUbuntu 16.04.2 LTS \n \l Current Time: Tue Jul 4 00:55:37 2017 Job-ID FOCUS Start-Time DurationFunction -- - -- 1 IO 20170704-00:44:45 0.0 hr(s) 10.0 min(s) IO_Focus 2 BASE20170704-00:44:52 0.0 hr(s) 10.0 min(s) Test FOCUS IO BASESUM TOTAL 76 25 101 FAIL0 4 4 PASS76 21 97 (%) (100%) (84%) (96%) >Now manually changed the smt value root@lotkvm:/home# ppc64_cpu --smt SMT=8 root@lotkvm:/home# date Tue Jul 4 00:46:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=2 root@lotkvm:/home# ppc64_cpu --smt SMT=2 root@lotkvm:/home# date Tue Jul 4 00:50:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=4 root@lotkvm:/home# ppc64_cpu --smt SMT=4 root@lotkvm:/home# date Tue Jul 4 00:54:38 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=8 [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2055.142915] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2055.143226] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 seconds. [ 2055.143647] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 seconds. [ 2055.144029] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds. [ 2055.144353] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds. [ 2055.144665] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds. [ 2055.144936] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds. [ 2055.145195] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2175.974848] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2175.975144] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > root@lotkvm:# ps -eaf | grep ppc* root 48054 12068 0 01:24 pts/000:00:00 grep --color=auto ppc* root 80305 5719 0 00:54 hvc0 00:00:00 ppc64_cpu --smt 8 > ppc64_cpu --smt command hangs here . Not able to change the SMT value from 4 to 8. > Attached dmesg logs == Comment: #2 - VIPIN K. PARASHAR - 2017-07-07 13:29:41 == >From kernel logs = [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2055.142915] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143055] jbd2/nvme0n1p6- D0 22052 2 0x0800 [ 2055.143059] Call Trace: [ 2055.143063] [c01e1c6537f0] [c017dfd2206c] 0xc017dfd2206c (unreliable) [ 2055.143070] [c01e1c6539c0] [c001be70] __switch_to+0x2c0/0x450 [ 2055.143075] [c01e1c653a20] [c0b9ee48] __schedule+0x2f8/0x970 [ 2055.143
[Kernel-packages] [Bug 1708130] Re: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708130 Title: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - INDIRA P. JOGA - 2017-07-07 03:56:54 == Description: -- Started Leaf IO and BASE(without smt tests)and then tried to change the SMT value manually where it hangs UBUNTU BUILD: 4.10.0-26-generic Steps to re-create: -- > Installed latest Ubuntu160403 kernel on system lotkvm 4.10.0-26-generic > Leaf microcode: KMIPP113 > Started Leaf IO and BASE tests(without smt tests). root@lotkvm:/home# show.report.py HOSTNAMEKERNEL VERSION DISTRO INFO ---- lotkvm 4.10.0-26-genericUbuntu 16.04.2 LTS \n \l Current Time: Tue Jul 4 00:55:37 2017 Job-IDFOCUS Start-Time DurationFunction --- -- 1 IO 20170704-00:44:45 0.0 hr(s) 10.0 min(s) IO_Focus 2 BASE20170704-00:44:52 0.0 hr(s) 10.0 min(s) Test FOCUS IO BASESUM TOTAL 76 25 101 FAIL 0 4 4 PASS 76 21 97 (%) (100%) (84%) (96%) >Now manually changed the smt value root@lotkvm:/home# ppc64_cpu --smt SMT=8 root@lotkvm:/home# date Tue Jul 4 00:46:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=2 root@lotkvm:/home# ppc64_cpu --smt SMT=2 root@lotkvm:/home# date Tue Jul 4 00:50:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=4 root@lotkvm:/home# ppc64_cpu --smt SMT=4 root@lotkvm:/home# date Tue Jul 4 00:54:38 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=8 [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2055.142915] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2055.143226] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 seconds. [ 2055.143647] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 seconds. [ 2055.144029] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds. [ 2055.144353] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds. [ 2055.144665] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds. [ 2055.144936] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds. [ 2055.145195] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2175.974848] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2175.975144] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > root@lotkvm:# ps -eaf | grep ppc* root 48054 12068 0 01:24 pts/000:00:00 grep --color=auto ppc* root 80305
[Kernel-packages] [Bug 1654068] Re: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful.
** Changed in: makedumpfile (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1654068 Title: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Yakkety: Confirmed Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-25 23:00:37 == ---Problem Description--- Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. ---Steps to Reproduce--- 1. Configure fadump. 2. Trigger crash. Logs = root@alp9:/home/ubuntu# service kdump status ? kdump.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) root@alp9:/home/ubuntu# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-32-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-32-generic current state:ready to fadump [-1;-1f[3.187917] kdump-tools[1049]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201612220208/dump-incomplete Copying data : [100.0 %] | [5.711820] kdump-tools[1049]: The kernel version is not supported. [5.712201] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.712515] kdump-tools[1049]: The dumpfile is saved to /var/crash/201612220208/dump-incomplete. [5.712849] kdump-tools[1049]: makedumpfile Completed. [5.720901] kdump-tools[1049]: * kdump-tools: saved vmcore in /var/crash/201612220208 [5.916826] kdump-tools[1049]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201612220208/dmesg.201612220208 [5.941113] kdump-tools[1049]: The kernel version is not supported. [5.941612] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.941969] kdump-tools[1049]: The dmesg log is saved to /var/crash/201612220208/dmesg.201612220208. [5.942340] kdump-tools[1049]: makedumpfile Completed. [5.942648] kdump-tools[1049]: * kdump-tools: saved dmesg content in /var/crash/201612220208 [5.994508] kdump-tools[1049]: Thu, 22 Dec 2016 02:08:35 -0500 [6.018241] kdump-tools[1049]: Rebooting. [6.025884] reboot: Restarting system == Comment: #3 - Hari Krishna Bathini - 2017-01-04 07:14:19 == Canonical, Please pick the latest version of makedumpfile (v1.6.1) which officially supports 4.8 kernels. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1654068/+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 1708130] dmesg_logs
Default Comment by Bridge ** Attachment added: "dmesg_logs" https://bugs.launchpad.net/bugs/1708130/+attachment/4925811/+files/file1 -- 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/1708130 Title: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - INDIRA P. JOGA - 2017-07-07 03:56:54 == Description: -- Started Leaf IO and BASE(without smt tests)and then tried to change the SMT value manually where it hangs UBUNTU BUILD: 4.10.0-26-generic Steps to re-create: -- > Installed latest Ubuntu160403 kernel on system lotkvm 4.10.0-26-generic > Leaf microcode: KMIPP113 > Started Leaf IO and BASE tests(without smt tests). root@lotkvm:/home# show.report.py HOSTNAMEKERNEL VERSION DISTRO INFO ---- lotkvm 4.10.0-26-genericUbuntu 16.04.2 LTS \n \l Current Time: Tue Jul 4 00:55:37 2017 Job-IDFOCUS Start-Time DurationFunction --- -- 1 IO 20170704-00:44:45 0.0 hr(s) 10.0 min(s) IO_Focus 2 BASE20170704-00:44:52 0.0 hr(s) 10.0 min(s) Test FOCUS IO BASESUM TOTAL 76 25 101 FAIL 0 4 4 PASS 76 21 97 (%) (100%) (84%) (96%) >Now manually changed the smt value root@lotkvm:/home# ppc64_cpu --smt SMT=8 root@lotkvm:/home# date Tue Jul 4 00:46:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=2 root@lotkvm:/home# ppc64_cpu --smt SMT=2 root@lotkvm:/home# date Tue Jul 4 00:50:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=4 root@lotkvm:/home# ppc64_cpu --smt SMT=4 root@lotkvm:/home# date Tue Jul 4 00:54:38 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=8 [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2055.142915] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2055.143226] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 seconds. [ 2055.143647] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 seconds. [ 2055.144029] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds. [ 2055.144353] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds. [ 2055.144665] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds. [ 2055.144936] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds. [ 2055.145195] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2175.974848] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2175.975144] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > root@lotkvm:# ps -eaf | grep ppc* root 48054 12068 0 01:24 pts/000:00:00 grep --color=auto ppc* root 80305 5719 0 00:54 hvc0 00:00:00 ppc64_cpu --smt 8 > ppc64_cpu --smt command hangs here . Not able to change the SMT value from 4 to 8. > Attached dmesg logs == Co
[Kernel-packages] [Bug 1708130] dmesg_logs
Default Comment by Bridge ** Attachment added: "dmesg_logs" https://bugs.launchpad.net/bugs/1708130/+attachment/4925809/+files/file -- 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/1708130 Title: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - INDIRA P. JOGA - 2017-07-07 03:56:54 == Description: -- Started Leaf IO and BASE(without smt tests)and then tried to change the SMT value manually where it hangs UBUNTU BUILD: 4.10.0-26-generic Steps to re-create: -- > Installed latest Ubuntu160403 kernel on system lotkvm 4.10.0-26-generic > Leaf microcode: KMIPP113 > Started Leaf IO and BASE tests(without smt tests). root@lotkvm:/home# show.report.py HOSTNAMEKERNEL VERSION DISTRO INFO ---- lotkvm 4.10.0-26-genericUbuntu 16.04.2 LTS \n \l Current Time: Tue Jul 4 00:55:37 2017 Job-IDFOCUS Start-Time DurationFunction --- -- 1 IO 20170704-00:44:45 0.0 hr(s) 10.0 min(s) IO_Focus 2 BASE20170704-00:44:52 0.0 hr(s) 10.0 min(s) Test FOCUS IO BASESUM TOTAL 76 25 101 FAIL 0 4 4 PASS 76 21 97 (%) (100%) (84%) (96%) >Now manually changed the smt value root@lotkvm:/home# ppc64_cpu --smt SMT=8 root@lotkvm:/home# date Tue Jul 4 00:46:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=2 root@lotkvm:/home# ppc64_cpu --smt SMT=2 root@lotkvm:/home# date Tue Jul 4 00:50:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=4 root@lotkvm:/home# ppc64_cpu --smt SMT=4 root@lotkvm:/home# date Tue Jul 4 00:54:38 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=8 [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2055.142915] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2055.143226] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 seconds. [ 2055.143647] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 seconds. [ 2055.144029] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds. [ 2055.144353] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds. [ 2055.144665] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds. [ 2055.144936] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds. [ 2055.145195] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2175.974848] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2175.975144] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > root@lotkvm:# ps -eaf | grep ppc* root 48054 12068 0 01:24 pts/000:00:00 grep --color=auto ppc* root 80305 5719 0 00:54 hvc0 00:00:00 ppc64_cpu --smt 8 > ppc64_cpu --smt command hangs here . Not able to change the SMT value from 4 to 8. > Attached dmesg logs == Com
[Kernel-packages] [Bug 1708130] hung-logs
Default Comment by Bridge ** Attachment added: "hung-logs" https://bugs.launchpad.net/bugs/1708130/+attachment/4925810/+files/hung-logs.zip -- 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/1708130 Title: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - INDIRA P. JOGA - 2017-07-07 03:56:54 == Description: -- Started Leaf IO and BASE(without smt tests)and then tried to change the SMT value manually where it hangs UBUNTU BUILD: 4.10.0-26-generic Steps to re-create: -- > Installed latest Ubuntu160403 kernel on system lotkvm 4.10.0-26-generic > Leaf microcode: KMIPP113 > Started Leaf IO and BASE tests(without smt tests). root@lotkvm:/home# show.report.py HOSTNAMEKERNEL VERSION DISTRO INFO ---- lotkvm 4.10.0-26-genericUbuntu 16.04.2 LTS \n \l Current Time: Tue Jul 4 00:55:37 2017 Job-IDFOCUS Start-Time DurationFunction --- -- 1 IO 20170704-00:44:45 0.0 hr(s) 10.0 min(s) IO_Focus 2 BASE20170704-00:44:52 0.0 hr(s) 10.0 min(s) Test FOCUS IO BASESUM TOTAL 76 25 101 FAIL 0 4 4 PASS 76 21 97 (%) (100%) (84%) (96%) >Now manually changed the smt value root@lotkvm:/home# ppc64_cpu --smt SMT=8 root@lotkvm:/home# date Tue Jul 4 00:46:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=2 root@lotkvm:/home# ppc64_cpu --smt SMT=2 root@lotkvm:/home# date Tue Jul 4 00:50:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=4 root@lotkvm:/home# ppc64_cpu --smt SMT=4 root@lotkvm:/home# date Tue Jul 4 00:54:38 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=8 [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2055.142915] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2055.143226] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 seconds. [ 2055.143647] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 seconds. [ 2055.144029] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds. [ 2055.144353] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds. [ 2055.144665] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds. [ 2055.144936] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds. [ 2055.145195] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2175.974848] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2175.975144] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > root@lotkvm:# ps -eaf | grep ppc* root 48054 12068 0 01:24 pts/000:00:00 grep --color=auto ppc* root 80305 5719 0 00:54 hvc0 00:00:00 ppc64_cpu --smt 8 > ppc64_cpu --smt command hangs here . Not able to change the SMT value from 4 to 8. > Attached dmesg logs
[Kernel-packages] [Bug 1707643] Re: HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) does not work
** Patch added: "Upstream patch that we apply to our Xenial 4.4.0 kernel build" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707643/+attachment/4925812/+files/HP_lt4132_quirk_4.4.0-87.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/1707643 Title: HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) does not work Status in linux package in Ubuntu: Confirmed Bug description: HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) modem does not work without this patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc3&id=a68491f895a937778bb25b0795830797239de31f Modem connects, but does not receive any packets. ifconfig shows; wwp0s20f0u10c3 Link encap:Ethernet HWaddr 9e:63:76:8e:c0:91 inet addr:10.137.74.102 Bcast:10.137.74.103 Mask:255.255.255.252 UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:50 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:3465 (3.4 KB) Booting to http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3/ fixes the problem. Modem works as expected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.83.89 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: it 1334 F pulseaudio CurrentDesktop: XFCE Date: Mon Jul 31 15:40:55 2017 HibernationDevice: RESUME=UUID=9e656f3b-ee00-4e30-83e9-43a15bd0a6d1 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b595 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 03f0:a31d Hewlett-Packard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 430 G4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=b7cbc0e4-b6dd-4df5-ac7a-7a3b513743d9 ro splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.04 dmi.board.name: 822C dmi.board.vendor: HP dmi.board.version: KBC Version 42.65 dmi.chassis.asset.tag: 5CD7274GN2 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.04:bd04/12/2017:svnHP:pnHPProBook430G4:pvr:rvnHP:rn822C:rvrKBCVersion42.65:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 430 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707643/+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 1708120] Re: Lenovo Yoga 910 Sensors
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708120 Title: Lenovo Yoga 910 Sensors Status in linux package in Ubuntu: Confirmed Bug description: Rotation and light sensors don't function in the current 4.11.0-10 Artful kernel. After applying the patch at https://patchwork.kernel.org/patch/9842347/, the sensors function correctly and brightness and screen rotation work as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1521 F pulseaudio CurrentDesktop: GNOME Date: Wed Aug 2 11:02:28 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 138a:0094 Validity Sensors, Inc. Bus 001 Device 002: ID 5986:2104 Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80VF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=fc5e4cce-4a17-4d07-980b-c8ee385a945e ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2JCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Agera dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 910-13IKB dmi.modalias: dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB: dmi.product.name: 80VF dmi.product.version: Lenovo YOGA 910-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708120/+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 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- 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/1700972 Title: Please only recommend or suggest initramfs-tools | linux-initramfs- tool for kernels able to boot without initramfs Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Committed Status in linux-gke package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux-aws source package in Xenial: In Progress Status in linux-azure source package in Xenial: Fix Committed Status in linux-gke source package in Xenial: In Progress Bug description: Linux kernel packages depend on initramfs-tools | linux-initramfs- tool, even when systems using the kernel can be booted without it. Demoting the dependency to Recommends: or Suggests: would allow creating smaller images without initramfs-tools installed and fully skipping initramfs updates upon kernel updates saving time. Please consider changing the Depends: to Recommends: or Suggests: for kernels capable of booting without initramfs. initramfs-tools is still a dependency of ubuntu-minimal thus accidental removal of initramfs-tools resulting an unbootable system would still be unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700972/+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 1683458] Re: kern.log flooded with xhci-hcd warning message
This also fills my syslog and ker.log I'm using an USB wifi dongle inside a Windows guest (Virtualbox) 148f:761a Ralink Technology, Corp. xhci_hcd :00:14.0: WARN Event TRB for slot 19 ep 8 with no TDs queued? -- 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/1683458 Title: kern.log flooded with xhci-hcd warning message Status in linux package in Ubuntu: Expired Bug description: Appears to be identical to #1541997 but submitting here using ubuntu- bug for completeness This message repeats forever, rapidly making the log file huge. Apr 17 11:42:31 gvlt kernel: [255517.557491] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557629] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557761] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557892] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-72-generic 4.4.0-72.93 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 3857 F pulseaudio Date: Mon Apr 17 11:48:29 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-06-17 (304 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 MachineType: Dell Inc. Precision 5510 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic.efi.signed root=UUID=e22b40a4-a1aa-49d7-963c-121a4c1fb4b3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 08R8KJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn08R8KJ:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683458/+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 1704903] Re: Hisilicon D05 onboard fibre NIC link indicator LEDs don't work
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- 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/1704903 Title: Hisilicon D05 onboard fibre NIC link indicator LEDs don't work Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: In Progress Bug description: [Impact] There are 4 onboard NICs on the HiSilicon D05 board. Each has LEDs that indicate link. While the LEDs work for the 1st & 2nd NICs, they do not light up for the 3rd & 4th (fibre). [Test Case] Connect the 3rd & 4th (fibre) NICs to a switch, bring those interface up & down using ip link set dev down/up and check that the LED accurate reflects the state. [Regression Risk] The fix is localized to a driver that is specific to a HiSilicon SoC. Regression risk is mitigated by testing on that system (boot, toggle link) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704903/+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 1705586] Re: Mute key LED does not work on HP ProBook 440
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- 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/1705586 Title: Mute key LED does not work on HP ProBook 440 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: New Bug description: [SRU Justification] [Impact] Mic mute led on HP ProBook 440 G4 does not work. [Test Case] The led should indicate mic mute/unmute status. [Fix] Commit 5cd5b1bdfb0137d0e814a51ff203d72c76b9f375 add GPIO mic mute led support for HP ZBook 15u G3. Mic mute led on HP ProBook 440 G4 is also supported. [Regression Potential] Low, very limited laptops will be affected. --- this is probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I was asked to file a new bug. The mute button on my laptop has a led that changes the color based on the status of the audio-master channel. At least it should. There is a slider for the LED in alsamixer but it doesn't change anything. Are there any tests I should run? cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17 --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 2550 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=4ce0e490-8f95-4de2-9a8f-456e1455444d InstallationDate: Installed on 2015-06-07 (774 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04ca:7063 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=27108123-06bd-4347-a0c5-9ea2ba62a034 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-07-09 (11 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.06 dmi.board.name: 822E dmi.board.vendor: HP dmi.board.version: KBC Version 42.65 dmi.chassis.asset.tag: 5CD709684F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.06:bd06/18/2017:svnHP:pnHPProBook440G4:pvr:rvnHP:rn822E:rvrKBCVersion42.65:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
Thanks for the fix CoolStar! When will this patch integrated into the main Linux kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[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)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1707643] Re: HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) does not work
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1707643 Title: HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) does not work Status in linux package in Ubuntu: Confirmed Bug description: HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) modem does not work without this patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc3&id=a68491f895a937778bb25b0795830797239de31f Modem connects, but does not receive any packets. ifconfig shows; wwp0s20f0u10c3 Link encap:Ethernet HWaddr 9e:63:76:8e:c0:91 inet addr:10.137.74.102 Bcast:10.137.74.103 Mask:255.255.255.252 UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:50 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:3465 (3.4 KB) Booting to http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3/ fixes the problem. Modem works as expected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.83.89 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: it 1334 F pulseaudio CurrentDesktop: XFCE Date: Mon Jul 31 15:40:55 2017 HibernationDevice: RESUME=UUID=9e656f3b-ee00-4e30-83e9-43a15bd0a6d1 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b595 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 03f0:a31d Hewlett-Packard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 430 G4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=b7cbc0e4-b6dd-4df5-ac7a-7a3b513743d9 ro splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.04 dmi.board.name: 822C dmi.board.vendor: HP dmi.board.version: KBC Version 42.65 dmi.chassis.asset.tag: 5CD7274GN2 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.04:bd04/12/2017:svnHP:pnHPProBook430G4:pvr:rvnHP:rn822C:rvrKBCVersion42.65:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 430 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707643/+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 1701316] Re: Data corruption with hio driver
Test: writing 32x10G random data and comparing sha hash. Tested with 4.10.0-29-generic and 4.11.0-12-generic from xenial- proposed. No diffs, no I/O errors. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- 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/1701316 Title: Data corruption with hio driver Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Invalid Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: Impact: Data corruption is seen when using the hio driver with 4.10 and later kernels. Fix: Patch to fix incorrect use of enumerated values as bitmasks. Test case: See below. Regression potential: Very low. Changes are simple and Obviously Correct (TM), and they only affect the hio driver. --- We are seeing data corruption issues using the hio driver with kernel 4.10.0 # uname -a Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Making xfs fails: root@arbok:~# mkfs.xfs /dev/hioa meta-data=/dev/hioa isize=512agcount=4, agsize=48835584 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=195342336, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=95382, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 bad magic number bad magic number Metadata corruption detected at xfs_sb block 0x0/0x200 libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200 The drive appears to be healthy. Firmware has been upgraded to ver 656: root@arbok:~# hio_info -d /dev/hioa hioaSerial number: 022XWV10G2000325 Size(GB): 800 Max size(GB): 800 Hardware version: 1.0 Firmware version: 656 Driver version: 2.1.0.28 Work mode: MLC Run time (sec.):8910490 Total read(MB):8499 Total write(MB):0 Lifetime remaining: 99.844% Max bad block rate: 0.167% Health: OK Comment:NA No relevant entries about read/write errors in dmesg Also just copying 8G random data and reading those back gives a hash mismatch: root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock sha256sum test.dat read- 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s root@arbok:~# sha256sum test.dat read-back.dat 6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a test.dat ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25 read-back.dat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701316/+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 1683458] Re: kern.log flooded with xhci-hcd warning message
uname -a Linux hostname 4.10.0-29-generic #33-Ubuntu SMP Wed Jul 19 13:34:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- 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/1683458 Title: kern.log flooded with xhci-hcd warning message Status in linux package in Ubuntu: Expired Bug description: Appears to be identical to #1541997 but submitting here using ubuntu- bug for completeness This message repeats forever, rapidly making the log file huge. Apr 17 11:42:31 gvlt kernel: [255517.557491] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557629] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557761] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557892] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-72-generic 4.4.0-72.93 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 3857 F pulseaudio Date: Mon Apr 17 11:48:29 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-06-17 (304 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 MachineType: Dell Inc. Precision 5510 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic.efi.signed root=UUID=e22b40a4-a1aa-49d7-963c-121a4c1fb4b3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 08R8KJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn08R8KJ:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683458/+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 1697829] Re: Upgrade Redpine WLAN/BT driver to ver. 1.2 (production release)
Tagging bug with verification-done-xenial since the driver has been tested on a Xenial-based snap. Thanks, @Shrirang. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1697829 Title: Upgrade Redpine WLAN/BT driver to ver. 1.2 (production release) Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: Upgrade the Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel to ver. 1.2. This version is supposed to be a production release. This is the latest version of the driver provided by Redpine. For now, this driver is enabled only on x86, x86_64 architectures. The impact is restricted to { SDIO_DEVICE(0x041B, 0x9330) } for SDIO based WiFi- BT modules and on USB bus, this driver binds only to RS9113, lets upstream kernel driver handle other RSI chipsets. Fixes since previous release(see lp: #1694607) Other fixes: - Redpine vendor driver - Switching to AP mode causes kernel panic (lp: #1700941) - ubuntu/rsi driver has several issues as picked up by static analysis (lp: #1694733) 1.2 - WLAN Supported Features: 1) Station mode 2) 802.11bgn 3) Secutiry modes: Open, WEP, WPA, WPA2 4) AP mode 5) Bgscan and roaming 6) Legacy and UAPSD power save 7) Regulatory support 8) WoWLAN 9) Management frame protection 10) Wi-Fi direct mode WLAN Bug Fixes: --- 1) WoWLAN from S5 fails (lp: #1686283) 2) After wifi-ap is set, system will kernel panic (lp: #1699753) 3) Connect to "n" AP will cause system kernel panic (lp: #1699686) 4) Low throughput observed in some channels for TCP downlink traffic in Coex mode. WLAN Limitations/Features NOT Supported: 1) For GTK rekey, wakeup trigger send to host. BT Supported Features: -- 1) BT EDR mode 2) BT LE mode 3) BT Coex mode * WLAN STA + BT EDR * WLAN STA + BT LE * WLAN STA + BT EDR + BT LE * WLAN AP + BT EDR * WLAN AP + BT EDR + BT LE BT Limitations/Features NOT Supported: 1) To connect multiple BT slaves, connection should be initiated from rsi module. 2) In coex mode, BT file transfer fails at times with certain mobiles. 1.2.RC16 - WLAN Bug Fixes: --- 1. WoWLAN from S5 fails (lp: #1686283) 2. After wifi-ap is set, system will kernel panic (lp: #1699753) 3. Connect to "n" AP will cause system kernel panic (lp: #1699686) WLAN Limitations/Features NOT Supported: 1) For GTK rekey, wakeup trigger send to host. 2) Low throughput observed for TCP downlink traffic in Coex mode BT Limitations/Features NOT Supported: 1) To connect multiple BT slaves, connection should be initiated from rsi module. 2) In coex mode, BT file transfer fails at times with certain mobiles. 1.2.RC15 - WLAN Bug Fixes: --- 1) Coverity scan fixes (lp: #1694733) 2) Avoid driver reload at S4 resume BT Limitations/Features NOT Supported: 1) To connect multiple BT slaves, connection should be initiated from rsi module. 2) In coex mode, BT file transfer fails at times with certain mobiles. 1.2.RC14 - WLAN Bug Fixes: --- 1) Low throughput with 40MHz issue resolved. WLAN Limitations/Features NOT Supported: 1) S5 with WoWLAN does not work. 2) For GTK rekey, wakeup trigger send to host. 3) Low throughput observed for TCP downlink traffic in Coex mode BT Limitations/Features NOT Supported: 1) To connect multiple BT slaves, connection should be initiated from rsi module. 2) In coex mode, BT file transfer fails at times with certain mobiles. 1.2.RC12 - WLAN Bug Fixes: --- 1) WoWLAN stress test cases issue resolved (when all wifi, bt, ble traffics run and suspend) WLAN Limitations/Features NOT Supported: 1) S5 with WoWLAN does not work. 2) For GTK rekey, wakeup trigger send to host. 3) Low throughput observed for TCP downlink traffic in Coex mode BT Limitations/Features NOT Supported: 1) To connect multiple BT slaves, connection should be initiated from rsi module. 2) In coex mode, BT file transfer fails at times with certain mobiles. 1.2.RC11 - WLAN New Features: -- 1) Module parameter for debug level(ven_r
[Kernel-packages] [Bug 1700941] Re: Redpine vendor driver - Switching to AP mode causes kernel panic
Tagging bug with verification-done-xenial since the driver has been tested on a Xenial-based snap. Thanks, @Shrirang. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1700941 Title: Redpine vendor driver - Switching to AP mode causes kernel panic Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: Switching from STA to AP mode on RS9113 Redpine Wifi-BT combo device, system reports a kernel panic. The Redpine driver (ver. 1.2 RC12) doesn't track the Linux 4.4.69 stable release which introduced following patches to mac80211 subsystem: - mac80211: pass RX aggregation window size to driver - mac80211: pass block ack session timeout to to driver - mac80211: RX BA support for sta max_rx_aggregation_subframes The Redpine driver ver. 1.2RC12 needs to be updated to handle the changes introduced in the patch: - mac80211: pass block ack session timeout to to driver (more details here: http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=U buntu-4.4.0-82.105&id=0b2141bd007213cc9c4228786f773a3c35c41c56 and https://bugs.launc hpad.net/bugs/1692900) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1700941/+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 1700480] Re: Update snapcraft.yaml
Snap build working as expected with the xenial kernel on -proposed. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1700480 Title: Update snapcraft.yaml Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: Update the snapcraft.yaml we ship in Xenial to exploit some of the new feature present in snapcraft's 3.21. Among the improvements: 1) include the linux-firmware / linux-firmware-snapdragon package in the final snap 2) rename it to pc-kernel / dragonboard-kernel to match the snaps we have in the store 3) dynamic versioning 4) autogenerated config from debian.$DEBIAN/config/* 5) generate from the same snap versions for i386, amd64, armhf, arm64, ppc64el and s390x (this only for -generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700480/+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 1694733] Re: ubuntu/rsi driver has several issues as picked up by static analysis
rsi driver verified to be working as expected, as reported on bug #1697829. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1694733 Title: ubuntu/rsi driver has several issues as picked up by static analysis Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: ** CID 1438209: Memory - corruptions (OVERRUN) /ubuntu/rsi/rsi_91x_core.c: 352 in rsi_core_qos_processor() *** CID 1438209: Memory - corruptions (OVERRUN) /ubuntu/rsi/rsi_91x_core.c: 352 in rsi_core_qos_processor() 346 347 if (status) { 348 mutex_unlock(&common->tx_lock); 349 break; 350 } 351 >>> CID 1438209: Memory - corruptions (OVERRUN) >>> Overrunning array "common->tx_stats.total_tx_pkt_send" of 5 4-byte elements at element index 5 (byte offset 20) using index "q_num" (which evaluates to 5). 352 common->tx_stats.total_tx_pkt_send[q_num]++; 353 354 tstamp_2 = jiffies; 355 mutex_unlock(&common->tx_lock); 356 357 if (tstamp_2 > tstamp_1 + (300 * HZ / 1000)) ** CID 1438210: Resource leaks (RESOURCE_LEAK) /ubuntu/rsi/rsi_91x_hci.c: 274 in rsi_deregister_bt() *** CID 1438210: Resource leaks (RESOURCE_LEAK) /ubuntu/rsi/rsi_91x_hci.c: 274 in rsi_deregister_bt() 268 cmd_frame->q_no = RSI_BT_MGMT_Q; 269 cmd_frame->pkt_type = RSI_BT_PKT_TYPE_DEREGISTR; 270 271 skb_put(skb, sizeof(struct rsi_bt_cmd_frame)); 272 273 //return rsi_coex_send_pkt(common, skb, RSI_BT_Q); >>> CID 1438210: Resource leaks (RESOURCE_LEAK) >>> Variable "skb" going out of scope leaks the storage it points to. 274 return common->priv->host_intf_ops->write_pkt(common->priv, skb->data, skb->len); 275 } 276 EXPORT_SYMBOL_GPL(rsi_deregister_bt); 277 278 int rsi_hci_recv_pkt(struct rsi_common *common, u8 *pkt) 279 { ** CID 1438211: Resource leaks (RESOURCE_LEAK) /ubuntu/rsi/rsi_91x_hci.c: 249 in rsi_send_rfmode_frame() *** CID 1438211: Resource leaks (RESOURCE_LEAK) /ubuntu/rsi/rsi_91x_hci.c: 249 in rsi_send_rfmode_frame() 243 cmd_frame->bt_rf_tx_power_mode = 0; 244 cmd_frame->bt_rf_tx_power_mode = 0; 245 246 skb_put(skb, sizeof(struct rsi_bt_rfmode_frame)); 247 248 //return rsi_coex_send_pkt(common, skb, RSI_BT_Q); >>> CID 1438211: Resource leaks (RESOURCE_LEAK) >>> Variable "skb" going out of scope leaks the storage it points to. 249 return common->priv->host_intf_ops->write_pkt(common->priv, skb->data, skb->len); 250 } 251 EXPORT_SYMBOL_GPL(rsi_send_rfmode_frame); 252 253 int rsi_deregister_bt(struct rsi_common *common) 254 { ** CID 1438212: Null pointer dereferences (REVERSE_INULL) /ubuntu/rsi/rsi_91x_sdio.c: 1388 in rsi_freeze() *** CID 1438212: Null pointer dereferences (REVERSE_INULL) /ubuntu/rsi/rsi_91x_sdio.c: 1388 in rsi_freeze() 1382 struct rsi_91x_sdiodev *sdev = 1383 (struct rsi_91x_sdiodev *)adapter->rsi_dev; 1384 #endif 1385 1386 ven_rsi_dbg(INFO_ZONE, "SDIO Bus freeze ===>\n"); 1387 >>> CID 1438212: Null pointer dereferences (REVERSE_INULL) >>> Null-checking "adapter" suggests that it may be null, but it has already been dereferenced on all paths leading to the check. 1388 if (!adapter) { 1389 ven_rsi_dbg(ERR_ZONE, "Device is not ready\n"); 1390 return -ENODEV; 1391 } 1392 1393 common->suspend_in_prog = true; ** CID 1438213: Control flow issues (UNREACHABLE) /ubuntu/rsi/rsi_91x_usb.c: 497 in rsi_usb_check_queue_status() *** CID 1438213: Control flow issues (UNREACHABLE) /ubuntu/rsi/rsi_91x_usb.c: 497 in rsi_usb_check_queue_status() 491 struct rsi_91x_usbdev *dev = (struct rsi_91x_usbdev *)adapter->rsi_dev; 492 int status; 493 u32 buf_status = 0; 494 495
[Kernel-packages] [Bug 1700747] Re: make snap-pkg support
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1700747 Title: make snap-pkg support Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: Integrates snapcraft in the kbuild environment of the Linux kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700747/+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 1701137] Re: enable ARCH_SUNXI (and friends) in arm64 kernel .config
I took a stab at this, there are many more options to decide on than mentioned here. I enabled these as modules when possible, and generally took the default for the rest. Please look over the options below and let me know if they look reasonable. Regarding CONFIG_PHY_SUN4I_USB, you've indicated that it should be =y but it is also available as a module. Is there any reason it cannot be =m instead? Note that this is with a 4.12-based kernel. CONFIG_ARCH_SUNXI=y CONFIG_AHCI_SUNXI=m CONFIG_DMA_SUN6I=m CONFIG_DWMAC_SUNXI=m CONFIG_IR_SUNXI=m CONFIG_KEYBOARD_SUN4I_LRADC=m CONFIG_MDIO_SUN4I=m CONFIG_MFD_AC100=m CONFIG_MFD_AXP20X_RSB=m CONFIG_MFD_SUN4I_GPADC=m CONFIG_MFD_SUN6I_PRCM=y CONFIG_MMC_SUNXI=m CONFIG_MTD_NAND_SUNXI=m CONFIG_NET_VENDOR_ALLWINNER=y CONFIG_NVMEM_SUNXI_SID=m CONFIG_PHY_SUN4I_USB=m CONFIG_PHY_SUN9I_USB=m # CONFIG_PINCTRL_SUN4I_A10 is not set CONFIG_PINCTRL_SUN50I_A64=y CONFIG_PINCTRL_SUN50I_A64_R=y CONFIG_PINCTRL_SUN50I_H5=y # CONFIG_PINCTRL_SUN5I is not set # CONFIG_PINCTRL_SUN6I_A31 is not set # CONFIG_PINCTRL_SUN6I_A31_R is not set # CONFIG_PINCTRL_SUN7I_A20 is not set # CONFIG_PINCTRL_SUN8I_A23 is not set # CONFIG_PINCTRL_SUN8I_A23_R is not set # CONFIG_PINCTRL_SUN8I_A33 is not set # CONFIG_PINCTRL_SUN8I_A83T is not set # CONFIG_PINCTRL_SUN8I_H3 is not set CONFIG_PINCTRL_SUN8I_H3_R=y # CONFIG_PINCTRL_SUN8I_V3S is not set # CONFIG_PINCTRL_SUN9I_A80 is not set # CONFIG_PINCTRL_SUN9I_A80_R is not set CONFIG_PINCTRL_SUNXI=y CONFIG_PWM_SUN4I=m CONFIG_RESET_SUNXI=y CONFIG_RTC_DRV_AC100=m CONFIG_RTC_DRV_SUN6I=y CONFIG_SERIO_SUN4I_PS2=m CONFIG_SND_SUN4I_CODEC=m CONFIG_SND_SUN4I_I2S=m CONFIG_SND_SUN4I_SPDIF=m CONFIG_SND_SUN8I_CODEC_ANALOG=m CONFIG_SPI_SUN4I=m CONFIG_SPI_SUN6I=m CONFIG_SUN4I_EMAC=m CONFIG_SUN4I_GPADC=m CONFIG_SUN50I_A64_CCU=y # CONFIG_SUN8I_H3_CCU is not set CONFIG_SUN8I_R_CCU=y CONFIG_SUNXI_CCU=y CONFIG_SUNXI_CCU_DIV=y CONFIG_SUNXI_CCU_FRAC=y CONFIG_SUNXI_CCU_GATE=y CONFIG_SUNXI_CCU_MP=y CONFIG_SUNXI_CCU_MUX=y CONFIG_SUNXI_CCU_NK=y CONFIG_SUNXI_CCU_NKM=y CONFIG_SUNXI_CCU_NKMP=y CONFIG_SUNXI_CCU_NM=y CONFIG_SUNXI_CCU_PHASE=y CONFIG_SUNXI_RSB=m CONFIG_SUNXI_SRAM=y CONFIG_SUNXI_WATCHDOG=m CONFIG_TOUCHSCREEN_SUN4I=m CONFIG_USB_MUSB_SUNXI=m ** Changed in: linux (Ubuntu Artful) Status: Triaged => 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/1701137 Title: enable ARCH_SUNXI (and friends) in arm64 kernel .config Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Incomplete Bug description: The mainline support for the ARM64 Allwinner SoCs (featured on the Pine64 boards and the Pinebook notebook, for instance, as well as other development boards like the BananaPi-M64) has come a long way by now, since 4.11 we have MMC and USB support working. Now can we just enable the proper .config bits to make the official Ubuntu kernel support those boards? The latest mainline U-Boot can load an EFI grub from some UEFI ESP partition, so any standard EFI installer should work. Apart from some minor hiccup (a missing MBR bootable flag/MBR at all) this works already with the Debian-testing netinst installer. The config symbols needed for decent support are (all enabled by the latest Debian kernel and the official mainline defconfig): ARCH_SUNXI=y CONFIG_USB_MUSB_SUNXI=m CONFIG_MMC_SUNXI=m CONFIG_RTC_DRV_SUN6I=y CONFIG_PHY_SUN4I_USB=y Those enable MMC and USB (the mandatory clocks, pinctrl and UART are enabled by default) and make those boards quite usable already. The on-SoC Ethernet driver will probably be merged into 4.13-rc1. Optionally: CONFIG_I2C_MV64XXX=m CONFIG_SPI_SUN6I=m give us I2C and SPI support as well. So can we add those symbols to the Ubuntu kernel .config to give users an out-of-the-box experience? Cheers, Andre. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701137/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume
The kernel on the image that I installed was linux-image-4.11.0-10-generic 4.11.0-10.15 and it worked fine. -- 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/1708043 Title: Lenovo X1 Carbon Gen5 fails to resume Status in linux package in Ubuntu: Confirmed Bug description: Last week it worked fine, this week however if I open the lid for it to resume the power light flashes for a bit, then comes on solid, the but screen stays blank and the machine is unresponsive. I have to power it off / on again in order to use it. It might be related to the APST issue with Samsung NVMe SSDs, I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dean 1652 F...m pulseaudio /dev/snd/controlC0: dean 1652 F pulseaudio CurrentDesktop: GNOME Date: Tue Aug 1 17:39:20 2017 HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nvme_core.default_ps_max_latency_us=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET37W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW 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:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain
** Changed in: linux (Ubuntu Artful) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1703339 Title: Unable to install Ubuntu on the NVMe disk under VMD PCI domain Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: It is not possible to install Ubuntu on the NVMe disk under VMD (Volume Management Device) PCI domain. The disk is not visible in the installer because VMD module is not available at this stage. I'm raising it against kernel package as I have impression VMD module must be included in linux-image dpkg package, not linux-image-extra. Please also assure VMD module gets included in initramfs by installer (if necessary). For more information about VMD please see bug 1591806. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.10.0.26.28 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: tomasz 1659 F...m pulseaudio /dev/snd/controlC0: tomasz 1659 F pulseaudio /dev/snd/timer: tomasz 1659 f pulseaudio CurrentDesktop: GNOME Date: Mon Jul 10 10:40:20 2017 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2017-07-06 (3 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170702) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.167 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703339/+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 1703430] Re: Set CONFIG_SATA_HIGHBANK=y on armhf
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Description changed: + SRU Justification + + Impact: CONFIG_SATA_HIGHBANK was changed from y to m after trusty, with + no justification appearing in the git history. This can cause problems + booting on some systems. + + Fix: Change the option back to y. + + Regression Potential: Minimal, as this only switches a driver from being + a module to being built-in, and the driver will only be used if the + device appears in a platform's device tree. + + --- + Sometime between trusty and xenial, CONFIG_SATA_HIGHBANK was changed from y to m. I believe the change was in utopic, but it's hard to tell. This makes booting on Calxeda Highbank systems pretty difficult since you can't get to the root filesystem on a SATA disk unless you were smart enough to have initramfs-tools include the sata_highbank module. On a clean install, you'd need to know to drop out of the installer, and rebuild the initramfs appropriately. Any chance that could be changed back to y for armhf? -- 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/1703430 Title: Set CONFIG_SATA_HIGHBANK=y on armhf Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: New Status in linux source package in Zesty: New Status in linux source package in Artful: Triaged Bug description: SRU Justification Impact: CONFIG_SATA_HIGHBANK was changed from y to m after trusty, with no justification appearing in the git history. This can cause problems booting on some systems. Fix: Change the option back to y. Regression Potential: Minimal, as this only switches a driver from being a module to being built-in, and the driver will only be used if the device appears in a platform's device tree. --- Sometime between trusty and xenial, CONFIG_SATA_HIGHBANK was changed from y to m. I believe the change was in utopic, but it's hard to tell. This makes booting on Calxeda Highbank systems pretty difficult since you can't get to the root filesystem on a SATA disk unless you were smart enough to have initramfs-tools include the sata_highbank module. On a clean install, you'd need to know to drop out of the installer, and rebuild the initramfs appropriately. Any chance that could be changed back to y for armhf? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703430/+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 1654068] Re: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful.
** Changed in: makedumpfile (Ubuntu Yakkety) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1654068 Title: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Yakkety: Won't Fix Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-25 23:00:37 == ---Problem Description--- Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. ---Steps to Reproduce--- 1. Configure fadump. 2. Trigger crash. Logs = root@alp9:/home/ubuntu# service kdump status ? kdump.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) root@alp9:/home/ubuntu# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-32-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-32-generic current state:ready to fadump [-1;-1f[3.187917] kdump-tools[1049]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201612220208/dump-incomplete Copying data : [100.0 %] | [5.711820] kdump-tools[1049]: The kernel version is not supported. [5.712201] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.712515] kdump-tools[1049]: The dumpfile is saved to /var/crash/201612220208/dump-incomplete. [5.712849] kdump-tools[1049]: makedumpfile Completed. [5.720901] kdump-tools[1049]: * kdump-tools: saved vmcore in /var/crash/201612220208 [5.916826] kdump-tools[1049]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201612220208/dmesg.201612220208 [5.941113] kdump-tools[1049]: The kernel version is not supported. [5.941612] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.941969] kdump-tools[1049]: The dmesg log is saved to /var/crash/201612220208/dmesg.201612220208. [5.942340] kdump-tools[1049]: makedumpfile Completed. [5.942648] kdump-tools[1049]: * kdump-tools: saved dmesg content in /var/crash/201612220208 [5.994508] kdump-tools[1049]: Thu, 22 Dec 2016 02:08:35 -0500 [6.018241] kdump-tools[1049]: Rebooting. [6.025884] reboot: Restarting system == Comment: #3 - Hari Krishna Bathini - 2017-01-04 07:14:19 == Canonical, Please pick the latest version of makedumpfile (v1.6.1) which officially supports 4.8 kernels. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1654068/+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 1704994] Re: linux: 3.13.0-126.175 -proposed tracker
** Tags added: regression-testing-passed -- 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/1704994 Title: linux: 3.13.0-126.175 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1704995 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1704994/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume
apport information ** Tags added: apport-collected ** Description changed: Last week it worked fine, this week however if I open the lid for it to resume the power light flashes for a bit, then comes on solid, the but screen stays blank and the machine is unresponsive. I have to power it off / on again in order to use it. It might be related to the APST issue with Samsung NVMe SSDs, I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dean 1652 F...m pulseaudio /dev/snd/controlC0: dean 1652 F pulseaudio CurrentDesktop: GNOME Date: Tue Aug 1 17:39:20 2017 HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nvme_core.default_ps_max_latency_us=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET37W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW 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:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO + --- + ApportVersion: 2.20.6-0ubuntu4 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2017-07-23 (9 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: artful wayland-session + Uname: Linux 4.13.0-041300rc3-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1708043/+attachment/4925885/+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/1708043 Title: Lenovo X1 Carbon Gen5 fails to resume Status in linux package in Ubuntu: Confirmed Bug description: Last week it worked fine, this week however if I open the lid for it to resume the power light flashes for a bit, then comes on solid, the but screen stays blank and the machine is unresponsive. I have to power it off / on again in order to use it. It might be related to the APST issue with Samsung NVMe SSDs, I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dean 1652 F...m pulseaudio /dev/snd/controlC0: dean 1652 F pulseaudio CurrentDesktop: GNOME Date: Tue Aug 1 17:39:20 2017 HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nvme_core.default_ps_max_latency_us=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux U
[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume
I tried the mainline kernel and got similar behavior. The only thing different with the 3.13 kernel is that when I closed the lid, the red dot never went dim and started blinking. It stayed red. After waiting a bit and opening the lid, it failed to resume, the screen did not turn on, and the computer was unresponsive. -- 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/1708043 Title: Lenovo X1 Carbon Gen5 fails to resume Status in linux package in Ubuntu: Confirmed Bug description: Last week it worked fine, this week however if I open the lid for it to resume the power light flashes for a bit, then comes on solid, the but screen stays blank and the machine is unresponsive. I have to power it off / on again in order to use it. It might be related to the APST issue with Samsung NVMe SSDs, I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dean 1652 F...m pulseaudio /dev/snd/controlC0: dean 1652 F pulseaudio CurrentDesktop: GNOME Date: Tue Aug 1 17:39:20 2017 HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nvme_core.default_ps_max_latency_us=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET37W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW 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:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: artful wayland-session Uname: Linux 4.13.0-041300rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1708043] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1708043/+attachment/4925886/+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/1708043 Title: Lenovo X1 Carbon Gen5 fails to resume Status in linux package in Ubuntu: Confirmed Bug description: Last week it worked fine, this week however if I open the lid for it to resume the power light flashes for a bit, then comes on solid, the but screen stays blank and the machine is unresponsive. I have to power it off / on again in order to use it. It might be related to the APST issue with Samsung NVMe SSDs, I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dean 1652 F...m pulseaudio /dev/snd/controlC0: dean 1652 F pulseaudio CurrentDesktop: GNOME Date: Tue Aug 1 17:39:20 2017 HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nvme_core.default_ps_max_latency_us=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET37W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW 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:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: artful wayland-session Uname: Linux 4.13.0-041300rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1705270] Re: linux: 4.4.0-88.111 -proposed tracker
** Tags added: regression-testing-passed -- 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/1705270 Title: linux: 4.4.0-88.111 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1705272 derivatives: 1705273,1705274,1705275,1705276 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1705270/+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 1705270] Re: linux: 4.4.0-88.111 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705270 Title: linux: 4.4.0-88.111 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1705272 derivatives: 1705273,1705274,1705275,1705276 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1705270/+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 1704994] Re: linux: 3.13.0-126.175 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704994 Title: linux: 3.13.0-126.175 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1704995 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1704994/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume
Hmm, 4.11.0-10.15 is already the latest one on Artful, and it doesn't have the issue per comment #6. So which kernel has the suspend/resume issue? Is it the mainline linux (Linux 4.13.0-041300rc3-generic) you installed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708043 Title: Lenovo X1 Carbon Gen5 fails to resume Status in linux package in Ubuntu: Confirmed Bug description: Last week it worked fine, this week however if I open the lid for it to resume the power light flashes for a bit, then comes on solid, the but screen stays blank and the machine is unresponsive. I have to power it off / on again in order to use it. It might be related to the APST issue with Samsung NVMe SSDs, I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dean 1652 F...m pulseaudio /dev/snd/controlC0: dean 1652 F pulseaudio CurrentDesktop: GNOME Date: Tue Aug 1 17:39:20 2017 HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nvme_core.default_ps_max_latency_us=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET37W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW 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:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: artful wayland-session Uname: Linux 4.13.0-041300rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1704995] Re: linux-lts-trusty: 3.13.0-126.175~precise1 -proposed tracker
No ADT testing available for ESM PPAs. ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1704995 Title: linux-lts-trusty: 3.13.0-126.175~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1704994 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1704995/+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 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- 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/1703339 Title: Unable to install Ubuntu on the NVMe disk under VMD PCI domain Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: It is not possible to install Ubuntu on the NVMe disk under VMD (Volume Management Device) PCI domain. The disk is not visible in the installer because VMD module is not available at this stage. I'm raising it against kernel package as I have impression VMD module must be included in linux-image dpkg package, not linux-image-extra. Please also assure VMD module gets included in initramfs by installer (if necessary). For more information about VMD please see bug 1591806. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.10.0.26.28 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: tomasz 1659 F...m pulseaudio /dev/snd/controlC0: tomasz 1659 F pulseaudio /dev/snd/timer: tomasz 1659 f pulseaudio CurrentDesktop: GNOME Date: Mon Jul 10 10:40:20 2017 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2017-07-06 (3 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170702) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.167 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703339/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
The patch isn't in the 4.13 master branch code. https://github.com/torvalds/linux/blob/master/drivers/mfd/intel-lpss- pci.c I think someone needs to make a pull request and lobby to get it merged :) -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[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)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1654068] Re: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful.
As to my understanding this is a cosmetic warning message rather than an incompatibility, my assessment is that this should not be treated as severity 'high' and is therefore not a candidate for an SRU. In the event of actual incompatibilities between the 16.04 rolling kernel and makedumpfile, we would absolutely make an exception to the SRU process for a new upstream version as appropriate. ** Changed in: makedumpfile (Ubuntu Xenial) Status: Confirmed => Won't Fix ** Changed in: ubuntu-power-systems Assignee: Canonical Foundations Team (canonical-foundations) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1654068 Title: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Yakkety: Won't Fix Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-25 23:00:37 == ---Problem Description--- Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful. ---Steps to Reproduce--- 1. Configure fadump. 2. Trigger crash. Logs = root@alp9:/home/ubuntu# service kdump status ? kdump.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) root@alp9:/home/ubuntu# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-32-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-32-generic current state:ready to fadump [-1;-1f[3.187917] kdump-tools[1049]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201612220208/dump-incomplete Copying data : [100.0 %] | [5.711820] kdump-tools[1049]: The kernel version is not supported. [5.712201] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.712515] kdump-tools[1049]: The dumpfile is saved to /var/crash/201612220208/dump-incomplete. [5.712849] kdump-tools[1049]: makedumpfile Completed. [5.720901] kdump-tools[1049]: * kdump-tools: saved vmcore in /var/crash/201612220208 [5.916826] kdump-tools[1049]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201612220208/dmesg.201612220208 [5.941113] kdump-tools[1049]: The kernel version is not supported. [5.941612] kdump-tools[1049]: The makedumpfile operation may be incomplete. [5.941969] kdump-tools[1049]: The dmesg log is saved to /var/crash/201612220208/dmesg.201612220208. [5.942340] kdump-tools[1049]: makedumpfile Completed. [5.942648] kdump-tools[1049]: * kdump-tools: saved dmesg content in /var/crash/201612220208 [5.994508] kdump-tools[1049]: Thu, 22 Dec 2016 02:08:35 -0500 [6.018241] kdump-tools[1049]: Rebooting. [6.025884] reboot: Restarting system == Comment: #3 - Hari Krishna Bathini - 2017-01-04 07:14:19 == Canonical, Please pick the latest version of makedumpfile (v1.6.1) which officially supports 4.8 kernels. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1654068/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
I can send a patch to upstream. Let's wait for CoolStar's response. -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[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)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Roberts, does the new kernel I built still have the issue? -- 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/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state Status in linux package in Ubuntu: In Progress Bug description: Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: drgrumpy 2192 F pulseaudio /dev/snd/pcmC1D0p: drgrumpy 2192 F...m pulseaudio /dev/snd/controlC1: drgrumpy 2192 F pulseaudio DistroRelease: Linux 18.2 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec InstallationDate: Installed on 2017-07-06 (15 days ago) InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.157.11 RfKill: Tags: sonya Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805
[Kernel-packages] [Bug 1694787] Re: Dell Precision 5520 crashing after connecting to ethernet
Yes, it's the one that came with the laptop. I can't isolate the exact problem. It'll initially work for a few minutes when I first plug it in, then it'll become completely unresponsive and I'll have to unplug it and use wireless. Then if I plug it in an hour later, it'll work fine for hours. -- 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/1694787 Title: Dell Precision 5520 crashing after connecting to ethernet Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell Precision 5520 that came pre-installed with Ubuntu 16.04. I use it at home on wireless exclusively. When I take it to work, I plug it into ethernet via the ethernet dongle. Without fail, almost an hour later, all networking stops working. I can ping neither domains not IPs, even on my local network. If I try to run `sudo service networking restart` or `sudo service network-manager restart` then Gnome-Shell hangs. If I switch to an Fn terminal, I can run some commands, but eventually all sudo commands there hang too. Holding down ctrl+alt+del says "ctrl+alt+del pressed 7 times in 2 seconds, rebooting immediately", but after 15 minutes, it still doesn't reboot, forcing me to do a hard reboot. Afterwards, the laptop works fine until the next day, when it all happens again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2444 F pulseaudio CurrentDesktop: GNOME Date: Wed May 31 14:14:09 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-03-09 (82 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=b3c434bc-85ba-4b42-a137-374a088e6c0f ro acpi_rev_override quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-78-generic N/A linux-backports-modules-4.4.0-78-generic N/A linux-firmware1.157.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.2 dmi.board.name: 0GPNW9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.2:bd12/28/2016:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0GPNW9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694787/+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 1708041] Re: zesty unable to handle kernel NULL pointer dereference on opening chrome tab
apport information ** Tags added: apport-collected ** Description changed: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_vma_bind+0x7e/0x170 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721580] __i915_vma_do_pin+0x2a5/0x450 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721607] i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721647] i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel:
[Kernel-packages] [Bug 1708041] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925968/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_vma_bind+0x7e/0
[Kernel-packages] [Bug 1708041] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925969/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i91
[Kernel-packages] [Bug 1708041] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925973/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_vma_bind+0x7e
[Kernel-packages] [Bug 1708041] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925974/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_
[Kernel-packages] [Bug 1708041] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925971/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i
[Kernel-packages] [Bug 1708041] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925972/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_vma_bind+0x7e
[Kernel-packages] [Bug 1708041] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925977/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555]
[Kernel-packages] [Bug 1708041] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925970/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_vma_bi
[Kernel-packages] [Bug 1708041] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925975/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.
[Kernel-packages] [Bug 1708041] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925976/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_
[Kernel-packages] [Bug 1708041] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925979/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_vma_
[Kernel-packages] [Bug 1708041] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925981/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_vma_bind+0x
[Kernel-packages] [Bug 1708041] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925978/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_
[Kernel-packages] [Bug 1708041] Re: zesty unable to handle kernel NULL pointer dereference on opening chrome tab
I've uploaded the files with apport-collect ** 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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_vma_bind+0x7e/0x170 [i915] Au
[Kernel-packages] [Bug 1708041] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925980/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_vma_bind+0x
[Kernel-packages] [Bug 1708041] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1708041/+attachment/4925982/+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/1708041 Title: zesty unable to handle kernel NULL pointer dereference on opening chrome tab Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Zesty about a week ago, and never had this problem in Yakkety under similar conditions. I usually have a large amount tabs in Chrome sitting open for days on end. Today, upon attempting to open probably the 100th tab, the system froze right when the tab was popped. Chrome is google-chrome-stable 60.0.3112.78-1 from Google PPA. $ cat version.log Ubuntu 4.10.0-28.32-generic 4.10.17 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720720] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720769] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720789] PGD 0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720790] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720804] Oops: 0002 [#1] SMP Aug 1 18:03:02 my-XPS-8910 kernel: [112698.720815] Modules linked in: binfmt_misc xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 r fcomm xt_tcpudp bridge stp llc ebtable_filter ebtables ip6_tables iptable_filter bnep nls_iso8859_1 arc4 8250_dw dell_wmi sparse_keymap i2c_designware_platform dell_smbios i2c_designware_core snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_c odec_realtek iwlmvm snd_hda_codec_generic kvm_intel kvm dcdbas mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core aes_x86_64 snd_hwdep crypto_simd glue_helper snd_pcm cryptd intel_cstate intel_r apl_perf cfg80211 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721007] snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq snd_seq_device snd_timer btusb hci_uart btrtl btbcm idma64 snd btqca virt_dma mei_me btintel soundcore mei bluetooth shpchp intel_lpss_pci intel_lpss_acpi inte l_lpss mac_hid acpi_pad acpi_als tpm_crb kfifo_buf industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm alx ahci mdio i2c_hid libahci hid pinctrl_sunrisepoint wmi video pinctrl_intel fjes Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721152] CPU: 1 PID: 4119 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721177] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.0.4 05/30/2016 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721196] task: 88385a04 task.stack: a70fc63bc000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721228] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721248] RSP: 0018:a70fc63bf880 EFLAGS: 00010246 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721264] RAX: 8834d62f4a80 RBX: 0003 RCX: 0003 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721284] RDX: RSI: 8832bfbb2000 RDI: 8838c95d8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721303] RBP: a70fc63bf8d8 R08: R09: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721322] R10: R11: 0002 R12: 88341bc6a000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721342] R13: 88385a33ba10 R14: fdb66000 R15: 8000 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721362] FS: 7f3fda70eb00() GS:8838eec4() knlGS: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721384] CS: 0010 DS: ES: CR0: 80050033 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721401] CR2: 0018 CR3: 0005da942000 CR4: 003406e0 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721421] DR0: DR1: DR2: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721440] DR3: DR6: fffe0ff0 DR7: 0400 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721459] Call Trace: Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721483] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721500] ? swiotlb_map_sg_attrs+0x49/0x110 Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721526] gen8_alloc_va_range+0x23d/0x470 [i915] Aug 1 18:03:02 my-XPS-8910 kernel: [112698.721555] i915_vm
[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Sorry, I have downloaded but haven't got to testing it yet have had to prioritise the day job... will aim to try this evening and report back tomorrow... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state Status in linux package in Ubuntu: In Progress Bug description: Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: drgrumpy 2192 F pulseaudio /dev/snd/pcmC1D0p: drgrumpy 2192 F...m pulseaudio /dev/snd/controlC1: drgrumpy 2192 F pulseaudio DistroRelease: Linux 18.2 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec InstallationDate: Installed on 2017-07-06 (15 days ago) InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.157.11 RfKill: Tags: sonya Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: Tr
[Kernel-packages] [Bug 1708222] Re: Long, multi-threaded compilations, segfault in Ryzen
The other log file. ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708222/+attachment/4926016/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Incomplete Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708222/+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 1708222] [NEW] Long, multi-threaded compilations, segfault in Ryzen
Public bug reported: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen-test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1708222/+attachment/4926015/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Incomplete Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708222/+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 1708222] 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 1708222 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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Incomplete Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708222/+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 1705900] Re: Lenovo e73 USB webcam problems
I reported the bug with the Microsoft one, but the same problem also occurs with Trust WB-5400 webcam. -- 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/1705900 Title: Lenovo e73 USB webcam problems Status in linux package in Ubuntu: Incomplete Bug description: I'm experiencing problems with USB webcam on Lenovo e73 with Ubuntu 16.04.2 Xenial 32bit. Originally with 4.4 connecting the camera often resulted in complete hang of the system (apparently not even SysRq worked, though I did not test that personally since it is a system I'm administering remotely for a family member). There was always a null pointer dereference just before the hang, so I suspect that is the culprit (see the attached kernel log). After some updates the system no longer hangs. I suspect this was fixed by going from linux 4.4 to 4.8. However, the webcam still often doesn't work and most application just return error. This is usually fixed after several tries, but sometimes it is necessary to reboot computer. Updating BIOS didn't help. The kernel logs still contain the same null pointer dereference with exactly the same stack trace for both 4.8 and 4.10. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: user 1852 F pulseaudio /dev/snd/controlC0: user 1852 F pulseaudio /dev/snd/controlC1: user 1852 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=de34a223-a620-435a-974a-e29dad30f1ac InstallationDate: Installed on 2017-05-05 (85 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) IwConfig: tun0 no wireless extensions. enp2s0no wireless extensions. lono wireless extensions. MachineType: LENOVO 10DR002SMC Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic root=UUID=07f94680-ac2c-498b-86e4-72ff6e4bd18f ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-58-generic N/A linux-backports-modules-4.8.0-58-generic N/A linux-firmware1.157.11 RfKill: Tags: xenial Uname: Linux 4.8.0-58-generic i686 UpgradeStatus: Upgraded to xenial on 2017-05-05 (85 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: FCKT82AUS dmi.board.name: 3098 dmi.board.vendor: LENOVO dmi.board.version: SDK0G00599 WIN dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrFCKT82AUS:bd02/13/2017:svnLENOVO:pn10DR002SMC:pvrThinkCentreE73:rvnLENOVO:rn3098:rvrSDK0G00599WIN:cvnLENOVO:ct3:cvr: dmi.product.name: 10DR002SMC dmi.product.version: ThinkCentre E73 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705900/+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 1708222] Re: Long, multi-threaded compilations, segfault in Ryzen
apport information ** Tags added: apport-collected zesty ** Description changed: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen-test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. - I am opening this bug report because I believe we should try to verify - if this is a widespread problem and inform potential users of the - problems. Hopefully AMD or the Kernel developers can find a workaround. - I have also already opened a bug report in the Linux Kernel Bugzilla - (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately - it is not calling the attention of the kernel developers. + I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. + --- + ApportVersion: 2.20.4-0ubuntu4.5 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 17.04 + HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 + InstallationDate: Installed on 2017-05-30 (63 days ago) + InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) + IwConfig: + enp33s0 no wireless extensions. + + lono wireless extensions. + MachineType: Micro-Star International Co., Ltd MS-7A34 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 + ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.10.0-29-generic N/A + linux-backports-modules-4.10.0-29-generic N/A + linux-firmware 1.164.1 + RfKill: + + Tags: zesty + Uname: Linux 4.10.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video + _MarkForUpload: True + dmi.bios.date: 07/06/2017 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.71 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: B350 TOMAHAWK (MS-7A34) + dmi.board.vendor: Micro-Star International Co., Ltd + dmi.board.version: 1.0 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Micro-Star International Co., Ltd + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: + dmi.product.name: MS-7A34 + dmi.product.version: 1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926043/+files/AlsaInfo.txt -- You
[Kernel-packages] [Bug 1708222] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926045/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1708222] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926044/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@
[Kernel-packages] [Bug 1708222] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926047/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-package
[Kernel-packages] [Bug 1708222] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926048/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-package
[Kernel-packages] [Bug 1708222] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926046/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1708222] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926049/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : k
[Kernel-packages] [Bug 1708222] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926050/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages P
[Kernel-packages] [Bug 1708222] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926053/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : k
[Kernel-packages] [Bug 1708222] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926051/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : k
[Kernel-packages] [Bug 1708222] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926055/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => 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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.lau
[Kernel-packages] [Bug 1708222] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926054/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packa
[Kernel-packages] [Bug 1708222] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1708222/+attachment/4926052/+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/1708222 Title: Long, multi-threaded compilations, segfault in Ryzen Status in linux package in Ubuntu: Confirmed Bug description: I have a Ryzen 1700X on a MSI B350 Motherboard and 64 Gb of RAM (Corsair LPX 2400). If I do a very intensive multi-threaded compilation session sometimes I get a segfault. This seems to be a problem with Ryzen it self nad maybe it is related to the bug described in bug #1690085 but I believe it is not the same. This bug affects many Linux users with Ryzen, see for example this thread in the AMD forum: https://community.amd.com/thread/215773?start=0&tstart=0 or the Gentoo Wiki that talks about this problem in the Troubleshoting section of their Ryzen page: https://wiki.gentoo.org/wiki/Ryzen#Troubleshooting It is also very easy to verify if you have a processor with the problem. Fortunately some smart people have created a simple script that always shows the problem in my system and in the systems of the other people of the thread. The script can be found in https://github.com/suaefar/ryzen-test You just have to clone the repository using git, move to the ryzen- test directory and run ./kill_ryzen.sh. It is a very simple script, it downloads gcc-7.1 source code into a vram disk and start #processors simultaneous compilation of it. If any compilation fails it writes a message in the console saying how long it took to get the failure. After a few minutes, the build in my system fails unless I turn off SMT. With SMT off it can take many hours, but still fails in less than one day. I am opening this bug report because I believe we should try to verify if this is a widespread problem and inform potential users of the problems. Hopefully AMD or the Kernel developers can find a workaround. I have also already opened a bug report in the Linux Kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=196481), but unfortunately it is not calling the attention of the kernel developers. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=b299e86c-e86e-4608-b025-586133a3f5a6 InstallationDate: Installed on 2017-05-30 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp33s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A34 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-29-generic root=UUID=ea2ac8eb-cc5f-42a3-b7db-3d6a870496a9 ro quiet iommu=soft splash rcu_nocbs=1-15 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-29.33-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-29-generic N/A linux-backports-modules-4.10.0-29-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video _MarkForUpload: True dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd07/06/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 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/1708222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
I got it working! It was definitely a bios setting. I made every paranoid kind of change without resorting to changing to legacy boot mode. 4.13.0-rc3 with the patch works. I have trackpad. -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[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)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
It seems that I have to power off the laptop and power it on to reboot, or I just get a black screen. -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[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)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
@mykesx, yes, it was my impression that "changing" a value in BIOS twice (to its original value was not an idempotent operation -- hence there are bugs in the BIOS). I can reproduce the black screen when rebooting, but it also happens for me on an unpatched kernel. I guess you should open a separate bug for that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[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)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
definitely. If I sudo reboot, I get black screen and no boot. If I power off the machine and boot, it works. Could be the RC kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[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)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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