Xorg 6.8.1 and SCHED_ULE vs. SCHED_4BSD

Kevin Oberman oberman at es.net
Tue Mar 1 20:27:33 GMT 2005

> Date: Tue, 1 Mar 2005 16:36:11 +0100
> From: Godwin Stewart <gstewart at bonivet.net>
> Sender: owner-freebsd-stable at freebsd.org
> Hash: SHA1
> On Tue, 1 Mar 2005 02:32:02 -0500 (EST), Jeff Roberson
> <jroberson at chesapeake.net> wrote:
> > Is the process that does the FFT in kernel, niced, or rtprio'd?
> last pid: 93131;  load averages:  0.96,  0.49,  0.24  up 0+05:18:20 15:29:47
> 48 processes:  2 running, 46 sleeping
> CPU states: 99.6% user,  0.0% nice,  0.4% system,  0.0% interrupt,  0.0% id> le
> Mem: 174M Active, 94M Inact, 86M Wired, 14M Cache, 48M Buf, 2564K Free
> Swap: 743M Total, 180K Used, 743M Free
> 93124 godwin   121    0 33288K 23836K RUN      2:22 13.72% 13.72% audacity
> WCPU and CPU climb to about 20%, drop to 0 during disk I/O, then start
> climbing again.
> Note that this is with SCHED_4BSD. I'd need to recompile a kernel to get
> similar information for ULE/PREEMPTION.
> fx: goes off and compiles a new kernel and comes back when it's done...
> Looks like I spoke too soon. The system is now perfectly stable and usable
> with ULE.
> The problems I was having with ULE were on 5.3-STABLE. I'm now on 5.4-PRE.
> Were there significant changes to the kernel in between?
Stable is a dynamic thing. Stable as of what date? Lots of fixes to ULE,
APIC, ACPI and other things have made it to the kernel at some point in
the life of 5.3-Stable. Several have made it rather recently. 

Comparing a dmesg from when it was not working with one now might be
instructive. (They can be found in /var/log/messages[.n.bz2].) Take a
look at the details of the device probes before disks are mounted in
particular, for changes.

> > Can you give me any information on the means by which you transfer data
> > from a cassette to your pc?
> Straightforward audio connection from the amp's line out to the sound
> card's line in. The FFT filtering isn't performed on the fly BTW. I use
> audacity to grab the audio and then work on it after it's "in the box".

Really sounds more and more like interrupts were not getting properly
delivered. Normally the disk IRQs are not shared, but it really looks
like something was broken here for your BIOS. (And it appears to have
been fixed!)
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634

More information about the freebsd-stable mailing list