Public bug reported:
[RELEASE VERSION]
Description:Ubuntu 18.04.3 LTS
Release:18.04
[PACKAGE VERSION]
linux-oem:
Installed: 4.15.0.1057.61
Candidate: 4.15.0.1057.61
Version table:
*** 4.15.0.1057.61 500
500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64
** Summary changed:
- i915: Display flickers during "flickerfree" boot (BIOS logo on a black
background)
+ i915: Display flickers (monitor loses signal briefly) during "flickerfree"
boot, while showing the BIOS logo on a black background
--
You received this bug notification because you are a
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850668
Title:
Kernel repeatedly logs "ima:
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849917
Title:
[iwlwifi] Repeated kernel
** Summary changed:
- No conozco el error
+ Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
We have a bug to track the enabling of v3d.ko
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
DRM_V3D.
In fact the DRM_V3D is crucial for graphical applications (such as
ubuntu-desktop :) as it removes the graphical overhead from the cpu to
the gpu, making the applications work much faster.
Please
You have been subscribed to a public bug:
NO se que le pasa
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
** Summary changed:
- CONFIG_KVM is disabled for linux-raspi2 (aarch64)
+ CONFIG_KVM is disabled for linux-raspi2 (aarch64 and armhf)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
** Summary changed:
- [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI
stuttering
+ [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI
stuttering in kernel 5.3 (but 5.0 has no problem)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
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
I have the same problem with my custom install, inherited and upgraded
from my Ubuntu 19.04 system. After each boot I run a small script to
export and import my three pools again. zsys is not installed anymore on
this manual install from early 2019. The system worked without problems
on Ubuntu
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Hello,
Apologies for a newbie question. Is there a scheduled release date for
the upgrade/update at ubuntu-19.10-preinstalled-server-arm64+raspi3.img?
Just need to get my ducks in a row by suspending work on the current
image with respect to items other than the total_mem issue. Thanks.
Kind
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** Changed in: linux (Ubuntu Xenial)
Assignee:
Could this be related?
[620533.9804061 RBP: R08: 0001 R09:
7f901480 [620533.981792] R10: 7f9014de0270 R11: 0206
R12: 7f90477fdlfe [620533.983039] R13: 7f90477fdlff R14:
7f901700 R15: 7f901fffe540 [620541.767819] watchdog:
** No longer affects: gcc-9 (Ubuntu)
** No longer affects: gcc-9 (Ubuntu Eoan)
** No longer affects: gcc-9 (Ubuntu Focal)
** No longer affects: linux (Ubuntu Focal)
** No longer affects: linux (Ubuntu Eoan)
** No longer affects: linux (Ubuntu)
--
You received this bug notification because
Public bug reported:
On Ubuntu 18.04
linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
According to https://www.mail-archive.com/ceph-
us...@ceph.io/msg00940.html the same happens on Disco with this kernel
version.
Processes that read data from CephFS get stuck, the system becomes
You have been subscribed to a public bug:
On Ubuntu 18.04
linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
According to https://www.mail-archive.com/ceph-
us...@ceph.io/msg00940.html the same happens on Disco with this kernel
version.
Processes that read data from CephFS get stuck,
I don't know if my problem is related specifically to the Realtek AC256
codec. In any case, it seems FreeBSD folk fixed a while back the same
issue: no headphone output through some patches related to this codec on
some Dell models.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219350
There is some reported regressions in autopkgtests for ppc64el and s390x, I'm
investigating.
Cheers,
Guilherme
--
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/1681909
Title:
Retested with Bionic-proposed version (1:1.6.5-1ubuntu1~18.04.3) and
Disco-proposed (1:1.6.5-1ubuntu1.3), both including the fix for this
bug.
All working fine. I've used the "droppkt" hack (see comment #24) to
simulate the problem, and it's fixed in the -proposed version.
Thanks,
Guilherme
**
kdump-tools requires a kernel to be loaded by kexec -p to work. There is
no workaround on that. If your /boot/ does not contain a kernel, it
could possibly use a kernel from somewhere else, but you would still
need a kernel.
There is a pending patch that I have in the works that would postpone
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Here's a fresh one:
Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: Microcode SW error
detected. Restarting 0x0.
Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: Status: 0x0040, count:
6
Oct 31 19:35:40
Just to give more insight about this, I just tried a live USB with
18.04.03 and the results are similar: the sound is extremely low, but
with no distortion whatsoever.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This is my replacement "minimized" losetup.c that exhibits the problem.
Simply, drop this into klibc sources
and run:
./debian/rules build; sudo ./usr/utils/static/losetup
1 Argc before find_unused_loop_devices()
0 Argc after find_unused_loop_devices()
Argc values before and after did not match.
https://lists.ubuntu.com/archives/kernel-team/2019-October/105157.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1850675
Title:
ARM CPU support update
Status in linux-aws
I've verified this bug using the following procedure:
a) For all the required series, download the "debian-installer" source package
and all of its build dependencies;
b) Modify the build/config/amd64.cfg to use the -proposed version of the kernel
for the series you're verifying;
c) Run make
This bug was fixed in the package klibc - 2.0.7-1ubuntu1
---
klibc (2.0.7-1ubuntu1) focal; urgency=low
* Merge from Debian unstable. Remaining changes:
* Fix FTBFS on eoan and later with new gcc
- cf-protection.patch: Disable cf-protection for syscalls stub.
*
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-390/20191030_143354_e7fac@/log.gz
** Affects:
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-435/20191030_151840_5f268@/log.gz
** Affects:
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => In Progress
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Tags added: 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/1850184
Title:
losetup -f broken in 2.0.6-1ubuntu2
Status in gcc-9 package in Ubuntu:
New
Status in klibc package
@Tom Sounds like a winner to me! I've submitted the patch to our process
pipeline:
https://lists.ubuntu.com/archives/kernel-team/2019-October/105155.html
A post will appear here once it lands in a production Bionic kernel
(most likely in our next three-week cycle, around 18-Nov).
Thanks again
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301819/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301822/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301816/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301820/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Attaching logs from a reproduction, occured at 10:09:50 localtime in the
journal on the computer.
** 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.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301818/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301817/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301815/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301813/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301821/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301810/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301814/+files/Lspci.txt
--
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/1850443
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301811/+files/CRDA.txt
--
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/1850443
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb3553 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2018-06-18 (500 days ago)
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301812/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Ah-ha. If loop0 is in use, then the test-case appropriately fails in
both unstable and eoan, which is comforting, as I didn't look forward to
figuring out why this works in Debian (it doesn't).
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Description changed:
[Impact]
- * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as
main(argc) is reset to zero, after ioctl() operations in a function call, quite
unexpectadly.
-
+ * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt,
+ as
Today I noticed when I start my system with the other kernel
5.0.0-32-generic #34-Ubuntu there are no problem regarding the mouse
movement (WiFi was activated)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The testcase here doesn't seem to be working (or, rather, failing) for
me, which makes it harder to investigate this. It passes on both sid
and eoan for me:
(sid-amd64)root@nosferatu:~# dpkg -l \*klibc\*
Desired=Unknown/Install/Remove/Purge/Hold
|
--- Comment From kuldip.na...@ibm.com 2019-10-31 10:20 EDT---
I thought a lot about it and I think this problem will come in any time the m/c
is network booted and diskless. So in a way it is still generic and not IBM
specific.
Based on this I now have second thought on if we should
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I have tried the v3d.ko with latest stable version of mesa
19.2
Which works well. glxinfo is the application to show everything is working and
it produces
...Accelerated: yes
for a fast
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1845716
Title:
package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to
install/upgrade: installed
--- Comment From kuldip.na...@ibm.com 2019-10-31 10:11 EDT---
This problem will be seen ion any of the diskless workstation;
Please note as I see there are three places which are of concern
/var/lib/dpkg/info/kdump-tools.postinst fails because:
1. It cannot make the initrd image because
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug:
It is done. Do my bug will be treated on this platform ?
--
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/1843644
Title:
touchpad not working on LHMZNIY Yepbook
Status in linux package
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Summary changed:
- linux-oem: -proposed tracker
+ bionic/linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated
** Description changed:
+ [Impact]
+
+ * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as
main(argc) is reset to zero, after ioctl() operations in a function call, quite
unexpectadly.
+
+ [Test Case]
+
+ * sudo /usr/lib/klibc/bin/losetup -vf
+
+should not
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 1850184
and then change the status of the bug to 'Confirmed'.
If, due to the
--- Comment From kuldip.na...@ibm.com 2019-10-31 10:05 EDT---
Hi,
Please see the detail information below
root@pok1-qz1-sr1-rk005-s10:~# mount | sed -e 's/^//g'
/proc on /proc type proc (rw,relatime)
/sys on /sys type sysfs
** Changed in: linux-raspi2 (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1783961
Title:
CONFIG_KVM is
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Patch added: "save-argc.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850184/+attachment/5301773/+files/save-argc.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
So, I'm not sure if this is a kernel headers/assembly bug (as ioctl is
used from there), gcc-9 bug, or the combination of the two.
I'm going to save argc, and use a saved copy for now, but this needs
deeper analysis. This sounds like a retpoline mitigation.
** Also affects: klibc (Ubuntu Focal)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
*** This bug is a duplicate of bug 1849002 ***
https://bugs.launchpad.net/bugs/1849002
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
@Kamal yes this seems to fix it. I was able to run my device stress
test for over 15 minutes. With the bug I was lucky if I could make it
15 seconds.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Also seeing this downstream in Pop!_OS. Here is a dkms build log using
kernel package 5.3.0-20:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.3.0-20-generic (x86_64)
Thu Oct 31 06:46:36 CDT 2019
make: Entering directory '/usr/src/linux-headers-5.3.0-20-generic'
CFG80211 API is prefered
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
[3.762069] i2c_hid i2c-SYNA3602:00: DEBUG!: i2c_acpi_get_irq:
acpi_dev_get_resources() = 0, irq = -2
This means the acpi_dev_get_resources() in i2c_acpi_get_irq() doesn't
get a valid IRQ.
Please file an upstream bug at https://bugzilla.kernel.org/
Product: ACPI
Component: Config-Interrupts
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
Public bug reported:
Hi,
I had a bug every now and then with the Nvidia proprietary driver 435
(installed via the "additionals proprietary drivers" GUI) where I try to
suspend my laptop, and the system freezes.
It happens from time to time, but so far, I have this issue quite
frequently, as I'm
Indeed, I forgot to upgrade so I missed the issue. Now that I did I see
the hiss is indeed much louder. Thanks Kai for sending this upstream
already.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've fixed my problem by applying the kernel suggested in [1]
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850769
Title:
package
1 - 100 of 133 matches
Mail list logo
