https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406
--- Comment #3 from n...@foobar.org ---
you can work around the problem by having 4 or fewer vmxnet3 interfaces, and
then using vlan interfaces on freebsd.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406
--- Comment #4 from timoth...@gmail.com ---
(In reply to nick from comment #3)
Thanks. I've switched to e1000 interfaces and the problem disappeared.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406
--- Comment #5 from n...@foobar.org ---
i wish you well with that :-) if you're running anything later than esxi build
799733, the em driver will periodically hang with watchdog timeout kernel
errors. This was catastrophic in freebsd 8/9 b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406
--- Comment #6 from timoth...@gmail.com ---
(In reply to nick from comment #5)
Awesome. Thanks for the heads up. Hopefully this bug will get some attention
soon, as I would think that using port groups with FreeBSD/pfsense would be
fairly c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200026
Bug ID: 200026
Summary: em driver reports "Watchdog timeout -- resetting" on
vmware ESXi
Product: Base System
Version: 10.1-RELEASE
Hardware: amd64
OS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200026
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|emulat...@freebsd.org
Su
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=16
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196483
Sean Bruno changed:
What|Removed |Added
CC||sbr...@freebsd.org
Attachment #151321
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196483
Sean Bruno changed:
What|Removed |Added
CC||ema...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198149
--- Comment #10 from John Baldwin ---
So I think I somewhat understand what is wrong. I'm not yet sure how to fix
it. What seems to happen is that on a context switch out, the read_pmc
operation is returning a very large value. The result
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200032
Bug ID: 200032
Summary: Race between VT and X11
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Some
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198149
--- Comment #11 from John Baldwin ---
Created attachment 156477
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=156477&action=edit
first_hack.patch
I tried this change which would cause iaf_read_pmc() to return -2 in this case
in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200032
--- Comment #1 from Hans Petter Selasky ---
Suspect: Dirty keyboard modifier(s) when Xorg starts. ALT modifier is pressed
for example.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198149
--- Comment #12 from John Baldwin ---
Finally snagged the hang with the first hack in place. By the end of the trace
all the PMCs have super high thresholds again, but here is where it went wrong:
211497 1 305651558868602 MDP:WRI:1: ia
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200032
--- Comment #2 from Hans Petter Selasky ---
Hi,
It might look like you can reproduce like this:
1) Boot computer into GDM / slim.
2) Wait more than 15 seconds.
3) Keyboard appears frozen.
4) Press ALT+F9
5) Keyboard works again.
If waiti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198149
--- Comment #13 from John Baldwin ---
Created attachment 156483
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=156483&action=edit
second_hack.patch
This prevents the PMC value from being saved as zero. When it hits zero during
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200032
Hans Petter Selasky changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|hsela...@freebsd.org
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187810
--- Comment #2 from jonas.bu...@gmail.com ---
The problem was likely caused by installing clang from ports. This defect can
be closed now.
--
You are receiving this mail because:
You are the assignee for the bug.
__
18 matches
Mail list logo
