[amd64] Reproducible cold boot failure (reboot succeeds) in -CURRENT

Stefan Esser se at freebsd.org
Fri Nov 11 12:11:20 UTC 2011

Am 10.11.2011 11:32, schrieb Attilio Rao:
> 2011/11/10 Stefan Esser<se at freebsd.org>:
>> I can produce further debug output on demand, but I do not have a serial or
>> firewire console setup for debugging.
>> Is anybody else affected by this boot problem?
> Can you setup a videocamera or a simple serial console?
> Did you try to boot with both -s and -v on?
> Attilio

I should be able to attach a serial console.

Booting with -s should make no difference (since booting fails during a 
very early initialization stage).

I tried -v, but found that I could not reproduce the cold boot problem
without the system being at least in S5 for hours (just switching off
power and waiting a few minutes did not suffice, but this morning the
system again booted only on the first attempt). This behavior obviously
limits the rate of tests possible ...

It looks as if the memory holding the loaded kernel and/or modules is
corrupted before the kernel is reloaded and started, as indicated by
this morning's boot failure:

kldload: unexpected relocation type 268435457
kldload: unexpected relocation type 67108865
Fatal trap 12: ...

The rest of the panic message and back trace is identical to the trap 12 
panic details in my previous message.

It really looks as if the loaded kernel image is corrupted at random
positions, leading to random panics (but often of the type trap 12 or
page fault in kernel) when execution reaches damaged code or data.

A reboot succeeded without any problem as in all prior cases ...

Any ideas?

Regards, STefan

More information about the freebsd-current mailing list