On Thu, Sep 5, 2019 at 9:00 PM Bastien Nocera wrote:
> Daniel, if you run into many more problems, there's also the
> possibility of adding a boot argument to disable the accelerometer (or
> maybe its effects?), either in iio-sensor-proxy or gnome-shell.
Thanks for the suggestion, manually adding
On Thu, Sep 5, 2019 at 6:07 PM Bastien Nocera wrote:
> I've read through this, and I'm happy blacklisting the hp_accel driver
> in code. For the other devices, I'd rather leave it as-is.
That would indeed avoid most problem cases that I've seen, and the
current case, probably enough to stop me gr
Hi,
Over the years we've seen a bunch of reports of systems that
automatically rotate the display to some incorrect orientation, based
on trusting some accelerometer data values which were not interpreted
correctly. I have another affected system in hand here.
When this unfortunate situation happ
On Thu, Nov 15, 2018 at 7:04 PM Michal Koutný wrote:
> @Daniel, is it possible there are some daemon-reloads running
> concurrently with the timer? More precisely, can it happen the timer
> expires exactly when systemd reloads?
I don't think so. The journal only show a single "systemd[1]:
Reloadi
On Thu, Nov 8, 2018 at 6:46 PM Andrei Borzenkov wrote:
> It is possible that system never ends booting. Do you have any pending
> jobs (systemctl list-jobs)? What "systemctl is-system-running" says?
Thanks for the suggestion! It sounds like a good one - I did reproduce
this on first boot and we d
Hi,
On Endless we have the following eos-autoupdater.timer:
[Unit]
Description=Endless OS Automatic Update Timer
Documentation=man:eos-autoupdater(8)
ConditionKernelCommandLine=!endless.live_boot
ConditionKernelCommandLine=ostree
[Timer]
OnBootSec=15m
OnUnitInactiveSec=1h
Rando
On Thu, Apr 23, 2015 at 9:32 AM, Lennart Poettering
wrote:
>> +Beyond the main process
>> +
>> + The KillMode= option primarily defines
>> + behavior up until the point where the main process has gone away.
>> + systemd expects that when killed with the signal specified by
>> +
While looking at the exact behavior of how systemd stops services,
I encountered some behavior that wasn't clear from reading the man
page.
Specifically, if the main process exits before its children, the child
processes will actually receive a second SIGTERM. If that doesn't
kill them, they will
On Mon, Apr 20, 2015 at 6:29 PM, Lennart Poettering
wrote:
> Sure, we don't want to keep track of which processes we already
> killed, to distuingish them from the processes newly created in the
> time between our sending of SIGTERM and receiving SIGCHLD for the main
> process.
>
> We assume that
On Mon, Apr 20, 2015 at 6:04 PM, Lennart Poettering
wrote:
>> I have stepped through and I think that systemd is being too
>> aggressive. Still running with the default KillMode=cgroup, here is
>> what happens:
>>
>> 1. service_enter_stop() is entered which calls:
>> service_enter_
On Mon, Apr 20, 2015 at 9:04 AM, Lennart Poettering
wrote:
> maybe the main gdm process is not the one waiting, but a worker
> process is, and the main process kills the worker process without the
> worker process handling that nicely?
Not really. I removed all the process-killing code from gdm a
On Mon, Apr 20, 2015 at 8:24 AM, Lennart Poettering
wrote:
> On Sun, 19.04.15 09:34, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
>> В Fri, 17 Apr 2015 14:04:18 -0600
>> Daniel Drake пишет:
>>
>> > Hi,
>> >
>> > I'm investigating why
Hi,
I'm investigating why "systemctl stop gdm; Xorg" usually fails. The
new X process complains that X is still running.
Here's what I think is happening:
1. systemd sends SIGTERM to gdm to stop the service
2. gdm exits - it has a simple SIGTERM handler which just quits the
mainloop without doi
On Sat, Apr 11, 2015 at 5:13 AM, David Herrmann wrote:
> Nice catch!
>
> There's indeed a small race between handling inotify and queuing up
> the change-event. We need to re-loop there. One day we should switch
> to sd-event to avoid such bugs... I mean the symptom is inherent to
> queuing up eve
udev uses inotify to implement a scheme where when the user closes
a writable device node, a change uevent is forcefully generated.
In the case of block devices, it actually requests a partition rescan.
This currently can't be synchronized with "udevadm settle", i.e. this
is not reliable in a scri
Hi,
On Sun, Mar 8, 2015 at 3:50 PM, Lennart Poettering
wrote:
> On Fri, 06.03.15 14:22, Daniel Drake (dr...@endlessm.com) wrote:
> To my knowledge newer versions don't do this anymore and actively
> watch drm devices coming.
I'm describing the behaviour of the newer version
Hi,
I'm looking at some issues with the plymouth boot splash system, and
why it intermittently fails to get graphics on screen.
plymouth watches for the creation of drm display devices during boot.
If it finds one, it starts a graphical splash and that is that.
However, if the system finishes loa
On Wed, Jul 2, 2014 at 1:36 PM, Lennart Poettering
wrote:
>> Then the system continues booting, switches root, and then
>> system-fsck-root.service starts from the root fs, and runs fsck on /
>> again. This is the bit I don't understand - we already checked from
>> the initramfs, why check again n
On Wed, Jul 2, 2014 at 1:13 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> Thinking about it, I'm not sure how the new systemd would know that
> systemd-fsck@dev-something.service from the initramfs is the same
> thing as systemd-fsck-root.service. Maybe that's the problem?
>
> Currently systemd-fsck-ro
Hi,
I'm trying to understand dracut/systemd fsck behaviour, in the context
of an ext4 filesystem root mounted read-only from dracut, remaining
read-only even when the system is fully booted (kiosk-style).
I see that systemd's fstab-generator rightly creates a mount unit for
/sysroot from the init
On Mon, Nov 19, 2012 at 7:57 PM, Lennart Poettering
wrote:
> parted is actually capable of doing this properly and settles the
> device. Have you looked into that?
Looks like as of version 3.0, parted can no longer resize partitions.
The functionality got dropped.
Daniel
Hi,
At OLPC we use sfdisk to grow a partition from the initramfs on first boot.
However, we are finding this to be unreliable. Working with Fedora 18,
systemd-195, and OLPC XO-4 hardware.
The core of the problem seems to be udev's response to BLKRRPART - the
ioctl used to ask the kernel to re-re
On Mon, Oct 29, 2012 at 7:19 PM, Lennart Poettering
wrote:
>> One more thing to add:
>>
>> It looks like /etc/sysconfig/network is still being parsed even though
>> the above link suggests otherwise. Putting HOSTNAME=myhostname in
>> /etc/sysconfig/network sets the default transient hostname. Hmm.
On Mon, Oct 29, 2012 at 1:33 PM, Daniel Drake wrote:
> I'm working on updating OLPC configuration for systemd-195 based on this info:
> http://lists.fedoraproject.org/pipermail/test/2012-October/111230.html
>
> I can't quite figure out the hostname thing.
One more thing
Hi,
I'm working on updating OLPC configuration for systemd-195 based on this info:
http://lists.fedoraproject.org/pipermail/test/2012-October/111230.html
I can't quite figure out the hostname thing.
We need to set unique hostnames for avahi; machines with the same name
cannot collaborate. Also,
Hi,
Not sure whether to submit a bug report or documentation patch for this.
ExecStart=/usr/bin/foo --arg1="foo bar"
Causes foo to be run with 2 command line args:
1. --arg1="foo
2. bar"
Not what I was hoping for.
Whereas:
ExecStart=/usr/bin/foo "--arg1=foo bar"
does what I want, just 1 c
On Wed, Aug 8, 2012 at 10:56 AM, Lennart Poettering
wrote:
> I don't think anything can be considered "clean" if it involves setting
> system-wide env vars. There must be another way to teach Python
> optimization system-wide...
I have yet to find the other way that you mention.
Anyway, I can agr
On Mon, Aug 6, 2012 at 3:09 PM, Kay Sievers wrote:
> systemctl set-environment ... ?
Maybe thats what I read about.
In this case I'm looking to set it in early boot though, so that it
affects all spawned processes from the very start. Is there a nice way
of doing this?
> But it's in almost all
Hi,
I thought I read somewhere that systemd offers a mechanism to set an
environment variable system-wide - i.e. the variable assignment will
be present in all the processes started by systemd.
But I can't find where I read this, or how to use it.
Does this functionality exist or am I getting co
On Wed, Jul 4, 2012 at 11:46 AM, Daniel Drake wrote:
> We're encountering a systemd hang on reboot which is proving hard to
> debug, on the OLPC XO platform (systemd-44 on Fedora 17). It doesn't
> happen every time, but it is frequent: when running a system that
> reboots
Hi,
We're encountering a systemd hang on reboot which is proving hard to
debug, on the OLPC XO platform (systemd-44 on Fedora 17). It doesn't
happen every time, but it is frequent: when running a system that
reboots once every 2-3 minutes, it reproduces with an hour (usually
much quicker). Can any
On Fri, Jun 1, 2012 at 4:03 AM, Michal Schmidt wrote:
> On 05/31/2012 05:46 PM, Daniel Drake wrote:
>>
>> In the case of reboot (or poweroff), what does this mean?
>> plymouth-reboot.service is queued to start, and prefdm.service is
>> queued to stop. What does After
On Wed, Apr 11, 2012 at 10:51 AM, Daniel Drake wrote:
> On Wed, Apr 11, 2012 at 9:42 AM, Lennart Poettering
> wrote:
>>> I tried modifying e.g. plymouth-reboot.service to have:
>>> Before=reboot.service shutdown.target umount.target final.target
>>> reboot.ta
Hi,
On Wed, Apr 25, 2012 at 9:46 AM, Daniel Drake wrote:
> This reverts commits d72238fcb34abc81aca97c5fb15888708ee937d3 and
> f3accc08.
>
> OLPC runs / as a bind-mount, so this must be remounted RO during
> shutdown to avoid corruption.
>
> As Lennert can't recall th
This reverts commits d72238fcb34abc81aca97c5fb15888708ee937d3 and
f3accc08.
OLPC runs / as a bind-mount, so this must be remounted RO during
shutdown to avoid corruption.
As Lennert can't recall the exact reasons for making the shutdown
code skip bind mounts, revert to previous behaviour to solve
Hi Lennart,
On Thu, Apr 12, 2012 at 8:46 AM, Daniel Drake wrote:
> The mmcblk0p2 message above suggests that / is being re-mounted
> readonly, and also on next boot the system no longer complains about /
> not being cleanly unmounted. Tested with 3 reboots to be sure.
>
> Revertin
On Thu, Apr 12, 2012 at 4:56 AM, Lennart Poettering
wrote:
> I think I added this logic primarily to make the shutdown loop quiet.
>
> However I must admit that that's just a guess and since my commit
> message is disappointingly unconclusive about this I am a bit lost...
>
> If you revert f3accc0
On Wed, Apr 11, 2012 at 9:42 AM, Lennart Poettering
wrote:
>> I tried modifying e.g. plymouth-reboot.service to have:
>> Before=reboot.service shutdown.target umount.target final.target
>> reboot.target
>
> That suggests that the plymouth client tool is not waiting for the
> operation to finish b
On Wed, Apr 11, 2012 at 9:40 AM, Lennart Poettering
wrote:
> So on shutdown after stopping all services we execute systemd-shutdown
> as PID 1 replacing the normal systemd process. This is useful to drop
> all references to files on disk, so that we can remount the disk r/o
> even on upgrades.
>
>
Hi,
As can be seen in my logs of a reboot:
http://dev.laptop.org/~dsd/20120411/shutdown.txt
The plymouth shutdown splash is being shown really quite late.
As systemd shuts down fantastically fast, this means that our pretty
shutdown graphic is not being drawn on OLPC laptops. Sometimes the
image
Hi,
On OLPC laptops we are seeing that ext4 complains on every boot that
the filesystem wasn't cleanly unmounted.
Looking at systemd debug logs of a shutdown would seem to agree, I
can't see where it attempts to remount / read-only as was done with
sysvinit.
http://dev.laptop.org/~dsd/20120411/s
On Tue, Apr 10, 2012 at 6:21 AM, Kay Sievers wrote:
> Libattr and libcap are gone now from the tools which do not need them:
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=d7832d2c6e0ef5f2839a2296c1cc2fc85c7d9632
Great! Thanks for slimming up my initramfs a bit :)
Daniel
_
On Wed, Apr 4, 2012 at 2:02 PM, Kay Sievers wrote:
> Right, when udevadm is there, then there is udevd, which definitely
> needs all of them.
Thats a good point - and if udevd really needs them, then there's no escaping.
So I guess there is nothing to gain here :(
Daniel
On Wed, Apr 4, 2012 at 10:53 AM, Daniel Drake wrote:
> However, dropping the link against libcap (which also includes
> libattr) would be nice. Here is a patch to do that.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.or
On Wed, Apr 4, 2012 at 10:36 AM, Daniel Drake wrote:
> But with selinux included, the task is more complicated. For example,
> label.c (part of libsystemd-basic) also uses libselinux, so we need to
> move it out somewhere else (lets say we put it in a new library:
> libsystemd-ext
Hi,
On Tue, Nov 1, 2011 at 4:39 PM, Lennart Poettering
wrote:
> Hmm, let me see if I get this right: with this patch applied we'd build
> cap and selinux support into libsystemd-basic.la, but we wouldn't link
> against the respective libraries but instead do that in the binaries
> which pull in t
Hi,
Running systemd-36 on Fedora 16.
$ ldd /lib/systemd/systemd-timestamp
linux-gate.so.1 => (0x00a84000)
libselinux.so.1 => /lib/libselinux.so.1 (0x0059c000)
libcap.so.2 => /lib/libcap.so.2 (0x00901000)
librt.so.1 => /lib/librt.so.1 (0x00a6a000)
libc.so.6
On Tue, Oct 11, 2011 at 1:44 AM, Lennart Poettering
wrote:
> So this is a the big issue here I believe. If you look at 87.293308
> you'll see that tmp.mount is suddenly mounted again for some reason,
> which systemd then takes as hint to get rid of
> poweroff.target/poweroff.service, since they co
On Thu, Sep 29, 2011 at 2:29 PM, Daniel Drake wrote:
> Full log of startup, shutdown, and sysrq dumps at point of first hang
> (before systemd-stdout-syslog-bridge.service wakeup), and second hang,
> then sysrq dumps again:
> http://dev.laptop.org/~dsd/20110929/systemd-shutdown-ha
On Wed, Sep 28, 2011 at 4:03 PM, Lennart Poettering
wrote:
> Hmm, so I don't see any obvious either.
I dug a little further. I have enabled lockdep to see if it can find
any deadlocks, and nothing comes up.
I also turned to sysrq-D (show locks held) - no locks are held at the
point of hang.
sys
On Tue, Sep 27, 2011 at 9:50 PM, Lennart Poettering
wrote:
> Boot with "systemd.log_level=debug" and "systemd.log_target=kmsg" on the
> kernel cmdline. Then shutdown and look at the output that is generated
> then. If you find nothing useful in it, please paste it somewhere so
> that I can have a
Hi,
Revisiting running recent Fedora versions on OLPC XO. This is a Fedora
spin with a custom kernel (which is now really just mainline but with
our own config).
One problem that we've always had since the systemd switch, which I've
never really investigated, is that shutdown never completes.
A
On 15 May 2011 15:16, Kay Sievers wrote:
> Just a first quick check of an issue we ran into with ATA disks:
> what's in /proc/sys/kernel/hotplug before you shut down? Or what's
> CONFIG_UEVENT_HELPER in your kernel setup, it must be ="" on modern
> systems, otherwise the kernel will they to exec()
On 10 May 2011 22:26, Daniel Drake wrote:
> If I log the error after it tries to connect to /run/systemd/private, I get:
> Failed to connect to socket /run/systemd/private: No such file or directory
>
> Indeed, there's nothing at that path, and the only thing in
> /run/
On 9 May 2011 22:46, Lennart Poettering wrote:
> You are lacking autofs4 support in the kernel. You should fix this first.
I'm not, autofs4 is present, we're working on figuring out on why
systemd complains at
https://bugs.freedesktop.org/show_bug.cgi?id=36993
> Your udev in your initrd is a dif
Hi,
Another systemd error I am encountering is:
Failed to get D-Bus connection: Failed to connect to socket
/org/freedesktop/systemd1/private: Connection refused
The message appears a lot throughout boot, full logs here:
http://dev.laptop.org/~dsd/20110509/systemd-boot.txt
It also means I can't
On 9 May 2011 11:50, Kay Sievers wrote:
> Works all fine here with:
> # grep SECURITY .config
> CONFIG_EXT3_FS_SECURITY=y
> CONFIG_EXT4_FS_SECURITY=y
> # CONFIG_SECURITY_DMESG_RESTRICT is not set
> # CONFIG_SECURITY is not set
> # CONFIG_SECURITYFS is not set
> CONFIG_DEFAULT_SECURITY_DAC=y
On 7 May 2011 23:43, Daniel Drake wrote:
> On 7 May 2011 23:30, Kay Sievers wrote:
>> You need capabilities in your kernel, or comment its use out, in the
>> service file.
>
> I think I have capabilities in my kernel: CONFIG_SECURITY=y which
> means security/capability.
On 7 May 2011 23:30, Kay Sievers wrote:
> You need capabilities in your kernel, or comment its use out, in the
> service file.
I think I have capabilities in my kernel: CONFIG_SECURITY=y which
means security/capability.c gets compiled in. Were you thinking of
something else?
Commenting out Capab
On 7 May 2011 21:49, Gustavo Sverzut Barbieri wrote:
> maybe need CONFIG_DEVTMPFS_MOUNT=y as well? But yeah, take a look
> from top->bottom in the log, don't bother investigating the last
> messages if there are errors before them.
CONFIG_DEVTMPFS_MOUNT is only for non-initramfs boot. I enabled
On 7 May 2011 21:23, Gustavo Sverzut Barbieri wrote:
> Failed to initialize automounter: No such file or directory
>
> This one is a big thing. Compile your kernel with autofs support. You
> don't need any userspace program, but you need this in the kernel so
> systemd works.
>
> You better ch
Hi,
Just built a Fedora rawhide-based image for the XO-1.5 laptop,
including systemd v26.
This is not "pure Fedora", it doesn't use the comps system/base
groups, so may be missing important things. No plymouth or selinux,
for example. We also use a custom kernel instead of Fedora's. So
perhaps I'
Hi Lennart,
On 8 March 2011 19:30, Lennart Poettering wrote:
> Heya,
>
> Mostly bugfixes:
>
> http://www.freedesktop.org/software/systemd/systemd-20.tar.bz2
Any chance of a build for Fedora rawhide? Latest there is v18.
Thanks,
Daniel
___
systemd-deve
On 7 September 2010 05:54, Lennart Poettering wrote:
>
> [Unit]
> Description=OLPC Configuration
> DefaultDependencies=no
> After=sysinit.target local-fs.target
> Before=base.target
>
> [Service]
> Type=oneshot
> ExecStart=/usr/bin/olpc-configure
>
> [Install]
> WantedBy=base.target
>
I assume
Hi,
First time user question...
The OLPC-Fedora distro needs to run a script early during boot. This
configures a few important things (particularly on first boot) such as
setting up the system locale and X config.
With sysvinit and its serialized nature, this was easy (just an init
script that
65 matches
Mail list logo
