LKML Archive on
help / color / mirror / Atom feed
From: Eric Lacombe <>
To: Steven French <>
Cc: linux-kernel <>
Subject: Re: Linux Freeze with CIFS mount
Date: Wed, 31 Jan 2007 15:51:08 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

First of all, thank you for your answer.

On Wednesday 31 January 2007 04:51:35 Steven French wrote:
> The cifs entries in the dmesg log do not indicate any errors, much less
> show the cause of this
> particular problem.


> The repeated entry:
>         CIFS VFS: Send error in SETFSUnixInfo = -5
> is expected on connection to certain older versions of Samba servers (or
> other servers that
> only partially support the current CIFS Unix Extensions).  It is harmless.
> It would be useful to know (e.g. if it is possible to trace the network
> traffic on the server side on your NAS box) whether
> any network traffic from the client is being sent when (or just before)
> the hang occurs.

Unfortunately, I can't easily do stuff on the NAS box other than what it was 
provided for. (An interesting project exists about the first version of the 
Maxtor Shared Storage : openmss, but this one is based on a totally different 

> It is possible that the restarting of the NAS box allows reconnection of
> the smb/cifs session to proceed
> which presumably could be hanging or looping in the network adapter
> driver, the tcp stack or cifs on
> the client, but it is hard to tell without more information.   I don't
> know much about either of the
> GigE drivers loaded on your system to determine if there is an easy way to
> tell their state.

The network device I use is :
"D-Link System Inc DGE-528T Gigabit Ethernet Adapter (rev 10)",

and the driver used is the one for "Realtek 8169 PCI Gigabit Ethernet adapter" 
(in the which is the only one that recognizes this device.

That problem also remind me that when I compiled this driver without 
the "CONFIG_NET_ETHERNET" (in the section "Ethernet (10 or 100Mbit)"), I have 
really poor performance with the net device. Maybe it is related, or not ;)

If it gives you more ideas ?
Maybe it could be interesting to know about the r8169 maintainer, but I dont 
know who he is.

> There are various ways to analyze system hangs including (at least in some
> cases) getting a system dump which
> can be used to isolate the failing location - hopefully

Could you give me some worthful URLs ?

Thank you again.


> wrote on 01/30/2007 06:37:48 AM:


> Steve French
> Senior Software Engineer
> Linux Technology Center - IBM Austin
> phone: 512-838-2294
> email: sfrench at-sign us dot ibm dot com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to
> More majordomo info at
> Please read the FAQ at

  reply	other threads:[~2007-01-31 14:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 12:37 Eric Lacombe
2007-01-31  3:51 ` Steven French
2007-01-31 14:51   ` Eric Lacombe [this message]
2007-02-13 13:52   ` Linux maybe a bug inside the r8169 network driver (was Re: Linux Freeze with CIFS mount) Eric Lacombe
2007-02-13 20:30     ` Francois Romieu
2007-02-14 10:49       ` Eric Lacombe
2007-03-05 21:19         ` Eric Lacombe
2007-03-05 22:16           ` Francois Romieu
2007-03-06 16:42             ` Eric Lacombe
2007-03-07 19:48               ` Eric Lacombe
2007-03-09  9:30                 ` Eric Lacombe

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Linux Freeze with CIFS mount' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).