https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214406
--- Comment #1 from Dave Cottlehuber ---
Created attachment 176867
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=176867=edit
service_netif_restart.log
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214406
--- Comment #3 from Dave Cottlehuber ---
dhclient log is either this - blank - or shows a DHCPOFFER received
but dhclient never responds and so the client times out.
# dhclient wlan0
DHCPDISCOVER on wlan0 to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214406
--- Comment #4 from Dave Cottlehuber ---
Fiddling with the MTU has no impact.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214406
Bug ID: 214406
Summary: [urtwn] discard frame, too short - flakey performance
- sometimes not even dhclient succeeds
Product: Base System
Version: 11.0-RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214406
--- Comment #2 from Dave Cottlehuber ---
Created attachment 176868
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=176868=edit
tcpdump_bootps.log
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214406
--- Comment #5 from Dave Cottlehuber ---
hw is
https://www.amazon.com/Edimax-EW-7811Un-150Mbps-Raspberry-Supports/dp/B003MTTJOY
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214235
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-ports-bugs@FreeBSD.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #2 from Sergey ---
(In reply to Adrian Chadd from comment #1)
Hi Adrian.
Now there's nothing more than this:
wlan0: Ethernet address: f8:1a:67:09:d2:7b
wlan0: link state changed to UP
wlan0: link state
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #6 from Maxim Usatov ---
Created attachment 175964
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175964=edit
dmesg after netif restart
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #7 from Maxim Usatov ---
For some reason resume worked fine and I couldn't capture dmesg, however, I
didn't have Wi-Fi straight after the next reboot. dmesg output attached.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #5 from Maxim Usatov ---
Created attachment 175963
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175963=edit
dmesg before netif restart, after successful boot, no Wi-fi
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #14 from Maxim Usatov ---
OK, patched (had to grab that header file from GitHub), installed new kernel,
still Wi-Fi not working after resume. Had to do service netif restart about 8
times to get it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #15 from Maxim Usatov ---
Created attachment 175969
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175969=edit
dmesg after patching, Wi-Fi not working after resume
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #9 from Andriy Voskoboinyk ---
Created attachment 175966
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175966=edit
Fix possible driver hang (see r305745)
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #11 from Maxim Usatov ---
Created attachment 175967
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175967=edit
my if_iwn.c before patching
It appears my if_iwn.c is different from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #12 from Andriy Voskoboinyk ---
Yes, it is from CURRENT (but this code path was not modified and patches should
apply anyway).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #13 from Maxim Usatov ---
Patched, but can't rebuild kernel: it can't find find
dev/drm2/i915/intel_bios.h (fatal error when including from i915_drv.h) The
file simply isn't there, although I have
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #8 from Andriy Voskoboinyk ---
Created attachment 175965
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175965=edit
Try to fix device timeouts after AUTH -> AUTH state transition
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #10 from Andriy Voskoboinyk ---
Try to apply both (first may fix device timeout's, second should fix automatic
interface restart).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213207
--- Comment #8 from Andriy Voskoboinyk ---
Created attachment 175673
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175673=edit
wlanaddr fix
Can you try the patch? It may fix MAC address change via 'wlanaddr'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213207
--- Comment #10 from f...@opal.com ---
Oh, to follow-up on what I said in that thread, we need either a way to
determine the ath's MAC address, e.g., a sysctl dev.ath.N.macaddr or similar,
so that we can use this to set the ethernet's MAC,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213207
--- Comment #9 from f...@opal.com ---
This affects us here, too.
In an email thread on freebsd-wireless, "Regression: ethernet + wireless/ath
under lagg", I posted an alternative work-around, but both the solution here
and that one require
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213207
Adrian Chadd changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213456
--- Comment #6 from Sergey ---
Hi Guys.
Had following line in rc.conf:
ifconfig_wlan0="WPA DHCP mtu 1480 county RU -bgscan ssid MYSSID" (which works
perfectly on my desktop with ath0)
changing it to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213456
Sergey changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213456
--- Comment #4 from Sergey ---
(In reply to Adrian Chadd from comment #2)
Yes it associates as 11n, but it did the same before, on 10.3 without any
issues and had good wireless speed. It works as 11n on 11.0 also,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213456
Vladimir Botka changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #5 from Adrian Chadd ---
hi,
can you capture the whole dmesg from association to disconnects? I'd like to
see what's going on the whole time.
Thanks!
-adrian
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #6 from Sergey ---
wlan0: _ieee80211_crypto_delkey: NONE keyix 65535 flags 0x3 rsc 0 tsc 0 len 0
wlan0: _ieee80211_crypto_delkey: AES-CCM keyix 1 flags 0x106 rsc 0 tsc 0 len 16
wlan0: [a0:f3:c1:46:1a:f3]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #7 from Adrian Chadd ---
God damnit, okay. So it /looks/ like a single bit corruption of the RSC, which
causes the AES-CCM code to consider everything afterwards to be a replay
attack.
ie:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #11 from Sergey ---
But I already have -bgscan disabled in rc.conf and powersave mode seems to be
turned off:
$ ifconfig -v wlan0 | grep -i power
AES-CCM 3:128-bit powersavemode OFF
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #10 from Adrian Chadd ---
Yeah, that's a beacon miss. I'm not sure why that is yet.
You can try -bgscan -powersave just to enforce things, but I don't know if it's
going to help all that much. The PN
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #8 from Sergey ---
Adrian,
Do you have any thoughts about how can I fix the problem ?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #9 from Sergey ---
Got another portion of messages after "disconnection"
wlan0: beacon miss, mode STA state RUN
wlan0: send probe req on channel 9 bssid a0:f3:c1:46:1a:f3 ssid "KPECT"
wlan0: beacon miss,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #14 from Sergey ---
Hello.
I haven't seen those replays before, only yesterday, due to the messages file
it happened at 15:48 and 21:59. That's it.
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #3 from Sergey ---
Hi Adrian.
Below is what I got. Up till TSFOOR line in dmesg is what came out when the
link disapperared.
Starting from 'wlan0: _ieee80211_crypto_delkey: NONE keyix 65535 flags 0x3 rsc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #20 from Andriy Voskoboinyk ---
Is it reproducible when HT is disabled? (create_args_wlan0="-ht")
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #4 from Sergey ---
Another excerpt from dmesg:
wlan0: ieee80211_sta_ps_timer_check: lastdata=18446744071562136372,
ticks=18446744071562137461
wlan0: ieee80211_sta_ps_timer_check:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
--- Comment #15 from Sergey ---
Something new in dmesg:
ath0: ath_tx_aggr_comp_aggr: AR5416 bug: hasba=0; txok=1, isaggr=1, seq_st=3882
Q1[ 0] (nseg=2) (DS.V:0xfe01b3125700 DS.P:0xbfe3f700) I: 168cc117
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #16 from Andriy Voskoboinyk ---
wlandebug -i wlan0 state+auth+assoc+scan ?
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
Bug ID: 213621
Summary: WIFI connection is lost periodically on ath0
Product: Base System
Version: 11.0-STABLE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213621
Adrian Chadd changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214264
Sean Farley changed:
What|Removed |Added
CC||s...@freebsd.org
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163455
Guido Falsi changed:
What|Removed |Added
Resolution|--- |Overcome By
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214422
sub...@gmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214422
--- Comment #2 from sub...@gmail.com ---
(In reply to Andriy Voskoboinyk from comment #1)
I confirm this. After applying path boot as usual. Thank!
Closed.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211894
Andriy Voskoboinyk changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214422
Andriy Voskoboinyk changed:
What|Removed |Added
See Also|
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214406
Andriy Voskoboinyk changed:
What|Removed |Added
See Also|
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214435
Bug ID: 214435
Summary: controller panic: iwn0: iwn_intr: fatal firmware error
error type = "BAD_COMMAND" (0x0007)
Product: Base System
Version: 11.0-RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214435
--- Comment #1 from Markus Graf ---
Created attachment 176911
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=176911=edit
rc.conf
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214435
--- Comment #2 from Markus Graf ---
Created attachment 176912
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=176912=edit
loader.conf
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #19 from Maxim Usatov ---
Here you go.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #17 from Maxim Usatov ---
Created attachment 175978
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175978=edit
dmesg (patched kernel) before suspend
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #18 from Maxim Usatov ---
Created attachment 175979
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175979=edit
dmesg (patched kernel) after resume
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
Andriy Voskoboinyk changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
da...@catwhisker.org changed:
What|Removed |Added
CC||da...@catwhisker.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213456
Joseph Mingrone changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213456
Bug ID: 213456
Summary: Problem with iwn firmware on 11-RELEASE
Product: Base System
Version: 11.0-STABLE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213453
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213456
Adrian Chadd changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
Andriy Voskoboinyk changed:
What|Removed |Added
Severity|Affects Many People |Affects
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213456
--- Comment #1 from Sergey ---
the firmware is compiled into kernel
$ kldstat -v |grep iwn
54 pci/iwn
55 iwn6000g2afw_fw
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
--- Comment #1 from Maxim Usatov ---
It appears I was too quick with a fix, I apologize. The issue seems to be
chaotic.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213444
Bug ID: 213444
Summary: iwn Wi-Fi not working after suspend/resume, after
upgrading to 11.0
Product: Base System
Version: 11.0-STABLE
Hardware: amd64
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213207
--- Comment #12 from f...@opal.com ---
I could not get Andriy's patch to work.
/etc/rc.conf was:
ifconfig_re0="up"
ether_re0="`ifconfig re0 ether`"
wlans_ath0=wlan0
create_args_wlan0="wlanaddr ${ether_re0##*ether } regdomain FCC country
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215025
Mark Linimon changed:
What|Removed |Added
CC|freebsd-am...@freebsd.org |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215265
Bug ID: 215265
Summary: TP-Link TL-WDN3200 device periodically loses
connection on some networks
Product: Base System
Version: 11.0-STABLE
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215301
Bug ID: 215301
Summary: ifconfig list scan still abbreviates some SSID in -v
mode
Product: Base System
Version: 11.0-RELEASE
Hardware: Any
OS: Any
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211689
Alan Somers changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=149516
mar...@sugioarto.com changed:
What|Removed |Added
CC||mar...@sugioarto.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203887
--- Comment #6 from m...@netfence.it ---
I'm not prepared to switch to 11.0 now (for some reasons I won't annoy you
with).
I might consider this in a short term if it really fixes, but, if it's
possible, I'd rather patch the driver.
Would
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214264
--- Comment #2 from Neptunium ---
Sean, that's great, that was, obviously, my problem too! Thank you for your
idea, I'd never in my life guess such a thing. However, with my configuration I
have one little
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203887
--- Comment #4 from Adrian Chadd ---
hi! i thought i fixed this in freebsd-head! have you tried 11.0-RELEASE?
-a
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203887
--- Comment #3 from m...@netfence.it ---
Hello.
As I said, I added the proposed patch a long time ago and had no such panics
for more than a year.
However my laptop had another one yesterday.
ani_state->listen_time is in fact 0!
This
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215025
Bug ID: 215025
Summary: Panic in arptimer
Product: Base System
Version: 11.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215025
Andriy Voskoboinyk changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215074
Adrian Chadd changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215079
Bug ID: 215079
Summary: [ath] [panic] (Qualcomm AR9227) stuck beacon after
running a while
Product: Base System
Version: 11.0-STABLE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215079
Adrian Chadd changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215079
--- Comment #3 from Adrian Chadd ---
It'll happen from time to time depending upon RF conditions. As long as it
doesn't go deaf over time then we're okay.
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215079
--- Comment #2 from c.kw...@gmail.com ---
Added to /etc/sysctl.conf and rebooted (just in case). Not that much difference
yet.
Dec 6 06:54:45 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec 6 06:54:50 limbo kernel: ath0:
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215074
Bug ID: 215074
Summary: [ath] [panic] (Qualcomm AR9227) nightly panic during
periodic runs
Product: Base System
Version: 11.0-STABLE
Hardware: amd64
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203745
--- Comment #36 from j...@jschneider.com ---
This is great! With 11.0, A2DP is working perfectly with iwn wireless device
and OontZ XL speaker. Thank you!
--
You are receiving this mail because:
You are the assignee for the bug.
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211689
Dominic Fandrey changed:
What|Removed |Added
Status|Open|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211689
--- Comment #7 from Dominic Fandrey ---
Created attachment 178330
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=178330=edit
panic: ifconfig lagg0 destroy
It panics when I try to destroy lagg0.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211689
Dominic Fandrey changed:
What|Removed |Added
Status|In Progress |Open
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211689
--- Comment #8 from Jan Kokemüller ---
The patch in comment #4 should fix the panic when destroying a lagg device.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218007
Mark Linimon changed:
What|Removed |Added
Keywords||patch
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
801 - 900 of 2223 matches
Mail list logo