panic: spin lock held too long (RELENG_8 from today)

[Hiroki Sato]

Hiroki Sato <hrs at freebsd.org> wrote
  in <20110818.043332.27079545013461535.hrs at allbsd.org>:

hr> Attilio Rao <attilio at freebsd.org> wrote
hr>   in <CAJ-FndCDOW0_B2MV0LZEo-tpEa9+7oAnJ7iHvKQsM4j4B0DLqg at mail.gmail.com>:
hr> 
hr> at> 2011/8/17 Hiroki Sato <hrs at freebsd.org>:
hr> at> > Hi,
hr> at> >
hr> at> > Mike Tancsa <mike at sentex.net> wrote
hr> at> >  in <4E15A08C.6090407 at sentex.net>:
hr> at> >
hr> at> > mi> On 7/7/2011 7:32 AM, Mike Tancsa wrote:
hr> at> > mi> > On 7/7/2011 4:20 AM, Kostik Belousov wrote:
hr> at> > mi> >>
hr> at> > mi> >> BTW, we had a similar panic, "spinlock held too long", the spinlock
hr> at> > mi> >> is the sched lock N, on busy 8-core box recently upgraded to the
hr> at> > mi> >> stable/8. Unfortunately, machine hung dumping core, so the stack trace
hr> at> > mi> >> for the owner thread was not available.
hr> at> > mi> >>
hr> at> > mi> >> I was unable to make any conclusion from the data that was present.
hr> at> > mi> >> If the situation is reproducable, you coulld try to revert r221937. This
hr> at> > mi> >> is pure speculation, though.
hr> at> > mi> >
hr> at> > mi> > Another crash just now after 5hrs uptime. I will try and revert r221937
hr> at> > mi> > unless there is any extra debugging you want me to add to the kernel
hr> at> > mi> > instead  ?
hr> at> >
hr> at> >  I am also suffering from a reproducible panic on an 8-STABLE box, an
hr> at> >  NFS server with heavy I/O load.  I could not get a kernel dump
hr> at> >  because this panic locked up the machine just after it occurred, but
hr> at> >  according to the stack trace it was the same as posted one.
hr> at> >  Switching to an 8.2R kernel can prevent this panic.
hr> at> >
hr> at> >  Any progress on the investigation?
hr> at> 
hr> at> Hiroki,
hr> at> how easilly can you reproduce it?
hr> 
hr>  It takes 5-10 hours.  I installed another kernel for debugging just
hr>  now, so I think I will be able to collect more detail information in
hr>  a couple of days.
hr> 
hr> at> It would be important to have a DDB textdump with these informations:
hr> at> - bt
hr> at> - ps
hr> at> - show allpcpu
hr> at> - alltrace
hr> at> 
hr> at> Alternatively, a coredump which has the stop cpu patch which Andryi can provide.
hr> 
hr>  Okay, I will post them once I can get another panic.  Thanks!

 I got the panic with a crash dump this time.  The result of bt, ps,
 allpcpu, and traces can be found at the following URL:

  http://people.allbsd.org/~hrs/FreeBSD/pool-panic_20110818-1.txt

-- Hiroki