Re: [E1000-devel] getting VF link info seems to be broken in 3.9-rc8

2013-04-25 Thread Alexander Duyck
On 04/25/2013 01:49 PM, David Miller wrote: > From: Stephen Hemminger > Date: Thu, 25 Apr 2013 13:45:13 -0700 > >> On Thu, 25 Apr 2013 13:36:06 -0700 >> Alexander Duyck wrote: >> >>> On 04/25/2013 01:25 PM, David Miller wrote: From: Alexander Duyck Date: Thu, 25 Apr 2013 13:20:24 -0700

Re: [E1000-devel] getting VF link info seems to be broken in 3.9-rc8

2013-04-25 Thread David Miller
From: Stephen Hemminger Date: Thu, 25 Apr 2013 13:45:13 -0700 > On Thu, 25 Apr 2013 13:36:06 -0700 > Alexander Duyck wrote: > >> On 04/25/2013 01:25 PM, David Miller wrote: >> > From: Alexander Duyck >> > Date: Thu, 25 Apr 2013 13:20:24 -0700 >> > >> >> On 04/25/2013 12:24 PM, David Miller wro

Re: [E1000-devel] getting VF link info seems to be broken in 3.9-rc8

2013-04-25 Thread Stephen Hemminger
On Thu, 25 Apr 2013 13:36:06 -0700 Alexander Duyck wrote: > On 04/25/2013 01:25 PM, David Miller wrote: > > From: Alexander Duyck > > Date: Thu, 25 Apr 2013 13:20:24 -0700 > > > >> On 04/25/2013 12:24 PM, David Miller wrote: > >>> From: Alexander Duyck > >>> Date: Thu, 25 Apr 2013 11:29:04 -070

Re: [E1000-devel] getting VF link info seems to be broken in 3.9-rc8

2013-04-25 Thread Alexander Duyck
On 04/25/2013 01:25 PM, David Miller wrote: > From: Alexander Duyck > Date: Thu, 25 Apr 2013 13:20:24 -0700 > >> On 04/25/2013 12:24 PM, David Miller wrote: >>> From: Alexander Duyck >>> Date: Thu, 25 Apr 2013 11:29:04 -0700 >>> >>> diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c >>> ind

Re: [E1000-devel] getting VF link info seems to be broken in 3.9-rc8

2013-04-25 Thread David Miller
From: Alexander Duyck Date: Thu, 25 Apr 2013 13:20:24 -0700 > On 04/25/2013 12:24 PM, David Miller wrote: >> From: Alexander Duyck >> Date: Thu, 25 Apr 2013 11:29:04 -0700 >> >> diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c >> index b65441d..23854b5 100644 >> --- a/net/core/rtnetlink.

Re: [E1000-devel] getting VF link info seems to be broken in 3.9-rc8

2013-04-25 Thread Alexander Duyck
On 04/25/2013 12:24 PM, David Miller wrote: > From: Alexander Duyck > Date: Thu, 25 Apr 2013 11:29:04 -0700 > >> I did a bit of digging and it looks like the issue is that the >> ext_filter_mask is not being found in the message received in >> rtnl_dump_ifinfo. I'm still trying to figure out why

Re: [E1000-devel] getting VF link info seems to be broken in 3.9-rc8

2013-04-25 Thread David Miller
From: Alexander Duyck Date: Thu, 25 Apr 2013 11:29:04 -0700 > I did a bit of digging and it looks like the issue is that the > ext_filter_mask is not being found in the message received in > rtnl_dump_ifinfo. I'm still trying to figure out why the kernel isn't > finding the flag when it was find

Re: [E1000-devel] getting VF link info seems to be broken in 3.9-rc8

2013-04-25 Thread Alexander Duyck
I did a bit of digging and it looks like the issue is that the ext_filter_mask is not being found in the message received in rtnl_dump_ifinfo. I'm still trying to figure out why the kernel isn't finding the flag when it was finding it previously, but I'm not much of a netlink expert. Thanks, Ale

Re: [E1000-devel] igb hardware error - recovery

2013-04-25 Thread Wyborny, Carolyn
Hello, That error means there's been a problem with the hw initialization. There's one driver instance for each port of the device, so looping through doesn't make sense. You have to find why the init is failing. Usually its because the driver doesn't recognize the part for some reason. If

Re: [E1000-devel] igb hardware error - recovery

2013-04-25 Thread ratheesh kannoth
what i meant is if is it ok to loop through and do until no hardware error. can i do while (!e1000_init_hw(hw)) ; -Ratheesh On Thu, Apr 25, 2013 at 7:15 PM, ratheesh kannoth wrote: > i could see "hardware error" some times . it is > coming from following code snippet in igb_main.c >

[E1000-devel] igb hardware error - recovery

2013-04-25 Thread ratheesh kannoth
i could see "hardware error" some times . it is coming from following code snippet in igb_main.c /**/ if (e1000_init_hw(hw)) dev_err(pci_dev_to_dev(pdev), "Hardware Error\n"); /**/ How