Public bug reported:
Recently a patch has been accepted on the Linux Kernel regarding the TCP
stack which fix an additional +40ms latency on ARM64 CPU architecture
without impacting other CPU types.
More information can be find in here:
https://lore.kernel.org/netdev/20240119190133.43698-1-dipi..
I switched to Wayland and the problem solved, but others arise! i.e.
the favourite menu starts not working
On 16/06/2023, Salvatore Campeggio wrote:
> This is the result of driver check:
>
> camp@camp-medion:~$ glxinfo -B
> name of display: :0
> display: :0 screen: 0
> dir
This is the result of driver check:
camp@camp-medion:~$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Mesa/X.org (0x)
Device: llvmpipe (LLVM 12.0.0, 256 bits) (0x)
Version: 21.2.6
I did it again, now the result is different, but the bug didn't change
camp@camp-medion:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic
root=UUID=cbfc0023-baf3-4a11-b0aa-6dadbd0f60f7 ro i915.enable_psr=0
On 16/06/2023, Daniel van Vugt <2023...@bugs.launchpad.net> wrote:
> Indeed
I already did it some time ago, with no result.
I did it again now, but cat /proc/cmdline report the same result as before:
camp@camp-medion:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic
root=UUID=cbfc0023-baf3-4a11-b0aa-6dadbd0f60f7 ro quiet splash
pci=noaer vt.handoff=7
On 16
** Tags added: kernel-bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2015400
Title:
losetup with mknod fails on jammy with kernel 5.15.0-69-generic
Status in linux package
** Also affects: linux-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: jammy
--
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/2015400
Title:
losetup with mkno
I updated to day to Pop OS! 22.04 (based on Ubuntu 22.04) and I am
pretty sure that the bug I am going to present you now is related to the
one mentioned in this thread.
I can't suspend my laptop anymore after the update. I tried both with
nvidia drivers 470 and 515. What happens is that if I try
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
If possible, try to participate in the bug report that I have opened on gitlab
and to share your experiences
If I am the only one discussing the problem, it will hardly be considered soon
https://gitlab.freedesktop.org/drm/intel/issues/1377
--
You received this bug notification because you are
https://gitlab.freedesktop.org/drm/intel/issues/1377
This is the first time I open a report, so I don't know if I did it
correctly
PS: in the initial part I reported the problem as it was written by the
user who opened the bug here, I hope it is not a problem
** Bug watch added: gitlab.freedeskt
I confirm the bug
The bug applies to all the distros I have tried:
Ubuntu; Linux Mint; Manjaro; Fedora; Opensuse etc.
I also tried various DEs: Kde, Gnome, Cinnamon, Xfce, Mate etc.
It's a general problem, not just of mutter and Gnome
The bug exists only with Mesa and Modesetting, if you install xf
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Same here:
[34617.702285] NETDEV WATCHDOG: eth0 (r8152): transmit queue 0 timed out
[34617.702302] WARNING: CPU: 0 PID: 0 at
/build/linux-hwe-9kWQFX/linux-hwe-5.0.0/net/sched/sch_generic.c:461
dev_watchdog+0x221/0x230
[34617.702303] Modules linked in: md4 nls_utf8 cifs ccm fscache snd_usb_audio
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
Almost same problem on Dell 9370.
My laptop freezes.
4.15.0-43 works.
** Attachment added: "kern.log.part"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813742/+attachment/5233839/+files/kern
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
It looks like you're out of disk space. Running `df -h` or `df -i` may
help you diagnose what partitions need attention.
** Information type changed from Private Security to Public
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
It looks like you're out of disk space. Running `df -h` or `df -i` may
help you diagnose what partitions need attention.
** Information type changed from Private Security to Public
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
se the 3.4 kernel module with Absence Patches:
http://www.absence.it/vaio-acpi/source/patches/
---
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: salvatore 3569 F pulseaudio
/dev/snd/controlC0: sa
ource/patches/
---
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: salvatore 3569 F pulseaudio
/dev/snd/controlC0: salvatore 3569 F pulseaudio
CRDA:
country IT:
(2402 - 2482 @ 40), (N/A, 2
---
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: salvatore 3569 F pulseaudio
/dev/snd/controlC0: salvatore 3569 F pulseaudio
CRDA:
country IT:
(2402 - 2482 @ 40), (N/A, 20)
(5170
Hi friend!
I've recently found that article on the web and the facts I had
found in it were just shocking! Please read it here http://bit.do/dxabM
Warmest regards, Salvatore Cristofaro
From: Bug 1069707 [mailto:1069...@bugs.launchpad.net]
Sent: Friday, June 23, 2017 2:19 AM
To: cr
I'm also experiencing the same WiFi problems related to the rt5390
wireless card. Currently using Ubuntu 16.04 with 4.4.0-34-generic linux
kernel.
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Kernel
Packages, which
It took me a week to get Debian Wheezy to run properly on a W541. I'll
give a list of the nexesary items. Many of which should be applicable to
Ubuntu. Firts of all, don't expetc to be able to boot this from a live
usb any time soon. The W541 is way too new. If you wish to install, then
there is ho
The bug is still hitting stable builds. Backport is possible, but we
should solve first the related guestfs issues (bug 1275267)
--
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/1273386
Titl
Crash dumps from test machine.
** Attachment added: "crash_dumps.log"
https://bugs.launchpad.net/neutron/+bug/1273386/+attachment/3963600/+files/crash_dumps.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
The kernel bug manifests when mounting of nbd devices is combined with ip
namespace operations.
Using openstack it can be reproduced only with the following configuration:
- compute service must run on the same node as the dhcp-agent and/or the
l3-agent
- file injection should be turned on: libvi
Stefan, regarding comment #12
A few of us have noticed that recent changes in the testing framework
are causing neutron network resources to not be deleted (I filed bug
1274410 this morning, but we have known about this for almost a week
unfortunately).
A side effect is that this leaves a rather
Sorry I was blind.
Kernel crash even with 3.11, same trace.
http://paste.openstack.org/show/62152/
--
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/1273386
Title:
Neutron namespace metada
It looks like the OVS and DNS failures were due to nodes not properly built and
these issues were resolved.
However, experimental jobs seem to be revealing "Timed out waiting to get to
ACTIVE" errors without any kernel crash dump.
The error is still what appears to be a hang while mounting the n
of course I did not mean "the new kernel is also unable to resolve the
hostname". the comment was referred to the node, not the 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/1273386
We have now rolled the new kernel in the nodes used for the experimental jobs.
This did not help anyway. In the logs the 'waiting for thing to become ACTIVE'
failures are still present, but there is a different failure mode (no kernel
crash).
However, openvswitch is just not working [1] and the
thanks Chris I will try your kernel asap!
--
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/1273386
Title:
Neutron namespace metadata proxy triggers kernel crash on Ubuntu
12.04/3.2 kerne
forgot to mention that when we dealt with bug 1224001 we were running
3.2.0-54
--
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/1273386
Title:
Neutron namespace metadata proxy triggers ker
Hi Stefan,
I have a few more info.
I am trying to run the tests which trigger the issue on two machines, one with
3.2.0-57 and the other with 3.2.0-58.
So far, after 20 runs on each machine, the crash did not happen, so I can't yet
confirm the regression.
However, back in october we had another
I've run the related patch twice, and the kernel bug was hit even with
SIGTERM rather than SIGKILL.
I think this kind of confirms that "failure to become ACTIVE" error is
related to issues while terminating metadata proxies and dnsmasq
instances.
--
You received this bug notification because you
More info.
The crash actually happen when a process is killed. This has consistently
happened in 10 failures I've analyzed.
So the first conclusion is that this might be, after all, a red herring, and
the kernel dump being merely a consequence of the abrupt killing of a process.
I've pushed this
I have worked a bit more on this issue, and it seems that the crash
happens when a process is executed in a namespace. So it's not the
metadata proxy doing something that crashes the kernel, but is the act
of launching the metadata proxy which causes the crash.
--
You received this bug notificati
The bug seems to affect also
Kubuntu 13.04 - Kernel version 3.8.0-29
Kubuntu 13.04 - Kernel version 3.8.0-30
No problem with 3.8.0-28 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/b
42 matches
Mail list logo
