Date: Wed, 03 Aug 2005 10:10:02 +0200 From: "Alexander S. Usov" <A.S.Usov@kvi.nl> To: freebsd-stable@freebsd.org Subject: Re: panic: sbflush_locked on 5.4-p5/i386 Message-ID: <dcpu4r$p9s$1@sea.gmane.org> References: <6eb82e0507241001615f7490@mail.gmail.com> <dc0m7k$enm$1@sea.gmane.org> <20050729002138.X60522@fledge.watson.org> <dcd588$tkf$1@sea.gmane.org> <20050729125525.D74149@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: > On Fri, 29 Jul 2005, Alexander S. Usov wrote: > >>>> I got a few similar panics. >>>> It looks that I managet to get rid of them by setting mpsafenet=0, but >>>> I am not sure -- I have to monitor it for a bit longer. >>>> I have managed to get a few dumps, so the traces are: >> >> Unfortunately I don't have these dumps anymore, I will try to switch >> mpsafenet back on and wait for a new ones. They were quite reproducable >> for me. > > Thanks. I will be away this weekend, but hope to have a chance to look > into this early next week. If you could send me the dmesg of the box > also, and the output of "sysctl -a", that would be helpful. Probably out > of band rather than via the list (or if you could put it on a web page I > could reach). Uhm. It's appeared to be not a very good idea to do some cleanup on the notebook before I had enought tee :( Managed to do part of this "cleanup" in the terminal logged in via ssh and to delete this core dump :( However over the night I got one more, and once it will be uploaded to the woking machine I will pust some details. -- Best regards, Alexander.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dcpu4r$p9s$1>