Re: Contents of freebsd-wireless digest.
___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
[Bugzilla] Commit Needs MFC
Hi, You have a bug in the Needs MFC state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by ead...@freebsd.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Contents of freebsd-wireless digest...
Re: Contents of freebsd-wireless digest... ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: iwn0 hangs randomly when starting the machine
Hi Adrian, On Sat, 7 Jun 2014 21:41:10 -0400 Adrian Chadd adr...@freebsd.org wrote: Can you pleease chase this up with me next week? We need to find/fix these issues. I'm not running v6 at home; I can easily flip that on when I get home next week. sorry for being late. I was travelling myself until yesterday. I updated my machine over the weekend to FreeBSD X220.alogt.com 10.0-STABLE FreeBSD 10.0-STABLE #38 r267699: Sun Jun 22 16:32:07 WITA 2014 er...@x220.alogt.com:/usr/obj/usr/src/sys/X220 amd64 I started it only a single time with IPV6 enabled and the machine crashed again. It looked to me that it was the same location but I did not verify it. I run the machine since then with IPV4 only and did not have any trouble. Maybe a word to the timezone. It seems that we are 12h apart. So, early morning and early evening would be the best pairing for us. Erich THanks, -a On 7 June 2014 21:21, Erich Dollansky erichsfreebsdl...@alogt.com wrote: Hi Adrian, On Fri, 23 May 2014 09:01:36 -0700 Adrian Chadd adr...@freebsd.org wrote: a photo will be fine. :-) did the photos help? I did not have any problems anymore since I deactivated IPV6. Erich -a On 23 May 2014 08:59, Erich Dollansky erichsfreebsdl...@alogt.com wrote: Hi, On Fri, 23 May 2014 08:36:31 -0700 Adrian Chadd adr...@freebsd.org wrote: Ok, it's a null pointer dereference (based on the address you posted) and it's ipv6 related. That's .. odd. Can you provide a backtrace from the crash? I can try tomorrow. Am I right that I can only take photos of the screen at this point of the boot process? Erich -a On 23 May 2014 04:13, Erich Dollansky erichsfreebsdl...@alogt.com wrote: Hi, On Tue, 8 Apr 2014 20:40:01 -0700 Adrian Chadd adr...@freebsd.org wrote: I'm not sure. I'd really like to see what the story is with coexistence somehow. I did some more investigations and came to the result that iwn crashes in 'in6_ifattach_linklocal'. When I disable ipv6, it all works fine. I did several reboots without a problem. To make this a bit more complicated, if I use only em0, the machine starts normal. When I use iwn0 alone or together with lagg0 and em0, the machine crashes during the boot process. The crashes only happen when IPV6 is enabled in rc.conf. Erich ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
