Re: Booting after make installworld takes ages [Was Re: Can't boot after make installworld]
On Fri, Jun 4, 2010 at 10:09 AM, Krzysztof Dajka krzysztof.da...@agora.plwrote: On Sunday, 21 of March 2010 20:15:29 Krzysztof Dajka wrote: Hi, I'm having problem with upgrading my FreeBSD to RELENG_8. Building world and kernel went smoothly I can boot with new kernel, but after 'make installworld' I could boot my system. My system prints only: BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is disk2 BIOS drive F: is disk3 | And freezes... I had a problem in march with booting after 'makeinstall' as stated above. It seems that I was impatient prejudged facts. For few months I was running newer kernel than world. After all I decided to upgrade whole system yesterday. After 'make installkernel', booting to new kernel went as usual. After 'make installworld' and rebooting it hangs at: BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is disk2 BIOS drive F: is disk3 | After waiting 50 seconds it started booting. During this time my usb flash drive, which contains only bootcode blinked as crazy. I remembered that Dan Naumov told me The ZFS bootloader has been changed in 8-STABLE compared to 8.0-RELEASE. Reinstall your boot blocks. So this time I did: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 But this didn't help, booting is still painfully slow. -- I have done few test and narrowed problem to probing usb devices. I have taken following steps: 1) I prepared installed bootcode to 3 devices - 512MB Kingston flash drive - 32MB SD Card - 1MB file (created with dd, mounted with mdconfig, added gpt partition and freebsd-boot slice) booted over pxe 2) All devices had newest bootcode, booting from every device was terrible slow, but sd card was significantly slower than others. 3) I played with my zpool # zpool offline zroot gpt/disk2 4) reboot 5) I booted with every device. Booting from both devices connected to usb bus, was slow. Booting over pxe from 1MB 'drive' with bootcode was very fast as it should be. 6) Booting over pxe with any device attached to usb bus was again slow! 7) I did: #zpool online zroot gpt/disk2 And rebooted over pxe. Still fast. I noticed that /boot/zfs/zpool.cache was updated after puting offline gpt/disk2, but I can't remember if it was updated after upgrading kernel and world. ___ 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
Booting after make installworld takes ages [Was Re: Can't boot after make installworld]
On Sunday, 21 of March 2010 20:15:29 Krzysztof Dajka wrote: Hi, I'm having problem with upgrading my FreeBSD to RELENG_8. Building world and kernel went smoothly I can boot with new kernel, but after 'make installworld' I could boot my system. My system prints only: BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is disk2 BIOS drive F: is disk3 | And freezes... I had a problem in march with booting after 'makeinstall' as stated above. It seems that I was impatient prejudged facts. For few months I was running newer kernel than world. After all I decided to upgrade whole system yesterday. After 'make installkernel', booting to new kernel went as usual. After 'make installworld' and rebooting it hangs at: BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is disk2 BIOS drive F: is disk3 | After waiting 50 seconds it started booting. During this time my usb flash drive, which contains only bootcode blinked as crazy. I remembered that Dan Naumov told me The ZFS bootloader has been changed in 8-STABLE compared to 8.0-RELEASE. Reinstall your boot blocks. So this time I did: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 But this didn't help, booting is still painfully slow. -- Niniejsza wiadomość pochodzi z domeny @agora.pl, należącej do Grupy Kapitałowej Agory. Główne spółki wchodzące w skład Grupy Kapitałowej Agory to: Agora SA, ul. Czerska 8/10, 00-732 Warszawa; Numer identyfikacji podatkowej: PL 526-030-56-44; Miejsce zarejestrowania: Sąd Rejonowy dla m. st. Warszawy: Numer rejestru KRS: 59944; Kapitał zakładowy: 50.937.386 zł, wpłacony w całości. Agora - Poligrafia Sp. z o.o., ul. Towarowa 4, 43-110 Tychy; Numer identyfikacji podatkowej: PL 646-20-72-095; Miejsce zarejestrowania: Sąd Rejonowy w Katowicach Numer rejestru KRS: 72481; Kapitał zakładowy: 1.000.000,00 zł. Grupa Radiowa Agory Sp. z o.o., ul. Czerska 8/10, 00-732 Warszawa; Numer identyfikacji podatkowej: PL 521-289-70-03; Miejsce zarejestrowania: Sąd Rejonowy dla m. st. Warszawy Numer rejestru KRS: 126767; Kapitał zakładowy: 25.019.500,00 zł. Więcej informacji o spółkach na stronie: www.agora.pl Wiadomość jest przeznaczona wyłącznie dla zamierzonego adresata i może zawierać informacje o charakterze poufnym. W razie stwierdzenia, że odbiorcą miała być inna osoba prosimy poinformować nadawcę oraz niezwłocznie usunąć wiadomość. Wiadomość może nie stanowić oficjalnego stanowiska spółki Agora SA i nie być związana z jej działalnością. This message was sent from domain @agora.pl belonging to Agora Group. Principal companies in the Agora Group structure are: Agora SA, ul. Czerska 8/10, 00-732 Warszawa; Polish VAT and tax ID no.: PL 526-030-56-44; Place of registration: Regional Court for the Capital City of Warsaw; Registration no.: 59944; Share capital: PLN 50.937.386, fully paid-up. Agora - Poligrafia Sp. z o.o., ul. Towarowa 4, 43-110 Tychy; Polish VAT and tax ID no.: PL 646-20-72-095; Place of registration: Regional Court in Katowice; Registration no.: 72481; Share capital: PLN 1.000.000,00. Grupa Radiowa Agory Sp. z o.o., ul. Czerska 8/10, 00-732 Warszawa; Polish VAT and tax ID no.: PL 521-289-70-03; Place of registration: Regional Court for the Capital City of Warsaw; Registration no.: 126767; Share capital: PLN 25.019.500,00. For more information about our companies see site: www.agora.pl This message is for the intended recipient only and it may contain confidential information. If you receive this message in error, please immediately delete it and notify the sender. This message may not represent the official views of Agora SA and may not be related to its business. ___ 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: Can't boot after make installworld
On Mon, Mar 22, 2010 at 08:41:35PM +, Krzysztof Dajka wrote: But still I am confused with FreeBSD naming and it's relation with tags which are used in standard-supfile. Please see the following for an overview: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/introduction.html#CURRENT The definition of the -STABLE branches is that we try to keep the interfaces to the kernel stable. While this helps also keep the src tree itself stable, from time to time regressions will be introduced as changes are merged back from the -CURRENT branch. So, for the src tree, there are: - releases, which are not updated; - releases plus security fixes; - -STABLE branches; - the -CURRENT branch. The ports tree is not branched, so you can consider that everything is current. If you need to stay with a ports tree that is more tested, you'll need to stay with the ports tree that came with a -release. mcl ___ 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: Can't boot after make installworld
On Mon, Mar 22, 2010 at 08:41:35PM +, Krzysztof Dajka wrote: At first I didn't knew that I am upgrading to bleeding edge/developer branch of FreeBSD. You're not. There seems to be some misconceptions with regards to what the tags represent, because people's opinions get in the way (mine included). I'll give you the run down as someone who's been using FreeBSD since the 2.2 days. I'm speaking strictly about src (base system, OS, etc.) and not ports. Ports are their own thing, and aren't tagged (the ports infrastructure should work on any of the below tags, which is why ports are always tag=.). I also include correlations to Debian release nomenclature. Hope this helps. -RELEASE (tag=RELENG_x_y) An official release of the OS when a new version comes out. Changes to this tag are rarely made; the exceptions to the rule are security fixes and *serious* (major/extreme) stability fixes. Serious means something that would impact the OS from functioning for all systems and is considered volatile -- it does not mean feature X doesn't work right or driver X doesn't function correctly. Users who encounter a problem of this nature are told to run -STABLE where the fix is. The FreeBSD user community often totes this as the most rock solid release tag there is, which in my opinion hasn't been the case since the 4.x days. We've used the STABLE branches since the 4.x days and have only run into problems on rare occasion (rolling back to a previous commit is as easy as using csup's date tag in the supfile). In the Debian world, this tag would correlate with stable/lenny. -STABLE (tag=RELENG_x) Identical to RELEASE except changes to this tag are made fairly regularly. OS/kernel, drivers, base system/userland, and security issues are all addressed here. Meaning: if you encounter something broken in non-CURRENT FreeBSD, the fix/change will most likely go into this branch. The more you read popular FreeBSD mailing lists (freebsd-stable, freebsd-users, freebsd-questions, etc.), the more you'll realise that's the case. MFCs (merge from CURRENT) are also occasionally brought down from HEAD (see below) into this branch for usability testing. This is where anti-STABLE advocates get their STABLE isn't stable at all, use RELEASE if you want stability viewpoint. The FreeBSD user community has split opinions of this branch; some believe it to be a development/unstable branch, while others (like myself) believe it to be more solid than RELEASE, since developers are much more focused on STABLE than RELEASE. Developers who break the STABLE branch are usually lectured/reprimanded in some way; such breakage usually appears as buildworld/buildkernel failing. Turnaround time for fixing such breakage is usually 24-48 hours tops. In the Debian world, this tag would correlate with testing/squeeze. -CURRENT (tag=., otherwise known as HEAD) This is where all the crazy, in-development code and features go. That includes library API changes, kernel ABI changes, kernel threading adjustments, experimental drivers (it works on this one system I have at home but that's it), or anything else a developer/committer is working on which is brand-spanking-new. It also encapsulates major underlying configuration changes in the OS, including pathname changes or syntactical changes. The OS is also significantly slower (kernel-wise out-of-the-box due to the default kernel configs enabling debugging/analysis features which are necessary for development. This branch is known to break quite often, and that's 100% OK. Data loss can happen as well, depending on what breaks or what bugs are introduced, so if you run this you should absolutely do back-ups. In the Debian world, this tag would correlate with unstable/sid. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: Can't boot after make installworld
Thanks a lot for clarifying. I think that I'm going to stick with STABLE release, as it reflects my expectations and time I can dedicate to tinker with my system. For some while I thought that I would return to Debian, because I became used to it's pros and cons. Thanks to experience I gained in few months in FreeBSD land I didn't think about Debian in GNU/Linux incarnation, but at least Debian/kFreeBSD. Unfortunately as of today Debian/kFreeBSD doesn't support booting from zfs. I think that it was good idea to migrate to FreeBSD, as for now I'm missing fast upgrades and deployment which are Debian assets, but I'm getting used to ports and possibility of tuning system. I've read thread http://lists.freebsd.org/pipermail/freebsd-fs/2010-March/007956.html, PJD is suggesting to enable few options in kernel: options WITNESS options WITNESS_SKIPSPIN options INVARIANTS options INVARIANT_SUPPORT options DEBUG_VFS_LOCKS options DEBUG_LOCKS options KDB options DDB Is there something else I should turn on in kernel before running bonnie++ which will surely crash my system? And one more question is there a way to build new kernel which would be called ie kernel_debug which I would load only when needed? On 3/24/10, Jeremy Chadwick free...@jdc.parodius.com wrote: Since you replied to Mark and I personally -- can you send a copy of this mail back to the mailing list? Others should be able to help answer the above questions; in this case, more eyes = good. :-) Sorry about that sending mails not to everyone happens to me all the time ;) ___ 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: Can't boot after make installworld
On Monday, 22 of March 2010 23:00:17 Dan Naumov wrote: On Mon, Mar 22, 2010 at 10:41 PM, Krzysztof Dajka alter...@gmail.com wrote: I've read that FreeBSD kernel supports 3D acceleration in ATI R7xx chipset and as I own motherboard with HD3300 built-in I thought that I would give it a try. I upgraded to see if there is any progress with ¿zfs? I don't really know if it's zfs related, but at certain load, my system crashes, and reboots. It happens only when using bonnie++ to benchmark I/O. If you can consistently panic your 8.0 system with just bonnie++ alone, something is really really wrong. Are you using an amd64 system with 2gb ram or more or is this i386 + 1-2gb ram? Amd64 systems with 2gb ram or more don't really usually require any tuning whatsoever (except for tweaking performance for a specific workload), but if this is i386, tuning will be generally required to archieve stability. I have AMD64 with ~3,6G ram (rest is assigned to built-in hd3300) and 3x500GB in raidz1. As it's full zfs system, I'm booting from SD card. What should I enable in kernel to produce good crashdump? ___ 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: Can't boot after make installworld
On Monday, 22 of March 2010 22:55:17 Dan Naumov wrote: I've read that FreeBSD kernel supports 3D acceleration in ATI R7xx chipset and as I own motherboard with HD3300 built-in I thought that I would give it a try. I upgraded to see if there is any progress with ¿zfs? I don't really know if it's zfs related, but at certain load, my system crashes, and reboots. It happens only when using bonnie++ to benchmark I/O. And I'm a little bit to lazy to prepare my system for coredumps - I don't have swap slice for crashdumps, because I wanted to simplify adding drives to my raidz1 configuration. Could anyone tell me what's needed, besides having swap to produce good crashdump? As of right now, even if you don't care about capability to take crash dumps, it is highly recommended to still use traditional swap partitions even if your system is otherwise fully ZFS. There are know stability problems involving using a ZVOL as a swap device. These issues are being worked on, but this is still the situation as of now. At first I didn't knew that I am upgrading to bleeding edge/developer branch of FreeBSD. I'll come straight out with it, 8.0-STABLE sounds more stable than 8.0-RELEASE-p2, which I was running before upgrade ;) I'm a little confused with FreeBSD release cycle at first I compared it with Debian release cycle, because I'm most familiar to it, and I used it a lot before using FreeBSD. Debian development is more one-dimensional - unstable/testing/stable/oldstable whereas FreeBSD has two stable branches - 8.0 and 7.2 which are actively developed. But still I am confused with FreeBSD naming and it's relation with tags which are used in standard-supfile. We have something like this: 9.0-CURRENT - tag=. 8.0-STABLE - tag=RELENG_8 8.0-RELEASE-p2 - tag=RELENG_8_0 ? (btw what does p2 mean?) If someone patient could explain it to me I'd be grateful. 9-CURRENT: the real crazyland 8-STABLE: a dev branch, from which 8.0 was tagged and eventually 8.1 will be RELENG_8_0: 8.0-RELEASE + latest critical security and reliability updates (8.0 is up to patchset #2, hence -p2) Same line of thinking applies to 7-STABLE, 7.3-RELEASE and so on. - Sincerely, Dan Naumov Thanks for clarifying. I will try turning swap ASAP. ___ 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: Can't boot after make installworld
The ZFS bootloader has been changed in 8-STABLE compared to 8.0-RELEASE. Reinstall your boot blocks. P.S: LOADER_ZFS_SUPPORT=YES is also deprecated in 8-STABLE, not to mention that you have it in the wrong place, for 8.0, it goes into make.conf, not src.conf. Is there any particular reason you are upgrading from a production release to a development branch of the OS? - Sincerely, Dan Naumov ___ 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: Can't boot after make installworld
On Mon, 22 Mar 2010 07:13, Dan Naumov wrote:
In Message-Id: cf9b1ee01003220413t14a75e95pc4acf072f876a...@mail.gmail.com
The ZFS bootloader has been changed in 8-STABLE compared to
8.0-RELEASE. Reinstall your boot blocks.
P.S: LOADER_ZFS_SUPPORT=YES is also deprecated in 8-STABLE, not to
mention that you have it in the wrong place, for 8.0, it goes into
make.conf, not src.conf.
P.S.S: src.conf is the correct place this should be placed but will also
work if placed in make.conf.
As stated in src.conf(5)
---
The src.conf file contains settings that will apply to every build
involving the FreeBSD source tree; see build(7).
The src.conf file uses the standard makefile syntax. However, src.conf
should not specify any dependencies to make(1). Instead, src.conf is to
set make(1) variables that control the aspects of how the system builds.
---
It would be almost to the same effect of doing this at the end of your
make.conf except it has already been done for you elsewhere.
.if ${.CURDIR:M/usr/src*}
.include /etc/src.conf
.endif
Is there any particular reason you are upgrading from a production
release to a development branch of the OS?
- Sincerely,
Dan Naumov
Regards,
--
jhell
___
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: Can't boot after make installworld
On Mar 22, 2010, at 7:01 AM, jhell jh...@dataix.net wrote:
On Mon, 22 Mar 2010 07:13, Dan Naumov wrote:
In Message-Id: cf9b1ee01003220413t14a75e95pc4acf072f876a...@mail.gmail.com
The ZFS bootloader has been changed in 8-STABLE compared to
8.0-RELEASE. Reinstall your boot blocks.
P.S: LOADER_ZFS_SUPPORT=YES is also deprecated in 8-STABLE, not to
mention that you have it in the wrong place, for 8.0, it goes into
make.conf, not src.conf.
P.S.S: src.conf is the correct place this should be placed but will
also work if placed in make.conf.
As stated in src.conf(5)
---
The src.conf file contains settings that will apply to every build
involving the FreeBSD source tree; see build(7).
The src.conf file uses the standard makefile syntax. However,
src.conf should not specify any dependencies to make(1). Instead,
src.conf is to set make(1) variables that control the aspects of how
the system builds.
---
It would be almost to the same effect of doing this at the end of
your make.conf except it has already been done for you elsewhere.
.if ${.CURDIR:M/usr/src*}
.include /etc/src.conf
.endif
And can be easily tuned via the SRCCONF variable (unless of course
WITHOUT_SRCCONF is defined...), as this logic is a part of bsd.own.mk .
Cheers,
-Garrett
___
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: Can't boot after make installworld
On 3/22/10, Dan Naumov dan.nau...@gmail.com wrote: The ZFS bootloader has been changed in 8-STABLE compared to 8.0-RELEASE. Reinstall your boot blocks. Thanks for pointers, I will run gpart to reinstall bootcode on my SD card. Is there any particular reason you are upgrading from a production release to a development branch of the OS? I've read that FreeBSD kernel supports 3D acceleration in ATI R7xx chipset and as I own motherboard with HD3300 built-in I thought that I would give it a try. I upgraded to see if there is any progress with ¿zfs? I don't really know if it's zfs related, but at certain load, my system crashes, and reboots. It happens only when using bonnie++ to benchmark I/O. And I'm a little bit to lazy to prepare my system for coredumps - I don't have swap slice for crashdumps, because I wanted to simplify adding drives to my raidz1 configuration. Could anyone tell me what's needed, besides having swap to produce good crashdump? At first I didn't knew that I am upgrading to bleeding edge/developer branch of FreeBSD. I'll come straight out with it, 8.0-STABLE sounds more stable than 8.0-RELEASE-p2, which I was running before upgrade ;) I'm a little confused with FreeBSD release cycle at first I compared it with Debian release cycle, because I'm most familiar to it, and I used it a lot before using FreeBSD. Debian development is more one-dimensional - unstable/testing/stable/oldstable whereas FreeBSD has two stable branches - 8.0 and 7.2 which are actively developed. But still I am confused with FreeBSD naming and it's relation with tags which are used in standard-supfile. We have something like this: 9.0-CURRENT - tag=. 8.0-STABLE - tag=RELENG_8 8.0-RELEASE-p2 - tag=RELENG_8_0 ? (btw what does p2 mean?) If someone patient could explain it to me I'd be grateful. ___ 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: Can't boot after make installworld
I've read that FreeBSD kernel supports 3D acceleration in ATI R7xx chipset and as I own motherboard with HD3300 built-in I thought that I would give it a try. I upgraded to see if there is any progress with ¿zfs? I don't really know if it's zfs related, but at certain load, my system crashes, and reboots. It happens only when using bonnie++ to benchmark I/O. And I'm a little bit to lazy to prepare my system for coredumps - I don't have swap slice for crashdumps, because I wanted to simplify adding drives to my raidz1 configuration. Could anyone tell me what's needed, besides having swap to produce good crashdump? As of right now, even if you don't care about capability to take crash dumps, it is highly recommended to still use traditional swap partitions even if your system is otherwise fully ZFS. There are know stability problems involving using a ZVOL as a swap device. These issues are being worked on, but this is still the situation as of now. At first I didn't knew that I am upgrading to bleeding edge/developer branch of FreeBSD. I'll come straight out with it, 8.0-STABLE sounds more stable than 8.0-RELEASE-p2, which I was running before upgrade ;) I'm a little confused with FreeBSD release cycle at first I compared it with Debian release cycle, because I'm most familiar to it, and I used it a lot before using FreeBSD. Debian development is more one-dimensional - unstable/testing/stable/oldstable whereas FreeBSD has two stable branches - 8.0 and 7.2 which are actively developed. But still I am confused with FreeBSD naming and it's relation with tags which are used in standard-supfile. We have something like this: 9.0-CURRENT - tag=. 8.0-STABLE - tag=RELENG_8 8.0-RELEASE-p2 - tag=RELENG_8_0 ? (btw what does p2 mean?) If someone patient could explain it to me I'd be grateful. 9-CURRENT: the real crazyland 8-STABLE: a dev branch, from which 8.0 was tagged and eventually 8.1 will be RELENG_8_0: 8.0-RELEASE + latest critical security and reliability updates (8.0 is up to patchset #2, hence -p2) Same line of thinking applies to 7-STABLE, 7.3-RELEASE and so on. - Sincerely, Dan Naumov ___ 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: Can't boot after make installworld
On Mon, Mar 22, 2010 at 10:41 PM, Krzysztof Dajka alter...@gmail.com wrote: I've read that FreeBSD kernel supports 3D acceleration in ATI R7xx chipset and as I own motherboard with HD3300 built-in I thought that I would give it a try. I upgraded to see if there is any progress with ¿zfs? I don't really know if it's zfs related, but at certain load, my system crashes, and reboots. It happens only when using bonnie++ to benchmark I/O. If you can consistently panic your 8.0 system with just bonnie++ alone, something is really really wrong. Are you using an amd64 system with 2gb ram or more or is this i386 + 1-2gb ram? Amd64 systems with 2gb ram or more don't really usually require any tuning whatsoever (except for tweaking performance for a specific workload), but if this is i386, tuning will be generally required to archieve stability. - Sincerely, Dan Naumov ___ 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
