RE: FreeBSD 5.1 stability
Well perhaps I'll hold off making world as I just cvsupped ;) Don't wanna lose any stability... -Original Message- From: Garance A Drosihn [mailto:[EMAIL PROTECTED] Sent: Thursday, 16 October 2003 03:16 To: Kris Kennaway; Valery V.Chikalov Cc: Martin Minkus; [EMAIL PROTECTED] Subject: Re: FreeBSD 5.1 stability At 11:28 PM -0700 10/14/03, Kris Kennaway wrote: >On Wed, Oct 15, 2003, Valery V.Chikalov wrote: > >> >10:21AM up 101 days, 17:12, 1 user, load averages: 0.33, 0.58, >> 0.44 > >> [EMAIL PROTECTED] uptime >> 8:22 up 112 days, 17:14, 1 user, load averages: 1,34 1,69 1,72 > >I can beat both of you :-) > >11:07PM up 147 days, 48 mins, 0 users, load averages: 2.29, 2.29, 2.24 > >That's a sparc64 in the bento package build cluster. I hate to rain on this parade, but that only tells us how reliable 5.x was 147 days ago. 5.x remains in a state of flux, and there have been many times in the last 147 days where you could cvsup into a very unstable system. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5.1 stability
I would just like to take this moment to congratulate all the people here who have made FreeBSD 5 the success that it is, and have put in all the hard work and effort to make it such a reliable and stable workhorse. I am not sure what sort of uptimes people have had with -CURRENT as it is a work in progress, but here is an uptime of a 5.1 box that has just passed 100 days. Unfortunately this machine has to move now which means shutting down so the uptime will be lost (and i have cvsup'd her just a few minutes ago), but it shows the reliability that we now have in FreeBSD 5. This box is a Dual CPU system with SCSI and IDE drives, two NIC's, and gets thrashed quite heavily at times. Keep up the good work people! :) Martin. diablo:~> uname -a FreeBSD diablo.diskiller.net 5.1-CURRENT FreeBSD 5.1-CURRENT #5: Thu Jun 12 20:19:23 CST 2003 [EMAIL PROTECTED]:/junk/src/sys/i386/compile/DIABLO i386 diablo:~> uptime 10:21AM up 101 days, 17:12, 1 user, load averages: 0.33, 0.58, 0.44 diablo:~> date Wed Oct 15 10:21:40 CST 2003 diablo:~> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Realtek 8139B detected
During boot, i get the following: rl0: port 0x6100-0x61ff mem 0xe1001000-0xe10010ff ir q 10 at device 14.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:00:21:f2:a5:47 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: port 0x6200-0x62ff mem 0xe100-0xe1ff ir q 12 at device 15.0 on pci0 rl1: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl1: Ethernet address: 00:00:21:f4:d8:7d miibus1: on rl1 rlphy1: on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ed0: port 0x6300-0x631f irq 5 at device 16. 0 on pci0 ed0: address 00:40:05:3b:eb:c9, type NE2000 (16 bit) And i basically find that my realtek network cards are useless. I can manually set them using ifconfig to use 100baseTX, etc, but they are NOT very happy in 100mbit mode, nor will they work in full duplex. (This evidence is supported by me looking at the LEDs that are illuminated on the switch). In FreeBSD 4.0 to 4.7-STABLE this has never been a problem. Why is the driver broken in 5.0? We are going backwards now? ;) I simply cannot make any realtek cards work. My only other cards are crappy old NE2000 compatibles (ISA's!) that are laying around, and haven't been used in a few years. And yeah, they are only 10mbit :/ What is going on? I really want to start upgrading to 5.0 (There are no other issues, and some people i know have been running 5.0-CURRENT ever since work on 5.0 began). Martin. -------- Martin Minkus Geac Enterprise Solutions 208 Greenhill Road, Eastwood 5063, South Australia Tel: +61 8 8372 6111 / Fax: +61 8 8372 6196 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SBlive driver
On Mon, 10 Apr 2000, Kent Hauser wrote: > Doug, > > On my -CURRENT system (from last week), I also found that > the SBlive driver caused spontaneous reset -- no panic, no > dump, just reset. I was using "realaudio7" as my audio > source. > > Kent I moved the SB Live driver from 5.0 into 4.0, and am using it with no ill effect. xmms, and several other programs (like emulators) use it fine, perfect crisp sound (only wavs play bad?), and 4.0 has not been crashing, or resetting, or anything. I've been using it like this for a few days. When will it be backported into 4.0? *hint* *hint* martin. -- Martin Minkus aka DiSKiLLeR Email: [EMAIL PROTECTED] Web: http://www.diskiller.net I live in a world of paradox... my willingness to destroy is your chance for improvement, my hate is your faith, my failure is your victory - a victory that won't last. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 problems...
On Fri, 7 Apr 2000, Thomas D. Dean wrote: > I had this problem a week ago. > > It was caused by my booting the kernel directly. > > 0:da(0,a)/kernel > > Using > > 0:da(0,a)/boot/loader > > cures the symptoms. Ohhh!! This explains why i get the same top: nlist failed error in 5.0. That machine's BIOS won't boot the hdd for some reason (beats the heck out o me, worked a few days ago), so i use a boot disk to boot FreeBSD 5.0 and Win2k. I just use 0:ad(0,a)/kernel. No wonder :) martin. -- Martin Minkus aka DiSKiLLeR Email: [EMAIL PROTECTED] Web: http://www.diskiller.net I live in a world of paradox... my willingness to destroy is your chance for improvement, my hate is your faith, my failure is your victory - a victory that won't last. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
