The bug for GCP n2d-standard-4.sev_snp can be tracked in bug 2051378
--
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/2034057
Title:
function_graph tracer in ftrace related tests trigg
** Summary changed:
- AMD phenix/phenix2 platforms facing amdgpu(PHX) hangs during stress loading
+ AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmwa
All autopkgtests for the newly accepted linux-meta-gcp-6.5
(6.5.0.1013.13~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
lxc/1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 (arm64)
Please visit the excuses page listed below and inve
False alarm. The screen blanking that GRUB_TERMINAL=console "fixes" was
actually caused by me using GRUB_TIMEOUT=3. Changing it back to the
default GRUB_TIMEOUT=0 also prevents the blanking mentioned in comment
#30.
--
You received this bug notification because you are a member of Kernel
Packages
Public bug reported:
With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
within a few minutes or sometimes even quicker. Also using mantic + v6.7
hit the hang, so need to update new FWs to fix this issue.
PHX series
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
You have linux-base 4.6 installed which is not an Ubuntu version of the
package. Please replace it with 4.5ubuntu9 from the Ubuntu archives.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Looks like systemd failed and started timing out for multiple things
before this happened. So there's nothing bluez can do about that.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Also you don't seem to be using a Raspberry Pi or Xorg here. Was the
mouse plugged into a different machine?
--
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/2051617
Title:
Raspberry Pi mo
Please check to see if the kernel is getting the button events:
sudo apt install evtest
sudo evtest
** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu)
** Changed in: linux-raspi (Ubuntu)
Status: New => Incomplete
** Package changed: linux-raspi (Ubuntu) => linux (Ubuntu)
**
> Display resolution stuck at 800x600 after using nomodeset in grub.
> But my Dell monitor has 1600x900 resolution.
This is correct behaviour. "nomodeset" means to disable the graphics
driver and to disable high resolution support.
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
** C
You have been subscribed to a public bug:
Using the event tracker tool
(
xmodmap -pp > ~/xmodmap-pp
xev | grep -i button
), buttons 4 and 5 are responsive, optical works (the cursor moves across the
screen).
Left and right click buttons are unresponsive. Mouse connected via USB.
MOUSE INFO:
R
You have been subscribed to a public bug:
Display resolution stuck at 800x600 after using nomodeset in grub. But
my Dell monitor has 1600x900 resolution.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Unam
Public bug reported:
i don't know why
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Arch
Oh I missed that. Having a problem with recovery mode probably means
this isn't as simple as bug 2028165. Instead I'll move this to being
just some new bug in kernel 6.5.
** Summary changed:
- Freeze
+ Freeze in kernel 6.5 (but 6.2 works)
** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)
**
You have been subscribed to a public bug:
Freeze began after a system update
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
*** This bug is a duplicate of bug 2028165 ***
https://bugs.launchpad.net/bugs/2028165
** This bug has been marked a duplicate of bug 2028165
nvidia-dkms-* FTBS with linux 6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-
All autopkgtests for the newly accepted linux-meta-oracle-5.15
(5.15.0.1051.57~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
linux-oracle-5.15/5.15.0-1051.57~20.04.1 (arm64)
Please visit the excuses page listed below an
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include check
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
Public bug reported:
I've been getting regular systems crashes for the last few months.
Because it was being triggered in kswapd0 I recently disabled swap
completed, but the issue still continues. I also moved swap to another
disk but again the problem persists several times per week. No other
c
Public bug reported:
Fresh install...Not doing anything other than installing brave and this
error kicked off
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: nvidia-firmware-535-535.154.05 535.154.05-0ubuntu0.23.10.1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.
Probably a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042867.
Try turning on proposed and getting 6.5.0-17.17 to see if it helps. It picks
up that fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed
I have not been able to use my VM properly since this behavior started.
Any update on whether this will be investigated?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/205002
> Also to prevent Grub from blanking the screen you need to uncomment:
Can you open another bug against GRUB to fix this default for Noble?
> Thanks for testing, so DRM_SIMPLEDRM needs to be built-in for it to
work properly
Yeah it should need to be built in.
> But bug 1970069 still pops up aft
> This seems to be a bug in the kernel documentation.
Yeah I guess so.
> I'm now waiting until my conversation with Daniel Vetter is concluded
before formulating a plan for how to approach dri-devel.
👍
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Description changed:
+ SRU Justification
- 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
+
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
Ran AppArmor tests from the QA Regression Tests [1] and POSIX mqueue
tests from the AppArmor test suite and they all passed as expected.
georgia@sec-jammy-amd64:~$ uname -a
Linux sec-jammy-amd64 5.15.0-1052-ibm-gt-fips #55+fips1-Ubuntu SMP Fri Jan 19
23:25:50 UTC 2024 x86_64 x86_64 x86_64 GNU/Lin
@p-pisati - I don't know where the last half of the commit:
c4e927da893b--> 68b99e94a4a2 came from. But I looked in our internal
JIRA and it shows this:
c4e927da893b thermal: intel_powerclamp: Remove accounting for IRQ wakes
This is the correct one.
--
You received this bug notification becau
Thanks for sharing that. Your cifs-utils is the same that I have on an
ubuntu 22 VM, which shows the issue with a server running an earlier
version of Samba (4.7.x) and a later version. I unfortunately don't
readily have a VM with 4.8.x readily available, but the brittleness of
file modtime preserv
** Description changed:
The tuned package has some plugins which rely on the perf python module
[1], and right now they are not working because we do not have the perf
python module available in Ubuntu.
Initially, this was reported in this other bug [2], but it seems the
scope of that
Its not immediately apparent from perf tool output that the "amd-uncore"
module is not loaded when opening "amd_df" or "amd_l3" events fail or
when they do not show up in "perf list" despite using a compatible
kernel. Since the primary motivation of the commit [1] that made it
possible for this to
I monitor with wireshark and it can be any TCP payload.
the common TCP header part is flag PUSH is ON.
It happens in both directions.
** Summary changed:
- tcp has MSS=1460, but TLSv1.3 payload is overshooting maximum segment size
+ tcp has MSS=1460, but a segment with PUSH flag is overshooting
*** This bug is a duplicate of bug 2028165 ***
https://bugs.launchpad.net/bugs/2028165
@bgd. Either use the PPA I linked to (
https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp )
or follow along with the master bug ( https://bugs.launchpad.net/bugs/2028165 )
to see if Ubuntu fixes it:
I updated my livecd-rootfs PPA test package that runs this section of
code in a loop to use this pattern, and it survived until the
autopkgtest timeout - 304 iterations:
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-
loop/noble/amd64/l/livecd-rootfs/20240128_061640_5c909@/log.gz
Public bug reported:
The tuned package has some plugins which rely on the perf python module
[1], and right now they are not working because we do not have the perf
python module available in Ubuntu.
Initially, this was reported in this other bug [2], but it seems the
scope of that bug is bigger
*** This bug is a duplicate of bug 2028165 ***
https://bugs.launchpad.net/bugs/2028165
I get the same issue :( on
Linux diana-desktop 6.5.0-15-generic #15~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri
Jan 12 18:54:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:Ubu
This bug was fixed in the package zfs-linux - 2.2.0-0ubuntu1~23.10.1
---
zfs-linux (2.2.0-0ubuntu1~23.10.1) mantic; urgency=medium
* d/p/u/zed-fix-typo-ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT.patch:
fix typo in configuration option in zed.rc (LP: #2046082)
-- Mauricio Faria de O
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 encounter
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-hwe-6.5 in
Ubuntu.
https://bugs.launchpad.net/bugs/2051542
Title:
package linux-modules-nvidia-470-6.5.0-15-generic
6.5.0-1
Public bug reported:
crashed during update
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-modules-nvidia-470-6.5.0-15-generic 6.5.0-15.15~22.04.1+1
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_mod
Thanks for testing, so DRM_SIMPLEDRM needs to be built-in for it to work
properly? I guess that's fine then..
--
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/1965303
Title:
Migrate from f
@Andrea, that's a good start, but it may be worth running some of the
Phoronix Tests too as they are a good spread of use cases.
--
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/2051342
Titl
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
Public bug reported:
$ sudo apt-get install linux-tools-common
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libffi6 libflashrom1 libftdi1-2 libisl19 libllvm13
li
Fix already included in 6.8
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Invalid
--
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/2036239
Title:
Intel E810-XXV - NETD
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Timo Aaltonen (tjaalton)
Status: Confirmed
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
--
You received this bug notification because you are a
Also to prevent Grub from blanking the screen you need to uncomment:
GRUB_TERMINAL=console
Then you get a smooth transition from BIOS to kernel graphics
(simpledrm). But bug 1970069 still pops up after that.
--
You received this bug notification because you are a member of Kernel
Packages, wh
OK I've got simpledrm working now. It needed:
FB_EFI=n
FB_VESA=n
CONFIG_SYSFB_SIMPLEFB=y
CONFIG_DRM_SIMPLEDRM=y
So now I have working graphics very early:
[0.588237] [drm] Initialized simpledrm 1.0.0 20200625 for
simple-framebuffer.0 on minor 0
...
[7.153876] [drm] Initialized i
If it's in stable 6.6 it should/will trickle down into the Ubuntu 6.5
kernels. We're slightly behind upstream stable, 6.6.4 is currently in
the works: bug #2051231
If you can't wait you can send a patch the the ML to expedite it.
https://wiki.ubuntu.com/KernelTeam/KernelUpdates
--
You received t
@colin-king thanks! Any suggestion in particular? I was thinking to
lmbench, netperf and fio.
--
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/2051342
Title:
Enable lowlatency settings in
> This requires Kernel config changes:
>
> FB_EFI=n
> FB_VESA=n
I'm testing this and it's a step backwards. The screen just turns black
for the first 6 seconds or so while Plymouth waits for i915drmfb to
start instead (might be Plymouth's fault for being too picky?). FB_EFI
was better because it
@dsmythies thank you so much for sharing the results of your tests,
really useful info!
I'm planning to do more tests setting the performance governor, I've
been doing my initial tests only with the default Ubuntu settings, that
means with the "Balanced" power mode enabled (that I think it's using
It may be worth trying a wider range of synthetic benchmarks to see how
it affects scheduling, I/O, RCU and power consumption.
--
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/2051342
Title:
54 matches
Mail list logo
