Ok, more in the sound department: A current src/sys/dev/sound with a
src/sys/dev/sound/pcm/dsp.c from the 22nd does not exhibit the high load
problem. Moving dsp.c to the 24th causes the problem to re-appear. Thus,
I'm prety convinced tha the big commit on the 23rd to dsp.c is the cause
of at l
On Mon, May 01, 2000 at 10:14:34AM -0400, Kenneth Wayne Culver wrote:
> It was working perfectly about 10 days ago. It stopped working right after
> one or two major commits. And also, it's in 5.0-CURRENT, not 4.0
I fully agree with this statement ... I am having some of the same weird
things ahp
It was working perfectly about 10 days ago. It stopped working right after
one or two major commits. And also, it's in 5.0-CURRENT, not 4.0
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems Administr
Kenneth Wayne Culver wrote:
>
> Hmm, I don't know then, I'm using that ViBRA 16X which seems to cause
> problems a lot.
>
> >
> On Sun, 30 Apr 2000, Ted Sikora wrote:
>
> > Kenneth Wayne Culver wrote:
> > >
> > > I guess it depends on your soundcard, I'm getting the behavior I'm getting
> > >
Hmm, I don't know then, I'm using that ViBRA 16X which seems to cause
problems a lot.
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems Administrator | ICQ #: 24767726 |
| and studen
Ok, I have some *gasp* actual usefull info about this. Backing
/src/sys/dev/sound up by 10 days via anoncvs makes the "feature" go away.
That narrows it down to kernel issues. I'm in the process of narowing it
down to the specific diff, but if I had to cast a bet, i'd go for the
massive change
Kenneth Wayne Culver wrote:
>
> I guess it depends on your soundcard, I'm getting the behavior I'm getting
> with a ViBRA 16X and a kernel as of this morning. This didn't start
> happening until about 4 days ago with a -CURRENT kernel. Maybe you have an
> older -CURRENT.
>
>
I did a make build/
I guess it depends on your soundcard, I'm getting the behavior I'm getting
with a ViBRA 16X and a kernel as of this morning. This didn't start
happening until about 4 days ago with a -CURRENT kernel. Maybe you have an
older -CURRENT.
==
Ted Sikora wrote:
>
> VINSON WAYNE HOWARD wrote:
> >
> > Ok, I checked, and vmstat shows cpu usage to be quite normal, about 6%
> > while playing. What's up w/ top?
> >
>
> Xmms on my SMP current machine: top shows 40 to 43% system
> vmstat shows 10 to 11%
>
vmstat -w 1 matches top exactly ab
VINSON WAYNE HOWARD wrote:
>
> Ok, I checked, and vmstat shows cpu usage to be quite normal, about 6%
> while playing. What's up w/ top?
>
Xmms on my SMP current machine: top shows 40 to 43% system
vmstat shows 10 to 11%
--
Ted Sikora
Jtl Development Group
[EMAIL PROTECTED]
To Unsubscribe
I'm also getting this behavior now. It's not the xmms binary that's taking
all the cpu though... top reports it as "system" CPU usage.
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems Administrator
I did reboot for that reason, but I retried it and got about 50. Mabey I
didn't run the player long enough...
> > Ok, I checked, and vmstat shows cpu usage to be quite normal, about 6%
> > while playing. What's up w/ top?
>
> Not on my computer:
>
> pantzer@skalman ~ >vmstat -w 1
> procs
> Ok, I checked, and vmstat shows cpu usage to be quite normal, about 6%
> while playing. What's up w/ top?
Not on my computer:
pantzer@skalman ~ >vmstat -w 1
procs memory pagedisks faults cpu
r b w avm fre flt re pi po fr sr ad0 da0 in sy
Ok, I checked, and vmstat shows cpu usage to be quite normal, about 6%
while playing. What's up w/ top?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
14 matches
Mail list logo
