netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@kvack.org>
To: Eric Dumazet <erdnetdev@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: 3.6.10 tcp crash - net/ipv4/tcp.c:1667 & tcp.c:1655
Date: Mon, 17 Dec 2012 14:52:13 -0500	[thread overview]
Message-ID: <20121217195212.GI22452@kvack.org> (raw)
In-Reply-To: <1355772853.9380.10.camel@edumazet-glaptop>

On Mon, Dec 17, 2012 at 11:34:13AM -0800, Eric Dumazet wrote:
> On Mon, 2012-12-17 at 12:41 -0500, Benjamin LaHaise wrote:
> > Hi folks,
> > 
> > I just hit the following crash with Fedora's 3.6.10-2.fc17 kernel.  I don't 
> > have time to debug this myself at the moment, but can certainly test patches 
> > or provide more info as needed.  I wasn't doing anything unusual at the time, 
> > just reading email/web browsing.  I believe the network driver in use was 
> > ipheth for tethering to an iPhone 4S over USB (the other driver being used 
> > intermittently on this laptop is iwlwifi).  Any ideas?
> 
> I see nothing really wrong on ipheth side.
> 
> I would be nice to know which driver is really in use when you have a
> panic, as its probably a driver issue.

I double checked the logs, and the wifi was disabled at the time (~30 
minutes beforehand), so it had to be ipheth.  The warnings were the last 
thing that made it to disk before the machine hung hard, so there may have 
been a more serious crash after the warning that did not get logged.

One thing I have observed with tethering is that the MTU handling is munged 
by the network in interesting ways.  Although the device claims to be 
ethernet with a 1500 byte MTU, a 'ping -s' works only up to 996 (with no 
effect trying the various -M options).  A number of website are broken by 
this, as the network doesn't seem to send ICMP frag needed errors to my 
tethered host (but I haven't traced this behaviour from both ends yet).  
Things do work for 1500 byte packets to the gateway IP, but that seems 
to be local to the phone.

		-ben
-- 
"Thought is the essence of where you are now."

      reply	other threads:[~2012-12-17 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 17:41 3.6.10 tcp crash - net/ipv4/tcp.c:1667 & tcp.c:1655 Benjamin LaHaise
2012-12-17 19:34 ` Eric Dumazet
2012-12-17 19:52   ` Benjamin LaHaise [this message]

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=20121217195212.GI22452@kvack.org \
    --to=bcrl@kvack.org \
    --cc=erdnetdev@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).