Re: [E1000-devel] 2.6.30-rc1: e1000: list_add corruption

From: Alexander Beregalov Date: Thu, 9 Apr 2009 08:16:00 +0400 > The host has two interfaces > eth0 - e1000, eth1 - forcedeth. > Both are not working after that messages. It looks like the NAPI pending list is being modified in an illegal state by forcedeth, and mid-stream to a list_del() an e10

Re: [E1000-devel] 2.6.30-rc1: e1000: list_add corruption

2009/4/9 Alexander Beregalov : > 2009/4/9 Alexander Beregalov : >>  WARNING: at lib/list_debug.c:30 __list_add+0x89/0x90() >>  Hardware name: >>  list_add corruption. prev->next should be next (c06ea834), but was >> f70244c8. (prev=c06ea834). >>  Modules linked in: w83627hf hwmon_vid i2c_nforce2 >>

Re: [E1000-devel] [PATCH] Be explict with what we are !'ing in ixgbe_sfp_config_module_task()

On Wed, Apr 08, 2009 at 07:26:08PM -0700, Jeff Kirsher wrote: > Thanks, I will add it to my queue of ixgbe patches. Thanks. > Remember to CC netdev mailing list for networking patches. I did but due to a misconfiguration on my latop all the lisst on vger.kernel.org rejected the messsages and I

Re: [E1000-devel] 2.6.30-rc1: e1000: list_add corruption

2009/4/9 Alexander Beregalov : >  WARNING: at lib/list_debug.c:30 __list_add+0x89/0x90() >  Hardware name: >  list_add corruption. prev->next should be next (c06ea834), but was > f70244c8. (prev=c06ea834). >  Modules linked in: w83627hf hwmon_vid i2c_nforce2 >  Pid: 1436, comm: portageq Not tainted

[E1000-devel] 2.6.30-rc1: e1000: list_add corruption

WARNING: at lib/list_debug.c:30 __list_add+0x89/0x90() Hardware name: list_add corruption. prev->next should be next (c06ea834), but was f70244c8. (prev=c06ea834). Modules linked in: w83627hf hwmon_vid i2c_nforce2 Pid: 1436, comm: portageq Not tainted 2.6.30-rc1 #1 Call Trace: [] warn_slowp

Re: [E1000-devel] [PATCH] Be explict with what we are !'ing in ixgbe_sfp_config_module_task()

On Tue, Apr 7, 2009 at 9:44 PM, Tony Breeds wrote: > GCC warns: > drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_sfp_config_module_task': > drivers/net/ixgbe/ixgbe_main.c:3920: warning: suggest parentheses around > operand of '!' or change '&' to '&&' or '!' to '~' > > Which I think is right.

[E1000-devel] How To Get A Girl To Do Anythinng And Everything In Bed

How To Get A Girl To Doo Anything And Everything In Bed - Be Absolutely Mind Blowing The socalled child of hester hamiltonthe child met with constantly. and then, of course, over it was in the attitude necessary to deal the first. -

[E1000-devel] Limited time invitation to connect on TimeBridge

David is asking you to join their network on TimeBridge. Get started by checking out David's calendar: http://app.timebridge.com/user/availability/NnURXoMmgIGVwv - The TimeBridge team -- Note: This invitation is set to expire. Please reply soon. Opt-out of future reminder emails: http

Re: [E1000-devel] [PATCH] Be explict with what we are !'ing in ixgbe_sfp_config_module_task()

Tony Breeds wrote: > GCC warns: > drivers/net/ixgbe/ixgbe_main.c: In function > 'ixgbe_sfp_config_module_task': > drivers/net/ixgbe/ixgbe_main.c:3920: warning: suggest parentheses > around operand of '!' or change '&' to '&&' or '!' to '~' > > Which I think is right. Bracket to remove ambiguity

Re: [E1000-devel] Tx Unit Hang on 82540EP

If it is an interrupt problem it could be due to an old BIOS. Please check to make sure you have the latest released BIOS on the system. Other than that, I agree with all that Jesse has said. Cheers, John --- "...that your people will j