Re: can't build 4.3-BETA GENERIC kernel with -g
On Thu, Mar 15, 2001 at 01:42:28AM -0600, Tim Zingelman wrote: > I built & installed world/kernel with -O -pipe, then later tried to make > kernel with just -pipe and it failed (with or without debug)... I guess if > I buildworld with -O I must build my kernel with -O. Is there any problem > getting info out of a crashdump if the kernel is compiled -O (along with -g) Actually it just means building without -O is just broken..it's not because you're mixing -O with non-O. It shouldn't matter for analysing dumps - the fact that it's broken means none of the developers have had a need to do that either :-) Kris PGP signature
Re: load stays at 1 on an idle machine
I, too, see this all the time, and have since I upgraded to 3.0 (same machine, have upgraded incrementally to 3.1, 3.2, 3.3, 4.0, 4.1, 4.2 (all -STABLEs)), and have seen this the whole time. Never tracked it down, either... (Just another data point) My machine: PII/266, 128MB memory, P2L97 motherboard (everything else has changed at one time or another) --David Bushong On Sat, Mar 10, 2001 at 05:27:22AM -0800, Mike Harding wrote: > > I have seen this behavior a number of times over the years, but never > tracked it down. I even looked at the kernel code which computed the > load to see if I could identify anything obvious. > > I have noticed that when this happes, the load is basically a > completely stable value of 1.0 or very close to it, almost like it is > in a locally stable state. Didn't look for zombies though - I use > junkbuster and it always keeps a few zombies around because the main > spawn loop is screwy. (grrr). > > - Mike Harding > >Date: Sat, 10 Mar 2001 23:58:51 +1100 (EST) >From: Bruce Evans <[EMAIL PROTECTED]> >X-Sender: [EMAIL PROTECTED] >Cc: Mikhail Teterin <[EMAIL PROTECTED]> >Content-Type: TEXT/PLAIN; charset=US-ASCII >Sender: [EMAIL PROTECTED] >X-Loop: FreeBSD.ORG >Precedence: bulk > >On Fri, 9 Mar 2001, Will Andrews wrote: > >> On Fri, Mar 09, 2001 at 10:39:53AM -0500, Mikhail Teterin wrote: >> > I was running a single instance of SETI@Home, when I observed the load >> > of 2. I stopped seti and the load went down to one. It stays there for >> > about 20 hours already. The machine is idle: > >> top(1) doesn't show all stats relevant to the load average. Check >> vmstat/systat/iostat/netstat/etc. > >Perhaps it is the entropy harvester reaping itself ;-). > >> Besides, the load average is a >> worthless metric if you ask me. > >Erm, it is a fundamental part of the scheduler. The scheduler is b0rked, >but not that part of it. > >Bruce > > >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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3ware problems
> Drat. There it is; you've got a command that looks like it's stuck in > the adapter. I'll go grab the can of WD-40. :) > I didn't see you respond to Mike T - are you using 64k or 128k stripes? I didn't get his query until I had already started the mysqd trying to break things. And now I'm at home, and while serial consoles are *really* great for most things, I can't get at the 3ware BIOS from here. I didn't want to respond until I had checked the bios. I'm /fairly/ sure that I took the default 64K stripes, but one time in rebinding the array I did change the stripe size. > If the latter, try changing the value of TWE_Q_LENGTH in > /sys/dev/twe/twereg.h to 100 and see if you can reproduce it. Rebuilding the kernel as I type. > I am worrying about firmware here at the moment We are running the latest firmware as of about 10 days ago. > Thanks for your patience. Are you kidding? Thanks for all the help. We really appreciate it. Anything we can do to help, let us know. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: can't build 4.3-BETA GENERIC kernel with -g
On Thu, 15 Mar 2001, Tim Zingelman wrote: > On Wed, 14 Mar 2001, Matt Dillon wrote: > > > :Am I missing something here... is this the wrong way to build a kernel > > :with debug symbols? Any help is appreciated. > > > > The correct solution is to add the following to your kernel > > configuration file. That is, the file /usr/src/sys/i386/conf/YOURKERNEL, > > NOT make.conf. > > makeoptions DEBUG="-g" > > The result is the same... > > make.conf now has: > CFLAGS= -pipe > COPTFLAGS= -pipe > > and I just removed the # from the line: > makeoptions DEBUG=-g > in /usr/src/sys/i386/conf/GENERIC > It turns out the problem has to do with my having removed the -O from either CFLAGS or COPTFLAGS. I built & installed world/kernel with -O -pipe, then later tried to make kernel with just -pipe and it failed (with or without debug)... I guess if I buildworld with -O I must build my kernel with -O. Is there any problem getting info out of a crashdump if the kernel is compiled -O (along with -g) Now that I've restored the -O, a debug GENERIC builds just fine. I had no idea that I could not mix -O and non -O code... sorry about that. - Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: KDE2.1 ++ GNOME 1.2
Hi Colon, I had a problem with bonobo failing, so I built bonobo on it's own then successfully resumed my build. Dru On Wed, 14 Mar 2001, Colin Legendre wrote: > If I do it one way it fail on KDEGames, the other it fails on bonobo. > > -Original Message- > From: Karel J. Bosschaart [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 14, 2001 12:29 PM > To: Colin Legendre > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: KDE2.1 ++ GNOME 1.2 > > > On Wed, Mar 14, 2001 at 10:17:42AM -0500, Colin Legendre wrote: > > I am having huge problems installing KDE2.1 and GNOME1.2 on the same box > > from the ports. > > > > It would seem that you cannot install both of them on the same box. > Because > > I tried installing kde first, that worked, then gnome and the gnome build > > failed! Then I tried installing Gnome first than kde and the kde build > > failed. Any help here guys.! > > > That sounds bizarre... you aren't running out of disk space, are you?? > What's the error you get in the build? > > Karel. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: KDE2.1 ++ GNOME 1.2
If I do it one way it fail on KDEGames, the other it fails on bonobo. -Original Message- From: Karel J. Bosschaart [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 14, 2001 12:29 PM To: Colin Legendre Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: KDE2.1 ++ GNOME 1.2 On Wed, Mar 14, 2001 at 10:17:42AM -0500, Colin Legendre wrote: > I am having huge problems installing KDE2.1 and GNOME1.2 on the same box > from the ports. > > It would seem that you cannot install both of them on the same box. Because > I tried installing kde first, that worked, then gnome and the gnome build > failed! Then I tried installing Gnome first than kde and the kde build > failed. Any help here guys.! > That sounds bizarre... you aren't running out of disk space, are you?? What's the error you get in the build? Karel. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: KDE2.1 ++ GNOME 1.2
On Wed, Mar 14, 2001 at 10:17:42AM -0500, Colin Legendre wrote: > I am having huge problems installing KDE2.1 and GNOME1.2 on the same box > from the ports. > > It would seem that you cannot install both of them on the same box. Because > I tried installing kde first, that worked, then gnome and the gnome build > failed! Then I tried installing Gnome first than kde and the kde build > failed. Any help here guys.! > That sounds bizarre... you aren't running out of disk space, are you?? What's the error you get in the build? Karel. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Uh oh. Looks like something broke with the AHC driver..
> A dmesg from the affected system would be a good start. I you have > a serial console cable and can use it to catch the full output of > from the driver, I can probably pin this down very quickly. As > it stands now, I don't even know which of the many controllers the > driver supports that you have in your machine. Fair enough - let me see what I can rig up. I'll also see if we can reproduce this with any of the machines in the lab. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: MFC: src/sys/i386/conf/GENERIC and sound support
> I noticed that this still hasn't been MFCed, even though it makes a lot > of sense for regular users (that is, those that do not recompile their > kernel regularily): > >revision 1.289 >date: 2000/11/14 01:11:13; author: jkh; state: Exp; lines: +4 -1 >In the year 2000, I think it's perfectly reasonable to include audio >support by default in GENERIC. It would be nice, but it's also just too late to change this for 4.3 given that we wouldn't have enough testing time to ensure that enabling sound didn't break something else. We'll just have to shoot for 4.4. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Major upgrade
On Wed, Mar 14, 2001 at 08:36:09AM -0800, Mike Harding wrote: > > Having done this before I would HIGHLY recommend doing a clean install > and restoring the 'good stuff' from backup. You can do the upgrades > in place, but it takes a while, and you have to do it in steps, and if > you misstep you may blow up the box, and so on. You should know how > to do clean installs and backups anyways. Since you have 2 machines, > assuming sufficient clear disk space on each, you can back one up onto > the other and so on. Some time ago, Ralf S. Engelschall posted a description about upgradeing a bunch of 3.5-STABLE boxes to 4.1.1-STABLE: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=699499+0+archive/2000/freebsd-stable/2806.freebsd-stable /Michael > > - Mike H. > >From: "Steffen Vorrix" <[EMAIL PROTECTED]> >Date: Wed, 14 Mar 2001 10:44:34 -0500 >Content-Type: multipart/alternative; > boundary="=_NextPart_000_000B_01C0AC73.C2523D80" >X-Priority: 3 >X-MSMail-Priority: Normal >X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 >X-MDRemoteIP: 208.60.70.195 >X-Return-Path: [EMAIL PROTECTED] >X-MDaemon-Deliver-To: [EMAIL PROTECTED] >Sender: [EMAIL PROTECTED] >X-Loop: FreeBSD.ORG >Precedence: bulk > >This is a multi-part message in MIME format. > >--=_NextPart_000_000B_01C0AC73.C2523D80 >Content-Type: text/plain; > charset="iso-8859-1" >Content-Transfer-Encoding: quoted-printable > >I have been tracking this list for about 3 or 4 weeks now, and I have = >learned alot more about FreeBSD then I thought I might. I have = >successfully upgrade my two home FreeBSD machines from 4.2 REL to the = >current stable version, and everything went just fine. However, I now = >need to upgrade 2 production machines for my employer, and these have to = >go as painlessly as possible. The problem is that these machines are = >3.4 REL. I have looked through the mail over the past weeks, and I have = >found people mention that 3.4 to 4 can have some gotcha's associated = >with it, but I haven't seen anything specifically mentioned. Are there = >things that I need to watch out for? The reference that I am referring = >to was a thread regarding remotely updating servers. While this was = >frowned upon by almost everyone in the list, one person specifically = >mentioned that remote updating would be a problem from a 3.x to a 4.x. = >I don't plan to do any remote updating, but I want to be sure there = >aren't other things I need to watch out for. > >Thanks a bunch. > >Chris Schremser > >--=_NextPart_000_000B_01C0AC73.C2523D80 >Content-Type: text/html; > charset="iso-8859-1" >Content-Transfer-Encoding: quoted-printable > > > >charset=3Diso-8859-1"> > > > > >I have been tracking this list for = >about 3 or 4=20 >weeks now, and I have learned alot more about FreeBSD then I thought I=20 >might. I have successfully upgrade my two home FreeBSD machines = >from 4.2=20 >REL to the current stable version, and everything went just fine. = >However,=20 >I now need to upgrade 2 production machines for my employer, and these = >have to=20 >go as painlessly as possible. The problem is that these machines = >are 3.4=20 >REL. I have looked through the mail over the past weeks, and I = >have found=20 >people mention that 3.4 to 4 can have some gotcha's associated with it, = >but I=20 >haven't seen anything specifically mentioned. Are there things = >that I need=20 >to watch out for? The reference that I am referring to was a = >thread=20 >regarding remotely updating servers. While this was frowned upon = >by almost=20 >everyone in the list, one person specifically mentioned that remote = >updating=20 >would be a problem from a 3.x to a 4.x. I don't plan to do any = >remote=20 >updating, but I want to be sure there aren't other things I need to = >watch out=20 >for. > >Thanks a bunch. > >Chris = >Schremser > >--=_NextPart_000_000B_01C0AC73.C2523D80-- > > > >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 > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Disk I/O problem in 4.3-BETA
> >First off, some disk caches are getting > 10megs, that's a lot > >of potnetial seeking after loosing power depending on the cache > >contents... > > I've heard that most modern drives reserve a contiguous area of the > disk the size of the cache near where the heads park to dump any > cache contents on power outage. This avoids most if not all seeking. > When the disk powers up again, the reserve track is read and the > transactions are written to the correct locations. Any disk that does > this should be safe to use with write caching enabled. As some one who has spent some time working with disk drive manufactures in the far past all sorts of work is done to make sure that the write cache is not a failure mechanism for lost data. Some of the designs include things like using the spindle motor as a generator and the inertia of the platters to drive it to insure the drive has adaquate power for a long enough period to flush any cached data. Other things done are in non-segmented write caches is to only cache write data for the current track (this is actually where the write cache does most of its good) and always flush it before doing any seek. Only broken WC designs loose data in a power out sitation. There are many broken designs out there. There are also many that work perfectly. The general tell tell on this is what state the WCE bit is in when the drive comes from the factory. Those manufactures who have good designs tend to ship with WCE on, those that tend to loose data always ship with WCE off. With the wonderful breakthroughs in supercapacitors it should now be possible to have some very large caches. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Major upgrade
Having done this before I would HIGHLY recommend doing a clean install and restoring the 'good stuff' from backup. You can do the upgrades in place, but it takes a while, and you have to do it in steps, and if you misstep you may blow up the box, and so on. You should know how to do clean installs and backups anyways. Since you have 2 machines, assuming sufficient clear disk space on each, you can back one up onto the other and so on. - Mike H. From: "Steffen Vorrix" <[EMAIL PROTECTED]> Date: Wed, 14 Mar 2001 10:44:34 -0500 Content-Type: multipart/alternative; boundary="=_NextPart_000_000B_01C0AC73.C2523D80" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-MDRemoteIP: 208.60.70.195 X-Return-Path: [EMAIL PROTECTED] X-MDaemon-Deliver-To: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] X-Loop: FreeBSD.ORG Precedence: bulk This is a multi-part message in MIME format. --=_NextPart_000_000B_01C0AC73.C2523D80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have been tracking this list for about 3 or 4 weeks now, and I have = learned alot more about FreeBSD then I thought I might. I have = successfully upgrade my two home FreeBSD machines from 4.2 REL to the = current stable version, and everything went just fine. However, I now = need to upgrade 2 production machines for my employer, and these have to = go as painlessly as possible. The problem is that these machines are = 3.4 REL. I have looked through the mail over the past weeks, and I have = found people mention that 3.4 to 4 can have some gotcha's associated = with it, but I haven't seen anything specifically mentioned. Are there = things that I need to watch out for? The reference that I am referring = to was a thread regarding remotely updating servers. While this was = frowned upon by almost everyone in the list, one person specifically = mentioned that remote updating would be a problem from a 3.x to a 4.x. = I don't plan to do any remote updating, but I want to be sure there = aren't other things I need to watch out for. Thanks a bunch. Chris Schremser --=_NextPart_000_000B_01C0AC73.C2523D80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have been tracking this list for = about 3 or 4=20 weeks now, and I have learned alot more about FreeBSD then I thought I=20 might. I have successfully upgrade my two home FreeBSD machines = from 4.2=20 REL to the current stable version, and everything went just fine. = However,=20 I now need to upgrade 2 production machines for my employer, and these = have to=20 go as painlessly as possible. The problem is that these machines = are 3.4=20 REL. I have looked through the mail over the past weeks, and I = have found=20 people mention that 3.4 to 4 can have some gotcha's associated with it, = but I=20 haven't seen anything specifically mentioned. Are there things = that I need=20 to watch out for? The reference that I am referring to was a = thread=20 regarding remotely updating servers. While this was frowned upon = by almost=20 everyone in the list, one person specifically mentioned that remote = updating=20 would be a problem from a 3.x to a 4.x. I don't plan to do any = remote=20 updating, but I want to be sure there aren't other things I need to = watch out=20 for. Thanks a bunch. Chris = Schremser --=_NextPart_000_000B_01C0AC73.C2523D80-- 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: Major upgrade
I've done the upgrade from 3.4 to 4.x stable a few times. I genrally go from 3.4->3.5-Stable and then 3.5-Stable -> 4.x-stable. Basically, if you follow the instructions in UPDATING, it should go well. If you take UPDATING seriously and actually reboot into single user when it tells you to, it will likely be painless. There are ways to get around going into single user, but if you have the luxury of a console, don't sweat it. -Marius On Wed, 14 Mar 2001, Steffen Vorrix wrote: > I have been tracking this list for about 3 or 4 weeks now, and I have learned alot >more about FreeBSD then I thought I might. I have successfully upgrade my two home >FreeBSD machines from 4.2 REL to the current stable version, and everything went just >fine. However, I now need to upgrade 2 production machines for my employer, and >these have to go as painlessly as possible. The problem is that these machines are >3.4 REL. I have looked through the mail over the past weeks, and I have found people >mention that 3.4 to 4 can have some gotcha's associated with it, but I haven't seen >anything specifically mentioned. Are there things that I need to watch out for? The >reference that I am referring to was a thread regarding remotely updating servers. >While this was frowned upon by almost everyone in the list, one person specifically >mentioned that remote updating would be a problem from a 3.x to a 4.x. I don't plan >to do any remote updating, but I want to be sure there aren't other things I need to >watch out for. > > Thanks a bunch. > > Chris Schremser > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: KDE 2.1
I had built this and run it under X4.02 until somebody broke it recently - it no longer builds, complaining about pthreads. - Mike Harding Date: Wed, 14 Mar 2001 08:42:42 -0500 From: "Brandon S. Allbery KF8NH" <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Sender: [EMAIL PROTECTED] X-Loop: FreeBSD.ORG Precedence: bulk On Wednesday, March 14, 2001 10:52:42 +0200, Irvine Short <[EMAIL PROTECTED]> wrote: +- | It now compiles straight out of the box, thanks for all the work guys! | | Now though it hangs a long time on "initialising peripherals" and then | gives me a plain grey screen. | | Anyone using it seccuessfully on FreeBSD? +--->8 I just built it... well, "just" meaning "it was compiling from Saturday morning until the middle of yesterday on my ancient dual-P200. I had similar hanging symptoms (kdeinit crashed, aborting startup) until I went back and rebuilt libpng. You might check to see if you have a kdeinit.core and a stack backtrace shows it dying in the PNG routines. -- brandon s. allbery [os/2][linux][solaris][japh] [EMAIL PROTECTED] system administrator[WAY too many hats] [EMAIL PROTECTED] electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] 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
Major upgrade
I have been tracking this list for about 3 or 4 weeks now, and I have learned alot more about FreeBSD then I thought I might. I have successfully upgrade my two home FreeBSD machines from 4.2 REL to the current stable version, and everything went just fine. However, I now need to upgrade 2 production machines for my employer, and these have to go as painlessly as possible. The problem is that these machines are 3.4 REL. I have looked through the mail over the past weeks, and I have found people mention that 3.4 to 4 can have some gotcha's associated with it, but I haven't seen anything specifically mentioned. Are there things that I need to watch out for? The reference that I am referring to was a thread regarding remotely updating servers. While this was frowned upon by almost everyone in the list, one person specifically mentioned that remote updating would be a problem from a 3.x to a 4.x. I don't plan to do any remote updating, but I want to be sure there aren't other things I need to watch out for. Thanks a bunch. Chris Schremser
Re: suspend/restore with ppp connections
On Tue, 13 Mar 2001, Mike Porter wrote: > Maybe it's just me, but why don't you just add into /etc/rc.suspend code to > ring down the ppp connection? (which is more or less what windoze does to get > around the pitfalls involved) In my experience, that's not enough. You actually have to power down the pcmcia card (or remove it, I suppose). Otherwise you get the crash on powerup, when something tries to use the device. The power thing might be a VAIO specific problem. --RDM To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
KDE2.1 ++ GNOME 1.2
I am having huge problems installing KDE2.1 and GNOME1.2 on the same box from the ports. It would seem that you cannot install both of them on the same box. Because I tried installing kde first, that worked, then gnome and the gnome build failed! Then I tried installing Gnome first than kde and the kde build failed. Any help here guys.! Colin Legendre CCNA, MCP [EMAIL PROTECTED]
Re: apache show "Exec format error"
At 10:16 PM 3/14/01 +1100, sam wun wrote: >Hi, > >I know this is not an appropriate newsgropu to post this msg, but I would >think >you guys konw more about it. >I got the following error when I tried to execue a perl program with calling >.css file: > >Exec format error: exec of /usr/local/cgi-bin/store/managerstylesheet.css >failed >[Wed Mar 14 22:10:03 2001] [error] [client 192.168.1.1] Premature end of >script >headers: >/usr/local/cgi-bin/store/managerstylesheet.css > >Does anyone know what is this all about? > >Thanks >Sam Sounds like /cgi-bin/ is set as a CGI Executable directory mapped to /usr/local/cgi-bin/, so it is trying to somehow execute a .css file which is normally some cascading style sheet file. .css files are like configuration files for html files IIRC. So that .css file should not be there but should be in the html root somewhere like /usr/local/htdocs/ -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
