Bug 4821 - Heavy load on smbfs gives smb_add_request: request timed out! and machine hangs.
Summary: Heavy load on smbfs gives smb_add_request: request timed out! and machine hangs.
Status: REJECTED WILL_NOT_FIX
Alias: None
Product: File System
Classification: Unclassified
Component: Samba/SMB (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: fs_samba-smb
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-30 07:36 UTC by Johan Bengtsson
Modified: 2007-07-10 19:18 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.11.8
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Johan Bengtsson 2005-06-30 07:36:39 UTC
[1.] One line summary of the problem:    
Heavy load on smbfs gives smb_add_request: request timed out! and machine hangs.



[2.] Full description of the problem/report:
I have a computer responsible for backup of several other computers over the
network. The other computers are running a mix of windows and linux but all
of them have their files mounted via smbfs. There are several different
backups and occasionally they run simultaneously. This usually result in the
machine doing the backup hangs.

This looks a lot like a couple of previous problems with smbfs (see section
at the bottom for futher notes about this).


[3.] Keywords (i.e., modules, networking, kernel):
smbfs
heavy load
simulateously
parallel
smb_add_request: request [xxxxxxxx, mid=yyyy] timed out!
Input/output error



[4.] Kernel version (from /proc/version):
Linux version 2.6.11.8 (root@tor) (gcc version 3.3.5 (Debian 1:3.3.5-12))
#6 Fri Jun 10 16:48:41 CEST 2005



[5.] Output of Oops..
No Oops.. message, machine hangs - no crash.

/var/log/messages:
This is the contents from the restart, during the full attempt and up to
the point where the machine hangs. I thought of trimming it, but decided
against it in case I would happen to cut out something actually useful.

Jun 29 15:53:02 tor syslogd 1.4.1#17: restart.
Jun 29 15:53:03 tor kernel: klogd 1.4.1#17, log source = /proc/kmsg started.
Jun 29 15:53:03 tor kernel: Cannot find map file.
Jun 29 15:53:03 tor kernel: No module symbols loaded - kernel modules not 
enabled. 
Jun 29 15:53:03 tor kernel: Linux version 2.6.11.8 (root@tor) (gcc version 
3.3.5 (Debian 1:3.3.5-12)) #6 Fri Jun 10 16:48:41 CEST 2005
Jun 29 15:53:03 tor kernel: BIOS-provided physical RAM map:
Jun 29 15:53:03 tor kernel:  BIOS-e820: 0000000000000000 - 000000000009e800 
(usable)
Jun 29 15:53:03 tor kernel:  BIOS-e820: 000000000009e800 - 00000000000a0000 
(reserved)
Jun 29 15:53:03 tor kernel:  BIOS-e820: 00000000000f0000 - 0000000000100000 
(reserved)
Jun 29 15:53:03 tor kernel:  BIOS-e820: 0000000000100000 - 0000000027fec000 
(usable)
Jun 29 15:53:03 tor kernel:  BIOS-e820: 0000000027fec000 - 0000000027fef000 
(ACPI data)
Jun 29 15:53:03 tor kernel:  BIOS-e820: 0000000027fef000 - 0000000027fff000 
(reserved)
Jun 29 15:53:03 tor kernel:  BIOS-e820: 0000000027fff000 - 0000000028000000 
(ACPI NVS)
Jun 29 15:53:03 tor kernel:  BIOS-e820: 00000000ffff0000 - 0000000100000000 
(reserved)
Jun 29 15:53:03 tor kernel: 639MB LOWMEM available.
Jun 29 15:53:03 tor kernel: DMI 2.3 present.
Jun 29 15:53:03 tor kernel: Allocating PCI resources starting at 28000000 (gap: 
28000000:d7ff0000)
Jun 29 15:53:03 tor kernel: Built 1 zonelists
Jun 29 15:53:03 tor kernel: Kernel command line: auto BOOT_IMAGE=Linux ro 
root=901
Jun 29 15:53:03 tor kernel: Initializing CPU#0
Jun 29 15:53:03 tor kernel: PID hash table entries: 4096 (order: 12, 65536 
bytes)
Jun 29 15:53:03 tor kernel: Detected 908.111 MHz processor.
Jun 29 15:53:03 tor kernel: Using tsc for high-res timesource
Jun 29 15:53:03 tor kernel: Console: colour VGA+ 80x50
Jun 29 15:53:03 tor kernel: Dentry cache hash table entries: 131072 (order: 7, 
524288 bytes)
Jun 29 15:53:03 tor kernel: Inode-cache hash table entries: 65536 (order: 6, 
262144 bytes)
Jun 29 15:53:03 tor kernel: Memory: 645704k/655280k available (1916k kernel 
code, 9072k reserved, 643k data, 380k init, 0k highmem)
Jun 29 15:53:03 tor kernel: Checking if this processor honours the WP bit even 
in supervisor mode... Ok.
Jun 29 15:53:03 tor kernel: Mount-cache hash table entries: 512 (order: 0, 4096 
bytes)
Jun 29 15:53:03 tor kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K 
(64 bytes/line)
Jun 29 15:53:03 tor kernel: CPU: L2 Cache: 256K (64 bytes/line)
Jun 29 15:53:03 tor kernel: CPU: AMD Athlon(tm) Processor stepping 02
Jun 29 15:53:03 tor kernel: Enabling fast FPU save and restore... done.
Jun 29 15:53:03 tor kernel: Checking 'hlt' instruction... OK.
Jun 29 15:53:03 tor kernel: ACPI: setting ELCR to 0200 (from 0ca0)
Jun 29 15:53:03 tor kernel: NET: Registered protocol family 16
Jun 29 15:53:03 tor kernel: PCI: PCI BIOS revision 2.10 entry at 0xf10f0, last 
bus=1
Jun 29 15:53:03 tor kernel: PCI: Using configuration type 1
Jun 29 15:53:03 tor kernel: ACPI: Subsystem revision 20050211
Jun 29 15:53:03 tor kernel: ACPI: Interpreter enabled
Jun 29 15:53:03 tor kernel: ACPI: Using PIC for interrupt routing
Jun 29 15:53:03 tor kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 
10 *11 12 14 15)
Jun 29 15:53:03 tor kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 
*10 11 12 14 15)
Jun 29 15:53:03 tor kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *7 9 
10 11 12 14 15)
Jun 29 15:53:03 tor kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 
10 11 12 14 15)
Jun 29 15:53:03 tor kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
Jun 29 15:53:03 tor kernel: PCI: Probing PCI hardware (bus 00)
Jun 29 15:53:03 tor kernel: PCI: Via IRQ fixup
Jun 29 15:53:03 tor kernel: Disabling VIA memory write queue (PCI ID 0305, rev 
02): [55] 81 & 1f -> 01
Jun 29 15:53:03 tor kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
Jun 29 15:53:03 tor kernel: SCSI subsystem initialized
Jun 29 15:53:03 tor kernel: PCI: Using ACPI for IRQ routing
Jun 29 15:53:03 tor kernel: ** PCI interrupts are no longer routed 
automatically.  If this
Jun 29 15:53:03 tor kernel: ** causes a device to stop working, it is probably 
because the
Jun 29 15:53:03 tor kernel: ** driver failed to call pci_enable_device().  As a 
temporary
Jun 29 15:53:03 tor kernel: ** workaround, the "pci=routeirq" argument restores 
the old
Jun 29 15:53:03 tor kernel: ** behavior.  If this argument makes the device 
work again,
Jun 29 15:53:03 tor kernel: ** please email the output of "lspci" to 
bjorn.helgaas@hp.com
Jun 29 15:53:03 tor kernel: ** so I can fix the driver.
Jun 29 15:53:03 tor kernel: Simple Boot Flag at 0x3a set to 0x1
Jun 29 15:53:03 tor kernel: Initializing Cryptographic API
Jun 29 15:53:03 tor kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Jun 29 15:53:03 tor kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jun 29 15:53:03 tor kernel: io scheduler noop registered
Jun 29 15:53:03 tor kernel: io scheduler anticipatory registered
Jun 29 15:53:03 tor kernel: io scheduler deadline registered
Jun 29 15:53:03 tor kernel: io scheduler cfq registered
Jun 29 15:53:03 tor kernel: Floppy drive(s): fd0 is 1.44M
Jun 29 15:53:03 tor kernel: FDC 0 is a post-1991 82077
Jun 29 15:53:03 tor kernel: Intel(R) PRO/1000 Network Driver - version 5.6.10.1-
k2-NAPI
Jun 29 15:53:03 tor kernel: Copyright (c) 1999-2004 Intel Corporation.
Jun 29 15:53:03 tor kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
Jun 29 15:53:03 tor kernel: PCI: setting IRQ 5 as level-triggered
Jun 29 15:53:03 tor kernel: ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 5 
(level, low) -> IRQ 5
Jun 29 15:53:03 tor kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network 
Connection
Jun 29 15:53:03 tor kernel: Uniform Multi-Platform E-IDE driver Revision: 
7.00alpha2
Jun 29 15:53:03 tor kernel: ide: Assuming 33MHz system bus speed for PIO modes; 
override with idebus=xx
Jun 29 15:53:03 tor kernel: PDC20269: IDE controller at PCI slot 0000:00:0b.0
Jun 29 15:53:03 tor kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
Jun 29 15:53:03 tor kernel: PCI: setting IRQ 10 as level-triggered
Jun 29 15:53:03 tor kernel: ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 10 
(level, low) -> IRQ 10
Jun 29 15:53:03 tor kernel: PDC20269: chipset revision 2
Jun 29 15:53:03 tor kernel: PDC20269: 100%% native mode on irq 10
Jun 29 15:53:03 tor kernel:     ide2: BM-DMA at 0x8400-0x8407, BIOS settings: 
hde:pio, hdf:pio
Jun 29 15:53:03 tor kernel:     ide3: BM-DMA at 0x8408-0x840f, BIOS settings: 
hdg:pio, hdh:pio
Jun 29 15:53:03 tor kernel: hde: Maxtor 4G120J6, ATA DISK drive
Jun 29 15:53:03 tor kernel: hdf: Maxtor 4G160J8, ATA DISK drive
Jun 29 15:53:03 tor kernel: ide2 at 0x9800-0x9807,0x9402 on irq 10
Jun 29 15:53:03 tor kernel: hda: IRQ probe failed (0xf9fa)
Jun 29 15:53:03 tor kernel: hda: IRQ probe failed (0xf9fa)
Jun 29 15:53:03 tor kernel: hda: no response (status = 0x0a), resetting drive
Jun 29 15:53:03 tor kernel: hda: IRQ probe failed (0xf9fa)
Jun 29 15:53:03 tor kernel: hda: no response (status = 0x0a)
Jun 29 15:53:03 tor kernel: hdb: IRQ probe failed (0xf9fa)
Jun 29 15:53:03 tor kernel: hdb: IRQ probe failed (0xf9fa)
Jun 29 15:53:03 tor kernel: hdb: no response (status = 0x0a), resetting drive
Jun 29 15:53:03 tor kernel: hdb: IRQ probe failed (0xf9fa)
Jun 29 15:53:03 tor kernel: hdb: no response (status = 0x0a)
Jun 29 15:53:03 tor kernel: hde: max request size: 1024KiB
Jun 29 15:53:03 tor kernel: hde: 240121728 sectors (122942 MB) w/2048KiB Cache, 
CHS=16383/255/63, UDMA(133)
Jun 29 15:53:03 tor kernel:  hde: unknown partition table
Jun 29 15:53:03 tor kernel: hdf: max request size: 1024KiB
Jun 29 15:53:03 tor kernel: hdf: 320173056 sectors (163928 MB) w/2048KiB Cache, 
CHS=19929/255/63, UDMA(133)
Jun 29 15:53:03 tor kernel:  hdf: hdf1
Jun 29 15:53:03 tor kernel: ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 5 
(level, low) -> IRQ 5
Jun 29 15:53:03 tor kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 7
Jun 29 15:53:03 tor kernel: PCI: setting IRQ 7 as level-triggered
Jun 29 15:53:03 tor kernel: ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 7 
(level, low) -> IRQ 7
Jun 29 15:53:03 tor kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA 
DRIVER, Rev 6.2.36
Jun 29 15:53:03 tor kernel:         <Adaptec 2940 Ultra SCSI adapter>
Jun 29 15:53:03 tor kernel:         aic7880: Ultra Wide Channel A, SCSI Id=7, 
16/253 SCBs
Jun 29 15:53:03 tor kernel: 
Jun 29 15:53:03 tor kernel: (scsi0:A:0): 40.000MB/s transfers (20.000MHz, 
offset 8, 16bit)
Jun 29 15:53:03 tor kernel:   Vendor: QUANTUM   Model: QM318000TD-SW     Rev: 
N1B0
Jun 29 15:53:03 tor kernel:   Type:   Direct-Access                      ANSI 
SCSI revision: 02
Jun 29 15:53:03 tor kernel: scsi0:A:0:0: Tagged Queuing enabled.  Depth 253
Jun 29 15:53:03 tor kernel: (scsi0:A:1): 40.000MB/s transfers (20.000MHz, 
offset 8, 16bit)
Jun 29 15:53:03 tor kernel:   Vendor: IBM       Model: IC35L036UWDY10-0  Rev: 
S29A
Jun 29 15:53:03 tor kernel:   Type:   Direct-Access                      ANSI 
SCSI revision: 03
Jun 29 15:53:03 tor kernel: scsi0:A:1:0: Tagged Queuing enabled.  Depth 253
Jun 29 15:53:03 tor kernel: (scsi0:A:2): 40.000MB/s transfers (20.000MHz, 
offset 8, 16bit)
Jun 29 15:53:03 tor kernel:   Vendor: IBM       Model: DDYS-T18350N      Rev: 
S96H
Jun 29 15:53:03 tor kernel:   Type:   Direct-Access                      ANSI 
SCSI revision: 03
Jun 29 15:53:03 tor kernel: scsi0:A:2:0: Tagged Queuing enabled.  Depth 253
Jun 29 15:53:03 tor kernel: scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA 
DRIVER, Rev 6.2.36
Jun 29 15:53:03 tor kernel:         <Adaptec 2940 Ultra SCSI adapter>
Jun 29 15:53:03 tor kernel:         aic7880: Ultra Wide Channel A, SCSI Id=7, 
16/253 SCBs
Jun 29 15:53:03 tor kernel: 
Jun 29 15:53:03 tor kernel: (scsi1:A:3): 40.000MB/s transfers (20.000MHz, 
offset 8, 16bit)
Jun 29 15:53:03 tor kernel:   Vendor: SONY      Model: TSL-11000         Rev: 
L0u6
Jun 29 15:53:03 tor kernel:   Type:   Sequential-Access                  ANSI 
SCSI revision: 02
Jun 29 15:53:03 tor kernel:   Vendor: SONY      Model: TSL-11000         Rev: 
L0u6
Jun 29 15:53:03 tor kernel:   Type:   Medium Changer                     ANSI 
SCSI revision: 02
Jun 29 15:53:03 tor kernel: st: Version 20041025, fixed bufsize 32768, s/g segs 
256
Jun 29 15:53:03 tor kernel: Attached scsi tape st0 at scsi1, channel 0, id 3, 
lun 0
Jun 29 15:53:03 tor kernel: st0: try direct i/o: yes (alignment 512 B), max 
page reachable by HBA 1048575
Jun 29 15:53:03 tor kernel: SCSI device sda: 35566499 512-byte hdwr sectors 
(18210 MB)
Jun 29 15:53:03 tor kernel: SCSI device sda: drive cache: write back
Jun 29 15:53:03 tor kernel: SCSI device sda: 35566499 512-byte hdwr sectors 
(18210 MB)
Jun 29 15:53:03 tor kernel: SCSI device sda: drive cache: write back
Jun 29 15:53:03 tor kernel:  sda: sda1 sda2 sda3 sda4
Jun 29 15:53:03 tor kernel: Attached scsi disk sda at scsi0, channel 0, id 0, 
lun 0
Jun 29 15:53:03 tor kernel: SCSI device sdb: 71687340 512-byte hdwr sectors 
(36704 MB)
Jun 29 15:53:03 tor kernel: SCSI device sdb: drive cache: write back
Jun 29 15:53:03 tor kernel: SCSI device sdb: 71687340 512-byte hdwr sectors 
(36704 MB)
Jun 29 15:53:03 tor kernel: SCSI device sdb: drive cache: write back
Jun 29 15:53:03 tor kernel:  sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 >
Jun 29 15:53:03 tor kernel: Attached scsi disk sdb at scsi0, channel 0, id 1, 
lun 0
Jun 29 15:53:03 tor kernel: SCSI device sdc: 35843670 512-byte hdwr sectors 
(18352 MB)
Jun 29 15:53:03 tor kernel: SCSI device sdc: drive cache: write back
Jun 29 15:53:03 tor kernel: SCSI device sdc: 35843670 512-byte hdwr sectors 
(18352 MB)
Jun 29 15:53:03 tor kernel: SCSI device sdc: drive cache: write back
Jun 29 15:53:03 tor kernel:  sdc: sdc1 sdc2 sdc3 sdc4
Jun 29 15:53:03 tor kernel: Attached scsi disk sdc at scsi0, channel 0, id 2, 
lun 0
Jun 29 15:53:03 tor kernel: Attached scsi generic sg0 at scsi0, channel 0, id 
0, lun 0,  type 0
Jun 29 15:53:03 tor kernel: Attached scsi generic sg1 at scsi0, channel 0, id 
1, lun 0,  type 0
Jun 29 15:53:03 tor kernel: Attached scsi generic sg2 at scsi0, channel 0, id 
2, lun 0,  type 0
Jun 29 15:53:03 tor kernel: Attached scsi generic sg3 at scsi1, channel 0, id 
3, lun 0,  type 1
Jun 29 15:53:03 tor kernel: Attached scsi generic sg4 at scsi1, channel 0, id 
3, lun 1,  type 8
Jun 29 15:53:03 tor kernel: mice: PS/2 mouse device common for all mice
Jun 29 15:53:03 tor kernel: input: AT Translated Set 2 keyboard on 
isa0060/serio0
Jun 29 15:53:03 tor kernel: md: linear personality registered as nr 1
Jun 29 15:53:03 tor kernel: md: raid5 personality registered as nr 4
Jun 29 15:53:03 tor kernel: raid5: measuring checksumming speed
Jun 29 15:53:03 tor kernel:    8regs     :  1284.000 MB/sec
Jun 29 15:53:03 tor kernel:    8regs_prefetch:  1148.000 MB/sec
Jun 29 15:53:03 tor kernel:    32regs    :  1020.000 MB/sec
Jun 29 15:53:03 tor kernel:    32regs_prefetch:   920.000 MB/sec
Jun 29 15:53:03 tor kernel:    pII_mmx   :  2432.000 MB/sec
Jun 29 15:53:03 tor kernel:    p5_mmx    :  3260.000 MB/sec
Jun 29 15:53:03 tor kernel: raid5: using function: p5_mmx (3260.000 MB/sec)
Jun 29 15:53:03 tor kernel: md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
Jun 29 15:53:03 tor kernel: NET: Registered protocol family 2
Jun 29 15:53:03 tor kernel: IP: routing cache hash table of 8192 buckets, 
64Kbytes
Jun 29 15:53:03 tor kernel: TCP established hash table entries: 131072 (order: 
8, 1048576 bytes)
Jun 29 15:53:03 tor kernel: TCP bind hash table entries: 65536 (order: 6, 
262144 bytes)
Jun 29 15:53:03 tor kernel: TCP: Hash tables configured (established 131072 
bind 65536)
Jun 29 15:53:03 tor kernel: IPv4 over IPv4 tunneling driver
Jun 29 15:53:03 tor kernel: NET: Registered protocol family 1
Jun 29 15:53:03 tor kernel: NET: Registered protocol family 17
Jun 29 15:53:03 tor kernel: md: Autodetecting RAID arrays.
Jun 29 15:53:03 tor kernel: md: autorun ...
Jun 29 15:53:03 tor kernel: md: considering sdc4 ...
Jun 29 15:53:03 tor kernel: md:  adding sdc4 ...
Jun 29 15:53:03 tor kernel: md: sdc3 has different UUID to sdc4
Jun 29 15:53:03 tor kernel: md: sdc2 has different UUID to sdc4
Jun 29 15:53:03 tor kernel: md:  adding sdb5 ...
Jun 29 15:53:03 tor kernel: md: sdb3 has different UUID to sdc4
Jun 29 15:53:03 tor kernel: md: sdb2 has different UUID to sdc4
Jun 29 15:53:03 tor kernel: md:  adding sda4 ...
Jun 29 15:53:03 tor kernel: md: sda3 has different UUID to sdc4
Jun 29 15:53:03 tor kernel: md: sda2 has different UUID to sdc4
Jun 29 15:53:03 tor kernel: md: created md2
Jun 29 15:53:03 tor kernel: md: bind<sda4>
Jun 29 15:53:03 tor kernel: md: bind<sdb5>
Jun 29 15:53:03 tor kernel: md: bind<sdc4>
Jun 29 15:53:03 tor kernel: md: running: <sdc4><sdb5><sda4>
Jun 29 15:53:03 tor kernel: raid5: device sdc4 operational as raid disk 2
Jun 29 15:53:03 tor kernel: raid5: device sdb5 operational as raid disk 1
Jun 29 15:53:03 tor kernel: raid5: device sda4 operational as raid disk 0
Jun 29 15:53:03 tor kernel: raid5: allocated 3154kB for md2
Jun 29 15:53:03 tor kernel: raid5: raid level 5 set md2 active with 3 out of 3 
devices, algorithm 2
Jun 29 15:53:03 tor kernel: RAID5 conf printout:
Jun 29 15:53:03 tor kernel:  --- rd:3 wd:3 fd:0
Jun 29 15:53:03 tor kernel:  disk 0, o:1, dev:sda4
Jun 29 15:53:03 tor kernel:  disk 1, o:1, dev:sdb5
Jun 29 15:53:03 tor kernel:  disk 2, o:1, dev:sdc4
Jun 29 15:53:03 tor kernel: md: considering sdc3 ...
Jun 29 15:53:03 tor kernel: md:  adding sdc3 ...
Jun 29 15:53:03 tor kernel: md: sdc2 has different UUID to sdc3
Jun 29 15:53:03 tor kernel: md:  adding sdb3 ...
Jun 29 15:53:03 tor kernel: md: sdb2 has different UUID to sdc3
Jun 29 15:53:03 tor kernel: md:  adding sda3 ...
Jun 29 15:53:03 tor kernel: md: sda2 has different UUID to sdc3
Jun 29 15:53:03 tor kernel: md: created md1
Jun 29 15:53:03 tor kernel: md: bind<sda3>
Jun 29 15:53:03 tor kernel: md: bind<sdb3>
Jun 29 15:53:03 tor kernel: md: bind<sdc3>
Jun 29 15:53:03 tor kernel: md: running: <sdc3><sdb3><sda3>
Jun 29 15:53:03 tor kernel: raid5: device sdc3 operational as raid disk 2
Jun 29 15:53:03 tor kernel: raid5: device sdb3 operational as raid disk 1
Jun 29 15:53:03 tor kernel: raid5: device sda3 operational as raid disk 0
Jun 29 15:53:03 tor kernel: raid5: allocated 3154kB for md1
Jun 29 15:53:03 tor kernel: raid5: raid level 5 set md1 active with 3 out of 3 
devices, algorithm 2
Jun 29 15:53:03 tor kernel: RAID5 conf printout:
Jun 29 15:53:03 tor kernel:  --- rd:3 wd:3 fd:0
Jun 29 15:53:03 tor kernel:  disk 0, o:1, dev:sda3
Jun 29 15:53:03 tor kernel:  disk 1, o:1, dev:sdb3
Jun 29 15:53:03 tor kernel:  disk 2, o:1, dev:sdc3
Jun 29 15:53:03 tor kernel: md: considering sdc2 ...
Jun 29 15:53:03 tor kernel: md:  adding sdc2 ...
Jun 29 15:53:03 tor kernel: md:  adding sdb2 ...
Jun 29 15:53:03 tor kernel: md:  adding sda2 ...
Jun 29 15:53:03 tor kernel: md: created md0
Jun 29 15:53:03 tor kernel: md: bind<sda2>
Jun 29 15:53:03 tor kernel: md: bind<sdb2>
Jun 29 15:53:03 tor kernel: md: bind<sdc2>
Jun 29 15:53:03 tor kernel: md: running: <sdc2><sdb2><sda2>
Jun 29 15:53:03 tor kernel: raid5: device sdc2 operational as raid disk 2
Jun 29 15:53:03 tor kernel: raid5: device sdb2 operational as raid disk 1
Jun 29 15:53:03 tor kernel: raid5: device sda2 operational as raid disk 0
Jun 29 15:53:03 tor kernel: raid5: allocated 3154kB for md0
Jun 29 15:53:03 tor kernel: raid5: raid level 5 set md0 active with 3 out of 3 
devices, algorithm 2
Jun 29 15:53:03 tor kernel: RAID5 conf printout:
Jun 29 15:53:03 tor kernel:  --- rd:3 wd:3 fd:0
Jun 29 15:53:03 tor kernel:  disk 0, o:1, dev:sda2
Jun 29 15:53:03 tor kernel:  disk 1, o:1, dev:sdb2
Jun 29 15:53:03 tor kernel:  disk 2, o:1, dev:sdc2
Jun 29 15:53:03 tor kernel: md: ... autorun DONE.
Jun 29 15:53:03 tor kernel: ...<6>md: syncing RAID array md1
Jun 29 15:53:03 tor kernel: md: minimum _guaranteed_ reconstruction speed: 1000 
KB/sec/disc.
Jun 29 15:53:03 tor kernel: md: using maximum available idle IO bandwith (but 
not more than 200000 KB/sec) for reconstruction.
Jun 29 15:53:03 tor kernel: md: using 128k window, over a total of 6996224 
blocks.
Jun 29 15:53:03 tor kernel: EXT3-fs: INFO: recovery required on readonly 
filesystem.
Jun 29 15:53:03 tor kernel: EXT3-fs: write access will be enabled during 
recovery.
Jun 29 15:53:03 tor kernel: kjournald starting.  Commit interval 5 seconds
Jun 29 15:53:03 tor kernel: EXT3-fs: recovery complete.
Jun 29 15:53:03 tor kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jun 29 15:53:03 tor kernel: VFS: Mounted root (ext3 filesystem) readonly.
Jun 29 15:53:03 tor kernel: Freeing unused kernel memory: 380k freed
Jun 29 15:53:03 tor kernel: Adding 995832k swap on /dev/md0.  Priority:-1 
extents:1
Jun 29 15:53:03 tor kernel: EXT3 FS on md1, internal journal
Jun 29 15:53:03 tor kernel: cipcb: CIPE driver vers 1.6.0 (c) Olaf Titz 1996-
2003, 100 channels, debug=1
Jun 29 15:53:03 tor kernel: cipcb: cipe_alloc_dev 0
Jun 29 15:53:03 tor kernel: program stinit is using a deprecated SCSI ioctl, 
please convert it to SG_IO
Jun 29 15:53:03 tor kernel: kjournald starting.  Commit interval 5 seconds
Jun 29 15:53:03 tor kernel: EXT3-fs warning: maximal mount count reached, 
running e2fsck is recommended
Jun 29 15:53:03 tor kernel: EXT3 FS on md2, internal journal
Jun 29 15:53:03 tor kernel: EXT3-fs: recovery complete.
Jun 29 15:53:03 tor kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jun 29 15:53:03 tor kernel: kjournald starting.  Commit interval 5 seconds
Jun 29 15:53:03 tor kernel: EXT3 FS on sda1, internal journal
Jun 29 15:53:03 tor kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jun 29 15:53:03 tor kernel: kjournald starting.  Commit interval 5 seconds
Jun 29 15:53:03 tor kernel: EXT3-fs warning: maximal mount count reached, 
running e2fsck is recommended
Jun 29 15:53:03 tor kernel: EXT3 FS on hde, internal journal
Jun 29 15:53:03 tor kernel: EXT3-fs: recovery complete.
Jun 29 15:53:03 tor kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jun 29 15:53:03 tor kernel: kjournald starting.  Commit interval 5 seconds
Jun 29 15:53:03 tor kernel: EXT3-fs warning: mounting fs with errors, running 
e2fsck is recommended
Jun 29 15:53:03 tor kernel: EXT3 FS on hdf1, internal journal
Jun 29 15:53:03 tor kernel: EXT3-fs: recovery complete.
Jun 29 15:53:03 tor kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jun 29 15:53:03 tor kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 
Mbps Full Duplex
Jun 29 15:53:05 tor kernel: cipcb0: alloc
Jun 29 15:53:05 tor kernel: cipcb: cipe_alloc_dev 1
Jun 29 15:53:05 tor kernel: cipcb1: setpar
Jun 29 15:53:05 tor kernel: cipcb1: setkey
Jun 29 15:53:05 tor kernel: cipcb1: attach
Jun 29 15:53:05 tor kernel: cipcb1: opened
Jun 29 15:53:05 tor kernel: cipcb1: cipe_sendmsg
Jun 29 15:53:05 tor kernel: cipcb1: cipe_recvmsg
Jun 29 15:53:09 tor lpd[853]: restarted
Jun 29 16:05:56 tor kernel: md: md1: sync done.
Jun 29 16:05:56 tor kernel: RAID5 conf printout:
Jun 29 16:05:56 tor kernel:  --- rd:3 wd:3 fd:0
Jun 29 16:05:56 tor kernel:  disk 0, o:1, dev:sda3
Jun 29 16:05:56 tor kernel:  disk 1, o:1, dev:sdb3
Jun 29 16:05:56 tor kernel:  disk 2, o:1, dev:sdc3
Jun 29 16:06:05 tor kernel: smb_receive_header: short packet: 0
Jun 29 16:06:35 tor kernel: smb_add_request: request [e59973e0, mid=16237] 
timed out!
Jun 29 16:06:35 tor kernel: smb_add_request: request [e59971e0, mid=16238] 
timed out!
Jun 29 16:06:35 tor kernel: smb_add_request: request [e59970e0, mid=16239] 
timed out!
Jun 29 16:06:36 tor kernel: smb_get_length: Invalid NBT packet, code=4d
Jun 29 16:07:06 tor kernel: smb_add_request: request [e59971e0, mid=19078] 
timed out!
Jun 29 16:07:06 tor kernel: smb_add_request: request [e59973e0, mid=19079] 
timed out!
Jun 29 16:07:06 tor kernel: smb_get_length: Invalid NBT packet, code=b0
Jun 29 16:07:36 tor kernel: smb_add_request: request [e59971e0, mid=26442] 
timed out!
Jun 29 16:07:36 tor kernel: smb_add_request: request [e59973e0, mid=26455] 
timed out!
Jun 29 16:08:08 tor kernel: smb_get_length: Invalid NBT packet, code=b4
Jun 29 16:08:38 tor kernel: smb_add_request: request [e59973e0, mid=29706] 
timed out!
Jun 29 16:08:38 tor kernel: smb_add_request: request [e59970e0, mid=29707] 
timed out!
Jun 29 16:08:38 tor kernel: smb_get_length: Invalid NBT packet, code=65
Jun 29 16:09:08 tor kernel: smb_add_request: request [e59970e0, mid=5718] timed 
out!
Jun 29 16:09:08 tor kernel: smb_add_request: request [e59973e0, mid=5719] timed 
out!
Jun 29 16:09:23 tor kernel: smb_get_length: Invalid NBT packet, code=40
Jun 29 16:09:53 tor kernel: smb_add_request: request [e5997de0, mid=45887] 
timed out!
Jun 29 16:09:53 tor kernel: smb_add_request: request [e59973e0, mid=45888] 
timed out!
Jun 29 16:09:54 tor kernel: smb_get_length: Invalid NBT packet, code=d1
Jun 29 16:10:24 tor kernel: smb_add_request: request [e5997de0, mid=60090] 
timed out!
Jun 29 16:10:24 tor kernel: smb_add_request: request [e59973e0, mid=60091] 
timed out!
Jun 29 16:10:35 tor kernel: smb_get_length: Invalid NBT packet, code=99
Jun 29 16:11:05 tor kernel: smb_add_request: request [e59973e0, mid=41646] 
timed out!
Jun 29 16:11:05 tor kernel: smb_add_request: request [e5997de0, mid=41647] 
timed out!
Jun 29 16:11:08 tor kernel: smb_get_length: Invalid NBT packet, code=4b
Jun 29 16:11:38 tor kernel: smb_add_request: request [e59973e0, mid=47301] 
timed out!
Jun 29 16:11:38 tor kernel: smb_add_request: request [e5997de0, mid=47302] 
timed out!
Jun 29 16:11:40 tor kernel: smb_get_length: Invalid NBT packet, code=35
Jun 29 16:12:10 tor kernel: smb_add_request: request [e5997de0, mid=39946] 
timed out!
Jun 29 16:12:10 tor kernel: smb_add_request: request [e59973e0, mid=39960] 
timed out!
Jun 29 16:12:13 tor kernel: smb_get_length: Invalid NBT packet, code=17
Jun 29 16:12:43 tor kernel: smb_add_request: request [e59973e0, mid=57137] 
timed out!
Jun 29 16:12:43 tor kernel: smb_add_request: request [e5997de0, mid=57138] 
timed out!
Jun 29 16:12:52 tor kernel: smb_get_length: Invalid NBT packet, code=ae
Jun 29 16:13:22 tor kernel: smb_add_request: request [e5997de0, mid=54096] 
timed out!
Jun 29 16:13:22 tor kernel: smb_add_request: request [e59973e0, mid=54112] 
timed out!
Jun 29 16:13:24 tor kernel: smb_get_length: Invalid NBT packet, code=71
Jun 29 16:13:54 tor kernel: smb_add_request: request [e59973e0, mid=10575] 
timed out!
Jun 29 16:13:54 tor kernel: smb_add_request: request [e5997de0, mid=10576] 
timed out!
Jun 29 16:14:06 tor kernel: smb_get_length: Invalid NBT packet, code=a
Jun 29 16:14:36 tor kernel: smb_add_request: request [e59970e0, mid=21366] 
timed out!
Jun 29 16:14:36 tor kernel: smb_add_request: request [e5997ce0, mid=21370] 
timed out!
Jun 29 16:14:39 tor kernel: smbiod_handle_request: smbiod got a request ... and 
we don't implement oplocks!
Jun 29 16:14:39 tor kernel: smb_get_length: Invalid NBT packet, code=8b
Jun 29 16:15:09 tor kernel: smb_add_request: request [e59973e0, mid=22214] 
timed out!
Jun 29 16:15:09 tor kernel: smb_add_request: request [e5997ce0, mid=22215] 
timed out!
Jun 29 16:15:22 tor kernel: smb_get_length: Invalid NBT packet, code=f3
Jun 29 16:15:27 tor kernel: smb_get_length: Invalid NBT packet, code=c
Jun 29 16:15:52 tor kernel: smb_add_request: request [e5997ce0, mid=6302] timed 
out!
Jun 29 16:15:57 tor kernel: smb_add_request: request [e59970e0, mid=14965] 
timed out!
Jun 29 16:15:58 tor kernel: smb_get_length: Invalid NBT packet, code=be
Jun 29 16:16:28 tor kernel: smb_add_request: request [e59973e0, mid=7531] timed 
out!
Jun 29 16:16:28 tor kernel: smb_add_request: request [e59970e0, mid=7532] timed 
out!
Jun 29 16:16:32 tor kernel: smb_receive_header: short packet: 0
Jun 29 16:17:02 tor kernel: smb_add_request: request [e59971e0, mid=10993] 
timed out!
Jun 29 16:17:02 tor kernel: smb_add_request: request [e59970e0, mid=10994] 
timed out!
Jun 29 16:17:02 tor kernel: smb_add_request: request [e59973e0, mid=10995] 
timed out!
Jun 29 16:17:04 tor kernel: smb_get_length: Invalid NBT packet, code=2f
Jun 29 16:17:34 tor kernel: smb_add_request: request [e59971e0, mid=17781] 
timed out!
Jun 29 16:17:34 tor kernel: smb_add_request: request [e59970e0, mid=17782] 
timed out!
Jun 29 16:17:40 tor kernel: smb_get_length: Invalid NBT packet, code=ff
Jun 29 16:18:10 tor kernel: smb_add_request: request [e59970e0, mid=47314] 
timed out!
Jun 29 16:18:10 tor kernel: smb_add_request: request [e59973e0, mid=47315] 
timed out!
Jun 29 16:18:18 tor kernel: smb_get_length: Invalid NBT packet, code=d8
Jun 29 16:18:48 tor kernel: smb_add_request: request [e59971e0, mid=41784] 
timed out!
Jun 29 16:18:48 tor kernel: smb_add_request: request [e59970e0, mid=41793] 
timed out!
Jun 29 16:19:01 tor kernel: smb_get_length: Invalid NBT packet, code=9d
Jun 29 16:19:31 tor kernel: smb_add_request: request [e59973e0, mid=46378] 
timed out!
Jun 29 16:19:31 tor kernel: smb_proc_readdir_long: error=-5, breaking
Jun 29 16:19:31 tor kernel: smb_add_request: request [e59971e0, mid=46394] 
timed out!
Jun 29 16:19:31 tor kernel: smb_add_request: request [e59972e0, mid=46407] 
timed out!
Jun 29 16:19:35 tor kernel: smb_get_length: Invalid NBT packet, code=51
Jun 29 16:20:05 tor kernel: smb_add_request: request [e5997ce0, mid=5412] timed 
out!
Jun 29 16:20:05 tor kernel: smb_proc_readdir_long: error=-5, breaking
Jun 29 16:20:05 tor kernel: smb_add_request: request [e59971e0, mid=5428] timed 
out!
Jun 29 16:20:05 tor kernel: smb_add_request: request [e59972e0, mid=5429] timed 
out!
Jun 29 16:20:24 tor kernel: smb_get_length: Invalid NBT packet, code=f2
Jun 29 16:20:49 tor kernel: smb_add_request: request [e5997ce0, mid=1010] timed 
out!
Jun 29 16:20:54 tor kernel: smb_add_request: request [e59971e0, mid=9130] timed 
out!
Jun 29 16:20:56 tor kernel: smb_get_length: Invalid NBT packet, code=62
Jun 29 16:21:26 tor kernel: smb_add_request: request [e5997ce0, mid=49769] 
timed out!
Jun 29 16:21:26 tor kernel: smb_add_request: request [e59970e0, mid=49770] 
timed out!
Jun 29 16:21:48 tor kernel: smb_get_length: Invalid NBT packet, code=4
Jun 29 16:22:18 tor kernel: smb_add_request: request [e59971e0, mid=29856] 
timed out!
Jun 29 16:22:18 tor kernel: smb_add_request: request [e59972e0, mid=29857] 
timed out!
Jun 29 16:22:25 tor kernel: smb_receive_header: long packet: 130853
Jun 29 16:22:55 tor kernel: smb_add_request: request [e5997ce0, mid=6803] timed 
out!
Jun 29 16:22:55 tor kernel: smb_add_request: request [e59971e0, mid=6813] timed 
out!
Jun 29 16:22:55 tor kernel: smb_add_request: request [e59972e0, mid=6814] timed 
out!
Jun 29 16:23:25 tor kernel: smb_add_request: request [e5997ce0, mid=6815] timed 
out!
Jun 29 16:23:25 tor kernel: smb_add_request: request [e59971e0, mid=6816] timed 
out!
Jun 29 16:23:25 tor kernel: smb_add_request: request [e59972e0, mid=6817] timed 
out!
Jun 29 16:23:55 tor kernel: smb_add_request: request [e5997ce0, mid=6818] timed 
out!
Jun 29 16:23:55 tor kernel: smb_add_request: request [e59971e0, mid=6819] timed 
out!
Jun 29 16:23:55 tor kernel: smb_add_request: request [e59972e0, mid=6820] timed 
out!
Jun 29 16:24:25 tor kernel: smb_add_request: request [e5997ce0, mid=6821] timed 
out!
Jun 29 16:24:25 tor kernel: smb_add_request: request [e59971e0, mid=6822] timed 
out!
Jun 29 16:24:25 tor kernel: smb_add_request: request [e59972e0, mid=6823] timed 
out!
Jun 29 16:24:55 tor kernel: smb_add_request: request [e5997ce0, mid=6824] timed 
out!
Jun 29 16:24:55 tor kernel: smb_add_request: request [e59971e0, mid=6825] timed 
out!
Jun 29 16:24:55 tor kernel: smb_add_request: request [e59972e0, mid=6826] timed 
out!
Jun 29 16:24:55 tor kernel: smb_lookup: find install/siemens failed, error=-5
Jun 29 16:25:25 tor kernel: smb_add_request: request [e5997ce0, mid=6827] timed 
out!
Jun 29 16:25:25 tor kernel: smb_add_request: request [e59971e0, mid=6828] timed 
out!
Jun 29 16:25:25 tor kernel: smb_add_request: request [e59972e0, mid=6829] timed 
out!



This output is from a run where three instances of the command below was
running. One of the instances reported this:
cp: cannot open `./HogiaArt/ARTSYS/Q_MJ.LOC' for reading: Text file busy
cp: cannot open `./HogiaArt/Data/8008/VDM89.tmp' for reading: Input/output error
find: ./HogiaOpen/arkiv/ScanArc Plasma Technologies AB/Brev: Input/output error
find: ./HogiaOpen/arkiv/Swedish Tissue/Brev: Input/output error
cp: reading `./HogiaOpen/pol-bak.mdb': Input/output error

The "Text file busy" line is completely ok - the file is probably open and
locked.

The other two instances didn't report anything before the machine hanged.



[6.] A small shell script or example program which triggers the problem
Running multiple instances of this command in different folders under the
same mounted smbfs:

find | (count=0; while read filename ;do if [[ -f "$filename" ]] ;then
cp "$filename" /dev/null; count=$(( $count + 1 )); fi; done; echo files: $count)


For reproducing the problem it seems the command have to run in more than
one instance, it seem that one instance doesn't trigger the problem at all.
Two instances triggers it occasionaly (but rarely). Three instances triggers
it faster. I don't know if there is an upper limit or if it gets worse the
more instances there are. It seems like the different instances should run
in different folders, but on the same mounted server (possibly requiring
the same mount point, I only have one mount point per server)

I have run this using a Win2k server, but it appears that doesn't alter
the fact that the problem arises. It might affect how often it does appear
however.




[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)

If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

Linux tor 2.6.11.8 #6 Fri Jun 10 16:48:41 CEST 2005 i686 GNU/Linux

Gnu C                  3.3.5
Gnu make               3.80
binutils               2.15
util-linux             2.12p
mount                  2.12p
module-init-tools      3.2-pre1
e2fsprogs              1.37
reiserfsprogs          line
reiser4progs           line
PPP                    2.4.3
Linux C Library        2.3.2
Dynamic linker (ldd)   2.3.2
Procps                 3.2.5
Net-tools              1.60
Console-tools          0.2.3
Sh-utils               5.2.1
./ver_linux: line 90: udevinfo: command not found
Modules Loaded         cipcb


Besides that I guess the version of smbmount might be relevant: 3.0.2-Debian



[7.2.] Processor information (from /proc/cpuinfo):

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 4
model name      : AMD Athlon(tm) Processor
stepping        : 2
cpu MHz         : 908.467
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat 
pse36 mmx fxsr pni syscall mmxext 3dnowext 3dnow
bogomips        : 1789.95



[7.3.] Module information (from /proc/modules):

cipcb 34536 1 - Live 0xe881a000



[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)

0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
03c0-03df : vga+
0cf8-0cff : PCI conf1
6400-643f : 0000:00:11.0
6800-6803 : 0000:00:11.0
7000-7007 : 0000:00:11.0
7400-7403 : 0000:00:11.0
7800-7807 : 0000:00:11.0
8000-803f : 0000:00:0d.0
  8000-803f : e1000
8400-840f : 0000:00:0b.0
  8400-8407 : ide2
  8408-840f : ide3
8800-8803 : 0000:00:0b.0
9000-9007 : 0000:00:0b.0
9400-9403 : 0000:00:0b.0
  9402-9402 : ide2
9800-9807 : 0000:00:0b.0
  9800-9807 : ide2
a000-a0ff : 0000:00:0a.0
a400-a4ff : 0000:00:09.0
d800-d80f : 0000:00:04.1
e400-e4ff : 0000:00:04.4
  e400-e47f : motherboard
    e400-e403 : PM1a_EVT_BLK
    e404-e405 : PM1a_CNT_BLK
    e408-e40b : PM_TMR
    e420-e423 : GPE0_BLK
e800-e80f : 0000:00:04.4
  e800-e80f : motherboard


00000000-0009e7ff : System RAM
0009e800-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000cc000-000d07ff : Adapter ROM
000d4000-000d47ff : Adapter ROM
000d8000-000da7ff : Adapter ROM
000dc000-000dcfff : Adapter ROM
000f0000-000fffff : System ROM
00100000-27febfff : System RAM
  00100000-002df2c1 : Kernel code
  002df2c2-0037feff : Kernel data
27fec000-27feefff : ACPI Tables
27fef000-27ffefff : reserved
27fff000-27ffffff : ACPI Non-volatile Storage
da800000-da81ffff : 0000:00:11.0
db000000-db01ffff : 0000:00:0d.0
  db000000-db01ffff : e1000
db800000-db81ffff : 0000:00:0d.0
  db800000-db81ffff : e1000
dc000000-dfffffff : 0000:00:0c.0
e2000000-e2003fff : 0000:00:0b.0
e2800000-e2800fff : 0000:00:0a.0
  e2800000-e2800fff : aic7xxx
e3000000-e3000fff : 0000:00:09.0
  e3000000-e3000fff : aic7xxx
e4000000-e7ffffff : 0000:00:00.0
ffff0000-ffffffff : reserved



[7.5.] PCI information ('lspci -vvv' as root)

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 
02)
        Subsystem: Asustek Computer, Inc. A7V Mainboard
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [a0] AGP version 2.0
                Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 
64bit- FW- AGP3- Rate=x1,x2
                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- 
Rate=<none>
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-
,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] 
(prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
        Capabilities: [80] Power Management version 2
                Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-
,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] 
(rev 22)
        Subsystem: Asustek Computer, Inc. A7V Mainboard
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping+ SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0

0000:00:04.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) (prog-if 8a 
[Master SecP PriP])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32
        Region 4: I/O ports at d800 [size=16]
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-
,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] 
(rev 30)
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin ? routed to IRQ 9
        Capabilities: [68] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-
,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:09.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U (rev 
01)
        Subsystem: Adaptec AHA-2940UW SCSI Host Adapter
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2000ns min, 2000ns max), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 5
        Region 0: I/O ports at a400 [disabled] [size=256]
        Region 1: Memory at e3000000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-
,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:0a.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U (rev 
01)
        Subsystem: Adaptec AHA-2940UW SCSI Host Adapter
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2000ns min, 2000ns max), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 7
        Region 0: I/O ports at a000 [disabled] [size=256]
        Region 1: Memory at e2800000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-
,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:0b.0 Unknown mass storage controller: Promise Technology, Inc. 20269 
(rev 02) (prog-if 85)
        Subsystem: Promise Technology, Inc. Ultra133TX2
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- 
<MAbort- >SERR- <PERR-
        Latency: 32 (1000ns min, 4500ns max), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 10
        Region 0: I/O ports at 9800 [size=8]
        Region 1: I/O ports at 9400 [size=4]
        Region 2: I/O ports at 9000 [size=8]
        Region 3: I/O ports at 8800 [size=4]
        Region 4: I/O ports at 8400 [size=16]
        Region 5: Memory at e2000000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [60] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-
,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:0c.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01) (prog-
if 00 [VGA])
        Subsystem: S3 Inc. ViRGE/DX
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (1000ns min, 63750ns max)
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at dc000000 (32-bit, non-prefetchable) [size=64M]
        Expansion ROM at 000c0000 [disabled] [size=64K]

0000:00:0d.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet 
Controller
        Subsystem: Intel Corp. PRO/1000 MT Desktop Adapter
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (63750ns min), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 5
        Region 0: Memory at db800000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at db000000 (32-bit, non-prefetchable) [size=128K]
        Region 2: I/O ports at 8000 [size=64]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-
,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [e4] PCI-X non-bridge device.
                Command: DPERE- ERO+ RBC=0 OST=0
                Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, 
DMMRBC=2, DMOST=0, DMCRS=0, RSCEM-
        Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 
Enable-
                Address: 0000000000000000  Data: 0000

0000:00:11.0 Unknown mass storage controller: Promise Technology, Inc. PDC20265 
(FastTrak100 Lite/Ultra100) (rev 02)
        Subsystem: Promise Technology, Inc. Ultra100
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32
        Interrupt: pin A routed to IRQ 10
        Region 0: I/O ports at 7800 [size=8]
        Region 1: I/O ports at 7400 [size=4]
        Region 2: I/O ports at 7000 [size=8]
        Region 3: I/O ports at 6800 [size=4]
        Region 4: I/O ports at 6400 [size=64]
        Region 5: Memory at da800000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: [58] Power Management version 1
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-
,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-



[7.6.] SCSI information (from /proc/scsi/scsi)

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: QUANTUM  Model: QM318000TD-SW    Rev: N1B0
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: IBM      Model: IC35L036UWDY10-0 Rev: S29A
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 02 Lun: 00
  Vendor: IBM      Model: DDYS-T18350N     Rev: S96H
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 03 Lun: 00
  Vendor: SONY     Model: TSL-11000        Rev: L0u6
  Type:   Sequential-Access                ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 03 Lun: 01
  Vendor: SONY     Model: TSL-11000        Rev: L0u6
  Type:   Medium Changer                   ANSI SCSI revision: 02



[7.7.] Other information that might be relevant to the problem
       (please look in /proc and include all information that you
       think to be relevant):

[7.7.1.] /proc/mounts:

rootfs / rootfs rw 0 0
/dev/root / ext3 rw 0 0
proc /proc proc rw,nodiratime 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
/dev/md2 /cvs ext3 rw 0 0
/dev/sda1 /boot ext3 rw 0 0
/dev/hde /backup/dbfiles ext3 rw 0 0
/dev/hdf1 /backup/newdb ext3 rw 0 0
//ygdrasil/d$ /net/ygdrasil/d smbfs 
ro,nodiratime,nosuid,nodev,uid=0,gid=0,file_mode=0755,dir_mode=0755 0 0
//rserver/big /net/rserver/big smbfs 
rw,nodiratime,nosuid,nodev,uid=0,gid=0,file_mode=0755,dir_mode=0755 0 0
//exserver/d$ /net/exserver/d smbfs 
ro,nodiratime,nosuid,nodev,uid=0,gid=0,file_mode=0755,dir_mode=0755 0 0
//ygdrasil/rest /net/ygdrasil/rest smbfs 
rw,nodiratime,nosuid,nodev,uid=34,gid=0,file_mode=0660,dir_mode=0777 0 0



[7.7.2.] /proc/config.gz: (slightly edited)

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11.8
# Fri Jun 10 16:47:26 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
# CONFIG_EXPERIMENTAL is not set
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
CONFIG_MK7=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_TSC=y

#
# Firmware Drivers
#
CONFIG_NOHIGHMEM=y

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_ASUS=m
CONFIG_ACPI_IBM=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_NAMES=y

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set

#
# Plug and Play support
#
CONFIG_PNP=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_INITRAMFS_SOURCE=""

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y

#
# SCSI low-level drivers
#
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=253
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_SCSI_QLA2XXX=y

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID5=y

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_NET_IPIP=y
CONFIG_INET_TUNNEL=y
CONFIG_IP_TCPDIAG=y
CONFIG_XFRM=y

#
# Network testing
#
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y

#
# Ethernet (1000 Mbit)
#
CONFIG_E1000=y
CONFIG_E1000_NAPI=y


#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768

#
# Input I/O drivers
#
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
CONFIG_SERIO_LIBPS2=y

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y

#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# Graphics support
#
CONFIG_VIDEO_SELECT=y

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y

#
# XFS support
#
CONFIG_DNOTIFY=y
CONFIG_AUTOFS4_FS=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y

#
# Network File Systems
#
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp850"

#
# Partition Types
#
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_ISO8859_1=y

#
# Kernel hacking
#
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_EARLY_PRINTK=y

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_DES=y

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y



[X.] Other notes, patches, fixes, workarounds:
I have run a memory diagnostics program on the computer - that resulted in
a replaced memory module - but the problem unfortunately remains and I
don't get any memory errors anymore.

I have googled for smb_add_request and found several references to a similar
problem (the symptoms are similar - if not the cause). Those seem to be
relatively old however and the solution usually says something about the
samba server version. I have, however, this problem even with a win2k server
and can't do very much about the version there. It is possible I get the
error faster for those samba server versions mentioned in those posts - but
they don't dissapear completely anyway.
I also see some new posts, but don't find a solution to those.
I apologise if I was supposed to post this under an existing bug, but I
didn't find any good one I thougt close enought to post under, please send
me a note if I should have done that so I know the next time... I guess
the actual cause behind this is the same as several other bug reports.

The frequency of the smb_add_request messages increase with load, and not
in a linear fashion, the increase are much higher than linear.

Heavy load distributed on different servers (or possibly different mount
points) doesn't count, it seems it is the load per server (or mount point?)
that counts.

Heavy load doing exacly the same work doesn't count either, I guess that
is because the information is cached locally and not generates new traffic.

In my tests it takes quite some time (like 20-120 minutes) before the
machine actually hangs and in some rare cases it didn't even hang either.

I am a programmer, but quite new to doing things with the kernel (and
actually linux programming in general) so I don't find my way there very
easy, but of course I will do whatever I can in solving this.

My computer is doing real work here at the office so I have to pick
testing time carefully but I can of course do further tests.

It seems like one part of the problem is running this in several instances
simultaneously. My real problem is backing up data and some of those
processes takes days to complete, and some have to be run periodically
once per day. At most I have four of these running at the same time (but
only for short times and at least one is suspended completely in that case)
but two seems to trigger it frequently enough to be a problem and I don't
currently see a solution not requering two simulatenous runs.
Comment 1 Johan Bengtsson 2005-07-14 12:38:29 UTC
I have switched to cifs instead of smbfs and currently don't seem to have any 
problem. I am going to ignore this if cifs actually solves my problem unless 
someone would like me to test something.
Comment 2 Dominik Karall 2005-08-08 14:17:13 UTC
same here with 2.6.13-rc6, shouldn't that be fixed till 2.6.13 release?

dmesg:
smb_get_length: Invalid NBT packet, code=11
smb_add_request: request [ffff810039a96ad0, mid=1802201963] timed out!
Slab corruption: start=ffff810039a96ad0, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff8020829a>](smb_add_request+0x41a/0x4c0)
010: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
150: 6b 6b 6b 6b 6b 6b 6b 6b 02 00 58 00 fb ff ff ff
Prev obj: start=ffff810039a96958, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff802008ce>](smb_newconn+0x36e/0x3e0)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Next obj: start=ffff810039a96c48, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff80202941>](smb_proc_readdir_long+0x691/0x6c0)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
smb_add_request: request [ffff810039a96088, mid=1802201963] timed out!
Slab corruption: start=ffff810039a96088, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff8020829a>](smb_add_request+0x41a/0x4c0)
010: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
150: 6b 6b 6b 6b 6b 6b 6b 6b 02 00 58 00 fb ff ff ff
Next obj: start=ffff810039a96200, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff80203061>](smb_proc_getattr_unix+0x71/0xa0)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
smb_get_length: Invalid NBT packet, code=35
smb_add_request: request [ffff810039a96200, mid=1802201963] timed out!
Slab corruption: start=ffff810039a96200, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff8020829a>](smb_add_request+0x41a/0x4c0)
010: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
150: 6b 6b 6b 6b 6b 6b 6b 6b 02 00 58 00 fb ff ff ff
Prev obj: start=ffff810039a96088, len=352
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<ffffffff80207c36>](smb_alloc_request+0x46/0x120)
000: 00 c1 14 20 00 81 ff ff d0 6a a9 39 00 81 ff ff
010: 02 00 00 00 00 00 00 00 01 00 00 00 ad 4e ad de
Next obj: start=ffff810039a96378, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff80203061>](smb_proc_getattr_unix+0x71/0xa0)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
smb_get_length: Invalid NBT packet, code=ff
smb_add_request: request [ffff810039a96088, mid=1802201963] timed out!
Slab corruption: start=ffff810039a96088, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff8020829a>](smb_add_request+0x41a/0x4c0)
010: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
150: 6b 6b 6b 6b 6b 6b 6b 6b 02 00 58 00 fb ff ff ff
Next obj: start=ffff810039a96200, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff80200a4b>](smb_proc_open+0x10b/0x120)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
smb_get_length: Invalid NBT packet, code=31
smb_add_request: request [ffff810039a96088, mid=1802201963] timed out!
Slab corruption: start=ffff810039a96088, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff8020829a>](smb_add_request+0x41a/0x4c0)
010: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
150: 6b 6b 6b 6b 6b 6b 6b 6b 02 00 58 00 fb ff ff ff
Next obj: start=ffff810039a96200, len=352
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff80200bd1>](smb_proc_close+0x81/0xb0)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
....
Next obj: start=ffff810039a96ad0, len=352
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<ffffffff80207c36>](smb_alloc_request+0x46/0x120)
000: 00 c1 14 20 00 81 ff ff c0 6d a9 39 00 81 ff ff
010: 02 00 00 00 00 00 00 00 01 00 00 00 ad 4e ad de
smb_add_request: request [ffff810039a967e0, mid=60986] timed out!
smb_add_request: request [ffff810039a96378, mid=60987] timed out!
smb_lookup: find Musik/xxx (3 CD) failed, error=-5
smb_add_request: request [ffff810039a96dc0, mid=60988] timed out!
smb_add_request: request [ffff810039a96ad0, mid=60989] timed out!


cheers,
dominik
Comment 3 Diego Calleja 2006-08-05 07:01:01 UTC
SMBFS is being deprecated, you should be using CIFS instead (see
http://lwn.net/Articles/183693/
Comment 4 Natalie Protasevich 2007-07-06 18:32:19 UTC
Dominik, were you able to switch to CIFS and solve your problems this way?
Thanks.
Comment 5 Johan Bengtsson 2007-07-10 04:34:14 UTC
Yes, switching to CIFS solved the problem

Note You need to log in before you can comment on or make changes to this bug.