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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, May 22, 2008 12:53 AM To: Ronciak, John Cc: e1000-devel@lists.sourceforge.net 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: [EMAIL PROTECTED] [EMAIL PROTECTED] > Sent: Wednesday, May 21, 2008 1:43 PM > > To: Ronciak, John > > Cc: e1000-devel@lists.sourceforge.net > 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 [EMAIL PROTECTED] > > il.com] > > > Sent: Wednesday, May 21, 2008 1:16 PM > > > > > > To: Tantilov, Emil S > > > > > > Cc: Ronciak, John; e1000-devel@lists.sourceforge.net > > 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 > [EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > > > [EMAIL PROTECTED] On Behalf Of > > Ronciak, > > > > > > > John > > > > > > > Sent: Wednesday, May 21, 2008 11:24 AM > > > > > > > To: Stanislav Bogatyrev > > > > > > > Cc: e1000-devel@lists.sourceforge.net > > > 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 [EMAIL PROTECTED] > > il.com] > > > > Sent: Wednesday, May 21, 2008 11:07 AM > > > > > > > To: Ronciak, John > > > > > > > Cc: e1000-devel@lists.sourceforge.net > > > 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 > > > [EMAIL PROTECTED] > .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: [EMAIL PROTECTED] > > >> [EMAIL PROTECTED] On Behalf Of > > >> Stanislav Bogatyrev > > > > > > >> Sent: Wednesday, May 21, 2008 6:52 AM > > > > > > >> To: e1000-devel@lists.sourceforge.net > > >> 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 > > > > > > >> E1000-devel@lists.sourceforge.net > > >> 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 > > > > > > > E1000-devel@lists.sourceforge.net > > > 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 > > > > > > E1000-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > > > > > > > > > > > ---- Msg sent via email.ru > > > > ---- Msg sent via email.ru ------------------------------------------------------------------------- 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 E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
