Re: PC-BSD and DesktopBSD compared to FreeBSD
Hello Charles, Thanks for your insight. I would also like to express my views in this regard. Every OS has a target audience and every OS has its own strengths and weaknesses. Something which would nicely for you does not mean that it would work exactly the same way for everyone else in the world. You are free to have personal opinions but please be kind enough to keep them *personal*. What you have done could very well generate a troll. PLEASE DO NOT TROLL. Also to the best of my knowledge the purpose of this list is to discuss about the different features/ changes of the STABLE tree. Feel free to move the discussion to advocacy@ mailing list. Thanks and Best Regards Subhro On 9/15/06, Charles P. Schaum [EMAIL PROTECTED] wrote: A note on PC-BSD and DesktopBSD as compared to my -STABLE experiences: -STABLE works best. First, PC-BSD will panic under more conditions than -RELEASE, -STABLE or DesktopBSD. I did some monkeying around and found that to be true, especially with older boxes. Second, DesktopBSD works better than PC-BSD, and noticeably so. But it's based on 5 and I want 6. So that kinda throws a spanner in the works. Both desktop installers, however, do not easily support an install over multiple disks or a lot of customization. FreeBSD does. That's the same reason why I like the Debian installer and the old Ubuntu installer over many of the others. (Although the Ubuntu installer, old and new, has geometry issues.) Fedora's default is to use an LVM setup that will be a pain in the tush if you install anything else over it unless you use a third-party util to hose all the LVM info. Merely creating a new FS, i.e., installing FBSD in the slice where Fedora was, won't cut it; you will get weirdness in the boot loader. When I want desktop, I don't want dumb. I want defaults for those that want them and then I want to depart from that when needed. The desktop attempts based on FreeBSD do not easily handle this. I see that as basically a show-stopper. The elegant thing about FreeBSD is the way in which one can vary things to meet individual needs. This is no canonical distro template mentality. The real trick is to make a desktop work with such variation. One thing I see, for example, is an opportunity to have a decision like here is some default art, themes, whatever in a port/package for those that want a my machine looks like FreeBSD feel. One might suggest that all ports that would normally be associated with menus and MIME types in XFCE, KDE and Gnome, etc. would arrange to install these in the expected places. Presently, some do; some don't. One need not integrate a lot into the OS. Indeed, scripts for removable media events and the like can safely remain in ports. But it strikes me that Linux and Windows, as well as MacOS, all have a certain look and feel per distro and that a move to say for those that want a default option of look and feel and don't want to continually edit menus (for which KDE is easiest) then we have a plan for you. This would not add too much burden to the port maintainers and it would just make the learning curve a little easier for noobs, until they do a BOFH-recommended action after failing to RTFM. Even running the autoconfig for X, if X is installed, and allowing a GUI login manager selection menu in the installer couldn't hurt. After all, if one bundles things like Gnome and KDE on distribution media, why not go the distance and give the option to do all the preliminary integration in the installer, if so selected? For example, I have no problem installing NetBSD, knowing that I first go to the utility menu and set up the NIC, then install, then say yes, I want those NIC settings to save some work, then do the reboots and set things up. Then I tweak more files and add software with pkgsrc. But that's extra work that FreeBSD already integrates to some extent into one installer session. Why not continue along that path? What about a menu that allows an expert mode for certain stages as well as just a default decision like I want FreeBSD with KDE/Gnome. For example, if pdftk or ImageMagick blow up /var/tmp when batch converting or if OpenOffice takes about 9G to compile, then one could consider a resource needs database correlating to packages desired at install time. Given, that puts stress on the size of the image. It could also be a DVD-only option. One could select the ports that one would eventually like (perhaps like synaptic) and the needs could be anticipated for install-time FS-tuning. A subsequent option might allow installation via pkg_add or simply set up a script and notify root to run it in the background to fetch and install the desired packages at a later time. Such an approach would take the selection of distributions and packages to perhaps another level. Yes, it violates the small is better dictum but it also recognizes that the folks at the middle of the bell curve are great in number and short on technical mastery. The decision comes
Re: Regression Tests ...
On Thu, Sep 14, 2006 at 10:53:27PM -0300, Marc G. Fournier wrote: For the PostgreSQL Project, we have a 'build farm' ... something that I think is similar to the tinderboxes ... but, their point isn't to just build the source tree, but to run its regression tests, and report when something fails: http://www.pgbuildfarm.org/cgi-bin/show_status.pl We do have something similar - Peter Holm's Stress: http://people.freebsd.org/~pho/stress/ He has a presentation at: http://www.linuxforum.dk/2006/slides/peterholm-lf06.pdf David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PC-BSD and DesktopBSD compared to FreeBSD
Charles P. Schaum wrote: A note on PC-BSD and DesktopBSD as compared to my -STABLE experiences: -STABLE works best. First, PC-BSD will panic under more conditions than -RELEASE, -STABLE or DesktopBSD. I did some monkeying around and found that to be true, especially with older boxes. Second, DesktopBSD works better than PC-BSD, and noticeably so. But it's based on 5 and I want 6. So that kinda throws a spanner in the works. The DesktopBSD development version is based on 6-Stable. they're waiting for the 6.2 release to release their new release. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Regression Tests ...
On Fri, 15 Sep 2006, 07:42+0100, David Malone wrote: On Thu, Sep 14, 2006 at 10:53:27PM -0300, Marc G. Fournier wrote: For the PostgreSQL Project, we have a 'build farm' ... something that I think is similar to the tinderboxes ... but, their point isn't to just build the source tree, but to run its regression tests, and report when something fails: http://www.pgbuildfarm.org/cgi-bin/show_status.pl We do have something similar - Peter Holm's Stress: http://people.freebsd.org/~pho/stress/ He has a presentation at: http://www.linuxforum.dk/2006/slides/peterholm-lf06.pdf Actually, stress perfomance tests are a different class of the tests. What we have in tools/regression are regression tests but the main problem we still don't have a unified way to write them and no infrastructure to run and report results. E.g. at the moment you can't cd /usr/src/tools/regression/ make. Perhaps we just need to steal NetBSD's bits until we invent something better. Btw, there is an item in the project ideas list: http://www.freebsd.org/projects/ideas/#p-regression -- Maxim Konovalov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: arrrrgh! Guys, who's breaking -STABLE's gmirror code?!
On Sep 15, 2006, at 24:34, hackmiester (Hunter Fuller) wrote: Hahahahaha... That's ironic... That wasn't meant to be ironic. Years of experience and observations of development lead to this conclusion. RIght. All i can say, though, is that someone that doesn't know any better would probably not think Oh! That means that upgrades are possible between releases, and not that my system will actually run, or anything! It just seems it'd be quite a cause of confusion. So, actually Microsoft may be correctly claiming that WindowsXP is more stable than Linux. That it spontaneously reboots as soon as I bore it isn't related at all... -- Alban Hertroys This person has performed an illegal operation, and will be shot down. !DSPAM:74,450a59b47241130310126! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Thanks
Thank you for the information and direction. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Followup on ACPI resume problems in STABLE
[ followup to
http://lists.freebsd.org/pipermail/freebsd-mobile/2006-September/008993.html ]
Hi all,
I went back to RELENG_6, updated, and rebuilt world and kernel, but this time
the GENERIC one. Similar (or possibly the same) lockup as with RELENG_6 and my
custom kernel.
I tried the suspend/ resume several times, each of them end up with a crash and
no info on log/messages or kernel dump.
On resume, the screen would turn a soft white colour. I could press
Caps lock and the LED would respond. In some instances, going to the console
where X is running would work, but it'd lock up within seconds. In most cases,
everything would lock up within 10 seconds, with no change in what I'd see on
screen. Caps lock LED would stop responding too.
I'm back to RELENG_6_1 now with my custom kernel...and rebuilding some
of my installed ports as some didnt like the regression.
I'd love to help, but i'm at loss wrt what to try next.
Cheers,
B
_
{Beto|Norberto|Numard} Meijome
Unix is user friendly. However, it isn't idiot friendly.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: page fault in kern_kevent
Hi,
Just wanted to say that I have the same problem, kernel crashing because
of kernel queues usage in Squid 2.6. I've reported some more information
on:
http://www.freebsd.org/cgi/query-pr.cgi?pr=103127
On Mon, Jul 17, 2006 at 12:20:29AM +0200, Pawel Worach wrote:
Under moderate kqueue load I caught the following:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x20:0x0
stack pointer = 0x28:0xe745db78
frame pointer = 0x28:0xe745dbb8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 582 (squid)
trap number = 12
panic: page fault
KDB: stack backtrace:
kdb_backtrace(c065b33b,c06a4780,c065344e,e745da80,100) at kdb_backtrace+0x2e
panic(c065344e,c066df69,c49c0dd0,1,1) at panic+0xb7
trap_fatal(e745db38,0,1,0,c05239e2) at trap_fatal+0x33e
trap_pfault(e745db38,0,0,e745db38,0) at trap_pfault+0x242
trap(c05e0008,c7310028,28,0,4) at trap+0x350
calltrap() at calltrap+0x5
--- trap 0xc, eip = 0, esp = 0xe745db78, ebp = 0xe745dbb8 ---
MAXCPU(c4b20500,e745dbe8,c65c3300,1,c0c38000) at 0
kern_kevent(c65c3300,3,5,80,e745dcbc) at kern_kevent+0xf8
kevent(c65c3300,e745dd04,18,16,c65c3300) at kevent+0x7a
syscall(821003b,3b,822003b,48106cf0,bfbfeec8) at syscall+0x380
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (363, FreeBSD ELF32, kevent), eip = 0x4821ccfb, esp =
0xbfbfedfc, ebp = 0xbfbfee48 ---
Uptime: 3d15h16m7s
Dumping 1023 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 1023MB (261884 pages) 1008 992 976 960 944 928 912 896 880
864 848 832 816 800 784 768 752 736 720 704 688 672 656 640 624 608 592
576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 336 320 304
288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc04c261c in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc04c299d in panic (fmt=0xc065344e %s)
at /usr/src/sys/kern/kern_shutdown.c:565
#3 0xc0637f7e in trap_fatal (frame=0xe745db38, eva=0)
at /usr/src/sys/i386/i386/trap.c:836
#4 0xc0637c12 in trap_pfault (frame=0xe745db38, usermode=0, eva=0)
at /usr/src/sys/i386/i386/trap.c:744
#5 0xc0637780 in trap (frame=
{tf_fs = -1067581432, tf_es = -953090008, tf_ds = 40, tf_edi = 0,
tf_esi = 4, tf_ebp = -414852168, tf_isp = -414852252, tf_ebx = 4, tf_edx
= -953052640, tf_ecx = -1066925280, tf_eax = -1066924800, tf_trapno =
12, tf_err = 0, tf_eip = 0, tf_cs = 32, tf_eflags = 66118, tf_esp =
-1068903001, tf_ss = -953052640})
at /usr/src/sys/i386/i386/trap.c:434
#6 0xc062498a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0x in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) l *kern_kevent+0xf8
0xc049c6d8 is in kern_kevent (/usr/src/sys/kern/kern_event.c:637).
632 goto done;
633 changes = keva;
634 for (i = 0; i n; i++) {
635 kevp = changes[i];
636 kevp-flags = ~EV_SYSFLAGS;
637 error = kqueue_register(kq, kevp, td, 1);
638 if (error) {
639 if (nevents != 0) {
640 kevp-flags = EV_ERROR;
641 kevp-data = error;
System is i386 UP running FreeBSD 6.1-STABLE #0: Sun Jul 9 01:11:16
CEST 2006
--
Pawel
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Anders.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em0: watchdog timeout -- resetting (6.1-STABLE)
I'm also seeing these on a Supermicro PDSMi board with a recent stable. Please tell me what debugging info that is needed to fix this. /Martin FreeBSD mailbox 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Sun Sep 10 17:43:15 CEST 2006 [EMAIL PROTECTED]:/usr/obj-local/usr/src/sys/SMP amd64 lspci -v output: 04:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03) Subsystem: Super Micro Computer Inc Unknown device 108c Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at ed20 (32-bit, non-prefetchable) I/O ports at 4000 Capabilities: [c8] Power Management version 2 Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [e0] Express Endpoint IRQ 0 05:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller Subsystem: Super Micro Computer Inc Unknown device 109a Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at ed30 (32-bit, non-prefetchable) I/O ports at 5000 Capabilities: [c8] Power Management version 2 Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [e0] Express Endpoint IRQ 0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
Jamie Bowden schrieb: On 9/9/06, Mark Andrews [EMAIL PROTECTED] wrote: Yeah, -STABLE is what you should run if you want stable code, right? No. STABLE means STABLE API. If you want stable code you run releases. Between releases stable can become unstable. Think of stable as permanent BETA code. Changes have passed the first level of testing in current which is permanent ALPHA code. No, this is what it means now. [...] Why do you say No if you mean Yes, but in former times ...? Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bge watchdog timeouts still happening
On Mon, Sep 11, 2006 at 02:17:22AM +0200, Herve Boulouis wrote: H Hi, H H I've recently put into production 2 web servers with 6.0-STABLE from H mid january and was bitten by the bge watchdog timeouts problems. H H I cvsupped the 2 boxes with the latest -stable (latest if_bge.c, H rev 1.91.2.17) but the problem still persists :( H H Server hardware is Dell poweredge 2550 with SMP kernel. H H Relevant portion of dmesg : H H bge0: Broadcom BCM5700 B2, ASIC rev. 0x7102 mem 0xfeb0-0xfeb0 irq 17 at device 8.0 on pci1 H miibus0: MII bus on bge0 H brgphy0: BCM5401 10/100/1000baseTX PHY on miibus0 H brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto H bge0: Ethernet address: 00:06:5b:1a:7f:4a Is it integrated or not? I've got exactly the same NIC and I can try to reproduce the problem if you describe the workload. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI it failed in Acer Ferrari 4005 wmli
On Sep 14, 2006, at 5:50 PM, Maher Mohamed wrote: The ACPI is not working on my machine, I am using FreeBSD 6.1 Stable. How can i fix and if there is any instruction regarding the fix, please do not just mention just some files, but rather instruct me where and how to put So you want specific instructions to fix a vague problem description? First, state precisely how ACPI is not working and the perhaps someone can tell you what to do. Also, is this Acer Ferrari 4005 wmli machine i386 or amd64? Are you booting from CD to install or what? Upgrade? You should also try backing to 6.1-RELEASE CD and see what happens. I'll put on my mindreader hat and guess that you probably need to just disable the ACPI timer. You do that at the boot menu by escaping to the boot prompt (option 6) then typing set debug.acpi.disabled=timer then type 'boot'. To make it permanent, put the above line without the word set into /boot/loader.conf
Re: em0: watchdog timeout -- resetting (6.1-STABLE)
On Thu, Sep 14, 2006 at 02:27:29AM +0200, Ronald Klop wrote: Them manual page em(4) mentions trying another cable when the watchdog timeout happens, so I tried that. But it didn't help. Is there anything I can test to (help) debug this? It happens a lot when my machine is under load. (100% CPU) Is it possible that it happens since I upgraded the memory from 1GB to 2 GB? I don't think it's the cable. I started getting these recently as well (starting about a week ago). Always when there's a lot of CPU and disk I/O load. Also sometimes my USB keyboard would become unresponsive at about the same time (under high load). Sometimes it would stutter and act like the key was being held down for a second or two. I built a new kernel (6.2-PRE now) on 9/12. The keyboard problem seems to be gone but I still get the em watchdog timeouts occasionally. Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
=?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= wrote: Jamie Bowden schrieb: On 9/9/06, Mark Andrews [EMAIL PROTECTED] wrote: Yeah, -STABLE is what you should run if you want stable code, right? No. STABLE means STABLE API. If you want stable code you run releases. Between releases stable can become unstable. Think of stable as permanent BETA code. Changes have passed the first level of testing in current which is permanent ALPHA code. No, this is what it means now. [...] Why do you say No if you mean Yes, but in former times ...? Stable is a misnomer that harms FreeBSD somewhat. A promoter of FreeBSD I know has long encouraged people to upgrade from release to stable. Some don't won't realise Stable is Not necessarily Stable, may get burnt. Much of the world speaks English only as a 2nd language. They won't benefit from the double trouble of foreign + weird BSD geek speak: Stable isn't Stable ? Yes or No ! It's stable, but it's OK to crash ? - I'll go Linux ! Imagine a boat labelled Stable: It sinks. The designers claim: Tough! We left the Application Interface (routes to bars toilets) stable, but changed other stuff. Hey ! Stable never meant Stable ! It'd be some work to eradicate the misnomer, but the name's perhaps less entrenched than one might guess, eg: ftp ftp.freebsd.org cd /pub/FreeBSD dir lrwxr-xr-x 1 ftpuser ftpusers19 Mar 24 14:58 FreeBSD-stable - branches/4.0-stable cd FreeBSD-stable 550 No such directory. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
On 15 September 2006, at 11:16, Julian H. Stacey wrote: Stable is a misnomer that harms FreeBSD somewhat. A promoter of FreeBSD I know has long encouraged people to upgrade from release to stable. Some don't won't realise Stable is Not necessarily Stable, may get burnt. Much of the world speaks English only as a 2nd language. They won't benefit from the double trouble of foreign + weird BSD geek speak: Stable isn't Stable ? Yes or No ! It's stable, but it's OK to crash ? - I'll go Linux ! Imagine a boat labelled Stable: It sinks. The designers claim: Tough! We left the Application Interface (routes to bars toilets) stable, but changed other stuff. Hey ! Stable never meant Stable ! This is the perfect explanation. Thank you for putting what I am trying to say in words so well. :-) It'd be some work to eradicate the misnomer, but the name's perhaps less entrenched than one might guess, eg: ftp ftp.freebsd.org cd /pub/FreeBSD dir lrwxr-xr-x 1 ftpuser ftpusers19 Mar 24 14:58 FreeBSD- stable - branches/4.0-stable cd FreeBSD-stable 550 No such directory. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http:// berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable- [EMAIL PROTECTED] -- hackmiester (Hunter Fuller) svinx yknow when you go to a party, and everyones hooked up except one guy and one girl svinx and so they look at each other like.. do we have to? svinx intel nvidia must be lookin at each other like that right now Phone Voice: +1 251 589 6348 Fax: Call the voice number and ask. Email General chat: [EMAIL PROTECTED] Large attachments: [EMAIL PROTECTED] SPS-related stuff: [EMAIL PROTECTED] IM AIM: hackmiester1337 Skype: hackmiester31337 YIM: hackm1ester Gtalk: hackmiester MSN: [EMAIL PROTECTED] Xfire: hackmiester ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bge watchdog timeouts still happening
Le 15/09/2006 18:05, Gleb Smirnoff a ?crit: H bge0: Broadcom BCM5700 B2, ASIC rev. 0x7102 mem 0xfeb0-0xfeb0 irq 17 at device 8.0 on pci1 H miibus0: MII bus on bge0 H brgphy0: BCM5401 10/100/1000baseTX PHY on miibus0 H brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto H bge0: Ethernet address: 00:06:5b:1a:7f:4a Is it integrated or not? I've got exactly the same NIC and I can try to reproduce the problem if you describe the workload. Yes, it's the onboard bge. Workload is 10-25 Mbit/s of web hosting. -- Herve Boulouis ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DNS query performance
You have tested with a GENERIC kernel? You should remove all debugging kernel options before testing performance. Sure. Removing debug I got: Kernel UP Timecounter queries/s --- - TSC 16541 There is no difference. -- Att., Marcelo Gardini ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
Julian H. Stacey wrote: Stable is a misnomer that harms FreeBSD somewhat. I agree. A promoter of FreeBSD I know has long encouraged people to upgrade from release to stable. Some don't won't realise Stable is Not necessarily Stable, may get burnt. Much of the world speaks English only as a 2nd language. They won't benefit from the double trouble of foreign + weird BSD geek speak: Stable isn't Stable ? Yes or No ! It's stable, but it's OK to crash ? - I'll go Linux ! Imagine a boat labelled Stable: It sinks. The designers claim: Tough! We left the Application Interface (routes to bars toilets) stable, but changed other stuff. Hey ! Stable never meant Stable ! It'd be some work to eradicate the misnomer, but the name's perhaps less entrenched than one might guess, eg: ftp ftp.freebsd.org cd /pub/FreeBSD dir lrwxr-xr-x 1 ftpuser ftpusers19 Mar 24 14:58 FreeBSD-stable - branches/4.0-stable cd FreeBSD-stable 550 No such directory. Why not rename 'stable' into 'stable-api' ? -- Hans Lambermont ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
On Fri, 15 Sep 2006, Hans Lambermont wrote: Julian H. Stacey wrote: Stable is a misnomer that harms FreeBSD somewhat. I agree. A promoter of FreeBSD I know has long encouraged people to upgrade from release to stable. Some don't won't realise Stable is Not necessarily Stable, may get burnt. Much of the world speaks English only as a 2nd language. They won't benefit from the double trouble of foreign + weird BSD geek speak: Stable isn't Stable ? Yes or No ! It's stable, but it's OK to crash ? - I'll go Linux ! Imagine a boat labelled Stable: It sinks. The designers claim: Tough! We left the Application Interface (routes to bars toilets) stable, but changed other stuff. Hey ! Stable never meant Stable ! It'd be some work to eradicate the misnomer, but the name's perhaps less entrenched than one might guess, eg: ftp ftp.freebsd.org cd /pub/FreeBSD dir lrwxr-xr-x 1 ftpuser ftpusers19 Mar 24 14:58 FreeBSD-stable - branches/4.0-stable cd FreeBSD-stable 550 No such directory. Why not rename 'stable' into 'stable-api' ? Or rename it what it is: 6.x-BETA Where x == the next -RELEASE ... But, I'm just curious here ... for all of the talk going around about this whole issue, how many ppl have truly ever been bitten by an unstable -STABLE? And for those that have, how long did it take to get help from a developer to get it fixed? In the case that started this thread, it seems to be that the developer fixed his mistake fairly quickly, which is what one would expect ... it shouldn't be so much that he *broke* -STABLE (shit happens, do you want your money back?), but it should be 'was he around to reverse his mistake in a reasonable amount of time?' ... ? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
Hans Lambermont wrote: Why not rename 'stable' into 'stable-api' ? .. or just stop calling it STABLE and call it RELENG_6 instead, which is what you are actually fetching from cvs :-) /Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
Marc G. Fournier wrote: On Fri, 15 Sep 2006, Hans Lambermont wrote: Julian H. Stacey wrote: Stable is a misnomer that harms FreeBSD somewhat. ... Why not rename 'stable' into 'stable-api' ? Or rename it what it is: 6.x-BETA Where x == the next -RELEASE ... Also fine by me :) I followed this long thread in slight amazement, but the 'what is stable' confusion is very recognizable. I'm open for changing the name. In the case that started this thread, it seems to be that the developer fixed his mistake fairly quickly, which is what one would expect ... it shouldn't be so much that he *broke* -STABLE (shit happens, do you want your money back?), but it should be 'was he around to reverse his mistake in a reasonable amount of time?' ... ? I think the answer is yes (and always has been afaik). regards, Hans Lambermont ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2 Release Cycle
FYI - we have begun the release cycle for FreeBSD-6.2. Code freeze on the RELENG_6 branch started last week. For people in the habit of tracking RELENG_6 you will start to notice various pieces of it that start saying 6.2 for version numbers (despite 6.2 not being officially released) as we progress through the release cycle. Sorry if that causes a bit of confusion or problems but we need to do this as part of the BETA/RC testing that gets done. Bumping things like the FreeBSD_version to reflect 6.2 now gives the ports folks a chance to get ready for it as part of their preparations for the release, etc. The current targets for the BETAs/RCs/Release are: BETA1 Sep. 17 BETA2 Oct. 1 RC1 Oct. 15 RC2 Oct. 29 RELEASE Nov. 13 We'll give a bit more information along with the BETA1 announcement. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
On Fri, Sep 15, 2006 at 03:41:04PM -0300, Marc G. Fournier wrote: But, I'm just curious here ... for all of the talk going around about this whole issue, how many ppl have truly ever been bitten by an unstable -STABLE? And for those that have, how long did it take to get help from a developer to get it fixed? After installing from 5.4-RELEASE, I've tracked stable, and I haven't had any real problems. This is a desktop system, not a server, BTW. Maybe it depends on the frequency of updating? I usually update after there has been a security advisory that affects me. Otherwise, if it ain't broken... shouldn't be so much that he *broke* -STABLE (shit happens, do you want your money back?), :-) Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpdquFzheEVn.pgp Description: PGP signature
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
On Fri, Sep 15, 2006 at 08:46:57PM +0200, Martin Nilsson wrote: Hans Lambermont wrote: Why not rename 'stable' into 'stable-api' ? .. or just stop calling it STABLE and call it RELENG_6 instead, which is what you are actually fetching from cvs :-) That's a good idea, IMHO. When I started with FreeBSD I found the difference between the branch names and cvs tags confusing. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpCYv8bks5SA.pgp Description: PGP signature
Re: bge watchdog timeouts still happening
On Friday 15 September 2006 09:28, Herve Boulouis wrote: Le 15/09/2006 18:05, Gleb Smirnoff a écrit: H bge0: Broadcom BCM5700 B2, ASIC rev. 0x7102 mem 0xfeb0-0xfeb0 irq 17 at device 8.0 on pci1 H miibus0: MII bus on bge0 H brgphy0: BCM5401 10/100/1000baseTX PHY on miibus0 H brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto H bge0: Ethernet address: 00:06:5b:1a:7f:4a Is it integrated or not? I've got exactly the same NIC and I can try to reproduce the problem if you describe the workload. Yes, it's the onboard bge. Workload is 10-25 Mbit/s of web hosting. It seems to be at the top of the tree somewhere because people are also seeing the watchdog timeouts on em and I get them on the gigabit re's. I got them downloading the kde-3.5.4 distfiles on a 768kb DSL line. I had setiathome running, which keeps the cpu useage close to 100%. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ I am Andean project. http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bge watchdog timeouts still happening
On Fri, 2006-09-15 at 12:33 -0700, Kent Stewart wrote: On Friday 15 September 2006 09:28, Herve Boulouis wrote: Le 15/09/2006 18:05, Gleb Smirnoff a écrit: H bge0: Broadcom BCM5700 B2, ASIC rev. 0x7102 mem 0xfeb0-0xfeb0 irq 17 at device 8.0 on pci1 H miibus0: MII bus on bge0 H brgphy0: BCM5401 10/100/1000baseTX PHY on miibus0 H brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto H bge0: Ethernet address: 00:06:5b:1a:7f:4a Is it integrated or not? I've got exactly the same NIC and I can try to reproduce the problem if you describe the workload. Yes, it's the onboard bge. Workload is 10-25 Mbit/s of web hosting. It seems to be at the top of the tree somewhere because people are also seeing the watchdog timeouts on em and I get them on the gigabit re's. I got them downloading the kde-3.5.4 distfiles on a 768kb DSL line. I had setiathome running, which keeps the cpu useage close to 100%. FWIW, I get repeated watchdog timeout errors on 6-STABLE with a dc-based Cardus NIC (Netgear FA511). The worst behaviour I observed was under heavy NFS load, with the link being unavailable for extended periods of time. Mostly, though, the problem manifests itself when the card is inserted and the interface is trying to be brought up via DHCP using dhclient, as if the NIC is not being initialised properly, perhaps. I don't know if this is the same problem, but I thought I'd mention it. Cheers, Paul. -- e-mail: [EMAIL PROTECTED] Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid. --- Frank Vincent Zappa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
On Fri, 15 Sep 2006, Roland Smith wrote: On Fri, Sep 15, 2006 at 08:46:57PM +0200, Martin Nilsson wrote: Hans Lambermont wrote: .. or just stop calling it STABLE and call it RELENG_6 instead That's a good idea, IMHO. When I started with FreeBSD I found the difference between the branch names and cvs tags confusing. Let me second that. I hadn't realised that STABLE==RELENG_n (where n is the current version number) until very recently, and I've seen the STABLE isn't stable thing crop up over and over again over the last few years, both on mailing lists and IRC. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em0: watchdog timeout -- resetting (6.1-STABLE)
Something with em0 is really wrong. I dont get timeouts, but Before cvsup I had 6.0-PRERELEASE and didn't have a problem. Now I have FreeBSD 6.2-PRERELEASE #8: Fri Sep 15 03:44:49 MSD 2006 and the problem is so: (On machine I have LARGE_NAT, em0, em1, em2) on fresh system ping to www.ru from client computer (goes to inet via nat) is 3-5ms after few hours (i see it in the night) then traffic is smaller ping to www.ru is 11-12 ms. Why? after reboot it still gut for a few ours. FreeBSD/amd64 kernel with options DEVICE_POLLING options HZ=2500 with HZ=1000 and without DEVICE_POLLING nothing changes - 11-12 still goes after few hours. PS Should I downgrade to 6.0-RELEASE or earlier or tonight cvsup updates could resolve a problem (files sounds like tcp...): Checkout src/sys/contrib/ipfilter/netinet/ip_nat.h Edit src/sys/netinet/in_pcb.c Edit src/sys/netinet/tcp_input.c Edit src/sys/netinet/tcp_subr.c Edit src/sys/netinet/tcp_timer.c Edit src/sys/netinet/tcp_timer.h Edit src/sys/netinet/tcp_var.h Edit src/sys/sys/param.h Edit src/usr.sbin/pkg_install/add/main.c PPS Now I rebuild kernels and tomorrow night will se. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
On Fri, Sep 15, 2006 at 03:41:04PM -0300, Marc G. Fournier wrote: On Fri, 15 Sep 2006, Hans Lambermont wrote: Julian H. Stacey wrote: Stable is a misnomer that harms FreeBSD somewhat. I agree. A promoter of FreeBSD I know has long encouraged people to upgrade from release to stable. Some don't won't realise Stable is Not necessarily Stable, may get burnt. Much of the world speaks English only as a 2nd language. They won't benefit from the double trouble of foreign + weird BSD geek speak: Stable isn't Stable ? Yes or No ! It's stable, but it's OK to crash ? - I'll go Linux ! Imagine a boat labelled Stable: It sinks. The designers claim: Tough! We left the Application Interface (routes to bars toilets) stable, but changed other stuff. Hey ! Stable never meant Stable ! You've got a good point. Wouldn't be be best to merge the mythical last-bug from x-BETA+ into x and have release-x be the (abs) most stable *for that release*? I have generally run -STABLE ((now/then -RELEASE)); it is to the developers' credit [[all get 5 stars from here!]] that -STABLE has run so flawlessly until now. ---Yeah, I am speaking only for myself; what else :-). Or rename it what it is: 6.x-BETA Where x == the next -RELEASE ... But, I'm just curious here ... for all of the talk going around about this whole issue, how many ppl have truly ever been bitten by an unstable -STABLE? And for those that have, how long did it take to get help from a developer to get it fixed? Indeed. This snafu didn't bite me because I was at 5.4... and right, hat's off and cheers for Pawel Dawidek. Everyone shouldbe as consciencious --it'd be a vastly better world (.) gary In the case that started this thread, it seems to be that the developer fixed his mistake fairly quickly, which is what one would expect ... it shouldn't be so much that he *broke* -STABLE (shit happens, do you want your money back?), but it should be 'was he around to reverse his mistake in a reasonable amount of time?' ... ? -- Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em0: watchdog timeout -- resetting (6.1-STABLE)
On 9/14/06, David C. Myers [EMAIL PROTECTED] wrote: watchdogs mean that the transmit ring is not being cleaned, so the question is what is your machine doing at 100% cpu, if its that busy the network watchdogs may just be a side effect and not the real problem? I get them with a completely idle machine. My home directory is mounted via NFS (from FreeBSD 6.1 on an amd64 machine), and with the kernel from earlier this week, the machine would just hang for 30 seconds to a couple of minutes. A slew of watchdog timeout messages would appear. Then I'd get a moment's responsiveness out of the machine, then another long wait, then a moment's responsiveness, then a long wait... The machine would never recover from this cycle (at least, so far as I was patient enough to wait). Going back to a kernel dated late July resolved everything. Someone else asked me for the hardware version of my em0 board... [EMAIL PROTECTED]:10:0: class=0x02 card=0x002e8086 chip=0x100e8086 rev=0x02 hdr=0x00vendor = 'Intel Corporation' device = '82540EM Gigabit Ethernet Controller' class= network subclass = ethernet Could you perhaps go back to the kernel you say was stable and then drop in the latest em driver? Or if that has issues building do it the other way around, take the em driver from the build that gave you no problems and put it on this kernel you are running now? It would be helpful to know if this is a driver problem or something in the stack. Cheers, Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em0: watchdog timeout -- resetting (6.1-STABLE)
On 9/15/06, Martin Nilsson [EMAIL PROTECTED] wrote: I'm also seeing these on a Supermicro PDSMi board with a recent stable. Please tell me what debugging info that is needed to fix this. /Martin FreeBSD mailbox 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Sun Sep 10 17:43:15 CEST 2006 [EMAIL PROTECTED]:/usr/obj-local/usr/src/sys/SMP amd64 lspci -v output: 04:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03) Subsystem: Super Micro Computer Inc Unknown device 108c Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at ed20 (32-bit, non-prefetchable) I/O ports at 4000 Capabilities: [c8] Power Management version 2 Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [e0] Express Endpoint IRQ 0 05:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller Subsystem: Super Micro Computer Inc Unknown device 109a Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at ed30 (32-bit, non-prefetchable) I/O ports at 5000 Capabilities: [c8] Power Management version 2 Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [e0] Express Endpoint IRQ 0 Martin, do you see similar problems using either port, I ask because this system may be similar to one that Yahoo has and there was only a problem with one port and not the other, can you check this out please? Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI HBAs
Anyone know if there is a working driver for either the QLogic QLA4050C or Adaptec 7211C iSCSI HBAs? I know there is a software based initiator in the works, but having a driver for the iSCSI HBA's would provide a great alternative to running diskless or FC SAN. -- Robert Blayzor, BOFH INOC, LLC rblayzor\@(inoc.net|gmail.com) PGP: 0x66F90BFC @ http://pgp.mit.edu Key fingerprint = 6296 F715 038B 44C1 2720 292A 8580 500E 66F9 0BFC Press Ctrl-Alt-Del now for IQ test. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DNS query performance
Although it sounds silly, could you try recompiling 6.1 and 7.0 with a non-SMP kernel and see how they perform? That would at least tell us if it's a general performance problem in 6.x and 7.x, or if SMP is somehow hurting performance in this case. Mike Silby Silbersack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Several issues on Dell 1950/2950 servers (6-STABLE and 7-CURRENT)
On 9/15/06, Conrad Burger [EMAIL PROTECTED] wrote: Hi Has anyone been able to solve the problem with the bce driver on 6.1-stable? I am running 6.1-stable(200609013)AMD64 on a Dell 1950 with a SMP kernel. The system boots up fine. When I copy data to an nfs mount the bce network interface times out and then resets. It never recovers from this state. From /var/log/messages--- Sep 13 05:01:13 gold kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting! Sep 13 05:01:13 gold kernel: bce0: link state changed to DOWN Sep 13 05:01:16 gold kernel: bce0: link state changed to UP Sep 13 05:02:41 gold kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting! Sep 13 05:02:41 gold kernel: bce0: link state changed to DOWN Sep 13 05:02:44 gold kernel: bce0: link state changed to UP Any help would be appreciated. Regards Conrad I was almost sure this problem had been solved by the 6-STABLE version of sys/dev/bce/, a month ago, or so. I can't back it up, however, since I'm currently using 7-CURRENT (i386) on my PE 1950, and this behaviour is not present in this FreeBSD version. By the way, is your server equipped with a LSI SAS 5/i controller, or Dell PERC 5/i? -- Alex Salazar BSD México www.bsd.org.mx ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI HBAs
There was some interest in QLogic's part a couple of years ago to get 4000 support and they contacted me, but I was pretty much uninterested in it as a project. Go poke them again and see if they want to try. Why do you think an iSCSI HBA would be of any benefit to anything other than the target mode side as a server? On 9/15/06, Robert Blayzor [EMAIL PROTECTED] wrote: Anyone know if there is a working driver for either the QLogic QLA4050C or Adaptec 7211C iSCSI HBAs? I know there is a software based initiator in the works, but having a driver for the iSCSI HBA's would provide a great alternative to running diskless or FC SAN. -- Robert Blayzor, BOFH INOC, LLC rblayzor\@(inoc.net|gmail.com) PGP: 0x66F90BFC @ http://pgp.mit.edu Key fingerprint = 6296 F715 038B 44C1 2720 292A 8580 500E 66F9 0BFC Press Ctrl-Alt-Del now for IQ test. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
