[Kernel-packages] [Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
I saw the upstream discussion about CONFIG_SND_INTEL_BYT_PREFER_SOF here: https://github.com/thesofproject/sof/issues/3868#issuecomment-1509831655 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Groovy: Won't Fix Bug description: [Impact] There is no ucm for ASUS C300 in the 20.04 and 20.10, as a result, the audio doesn't work on this machine after installing the 20.04 or 20.10. [Fix] The ucm files for this machine are in the alsa-ucm-conf 1.2.3, cherry-pick them to ubuntu 20.04 and 20.10 [Test Case] After booting up, use speaker to play some sound, it works well, plug a headset, play sound to headphone, it basically works but has some crankling noise, it is a kernel issue for this noise. [Regression Risk] This SRU adds new ucm files, If the machine uses the audio driver of chtmax98090, it will apply this new added ucm files, there will be speaker/headphone in the UI. So the possible regression is with this SRU, users could see the audio devices in the UI but the audio doesn't work (without this SRU, users couldn't see the audio devices in the UI at all and the audio doesn't work). This possibility is low since we tested it on the ASUS C300. Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-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: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.name: Quawks dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to:
[Kernel-packages] [Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
Status for sound on Dell Chromebook 3120. On Ubuntu 22.04.2 (kernel 5.15.0-69-generic): 1. alsa-ucm-conf now seems to include the required UCM2 files. Hurrah! 2. you also need the firmware-sof-signed package, which you have to enable the "restricted" apt repository to get. Some people enable "restricted" already, when they install Ubuntu. 3. after a few minutes continuous playback the sound breaks (continuous beep). This is fixed by adding the module/boot option snd_sof.sof_debug=1, as described here: https://github.com/thesofproject/sof/issues/5437 Secondly, this system is affected by the same "after setting snd_intel_dspcfg.dsp_driver=2 the Sound is Pitched down and too slow". NOTICE: Upstream has suggested that future kernels will effectively default to "snd_intel_dspcfg.dsp_driver=2" on this hardware. I.e. the default would change from SOF to SST. If you have this "pitched down" problem, my only solution is to change back using the boot/module option "snd_intel_dspcfg.dsp_driver=3" ** Bug watch added: github.com/thesofproject/sof/issues #5437 https://github.com/thesofproject/sof/issues/5437 ** Bug watch added: github.com/thesofproject/sof/issues #3868 https://github.com/thesofproject/sof/issues/3868 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Groovy: Won't Fix Bug description: [Impact] There is no ucm for ASUS C300 in the 20.04 and 20.10, as a result, the audio doesn't work on this machine after installing the 20.04 or 20.10. [Fix] The ucm files for this machine are in the alsa-ucm-conf 1.2.3, cherry-pick them to ubuntu 20.04 and 20.10 [Test Case] After booting up, use speaker to play some sound, it works well, plug a headset, play sound to headphone, it basically works but has some crankling noise, it is a kernel issue for this noise. [Regression Risk] This SRU adds new ucm files, If the machine uses the audio driver of chtmax98090, it will apply this new added ucm files, there will be speaker/headphone in the UI. So the possible regression is with this SRU, users could see the audio devices in the UI but the audio doesn't work (without this SRU, users couldn't see the audio devices in the UI at all and the audio doesn't work). This possibility is low since we tested it on the ASUS C300. Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0
[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
I mean, use the link "Report a bug" at the top-right of this page. Not
add comments to this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
after suspend
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This upstream bug has been confirmed to affect Ubuntu users[1]. As
per the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
from system sleep. Frequency of the bug is described as once every
few days[2].
[1] E.g. this user confirms the bug & very specific workaround:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
[2] E.g. this log of crashes:
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23
This is a bug in blk-core.c. It is not specific to any one hardware
driver. Technically the suspend bug is triggered by the SCSI core -
which is used by *all SATA devices*.
The commit also includes a test which quickly and reliably proves the
existence of a horrifying bug.
I guess you might avoid this bug only if you have root on NVMe. The
other way to not hit the Xorg crash is if you don't use all your RAM,
so there's no pressure that leads to cold pages of Xorg being swapped.
Also, you won't reproduce the Xorg crash if you suspend+resume
immediately. (This frustrated my tests at one point, it only
triggered after left the system suspended over lunch :).
Fix: "block: do not use interruptible wait anywhere"
in kernel 4.17:
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428
in kernel 4.16.8:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6
lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-24.26#n856
I.e., this bug is still present in Ubuntu source package
linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details
(lspci-vnvn.log) of a system where this bug is known to happen.
Regards
Alan
WORKAROUND: Use kernel parameter:
scsi_mod.scan=sync
== Fix ==
1dc3039bc87a ("block: do not use interruptible wait anywhere")
== Regression Potential ==
Low. This patch has been sent to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
That's not enough information. At this point you should report a new
bug, please.
Notice the linked bug #1760450 includes a crash trace. (Not saying for
sure you'd be able to do the same). The fatal signal is SIGBUS, as
opposed to the usual SIGSEGV or abort. If you've got a SIGSEGV or an
abort instead, you don't have this bug.
If you do, you can link to this bug for the historical reminder. (The
analysis of these crash traces is a bit unusual).
I'd be pretty surprised if there was a regression on this. Axboe
demanded a regression test for blktests, so it can't be exactly the
same. And the cause of the bug was something pretty silly during the
transition to blk-mq... I don't know why it would get introduced
elsewhere.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
after suspend
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This upstream bug has been confirmed to affect Ubuntu users[1]. As
per the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
from system sleep. Frequency of the bug is described as once every
few days[2].
[1] E.g. this user confirms the bug & very specific workaround:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
[2] E.g. this log of crashes:
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23
This is a bug in blk-core.c. It is not specific to any one hardware
driver. Technically the suspend bug is triggered by the SCSI core -
which is used by *all SATA devices*.
The commit also includes a test which quickly and reliably proves the
existence of a horrifying bug.
I guess you might avoid this bug only if you have root on NVMe. The
other way to not hit the Xorg crash is if you don't use all your RAM,
so there's no pressure that leads to cold pages of Xorg being swapped.
Also, you won't reproduce the Xorg crash if you suspend+resume
immediately. (This frustrated my tests at one point, it only
triggered after left the system suspended over lunch :).
Fix: "block: do not use interruptible wait anywhere"
in kernel 4.17:
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428
in kernel 4.16.8:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6
lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-24.26#n856
I.e., this bug is still present in Ubuntu source package
linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details
(lspci-vnvn.log) of a system where this bug is known to happen.
Regards
Alan
WORKAROUND: Use kernel parameter:
scsi_mod.scan=sync
== Fix ==
1dc3039bc87a ("block: do not use interruptible wait anywhere")
== Regression Potential ==
Low. This patch has been sent to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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 1769819] Re: [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → nvidia_drv.so+60a46c → [heap]+d35cb0
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1769819 Title: [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → nvidia_drv.so+60a46c → [heap]+d35cb0 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: after putting the system to sleep, and waking it up, Xorg crashes, and I'm lead to a new greeter / login screen. naturally the state of my desktop is lost in this process, and I'm stuck with a new login with no apps running. the error reporter says: Error: [Errno 21] is a directory: '/proc/driver/nvidia/gpus/:01:00.0/' which is indeed true: $ ls /proc/driver/nvidia/gpus/\:01\:00.0/ information registry the same system worked fine with ubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 8 07:51:42 2018 DistUpgraded: 2018-05-04 09:38:04,874 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.13.0-39-generic, x86_64: installed nvidia, 390.48, 4.15.0-20-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GK104 [GeForce GTX 680] [10de:1180] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 680] [3842:3687] InstallationDate: Installed on 2016-04-03 (764 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=e56cb504-229d-4c7a-b16c-b259d05e992b ro noprompt quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-05-04 (3 days ago) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Mon May 7 08:48:46 2018 xserver.configfile: default xserver.logfile:
[Kernel-packages] [Bug 1769819] Re: [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → nvidia_drv.so+60a46c → [heap]+d35cb0
CurrentDmesg.txt: [58189.152330] PM: suspend exit [58189.162027] Read-error on swap-device (253:0:361608) [58189.167038] Read-error on swap-device (253:0:361672) "People die when they are killed". Specifically "Read-error on swap- device" kills you with SIGBUS. Mystery solved. I really expect if you looked at the crash, you would notice it is SIGBUS, with si_code == BUS_ADRERR (2). This means a read error when trying to load a page of virtual memory back in from swap or from the filesystem. There's a common bug which matches this, so please read #1776887 "Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend". I'm sure this applies to at least some users who marked themselves as affected, or some duplicates of this bug. This particular kernel log includes some other errors as well though, so I can't rule out that they also have some relation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1769819 Title: [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → nvidia_drv.so+60a46c → [heap]+d35cb0 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: after putting the system to sleep, and waking it up, Xorg crashes, and I'm lead to a new greeter / login screen. naturally the state of my desktop is lost in this process, and I'm stuck with a new login with no apps running. the error reporter says: Error: [Errno 21] is a directory: '/proc/driver/nvidia/gpus/:01:00.0/' which is indeed true: $ ls /proc/driver/nvidia/gpus/\:01\:00.0/ information registry the same system worked fine with ubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 8 07:51:42 2018 DistUpgraded: 2018-05-04 09:38:04,874 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.13.0-39-generic, x86_64: installed nvidia, 390.48, 4.15.0-20-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GK104 [GeForce GTX 680] [10de:1180] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 680] [3842:3687] InstallationDate: Installed on 2016-04-03 (764 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=e56cb504-229d-4c7a-b16c-b259d05e992b ro noprompt quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-05-04 (3 days ago) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To
[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Also, I can confirm Maxim Loparev's comment #12. The current -hwe
kernels in Ubuntu 16.04 "Xenial" are also missing this critical kernel
fix. Please can you either update the list of affected Ubuntu versions,
or let us know if the bug needs reporting separately?
Link to HEAD source: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/xenial/tree/block/blk-core.c?h=hwe#n856
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
after suspend
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This upstream bug has been confirmed to affect Ubuntu users[1]. As
per the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
from system sleep. Frequency of the bug is described as once every
few days[2].
[1] E.g. this user confirms the bug & very specific workaround:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
[2] E.g. this log of crashes:
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23
This is a bug in blk-core.c. It is not specific to any one hardware
driver. Technically the suspend bug is triggered by the SCSI core -
which is used by *all SATA devices*.
The commit also includes a test which quickly and reliably proves the
existence of a horrifying bug.
I guess you might avoid this bug only if you have root on NVMe. The
other way to not hit the Xorg crash is if you don't use all your RAM,
so there's no pressure that leads to cold pages of Xorg being swapped.
Also, you won't reproduce the Xorg crash if you suspend+resume
immediately. (This frustrated my tests at one point, it only
triggered after left the system suspended over lunch :).
Fix: "block: do not use interruptible wait anywhere"
in kernel 4.17:
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428
in kernel 4.16.8:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6
lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-24.26#n856
I.e., this bug is still present in Ubuntu source package
linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details
(lspci-vnvn.log) of a system where this bug is known to happen.
Regards
Alan
WORKAROUND: Use kernel parameter:
scsi_mod.scan=sync
== Fix ==
1dc3039bc87a ("block: do not use interruptible wait anywhere")
== Regression Potential ==
Low. This patch has been sent to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
I don't see it! The changelog doesn't include this fix
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887
the fix never reached the GIT tree to start with, unless it was force-
pushed away when I wasn't looking? The interruptible wait remains
present in blk-core.c.
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-29.31#n856
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
after suspend
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This upstream bug has been confirmed to affect Ubuntu users[1]. As
per the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
from system sleep. Frequency of the bug is described as once every
few days[2].
[1] E.g. this user confirms the bug & very specific workaround:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
[2] E.g. this log of crashes:
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23
This is a bug in blk-core.c. It is not specific to any one hardware
driver. Technically the suspend bug is triggered by the SCSI core -
which is used by *all SATA devices*.
The commit also includes a test which quickly and reliably proves the
existence of a horrifying bug.
I guess you might avoid this bug only if you have root on NVMe. The
other way to not hit the Xorg crash is if you don't use all your RAM,
so there's no pressure that leads to cold pages of Xorg being swapped.
Also, you won't reproduce the Xorg crash if you suspend+resume
immediately. (This frustrated my tests at one point, it only
triggered after left the system suspended over lunch :).
Fix: "block: do not use interruptible wait anywhere"
in kernel 4.17:
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428
in kernel 4.16.8:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6
lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-24.26#n856
I.e., this bug is still present in Ubuntu source package
linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details
(lspci-vnvn.log) of a system where this bug is known to happen.
Regards
Alan
WORKAROUND: Use kernel parameter:
scsi_mod.scan=sync
== Fix ==
1dc3039bc87a ("block: do not use interruptible wait anywhere")
== Regression Potential ==
Low. This patch has been sent to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Is there an estimate for when users will receive the SRU? (Which was
submitted on 2018-06-29). So far I've seen 8 separate questions on
askubuntu.com which match this bug. Poke :-).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
after suspend
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
This upstream bug has been confirmed to affect Ubuntu users[1]. As
per the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
from system sleep. Frequency of the bug is described as once every
few days[2].
[1] E.g. this user confirms the bug & very specific workaround:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
[2] E.g. this log of crashes:
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23
This is a bug in blk-core.c. It is not specific to any one hardware
driver. Technically the suspend bug is triggered by the SCSI core -
which is used by *all SATA devices*.
The commit also includes a test which quickly and reliably proves the
existence of a horrifying bug.
I guess you might avoid this bug only if you have root on NVMe. The
other way to not hit the Xorg crash is if you don't use all your RAM,
so there's no pressure that leads to cold pages of Xorg being swapped.
Also, you won't reproduce the Xorg crash if you suspend+resume
immediately. (This frustrated my tests at one point, it only
triggered after left the system suspended over lunch :).
Fix: "block: do not use interruptible wait anywhere"
in kernel 4.17:
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428
in kernel 4.16.8:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6
lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-24.26#n856
I.e., this bug is still present in Ubuntu source package
linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details
(lspci-vnvn.log) of a system where this bug is known to happen.
Regards
Alan
WORKAROUND: Use kernel parameter:
scsi_mod.scan=sync
== Fix ==
1dc3039bc87a ("block: do not use interruptible wait anywhere")
== Regression Potential ==
Low. This patch has been sent to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Awesome. Thanks. I can't test suspend in a VM, and I don't have a physical Ubuntu install. The block developers arranged a more convenient test for the underlying issue in https://github.com/osandov/blktests/ Before (i.e. linux-image-4.15.0-23-generic): $ sudo ./check block/016 block/016 (send a signal to a process waiting on a frozen queue) block/016 (send a signal to a process waiting on a frozen queue) [failed] runtime ... 8.112s --- tests/block/016.out 2018-06-15 10:05:09.080764871 +0100 +++ results/nodev/block/016.out.bad 2018-06-15 10:05:27.236769759 +0100 @@ -1,2 +1,3 @@ Running block/016 +dd: error reading '/dev/nullb0': Input/output error Test complete After (i.e. 4.15.0-23.26~lp1776887): $ sudo ./check block/016 block/016 (send a signal to a process waiting on a frozen queue) [passed] runtime 8.112s ... 10.086s $ I don't see any problem with the patched VM, though obviously it would be nice to have someone test both normal suspend and the pm_test reproducer on a physical install. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk- core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan WORKAROUND: Use kernel parameter: scsi_mod.scan=sync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Sorry, it's not convenient for me to test Ubuntu at the moment. I abuse the above instructions to assert that this bug is confirmed, citing the URLs provided. (1: The patch+description linked for kernel 4.17, 2: the lack of fix evidenced in the link for kernel 4.15.0-24.26). I appeal to authority based on me being the author of the fix, which was merged to the Linux kernel :). Furthermore, I do so on behalf of two Ubuntu users active on Ubuntu bug linked above.[1] In the first instance, I analysed the crash dump and explained the very distinct signature which it shows, indicating this bug. The second user confirmed that they suffered this bug and used a very specific workaround to avoid it. [1] https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/ (The Ubuntu bug is marked as affecting 7 people overall. I am certain this is an understatement. I mentioned in my comment in the bug, how the nature of the crashes made them hard for users to identify. One part is the same as the experience we had in Fedora. Automatically reported crashes were not reliably detected as duplicates, because the fatal SIGBUS signal can happen at a number of different points). ** 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/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend Status in linux package in Ubuntu: Confirmed Bug description: This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk- core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
** Patch added: "A copy of the original patch that was merged upstream" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+attachment/5152516/+files/0001-block-do-not-use-interruptible-wait-anywhere.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend Status in linux package in Ubuntu: New Bug description: This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk- core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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 1776887] [NEW] Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Public bug reported: This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable /linux- stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk- core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1776887/+attachment/5152515/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend Status in linux package in Ubuntu: New Bug description: This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk- core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
hackeron, search for "intel_idle.max_cstate=1" in relation to this hardware; it's a workaround for random freezes which (some) people are encountering. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) Status in linux package in Ubuntu: Expired Bug description: I have an Intel NUC NUC5CPYH. This is the unit: http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5cpyh.html It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux- image-3.19.0-34-generic -- but when I try to boot with linux- image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio - Tried selecting "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from the list, it does not boot into the recovery console either :( - I tried installing a clean 15.10 version on a blank hard drive (with debootstrap so latest packages) I am able to boot if I add systemd.unit=emergency.target to the kernel line. I can run "systemctl start networking" for example and it works, but if I run "systemctl start apport" (or ssh even) - I see this and the system freezes: https://www.dropbox.com/s/gmpse7bx0c70e4v/IMG_1479.jpg?dl=0 I am not sure how to troubleshoot further. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog or journalctl from the failed boot :( Any suggestions? - EDIT: It seems downgrading from the latest PY0044 BIOS version to PY0043 allows me to boot the system, but it freezes if running "reboot" - more details in this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+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 1062796] Re: usb-storage devices don't work, unless plugged in *after* booting - happens when setting MODULES=dep in initramfs.conf
Interesting tags.
Which upstream needs testing exactly? Do you want the latest mainline
kernel tested with CONFIG_USB_LIBUSUAL and MODULES=dep in
initramfs.conf? That would be very easy for me to do (on kubuntu
12.04).
That said it looks like libusual was removed in v3.7. At least
usb/storage/libusual.c was. I have a suspicion the only reason for it,
Low Performance USB Block driver as above, was removed at some point.
I guess you're also calling the BIOS outdated. It was upgraded at the
time of purchase, which was indeed 2012-10. In case you're tempted to
ask (?!), I'm not going to update 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/1062796
Title:
usb-storage devices don't work, unless plugged in *after* booting -
happens when setting MODULES=dep in initramfs.conf
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Hopefully I have time to root-cause this.
We have two Kubuntu 12.04 LTS machines. One of them has a USB card
reader, which we want to leave permanently attached. We use it to
upload photos to Digikam several times a month.
Recently we noticed the card reader not working. It showed up in
lsusb, BUT ls /dev/sd* showed only one device (the internal hard
drive). Unplugging the entire card reader and plugging it back in
again fixes it.
Today, I confirmed that modprobe usb-storage fixed it without re-
plugging the cardreader.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-31-generic 3.2.0-31.50
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: VT1708S Analog [VT1708S Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alan 2413 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c1 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:11060397,10438415,0010
HDA:80862806,80860101,0010'
Controls : 48
Simple ctrls : 23
Date: Sat Oct 6 12:27:35 2012
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic
root=UUID=a6efc5b5-c8c5-4ae1-9970-61943a7f9396 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-31-generic N/A
linux-backports-modules-3.2.0-31-generic N/A
linux-firmware1.79.1
RfKill:
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0703
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B75-M LE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd08/24/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1062796/+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 1173725] Re: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor
That is, I'm hoping the brightness keys will work (e.g. under KDE) when using the commit ACPI / video / i915: No ACPI backlight if firmware expects Windows 8. With the non-working acpi_backlight removed, KDE would use the working intel_backlight 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/1173725 Title: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor Status in “linux” package in Ubuntu: Incomplete Bug description: The boot parameter is suggested as a fix for this model by http://www.linlap.com/acer_aspire_v5-171 (so if it would help, I would suggest classing this bug as confirmed). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1919 F pulseaudio Date: Sat Apr 27 19:59:23 2013 InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer V5-171 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic.efi.signed root=UUID=ad03cbd3-39e0-4f7e-b0ab-e1ef3abaa88e ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnV5-171:pvrV2.04:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04: dmi.product.name: V5-171 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173725/+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 1173725] Re: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor
Sorry I've been neglecting this (and my original report may have fluffed the detail). This is Windows 8 hardware. Manually poking the intel_backlight driver in sysfs (echo 100 | sudo tee /sys/class/intel_backlight/brightness) works fine. So for now I'm assuming the problem is what's referred to here: http://permalink.gmane.org/gmane.linux.kernel.commits.head/396675 (I first saw this referred to when it was reverted in 3.11-rc3. Linus' release announcement says But never fear, we have top people looking at it). That should be nice easy to test compared to the _other_ bug I'm tracking on this laptop. So I'll see if I can get there feedback to upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1173725 Title: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor Status in “linux” package in Ubuntu: Incomplete Bug description: The boot parameter is suggested as a fix for this model by http://www.linlap.com/acer_aspire_v5-171 (so if it would help, I would suggest classing this bug as confirmed). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1919 F pulseaudio Date: Sat Apr 27 19:59:23 2013 InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer V5-171 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic.efi.signed root=UUID=ad03cbd3-39e0-4f7e-b0ab-e1ef3abaa88e ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnV5-171:pvrV2.04:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04: dmi.product.name: V5-171 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173725/+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 1173725] Re: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor
** Bug watch added: Linux Kernel Bug Tracker #51231 http://bugzilla.kernel.org/show_bug.cgi?id=51231 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=51231 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1173725 Title: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: The boot parameter is suggested as a fix for this model by http://www.linlap.com/acer_aspire_v5-171 (so if it would help, I would suggest classing this bug as confirmed). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1919 F pulseaudio Date: Sat Apr 27 19:59:23 2013 InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer V5-171 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic.efi.signed root=UUID=ad03cbd3-39e0-4f7e-b0ab-e1ef3abaa88e ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnV5-171:pvrV2.04:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04: dmi.product.name: V5-171 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1173725/+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 1173725] Re: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor
Sorry, I don't think the backlight problem on the V5-171 is a regression. I've never had it work as expected. I've now tried the acpi_osi=!Windows 2012 test, to see if this machine could be added to the temporary blacklist. I.e. whether my bug was a regression caused when Linux added the Windows 2012 OSI string.[1] Unfortunately that boot option didn't help. [1] https://bugzilla.kernel.org/show_bug.cgi?id=51231#c137 The result from testing v3.11-rc2 is that it does fix the problem. And as expected, the revert in v3.11-rc3 breaks it again. To answer the question about firmware upgrades, I'm not going to try that unless it helps upstream. It's not worth reflashing at my own risk just to avoid passing acpi_backlight=vendor. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1173725 Title: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: The boot parameter is suggested as a fix for this model by http://www.linlap.com/acer_aspire_v5-171 (so if it would help, I would suggest classing this bug as confirmed). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1919 F pulseaudio Date: Sat Apr 27 19:59:23 2013 InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer V5-171 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic.efi.signed root=UUID=ad03cbd3-39e0-4f7e-b0ab-e1ef3abaa88e ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnV5-171:pvrV2.04:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04: dmi.product.name: V5-171 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1173725/+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
