...will try the patch from [1]: - Sedat - [1] http://marc.info/?l=linux-netdev&m=130215119417648&w=2 On Thu, Apr 7, 2011 at 12:49 PM, Sedat Dilek <sedat.dilek@xxxxxxxxxxxxxx> 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 - > -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
