Bug #1599
closedCrash on boot
0%
Description
shiningsilence.com will panic very early in the boot process as shown here:
http://www.shiningsilence.com/bootcrash.jpg
It's happened twice so far, and I have swapped out the
case/motherboard/power supply between the two events. The kernel config:
http://www.shiningsilence.com/WWW
APIC_IO is commented out, but SMP is not - I think this matches
leaf.dragonflybsd.org's setup. I wonder, though, since the panic's
happening while bringing up the CPU. It's running 2.4.1.
Updated by dillon almost 15 years ago
:shiningsilence.com will panic very early in the boot process as shown here:
:
:http://www.shiningsilence.com/bootcrash.jpg
:
:It's happened twice so far, and I have swapped out the
:case/motherboard/power supply between the two events. The kernel config:
:
:http://www.shiningsilence.com/WWW
:
:APIC_IO is commented out, but SMP is not - I think this matches
:leaf.dragonflybsd.org's setup. I wonder, though, since the panic's
:happening while bringing up the CPU. It's running 2.4.1.
I have occassionally seen the same panic w/ LEAF, and my other
Phenom II. Sometimes it can't bring up one of the CPUs. I'm
guessing it is a bug in our code somewhere but I do not know
where it might be.
-Matt
Matthew Dillon
<dillon@backplane.com>
Updated by sepherosa almost 15 years ago
On Wed, Nov 11, 2009 at 11:40 AM, Matthew Dillon
<dillon@apollo.backplane.com> wrote:
:shiningsilence.com will panic very early in the boot process as shown here:
:
:http://www.shiningsilence.com/bootcrash.jpg
:
:It's happened twice so far, and I have swapped out the
:case/motherboard/power supply between the two events. The kernel config:
:
:http://www.shiningsilence.com/WWW
:
:APIC_IO is commented out, but SMP is not - I think this matches
:leaf.dragonflybsd.org's setup. I wonder, though, since the panic's
:happening while bringing up the CPU. It's running 2.4.1.I have occassionally seen the same panic w/ LEAF, and my other
Hmm, me too. I got that seldomly on my phenom 9550., however, I only
saw it on phenom.
Maybe we have missed some configuration for phenom before sending the
startup ipi?
Best Regards,
sephe
Updated by justin over 12 years ago
- Description updated (diff)
- Status changed from New to Closed
- Assignee deleted (
0)
Hardware replaced, so no longer relevant.