This bug was fixed in the package linux - 5.4.0-169.187
---
linux (5.4.0-169.187) focal; urgency=medium
* focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)
* USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core:
This bug was fixed in the package linux-azure - 5.15.0-1053.61
---
linux-azure (5.15.0-1053.61) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1053.61 -proposed tracker (LP: #2041565)
* Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
*
This bug was fixed in the package linux-raspi - 5.15.0-1044.47
---
linux-raspi (5.15.0-1044.47) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1044.47 -proposed tracker (LP: #2041598)
* [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to
This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to
** Changed in: linux-azure (Ubuntu Jammy)
Status: Confirmed => Fix Committed
** Changed in: linux-azure (Ubuntu Lunar)
Status: Confirmed => Fix Committed
** Changed in: linux-azure (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
This bug was fixed in the package linux-bluefield - 5.4.0-1076.82
---
linux-bluefield (5.4.0-1076.82) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1076.82 -proposed tracker (LP:
#2041621)
* pwr-mlxbf: Several bug fixes for focal (LP: #2041996)
- SAUCE: Fix race
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug was fixed in the package linux - 5.4.0-169.187
---
linux (5.4.0-169.187) focal; urgency=medium
* focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)
* USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core:
This bug was fixed in the package linux - 5.4.0-169.187
---
linux (5.4.0-169.187) focal; urgency=medium
* focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)
* USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core:
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If
This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2040181
updating mantic to 2.2.0 final is in mantic-proposed, and this bug here
is in mantic-unapproved.
Should we drop 2.2.0 from mantic-proposed in favor of this one here?
--
You received this bug notification because you are a member
Outcome of testing with your kernel 6.5.0-2007-oem:
1) with your kernel batttery drain is 8% in 4 days;
2) with Ubuntu 22.04 6.2.0-37 kernel also 8% in 4 days;
3) with power reset workaround (see #49 above) it is 2% in 4 days.
So my conclusion is that 6.5.0-2007-oem has same battery drain still.
This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If
This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If
This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to
This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to
This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug was fixed in the package linux - 5.4.0-169.187
---
linux (5.4.0-169.187) focal; urgency=medium
* focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)
* USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core:
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug was fixed in the package linux - 5.4.0-169.187
---
linux (5.4.0-169.187) focal; urgency=medium
* focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)
* USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core:
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
This bug was fixed in the package linux - 5.4.0-169.187
---
linux (5.4.0-169.187) focal; urgency=medium
* focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)
* USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core:
This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
This bug is awaiting verification that the linux-gkeop/5.4.0-1083.87
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-gkeop' to 'verification-done-focal-
linux-gkeop'. If
This bug is awaiting verification that the linux-raspi/5.4.0-1100.112
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-raspi' to 'verification-done-focal-
linux-raspi'. If
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
reply #44
Hello,
We've done the firmware update on 22.04, could you try to remove linux-
modules-iwlwifi deb and use the in-tree kernel to see if you can still
reproduce the issue.
Thanks,
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
verified ipu6-drivers/mantic-proposed version
0~git202310180730.3f813580-0ubuntu0.23.10.1
** Tags removed: verification-needed-mantic
** Tags added: verification-done-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5
** Package changed: syslog-ng (Ubuntu) => linux (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/1903203
Title:
System becomes un-responsive due to gpu segfault
Status in linux
Wait... I seem to be confused by this:
>>>
mafoelffen@noble-d05:~$ apt-cache show zfsutils-linux | grep 'Package:\|Breaks:'
Package: zfsutils-linux
Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (>>
2.2.2-0ubuntu1...), zfs-dkms (<< 2.2.2-0ubuntu1)
>>>
Does that mean, even
** Tags added: jammy regression-update
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Nishit Majithia (0xnishit)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2045931
You have been subscribed to a public bug:
I was using:
Ubuntu 20.04 (installed a month ago, updated recently)
Vmware Workstation 16 (Ubuntu 20.04 VM)
Nvidia GTX 1080 TI Driver Version: 450.80.02 CUDA Version: 11.0
What happened:
System instantly became unresponsive. Mouse stopped moving,
This sounds like it might be a feature and the bug was that previous
versions DIDN'T ask. Try entering PIN:
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
Public bug reported:
While trying to access spidev0 on ubuntu 23.10 server version for
raspberrypi model 5 did not find spidev0.
On further debugging with raspi team it was observed that DMA is not set.
Link to the discussion:
https://forums.raspberrypi.com/viewtopic.php?t=360436=25
It looks like the problem was just no response provided to:
Configuration file '/etc/bluetooth/input.conf'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
어떻게 하시겠습니까? 다음 중에 하나를 선택할 수 있습니다:
Y 또는 I : 패키지 관리자의 버전을 설치합니다
N 또는 O :
FWIW, we updated our NICs to 4.30 as they were individually purchased
and not part of pre-built servers and also have this issue.
So in essence the issue also exists with the latest firmware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
We would like to collect some additional information about your system.
>From a terminal, please run the following:
apport-collect BUG_ID
or to a file:
apport-bug --save /tmp/report.BUG_ID linux
If apport can't be run:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn >
Oh, I missed this bit in https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/2040181/comments/10 in the other bug:
"It is still worth it to release this sru, before staging the next one
in proposed"
--
You received this bug notification because you are a member of Kernel
Packages, which
** Tags removed: verification-needed
** Tags added: verification-done
** Tags removed: verification-done-lunar
** Tags added: verification-needed
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This bug is awaiting verification that the linux-iot/5.4.0-1028.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-iot' to 'verification-done-focal-
linux-iot'. If the
This bug is awaiting verification that the linux-oracle/5.4.0-1115.124
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-oracle' to 'verification-done-
focal-linux-oracle'.
This bug is awaiting verification that the linux-oracle/5.4.0-1115.124
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-oracle' to 'verification-done-
focal-linux-oracle'.
This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Could https://github.com/openzfs/zfs/pull/15651 be picked up for this
update still?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Hello You-Sheng, or anyone else affected,
Accepted ipu6-drivers into mantic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/ipu6-drivers/0~git202310180730.3f813580-0ubuntu0.23.10.1
in a few hours, and then in the -proposed repository.
Please help us
This can be found on J-oracle-6.5.0-1013.13~22.04.4 as well.
** Tags added: 6.5 sru-20231030
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1988582
Title:
RT test failures:
Public bug reported:
Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
to connect my PS3 Sixasis controller via bluetooth. It is aking to enter
a PIN in the device (not possible to enter a pin in the gamepad).
Source pacakge (from "apt list -a bluez"):
Rick and I have been testing the Proposed 2.2.2 packages in Noble since
yesterday morning. Great so far.
@fl140 --
Thanks you for the link. I'll pass that on.
Waiting to see if anything of this helps with: zfs-dkms
2.1.5-1ubuntu6~22.04.2 https://bugs.launchpad.net/ubuntu/+source/zfs-
Just passed on to me from FL140:
https://github.com/openzfs/zfs/issues/15586#issuecomment-1836806381
Is an updated script to manually build and install the OpenZFS native
deb packages, including 'zfs-dkms' 2.2.2.
** Bug watch added: github.com/openzfs/zfs/issues #15586
BTW I have the 2.2.2 self built custom package running here on a 23.10
Ubuntu installation and it looks good so far. I would also advice to
check any possible affected pools running `zdb -ccc -vvv pool_name`
(Note: I don't know if the third -c makes any difference found nothing
in the man page.
FYI The `zdb -ccc` command does NOT show you which files where affected,
but it helped me to identify at least one zpool which got corrupted
between 2.2.0 and 2.2.1, but the source of this has to be investigated
further. At least it can't hurt to see if at least the pool is
consistent (there still
** Description changed:
+ [ Impact ]
+ Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks
which have been proven invalid for at least some hardware setups. A user trying
to run Focal with HWE 5.15 kernel is not able to get any video output.
+ After going through
I've got the same problem. I'm not sure that any sort of log collection
is impossible however, as the system doesn't crash until after GUI
login. I can switch to text only (ctrl-alt-F2) and login that way. A
crash report is saved when the crash occurs - I can collect some stuff
after rebooting.
*** This bug is a duplicate of bug 2044131 ***
https://bugs.launchpad.net/bugs/2044131
Public bug reported:
[ Impact ]
Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks
which have been proven invalid for at least some hardware setups. A user trying
to run Focal
*** This bug is a duplicate of bug 2044131 ***
https://bugs.launchpad.net/bugs/2044131
Adding dmesg and lspci from affected system
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045891/+attachment/5727216/+files/dmesg
--
You received this bug
*** This bug is a duplicate of bug 2044131 ***
https://bugs.launchpad.net/bugs/2044131
** Attachment added: "lspci"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045891/+attachment/5727217/+files/lspci
--
You received this bug notification because you are a member of Kernel
*** This bug is a duplicate of bug 2044131 ***
https://bugs.launchpad.net/bugs/2044131
** Patch added:
"0001-drm-i915-Skip-some-timing-checks-on-BXT-GLK-DSI-tran.patch"
** Changed in: linux
Status: Unknown => Fix Released
--
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/2044131
Title:
i915 regression introduced with 5.5 kernel
Status in Linux:
Public bug reported:
The partner report below syslog error related to:
Aug 30 09:10:48 localhost kernel: [7.335926] tegra186-gpio NVDA0508:00:
invalid resource
Aug 30 09:10:48 localhost kernel: [7.341446] tegra186-gpio NVDA0508:00:
invalid resource
Aug 30 09:10:48 localhost kernel: [
I was asked whether it relate to no actually device (LCD) connected and
could be safely ignored?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2045882
Title:
tegra-qspi
Same thing happened again today, but this time it fully crashed the PC
after a few seconds of flickering.
I'll keep an eye on if it also happens in Arch Linux or Windows.
** Attachment added: "dmesg-gpu2-txt"
** Attachment added: "OlderDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+attachment/5727266/+files/OlderDmesg.txt
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
I saw similar messages in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032386 but that
only caused hangs and not block the entire desktop (and Firefox is good
now so I don't know)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Waiting for 6.5.13 to actually build but on 6.6.0-14 from proposed now
which is based on 6.6.3 which probably has all the fancy patches too
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Andre,
I successfully installed on the machines with NVMUpdate64 tool. That is
on HPE machines.
$ sudo ./nvmupdate64e
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.39.56.8
Copyright(C) 2013 - 2023 Intel Corporation.
WARNING: To avoid damage to your device, do not stop the update or
Public bug reported:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level but
the GUI doesn't actually recover and I also can switch tty with the
keyboard.
I have attached the two crashes from yesterday, they look
** 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/2044131
Title:
i915 regression introduced with 5.5 kernel
Status in Linux:
Fix Released
Status in linux package in
These ones I don't remember seeing before:
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
--
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/2045899
Title:
More
please try a later point release mainline kernel:
https://kernel.ubuntu.com/mainline/v6.5.13/
which is also the last one for 6.5
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
Yeah, I knew about that 4.30 update in Intel website, but it is not present on
Dell tools yet and the customer did not want to void their warranty
(potentially), so I did not try it. That is something to keep in mind while we
debug it.
--
You received this bug notification because you are a
1 - 100 of 105 matches
Mail list logo
