it would entail installing an upstream kernel, best on a test machine and if it's still the upstream behavior open a bug on https://bugzilla.kernel.org/
i don't have a a580 to test here at the moment so I can't do the test myself sadly
mhmm the only thing that stands out is that ASPM L1 is enabled on the working system while not on the not working one.
between those kernels there are only a few ASPM related changes, and only one is generic...
can you also attach a lspci output from a bad kernel?
EDIT: also please run lspci as root, otherwise some information is not visible there (such as the capabilities, etc.)
i forwarded this internally, not sure if we want to go against upstream here since the vfio-pci binding works already (and is recommended for passthrough anyway)
if you can reproduce with the upstream kernel, i'd report it on the official...
mhmm could you also check the -17, -18 and -19 kernels? this would shrink the possible regression window by a lot
from a good and a bad boot the following output would also be practical:
lspci -PP -vvv
can you try to turn off aspm for the device? e.g. via the kernel commandline: `amdgpu.aspm=0`
EDIT: or try to bind the card to vfio-pci before amdgpu with a vfio-pci.ids=<ids> (and maybe a softdep) see...
yes, this combination of modes would not really be desireable except if you're forcing a new media set (e.g. when doing a manual tape backup and check 'force new media-set')
no, as i said, we consider the media-set as smallest coherent unit...
for completeness sake i found bug report that seems to match: https://bugzilla.mozilla.org/show_bug.cgi?id=2016487
and it seems there is a fix which will lands in firefox 159
hi, please check if this happens with latest upstream firefox and report it there, since a 'normal' webpage shouldn't be able to crash the whole browser...
you're right that pbs does does not store multiple media sets on a single tape and every backup made with it is fully deduplicated (within one media set)
The idea here is that a media-set is the smallest consistent unit, so we'd recommend having...
no, not yet. but feel free to open an enhancement request here: https://bugzilla.proxmox.com
i think it makes sense to have maybe a 'table-like' resource view, similar to what the tree view widget + usage graphs could be
hi,
yeah this was probably just copied over from pve/pbs. There are currently no groups in PDM because nobody implemented it yet, and it seems there was not much demand for it yet.
you're right, the docs could be much better here. would you mind...
for that i sent a patch [0] to improve the error message in that case:
what should also have worked besides clearing out the tape manually would have been:
proxmox-tape format --drive <driveid>
(or clicking format in the webui)
this erases...
hi,
could you try to create a new user from the cli (pveum) with a very simple password and try that?
also a section from the journal during login would maybe help.
(it seems there are a few things not right on the system, the zpool, the rrd...
i couldn't reproduce it here yet, but the browser crashing doesn't sound like it's a fault on our side.
can you open firefox from the commandline and e.g. enable some debug logging to see if there is any hint where this might come from? anything...