Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Jan 2003 13:52:12 -0800
From:      Sean Chittenden <sean@chittenden.org>
To:        "M. Warner Losh" <imp@bsdimp.com>
Cc:        b@etek.chalmers.se, sam@errno.com, current@FreeBSD.org
Subject:   Re: HEADS UP: new wi driver
Message-ID:  <20030124215212.GB1224@perrin.int.nxad.com>
In-Reply-To: <20030117.102821.89423323.imp@bsdimp.com>
References:  <1e4301c2bd82$03de8cb0$5a557f42@errno.com> <Pine.BSF.4.44.0301171716010.49553-100000@scrooge.etek.chalmers.se> <20030117.102821.89423323.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> : dstumbler breaks; on startup it reports
> :     "unable to ioctl device socket: Input/output error".
> 
> As root or no?

I have a rebuilt system finally that I could test this against and I'm
actually getting a different error message on startup of dstumbler:

error: unable to ioctl device socket: Invalid argument

From ktrace:

 43042 dstumbler CALL  sigaction(0x12,0x280b5850,0)
 43042 dstumbler RET   sigaction 0
 43042 dstumbler CALL  socket(0x2,0x2,0)
 43042 dstumbler RET   socket 3
 43042 dstumbler CALL  ioctl(0x3,SIOCGIFGENERIC,0xbfbff4b0)
 43042 dstumbler RET   ioctl 0
 43042 dstumbler CALL  ioctl(0x3,SIOCSIFGENERIC,0xbfbff4c0)
 43042 dstumbler RET   ioctl 0
 43042 dstumbler CALL  ioctl(0x3,SIOCGIFGENERIC,0xbfbff4b0)
 43042 dstumbler RET   ioctl 0
 43042 dstumbler CALL  ioctl(0x3,SIOCSIFGENERIC,0xbfbff4c0)
 43042 dstumbler RET   ioctl -1 errno 22 Invalid argument
 43042 dstumbler CALL  sigaction(0x12,0x280b5838,0x280b5850)
 43042 dstumbler RET   sigaction 0
 43042 dstumbler CALL  poll(0xbfbff3e8,0x1,0)
 43042 dstumbler RET   poll 0
 43042 dstumbler CALL  poll(0xbfbff3e8,0x1,0)
 43042 dstumbler RET   poll 0
 43042 dstumbler CALL  write(0x1,0x8060000,0x5e)
 43042 dstumbler GIO   fd 1 wrote 94 bytes
       "\^[[52;22H\^[[34m\^[[1m[\^[[31m error: unable to ioctl device socket: \
        Invalid argument \^[[C\^[[39;49m\^[[m\^O"


wistat.c, line 225 seems to be the offending line that is no longer
working.  Does dstumbler need to be updated or is this a bug in the
new wlan code?  -sc

-- 
Sean Chittenden

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030124215212.GB1224>