Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Maciej Wasilak <wasilak@gmail.com>
Cc: Rohit Kulkarni <rmkulkar@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: Device or resource busy
Date: Thu, 22 Jan 2015 23:20:15 +0100	[thread overview]
Message-ID: <20150122222013.GB18612@omega> (raw)
In-Reply-To: <CAFUtXGwkG7p-LLjRdV5fKrCLQMMVJzMDqBtG4Dt148xAKAm-XQ@mail.gmail.com>

Hi,

On Thu, Jan 22, 2015 at 10:58:32PM +0100, Maciej Wasilak wrote:
...
> socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
> access("/proc/net/if_inet6", R_OK)      = 0
> socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 5
> access("/proc/net/ax25", R_OK)          = -1 ENOENT (No such file or directory)
> access("/proc/net/nr", R_OK)            = -1 ENOENT (No such file or directory)
> access("/proc/net/rose", R_OK)          = -1 ENOENT (No such file or directory)
> access("/proc/net/ipx", R_OK)           = -1 ENOENT (No such file or directory)
> access("/proc/net/appletalk", R_OK)     = -1 ENOENT (No such file or directory)
> access("/proc/sys/net/econet", R_OK)    = -1 ENOENT (No such file or directory)
> access("/proc/sys/net/ash", R_OK)       = -1 ENOENT (No such file or directory)
> access("/proc/net/x25", R_OK)           = -1 ENOENT (No such file or directory)
> ioctl(4, SIOCGIFFLAGS, {ifr_name="wpan0",
> ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_NOARP}) = 0
> ioctl(4, SIOCSIFFLAGS, {ifr_name="wpan0",
> ifr_flags=IFF_BROADCAST|IFF_RUNNING|IFF_NOARP}) = 0
> exit_group(0)                           = ?
> 

I see no issues here. The values also readback and there is no "IFF_UP"
in the last ioctl of file descriptor 4.

Do you are sure that there is no daemon running or something else which
automatically ifup the interface again if you want to set it down? Maybe
just mv the /etc/$NETWORKING_STUFF into a separate directory and try again.

- Alex

  reply	other threads:[~2015-01-22 22:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 12:28 Device or resource busy Rohit Kulkarni
2015-01-20 19:44 ` Alexander Aring
2015-01-21 10:30   ` Rohit Kulkarni
2015-01-21 11:58     ` Maciej Wasilak
     [not found]       ` <54bf9983.07f4440a.7103.0a2e@mx.google.com>
     [not found]         ` <CAFUtXGx-naVAhPOM4OEQt9EoJEQ7NiiG7ni3kxd5zzsiNT52iA@mail.gmail.com>
     [not found]           ` <54bfa40a.c51e460a.6035.ffff8290@mx.google.com>
     [not found]             ` <CAFUtXGwbcBF=90bZtwJ26AWaoSoOvxnxotikjwfNcNfhAjEaOQ@mail.gmail.com>
2015-01-21 13:34               ` Rohit Kulkarni
2015-01-21 15:46         ` Alexander Aring
2015-01-22  7:59           ` Rohit Kulkarni
2015-01-22 20:59             ` Alexander Aring
2015-01-22 21:58               ` Maciej Wasilak
2015-01-22 22:20                 ` Alexander Aring [this message]
2015-01-23  7:59                   ` Alexander Aring
2015-01-25 11:36                     ` Maciej Wasilak
2015-01-25 15:24                       ` Alexander Aring
2015-01-27  9:24                       ` Rohit Kulkarni

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=20150122222013.GB18612@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=rmkulkar@gmail.com \
    --cc=wasilak@gmail.com \
    /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