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
