similar to: [BUG] Dovecot 2.2.21 crashing with assertion failed: (!have_wait_unfinished || unfinished_count > 0)

On 04.01.2016 11:54, Teemu Huovila wrote: > Thank you for the report. Could you execute "bt full" in gdb please. Also the output of doveconf -n would be useful. Hi, Requested info below. Florian bt f > #0 0x00007f6f99b8f5f8 in raise () from /usr/lib/libc.so.6 > No symbol table info available. > #1 0x00007f6f99b90a7a in abort () from /usr/lib/libc.so.6 > No symbol

Hi, I'm seeing the following in my logs. Twice so far, no idea what caused it. I do however have the core dump if that is of any use. > Jan 4 11:14:11 karif dovecot[20876]: imap(username): Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) > Jan 4 11:14:11 karif dovecot[20876]: imap(username): Error:

On 22 Jan 2016, at 12:36, Andre Helwig <a.helwig at heinlein-support.de> wrote: > > imap(p24062p6): Panic: file imap-client.c: line 852 > (client_check_command_hangs): assertion failed: (!have_wait_unfinished > || unfinished_count > 0) I think this was fixed by https://github.com/dovecot/core/commit/f136b0050b3125b466af73984177250b7ed1a3be

We're running Dovecot 2.2.21 from Stephan Bosch's build service on Dovecot 7.x. Everything's up2date. # 2.2.devel (7ab22fc): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.11 (71e908a) # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.9 root at mailimap01:/etc/dovecot/conf.d # apt-show-versions | grep dovecot debian-dovecot-auto-keyring/oldstable-auto uptodate 2010.01.30

> On 22 Jan 2016, at 15:07, Peer Heinlein <p.heinlein at heinlein-support.de> wrote: > > Am 22.01.2016 um 12:46 schrieb Timo Sirainen: > > >> I think this was fixed by https://github.com/dovecot/core/commit/f136b0050b3125b466af73984177250b7ed1a3be > > But our installed release ~2.2.21-1~auto+66 has been build on January, > 21th 13:58... So it should be

(Apologies for any duplication, yesterday's e-mail doesn't seem to have made it through moderation) I've had several recent crashes of the nouveau kernel driver over the past month or so. My suspicion is that Firefox is causing it. The screen goes black and then the computer reboots. Nothing much in the syslogs, however I've managed to get netconsole output. I've also run

Hi all! I've just recently noticed these lines in the dmesg output: Please enable the IOMMU option in the BIOS setup This costs you 64 MB of RAM they may have been there forever, but I never noticed them before. This system is an AMD Phenom-II X2 CPU on a Gigabyte MA770-UD3 motherboard. I have no idea which BIOS option I need to change to solve this, I see nothing in the setup that

I've had several recent crashes of the nouveau kernel driver over the past month or so. My suspicion is that Firefox is causing it. The screen goes black and then the computer reboots. Nothing much in the syslogs, however I've managed to get netconsole output. It happens very infrequently and I'm afraid I don't know how to reproduce it, however I'll be more than happy to

Hi, I work for a small company that makes radar systems for research organisations and we use FreeBSD on the PCs for data acquisition and processing. We have recently shifted to FreeBSD6/amd64 and one machine in particular is exhibiting a strange problem. The acquisition process is a Tcl interpreter with a largish chunk of C code which talks to the hardware (via RS485 and a custom PCI card).

Greetings, I have a samba server deployed. The machine has these: cpu: amd64 -4 cores motherboard :GA-990XA-UD3 with 6 sata ports and StarTech 2 Port SATA 6Gbps PCIe SATA Card memory: 16GBytes disks: raid 10 (6 disks) os: cblfs/linux kernel-3.1.5 pure 64bit and samba-3.6.0 The machine in deployed as a data-storage-device for windows7-based machines doing

Hi all, I''m not sure if this would be the right place to ask this since it''s about xenserver, still I want to exploit any help I can get ;) The Problem:As it turns out I can run 2 VM''s with passedthrough pci devices without any problems, but when I try to start a third one I get the "Internal error: xenopsd internal error: Xenctrl.Error("14: Bad

Hi! I'm building up a new computer and this evening have had several events during installation in which Anaconda has crashed. It's not clear that there is a lot of commonality between the different crashes. the first time I got all the way through package selection (selecting at the individual package level) before it crashed. the second time I made a mistake in partitioning and did

Dear mailinglist, I own a Gigabyte motherboard GA 970A UD3 with IOMMU support. Since the update XSA-36 (also part of the latest debian wheezy pkg), the IO-Virtualisation does not work any more as discussed on this mailinglist [0] and [1]. I like to ask, if there is an "official" solution in sight. I''m not sure about my alternatives. How "dangerous" is the

Hi all, I recently experienced a disk failure on my home server and observed checksum errors while resilvering the pool and on the first scrub after the resilver had completed. Now everything seems fine but I''m posting this to get help with calming my nerves and detect any possible future faults. Lets start with some specs. OSOL 2009.06 Intel SASUC8i (w LSI 1.30IT FW) Gigabyte

Hello, Like many trying and posting here, I''m new to VGA passthrough. Computer was bought, checking compatibility from http://wiki.xen.org/wiki/VTd_HowTo The hardware is mostly not exactly on the list, but mainly new versions of the same series (I think). IOMMU "seems" to be working (not 100% sure what to check). I used debian/wheezy kernel and xen, dom0 and HVM domu.

Just got another core-dump from Dovecot's imap process on our mail server. Dovecot 2.2.20 Solaris 10 / x86 Maildir Output from syslog: Dec 14 10:58:12 mail dovecot: [ID 583609 mail.crit] imap(oling): Panic: file imap-fetch.c: line 554: assertion failed: (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock == cmd) Dec 14 10:58:15 mail dovecot: [ID 583609

I have the same motherboard. The chipset has 2 IOAPICs: one in the NB (00:00.1), and another in the SB (00:14.0). As currently configured by the BIOS, the NB IOAPIC is _entirely_ disabled, with only the SB IOAPIC enabled and configured. From 48693.pdf, it would seem that the NB is improperly configured, as 6.4.1 recommends that "The IOAPIC should be enabled by the system BIOS and the

Hello, since applying the patches related to XSA-36 Xen recognizes a broken IVRS ACPI table and disables I/O virtualisation. I contacted the manufacturer of the mainboard/BIOS and they want to help me by providing a patched BIOS - so far so good. However, they need details about what to fix, which I don''t know either. Could you pls. give me some hints which I can forward to the

pid 31943 (dovecot), uid 0: exited on signal 11 (core dumped) dovecot --version 2.2.21 (5345f22) uname -a FreeBSD 10.3-BETA2 #0 r295966M: amd64 bt full #0 0x00000008008eb037 in t_push (marker=0x0) at data-stack.c:133 133 data-stack.c: No such file or directory. in data-stack.c (gdb) bt full #0 0x00000008008eb037 in t_push (marker=0x0) at data-stack.c:133 frame_block = (struct

dovecot --version 2.2.21 (5345f22) FreeBSD 10.2-RELEASE-p11 FreeBSD 10.2-RELEASE-p11 #0 r294908M: amd64 Core was generated by `dovecot'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/dovecot/libdovecot.so.0...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libc.so.7...Reading symbols from