@Vedran,
I still doubt the nvidia graphic driver make the system hang. you could
do a test: disable the nvidia graphic card from BIOS, only uses the
Integrated intel graphic card. then test if it still hang or not.
If that doesn't help. need to test with other kernel versions like
I tried kernel 5.8 and latest firmware or try change QCA6174 with
kvalo's firmware [1] and re-modprobe in a live CD, however, it's still
broken like above.
[1] https://github.com/kvalo/ath10k-firmware
** Changed in: linux-firmware (Ubuntu)
Status: Expired => Confirmed
--
You received
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1893052
and then change the status of the bug to 'Confirmed'.
If, due to the
--- Comment From heinz-werner_se...@de.ibm.com 2020-08-26 09:51 EDT---
IBM Bugzilla status-> closed -> Documented
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1875826
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888332
Title:
[Potential Regression]
@Hui Wang #31
No. The system will freeze ONLY WITHOUT dmic_detect=0.
--
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/1892714
Title:
Microphone not working on HP Omen 17
Status in linux
Public bug reported:
The F1 and F4 LEDs are not working when a USB-C headset is plugged in.
The LEDs work correctly for internal devices and when using the bantam
jack. This is on 20.04 LTS release.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received
--- Comment From heinz-werner_se...@de.ibm.com 2020-08-26 09:11 EDT---
@Canonical, any update available? Many thx
--
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/1886814
Title:
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Focal)
Importance: High => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1887674
and then change the status of the bug to 'Confirmed'.
If, due to the
About the uninstall the retask, just remove the kernel modules of
patch=...
snd_hda_intel: patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-
retask.fw,hda-jack-retask.fw
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** 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/1861554
Title:
Radeon mobility HD3450 (RV620) heavy screen flickering
I can control the brightness (with step up or down) using these
commands:
gdbus call --session --dest org.gnome.SettingsDaemon.Power --object-path
/org/gnome/SettingsDaemon/Power --method
org.gnome.SettingsDaemon.Power.Screen.StepUp
gdbus call --session --dest org.gnome.SettingsDaemon.Power
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
This command don't cause screen freeze:
echo 500 > /sys/class/backlight/intel_backlight/brightness
--
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/1891032
Title:
Brightness key freeze
These 3 cause screen freeze
1. sudo acpidbg -b "e EV5 1 0" ("2 0" for brightness down)
2. sudo acpidbg -b "e \_SB.PCI0.GFX0.BRT6 1 0" ("2 0" for brightness down)
3. sudo acpidbg -b "notify \_SB.PCI0.GFX0.LCD 0x86" (0x86 for brightness down)
And these 2 don't work (tee:
Do you mean the system will freeze even you add dmic_detect=0? I thought
the system only freezes without dmic_detect=0.
--
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/1892714
Title:
@Hui Wang
When you say:
> uninstall the workaround of retasking codec pin ([ 2.997562] snd_hda_intel
> :01:00.1: Applying patch firmware 'hda-jack-retask.fw')
Did I includ this by installing the "hdajackretask" package (I think I
installed it, and that it wasn't installed by default, but
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-restricted-modules (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Kernel SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2020-August/thread.html#113008
Updating status to 'In Progress'.
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed
Just to make it clear #27 is done without any modifications on top of
the original post, that is:
"alsa-ucm-conf/focal-updates,focal-updates,now 1.2.2-1ubuntu0.1 all"
was already installed (with and without dmic_detect=0).
Both the freezing and the second attempts I mentioned in #27 are done
So far I have no idea why the system crashes or hangs.
Could you please test the 5.6.0-oem kernel like 1021 or 1022. remove the
dmic_detect=0 to see if this kernel is better than 5.4.0-42 kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is
@colin-king with or without additional measurements default to
performance and relying on userspace to switch to ondemand at some later
point during boot is wrong. It means we are risking melting laptops and
catching fire. I.e. boot machine, walk away, it sits in the initrd at
the LUKS unlock
@julian Ubuntu Desktop in 20.04.2 will receive the 20.10's kernel by
default and thus will adopt the 20.10 default. Imho the linux-generic
(ga) kernel should also be updated to the same default, to make it the
same across -generic, -hwe, -oem kernel flavours in 20.04. Because in
20.04, defaulting
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1021.21+20.10.2
---
linux-oem-5.6 (5.6.0-1021.21+20.10.2) groovy; urgency=medium
* dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] autoreconstruct -- manage executable debian files
linux-oem-5.6
This issue seems to have been fixed as of 5.8.3 kernel.
I recently reported this upstream
https://bugzilla.kernel.org/show_bug.cgi?id=208841 and after I was asked
to re-test with the newer kernel, it turned out the problem no longer
reproducible. I figured I should search if there were other
I now booted with and without "options snd-hda-intel dmic_detect=0". The
first boot attempt froze the screen, and in the second the mic was
working, but after 3-4 min the audio system "crashed". The Settings show
https://pasteboard.co/Jo955xN.png . And in both cases I do see:
~$ apt list
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=209043.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
finaly I can use screenpad as a display with NVIDIA-proprietary driver.
- Edit /usr/share/X11/xorg.conf.d/10-nvidia.conf
- Add the following to the Section:
Option "ModeValidation"
** Tags added: sru-20200810
--
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/1867570
Title:
reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on
ppc64le
Status in
The internal microphone IS WORKING without "options snd-hda-intel
dmic_detect=0". But without this option the system DOES freeze.
The freeze is basically the same as described in comment #29 in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874698
(Would be strange if the graphics is
Thanks Julian, I'd like to find range of recent kit and do a full
analysis. I fear that what ever the default, it will be suboptimal for
some configurations.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
For example, the measurements on the X220 do not reflect situation on
modern Intel systems, as they scale differently from Skylake and newer,
as they do not have HWP.
A CPU with HWP (hardware P-states) behaves as you'd expect sort of - it
runs at close to max frequency all the time, and scales
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893027
Title:
[UBUNTU 20.04] lscpumf display raw event number incorrectly
Why are we looking at focal now? The change to systemd only happened
after the opening of groovy.
Data is tricky. There are a ton of different cpufreq drivers that are
affected, and they all have different behavior. pstates alone has
different behavior on newer intels that do pstates in hardware
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * There is a zPCI attach/detach issue in combination with PF/VF linking
+ support.
+
+ * On IBM Z with zPCI, VFs can be enabled/disabled individually with
+ /sys/bus/pci/slots//power.
+
+ * If this was done
Default Comment by Bridge
** Attachment added: "Fix wrong output of lscpumf when device cpum_cf has
different type than 4"
https://bugs.launchpad.net/bugs/1893027/+attachment/5404698/+files/0001-cpumf-lscpumf.pl-displays-raw-event-number-incorrect.patch
** Changed in: ubuntu
Assignee:
You have been subscribed to a public bug:
Fix wrong output of lscpumf when device cpum_cf has different type than
4
Please apply to ubuntu 20.04 (s390-tools version 2.12)
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Test passed with 5.4.0-44.48
Closing this bug.
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Released
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
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/1893024
Title:
failing ftrace self tests from 5.7+
Public bug reported:
Ftrace regression tests in tools/testing/selftests/ftrace are picking up
regressions in 5.7+ - not sure if these are kernel regressions or bugs
in ftrace selftests.
I'm seeing the following ftrace test regresions:
5.9-rc2 test failures with ARM64 in a 4GM VM + 8 CPUs
Test
Hi Tim,
good to have this sorted out.
In this case please follow the guidance and questions I have put into comment
#2 and let us know the results.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Is this issue associated with the Xenial GA (4.4) kernel or the Xenial
HWE (4.15) kernel?
** Changed in: ubuntu-power-systems
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Patricia Domingues (patriciasd)
** Changed in: ubuntu-power-systems
Status: Triaged
--- Comment From heinz-werner_se...@de.ibm.com 2020-08-26 05:19 EDT---
Verified ok for focal:
root@t35lp46:~# uname -a
Linux t35lp46 5.4.0-44-generic #48 SMP Tue Aug 25 12:53:01 UTC 2020 s390x s390x
s390x GNU/Linux
root@t35lp46:~# ll /sys/devices/cpum_cf/events/| fgrep DFLT
-r--r--r-- 1
--- Comment From niklas.schne...@ibm.com 2020-08-26 04:59 EDT---
(In reply to comment #8)
> I made builds of patched focal (master-next) kernel packages available here
> for further testing:
> https://people.canonical.com/~fheimes/lp1891437+lp1892849/
I've tested this build as KVM host
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux-signed - 5.8.0-16.17
---
linux-signed (5.8.0-16.17) groovy; urgency=medium
* Master version: 5.8.0-16.17
linux-signed (5.8.0-15.16) groovy; urgency=medium
* Master version: 5.8.0-15.16
linux-signed (5.8.0-14.15) groovy; urgency=medium
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
** Tags added: sru-20200810
--
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/1846297
Title:
generic/440 from ubuntu_xfstests_ext4 failed on D/F
Status in ubuntu-kernel-tests:
New
** Tags added: sru-20200810
--
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/1846298
Title:
generic/435 from ubuntu_xfstests_ext4 failed on D/F
Status in ubuntu-kernel-tests:
New
** Tags added: sru-20200810
--
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/1846302
Title:
generic/419 from ubuntu_xfstests_ext4 failed on D/F
Status in ubuntu-kernel-tests:
New
** Tags added: sru-20200810
--
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/1846301
Title:
generic/429 from ubuntu_xfstests_ext4 failed on D/F
Status in ubuntu-kernel-tests:
New
** Tags added: sru-20200810
--
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/1846303
Title:
generic/399 from ubuntu_xfstests_ext4 failed on D/F
Status in ubuntu-kernel-tests:
New
** Tags added: sru-20200810
--
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/1846304
Title:
generic/398 from ubuntu_xfstests_ext4 failed on D/F
Status in ubuntu-kernel-tests:
New
** Tags added: sru-20200810
--
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/1846308
Title:
generic/228 from ubuntu_xfstests_btrfs / ext4 / xfs failed on B/D/F
Status in
** Summary changed:
- generic/394 from ubuntu_xfstests_btrfs / ext4 / xfs failed on B/D
+ generic/394 from ubuntu_xfstests_btrfs / ext4 / xfs failed on B/D/F
** Tags added: sru-20200810
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags added: sru-20200810
--
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/1846305
Title:
generic/397 from ubuntu_xfstests_ext4 failed
Status in ubuntu-kernel-tests:
New
Status in
** Tags added: sru-20200810
--
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/1878356
Title:
generic/001 from ubuntu_xfstests_btrfs / ext4 / xfs failed on F
Status in ubuntu-kernel-tests:
ping
--
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/1881888
Title:
Atheros AR3012 BluetoothBluetooth [04ca:300b] Always Disconnected
After Suspend
Status in linux package in
On 5.4 the error message is a bit different:
# selftests: memory-hotplug: mem-on-off-test.sh
# Warning: file mem-on-off-test.sh is not executable, correct this.
not ok 1 selftests: memory-hotplug: mem-on-off-test.sh
--
You received this bug notification because you are a member of Kernel
Issue spotted on F-5.4 ARM64 (there is no such issue on amd64 / PowerPC
/s390x)
** Summary changed:
- [Potential Regression] memory-hotplug test from ubuntu_kernel_selftests
failed on X-4.15 / B-4.15 ARM64
+ [Potential Regression] memory-hotplug test from ubuntu_kernel_selftests
failed on
Public bug reported:
this bug is for tracking purpose.
** Affects: alsa-ucm-conf (Ubuntu)
Importance: High
Assignee: Hui Wang (hui.wang)
Status: New
** Affects: alsa-ucm-conf (Ubuntu Focal)
Importance: High
Assignee: Hui Wang (hui.wang)
Status: New
**
Public bug reported:
This bug is for tracking purpose.
** Affects: alsa-ucm-conf (Ubuntu)
Importance: High
Assignee: Hui Wang (hui.wang)
Status: New
** Affects: alsa-ucm-conf (Ubuntu Focal)
Importance: High
Assignee: Hui Wang (hui.wang)
Status: New
**
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1391
https://gitlab.gnome.org/GNOME/mutter/-/issues/1391
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1391
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc2/amd64/
Particularly,
commit b292b50b0efcc7095d8bf15505fba6909bb35dce
Author: Tetsuo Handa
Date: Mon Jul 13 11:12:54 2020 +0900
driver core: Fix probe_count imbalance in really_probe()
Lenovo release new version BIOS for Legion R7000 or Legion 5-15ARH05.
2020/8/20
BIOS Version: EUCN22WW,
EC Version: EUEC22WW
EUCN22WW:
BIOS Notification:
1. Fixed
1) Fix panel brightness almost not changed when change from the level 0 to
level 1.
2. Add
1) None.
3. Modified
1)
** Tags removed: verification-needed-bionic verification-needed-eoan
** Tags added: verification-done-bionic verification-done-eoan
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Kernel
101 - 200 of 205 matches
Mail list logo
