Am Donnerstag, den 09.09.2010, 04:23 +0100 schrieb Ben Hutchings:
> On Tue, 2010-09-07 at 13:25 +0200, Lukas Kolbe wrote:
> > On Wed, 2010-09-01 at 05:26 +0100, Ben Hutchings wrote:
> > > On Tue, 2010-08-31 at 17:34 +0200, Lukas Kolbe wrote:
> > > > On Tue, 2010-08-31 at 06:35 -0700, Greg KH wrote:
On Tue, 2010-09-07 at 13:25 +0200, Lukas Kolbe wrote:
> On Wed, 2010-09-01 at 05:26 +0100, Ben Hutchings wrote:
> > On Tue, 2010-08-31 at 17:34 +0200, Lukas Kolbe wrote:
> > > On Tue, 2010-08-31 at 06:35 -0700, Greg KH wrote:
> > [...]
> > > > Then how about convincing the Debian kernel developers
On Wed, 2010-09-01 at 05:26 +0100, Ben Hutchings wrote:
> On Tue, 2010-08-31 at 17:34 +0200, Lukas Kolbe wrote:
> > On Tue, 2010-08-31 at 06:35 -0700, Greg KH wrote:
> [...]
> > > Then how about convincing the Debian kernel developers to accept these
> > > patches, and work through any regressions
On Tue, 2010-08-31 at 17:34 +0200, Lukas Kolbe wrote:
> On Tue, 2010-08-31 at 06:35 -0700, Greg KH wrote:
[...]
> > Then how about convincing the Debian kernel developers to accept these
> > patches, and work through any regressions that might be found and after
> > that, reporting back to us?
>
>
On Tue, 2010-08-31 at 06:35 -0700, Greg KH wrote:
> On Tue, Aug 31, 2010 at 10:16:56AM +0200, Lukas Kolbe wrote:
> > Am Montag, den 30.08.2010, 10:21 -0700 schrieb Greg KH:
> > > On Mon, Aug 30, 2010 at 09:46:36AM -0700, David Miller wrote:
> > > > From: Greg KH
> > > > Date: Mon, 30 Aug 2010 07:5
On Tue, Aug 31, 2010 at 10:16:56AM +0200, Lukas Kolbe wrote:
> Am Montag, den 30.08.2010, 10:21 -0700 schrieb Greg KH:
> > On Mon, Aug 30, 2010 at 09:46:36AM -0700, David Miller wrote:
> > > From: Greg KH
> > > Date: Mon, 30 Aug 2010 07:50:17 -0700
> > >
> > > > As I stated above, I need the ACK
> > Who's done the checks to find out any problems with these patches?
>
> I'll skim the changelogs in 2.6.3[345].x to see if there are any related
> patches.
This is all I could find in current 2.6.36-rc2 (via git log | grep,
minus rps/rfs patches). I don't know anything about these, but they
s
Am Montag, den 30.08.2010, 10:21 -0700 schrieb Greg KH:
> On Mon, Aug 30, 2010 at 09:46:36AM -0700, David Miller wrote:
> > From: Greg KH
> > Date: Mon, 30 Aug 2010 07:50:17 -0700
> >
> > > As I stated above, I need the ACK from David to be able to add these
> > > patches.
> > >
> > > David?
> >
On Mon, Aug 30, 2010 at 09:46:36AM -0700, David Miller wrote:
> From: Greg KH
> Date: Mon, 30 Aug 2010 07:50:17 -0700
>
> > As I stated above, I need the ACK from David to be able to add these
> > patches.
> >
> > David?
>
> I believe there were some regressions caused by these changes that wer
From: Greg KH
Date: Mon, 30 Aug 2010 07:50:17 -0700
> As I stated above, I need the ACK from David to be able to add these
> patches.
>
> David?
I believe there were some regressions caused by these changes that were
fixed later, a bit after those commites went into the tree.
I'm only conforta
On Mon, Aug 30, 2010 at 03:59:57PM +0200, Lukas Kolbe wrote:
> On Thu, 2010-08-26 at 09:32 +0200, Lukas Kolbe wrote:
>
> Hi,
>
> > > > I was finally able to identify the patch series that introduced the fix
> > > > (they were introduced to -stable in 2.6.33.2):
> > > >
> > > > cb63112 net: add _
On Thu, 2010-08-26 at 09:32 +0200, Lukas Kolbe wrote:
Hi,
> > > I was finally able to identify the patch series that introduced the fix
> > > (they were introduced to -stable in 2.6.33.2):
> > >
> > > cb63112 net: add __must_check to sk_add_backlog
> > > a12a9a2 net: backlog functions rename
> >
Hi all,
> > I was finally able to identify the patch series that introduced the fix
> > (they were introduced to -stable in 2.6.33.2):
> >
> > cb63112 net: add __must_check to sk_add_backlog
> > a12a9a2 net: backlog functions rename
> > 51c5db4 x25: use limited socket backlog
> > c531ab2 tipc: us
Hi all,
> > I was finally able to identify the patch series that introduced the fix
> > (they were introduced to -stable in 2.6.33.2):
> >
> > cb63112 net: add __must_check to sk_add_backlog
> > a12a9a2 net: backlog functions rename
> > 51c5db4 x25: use limited socket backlog
> > c531ab2 tipc: u
On Sun, Aug 15, 2010 at 09:37:34AM +0200, Lukas Kolbe wrote:
> Hi Ben, Greg,
>
> I was finally able to identify the patch series that introduced the fix
> (they were introduced to -stable in 2.6.33.2):
>
> cb63112 net: add __must_check to sk_add_backlog
> a12a9a2 net: backlog functions rename
> 5
Hi Ben, Greg,
I was finally able to identify the patch series that introduced the fix
(they were introduced to -stable in 2.6.33.2):
cb63112 net: add __must_check to sk_add_backlog
a12a9a2 net: backlog functions rename
51c5db4 x25: use limited socket backlog
c531ab2 tipc: use limited socket backl
Am Mittwoch, den 11.08.2010, 04:13 +0100 schrieb Ben Hutchings:
> On Mon, 2010-08-09 at 11:24 +0200, Lukas Kolbe wrote:
> > So, testing begins.
> >
> > First conclusion: not all traffic patterns produce the page allocation
> > failure. rdiff-backup only writing to an nfs-share does no harm;
> > rd
On Mon, 2010-08-09 at 11:24 +0200, Lukas Kolbe wrote:
> So, testing begins.
>
> First conclusion: not all traffic patterns produce the page allocation
> failure. rdiff-backup only writing to an nfs-share does no harm;
> rdiff-backup reading and writing (incremental backup) leads to (nearly
> immed
Okay, next round: This time, 2.6.32-19 and virtio in guest, 2.6.32-18 in
the host and sadly, it's not fixed:
[ 159.772700] rdiff-backup.bi: page allocation failure. order:0, mode:0x20
[ 159.772708] Pid: 2524, comm: rdiff-backup.bi Not tainted 2.6.32-5-amd64 #1
[ 159.772710] Call Trace:
[ 159.7
So, testing begins.
First conclusion: not all traffic patterns produce the page allocation
failure. rdiff-backup only writing to an nfs-share does no harm;
rdiff-backup reading and writing (incremental backup) leads to (nearly
immediate) error.
The nfs-share is always mounted with proto=tcp and n
Hi Ben,
Am Sonntag, den 08.08.2010, 03:36 +0100 schrieb Ben Hutchings:
> This is not the same bug as was originally reported, which is that
> virtio_net failed to retry refilling its RX buffer ring. That is
> definitely fixed. So I'm treating this as a new bug report, #592187.
Okay, thanks.
>
This is not the same bug as was originally reported, which is that
virtio_net failed to retry refilling its RX buffer ring. That is
definitely fixed. So I'm treating this as a new bug report, #592187.
On Sat, 2010-08-07 at 18:17 +0200, Lukas Kolbe wrote:
> Am Samstag, den 07.08.2010, 12:18 +0100
Am Samstag, den 07.08.2010, 12:18 +0100 schrieb Ben Hutchings:
> On Sat, 2010-08-07 at 11:21 +0200, Lukas Kolbe wrote:
> > Hi,
> >
> > I sent this earlier today but the bug was archived so it didn't appear
> > anywhere, hence the resend.
> >
> > I believe this issue is not fixed at all in 2.6.32-
On Sat, 2010-08-07 at 11:21 +0200, Lukas Kolbe wrote:
> Hi,
>
> I sent this earlier today but the bug was archived so it didn't appear
> anywhere, hence the resend.
>
> I believe this issue is not fixed at all in 2.6.32-18. We have seen this
> behaviour in various kvm guests using virtio_net with
24 matches
Mail list logo
