disable RAM parity error
Hello List, In continuation to my earlier mail, I am now convinced(nearly) that the freezes faced by me are "RAM parity error" indeed. http://www.mail-archive.com/freebsd-hack...@freebsd.org/msg70730.html when using internet via wpi0, FreeBSD freezes are very prone to occur compared to when I am using bfe0. But they do occur, due to some reason it feels stable when connected via bfe0. Over course of time I have accumulated some core.txt. files, which I have uploaded to pastebin and their links are below. My question is why only FreeBSD minds about RAM parity error check, while latest offering from Redmond does not ? is there a way to IGNORE RAM parity check ? is it possible to get hold of offending address from these core files ? while I observe "stack pointer" and "frame pointer" have repeated values in core files, I cannot conclude anything from this observation. Anybody here care ? core.txt.1 -- http://pastebin.com/HDji1Xvs core.txt.2 -- http://pastebin.com/yXg1iXAN core.txt.3 -- http://pastebin.com/xEfcgtQf core.txt.4 -- http://pastebin.com/zVQspP4g core.txt.5 -- http://pastebin.com/7RjL2san core.txt.6 -- http://pastebin.com/q4yjVefB Masoom Shaikh ___ 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"
FreeBSD RELEASE-8.0-p3 panic
Howdy, here is the image of my FreeBSD panic http://images.cjb.net/d64f4.jpg the error says RAM parity error(not visible in pic). but I have following reasons to believed it could be wrong 1. I have 1GB of RAM, with two chips of 512MB each. It panics even if I boot with only 512MB of total RAM. i.e. one chip removed. It panics for both chips individually. 2. I tried replacing my both 512MB chips with two 512MB chips from my friends laptop, it still panics with exact same error. RAM parity error, it is very unlikely that his chips have this problem. He runs Ubuntu on those chips and Windows7 with no issues whatsoever. 3. Windows7 operates on this(my) laptop just fine. sometimes it take 3-4 attempts to boot it, since it panics the moment KDM tries to load. But once running it runs few hours if I do not subject it to load. Even moderate load like browsing some multimedia content websites, e.g. youtube or some site with lots of flash based ads or even some javascript heavy page like GMail etc... It appears the moment I start subjecting the machine to load, mem usage increases and it hits the part of RAM which might possibly have parity error. have a look at the pic, the frame pointer is always remains same 0x803f1ef1. I have already asked, and again ask, is there a way to ask FreeBSD to "ignore" some part of RAM ? how do I zero in on the exact point of failure ? I am aware, just too many variables are here, some wild guesses ? I am very sorry for my feeble OS debugging skills if any, but FreeBSD has nothing to do with my day job, it is just a hobby for me. I sincerely want it to work. regards, Masoom Shaikh ___ 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: kernel: warning: attempt to domain_add(bluetooth) after domainfinalize()
On Friday January 8 2010 13:43:21 John Baldwin wrote: > On Friday 08 January 2010 4:51:19 am martinko wrote: > > Hi, > > > > I've been seeing the following on 7.x and 8.0 during boot: > > > > Jan 8 09:38:49 mb-aw1n-bsd kernel: WARNING: attempt to > > domain_add(bluetooth) after domainfinalize() > > > > It did not happen on 6.x. Is it a known issue ? > > I believe so. You can make the warning go away by compiling the bluetooth > modules into your kernel or loading them via loader.conf. > I load the bluetooth netgraph node via loader.conf ng_ubt_load="YES" I receive this warning as well, no idea with previous releases prior to 7.0 but I have always observed this warning. slightly off topic how to compile ng_ubt in kernel, it is not mentioned in man page, never bothered to dig, as it not required but kind of nice to have ___ 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: freebsd7, radeon, xorg-server -> deadlock or so
On Wed, Feb 10, 2010 at 4:54 AM, Oliver Pinter wrote: > Hi all! > > After updated the xorg* and dri* and dependency, the system going to > deadlock at second start of xserver. I think it is not an uniqe issue, > as others wrote them at freebsd-x11: > http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009370.html > > The symptoms: > * independent from enabled or disabled DRI or GLX, first I think, this > is the error, but not > * the system going to deadlock state > * no coredumps of xorgs > * no panic, but the system is unusuable > * independent from the driver: probed the radeon and radeonhd driver > * independent from the WITHOUT_NOUVEAU or WITH_NOUVEAU compile options > (make.conf) > * the system is: FreeBSD peonia.teteny.bme.hu 7.3-PRERELEASE FreeBSD > 7.3-PRERELEASE #29 r203612+fa83fdf: Mon Feb 8 02:11:08 CET 2010 > r...@peonia.teteny.bme.hu:/usr/obj/usr/src/sys/stable amd64 > ___ > 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" > are you using intel wireless cards ? I had/having similar issues when such freeze happens hard boot is the only option. I think it has something to do with wlandev or something related to wpi driver. I cannot comment more since coredumps are occasional and back trace suggests it is doadump(). here is my report earlier http://lists.freebsd.org/pipermail/freebsd-questions/2009-November/207768.html ___ 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"
Fwd: random FreeBSD panics
-- Forwarded message -- From: Masoom Shaikh Date: Sun, Mar 28, 2010 at 8:28 AM Subject: random FreeBSD panics To: freebsd-hack...@freebsd.org, freebsd-questions 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 :( Many times I get vmcore files, not always. I have dumpdev set to AUTO in my rc.conf. Almost every time it just fsck's the file-system on reboot. I have not lost any files though. This is a Dell Inspiron 1525 Laptop with 1GB ram, Intel Core2 Duo T5500 with ATI Radeon X1400 card. The installation in question is KDE4 from ports, with radeon/ati driver. I felt the problem is with wpi driver, then suspected dri driver of X. Then I observed system freezes even if none of this is installed. e.g. if it is under some load, like building a port and simultaneously fetching something over network it hangs, and hangs hard. This persuaded me to think something is wrong in kernel scheduling itself. May be it is lost in some deadlock, etc... Thus last weekend I thought I would see how immediate previous version i.e. FreeBSD-7.3-RELEASE would behave. I reinstalled FreeBSD7.1 from iso images, svn up'ed FreeBSD7.3 source, did the normal buildworld, buildkernel, installkernel, installworld cycle. Unfortunatly this kernel is naughty as well ;-), it also freezes with same stubbornness. But difference is this time I happen to catch something interesting. It panics on NMI, fatal trap 19 while in kernel mode. Loaded the vmcore file in kgdb and got the backtrace. I obtained vmcore files on two occasions. I have attached both the back traces. This error most likely suggests hardware error in RAM, but Windox7 and XP boot just fine and never caused any errors. To verify if I have errors in my RAM I let run sysutils/memtest86+ overnight, to double verify I also executed Windows Memory Diagnostic test for four times. None of them reported errors. Can anyone here suggest any solution. Masoom Shaikh forwarding to stable@ with respect to a generous suggestion vmcore0.log Description: Binary data vmcore1.log Description: Binary data ___ 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: random FreeBSD panics
On Sun, Mar 28, 2010 at 12:03 PM, Ivan Voras wrote: > On 28 March 2010 13:18, Masoom Shaikh wrote: >> On Sun, Mar 28, 2010 at 10:32 AM, Ivan Voras 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. ___ 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: random FreeBSD panics
On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote: > On 28 March 2010 16:42, Masoom Shaikh 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 this option is already there > configuration file if you can, to see if you can get a less mangled > log outout. > ___ 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: random FreeBSD panics
On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote: > On 28 March 2010 16:42, Masoom Shaikh 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 ___ 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: random FreeBSD panics
On Thu, Apr 8, 2010 at 4:45 PM, Anoop Kumar Narayanan wrote: > On Sat, Apr 3, 2010 at 6:21 PM, Masoom Shaikh wrote: >> On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote: >>> On 28 March 2010 16:42, Masoom Shaikh 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-questi...@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" >> > can u load that file in kgdb in get backtrace ? ___ 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: Freeze on my laptop.
On Wed, Apr 14, 2010 at 3:31 AM, Demelier David wrote: > Hi, > > I'm so sad because FreeBSD is the one which can runs almost perfectly > on > my laptop. But it freezes. Sometime I just do anything and I want to > click on a link in firefox, or open a terminal and then freeze. > > There is no messages, no reboot nothing. Can't know where that come > from. > > I'm running 8.0-STABLE on a hp probook 4510s. > > King regards, > -- > Demelier David > ___ > 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" > do u have dumpdev set in your rc.conf ? try setting it to AUTO, you might get a core dump on next reebot dumpdev="AUTO" there is very little in your mail to infer anything, do you use wireless net access ? what graphics card you have ? these threads might be of help to you http://lists.freebsd.org/pipermail/freebsd-questions/2010-March/214339.html http://lists.freebsd.org/pipermail/freebsd-stable/2010-April/056096.html http://lists.freebsd.org/pipermail/freebsd-hackers/2006-April/016107.html ___ 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: FreeBSD RoadMap
can this help ? http://ivoras.sharanet.org/freebsd/freebsd8.html On Mon, Jul 13, 2009 at 7:55 AM, Andrew Reilly < andrew-free...@areilly.bpc-users.org> wrote: > On Mon, Jul 13, 2009 at 12:55:19AM -0400, grarpamp wrote: > > Is there a general roadmap of what's planned > > for future major releases? I don't mean minor > > stuff like driver or contributed version bumps. > > But bigger, or just plain cool things, like as SMP, > > soft updates, ZFS, netgraph, pf, etc, were in the past. > > I doubt that there's much "big" in the ambit of "Unix-like OS" > that isn't already in the 8-current series. > > In a project like FreeBSD, "what's in the roadmap" equates > pretty closely with "what are the developers working on", and > that is summarised in the quarterly status reports, such as this > one: > http://www.freebsd.org/news/status/report-2009-01-2009-03.html > > As for when any of this will "hit the tree" and find its way > into a release, that's very much a "how long is a piece of > string" sort of question; not really the way FreeBSD works. > Particularly since it moved to a calendar-based release > schedule. > > IMO, YMMV, i-do-not-speak-for-freebsd, etc. > > Cheers, > > -- > Andrew > ___ > 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" > ___ 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"
