Alex,

Thank you for the patch.  I've just hit an serious
work crunch, so I have to set this project aside
for about a month.  Sorry about that.

I will check out the patch once the other critical
deadline is met.

David




At 09:40 10/20/2008 -0700, Duyck, Alexander H wrote:
>David,
>
>The attached patch does two things.  One it adds a bit more to 
>the dmesg output for the driver when the interface is brought up 
>via ifconfig.  You should seem some messages about MSIXBM(x) in 
>there.  Also there is a workaround included to bring the link up 
>without need for the link status change interrupt, but it will 
>only work on initial driver load if the interface is already 
>connected.
>
>My main concern at this point is that the interrupts don't seem 
>to be making it from the adapter to the system.  This could 
>either be due to a misrouting or dropping of the interrupt.  If 
>you could try the attached patch and let me know how it works I 
>would appreciate it.  Basically the two things I would be 
>looking for would be the dmesg output after you configure the IP 
>address of the interface, and a dump of /proc/interrupts after 
>trying to pass some traffic.
>
>Thanks,
>
>Alex
>
>
><file://C:\w\Eudora\attach\igb_82575_msix_info.patch> 
>igb_82575_msix_info.patch 


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel

Reply via email to