[Kernel-packages] [Bug 2013086] Re: regression: max number of loop devices
** Description changed: Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter. In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means no more than 8 loop devices are supported. This is a regression. At least one other distro solves this by compiling with CONFIG_BLK_DEV_LOOP_MIN_COUNT=0 [1]; maybe Ubuntu could start doing that as well. We currently workaround this by setting max_loop=0 on the kernel cmdline but would rather not have to. - - [1] https://aur.archlinux.org/cgit/aur.git/tree/config?h=linux-lts515#n2492 + [1] https://github.com/archlinux/svntogit- + packages/blob/62b8243b1d485493d3e8b10b05281efa20fe7918/trunk/config#L2517 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2013086 Title: regression: max number of loop devices Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter. In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means no more than 8 loop devices are supported. This is a regression. At least one other distro solves this by compiling with CONFIG_BLK_DEV_LOOP_MIN_COUNT=0 [1]; maybe Ubuntu could start doing that as well. We currently workaround this by setting max_loop=0 on the kernel cmdline but would rather not have to. [1] https://github.com/archlinux/svntogit- packages/blob/62b8243b1d485493d3e8b10b05281efa20fe7918/trunk/config#L2517 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2013086/+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 2013086] [NEW] regression: max number of loop devices
Public bug reported: Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter. In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means no more than 8 loop devices are supported. This is a regression. At least one other distro solves this by compiling with CONFIG_BLK_DEV_LOOP_MIN_COUNT=0 [1]; maybe Ubuntu could start doing that as well. We currently workaround this by setting max_loop=0 on the kernel cmdline but would rather not have to. [1] https://aur.archlinux.org/cgit/aur.git/tree/config?h=linux-lts515#n2492 ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2013086 Title: regression: max number of loop devices Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter. In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means no more than 8 loop devices are supported. This is a regression. At least one other distro solves this by compiling with CONFIG_BLK_DEV_LOOP_MIN_COUNT=0 [1]; maybe Ubuntu could start doing that as well. We currently workaround this by setting max_loop=0 on the kernel cmdline but would rather not have to. [1] https://aur.archlinux.org/cgit/aur.git/tree/config?h=linux-lts515#n2492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2013086/+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 1996678] Re: containerd sporadic timeouts
Note that this is not limited to containerd; we're running an upstream version of the prometheus `node_exporter` on several hosts that is also seeing spurious hangs that started after upgrading to the -132 kernel. Rebooting into -131 fixes it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996678 Title: containerd sporadic timeouts Status in containerd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in containerd source package in Focal: Confirmed Status in linux source package in Focal: In Progress Bug description: This morning I routinely upgraded security upgrades on number of machines. Containerd has upgraded from `1.5.9-0ubuntu1~20.04.4` for me `1.5.9-0ubuntu1~20.04.5`. What happened next: at some random time on machines with new containerd something happens with containerd tasks and/or cgroups. This is how it's seen in syslog: containerd[710]: time="2022-11-16T03:21:21.004153517Z" level=error msg="get state for 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a" error="context deadline exceeded: unknown" And some ctr commands: # ctr --namespace k8s.io task ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a0 UNKNOWN See that the status of the task is UNKNOWN (!!!) # ctr --namespace k8s.io container ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a k8s.gcr.io/pause:3.5 io.containerd.runc.v2 Cgroups: ├─kubepods-besteffort-pod3fdc0061_bbf6_47d1_97f5_b1f271b46e23.slice │ ├─cri-containerd-5f78e0cb957de97fd8465cc42c842bdd764d981ca7a903a2515bbc6bb06796a9.scope … │ │ └─2677 /csi-node-driver-registrar --v=0 --csi-address=/csi/csi.sock --k… │ ├─cri-containerd-af070f16c1f0ff22eb16661e787e85db3810727909abd23d69a6a43578c1dced.scope … │ │ └─3264 /usr/local/bin/cephcsi --type=liveness --endpoint=unix:///csi/cs… │ ├─cri-containerd-4e063ef0c8f768dbf34cf7a179bca5cc98a04fa7e00b29d20c17d3031d409f86.scope … │ │ └─2960 /usr/local/bin/cephcsi --nodeid=nas-decent-bobcat.dev-k8s-1.hq.w… │ └─cri-containerd-2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a.scope … │ └─2414 /pause # ps auxf|grep 2414 -B 2 root2279 0.1 0.0 114100 4956 ?Sl Nov15 0:42 /usr/bin/containerd-shim-runc-v2 -namespace k8s.io -id 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a -address /run/containerd/containerd.sock 65535 2414 0.0 0.0964 4 ?Ss Nov15 0:00 \_ /pause It happens not immediately - but after some random time. Sometimes it's several minutes, sometimes it's around an hour. But nonetheless - all machines with the new package get into this weird state. As long as I revert package - it all returns to run as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1996678/+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 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
@Simon, you should upgrade the ubuntu-mainline-kernel script, the directory layout on kernel-ppa has changed, so the kernels are in a different location. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
As a workaround you can add "initcall_blacklist=elants_i2c_driver_init" to GRUB_CMDLINE_LINUX, run 'update-grub', power down the laptop and start it again. Works for me. (5.7.1 kernel-ppa mainline) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1851470] Re: cephfs mounts hangs machine when written to
We're seeing a similar crash on a 16.04 based machine running 4.15.0-66-generic ; downgrading to 4.15.0-51-generic appears to prevent it. Appended kernel log with very similar entries. ** Attachment added: "kernel log from loading ceph to reboot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851470/+attachment/5303454/+files/kern.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/1851470 Title: cephfs mounts hangs machine when written to Status in linux package in Ubuntu: Confirmed Bug description: As reported on the ceph-users mailing list, the latest HWE kernel for ubuntu 18.04 (and the current kernel for disco 19.04) has a problem with cephfs mounts when you write to it. (kernel version 5.0.0-32) We are using cephfs to write backups to with amanda (virtual tapes) and the backups started failing when the virtual machine was running this version of the kernel. As it is the latest kernel version and we like to keep up with updates, we have trouble uninstalling the latest kernel version, because then we also need to uninstall the package that depends on the latest hwe kernel. https://www.mail-archive.com/ceph-users@ceph.io/msg00940.html downgrading to (or booting) 5.0.0-31 helps: https://www.mail-archive.com/ceph-users@ceph.io/msg00941.html The problem seems to be this backported patch: "ceph: use ceph_evict_inode to cleanup inode's resource" The severity is high when using cephfs mounted while running this kernel, the file system is unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851470/+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 1761930] Re: System lockup immediatly after Unity launches on upgrade to 4.13.0-38-generic
Also tested 4.13.0-38-generic without any of the extras modules packages etc. ** Tags added: kernel-fixed-upstream ** 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/1761930 Title: System lockup immediatly after Unity launches on upgrade to 4.13.0-38-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to 4.13.0-38-generic my system (Acer S7 392) locks up after unity launches on startup. The mouse cursor is present but non responsive. ctrl-alt-delete/backspace/F1/F2... have no effect. Power off by holding power button is the only way to shutdown. Rebooting with 4.13.0-7-generic works as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jasper 2791 F pulseaudio /dev/snd/controlC0: jasper 2791 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Apr 7 17:49:22 2018 HibernationDevice: RESUME=UUID=26d3afe5-0e06-4669-8d23-c639f3ca7011 InstallationDate: Installed on 2015-04-14 (1089 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-30 (158 days ago) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.family: Sharkbay System dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761930/+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 1761930] [NEW] System lockup immediatly after Unity launches on upgrade to 4.13.0-38-generic
Public bug reported: After upgrade to 4.13.0-38-generic my system (Acer S7 392) locks up after unity launches on startup. The mouse cursor is present but non responsive. ctrl-alt-delete/backspace/F1/F2... have no effect. Power off by holding power button is the only way to shutdown. Rebooting with 4.13.0-7-generic works as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jasper 2791 F pulseaudio /dev/snd/controlC0: jasper 2791 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Apr 7 17:49:22 2018 HibernationDevice: RESUME=UUID=26d3afe5-0e06-4669-8d23-c639f3ca7011 InstallationDate: Installed on 2015-04-14 (1089 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-30 (158 days ago) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.family: Sharkbay System dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761930 Title: System lockup immediatly after Unity launches on upgrade to 4.13.0-38-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to 4.13.0-38-generic my system (Acer S7 392) locks up after unity launches on startup. The mouse cursor is present but non responsive. ctrl-alt-delete/backspace/F1/F2... have no effect. Power off by holding power button is the only way to shutdown. Rebooting with 4.13.0-7-generic works as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jasper 2791 F pulseaudio /dev/snd/controlC0: jasper 2791 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Apr 7 17:49:22 2018 HibernationDevice: RESUME=UUID=26d3afe5-0e06-4669-8d23-c639f3ca7011 InstallationDate: Installed on 2015-04-14 (1089 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-30 (158 days ago) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.family: Sharkbay System dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761930/+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 882147] Re: overlayfs does not implement inotify interfaces correctly
tail -f works because it checks the file every sleep-interval seconds (defaults to 1 second). tail -f -s 10 /var/log/syslog gives a burst of new lines every 10 seconds. With this test I see 10-seconds bursts with linux 4.10.0 and 4.13.0 indicating this bug isn't fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/882147 Title: overlayfs does not implement inotify interfaces correctly Status in coreutils package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Status in coreutils source package in Precise: Confirmed Status in linux source package in Precise: Triaged Bug description: When using tail on the liveCD some updates are not reported. This seems to be triggered by tail using inotify to identify modified files. Overlayfs does not appear to be implementing inotify quite the way you might hope reporting only against the underlying filesystems. Related bugs: * bug 1213925: upstart should notice "/etc" inode change ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu3 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apw2296 F pulseaudio /dev/snd/pcmC0D0c: apw2296 F...m pulseaudio /dev/snd/pcmC0D0p: apw2296 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc70 irq 47' Mixer name : 'Intel Cantiga HDMI' Components : 'HDA:111d7675,1028029f,00100103 HDA:80862802,80860101,0010' Controls : 20 Simple ctrls : 11 Date: Wed Oct 26 17:46:16 2011 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d8328455-deac-4bae-877d-c408d371cefe MachineType: Dell Inc. Studio 1537 ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=cf503727-25f2-4ecd-b0f3-2b894523bcba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 SourcePackage: linux UpgradeStatus: Upgraded to oneiric on 2011-10-17 (9 days ago) WpaSupplicantLog: dmi.bios.date: 09/22/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A03 dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03: dmi.product.name: Studio 1537 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/882147/+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 1452460] Re: Turbo mode on i7 is not enabled upon resume
Sorry Christopher, Further testing reveals that the bug is still present in 4.1-rc2. No idea why it worked the first time, but it has not subsequently. ** Tags removed: kernel-bug-fixed-upstream kernel-bug-fixed-upstream-4.1-rc2 needs-reverse-bisect ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1-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/1452460 Title: Turbo mode on i7 is not enabled upon resume Status in linux package in Ubuntu: Incomplete Bug description: Turbo mode is not enabled upon resume from suspend. To enable I must issue: ``echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo`` I would expect that Turbo was re-enabled by default from resume. I created a script in /usr/lib/pm-utils/sleep.d/ to issue the above commands, but clearly that mechanism is depreciated. I am reporting this bug against systemd as I assume that it is managing the running of startup and resume scripts. A quick hack solution would be appreciated in the short term. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 Uname: Linux 4.0.0-04rc7-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 09:11:12 2015 InstallationDate: Installed on 2015-04-14 (22 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc7-generic root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452460/+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 1452460] Re: Turbo mode on i7 is not enabled upon resume
I have never used this machine with anything less than 15.04, so sorry I cannot say. On 10 May 2015 at 12:13, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Jasper, did this issue not occur in a release prior to Vivid? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1452460 Title: Turbo mode on i7 is not enabled upon resume Status in linux package in Ubuntu: Incomplete Bug description: Turbo mode is not enabled upon resume from suspend. To enable I must issue: ``echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo`` I would expect that Turbo was re-enabled by default from resume. I created a script in /usr/lib/pm-utils/sleep.d/ to issue the above commands, but clearly that mechanism is depreciated. I am reporting this bug against systemd as I assume that it is managing the running of startup and resume scripts. A quick hack solution would be appreciated in the short term. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 Uname: Linux 4.0.0-04rc7-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 09:11:12 2015 InstallationDate: Installed on 2015-04-14 (22 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc7-generic root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452460/+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/1452460 Title: Turbo mode on i7 is not enabled upon resume Status in linux package in Ubuntu: Incomplete Bug description: Turbo mode is not enabled upon resume from suspend. To enable I must issue: ``echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo`` I would expect that Turbo was re-enabled by default from resume. I created a script in /usr/lib/pm-utils/sleep.d/ to issue the above commands, but clearly that mechanism is depreciated. I am reporting this bug against systemd as I assume that it is managing the running of startup and resume scripts. A quick hack solution would be appreciated in the short term. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 Uname: Linux 4.0.0-04rc7-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 09:11:12 2015 InstallationDate: Installed on 2015-04-14 (22 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc7-generic root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452460/+subscriptions -- Mailing
[Kernel-packages] [Bug 1452460] Re: Turbo mode on i7 is not enabled upon resume
I do not use the workaround, and turbo mode is automatically enabled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452460 Title: Turbo mode on i7 is not enabled upon resume Status in linux package in Ubuntu: Incomplete Bug description: Turbo mode is not enabled upon resume from suspend. To enable I must issue: ``echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo`` I would expect that Turbo was re-enabled by default from resume. I created a script in /usr/lib/pm-utils/sleep.d/ to issue the above commands, but clearly that mechanism is depreciated. I am reporting this bug against systemd as I assume that it is managing the running of startup and resume scripts. A quick hack solution would be appreciated in the short term. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 Uname: Linux 4.0.0-04rc7-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 09:11:12 2015 InstallationDate: Installed on 2015-04-14 (22 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc7-generic root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452460/+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 1452460] Re: Turbo mode on i7 is not enabled upon resume
Using linus' latest kernel from git (12 hours old) the `problem' persists, and turbo must be re-enabed manually or via systemd script. I built the deb-pkg target. I will test the other ubuntu versions soon. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1.0-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/1452460 Title: Turbo mode on i7 is not enabled upon resume Status in linux package in Ubuntu: Incomplete Bug description: Turbo mode is not enabled upon resume from suspend. To enable I must issue: ``echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo`` I would expect that Turbo was re-enabled by default from resume. I created a script in /usr/lib/pm-utils/sleep.d/ to issue the above commands, but clearly that mechanism is depreciated. I am reporting this bug against systemd as I assume that it is managing the running of startup and resume scripts. A quick hack solution would be appreciated in the short term. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 Uname: Linux 4.0.0-04rc7-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 09:11:12 2015 InstallationDate: Installed on 2015-04-14 (22 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc7-generic root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452460/+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 1452460] Re: Turbo mode on i7 is not enabled upon resume
The `problem' is fixed in 4.1-rc2. But As with the `echo 0... echo 1`... method the processor is _always_ in turbo once it has resumed from sleep. On my i7-4500U this is about 2.78 and 2.97Ghz. ** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1.0-rc2 ** Tags added: kernel-bug-fixed-upstream-4.1-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/1452460 Title: Turbo mode on i7 is not enabled upon resume Status in linux package in Ubuntu: Incomplete Bug description: Turbo mode is not enabled upon resume from suspend. To enable I must issue: ``echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo`` I would expect that Turbo was re-enabled by default from resume. I created a script in /usr/lib/pm-utils/sleep.d/ to issue the above commands, but clearly that mechanism is depreciated. I am reporting this bug against systemd as I assume that it is managing the running of startup and resume scripts. A quick hack solution would be appreciated in the short term. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 Uname: Linux 4.0.0-04rc7-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 09:11:12 2015 InstallationDate: Installed on 2015-04-14 (22 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc7-generic root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452460/+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 1452460] Re: Turbo mode on i7 is not enabled upon resume
Many thanks for the quick response. I will disseminate this to the many questions in ask-ubuntu relating to resume scripts. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452460 Title: Turbo mode on i7 is not enabled upon resume Status in linux package in Ubuntu: New Bug description: Turbo mode is not enabled upon resume from suspend. To enable I must issue: ``echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo`` I would expect that Turbo was re-enabled by default from resume. I created a script in /usr/lib/pm-utils/sleep.d/ to issue the above commands, but clearly that mechanism is depreciated. I am reporting this bug against systemd as I assume that it is managing the running of startup and resume scripts. A quick hack solution would be appreciated in the short term. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 Uname: Linux 4.0.0-04rc7-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 09:11:12 2015 InstallationDate: Installed on 2015-04-14 (22 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc7-generic root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452460/+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 1406132] Re: Radeon GFX card fails on 3.16.0-28
All kernels from mainline worked (took a selection from 3.16.0 to 3.19) It turns out that 3.16.0-28 works without linus-image-extras-3.16.0-28-generic which contains /lib/modules/3.16.0-28-generic/kernel/drivers/gpu/drm/radeon/radeon.ko and /lib/modules/3.16.0-28-generic/kernel/drivers/video/fbdev/aty/radeonfb.ko But 3.16.0-29-generic (linux-image and linux-image-extra) from ./ubuntu/pool/main/l/linux/ works perfectly. So a blip eh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1406132 Title: Radeon GFX card fails on 3.16.0-28 Status in linux package in Ubuntu: Incomplete Bug description: Expected behaviour, and behaviour on previous kernels (3.16.0-25 and before): Normal boot, ending in Lighdm login screen or in my case Kodi Observed behaviour: Boot ends with blank screen, dmesg shows errors. Hypothesus: This is a bug related to upgrading the kernel. What I have done: Using apt-btrfs-snapshots I reverted until I found the upgrade that caused the problem. No X, or X related components were updated on this boundary. Changing the booted kernel did show the problem. Kernels tried that worked: vmlinuz-3.16.0-23-generic vmlinuz-3.16.0-24-generic vmlinuz-3.16.0-25-generic Assuming that 'ubuntu-bug linux' has included enough information. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 Date: Mon Dec 29 09:22:51 2014 HibernationDevice: RESUME=UUID=3493ba1a-188f-4b7d-b9cf-c404cb204ece InstallationDate: Installed on 2014-05-31 (210 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G7 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-28-generic root=UUID=80479971-6f5f-49ed-9923-0ea40b093cb5 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.140 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: lirc_serial UpgradeStatus: Upgraded to vivid on 2014-08-03 (146 days ago) dmi.bios.date: 07/01/2013 dmi.bios.vendor: HP dmi.bios.version: J01 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ01:bd07/01/2013:svnHP:pnProLiantML110G7:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant ML110 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1406132/+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 1406132] Re: Radeon GFX card fails on 3.16.0-28
Cheers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1406132 Title: Radeon GFX card fails on 3.16.0-28 Status in linux package in Ubuntu: Triaged Bug description: Expected behaviour, and behaviour on previous kernels (3.16.0-25 and before): Normal boot, ending in Lighdm login screen or in my case Kodi Observed behaviour: Boot ends with blank screen, dmesg shows errors. Hypothesus: This is a bug related to upgrading the kernel. What I have done: Using apt-btrfs-snapshots I reverted until I found the upgrade that caused the problem. No X, or X related components were updated on this boundary. Changing the booted kernel did show the problem. Kernels tried that worked: vmlinuz-3.16.0-23-generic vmlinuz-3.16.0-24-generic vmlinuz-3.16.0-25-generic Assuming that 'ubuntu-bug linux' has included enough information. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 Date: Mon Dec 29 09:22:51 2014 HibernationDevice: RESUME=UUID=3493ba1a-188f-4b7d-b9cf-c404cb204ece InstallationDate: Installed on 2014-05-31 (210 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G7 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-28-generic root=UUID=80479971-6f5f-49ed-9923-0ea40b093cb5 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.140 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: lirc_serial UpgradeStatus: Upgraded to vivid on 2014-08-03 (146 days ago) dmi.bios.date: 07/01/2013 dmi.bios.vendor: HP dmi.bios.version: J01 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ01:bd07/01/2013:svnHP:pnProLiantML110G7:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant ML110 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1406132/+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 1406132] Re: Radeon GFX card fails on 3.16.0-28
Thank you. Upstream kernel 3.19-rc2 (generic and low latency for Vivid) solved the issue. ** Tags added: kernel-fixed-upstream-3.19-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/1406132 Title: Radeon GFX card fails on 3.16.0-28 Status in linux package in Ubuntu: Incomplete Bug description: Expected behaviour, and behaviour on previous kernels (3.16.0-25 and before): Normal boot, ending in Lighdm login screen or in my case Kodi Observed behaviour: Boot ends with blank screen, dmesg shows errors. Hypothesus: This is a bug related to upgrading the kernel. What I have done: Using apt-btrfs-snapshots I reverted until I found the upgrade that caused the problem. No X, or X related components were updated on this boundary. Changing the booted kernel did show the problem. Kernels tried that worked: vmlinuz-3.16.0-23-generic vmlinuz-3.16.0-24-generic vmlinuz-3.16.0-25-generic Assuming that 'ubuntu-bug linux' has included enough information. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 Date: Mon Dec 29 09:22:51 2014 HibernationDevice: RESUME=UUID=3493ba1a-188f-4b7d-b9cf-c404cb204ece InstallationDate: Installed on 2014-05-31 (210 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G7 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-28-generic root=UUID=80479971-6f5f-49ed-9923-0ea40b093cb5 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.140 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: lirc_serial UpgradeStatus: Upgraded to vivid on 2014-08-03 (146 days ago) dmi.bios.date: 07/01/2013 dmi.bios.vendor: HP dmi.bios.version: J01 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ01:bd07/01/2013:svnHP:pnProLiantML110G7:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant ML110 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1406132/+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 1406132] [NEW] Radeon GFX card fails on 3.16.0-28
Public bug reported: Expected behaviour, and behaviour on previous kernels (3.16.0-25 and before): Normal boot, ending in Lighdm login screen or in my case Kodi Observed behaviour: Boot ends with blank screen, dmesg shows errors. Hypothesus: This is a bug related to upgrading the kernel. What I have done: Using apt-btrfs-snapshots I reverted until I found the upgrade that caused the problem. No X, or X related components were updated on this boundary. Changing the booted kernel did show the problem. Kernels tried that worked: vmlinuz-3.16.0-23-generic vmlinuz-3.16.0-24-generic vmlinuz-3.16.0-25-generic Assuming that 'ubuntu-bug linux' has included enough information. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 Date: Mon Dec 29 09:22:51 2014 HibernationDevice: RESUME=UUID=3493ba1a-188f-4b7d-b9cf-c404cb204ece InstallationDate: Installed on 2014-05-31 (210 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G7 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-28-generic root=UUID=80479971-6f5f-49ed-9923-0ea40b093cb5 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.140 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: lirc_serial UpgradeStatus: Upgraded to vivid on 2014-08-03 (146 days ago) dmi.bios.date: 07/01/2013 dmi.bios.vendor: HP dmi.bios.version: J01 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ01:bd07/01/2013:svnHP:pnProLiantML110G7:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant ML110 G7 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug staging vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1406132 Title: Radeon GFX card fails on 3.16.0-28 Status in linux package in Ubuntu: New Bug description: Expected behaviour, and behaviour on previous kernels (3.16.0-25 and before): Normal boot, ending in Lighdm login screen or in my case Kodi Observed behaviour: Boot ends with blank screen, dmesg shows errors. Hypothesus: This is a bug related to upgrading the kernel. What I have done: Using apt-btrfs-snapshots I reverted until I found the upgrade that caused the problem. No X, or X related components were updated on this boundary. Changing the booted kernel did show the problem. Kernels tried that worked: vmlinuz-3.16.0-23-generic vmlinuz-3.16.0-24-generic vmlinuz-3.16.0-25-generic Assuming that 'ubuntu-bug linux' has included enough information. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 Date: Mon Dec 29 09:22:51 2014 HibernationDevice: RESUME=UUID=3493ba1a-188f-4b7d-b9cf-c404cb204ece InstallationDate: Installed on 2014-05-31 (210 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G7 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-28-generic root=UUID=80479971-6f5f-49ed-9923-0ea40b093cb5 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.140 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: lirc_serial UpgradeStatus: Upgraded to vivid on 2014-08-03 (146 days ago) dmi.bios.date: 07/01/2013 dmi.bios.vendor: HP dmi.bios.version: J01 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ01:bd07/01/2013:svnHP:pnProLiantML110G7:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant ML110 G7 dmi.sys.vendor: HP To manage
[Kernel-packages] [Bug 1402172] Re: kernel 3.16.0-28-generic breaks Radeon HD 6310
] systemd-logind[1965]: Failed to start user service: Unknown unit: user@1000.service [ 160.918592] systemd-logind[1965]: New session 2 of user jasper. [ 240.043467] INFO: task kworker/2:1:199 blocked for more than 120 seconds. [ 240.043500] Tainted: G C3.16.0-28-generic #38-Ubuntu [ 240.043527] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 240.043559] kworker/2:1 D 880127453840 0 199 2 0x [ 240.043605] Workqueue: events output_poll_execute [drm_kms_helper] [ 240.043632] 880036483d40 0046 880036469e90 00013840 [ 240.043669] 880036483fd8 00013840 880036469e90 8800c74dc208 [ 240.043705] 8800c74dc20c 880036469e90 8800c74dc210 [ 240.045664] Call Trace: [ 240.047609] [817855c9] schedule_preempt_disabled+0x29/0x70 [ 240.049553] [81787b65] __mutex_lock_slowpath+0xd5/0x1f0 [ 240.051477] [81787c9f] mutex_lock+0x1f/0x30 [ 240.053378] [c062d55b] output_poll_execute+0x4b/0x180 [drm_kms_helper] [ 240.055293] [8108da32] process_one_work+0x182/0x4e0 [ 240.057150] [8108ddfb] worker_thread+0x6b/0x6a0 [ 240.058927] [81784b2d] ? __schedule+0x39d/0x890 [ 240.060654] [8108dd90] ? process_one_work+0x4e0/0x4e0 [ 240.062317] [81094c6b] kthread+0xdb/0x100 [ 240.063939] [81094b90] ? kthread_create_on_node+0x1c0/0x1c0 [ 240.065562] [81789e3c] ret_from_fork+0x7c/0xb0 [ 240.067188] [81094b90] ? kthread_create_on_node+0x1c0/0x1c0 [ 240.068820] INFO: task Xorg:2133 blocked for more than 120 seconds. [ 240.070416] Tainted: G C3.16.0-28-generic #38-Ubuntu [ 240.072016] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 240.073624] XorgD 880127473840 0 2133 1939 0x0040 [ 240.075247] 8800b5837380 0086 8800365be5e0 00013840 [ 240.076899] 8800b5837fd8 00013840 8800365be5e0 8800c74dc208 [ 240.078528] 8800c74dc20c 8800365be5e0 8800c74dc210 [ 240.080154] Call Trace: [ 240.081765] [817855c9] schedule_preempt_disabled+0x29/0x70 [ 240.083377] [81787b65] __mutex_lock_slowpath+0xd5/0x1f0 [ 240.084983] [81787c9f] mutex_lock+0x1f/0x30 [ 240.086598] [c05d1072] drm_modeset_lock_all+0x42/0xd0 [drm] [ 240.088197] [c062f2bf] drm_fb_helper_pan_display+0x2f/0xf0 [drm_kms_helper] [ 240.089802] [8141772a] fb_pan_display+0x9a/0x160 [ 240.091406] [814118c0] bit_update_start+0x20/0x50 [ 240.092985] [8140ff04] fbcon_switch+0x3b4/0x5a0 [ 240.094558] [81499d39] redraw_screen+0x199/0x260 [ 240.096128] [8140e51a] fbcon_blank+0x20a/0x300 [ 240.097691] [810cd7b4] ? wake_up_klogd+0x34/0x50 [ 240.099246] [810cda48] ? console_unlock+0x278/0x420 [ 240.100795] [8107cd2b] ? lock_timer_base.isra.34+0x2b/0x50 [ 240.102348] [8107c4df] ? internal_add_timer+0x2f/0x70 [ 240.103890] [8107e309] ? mod_timer+0x129/0x1f0 [ 240.105425] [8149a87a] do_unblank_screen+0xba/0x1f0 [ 240.106973] [8149a9c0] unblank_screen+0x10/0x20 [ 240.108512] [813aa639] bust_spinlocks+0x19/0x40 [ 240.110042] [81016be8] oops_end+0x38/0x150 [ 240.111577] [8105c5bc] no_context+0x12c/0x310 [ 240.113102] [8105c81d] __bad_area_nosemaphore+0x7d/0x210 [ 240.114563] [8107cd2b] ? lock_timer_base.isra.34+0x2b/0x50 [ 240.115964] [8105c9c3] bad_area_nosemaphore+0x13/0x20 [ 240.117369] [8105cd4e] __do_page_fault+0xce/0x580 [ 240.118779] [c0805a2e] ? atom_op_move+0xbe/0x1e0 [radeon] [ 240.120188] [c07eb50a] ? cail_reg_write+0x1a/0x20 [radeon] [ 240.121562] [c0802c38] ? atom_put_dst+0x478/0x560 [radeon] [ 240.122911] [8105d231] do_page_fault+0x31/0x70 [ 240.124277] [c08614f7] ? evergreen_hdmi_setmode+0x8d7/0xbd0 [radeon] [ 240.125598] [8178bf28] page_fault+0x28/0x30 [ 240.126928] [c08614f7] ? evergreen_hdmi_setmode+0x8d7/0xbd0 [radeon] [ 240.128254] [811c2046] ? kfree+0x56/0x150 [ 240.129598] [c08614f7] evergreen_hdmi_setmode+0x8d7/0xbd0 [radeon] [ 240.130941] [c05d8cf4] ? drm_detect_hdmi_monitor+0x74/0xc0 [drm] [ 240.132290] [c0868b58] radeon_atom_encoder_mode_set+0x158/0x2d0 [radeon] [ 240.133612] [c062b966] drm_crtc_helper_set_mode+0x356/0x530 [drm_kms_helper] [ 240.134912] [c062c6db] drm_crtc_helper_set_config+0x98b/0xb10 [drm_kms_helper] [ 240.136194] [8139c971] ? idr_mark_full+0x61/0x70 [ 240.137464] [c0813d64] radeon_crtc_set_config+0x44/0x120 [radeon] [ 240.138722] [c05d06d1] drm_mode_set_config_internal+0x61/0xe0 [drm] [ 240.139978] [c05d4413] drm_mode_setcrtc+0x283/0x580
