From: "Simon Holm Thøgersen" <odie@cs.aau.dk>
To: w.landgraf@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: multiple bugs
Date: Sun, 11 Jan 2009 16:17:29 +0100 [thread overview]
Message-ID: <1231687049.17759.12.camel@odie.local> (raw)
In-Reply-To: <929931.34382.qm@web112216.mail.gq1.yahoo.com>
(Please use reply-to-all in order not to break threading, it makes it a
pain for everyone that tries to follow the discussion.)
søn, 11 01 2009 kl. 06:46 -0800, skrev We La:
> 1) More exactly, with all kernels since 2.6.27 -rcX until now, on attempts
> on about 10 machines, I don't get connection or data transfer. Thus I
> think it's not a regression on particular eth drivers, but perhaps on
> the routing or package handling. On my original message, I gave the
> config for one of these kernels. Below I give, for comparison, the
> config of 2.6.26.2 with which it still was working. I have no idea
> which of the differences of the config, or new features, can cause
> this problem.
How do you generate the config for 2.6.27-* and the other versions that
fail? You should normally just use the .config for 2.6.26.2 or whatever
you used last and run 'make oldconfig' selecting the default answer to
each new option unless you have a good reason not to and have read and
understood the help text that goes along with the option. This way you
wouldn't have run into the problem with kernel mode setting either.
And still, even if it is not a problem with a network driver but in
another part of the network layer etc. a bisection run would be a good
way to pinpoint the issue. But see if it is not your config that causes
the problem first.
Simon Holm Thøgersen
next prev parent reply other threads:[~2009-01-11 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 14:46 We La
2009-01-11 15:17 ` Simon Holm Thøgersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-11 4:21 We La
2009-01-11 10:39 ` multiple bugs Simon Holm Thøgersen
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=1231687049.17759.12.camel@odie.local \
--to=odie@cs.aau.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=w.landgraf@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®