On 18 November 2015 at 18:23, Michael Biebl wrote:
> Am 18.11.2015 um 18:35 schrieb Steven Capper:
> > Upgrading to 227-1 caused immediate segfaults and led to the same
> > unbootable machine.
> >
> > So it looks like something introduced 227-1.
>
> I would guess this was introduced by
>
>
> http
Am 18.11.2015 um 18:35 schrieb Steven Capper:
> Upgrading to 227-1 caused immediate segfaults and led to the same
> unbootable machine.
>
> So it looks like something introduced 227-1.
I would guess this was introduced by
https://github.com/poettering/systemd/commit/75f86906c52735c98dc0aa7e24b77
Hello,
Steven Capper [2015-11-18 15:52 +]:
> I neglected to mention that this running under a QEMU virtual machine (same
> error for both KVM acceleration on and off).
As a data point: I can boot arm64 instances in our cloud, and systemd
225 on Linux 4.2.0 works fine. But I don't know which k
On 18 November 2015 at 17:20, Michael Biebl wrote:
> Hi Steve,
>
> Am 18.11.2015 um 16:52 schrieb Steven Capper:
> > I neglected to mention that this running under a QEMU virtual machine
> (same
> > error for both KVM acceleration on and off).
> >
> > I will dig into this a little bit here and wi
Hi Steve,
Am 18.11.2015 um 16:52 schrieb Steven Capper:
> I neglected to mention that this running under a QEMU virtual machine (same
> error for both KVM acceleration on and off).
>
> I will dig into this a little bit here and will update if I find anything.
Can you pinpoint the version when th
I neglected to mention that this running under a QEMU virtual machine (same
error for both KVM acceleration on and off).
I will dig into this a little bit here and will update if I find anything.
Cheers,
--
Steve
6 matches
Mail list logo
