From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, htmldeveloper@gmail.com
Subject: Re: [Bugme-new] [Bug 34182] New: Hard hang arising from TCP/IP related bug in 2.6.39-rc4
Date: Sun, 1 May 2011 10:42:12 -0700 [thread overview]
Message-ID: <20110501104212.273a9726.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-34182-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sun, 1 May 2011 17:32:07 GMT bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=34182
>
> Summary: Hard hang arising from TCP/IP related bug in
> 2.6.39-rc4
> Product: Networking
> Version: 2.5
> Kernel Version: 2.6.39-rc4
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: blocking
> Priority: P1
> Component: IPV4
> AssignedTo: shemminger@linux-foundation.org
> ReportedBy: htmldeveloper@gmail.com
> Regression: No
>
>
> Created an attachment (id=56082)
> --> (https://bugzilla.kernel.org/attachment.cgi?id=56082)
> kernel crash log via dmesg
>
> I did a git-update of linus git tree on 27 Apr 2011, built the new kernel
> image. Ever since using the new image, I have been *consistently* getting
> many crashes - especially whenever my google chrome is retoring all its
> previous session connection.
>
> Two crashes (entire system freezes) are shown in attachment. Ever since I
> have revert to previous version - as booting up twice and consistently twice it
> will fail within a few minutes after Chrome is used.
>
> v2.6.39-rc4-245-g4175242
>
> Previously working version: 2.6.38-rc2+. Did not test anything between
> 2.6.38-rc2+ and 2.6.39-rc3, and 2.6.39-rc3 failed for me in other ways as well.
>
> (http://bugzilla.kernel.org/show_bug.cgi?id=33272)
>
parent reply other threads:[~2011-05-01 17:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-34182-10286@https.bugzilla.kernel.org/>]
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=20110501104212.273a9726.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=htmldeveloper@gmail.com \
--cc=netdev@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).