atom feed16 messages in org.freebsd.freebsd-currentRe: AP#1 Failed! panic y/n?
FromSent OnAttachments
Patrick LamaiziereAug 19, 2009 6:00 am 
Rink SpringerAug 19, 2009 6:20 am 
Ed SchoutenAug 19, 2009 7:17 am 
pluknetAug 19, 2009 7:36 am 
Ed SchoutenAug 19, 2009 7:41 am 
pluknetAug 19, 2009 7:55 am 
Patrick LamaiziereAug 19, 2009 8:07 am 
Ed SchoutenAug 19, 2009 8:09 am 
Patrick LamaiziereAug 19, 2009 10:16 am 
Patrick LamaiziereAug 19, 2009 10:19 am 
John BaldwinAug 19, 2009 10:51 am 
Jung-uk KimAug 19, 2009 11:17 am 
Jung-uk KimAug 19, 2009 11:48 am 
Ed SchoutenAug 19, 2009 11:54 pm 
pluknetAug 20, 2009 2:09 am 
pluknetAug 20, 2009 2:11 am 
Subject:Re: AP#1 Failed! panic y/n?
From:pluknet (pluk@gmail.com)
Date:Aug 19, 2009 7:55:14 am
List:org.freebsd.freebsd-current

2009/8/19 Ed Schouten <ed@80386.nl>:

* pluknet <pluk@gmail.com> wrote:

I'm not Patrik, but I saw this on two Intel boxes running on 6.2.  smbios.system.product="S5000PAL". I didn't try the later releases on them.

I wouldn't mind adding non-Apple hardware to this list, but only if you can tell me the following:

- Is this piece of hardware capable of running FreeBSD/amd64?

It seems so. This is a system with two Xeon 5130 populated. AMD Features=0x20000000<LM>

AP #3 (PHY# 7) failed! panic y/n? [y] panic: bye-bye cpuid = 0 KDB: enter: panic

[thread pid 0 tid 0 ] Stopped at kdb_enter+0x2b: nop db> x/s *panicstr buf.1: bye-bye db> bt Tracing pid 0 tid 0 td 0xc0a04d40 kdb_enter(c0924c08) at kdb_enter+0x2b panic(c09431b0,c0c26000,a,9,3,...) at panic+0x127 start_all_aps(10,c0c20d44,c0c20d5c,c067a5ba,c0a113c0,...) at start_all_aps+0x243 cpu_mp_start(c0a113c0,c0926d2b,0,1,c0c20d88,...) at cpu_mp_start+0x10c mp_start(0,c1ec00,c1e000,0,c044f3f5,...) at mp_start+0x47 mi_startup() at mi_startup+0x96 begin() at begin+0x2c

- Can you try latest HEAD on this system and test whether adding this  string has any influence?

This issue is repeated on boot rather seldom, one per dozen or so. I'll try anyway.