From: "Andri Möll" <andri@dot.ee>
To: linux-kernel@vger.kernel.org
Subject: CIFSd oops (Linux 2.6.22)
Date: Tue, 09 Oct 2007 12:59:56 +0300 [thread overview]
Message-ID: <470B511C.3070903@dot.ee> (raw)
Morning,
Lately I've been having issues with one of my machines' CIFS mounts. Failure
seems rather random to me, but most often occurs after adding new torrents to
Azureus.
I see no irregular messages on my Samba server machine, and other machines can
access the server fine.
Dmesg:
CIFS VFS: server not responding
CIFS VFS: No response to cmd 46 mid 11858
CIFS VFS: Send error in read = -11
CIFS VFS: Send error in Close = -9
CIFS VFS: Send error in Close = -9
...same line repeated for a while...
CIFS VFS: Send error in Close = -9
CIFS VFS: server not responding
CIFS VFS: No response to cmd 46 mid 17985
CIFS VFS: Send error in read = -11
CIFS VFS: Send error in Close = -9
CIFS VFS: Send error in Close = -9
...same line repeated for a while...
CIFS VFS: Send error in Close = -9
CIFS VFS: Send error in Close = -9
CIFS VFS: Send error in Close = -9
CIFS VFS: Invalid size SMB length 4 pdu_length 1412112
CIFS VFS: No response to cmd 46 mid 35861
CIFS VFS: Send error in read = -11
CIFS VFS: Send error in read = -9
CIFS VFS: Send error in Close = -9
CIFS VFS: Invalid size SMB length 4 pdu_length 4
BUG: unable to handle kernel NULL pointer dereference at virtual address 000000c8
printing eip:
c01e8f8c
*pde = 00000000
Oops: 0000 [#1]
SMP
Modules linked in: nvidia(P) ext3 jbd
CPU: 0
EIP: 0060:[<c01e8f8c>] Tainted: P VLI
EFLAGS: 00010246 (2.6.22-gentoo-r8 #1)
eax: 000000c0 ebx: f54f1a00 ecx: 00000077 edx: 00000002
esi: 00000000 edi: 00000004 ebp: 00000233 esp: f5649f5c
ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
Process cifsd (pid: 3991, ti=f5648000 task=f54ce510 task.ti=f5648000)
Stack: 00000233 c011b757 c0402f2e 00000000 00000000 c01eb797 c0402f2e 00000004
00000004 f54f1a00 ccb30000 db9b0000 c8069700 e5940480 d434c2c0 00000001
735c3e80 0000000d 00000000 00000000 f5649fc0 00000001 00000000 00000000
Call Trace:
[<c011b757>] <0> [<c01eb797>] <0> [<c0114fc4>] <0> [<c01eb473>] <0>
[<c0129feb>] <0> [<c0129fb3>] <0> [<c0104857>] <0> =======================
Code: 64 f6 05 20 aa 4f c0 01 74 19 8b 42 04 8b 12 c7 04 24 b5 20 40 c0 89 44 24
08 89 54 24 04 e8 b8 27 f3 ff 8b 43 30 ba 02 00 00 00 <8b> 48 08 ff 51 30 f6 05
20 aa 4f c0 01 74 1c 8b 43 30 8b 50 04
EIP: [<c01e8f8c>] SS:ESP 0068:f5649f5c
CIFS VFS: No response to cmd 47 mid 36433
CIFS VFS: Write2 ret -11, written = 0
CIFS VFS: Write2 ret -112, written = 0
CIFS VFS: Write2 ret -112, written = 0
CIFS VFS: Write2 ret -112, written = 0
CIFS VFS: Write2 ret -112, written = 0
CIFS VFS: Write2 ret -112, written = -290816
CIFS VFS: Write2 ret -112, written = 4
CIFS VFS: Write2 ret -112, written = -364646400
CIFS VFS: Write2 ret -112, written = -364646400
CIFS VFS: Write2 ret -112, written = -364646400
CIFS VFS: Error 0xffffff90 on cifs_get_inode_info in lookup of /foo
...the above message repeats for dozens of times for various open files...
Closing all applications (otherwise unmounting fails due to open files) and then
remounting seems to "solve" this.
If replying, please CC to me.
Thank you in advance for any suggestions and ideas!
Andri
reply other threads:[~2007-10-09 10:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=470B511C.3070903@dot.ee \
--to=andri@dot.ee \
--cc=linux-kernel@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