Menu
▾
▴
e1000-devel — Discussion of the Intel Ethernet out-of-tree drivers
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
(1) |
Apr
(9) |
May
(3) |
Jun
|
Jul
(3) |
Aug
(6) |
Sep
|
Oct
(7) |
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
(5) |
Mar
(10) |
Apr
(2) |
May
(22) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(3) |
Oct
|
Nov
(36) |
Dec
(52) |
| 2005 |
Jan
(9) |
Feb
(13) |
Mar
(9) |
Apr
|
May
(14) |
Jun
(5) |
Jul
(20) |
Aug
(31) |
Sep
(2) |
Oct
(3) |
Nov
(18) |
Dec
(18) |
| 2006 |
Jan
(36) |
Feb
(16) |
Mar
(76) |
Apr
(78) |
May
(32) |
Jun
(30) |
Jul
(67) |
Aug
(43) |
Sep
(54) |
Oct
(116) |
Nov
(223) |
Dec
(158) |
| 2007 |
Jan
(180) |
Feb
(71) |
Mar
(110) |
Apr
(114) |
May
(203) |
Jun
(100) |
Jul
(238) |
Aug
(191) |
Sep
(177) |
Oct
(171) |
Nov
(211) |
Dec
(159) |
| 2008 |
Jan
(227) |
Feb
(288) |
Mar
(197) |
Apr
(253) |
May
(132) |
Jun
(152) |
Jul
(109) |
Aug
(143) |
Sep
(157) |
Oct
(198) |
Nov
(121) |
Dec
(147) |
| 2009 |
Jan
(105) |
Feb
(61) |
Mar
(191) |
Apr
(161) |
May
(118) |
Jun
(172) |
Jul
(166) |
Aug
(67) |
Sep
(86) |
Oct
(79) |
Nov
(118) |
Dec
(181) |
| 2010 |
Jan
(136) |
Feb
(154) |
Mar
(92) |
Apr
(83) |
May
(101) |
Jun
(66) |
Jul
(118) |
Aug
(78) |
Sep
(134) |
Oct
(131) |
Nov
(132) |
Dec
(104) |
| 2011 |
Jan
(79) |
Feb
(104) |
Mar
(144) |
Apr
(145) |
May
(130) |
Jun
(169) |
Jul
(146) |
Aug
(76) |
Sep
(113) |
Oct
(82) |
Nov
(145) |
Dec
(122) |
| 2012 |
Jan
(132) |
Feb
(106) |
Mar
(145) |
Apr
(238) |
May
(140) |
Jun
(162) |
Jul
(166) |
Aug
(147) |
Sep
(80) |
Oct
(148) |
Nov
(192) |
Dec
(90) |
| 2013 |
Jan
(139) |
Feb
(162) |
Mar
(174) |
Apr
(81) |
May
(261) |
Jun
(301) |
Jul
(106) |
Aug
(175) |
Sep
(305) |
Oct
(222) |
Nov
(95) |
Dec
(120) |
| 2014 |
Jan
(196) |
Feb
(171) |
Mar
(146) |
Apr
(118) |
May
(127) |
Jun
(93) |
Jul
(175) |
Aug
(66) |
Sep
(85) |
Oct
(120) |
Nov
(81) |
Dec
(192) |
| 2015 |
Jan
(141) |
Feb
(133) |
Mar
(189) |
Apr
(126) |
May
(59) |
Jun
(117) |
Jul
(56) |
Aug
(97) |
Sep
(44) |
Oct
(48) |
Nov
(33) |
Dec
(87) |
| 2016 |
Jan
(37) |
Feb
(56) |
Mar
(72) |
Apr
(65) |
May
(66) |
Jun
(65) |
Jul
(98) |
Aug
(54) |
Sep
(84) |
Oct
(68) |
Nov
(69) |
Dec
(60) |
| 2017 |
Jan
(30) |
Feb
(38) |
Mar
(53) |
Apr
(6) |
May
(2) |
Jun
(5) |
Jul
(15) |
Aug
(15) |
Sep
(7) |
Oct
(18) |
Nov
(23) |
Dec
(6) |
| 2018 |
Jan
(39) |
Feb
(5) |
Mar
(34) |
Apr
(26) |
May
(27) |
Jun
(5) |
Jul
(12) |
Aug
(4) |
Sep
|
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2019 |
Jan
(7) |
Feb
(10) |
Mar
(21) |
Apr
(26) |
May
(4) |
Jun
(5) |
Jul
(11) |
Aug
(6) |
Sep
(7) |
Oct
(13) |
Nov
(3) |
Dec
(17) |
| 2020 |
Jan
|
Feb
(3) |
Mar
(3) |
Apr
(5) |
May
(2) |
Jun
(5) |
Jul
|
Aug
|
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(7) |
| 2021 |
Jan
(9) |
Feb
(10) |
Mar
(18) |
Apr
(1) |
May
(3) |
Jun
|
Jul
(16) |
Aug
(2) |
Sep
|
Oct
|
Nov
(9) |
Dec
(2) |
| 2022 |
Jan
(3) |
Feb
|
Mar
(9) |
Apr
(8) |
May
(5) |
Jun
(6) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(7) |
Dec
(2) |
| 2023 |
Jan
(7) |
Feb
(2) |
Mar
(6) |
Apr
|
May
(4) |
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(2) |
Nov
(4) |
Dec
(10) |
| 2024 |
Jan
(4) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
1
(6) |
2
(9) |
3
(2) |
|
4
(1) |
5
(4) |
6
(5) |
7
(7) |
8
(4) |
9
|
10
(2) |
|
11
|
12
(5) |
13
(5) |
14
(10) |
15
(8) |
16
(4) |
17
(1) |
|
18
(1) |
19
(14) |
20
(8) |
21
(15) |
22
(12) |
23
(3) |
24
|
|
25
|
26
(1) |
27
(1) |
28
(2) |
29
(1) |
30
(1) |
31
|
|
From: Aysche h. <dk...@bo...> - 2008-05-30 08:16:16
|
Ein international taetiges Betrieb ist seit kurzem in Europa. Wir suchen nach Ihnen!! Sie moechten eine neue und interessante Arbeit, haben etwas Zeit und kennen Sich ein wenig mit Internet aus. Melden Sie sich bei uns fuer gratis Info unter : el...@bo... und lassen Sie sich faszinieren. 2000 monatlich zu kriegen moeglich Mit freundlichen Gruessen EL Team |
|
From: Brandeburg, J. <jes...@in...> - 2008-05-29 16:33:10
|
March, Agustin M wrote: > Hi > I am having some issues with the ibg driver (1.2.22) and Intel > Corp. 82575EB Gigabit Network attached to Intel Corp. 82801I (ICH9 > Family) PCI Express on RedHat 2.6.18-53.el5 x86_64 arch. > > I am working with HPC equipment, I need to disable the Interruption, > so I set the InterruptThrottleRate parameter to 0,0 in order to > disable. However, the Interrupt seems to be not fully disabled. For > instance, so you want to disable any interrupt moderation in order to minimize end to end latency, correct? > 1- if I left the InterruptThrottleRate as defult and irq balance on > --- the latency is ~60uSeg > 2- if I set the InterruptThrottleRate to O,O irq balance on --- the > latency is ~29uSeg > > 3- if I set the InterruptThrottleRate to O,O and IntMode=0,0 irq > balance off --- the latency is ~20uSeg > 4- if I set the InterruptThrottleRate to O,O and IntMode=1,1 irq > balance off --- the latency is ~18uSeg what test are you using to measure latency? netperf? netpipe? have you tried InterruptThrottleRate=100000,100000 instead of 0,0? looking at cat /proc/interrupts during your test would provide some interesting feedback. 1) load driver: 2) start test: 3) for ((i=1;i<20;i++)); do echo -n `date` >> intfile ; grep eth /proc/interrupts >> intfile; sleep 1; done send us intfile (inline in mail is best, list doesn't take attachments very well) > Could some one explain me what could be happening? It is correct to > modify the IntMode and the Irqbalance to switch to off for this king > of chipset? > Please, any comment will be a great help to us when you play with IntMode you're modifying the kind of interrupt and how many there are in the driver. MSI-X mode (the default) *should* be the lowest overhead. IntMode=0 is least preferable because you might end up sharing an interrupt. IntMode=1 or 2 is preferred, but whichever works best for you is probably okay. the best way for you to compare the interrupts would be to boot with maxcpus=1 and then run your tests. This would tell you if you need to be sure to run taskset and set smp_affinity on the interrupts, in addition to disabling irqbalance user space daemon. Jesse |
|
From: Ronciak, J. <joh...@in...> - 2008-05-28 22:53:54
|
They should be shipping in early Q3 I think. I can't speak for the marketing folks however. This is an engineering list. You can contact your local Intel office who should be able to tell you an exact date. Cheers, John ----------------------------------------------------------- "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety.", Benjamin Franklin 1755 -----Original Message----- From: e10...@li... [mailto:e10...@li...] On Behalf Of Richard Scobie Sent: Tuesday, May 27, 2008 9:49 PM To: e10...@li... Subject: [E1000-devel] Intel(r) 10 Gigabit AT Server Adapter Anyone know when this will be available for purchase? http://www.intel.com/network/connectivity/products/10GbE_AT_server_adapt er/overview.htm Regards, Richard ------------------------------------------------------------------------ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ E1000-devel mailing list E10...@li... https://lists.sourceforge.net/lists/listinfo/e1000-devel |
|
From: Richard S. <ri...@sa...> - 2008-05-28 04:41:56
|
Anyone know when this will be available for purchase? http://www.intel.com/network/connectivity/products/10GbE_AT_server_adapter/overview.htm Regards, Richard |
|
From: Graffa <Sam...@Le...> - 2008-05-27 13:56:29
|
I just realized my dreams of sex in the city http://www.posalgo.com/ |
|
From: baden <rag...@Vi...> - 2008-05-26 14:07:20
|
Your long and hard tool is set to satisfy http://www.diplexen.com/ |
|
From: March, A. M <agu...@in...> - 2008-05-23 22:17:40
|
Hi
I am having some issues with the ibg driver (1.2.22) and Intel
Corp. 82575EB Gigabit Network attached to Intel Corp. 82801I (ICH9
Family) PCI Express on RedHat 2.6.18-53.el5 x86_64 arch.
I am working with HPC equipment, I need to disable the Interruption, so
I set the InterruptThrottleRate parameter to 0,0 in order to disable.
However, the Interrupt seems to be not fully disabled. For instance,
1- if I left the InterruptThrottleRate as defult and irq balance on ---
the latency is ~60uSeg
2- if I set the InterruptThrottleRate to O,O irq balance on --- the
latency is ~29uSeg
3- if I set the InterruptThrottleRate to O,O and IntMode=0,0 irq balance
off --- the latency is ~20uSeg
4- if I set the InterruptThrottleRate to O,O and IntMode=1,1 irq balance
off --- the latency is ~18uSeg
Could some one explain me what could be happening? It is correct to
modify the IntMode and the Irqbalance to switch to off for this king of
chipset?
Please, any comment will be a great help to us
filename: /lib/modules/2.6.18-53.el5/kernel/drivers/net/igb/igb.ko
version: 1.2.22
license: GPL
description: Intel(R) Gigabit Ethernet Network Driver
author: Intel Corporation, <e10...@li...>
srcversion: 3453E88A6E046972DD03154
alias: pci:v00008086d000010D6sv*sd*bc*sc*i*
alias: pci:v00008086d000010A9sv*sd*bc*sc*i*
alias: pci:v00008086d000010A7sv*sd*bc*sc*i*
depends:
vermagic: 2.6.18-53.el5 SMP mod_unload gcc-4.1
parm: InterruptThrottleRate:Interrupt Throttling Rate (array
of int)
parm: IntMode:Interrupt Mode (array of int)
parm: LLIPort:Low Latency Interrupt TCP Port (array of int)
parm: LLIPush:Low Latency Interrupt on TCP Push flag (array of
int)
parm: LLISize:Low Latency Interrupt on Packet Size (array of
int)
parm: debug:Debug level (0=none, ..., 16=all) (int)
Kernel Parameter
ro root=LABEL=/ pci=msi console=ttyS1,115200
..
Regards,
Agustin March <mailto:agu...@in...>
Argentina Distributing Computing Solution
+54 351 5265618
Intel Argentina S.A.
|
|
From: constantino s. <pau...@tv...> - 2008-05-23 18:15:56
|
Play games - poker - casino - win - money gamble on the best since 1998. |
|
From: Tantilov, E. S <emi...@in...> - 2008-05-23 15:38:12
|
Thanks for the info. I will try to reproduce here in the lab. You mentioned that the distribution you use is SLES10 - can you provide the exact kernel version (uname -a)? Thanks, Emil -----Original Message----- From: z1...@au... [mailto:z1...@au...] Sent: Thursday, May 22, 2008 12:14 AM To: Ronciak, John; Tantilov, Emil S Cc: e10...@li... Subject: Re: RE: [E1000-devel] e1000 freezing during boot Yes it is reproducible (though unfortunately not very reliable) on multiple systems, with three types of hardware in them. First type has two interfaces with ethernet pro 100 cards and one 82540EM based Second type has three interfaces all 82546GB based Third type with three 82571EB interfaces 1. yes 2. yes 3. yes (it is always after a reboot, card never enters this state during runtime - as far as we have seen) On Thu 22/05/08 2:01 AM , "Tantilov, Emil S" sent: > z1...@au... > wrote: > > Hello, > > > This may sound doubtful, but this is not happening on > one box, or > > only in one network environment, and is reproducible > > > though not really reliable, but 5-6 reboots bring NIC > into this state > > > OK - so from your description it seems that the issue is reproducible on > > multiple (different?) systems - is this correct? > > > > If we can get some more details about the failure it will at least point > > to whether this is system or NIC specific. Please reply with yes or no: > > > > 1. Are you seeing the issue on multiple systems (preferably not of the > > same type).? > > > > 2. Are you seeing this with different NICs or just the one you reported > > in the initial email? > > > > 3. Can you provide simple steps to reproduce? You mentioned reboots - is > > it fair to say that you see the issue after several reboots? > > > > > when we first get rx_no_buffer_count in -S then after > some > > point it stops and starts counting rx_missed packets. > This has been > > seen on 8 boxes so far, probably more, but only 8 > reported. And the > > problem started to show itself after update from 7.0.33 > to 7.6.15.5. > > > 7.0.33 to 7.6.15.5 is a big leap, if you can maybe narrow the gap a bit > > more by testing versions in betweeen that would certainly help. > > > > Thanks, > > Emil > > > > ---- Msg sent via email.ru |
|
From: Ronciak, J. <joh...@in...> - 2008-05-22 17:32:46
|
IPMI is configured in the system and I think the BIOS. Turn it off completely. If ther eis a BIOS setting disable it there. If not, disable it on the system. This may mean you have to unload the ipmi driver. There is plenty out there so just google for it. Cheers, John ----------------------------------------------------------- "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety.", Benjamin Franklin 1755 -----Original Message----- From: z1...@au... [mailto:z1...@au...] Sent: Thursday, May 22, 2008 12:53 AM To: Ronciak, John Cc: e10...@li... Subject: Re: RE: Re: [E1000-devel] e1000 freezing during boot unplugging the cables from two other interfaces doesn't have any effect. the same situation - packets not being received after several reboots. What do you mean by "ipmi being not configured"? Just disable BMC Arp control? On Thu 22/05/08 12:46 AM , "Ronciak, John" sent: > Please answer the questions that I asked. They will add information to > > this problem which nobody else outside you and your team are seeing. > > > > > > Cheers, > > John > > ----------------------------------------------------------- > > "Those who would give up essential Liberty, to purchase a little > > temporary Safety, deserve neither Liberty nor Safety.", Benjamin > > Franklin 1755 > > > > -----Original Message----- > > From: z1...@au... [z1...@au...] > Sent: Wednesday, May 21, 2008 1:43 PM > > To: Ronciak, John > > Cc: e10...@li... > Subject: Re: Re: [E1000-devel] e1000 freezing during boot > > > > Hello, > > This may sound doubtful, but this is not happening on one box, or only > > in one network environment, and is reproducible > > though not really reliable, but 5-6 reboots bring NIC into this state > > when we first get rx_no_buffer_count in -S then after some > > point it stops and starts counting rx_missed packets. This has been seen > > on 8 boxes so far, probably more, but only 8 reported. And the problem > > started to show itself after update from 7.0.33 to 7.6.15.5. Maybe we > > are missing something in configuration? Maybe some driver parameters are > > incorrect? setting debug to 16, or to 21 (as suggested in one of the > > mails in another thread) doesn't produce any useful info to understand > > what is wrong. Though dmesg show that watchdog for eth2 is running and a > > message that TSO is on follows.. > > > > Thanks for the support. > > > > On Thu 22/05/08 12:25 AM , "Ronciak, John" sent: > > > Doubtful. This is not happening to anyone else so it's > something to > do > > > > > > with your configuration or environment. > > > > > > > > > > > > If you don't have the other 2 interface running at all, > does it work? > > > > > How about if you don't have IPMI configured on the > first 2 interfaces? > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > John > > > > > > > ----------------------------------------------------------- > > > > > "Those who would give up essential Liberty, to purchase > a little > > > > > temporary Safety, deserve neither Liberty nor Safety.", > Benjamin > > > > > Franklin 1755 > > > > > > > > > > > > -----Original Message----- > > > > > > From: Stanislav Bogatyrev [realloc@gma > > il.com] > > > Sent: Wednesday, May 21, 2008 1:16 PM > > > > > > To: Tantilov, Emil S > > > > > > Cc: Ronciak, John; e10...@li... > > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > > > > > > > > > Hello, > > > > > > > > > > > > ethtool -r helps, but not always... ifconfig down/up > never helps. What > > > > > can cause this problem? It seems that driver > incorrectly detects NIC > > > > > state and doen't start receiver properly? > > > > > > > > > > > > On Wed, May 21, 2008 at 10:29 PM, Tantilov, Emil S > > > > > > emi > > > l.s.ta > nt...@in...> wrote: > > > This command will reset the interface. I bet the same > > > effect can be > > > > achieved with ethtool -r eth0 > > > > > > > > > > > > > > Have you tried ifconfig eth0 down/up? Looks like an > > > interface reset > > > > "resolves" the issue. > > > > > > > > > > > > > > Thanks, > > > > > > > Emil > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: e10...@li... > > > [e10...@li...] On Behalf Of > > Ronciak, > > > > > > > John > > > > > > > Sent: Wednesday, May 21, 2008 11:24 AM > > > > > > > To: Stanislav Bogatyrev > > > > > > > Cc: e10...@li... > > > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > > > > > > > > > > > ethtool was already reporting the interface to be > > > twisted pair (tp) > > > from > > > > > > > your other email. So the command should not be doing > > > anything. What > > > > made you try this? > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > John > > > > > > > > > > > ----------------------------------------------------------- > > > "Those who would give up essential Liberty, to > purchase > > a little > > > > temporary Safety, deserve neither Liberty nor > Safety.", > > Benjamin > > > > Franklin 1755 > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: Stanislav Bogatyrev [realloc@gma > > il.com] > > > > Sent: Wednesday, May 21, 2008 11:07 AM > > > > > > > To: Ronciak, John > > > > > > > Cc: e10...@li... > > > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > > > > > > > > > > > Hello, > > > > > > > Also, when eth2 is in freeze state, running `ethtool > -s > > eth2 port tp` > > > > solves the problem. > > > > > > > > > > > > > > On Wed, May 21, 2008 at 7:13 PM, Ronciak, John > > > > > > john.r > > > onciak@intel > .com> > > > wrote: > > > > > > >> Does the driver that comes with SLES10 work? Does > > > eth0 or eth1 work? > > > >> > > > > > > >> What is the output from: > > > > > > >> ethtool > > > > > > >> ethtool -i > > > > > > >> netstate -i > > > > > > >> ifconfig ethx > > > > > > >> > > > > > > >> > > > > > > >> Cheers, > > > > > > >> John > > > > > > >> > > > > ----------------------------------------------------------- > > >> "Those who would give up essential Liberty, to > > > purchase a little > > > >> temporary Safety, deserve neither Liberty nor > > > Safety.", Benjamin > > > >> Franklin 1755 > > > > > > >> > > > > > > >> -----Original Message----- > > > > > > >> From: e10...@li... > > >> [e10...@li...] On Behalf Of > > >> Stanislav Bogatyrev > > > > > > >> Sent: Wednesday, May 21, 2008 6:52 AM > > > > > > >> To: e10...@li... > > >> Subject: [E1000-devel] e1000 freezing during boot > > > > > > >> > > > > > > >> Hello, All! > > > > > > >> > > > > > > >> I run SLES-10 Linux with kernel 2.6.16. When system > > > boots up. It > > > >> configures network interfaces, but stays > unreachable. > > When pingning > > > >> from a remote - we just don't get ARP reply. When > > > pinging from > > > >> computer with the problem we see arp requests and > arp > > replies > > > (tcpdump > > > > > > >> on the target), but those replies do not come to OS > > > level. > > > Compilation > > > > > > >> with MSI disabled or with NAPI disabled doesn't > solve > > the issue. > > > >> > > > > > > >> Is there any workaround for this issue? > > > > > > >> > > > > > > >> kernel: 2.6.16-SLES10 > > > > > > >> driver: e1000 > > > > > > >> version: 7.6.15.5 > > > > > > >> firmware-version: N/A > > > > > > >> bus-info: 0000:02:06.0 > > > > > > >> 02:06.0 Ethernet controller: Intel Corporation > 82546GB > > Gigabit > > > >> Ethernet Controller (rev 03) > > > > > > >> Subsystem: Intel Corporation PRO/1000 MT Dual > > > Port Network > > > >> Connection > > > > > > >> Control: I/O+ Mem+ BusMaster+ SpecCycle- > > > MemWINV- VGASnoop- > > > >> ParErr- Stepping- SERR- FastB2B- > > > > > > >> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- > > > DEVSEL=medium > > > >>>TAbort- SERR- > > > >> Latency: 32 (63750ns min), Cache Line Size 08 > > > > > > >> Interrupt: pin A routed to IRQ 177 > > > > > > >> Region 0: Memory at d0000000 (64-bit, > > > non-prefetchable) > > > >> [size=128K] > > > > > > >> Region 4: I/O ports at c000 [size=64] > > > > > > >> Capabilities: [dc] Power Management version 2 > > > > > > >> Flags: PMEClk- DSI+ D1- D2- > > > AuxCurrent=0mA > > > >> PME(D0+,D1-,D2-,D3hot+,D3cold+) > > > > > > >> Status: D0 PME-Enable- DSel=0 > DScale=1 > > PME- > > > >> Capabilities: [e4] PCI-X non-bridge device > > > > > > >> Command: DPERE- ERO > > > > > > >> [17:39:55] byte_0xEB_0xFE: + RBC=512 OST=1 > > > > > > >> Status: Dev=02:06.0 64bit+ 133MHz+ > SCD- > > USC- DC=simple > > > >> DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- > > > > > > >> Capabilities: [f0] Message Signalled > > > Interrupts: 64bit+ > > > >> Queue=0/0 Enable- > > > > > > >> Address: 0000000000000000 Data: 0000 > > > > > > >> > > > > > > >> > > > > > > >> Settings for eth2: > > > > > > >> Supported ports: [ TP ] > > > > > > >> Supported link modes: 10baseT/Half > > > 10baseT/Full > > > >> 100baseT/Half > > > 100baseT/Full > > > >> 1000baseT/Full > > > > > > >> Supports auto-negotiation: Yes > > > > > > >> Advertised link modes: 10baseT/Half > > > 10baseT/Full > > > >> 100baseT/Half > > > 100baseT/Full > > > >> 1000baseT/Full > > > > > > >> Advertised auto-negotiation: Yes > > > > > > >> Speed: 1000Mb/s > > > > > > >> Duplex: Full > > > > > > >> Port: Twisted Pair > > > > > > >> PHYAD: 1 > > > > > > >> Transceiver: internal > > > > > > >> Auto-negotiation: on > > > > > > >> Supports Wake-on: umbg > > > > > > >> Wake-on: g > > > > > > >> Current message level: 0x00000007 (7) > > > > > > >> Link detected: yes > > > > > > >> > > > > > > >> Offset Values > > > > > > >> ------ ------ > > > > > > >> 0x0000 00 e0 81 5a f7 86 30 08 ff ff ff ff > ff > > ff ff ff > > > >> 0x0010 14 c4 03 21 0b 46 79 11 86 80 79 10 > 86 > > 80 e8 b4 > > > >> 0x0020 0c 00 7a 10 00 00 05 03 cc 1e ff ff > ff > > ff ff ff > > > >> 0x0030 ff ff ff ff ff ff ff ff ff ff ff ff > ff > > ff ff ff > > > >> 0x0040 0c c3 63 ff 04 50 05 03 c8 0c ff ff > ff > > > > > >> [17:39:57] byte_0xEB_0xFE: ff ff ff > > > > > > >> 0x0050 ff ff ff ff ff ff ff ff ff ff ff ff > ff > > ff 02 06 > > > >> 0x0060 00 01 00 40 11 12 ff ff ff ff ff ff > ff > > ff ff ff > > > >> 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff > ff > > ff 85 40 > > > >> > > > > > > >> CPU0 CPU1 > > > > > > >> 0: 614377 0 IO-APIC-edge timer > > > > > > >> 1: 388 0 IO-APIC-edge i8042 > > > > > > >> 4: 1272 0 IO-APIC-edge serial > > > > > > >> 9: 0 0 IO-APIC-level acpi > > > > > > >> 169: 17752 0 IO-APIC-level eth1 > > > > > > >> 177: 137808 0 IO-APIC-level libata, > > > eth2 > > > >> 201: 25860 0 IO-APIC-level eth0 > > > > > > >> NMI: 0 0 > > > > > > >> LOC: 614176 614269 > > > > > > >> ERR: 0 > > > > > > >> MIS: 0 > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> -- > > > > > > >> Best regards, > > > > > > >> Stanislav Bogatyrev aka realloc() > > > > > > >> > > > > > > >> > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > >> - > > > > > > >> This SF.net email is sponsored by: Microsoft > > > > > > >> Defy all challenges. Microsoft(R) Visual Studio > 2008. > > > > > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > >> _______________________________________________ > > > > > > >> E1000-devel mailing list > > > > > > >> E10...@li... > > >> https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Best regards, > > > > > > > Stanislav Bogatyrev aka realloc() > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > - > > > > > > > This SF.net email is sponsored by: Microsoft > > > > > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > _______________________________________________ > > > > > > > E1000-devel mailing list > > > > > > > E10...@li... > > > https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Best regards, > > > > > > Stanislav Bogatyrev aka realloc() > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > - > > > > > > This SF.net email is sponsored by: Microsoft > > > > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > > > > > E1000-devel mailing list > > > > > > E10...@li... > > https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > > > > > > > > > > > ---- Msg sent via email.ru > > > > ---- Msg sent via email.ru |
|
From: Richard S. <ri...@sa...> - 2008-05-22 17:27:45
|
Allan, Bruce W wrote: > Just because it is enabled in the kernel config file does not mean it is > in reality enabled in the kernel. I have seen kernels from RedHat in > which MSI is explicitly disabled no matter what CONFIG_PCI_MSI is set > to. One method that might enable it is to add pci=msi to the kernel > boot command line. Many thanks Bruce, that did it. I even looked for a parameter like this, but pci=msi does not appear in Documentation/kernel-parameters.txt. Regards, Richard |
|
From: Allan, B. W <bru...@in...> - 2008-05-22 16:21:38
|
Just because it is enabled in the kernel config file does not mean it is in reality enabled in the kernel. I have seen kernels from RedHat in which MSI is explicitly disabled no matter what CONFIG_PCI_MSI is set to. One method that might enable it is to add pci=msi to the kernel boot command line. It could also be that a problem with MSI had been discovered with the type of system/chipset/etc. you are using and as a result MSI is disabled as a quirk (see ./drivers/pci/quirks.c), but that should be indicated by a warning message during bootup. >-----Original Message----- >From: e10...@li... [mailto:e1000-devel- >bo...@li...] On Behalf Of Richard Scobie >Sent: Wednesday, May 21, 2008 8:59 PM >To: Tantilov, Emil S >Cc: e10...@li... >Subject: Re: [E1000-devel] e1000e MSI > >Tantilov, Emil S wrote: >> Check your kernel configuration - CONFIG_PCI_MSI should be enabled. >> >> The driver defaults to MSI. >> >> Thanks, >> Emil > >Hi Emil, > >Yes, this is enabled in this kernel, so that's a mystery. > >cat /boot/config-2.6.25.3-18.fc9.x86_64 |grep CONFIG_PCI_MSI >CONFIG_PCI_MSI=y > > >Regards, > >Richard > >----------------------------------------------------------------------- -- >This SF.net email is sponsored by: Microsoft >Defy all challenges. Microsoft(R) Visual Studio 2008. >http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >_______________________________________________ >E1000-devel mailing list >E10...@li... >https://lists.sourceforge.net/lists/listinfo/e1000-devel |
|
From: Jeff G. <jg...@po...> - 2008-05-22 10:22:22
|
Becky Bruce wrote: > The use of unsigned long causes the driver to fail on 32-bit systems > which support 64-bit resources. > > Signed-off-by: Becky Bruce <bec...@fr...> > --- > > Resend, with proper CC. > > drivers/net/e1000e/netdev.c | 4 ++-- > 1 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/net/e1000e/netdev.c b/drivers/net/e1000e/netdev.c > index 8991ab8..dae3269 100644 > --- a/drivers/net/e1000e/netdev.c > +++ b/drivers/net/e1000e/netdev.c > @@ -3897,8 +3897,8 @@ static int __devinit e1000_probe(struct pci_dev *pdev, > struct e1000_adapter *adapter; > struct e1000_hw *hw; > const struct e1000_info *ei = e1000_info_tbl[ent->driver_data]; > - unsigned long mmio_start, mmio_len; > - unsigned long flash_start, flash_len; > + resource_size_t mmio_start, mmio_len; > + resource_size_t flash_start, flash_len; > applied |
|
From: <z1...@au...> - 2008-05-22 08:12:05
|
unplugging the cables from two other interfaces doesn't have any effect. the same situation - packets not being received after several reboots. What do you mean by "ipmi being not configured"? Just disable BMC Arp control? On Thu 22/05/08 12:46 AM , "Ronciak, John" sent: > Please answer the questions that I asked. They will add information to > > this problem which nobody else outside you and your team are seeing. > > > > > > Cheers, > > John > > ----------------------------------------------------------- > > "Those who would give up essential Liberty, to purchase a little > > temporary Safety, deserve neither Liberty nor Safety.", Benjamin > > Franklin 1755 > > > > -----Original Message----- > > From: z1...@au... [z1...@au...] > Sent: Wednesday, May 21, 2008 1:43 PM > > To: Ronciak, John > > Cc: e10...@li... > Subject: Re: Re: [E1000-devel] e1000 freezing during boot > > > > Hello, > > This may sound doubtful, but this is not happening on one box, or only > > in one network environment, and is reproducible > > though not really reliable, but 5-6 reboots bring NIC into this state > > when we first get rx_no_buffer_count in -S then after some > > point it stops and starts counting rx_missed packets. This has been seen > > on 8 boxes so far, probably more, but only 8 reported. And the problem > > started to show itself after update from 7.0.33 to 7.6.15.5. Maybe we > > are missing something in configuration? Maybe some driver parameters are > > incorrect? setting debug to 16, or to 21 (as suggested in one of the > > mails in another thread) doesn't produce any useful info to understand > > what is wrong. Though dmesg show that watchdog for eth2 is running and a > > message that TSO is on follows.. > > > > Thanks for the support. > > > > On Thu 22/05/08 12:25 AM , "Ronciak, John" sent: > > > Doubtful. This is not happening to anyone else so it's > something to > do > > > > > > with your configuration or environment. > > > > > > > > > > > > If you don't have the other 2 interface running at all, > does it work? > > > > > How about if you don't have IPMI configured on the > first 2 interfaces? > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > John > > > > > > > ----------------------------------------------------------- > > > > > "Those who would give up essential Liberty, to purchase > a little > > > > > temporary Safety, deserve neither Liberty nor Safety.", > Benjamin > > > > > Franklin 1755 > > > > > > > > > > > > -----Original Message----- > > > > > > From: Stanislav Bogatyrev [realloc@gma > > il.com] > > > Sent: Wednesday, May 21, 2008 1:16 PM > > > > > > To: Tantilov, Emil S > > > > > > Cc: Ronciak, John; e10...@li... > > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > > > > > > > > > Hello, > > > > > > > > > > > > ethtool -r helps, but not always... ifconfig down/up > never helps. What > > > > > can cause this problem? It seems that driver > incorrectly detects NIC > > > > > state and doen't start receiver properly? > > > > > > > > > > > > On Wed, May 21, 2008 at 10:29 PM, Tantilov, Emil S > > > > > > emi > > > l.s.ta > nt...@in...> wrote: > > > This command will reset the interface. I bet the same > > > effect can be > > > > achieved with ethtool -r eth0 > > > > > > > > > > > > > > Have you tried ifconfig eth0 down/up? Looks like an > > > interface reset > > > > "resolves" the issue. > > > > > > > > > > > > > > Thanks, > > > > > > > Emil > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: e10...@li... > > > [e10...@li...] On Behalf Of > > Ronciak, > > > > > > > John > > > > > > > Sent: Wednesday, May 21, 2008 11:24 AM > > > > > > > To: Stanislav Bogatyrev > > > > > > > Cc: e10...@li... > > > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > > > > > > > > > > > ethtool was already reporting the interface to be > > > twisted pair (tp) > > > from > > > > > > > your other email. So the command should not be doing > > > anything. What > > > > made you try this? > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > John > > > > > > > > > > > ----------------------------------------------------------- > > > "Those who would give up essential Liberty, to > purchase > > a little > > > > temporary Safety, deserve neither Liberty nor > Safety.", > > Benjamin > > > > Franklin 1755 > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: Stanislav Bogatyrev [realloc@gma > > il.com] > > > > Sent: Wednesday, May 21, 2008 11:07 AM > > > > > > > To: Ronciak, John > > > > > > > Cc: e10...@li... > > > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > > > > > > > > > > > Hello, > > > > > > > Also, when eth2 is in freeze state, running `ethtool > -s > > eth2 port tp` > > > > solves the problem. > > > > > > > > > > > > > > On Wed, May 21, 2008 at 7:13 PM, Ronciak, John > > > > > > john.r > > > onciak@intel > .com> > > > wrote: > > > > > > >> Does the driver that comes with SLES10 work? Does > > > eth0 or eth1 work? > > > >> > > > > > > >> What is the output from: > > > > > > >> ethtool > > > > > > >> ethtool -i > > > > > > >> netstate -i > > > > > > >> ifconfig ethx > > > > > > >> > > > > > > >> > > > > > > >> Cheers, > > > > > > >> John > > > > > > >> > > > > ----------------------------------------------------------- > > >> "Those who would give up essential Liberty, to > > > purchase a little > > > >> temporary Safety, deserve neither Liberty nor > > > Safety.", Benjamin > > > >> Franklin 1755 > > > > > > >> > > > > > > >> -----Original Message----- > > > > > > >> From: e10...@li... > > >> [e10...@li...] On Behalf Of > > >> Stanislav Bogatyrev > > > > > > >> Sent: Wednesday, May 21, 2008 6:52 AM > > > > > > >> To: e10...@li... > > >> Subject: [E1000-devel] e1000 freezing during boot > > > > > > >> > > > > > > >> Hello, All! > > > > > > >> > > > > > > >> I run SLES-10 Linux with kernel 2.6.16. When system > > > boots up. It > > > >> configures network interfaces, but stays > unreachable. > > When pingning > > > >> from a remote - we just don't get ARP reply. When > > > pinging from > > > >> computer with the problem we see arp requests and > arp > > replies > > > (tcpdump > > > > > > >> on the target), but those replies do not come to OS > > > level. > > > Compilation > > > > > > >> with MSI disabled or with NAPI disabled doesn't > solve > > the issue. > > > >> > > > > > > >> Is there any workaround for this issue? > > > > > > >> > > > > > > >> kernel: 2.6.16-SLES10 > > > > > > >> driver: e1000 > > > > > > >> version: 7.6.15.5 > > > > > > >> firmware-version: N/A > > > > > > >> bus-info: 0000:02:06.0 > > > > > > >> 02:06.0 Ethernet controller: Intel Corporation > 82546GB > > Gigabit > > > >> Ethernet Controller (rev 03) > > > > > > >> Subsystem: Intel Corporation PRO/1000 MT Dual > > > Port Network > > > >> Connection > > > > > > >> Control: I/O+ Mem+ BusMaster+ SpecCycle- > > > MemWINV- VGASnoop- > > > >> ParErr- Stepping- SERR- FastB2B- > > > > > > >> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- > > > DEVSEL=medium > > > >>>TAbort- SERR- > > > >> Latency: 32 (63750ns min), Cache Line Size 08 > > > > > > >> Interrupt: pin A routed to IRQ 177 > > > > > > >> Region 0: Memory at d0000000 (64-bit, > > > non-prefetchable) > > > >> [size=128K] > > > > > > >> Region 4: I/O ports at c000 [size=64] > > > > > > >> Capabilities: [dc] Power Management version 2 > > > > > > >> Flags: PMEClk- DSI+ D1- D2- > > > AuxCurrent=0mA > > > >> PME(D0+,D1-,D2-,D3hot+,D3cold+) > > > > > > >> Status: D0 PME-Enable- DSel=0 > DScale=1 > > PME- > > > >> Capabilities: [e4] PCI-X non-bridge device > > > > > > >> Command: DPERE- ERO > > > > > > >> [17:39:55] byte_0xEB_0xFE: + RBC=512 OST=1 > > > > > > >> Status: Dev=02:06.0 64bit+ 133MHz+ > SCD- > > USC- DC=simple > > > >> DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- > > > > > > >> Capabilities: [f0] Message Signalled > > > Interrupts: 64bit+ > > > >> Queue=0/0 Enable- > > > > > > >> Address: 0000000000000000 Data: 0000 > > > > > > >> > > > > > > >> > > > > > > >> Settings for eth2: > > > > > > >> Supported ports: [ TP ] > > > > > > >> Supported link modes: 10baseT/Half > > > 10baseT/Full > > > >> 100baseT/Half > > > 100baseT/Full > > > >> 1000baseT/Full > > > > > > >> Supports auto-negotiation: Yes > > > > > > >> Advertised link modes: 10baseT/Half > > > 10baseT/Full > > > >> 100baseT/Half > > > 100baseT/Full > > > >> 1000baseT/Full > > > > > > >> Advertised auto-negotiation: Yes > > > > > > >> Speed: 1000Mb/s > > > > > > >> Duplex: Full > > > > > > >> Port: Twisted Pair > > > > > > >> PHYAD: 1 > > > > > > >> Transceiver: internal > > > > > > >> Auto-negotiation: on > > > > > > >> Supports Wake-on: umbg > > > > > > >> Wake-on: g > > > > > > >> Current message level: 0x00000007 (7) > > > > > > >> Link detected: yes > > > > > > >> > > > > > > >> Offset Values > > > > > > >> ------ ------ > > > > > > >> 0x0000 00 e0 81 5a f7 86 30 08 ff ff ff ff > ff > > ff ff ff > > > >> 0x0010 14 c4 03 21 0b 46 79 11 86 80 79 10 > 86 > > 80 e8 b4 > > > >> 0x0020 0c 00 7a 10 00 00 05 03 cc 1e ff ff > ff > > ff ff ff > > > >> 0x0030 ff ff ff ff ff ff ff ff ff ff ff ff > ff > > ff ff ff > > > >> 0x0040 0c c3 63 ff 04 50 05 03 c8 0c ff ff > ff > > > > > >> [17:39:57] byte_0xEB_0xFE: ff ff ff > > > > > > >> 0x0050 ff ff ff ff ff ff ff ff ff ff ff ff > ff > > ff 02 06 > > > >> 0x0060 00 01 00 40 11 12 ff ff ff ff ff ff > ff > > ff ff ff > > > >> 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff > ff > > ff 85 40 > > > >> > > > > > > >> CPU0 CPU1 > > > > > > >> 0: 614377 0 IO-APIC-edge timer > > > > > > >> 1: 388 0 IO-APIC-edge i8042 > > > > > > >> 4: 1272 0 IO-APIC-edge serial > > > > > > >> 9: 0 0 IO-APIC-level acpi > > > > > > >> 169: 17752 0 IO-APIC-level eth1 > > > > > > >> 177: 137808 0 IO-APIC-level libata, > > > eth2 > > > >> 201: 25860 0 IO-APIC-level eth0 > > > > > > >> NMI: 0 0 > > > > > > >> LOC: 614176 614269 > > > > > > >> ERR: 0 > > > > > > >> MIS: 0 > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> -- > > > > > > >> Best regards, > > > > > > >> Stanislav Bogatyrev aka realloc() > > > > > > >> > > > > > > >> > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > >> - > > > > > > >> This SF.net email is sponsored by: Microsoft > > > > > > >> Defy all challenges. Microsoft(R) Visual Studio > 2008. > > > > > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > >> _______________________________________________ > > > > > > >> E1000-devel mailing list > > > > > > >> E10...@li... > > >> https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Best regards, > > > > > > > Stanislav Bogatyrev aka realloc() > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > - > > > > > > > This SF.net email is sponsored by: Microsoft > > > > > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > _______________________________________________ > > > > > > > E1000-devel mailing list > > > > > > > E10...@li... > > > https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Best regards, > > > > > > Stanislav Bogatyrev aka realloc() > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > - > > > > > > This SF.net email is sponsored by: Microsoft > > > > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > > > > > E1000-devel mailing list > > > > > > E10...@li... > > https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > > > > > > > > > > > ---- Msg sent via email.ru > > > > ---- Msg sent via email.ru |
|
From: <z1...@au...> - 2008-05-22 07:14:40
|
Yes it is reproducible (though unfortunately not very reliable) on multiple systems, with three types of hardware in them. First type has two interfaces with ethernet pro 100 cards and one 82540EM based Second type has three interfaces all 82546GB based Third type with three 82571EB interfaces 1. yes 2. yes 3. yes (it is always after a reboot, card never enters this state during runtime - as far as we have seen) On Thu 22/05/08 2:01 AM , "Tantilov, Emil S" sent: > z1...@au... > wrote: > > Hello, > > > This may sound doubtful, but this is not happening on > one box, or > > only in one network environment, and is reproducible > > > though not really reliable, but 5-6 reboots bring NIC > into this state > > > OK - so from your description it seems that the issue is reproducible on > > multiple (different?) systems - is this correct? > > > > If we can get some more details about the failure it will at least point > > to whether this is system or NIC specific. Please reply with yes or no: > > > > 1. Are you seeing the issue on multiple systems (preferably not of the > > same type).? > > > > 2. Are you seeing this with different NICs or just the one you reported > > in the initial email? > > > > 3. Can you provide simple steps to reproduce? You mentioned reboots - is > > it fair to say that you see the issue after several reboots? > > > > > when we first get rx_no_buffer_count in -S then after > some > > point it stops and starts counting rx_missed packets. > This has been > > seen on 8 boxes so far, probably more, but only 8 > reported. And the > > problem started to show itself after update from 7.0.33 > to 7.6.15.5. > > > 7.0.33 to 7.6.15.5 is a big leap, if you can maybe narrow the gap a bit > > more by testing versions in betweeen that would certainly help. > > > > Thanks, > > Emil > > > > ---- Msg sent via email.ru |
|
From: Richard S. <ri...@sa...> - 2008-05-22 04:51:19
|
Tantilov, Emil S wrote: > > Also check dmesg after loading the driver - that should give some > messages about not being able to obtain MSI interrupts. These types of > issues are usually kernel/config related. On loading the module, I get: ACPI: PCI interrupt for device 0000:0f:00.1 disabled ACPI: PCI interrupt for device 0000:0f:00.0 disabled ACPI: PCI interrupt for device 0000:04:00.1 disabled ACPI: PCI interrupt for device 0000:04:00.0 disabled ACPI: PCI interrupt for device 0000:03:00.1 disabled ACPI: PCI interrupt for device 0000:03:00.0 disabled e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0 e1000e: Copyright (c) 1999-2007 Intel Corporation. ACPI: PCI Interrupt 0000:03:00.0[B] -> GSI 17 (level, low) -> IRQ 17 PCI: Setting latency timer of device 0000:03:00.0 to 64 eth0: (PCI Express:2.5GB/s:Width x4) 00:15:17:75:e1:6d eth0: Intel(R) PRO/1000 Network Connection eth0: MAC: 0, PHY: 4, PBA No: d72468-003 ACPI: PCI Interrupt 0000:03:00.1[A] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:03:00.1 to 64 eth1: (PCI Express:2.5GB/s:Width x4) 00:15:17:75:e1:6c eth1: Intel(R) PRO/1000 Network Connection eth1: MAC: 0, PHY: 4, PBA No: d72468-003 ACPI: PCI Interrupt 0000:04:00.0[B] -> GSI 18 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:04:00.0 to 64 eth2: (PCI Express:2.5GB/s:Width x4) 00:15:17:75:e1:6f eth2: Intel(R) PRO/1000 Network Connection eth2: MAC: 0, PHY: 4, PBA No: d72468-003 ACPI: PCI Interrupt 0000:04:00.1[A] -> GSI 17 (level, low) -> IRQ 17 PCI: Setting latency timer of device 0000:04:00.1 to 64 eth3: (PCI Express:2.5GB/s:Width x4) 00:15:17:75:e1:6e eth3: Intel(R) PRO/1000 Network Connection eth3: MAC: 0, PHY: 4, PBA No: d72468-003 ACPI: PCI Interrupt 0000:0f:00.0[A] -> GSI 18 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:0f:00.0 to 64 eth4: (PCI Express:2.5GB/s:Width x4) 00:e0:81:b0:80:d4 eth4: Intel(R) PRO/1000 Network Connection eth4: MAC: 3, PHY: 5, PBA No: ffffff-0ff ACPI: PCI Interrupt 0000:0f:00.1[B] -> GSI 19 (level, low) -> IRQ 19 So I guess the next thing would be to try the latest sourceforge driver. Regards, Richard |
|
From: Richard S. <ri...@sa...> - 2008-05-22 04:41:09
|
Tantilov, Emil S wrote: > cat /proc/cmdline? > > are you using the e1000e with the kernel or from e1000.sf.net? > > Also check dmesg after loading the driver - that should give some > messages about not being able to obtain MSI interrupts. These types of > issues are usually kernel/config related. > > Thanks, > Emil # cat /proc/cmdline ro root=/dev/md4 # dmesg |grep MSI assign_interrupt_mode Found MSI capability assign_interrupt_mode Found MSI capability assign_interrupt_mode Found MSI capability assign_interrupt_mode Found MSI capability assign_interrupt_mode Found MSI capability assign_interrupt_mode Found MSI capability assign_interrupt_mode Found MSI capability assign_interrupt_mode Found MSI capability I am using the Fedora 9 e1000e. I'm sure you are correct - the exact same hardware setup worked fine with MSI on Fedora 8. Regards, Richard |
|
From: Tantilov, E. S <emi...@in...> - 2008-05-22 04:29:52
|
cat /proc/cmdline? are you using the e1000e with the kernel or from e1000.sf.net? Also check dmesg after loading the driver - that should give some messages about not being able to obtain MSI interrupts. These types of issues are usually kernel/config related. Thanks, Emil -----Original Message----- From: Richard Scobie [mailto:ri...@sa...] Sent: Wednesday, May 21, 2008 8:59 PM To: Tantilov, Emil S Cc: e10...@li... Subject: Re: [E1000-devel] e1000e MSI Tantilov, Emil S wrote: > Check your kernel configuration - CONFIG_PCI_MSI should be enabled. > > The driver defaults to MSI. > > Thanks, > Emil Hi Emil, Yes, this is enabled in this kernel, so that's a mystery. cat /boot/config-2.6.25.3-18.fc9.x86_64 |grep CONFIG_PCI_MSI CONFIG_PCI_MSI=y Regards, Richard |
|
From: Richard S. <ri...@sa...> - 2008-05-22 03:51:18
|
Tantilov, Emil S wrote: > Check your kernel configuration - CONFIG_PCI_MSI should be enabled. > > The driver defaults to MSI. > > Thanks, > Emil Hi Emil, Yes, this is enabled in this kernel, so that's a mystery. cat /boot/config-2.6.25.3-18.fc9.x86_64 |grep CONFIG_PCI_MSI CONFIG_PCI_MSI=y Regards, Richard |
|
From: Tantilov, E. S <emi...@in...> - 2008-05-22 03:23:38
|
Check your kernel configuration - CONFIG_PCI_MSI should be enabled. The driver defaults to MSI. Thanks, Emil -----Original Message----- From: e10...@li... [mailto:e10...@li...] On Behalf Of Richard Scobie Sent: Wednesday, May 21, 2008 7:46 PM To: e10...@li... Subject: [E1000-devel] e1000e MSI I've just updated from FC8 - 2.6.24.7-92.fc8 to FC9 - 2.6.25.3-18.fc9.x86_64. When I was rumnning FC8, a quad port PRO/1000 PT card was using MSI interrupts. With FC9 installed, the card is now using IO-APIC-fasteoi IRQs, which is not the best as one port is sharing with a SAS controller. Modinfo on e1000e shows no parameter I can use to enable MSI - am I out of luck or is there a good reason MSI is disabled? Regards, Richard ------------------------------------------------------------------------ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ E1000-devel mailing list E10...@li... https://lists.sourceforge.net/lists/listinfo/e1000-devel |
|
From: Richard S. <ri...@sa...> - 2008-05-22 02:37:50
|
I've just updated from FC8 - 2.6.24.7-92.fc8 to FC9 - 2.6.25.3-18.fc9.x86_64. When I was rumnning FC8, a quad port PRO/1000 PT card was using MSI interrupts. With FC9 installed, the card is now using IO-APIC-fasteoi IRQs, which is not the best as one port is sharing with a SAS controller. Modinfo on e1000e shows no parameter I can use to enable MSI - am I out of luck or is there a good reason MSI is disabled? Regards, Richard |
|
From: Tantilov, E. S <emi...@in...> - 2008-05-21 22:02:19
|
z1...@au... wrote: > Hello, > This may sound doubtful, but this is not happening on one box, or > only in one network environment, and is reproducible > though not really reliable, but 5-6 reboots bring NIC into this state OK - so from your description it seems that the issue is reproducible on multiple (different?) systems - is this correct? If we can get some more details about the failure it will at least point to whether this is system or NIC specific. Please reply with yes or no: 1. Are you seeing the issue on multiple systems (preferably not of the same type).? 2. Are you seeing this with different NICs or just the one you reported in the initial email? 3. Can you provide simple steps to reproduce? You mentioned reboots - is it fair to say that you see the issue after several reboots? > when we first get rx_no_buffer_count in -S then after some > point it stops and starts counting rx_missed packets. This has been > seen on 8 boxes so far, probably more, but only 8 reported. And the > problem started to show itself after update from 7.0.33 to 7.6.15.5. 7.0.33 to 7.6.15.5 is a big leap, if you can maybe narrow the gap a bit more by testing versions in betweeen that would certainly help. Thanks, Emil |
|
From: Ronciak, J. <joh...@in...> - 2008-05-21 20:46:43
|
Please answer the questions that I asked. They will add information to this problem which nobody else outside you and your team are seeing. Cheers, John ----------------------------------------------------------- "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety.", Benjamin Franklin 1755 -----Original Message----- From: z1...@au... [mailto:z1...@au...] Sent: Wednesday, May 21, 2008 1:43 PM To: Ronciak, John Cc: e10...@li... Subject: Re: Re: [E1000-devel] e1000 freezing during boot Hello, This may sound doubtful, but this is not happening on one box, or only in one network environment, and is reproducible though not really reliable, but 5-6 reboots bring NIC into this state when we first get rx_no_buffer_count in -S then after some point it stops and starts counting rx_missed packets. This has been seen on 8 boxes so far, probably more, but only 8 reported. And the problem started to show itself after update from 7.0.33 to 7.6.15.5. Maybe we are missing something in configuration? Maybe some driver parameters are incorrect? setting debug to 16, or to 21 (as suggested in one of the mails in another thread) doesn't produce any useful info to understand what is wrong. Though dmesg show that watchdog for eth2 is running and a message that TSO is on follows.. Thanks for the support. On Thu 22/05/08 12:25 AM , "Ronciak, John" sent: > Doubtful. This is not happening to anyone else so it's something to do > > with your configuration or environment. > > > > If you don't have the other 2 interface running at all, does it work? > > How about if you don't have IPMI configured on the first 2 interfaces? > > > > > > Cheers, > > John > > ----------------------------------------------------------- > > "Those who would give up essential Liberty, to purchase a little > > temporary Safety, deserve neither Liberty nor Safety.", Benjamin > > Franklin 1755 > > > > -----Original Message----- > > From: Stanislav Bogatyrev [realloc@gma > il.com] > Sent: Wednesday, May 21, 2008 1:16 PM > > To: Tantilov, Emil S > > Cc: Ronciak, John; e10...@li... > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > Hello, > > > > ethtool -r helps, but not always... ifconfig down/up never helps. What > > can cause this problem? It seems that driver incorrectly detects NIC > > state and doen't start receiver properly? > > > > On Wed, May 21, 2008 at 10:29 PM, Tantilov, Emil S > > emi > l.s...@in...> wrote: > > This command will reset the interface. I bet the same > effect can be > > achieved with ethtool -r eth0 > > > > > > Have you tried ifconfig eth0 down/up? Looks like an > interface reset > > "resolves" the issue. > > > > > > Thanks, > > > Emil > > > > > > -----Original Message----- > > > From: e10...@li... > > [e10...@li...] On Behalf Of > Ronciak, > > > John > > > Sent: Wednesday, May 21, 2008 11:24 AM > > > To: Stanislav Bogatyrev > > > Cc: e10...@li... > > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > > > ethtool was already reporting the interface to be > twisted pair (tp) > from > > > your other email. So the command should not be doing > anything. What > > made you try this? > > > > > > > > > Cheers, > > > John > > > > ----------------------------------------------------------- > > "Those who would give up essential Liberty, to purchase > a little > > temporary Safety, deserve neither Liberty nor Safety.", > Benjamin > > Franklin 1755 > > > > > > -----Original Message----- > > > From: Stanislav Bogatyrev [realloc@gma > il.com] > > Sent: Wednesday, May 21, 2008 11:07 AM > > > To: Ronciak, John > > > Cc: e10...@li... > > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > > > Hello, > > > Also, when eth2 is in freeze state, running `ethtool -s > eth2 port tp` > > solves the problem. > > > > > > On Wed, May 21, 2008 at 7:13 PM, Ronciak, John > > john.r > on...@in...> > > wrote: > > >> Does the driver that comes with SLES10 work? Does > eth0 or eth1 work? > >> > > >> What is the output from: > > >> ethtool > > >> ethtool -i > > >> netstate -i > > >> ifconfig ethx > > >> > > >> > > >> Cheers, > > >> John > > >> > ----------------------------------------------------------- > >> "Those who would give up essential Liberty, to > purchase a little > >> temporary Safety, deserve neither Liberty nor > Safety.", Benjamin > >> Franklin 1755 > > >> > > >> -----Original Message----- > > >> From: e10...@li... > >> [e10...@li...] On Behalf Of > >> Stanislav Bogatyrev > > >> Sent: Wednesday, May 21, 2008 6:52 AM > > >> To: e10...@li... > >> Subject: [E1000-devel] e1000 freezing during boot > > >> > > >> Hello, All! > > >> > > >> I run SLES-10 Linux with kernel 2.6.16. When system > boots up. It > >> configures network interfaces, but stays unreachable. > When pingning > >> from a remote - we just don't get ARP reply. When > pinging from > >> computer with the problem we see arp requests and arp > replies > (tcpdump > > >> on the target), but those replies do not come to OS > level. > Compilation > > >> with MSI disabled or with NAPI disabled doesn't solve > the issue. > >> > > >> Is there any workaround for this issue? > > >> > > >> kernel: 2.6.16-SLES10 > > >> driver: e1000 > > >> version: 7.6.15.5 > > >> firmware-version: N/A > > >> bus-info: 0000:02:06.0 > > >> 02:06.0 Ethernet controller: Intel Corporation 82546GB > Gigabit > >> Ethernet Controller (rev 03) > > >> Subsystem: Intel Corporation PRO/1000 MT Dual > Port Network > >> Connection > > >> Control: I/O+ Mem+ BusMaster+ SpecCycle- > MemWINV- VGASnoop- > >> ParErr- Stepping- SERR- FastB2B- > > >> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- > DEVSEL=medium > >>>TAbort- SERR- > >> Latency: 32 (63750ns min), Cache Line Size 08 > > >> Interrupt: pin A routed to IRQ 177 > > >> Region 0: Memory at d0000000 (64-bit, > non-prefetchable) > >> [size=128K] > > >> Region 4: I/O ports at c000 [size=64] > > >> Capabilities: [dc] Power Management version 2 > > >> Flags: PMEClk- DSI+ D1- D2- > AuxCurrent=0mA > >> PME(D0+,D1-,D2-,D3hot+,D3cold+) > > >> Status: D0 PME-Enable- DSel=0 DScale=1 > PME- > >> Capabilities: [e4] PCI-X non-bridge device > > >> Command: DPERE- ERO > > >> [17:39:55] byte_0xEB_0xFE: + RBC=512 OST=1 > > >> Status: Dev=02:06.0 64bit+ 133MHz+ SCD- > USC- DC=simple > >> DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- > > >> Capabilities: [f0] Message Signalled > Interrupts: 64bit+ > >> Queue=0/0 Enable- > > >> Address: 0000000000000000 Data: 0000 > > >> > > >> > > >> Settings for eth2: > > >> Supported ports: [ TP ] > > >> Supported link modes: 10baseT/Half > 10baseT/Full > >> 100baseT/Half > 100baseT/Full > >> 1000baseT/Full > > >> Supports auto-negotiation: Yes > > >> Advertised link modes: 10baseT/Half > 10baseT/Full > >> 100baseT/Half > 100baseT/Full > >> 1000baseT/Full > > >> Advertised auto-negotiation: Yes > > >> Speed: 1000Mb/s > > >> Duplex: Full > > >> Port: Twisted Pair > > >> PHYAD: 1 > > >> Transceiver: internal > > >> Auto-negotiation: on > > >> Supports Wake-on: umbg > > >> Wake-on: g > > >> Current message level: 0x00000007 (7) > > >> Link detected: yes > > >> > > >> Offset Values > > >> ------ ------ > > >> 0x0000 00 e0 81 5a f7 86 30 08 ff ff ff ff ff > ff ff ff > >> 0x0010 14 c4 03 21 0b 46 79 11 86 80 79 10 86 > 80 e8 b4 > >> 0x0020 0c 00 7a 10 00 00 05 03 cc 1e ff ff ff > ff ff ff > >> 0x0030 ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff > >> 0x0040 0c c3 63 ff 04 50 05 03 c8 0c ff ff ff > > >> [17:39:57] byte_0xEB_0xFE: ff ff ff > > >> 0x0050 ff ff ff ff ff ff ff ff ff ff ff ff ff > ff 02 06 > >> 0x0060 00 01 00 40 11 12 ff ff ff ff ff ff ff > ff ff ff > >> 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff > ff 85 40 > >> > > >> CPU0 CPU1 > > >> 0: 614377 0 IO-APIC-edge timer > > >> 1: 388 0 IO-APIC-edge i8042 > > >> 4: 1272 0 IO-APIC-edge serial > > >> 9: 0 0 IO-APIC-level acpi > > >> 169: 17752 0 IO-APIC-level eth1 > > >> 177: 137808 0 IO-APIC-level libata, > eth2 > >> 201: 25860 0 IO-APIC-level eth0 > > >> NMI: 0 0 > > >> LOC: 614176 614269 > > >> ERR: 0 > > >> MIS: 0 > > >> > > >> > > >> > > >> -- > > >> Best regards, > > >> Stanislav Bogatyrev aka realloc() > > >> > > >> > > > > > ------------------------------------------------------------------------ > > >> - > > >> This SF.net email is sponsored by: Microsoft > > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > > >> E1000-devel mailing list > > >> E10...@li... > >> https://lists.sourceforge.net/lists/listinfo/e1000-devel > > >> > > > > > > > > > > > > -- > > > Best regards, > > > Stanislav Bogatyrev aka realloc() > > > > > > > > ------------------------------------------------------------------------ > > > - > > > This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > > E1000-devel mailing list > > > E10...@li... > > https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > > > > > > > > -- > > Best regards, > > Stanislav Bogatyrev aka realloc() > > > > ------------------------------------------------------------------------ - > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > > E1000-devel mailing list > > E10...@li... > https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > ---- Msg sent via email.ru |
|
From: <z1...@au...> - 2008-05-21 20:43:26
|
Hello, This may sound doubtful, but this is not happening on one box, or only in one network environment, and is reproducible though not really reliable, but 5-6 reboots bring NIC into this state when we first get rx_no_buffer_count in -S then after some point it stops and starts counting rx_missed packets. This has been seen on 8 boxes so far, probably more, but only 8 reported. And the problem started to show itself after update from 7.0.33 to 7.6.15.5. Maybe we are missing something in configuration? Maybe some driver parameters are incorrect? setting debug to 16, or to 21 (as suggested in one of the mails in another thread) doesn't produce any useful info to understand what is wrong. Though dmesg show that watchdog for eth2 is running and a message that TSO is on follows.. Thanks for the support. On Thu 22/05/08 12:25 AM , "Ronciak, John" sent: > Doubtful. This is not happening to anyone else so it's something to do > > with your configuration or environment. > > > > If you don't have the other 2 interface running at all, does it work? > > How about if you don't have IPMI configured on the first 2 interfaces? > > > > > > Cheers, > > John > > ----------------------------------------------------------- > > "Those who would give up essential Liberty, to purchase a little > > temporary Safety, deserve neither Liberty nor Safety.", Benjamin > > Franklin 1755 > > > > -----Original Message----- > > From: Stanislav Bogatyrev [realloc@gma > il.com] > Sent: Wednesday, May 21, 2008 1:16 PM > > To: Tantilov, Emil S > > Cc: Ronciak, John; e10...@li... > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > Hello, > > > > ethtool -r helps, but not always... ifconfig down/up never helps. What > > can cause this problem? It seems that driver incorrectly detects NIC > > state and doen't start receiver properly? > > > > On Wed, May 21, 2008 at 10:29 PM, Tantilov, Emil S > > emi > l.s...@in...> wrote: > > This command will reset the interface. I bet the same > effect can be > > achieved with ethtool -r eth0 > > > > > > Have you tried ifconfig eth0 down/up? Looks like an > interface reset > > "resolves" the issue. > > > > > > Thanks, > > > Emil > > > > > > -----Original Message----- > > > From: e10...@li... > > [e10...@li...] On Behalf Of > Ronciak, > > > John > > > Sent: Wednesday, May 21, 2008 11:24 AM > > > To: Stanislav Bogatyrev > > > Cc: e10...@li... > > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > > > ethtool was already reporting the interface to be > twisted pair (tp) > from > > > your other email. So the command should not be doing > anything. What > > made you try this? > > > > > > > > > Cheers, > > > John > > > > ----------------------------------------------------------- > > "Those who would give up essential Liberty, to purchase > a little > > temporary Safety, deserve neither Liberty nor Safety.", > Benjamin > > Franklin 1755 > > > > > > -----Original Message----- > > > From: Stanislav Bogatyrev [realloc@gma > il.com] > > Sent: Wednesday, May 21, 2008 11:07 AM > > > To: Ronciak, John > > > Cc: e10...@li... > > Subject: Re: [E1000-devel] e1000 freezing during boot > > > > > > Hello, > > > Also, when eth2 is in freeze state, running `ethtool -s > eth2 port tp` > > solves the problem. > > > > > > On Wed, May 21, 2008 at 7:13 PM, Ronciak, John > > john.r > on...@in...> > > wrote: > > >> Does the driver that comes with SLES10 work? Does > eth0 or eth1 work? > >> > > >> What is the output from: > > >> ethtool > > >> ethtool -i > > >> netstate -i > > >> ifconfig ethx > > >> > > >> > > >> Cheers, > > >> John > > >> > ----------------------------------------------------------- > >> "Those who would give up essential Liberty, to > purchase a little > >> temporary Safety, deserve neither Liberty nor > Safety.", Benjamin > >> Franklin 1755 > > >> > > >> -----Original Message----- > > >> From: e10...@li... > >> [e10...@li...] On Behalf Of > >> Stanislav Bogatyrev > > >> Sent: Wednesday, May 21, 2008 6:52 AM > > >> To: e10...@li... > >> Subject: [E1000-devel] e1000 freezing during boot > > >> > > >> Hello, All! > > >> > > >> I run SLES-10 Linux with kernel 2.6.16. When system > boots up. It > >> configures network interfaces, but stays unreachable. > When pingning > >> from a remote - we just don't get ARP reply. When > pinging from > >> computer with the problem we see arp requests and arp > replies > (tcpdump > > >> on the target), but those replies do not come to OS > level. > Compilation > > >> with MSI disabled or with NAPI disabled doesn't solve > the issue. > >> > > >> Is there any workaround for this issue? > > >> > > >> kernel: 2.6.16-SLES10 > > >> driver: e1000 > > >> version: 7.6.15.5 > > >> firmware-version: N/A > > >> bus-info: 0000:02:06.0 > > >> 02:06.0 Ethernet controller: Intel Corporation 82546GB > Gigabit > >> Ethernet Controller (rev 03) > > >> Subsystem: Intel Corporation PRO/1000 MT Dual > Port Network > >> Connection > > >> Control: I/O+ Mem+ BusMaster+ SpecCycle- > MemWINV- VGASnoop- > >> ParErr- Stepping- SERR- FastB2B- > > >> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- > DEVSEL=medium > >>>TAbort- SERR- > >> Latency: 32 (63750ns min), Cache Line Size 08 > > >> Interrupt: pin A routed to IRQ 177 > > >> Region 0: Memory at d0000000 (64-bit, > non-prefetchable) > >> [size=128K] > > >> Region 4: I/O ports at c000 [size=64] > > >> Capabilities: [dc] Power Management version 2 > > >> Flags: PMEClk- DSI+ D1- D2- > AuxCurrent=0mA > >> PME(D0+,D1-,D2-,D3hot+,D3cold+) > > >> Status: D0 PME-Enable- DSel=0 DScale=1 > PME- > >> Capabilities: [e4] PCI-X non-bridge device > > >> Command: DPERE- ERO > > >> [17:39:55] byte_0xEB_0xFE: + RBC=512 OST=1 > > >> Status: Dev=02:06.0 64bit+ 133MHz+ SCD- > USC- DC=simple > >> DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- > > >> Capabilities: [f0] Message Signalled > Interrupts: 64bit+ > >> Queue=0/0 Enable- > > >> Address: 0000000000000000 Data: 0000 > > >> > > >> > > >> Settings for eth2: > > >> Supported ports: [ TP ] > > >> Supported link modes: 10baseT/Half > 10baseT/Full > >> 100baseT/Half > 100baseT/Full > >> 1000baseT/Full > > >> Supports auto-negotiation: Yes > > >> Advertised link modes: 10baseT/Half > 10baseT/Full > >> 100baseT/Half > 100baseT/Full > >> 1000baseT/Full > > >> Advertised auto-negotiation: Yes > > >> Speed: 1000Mb/s > > >> Duplex: Full > > >> Port: Twisted Pair > > >> PHYAD: 1 > > >> Transceiver: internal > > >> Auto-negotiation: on > > >> Supports Wake-on: umbg > > >> Wake-on: g > > >> Current message level: 0x00000007 (7) > > >> Link detected: yes > > >> > > >> Offset Values > > >> ------ ------ > > >> 0x0000 00 e0 81 5a f7 86 30 08 ff ff ff ff ff > ff ff ff > >> 0x0010 14 c4 03 21 0b 46 79 11 86 80 79 10 86 > 80 e8 b4 > >> 0x0020 0c 00 7a 10 00 00 05 03 cc 1e ff ff ff > ff ff ff > >> 0x0030 ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff > >> 0x0040 0c c3 63 ff 04 50 05 03 c8 0c ff ff ff > > >> [17:39:57] byte_0xEB_0xFE: ff ff ff > > >> 0x0050 ff ff ff ff ff ff ff ff ff ff ff ff ff > ff 02 06 > >> 0x0060 00 01 00 40 11 12 ff ff ff ff ff ff ff > ff ff ff > >> 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff > ff 85 40 > >> > > >> CPU0 CPU1 > > >> 0: 614377 0 IO-APIC-edge timer > > >> 1: 388 0 IO-APIC-edge i8042 > > >> 4: 1272 0 IO-APIC-edge serial > > >> 9: 0 0 IO-APIC-level acpi > > >> 169: 17752 0 IO-APIC-level eth1 > > >> 177: 137808 0 IO-APIC-level libata, > eth2 > >> 201: 25860 0 IO-APIC-level eth0 > > >> NMI: 0 0 > > >> LOC: 614176 614269 > > >> ERR: 0 > > >> MIS: 0 > > >> > > >> > > >> > > >> -- > > >> Best regards, > > >> Stanislav Bogatyrev aka realloc() > > >> > > >> > > > > > ------------------------------------------------------------------------ > > >> - > > >> This SF.net email is sponsored by: Microsoft > > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > > >> E1000-devel mailing list > > >> E10...@li... > >> https://lists.sourceforge.net/lists/listinfo/e1000-devel > > >> > > > > > > > > > > > > -- > > > Best regards, > > > Stanislav Bogatyrev aka realloc() > > > > > > > > ------------------------------------------------------------------------ > > > - > > > This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > > E1000-devel mailing list > > > E10...@li... > > https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > > > > > > > > -- > > Best regards, > > Stanislav Bogatyrev aka realloc() > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > > E1000-devel mailing list > > E10...@li... > https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > ---- Msg sent via email.ru |
|
From: Ronciak, J. <joh...@in...> - 2008-05-21 20:25:26
|
Doubtful. This is not happening to anyone else so it's something to do with your configuration or environment. If you don't have the other 2 interface running at all, does it work? How about if you don't have IPMI configured on the first 2 interfaces? Cheers, John ----------------------------------------------------------- "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety.", Benjamin Franklin 1755 -----Original Message----- From: Stanislav Bogatyrev [mailto:re...@gm...] Sent: Wednesday, May 21, 2008 1:16 PM To: Tantilov, Emil S Cc: Ronciak, John; e10...@li... Subject: Re: [E1000-devel] e1000 freezing during boot Hello, ethtool -r helps, but not always... ifconfig down/up never helps. What can cause this problem? It seems that driver incorrectly detects NIC state and doen't start receiver properly? On Wed, May 21, 2008 at 10:29 PM, Tantilov, Emil S <emi...@in...> wrote: > This command will reset the interface. I bet the same effect can be > achieved with ethtool -r eth0 > > Have you tried ifconfig eth0 down/up? Looks like an interface reset > "resolves" the issue. > > Thanks, > Emil > > -----Original Message----- > From: e10...@li... > [mailto:e10...@li...] On Behalf Of Ronciak, > John > Sent: Wednesday, May 21, 2008 11:24 AM > To: Stanislav Bogatyrev > Cc: e10...@li... > Subject: Re: [E1000-devel] e1000 freezing during boot > > ethtool was already reporting the interface to be twisted pair (tp) from > your other email. So the command should not be doing anything. What > made you try this? > > > Cheers, > John > ----------------------------------------------------------- > "Those who would give up essential Liberty, to purchase a little > temporary Safety, deserve neither Liberty nor Safety.", Benjamin > Franklin 1755 > > -----Original Message----- > From: Stanislav Bogatyrev [mailto:re...@gm...] > Sent: Wednesday, May 21, 2008 11:07 AM > To: Ronciak, John > Cc: e10...@li... > Subject: Re: [E1000-devel] e1000 freezing during boot > > Hello, > Also, when eth2 is in freeze state, running `ethtool -s eth2 port tp` > solves the problem. > > On Wed, May 21, 2008 at 7:13 PM, Ronciak, John <joh...@in...> > wrote: >> Does the driver that comes with SLES10 work? Does eth0 or eth1 work? >> >> What is the output from: >> ethtool <ethx> >> ethtool -i <ethx> >> netstate -i >> ifconfig ethx >> >> >> Cheers, >> John >> ----------------------------------------------------------- >> "Those who would give up essential Liberty, to purchase a little >> temporary Safety, deserve neither Liberty nor Safety.", Benjamin >> Franklin 1755 >> >> -----Original Message----- >> From: e10...@li... >> [mailto:e10...@li...] On Behalf Of >> Stanislav Bogatyrev >> Sent: Wednesday, May 21, 2008 6:52 AM >> To: e10...@li... >> Subject: [E1000-devel] e1000 freezing during boot >> >> Hello, All! >> >> I run SLES-10 Linux with kernel 2.6.16. When system boots up. It >> configures network interfaces, but stays unreachable. When pingning >> from a remote - we just don't get ARP reply. When pinging from >> computer with the problem we see arp requests and arp replies (tcpdump >> on the target), but those replies do not come to OS level. Compilation >> with MSI disabled or with NAPI disabled doesn't solve the issue. >> >> Is there any workaround for this issue? >> >> kernel: 2.6.16-SLES10 >> driver: e1000 >> version: 7.6.15.5 >> firmware-version: N/A >> bus-info: 0000:02:06.0 >> 02:06.0 Ethernet controller: Intel Corporation 82546GB Gigabit >> Ethernet Controller (rev 03) >> Subsystem: Intel Corporation PRO/1000 MT Dual Port Network >> Connection >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- >> ParErr- Stepping- SERR- FastB2B- >> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >>>TAbort- <TAbort- <MAbort- >SERR- <PERR- >> Latency: 32 (63750ns min), Cache Line Size 08 >> Interrupt: pin A routed to IRQ 177 >> Region 0: Memory at d0000000 (64-bit, non-prefetchable) >> [size=128K] >> Region 4: I/O ports at c000 [size=64] >> Capabilities: [dc] Power Management version 2 >> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA >> PME(D0+,D1-,D2-,D3hot+,D3cold+) >> Status: D0 PME-Enable- DSel=0 DScale=1 PME- >> Capabilities: [e4] PCI-X non-bridge device >> Command: DPERE- ERO >> [17:39:55] byte_0xEB_0xFE: + RBC=512 OST=1 >> Status: Dev=02:06.0 64bit+ 133MHz+ SCD- USC- DC=simple >> DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- >> Capabilities: [f0] Message Signalled Interrupts: 64bit+ >> Queue=0/0 Enable- >> Address: 0000000000000000 Data: 0000 >> >> >> Settings for eth2: >> Supported ports: [ TP ] >> Supported link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> 1000baseT/Full >> Supports auto-negotiation: Yes >> Advertised link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> 1000baseT/Full >> Advertised auto-negotiation: Yes >> Speed: 1000Mb/s >> Duplex: Full >> Port: Twisted Pair >> PHYAD: 1 >> Transceiver: internal >> Auto-negotiation: on >> Supports Wake-on: umbg >> Wake-on: g >> Current message level: 0x00000007 (7) >> Link detected: yes >> >> Offset Values >> ------ ------ >> 0x0000 00 e0 81 5a f7 86 30 08 ff ff ff ff ff ff ff ff >> 0x0010 14 c4 03 21 0b 46 79 11 86 80 79 10 86 80 e8 b4 >> 0x0020 0c 00 7a 10 00 00 05 03 cc 1e ff ff ff ff ff ff >> 0x0030 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> 0x0040 0c c3 63 ff 04 50 05 03 c8 0c ff ff ff >> [17:39:57] byte_0xEB_0xFE: ff ff ff >> 0x0050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 02 06 >> 0x0060 00 01 00 40 11 12 ff ff ff ff ff ff ff ff ff ff >> 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 85 40 >> >> CPU0 CPU1 >> 0: 614377 0 IO-APIC-edge timer >> 1: 388 0 IO-APIC-edge i8042 >> 4: 1272 0 IO-APIC-edge serial >> 9: 0 0 IO-APIC-level acpi >> 169: 17752 0 IO-APIC-level eth1 >> 177: 137808 0 IO-APIC-level libata, eth2 >> 201: 25860 0 IO-APIC-level eth0 >> NMI: 0 0 >> LOC: 614176 614269 >> ERR: 0 >> MIS: 0 >> >> >> >> -- >> Best regards, >> Stanislav Bogatyrev aka realloc() >> >> > ------------------------------------------------------------------------ >> - >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> E1000-devel mailing list >> E10...@li... >> https://lists.sourceforge.net/lists/listinfo/e1000-devel >> > > > > -- > Best regards, > Stanislav Bogatyrev aka realloc() > > ------------------------------------------------------------------------ > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > E1000-devel mailing list > E10...@li... > https://lists.sourceforge.net/lists/listinfo/e1000-devel > -- Best regards, Stanislav Bogatyrev aka realloc() |
10 messages has been excluded from this view by a project administrator.
