Date: Sat, 14 Dec 2013 08:44:39 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: r259072 is not a happy camper... Message-ID: <55350.1387010679@critter.freebsd.dk> In-Reply-To: <201312131620.25107.jhb@freebsd.org> References: <27325.1386444776@critter.freebsd.dk> <201312091216.04052.jhb@freebsd.org> <44591.1386966997@critter.freebsd.dk> <201312131620.25107.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55350.1387010679>