i'd guess the most reciently changed devices should head the list of
leading suspects:
--rw-rw-r-- M 72 glenda sys 1591 Oct 4 01:40 pcmciamodem.c
--rw-rw-r-- M 72 glenda sys 30411 Oct 8 19:31 ether82557.c
--rw-rw-r-- M 72 geoffsys 37571 Oct 8 20:30 sdiahci.c
--rw-rw-r-- M 72 geoff
On Nov 21, 2007 10:28 AM, Gabriel Diaz <[EMAIL PROTECTED]> wrote:
> Hello
>
> I'm getting the same with a new kernel (pulled minutes ago), i tried two
> kernel configurations (for pcf kernel), one configured with a default pcf
> and other with settings to build just what i think i need.
>
> With bo
Hello
I'm getting the same with a new kernel (pulled minutes ago), i tried two
kernel configurations (for pcf kernel), one configured with a default pcf
and other with settings to build just what i think i need.
With both kernels i get high intr. rates (stats shows ~28), with and
without time
On Nov 21, 2007 8:06 AM, Russ Cox <[EMAIL PROTECTED]> wrote:
> > Ok another fresh install, I killed timesync, but am still getting
> > thousands of interrupts. And I'm noticing I'm getting about 18 fossil
> > instances and 14 venti instances.
> >
> > not sure if that's normal or not.
>
> Are you s
> Ok another fresh install, I killed timesync, but am still getting
> thousands of interrupts. And I'm noticing I'm getting about 18 fossil
> instances and 14 venti instances.
>
> not sure if that's normal or not.
Are you sure you have a recent CD?
What you're describing sounds like the venti sy
On Nov 21, 2007 6:47 AM, erik quanstrom <[EMAIL PROTECTED]> wrote:
> what chipset & ethernet controller.
>
> - erik
>
It's an nForce 2 I believe (haven't really turned this thing on for
like a year or so).
3com Ethernet controller 3c59x seems correct :-)
It's got an nvidia ethernet controller to
On Nov 21, 2007 7:27 AM, David Leimbach <[EMAIL PROTECTED]> wrote:
> On Nov 21, 2007 6:51 AM, andrey mirtchovski <[EMAIL PROTECTED]> wrote:
> > that is probably correct. doesn't amd only "suggest" the clock
> > frequency to be what they think the processor speed is when compared
> > to the original
On Nov 21, 2007 6:51 AM, andrey mirtchovski <[EMAIL PROTECTED]> wrote:
> that is probably correct. doesn't amd only "suggest" the clock
> frequency to be what they think the processor speed is when compared
> to the original 1GHz Athlon?
Yeah their product numbers are not really the clock speed.
that is probably correct. doesn't amd only "suggest" the clock
frequency to be what they think the processor speed is when compared
to the original 1GHz Athlon?
what is the current time reported by the system? try running timesync
and monitor the cpufreq for sudden increase/decreases. of course th
what chipset & ethernet controller.
- erik
On Nov 21, 2007 6:34 AM, andrey mirtchovski <[EMAIL PROTECTED]> wrote:
> timesync can cause the kernel to think that the cpu has a much
> different frequency than it really does, which can cause time to speed
> up, timers to fire much sooner than usual and so on. see what
> /dev/cputype says...
>
timesync can cause the kernel to think that the cpu has a much
different frequency than it really does, which can cause time to speed
up, timers to fire much sooner than usual and so on. see what
/dev/cputype says...
On Nov 21, 2007 6:28 AM, David Leimbach <[EMAIL PROTECTED]> wrote:
>
> On Nov 20, 2007 4:21 PM, andrey mirtchovski <[EMAIL PROTECTED]> wrote:
> > the best way to catch timesync-related issues is to use a stop watch
> > to measure the duration of 'sleep 60'. seriously :)
> >
> >
> > On Nov 20, 2007
On Nov 20, 2007 4:21 PM, andrey mirtchovski <[EMAIL PROTECTED]> wrote:
> the best way to catch timesync-related issues is to use a stop watch
> to measure the duration of 'sleep 60'. seriously :)
>
>
> On Nov 20, 2007 5:08 PM, erik quanstrom <[EMAIL PROTECTED]> wrote:
> >
> > On Tue Nov 20 17:38:05
On Nov 20, 2007 4:08 PM, erik quanstrom <[EMAIL PROTECTED]> wrote:
>
> On Tue Nov 20 17:38:05 EST 2007, [EMAIL PROTECTED] wrote:
> > I figured maybe something is going on with venti and an initial
> > snapshot after an install, but it's been doing this now for > 6hours.
> >
> > I've got gnot showin
the best way to catch timesync-related issues is to use a stop watch
to measure the duration of 'sleep 60'. seriously :)
On Nov 20, 2007 5:08 PM, erik quanstrom <[EMAIL PROTECTED]> wrote:
>
> On Tue Nov 20 17:38:05 EST 2007, [EMAIL PROTECTED] wrote:
> > I figured maybe something is going on with v
On Tue Nov 20 17:38:05 EST 2007, [EMAIL PROTECTED] wrote:
> I figured maybe something is going on with venti and an initial
> snapshot after an install, but it's been doing this now for > 6hours.
>
> I've got gnot showing about 15000 and higher interrupts per second...
could be timesync misconfig
I figured maybe something is going on with venti and an initial
snapshot after an install, but it's been doing this now for > 6hours.
I've got gnot showing about 15000 and higher interrupts per second...
18 matches
Mail list logo
