search for: 184kb

Hello all, forgive me if this is old news but it seems to me that smbclient is prone to getting into an infinite loop when mget'ting a stack of files. I have tested (compiled from source with defaults) samba versions 3.0.10, 11, 12, 13, 14, 14a Versions prior to 3.0.13 are fine, in my environment, versions 3.0.13 and later are causing the problem. The basic data on my system is -a P4 3.2

...ex1 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: speex The following NEW packages will be installed: libspeex1 0 upgraded, 1 newly installed, 0 to remove and 10 not upgraded. Need to get 0B/75.3kB of archives. After this operation, 184kB of additional disk space will be used. Selecting previously deselected package libspeex1. (Reading database ... 22077 files and directories currently installed.) Unpacking libspeex1 (from .../libspeex1_1.1.12-3ubuntu0.8.04.1_i386.deb) ... Setting up libspeex1 (1.1.12-3ubuntu0.8.04.1) ... Processin...

...48 Apr 17 07:49:11 mail2 kernel: DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no Apr 17 07:49:11 mail2 kernel: lowmem_reserve[]: 0 0 880 4848 Apr 17 07:49:11 mail2 kernel: Normal free:3684kB min:3756kB low:4692kB high:5632kB active:184kB inactive:20kB present:901120kB pages_scanned:361 all_unreclaimable? yes Apr 17 07:49:11 mail2 kernel: lowmem_reserve[]: 0 0 0 31744 Apr 17 07:49:11 mail2 kernel: HighMem free:2863824kB min:512kB low:4748kB high:8988kB active:360868kB inactive:38568kB present:4063232kB pages_scanned:0 all_unrecla...

...ding dependency tree > Reading state information... Done > Suggested packages: > ?speex > The following NEW packages will be installed: > ?libspeex1 > 0 upgraded, 1 newly installed, 0 to remove and 10 not upgraded. > Need to get 0B/75.3kB of archives. > After this operation, 184kB of additional disk space will be used. > Selecting previously deselected package libspeex1. > (Reading database ... 22077 files and directories currently installed.) > Unpacking libspeex1 (from .../libspeex1_1.1.12-3ubuntu0.8.04.1_i386.deb) ... > Setting up libspeex1 (1.1.12-3ubuntu0.8....

...omain > raise exn > VmError: Failed to assign device to IOMMU > (0000:0e:00.0@100,msitranslate=1,power_mgmt=0) > > > xm dmes > ------------- > > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch > input to Xen) > (XEN) Freed 184kB init memory. > (XEN) mtrr: type mismatch for fb000000,800000 old: write-back new: > write-combining > (XEN) [VT-D]iommu.c:1461: d0:PCI: unmap bdf = e:0.0 > (XEN) [VT-D]iommu.c:1332: d1:PCI: map bdf = e:0.0 > (XEN) domctl.c:853:d0 XEN_DOMCTL_assign_device: assign device (e:0.0) &g...

Hello, I''m hoping someone may be able to push us in the right direction. I''m trying to get one of our products to work with the current branch of Xen (4.0/4.0.0) but I''m hitting a problem. We are currently using Xen 3.3.2 on a Sun Blade 600 chassis (with x6270 blades) this works great. But when we upgrade to Xen 4.0/4.0.1 we get the following message when

...(XEN) ******* timekeeping. It is NOT recommended for production use! (XEN) ********************************************** (XEN) 3... 2... 1... (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) (XEN) Freed 184kB init memory. With staring at the console I could see that the switch to the screen pattern is around the following messages (but no guarantee): (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.0 (...