Bug#497392: e1000e driver does not initialize correctly
Package: linux-image-2.6.26-1-686
Version: 2.6.26-3
Severity: important
The e1000e kernel module does not initialize correctly, then the network cannot initialize.
It does not complain, but packets do not exit correctly. The port's LED on switch blinks quickly all time, IPv6 RA's are recevied by the kernel, but no DHCP packet reaches router, nor any ICMP one after manual configuration.
rmmod / modprobe module *sometimes* makes it working correctly, then the network interface is bringed up, DHCP responds, and communication can be established.
e1000e worked correctly with linux-image-2.6.25-2-686 kernel.
-- Package-specific info:
** Version:
Linux version 2.6.26-1-686 (Debian 2.6.26-3) (waldi@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Aug 20 12:56:41 UTC 2008
** Command line:
root=/dev/sda6 ro
** Not tainted
** Kernel log:
[ 5.639460] EXT3-fs: mounted filesystem with ordered data mode.
[ 6.838118] udevd version 125 started
[ 7.555905] input: PC Speaker as /class/input/input3
[ 8.116282] ACPI: PCI Interrupt 0000:00:1f.3[b] -> GSI 18 (level, low) -> IRQ 18
[ 8.240908] Linux agpgart interface v0.103
[ 8.280909] agpgart: Detected an Intel G33 Chipset.
[ 8.280909] agpgart: Detected 7164K stolen memory.
[ 8.294893] agpgart: AGP aperture is 256M @ 0xd0000000
[ 8.297597] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[ 8.316909] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008)
[ 8.316909] iTCO_wdt: Found a ICH9R TCO device (Version=2, TCOBASE=0x0460)
[ 8.316909] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 8.568520] input: Power Button (FF) as /class/input/input4
[ 8.620819] ACPI: Power Button (FF) [PWRF]
[ 8.620945] input: Power Button (CM) as /class/input/input5
[ 8.669703] ACPI: Power Button (CM) [PWRB]
[ 9.048402] Error: Driver 'pcspkr' is already registered, aborting...
[ 9.068403] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22
[ 9.068403] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[ 9.104403] hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
[ 9.888929] Adding 1847432k swap on /dev/sda12. Priority:-1 extents:1 across:1847432k
[ 10.222051] EXT3 FS on sda6, internal journal
[ 10.641805] it87: Found IT8718F chip at 0x290, revision 3
[ 10.641805] it87: in3 is VCC (+5V)
[ 10.641805] it87: in7 is VCCH (+5V Stand-By)
[ 10.657357] coretemp coretemp.0: Using relative temperature scale!
[ 10.657357] coretemp coretemp.1: Using relative temperature scale!
[ 10.745725] device-mapper: uevent: version 1.0.3
[ 10.745725] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-devel@redhat.com
[ 26.582047] kjournald starting. Commit interval 5 seconds
[ 26.582047] EXT3 FS on sda10, internal journal
[ 26.582047] EXT3-fs: mounted filesystem with ordered data mode.
[ 26.605941] kjournald starting. Commit interval 5 seconds
[ 26.605941] EXT3 FS on sda8, internal journal
[ 26.605941] EXT3-fs: mounted filesystem with ordered data mode.
[ 26.641371] kjournald starting. Commit interval 5 seconds
[ 26.641371] EXT3-fs: mounted filesystem with ordered data mode.
[ 26.661274] kjournald starting. Commit interval 5 seconds
[ 26.661274] EXT3-fs: mounted filesystem with ordered data mode.
[ 26.677206] kjournald starting. Commit interval 5 seconds
[ 26.677206] EXT3-fs: mounted filesystem with ordered data mode.
[ 29.971694] eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
[ 29.971758] eth0: 10/100 speed: disabling TSO
[ 42.084477] NET: Registered protocol family 10
[ 42.085051] lo: Disabled Privacy Extensions
[ 42.899159] lp: driver loaded but no devices found
[ 42.955150] ppdev: user-space parallel port driver
[ 44.514082] RPC: Registered udp transport module.
[ 44.514082] RPC: Registered tcp transport module.
[ 44.540877] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 44.588337] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 44.603502] NFSD: starting 90-second grace period
[ 45.513208] warning: `ntpd' uses 32-bit capabilities (legacy support in use)
[ 50.493377] [drm] Initialized drm 1.1.0 20060810
[ 50.507808] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 50.507819] PCI: Setting latency timer of device 0000:00:02.0 to 64
[ 50.507903] [drm] Initialized i915 1.6.0 20060119 on minor 0
[ 51.063638] set status page addr 0x00033000
[ 72.047875] UDF-fs: Partition marked readonly; forcing readonly mount
[ 72.079879] UDF-fs INFO UDF: Mounting volume 'VIIS', timestamp 2007/08/30 17:19 (1078)
[ 120.622085] ACPI: PCI interrupt for device 0000:00:19.0 disabled
[ 161.188681] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k2
[ 161.188681] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 161.188681] ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 20
[ 161.188681] PCI: Setting latency timer of device 0000:00:19.0 to 64
[ 161.278868] eth0: (PCI Express:2.5GB/s:Width x1) 00:1d:09:78:34:2b
[ 161.278874] eth0: Intel(R) PRO/10/100 Network Connection
[ 161.278900] eth0: MAC: 5, PHY: 7, PBA No: ffffff-0ff
[ 161.321589] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 162.876381] eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
[ 162.876381] eth0: 10/100 speed: disabling TSO
[ 162.876381] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 175.200514] eth0: no IPv6 routers present
[ 207.020907] ACPI: PCI interrupt for device 0000:00:19.0 disabled
[ 209.857248] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[ 209.857255] Copyright (c) 1999-2006 Intel Corporation.
[ 261.918883] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k2
[ 261.918883] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 261.918883] ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 20
[ 261.918883] PCI: Setting latency timer of device 0000:00:19.0 to 64
[ 262.006886] eth0: (PCI Express:2.5GB/s:Width x1) 00:1d:09:78:34:2b
[ 262.006886] eth0: Intel(R) PRO/10/100 Network Connection
[ 262.006886] eth0: MAC: 5, PHY: 7, PBA No: ffffff-0ff
[ 262.050364] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 263.799046] eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
[ 263.799053] eth0: 10/100 speed: disabling TSO
[ 263.799283] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 320.581736] ACPI: PCI interrupt for device 0000:00:19.0 disabled
[ 325.196148] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k2
[ 325.196148] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 325.196148] ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 20
[ 325.196148] PCI: Setting latency timer of device 0000:00:19.0 to 64
[ 325.282805] eth0: (PCI Express:2.5GB/s:Width x1) 00:1d:09:78:34:2b
[ 325.282811] eth0: Intel(R) PRO/10/100 Network Connection
[ 325.282837] eth0: MAC: 5, PHY: 7, PBA No: ffffff-0ff
[ 325.330808] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 327.014511] eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
[ 327.014517] eth0: 10/100 speed: disabling TSO
[ 327.014760] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1182.677148] EXT3 FS on sda7, internal journal
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-1-686 depends on:
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92f tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.26-1-686 recommends:
ii libc6-i686 2.7-13 GNU C Library: Shared libraries [i
Versions of packages linux-image-2.6.26-1-686 suggests:
ii grub 0.97-46 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.26 <none> (no description available)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-21-2008, 01:14 PM
Bastian Blank
Bug#497392: e1000e driver does not initialize correctly
On Mon, Sep 01, 2008 at 02:22:00PM +0200, Bastien Durel wrote:
> The e1000e kernel module does not initialize correctly, then the network cannot initialize.
Please explain, the attached log does not show strange e1000 related
messages.
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 222
> Region 0: Memory at fdfc0000 (32-bit, non-prefetchable) [size=128K]
> Region 1: Memory at fdfff000 (32-bit, non-prefetchable) [size=4K]
> Region 2: I/O ports at fe00 [size=32]
> Capabilities: <access denied>
> Kernel driver in use: e1000e
> Kernel modules: e1000e
Mine is know to work.
02:00.0 Ethernet controller [0200]: Intel Corporation 82573L Gigabit Ethernet Controller [8086:109a]
Subsystem: Lenovo Device [17aa:207e]
Flags: bus master, fast devsel, latency 0, IRQ 218
Memory at ee000000 (32-bit, non-prefetchable) [size=128K]
I/O ports at 2000 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e
Bstian
--
Too much of anything, even love, isn't necessarily a good thing.
-- Kirk, "The Trouble with Tribbles", stardate 4525.6
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-22-2008, 11:44 AM
Bastien Durel
Bug#497392: e1000e driver does not initialize correctly
Le dimanche 21 septembre 2008 à 15:14 +0200, Bastian Blank a écrit :
> On Mon, Sep 01, 2008 at 02:22:00PM +0200, Bastien Durel wrote:
> > The e1000e kernel module does not initialize correctly, then the network cannot initialize.
>
> Please explain, the attached log does not show strange e1000 related
> messages.
>
Well,
when the module is inserted, nothing complains, the RAs are recevied,
but ipv4 cannot be used on the interface. DHCP does not respond, and
manual configuration does not allow packets to reach another computer.
tcpdump on the router does not show any packet going from the computer
during DHCP or after manual configuration.
After a few(exact number may change) rmmod's modprobe's, IPv4 can goes
through interface. *That's* very strange.
> > 00:19.0 Ethernet controller [0200]: Intel Corporation 82562V-2 10/100 Network Connection [8086:10c0] (rev 02)
> > Subsystem: Dell Device [1028:0238]
>
> Which sort of controller is this?
>
It's an onboard 10/100 controler, on a Vostro-200 dell computer.
--
Bastien Durel
11-07-2008, 10:01 PM
Moritz Muehlenhoff
Bug#497392: e1000e driver does not initialize correctly
On Mon, Sep 22, 2008 at 01:44:38PM +0200, Bastien Durel wrote:
> Le dimanche 21 septembre 2008 à 15:14 +0200, Bastian Blank a écrit :
> > On Mon, Sep 01, 2008 at 02:22:00PM +0200, Bastien Durel wrote:
> > > The e1000e kernel module does not initialize correctly, then the network cannot initialize.
> >
> > Please explain, the attached log does not show strange e1000 related
> > messages.
> >
> Well,
>
> when the module is inserted, nothing complains, the RAs are recevied,
> but ipv4 cannot be used on the interface. DHCP does not respond, and
> manual configuration does not allow packets to reach another computer.
> tcpdump on the router does not show any packet going from the computer
> during DHCP or after manual configuration.
>
> After a few(exact number may change) rmmod's modprobe's, IPv4 can goes
> through interface. *That's* very strange.
Is this behaviour also reproducible if you try a current 2.6.28-rcX
kernel? If so, could you file a report at bugzilla.kernel.org?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-09-2008, 09:35 PM
Bastien Durel
Bug#497392: e1000e driver does not initialize correctly
Le samedi 08 novembre 2008 à 00:01 +0100, Moritz Muehlenhoff a écrit :
> On Mon, Sep 22, 2008 at 01:44:38PM +0200, Bastien Durel wrote:
> > Le dimanche 21 septembre 2008 à 15:14 +0200, Bastian Blank a écrit :
> > > On Mon, Sep 01, 2008 at 02:22:00PM +0200, Bastien Durel wrote:
> > > > The e1000e kernel module does not initialize correctly, then the network cannot initialize.
> > >
> > > Please explain, the attached log does not show strange e1000 related
> > > messages.
> > >
> > Well,
> >
> > when the module is inserted, nothing complains, the RAs are recevied,
> > but ipv4 cannot be used on the interface. DHCP does not respond, and
> > manual configuration does not allow packets to reach another computer.
> > tcpdump on the router does not show any packet going from the computer
> > during DHCP or after manual configuration.
> >
> > After a few(exact number may change) rmmod's modprobe's, IPv4 can goes
> > through interface. *That's* very strange.
>
> Is this behaviour also reproducible if you try a current 2.6.28-rcX
> kernel? If so, could you file a report at bugzilla.kernel.org?
>
> Cheers,
> Moritz
I reproduce it with 2.6.28-rc3
Linux sietchtabr 2.6.28-rc3 #2 SMP Sun Nov 9 23:05:00 CET 2008 i686
GNU/Linux
I copied .configure from linux-headers-2.6.22-3-686, adding e1000e
support.
rmmod e1000e ; modprobe e1000e was required to recieve DHCP info.
Cheers,
--
Bastien Durel
02-22-2010, 11:13 AM
Jérôme Avond
Bug#497392: e1000e driver does not initialize correctly
I can confirm the same behaviour on 6 Dell's desktop computer, with
Intel Corporation 82562V-2 10/100 Network Connection Ethernet card
embeded in the motherboard.
First we thougth it was because of wires or old-switch, but now
everythings fine, we reproduce the sames problems :
- dhcp doesn't bring up, with tcpdump silent
- modprobe e1000e/ -r e1000e make it works
- plug / unplug card/or/switch/or/power of switch
$ sudo lspci | grep 8256
00:19.0 Ethernet controller: Intel Corporation 82562V-2 10/100 Network
Connection (rev 02)
$ sudo lsmod |grep e1
e1000e 84612 0
$ sudo cat /etc/issue
Debian GNU/Linux 5.0
l
$ uname -a
Linux formaxo2 2.6.26-2-686 #1 SMP Sun Jun 21 04:57:38 UTC 2009 i686
GNU/Linux
$ sudo modinfo e1000e
filename: /lib/modules/2.6.26-2-686/kernel/drivers/net/e1000e/e1000e.ko
version: 0.3.3.3-k2
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
srcversion: 91473E7675870049C25134A
...
$ sudo aptitude search ~i~n"^linux"
i A linux-headers-2.6-486 - Header files for
Linux 2.6-486
i A linux-headers-2.6.26-2-486 - Header files for
Linux 2.6.26-2-486
i linux-headers-2.6.26-2-686 - Header files for
Linux 2.6.26-2-686
i A linux-headers-2.6.26-2-common - Common header
files for Linux 2.6.26-2
i linux-image-2.6-686 - image du noyau
Linux version 2.6 pour PPro/Celeron/PII/PII
i A linux-image-2.6.26-2-486 - Linux 2.6.26
image on x86
i A linux-image-2.6.26-2-686 - Linux 2.6.26
image on PPro/Celeron/PII/PIII/P4
i A linux-kbuild-2.6.26 - Kbuild
infrastructure for Linux 2.6.26
i A linux-libc-dev - Linux support
headers for userspace development
i A linux-sound-base - Paquet de base
pour les systèmes de son ALSA et OSS
...
$ ls -l /lib/modules/2.6.*/kernel/drivers/net/e1000e/e1000e.ko
-rw-r--r-- 1 root root 111371 fév 10
13:25 /lib/modules/2.6.26-2-486/kernel/drivers/net/e1000e/e1000e.ko
-rw-r--r-- 1 root root 112627 fév 10
13:26 /lib/modules/2.6.26-2-686/kernel/drivers/net/e1000e/e1000e.ko
--
Jérôme Avond <j.avond@axolys.fr>
Axolys, Société de services en logiciels libres
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1266840825.8630.15.camel@jay1">http://lists.debian.org/1266840825.8630.15.camel@jay1