[E1000-devel] [PATCH] net: e100: ucode is optional in some cases

2012-07-19 Thread Bjørn Mork
commit 9ac32e1b firmware: convert e100 driver to request_firmware() did a straight conversion of the in-driver ucode to external files. This introduced the possibility of the driver failing to enable an interface due to missing ucode. There was no evaluation of the importance of the ucode at

Re: [E1000-devel] [PATCH] net: e100: ucode is optional in some cases

2012-07-19 Thread David Miller
From: Bjørn Mork bj...@mork.no Date: Thu, 19 Jul 2012 11:33:13 +0200 + * http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/fxp/rcvbundl.h?rev=HEAD;content-type=text%2Fplain Please don't put URLs into the source code, they generally lack permanence.

[E1000-devel] Informasi Training Effective communication skill Training Coaching and Counseling

2012-07-19 Thread info training
Your email client cannot read this email. To view it online, please go here: http://www.solutioncentreindonesia.com/mm/display.php?M=16912C=661d88d746197c1376c21d5547a358f8S=14L=1N=14 To stop receiving these

[E1000-devel] [PATCH v2] net: e100: ucode is optional in some cases

2012-07-19 Thread Bjørn Mork
commit 9ac32e1b firmware: convert e100 driver to request_firmware() did a straight conversion of the in-driver ucode to external files. This introduced the possibility of the driver failing to enable an interface due to missing ucode. There was no evaluation of the importance of the ucode at

Re: [E1000-devel] [PATCH v2] net: e100: ucode is optional in some cases

2012-07-19 Thread David Miller
From: Bjørn Mork bj...@mork.no Date: Thu, 19 Jul 2012 18:28:40 +0200 commit 9ac32e1b firmware: convert e100 driver to request_firmware() did a straight conversion of the in-driver ucode to external files. This introduced the possibility of the driver failing to enable an interface due to

Re: [E1000-devel] 82571EB - Detected Hardware Unit Hang

2012-07-19 Thread Andrew Peng
Attached is the dmesg output. Please let me know if this looks right. There are two instances of the error here: [361106.726601] e1000e :02:00.0: eth1: Detected Hardware Unit Hang: [361106.726604] TDH c5 [361106.726606] TDT c7 [361106.726607]

Re: [E1000-devel] 82571EB - Detected Hardware Unit Hang

2012-07-19 Thread Flavio Leitner
Those messages reminds me this bug: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=09357b00255c233705b1cf6d76a8d147340545b8 and then: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=bf03085f85112eac2d19036ea3003071220285bb Can you

Re: [E1000-devel] 82571EB - Detected Hardware Unit Hang

2012-07-19 Thread Dave, Tushar N
Andrew, I don't think current message level set correctly. Have you ran 'ethtool -s ethx msglvl 0x2c01' I don't see HW ring dump in the log. Please confirm that msglvl is set correctly by running 'ethtool ethx' -Tushar -Original Message- From: Andrew Peng [mailto:peng...@gmail.com]

Re: [E1000-devel] 82571EB - Detected Hardware Unit Hang

2012-07-19 Thread Andrew Peng
Flavio; I am using the stock kernel driver with the stock Debian Squeeze kernel. Tushar; I've double checked that the message level is set correctly: Current message level: 0x2c01 (11265) Link detected: yes However, I just checked all of the logs on the server and I do not

Re: [E1000-devel] 82571EB - Detected Hardware Unit Hang

2012-07-19 Thread Flavio Leitner
On Thu, 19 Jul 2012 20:17:14 -0500 Andrew Peng peng...@gmail.com wrote: Flavio; I am using the stock kernel driver with the stock Debian Squeeze kernel. Well, I don't have the debian kernel sources handy to check, but based on the version 2.6.32-5-amd64, It sounds like you don't have. I

Re: [E1000-devel] 82571EB - Detected Hardware Unit Hang

2012-07-19 Thread Dave, Tushar N
In that case, you can use our e1000e outbox driver from Sourceforge (which should have patches mentioned by Flavio). -Tushar -Original Message- From: Flavio Leitner [mailto:f...@redhat.com] Sent: Thursday, July 19, 2012 6:39 PM To: Andrew Peng Cc: Dave, Tushar N;