Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server
On Tue, Dec 20, 2011 at 03:29:25PM -0800, Jeremy Chadwick wrote: > > This also interested me: > > * Linux system crashed > http://leaf.dragonflybsd.org/mailarchive/kernel/2011-11/msg8.html > > * OpenIndiana system crashed same way as Linux system > http://leaf.dragonflybsd.org/mailarchive/kernel/2011-11/msg00017.html > > I cannot help but wonder if the Linux and OpenIndiana installations were > more stressful on the hardware -- getting more out of the system, maybe > resulting in increased power/load, which in turn resulted in the systems > locking up (shoddy PSU, unstable mainboard, MCH problems, etc.). > > My point is that Francois states these things in such a way to imply > that "DragonflyBSD was more stable", Same thing can be said for FreeBSD, only Linux and OpenIndiana crashed reliably if I remember correctly. > when in fact I happen to wonder the > opposite point -- that is to say, Linux and OpenIndiana were trying to > use the hardware more-so than DragonflyBSD, thus tickled what may be a > hardware-level problem. I actually ran the benchmarks on two different machines with the same hardware -- brand new Supermicro boxes with ECC memory and no cut corners. Since then, I've found I could stop the Linux crashes by disabling some options in the BIOS setup: - advanced ACPI settings (don't remember exactly which ones) - and a new WHEA one. WHEA means Windows Hardware Error Architecture. For all I know, it may have been the only culprit but I didn't have time to verify if the machines also ran fine with only this option disabled. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Fri, Feb 18, 2011 at 02:38:32PM -0800, Jeremy Chadwick wrote: > > > Please be aware of a performance issue affecting certain models of WD > RE4 disks. Specifics are still sketchy, but you should read the thread > "immense delayed write to file system (ZFS and UFS2), performance > issues" in full to get an idea of the problem: > > http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/thread.html#54185 > > There's confirmation of the problem here, with the statement that WD > gave at least one person a firmware image that fixed the problem: > > http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/054489.html I'm not sure if this is exactly the same issue, but I also had to flash some WD drives a few month ago. There was a bad firmware version on some 2TB RE4-GP models; disks kept getting removed from RAID volumes due to write timeouts. > Buyer beware. :-) And remember, it's not an issue with the > brand/vendor, just certain models. Disks these days are no longer just disks, but complete computers with ram, many processors, and the associated software issues... -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: LSI SAS 2008 (mfi) on SuperMicro X8SI6-F
On Wed, Feb 16, 2011 at 07:23:26PM +0300, Dmitry Morozovsky wrote: > On Wed, 16 Feb 2011, Daniel Kalchev wrote: > > DK> PS: My experiments were with the X8DTL-6F motherboard and Supermicro > chassis > DK> with E16 expander. There is no reason the HBA chip in the single processor > DK> motherboard to be different. > > My box is actually the same (846E1) Not exactly: with Supermicro, E1 means a SAS 3 Gb/s backplane and E16 is for SAS 6Gb/s -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: PXE boot FreeBSD without need of NFS server
On Thu, May 28, 2009 at 09:10:50AM +0200, Mikael Bak wrote: > Pertti, András, > Thank You for the useful links! > Kiitos and Köszönöm szépen :-) > > Gót András wrote: > > Hi, > > > > AFAIK only the kernel and initrd (in the linux case) can be booted from > > tftp, that's a PXE feature. When the kernel loaded it takes over and from > > then on the kernel will need a rootfs from somewhere. I don't think that a > > tftp rootfs is possible. > > > > Yes, I know it's not possible to have the rootfs on tftp. That is not my > goal. I only wish to host an image file containing a rootfs that will > act as a ram disk. Much like the initrd does in the Linux world. The > rootfs will only contain the things needed to start the installation > process. Have a look at ThinBSD. It a mini FreeBSD-5.x system which uses a ramdisk image as root. It can be booted from a TFTP server, without NFS. The web site is here: http://thinbsd.zefyris.com/ I use it everyday to run a X terminal. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: buildworld failure in libexec.mail.local on 6.1 Release
On Wed, May 10, 2006 at 12:58:49PM +0200, Spil Oss wrote: > l.s. > > After running cvsup to RELENG_6_1, I started `make buildworld > KERNCONF=BEASTIE61` as per the handbook's '21.4.1 The Canonical Way to > Update Your System' > > In libexec/mail.local I get the following on stderr > /usr/obj/usr/src/tmp/usr/bin/ld: warning: libldap-2.2.so.7, needed by > /usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link) > /usr/obj/usr/src/tmp/usr/bin/ld: warning: liblber-2.2.so.7, needed by > /usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link) > /usr/local/lib/libsasl.so: undefined reference to `ldap_get_dn' > /usr/local/lib/libsasl.so: undefined reference to `ldap_unbind' > /usr/local/lib/libsasl.so: undefined reference to `ldap_first_entry' > /usr/local/lib/libsasl.so: undefined reference to `ldap_simple_bind_s' > /usr/local/lib/libsasl.so: undefined reference to `ldap_set_option' > /usr/local/lib/libsasl.so: undefined reference to `ldap_memfree' > /usr/local/lib/libsasl.so: undefined reference to `ldap_init' > /usr/local/lib/libsasl.so: undefined reference to `ldap_search_ext_s' > /usr/local/lib/libsasl.so: undefined reference to `ldap_msgfree' > > >From stdout I had > ===> libexec/mail.local (all) > cc -O2 -pipe -funroll-loops -march=pentium3m > -I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I. > -I/usr/local/include/sasl1 -DSASL -c > /usr/src/libexec/mail.local/../../contrib/sendmail/mail.local/mail.local.c > cc -O2 -pipe -funroll-loops -march=pentium3m > -I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I. > -I/usr/local/include/sasl1 -DSASL -L/usr/local/lib -o mail.local > mail.local.o /usr/obj/usr/src/libexec/mail.local/../../lib/libsm/libsm.a > -lsasl > *** Error code 1 I guess you're trying to use a sendmail compiled with SMTP AUTH support. I have the same problem here. Even though libldap-2.2.so.7 and liblber-2.2.so.7 are in /usr/local/lib and cc has a -L/usr/local/lib flag, ld doesn't find them. Even putting the libraries in /usr/lib doesn't correct this error. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Instant crash with FreeBSD 6.1-RC and 4GB RAM
On Thu, Apr 13, 2006 at 03:46:03AM +0400, Alexey Karagodov wrote: > try to update BIOS ... Already done. The machine remains unusable with 4GB. I will try to use a Tyan Tomcat K8E. Hopefully this one will work as advertised... -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Instant crash with FreeBSD 6.1-RC and 4GB RAM
On Wed, Apr 12, 2006 at 03:47:02PM -0400, Kris Kennaway wrote: > On Wed, Apr 12, 2006 at 09:43:06PM +0200, Francois Tigeot wrote: > > > > I just tried booting a FreeBSD-6.1-RC1/amd64 CD in a machine with an > > Athlon-64 X2 4400+ and 4GB of memory. > > > > The mainboard is an Asus A8V-E-SE. > > > > The kernel displays its copyright and then crashes almost instantly. The > > screen is filled with the letter 'k' and the machine reboots soon after > > that. [...] > > If the memory is limited to 3GB in the BIOS, FreeBSD boots as expected. > > > > I would appreciate if someone could share some insight about this problem. > > Replace the broken 1GB memory stick? :-) Well, with the same sticks, the same CD boots correctly in an Opteron/Supermicro H8SSL-i machine Silly me, I thought it could have been a software bug, when it was in fact a hardware one... Any recommandation for a known working socket 939 mainboard with PCI-E graphics ? -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Instant crash with FreeBSD 6.1-RC and 4GB RAM
Hello, I just tried booting a FreeBSD-6.1-RC1/amd64 CD in a machine with an Athlon-64 X2 4400+ and 4GB of memory. The mainboard is an Asus A8V-E-SE. The kernel displays its copyright and then crashes almost instantly. The screen is filled with the letter 'k' and the machine reboots soon after that. Here is a copy of the verbose boot messages (transcripted by hand): SMAP type=01 base= len=0009f400 SMAP type=02 base=000f len=0001 SMAP type=02 base=fec0 len=0140 SMAP type=02 base=e000 len=1000 SMAP type=03 base=afee3000 len=d000 SMAP type=04 base=afee len=3000 SMAP type=02 base=0009f400 len=0c00 SMAP type=02 base=afef len=0001 SMAP type=01 base=0010 len=afde SMAP type=01 base=0001 len=5000 Copyright (c) 1992-2006 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 6.1-RC1 #0: Mon Apr 10 20:16:14 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC (crash here) If the memory is limited to 3GB in the BIOS, FreeBSD boots as expected. I would appreciate if someone could share some insight about this problem. TIA, -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: watchdog network card
On Mon, Mar 27, 2006 at 12:37:20PM +0200, Albert Shih wrote: > > I can't add another PCI card because all my PCI slot is in use. > > On my server I need 5 network Interface, and I've 2 bi-dual-gigabits PCI > card and one on mothercard. You still have the option to replace on of the dual ports NIC by a quad port one. http://www.intel.com/network/connectivity/products/pro1000mt_quad_server_adapter.htm -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 release date and stability
On Mon, Oct 17, 2005 at 07:56:34PM -0600, Brett Glass wrote: > At 06:38 PM 10/17/2005, Mike Tancsa wrote: > > >Two of our scanners in the cluster are SMP boxes-- dual core AMD running in > >386 mode and an Intel D830. > >Both work really well, and take quite a load against them network / cpu > >wise. Lots of threads running. > >Also have FAST_IPSEC clients and a server running RELENG_6 from around Beta > >1. > > How is AMD in AMD64 mode? One thing we're looking at doing is deploying some > single-core AMD64s. Very stable since -BETA4 on a single core machine here (workstation and X11 terminal server). It had crashes under load with previous -BETA. Uptime went to 20+ days without trouble before I upgraded it to -RC1. The hardware is a MSI board with VIA chipset. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: autologin only in one ttyv
On Thu, Sep 01, 2005 at 09:59:20PM +0200, Mathieu PREVOT wrote: > > I would like to autologin in *only one* ttyv (eg ttyv1) and then launch > X with xinit manually or with a script. > I used ":al=:" in /etc/gettytab and added or not xinit in > /etc/, but it's not very satisfying! > Hence, I would like this to occur only for ttyv1. Can someone help me? I have done a similar thing for ThinBSD. Look here: http://www.thinbsd.org/cvsweb/ThinBSD/diskimage/files/ In addition to gettytab, I had to modify /etc/ttys to use the autologin feature on only one vt. You can then launch X from the user's .profile -- Francois Tigeot, Zefyris http://www.zefyris.com/ ___ 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
On Thu, Jul 21, 2005 at 12:20:34PM -0700, Eli K. Breen wrote: > > Does anyone have a good handle on how to replicate (read: image) a > freebsd machine from one machine to an ostensibly similar machine? [...] > 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. I have found the following paper to be incredibly usefull : http://www.pix.net/software/pxeboot/archive/SANE.pdf I used some of the ideas in it to clone machines in the 5.1-5.2 era. -- Francois Tigeot, CEO, Zefyris http://www.zefyris.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: What to use to get remote display from a amd64 machine?
On Tue, Jun 07, 2005 at 10:20:03PM +0200, Torfinn Ingolfsen wrote: > On Tue, 07 Jun 2005 12:03:41 +0200 > Francois Tigeot <[EMAIL PROTECTED]> wrote: > > > Stock X is sufficient. > > Well, stock X will probably work. I have used that in the past on a > per-program basis. You know, the 'DISPLAY=host:0.0 program ...' routine. > > I'm sorry that my little question lacked enough detail to avoid all this > confusion. On the other hand, it sparked an interssting debate. :) > The enironment is LAN. > The reason that I forgot to mention stock X, is that vnc (which I'm > partial to, since that's what I have been using) is so much easier to > use: > a) it gives me a complete X desktop which is separate from the X desktop > I use when I log in locally. This means I can tailor the remote desktop > to another wm, another display size and so on. You could probably do this by customizing ~/.xinitrc or ~/.xsession. I agree it would not be the easiest thing to do, though > b) it allows me to run the display in a web browser (java required) This seems to be a good reason to use VNC. > > My users use ThinBSD based thin clients to connect to a > > FreeBSD/amd64 server. > > And on the server you run xdm or something like that? I run xdm, yes. Since I do not like the "official" way to launch it from /etc/ttys, I made a port which provides a script in /usr/local/etc/rc.d : http://www.thinbsd.org/cvsweb/ThinBSD/ports/xdm-rc/ -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: What to use to get remote display from a amd64 machine?
On Tue, Jun 07, 2005 at 12:19:19PM +0200, Marc Olzheim wrote: > On Tue, Jun 07, 2005 at 12:03:41PM +0200, Francois Tigeot wrote: > > > > Stock X is sufficient. > > That's really not a substitue for nxserver's performance... Assuming > Torfinn is working over a high latency connection. I assumed the environment was a lan. For a wan, ssh display forwarding and compression could help. > Perhaps run the nxserver compiled on i386 in compat32 mode... ? I would be very interested by the results. The only showstopper to obtain an amd64 binary seems to be the lack of -fPIC somewhere in the Makefiles. Perhaps a future version could be run natively. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: What to use to get remote display from a amd64 machine?
On Tue, Jun 07, 2005 at 12:03:01AM +0200, Torfinn Ingolfsen wrote: > > What are people using for remote X displays on amd64 machines? Stock X is sufficient. My users use ThinBSD based thin clients to connect to a FreeBSD/amd64 server. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Creating a mini install disk, for particular needs
On Wed, May 11, 2005 at 12:56:07AM +0100, Chris Phillips wrote: > > I am trying to find a suitable alternative to our crappy, solid-state, > thin client boxes (because they are so awfully unreliable & the > manufacturer has also gone down the tubes). > > We need a fairly painless way, to roll out a fresh install onto some > random i386 hardware we have lying around (there's a plentiful supply), > for any new users, who require a basic functioning GUI, with access to > graphical email client, web browser & 'rdesktop' (for the windows > applications, that they are all hooked on). You may also try to use your PCs as thin clients. Check out http://www.thinbsd.org/ , it is a small FreeBSD based system to create X11 or Windows terminals. (Don't be afraid by the release dates, the project is not dead). > What I'd love to be able to do, is to create a FreeBSD (it's my > favorite) CD, that contains all that I need for these basic systems. > Either, set up so that the install is automated, with just the minimal > of setup, or so that it's got all the packages that I want & can all be > installed straight off the CD (perhaps by choosing the "All Packages" > option). > > Is what I've described actually possible? There are informations to script the install process in sysinstall(8) I had to install FreeBSD and Linux on dozens of workstations before and found out the CD thing was not the most practicable way. I ended up doing a fairly complete install on a master machine and cloning it via PXE booting and dd (disks were identicals). Check out this paper for a similar technique: http://www.pix.net/software/pxeboot/archive/SANE.pdf -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
On Tue, Apr 19, 2005 at 04:18:17PM -0700, David G. Lawrence wrote: > >I assume you saw this in the tftpd manual page? > > BUGS > Files larger than 33488896 octets (65535 blocks) cannot be transferred > without client and server supporting blocksize negotiation (RFC1783). > > Many tftp clients will not transfer files over 1678 octets (32767 > blocks). There is a PR open with a patch to fix this: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/67550 -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Qt applications hang
On Sun, Mar 20, 2005 at 11:30:29AM +0200, Andy Fawcett wrote: > On Sunday 20 March 2005 09:26, Francois Tigeot wrote: > > On Sat, Mar 19, 2005 at 05:47:01PM -0800, David Wolfskill wrote: > > > There's a recent entry in /usr/ports/UPDATING that may be relevant. > > > > I suspected at one time the system compiler to be busted, but I recompiled > > everything with -O -pipe and the problem remains. > > > > Cc to -amd64 to see if there may be something architecture specific. > > > > [For the record, every QT application hang immediately when some menu > > options are selected. The system is 5.4-PRERELEASE/amd64] > > I have 5.4-PRE on my work amd64 box (kernel/world built a few days ago) and > I'm running KDE from ports in it without apparent problems. The strange thing is, most of the things work (I have a user running kde from an X terminal and not complaining). Trying to open a file dialog (Location/Open Location in Konqueror) will howewer result in a freezed gui. There must be something locally broken, but so far I was unable to find it. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Qt applications hang
On Sat, Mar 19, 2005 at 05:47:01PM -0800, David Wolfskill wrote: > There's a recent entry in /usr/ports/UPDATING that may be relevant. Thanks, but I fail to see what is relevant in this case. I suspected at one time the system compiler to be busted, but I recompiled everything with -O -pipe and the problem remains. Cc to -amd64 to see if there may be something architecture specific. [For the record, every QT application hang immediately when some menu options are selected. The system is 5.4-PRERELEASE/amd64] -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Qt applications hang
I'm experiencing a very strange problem: everything on my system appears to work fine, with the exception of QT-based applications. When I launch one, the GUI appears normally and the menus are working. Most of the menu items also appear to work fine. As soon as I try to open a file selection dialog (File/Open Location in konqueror), the whole GUI becomes irresponsive, but the application can still be killed. So far I have had the problem with konqueror and print/scribus The machine is running 5.4-PRERELEASE/amd64. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA RAID Support
On Fri, Feb 25, 2005 at 05:21:17PM -0800, Doug White wrote: > On Fri, 25 Feb 2005, Oliver Brandmueller wrote: > > > Under heavy load (I/O load on the disks constantly over 200 tps, average > > at about 250 tps, peaks over 600 tps) a random drive disconnects from > > the RAID 10. After removing the drive from the config and rescanning the > > bus, the drive does not show up anymore. The only way to get the drive > > back is to unplug the drive (or switch the computer off, so that power > > is removed). After that there is no problem to rebuild the RAID with > > the drive. > > We were having problems with this even under light load, with Western > Digital SATA disks (not Raptors I don't think). In some cases all of the > disks would drop off the array. It was determined to be an incompatibility > between the controller (8506, I believe) and the motherboard (Tyan S2721). This is an other issue: 3Ware 8506 cards PCI timings are marginal and fail with some mainboards (mainly Tyan and Intel ones if I remember correctly). AFAIK, this is fixed with the 950x series. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA RAID Support
On Fri, Feb 25, 2005 at 12:05:43PM +0100, Oliver Brandmueller wrote: > > On Fri, Feb 25, 2005 at 09:33:39AM +0100, Francois Tigeot wrote: > > On Fri, Feb 25, 2005 at 12:31:22AM +0100, Oliver Brandmueller wrote: > > > We had problems here with 3ware + 72GB Raptors (10 krpm), so we moved to > > > > What sort of problems ? > > I was planning to use some sort of 3Ware/Raptor combination with amd64 > > -STABLE machines in the near future, and I am very interested by your > > experience... > > Under heavy load (I/O load on the disks constantly over 200 tps, average > at about 250 tps, peaks over 600 tps) a random drive disconnects from > the RAID 10. After removing the drive from the config and rescanning the > bus, the drive does not show up anymore. The only way to get the drive > back is to unplug the drive (or switch the computer off, so that power > is removed). After that there is no problem to rebuild the RAID with > the drive. Interesting. AFAIR the same sort of errors occured with some older WD drives and 3Ware 750x controllers. The solution was to flash the drives firmware. A quick googling found some reference to the problem on this document: http://japan.3ware.com/products/pdf/Drive_compatibility_list.pdf -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA RAID Support
On Fri, Feb 25, 2005 at 12:31:22AM +0100, Oliver Brandmueller wrote: > > We had problems here with 3ware + 72GB Raptors (10 krpm), so we moved to What sort of problems ? I was planning to use some sort of 3Ware/Raptor combination with amd64 -STABLE machines in the near future, and I am very interested by your experience... -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Merging phk's filedesc cleanup and lock pushdown.
On Thu, Feb 24, 2005 at 03:18:49AM -0500, Jeff Roberson wrote: > I am going to MFC phk's filedesc related work in the next few days. This > is required if I am ever to merge the vfs smp changes. I have a patch > available at: > > http://www.chesapeake.net/~jroberson/fdesc.patch > > I'd appreciate it if anyone who can would test this. It has been running > on current for 3-4 months, depending on the bit, but there's always a > chance of a botched merge. World doesn't build with this patch: cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /usr/src/usr.bin/fstat/fstat.c /usr/src/usr.bin/fstat/fstat.c: In function `dofiles': /usr/src/usr.bin/fstat/fstat.c:325: error: storage size of 'filed0' isn't known /usr/src/usr.bin/fstat/fstat.c:363: error: `NDFILE' undeclared (first use in this function) /usr/src/usr.bin/fstat/fstat.c:363: error: (Each undeclared identifier is reported only once /usr/src/usr.bin/fstat/fstat.c:363: error: for each function it appears in.) /usr/src/usr.bin/fstat/fstat.c:325: warning: unused variable `filed0' *** Error code 1 Stop in /usr/src/usr.bin/fstat. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. nice make buildworld 1209,00s user 251,75s system 78% cpu 31:04,65 total This machine is an amd64 5.3-STABLE host. The same sources build nicely without the patch. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 Release Schedule
On Tue, Feb 01, 2005 at 09:43:03PM -0500, Ken Smith wrote: > > Just a heads-up to say that the 5.4 release activities will begin towards > the end of February, with an expected release date of April 4th. Will there be a MFC of the ata code ? SATA-II controllers are beginning to show up quite often these days... -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building your own FreeBSD installation CD-ROM
On Tue, Jan 18, 2005 at 06:14:52PM +0100, David Landgren wrote: > > how does one go about creating a FreeBSD install CD-ROM? I'd like to be > able to build my own CD-ROM with as much as possible of the install > process done automatically. For instance, what parts of FreeBSD to > install: X or not, games or not, etc. etc. And which ports to install > straight away. I could also set up cfengine so that as soon as the > machine came to life it could go and connect to my cfengine repository > and download all the latest configurations to move into operational status. There is some documentation in /usr/src/release on how to build a custom release (I did it successfully around 4.4 time). It is also possible to script the installer via a configuration file. Look at sysinstall(8) manpage for details. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
