similar to: DTMF Recognition

I have a Xen DomU configuration that was made in the days before libvirt and virt-install. In this configuration I have: vif = [ ''mac=00:16:3e:05:06:01, bridge=xenbr0'', ''mac=00:16:3e:05:06:0a, bridge=xenbr1'' ] and then in xend-config.sxp I define (network-script my-network-bridge) where my-network-bridge is in the scripts directory and looks like this:

I am posting the message below again because it did not go through last night. Help! Steve Timm -- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.

I have the xensource 3.1.0 x86_64 tarball installed over a RHEL5 clone distribution. The "ethtool" utility only returns the following information: [root@fermigrid5 etc]# ethtool eth0 Settings for eth0: Link detected: yes [root@fermigrid5 etc]# Since I have no vanilla-installed rhel5 machines with which to compare, I am not sure if I am dealing with a bug in the ethtool (whose

I''m running xen 3.1.2 as bastardized by RedHat on a redhat clone operating system. I''m using the xendomains script as it came out of the box to start my domU''s at boot and stop them at shutdown. There are three problems right now: 1) left to its own devices, service xendomains stop attempts to do "xm save" on each of the domU''s. that takes quite a

Hi LLVM-Devs, I have managed to complete updating our sources from LLVM v4.0 to v5.0, but I am getting selection errors for 'callseq_end'. I am aware that the 'ADJCALLSTACKUP' and 'ADJCALLSTACKDOWN' patterns have changed, and have added an additional argument to the TD descriptions for these. There are interactions with 'ISD::CALL' and 'ISD::RET_FLAG',

Hi Martin, Pseudo CALLSEQ_START was changed in r302527, commit message contains details on the changes. However CALLSEQ_END was not modified. If your made changes to ADJCALLSTACKUP to add additional argument, that may result in error. Thanks, --Serge 2017-09-15 19:09 GMT+07:00 Martin J. O'Riordan via llvm-dev < llvm-dev at lists.llvm.org>: > Hi LLVM-Devs, > > I have managed

Hi Serge, Thanks for your help. I have looked at the change log, and so far as I can tell, my implementation is pretty much identical to all of the in-tree targets, but I’m missing something and can’t see what it is. I have simplified my TD description to just: def MyCallseqStart : SDNode<"ISD::CALLSEQ_START", SDCallSeqStart<[SDTCisVT<0, i32>,

I have seen the following kernel panic 5 times today on three different machines, two of which had been stable for months and one of which is a brand new install. We are running the x86_64 xen kernel and userland tools that came in the Xen 3.1.0 tarball from xen.org, on top of scientific linux (redhat clone) 5.1 or 5.2. <Aug/28 12:21 pm>Unable to handle kernel NULL pointer dereference at

Has anyone yet figured out what it would take to make Xen run on top of the Red Hat Enterprise Linux 6 beta? We are heavily invested in Xen under RHEL5 (actually a redhat clone) distribution, but already the xen kernel they are shipping with update 4 and 5 is shaky and has bugs which they don''t seem to be in a hurry to fix. Basically I am wondering if Redhat 6 is just going to have

I have installed the xen 3.1.0 x86_64 tarball compiled for RHEL5 on a RHEL5 system. The system in question was able to boot with the xen kernel that came with RHEL5. I untarred the tarball, and did cd /boot mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen The command exited properly and made a initrd image. The machine booted with a grub.conf entry like this: title Xen 3.1.0 root

Does anyone know if the Xen 3.1.0 kernels as distributed in the "open source" tarballs (x86_64 version) are vulnerable to the recently-announced vulnerability CVE-2007-4573? IF so, is there any plan to release patched tarballs anytime soon? Thanks Steve Timm -- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov

I installed 64-bit xen 3.1.0 (from xensource.com tarballs) on three new machines today, using a configuration setup that I''ve used successfully many times before. However, I encountered a new problem. These are Dell Poweredge 1950 servers, by the way. >From lspci 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 08:00.0 Ethernet

Setup: RedHat/Centos/Sci. Linux 5 update 3, Dom0: kernel-xen-2.6.18-164.10.1.el5xen 64-bit (on Dell Poweredge 2950 dual quad-core). DomU: kernel-xen-2.6.18-164.10.1.el5xen 32-bit, 1 vcpu 6 domU''s per dom0. We have also seen the same problem with 2.6.18-164.9.1 and 2.6.18-164.6.1 kernels on this branch. Symptom: On 32-bit domU only (we have never seen 64-bit domU be affected), we observe

Hi On 5 October 2012 21:25, <X-Dimension at gmx.net> wrote: > > -------- Original-Nachricht -------- >> Datum: Thu, 4 Oct 2012 12:22:54 +0200 >> Von: Michael Wood <esiotrot at gmail.com> >> An: Julian Timm <X-Dimension at gmx.net> >> CC: samba at lists.samba.org >> Betreff: Re: [Samba] Samba-tool dbcheck shows "incorrect GUID" after

HI, guys Recently,I met a problem. Xen''s version: 3.4.3 guest os:redhat 4.8 32bit And xen.independent_wallclock = 1 has been set. The time of guest os change to be fast suddenly, about 2000 second. because the change is too wild, ntp didn''t sync to the ntp server''s time. my application is dependent on the systme time. And this occurs a lot of times. I don''t

I have never tried submitting a patch for anything previously, didn't know how to go about it with this particular software project (since the website has been down) and know little to nothing about git since I am stuck in a ClearCase world with work. Please find the previous patch, as an attachment. Sorry it is against 4.04, I have had no specific reason to update but it should still work.

Does anyone have any idea what is causing wineprefixcreate to fail with these messages? output from running wineprefixcreate: wine: Unhandled page fault on write access to 0x003ffd80 at address 0x60a3d103 (thread 0009), starting debugger... wine: Unhandled page fault on write access to 0x003ffd80 at address 0x60a3d103 (thread 000b), starting debugger... err:seh:raise_exception

>Date: Fri, 2 May 2003 10:03:23 -0400 (EDT) From: Morten Welinder <welinder@rentec.com> >To: p.dalgaard@biostat.ku.dk >CC: r-devel@stat.math.ethz.ch, R-bugs@biostat.ku.dk >Subject: Re: [Rd] qbeta hang (PR#2894) > >Ok, I can confirm that it does not, in fact, loop forever. Just a close >approximation. ... >There are lots of other places that worry me with respect to

I saw a post by Timm Gleason back in Oct. 2011 - http://www.syslinux.org/archives/2011-October/016928.html This would also be handy for something I'm doing, but my group is leery of "owning" syslinux in order to incorporate this patch. I did a quick test to my own build, and it seemed to work well. What would it take to get this incorporated into a future syslinux release? Is

Hi Gurus. I searched the lists, wiki and the rest of the web but I still do not understand this. My Setup is as follows: [ISDN via chan_capi or IAX2 DiD Provider] => [* PBX] => [IAX2 Clients (Atcom AT-320ED)] I want to get callgroup/pickupgroup and callwaiting working on the IAX phones. Some web sources told me that this was not implemented, others say that the phone has to handle