RE: "profiling timer expired" on new kernel builds in 4.1-R and4.1-S
Hi all, I mostly always see this error message (Profiling timer expired) when I try to dump a large MySQL database with the mysqldump comamnd. I have no clue how to fix this, and I would greatly appreciate any hint on this subject. Thanks, Noor -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Matt Groener Sent: Friday, September 08, 2000 5:46 AM To: Neil Hoggarth Cc: [EMAIL PROTECTED] Subject: Re: "profiling timer expired" on new kernel builds in 4.1-R and4.1-S > > I'm running a Dell Dimension P-II 400MHz, 384MB RAM, 18GB SCSI on a > > Qlogic card. > > Aha! I have a Qlogic ISP1040 SCSI card. I think we have a suspect ... > I use a Qlogic 1040B (FW-SE). Can anyone on the distribution lend a light to a link between the profiling errors and Qlogic (or isp device) cards? Realize I am guessing, but it's something to go on... -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Perl Doesn't like XFree-4.0.1
In message <[EMAIL PROTECTED]> Ryan Losh writes: : that "THIS is where the LC_CTYPE is being set." Therefore, I need to : read the FreeBSD handbook and see how one goes about reporting a bug : in the ports (gnomelibs-1.2.4, to be exact). I am not an expert, but Short answer: cd /usr/ports/*/gnomelibs mail -s "Bug report" `make -V MAINTAINER` Longer answer involves submitting a PR, but I usually like to send mail to the maintainer first. : I don't think that hardcoding this value in a shared library is "The : Right Way To Get The Job Done (TM)" You are 100% correct about that. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Perl Doesn't like XFree-4.0.1
imp> could be the X server. To see if this is the case, use the following imp> .xinitrc: imp>#!/bin/sh imp>xterm imp> and then do a printenv. I kinda doubt it as I don't see this on my imp> systems here, but I use XFree86 3.3.6. imp> Yes, I don't see it (LC_CTYPE) either... imp> Second, it could be coming gnome-terminal. You can test this out by imp> changing the above script in the obvious way. Do a printenv as well. imp> This likely is where the problem came from. I don't use kde, gnome, imp> or anything more complex than twm + xterm or qvwm + xterm. imp> I tested that (.xinitrc with *ONLY* a gnome-terminal), and again, I don't see the LC_CTYPE var getting set. I took it one step further: I did a startx with the following .xinitrc: #!/bin/sh ktrace gnome-session I looked for "en_US" in *EVERY* file that gets opened during a startx, and I discovered that "LC_CTYPE" and "en_US" are *HARDCODED* into the libgnomeui.so.4 file/shared library. I would say without reservation that "THIS is where the LC_CTYPE is being set." Therefore, I need to read the FreeBSD handbook and see how one goes about reporting a bug in the ports (gnomelibs-1.2.4, to be exact). I am not an expert, but I don't think that hardcoding this value in a shared library is "The Right Way To Get The Job Done (TM)" Ryan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: "profiling timer expired" on new kernel builds in 4.1-R and4.1-S
> > I'm running a Dell Dimension P-II 400MHz, 384MB RAM, 18GB SCSI on a > > Qlogic card. > > Aha! I have a Qlogic ISP1040 SCSI card. I think we have a suspect ... > I use a Qlogic 1040B (FW-SE). Can anyone on the distribution lend a light to a link between the profiling errors and Qlogic (or isp device) cards? Realize I am guessing, but it's something to go on... -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: XFree86 4 and DRI with voodoo3
Wow! I loved being proved wrong. So do you need a kernel module for that to work? Just agpart? Any documentation you looked at for this? --David Bushong On Thu, Sep 07, 2000 at 10:23:13PM -0400, Coleman Kane wrote: > Two possibilities: > 1) You are not loading the tdfx.ko that can be built from the XFree86 source > tree. > 2) You are running in a resolution that your card does not support for GL. > > I have a Matrox G200 that works in FreeBSD for DRI. > > David Bushong had the audacity to say: > > Alas, from: http://dri.sourceforge.net/DRIuserguide.html : > > > > * With XFree86 4.0 and the Direct Rendering Interface (DRI), hardware > > * accelerated 3D graphics can be considered a standard feature on Linux > > * workstations. Support for other operating systems, such as FreeBSD, is > > * underway. > > > > Each DRI driver, AFAICT, needs its own accompanying kernel module, and the > > FreeBSD kernel modules just don't exist yet. Sigh. I'll keep running 3.3.6 > > with Utah-GLX for now... > > > > --David Bushong > > > > > > On Sat, Sep 02, 2000 at 02:26:52PM +, Thomas Koper wrote: > > > Hi, > > > I'm trying to use DRI with XFree 4 and the voodoo3 agp card, but as > > > as I start x windows I get the message that DRI is disabled: > > > ... > > > (II) TDFX(0): initializing int10 > > > (==) TDFX(0): Write-combining range (0xa,0x2) was already clear > > > (II) TDFX(0): Primary V_BIOS segment is: 0xc000 > > > (II) TDFX(0): VESA Bios detected > > > (II) TDFX(0): VESA VBE DDC supported > > > (==) TDFX(0): Write-combining range (0xec00,0x200) was already clear > > > (==) TDFX(0): Write-combining range (0xe000,0x200) > > > (==) TDFX(0): Write-combining range (0xa,0x1) was already clear > > > (II) TDFX(0): Textures Memory 10.99 MB > > > II) TDFX(0): Using XFree86 Acceleration Architecture (XAA) > > > Screen to screen bit blits > > > Solid filled rectangles > > > 8x8 mono pattern filled rectangles > > > Indirect CPU to Screen color expansion > > > Solid Lines > > > Dashed Lines > > > Offscreen Pixmaps > > > Driver provided NonTEGlyphRenderer replacement > > > Setting up tile and stipple cache: > > > 8 128x128 slots > > > (==) TDFX(0): Backing store disabled > > > (==) TDFX(0): Silken mouse enabled > > > (II) TDFX(0): direct rendering disabled > > > (**) Mouse1: Protocol: "Auto" > > > (**) Mouse1: Core Pointer > > > (==) Mouse1: Buttons: > > > ... > > > > > > Why does it say "(II) TDFX(0): direct rendering disabled" ? > > > I compiled XFree86-4 from the ports and it starts up fine, I confiured > > > it to load the GLX and DRI modules, like it says in the installation > > > guide. Do I have to install anything else beside this? I just started with an > > > fresh 4.1S Box. Could someone help me to get this to work?? > > > > > > Regards Thomas Koper > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > Coleman Kane > President, > UC Free O.S. Users Group - http://www.free-os.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Odd Load average problem
For what it's worth, I see this occasionally on my laptop. It seems to be amd and/or some NFS activity that kicks up the load-average to 1. It comes back down after a while so I haven't cared to get any further into it. As usual, I Could Be Wrong. -- Parag Patel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: NO_TCSH issue
On Thu, Sep 07, 2000 at 07:54:17PM -0700, Eric P. Scott wrote: > What individuals choose as defaults for their personal accounts > is their business. I don't see a problem with having sh, ksh, > zsh, bash, csh, tcsh, _whatever_ available. But I stand by my > opinion that replacing csh with tcsh in 4.1-RELEASE was the > single most ill-conceived action taken by the committers. I'd argue that allowing posts from your domain is currently holding that position. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
floppy drive
Hello, I have just discovered a strange problem on my new PC. The mother board is an Abit KT7 hosting a Duron with Via chipset. I can triple boot FreeBSD 4.1-RELEASE (stock GENERIC kernel) Linux and Win98. Problem: under freebsd i cannot run fdformat fd0. Immediately bad crc errors appear, only some sectors come out with V. Of course i have tried with several floppies and two floppy drives, one of them working very well in another machine. Much stranger: with the same floppy and floppy drive and machine, formatting works perfectly OK with Linux and Win98. To add to the bizarre, once i have a good fdformatted floppy (under linux) i can perfectly read and write to it under freebsd. dd if=/dev/fd0 of= /tmp/flopworks and is quite fast. dd if=/tmp/flop of=/dev/fd0 also works. Floppy drives are Sony, and it is the first time i see that on a freebsd machine. -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Which release of 4.1 supports i810 with XFree86 4.0.1?
On Wed, Sep 06, 2000 at 11:33:05PM -0700, Doug White wrote: > On Wed, 6 Sep 2000, Alan Bindemann wrote: > > > >From: Doug White <[EMAIL PROTECTED]> > > >Don't expect to get lots of help for this; XFree86 4 is very, very beta > > >and has lots of nasty bugs. [snip] > > > > > >I suggest using 3.3.6 for production use. > > > > I was under the impression that the i810 chipset was not supported under > > 3.3.6. Am I mistaken? If so, do I need to rebuild 3.3.6 with some patches > > for i810 support? > > I stay away from such broken hardware. > > As X 4 is beta, don't expect any help from this list for it. > Perhaps X 4 is beta, but X 3 does not work or work poorly on some video cards which are amongst the best on the market (GeForce). So a shift to 4.01 will soon to be considered. Do you think people will only buy Matrox G 400 because it is very well supported by X 3? To speak for my case, i have received mail that GeForce works with X 3 but my own works very poorly, if at all. I am obliged to go to 4.01 and install nVidia drivers under Linux. Corresponding drivers for freebsd are said to be in preparation. -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
HEADS UP: RSA liberated
The native OpenSSL implementation of RSA has been activated by default in -stable, meaning rsaref and librsaUSA are no longer required, and new installs will be able to make use of openssh in ssh1 mode by default. Basically, the situation for US people has caught up with what international folk have enjoyed for many months. Further cleanups will be taking place over the next few days. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Which release of 4.1 supports i810 with XFree86 4.0.1?
Alan Bindemann wrote: > > >From: Doug White <[EMAIL PROTECTED]> > >Don't expect to get lots of help for this; XFree86 4 is very, very beta > >and has lots of nasty bugs. [snip] > > > >I suggest using 3.3.6 for production use. > > I was under the impression that the i810 chipset was not supported under > 3.3.6. Am I mistaken? If so, do I need to rebuild 3.3.6 with some patches > for i810 support? AFAIK, the i810 is only supported under 4.0.1 with FreeBSD 4.1 It's working here :o) -- ANTONY T CURTIS Tel: +44 (1635) 36222 Abacus Polar Holdings Ltd Fax: +44 (1635) 38670 > Arbitrary systems, pl.n.: > Systems about which nothing general can be said, save "nothing > general can be said." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: NO_TCSH issue
On Wed, 6 Sep 2000, Eric P. Scott wrote: > [Neil Blakey-Milner] > >tcsh is fully csh-compatible. > > No, it isn't. And not including a 44bsd-csh package on > 4.1-RELEASE's CD #1 (note that 44bsd-more is there) was downright > malicious. Yes, we did it to deliberately screw with your life. :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
