Subject: Re: More amd64 instability
To: None <paul@whooppee.com>
From: Greg Oster <oster@cs.usask.ca>
List: current-users
Date: 11/20/2007 16:19:26
Paul Goyette writes:
> On Tue, 20 Nov 2007, Juan RP wrote:
>
> > I see that sysmon_envsys* files in your kernel are not the newest ones,
> > could you please try updating? the locking in sme_events_check() was change
> d
> > recently.
>
> Well, I did a 'cvs update' in /usr/src/sys then rebuilt my kernel. It's
> worse than before!
>
> Right after it successfully probes the azalia0, I get
>
> uvm_fault(0xffffffff805e8c80, 0x0, 2) -> e
> kernel: page fault trap, code=0
> Stopped in pid 0.1 (system) at netbsd:softintr_schedule+0x60: movq %r12, 0(%
> rax)
here's what I just got:
scsibus0: waiting 2 seconds for devices to settle...
uvm_fault(0xffffffff80be9960, 0x0, 2) -> e
kernel: page fault trap, code=0
Stopped in pid 0.2 (system) at netbsd:softintr_schedule+0x60: movq %r12,0(%
rax)
db{0}> tr
softintr_schedule() at netbsd:softintr_schedule+0x60
Xresume_lapic_ltimer() at netbsd:Xresume_lapic_ltimer+0x21
--- interrupt ---
x86_stihlt() at netbsd:x86_stihlt+0x6
idle_loop() at netbsd:idle_loop+0x155
db{0}> machine cpu 1
using CPU 1
db{0}> tr
x86_stihlt() at netbsd:x86_stihlt+0x6
idle_loop() at netbsd:idle_loop+0x155
Bad frame pointer: 0xffff8000542672e0
db{0}> machine cpu 2
using CPU 2
db{0}> tr
x86_stihlt() at netbsd:x86_stihlt+0x6
idle_loop() at netbsd:idle_loop+0x155
Bad frame pointer: 0xffff80005426cba0
db{0}> machine cpu 3
using CPU 3
db{0}> tr
_kernel_lock() at netbsd:_kernel_lock+0xe8
db{0}>
> Exact same results on two consecutive boots.
Ditto for me too.
Later...
Greg Oster