On Wed, 2022-07-20 at 06:50 -0400, Sam Varshavchik wrote:
> Patrick O'Callaghan writes:
>
> > On Wed, 2022-07-20 at 13:20 +1000, Eyal Lebedinsky wrote:
> > >
> > >
> > > On 19/07/2022 14.39, Eyal Lebedinsky wrote:
> > > >
> > > > On 19/07/2022 07.42, Sam Varshavchik wrote:
> > > > > Am I the on
Patrick O'Callaghan writes:
On Wed, 2022-07-20 at 13:20 +1000, Eyal Lebedinsky wrote:
>
>
> On 19/07/2022 14.39, Eyal Lebedinsky wrote:
> >
> > On 19/07/2022 07.42, Sam Varshavchik wrote:
> > > Am I the only one lucky enough to have kernel-5.18.11-
> > > 200.fc36.x86_64 crash reliably, on partic
On Wed, 2022-07-20 at 13:20 +1000, Eyal Lebedinsky wrote:
>
>
> On 19/07/2022 14.39, Eyal Lebedinsky wrote:
> >
> > On 19/07/2022 07.42, Sam Varshavchik wrote:
> > > Am I the only one lucky enough to have kernel-5.18.11-
> > > 200.fc36.x86_64 crash reliably, on particular hardware, after
> > > s
On 19/07/2022 14.39, Eyal Lebedinsky wrote:
On 19/07/2022 07.42, Sam Varshavchik wrote:
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64 crash
reliably, on particular hardware, after starting a VM in virt-manager?
At least I think it's a crash. One second after a VM sta
On Jul 19, 2022, at 17:52, Sam Varshavchik wrote:
> No, there's nothing worthwhile to report. "Crashes with Qemu on some
> hardware" isn't a very useful bug report.
>
> Here's an example of a useful bug report: 2107827
>
> That one looks like like my bug, except that I do not have anything to
On 7/19/22 14:50, Sam Varshavchik wrote:
No, there's nothing worthwhile to report. "Crashes with Qemu on some
hardware" isn't a very useful bug report.
Post all you version numbers and post your XML file.
They should be able to reproduce for themselves
from there.
_
ToddAndMargo via users writes:
On 7/18/22 14:42, Sam Varshavchik wrote:
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64 crash
reliably, on particular hardware, after starting a VM in virt-manager?
At least I think it's a crash. One second after a VM start it's brick-cit
On 7/18/22 14:42, Sam Varshavchik wrote:
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64
crash reliably, on particular hardware, after starting a VM in
virt-manager?
At least I think it's a crash. One second after a VM start it's
brick-city. Display frozen, no response f
On 19/07/2022 07.42, Sam Varshavchik wrote:
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64 crash
reliably, on particular hardware, after starting a VM in virt-manager?
At least I think it's a crash. One second after a VM start it's brick-city.
Display frozen, no respons
On Mon, 2022-07-18 at 17:42 -0400, Sam Varshavchik wrote:
> But, these days, no more RS-232 ports.
If it's not a laptop, there may still be one. But just on a header
that needs a flylead to an external connector.
--
uname -rsvp
Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28 UTC
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64 crash
reliably, on particular hardware, after starting a VM in virt-manager?
At least I think it's a crash. One second after a VM start it's brick-city.
Display frozen, no response from the network. I've got nothing: after
11 matches
Mail list logo
