RE: SMPng CPU states
FWIW, it looks like VESA support broke after the SMPng commit. I used to run my VTYs in VESA_800x600 mode, but just after the commit it hung the machine (this is on a dual-processor system, with a Voodoo 5500). PYD -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Brandon Hume Sent: 09 September 2000 10:04 To: [EMAIL PROTECTED] Subject: Re: SMPng CPU states > FWIW, I've had no trouble running X on my development box. Well, the > monitor can only do 640x480, but that's not an OS issue. I was able to get X going initially... its when I attempt to make use of DRI that the box hangs, which may not be a problem that anyone can do anything about here, since the mga and drm .ko's come from the XFree-4 source. I can load the modules via kldload just fine, without trouble. Its when I actually try and launch into X with DRI enabled that doom befalls me. I'll have to do a bit more science with it. -- Brandon Hume- hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPng CPU states
> FWIW, I've had no trouble running X on my development box. Well, the > monitor can only do 640x480, but that's not an OS issue. I was able to get X going initially... its when I attempt to make use of DRI that the box hangs, which may not be a problem that anyone can do anything about here, since the mga and drm .ko's come from the XFree-4 source. I can load the modules via kldload just fine, without trouble. Its when I actually try and launch into X with DRI enabled that doom befalls me. I'll have to do a bit more science with it. -- Brandon Hume- hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPng CPU states
On Friday, 8 September 2000 at 14:17:58 -0300, Brandon Hume wrote: > I've built world and kernel yesterday, and was delighted to see the AIC7xxx > problems had gone away. I actually got tripped up by having Linux emulation > enabled and forgetting to remove old modules, but that was fixed quick. > > All-in-all, I'm not having a rough time at all with the new code. My > machine has been up for 7.5 hours now without a hiccup. I DID notice that > I can't load X without a hang, which I think is the same AGP problem someone > else mentioned. FWIW, I've had no trouble running X on my development box. Well, the monitor can only do 640x480, but that's not an OS issue. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPng CPU states
Brandon Hume wrote: > I've built world and kernel yesterday, and was delighted to see the AIC7xxx > problems had gone away. I actually got tripped up by having Linux emulation > enabled and forgetting to remove old modules, but that was fixed quick. > > All-in-all, I'm not having a rough time at all with the new code. My > machine has been up for 7.5 hours now without a hiccup. I DID notice that > I can't load X without a hang, which I think is the same AGP problem someone > else mentioned. > > The only other thing I've noticed is top telling me that the CPU is steady > at 50.0% system and 50.0% idle. The box is completely quiescent, except for > me ssh'd in and running top. vmstat says sy=50 and id=50 as well. If I > start a CPU-chewing process (sh -c 'while true; do true; done') the resultant > CPU usage in %user seems to come from %system. Process accounting is somewhat broken. The actual runtime of each process (p_runtime, or TIME in top) is accurate, but many of the other statistics are broken at the moment since statclock() no longer has a proper stackframe to work with. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMPng CPU states
I've built world and kernel yesterday, and was delighted to see the AIC7xxx problems had gone away. I actually got tripped up by having Linux emulation enabled and forgetting to remove old modules, but that was fixed quick. All-in-all, I'm not having a rough time at all with the new code. My machine has been up for 7.5 hours now without a hiccup. I DID notice that I can't load X without a hang, which I think is the same AGP problem someone else mentioned. The only other thing I've noticed is top telling me that the CPU is steady at 50.0% system and 50.0% idle. The box is completely quiescent, except for me ssh'd in and running top. vmstat says sy=50 and id=50 as well. If I start a CPU-chewing process (sh -c 'while true; do true; done') the resultant CPU usage in %user seems to come from %system. -- Brandon Hume- hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
