LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-next <linux-next@vger.kernel.org>,
	Tom Herbert <therbert@google.com>
Cc: "Jay Vosburgh" <fubar@us.ibm.com>,
	"Andy Gospodarek" <andy@greyhouse.net>,
	"David S. Miller" <davem@davemloft.net>,
	"Alexey Kuznetsov" <kuznet@ms2.inr.ac.ru>,
	"Pekka Savola (ipv6)" <pekkas@netcore.fi>,
	"James Morris" <jmorris@namei.org>,
	"Hideaki YOSHIFUJI" <yoshfuji@linux-ipv6.org>,
	"Patrick McHardy" <kaber@trash.net>,
	"Eric Dumazet" <eric.dumazet@gmail.com>,
	"Changli Gao" <xiaosuo@gmail.com>,
	"Jesse Gross" <jesse@nicira.com>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"Ben Hutchings" <bhutchings@solarflare.com>,
	"Stanislaw Gruszka" <sgruszka@redhat.com>,
	"Kees Cook" <kees.cook@canonical.com>,
	"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: [net-next-2.6] Revert "net: Allow no-cache copy from user on transmit"
Date: Thu, 7 Apr 2011 14:07:34 +0200	[thread overview]
Message-ID: <BANLkTiketFqStHcucXPFnuL3awGgpHQMQw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=GFbgwV_7XJAJgKrY6A6J8-4FAdQ@mail.gmail.com>

On Thu, Apr 7, 2011 at 1:03 PM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> ...will try the patch from [1]:
>
> - Sedat -
>
> [1] http://marc.info/?l=linux-netdev&m=130215119417648&w=2
>

The patch from above fixes my network problems.
Thanks.

- Sedat -

> On Thu, Apr 7, 2011 at 12:49 PM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
>> [ The long CC list I got via ./scripts/get_maintainer.pl ]
>>
>> Hi,
>>
>> with yesterday's linux-next (next-20110406) I discovered first time
>> network problems.
>> Today's next-20110407 shows the same symptoms.
>> In my IRC client the connection via SSL-encryption to freenode and
>> oftc are not established.
>> Also, I saw "stalls" on websites in firefox.
>>
>> Luckily, next-20110405 was OK, so I started to look at the
>> net-next-2.6 merge and its commits.
>> ( Furthermore, I tested a 2.6.39-rc2 vanilla kernel to ensure the
>> problem comes from linux-next patch. )
>>
>> By reverting all 10 commits my system worked as expected, here the list:
>>
>> 0001-Revert-net-Allow-no-cache-copy-from-user-on-transmit.patch
>> 0002-Revert-bridge-range-check-STP-parameters.patch
>> 0003-Revert-bridge-allow-creating-bridge-devices-with-net.patch
>> 0004-Revert-bridge-allow-creating-deleting-fdb-entries-vi.patch
>> 0005-Revert-bridge-add-netlink-notification-on-forward-en.patch
>> 0006-Revert-bridge-split-rcu-and-no-rcu-cases-of-fdb-look.patch
>> 0007-Revert-bridge-track-last-used-time-in-forwarding-tab.patch
>> 0008-Revert-bridge-change-arguments-to-fdb_create.patch
>> 0009-Revert-pkt_sched-QFQ-quick-fair-queue-scheduler.patch
>> 0010-Revert-xen-netfront-assume-all-hw-features-are-avail.patch
>>
>> In a next run, I started with only
>> "0001-Revert-net-Allow-no-cache-copy-from-user-on-transmit.patch".
>> It turned out that this is the culprit commit.
>> ( I have not played with the new ethtool option tx-nocache-copy in
>> "BROKEN" kernel. )
>>
>> My wificard is an Atheros ath5k.
>> I attached my kernel-config and the revert-patch which makes the
>> system stable again.
>>
>> Can you have a look at it?
>>
>> I you want me to help with debugging, please give me precise instructions.
>>
>> Regards,
>> - Sedat -
>>
>

      reply	other threads:[~2011-04-07 12:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07 10:49 Sedat Dilek
2011-04-07 11:03 ` Sedat Dilek
2011-04-07 12:07   ` Sedat Dilek [this message]

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=BANLkTiketFqStHcucXPFnuL3awGgpHQMQw@mail.gmail.com \
    --to=sedat.dilek@googlemail.com \
    --cc=andy@greyhouse.net \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=fubar@us.ibm.com \
    --cc=jesse@nicira.com \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kees.cook@canonical.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=netdev@vger.kernel.org \
    --cc=pekkas@netcore.fi \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sgruszka@redhat.com \
    --cc=therbert@google.com \
    --cc=xiaosuo@gmail.com \
    --cc=yoshfuji@linux-ipv6.org \
    --subject='Re: [net-next-2.6] Revert "net: Allow no-cache copy from user on transmit"' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).