public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Steven French <sfrench@us.ibm.com>
Cc: linux-cifs-client@lists.samba.org, linux-kernel@vger.kernel.org,
	samba-technical@lists.samba.org, sfrench@samba.org
Subject: Re: [linux-cifs-client] 2.6.16-rc: CIFS reproducibly freezes the	computer
Date: Thu, 16 Feb 2006 13:07:23 +0100	[thread overview]
Message-ID: <20060216120723.GC3511@stusta.de> (raw)
In-Reply-To: <OFD6EC212C.9D3CD1CC-ON87257115.0057751D-86257115.0057E155@us.ibm.com>

On Tue, Feb 14, 2006 at 10:01:59AM -0600, Steven French wrote:
> 
> >...
> > It doesn't occur in 2.6.15.4, because with this kernel (and AFAIR also
> > with older kernels) my computer refuses to mount this share.
> >...

Is this issue I mentioned in my bug report expected, or could it be 
related to my problem?

>...
> Command 46 is an SMB Read.  IIRC send error in read -11 is EAGAIN which
> could
> indicate that the socket is congested and stayed congested but normally
> that would be accompanied by a "sends on socket stuck for x seconds"
> 
> Could you check /proc/fs/cifs/DebugData and see if the number of
> reconnections
> is non-zero (indicating that the tcp session to the server died).

I don't see this, do I need CONFIG_CIFS_STATS for seeing it?

> Any chance you could do an ethereal network trace of the failure (perhaps
> on the server, if the client is hanging) so we could see the
> last request (presumably a read) that the client sent (and whether the
> server responded).
> 
> Also is it possible to build your kernel with some of the debugging options
> turned on (e.g. "Debug Memory allocations" and "mutex debugging, deadlock
> detection" and
> "detect soft lockups") to see if we are overwritting memory and hitting an
> obscure
> deadlock.

Both are now on my TODO list.

> It would also be helpful, if the problem turns out to be non-obvious, to
> track this via a new bug # in bugzilla.samba.org

OK.

> Steve French

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      parent reply	other threads:[~2006-02-16 12:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14 13:50 2.6.16-rc: CIFS reproducibly freezes the computer Adrian Bunk
2006-02-14 15:00 ` Marc Koschewski
2006-02-14 15:59 ` Christian
2006-02-14 16:40   ` Marc Koschewski
2006-02-14 18:47     ` Ross Vandegrift
2006-02-15 13:35       ` Marc Koschewski
2006-02-15 16:47         ` Ross Vandegrift
2006-02-16 12:11         ` Adrian Bunk
2006-02-16 13:32           ` Marc Koschewski
2006-02-27  6:29       ` Adrian Bunk
2006-02-28  3:02         ` Ross Vandegrift
2006-02-14 18:12 ` Jan Engelhardt
2006-02-14 18:33   ` Lee Revell
     [not found] ` <OFD6EC212C.9D3CD1CC-ON87257115.0057751D-86257115.0057E155@us.ibm.com>
2006-02-16 12:07   ` Adrian Bunk [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=20060216120723.GC3511@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.org \
    --cc=sfrench@us.ibm.com \
    /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