https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=116747
Alan Somers changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282789
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #12
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #13 from oleg.nau...@gmail.com ---
(In reply to Bjoern A. Zeeb from comment #10)
It caused kernel panic after 1 hour 47 minutes of uptime
Jan 17 08:21:23 kernel: rtw880: ERROR lkpi_80211_txq_tx_one: skb alloc failed
48 + 163,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #12 from Guillaume Outters ---
(In reply to Bjoern A. Zeeb from comment #10)
I would be glad to add my laptop to the test battery,
but I will need a bit of guidance on how a total newbie can run this patched
driver (until now I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #11 from oleg.nau...@gmail.com ---
(In reply to Bjoern A. Zeeb from comment #10)
Hello Bjoern,
I will test it tomorrow.
Thank you
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #10 from Bjoern A. Zeeb ---
This is a shot in the dark and a hack but can you two try to apply the changes
from
https://reviews.freebsd.org/D48474
and see if that helps? If it does we can find a proper solution not abusing an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #9 from Guillaume Outters ---
OK, I was wrong thinking the compiler eating mem induced rtw88 into error:
now I'm convinced that rtw88 ate so much mem that clang hadn't enough anymore.
Twice this week I observed lpkiskb going ro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #8 from Guillaume Outters ---
Created attachment 256704
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=256704&action=edit
vmstat req and mem during scp before / after going rogue
--
You are receiving this mail becau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Rene Ladan changed:
What|Removed |Added
CC||r...@freebsd.org
--- Comment #96 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163318
Mark Linimon changed:
What|Removed |Added
Attachment #120520|text/x-patch; |text/plain
mime type|chars
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #7 from Guillaume Outters ---
Whoops, I got a new one!
After an uptime of more than 2 days without any problem, I once again had two
killed processes yesterday evening (while building GHC, the Haskell compiler),
and then this mo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #6 from oleg.nau...@gmail.com ---
Hello,
It would be nice if you provide Bjoern with output
vmstat -m | egrep -E "lkpiskb|Memory"
when it happens again
--
You are receiving this mail because:
You are on the CC list for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #5 from Guillaume Outters ---
(In reply to oleg.nauman from comment #4)
Yes, I have the same:
Dec 31 16:39:14 pasdfric kernel: rtw880: ERROR lkpi_80211_txq_tx_one: skb alloc
failed
as you, with a sysctl compat.linuxkpi.skb.mem_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #4 from oleg.nau...@gmail.com ---
(In reply to Guillaume Outters from comment #3)
Hello,
I can not confirm that "skb allocation failure" happens only when virtual
memory is exhausted
Could you please directly confirm that you a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
--- Comment #3 from Guillaume Outters ---
Here it seems to happen only after memory has been exhausted at least once:
after a reboot there *always* (see (1)) have to happen a bunch of "kernel: pid
xxx (x), jid 0, uid 1001, was killed: f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
Guillaume Outters changed:
What|Removed |Added
CC||guillaume-freebsd@outters.e
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247528
Quentin Thébault changed:
What|Removed |Added
CC||quentin.theba...@defenso.fr
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #23 from Bjoern A. Zeeb ---
(In reply to Guillaume Outters from comment #21)
Oleg opened https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903 on my
request now for the skb leak; so we'll ignore that bit in this PR.
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903
oleg.nau...@gmail.com changed:
What|Removed |Added
Blocks||273621
Referenced Bugs:
h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
Bjoern A. Zeeb changed:
What|Removed |Added
Flags||mfc-stable14?,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #22 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=2372f8cc640c2f4ab82831e6ac0e27ab6c18321a
commit 2372f8cc640c2f4ab82831e6ac0e27ab6c18321a
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #95 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=2372f8cc640c2f4ab82831e6ac0e27ab6c18321a
commit 2372f8cc640c2f4ab82831e6ac0e27ab6c18321a
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #21 from Guillaume Outters ---
(In reply to Oleg Nauman from comment #20)
Bjoern, is there a reference for that "old good bug still there" with
"lkpi_80211_txq_tx_one: skb alloc failed", slugging or freezing the whole
system?
I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
fly...@gmail.com changed:
What|Removed |Added
CC||fly...@gmail.com
--- Comment #94
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
Mark Linimon changed:
What|Removed |Added
CC||wireless@FreeBSD.org
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218007
Alexander Vereeken changed:
What|Removed |Added
Keywords|patch |
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213214
Alexander Vereeken changed:
What|Removed |Added
Keywords|patch |
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206199
Alexander Vereeken changed:
What|Removed |Added
CC||Alexander88207@protonmail.c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280430
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280546
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183644
Alexander Vereeken changed:
What|Removed |Added
CC||Alexander88207@protonmail.c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283015
Graham Perrin changed:
What|Removed |Added
Flags|maintainer-feedback?(bz@Fre |
|eBSD.org)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283015
--- Comment #11 from Graham Perrin ---
Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283015
Mark Johnston changed:
What|Removed |Added
Flags||mfc-stable14+,
|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283015
Mark Johnston changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283015
--- Comment #10 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=2a6c77b343f6789eb56bc42ccba12559a58b464c
commit 2a6c77b343f6789eb56bc42ccba12559a58b464c
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281994
--- Comment #6 from Bill Blake ---
(In reply to Bjoern A. Zeeb from comment #4)
Some points about my setup and an overview of what I did:
My laptop runs FreeBSD 14.1 and connects to the net via the hotspot on MyPhone,
an Android phone whi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281994
--- Comment #5 from Bill Blake ---
Created attachment 256052
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=256052&action=edit
The full set of iwm panics from yesterday.
--
You are receiving this mail because:
You are the assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281994
--- Comment #4 from Bjoern A. Zeeb ---
(In reply to Bill Blake from comment #3)
/var/log/message is fine for me for the moment; at least I get an idea.
If it happens again we'll see.
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281994
--- Comment #3 from Bill Blake ---
If you want what's in /var/log/messages, I can cut and paste.
But here's a data point: After reading another bug report that suggested that
the band matters, I told my phone's hotspot to use 2.4GHz. And
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281994
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281994
Bill Blake changed:
What|Removed |Added
CC||billblake2...@gmail.com
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283436
Bjoern A. Zeeb changed:
What|Removed |Added
Resolution|--- |Works As Intended
Sta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283436
--- Comment #7 from Martin Filla ---
(In reply to Bjoern A. Zeeb from comment #6)
Thank you Bjoern. It works. Problem was in "password".
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283436
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
--- Comment #6 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283436
--- Comment #5 from Martin Filla ---
(In reply to Oleksandr Kryvulia from comment #4)
No but I can to try iwlwifi(4). I use FreeBSD 14.2-RELEASE
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283436
--- Comment #4 from Oleksandr Kryvulia ---
Have you tried an iwlwifi(4) driver? Which FreeBSD version are you using?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283436
--- Comment #3 from Martin Filla ---
(In reply to Oleksandr Kryvulia from comment #2)
Thank you for the idea but I have the same problem
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283436
Oleksandr Kryvulia changed:
What|Removed |Added
CC||o.kryvu...@flex-it.com.ua
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280546
Bjoern A. Zeeb changed:
What|Removed |Added
Assignee|wireless@FreeBSD.org|b...@freebsd.org
--- Comment #8 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
Bjoern A. Zeeb changed:
What|Removed |Added
Status|Open|In Progress
Assignee|wi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283436
--- Comment #1 from Martin Filla ---
firmware looks like loaded
<118>Autoloading module: if_iwm
iwm0: mem 0xf040-0xf0401fff irq 17 at
device 0.0 on pci2
iwm0: hw rev 0x140, fw ver 17.352738.0, address e8:b1:fc:95:42:7d
<118> parent
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233949
--- Comment #19 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=eb6314510c882472628984e6190e39a6ab70687e
commit eb6314510c882472628984e6190e39a6ab70687e
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280546
--- Comment #7 from mmata...@gmail.com ---
Bluetooth drivers get loaded but do not work on this laptop (AX2000 or whatever
the chipset is).
The crash happens to me once every day or 2 so I'm happy to run anything you
want. I am currently n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #16 from Bjoern A. Zeeb ---
(In reply to solidwarea from comment #15)
It's still open. I had been on the road but strated looking yesterday amongst
other things. I checked diffs between 14.1 and 14.2 to see if I could spot
any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #15 from solidwa...@outlook.com ---
(In reply to Bjoern A. Zeeb from comment #3)
Hello, I’m wondering if this thread has come to a halt since there haven’t been
any updates in over a week.
If you’re busy I completely understand,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280546
--- Comment #6 from Bjoern A. Zeeb ---
(In reply to mmatalka from comment #5)
Are you using BT with that machine or in the vicinity?
It sounds like it is reproducible for you (even at random)? Would you be
willing/able to further debug o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #93 from Al Hoang ---
Created attachment 255936
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255936&action=edit
/var/log/messages from today with message occurring
--
You are receiving this mail because:
You are o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280546
mmata...@gmail.com changed:
What|Removed |Added
CC||mmata...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
Keywords|tracking|
--- Comment #92 from Bjoern A. Z
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280546
--- Comment #4 from Bjoern A. Zeeb ---
There's another report in
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255934
attached to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280430 which
should belong here.
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280430
--- Comment #10 from Bjoern A. Zeeb ---
(In reply to mmatalka from comment #9)
The crash in comment #9 (attachment) is a duplicate of bug 280546 it seems but
not this one.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280546
Bjoern A. Zeeb changed:
What|Removed |Added
CC||tr...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283399
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280430
--- Comment #9 from mmata...@gmail.com ---
Created attachment 255934
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255934&action=edit
Crash in wifi driver
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283399
Charlie Li changed:
What|Removed |Added
Keywords||crash
Blocks|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Al Hoang changed:
What|Removed |Added
CC||hoa...@gmail.com
--- Comment #91 from A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
Guillaume Outters changed:
What|Removed |Added
CC||guillaume-freebsd@outters.e
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256494
--- Comment #15 from Bjoern A. Zeeb ---
(In reply to Slawomir Wojciech Wojtczak from comment #14)
There can be multiple circumstances; e.g., was 11n being used, which flags the
hotspot had set; basically it would mean if an AP goes away d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256494
Slawomir Wojciech Wojtczak changed:
What|Removed |Added
Flags||maintainer-feedback?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256494
Bjoern A. Zeeb changed:
What|Removed |Added
Flags|maintainer-feedback?(bz@Fre |
|eBSD.org)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256494
--- Comment #12 from Bjoern A. Zeeb ---
I am getting "forbidden" when I try to fetch a kernel crash. Having had a
backtrace/panic message i the bug report would have helped.
Is there any chance the files still exist?
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256494
Bjoern A. Zeeb changed:
What|Removed |Added
Summary|KERNEL PANIC - WiFi - after |iwn: kernel panic after hot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256494
Bjoern A. Zeeb changed:
What|Removed |Added
Blocks||278175
Referenced Bugs:
https:/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283293
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
Bloc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248584
Mark Linimon changed:
What|Removed |Added
Summary|usr.sbin/bluetooth/btpand: |usr.sbin/bluetooth/btpand:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256494
Graham Perrin changed:
What|Removed |Added
CC||b...@freebsd.org
Flag
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280430
mmata...@gmail.com changed:
What|Removed |Added
CC||mmata...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283015
Mark Johnston changed:
What|Removed |Added
Status|Open|In Progress
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283015
--- Comment #9 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=926905796749750da6464b97ec4f8eec0882cc0e
commit 926905796749750da6464b97ec4f8eec0882cc0e
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283293
Bug ID: 283293
Summary: ath0 (Atheros AR946x/AR948x) timeout issues
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
Severi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #13 from solidwa...@outlook.com ---
(In reply to Bjoern A. Zeeb from comment #12)
I tried running WPA supplicant using the argument you specified. It give a ton
of information quite quickly but I’ve tried reading through it to lo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #12 from Bjoern A. Zeeb ---
(In reply to imbutler from comment #11)
Beware that main and stable/14 have different versions of the driver.
stable/14 hasn't been touched in a longer while.
I'll be on travels but I'll try to look
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #11 from imbutler ---
(In reply to solidwarea from comment #9)
I'm fairly certain this is a driver-related issue. The supplicant seems to be
doing all the right things in asking to associate but I see no evidence of the
AP ever
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
oleg.nau...@gmail.com changed:
What|Removed |Added
CC||oleg.nau...@gmail.com
--- C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #9 from solidwa...@outlook.com ---
(In reply to Bjoern A. Zeeb from comment #3)
Sorry for my incredibly slow replies, I’ve been quite busy the last few days.
I’ve got some free time today, I’ll boot FreeBSD 14.2 on an external H
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282789
Bjoern A. Zeeb changed:
What|Removed |Added
Flags||mfc-stable14?,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282789
--- Comment #11 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=87e140a5c6f89eea7ea6320d1ae34566492abfc0
commit 87e140a5c6f89eea7ea6320d1ae34566492abfc0
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282789
--- Comment #10 from Ruslan Makhmatkhanov ---
(In reply to Bjoern A. Zeeb from comment #8)
works here too! Thank you.
Intel(R) Wireless WiFi based driver for FreeBSD
iwlwifi0: mem 0xef738000-0xef73bfff at device 20.3 on pci0
iwlwifi0: De
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282789
--- Comment #9 from p...@nomadlogic.org ---
Hi, I can confirm that this patch now allows me to successfully load the
iwlwifi kernel module on my CNVi device
$ dmesg|grep iwlwifi
iwlwifi0: mem 0xdd338000-0xdd33bfff at device 20.3 on pci0
iw
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282789
Bjoern A. Zeeb changed:
What|Removed |Added
CC||wireless@FreeBSD.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #8 from imbutler ---
(In reply to imbutler from comment #7)
I stand corrected, the router is apparently manufactured by "Arcadyan
Technology Corporation"
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #7 from imbutler ---
(In reply to Bjoern A. Zeeb from comment #6)
"ifconfig -v wlan0 list scan" returns:
Redacted00:11:22:33:44:556 54M -34:-96 100 EP SSID
RATES DSPARMS<6> TIM<05040003> COUNTRY ERP<0x4>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273622
Graham Perrin changed:
What|Removed |Added
CC|wireless@FreeBSD.org|
--
You are receiving this mail b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273622
Graham Perrin changed:
What|Removed |Added
CC|grahamper...@gmail.com |wireless@FreeBSD.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283015
Graham Perrin changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
Sum
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #6 from Bjoern A. Zeeb ---
(In reply to imbutler from comment #4)
okay, so scanning works but authentication times out:
wpa_supplicant[55824]: wlan0: Trying to associate with 00:11:33:44:55:66
(SSID='redacted' freq=2437 MHz)
w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142
--- Comment #5 from imbutler ---
wpa_supplicant with -dd yields ..
/usr/sbin/wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -D bsd -P
/var/run/wpa_supplicant/wlan0.pid -dd
wpa_supplicant v2.11
Successfully initialized wpa_supplicant
I
1 - 100 of 2030 matches
Mail list logo