Date: Mon, 24 Sep 2007 12:05:35 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: Borja Marcos <BORJAMAR@SARENET.ES> Cc: freebsd-hackers@freebsd.org, Benjie Chen <benjie@addgene.org> Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load Message-ID: <46F78BEF.4070406@FreeBSD.org> In-Reply-To: <BE519EAF-6927-4C78-867C-5D87AAC14F88@SARENET.ES> References: <c53be070709211526j2178ebb7ia6ea39e1a5df303c@mail.gmail.com> <FADD8244-DE07-4AA7-8EF0-C49257D4746B@SARENET.ES> <46F78459.4060607@FreeBSD.org> <BE519EAF-6927-4C78-867C-5D87AAC14F88@SARENET.ES>
next in thread | previous in thread | raw e-mail | index | archive | help
Borja Marcos wrote: > > On 24 Sep 2007, at 11:33, Kris Kennaway wrote: > >> Borja Marcos wrote: >>> I don't have the exact IP address involved, but we experienced >>> consistent panics in two heavily loaded mail servers (same hardware >>> models, Dell Powereedge) runnning Postfix and FreeBSD 6.2. >>> Suspecting an issue with the IP stack and smp I tried to set >>> "debug.mpsafenet=0" and the problems are gone. Of course I've lost >>> some performance, but the systems have been solid for some weeks so far. >> >> What number is the PR with the details? > > Sorry, I couldn't diagnose anything properly. When it happened the > sysadmin didn't give me the panic details, and being production machines > the main priority was to put them back into service as soon as possible. > > Would it be a good idea to file a PR with such fuzzy information? I > don't think so, that's why I didn't do it. Of course I can do it if > someone thinks it's worth. But unfortunately I cannot get more precise > details. No it isn't. You will need to do some more work to obtain this information, otherwise your bug will probably not be fixed. debug.mpsafenet=0 is no longer an option in 7.0, so you will have to deal with this sooner or later. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46F78BEF.4070406>