search for: mishap

...mean (audio test failed) it failed to detect sound drivers or that it failed to implement it's own drivers (i.e. alsa, oss and what not) or something else? 3, What needs to be done now (I'm new to Linux so I don't even know whether this is an issue of missing components, configuration mishap or a bug).

I am attempting to plot a trellis object on a grid. vplayout = viewport(layout.pos.row=x, layout.pos.col=y) grid.newpage() pushViewport(viewport(layout=grid.layout(2,2))) g1 = ggplot() ... g2 = ggplot() ... g3 = ggplot() ... p = xyplot() ... # works as expected print(g1, vp=vplayout(1,1)) print(g2, vp=vplayout(1,2)) print(g3, vp=vplayout(2,1)) # does not work print( p,

Evening all, I''m new to Solaris but after drooling over zfs for ages I finally took the plunge. First off I had 2x1Tb hdd in raid1 XFS format using mdadm, so using a opensolaris vm image I transfered one side of the mirror to the other in zfs. (using rsync and it took 3days!) So with a 1 disk zpool carrying all my data I brought both the drives over in a new box, all going swimmingly

...regression tests [[[ etc ]]] I'm curious about the "creating library" message popping out twice. Sometimes ninja builds will die on me, complaining about a corrupted object file, usually related to LTO. Rerunning ninja usually completes successfully. So I wonder if there's some mishap in the dependencies somewhere that actually causes the build to try to link the DLL twice, which of course might corrupt a file if the links are overlapping in time. Thought I'd throw this out there in case someone wants to take a look. --paulr

...one phrase was being commanded by the existing extensions_additional.conf file. I re-edited the file, updated, and things worked again. !!!? What happened to my edited, updated, and Re-Read extensions_additional.conf file? Anybody ever encounter this behavior? What to do, in order to avoid this mishap in the future? Ideas, thoughts? Thanks, Jim Hanlon

...gt; I'm curious about the "creating library" message popping out twice. >> Sometimes ninja builds will die on me, complaining about a corrupted >> object file, usually related to LTO. Rerunning ninja usually completes >> successfully. So I wonder if there's some mishap in the dependencies >> somewhere that actually causes the build to try to link the DLL twice, >> which of course might corrupt a file if the links are overlapping in >> time. >> >> Thought I'd throw this out there in case someone wants to take a look. >> --pa...

Whilst always using the DMA API is OK on ARM systems in most cases, there can be a problem if a hypervisor fails to tell its guest that a virtio device is cache-coherent. In that case, the guest will end up making non-cacheable mappings for DMA buffers (i.e. the vring), which, if the host is using a cacheable view of the same buffer on the other end, is not a recipe for success. It turns out that

Whilst always using the DMA API is OK on ARM systems in most cases, there can be a problem if a hypervisor fails to tell its guest that a virtio device is cache-coherent. In that case, the guest will end up making non-cacheable mappings for DMA buffers (i.e. the vring), which, if the host is using a cacheable view of the same buffer on the other end, is not a recipe for success. It turns out that

Hi Galina, I have observed that some of my bots timeout for no apparent reason (no external load, no network mishaps, no issues), and when I go to check the buildslave process, I see that it has just being restarted. Do you know what could be causing this? Swap is untouched, plenty of disk left, CPUs a plenty. So, I'm contemplating the possibility that the master lost connectivity to it and didn't get...

...we want to move folder test into his subfolder test1 (nonsense action, but quite a few employees trying to do that...) Outlook displays error message subscriptions shows correctly: test test1 BUT the directory structure of maildir is .test.test1.test.test1 .test.test1.test.test1.test Is this a mishap of Dovecot or Outlook? Regards, Knut

In August Peter commented that the klibc git repo had a severely corrupted commit: http://www.zytor.com/pipermail/klibc/2009-August/002440.html Is the repo intact and we can just ignore that mishap? Or does this indicate a more severe problem? Depending on the answer to that, I suppose, would you consider making a release? I sent my DHCP patches in April and it would be nice to see them eventually in distros. Thanks, Aron

...can look at /proc/mdstat to see its status, > although from what I remember from previous posts, it's better to just > let the BIOS think it's a JBOD and use the linux software RAID tools > directly. > I see, thank you. Right now I am running off one of the disks because of the mishap, I am also waiting for a systemboard replacement at which time I can decided whether to go with Linux software RAID, ie mdadm, or back to the Intel BIOS RAID. The latter lacks any progress indicators in BIOS when rebuilding an array which took around 20 hours for a 256 GB RAID 1 setup and it is an...

(Fixed the cfe email address) On 12/18/2015 09:34 PM, Tim Northover wrote: > On 18 December 2015 at 19:15, Richard Pennington via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> It turns out that it can with some simple patches. > This sounds really cool. I think we should seriously consider putting > these patches into LLVM mainline. > >> Information on

...c ]]] > > I'm curious about the "creating library" message popping out twice. > Sometimes ninja builds will die on me, complaining about a corrupted > object file, usually related to LTO. Rerunning ninja usually completes > successfully. So I wonder if there's some mishap in the dependencies > somewhere that actually causes the build to try to link the DLL twice, > which of course might corrupt a file if the links are overlapping in > time. > > Thought I'd throw this out there in case someone wants to take a look. > --paulr > > __________...

I got this error when I tried to install the package in order to use the "logit"(logit transformation) function on linux. > install.packages(car) Error in install.packages(car) : object 'car' not found I was using the Terminal in my macbook accessing the server in the lab. I could successfully using library(car) to install this package use R.app GUI in my laptop, after

...so much more flexible. They got pushed to the bottom of my change list, and then completely forgotton. 4. In the last few weeks issues with anova.coxph, and predict.coxph/factors/newdata were raised. The fixes were added to Rforge last night, and include 2 new test cases to avoid future mishaps. Terry T.

...in! I know that the designers tried to build in safeguards (from the man page): the `=' is only allowed at the top level (that is, in the complete expression typed by the user) or as one of the subexpressions in a braced list of expressions. These safeguards don't prevent the mishap shown above. Is there any way to detect this case syntactically (check for assignments inside subsetting operations??), or will I just have to train my students to watch out for this possibility? ---- 318 Carr Hall bolker@zoo.ufl.edu Zoology Department, Universit...

On Tue, Jan 2, 2018 at 10:10 AM, Akemi Yagi <toracat at elrepo.org> wrote: > > On Thu, Dec 7, 2017 at 6:23 AM, Stijn De Weirdt <stijn.deweirdt at ugent.be> wrote: >> latest kmod update 20-15.el7_4.6 is broken on our systems, while >> previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue). >> >> the issue is with modules from mellanox

...regression tests [[[ etc ]]] I'm curious about the "creating library" message popping out twice. Sometimes ninja builds will die on me, complaining about a corrupted object file, usually related to LTO. Rerunning ninja usually completes successfully. So I wonder if there's some mishap in the dependencies somewhere that actually causes the build to try to link the DLL twice, which of course might corrupt a file if the links are overlapping in time. Thought I'd throw this out there in case someone wants to take a look. --paulr _______________________________________________...

...ise. This does not affect devices setting the VIRTIO_F_IOMMU_PLATFORM flag, which as before are still at the mercy of architecture code correctly knowing their coherency, so explicitly call this out in the virtio-mmio DT binding in the hope of heading off any further workarounds for future firmware mishaps. Fixes: c7070619f340 ("vring: Force use of DMA API for ARM-based systems with legacy devices") Signed-off-by: Robin Murphy <robin.murphy at arm.com> --- Documentation/devicetree/bindings/virtio/mmio.txt | 3 +++ drivers/virtio/virtio_ring.c | 11 ++++++++---...