** Description changed:
Hello Ubuntu Team,
I notice issue today with Maxlinear Ethernet GPY115B controller.
This controller report issue in dmesg and port not have link up.
My target is: OnLogic HX310 with two Ethernet Ports.
> Official page:
** Attachment added: "inxi - 6.8.0 - generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+attachment/5767539/+files/inxi-6.8.0-22-generic.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "lspci - 6.8.0 - generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+attachment/5767538/+files/lspci-6.8.0-22-generic.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "lshw - 6.8.0 - generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+attachment/5767537/+files/lshw-6.8.0-22-generic.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Hello Ubuntu Team,
I notice issue today with Maxlinear Ethernet GPY115B controller.
This controller report issue in dmesg and port not have link up.
My target is: OnLogic HX310 with two Ethernet Ports.
> Official page:
** Attachment added: "dmesg - 6.8.0 - generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+attachment/5767536/+files/dmesg-6.8.0-22-generic.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi @juozaspo,
This is fixed now.
I use latest image:
https://cdimage.ubuntu.com/daily-live/20240412/noble-desktop-amd64.iso
Ticket is verifed.
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
"apt-get dist-upgrade" command causes the display to stop working - OS
is broken
OS: Ubuntu Noble 24.04 LTS
Kernel: 6.8.0 Canonical
Command: apt-get dist-upgrade
Status: First installation and execute dist-upgrade command to have latest
packages.
OS image:
** Patch added: "nvidia-drm-take-modeset-ownership-earlier.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2052420/+attachment/5761484/+files/nvidia-drm-take-modeset-ownership-earlier.patch
--
You received this bug notification because you are a member of
Hi,
I have question,
Is possible to add this patches:
PATCH[0]="disable_fstack-clash-protection_fcf-protection.patch"
PATCH[1]="buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch"
PATCH[2]="buildfix_kernel_6.8-gpl-pfn_valid.patch"
** Patch added: "nvidia-drm-hotplug-workqueue.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2052420/+attachment/5761485/+files/nvidia-drm-hotplug-workqueue.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
Hi Ubuntu Kernel Team,
I notice this today.
This option CONFIG_IRQ_TIME_ACCOUNTING is not enabled in Ubuntu Noble 6.8
Kernel.
Is possible to add this at built-in?
# CONFIG_IRQ_TIME_ACCOUNTING is not set
It would help me for profiling in the future, when testing
** Attachment added: "devices 2 6.8.0 noble - master-next - today"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+attachment/5755595/+files/devices2.txt
** Description changed:
hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8
version
device is
** Attachment added: "devices 1 6.8.0 noble - master-next - today"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+attachment/5755594/+files/devices.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "journalctl 6.8.0 noble - master-next - today"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+attachment/5755593/+files/journalctl-6.8.0-ubuntu-noble-lowlatency1.txt
--
You received this bug notification because you are a member of Kernel
Packages, which
** Attachment added: "dmesg 6.8.0 noble - master-next - today"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+attachment/5755592/+files/dmesg-6.8.0-ubuntu-noble-lowlatency1.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8
version
device is not recognized when using 6.8 kernel version
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
Using kernel 6.8.0-rc5 this is working correctly with nvidia-
driver-545=545.29.06-0ubuntu5.
dpkg -l | grep nvidia
ii libnvidia-cfg1-545:amd64 545.29.06-0ubuntu5
amd64NVIDIA binary OpenGL/GLX configuration library
ii libnvidia-common-545
Public bug reported:
Hi Ubuntu Kernel Team,
I have one question regarding C-states and Thermal functions.
Why turbostat report three C-states with ACPI keyword(CxACPI)?
Shouldn't I see up to 8 states inclusive? C7-C8?
<
cpu0: POLL: CPUIDLE CORE POLL IDLE
cpu0: C1ACPI: ACPI FFH MWAIT 0x0
This is reproduced again when using 5.15.0-1045-intel-iotg or
5.15.0-1046-intel-iotg.
sudo apt install linux-tools-intel-iotg -f
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-tools-intel-iotg is already the newest version
** Attachment added: "journalctl-5.15.0-1043-intel-iotg"
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2045652/+attachment/5726397/+files/journalctl-5.15.0-1043-intel-iotg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "dmesg-5.15.0-1043-intel-iotg"
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2045652/+attachment/5726396/+files/dmesg-5.15.0-1043-intel-iotg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
Hi Ubuntu Team,
I notice this today when using 5.15.0-1043-intel-iotg version:
ieee80211 phy0: Hardware restart was requested
[ cut here ]
WARNING: CPU: 10 PID: 25430 at net/mac80211/scan.c:436
__ieee80211_scan_completed+0x2ba/0x2d0 [mac80211]
** Summary changed:
- linux-intel-iotg package - bump to 6.5 kernel version - linux-intel-iotg-b
+ linux-intel-iotg package - bump to 6.6 kernel version - linux-intel-iotg-b
** Description changed:
- linux-intel-iotg package - bump to 6.5 kernel version - linux-intel-
+ linux-intel-iotg package
Public bug reported:
Hello Ubuntu Team,
I notice today using default iot and proposed iot kernel, missing TGPIO
and GPIO support.
IOT: 5.15.0-1040-intel-iotg
Proposed IOT: 5.15.0-1042-intel-iotg
With TGPIO support in kernel, i have this in dmesg:
dmesg | grep -i gpio
[1.954807] acpi
Public bug reported:
OS: Ubuntu 22.04 IOT LTS (Desktop Variant)
Kernel: 5.15.0-1041-intel-iotg
I saw these messages in dmesg, which kept repeating.
They appear from a connected camera.
>From what I checked, on 5.15.x and 6.1.x these messages are reproduced.
But in more recent versions this no
Public bug reported:
linux-intel-iotg package - bump to 6.5 kernel version - linux-intel-
iotg-b
** Affects: linux-intel-iotg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
linux-intel-iotg package - bump to 6.1 kernel version - linux-intel-
iotg-a
** Affects: linux-intel-iotg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hi Steve Langasek,
I reinstalled today my PC with Ubuntu Desktop IOT.
And i use latest packages from proposed repository.
This issue is now resolved.
My PC now running this:
Kernel version: 5.15.0-1035-intel-iotg #40-Ubuntu SMP Fri Jul 14
08:03:36 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Hi Andreas,
I reinstalled today my PC with Ubuntu Desktop IOT.
And i use latest packages from proposed repository.
This issue is now resolved.
My PC now running this:
Kernel version: 5.15.0-1035-intel-iotg #40-Ubuntu SMP Fri Jul 14
08:03:36 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mutter
Hi Andreas,
Will try to check new packages in next days.
Thanks for all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2026887
Title:
gnome-shell 42.9 Wayland sessions fail
Hi Daniel,
I reinstalled today my ADL-P PC with Ubuntu Desktop 22.04.02.
And this is not reproduced with -generic kernel.
I have this: 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun
21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
And no error with this.
LIBMUTTER VERSION:
Public bug reported:
Error during upgrade
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-1003-oracle 6.2.0-1003.3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
Thank you Daniel!
I have added the bug information here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978534
--
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/1967274
Title:
I am using kernel v5.15.0-37 but I am still affected by this bug on my
XPS 15 (9500). Installed mutter is 42.1.
Also, the Night Light is not working (I saw some references in this
thread about this feature).
Is there anything else I must update on my system to have it working
properly?
Thanks!
I've tested the same scenarios as @Vivien GUEANT (vivienfr) on a Dell R210 II
with Matrox G200 integrated GPU
- Ubuntu 20.04 server installs without any issue
- Ubuntu 22.04 server does not install and I get a black screen and the monitor
is showing this error “input signal out of range”
-
Public bug reported:
It's pretty much this problem: https://askubuntu.com/questions/1100982
/not-sure-if-i-have-a-nvidia-driver-410-bug-or-an-error , but with
Ubuntu 20.04 LTS
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvidia-settings 440.64-0ubuntu1
ProcVersionSignature: Ubuntu
The same happen with my XPS 13. Since a couple of days I have noticed
this annoying hiss. I use Ubuntu 19.04.
The workaround also fixes the issue for me (amixer -c 0 set 'Headphone
Mic Boost',0 1)
Regards
--
You received this bug notification because you are a member of Kernel
Packages, which
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
I also encountered this issue on Ubuntu 16.04.6 LTS, kernel
4.15.0-48-generic, on ThinkSystem SR650.
Jul 6 07:29:04 ic-defraf1-s4ahu919 kernel: [2837234.471731] BUG: unable to
handle kernel NULL pointer
We haven't seen it in Xenial, but we managed to reproduce it back to the
daily Bionic build from the 2nd of March. We haven't tested Bionic daily
builds before the 2nd of March, nor did I try to reproduce it on Zesty
or or Artful.
--
You received this bug notification because you are a member of
I have opened a different bug for the first issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640
Regarding the second issue, as mentioned in comment #13, the tested
kernels did not exhibit issue #2.
** Description changed:
While testing Bionic daily build with kernel
I have tested this on kernel 4.15.0-24.26 and linux-cloud-tools
4.15.0-24.26 and the issue persists.
--
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/1779640
Title:
[Hyper-V] KVP daemon
** Package changed: linux-azure (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/1779640
Title:
[Hyper-V] KVP daemon crashes at startup
Status in linux package
Public bug reported:
While testing Bionic daily build with kernel 4.15.0-20-generic we saw
the following issue with the KVP daemon:
KVP daemon crashes after approximatively 2 minutes of uptime and it enters in a
failed state. The daemon can be manually started and it enters back in active
Regarding comment #11:
I have tested both kernels provided with the following results:
- 4.14 Bionic kernel (4.14.0-16-generic) does NOT exhibit issue #2
(missing files), but it does exhibit issue #1 (KVP daemon failure after
boot). Linux-cloud-tools version installed is 4.14.0-16.19.
- 4.15
I have tested Bionic with kernel 4.15.0-22-generic, linux-cloud-
tools-4.15.0-22.24 and linux-tools-4.15.0-22.24 and both issues still
occur.
While testing the above mentioned kernel, I saw the following behavior:
1. Right after booting the system the KVP daemon reports it is active
(running).
I tested back to the daily build from 2nd of March and I can confirm the
second issue (regarding the binaries path), but not the first one
(regarding the daemon crash). On the build from the 2nd of March the
linux-tools and linux-cloud-tools version is 4.15.0-10.11
--
You received this bug
Public bug reported:
While testing Bionic daily build with kernel 4.15.0-20-generic we saw
that there are 2 issues with the KVP daemon:
1. KVP daemon crashes after approximatively 2 minutes of uptime and it enters
in a failed state. The daemon can be manually started and it enters back in
Public bug reported:
Issue description: Memory demand increases very fast up to the maximum
available memory, call traces show up in /var/log/syslog, the VM becomes
unresponsive during the memory consumption, but it becomes responsive
right after stress-ng ends its execution, therefore we can say
I have tested the proposed kernel, but with this version both bugs are
showing up.
Could it be that the bug is not in the kernel, but in systemd?
Below is a comparison of the strace command ran on RHEL 7.3 and Ubuntu 16.04.1,
when trying to re-enable the Data Exchange integration service:
I have tested Xenial back to 4.2.0-16 from here: https://launchpad.net
/~canonical-kernel-team/+archive/ubuntu/ppa/+build/8099555
The second issue is still present.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have tested 4.4.0-2.16 from here:
https://launchpad.net/ubuntu/+source/linux/4.4.0-2.16/+build/8908724
In this case, the daemon remains running when the integration service is
being disabled. systemctl status shows the daemon running and active,
but the daemon is not working actually.
I have tested the mainline kernel provided with the compiled daemons
form linux-next. In this case, the daemons do stop when the integration
service is being disabled, but do not automatically start after we re-
enable the integration service. Manually starting the service works
fine. So the
I have tested the kernel provided with commit ef754413085f5 and the bug
persists. The daemons do not stop if the integration services are being
disabled.
The kernel provided in comment #36 was not affected by the bug. That was
the first good commit.
Regarding comment #27, the kernel tested was
I have tested both kernels provided, and both exhibit the bug. In both
cases the daemon does not stop after the integration services is being
disabled.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have tested the above kernel. The daemon stops if the integration
service is being disabled, but does not automatically start after the
service is being enabled again (same behavior as 4.4.0-3).
--
You received this bug notification because you are a member of Kernel
Packages, which is
I have tested the above kernel build. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable
I have tested the above kernel build. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable
Tested the above kernel build. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
Tested the above kernel build. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
I have tested the kernel above. The daemon still remains running after
the integration service is being disabled.
--
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/1701222
Title:
[Hyper-V]
I have tested the kernel above. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
I have tested the kernel provided. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
I have tested the kernel provided. The issue still occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
I have tested the kernel provided in the link above. The issue still
occurs.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after
I have tested the kernel provided in the link above. The daemons do not
stop when the integration services are disabled.
--
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/1701222
Title:
I have checked back to 4.2.0-16. It seems that 4.4.0-2 is the last
kernel where the daemons remain running even if integration services are
being disabled. Starting with 4.4.0-3 the daemons stop if the
integration services are disabled, but do not automatically start if the
integrations services
The same happens on 4.4.0-20 kernel.
--
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/1701222
Title:
[Hyper-V] LIS daemons fail to start after disable/re-enable VM
integration services
It this is a kernel bug then booting an older kernel should avoid this
issue, right? I have tried on a 3.19.0.25 kernel and the issue is still
there. I have also installed v3.19.8-ckt6 and the display port issue is
still there.
--
You received this bug notification because you are a member of
I think it is a hardware issue after all ... the dp interface on the
monitor ... sorry for wasting your time
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
70 matches
Mail list logo
