Date: Thu, 18 Aug 2011 04:33:32 +0900 (JST) From: Hiroki Sato <hrs@FreeBSD.org> To: attilio@FreeBSD.org Cc: kostikbel@gmail.com, freebsd-stable@FreeBSD.org, avg@FreeBSD.org Subject: Re: panic: spin lock held too long (RELENG_8 from today) Message-ID: <20110818.043332.27079545013461535.hrs@allbsd.org> In-Reply-To: <CAJ-FndCDOW0_B2MV0LZEo-tpEa9%2B7oAnJ7iHvKQsM4j4B0DLqg@mail.gmail.com> References: <4E15A08C.6090407@sentex.net> <20110818.023832.373949045518579359.hrs@allbsd.org> <CAJ-FndCDOW0_B2MV0LZEo-tpEa9%2B7oAnJ7iHvKQsM4j4B0DLqg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Thu_Aug_18_04_33_32_2011_840)-- Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Attilio Rao <attilio@freebsd.org> wrote in <CAJ-FndCDOW0_B2MV0LZEo-tpEa9+7oAnJ7iHvKQsM4j4B0DLqg@mail.gmail.co= m>: at> 2011/8/17 Hiroki Sato <hrs@freebsd.org>: at> > Hi, at> > at> > Mike Tancsa <mike@sentex.net> wrote at> > =A0in <4E15A08C.6090407@sentex.net>: at> > at> > mi> On 7/7/2011 7:32 AM, Mike Tancsa wrote: at> > mi> > On 7/7/2011 4:20 AM, Kostik Belousov wrote: at> > mi> >> at> > mi> >> BTW, we had a similar panic, "spinlock held too long", the= spinlock at> > mi> >> is the sched lock N, on busy 8-core box recently upgraded = to the at> > mi> >> stable/8. Unfortunately, machine hung dumping core, so the= stack trace at> > mi> >> for the owner thread was not available. at> > mi> >> at> > mi> >> I was unable to make any conclusion from the data that was= present. at> > mi> >> If the situation is reproducable, you coulld try to revert= r221937. This at> > mi> >> is pure speculation, though. at> > mi> > at> > mi> > Another crash just now after 5hrs uptime. I will try and re= vert r221937 at> > mi> > unless there is any extra debugging you want me to add to t= he kernel at> > mi> > instead =A0? at> > at> > =A0I am also suffering from a reproducible panic on an 8-STABLE b= ox, an at> > =A0NFS server with heavy I/O load. =A0I could not get a kernel du= mp at> > =A0because this panic locked up the machine just after it occurre= d, but at> > =A0according to the stack trace it was the same as posted one. at> > =A0Switching to an 8.2R kernel can prevent this panic. at> > at> > =A0Any progress on the investigation? at> = at> Hiroki, at> how easilly can you reproduce it? It takes 5-10 hours. I installed another kernel for debugging just now, so I think I will be able to collect more detail information in a couple of days. at> It would be important to have a DDB textdump with these information= s: at> - bt at> - ps at> - show allpcpu at> - alltrace at> = at> Alternatively, a coredump which has the stop cpu patch which Andryi= can provide. Okay, I will post them once I can get another panic. Thanks! -- Hiroki ----Security_Multipart(Thu_Aug_18_04_33_32_2011_840)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAk5MF4wACgkQTyzT2CeTzy0Z6gCgluxIPrG308LTbGGysww6wQ4R 4TsAnj2fiZoQOXYk0jycI9e3TPKTFcpy =lTzB -----END PGP SIGNATURE----- ----Security_Multipart(Thu_Aug_18_04_33_32_2011_840)----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110818.043332.27079545013461535.hrs>