On 4/22/11 5:08 PM, Andrew Boyer wrote:
Hello Steve and Jack,
You need to handle the SIOCSIFADDR ioctl or it gets passed up the stack to
ether_ioctl(). When it goes up the interface gets reset. See the comments in
em_ioctl() and igb_ioctl().
We fixed this in ixgbe in our internal tree and it
On 4/22/11 3:35 PM, Jack Vogel wrote:
OK, did some testing, this re-init with link transition will happen on both
the 1G
drivers as well as ixgbe, its due to the stack/ioctl behavior when you do
the
ifconfig.
So, what are you comparing this to that DOESN'T do this?? If this were to
be kept from
Whoops, I see what you're talking about Andrew, OK, I get it, Steve I have
another
set of changes to get into ixgbe soon anyway, I'll roll this change up with
that and
then let you test it as soon as I get something ready, ok? Early next week.
Jack
On Fri, Apr 22, 2011 at 5:08 PM, Andrew Boyer w
Hello Steve and Jack,
You need to handle the SIOCSIFADDR ioctl or it gets passed up the stack to
ether_ioctl(). When it goes up the interface gets reset. See the comments in
em_ioctl() and igb_ioctl().
We fixed this in ixgbe in our internal tree and it seems to work fine with
82598 and 82599.
Just double checked on igb1 on the same machine, adding an alias causes
no loss in network from the primary or existing ip aliases for the nic.
So this should be eliminating most variables except the driver?
Regards
Steve
- Original Message -
From: "Jack Vogel"
To: "Steven Hart
Yes that works just as expected, never had this behaviour with any nic. Noticed
straight away when we
swapped from the igb (was em on 7.0) as when the jails on the machines booted
they broke services
on the main machine which where in the middle of initialising when the network
went down again.
OK, did some testing, this re-init with link transition will happen on both
the 1G
drivers as well as ixgbe, its due to the stack/ioctl behavior when you do
the
ifconfig.
So, what are you comparing this to that DOESN'T do this?? If this were to
be kept from happening I'm not sure where the respon
I see you have igb devices, if you do this with those interfaces is the
behavior different?
I will have to look into this, thanks for the report.
Jack
On Fri, Apr 22, 2011 at 3:08 PM, Steven Hartland wrote:
> Sorry yes I did meant just add an ip alias to the nic or remove it
> e.g.
> ifconfig
Sorry yes I did meant just add an ip alias to the nic or remove it
e.g.
ifconfig ix0 10.10.1.10/32 alias
ifconfig ix0 10.10.1.10 -alias
pciconf -lv
hostb0@pci0:0:0:0: class=0x06 card=0xa28015d9 chip=0x40038086 rev=0x20
hdr=0x00
vendor = 'Intel Corporation'
device = '5400B
It looks like it helped me too. It's great. How did you found that
workaround?
Do you have ideas why negotiations breaks connection?
- CG
22.04.2011 19:22 пользователь "K. Macy" написал:
On Fri, Apr 22, 2011 at 4:58 PM, cyberGn0m wrote:
> At Linux I have no problem...
I don't think disabling
On Wed, Apr 20, 2011 at 9:37 AM, Steven Hartland
wrote:
> Seems there's an issue with the intel ix driver which causes
> it to bin connections when you manipulate ip aliases.
>
> This causes issues on boot when jails start as it bins other
> active sessions.
>
> Is this a know issue?
>
> Running 8
Please give me the exact steps that are performed that create this, not
sure what you mean by "manipulate ip aliases", if you mean ifconfig ix0
address,
then this has always caused a reinit of the device, the same behavior is in
the
1G devices. Or do you mean something else?
Oh, and while at it, p
Hi Jack do you have any idea what's going on here as it very disruptive
for every IP change to cause total outage on the machine?
- Original Message -
From: "Steven Hartland"
To:
Sent: Wednesday, April 20, 2011 2:37 PM
Subject: Intel ix (X520) disconnects when manipulating ips?
See
On Fri, Apr 22, 2011 at 4:58 PM, cyberGn0m wrote:
> At Linux I have no problems with this device. How to disable negotiation?
I don't think disabling checksums and tso are necessary, but they
don't really matter at 100Mbps.
# This file now contains just the overrides from /etc/defaults/rc.conf.
At Linux I have no problems with this device. How to disable negotiation?
2011/4/22 K. Macy
> I've had the same problem on my Shuttle box on both Linux and FreeBSD.
> I work around it by disabling auto-negotiation and forcing it to
> 100Mbit.
>
> On Thu, Apr 21, 2011 at 10:45 AM, cyberGn0m wrot
I've had the same problem on my Shuttle box on both Linux and FreeBSD.
I work around it by disabling auto-negotiation and forcing it to
100Mbit.
On Thu, Apr 21, 2011 at 10:45 AM, cyberGn0m wrote:
> Hi all
>
> Some other investigations done and I found the following: device still
> receives data b
On Fri, 2011-04-22 at 14:09 +0200, Marius Strobl wrote:
> On Fri, Apr 22, 2011 at 10:07:11AM +, Bjoern A. Zeeb wrote:
[...]
> > One thing I am still pondering is whether we would be able to reserve
> > enough spares (wherever needed) to be able to eventually allow to
> > query-through and gat
On Fri, Apr 22, 2011 at 10:07:11AM +, Bjoern A. Zeeb wrote:
> On Apr 21, 2011, at 8:33 PM, Marius Strobl wrote:
>
> Hi,
Hi
>
> I fear the change is too big for me to review currently.
Given that the majority of changes break backwards compatibility in
some way I intend to comitting them in
On Apr 21, 2011, at 8:33 PM, Marius Strobl wrote:
Hi,
I fear the change is too big for me to review currently.
One thing I am still pondering is whether we would be able to reserve enough
spares (wherever needed) to be able to eventually allow to query-through and
gather a lot more information
19 matches
Mail list logo
