search for: unwedged

I'm having a problem with the dovecot server. I've upgraded to 1.0rc7 to no avail. My naive view is that a cache file is corrupt, or a lock file cannot be unset. Certain mailboxes cannot be accessed to read or write. Checking the process, the server looks stuck in an infinite poll/wait loop. telnetting directly to the server shows that things are definately amiss, though the original

A few hours ago I downloaded .../i386/ISO-IMAGES/4.9-RC1-i386-disc1.iso and made kern/mfsroot floppies from it. If I enable my ICH5R SATA controller in "native" mode, the 4.9-RC1 GENERIC kernel hangs solidly (only the system reset button can unwedge it) during device configuration. The last line of bootstrap monologue written by the kernel is: plip0" <PLIP network

...> I don't have much of an explanation for this. I would suggest > specifying all three (build/host/target) parameters if you're running > into this problem. It might help in the short term while we figure out > the issue. I've been doing that all the time, and it got LLVM unwedged. It wasn't enough to get LLVM-GCC to compile though. > > 3) On a 64-bit Ubuntu, setting --build/host/target=i686-pc-linux-gnu > > will work when compiling with gcc, but llvm-gcc will try to feed 64-bit > > machine code to the assembler in this situation. At least that's w...

I don't know if this was present (maybe not?) when the script was written, but the script for taking a snapshot in the instructions for shadow_copy: that looks like this: ---- xfs_freeze -f /home/ lvcreate -L10M -s -n $SNAPNAME /dev/Home/lvol0 xfs_freeze -u /home/ mkdir /home/shadow_share/@GMT-$SNAPNAME mount /dev/Home/$SNAPNAME \ /home/shadow_share/@GMT-$SNAPNAME -onouuid,ro ----

.../Mailman/ListAdmin.py", line 146, in HoldMessage self.__opendb() File "/var/lib/mailman/Mailman/ListAdmin.py", line 70, in __opendb self.__db = marshal.load(fp) EOFError: EOF read where object expected The solution was to delete the request.db (or at least move it), which unwedged mailman mostly. The final solution was to run ''listzap'' by Wichert Akkerman, which zonked the outstanding requests database, allowing the mailman administrative website to function again. Thanks Wichert! Anyhow, happy LARTC-ing! -- http://www.PowerDNS.com Open source, data...

A warning to those considering to upgrade to Debian 10 (buster): we have seen occasional NFS hangs with dovecot when using the stock debian buster kernel (4.19.67-2+deb10u1). When we downgrade to the debian stretch kernel (4.9.189-3+deb9u1), the issue does not occur. Note that we *only* downgraded the kernel, the rest of the OS is still debian buster. Dovecot 2.3.8. A little more info: we have a

...ve much of an explanation for this. I would suggest >> specifying all three (build/host/target) parameters if you're running >> into this problem. It might help in the short term while we figure out >> the issue. > > I've been doing that all the time, and it got LLVM unwedged. > It wasn't enough to get LLVM-GCC to compile though. > >> > 3) On a 64-bit Ubuntu, setting --build/host/target=i686-pc-linux-gnu >> > will work when compiling with gcc, but llvm-gcc will try to feed 64-bit >> > machine code to the assembler in this situation....

On Tue, May 13, 2008 at 2:24 AM, Joachim Durchholz <jo at durchholz.org> wrote: > > Am Dienstag, den 13.05.2008, 00:42 -0700 schrieb Bill Wendling: >> Sorry to step into this in the middle of a thread, but what exactly is >> LLVM's autoconf doing that "autoconf shouldn't do if properly set up"? > > 1) Variables like CC, CXX, CFLAGS don't work

Am Dienstag, den 13.05.2008, 00:42 -0700 schrieb Bill Wendling: > Sorry to step into this in the middle of a thread, but what exactly is > LLVM's autoconf doing that "autoconf shouldn't do if properly set up"? 1) Variables like CC, CXX, CFLAGS don't work properly when submitted via the command line. The handling seems to be inconsistent, i.e. it seems that parts of

A new intel-gpu-tools quarterly release is available with the following changes: General changes: - Bumped used C standard to gnu11. (Lucas De Marchi) - Bumped required meson version to 0.44. (Petri Latvala) - Introduced meson options for explicit control over optional dependencies. (Petri Latvala) - Added a meson option to set runpath for the installed executables. (Petri Latvala) -

A new intel-gpu-tools quarterly release is available with the following changes: Library changes: - Various changes to library functions so that they don't assume Intel hardware. (Lyude) - Added helper functions for managing synchronization primitives. (Robert Foss) - Added support for the new generic CRC capture kernel ABI. (Tomeu Vizoso) - Added Geminilake platform support. (Ander

...drag misha in [23:12] <DannyB> okey [23:12] <sabre> Thanks Dan! [23:13] <brg> i think i'll at least update to 2.16.5 [23:13] <sabre> brg: that would be cool [23:15] <sabre> brg: did you just do something to bugzilla? [23:15] <sabre> It seems like it just got unwedged or something [23:15] <brg> yup, i upgraded it to 2.16.5, and fixed the sanity check error that i got [23:15] <sabre> already?? [23:15] <brg> i think it let loose with a bunch of old mail [23:15] <sabre> ya [23:15] <brg> yeah it's pretty easy to do the minor upgrade...

A new intel-gpu-tools quarterly release is available with the following changes: Library changes: - Added helpers for launching external processes and capturing their outputs. (Abdiel Janulgue) - Increased max pipe count to 6 to support AMD GPUs. (Leo (Sunpeng) Li) - Various improvements for Chamelium support. (Paul Kocialkowski) - Added Coffeelake platform support. (Rodrigo Vivi, Anusha