Re: [systemd-devel] sd-bus delayed reply

[Jean Valjean]

I feel like Tom Hanks in the Cast Away when he made fire. Thank you.

Boris


On Mon, 28 Jan 2019 at 14:07, Lennart Poettering  wrote:
>
> On Mo, 28.01.19 14:00, Jean Valjean (valjean.jean1...@gmail.com) wrote:
> 65;5403;1c
> > Can I, in principle, register objects and interfaces with
> > sd_bus_add_object_vtable like in
> > http://0pointer.net/blog/the-new-sd-bus-api-of-systemd.html
> > and in handler function, take a copy, of a reference to message
> > object, to global variable and use it later with
> > sd_bus_reply_method_return?
> > I tried to do that. But it seems, that when handler function returns,
> > it sends an error message to calling client if
> > sd_bus_reply_method_return
> > was not called inside handler.
>
> Depends on what you return in the handler function:
>
> 1. Returning < 0 means sd-bus will generate an automatic error reply
>for you, taking the returned value as negative errno (or looking
>into the sd_bus_error struct passed to you, which takes
>precedence).
>
> 2. Returning 0 means it will generate an automatic response suggesting
>that the method call was not handled.
>
> 3. Returning > 0 means however that you handled the message, and
>sd-bus will not generate any reply.
>
> Hence, just exit your function with "return 1" if you don't want any
> automatic reply to be generated and all is good.
>
> (The above applies to all msg handler functions in sd-bus
> basically. The reason for doing #2 is that if you install filter
> functions that are called on every single incoming msg you can decide
> by returning 0 or 1 whether further filter functions shall be called,
> or not)
>
> Lennart
>
> --
> Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Fail to load network modules properly

[Łukasz Słaboń]

Yes, as far as I know it should load firmware. Is there a possibility to
force loading wl driver and module only after partition is mounted? I
assume that something systemd scripts needs to be changed to force
different boot sequence.

Regards,

Łukasz Słaboń


On Mon, Jan 28, 2019 at 10:48 AM juice  wrote:

> Łukasz Słaboń kirjoitti 2019-01-28 11:18:
> > Apparently the same bug is in the open-source driver. As I said in my
> > previous e-mail I'm experiencing same problem with all possible
> > drivers for my wifi card.
> >
> > Regards,
> >
> > Łukasz Słaboń
>
>
> Does your driver require firmware to be loaded before operation?
> Is it possible that if the driver starts early enough your /lib/firmware
> is not on a mounted partition (or not on initramfs)
>
>- juice -
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Bugfix release(s)

[Ryan Gonzalez]

>From here everything looks good!

On Mon, Jan 28, 2019 at 7:39 AM Lennart Poettering 
wrote:

> On Mo, 28.01.19 14:32, Lennart Poettering (lenn...@poettering.net) wrote:
>
> > On Sa, 26.01.19 16:56, Ryan Gonzalez (rym...@gmail.com) wrote:
> >
> > > I'll send you the webhook target and webhook secret in a PGP-encrypted
> > > email off-list (maybe overkill, but better safe than sorry).
>
> It's set up now. I used the JSON submission format, and github said a
> ping succeeded. Does everything look OK from your side too? If so, we
> can probably tag v240-rc2 or so today, as a test case for this.
>
> Please let me know when you think all is set up properly. I'll then
> do the rc2 tag.
>
> Lennart
>
> --
> Lennart Poettering, Red Hat
>


-- 
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Bugfix release(s)

[Lennart Poettering]

On Mo, 28.01.19 14:32, Lennart Poettering (lenn...@poettering.net) wrote:

> On Sa, 26.01.19 16:56, Ryan Gonzalez (rym...@gmail.com) wrote:
>
> > I'll send you the webhook target and webhook secret in a PGP-encrypted
> > email off-list (maybe overkill, but better safe than sorry).

It's set up now. I used the JSON submission format, and github said a
ping succeeded. Does everything look OK from your side too? If so, we
can probably tag v240-rc2 or so today, as a test case for this.

Please let me know when you think all is set up properly. I'll then
do the rc2 tag.

Lennart

--
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Bugfix release(s)

[Lennart Poettering]

On Sa, 26.01.19 16:56, Ryan Gonzalez (rym...@gmail.com) wrote:

> I'll send you the webhook target and webhook secret in a PGP-encrypted
> email off-list (maybe overkill, but better safe than sorry).
>
> As a side note, the bot currently watches tags. Would it be better to watch
> releases, or will tags be fine for now?

Hmm, I must admit that I don't fully grasp the semantical differences
between both. So far we have always generated a release from every
single tag, hence the difference doesn't really matter to us.

Maybe I am missing something but I am not sure we actually care about
the "Release" concept in github so much, and for us it's just some
extra step we have to manually do on each release, and we'd rather
not. Because of that I think watching tags is fine and preferable)

(Unless I am missing something we'd like an automatism that makes
every tag that matches the regexp /^v[0-9]+$/ a github release and
every tag that matches the regexp /^v[0-9]+-rc[0-9]+$/ a github
pre-release, and ignore all others, which is pretty much what you
implemented for the mail notifier thing too.)

Anyway, I think the current implementation is fine hence (but maybe I
am just not fully grasping the "Release" concept in GitHUB).

Lennart

--
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Systemd-analyze time not giving kernal bootup time.

[deepan muthusamy]

"systemd-analyze time" directly provides time.
I don't know about journalctl MESSAGE_ID.

On Mon, 28 Jan 2019, 5:40 pm Mantas Mikulėnas  On Mon, Jan 28, 2019 at 11:22 AM deepan muthusamy 
> wrote:
>
>> My target(RCAR-H3) runs with yocto project have boot up time of 13
>> seconds before init starts as of my observation. because I am starting
>> Weston in basic.target which is starting after 13 seconds from the time I
>> pressed power button.
>>
>> Note: I am booting the board from SD card(The image is in SD card).
>>
>> "Systemd-analyze time " giving "Startup finished in 11.814s(userspace) =
>> 13.519s".
>> It is not giving kernal bootup time.
>>
>
> Which timestamps do you see from:
>
> journalctl MESSAGE_ID=b07a249cd024414a82dd00cd181378ff
>
> journalctl MESSAGE_ID=eed00a68ffd84e31882105fd973abdd1
>
> --
> Mantas Mikulėnas
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Systemd-analyze time not giving kernal bootup time.

[deepan muthusamy]

The systems version is "systemd 230".

I'm not sure about what the container is. My system having only one user
(root). No other users.

On Mon, 28 Jan 2019, 2:56 pm Jérémy ROSEN  What version of systemd are you using ?
>
> Kernel time is usually not displayed when systemd is run inside a
> container (since it makes no sense). There might be something wrong with
> container detection here, though...
>
> Le lun. 28 janv. 2019 à 10:22, deepan muthusamy 
> a écrit :
>
>> My target(RCAR-H3) runs with yocto project have boot up time of 13
>> seconds before init starts as of my observation. because I am starting
>> Weston in basic.target which is starting after 13 seconds from the time I
>> pressed power button.
>>
>> Note: I am booting the board from SD card(The image is in SD card).
>>
>> "Systemd-analyze time " giving "Startup finished in 11.814s(userspace) =
>> 13.519s".
>> It is not giving kernal bootup time.
>> Help me with this.
>>
>>
>> ___
>> systemd-devel mailing list
>> systemd-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>
>
> --
> [image: SMILE]  
>
> 20 rue des Jardins
> 92600 Asnières-sur-Seine
> *Jérémy ROSEN*
> Architecte technique
>
> [image: email] jeremy.ro...@smile.fr
> [image: phone]  +33 6 88 25 87 42
> [image: url] http://www.smile.eu
>
> [image: Twitter]  [image: Facebook]
>  [image: LinkedIn]
>  [image: Github]
> 
>
> [image: Découvrez l’univers Smile, rendez-vous sur smile.eu]
> 
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Systemd-analyze time not giving kernal bootup time.

[Mantas Mikulėnas]

On Mon, Jan 28, 2019 at 11:22 AM deepan muthusamy 
wrote:

> My target(RCAR-H3) runs with yocto project have boot up time of 13 seconds
> before init starts as of my observation. because I am starting Weston in
> basic.target which is starting after 13 seconds from the time I pressed
> power button.
>
> Note: I am booting the board from SD card(The image is in SD card).
>
> "Systemd-analyze time " giving "Startup finished in 11.814s(userspace) =
> 13.519s".
> It is not giving kernal bootup time.
>

Which timestamps do you see from:

journalctl MESSAGE_ID=b07a249cd024414a82dd00cd181378ff

journalctl MESSAGE_ID=eed00a68ffd84e31882105fd973abdd1

-- 
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] sd-bus delayed reply

[Lennart Poettering]

On Mo, 28.01.19 14:00, Jean Valjean (valjean.jean1...@gmail.com) wrote:
65;5403;1c
> Can I, in principle, register objects and interfaces with
> sd_bus_add_object_vtable like in
> http://0pointer.net/blog/the-new-sd-bus-api-of-systemd.html
> and in handler function, take a copy, of a reference to message
> object, to global variable and use it later with
> sd_bus_reply_method_return?
> I tried to do that. But it seems, that when handler function returns,
> it sends an error message to calling client if
> sd_bus_reply_method_return
> was not called inside handler.

Depends on what you return in the handler function:

1. Returning < 0 means sd-bus will generate an automatic error reply
   for you, taking the returned value as negative errno (or looking
   into the sd_bus_error struct passed to you, which takes
   precedence).

2. Returning 0 means it will generate an automatic response suggesting
   that the method call was not handled.

3. Returning > 0 means however that you handled the message, and
   sd-bus will not generate any reply.

Hence, just exit your function with "return 1" if you don't want any
automatic reply to be generated and all is good.

(The above applies to all msg handler functions in sd-bus
basically. The reason for doing #2 is that if you install filter
functions that are called on every single incoming msg you can decide
by returning 0 or 1 whether further filter functions shall be called,
or not)

Lennart

--
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] sd-bus delayed reply

[Jean Valjean]

Can I, in principle, register objects and interfaces with
sd_bus_add_object_vtable like in
http://0pointer.net/blog/the-new-sd-bus-api-of-systemd.html
and in handler function, take a copy, of a reference to message
object, to global variable and use it later with
sd_bus_reply_method_return?
I tried to do that. But it seems, that when handler function returns,
it sends an error message to calling client if
sd_bus_reply_method_return
was not called inside handler.

In my event loop I will receive messages and then use something like
sd_bus_message_is_method_call to call appropriate handlers
or store reference to message and reply later. I my event loop I
basically call sd_bus_process to get messages.
A second parameter to sd_bus_process gives me message that I can store
and use to reply later.
But what about introspection? If i don't use sd_bus_add_object_vtable,
I can't use busctl or d-feet(GUI introspecting d-bus service),
to view what objects service provides and signatures for interfaces,
like was explained in a blog post I referenced above.

Boris

On Mon, 28 Jan 2019 at 12:54, Lennart Poettering  wrote:
>
> On Mo, 28.01.19 12:25, Jean Valjean (valjean.jean1...@gmail.com) wrote:
>
> > Is there a possibility to send a delayed response to a method call?
>
> Yes. Just keep a reference to the incoming method call message object
> around, and then, when you are ready to respond, respond.
>
> > The scenario is
> > 1. Message A with input data is received by a service and placed into
> > a list. This message will be used to reply later.
> > 2. A routine is invoked that might take a long time to prepare a reply
> > on a background thread
> > 3. While reply is being prepared service can still receive and process
> > new incoming messages B, C, D and send replies to them
> > 4. Once routine is done A is taken from the list and used to send a reply.
> >
> > I know that it is possible to use sd_bus_process to get and process
> > incoming messages.
> > But in that case I wonder how do I add an object so that it is visible
> > in the tree produced by
> > busctl --user tree org.example
> > I can't use sd_bus_add_object or sd_bus_add_object_vtable because If I
> > execute the routine in handlers then
> > it will block the service from receiving other messages.
>
> I am not sure I follow what precisely you are trying to do, but note
> that sd-bus is not supposed to be dispatched recursively, i.e. you
> cannot run the sd-bus event loop from inside the sd-bus event loop if
> you follow what I mean.
>
> Hence, when you want to do what you are trying to do the usual
> approach is to run a top-level event loop (i.e. sd-event or glib or
> any other you like), then when you get the incoming method call, you
> initiate your long-running action, and quickly return to the event
> loop so that the event loop can continue to process further
> events. And then when you are done you respond to the message you kept
> a reference on.
>
> Now, you might wonder how to "initiate your long-running action" while
> at the same time "quickly returning to the event loop". You have
> multiples options there. You can either do threads (i.e. pass of the
> long-running work to another worker thread, which then reports
> completion back to the main event loop — maybe through a pipe() —
> which can then reply to the message), or in many cases you can split
> up your work in shorter units that can run from separate
> low-priorized event loop handlers (in sd-event for example in "defer"
> event loops running at a low priority), and then run everything from
> the same event loop. I personally usually go for the latter, but it
> comes with its own complexities.
>
> Lennart
>
> --
> Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Many user slices created and user managers spawned on boot

[Simon McVittie]

On Sat, 26 Jan 2019 at 10:26:23 -0600, Steve Bergman wrote:
> possibly since before the upgrade from Debian 7 with sysvinit to
> Debian 9 with systemd

I hope you upgraded from Debian 7 (usually booted with sysvinit) to Debian 8
(usually booted with systemd), then rebooted, cleaned up any obsolete packages,
and upgraded from Debian 8 to Debian 9 as a separate step. Debian does not
support upgrades that skip a release: our releases are about 2 years apart, and
applying 4 or more years of development to a running system is too much change
to do reliably in one go. If this system is working, it's probably fine now,
but please upgrade in 1-release steps if you upgrade any similar systems.

The major "Debianism" to be aware of with systemd is that in upstream
systemd, logind's [Login] KillUserProcesses option defaults to "yes",
whereas in Debian it defaults to "no".

The benefit of that change is that on Debian systems, tools like screen(1) and
tmux(1) work as intended without needing special steps to exclude them from the
session scope; the cost is that processes that continue to run after a user's
session has ended are not cleaned up (because systemd can't know that they
weren't meant to behave like screen or tmux).

smcv
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] sd-bus: calling D-Bus method from a D-Bus method callback upon the same D-Bus connection

[Simon McVittie]

On Sat, 26 Jan 2019 at 16:22:47 +0100, Lennart Poettering wrote:
> Yes, you may synchronously call into other bus services from an async
> msg hander, but as long as that call runs no incoming msgs besides the
> expected reply will be processed. This means effectively that while
> the synchronous call is running all incoming messages are queued until
> the reply is seen, then the reply is processed and the call returns,
> and only then after you return back into the event loop the queued
> incoming messages are dispatched.
> 
> This also means that while in dbus normally everything is strictly
> ordered, if you do things in this way the reply is "pulled ahead"
> during processing, and the other msgs incoming "pushed back".

For what it's worth, it sounds as though this is the same behaviour as in other
popular D-Bus implementations. In libdbus (the reference implementation) there
is a convention that the functions that behave like this mostly end with
_block, for example dbus_connection_send_message_with_reply_and_block(). In
GDBus (part of GLib) they conventionally end with _sync, for example
g_dbus_connection_call_sync(). In Qt they use mode QDBus::Block. Any advice or
warnings you see about those API families will probably apply equally to the
equivalents in sd-bus.

Reiterating what Lennart said, if you don't use synchronous/blocking calls,
D-Bus messages via the dbus-daemon or a reimplementation like dbus-broker are
usually seen in the same order by everyone on the bus (a mathematician would
say there's a "total order" on the set of messages). If you use
synchronous/blocking calls, you lose that guarantee, because you are processing
some messages out-of-order.

See also http://smcv.pseudorandom.co.uk/2008/11/nonblocking/ (which was written
before the addition of sd-bus and GDBus and the deprecation of dbus-glib, but
is otherwise still relevant).

smcv
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] sd-bus delayed reply

[Lennart Poettering]

On Mo, 28.01.19 12:25, Jean Valjean (valjean.jean1...@gmail.com) wrote:

> Is there a possibility to send a delayed response to a method call?

Yes. Just keep a reference to the incoming method call message object
around, and then, when you are ready to respond, respond.

> The scenario is
> 1. Message A with input data is received by a service and placed into
> a list. This message will be used to reply later.
> 2. A routine is invoked that might take a long time to prepare a reply
> on a background thread
> 3. While reply is being prepared service can still receive and process
> new incoming messages B, C, D and send replies to them
> 4. Once routine is done A is taken from the list and used to send a reply.
>
> I know that it is possible to use sd_bus_process to get and process
> incoming messages.
> But in that case I wonder how do I add an object so that it is visible
> in the tree produced by
> busctl --user tree org.example
> I can't use sd_bus_add_object or sd_bus_add_object_vtable because If I
> execute the routine in handlers then
> it will block the service from receiving other messages.

I am not sure I follow what precisely you are trying to do, but note
that sd-bus is not supposed to be dispatched recursively, i.e. you
cannot run the sd-bus event loop from inside the sd-bus event loop if
you follow what I mean.

Hence, when you want to do what you are trying to do the usual
approach is to run a top-level event loop (i.e. sd-event or glib or
any other you like), then when you get the incoming method call, you
initiate your long-running action, and quickly return to the event
loop so that the event loop can continue to process further
events. And then when you are done you respond to the message you kept
a reference on.

Now, you might wonder how to "initiate your long-running action" while
at the same time "quickly returning to the event loop". You have
multiples options there. You can either do threads (i.e. pass of the
long-running work to another worker thread, which then reports
completion back to the main event loop — maybe through a pipe() —
which can then reply to the message), or in many cases you can split
up your work in shorter units that can run from separate
low-priorized event loop handlers (in sd-event for example in "defer"
event loops running at a low priority), and then run everything from
the same event loop. I personally usually go for the latter, but it
comes with its own complexities.

Lennart

--
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Systemd-analyze time not giving kernal bootup time.

[Shuang Liu]

Looks like

https://github.com/systemd/systemd/pull/9801
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] sd-bus delayed reply

[Jean Valjean]

Is there a possibility to send a delayed response to a method call?
The scenario is
1. Message A with input data is received by a service and placed into
a list. This message will be used to reply later.
2. A routine is invoked that might take a long time to prepare a reply
on a background thread
3. While reply is being prepared service can still receive and process
new incoming messages B, C, D and send replies to them
4. Once routine is done A is taken from the list and used to send a reply.

I know that it is possible to use sd_bus_process to get and process
incoming messages.
But in that case I wonder how do I add an object so that it is visible
in the tree produced by
busctl --user tree org.example
I can't use sd_bus_add_object or sd_bus_add_object_vtable because If I
execute the routine in handlers then
it will block the service from receiving other messages.

Boris
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Fail to load network modules properly

[juice]

Łukasz Słaboń kirjoitti 2019-01-28 11:18:

Apparently the same bug is in the open-source driver. As I said in my
previous e-mail I'm experiencing same problem with all possible
drivers for my wifi card.

Regards,

Łukasz Słaboń



Does your driver require firmware to be loaded before operation?
Is it possible that if the driver starts early enough your /lib/firmware
is not on a mounted partition (or not on initramfs)

  - juice -
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Systemd-analyze time not giving kernal bootup time.

[Jérémy ROSEN]

What version of systemd are you using ?

Kernel time is usually not displayed when systemd is run inside a container
(since it makes no sense). There might be something wrong with container
detection here, though...

Le lun. 28 janv. 2019 à 10:22, deepan muthusamy  a
écrit :

> My target(RCAR-H3) runs with yocto project have boot up time of 13 seconds
> before init starts as of my observation. because I am starting Weston in
> basic.target which is starting after 13 seconds from the time I pressed
> power button.
>
> Note: I am booting the board from SD card(The image is in SD card).
>
> "Systemd-analyze time " giving "Startup finished in 11.814s(userspace) =
> 13.519s".
> It is not giving kernal bootup time.
> Help me with this.
>
>
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>


-- 
[image: SMILE]  

20 rue des Jardins
92600 Asnières-sur-Seine
*Jérémy ROSEN*
Architecte technique

[image: email] jeremy.ro...@smile.fr
[image: phone]  +33 6 88 25 87 42
[image: url] http://www.smile.eu

[image: Twitter]  [image: Facebook]
 [image: LinkedIn]
 [image: Github]


[image: Découvrez l’univers Smile, rendez-vous sur smile.eu]

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Systemd-analyze time not giving kernal bootup time.

[deepan muthusamy]

My target(RCAR-H3) runs with yocto project have boot up time of 13 seconds
before init starts as of my observation. because I am starting Weston in
basic.target which is starting after 13 seconds from the time I pressed
power button.

Note: I am booting the board from SD card(The image is in SD card).

"Systemd-analyze time " giving "Startup finished in 11.814s(userspace) =
13.519s".
It is not giving kernal bootup time.
Help me with this.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Fail to load network modules properly

[Łukasz Słaboń]

Apparently the same bug is in the open-source driver. As I said in my
previous e-mail I'm experiencing same problem with all possible drivers for
my wifi card.

Regards,

Łukasz Słaboń


On Mon, Jan 28, 2019 at 8:32 AM Greg KH  wrote:

> On Sun, Jan 27, 2019 at 09:14:37PM +0100, Łukasz Słaboń wrote:
> > Hello everyone,
> >
> > Since starting using linux last year (xubuntu 18.04) I am experiencing
> > occasional problems with wifi interface (broadcom BCM43224 rev 01
> > 14e4:4353). From time to time (every 3 - 4 starts) my wifi card is not
> > recognized and I do not see wifi interface after boot. After comparing
> > dmesg listings from successful and failed boots I have discovered one
> > difference. My main partition is mounted twice and in successful boot it
> is
> > done before  before cfg80211 module. In failed boot second mount is done
> > after cfg80211 module. Can this be a cause of network interface problems?
> > If yes is there any possibility to solve this within systemd? Just to
> > clarify such situations happen with proprietary and open-source drivers
> as
> > well.
> >
> > Here is the fragment of dmesg listing after successful boot:
> > [4.452703] [drm] Initialized radeon 2.50.0 20080528 for :02:00.0
> on
> > minor 0
> > [4.601495] EXT4-fs (sda5): mounted filesystem with ordered data mode.
> > Opts: (null)
> > [4.669690] clocksource: Switched to clocksource tsc
> > [5.068753] input: SynPS/2 Synaptics TouchPad as
> > /devices/platform/i8042/serio1/input/input5
> > [5.774502] random: crng init done
> > [5.774503] random: 7 urandom warning(s) missed due to ratelimiting
> > [6.151902] ip_tables: (C) 2000-2006 Netfilter Core Team
> > [9.336683] lp: driver loaded but no devices found
> > [9.366325] ppdev: user-space parallel port driver
> > [9.405084] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
> > [   12.325130] Adding 2097148k swap on /swapfile.  Priority:-2 extents:6
> > across:2260988k FS
> > [   20.381638] cfg80211: Loading compiled-in X.509 certificates for
> > regulatory database
> > [   20.385106] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> > [   20.863926] wl: loading out-of-tree module taints kernel.
> > [   20.863932] wl: module license 'MIXED/Proprietary' taints kernel.
> > [   20.863932] Disabling lock debugging due to kernel taint
> > [   20.866504] wl: module verification failed: signature and/or required
> > key missing - tainting kernel
> > [   20.941673] wlan0: Broadcom BCM4353 802.11 Hybrid Wireless Controller
> > 6.30.223.271 (r587334)
> >
> > Here is the fragment of dmesg listing after failed boot:
> > [5.194759] EXT4-fs (sda5): mounted filesystem with ordered data mode.
> > Opts: (null)
> > [6.249451] random: crng init done
> > [6.249454] random: 7 urandom warning(s) missed due to ratelimiting
> > [6.728424] ip_tables: (C) 2000-2006 Netfilter Core Team
> > [9.888353] lp: driver loaded but no devices found
> > [9.913126] ppdev: user-space parallel port driver
> > [   10.152833] cfg80211: Loading compiled-in X.509 certificates for
> > regulatory database
> > [   10.156199] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> > [   10.174030] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
> > [   21.275568] Adding 2097148k swap on /swapfile.  Priority:-2 extents:6
> > across:2260988k FS
> > [   21.472260] wl: loading out-of-tree module taints kernel.
> > [   21.472264] wl: module license 'MIXED/Proprietary' taints kernel.
> > [   21.472265] Disabling lock debugging due to kernel taint
> > [   21.474938] wl: module verification failed: signature and/or required
> > key missing - tainting kernel
> > [   21.477657] wl :08:00.0: enabling device ( -> 0002)
> > [   21.477881] wl driver 6.30.223.271 (r587334) failed with code 1
> > [   21.477882] ERROR @wl_cfg80211_detach :
> > [   21.477883] NULL ndev->ieee80211ptr, unable to deref wl
>
> Looks like a bug in the closed-source wl kernel driver.  Please contact
> the authors of that code and ask them for help as there's really nothing
> we can do about this.
>
> sorry,
>
> greg k-h
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel