From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-mm1 bugs
Date: Fri, 15 Feb 2008 10:36:05 -0800 [thread overview]
Message-ID: <47B5DB95.3020002@intel.com> (raw)
In-Reply-To: <E1JQ5Er-0005p7-HD@pomaz-ex.szeredi.hu>
Miklos Szeredi wrote:
>> the register dump looks OK as far as I can see. Since initialization
>> works OK and the adapter seems to be setup OK reading from the
>> register dump, I'm not sure at all what is going on.
>>
>> can you try manually ifup-ing the device and running tcpdump? do you
>> see packets coming in?
>
> Well it does seem to receive the DHCP reply.
>
>> just for kicks, have you tried a different cable? or is the adapter
>> consistently working properly using a different kernel/driver?
>
> It has been consistently working properly for a long time with various
> kernels (and the e1000 driver). I've now swithed to 2.6.24-mm1 and
> e1000e, and it's almost consistently broken after boot and resume, and
> sometimes needs several tries (with the KDE NetworkManager thingy) to
> make it work.
maybe it's worth trying linux-2.6.git instead for now? The e1000e driver is
actually involved in the dhcp handshake so we can't just rule a bug out yet.
However, with my own t60 things appear to work just fine.
how does manually getting a dhcp address go? can you eliminate networkmanager
perhaps? just kill & restart dhclient over and over again...
Auke
next prev parent reply other threads:[~2008-02-15 18:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 11:43 2.6.24-mm1 bugs Miklos Szeredi
2008-02-15 12:45 ` Peter Zijlstra
2008-02-15 12:54 ` Miklos Szeredi
2008-02-18 12:05 ` Miklos Szeredi
2008-02-15 16:28 ` Kok, Auke
2008-02-15 16:41 ` Miklos Szeredi
2008-02-15 16:53 ` Kok, Auke
2008-02-15 17:51 ` Miklos Szeredi
2008-02-15 18:15 ` Miklos Szeredi
2008-02-15 18:16 ` Kok, Auke
2008-02-15 18:24 ` Miklos Szeredi
2008-02-15 18:36 ` Kok, Auke [this message]
2008-02-15 16:42 ` Kok, Auke
2008-02-15 16:46 ` isofs - " Valdis.Kletnieks
2008-02-15 20:15 ` Andrew Morton
2008-02-15 18:47 ` Jeff Dike
2008-02-15 19:52 ` Miklos Szeredi
2008-02-15 20:27 ` Bartlomiej Zolnierkiewicz
2008-02-15 20:46 ` Jeff Dike
2008-02-15 21:00 ` Miklos Szeredi
2008-02-18 21:03 ` [bug] uml doesn't boot under 2.6.25-rc1 host (was Re: 2.6.24-mm1 bugs) Miklos Szeredi
2008-02-21 17:20 ` Miklos Szeredi
2008-02-21 23:54 ` Jeff Dike
2008-02-22 4:37 ` Roland McGrath
2008-02-22 4:37 ` [PATCH] x86 ptrace: fix compat PTRACE_SETREGS Roland McGrath
2008-02-22 9:08 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47B5DB95.3020002@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.