Re: port-amd64/38478 (panic on boot when attaching cpu17)

["Christoph Egger" <Christoph_Egger%gmx.de@localhost>]

The following reply was made to PR port-amd64/38478; it has been noted by GNATS.

From: "Christoph Egger" <Christoph_Egger%gmx.de@localhost>
To: gnats-bugs%NetBSD.org@localhost, ad%NetBSD.org@localhost, 
gnats-admin%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost, port-amd64-maintainer%netbsd.org@localhost
Cc: 
Subject: Re: port-amd64/38478 (panic on boot when attaching cpu17)
Date: Tue, 13 May 2008 15:45:42 +0200

 > Synopsis: panic on boot when attaching cpu17
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: ad%NetBSD.org@localhost
 > State-Changed-When: Sun, 11 May 2008 22:57:34 +0000
 > State-Changed-Why:
 > Can you confirm that this is fixed in -current?
 
 Yes, partially at least.
 There's still a panic on boot related to many cpus:
 
 kernel double fault trap, code=0
 Stopped in pid 0.12 (system) at netbsd:Xintr_lapic_ltimer+0x38: movq   
%rdi,0(%rsp)
 
 %rsp value is 0xffff80004677afd0
 
 The double fault comes from a stack corruption/overflow.
 The interrupt stack is filled up with so many lapic timer handler's running 
concurrently.
 
 I suggest to make the interrupt stack per-cpu.
 
 
 -- 
 
 Christoph