similar to: i8253 count too high! resetting

I'm trying to get a souped-up test machine(G5 Xserve) from Terrasoft to do some testing in a few weeks. If/when I actually get it I'll certainly post the results here. In theory the G5 should mop the floor with the Intel for high-volume Asterisk Zaptel usage, and I have heard from several Mac-heads that they have run three quad T1 digium cards on the Mac platform with no problems.

I would like to integrate * with an existing Altigen PBX. I want to spend as little money as possible to make it happen. My main goal is to inexpensively connect a branch office to the phone system. Eventually I would like to replace the Altigen system with an Asterisk server so I don't want to spend any money on Altigen hardware. Currently the Altigen has analog interfaces with a couple

Did you get this working I'm having the same issues. Sean -----Original Message----- From: Geoff Nordli [mailto:geoffn@gnaa.net] Sent: 22 September 2004 18:29 To: 'Asterisk Users Mailing List - Non-Commercial Discussion' Subject: [Asterisk-Users] make update and upgrade failed with `ZT_EVENT_POLARITY' undeclared Hello everyone. I am trying to do a cvs update. I do the make

Anyone have any experience with a R510 with the PERC H200/H700 controller with ZFS? My perception is that Dell doesn''t play well with OpenSolaris. Thanks, Geoff

I am trying to configure a system where I have two different NFS shares which point to the same directory. The idea is if you come in via one path, you will have read-only access and can''t delete any files, if you come in the 2nd path, then you will have read/write access. For example, create the read/write nfs share: zfs create tank/snapshots zfs set sharenfs=on tank/snapshots root

I am considering a G5/XServe for a conferencing system. I need to put a TDM card in the machine for timing. Is anyone out there using Asterisk on Mac with zaptel drivers? I am looking at using Linux for the OS. If so what is your experience? Have a great day! Geoff

Hi Everyone. Asterisk is one of those applications that need to be built from cvs on a regular basis to keep up with the changes. I have always used package management tools like apt. How does everyone manage their Asterisk servers? Geoff

Commit-ID: 35b69a420bfb56b7b74cb635ea903db05e357bec Gitweb: https://git.kernel.org/tip/35b69a420bfb56b7b74cb635ea903db05e357bec Author: Michael Kelley <mikelley at microsoft.com> AuthorDate: Sun, 4 Nov 2018 03:48:54 +0000 Committer: Thomas Gleixner <tglx at linutronix.de> CommitDate: Sun, 4 Nov 2018 11:04:46 +0100 clockevents/drivers/i8253: Add support for PIT shutdown quirk

4.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Michael Kelley <mikelley at microsoft.com> commit 35b69a420bfb56b7b74cb635ea903db05e357bec upstream. Add support for platforms where pit_shutdown() doesn't work because of a quirk in the PIT emulation. On these platforms setting the counter register to zero causes the PIT to start

4.19-stable review patch. If anyone has any objections, please let me know. ------------------ From: Michael Kelley <mikelley at microsoft.com> commit 35b69a420bfb56b7b74cb635ea903db05e357bec upstream. Add support for platforms where pit_shutdown() doesn't work because of a quirk in the PIT emulation. On these platforms setting the counter register to zero causes the PIT to start

4.18-stable review patch. If anyone has any objections, please let me know. ------------------ From: Michael Kelley <mikelley at microsoft.com> commit 35b69a420bfb56b7b74cb635ea903db05e357bec upstream. Add support for platforms where pit_shutdown() doesn't work because of a quirk in the PIT emulation. On these platforms setting the counter register to zero causes the PIT to start

4.14-stable review patch. If anyone has any objections, please let me know. ------------------ From: Michael Kelley <mikelley at microsoft.com> commit 35b69a420bfb56b7b74cb635ea903db05e357bec upstream. Add support for platforms where pit_shutdown() doesn't work because of a quirk in the PIT emulation. On these platforms setting the counter register to zero causes the PIT to start

4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Michael Kelley <mikelley at microsoft.com> commit 35b69a420bfb56b7b74cb635ea903db05e357bec upstream. Add support for platforms where pit_shutdown() doesn't work because of a quirk in the PIT emulation. On these platforms setting the counter register to zero causes the PIT to start

3.16.63-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Michael Kelley <mikelley at microsoft.com> commit 35b69a420bfb56b7b74cb635ea903db05e357bec upstream. Add support for platforms where pit_shutdown() doesn't work because of a quirk in the PIT emulation. On these platforms setting the counter register to zero causes the PIT to start

This is a note to let you know that I've just added the patch titled clockevents/drivers/i8253: Add support for PIT shutdown quirk to the 4.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: clockevents-drivers-i8253-add-support-for-pit-shutdown-quirk.patch and it can be found in the

This is a note to let you know that I've just added the patch titled clockevents/drivers/i8253: Add support for PIT shutdown quirk to the 4.9-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: clockevents-drivers-i8253-add-support-for-pit-shutdown-quirk.patch and it can be found in the

This is a note to let you know that I've just added the patch titled clockevents/drivers/i8253: Add support for PIT shutdown quirk to the 4.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: clockevents-drivers-i8253-add-support-for-pit-shutdown-quirk.patch and it can be found in

This is a note to let you know that I've just added the patch titled clockevents/drivers/i8253: Add support for PIT shutdown quirk to the 4.18-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: clockevents-drivers-i8253-add-support-for-pit-shutdown-quirk.patch and it can be found in

This is a note to let you know that I've just added the patch titled clockevents/drivers/i8253: Add support for PIT shutdown quirk to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: clockevents-drivers-i8253-add-support-for-pit-shutdown-quirk.patch and it can be found in

On 01/11/2018 18:30, Michael Kelley wrote: > pit_shutdown() doesn't work on Hyper-V because of a quirk in the > PIT emulation. This problem exists in all versions of Hyper-V and > had not been noticed previously. When the counter register is set > to zero, the emulated PIT continues to interrupt @18.2 HZ. > > So add a test for running on Hyper-V, and use that test to skip