Alessandro Ren wrote:
Have any of you tried to disable ACPI on the kernel?
I turn-off the ACPI service, but I haven't removed it from the kernel.
Is there a problem with ACPI holding an interrupt?
Thanks,
--
Michael Welter
Introspect Telephony Corp.
Denver, Colorado US
+1.303.674.2575
[EMAIL
Title: OpSign
Have any of you tried to disable ACPI on the kernel?
Rich Adamson wrote:
On Wed, 2004-12-01 at 13:03 -0700, Michael Welter wrote:
Steven Critchfield wrote:
On Wed, 2004-12-01 at 13:36 -0600, Rich Adamson wrote:
On Wednesday 01 December 2004 20:31, Steven Critchfield wrote:
>
> I am glad it solved the problem. Now if only someone knew what it was
> about the stock RH or FC kernel that makes it happen you could get RH or
> FC to stop using that patch. That or maybe more people will be like me
> and always c
The problem of CPU spikes went away on the x86_64 machine with
kernel-2.6.9. I have just installed 2.6.9 on an Athlon (K7) box and I'm
getting CPU spikes again, this time every three seconds. :-( Unloading
wcfxs causes CPU to stay at 0%.
Mike
Richard Scobie wrote:
Rich Adamson wrote:
Is thei
Rich Adamson wrote:
Is their an open Bug # that we can track against for those of us that
watch the -cvs list and have a vested interest?
I tried, see Bug 2901. Seems probable driver issues don't count as bugs.
Reported it to support, who were aware of the issue, requested login to
my machine and
On Thursday 02 December 2004 18:30, Andrew Kohlsmith wrote:
> On December 2, 2004 12:35 pm, Bob Goddard wrote:
> > > vmstat only polls every 1 second, *but* it does give interrupt counts
> > > and context switches per period.
> >
> > You can give an interval time and count to vmstat.
>
> from vmsta
On December 2, 2004 12:35 pm, Bob Goddard wrote:
> > vmstat only polls every 1 second, *but* it does give interrupt counts and
> > context switches per period.
>
> You can give an interval time and count to vmstat.
from vmstat(8):
delay is the delay between updates in seconds.
Your granularit
On Thursday 02 December 2004 16:25, Andrew Kohlsmith wrote:
> On December 1, 2004 02:48 pm, Juan J. Sierralta P. wrote:
> > Maybe vmstat(8) could be of help instead of the so flamed top(1).
>
> vmstat only polls every 1 second, *but* it does give interrupt counts and
> context switches per pe
On December 1, 2004 02:48 pm, Juan J. Sierralta P. wrote:
> Maybe vmstat(8) could be of help instead of the so flamed top(1).
vmstat only polls every 1 second, *but* it does give interrupt counts and
context switches per period.
-A.
___
Asterisk-
> So, isn't the issue he/I are chasing after essentially 'why is cpu
> consumption
> jumping 30% (or 100%) every ten seconds when zaptel is running with
> no calls present?
> >>>
> >>>
> >>>So where is that CPU time going? Is it in the system, or userspace? Have
> >>>you tried chan
Steven Critchfield wrote:
On Wed, 2004-12-01 at 13:03 -0700, Michael Welter wrote:
Steven Critchfield wrote:
On Wed, 2004-12-01 at 13:36 -0600, Rich Adamson wrote:
So, isn't the issue he/I are chasing after essentially 'why is cpu consumption
jumping 30% (or 100%) every ten seconds when zaptel is
On Wed, 2004-12-01 at 14:47 -0600, Rich Adamson wrote:
> >Looking at the Changlog for 2.6.9, it would appear a fair amount of
> work has been down in the pci stuff and the interrupt support areas.
> Since that seems to be an issue that keeps rearing its head with the
> digium analog cards, maybe th
Rich Adamson wrote:
Looking at the Changlog for 2.6.9, it would appear a fair amount of
work has been down in the pci stuff and the interrupt support areas.
Since that seems to be an issue that keeps rearing its head with the
digium analog cards, maybe there is something 'fixed' in that area.
Not b
It did not fix my spandsp/TxFax problems, however :-(
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-use
> On Wed, 2004-12-01 at 13:03 -0700, Michael Welter wrote:
> > Steven Critchfield wrote:
> > > On Wed, 2004-12-01 at 13:36 -0600, Rich Adamson wrote:
> > >
> > >
> > >>So, isn't the issue he/I are chasing after essentially 'why is cpu
> > >>consumption
> > >>jumping 30% (or 100%) every ten secon
On Wed, 2004-12-01 at 13:03 -0700, Michael Welter wrote:
> Steven Critchfield wrote:
> > On Wed, 2004-12-01 at 13:36 -0600, Rich Adamson wrote:
> >
> >
> >>So, isn't the issue he/I are chasing after essentially 'why is cpu
> >>consumption
> >>jumping 30% (or 100%) every ten seconds when zaptel i
Steven Critchfield wrote:
On Wed, 2004-12-01 at 13:36 -0600, Rich Adamson wrote:
So, isn't the issue he/I are chasing after essentially 'why is cpu consumption
jumping 30% (or 100%) every ten seconds when zaptel is running with
no calls present?
So where is that CPU time going? Is it in the syste
On Wed, 2004-12-01 at 13:36 -0600, Rich Adamson wrote:
> So, isn't the issue he/I are chasing after essentially 'why is cpu consumption
> jumping 30% (or 100%) every ten seconds when zaptel is running with
> no calls present?
So where is that CPU time going? Is it in the system, or userspace? Hav
Hi,
Maybe vmstat(8) could be of help instead of the so flamed top(1).
> > Steven Critchfield wrote:
> >
> > > top will only report userspace problems, and to top it off, top only
> > > reports on snapshots of the system on as low as 1 second. With Zap
> > > hardware hitting the system 100
> > > I'm debugging a TxFax problem whereby the fax transmission fails. I
> > > suspect interrupt latency--some interrupt routine is holding its
> > > interrupt too long. I have all unnecessary services switched off and X
> > > is not running when I perform these tests. Some transmission are
On Wed, 2004-12-01 at 11:46 -0700, Michael Welter wrote:
> Steven Critchfield wrote:
>
> > top will only report userspace problems, and to top it off, top only
> > reports on snapshots of the system on as low as 1 second. With Zap
> > hardware hitting the system 1000 times a second for service, yo
Steven Critchfield wrote:
top will only report userspace problems, and to top it off, top only
reports on snapshots of the system on as low as 1 second. With Zap
hardware hitting the system 1000 times a second for service, you might
happen to get an occasional hit time here top and the hardware hit
I'm seeing a correlation between the fax transmission failure and the
second hand on my watch.
Failures occur at about :02, :12, :22, :32, :42, and :52. This is +/-
the same time as the CPU spike.
Can anyone from Digium help with this?
Thanks,
--
Michael Welter
Introspect Telephony Corp.
Denve
Steve Clark wrote:
Forget what I just posted - after watching top for a while about every
30 seconds I see irq% go to about 30%.
Steve
What are your command line options?
--
Michael Welter
Introspect Telephony Corp.
Denver, Colorado US
+1.303.674.2575
[EMAIL PROTECTED]
www.introspect.com
On Wed, 2004-12-01 at 13:12 -0500, Steve Clark wrote:
> Michael Welter wrote:
> > I'm debugging a TxFax problem whereby the fax transmission fails. I
> > suspect interrupt latency--some interrupt routine is holding its
> > interrupt too long. I have all unnecessary services switched off and X
Michael Welter wrote:
I'm debugging a TxFax problem whereby the fax transmission fails. I
suspect interrupt latency--some interrupt routine is holding its
interrupt too long. I have all unnecessary services switched off and X
is not running when I perform these tests. Some transmission are
s
Michael Welter wrote:
I'm debugging a TxFax problem whereby the fax transmission fails. I
suspect interrupt latency--some interrupt routine is holding its
interrupt too long. I have all unnecessary services switched off and X
is not running when I perform these tests. Some transmission are
s
> I'm debugging a TxFax problem whereby the fax transmission fails. I
> suspect interrupt latency--some interrupt routine is holding its
> interrupt too long. I have all unnecessary services switched off and X
> is not running when I perform these tests. Some transmission are
> successful wh
I'm debugging a TxFax problem whereby the fax transmission fails. I
suspect interrupt latency--some interrupt routine is holding its
interrupt too long. I have all unnecessary services switched off and X
is not running when I perform these tests. Some transmission are
successful while others
29 matches
Mail list logo
