Yes - it is a work around for broken/incomplete emulation or incorrect
interrupt routing. Always doing this would result in a performance hit on all
systems. As shown in your dmesg, both em(4) devices are using the same IRQ:
Long time ago I tried five Intel network cards in the same computer,
On 2012-11-26, Mihai Popescu mih...@gmail.com wrote:
Yes - it is a work around for broken/incomplete emulation or incorrect
interrupt routing. Always doing this would result in a performance hit on all
systems. As shown in your dmesg, both em(4) devices are using the same IRQ:
Long time ago I
Doing Per-Olov's advice on
http://marc.info/?l=openbsd-miscm=133771632704741w=2
and applying the following, fixes the problem.
Should I stick with this or is there another reason it has not been
included in current so far?
regards,
Giannis
Index: machdep.c
On Thu, 22 Nov 2012, Kapetanakis Giannis wrote:
Doing Per-Olov's advice on
http://marc.info/?l=openbsd-miscm=133771632704741w=2
and applying the following, fixes the problem.
Should I stick with this or is there another reason it has not been
included in current so far?
Yes - it is a work
On 22/11/12 15:42, Joel Sing wrote:
On Thu, 22 Nov 2012, Kapetanakis Giannis wrote:
Doing Per-Olov's advice on
http://marc.info/?l=openbsd-miscm=133771632704741w=2
and applying the following, fixes the problem.
Should I stick with this or is there another reason it has not been
included in
Hi,
It seems I come up on this
http://marc.info/?l=openbsd-miscm=133651882630852w=2
I've running latest -current i386 on KVM with mpbios disabled.
Today I've enabled a new em(4) interface. Immediately when I enable the
second interface and set an IP I get
em1: watchdog timeout -- resetting
6 matches
Mail list logo
