Current problem reports assigned to freebsd-wireless@FreeBSD.org

2013-08-12 Thread FreeBSD bugmaster
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker

ath as AP panics

2013-08-12 Thread Lev Serebryakov
Hello, Freebsd-wireless. r254238 with ath used as AP panics in fragment processing. This patch from adrian: Index: ieee80211_output.c === --- ieee80211_output.c (revision 254224) +++ ieee80211_output.c (working copy) @@ -458,6

RE: [iwn]Review Split 6

2013-08-12 Thread Cedric GROSS
De : adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] De la part de Adrian Chadd Envoyé : dimanche 11 août 2013 19:09 À : Cedric GROSS Cc : freebsd-wireless@freebsd.org Objet : Re: [iwn]Review Split 6 On 11 August 2013 10:06, Cedric GROSS c...@cgross.info wrote: U1 stand for

Re: ath as AP panics

2013-08-12 Thread Adrian Chadd
Hi, So the if_transmit() change did change a few things. if_start() / *_ENQUEUE() clears m_nextpkt(). I'd like to know where m_nextpkt() is NOT being cleared. How about triggering it quickly - put in a panic there rather than NULL'ing it, then when it immediately panics, do a backtrace?

Re: ath as AP panics

2013-08-12 Thread Lev Serebryakov
Hello, Adrian. You wrote 12 августа 2013 г., 21:29:08: AC So the if_transmit() change did change a few things. if_start() / AC *_ENQUEUE() clears m_nextpkt(). AC I'd like to know where m_nextpkt() is NOT being cleared. AC How about triggering it quickly - put in a panic there rather than AC

Re: ath as AP panics

2013-08-12 Thread Adrian Chadd
Hm. OK. What I want is the code path _in_ that's queuing a frame via ieee80211_vap_transmit() with m_nextpkt set to NON-NULL. -adrian On 12 August 2013 10:32, Lev Serebryakov l...@freebsd.org wrote: Hello, Adrian. You wrote 12 августа 2013 г., 21:29:08: AC So the if_transmit() change did

Re: ath as AP panics

2013-08-12 Thread Adrian Chadd
On 12 August 2013 10:41, Lev Serebryakov l...@freebsd.org wrote: Hello, Adrian. You wrote 12 августа 2013 г., 21:34:04: AC Hm. OK. AC What I want is the code path _in_ that's queuing a frame via AC ieee80211_vap_transmit() with m_nextpkt set to NON-NULL. I could set breakpoint on printf()

Re: [iwn]Review Split 6

2013-08-12 Thread Adrian Chadd
On 12 August 2013 10:41, Cedric GROSS c...@cgross.info wrote: But again, as current version is not stable in normal operation, I haven't test it further. What could be interest of this ? Wifi relay, bridge or whatever usage of 2 wireless but only with 1 card. It's likely for STA on one VAP

Re: [iwn]Review Split 6

2013-08-12 Thread Adrian Chadd
Ok, so this PAN support is .. pretty terrifying. We'll have to tidy it up once the rest of this work is debugged. I guess '_u1' here is 'PAN VAP'. We'll eventually rename this stuff and maybe shift it into a separate source file so all the PAN stuff clearly lives elsewhere. I wonder which NICs

RE: [iwn]Review Split 6

2013-08-12 Thread Cedric GROSS
-Message d'origine- De : adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] De la part de Adrian Chadd Envoyé : lundi 12 août 2013 20:25 À : Cedric GROSS Cc : freebsd-wireless@freebsd.org Objet : Re: [iwn]Review Split 6 Ok, so this PAN support is .. pretty terrifying. We'll

Re: ath as AP panics

2013-08-12 Thread Lev Serebryakov
Hello, Adrian. You wrote 12 августа 2013 г., 21:47:46: AC Hm. OK. AC What I want is the code path _in_ that's queuing a frame via AC ieee80211_vap_transmit() with m_nextpkt set to NON-NULL. I could set breakpoint on printf() from patch and get backtrace when it will be hit. Is it enough?

Re: ath as AP panics

2013-08-12 Thread Adrian Chadd
Ugh, I missed another m_nextpkt = NULL assignment. Try updating again. Thanks! -adrian On 12 August 2013 14:35, Lev Serebryakov l...@freebsd.org wrote: Hello, Adrian. You wrote 12 августа 2013 г., 21:47:46: AC Hm. OK. AC What I want is the code path _in_ that's queuing a frame via AC

Re: kern/181100: [bwi] Turning up bwi0 crashes / deadlocks the kernel

2013-08-12 Thread Julio Merino
On 2013-08-11 23:19 , Adrian Chadd wrote: Try this patch in sys/dev/bwi/ : This is what I got: bwi_mac_set_ackrates: i=0 (of 12); rs-rs_rates = 130 ___ freebsd-wireless@freebsd.org mailing list

Re: kern/181100: [bwi] Turning up bwi0 crashes / deadlocks the kernel

2013-08-12 Thread Adrian Chadd
Oh, god damnit! On 12 August 2013 19:41, Julio Merino ju...@meroh.net wrote: On 2013-08-11 23:19 , Adrian Chadd wrote: Try this patch in sys/dev/bwi/ : This is what I got: bwi_mac_set_ackrates: i=0 (of 12); rs-rs_rates = 130 Oh hm, the problem is that rs_rates[] shouldn't be directly used