Writing to Samba share causes crashes after a few 100 MB

If this is the right forum i don’t know, but I’m having a problem which crashes my home server when writing to Samba.

Googling and a quick search in this forum didn’t help me any further. Is there anyone with a clue what to do?

When I write several hundreds MB to my Samba share from a Windows machine the machine crashes (both with Win XP and Win 7). The problem is reproducible, although the precise moment (about 1 minute) or amount transfered data varies (about 300 to 800 MB). Small writes go well.

Reading about 5 GB from Samba to Windows went without a hitch.


  • Foxconn r10-s3 (includes Atom N330) with 2 GB RAM


  • OpenSuse 11.3
  • Samba 3.5.4-4.1-2382-SUSE-SL11.3
  • Kernel 2.6.34-12-desktop
   403.063581] BUG: unable to handle kernel paging request at 0000000000090029
   403.063598] IP: <ffffffff8149fc0c>] mutex_trylock+0x1c/0x50
   403.063616] PGD 7e4a0067 PUD 7df81067 PMD 0 
   403.063625] Oops: 0002 #1] PREEMPT SMP 
   403.063633] last sysfs file: /sys/devices/system/cpu/cpu3/cache/index2/shared_cpu_map
   403.063642] CPU 3 
   403.063645] Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd af_packet mperf fuse loop dm_mod snd_hda_codec_realtek snd_hda_intel snd_hda_codec sr_mod snd_hwdep iTCO_wdt cdrom ppdev sg snd_pcm serio_raw iTCO_vendor_support pcspkr parport_pc i2c_i801 usb_storage snd_timer 8139too parport snd soundcore snd_page_alloc ext4 jbd2 crc16 i915 drm_kms_helper drm i2c_algo_bit sd_mod button video intel_agp fan processor ata_generic ata_piix ahci libata scsi_mod thermal thermal_sys [last unloaded: preloadtrace]
   403.063730] Pid: 47, comm: kswapd0 Not tainted 2.6.34-12-desktop #1 45CS/45CSX/O.E.M
   403.063735] RIP: 0010:<ffffffff8149fc0c>]  <ffffffff8149fc0c>] mutex_trylock+0x1c/0x50
   403.063746] RSP: 0018:ffff88003764bc98  EFLAGS: 00010282
   403.063751] RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000002
   403.063756] RDX: 0000000000000000 RSI: 00000000000000d0 RDI: 0000000000090029
   403.063761] RBP: ffff88007d282000 R08: 000000000000000c R09: 0000000000000000
   403.063767] R10: 28f5c28f5c28f5c3 R11: 0000000000000001 R12: 0000000000090029
   403.063772] R13: 0000000000000000 R14: 0000000000074bf5 R15: 0000000000000080
   403.063778] FS:  0000000000000000(0000) GS:ffff880001f80000(0000) knlGS:0000000000000000
   403.063783] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
   403.063788] CR2: 0000000000090029 CR3: 0000000037f56000 CR4: 00000000000006e0
   403.063794] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
   403.063799] DR3: 00000000000Jul 21 20:57:41 atom kernel: imklog 5.4.0, log source = /proc/kmsg started.

So I have A Windows 7 machine along with a openSUSE 11.3 machine running Samba. I copied 1.3 GB of video files first from the Windows 7 machine to the openSUSE computer and then from openSUSE back to the Windows 7 computer without a problem. This brings to mind one of two issues. There may be a problem with your Samba setup or there may be a hardware or driver problem with your openSUSE computer. In your message it was hard to tell which computer you was saying crashed, openSUSE or Windows.

First I have a write up on how I setup Samba you might to look at:

Samba SMB file sharing in openSUSE 11.2

Next, you need to tell us more about your computer hardware. CPU, speed, memory, video, disk space, 64 or 32 bit. Anything that might help on the setup of your PC.

Thank You,

The machine itself is working 24x7 and stable. Samba on it’s own is working well. As long if the number of writes using SMB is limited everything seems to be fine.
I think it might be a hardware, driver or maybe even a kernel issue. Until now the problem only occurs when I use Samba.

In your message it was hard to tell which computer you was saying crashed, openSUSE or Windows.

OpenSUSE crashes. :frowning:

Next, you need to tell us more about your computer hardware. CPU, speed, memory, video, disk space, 64 or 32 bit. Anything that might help on the setup of your PC.

My pc/server is a Foxconn R10-S3 barebone with everything on board. Commercial specs. Basics:
CPU Intel(R) Atom™ CPU 330 @ 1.60GHz
Video Intel 945G Chipset
LAN Realtek RTL-8139/8139C/8139C+ (kernel module 8139too)
Audio Intel 82801G (ICH7 Family) High Definition Audio Controller

The machine is further equipped with 2 GB RAM, 1 TB SAMSUNG HD103SJ, LG DVD GH22NS50

Fresh install (brand new HD) of OpenSUSE 11.3, 64 Bit, installed from DVD.

Diskspace (Dutch labels)

# df -h
Bestandssysteem       Grtte Gebr Besch Geb% Aangekoppeld op
/dev/sda2              20G  4,9G   14G  27% /
devtmpfs              999M  228K  999M   1% /dev
tmpfs                1000M  4,0K 1000M   1% /dev/shm
/dev/sda3             896G  6,8G  844G   1% /home

Already tested:

  • Switching hyper threading on/off in bios makes no difference.
  • Opening a smb-connection from Dolphin and pulling the files from the Win 7 machine made the linux machine also crash after (approx) 280 files / 1.1 GB.
  • Bios reset to factory defaults / recommended settings

I’ve made a complete diagnostic dump with Yast but over 400 K a little overdone to post overhere.

So this is an Atom CPU and you have 2 GB of memory and running 64 bit openSUSE. I am no expert on the Atom, but I still think it is a hardware issue of some sort. Have you considered adding in more memory (2 GB more) or dropping down to a 32 bit install? It is my opinion, which not everyone agrees with, that you need 4 GB or more for 64 bit operation. Now does this apply to an Atom CPU? I do not know that. One would need to look at your memory usage when the system locks up and also to see if the swap is being used. You did not indicate how large a swap partition was installed? I would wonder just what the video system is doing during the lock ups? Should a more basic video sub-system be installed (like vesa)? I would be lying if I did not tell you I am guessing here, but these are the issues I would look at.

Thank You,

Please post here the contents of your samba configuration file, smb.conf, located at /etc/samba/smb.conf

Also, what do you mean “crashes”, a bit more detail please.

After a short vacation and several additional tests I think the problem is caused by faulty hardware.

I installed the following OpenSUSE releases and was able to reproduce the crashes on the following releases (out of the box installation, Samba configured using Yast):
10.2 64-bit,
10.3 64-bit
10.3 32-bit

Replacing the (brand new) hard disk with an other hard disk (Western Digital WD10EADS) makes no difference. The problem reoccurs.

I also installed a second networkcard (Asus, NX1101 with an IP1000A chip) which didn’t help either. This card (not the machine!) crashes silently without any traces in the logs after a few 100 MB IO.

A test with Memtest showed no errors.
Leaving the machine running the whole day for several days goes well. Browsing and watching Youtube using Firefox goes perfect.

Today I activated vsftpd and after moving a couple of MP3’s from my home-folder to /srv/ftp the machine crashed again.

So I think has something to do with the hardware not able to handle “heavy” IO.
I will RMA the machine because it’s capable of performing the job it was inteded for. :’(

Suggestions are still welcome, but I think it will be better to close this thread.