Dear Ulrich，
Thanks for your suggest. I have added some debug info, but not display. I will
add more.
I want ask a question, What commands does udevadm in systemd execute and what
functions are corresponding to the driver?
thanks,
Byron
At 2019-10-15 20:36:41, "Ulrich Windl"
wrote:
On Tue, Oct 15, 2019 at 3:02 PM www wrote:
> Dear all,
>
> I add a new driver to kernel, and it probe success. When enter into
> systemd, the udevadm generate a kernel panic.
> I want to ask how to debug it and find out where the error occurred? When
> did udevadm load? What commands are used by
* flock leaves the lock file behind so you'd need some type of
cleanup in case you really want the jobs to be trace-free. This is
not as trivial is it might seem, e.g. you cannot do it from the
service units themselves in `ExecStartPost=` or similar.
An
ExecStartPost=-/usr/bin/flock -F
I initiated an unsubscribe from this web page:
https://lists.freedesktop.org/mailman/options/systemd-devel
That created a confirmation email, that I replied to.
That yielded this bounce message:
:
131.252.210.177 does not like recipient.
Remote host said: 550 5.1.1 :
Recipient
Moji, Shashidhar wrote on 15/10/2019 05:15:
> Hi,
>
> We have VMware vApp based solution. Our application gets installed
> during first boot.
>
> Till now we had SLES11 OS based VM and we upgraded to SLES12. Now we
> have systemd instead of init scripts for service handling.
>
> In SLES11, we
Am 15.10.19 um 06:15 schrieb Moji, Shashidhar:
> We have VMware vApp based solution. Our application gets installed
> during first boot.
>
> Till now we had SLES11 OS based VM and we upgraded to SLES12. Now we
> have systemd instead of init scripts for service handling.
>
> In SLES11, we had
Am Montag, den 14.10.2019, 18:30 +0200 schrieb Alexander Koch:
> > exactly for this you would use a flock(1) in your .service.
>
> Thanks for the hint, didn't have that in mind. So you're suggesting
> something like this?
>
> # service-a.service
> # (...)
> [Service]
>
Dear all,
I add a new driver to kernel, and it probe success. When enter into systemd,
the udevadm generate a kernel panic.
I want to ask how to debug it and find out where the error occurred? When did
udevadm load? What commands are used by udevadm, and what are the specific
operations?
[
Hi!
I think your driver loads OK, but it is not working correctly. Maybe enable
kernel debug messages and add debug prints to your driver, especially regarding
any queries. I suspect some NULL pointer or empty string being returned.
Regards,
Ulrich
>>> www schrieb am 15.10.2019 um 13:46 in
