Re: panic: APIC: Previous IPI is stuck
From: Doug White (dwhite_at_gumbysoft.com)
Date: 07/18/04
- Previous message: Norikatsu Shigemura: "Re: Call for PRs: nullfs"
- In reply to: Kris Kennaway: "Re: panic: APIC: Previous IPI is stuck"
- Next in thread: Matthew Dillon: "Re: panic: APIC: Previous IPI is stuck"
- Reply: Matthew Dillon: "Re: panic: APIC: Previous IPI is stuck"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 17 Jul 2004 15:53:13 -0700 (PDT) To: Kris Kennaway <kris@obsecurity.org>
On Sat, 17 Jul 2004, Kris Kennaway wrote:
> > Does it only happen with a constant $NCPU+ load average? I have never
> > seen it here.
>
> Yeah, it's usually a pretty busy machine. It does a lot of
> buildworlds, nfs, concurrent www serving and ssh dispatching.
I triggered one of these last weekend, too. Peter mentioned something to
me about it being caused by both CPUs IPIng at once and there no deadlock
avoidance in that case. It died for me in installworld, though, which
made for a messy fixup job.
I guess our work on getting the kernel free-running is uncovering all
sorts of fun issues.
-- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Norikatsu Shigemura: "Re: Call for PRs: nullfs"
- In reply to: Kris Kennaway: "Re: panic: APIC: Previous IPI is stuck"
- Next in thread: Matthew Dillon: "Re: panic: APIC: Previous IPI is stuck"
- Reply: Matthew Dillon: "Re: panic: APIC: Previous IPI is stuck"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|