[Bug 215079] [ath] [panic] (Qualcomm AR9227) stuck beacon after running a while

2016-12-05 Thread bugzilla-noreply
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 on the CC list for the bug. ___

[Bug 215079] [ath] [panic] (Qualcomm AR9227) stuck beacon after running a while

2016-12-05 Thread bugzilla-noreply
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: s

[Bug 215079] [ath] [panic] (Qualcomm AR9227) stuck beacon after running a while

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215079 Adrian Chadd changed: What|Removed |Added CC||adr...@freebsd.org --- Comment #1 f

[Bug 215079] [ath] [panic] (Qualcomm AR9227) stuck beacon after running a while

2016-12-05 Thread bugzilla-noreply
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 O

[Bug 215077] bhyve should allow per-guest configuration of CPU socket/cores/threads

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215077 Peter Grehan changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|gre...@freebsd.org Keywor

[Bug 215077] bhyve should allow per-guest configuration of CPU socket/cores/threads

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215077 Bug ID: 215077 Summary: bhyve should allow per-guest configuration of CPU socket/cores/threads Product: Base System Version: CURRENT Hardware: amd64 O

[Bug 215074] [ath] [panic] (Qualcomm AR9227) nightly panic during periodic runs

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215074 Adrian Chadd changed: What|Removed |Added CC||adr...@freebsd.org --- Comment #1 f

[Bug 215074] [ath] [panic] (Qualcomm AR9227) nightly panic during periodic runs

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215074 --- Comment #2 from Adrian Chadd --- (please file a separate bug for "AR9227 stuck beacon after running a while"; as those need to get addressed still!) -- You are receiving this mail because: You are on the CC list for the bug. _

[Bug 215074] [ath] [panic] (Qualcomm AR9227) nightly panic during periodic runs

2016-12-05 Thread bugzilla-noreply
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 O

[Bug 215067] [zfs] g_dev_taste: make_dev_p() failed on importing pool with snapshots with long names

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215067 Bug ID: 215067 Summary: [zfs] g_dev_taste: make_dev_p() failed on importing pool with snapshots with long names Product: Base System Version: 10.3-RELEASE Hardware: a