On Sun, Mar 28, 2010 at 12:03 PM, Ivan Voras <ivoras@freebsd.org> wrote:> On 28 March 2010 13:18, Masoom Shaikh <masoom.shaikh@gmail.com> wrote: >> On Sun, Mar 28, 2010 at 10:32 AM, Ivan Voras <ivoras@freebsd.org> wrote: >>> Masoom Shaikh wrote: >>>> >>>> Hello List, >>>> >>>> I was a happy FreeBSD user, just before I installed FreeBSD8.0-RC1. Since >>>> then, system randomly just freezes, and there is no option other than hard >>>> boot. I guessed this will get solved in 8.0-RELEASE, but it was not :( >>> >>> I wild shot - did you try disabling superpages? >> >> umm, how do I do that ? > > Set > > vm.pmap.pg_ps_enabled=0 > > in /boot/loader.conf and reboot. Report back if it helps or not. >nopes, this didn't help too, machine freezed again after using for 30 minutes or so all it was doing is playing amarok, fetching sources from svn repos, and using firefox lets assume if this is h/w problem, then how can other OSes overcome this ? is there a way to make FreeBSD ignore this as well, let it result in reasonable performance penalty.
On Sun, Mar 28, 2010 at 8:42 AM, Masoom Shaikh <masoom.shaikh@gmail.com>wrote:> nopes, this didn't help too, machine freezed again after using for 30 > minutes or so > all it was doing is playing amarok, fetching sources from svn repos, > and using firefox > > lets assume if this is h/w problem, then how can other OSes overcome > this ? is there a way to make FreeBSD ignore this as well, let it > result in reasonable performance penalty. >They would remove or replace the bad hardware. I've seen more that one DIMM which passed every memory checker I could find in it's most extensive testing mode. Only consistently effective option is to replace with a known good piece of memory. -- Adam Vande More
On 28 March 2010 16:42, Masoom Shaikh <masoom.shaikh@gmail.com> wrote:> lets assume if this is h/w problem, then how can other OSes overcome > this ? is there a way to make FreeBSD ignore this as well, let it > result in reasonable performance penalty.Very probably, if only we could detect where the problem is. Try adding "options PRINTF_BUFR_SIZE=128" to the kernel configuration file if you can, to see if you can get a less mangled log outout.
On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras <ivoras@freebsd.org> wrote:> On 28 March 2010 16:42, Masoom Shaikh <masoom.shaikh@gmail.com> wrote: > >> lets assume if this is h/w problem, then how can other OSes overcome >> this ? is there a way to make FreeBSD ignore this as well, let it >> result in reasonable performance penalty. > > Very probably, if only we could detect where the problem is. > Try adding "options ? ? PRINTF_BUFR_SIZE=128" to the kernelthis option is already there> configuration file if you can, to see if you can get a less mangled > log outout. >
On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras <ivoras@freebsd.org> wrote:> On 28 March 2010 16:42, Masoom Shaikh <masoom.shaikh@gmail.com> wrote: > >> lets assume if this is h/w problem, then how can other OSes overcome >> this ? is there a way to make FreeBSD ignore this as well, let it >> result in reasonable performance penalty. > > Very probably, if only we could detect where the problem is. > Try adding "options ? ? PRINTF_BUFR_SIZE=128" to the kernel > configuration file if you can, to see if you can get a less mangled > log outout. >ok, after few days of silence I am back with more questions this time system feels little better, it is able to sustain for more time that what 7.3-RELEASE could FreeBSD raptor 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Thu Apr 1 01:20:45 UTC 2010 root@:/usr/obj/usr/src/sys/INSPIRON amd64 I am using KDE4, and when OS freezes, well it freezes, means I cannot change to tty0 and see the panic text, if any it might possibly have spit. the stuck frozen GUI keeps staring there. So the question is how to I capture that panic text ? unfortunately I am not getting core files too, so there is nothing I can pick up hints is there some option (KDB, DDB), so that on panic system drop to debugger ? Masoom Shaikh
On Sat, Apr 3, 2010 at 6:21 PM, Masoom Shaikh <masoom.shaikh@gmail.com> wrote:> On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras <ivoras@freebsd.org> wrote: >> On 28 March 2010 16:42, Masoom Shaikh <masoom.shaikh@gmail.com> wrote: >> >>> lets assume if this is h/w problem, then how can other OSes overcome >>> this ? is there a way to make FreeBSD ignore this as well, let it >>> result in reasonable performance penalty. >> >> Very probably, if only we could detect where the problem is. >> Try adding "options ? ? PRINTF_BUFR_SIZE=128" to the kernel >> configuration file if you can, to see if you can get a less mangled >> log outout. >> > > ok, after few days of silence I am back with more questions > this time system feels little better, it is able to sustain for more > time that what 7.3-RELEASE could > > FreeBSD raptor 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Thu Apr ?1 > 01:20:45 UTC 2010 ? ? root@:/usr/obj/usr/src/sys/INSPIRON ?amd64 > > I am using KDE4, and when OS freezes, well it freezes, means I cannot > change to tty0 and see the panic text, if any it might possibly have > spit. the stuck frozen GUI keeps staring there. So the question is how > to I capture that panic text ? unfortunately I am not getting core > files too, so there is nothing I can pick up hints > > is there some option (KDB, DDB), so that on panic system drop to debugger ? > > Masoom ShaikhI am having the very same problem, with my AMD64 running i386 (both 7.3-REL and 8.0-REL) keeps crashing, The best part is, if I disable ACPI it crashes before it even boots up so is the case with safe-mode and single-user-mode. With ACPI it boots up but crashes after a while. I have the vmcore files on the system. Who do I contact on this regard ?> _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
On Thu, Apr 8, 2010 at 4:45 PM, Anoop Kumar Narayanan <anoop.kn@gmail.com> wrote:> On Sat, Apr 3, 2010 at 6:21 PM, Masoom Shaikh <masoom.shaikh@gmail.com> wrote: >> On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras <ivoras@freebsd.org> wrote: >>> On 28 March 2010 16:42, Masoom Shaikh <masoom.shaikh@gmail.com> wrote: >>> >>>> lets assume if this is h/w problem, then how can other OSes overcome >>>> this ? is there a way to make FreeBSD ignore this as well, let it >>>> result in reasonable performance penalty. >>> >>> Very probably, if only we could detect where the problem is. >>> Try adding "options ? ? PRINTF_BUFR_SIZE=128" to the kernel >>> configuration file if you can, to see if you can get a less mangled >>> log outout. >>> >> >> ok, after few days of silence I am back with more questions >> this time system feels little better, it is able to sustain for more >> time that what 7.3-RELEASE could >> >> FreeBSD raptor 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Thu Apr ?1 >> 01:20:45 UTC 2010 ? ? root@:/usr/obj/usr/src/sys/INSPIRON ?amd64 >> >> I am using KDE4, and when OS freezes, well it freezes, means I cannot >> change to tty0 and see the panic text, if any it might possibly have >> spit. the stuck frozen GUI keeps staring there. So the question is how >> to I capture that panic text ? unfortunately I am not getting core >> files too, so there is nothing I can pick up hints >> >> is there some option (KDB, DDB), so that on panic system drop to debugger ? >> >> Masoom Shaikh > > I am having the very same problem, with my AMD64 running i386 (both > 7.3-REL and 8.0-REL) keeps crashing, The best part is, if I disable > ACPI it crashes before it even boots up so is the case with safe-mode > and single-user-mode. With ACPI it boots up but crashes after a while. > I have the vmcore files on the system. Who do I contact on this regard > ? > >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >> >can u load that file in kgdb in get backtrace ?