[Kernel-packages] [Bug 1856704] [NEW] backport 5.3 zfs support to bionic for HWE kernel support
Public bug reported: 5.3 kernel functionality back through to 4.15 is required for 5.3 HWE kernel support in ZFS and SPL modules. ** Affects: spl-linux (Ubuntu) Importance: High Assignee: Colin Ian King (colin-king) Status: In Progress ** Affects: zfs-linux (Ubuntu) Importance: High Assignee: Colin Ian King (colin-king) Status: In Progress ** Also affects: spl-linux (Ubuntu) Importance: Undecided Status: New ** Changed in: spl-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: spl-linux (Ubuntu) Status: New => Incomplete ** Changed in: spl-linux (Ubuntu) Importance: Undecided => High ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => High ** Changed in: spl-linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: zfs-linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1856704 Title: backport 5.3 zfs support to bionic for HWE kernel support Status in spl-linux package in Ubuntu: In Progress Status in zfs-linux package in Ubuntu: In Progress Bug description: 5.3 kernel functionality back through to 4.15 is required for 5.3 HWE kernel support in ZFS and SPL modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spl-linux/+bug/1856704/+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 1856701] Re: focal/linux: -proposed tracker
** Summary changed: - linux: -proposed tracker + focal/linux: -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + packages: + lrm: linux-restricted-modules + main: linux + meta: linux-meta + signed: linux-signed + phase: Ready for Packaging + phase-changed: Tuesday, 17. December 2019 13:13 UTC + reason: + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856701 Title: focal/linux: 5.4.0-10.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Tuesday, 17. December 2019 13:23 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856701/+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 1852493] Re: Freeze on suspend (Acer SF314-57)
My laptop already has /sys/power/mem_sleep as "deep" and it still hangs when I suspend. This is on the 5.4 mainline kernel. Norbert, did you have luck with "deep" with 5.4 or vanilla 19.10 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/1852493 Title: Freeze on suspend (Acer SF314-57) Status in linux package in Ubuntu: Confirmed Bug description: I freshly installed Ubuntu Budgie 19.10 today after receiving my new notebook. However, when putting the system to suspend (or hibernate), the screen goes off and the system freezes. The fan keeps running, keyboard backlight and power led are on. Sometimes, when pressing a button, I can get the screen to turn back on, but its frozen as well (no mouse movement, clock stuck etc.) So far I tried increasing the swap file size, however this did not help. I also livebooted Ubuntu 19.10 and tried suspend, but I had the same issue. Could this be a problem of my fairly new chipset (Intel i7 1065G7)? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: norbert1508 F pulseaudio /dev/snd/pcmC0D0p: norbert1508 F...m pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-13 (1 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Swift SF314-57 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/vgubuntu--budgie-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852493/+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 1856701] [NEW] focal/linux: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Packaging phase-changed: Tuesday, 17. December 2019 13:13 UTC reason: prepare-package: Pending -- version not specified variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags: focal kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.10.16-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: focal kernel-release-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + -- swm properties -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.10.16-1 ** Changed in: kernel-sru-workflow
[Kernel-packages] [Bug 1849833] Re: blank screen in X11 / lightdm
Problem resolved in kernel 5.3.0.24 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849833 Title: blank screen in X11 / lightdm Status in linux package in Ubuntu: Confirmed Bug description: boot message show well, and until start X11. Both two monitors just blank out. One of them even enter sleep mode. Seem related to this https://bugs.archlinux.org/task/64001 It works well if I rollback to 5.0.0-32-generic from 19.04 Fail on linux-image-5.3.0-19-generic. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.0.0-32-generic. ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dcheung1486 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xa131 irq 139' Mixer name : 'Realtek ALC887-VD' Components : 'HDA:10ec0887,104386c7,00100302 HDA:8086280b,80860101,0010' Controls : 75 Simple ctrls : 27 Date: Fri Oct 25 21:15:40 2019 InstallationDate: Installed on 2018-12-17 (312 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=ca0e4058-cba9-4a9d-9166-385dd0730aed ro pti=off spectre_v2=off l1tf=off lp=none scsi_mod.use_blk_mq=1 mitigations=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-25 (0 days ago) dmi.bios.date: 10/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd10/23/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849833/+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 1856694] 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/1856694 Title: my touchpad is not working since last software update Status in linux package in Ubuntu: Confirmed Bug description: my touchpad is not working since last update. it just freezes on startup.the touchpad works fine on windows ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: naman 1389 F pulseaudio /dev/snd/controlC0: naman 1389 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 17 17:47:40 2019 HibernationDevice: RESUME=UUID=53cdac06-44c5-49ba-aa07-20b890659c5c InstallationDate: Installed on 2019-01-31 (320 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3446 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=ce44f511-99b3-48a0-b2c5-391868309035 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856694/+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 1856694] [NEW] my touchpad is not working since last software update
Public bug reported: my touchpad is not working since last update. it just freezes on startup.the touchpad works fine on windows ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: naman 1389 F pulseaudio /dev/snd/controlC0: naman 1389 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 17 17:47:40 2019 HibernationDevice: RESUME=UUID=53cdac06-44c5-49ba-aa07-20b890659c5c InstallationDate: Installed on 2019-01-31 (320 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3446 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=ce44f511-99b3-48a0-b2c5-391868309035 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856694 Title: my touchpad is not working since last software update Status in linux package in Ubuntu: Confirmed Bug description: my touchpad is not working since last update. it just freezes on startup.the touchpad works fine on windows ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: naman 1389 F pulseaudio /dev/snd/controlC0: naman 1389 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 17 17:47:40 2019 HibernationDevice: RESUME=UUID=53cdac06-44c5-49ba-aa07-20b890659c5c InstallationDate: Installed on 2019-01-31 (320 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3446 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=ce44f511-99b3-48a0-b2c5-391868309035 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856694/+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 1846214] Re: Freezes instead of suspending, most times
Thank you for the suggestion, Kai-Heng. Tried with the nvidia-driver-435 installed, after reboot, and 2 out of 2 failures. I also made sure that `lsmod | grep nvidia` prints some modules. Not sure which modules exactly I'm looking for. Perhaps looking at some logs would be better, but I have a feeling that's sufficient. What did we learn, please? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846214 Title: Freezes instead of suspending, most times Status in linux package in Ubuntu: Confirmed Bug description: Hi and thank you for all your free software work. This system usually freezes instead of suspending. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mightyiam 2139 F pulseaudio /dev/snd/controlC0: mightyiam 2139 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 20:28:30 2019 MachineType: Micro-Star International Co., Ltd. GS60 2QE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic root=/dev/mapper/ubuntu-encrypted_root_crypt ro splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-06-11 (112 days ago) dmi.bios.date: 02/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H5IMS.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H5IMS.111:bd02/22/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS602QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H5:rvrREV0.B:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GS60 2QE dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+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 1856682] Re: GCC Miscompilation in vectorized code
** Package changed: linux (Ubuntu) => gcc-defaults (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: gcc-defaults (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: gcc-defaults (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical
Foundations Team (canonical-foundations)
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856682
Title:
GCC Miscompilation in vectorized code
Status in Ubuntu on IBM z Systems:
Triaged
Status in gcc-defaults package in Ubuntu:
New
Bug description:
Miscompilation in autovectorized code.
---Steps to Reproduce---
See GCC BZ: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92950
The following testcase abort when being compiled with -O3 -march=z13
on IBM Z:
struct a {
int b;
char c;
};
struct a d = {1, 16};
struct a *e =
int f = 0;
int main() {
struct a g = {0, 0 };
f = 0;
for (; f <= 1; f++) {
g = d;
*e = g;
}
if (d.c != 16)
__builtin_abort();
}
The movv1qi pattern emits halfword load instructions instead of character
loads.
All GCC versions since GCC 5 are affected.
Patches for GCC 8, 9, and 10 have been committed to the gcc.gnu.org branches.
Userspace tool common name: gcc
The userspace tool has the following bit modes: 64
Userspace rpm: various Ubuntu gcc packages
Package need to updated within LP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1856682/+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 1856682] [NEW] GCC Miscompilation in vectorized code
Public bug reported:
Miscompilation in autovectorized code.
---Steps to Reproduce---
See GCC BZ: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92950
The following testcase abort when being compiled with -O3 -march=z13 on
IBM Z:
struct a {
int b;
char c;
};
struct a d = {1, 16};
struct a *e =
int f = 0;
int main() {
struct a g = {0, 0 };
f = 0;
for (; f <= 1; f++) {
g = d;
*e = g;
}
if (d.c != 16)
__builtin_abort();
}
The movv1qi pattern emits halfword load instructions instead of character
loads.
All GCC versions since GCC 5 are affected.
Patches for GCC 8, 9, and 10 have been committed to the gcc.gnu.org branches.
Userspace tool common name: gcc
The userspace tool has the following bit modes: 64
Userspace rpm: various Ubuntu gcc packages
Package need to updated within LP
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-182958 severity-high
targetmilestone-inin2004
** Tags added: architecture-s39064 bugnameltc-182958 severity-high
targetmilestone-inin2004
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-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/1856682
Title:
GCC Miscompilation in vectorized code
Status in linux package in Ubuntu:
New
Bug description:
Miscompilation in autovectorized code.
---Steps to Reproduce---
See GCC BZ: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92950
The following testcase abort when being compiled with -O3 -march=z13
on IBM Z:
struct a {
int b;
char c;
};
struct a d = {1, 16};
struct a *e =
int f = 0;
int main() {
struct a g = {0, 0 };
f = 0;
for (; f <= 1; f++) {
g = d;
*e = g;
}
if (d.c != 16)
__builtin_abort();
}
The movv1qi pattern emits halfword load instructions instead of character
loads.
All GCC versions since GCC 5 are affected.
Patches for GCC 8, 9, and 10 have been committed to the gcc.gnu.org branches.
Userspace tool common name: gcc
The userspace tool has the following bit modes: 64
Userspace rpm: various Ubuntu gcc packages
Package need to updated within LP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856682/+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 1856682] [NEW] GCC Miscompilation in vectorized code
You have been subscribed to a public bug:
Miscompilation in autovectorized code.
---Steps to Reproduce---
See GCC BZ: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92950
The following testcase abort when being compiled with -O3 -march=z13 on
IBM Z:
struct a {
int b;
char c;
};
struct a d = {1, 16};
struct a *e =
int f = 0;
int main() {
struct a g = {0, 0 };
f = 0;
for (; f <= 1; f++) {
g = d;
*e = g;
}
if (d.c != 16)
__builtin_abort();
}
The movv1qi pattern emits halfword load instructions instead of character
loads.
All GCC versions since GCC 5 are affected.
Patches for GCC 8, 9, and 10 have been committed to the gcc.gnu.org branches.
Userspace tool common name: gcc
The userspace tool has the following bit modes: 64
Userspace rpm: various Ubuntu gcc packages
Package need to updated within LP
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-182958 severity-high
targetmilestone-inin2004
--
GCC Miscompilation in vectorized code
https://bugs.launchpad.net/bugs/1856682
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
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 1856605] Re: [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM
Joe, just to be clear: 1) Are you saying that you ran the test on a single system but 18.04 reported a different MT2xxx family compared to 16.04, or did you run this on two different systems? 2) Can you please provide the exact kernel versions that you tried: 16.04 that passes, 16.04 that fails, 18.04 that passes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856605 Title: [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM Status in linux-azure package in Ubuntu: Confirmed Bug description: We ran an RDMA test case against gallery image Ubuntu 16.04 (with proposed kernel), and found the below issue. The kernel prior to proposed does not exhibit this bug, so it is a regression: The issue is when ibv_devinfo is run, we get the below info: ibv_devinfo libibverbs: Warning: no userspace device-specific driver found for /sys/class/infiniband_verbs/uverbs0 No IB devices found ibv_devices libibverbs: Warning: no userspace device-specific driver found for /sys/class/infiniband_verbs/uverbs0 device node GUID -- Ibstat works as expected CA 'mlx5_0' CA type: MT4120 Number of ports: 1 Firmware version: 16.23.1020 Hardware version: 0 Node GUID: 0x00155dfffe33ff49 System image GUID: 0x506b4b0300f521ec Port 1: State: Active Physical state: LinkUp Rate: 100 Base lid: 713 LMC: 0 SM lid: 16 Capability mask: 0x2651ec48 Port GUID: 0x00155dfffd33ff49 Link layer: InfiniBand This Family exhibits the bug, with a subsystem of MT28800: lspci -v|egrep 'Mel|mlx' 0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Subsystem: Mellanox Technologies MT28800 Family [ConnectX-5 Virtual Function] Kernel driver in use: mlx5_core Kernel modules: mlx5_core This issue does not occur with Ubuntu 18.04, which has a different Subsystem(MT27800): lspci -v|egrep 'Mel|mlx' 0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Subsystem: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Kernel driver in use: mlx5_core Kernel modules: mlx5_core If we could, we would like to move to rmda-core to version 22 or higher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856605/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
I have submitted the patch for stable kernels: https://patchwork.kernel.org/patch/11297115/ Assuming it is accepted, it will probably turn up in Ubuntu kernels eventually. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1856605] Re: [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM
Joe, is there anything in the kernel log when this fails? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856605 Title: [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM Status in linux-azure package in Ubuntu: Confirmed Bug description: We ran an RDMA test case against gallery image Ubuntu 16.04 (with proposed kernel), and found the below issue. The kernel prior to proposed does not exhibit this bug, so it is a regression: The issue is when ibv_devinfo is run, we get the below info: ibv_devinfo libibverbs: Warning: no userspace device-specific driver found for /sys/class/infiniband_verbs/uverbs0 No IB devices found ibv_devices libibverbs: Warning: no userspace device-specific driver found for /sys/class/infiniband_verbs/uverbs0 device node GUID -- Ibstat works as expected CA 'mlx5_0' CA type: MT4120 Number of ports: 1 Firmware version: 16.23.1020 Hardware version: 0 Node GUID: 0x00155dfffe33ff49 System image GUID: 0x506b4b0300f521ec Port 1: State: Active Physical state: LinkUp Rate: 100 Base lid: 713 LMC: 0 SM lid: 16 Capability mask: 0x2651ec48 Port GUID: 0x00155dfffd33ff49 Link layer: InfiniBand This Family exhibits the bug, with a subsystem of MT28800: lspci -v|egrep 'Mel|mlx' 0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Subsystem: Mellanox Technologies MT28800 Family [ConnectX-5 Virtual Function] Kernel driver in use: mlx5_core Kernel modules: mlx5_core This issue does not occur with Ubuntu 18.04, which has a different Subsystem(MT27800): lspci -v|egrep 'Mel|mlx' 0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Subsystem: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Kernel driver in use: mlx5_core Kernel modules: mlx5_core If we could, we would like to move to rmda-core to version 22 or higher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856605/+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 1849713] Re: Warning message in logs after kernel update to linux-image-4.15.0-66-generic
Please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
Yes, it should be the one picked by GRUB. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" Status in linux package in Ubuntu: Incomplete Bug description: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSBC1 Internal Connector Type: None External Reference Designator: USB TYPEC External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0007, DMI type 8, 9 bytes Port Connector Information Internal
[Kernel-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend
Can you please file a new bug report so it can be tracked separately? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Status in xserver-xorg-video-amdgpu source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in xserver-xorg-video-amdgpu source package in Eoan: Invalid Bug description: === SRU Justification === [Impact] Screen freeze after S3 on AMD Stoney Ridge. [Fix] Pin the VRAM so it won't contain garbage data after S3. [Test] After applying this patch I can confirm the issue is gone on Dell Inspiron 3180, a Stoney Ridge laptop. [Regression Potential] Low. This patch only touched a small subset of amdgpu. === Original Bug Report === It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+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 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello You-Sheng, Thanks for responding again. Yes, I was just looking at doing a bisect. I've done it before for another problem. I just have to familiarise myself again with the procedures for it. Will attend to it soon. Regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release Status in linux package in Ubuntu: Confirmed Bug description: After the update to install kernel 4.15.0-72-generic (a bit over a week ago) my computer will not boot. On boot, all I see is the purple screen with: Loading Linux 4.15.0-72-generic ... Loading initial ramdisk ... and nothing happens. Just sits there. I've waited about 5-10 minutes on occasion but to no avail. I've checked a number of logs in /var/log but not found anything. If I go into the advanced options and select kernel 4.15.0-70-generic, the computer boots normally. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 21:53:14 2019 HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1 InstallationDate: Installed on 2018-09-16 (454 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE Sabre 17WV8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=9455257c-d3b7-4d61-853d-ab0b0ee40013 ro acpi=off RelatedPackageVersions: linux-restricted-modules-4.15.0-70-generic N/A linux-backports-modules-4.15.0-70-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F05 dmi.board.asset.tag: Tag 12345 dmi.board.name: Sabre 17WV8 dmi.board.vendor: GIGABYTE dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF05:bd05/22/2018:svnGIGABYTE:pnSabre17WV8:pvrNotApplicable:rvnGIGABYTE:rnSabre17WV8:rvrNotApplicable:cvnGIGABYTE:ct10:cvrN/A: dmi.product.family: Sabre dmi.product.name: Sabre 17WV8 dmi.product.version: Not Applicable dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+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 1823037] Re: amd_iommu possible data corruption
Running Ubuntu 19.10 5.4.3-050403-generic Ryzen 3900x GA x570 UD mainboard DDR 3200 , I have been getting data corruption on my 4x SSD on Sata ports ( btrfs/ext4) disks running from my LSI / Avago SAS Raid 9302-16e 12Gb/s PCIe 3.0 controller (btrfs/EXT4) and all my disks running from my HBA (zfs) I started off with PCI-e gen 4 dropped it to gen 3 as that is what my raid controller is as not using a NVMe yet all 64 gig Memory test's good and HDD's test good if tested individually anymore than 8 being accessed at a time they fail being 3 separate controllers and multiple disks I am leading towards a software issue and I remember having data issues before when I had my a10-5800k and that was solved by disabling iommu , I had no issues with this setup while running my intel 4790k -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. The exlcusion range limit register needs to contain the base-address of the last page that is part of the range, as bits 0-11 of this register are treated as 0xfff by the hardware for comparisons. So correctly set the exclusion range in the hardware to the last page which is _in_ the range. [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly These can be picked from my branches here: Bionic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic 1823037-amd_iommu-cherrypick b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range in iova-domain ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range correctly Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic 1823037-amd_iommu-cherrypick 0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range in iova-domain fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range correctly Disco: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco 1823037-amd_iommu-cherrypick 6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range correctly Note Disco only required f1cd47fe12 as the first patch was already picked in LP: #1830934 Not necessary for Eoan as these are already upstream in 5.2-rc1 [Regression Risk] Low,this adds memory protection to the driver and has already been applied upstream and tested by Dell for 24 hours with no failures noted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+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 1856440] Re: cpufreq: no or unknown cpufreq driver
** 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/1856440 Title: cpufreq: no or unknown cpufreq driver Status in linux package in Ubuntu: Confirmed Bug description: Not sure where this goes, but no cpufreq driver is available in 19.10 or 20.04 on AMD CPUs. I'm not sure why this is happening, but no cpufreq driver gets loaded. Output of cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. Output of cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency coordinated by software: Not Available maximum transition latency: Cannot determine or is not supported. Not Available available cpufreq governors: Not Available Unable to determine current policy current CPU frequency: Unable to call hardware current CPU frequency: Unable to call to kernel boost state support: Supported: yes Active: yes Boost States: 3 Total States: 8 Pstate-Pb0: 3300MHz (boost state) Pstate-Pb1: 3100MHz (boost state) Pstate-Pb2: 2800MHz (boost state) Pstate-P0: 2600MHz Pstate-P1: 2200MHz Pstate-P2: 1800MHz Pstate-P3: 1400MHz Pstate-P4: 1200MHz Issue is present in 19.10. Upgraded to 20.04 to see if issue persists and it does. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.3.0-24-lowlatency 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: erich 3958 F pulseaudio /dev/snd/controlC3: erich 3958 F pulseaudio /dev/snd/controlC1: erich 3958 F pulseaudio /dev/snd/controlC0: erich 3958 F pulseaudio CurrentDesktop: GNOME Date: Sat Dec 14 20:59:10 2019 InstallationDate: Installed on 2019-02-12 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) MachineType: Dell Inc. Inspiron 5576 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-lowlatency root=UUID=cbf0a967-a34d-43b1-a42e-993daa70b8f7 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-lowlatency N/A linux-backports-modules-5.3.0-24-lowlatency N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-15 (0 days ago) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0HJ6MY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd01/29/2018:svnDellInc.:pnInspiron5576:pvr1.0.7:rvnDellInc.:rn0HJ6MY:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5576 dmi.product.sku: 07E2 dmi.product.version: 1.0.7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856440/+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 1852907] Re: [Ivy Bridge] Booting problem
Please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ If it doesn't work, Please file an upstream bug at intel graphics upstream: https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852907 Title: [Ivy Bridge] Booting problem Status in linux package in Ubuntu: Confirmed Bug description: the booting problem was sometimes solved by turn the laptop off and wait for few minutes to turn it on again. but it was not always worked. my laptop was preinstalled with windows 8 and upgraded into windows 10. then i chosed to erased all data and install ubuntu 18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 19:08:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics Controller [1179:fb71] InstallationDate: Installed on 2018-07-21 (484 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: TOSHIBA Satellite P845t ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=fa82f47e-1fa8-4ba5-8e85-89c92962e160 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: 6.50 dmi.board.asset.tag: NULL dmi.board.name: TOSHIBA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr6.50:bd09/26/2012:svnTOSHIBA:pnSatelliteP845t:pvrPSPJ5U-009002:rvnTOSHIBA:rnTOSHIBA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: Satellite P845t dmi.product.version: PSPJ5U-009002 dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852907/+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 1847499] Re: USB Huion 1060PLUS and kernel 5.3.0 on Eoan [on hold]
Would it be possible for you to do a kernel bisection? First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the working version you found) $ git bisect bad $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847499 Title: USB Huion 1060PLUS and kernel 5.3.0 on Eoan [on hold] Status in linux package in Ubuntu: Confirmed Bug description: I am having issues with the tablet above. Since the upgrade to Eoan (I know, development..) the tablet is not working any more. Dmesg below: [ 7199.742905] usb 1-4: USB disconnect, device number 9 [ 7199.742911] usb 1-4.1: USB disconnect, device number 10 [ 7199.743381] usb 1-4.4: USB disconnect, device number 11 [ 7206.101315] usb 1-4: new high-speed USB device number 12 using xhci_hcd [ 7206.227830] usb 1-4: New USB device found, idVendor=058f, idProduct=6254, bcdDevice= 1.00 [ 7206.227836] usb 1-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 7206.227840] usb 1-4: Product: USB2.0Hub [ 7206.230807] hub 1-4:1.0: USB hub found [ 7206.230868] hub 1-4:1.0: 4 ports detected [ 7206.518332] usb 1-4.1: new full-speed USB device number 13 using xhci_hcd [ 7206.621492] usb 1-4.1: New USB device found, idVendor=256c, idProduct=006e, bcdDevice=30.00 [ 7206.621498] usb 1-4.1: New USB device strings: Mfr=5, Product=6, SerialNumber=0 [ 7206.627684] usb 1-4.1: can't set config #1, error -32 [ 7206.703319] usb 1-4.4: new high-speed USB device number 14 using xhci_hcd [ 7206.794338] usb 1-4.4: New USB device found, idVendor=058f, idProduct=6366, bcdDevice= 1.00 [ 7206.794346] usb 1-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7206.794351] usb 1-4.4: Product: Mass Storage Device [ 7206.794353] usb 1-4.4: Manufacturer: Generic [ 7206.794356] usb 1-4.4: SerialNumber: 058F0OB1 [ 7206.799699] usb-storage 1-4.4:1.0: USB Mass Storage device detected Unfortunately there is not much to be found regarding the >>can't set config<< thing with the code 32. The digimind driver compiles fine. The funny part is: After a suspend and resume the tablet is working until unplugged and plugged in. Any sugestions? Kernel 5.2 is working fine, have to sort out the ZFS module though and it would be nice to stick with the official components. Cheers, Henning ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-13-lowlatency 5.3.0-13.14 ProcVersionSignature: Ubuntu 5.3.0-13.14-lowlatency 5.3.0 Uname: Linux 5.3.0-13-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henninge 2253 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 9 17:42:28 2019 InstallationDate: Installed on 2018-10-24 (349 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire VN7-572G ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-lowlatency root=UUID=b0b1c52f-0c00-4a1a-aa55-bcf97ee20897 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-lowlatency N/A linux-backports-modules-5.3.0-13-lowlatency N/A linux-firmware 1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-27 (12 days ago) dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-572G dmi.board.vendor: Acer dmi.board.version: V1.05 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd09/25/2015:svnAcer:pnAspireVN7-572G:pvrV1.05:rvnAcer:rnAspireVN7-572G:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: SKL dmi.product.name: Aspire VN7-572G dmi.product.sku: Aspire VN7-572G_1037_1.05 dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1856091] Re: [amdgpu] kernel: [ 6767.461655] INFO: task Xorg:3261 blocked for more than 120 seconds.
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc2/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856091 Title: [amdgpu] kernel: [ 6767.461655] INFO: task Xorg:3261 blocked for more than 120 seconds. Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: kernel: [ 6767.461655] INFO: task Xorg:3261 blocked for more than 120 seconds. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 21:05:05 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:0b36] InstallationDate: Installed on 2019-11-07 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=2e5c8ff6-67d0-4aa4-ae83-63a0b2838d04 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856091/+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 1856427] Re: k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
Thank you for your report. This looks like a valid warning to me, rather than a bug in Ubuntu. Also the bug lacks some details to go any further on it. You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu. If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: lm-sensors (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1856427 Title: k8temp :00:18.3: Temperature readouts might be wrong - check erratum #141 Status in linux package in Ubuntu: Incomplete Status in lm-sensors package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) sensors version 3.5.0 with libsensors version 3.5.0 3) No error. 4) Error in logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856427/+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 1856507] Re: [nvidia] Login screen doesn't show up after installing the Nvidia driver, on a desktop with only an Nvidia GPU
Thank you, Daniel. >From one boot after the failed one, here it is attached. ** Attachment added: "journalctl -b-1" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1856507/+attachment/5313189/+files/prevboot.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1856507 Title: [nvidia] Login screen doesn't show up after installing the Nvidia driver, on a desktop with only an Nvidia GPU Status in gdm3 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-435 package in Ubuntu: Incomplete Bug description: Attempting to boot after installing nvidia-driver-435, the login screen does not show up. I tried editing /etc/gdm3/custom.conf and uncommenting the line: #WaylandEnable=false And then rebooting. No apparent change. Still no login screen. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 10:46:58 2019 InstallationDate: Installed on 2010-10-12 (3351 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: Upgraded to eoan on 2019-10-23 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856507/+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 1854680] Re: Wireless mouse stops working after closing lid and using external monitor
Does this issue happen if evdi (i.e. DisplayLink) driver is removed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854680 Title: Wireless mouse stops working after closing lid and using external monitor Status in linux package in Ubuntu: Confirmed Bug description: My Lenovo Thinkpad i7 runs Ubuntu 5.3.0-23 with ease however I noticed that when I close the lid on my computer all usb mouses act up (new or old). After the lid is closed the mouse seems to "pressed" thus not working as normal -- oddly the same keyboard or any keyboard is fine though. I have uploaded the two log files in addition to a desktop screen- record of how the mouse acts up when I used it after and before closing the lid. Docking Station: Dell D3100 Monitors: 3 Dell U2415 Ubuntu kernel 5.3.0-23 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexander 12914 F pulseaudio /dev/snd/controlC0: alexander 12914 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19.2 EcryptfsInUse: Yes InstallationDate: Installed on 2019-11-09 (32 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 MachineType: LENOVO 2355CE9 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.173.12 Tags: tina Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETB5WW (2.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 2355CE9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETB5WW(2.75):bd06/10/2019:svnLENOVO:pn2355CE9:pvrThinkPadT430s:rvnLENOVO:rn2355CE9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2355CE9 dmi.product.sku: LENOVO_MT_2355 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854680/+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 1853997] Re: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset
=>Is this bug duplicate of bug 1853999? No, it should inject diff error type. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853997 Title: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset Status in kunpeng920: Triaged Status in kunpeng920 ubuntu-18.04 series: Triaged Status in kunpeng920 ubuntu-18.04-hwe series: Triaged Status in kunpeng920 ubuntu-19.04 series: Triaged Status in kunpeng920 ubuntu-19.10 series: Triaged Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Triaged Status in linux source package in Disco: Triaged Status in linux source package in Eoan: Triaged Status in linux source package in Focal: Fix Released Bug description: "[Steps to Reproduce] 1. Close all the PHYS; 2. Inject error; 3. Open one PHY; [Actual Results] Some disk will be lost [Expected Results] No disk will be lost [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA+I59 Kernel: NA [Resolution] When init device for SAS disks, it will send TMF IO to clear disks. At that time TMF IO is broken by some operations such as injecting controller reset from HW RAs event, the TMF IO will be timeout, and at last device will be gone. Print is as followed: hisi_sas_v3_hw :74:02.0: dev[240:1] found ... hisi_sas_v3_hw :74:02.0: controller resetting... hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11 hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11 hisi_sas_v3_hw :74:02.0: controller reset complete hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done hisi_sas_v3_hw :74:02.0: dev[240:1] is gone sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d, error:5 To improve the reliability, retry TMF IO max of 3 times for SAS disks which is the same as softreset does." scsi: hisi_sas: Fix the conflict between device gone and host reset To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853997/+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 1760273] Re: kernel: (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info()
Yep, agreeing tho You-Sheng. People are seeing this when e.g. using lm-sensores as it will trigger the hwmon interfaces which have plenty of these old calls. Here an example list: Documentation/hwmon/hwmon-kernel-api.rst:27: hwmon_device_register_with_groups(struct device *dev, const char *name, Documentation/hwmon/hwmon-kernel-api.rst:32: devm_hwmon_device_register_with_groups(struct device *dev, Documentation/hwmon/hwmon-kernel-api.rst:37: hwmon_device_register_with_info(struct device *dev, Documentation/hwmon/hwmon-kernel-api.rst:43: devm_hwmon_device_register_with_info(struct device *dev, Documentation/hwmon/hwmon-kernel-api.rst:53:hwmon_device_register_with_groups registers a hardware monitoring device. Documentation/hwmon/hwmon-kernel-api.rst:58:hwmon_device_register_with_groups will attach this pointer to the newly Documentation/hwmon/hwmon-kernel-api.rst:62:hwmon_device_register_with_groups creates the hwmon device with name attribute Documentation/hwmon/hwmon-kernel-api.rst:67:devm_hwmon_device_register_with_groups is similar to Documentation/hwmon/hwmon-kernel-api.rst:68:hwmon_device_register_with_groups. However, it is device managed, meaning the Documentation/hwmon/hwmon-kernel-api.rst:71:hwmon_device_register_with_info is the most comprehensive and preferred means Documentation/hwmon/hwmon-kernel-api.rst:78:devm_hwmon_device_register_with_info is similar to Documentation/hwmon/hwmon-kernel-api.rst:79:hwmon_device_register_with_info. However, it is device managed, meaning the Documentation/hwmon/hwmon-kernel-api.rst:86:hwmon_device_register_with_groups or hwmon_device_register_with_info. Documentation/hwmon/hwmon-kernel-api.rst:90:the call to devm_hwmon_device_register_with_groups or Documentation/hwmon/hwmon-kernel-api.rst:91:hwmon_device_register_with_info and if the automatic (device managed) Documentation/hwmon/hwmon-kernel-api.rst:98:Using devm_hwmon_device_register_with_info() Documentation/hwmon/hwmon-kernel-api.rst:101:hwmon_device_register_with_info() registers a hardware monitoring device. Documentation/hwmon/hwmon-kernel-api.rst:339:hwmon_device_register_with_info or devm_hwmon_device_register_with_info, Documentation/hwmon/submitting-patches.rst:127:* Use devm_hwmon_device_register_with_info() or, if your driver needs a remove Documentation/hwmon/submitting-patches.rst:128: function, hwmon_device_register_with_info() to register your driver with the Documentation/hwmon/submitting-patches.rst:130: possible. Do not use hwmon_device_register(). drivers/net/phy/nxp-tja11xx.c:349: devm_hwmon_device_register_with_info(dev, priv->hwmon_name, drivers/net/phy/aquantia_hwmon.c:244: hwmon_dev = devm_hwmon_device_register_with_info(dev, hwmon_name, drivers/net/phy/sfp.c:1173: sfp->hwmon_dev = hwmon_device_register_with_info(sfp->dev, drivers/net/phy/marvell10g.c:191: priv->hwmon_dev = devm_hwmon_device_register_with_info(dev, drivers/net/phy/marvell.c:2047: priv->hwmon_dev = devm_hwmon_device_register_with_info( drivers/net/ethernet/sfc/mcdi_mon.c:505:hwmon->device = hwmon_device_register_with_groups(>pci_dev->dev, drivers/net/ethernet/emulex/benet/be_main.c:6014: devm_hwmon_device_register_with_groups(>dev, drivers/net/ethernet/qlogic/qlcnic/qlcnic_sysfs.c:1301: hwmon_dev = hwmon_device_register_with_groups(dev, qlcnic_driver_name, drivers/net/ethernet/intel/ixgbe/ixgbe_sysfs.c:196: hwmon_dev = devm_hwmon_device_register_with_groups(>pdev->dev, drivers/net/ethernet/intel/igb/igb_hwmon.c:213: hwmon_dev = devm_hwmon_device_register_with_groups(>pdev->dev, drivers/net/ethernet/broadcom/tg3.c:10877: tp->hwmon_dev = hwmon_device_register_with_groups(>dev, "tg3", drivers/net/ethernet/broadcom/bnxt/bnxt.c:8950: bp->hwmon_dev = hwmon_device_register_with_groups(>dev, drivers/net/ethernet/mellanox/mlxsw/core_hwmon.c:660: hwmon_dev = hwmon_device_register_with_groups(mlxsw_bus_info->dev, drivers/net/ethernet/netronome/nfp/nfp_hwmon.c:150: pf->hwmon_dev = hwmon_device_register_with_info(>pdev->dev, "nfp", drivers/net/ethernet/aquantia/atlantic/aq_drvinfo.c:116:hwmon_dev = devm_hwmon_device_register_with_info(dev, drivers/net/wireless/ath/ath10k/thermal.c:188: /* Avoid linking error on devm_hwmon_device_register_with_groups, I drivers/net/wireless/ath/ath10k/thermal.c:194: hwmon_dev = devm_hwmon_device_register_with_groups(ar->dev, drivers/thermal/thermal_hwmon.c:150:hwmon->device = hwmon_device_register_with_info(>device, hwmon->type, drivers/w1/w1.c:647:= hwmon_device_register_with_info(>dev, drivers/input/touchscreen/sun4i-ts.c:353: hwmon = devm_hwmon_device_register_with_groups(ts->dev, "sun4i_ts", drivers/input/touchscreen/ads7846.c:530:ts->hwmon = hwmon_device_register_with_groups(>dev, spi->modalias, drivers/power/supply/power_supply_hwmon.c:350: hwmon = devm_hwmon_device_register_with_info(dev, name,
[Kernel-packages] [Bug 1856297] Re: Processes freeze and need to restart -skill will not stop the process
Does this issue happen if proprietary Nvidia driver is used instead? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856297 Title: Processes freeze and need to restart -skill will not stop the process Status in linux package in Ubuntu: Confirmed Bug description: i first thought that it is a graphic issue. but update Manager freezes as well. that does not block ubuntu but but some programs we hen they freeze do ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julia 1271 F pulseaudio /dev/snd/controlC0: julia 1271 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 10:34:11 2019 HibernationDevice: RESUME=UUID=b7cdfca6-a479-4b51-afb2-fdd14b39b95c MachineType: Dell Inc. Precision M4500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-13 (29 days ago) dmi.bios.date: 11/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 041WH1 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/20/2010:svnDellInc.:pnPrecisionM4500:pvr0001:rvnDellInc.:rn041WH1:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4500 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856297/+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
