search for: 65s

********************************************************************** Este email assim como os ficheiros que possa ter em anexo s?o confidenciais e para uso exclusivo da pessoa ou organiza??o para o qual foi enviado. Se recebeu este email por engano por favor notifique Redes@bnc.pt Esta nota confirma que esta mensagem foi verificada pelo MIMEsweeper n?o tendo sido encontrados virus.

...DR+C$V."XQ+B Q,C<N#0H-"EMP=6)L:6-=#0H@(" @(" @('!A M=&@@(" @(" @(" @(" @(" @(" @(#T@+VAO;64O9G1P+W!U8@T*(" @(" @ M("!B<F]W<V5A8FQE(" @(" @(" @(" @(" ]('EE<PT*(" @(" @("!G=65S M="!O:R @(" @(" @(" @(" @(" ]('EE<PT*(" @(" @("!R96%D(&]N;'D@ M(" @(" @(" @(" @(" ]('EE<PT*#0I;=7-E<ET-"B @(" @(" @<&%T:" @ M(" @(" @(" @(" @(" @("...

...uot;@S-# I"B @57-E<B!N86UE.B!N;V)O9'D)4F5A;"!N M86UE.B!.;V)O9'D*6S(P,#,O,3$O,3D@,C Z,30Z,#0L(#-=('-M8F0O<')O M8V5S<RYC.F-H86EN7W)E<&QY*#$P,C,I"B @0VAA:6YE9"!M97-S86=E"ELR M,# S+S$Q+S$Y(#(P.C$T.C T+" S72!S;6)D+W!R;V-E<W,N8SIS=VET8VA? M;65S<V%G92@V.#4I"B @<W=I=&-H(&UE<W-A9V4@4TU"=&-O;E@@*'!I9" R M.3,W,RD*6S(P,#,O,3$O,3D@,C Z,30Z,#0L(#-=('-M8F0O<V5C7V-T>"YC M.G-E=%]S96-?8W1X*#,R.2D*("!S971T:6YG('-E8R!C='@@*# L(# I("T@ M<V5C7V-T>%]S=&%C:U]N9'@@/2 P&qu...

...39;'access=w,vdev=xvda1,backend=storage,target=/root/domsi.img''] And I got this console log - [ 5.588091] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 270.588319] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, r...

...39;'access=w,vdev=xvda1,backend=storage,target=/root/domsi.img''] And I got this console log - [ 5.588091] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 270.588319] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, r...

...)%9%4D)/4T4@/2!Y97, at 73L@=&AE;@H) M"65C:&\@+6X@(B0P.B!.;W1I8V4Z($=E='1I;F<@8V]R92!D=6UP<R!I;B`D M1$E2(&]F("0Q('!R;V-E<W-E<SHB(#XF, at H)("`@(&9I"@D@("`@9F]R(%!) M1"!I;B`D4$E$4SL at 9&\*"0EI9B!;("1615)"3U-%(#T@>65S(%T[('1H96X* M"0D@("`@96-H;R`M;B`B("10240B(#XF, at H)"69I"@D)9V-O<F4 at +6,@(B1$ M25(O8V]R92XD4$E$(B`B)%!)1"(*"2`@("!D;VYE"@D@("`@:68 at 6R`D5D52 M0D]312`]('EE<R!=.R!T:&5N"@D)96-H;R`B(B`^)C(*"2`@("!F:0H)9FD* M("`...

...ck in the function is another idea, but I am not sure if that is possible (I don't think this is currently supported). This brings down the compilation time (using clang -emit-llvm) from 350s to 30s (it still takes about 23s to do GVN). It also might fix PR17855 (the program that used to take 65s to compile now takes just 11s): http://llvm.org/bugs/show_bug.cgi?id=17855 2. Cache the ordering of loads and stores in LoadAndStorePromoter::run. I don't know how hard it would be to implement this, but I think it would be as fast as 1 (using mem2reg). 3. Insert a pass that splits huge b...

...mWg7M9/AAAB&gt;: Info: net_connect_unix(/var/run/dovecot/imap-master) failed: Permission denied in=28 out=724 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Mar 09 13:26:42 imap-login: Info: proxy(q2 at a.com): disconnecting 192.168.14.1 (Disconnected by server(65s idle, in=244, out=865)): user=<q2 at a.com&gt;, method=PLAIN, rip=192.168.14.1, lip=192.168.14.11, session=<BadPNmWgePTAqA4B&gt; Mar 09 13:26:42 imap-login: Info: Login: user=<q2 at a.com&gt;, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=90413, secured, session=<ZVKPP2Wg...

...nstall a suse11 pv guest on redhat5.2 virtualization platform. But the startup process hung with messages: xen-vbd: registered block device major 202 xvda:<6>netfront: Initialising virtual ethernet driver. XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...<6>Uniform Multi-Platform E-IDE driver SCSI subsystem initialized st: Version 20080504,...

I got roughly the same performance results when I use the openssl speed test with and without a hifn 7956 cryto card Here's what I did: After the card is plugged in, kldload hifn; kldload cryptodev; I got the message: hifn0 mem 0xfc8f0000-0xfc8f7ffff, 0xfc8f0000-0xfc8f7ffff, 0xfc8f0000-0xfc8f7ffff irg 28 at device 3.0 on pci1 hifn0: Hifn 7956, rev 0, 32KB dram, pll=0x800<pci clk, 4x

All, using Samba as an AD (2k12) domain member in Stretch (2:4.5.12+dfsg-2+deb9u4) with tdb as default and rid as domain backend. No overlapping. Everything works fine. Setup was done as in the wiki [1]. If you're connecting from a Windows 10 client and do not add dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and keytab winbind refresh tickets = Yes to

...core: registered rtc_cmos as rtc0 [ 0.976298] No iBFT detected. [ 0.976641] TCP cubic registered [ 0.976647] NET: Registered protocol family 17 [ 0.976739] registered taskstats version 1 [ 6.077230] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s......

...ice nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s......

...oft lockup - CPU#3 stuck for 33s! [swift-object-up:11358] Message from syslogd at amer at Jan 27 19:33:55 ... kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 24s! [dmeventd:71548] Message from syslogd at amer at Jan 27 19:34:25 ... kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 65s! [kworker/2:0:59993] Message from syslogd at amer at Jan 27 19:37:50 ... kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 24s! [kworker/u256:3:8447] Message from syslogd at amer at Jan 27 19:37:50 ... kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [ksoftirqd/5:34] Message...

...&-H96-K:6YG(&9O<B!A('-E9"!T:&%T(&1O97,@;F]T M('1R=6YC871E(&]U='!U= IC;VYF:6=U<F4Z,3DU-3H at 8VAE8VMI;F<@=VAE M=&AE<B!L;B M<R!W;W)K<PIC;VYF:6=U<F4Z,3DW-CH at 8VAE8VMI;F<@:&]W M('1O(')E8V]G;FES92!D97!E;F1E;G0@;&EB<F%R:65S"F-O;F9I9W5R93HR M,38R.B!C:&5C:VEN9R!F;W(@;V)J96-T('-U9F9I> IC;VYF:6=U<F4Z,C$X M.#H at 8VAE8VMI;F<@9F]R(&5X96-U=&%B;&4@<W5F9FEX"F-O;F9I9W5R93HR M,C(Y.B!C:&5C:VEN9R!C;VUM86YD('1O('!A<G-E("]U<W(O8FEN+VYM("UP M(&]U='!U= IC;VY...

...ave stabilized), you can't > trust it. [even then, I don't remember if ntp is accurate enough for this]. > > > > Andrew Kohlsmith wrote: > > >I've been keeping an eye on the jitter buffer ever since upgrading and using > >Steve's patch to fix the 65s dead air problem but I've been noticing > >something... > > > >... Asterisk frequently gets "lag" and "jitter" mixed up. > > > >This directly affects the jitter buffer, as the jitter buffer only grows when > >jitter grows. > > Hi...

...&EL M:6YG(&QI8G-M8B]C;&EE;G1G96XN8PT*0V]M<&EL:6YG(&QI8G-M8B]C;&EC M;VYN96-T+F,-"D-O;7!I;&EN9R!L:6)S;6(O8VQI9FEL92YC#0I#;VUP:6QI M;F<@;&EB<VUB+V-L:7)A<"YC#0I#;VUP:6QI;F<@;&EB<VUB+V-L:65R<F]R M+F,-"D-O;7!I;&EN9R!L:6)S;6(O8VQI;65S<V%G92YC#0I#;VUP:6QI;F<@ M;&EB<VUB+V-L:7)E861W<FET92YC#0I#;VUP:6QI;F<@;&EB<VUB+V-L:6QI M<W0N8PT*0V]M<&EL:6YG(&QI8G-M8B]C;&EP<FEN="YC#0I#;VUP:6QI;F<@ M;&EB<VUB+V-L:71R86YS+F,-"D-O;7!I;&EN9R!L:6)S;6(O8VQI<V5C9&5S M8RYC#0I#;V...

...eling driver [ 0.260194] NET: Registered protocol family 17 [ 0.260213] Bridge firewalling registered [ 5.360075] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s... 205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s... 150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s... 95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s... 35s...30s...25s...20s...15s...10s...5s...0s... [ 270.360180] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3...

On CentOS5 with the latest updates applied, the logwatch filter for postfix returns way too many lines from the log. I get an "unmatched entries" message and all messages that have gone through the system is listed. Here is an example: 8F930A8092: to=<morten at foo.bar>, orig_to=<morten at localhost>, relay=local, delay=0.19, delays=0.06/0.01/0/0.12, dsn=2.0.0,

...idea, but I am not sure if that is possible (I don't think this > is currently supported). > > > This brings down the compilation time (using clang -emit-llvm) from 350s > to 30s (it still takes about 23s to do GVN). It also might fix PR17855 (the > program that used to take 65s to compile now takes just 11s): > > > http://llvm.org/bugs/show_bug.cgi?id=17855 > > Chandler commented here, I'll defer to him. > > > 2. Cache the ordering of loads and stores in LoadAndStorePromoter::run. > I don't know how hard it would be to implement this,...