Re: kern/178612: [run] kernel panic due the problems with run driver

2013-06-18 Thread PseudoCylon
The following reply was made to PR kern/178612; it has been noted by GNATS. From: PseudoCylon To: bug-follo...@freebsd.org, core.dumped...@gmail.com Cc: Subject: Re: kern/178612: [run] kernel panic due the problems with run driver Date: Tue, 18 Jun 2013 14:53:02 -0600 Try removing the line

Re: kern/178612: [run] kernel panic due the problems with run driver

2013-05-18 Thread PseudoCylon
The following reply was made to PR kern/178612; it has been noted by GNATS. From: PseudoCylon To: bug-follo...@freebsd.org, core.dumped...@gmail.com Cc: Subject: Re: kern/178612: [run] kernel panic due the problems with run driver Date: Sat, 18 May 2013 20:01:54 -0600 This must be the same

Re: Block ACK in Ralink RT2860

2013-01-30 Thread PseudoCylon
aggregate packets. How is ampdu working on ral(4)? I cannot test because I do not have any ral(4) nic (only have run(4) nics). AK > > > On Thu, Jan 24, 2013 at 5:13 PM, PseudoCylon > wrote: >> >> > Message: 6 >> > Date: Thu, 24 Jan 2013 12:23:55 -0500 >&g

Re: Block ACK in Ralink RT2860

2013-01-24 Thread PseudoCylon
> Message: 6 > Date: Thu, 24 Jan 2013 12:23:55 -0500 > From: Ramanujan Seshadri > To: freebsd-net@freebsd.org > Subject: Block ACK in Ralink RT2860 > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all, > I am trying to read the contents of block ack's in a Ralink RT2

Re: freebsd-net Digest, Vol 504, Issue 7

2012-12-01 Thread PseudoCylon
> -- > > Message: 12 > Date: Sat, 1 Dec 2012 17:12:53 -0500 > From: Ramanujan Seshadri > To: freebsd-net@freebsd.org > Subject: MCS selected for each transmission in Ralink RT2860 > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > > Hello all, >

Re: Ralink RT2860 Driver Code

2012-12-01 Thread PseudoCylon
out, i.e by reading BA packet or checking what other end is receiving. Unfortunately, this is what you need to do when you are writing a driver without proper documentation. AK > > -Ram > > On Thu, Nov 29, 2012 at 3:35 AM, PseudoCylon > wrote: >> >> On Wed, Nov 28, 2012

Re: Ralink RT2860 Driver Code

2012-11-29 Thread PseudoCylon
uld be saved into AggSizeNCount with host's byte order. So, right sifting means dividing regardless of the byte order. >>1 == /2 ... >>4 == /16 They are playing nice to CPUs, I think. AK > > Thanks for the help. > > -ram > > > On Tue, Nov 27, 2012 at 6:07 PM, P

Re: Ralink RT2860 Driver Code

2012-11-27 Thread PseudoCylon
ess you read the counters on each Tx. AK > > -ram > > > On Tue, Nov 27, 2012 at 2:11 PM, PseudoCylon > wrote: >> >> > -- >> > >> > Message: 12 >> > Date: Tue, 27 Nov 2012 04:33:37 -0500 >> > From: Ramanuj

Re: Ralink RT2860 Driver Code

2012-11-27 Thread PseudoCylon
> -- > > Message: 12 > Date: Tue, 27 Nov 2012 04:33:37 -0500 > From: Ramanujan Seshadri > To: freebsd-net@freebsd.org > Subject: Ralink RT2860 Driver Code > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > > Hello, > Can i know how to get the MP

Re: request for help: 'fixing' the 802.11 TX path

2012-10-29 Thread PseudoCylon
On Mon, Oct 29, 2012 at 3:47 AM, Andre Oppermann wrote: > On 29.10.2012 04:53, Adrian Chadd wrote: >> >> On 28 October 2012 20:43, PseudoCylon wrote: >> >>> Cannot we just add custom hand off function to ieee80211_start()? >> >> >> Yes. That&#x

Re: request for help: 'fixing' the 802.11 TX path

2012-10-28 Thread PseudoCylon
> -- > > Message: 1 > Date: Sat, 27 Oct 2012 16:18:11 -0700 > From: Adrian Chadd > To: freebsd-wirel...@freebsd.org > Cc: FreeBSD Net , freebsd-a...@freebsd.org > Subject: request for help: 'fixing' the 802.11 TX path > Message-ID

Re: Proposal for changes to network device drivers and network stack (RFC)

2012-08-28 Thread PseudoCylon
> -- > > Message: 2 > Date: Fri, 24 Aug 2012 21:11:45 -0700 > From: Anuranjan Shukla > Subject: Proposal for changes to network device drivers and network > stack (RFC) > To: "freebsd-net@freebsd.org" > Message-ID: > Content-Type: text/plain; charset="us-ascii

Re: [urtw] Wifi link dying randomly. reboot required to reconnect.

2011-10-15 Thread PseudoCylon
> My system on the other hand just reports "No Carrier" in ifconfig, > even after resetting the router, and other devices in the home can see > it, and connect to it fine. > Can you #wlandebug -i wlan0 crypto+assoc+auth+scan and re-run wpa_supplicant when the link is droped? I wonder what is faili

Re: [urtw] Wifi link dying randomly. reboot required to reconnect.

2011-10-10 Thread PseudoCylon
> Date: Thu, 6 Oct 2011 19:02:15 -0500 > From: Chuck Burns > Subject: Re: [urtw] Wifi link dying randomly. reboot required to >        reconnect. > To: Gary Palmer > Cc: freebsd-net@freebsd.org > Message-ID: <201110061902.15838.brea...@gmail.com> > Content-Type: Text/Plain;  charset="iso-8859-1"

Re: if_run in hostap mode: issue with stations in the power save mode

2011-02-08 Thread PseudoCylon
- Original Message > From: Bernhard Schmidt > To: PseudoCylon ; Alexander Zagrebin > > Cc: freebsd-net@freebsd.org > Sent: Tue, February 8, 2011 2:52:53 AM > Subject: Re: if_run in hostap mode: issue with stations in the power save mode > > > > >

Re: if_run in hostap mode: issue with stations in the power save mode

2011-02-07 Thread PseudoCylon
- Original Message > From: Bernhard Schmidt > To: PseudoCylon > Cc: Alexander Zagrebin ; freebsd-net@freebsd.org > Sent: Sun, February 6, 2011 3:42:43 AM > Subject: Re: if_run in hostap mode: issue with stations in the power save mode Afaik iwn(4) doesn't use P

Re: if_run in hostap mode: issue with stations in the power save mode

2011-02-04 Thread PseudoCylon
- Original Message > From: Bernhard Schmidt > To: Alexander Zagrebin > Cc: freebsd-net@freebsd.org; PseudoCylon > Sent: Fri, February 4, 2011 5:14:17 AM > Subject: Re: if_run in hostap mode: issue with stations in the power save mode > > On Friday 04 February 20

Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic

2011-01-31 Thread PseudoCylon
The following reply was made to PR kern/153938; it has been noted by GNATS. From: PseudoCylon To: Juergen Lock Cc: bug-follo...@freebsd.org, Juergen Lock Subject: Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic Date: Mon, 31 Jan 2011 15:28:25 -0800 (PST

Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic

2011-01-22 Thread PseudoCylon
The following reply was made to PR kern/153938; it has been noted by GNATS. From: PseudoCylon To: bug-follo...@freebsd.org, Juergen Lock Cc: Juergen Lock Subject: Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic Date: Sat, 22 Jan 2011 23:35:14 -0800 (PST

Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic

2011-01-20 Thread PseudoCylon
The following reply was made to PR kern/153938; it has been noted by GNATS. From: PseudoCylon To: bug-follo...@freebsd.org, Juergen Lock Cc: Subject: Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic Date: Thu, 20 Jan 2011 16:35:48 -0800 (PST) Hello, I have

Re: if_run and wlan_amrr: kernel panics on 8.2-PRERELEASE amd64

2011-01-19 Thread PseudoCylon
- Original Message > From: Alexander Zagrebin > To: PseudoCylon > Cc: freebsd-net@freebsd.org > Sent: Wed, January 19, 2011 5:07:46 AM > Subject: Re: if_run and wlan_amrr: kernel panics on 8.2-PRERELEASE amd64 > > > Yes, there is. > > Due to lack of do

Re: if_run and wlan_amrr: kernel panics on 8.2-PRERELEASE amd64

2011-01-19 Thread PseudoCylon
> Message: 19 > Date: Tue, 18 Jan 2011 13:26:58 +0300 > From: Alexander Zagrebin > Subject: if_run and wlan_amrr: kernel panics on 8.2-PRERELEASE amd64 > To: freebsd-net@freebsd.org > Message-ID: <20110118102658.ga3...@gw.zagrebin.ru> > Content-Type: text/plain; charset=us-ascii > mostly wor

Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic

2011-01-16 Thread PseudoCylon
The following reply was made to PR kern/153938; it has been noted by GNATS. From: PseudoCylon To: Juergen Lock Cc: bug-follo...@freebsd.org, n...@jelal.kn-bremen.de Subject: Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic Date: Sun, 16 Jan 2011 22:24:07 -0800 (PST

Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic

2011-01-13 Thread PseudoCylon
The following reply was made to PR kern/153938; it has been noted by GNATS. From: PseudoCylon To: bug-follo...@freebsd.org, n...@jelal.kn-bremen.de Cc: Subject: Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic Date: Thu, 13 Jan 2011 16:47:21 -0800 (PST

Re: [run] [panic] [patch] Workaround for use-after-free panic

2011-01-13 Thread PseudoCylon
- Original Message > From: Juergen Lock > To: freebsd-gnats-sub...@freebsd.org > Cc: moonlightak...@yahoo.ca; freebsd-net@freebsd.org > Sent: Wed, January 12, 2011 12:55:59 PM > Subject: [run] [panic] [patch] Workaround for use-after-free panic > > > >Submitter-Id: current-users > >

trouble sending BAR frame

2010-07-05 Thread PseudoCylon
Hello, Hiccups sending BAR frame. 1) ieee80211_send_bar() in ieee80211_ht.c http://fxr.watson.org/fxr/source/net80211/ieee80211_ht.c?im=bigexcerpts#L2146 2146 ret = ic->ic_raw_xmit(ni, m, NULL); 2147 if (ret != 0) { 2148 /* xmit failed, clear state flag */ 214

Fix available for run driver

2009-11-28 Thread PseudoCylon
Hello, There are some fixes for run driver for 8.0 release and current. It can be downloaded from freebsd forums at http://forums.freebsd.org/showpost.php?s=87e376cf71273061f7de5aaf258132a1&p=44110&postcount=1 Some packet loss/drop and memory leak have been identified and fixed. (It improved so

Re: LINKSYS WUSB600N, 802.11a/b/g

2009-11-07 Thread PseudoCylon
- Original Message > From: Weongyo Jeong > To: Ivor Prebeg > Cc: freebsd-net@freebsd.org; Tango > Sent: Sat, November 7, 2009 4:06:12 PM > Subject: Re: LINKSYS WUSB600N, 802.11a/b/g > > On Wed, Oct 28, 2009 at 10:09:59AM +0100, Ivor Prebeg wrote: > > Does anyone know if this usb wifi a