Bug#497392: maybe a duplicate of bug 601017

2010-11-22 Thread Bastien Durel 
Le lundi 22 novembre 2010 à 12:37 +, Ben Hutchings a écrit :
> On Mon, 2010-11-22 at 03:18 -0800, Kenyon Ralph wrote:
> > This looks like a duplicate of bug 601017, which was marked fixed in
> > version linux-2.6/2.6.32-27:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601017
> 
> Yes, it could be.  Bastien, please could you test the new version.
> 
> Ben.
> 
Hello,

The bug was hardware-dependent (it cannot be reproduced with any switch)
and I throw the old one I had problem with. Then I cannot try.
The specific bug was followed by intel's guy at
https://bugzilla.kernel.org/show_bug.cgi?id=11998 

the "fix" I used was introduction of a "mdix" parameter, which is not
shown on 2.6.32-5-amd64's e1000e modinfo

I'm sorry to cannot test that.

-- 
Bastien Durel



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1290432772.3292.15.ca...@sietchtabr.geekwu.org

Bug#497392: e1000e driver does not initialize correctly

2008-11-09 Thread Bastien Durel 
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


smime.p7s
Description: S/MIME cryptographic signature

Bug#497392: e1000e driver does not initialize correctly

2008-09-22 Thread Bastien Durel 
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


smime.p7s
Description: S/MIME cryptographic signature

Bug#497392: e1000e driver does not initialize correctly

2008-09-01 Thread Bastien Durel 
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) ([EMAIL PROTECTED]) (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 :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 @ 0xd000
[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 :00:1b.0[A] -> GSI 22 (level, low) -> 
IRQ 22
[9.068403] PCI: Setting latency timer of device :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: 
[EMAIL PROTECTED]
[   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 [EMAIL PROTECTED]).
[   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 :00:02.0[A] -> GSI 16 (level, low) -> 
IRQ 16
[   50.507819] PCI: Setting latency timer of device :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 :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 :00:19.0[A] -> GSI 20 (level, low) -