On Saturday, December 14, 2013 3:44:39 am Poul-Henning Kamp wrote:
> In message <201312131620.25107....@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.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"