.
If you or Bernhard can point me at what information I need to gather,
I'll open one. (Nogte that I moved this to wireless, since it seems to
belong either there or stable, not current.
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
On Sat, Nov 24, 2012 at 9:06 PM, Adrian Chadd
MANUAL
Any idea of the problem or what information I could provide?
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
and require an
interface restart.
Does this provide anything useful?
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
iwn_debug.log
Description: Binary data
___
freebsd-wireless@freebsd.org mailing list
http
a difference.
Kevin
-a
On 15 January 2014 18:04, Kevin Oberman rkober...@gmail.com wrote:
Sorry, It's been a little busy the past couple of days.
No, I have had only one interface losing association and not recovering
since my first report. That one did not occur in conjunction
On Fri, Jan 10, 2014 at 9:51 PM, Kevin Oberman rkober...@gmail.com wrote:
On Fri, Jan 10, 2014 at 9:37 AM, Adrian Chadd adr...@freebsd.org wrote:
.. when you see it hang, does anything get logged in dmesg (eg a
firmware panic) ?
Try recompiling your kernel with:
IEEE80211_DEBUG
IWN_DEBUG
, 2014 2:16 AM, Kevin Oberman rkober...@gmail.com wrote:
On Fri, Jan 10, 2014 at 9:51 PM, Kevin Oberman rkober...@gmail.comwrote:
On Fri, Jan 10, 2014 at 9:37 AM, Adrian Chadd adr...@freebsd.orgwrote:
.. when you see it hang, does anything get logged in dmesg (eg a
firmware panic) ?
Try
am curious, if
anyone has any idea.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.o
gt;
>
> -adrian
>
> On Fri, 22 May 2020 at 13:03, Kevin Oberman wrote:
> >
> > in the past few days my logs have been filled with "iwn0:
> null_update_chw:
> > need callback" messages. No change to the driver for over a year, so it
> was
> > proba
