From owner-freebsd-current Fri Jan 24 13:52:39 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 653CA37B401 for ; Fri, 24 Jan 2003 13:52:37 -0800 (PST) Received: from perrin.int.nxad.com (internal.ext.nxad.com [66.250.180.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3956D43F5F for ; Fri, 24 Jan 2003 13:52:36 -0800 (PST) (envelope-from sean@perrin.int.nxad.com) Received: by perrin.int.nxad.com (Postfix, from userid 1001) id A376521062; Fri, 24 Jan 2003 13:52:12 -0800 (PST) Date: Fri, 24 Jan 2003 13:52:12 -0800 From: Sean Chittenden To: "M. Warner Losh" 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> References: <1e4301c2bd82$03de8cb0$5a557f42@errno.com> <20030117.102821.89423323.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030117.102821.89423323.imp@bsdimp.com> User-Agent: Mutt/1.4i X-PGP-Key: finger seanc@FreeBSD.org X-PGP-Fingerprint: 6CEB 1B06 BFD3 70F6 95BE 7E4D 8E85 2E0A 5F5B 3ECB X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > : 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