From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: Suresh Jayaraman <sjayaraman@suse.com>,
linux-kernel@vger.kernel.org,
linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: 3.1-rc4: CIFS VFS: Received no data, expecting 4
Date: Wed, 21 Sep 2011 07:56:57 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1109210756390.31360@p34.internal.lan> (raw)
In-Reply-To: <20110921075730.74c3b512@corrin.poochiereds.net>
On Wed, 21 Sep 2011, Jeff Layton wrote:
> On Wed, 21 Sep 2011 16:54:08 +0530
> Suresh Jayaraman <sjayaraman@suse.com> wrote:
>
>> Adding linux-cifs@vger.kernel.org to Cc.
>>
>> On 09/18/2011 10:29 PM, Justin Piszcz wrote:
>>> Hello,
>>>
>>> What does this mean and why does it occur?
>>
>> This error seems to occur when we try to read from a socket and actually
>> read no data. Not sure when this would occur.
>>
>
> It would be nice to know what was returned by kernel_recvmsg here. Was
> it "0" or an error code of some kind?
Hi,
It seemed to start like that:
Sep 18 12:02:52 p34 kernel: [ 71.039405] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Sep 18 12:02:52 p34 kernel: [ 71.039970] NFSD: starting 90-second grace period
Sep 18 12:17:06 p34 kernel: [ 923.377483] CIFS VFS: Received no data, expecting 4
Sep 18 12:17:23 p34 kernel: [ 940.991731] [drm] nouveau 0000:04:00.0: Setting dpms mode 3 on tmds encoder (output 1)
Sep 18 12:18:23 p34 kernel: [ 1000.699094] CIFS VFS: Received no data, expecting 4
Sep 18 12:18:53 p34 kernel: [ 1030.668222] CIFS VFS: Received no data, expecting 4
Sep 18 12:19:23 p34 kernel: [ 1060.637386] CIFS VFS: Received no data, expecting 4
Sep 18 12:19:53 p34 kernel: [ 1090.606501] CIFS VFS: Received no data, expecting 4
Sep 18 12:20:23 p34 kernel: [ 1120.575675] CIFS VFS: Received no data, expecting 4
Sep 18 12:20:53 p34 kernel: [ 1150.544783] CIFS VFS: Received no data, expecting 4
Sep 18 12:21:23 p34 kernel: [ 1180.513925] CIFS VFS: Received no data, expecting 4
Sep 18 12:21:53 p34 kernel: [ 1210.483044] CIFS VFS: Received no data, expecting 4
Sep 18 12:22:23 p34 kernel: [ 1240.452187] CIFS VFS: Received no data, expecting 4
Sep 18 12:22:53 p34 kernel: [ 1270.421345] CIFS VFS: Received no data, expecting 4
Sep 18 12:23:23 p34 kernel: [ 1300.390432] CIFS VFS: Received no data, expecting 4
Sep 18 12:23:53 p34 kernel: [ 1330.359595] CIFS VFS: Received no data, expecting 4
Sep 18 12:24:23 p34 kernel: [ 1360.328755] CIFS VFS: Received no data, expecting 4
Sep 18 12:24:53 p34 kernel: [ 1390.283901] CIFS VFS: Received no data, expecting 4
Sep 18 12:25:23 p34 kernel: [ 1420.249492] CIFS VFS: Received no data, expecting 4
Sep 18 12:25:53 p34 kernel: [ 1450.218690] CIFS VFS: Received no data, expecting 4
Sep 18 12:26:23 p34 kernel: [ 1480.187842] CIFS VFS: Received no data, expecting 4
Sep 18 12:26:53 p34 kernel: [ 1510.156925] CIFS VFS: Received no data, expecting 4
Sep 18 12:27:23 p34 kernel: [ 1540.126080] CIFS VFS: Received no data, expecting 4
Sep 18 12:27:54 p34 kernel: [ 1570.095264] CIFS VFS: Received no data, expecting 4
Justin.
next prev parent reply other threads:[~2011-09-21 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 16:59 Justin Piszcz
2011-09-21 11:24 ` Suresh Jayaraman
2011-09-21 11:57 ` Jeff Layton
2011-09-21 11:56 ` Justin Piszcz [this message]
2011-09-21 13:15 ` Jeff Layton
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=alpine.DEB.2.02.1109210756390.31360@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=jlayton@poochiereds.net \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjayaraman@suse.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
all inboxes | Powered by JetHome®