From: Adrian Bunk <bunk@stusta.de>
To: sfrench@samba.org
Cc: linux-cifs-client@lists.samba.org,
samba-technical@lists.samba.org, linux-kernel@vger.kernel.org
Subject: 2.6.16-rc: CIFS reproducibly freezes the computer
Date: Tue, 14 Feb 2006 14:50:16 +0100 [thread overview]
Message-ID: <20060214135016.GC10701@stusta.de> (raw)
Hi Steve,
I do obvserve the following on my i386 computer:
I'm connecting to a Samba server.
Copying data to the server works without any problems.
When trying to copy some GB from the server, my computer completely
frezzes after some 100 MB. This is reproducible.
"Complete freeze" is:
- no reaction to any input, even when I was in the console the magic
SysRq key is not working
- if XMMS was playing, the approx. half a second of the song that was
playing at the time when it happened is played in an endless loop by
the sound chip
I once switched to the console waiting for the crash, and I saw the
following messages:
CIFS VFS: No response to cmd 46 mid 5907
CIFS VFS: Send error in read = -11
There are no other CIFS messages in my logs, and the messages above
didn't make it into the logs (there's nothing recorded in the logs at
the time of the crashes).
I tried kernel 2.6.16-rc2 and 2.6.16-rc3.
CIFS options in my kernel:
CONFIG_CIFS=y
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
I'm mounting with (slightly anonymized):
mount -t cifs -o user="foo",ip=11.22.33.44 //DAT/bar bar
I'm using the smbfs 3.0.21a-4 package from Debian.
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.
Mounting the same share with smbfs works without big problems (on some
rare occassions the connection might become stale and I have to umount
and remount the share, but this is rare and it never affects the
stability of my computer).
I'm using an e100 network card with a 10 MBit/s connection.
Any other information I can provide for helping to debug this problem?
TIA
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
next reply other threads:[~2006-02-14 13:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 13:50 Adrian Bunk [this message]
2006-02-14 15:00 ` 2.6.16-rc: CIFS reproducibly freezes the computer 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 ` [linux-cifs-client] " Adrian Bunk
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=20060214135016.GC10701@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 \
/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