From: Miroslav Skoric <skoric@uns.ac.rs>
To: linux-hams@vger.kernel.org
Subject: [...] unregister_netdevice: waiting for ax0 to become free. Usage count = -1
Date: Sun, 28 Apr 2024 17:57:30 +0200 [thread overview]
Message-ID: <dd43a40e-ab22-a751-185f-3931ade2fa8f@uns.ac.rs> (raw)
Hi,
One of my two machines in the LAN goes into 'endless' repeating of the
following lines when I want to shut it down. (Ok, not really endless but
it does take some half an hour.) That comp runs an older version of ax25
subsystem and on top of it runs FPAC node and FBB mailbox. The issue
happens whenever the *other* machine has some netrom activity such as a
BPQ node/bbs or like.
[...] unregister_netdevice: waiting for ax0 to become free. Usage count = -1
[...] unregister_netdevice: waiting for ax0 to become free. Usage count = -1
[...] unregister_netdevice: waiting for ax0 to become free. Usage count = -1
...
...
after some 30 minutes there appear two other lines:
[TIME] Timed out starting Power-Off.
[ !! ] Forcibly powering off: job timed out
and it resumes repeating the above for a while:
[...] unregister_netdevice: waiting for ax0 to become free. Usage count = -1
[...] unregister_netdevice: waiting for ax0 to become free. Usage count = -1
and it finally powers off after a minute or so.
It makes me wonder why it behaves like that. I tested that behaviour
thoroughly (by having the other machine running, or not running some
packet node stuff) and realized that it shuts down properly, without any
delay only when the other machine is not having any packet node active.
(The other comp can be switched on, but without any node/bbs running.)
Any idea?
Misko YT7MPB
next reply other threads:[~2024-04-28 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 15:57 Miroslav Skoric [this message]
2024-04-28 19:57 ` [...] unregister_netdevice: waiting for ax0 to become free. Usage count = -1 Lars Kellogg-Stedman
2024-04-29 10:22 ` Miroslav Skoric
2024-04-28 20:03 ` David Ranch
2024-04-29 10:19 ` Miroslav Skoric
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd43a40e-ab22-a751-185f-3931ade2fa8f@uns.ac.rs \
--to=skoric@uns.ac.rs \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).