On Sun, May 19, 2019, 3:33 PM Olaf van der Spek wrote:
> On Sun, May 19, 2019 at 2:31 PM tedheadster wrote:
> >
> > On Sun, May 19, 2019 at 7:31 AM Olaf van der Spek wrote:
> > >
> > > What's eax after cpuid function 0?
> >
> > After calling cpuid function 0x0, %eax returns the expected 0x1.
>
On Sun, May 19, 2019 at 2:31 PM tedheadster wrote:
>
> On Sun, May 19, 2019 at 7:31 AM Olaf van der Spek wrote:
> >
> > What's eax after cpuid function 0?
>
> After calling cpuid function 0x0, %eax returns the expected 0x1.
>
> Here is the output of 'cpuid -r'.
>
> # cpuid -r
> CPU 0:
>0x
Hello.
What is the proper way to do that? I have a unit that creates gvt device in the
system
ExecStart = "sh -c 'echo a297db4a-f4c2-11e6-90f6-d3b88d6c9525 >
/sys/bus/pci/devices/:00:02.0/mdev_supported_types/i915-GVTg_V5_8/create'";
ExecStop = "sh -c 'echo 1 >
/sys/bus/pci/devices/:00:
On Sun, May 19, 2019 at 7:31 AM Olaf van der Spek wrote:
>
> What's eax after cpuid function 0?
After calling cpuid function 0x0, %eax returns the expected 0x1.
Here is the output of 'cpuid -r'.
# cpuid -r
CPU 0:
0x 0x00: eax=0x0001 ebx=0x746e6543 ecx=0x736c7561 edx=0x48727561
On Sat, May 11, 2019 at 7:19 PM tedheadster wrote:
>
> On Sat, May 11, 2019 at 12:30 PM Florian Weimer wrote:
> > Can you capture register contents at the point of the crash?
> >
> > Does this reproduce in a chroot? Maybe you can trace the whole thing
> > with a debugger. Does the crash reprodu
On Sun, May 19, 2019 at 11:26 AM Reindl Harald
wrote:
>
>
> Am 19.05.19 um 11:45 schrieb Olaf van der Spek:
> > ExecStartPre is sometimes used to check the configuration. Does this
> make sense?
> > It seems this causes a lot of code to run twice, as the configuration
> > is checked on the real i
Am 19.05.19 um 11:45 schrieb Olaf van der Spek:
> ExecStartPre is sometimes used to check the configuration. Does this make
> sense?
> It seems this causes a lot of code to run twice, as the configuration
> is checked on the real invocation anyway.
>
> [Unit]
> Description=Lighttpd Daemon
> Aft
Hi,
ExecStartPre is sometimes used to check the configuration. Does this make sense?
It seems this causes a lot of code to run twice, as the configuration
is checked on the real invocation anyway.
[Unit]
Description=Lighttpd Daemon
After=network-online.target
[Service]
Type=simple
PIDFile=/var/r
