From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: netdev@vger.kernel.org
Subject: Re: Linux 3.6.x kernel crash in tcp_slow_start / bictcp_cong_avoid with wfica
Date: Wed, 23 Jan 2013 14:25:44 -0800 [thread overview]
Message-ID: <1358979944.12374.1143.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130123215151.GF8912@reaktio.net>
On Wed, 2013-01-23 at 23:51 +0200, Pasi Kärkkäinen wrote:
> On Wed, Jan 23, 2013 at 10:44:45PM +0100, Hannes Frederic Sowa wrote:
> > On Wed, Jan 23, 2013 at 06:12:38PM +0200, Pasi Kärkkäinen wrote:
> > > My laptop running Fedora 17 randomly crashes when using wfica (Citrix Receiver / ICA Client)
> > > proprietary closed source client for accessing remote desktop server.
> > > wfica is running as a normal user, so it shouldn't be able to cause a kernel crash.
> > >
> > > Crashes seem to happen most often when I use either wlan- or 3G mobile data Internet connection.
> > > These kernel crashes happen ramdomly, often 1-2 times a week.
> > > What usually happens is that I notice the Internet connection has died,
> > > and when I check the kernel dmesg I'm seeing the traceback.
> > > At this point I'm still able to use the gnome desktop for maybe 1-5 minutes,
> > > but applications start to fail one by one, and finally everything just halts
> > > and I need to power cycle the laptop.
> >
> > Would it be possible to capture a strace -e network, so we could see which
> > setsockopt combinations are being applied to the socket. Is capturing ss -ioem
> > in such moments still possible?
> >
>
> I don't think I'm able to strace or anything at that point..
> It took me at least 10 tries (=crashes) before I was able to "dmesg > log.txt" successfully ..
> (usually writing/redirecting to a file fails because the disk/fs is already unavailable..)
>
> I can always try though!
>
> Any other ideas?
Something sets tp->snd_cwnd to 0, and thats a bug.
next prev parent reply other threads:[~2013-01-23 22:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 16:12 Linux 3.6.x kernel crash in tcp_slow_start / bictcp_cong_avoid with wfica Pasi Kärkkäinen
2013-01-23 21:44 ` Hannes Frederic Sowa
2013-01-23 21:51 ` Pasi Kärkkäinen
2013-01-23 22:00 ` Hannes Frederic Sowa
2013-01-24 7:14 ` Pasi Kärkkäinen
2013-01-23 22:25 ` Eric Dumazet [this message]
2013-01-23 23:26 ` Stephen Hemminger
2013-01-23 23:41 ` Hannes Frederic Sowa
2013-01-23 23:47 ` Eric Dumazet
2013-01-24 6:59 ` Pasi Kärkkäinen
2013-01-24 13:51 ` Hannes Frederic Sowa
2013-02-02 3:51 ` Eric Dumazet
2013-02-02 14:28 ` Pasi Kärkkäinen
2013-02-02 15:14 ` [PATCH] tcp: tcp_process_frto() should not set snd_cwnd to 0 Eric Dumazet
2013-02-02 15:57 ` Neal Cardwell
2013-02-02 17:32 ` Eric Dumazet
2013-02-03 19:13 ` [PATCH] tcp: frto " Eric Dumazet
2013-02-03 21:01 ` David Miller
2013-02-04 12:14 ` Ilpo Järvinen
2013-02-04 15:07 ` Eric Dumazet
2013-02-05 19:44 ` Eric Dumazet
2013-02-05 19:49 ` Neal Cardwell
2013-02-06 20:55 ` David Miller
2013-02-06 21:13 ` Pasi Kärkkäinen
2013-02-06 21:19 ` David Miller
2013-02-06 21:21 ` Pasi Kärkkäinen
2013-02-02 15:23 ` [PATCH] tcp: fix an infinite loop in tcp_slow_start() Eric Dumazet
2013-02-03 21:01 ` David Miller
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=1358979944.12374.1143.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pasik@iki.fi \
/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