lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 11 Nov 2009 15:19:54 -0500
From:	Caleb Cushing <>
To:	Frans Pop <>
Subject: Re: large packet loss take2 2.6.31.x

not to be impatient or ungrateful, but has anyone had time to look at
this? will I be able to upgrade to 31.6? will 32.0 work?

On Sat, Oct 31, 2009 at 1:44 PM, Frans Pop <> wrote:
> Adding netdev in CC. Original message + attachments follow.
> =========
> so ever since arch rolled out 2.6.31.x I've been having problems with
> my network (again) where I've been losing a large amount of packets
> (just testing with mtr somewhere between 30/50%). first I figured it
> was the same problem as I had in 2.6.30.x (and maybe it is?) but that
> appeared to get fixed. when I started bisecting the bug wasn't
> apparent in but I knew for sure it was in .5 (I couldn't
> remember if I had noticed it again in .3)
> I'm attaching the bisection log and a 'good' dmesg output.
> c9fb3ded7a8a6769f3bcb3ef3d9aed61d3e376a9 is the first bad commit
> I'm not going to pretend to understand why this patch is breaking my
> networking but between bisection and testing it appears to be... I've
> never bisected before and I'm definitely not a kernel hacker (I can
> barely read C).
> I should also note that the wireshark dump here
> is related to this.
> and if it's not the same bug then possibly a new one should be opened.
> P.S. I'm not subscribed to the list please CC me
> Caleb Cushing

Caleb Cushing
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists