Public bug reported:
suddenly, my computer did not launch and it popped up "kernel error..."
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: broadcom-sta-dkms 6.30.223.271-23ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-29.29~24.04.1-generic 6.11.11
Uname: Linux 6.11.0-29-generic x86_64
N
Sorry for the late response..
Is this included in 2.7 ? I wasn't able to test the files on my current
installation
thanks
Luis
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858201
Title:
volum
I'm out of station until Feb 3rd. I'll check when I arrive
On Thu, Jan 23, 2020, 4:20 AM Newell Jensen
wrote:
> Luis,
>
> If you still have your zfs setup, could you please test the linked
> branch? You would only need to update /usr/lib/python3/dist-
> packages/provisioningserver/drivers/pod/
On Sat, Jan 18, 2020 at 12:37 AM Newell Jensen
wrote:
> $ virsh dumpxml
>
root@node35:~# virsh dumpxml testers
testers
ad6b59c9-76b5-4481-a0bb-dc896782f27e
1048576
1048576
1
hvm
destroy
restart
restart
Maybe one last thing, is that after I tried to create the machine in MAAS
and gave the error, it is not shown in MAAS composed machines, but it is
shown in virsh list --all, so I have to manually delete it
On Sat, Jan 18, 2020 at 9:15 AM Luis Alfonso Rodríguez Aragonés <
larago...@gmail.com> wrote
Yes.. what should I do?
On Fri, Jan 17, 2020 at 2:50 AM Newell Jensen
wrote:
> Luis,
>
> Do you still happen to have your zfs setup to get the requested
> information from (XMLs etc)? My setup was deleted and I have been busy
> with other higher priority items. Might take me a bit to get to th
It sounds like what I was getting.
On Thu, Jan 16, 2020 at 11:05 PM Colin Ian King <1799...@bugs.launchpad.net>
wrote:
> After quite a bit of experimentation I found that I can reproduce the bug
> if I have zram *and* also swap on the filesystem enabled while exercising
> the brk stressors and a
Please note that from MAAS you can't specify the size in KB, only in GB.
the command being executed is having the argument in KB.. And that
translation from 8GB to 8789063K is not a multiple of the block size of
8. THis is the command that is being executed from libvirt I suppose
(taken from the l
Hi.. I had to remove zram config from my production servers long ago. ...
since then I don't have the issue. I was using LXD containers a lot on the
hosts with different kind of usage,, But I don't have any other setup at
the moment
On Fri, Jan 10, 2020 at 12:11 AM Colin Ian King <1799...@bugs.la
OK.. it is been quite a while with no locks I had it once after the zram
config pacakge was removed,, but no other locks since then.
kernel version is 4.15.0-33 to 38 in different servers.. I am going to
update the servers to latest version reboot, and wait for a little
longer.
then I am going t
Got a hot locked with no zram-config installed.. Same behaviour, no log
information, can't even type in the console, no ssh, no ping. ALso all
the LXD containers don't ping either
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Correct.. I ould like to give it some more time to see if it doesn't
happen. So far so good, no lockups. I hadnt have to restart any server
in a week and a half.
I'll try to prepare the same setup on another server with zram-config to
see if it happens again on that particular server
--
You re
In my case it hasn't happen again.. Although I removed package zram-
config from the host servers ( I think this is the only difference in
software from 16.04 to 18.04 that I added. I would like to either
discard or confirm that that it has an effect on the issue
--
You received this bug notifi
Hello, I sumbitted the report on LXD since that is the only thing I have
installed on the server that is actively running as Stéphane mentioned
on https://github.com/lxc/lxd/issues/5197
I also thought it maybe hardware issue, but since upgrading to 18.04 in
May I have experienced this on a variety
thanks,
this
sudo apt install --reinstall shim-signed
didn't work for me.. still getting the same error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776271
Title:
Could not prepare Boot variable
I had flashed the latest firmware a few months back, did you re-flash
the same version or a new one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776271
Title:
Could not prepare Boot variable: No
Sure, this is happening on an IBM Tower System x3400 M3
Product name System x3400 M3
Machine type and model: 737954A
Firmware VPD
Firmware Type Version String Release Date
IMM YUOOH5A-1.55 01/15/2018
UEFI Y4E161A-1.17 06/07/2018
DSA DSYT83D-3.33 01/07/2011
--
You received this b
Same error after upgrade
root@node13:/boot/efi/EFI/ubuntu# efibootmgr -v
BootCurrent: 000D
Timeout: 10 seconds
No BootOrder is set; firmware will attempt recovery
Boot* CD/DVD RomVenMedia(0c588db8-6af4-11dd-a992-00197d890238,0c)
Boot0001* Floppy Disk VenMedia(0c588db8-6af4-11dd-a992-0019
Public bug reported:
No me reproduce sonido
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Public bug reported:
I dont know what is the problem.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.8.0-54-generic 4.8.0-54.57~16.04.1
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.1-0ubu
Public bug reported:
I dont know what is the problem.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.8.0-54-generic 4.8.0-54.57~16.04.1
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.1-0ubu
Public bug reported:
i don't kno what is the problem
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.8.0-54-generic 4.8.0-54.57~16.04.1
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.1-0ubun
Public bug reported:
I dont know
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.8.0-54-generic 4.8.0-54.57~16.04.1
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: am
problemas vinieron después de actualizar Ubuntu 10.10 ( este
funcionaba)
Gracias: J Luis Rodriguez.
2013/1/4 Adolfo Jayme Barrientos
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately, we cannot work on this bug because your
> descripti
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/999105
Title:
I dont update ubuntu 12.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/999105/+s
Public bug reported:
I dont understud very well English, I speak Spanish
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ubiquity 2.8.7
ProcVersionSignature: Ubuntu 3.0.0-19.33-generic 3.0.27
Uname: Linux 3.0.0-19-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Mon May 14
26 matches
Mail list logo