Jonathan Nieder :
[...]
> - Is the PCI commit after writing to IntrStatus needed in the
>context of 3.0.y which does not have 92fc43b4159b ("r8169: modify
>the flow of the hw reset") but does call irq_mask_and_ack from time
>to time without a PCI commit immediately afterward? What sy
Hi,
Gerd, Lucas, can you test the attached patch? It works like this:
# prerequisites
apt-get install git build-essential
kernelrepos=git://git.kernel.org/pub/scm/linux/kernel/git/
# get the Linux kernel if you don't already have it
git clone $kernelrepos/torvalds/linux.git
# enter
Francois Romieu wrote:
> It's part of the "no processing" policy: the driver only acks what
> it cares about.
While you're here, a few more questions. ;-) No more after these,
I promise.
- Is the PCI commit after writing to IntrStatus needed in the
context of 3.0.y which does not have 92fc
Jonathan Nieder :
[...]
> From: Jonathan Nieder
> Subject: r8169: use event mask when disabling interrupts
>
> [ Extracted from commit 811fd3010cf512f2e23e6c4c912aad54516dc706
> upstream, which was written by François Romieu. ]
>
> Not sure what this one is about, to be honest.
It's part of
Ben Hutchings wrote:
> A backport to 3.0.y is good enough for Debian's purposes since squeeze
> now has r8169 from 3.0.2.
Oh! Thanks for the hint.
Here's a rough backport of the patch to Greg's linux-3.0.y branch and
split into 4 pieces, with an explanation involving some guesswork for
each. I
On Sun, 2012-02-19 at 20:45 -0600, Jonathan Nieder wrote:
> boos...@wolke7.net wrote:
>
> > If there are any backports of the fix to the 3.0 and 2.6 kernels I can
> > test them as well if you like.
>
> Thanks again for the offer. Backporting the fix to 3.0.y is
> straightforward; I haven't tried
boos...@wolke7.net wrote:
> If there are any backports of the fix to the 3.0 and 2.6 kernels I can
> test them as well if you like.
Thanks again for the offer. Backporting the fix to 3.0.y is
straightforward; I haven't tried 2.6.32.y yet. Followed up upstream
--- it would be best if we can do t
Jonathan Nieder wrote:
Hi again,
Jonathan Nieder wrote:
Something very similar to the fix you tested plus a couple more r8169
fixes were applied upstream:
- v3.2-rc5~38^2~5 (r8169: Rx FIFO overflow fixes, 2011-12-04), which
is the fix you helped with
- v3.2-rc5~38^2~4 (r816
Hi again,
Jonathan Nieder wrote:
> Something very similar to the fix you tested plus a couple more r8169
> fixes were applied upstream:
>
> - v3.2-rc5~38^2~5 (r8169: Rx FIFO overflow fixes, 2011-12-04), which
>is the fix you helped with
> - v3.2-rc5~38^2~4 (r8169: fix Rx index race between
Jonathan Nieder wrote:
> If you have time for it, please test the fix on top of the 3.0.y
> branch. It works like this:
[...]
> 2. git checkout -f stable/linux-3.0.y
> git am -3 $HOME/downloads/0001-r8169-Rx-FIFO-overflow-fixes.patch
>
> make localmodconfig; # minimal configuration
>
Hi Gerd,
boos...@wolke7.net wrote:
> All the squeeze kernels cause the same hang during high load at the network.
> Today I installed the 3.1 kernel and did some testing by copying files
> with samba.
> The problem still exists and is even worse: Now the CPU hangs during the
> interrupts:
Someth
found 642911 linux-2.6/2.6.32-39
found 642911 linux-2.6/3.1.1-1
forwarded 642911 http://thread.gmane.org/gmane.linux.network/212958
quit
boos...@wolke7.net wrote:
> All the squeeze kernels cause the same hang during high load at the network.
> Today I installed the 3.1 kernel and did some testing
Hi Gerd,
Ben Hutchings wrote:
> On Wed, 2011-09-28 at 08:37 +0200, boos...@wolke7.net wrote:
>> I tested version 2.6.32-37. The network seems to be more stable, but I still
>> have connection timeouts. There are no more dmesg lines for "eth0: link
>> up" but my
>> ssh connection still terminates
13 matches
Mail list logo