From: Stephen Hemminger <stephen@networkplumber.org>
To: samuel@sortiz.org
Cc: netdev@vger.kernel.org
Subject: Fw: [Bug 195217] New: irda doesn't work
Date: Sat, 1 Apr 2017 16:42:51 -0700 [thread overview]
Message-ID: <20170401164251.0c69b16d@plumbers-lap.home.lan> (raw)
Begin forwarded message:
Date: Sat, 01 Apr 2017 22:02:08 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 195217] New: irda doesn't work
https://bugzilla.kernel.org/show_bug.cgi?id=195217
Bug ID: 195217
Summary: irda doesn't work
Product: Networking
Version: 2.5
Kernel Version: 4.9.X, 4.10.X, 4.11-rcX
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: jb_69100@yahoo.com
Regression: No
keyword : irda, MCS7780, networking, SIOCSIFFLAGS
Unable to run irda0 with kernel greater than 4.8.17
"ifconfig irda0 up" works with kernel 4.8.17 but fails with kernel 4.9.X,
4.10.X and 4.11-rcX. (SIOCSIFFLAGS: Ressource temporairement non disponible)
________________________________________________
Debian Release: 9.0
Architecture: amd64 (x86_64)
Kernel: Linux 4.10.8---2017-03-31.15h31mn (SMP w/8 CPU cores)
root@myPC:/# lsusb | grep MCS7780
Bus 006 Device 002: ID 9710:7780 MosChip Semiconductor MCS7780 4Mbps Fast IrDA
Adapter
root@myPC:/# ifconfig irda0
irda0: flags=128<NOARP> mtu 2048
irda 00:00:00:00 txqueuelen 8 (IrLAP)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@myPC:/# ifconfig irda0 up
SIOCSIFFLAGS: Ressource temporairement non disponible
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2017-04-01 23:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170401164251.0c69b16d@plumbers-lap.home.lan \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=samuel@sortiz.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 NNTP newsgroup(s).