I can confirm this bug an add the following information:
Kernel 5.15.0-116-generic: VBox 6.1.50 is not working at all
Kernel 5.15.0-112-generic and 5.15.0-113-generic: VBox 6.1.50 is working
with boot workaround amg_iommu=off due to the bug in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
I can confirm, proposed image -116 works without disabling amd_iommu:
berni@enterprise:~$ uname -rv
5.15.0-116-generic #126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Some more info on booting -112 related to amdgpu, which is crashing:
Jun 7 09:29:22 enterprise kernel: [2.809882] AMD-Vi: AMD IOMMUv2 loaded
and initialized
Jun 7 09:29:22 enterprise kernel: [2.979171] amdgpu: Topology: Add APU
node [0x0:0x0]
Jun 7 09:29:22 enterprise kernel: [2.9
Quick-Fix: GRUB_CMDLINE_LINUX_DEFAULT="amd_iommu=off"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068738
Title:
Kernel update 5.15.0-112 might cause severe problems with specific AMD
GPUs
To m
@Fred: setting nomodeset is only a small workaround, it disables full
graphic support, no multi display usage, no high resolution ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068738
Title:
Ker
Public bug reported:
System is not booting while using AMD Picasso/Raven 2 graphics after
update to 5.15.0-112
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
vendor: Hewlett-Packard driver: amdgpu v: kernel bus-ID: 04:00.0
Display: x11 server: X.Org v:
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/51883714/Dependencies.txt
** Attachment added: "VarLogDistupgrade201007122202.gz"
http://launchpadlibrarian.net/51883715/VarLogDistupgrade201007122202.gz
--
package python 2.6.5-0ubuntu1 failed to install/upgrade:
https
Public bug reported:
Automatic update failed with python stuff
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: python 2.6.5-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Confirmed on Hardy too.
Fixed this way and rmagic is working now.
--
rmagic fails on call to GD
https://bugs.launchpad.net/bugs/315280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
I have a similar stack trace maybe related to this, happens often a
network user tries to access a network device, he got the windows
messages that the network share is not available, smbd crashes and after
that, the user can access the network share. But from time to time, the
crash continues and
So again here is the last panic action output, a little longer, but
still the NPROC limit error in the host logfile:
[2008/10/06 08:49:27, 0] lib/util_sec.c:set_effective_uid(205)
setresuid failed with EAGAIN. uid(1001) might be over its NPROC limit
[2008/10/06 08:49:27, 0] lib/util_sec.c:assert
Steve,
this could not be normal - in /etc/security/limits.conf there is no limit
configured, and I dont know,
but could it be unlimited as default in Ubuntuty Hardy ?
Commenting out panic-action does not solve the problem, because it only
prevents the mail
and not the action. smbd still crashes
I can confirm this kind of bug!
On a new installed Hardy, Samab crashes not everytime but often:
Log from the per Host logfile:
[2008/10/04 20:09:57, 0] lib/util_sec.c:set_effective_uid(205)
setresuid failed with EAGAIN. uid(1001) might be over its NPROC limit
[2008/10/04 20:09:57, 0] lib/util_s
13 matches
Mail list logo
