similar to: imposing constraints on the covariance matrix of random effects in lme4?

Hi All I can specify whatever inits, it has no effect on the estimation. I am replicating a textbook example. The result is completely trash, having estimates of -58.7 (sd=59.3), where it should be closer to an ml estimate of 0.585 (SE=0.063). The two chains within one run are different, but with different inits for different runs, I get exactly the same chains, and I mean exactly. If I set

Full_Name: MJ Ray Version: 0.99.0a OS: Linux 2.2.13 Slackware 7.0 Submission from: (NULL) (195.7.239.50) I consistently get a sig11 on one file: gcc -I. -I../include -I../../src/include -I../../src/include/R_ext -DHAVE_CONFIG_H -mieee-fp -g -O2 -c fft.c -o fft.o gcc: Internal compiler error: program cc1 got fatal signal 11 make[3]: *** [fft.o] Error 1 However, other files and parts of the

Sometimes I'll get an email from a luser which will cause the POP3 daemon to sig11. The email "appears" to be legal. The sig11s only happen on specific emails, and once I remove the emails from the server, the rest can be downloaded. I gzipped the email, and its at http://theapt.org/bogusemail.gz. While this example is international spam, the sig11s happen with real emails too.

This happened from one user near noon on the 17th and 19th (today) of this month. From the backtrace it looks like they were searching, but I won't know for sure unless I need to ask them. Is this possibly fixed already? I just haven't upgraded dovecot in a while due to lack of problems. The sig11 happened a few dozen times, a few seconds apart each day. I have one coredump from

Hi all! This is my first post on this list. Please pardon me if I overlooked or misunderstood some things. I had some imap crashes (sig11) starting at the end of 2019 after an upgrade of dovecot. I found out, that I didn't have any problems using version v2.3.8, but any version v2.3.9 and higher would trigger the crashes. After investigating more deeply and creating a core dump, I saw that

Hi! On 2020-06-16 12:37 -0000, Stuart Henderson wrote: > On 2020-06-15, Alexander Strasser <eclipse7 at gmx.net> wrote: > > I had some imap crashes (sig11) starting at the end of 2019 after > > an upgrade of dovecot. > > > > I found out, that I didn't have any problems using version v2.3.8, > > but any version v2.3.9 and higher would trigger the crashes.

Hi all, We recently moved our CVS repository from a 4.6-STABLE machine to a brand new 4.8 install, on another identical machine. The server runs cvs in 'pserver' mode, for remote access by various Windows/Solaris/Linux/FreeBSD clients. We pretty soon noticed that the cvs server process was occasionally crashing on sig11 (ie. a segfault). The only evidence for this was in the message

Hi, Here is the backtrace. -- Nico Que de tout inconnu le sage se m?fie. -+- Jean de La Fontaine (1621-1695), Le Renard, le Loup et le Cheval (Fables XII.17) -+- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Dovecot-1.0-test57-backtrace URL:

When I compile the latest CVS, I get the following error: Compiling param/params.c gcc.colorgcc: Internal compiler error: program cpp got fatal signal 11 make: *** [param/params.o] Error 1 What did I do wrong?? Stephen Gerstacker The Gradall Company phone: 339-2211 ext. 8814 ******************************************************* The information contained in this transmission is

Linux 2.2.13 Intel samba-2.0.7pre2 will Sig11 and die on me right after processing NetBIOS name = FOO in smb.conf. Not always, but sometimes I have to start smbd 2 or 3 times. It always fails there. Any reason why 2.0.7pre2 would do this, and 2.0.6 (from rpm) never did? -- Edward Schernau http://www.schernau.com Network Architect mailto:ed@schernau.com Rational Computing Providence, RI,

I downloaded the latest wine from the cvs site and ran its ./tools/wineinstall. It ran for quite a while and croaked on /wine/server/semaphore.c. Basically, gcc says "Internal compiler error: program cc1 bog fatal signal 11". The compiler is 2.91.66 (aka egcs-1.1.2 release) and compiles other programs including 2.4.1 & 2.4.2 Linux kernels just fine. I am puzzled what 'fatal

Hi, I have a bivariate longitudinal dataset. As an example say, i have the data frame with column names var1 var2 Unit time trt (trt represents the treatment) Now suppose I want to fit a joint model of the form for the *i* th unit var1jk = alpha1 + beta1*timejk + gamma1* trtjk + delta1* timejk:trtjk + error1jk var2 = alpha2 + beta2*timejk + gamma2* trtjk + delta2* timejk:trtjk +

Hi, I am consistently getting a signal 6 error compiling passdb.c on a certain machine. It seems to compile fine on other machines so I wonder if it might be hardware related? Compiling passdb/passdb.c gcc: Internal compiler error: program cc1 got fatal signal 6 make: *** [passdb/passdb.o] Error 1 Since it seems to be machine specific I have to assume hardware but I don't have problems with

System info: ------------ [root@angel root]# cat /etc/issue Red Hat Linux release 7.2 (Enigma) Kernel \r on an \m [root@angel root]# uname -a Linux angel 2.4.9-34 #1 Sat Jun 1 06:25:16 EDT 2002 i686 unknown This problem occured after upgrade to kernel 2.4.18-17.7, backed out to previous version now (2.4.9-34). All other system RPMs are up to date according to RHN, and nothing, aside from

I am experiencing a problem with all time stamps having the same date and time stamp. I found this bug report http://us1.samba.org/listproc/samba/June1998/0239.html and see there is a fix. The question I have is has this issue been resolved in later versions of Samba code. It would be easier to upgrade than deal with a code change and re compilation. Scott Ranzal -------------- next part

I can't get recent cvs versions to compile. After running cvs update -PAd and ./tools/installwine I get these messages gcc: Internal compiler error: program cc1 got fatal signal 11 make[2]: *** [ordinal.o] Error 1 make[2]: Leaving directory `/usr/local/src/wine/dlls/shlwapi' make[1]: *** [shlwapi/shlwapi.dll.so] Error 2 make[1]: Leaving directory `/usr/local/src/wine/dlls' make: ***

For quite some time I have seen dovecot imap exit with a sig11 without any other error message, but usually with the frequency of between once per week and once per day (per server). A few weeks ago I finally enabled core dumping with debug symbols and it seemed to happen less often. I finally caught a coredump that wasn't overwritten. I have no idea what on the client end may cause it,

We have here an knfs fileserver running ext3 on 2.4.18 kernel with three filesystems: <CLIP> Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda3 10080520 3609632 6368476 37% / /dev/hda4 16437332 12295408 3974932 76% /home /dev/md1 1024872060 409906136 614441636 41% /fs </CLIP> The /fs filesystem lives on a

Hello. When trying to sort a folder by thread (with pine4.61), I get a sig11. The mailstore is Maildir, indexes stored in /var/indexes/%u. The syslog on the server shows this: Nov 29 11:37:55 olan dovecot: IMAP(kowalski): Corrupted index cache file /var/indexes/kowalski/.INBOX/dovecot.index.cache: record points outside file Nov 29 11:37:56 olan dovecot: child 14344 (imap) killed with signal 11

Hello. My smbd dies with SIG11. This occurs in 1.9.18p10 as well in 2.0.0beta2. I've read the Samba archive and found the article "Re: 1.9.17p4 - SIGNAL 11 error ??" from Luke and recompiled it with "-g -g". Here the results: After a "smbclient -L localhost" or any other tries to connect to the server the server dies an --- output of "gdb smbd core"