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.launch
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 "
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 m
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
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
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
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.
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.launch
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
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
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 authorit
** 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
Pack
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
da
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
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/
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 "Wind
** 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 K
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
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 b
19 matches
Mail list logo
