Menu
▾
▴
Re: [E1000-devel] Problems compiling e1000 drivers
|
From: Brian M. <bmc...@gm...> - 2006-10-30 07:00:42
|
After some testing with the new driver (7.3.15_tdhdump according to modinfo), I'm still having the same problem as before. That is, traffic over the interface halts when I start passing a lot of traffic over it. I haven't done any testing to determine what that threshold is. Bouncing the interface fixes the problem until the next burst of traffic happens. -- Brian McNally On Oct 29, 2006, at 10:40 PM, Brian McNally wrote: > Thanks for the quick reply Auke. I was a bit concerned that my > message had even be sent to the list because the sourceforge web > interface hasn't shown any messages since 9/27/2006. > > I'm using the PWLA8391GT card. I've got the full kernel source, and > not just the headers. I ran `make versioncheck` without luck. > However, copying my .config from /boot and running just `make` in > my source directory created the appropriate files. I was able to > compile the driver afterwards. > > I'm having some problems actually inserting the new module though. > After running `make` I removed the old e1000 with `modprobe -n > e1000` which appeared to work according to lsmod. Then, I inserted > the new one with `insmod e1000.ko`. According to modinfo that > loaded the same version of the module that I already had (7.0.33- > k2). Is there something I'm doing wrong here? > > `lspci -vv` indicates the following: > > 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/ > KM133] (rev 03) > 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: 0 > Region 0: Memory at d8000000 (32-bit, prefetchable) [size=64M] > Capabilities: <available only to root> > > 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/ > KM133 AGP] (prog-if 00 [Normal decode]) > 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: 0 > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > Memory behind bridge: dc000000-ddffffff > Prefetchable memory behind bridge: d0000000-d7ffffff > BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B- > Capabilities: <available only to root> > > 0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo > Super South] (rev 40) > Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge > 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: 0 > Capabilities: <available only to root> > > 0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/ > VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a > [Master SecP PriP]) > Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/ > VT8233/A/C/VT8235 PIPC Bus Master IDE > 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 > Region 4: I/O ports at c000 [size=16] > Capabilities: <available only to root> > > 0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super > ACPI] (rev 40) > Subsystem: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] > 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- > Interrupt: pin ? routed to IRQ 5 > Capabilities: <available only to root> > > 0000:00:0a.0 RAID bus controller: Silicon Image, Inc. SiI 3512 > [SATALink/SATARaid] Serial ATA Controller (rev 01) > Subsystem: Silicon Image, Inc. SiI 3512 SATARaid Controller > 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, Cache Line Size: 0x08 (32 bytes) > Interrupt: pin A routed to IRQ 10 > Region 0: I/O ports at cc00 [size=8] > Region 1: I/O ports at d000 [size=4] > Region 2: I/O ports at d400 [size=8] > Region 3: I/O ports at d800 [size=4] > Region 4: I/O ports at dc00 [size=16] > Region 5: Memory at df040000 (32-bit, non-prefetchable) > [size=512] > Expansion ROM at 20000000 [disabled] [size=512K] > Capabilities: <available only to root> > > 0000:00:0b.0 Ethernet controller: D-Link System Inc RTL8139 > Ethernet (rev 10) > Subsystem: D-Link System Inc DFE-530TX+ 10/100 Ethernet > Adapter > 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 (8000ns min, 16000ns max) > Interrupt: pin A routed to IRQ 12 > Region 0: I/O ports at e000 [size=256] > Region 1: Memory at df041000 (32-bit, non-prefetchable) > [size=256] > Capabilities: <available only to root> > > 0000:00:0d.0 Ethernet controller: Intel Corporation 82541PI Gigabit > Ethernet Controller (rev 05) > Subsystem: Intel Corporation: Unknown device 1376 > 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: 0x08 (32 bytes) > Interrupt: pin A routed to IRQ 11 > Region 0: Memory at df000000 (32-bit, non-prefetchable) > [size=128K] > Region 1: Memory at df020000 (32-bit, non-prefetchable) > [size=128K] > Region 2: I/O ports at e400 [size=64] > Expansion ROM at 20080000 [disabled] [size=128K] > Capabilities: <available only to root> > > 0000:00:0e.0 Ethernet controller: D-Link System Inc RTL8139 > Ethernet (rev 10) > Subsystem: D-Link System Inc DFE-530TX+ 10/100 Ethernet > Adapter > 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 (8000ns min, 16000ns max) > Interrupt: pin A routed to IRQ 10 > Region 0: I/O ports at e800 [size=256] > Region 1: Memory at df042000 (32-bit, non-prefetchable) > [size=256] > Capabilities: <available only to root> > > 0000:01:00.0 VGA compatible controller: nVidia Corporation NV15 > [GeForce2 GTS/Pro] (rev a3) (prog-if 00 [VGA]) > Subsystem: Guillemot Corporation: Unknown device 7000 > 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 (1250ns min, 250ns max) > Interrupt: pin A routed to IRQ 11 > Region 0: Memory at dc000000 (32-bit, non-prefetchable) > [size=16M] > Region 1: Memory at d0000000 (32-bit, prefetchable) > [size=128M] > Expansion ROM at dd000000 [disabled] [size=64K] > Capabilities: <available only to root> > > -- > Brian McNally > > > On Oct 29, 2006, at 6:32 PM, Auke Kok wrote: > >> Brian McNally wrote: >>> Like others on this list, I've got the "e1000_clean_tx_irq: >>> Detected Tx Unit Hang" error. For reference, I'm running Ubuntu >>> Server 6.06 and the 2.6.15-26 kernel. I've been told that recent >>> versions of the driver may fix my problem. >> >> it also depends heavily on your hardware, so please include `lspci >> -vv` output for the device. What chipset is on your e1000? >> >>> From looking at the Makefile, it looks like I need version.h and >>> autoconf.h. The linux-source-2.6.15 package doesn't have these >>> files though, which expectedly causes make to fail. What can I >>> do to fix or work around this? I've tried copying these files >>> from another 2.6.15 kernel source, but that didn't work. >> >> the kernel autogenerates those as soon as you start compiling. You >> will need them available in the sources. Depending on your distro, >> this may be as easy as doing `make versioncheck` in your /usr/src/ >> linux directory. "only" kernel-headers may not be enough, having >> the full kernel sources installed will always work though, once >> they have been configured properly. >> >> BTW, in 2.6.18 you need utsrelease.h instead of version.h >> >>> Also, is there a command I can use to list the version of a >>> loaded module? If I'm successful with getting these drivers >>> compiled that would probably be a helpful command to have. >> >> `modinfo e1000` shows you the version number of the properly >> installed e1000 module for the currently running kernel, whether >> the e1000 module was loaded or not. >> >> hth, >> >> Auke > |
