RE: What to do when panic?
I've never debugged FreeBSD, but now I've decided to help the testing process of FreeBSD 6. I installed it, and then I had a panic. I got a debugger prompt, but I don't know what to do with that. I don't know the debugger commands. Please let me know what should I do when I have an another panic. What should I type and what kind of information should I send as a PR. You should also have a look at http://www.lemis.com/grog/Papers/Debug-tutorial/tutorial.pdf. That's Greg Lehey's script of his excellent tutorial on kernel debugging. Norbert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Machine Replication
For what its worth I use Norton Ghost to regularly set up a classroom of machines with FreeBSD 5.3, mostly because other teachers put Windoze stuff on the same boxes so the Ghost setup makes sense. Ghost doesn't understand UFS but doesn't need to. It just takes a block by block copy of the whole partition. To keep the images a reasonable size I do a dd if=/dev/zero bs=1m of=/junk; rm /junk (repeat for every file system) before imaging and tell ghost to do high compression. Compressing lots of zeros is really efficient so the images come out a reasonable size. Using multicasting I can dump the image in parallel onto 15 machines and have the system installed in under 10 minutes. IP configuration is done with DHCP so thats all straightforward. I use a small dhcp client hook script to change the system name based on IP so I even get unique system names The fact that the hardware on all of the target machines is the same is obviously a huge benefit because I can use a single X configuration, but FreeBSD travels to new hardware a lot better than any of the other O/Ss do. The only real issue is that I have some variety of hard disk types but providing the original partition isn't bigger than my smallest target drive, Ghost looks after everything properly. I haven't found a decent freeware alternative that I could get the same results from but hope to some day. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eli K. Breen Sent: Friday, 22 July 2005 5:21 AM To: freebsd-stable@freebsd.org Subject: Machine Replication All, Does anyone have a good handle on how to replicate (read: image) a freebsd machine from one machine to an ostensibly similar machine? So far I've used countless variations and combinations of the following: dd (Slow, not usefull if the hardware isn't identical?) tar (Doesn't replicate MBR) rsync (No MBR support) Norton Ghost(Doesn't support UFS/UFS2?) G4U (little experience with this) Now whether my details are a bit off, that's fine, I don't want this to be diluted in to discussion of minute frivolous details (as these things are wont to do), but what I _am_ looking for is a tried, tested and true method of FreeBSD machine replication, specifically for the 5.3+ releases. Many thanks, -E- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD IO Performance (was Re: Quality of FreeBSD)
I happened to have received a 'new' machine, and wanted to see what its IO system was capable of. So took the opportunity to run 4.10 and 5.4 against each other a few times. (fresh re-installs each time). Its documented at: http://homepages.paradise.net.nz/markir/freebsd/ I wanted to play with Docbook as well :-), so excuse the book format (might be a few typos too). But to cut to the chase, the results were overall very similar - 4.10 probably a little (4-8%) faster (allowing for run variation). So really 5.4 is reasonably fast. The actual figures weren't too bad either - 70-80Mb/s read and writes on a 2 disk ATA array. The most interesting thing discovered, was 5.4's out of the box sequential *read* performance was considerably less then 4.10, but could be brought up to almost the same by setting. vfs.read_max=16 Hope this provides some interest, again - gotta qualify, this is all one man's experiment on his hardware... Cheers Mark P.s : of course, it would be nice if 5.x (or perhaps more importantly 6.x) was *faster* than 4.10 Michael Schuh wrote: Hi, Now my question to you : is the performance of ata-related disk-access under UFS-Filesystem not important for other application, so that the performance can be a half of them that RELENG_4 does? In fact under RELENG_4 i can write a GIG FIle double as fast as under RELENG_5 ! and i would not hear any thing about serial performance or that this is not really like the real world, if i syimulate that with: /usr/bin/time dd if=/dev/zero of=/zerofile bs=1024 count=1024k; this is reality poor! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6 scroll wheel
Hej jonguk, Jonguk Kim wrote: Marian Hettwer wrote: from /etc/X11/xorg.conf Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse I think 'Option Buttons 5' can help you. nope, didn't do the trick. But thanks for the suggestion anyway :) Strange thing though, same config worked under RELENG_5 without problems. best regards, Marian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Quality of FreeBSD
On Thu, 2005-Jul-21 17:46:13 +0200, Martin wrote: One more thing about cheap hardware: if you know that a piece of hardware is potentially buggy (I mean real BUGS and not missing support), please publish your opinion, because I will buy hardware FOR FREEBSD, so I avoid major problems. How about test suites for ACPI quality, e.g.? Would it be possible? In general, I'd say what you want isn't achievable. Firstly, there's the risk of legal action from a vendor who believes they have been maligned and the reliability (or lack thereof) of the supplied opinions. More critically, vendors often make (significant to FreeBSD) changes to products without any obvious external differences. For example, wireless cards that are externally identical but have different chipsets when you open the packaging. And there's no way to ensure that the BIOS and ACPI in the motherboard you bought last week bears any resemblance to the BIOS and ACPI in the supposedly identical motherboard that I buy this week. As far as the vendor is concerned, as long as it (sort of) works on Windoze when you use the vendor-supplied driver then the vendor has fulfilled their fit-for-use responsibility. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mail System Error - Returned Mail
To send mail to me, you need to add [laundry] to the end of the subject line (eg: Subject: Random message [laundry]). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Machine Replication
At 2005-07-21 19:20:34+, Eli K. Breen writes: All, Does anyone have a good handle on how to replicate (read: image) a freebsd machine from one machine to an ostensibly similar machine? So far I've used countless variations and combinations of the following: dd(Slow, not usefull if the hardware isn't identical?) I have used dd | gzip -9 on many occasions. I don't find it especially slow (it will run at full disk bandwidth, typically 50 MB/sec on current ATA desktop disks, i.e. 3G/minute), and if you want an actual bit-for-bit identical replication then it's the only way to go. It's also very handy for keeping multi-boot slice images around (e.g. images of Windows partitions in various states, for testing purposes). The compressed images often end up nice and small. The disadvantage you may have is that your slice table and/or partition table will be wrong if your target machine has a larger disk. This is pretty easy to fix after the fact with a script using disklabel and/or fdisk. You will get better compression if you dd /dev/zero to your source machine before the initial installation, so that empty sectors are all zeroes. One day I will write a program which zeroes empty blocks of an unmounted filesystem tar (Doesn't replicate MBR) rsync (No MBR support) Replicating the MBR is exceptionally easy with dd: it's the first sector of the disk. Note that this first sector also includes the slice table. You could easily use dd in combination with tar and rsync. Norton Ghost (Doesn't support UFS/UFS2?) G4U (little experience with this) I notice that 'dump' is not in your list. Why is that? Nick Barnes Ravenbrook Limited ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Machine Replication
Danny Howard([EMAIL PROTECTED]) on 2005.07.21 15:10:54 +: machine-specific customization. Then PUBLISH your work before you get laid off. (That is how my last efforts were concluded.) Oh, yeah :-) http://www.mathematik.uni-marburg.de/sys/os/freebsd/ the page is in german, sorry... Benno -- Sebastian Benoit [EMAIL PROTECTED] My mail is GnuPG signed -- Unsigned ones are bogus -- http://www.gnupg.org/ GnuPG 0xD777DBA7 2003-09-10 D02B D0E0 3790 1AA1 DA3A B508 BF48 87BF D777 DBA7 The man who does not read good books has no advantage over the man who can't read them. -- Mark Twain pgp6KISPmW6S4.pgp Description: PGP signature
Re: Machine Replication
Just as a point of note, I'm not trying to roll out squeeky-clean new machines. Let's say I've got ten-fifteen sets of clusters, I need to be able to just rip a copy and blast it to another machine. Thanks for all the responses so far. you should invest some time to set up a diskless/pxe environment, then booting diskless is zero pain, and you can then copy disks without stepping on your toes (or foot shooting). my .5$ danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_DMA, WRITE_DMA errors
Steve wrote: If anyone has that link handy, please post. (for the patch) http://people.freebsd.org/~sos/ATA/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Resize UFS2
Hi List, Is possible resize UFS2? For example. I have 5 disks with RAID5, and reconstruct to 6 disks with RAID5, after that FreeBSD mount RAID perfectly, but with the same space before reconstruct RAID5. Exists one method to FreeBSD recognize more space? Hardware is: Dell PV220S + PERC4/DC (MegaRAID SCSI 320-2X) Thanks for any help -- Marcus Grando Grupos Internet S/A marcus(at)corp.grupos.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
make -j as a stress test (was: Re: Quality of FreeBSD)
Karl Denninger wrote: As I pointed out in my PR, make -j4 buildworld is more than sufficient to demonstrate the problem. ( ... ) I'll pull over 6.0-BETA1, rebuild the array (that is the time-consuming part of this test - takes 6-8 hours for the rebuild to run) and see if it fails during a buildworld. Maybe I'm wrong, but in my tests I had the impression that RELENG_6 includes the phk's update to make which corrects the -j behaviour. In 4.x and 5.x, every submake will spawn up to n tasks (n being the number provided with -j), and a buildworld -j4 in UP hardware easily produces a 2 digits system load. That's not more the case with 6.x (if I'm not wrong), in my test buildworld -j4 puts the load right near 4. So I hope you have other ways to test the new ATA, as make buildworld might not more be the monster it used to be. Angelo Turetta ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ATA and SATA problems (timeouts/resetting)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey everyone, I hope this goes through. For some reason I get bounces saying it can't reverse my IP, though I see no problems. I'm having major issues getting FreeBSD to install on a server. It's been a couple weeks now and nothing I've tried has helped. The server in question used to be running 4-STABLE until I upgraded it to 5-STABLE, which is when I started getting ATAPI errors: ata1-master FAILURE - ATAPI_IDENTIFY timed out The only ATA/IDE device plugged in is a CD-ROM, which was in secondary master position when this error happened. I've moved it around and nothing helps, it just changes the source of the problem (ata0-master, etc.). The system also has a 3ware SATA RAID PCI card in it, twa0, which it is booting from. Both the system BIOS and 3ware firmware is fresh. After three of the above errors it gives up I guess and then I get these: twa0: Request timed out! twa0: Resetting controller twa0: INFO: 0x04 0x005e Cache synchronized after power fail twa0: INFO: 0x04 0x0001 Controller reset occurred twa0: Controller reset done! I get the same thing with the latest 6 ISO (beta 1?). I have an almost identical system that is working just fine with 5-STABLE. The only difference is that machine has a LSI MegaRAID SCSI card also. I had these problems initially with that machine, but they just disappeared and it's running/rebooting fine, which worries me a bit. I think I booted into safe mode and cvsuped, custom kernel, and it started working, but I tried that with the new machine (same kernel config file) and it didn't have the same effect. I've scoured through the BIOSes and they're set up identically. It isn't sporadic either, I get the errors every single time, just after the timecounters tick at 1msec line (or whatever it is, I forget). Anyway I found some into online about mkIII patches and applied those and now I just get different errors. I don't remember specifically what they were, I can reinstall again and get them, but it was similar, timeout setting transferrate (or tranfer mode), then it said danger will robinson and started mixing in the above twa0 errors. Booting normally doesn't work at all, neither does single-user mode. The only way I can get in (to use and/or initially install) is using safe mode. I added an option to the menu Safer Mode to try and find out what difference was causing it but tried with/without the ATA/DMA, APIC, and ACPI lines individually and it didn't change anything. I've tried GENERIC and SMP (they are DP machines) and various kernel changes, stripping it bare, disabling DMS and ACPI in /boot/loader.conf...nothing helped. I turned off DMA in the BIOS, changed the transfer speed (PIO, standard, etc.) and just about every other thing I could think of. I just successfully installed 4.11 and it boots fine, no errors whatsoever. I was wondering if it's a hardware problem, but everything seems to run fine on the other 5.x machine (after the problems went away :/) and this 4.x one, so I'm not sure. Anyone have any ideas what I can do to troubleshoot or (hopefully) fix this? I'd much rather run 5 on it than 4, but if all else fails I guess I'm stuck with what works. Thanks, Josh -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC4QBeV/+PyAj2L+IRAtmgAJ4s68SSJQjQtxQTzL+/gi2FN4Qm1gCeM0oN 2LBqpERB6cOpZCbWMG2+crQ= =wTZf -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Quality of FreeBSD
Just to clarify the ATA code that is in FreeBSD 5.x is ATA-ng, the ATA code that is in FreeBSD 6.x+ is the ATA mkIII code. ATA-ng Preview1 http://lists.freebsd.org/mailman/htdig/freebsd-current/2003-August/008351.html ATA-ng Preview2 http://lists.freebsd.org/mailman/htdig/freebsd-current/2003-August/008736.html If you want to ensure that the ATA mkIII code works for your systems, you need to apply the patches that Soren had provided to your FreeBSD 5.x system. If you are still having problems with it, then let Soren know so he can fix the problems. You can get the ATA mkIII patches from here: http://people.freebsd.org/~sos/ATA/ Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OS suddenly VERY busy
середа 20 липень 2005 01:34, John-Mark Gurney Ви написали: This is a single-CPU Opteron running: FreeBSD 5.4-STABLE #0: Fri Jun 10 09:11:30 EDT 2005 amd64 The box has 2Gb of RAM, but NO SWAP. run ps lax a few times, and notice which process is fork bombing your box by seeing which process has the most changing children... If found the culprit, and it was not fork bombing. It was vlc (multimedia/vlc-devel), that was not supposed to do anything. On the list of interrupts I posted originally, observe the 40 to 50 irqs/sec on pcm. Once I told vlc to exit, the system returned back to normal... Does not seem right :-( -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
dhclient: send_packet: No buffer space available
What could cause dhclient sometimes to fail renew the lease? I updated world and moved to pf from ipfw same time so i don't know which to blame. This happens from twice a day to every few days. Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available Jul 21 03:45:02 myserver dhclient: New IP Address (xl0): x.x.x.x Jul 21 03:45:02 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 21 03:45:02 myserver dhclient: New Broadcast Address (xl0): x.x.x.x Jul 21 03:45:02 myserver dhclient: New Routers: x.x.x.x Pf.conf dmesg: http://www.saunalahti.fi/~pkosunen/pf.conf http://www.saunalahti.fi/~pkosunen/dmesg ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Status Report Second Quarter 2005
March-June 2005 Status Report Introduction The second quarter of 2005 has again been very exciting. The BSDCan and MeetBSD conferences were both very interesting and and the sources of very good times. I highly recommend attending them again next year. The Google Summer of Code project has also generated quite a bit of excitement. FreeBSD has been granted 18 funded mentorship spots, the fourth most of all of participating organizations. Projects being worked on range from UFS Journalling to porting the new BSDInstaller to redesigning the venerable www.FreeBSD.org website. We are quite pleased to be working with so many talented students, and eagerly await the results of their work. More information and status can be found at the Wiki site at http://wikitest.freebsd.org/moin.cgi/SummerOfCode2005. The FreeBSD 6.0 release cycle is also starting up. The purpose of quickly jumping from 5.x to 6.0 is to reduce the amount of transition pain that most users and developers felt when switching from 4-STABLE to 5.x. 6.0 will feature improved performance and stability over 5.x, experimental PowerPC support, and many new WiFi/802.11 features. The 5.x series will continue for at least one more release this fall, and will then be supported by the security team for at least 2 years after that. We encourage everyone to give the 6.0-BETA snapshots a try and help us make it ready for production. We hope to release FreeBSD 6.0 by the end of August. Thanks again to everyone who submitted reports, and thanks to Max Laier for running the show and putting the reports together. Enjoy reading! _ Google summer of code * FreeBSD Summer of Code * FreeBSD website improvements * FreeSBIE toolkit integration * gjournal * gvinum 'move', 'rename' * Improve libalias * Integrate the BSD Installer into FreeBSD * launchd(8) for FreeBSD * Network Interface API Cleanup * Nsswitch / Caching daemon * SEBSD * UFSJ -- Journaling for UFS Projects * Fundraising - TCP IP Routing Optimization * GEOM Gate rewrite * TODO list for volunteers * VFS SMP Documentation * The FreeBSD Dutch Documentation Project Kernel * Autotuning of the page queue coloring algorithm * CPU Cache Prefetching * libmemstat(3), UMA(9) and malloc(9) statistics * Low-overhead performance monitoring for FreeBSD * Removable interface improvements * SMP Network Stack * Transparent support for superpages in the FreeBSD Kernel * TrustedBSD Audit Network infrastructure * Dingo * if_bridge * IPv6 Support for IPFW * Move ARP out of routing table * TCP Reassembly Rewrite and Optimization * TTCPv2: Transactional TCP version 2 * Wireless Networking Support Userland programs * OpenBSD dhclient import. * Removing of old basesystem files and directories Architectures * PowerPC Port Ports * FreshPorts * Porting v9 of Intels C/C++ Compiler * Update of the Linux userland infrastructure Vendor / 3rd Party Software * OpenBSD packet filter - pf Miscellaneous * BSDCan * EuroBSDCon 2005 - Basel * FreeBSD Security Officer and Security Team * TrustedBSD SEBSD _ Autotuning of the page queue coloring algorithm URL: http://www.Leidinger.net/FreeBSD/current-patches/pq.diff Contact: Alexander Leidinger [EMAIL PROTECTED] The VM subsystem has code to reduce the amount of cache collisions of VM pages. Currently this code needs to be tuned with a kernel option. I have a patch which changes this to auto-tuning at boot time. The auto-tuning is MI, the cache size detection is MD. Cache size detection is currently available for x86/amd64 (on other systems it uses default values). Open tasks: 1. Add cache-detection code for other arches too (Marius told me how to do this for sparc64). 2. Analyze why the cache detection on Athlons doesn't work (no problems on a P4, but it uses a different code-path). _ BSDCan URL: http://www.bsdcan.org/2005/ Contact: Dan Langille [EMAIL PROTECTED] The second annual BSDCan conference was well presented, well attended, and everyone went away with good stories to tell. If you know anything that attended, get them to tell you what they did, who they met with, and talks they listened to. We had 197 people from 15 different countries. That's a strong turnout by any definition. We'll be adding more people to the program committee for BSDCan 2006. This job involves prodding and poking people from your respective projects. You get them to
Re: make -j as a stress test (was: Re: Quality of FreeBSD) [WARNING - 6.0-BETA1 still hosed!]
It is definitely NOT fixed in 6.0-BETA1 Within SECONDS of starting a buildworld after the provider rebuild completed, I got this... GEOM_MIRROR: Device boot: provider ad4s1 detected. GEOM_MIRROR: Device boot: rebuilding provider ad4s1. GEOM_MIRROR: Device boot: provider ad6s1 detected. GEOM_MIRROR: Device boot: rebuilding provider ad6s1. GEOM_MIRROR: Device boot: rebuilding provider ad4s1 finished. GEOM_MIRROR: Device boot: provider ad4s1 activated. GEOM_MIRROR: Device boot: rebuilding provider ad6s1 finished. GEOM_MIRROR: Device boot: provider ad6s1 activated. subdisk4: detached ad4: detached unknown: FAILURE - SETFEATURES SET TRANSFER MODE timed out unknown: timeout waiting to issue command unknown: error issueing SETFEATURES SET TRANSFER MODE command GEOM_MIRROR: Device boot: provider ad4s1 disconnected. GEOM_MIRROR: Request failed (error=6). ad4s1[READ(offset=35096543232, length=10240)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35463411712, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35467393024, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35501357056, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35501551616, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35501553664, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35502305280, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35502583808, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35502764032, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35648684032, length=16384)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=3570560, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35840983040, length=16384)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35840999424, length=16384)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35848910848, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35854632960, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=35866456064, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=36226842624, length=16384)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=36226859008, length=16384)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=36233115648, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=36234352640, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=36234868736, length=2048)] GEOM_MIRROR: Request failed (error=6). ad4s1[WRITE(offset=36274173952, length=2048)] unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! unknown: req=0xc1e2e320 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! This is significantly WORSE than 5.3-RELEASE in that it appears not only to detach the disk, but then to go on to whine mightily about other things (I have no idea whether I've taken a data corruption hit at this point or
Re: Quality of FreeBSD
Am Donnerstag, 21. Juli 2005 22:06 CEST schrieb Matthias Buelow: [EMAIL PROTECTED] writes: My main problem, and to others after seeing the question from times to times, is to know which is a good (not necessarly the best) hardware to run FreeBSD on? When I buy a new motherboard, which chipset to choose/avoid, which controllers ? Maybe some website like it is being done for notebooks (with Linux/FreeBSD support) would be in order. I'm thinking about something like http://www.linux-laptop.net/, only for FreeBSD and all kinds of machines, not just notebooks. (Or, if some collaboration would be ok, for *BSD in general, with people posting experience from NetBSD, OpenBSD, Dragonfly, even Darwin aswell. That way one could also compare support for hardware and see what problems the individual systems have.) Make it a Wiki, or something similar, where people can freely post experiences they have with their hardware. That could be whole machines (Dell model xxx desktop, IBM yyy laptop, HP zzz server) aswell as components (Asus blah motherboard, 3Com wlan card model foobar, etc.) and make the thing searchable, and perhaps allow one to post comments on entries (easy with a Wiki). That way people can quickly search review hardware, awell as test suggested workarounds by the posters, without having to google for obscured mailing list entries, or problem reports. Well, there are numerous great FreeBSD sites out there which assist in such question, but I also like the idea of a purely hardware database site. If nobody want's to extend his site I'd offer to start a new one, I have spare capacity in both, my servers (if they go online, in some days I hope) and my leased line, so I'd be glad to contribute something. If anybody with wiki-experience wants to step in, you're welcome, I'm not the big webmaster... Maybe Eric Anderson wants to contribute his bsdhardware.org domain, or we could name it hardware.freebsd.org I'll be back when I have something online. Best regards, -Harry pgpkZbIH4xWEY.pgp Description: PGP signature
Re: make -j as a stress test (was: Re: Quality of FreeBSD) [WARNING - 6.0-BETA1 still hosed!]
On Fri, Jul 22, 2005 at 02:40:09PM -0500, Karl Denninger wrote: It is definitely NOT fixed in 6.0-BETA1 Within SECONDS of starting a buildworld after the provider rebuild completed, I got this... GEOM_MIRROR: Device boot: provider ad4s1 detected. GEOM_MIRROR: Device boot: rebuilding provider ad4s1. GEOM_MIRROR: Device boot: provider ad6s1 detected. GEOM_MIRROR: Device boot: rebuilding provider ad6s1. GEOM_MIRROR: Device boot: rebuilding provider ad4s1 finished. GEOM_MIRROR: Device boot: provider ad4s1 activated. GEOM_MIRROR: Device boot: rebuilding provider ad6s1 finished. GEOM_MIRROR: Device boot: provider ad6s1 activated. subdisk4: detached ad4: detached unknown: FAILURE - SETFEATURES SET TRANSFER MODE timed out unknown: timeout waiting to issue command unknown: error issueing SETFEATURES SET TRANSFER MODE command GEOM_MIRROR: Device boot: provider ad4s1 disconnected. GEOM_MIRROR: Request failed (error=6). ad4s1[READ(offset=35096543232, length=10240)] Note carefully from this that there is NO ERROR INDICATION AS TO WHY THE DISK DETACHED! At least with the 5.x problems you'd SEE an error before it went BOOM. This time around, nope - just death. What's worse, the complaints continue even through a shutdown, making any attempt to shutdown and reboot the machine futile. After waiting over 10 minutes for a shutdown to complete I had to resort to the use of the power switch. This is NOT good, because if you get hosed by this kind of thing you have no way out of it remotely. Thus, my contention is that 6.0-BETA1 is far WORSE than 5.x is in this regard. Be careful out there -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://homecuda.com Emerald Coast: Buy / sell homes, cars, boats! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
SMP support maturity? AMD64x2 or FX-57?
SMP support in FreeBSD seems to be a perpetually favorite feature to gripe about, but every release seems to say that its getting better. I'm about to build a new server and am trying to determine if I should go with dual procs or just a single. The AMD64x2 is slightly cheaper than the FX-57 so I'm leaning that way, but it would be a rather pointless savings if SMP isn't well supported. So, is SMP in -STABLE ready for primetime? Can it really make use of two processors? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP support maturity? AMD64x2 or FX-57?
Brandon Fosdick wrote: SMP support in FreeBSD seems to be a perpetually favorite feature to gripe about, but every release seems to say that its getting better. I'm about to build a new server and am trying to determine if I should go with dual procs or just a single. The AMD64x2 is slightly cheaper than the FX-57 so I'm leaning that way, but it would be a rather pointless savings if SMP isn't well supported. So, is SMP in -STABLE ready for primetime? Can it really make use of two processors? Sigh. You know, I've been running with two processors since 4.1 or thereabouts. Sure, the BGL scheme is inefficient as far as the kernel itself is concerned, but for compute-bound user processes it worked just fine. Naturally I avoided 5.0/1/2 for my production boxen, waiting for the complete overhaul of SMP to stabilize, but when I booted 5.3, everything was fine and I haven't looked back. Personally I don't have the first clue what people have found to gripe about. It has been good, it got a _lot_ better in 5.x, and it's continuing to improve. Ports to new processor families are an entirely different kettle of fish and have their own sets of problems, virtually all of which have to do with the new architecture and not with the general SMP support itself. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADS-UP: ABI compatibility of getaddrinfo(3) was lost.
Hi, I've nuked the padding for ai_addrlen member of struct addrinfo on RELENG_6. It broke ABI compatibility of getaddrinfo(3) on 64 bit architecture. You have to recompile userland programs that use getaddrinfo(3) on 64 bit architecture. Sincerely, ---BeginMessage--- ume 2005-07-22 20:17:30 UTC FreeBSD src repository Modified files:(Branch: RELENG_6) include netdb.h lib/libc/net getaddrinfo.c Log: MFC: Remove padding for ABI compatibility of ai_addrlen member from struct addrinfo. This change break ABI compatibility on 64 bit arch. include/netdb.h:1.39 lib/libc/net/getaddrinfo.c: 1.70 Approved by:re (kensmith) Revision ChangesPath 1.38.2.1 +0 -19 src/include/netdb.h 1.69.2.1 +0 -3 src/lib/libc/net/getaddrinfo.c ---End Message--- -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED],jp.}FreeBSD.org http://www.imasy.org/~ume/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP support maturity? AMD64x2 or FX-57?
On Friday 22 July 2005 04:06 pm, Brandon Fosdick wrote: SMP support in FreeBSD seems to be a perpetually favorite feature to gripe about, but every release seems to say that its getting better. I'm about to build a new server and am trying to determine if I should go with dual procs or just a single. The AMD64x2 is slightly cheaper than the FX-57 so I'm leaning that way, but it would be a rather pointless savings if SMP isn't well supported. So, is SMP in -STABLE ready for primetime? Can it really make use of two processors? ___ I'm running RELENG_6 on a dual processor Opteron in 64 bit mode and it's working fine as long as I'm using the 4BSD scheduler. -- Anish Mistry pgpQ6acVURTkC.pgp Description: PGP signature
ATA issue on 5.4
Greetings all. I would appreciate any incite that you can give me with this problem. I am sure that you have visited this issue in the past, but I have been unable to find a resolution. The symptoms are ad1: TIMEOUT - READ_DMA retrying (2 retries left) LBA=10027551 ad0: WARNING - removed from configuration ad1: WARNING - removed from configuration ata0-slave: FAILURE - READ_DMA timed out After these messages the machine is unusable until it is power cycled. The machine can is described by dmesg below, but here is some history. The machine has been running FreeBSD 4.8 - 4.10 for the last several years with two disks on the ATA0 controller. (ad0= Maxtor 51024H2 10GB, ad1=WD400BB 40GB) I finally decided it was time to move to 5.x release. I also decided it was time to upgrade the disks I used a Maxtor 20GB for ad0 and WD2500JB for ad1. The Maxtor disk has been used before but the WD is brand new. The machine is a 733 MHz Compaq Deskpro EN (Intel 815e chipset with an ICH 2 ata controller). I have turned off all power management functions in the CMOS. I am currently running the GENERIC Kernel as taken from the 5.4 ISO install. I upgraded to p4 but it did not help my situation so I backed off. I have searched high and low and have found a suggestion of adding a command to the /boot/loader.conf to no avail. I do not believe that the issue is the ata controller, however, it could have to do with compatibility with the 250GB WD drive with FreeBSD. I have not used the WD before but I have tested it with Western Digital's Data Lifeguard Diagnostics as it was installed in the box for both communication and media errors with no errors found. The issue seems to occur when the system has been idle for some time (an hour or so). Below is my dmesg output. I do not want to reload 4.10 to have a working system. Thanks for the help. Ray Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (730.90-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 535822336 (511 MB) avail memory = 514658304 (490 MB) MPTable: COMPAQ Deskpro ioapic0: Changing APIC ID to 8 ioapic0: Assuming intbase of 0 ioapic0 Version 2.0 irqs 0-23 on motherboard npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: MPTable Host-PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 agp0: Intel 82815 (i815 GMCH) SVGA controller mem 0x4050-0x4057,0x4400-0x47ff irq 16 at device 2.0 on pci0 pcib1: MPTable PCI-PCI bridge at device 30.0 on pci0 pci2: PCI bus on pcib1 fxp0: Intel 82801BA/CAM (ICH2/3) Pro/100 Ethernet port 0x1000-0x103f mem 0x4010-0x40100fff irq 20 at device 8.0 on pci2 miibus0: MII bus on fxp0 inphy0: i82562EM 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:50:8b:d8:70:af fxp1: Intel 82559 Pro/100 Ethernet port 0x1040-0x107f mem 0x4000-0x400f,0x4020-0x40200fff irq 18 at device 9.0 on pci2 miibus1: MII bus on fxp1 inphy1: i82555 10/100 media interface on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:d0:b7:0f:a7:f4 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0x2460-0x246f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0x2440-0x245f irq 23 at device 31.4 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcm0: Intel ICH2 (82801BA) port 0x2400-0x243f,0x2000-0x20ff irq 17 at device 31.5 on pci0 pcm0: Analog Devices AD1885 AC97 Codec orm0: ISA Option ROMs at iomem 0xe-0xe,0xcb000-0xd87ff,0xca000-0xcafff,0xc-0xc9fff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: Enhanced floppy controller at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/13 bytes threshold ppbus0:
Re: make -j as a stress test (was: Re: Quality of FreeBSD) [WARNING - 6.0-BETA1 still hosed!]
On Fri, Jul 22, 2005 at 02:53:57PM -0500, Karl Denninger wrote: [...] Note carefully from this that there is NO ERROR INDICATION AS TO WHY THE DISK DETACHED! At least with the 5.x problems you'd SEE an error before it went BOOM. This time around, nope - just death. What's worse, the complaints continue even through a shutdown ... While I agree with Karl that introducing instability is a very bad thing, I guess we now have an answer to Karl's vexation yesterday: [ http://lists.freebsd.org/pipermail/freebsd-stable/2005-July/017210.html ] What I don't understand Robert is why Soren's code is too sensitive to commit, but the explosive reduction in stability that the changes made between 4.x and 5.3 caused weren't enough to back THAT out until it could be fixed. The answer would seem to be that when someone actually does test the untested code, it is even worse than the code we are already upset with. :) Love, -danny -- http://dannyman.toldme.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP support maturity? AMD64x2 or FX-57?
On Fri, Jul 22, 2005 at 01:27:30PM -0700 I heard the voice of Frank Mayhar, and lo! it spake thus: Sigh. You know, I've been running with two processors since 4.1 or thereabouts. Sure, the BGL scheme is inefficient as far as the kernel itself is concerned, but for compute-bound user processes it worked just fine. Naturally I avoided 5.0/1/2 for my production boxen, waiting for the complete overhaul of SMP to stabilize, but when I booted 5.3, everything was fine and I haven't looked back. This system (this one, right here, that I'm typing on) is dual processor, and I installed it fresh with 4-CURRENT just after RELENG_3 was branched. Except for an excursion on RELENG_5, it's always run -CURRENT. Sometimes I'd go a year without updating, sometimes a week. It's running -CURRENT from a couple weeks ago now. Sometimes it's a bit twitchy, but I think running X has a whole lot to do with that, since MP systems under heavier loads without X would do just peachy with the exact same build that was flaky here. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make -j as a stress test (was: Re: Quality of FreeBSD) [WARNING - 6.0-BETA1 still hosed!]
On Fri, Jul 22, 2005 at 07:53:00PM -0700, Danny Howard wrote: On Fri, Jul 22, 2005 at 02:53:57PM -0500, Karl Denninger wrote: [...] Note carefully from this that there is NO ERROR INDICATION AS TO WHY THE DISK DETACHED! At least with the 5.x problems you'd SEE an error before it went BOOM. This time around, nope - just death. What's worse, the complaints continue even through a shutdown ... While I agree with Karl that introducing instability is a very bad thing, I guess we now have an answer to Karl's vexation yesterday: [ http://lists.freebsd.org/pipermail/freebsd-stable/2005-July/017210.html ] What I don't understand Robert is why Soren's code is too sensitive to commit, but the explosive reduction in stability that the changes made between 4.x and 5.3 caused weren't enough to back THAT out until it could be fixed. The answer would seem to be that when someone actually does test the untested code, it is even worse than the code we are already upset with. :) Love, -danny Point taken. Can we get a COMMITMENT from the development team that 6.x will NOT go out the door until this problem is identified and FIXED (e.g. the PR I submitted against this early in the year is closed)? The problem is trivially easy to reproduce, as I've pointed out. My hardware is hardly anything special - its a Dell Poweredge 400SC, a rather pedestrian 2.4Ghz P4/HT machine with 512MB of RAM and nothing special in terms of boards in it. Indeed, on the sandbox machine the ONLY cards in the machine are the Adaptec SATA card and a video board! The ICH SATA onboard adapter works fine. No problems, even if you beat the snot out of the disks. Ditto for the onboard PATA channels. ANY PCI SII-chipset SATA card (nothing fancy here, no onboard RAID, just a disk adapter) that I've tried thus far - Bustek or Adaptec - causes trouble in an absolutely reproducable fashion when put under heavy load. If both channels are in use the trouble is immediate and dramatic, although you CAN provoke errors even with only one of the two channels in operation if you can get the I/O load up high enough. Gmirror is great for provoking this as it queues traffic to both channels in a nicely balanced and heavily-utilized fashion, although I'm willing to bet that Gmirror itself is not involved as the actual cause of the problem, since I had trouble once DURING install (before I had put a gmirror'ed config on the disks.) Note that a MIX of read and writes appears to be required - a REBUILD of the disks by Gmirror (which is all writes to those two disks) succeeds. As soon as you have all three subdisks in the array, however, a make buildworld produces fireworks. If necessary (or useful) I can give one or more developers a way to log into the sandbox machine here via ssh. I do not have a way to get a serial console on the box, however, so if its blown up in an unrecoverable fashion remotely someone would have to call or IM me to push the big red button. If that's NOT necessary (or desired), then I want to move those two disks back to the production machine as they are how my offsite/offline backups are done - I've no problem with leaving them on the sandbox IF the problem is being actively worked though. -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://homecuda.com Emerald Coast: Buy / sell homes, cars, boats! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP support maturity? AMD64x2 or FX-57?
At 04:27 PM 7/22/2005, Frank Mayhar wrote: Brandon Fosdick wrote: SMP support in FreeBSD seems to be a perpetually favorite feature to gripe about, but every release seems to say that its getting better. I'm about to build a new server and am trying to determine if I should go with dual procs or just a single. The AMD64x2 is slightly cheaper than the FX-57 so I'm leaning that way, but it would be a rather pointless savings if SMP isn't well supported. So, is SMP in -STABLE ready for primetime? Can it really make use of two processors? Sigh. You know, I've been running with two processors since 4.1 or thereabouts. Sure, the BGL scheme is inefficient as far as the kernel itself is concerned, but for compute-bound user processes it worked just fine. Naturally I avoided 5.0/1/2 for my production boxen, waiting for the complete overhaul of SMP to stabilize, but when I booted 5.3, everything was fine and I haven't looked back. Personally I don't have the first clue what people have found to gripe about. It has been good, it got a _lot_ better in 5.x, and it's continuing to improve. Ports to new processor families are an entirely different kettle of fish and have their own sets of problems, virtually all of which have to do with the new architecture and not with the general SMP support itself. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ I agree. I'm not a FreeBSD expert by any means, but I do enjoy using it very much. I've learned a lot about it over the past year or so that I've been running it. I have both a 4.11 and 5.4 box that have dual processors and are running like champs. The 5.4 box is doing a lot more work actually, and it never has a problem. It's been all good for me, but then again, I probably don't delve quite as deeply into some of the complex heavy loaded things other do. Vinny Abello Network Engineer Server Management [EMAIL PROTECTED] (973)300-9211 x 125 (973)940-6125 (Direct) PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A Tellurian Networks - The Ultimate Internet Connection http://www.tellurian.com (888)TELLURIAN Courage is resistance to fear, mastery of fear - not absence of fear -- Mark Twain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
