Date: Wed, 18 Dec 2013 14:58:20 -0500 From: John Baldwin <jhb@freebsd.org> To: "Poul-Henning Kamp" <phk@phk.freebsd.dk> Cc: freebsd-current@freebsd.org Subject: Re: r259072 is not a happy camper... Message-ID: <201312181458.20649.jhb@freebsd.org> In-Reply-To: <55350.1387010679@critter.freebsd.dk> References: <27325.1386444776@critter.freebsd.dk> <201312131620.25107.jhb@freebsd.org> <55350.1387010679@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, December 14, 2013 3:44:39 am Poul-Henning Kamp wrote: > In message <201312131620.25107.jhb@freebsd.org>, John Baldwin writes: > > >> >Hmmm. Maybe do 'show lapic' and 'show apic' in ddb and paste that here? > >> > >> sorry about the delay... > >> > >> db> show lapic > >> lapic ID = 2 > >> version = 1.0 > >> max LVT = 5 > >> SVR = ff (enabled) > >> TPR = 00 > >> In-service Interrupts: > > > >Hmm, this is empty. It should not be empty. :( > > > >Never the less, the panic is further down than I thought it was. The system > >thinks it had a valid IRQ that required an ithread to be scheduled, but when > >it went to schedule the ithread, there was no thread to schedule: > > >Does it get a crashdump if you try? > > No :-( > > There may be a connection to unclean UFS filesystems (SU + TRIM, no J). Is this reproducible? If so, build with KTR enabled and KTR_INTR set in KTR_COMPILE and KTR_MASK. That should at least let us see which interrupt it thinks it is triggering. 'show irqs' from DDB combined with 'show ktr' would then be useful. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201312181458.20649.jhb>