From owner-freebsd-current@FreeBSD.ORG Fri Nov 11 12:15:59 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8634106566B; Fri, 11 Nov 2011 12:15:59 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 351808FC1A; Fri, 11 Nov 2011 12:15:58 +0000 (UTC) Received: by wwg14 with SMTP id 14so3281721wwg.31 for ; Fri, 11 Nov 2011 04:15:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=H6w7hKtEPjL/rq0bPwZMRwOHGm0ToEU0blBfYwTSPuQ=; b=QFCLAICEAsgEsJOJV01VcAJJXK+gdNJ5m/ZQOhBVWNXYlfsU7pjJjTqSs9esEJ/0at epPJuA+7zCtxB6Oo5HFz9KKRpK6Ow6wWyVYRxX8Eak8L9IQnXH5td6zNOjXYCRJFDAQf cO5L4I+GNzDj5hHH4zBEzS3tvqRGWcIdqqWYM= MIME-Version: 1.0 Received: by 10.216.176.14 with SMTP id a14mr101216wem.14.1321013757174; Fri, 11 Nov 2011 04:15:57 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.216.182.3 with HTTP; Fri, 11 Nov 2011 04:15:57 -0800 (PST) In-Reply-To: <4EBD10E6.9000302@freebsd.org> References: <4EBB885E.9060908@freebsd.org> <4EBD10E6.9000302@freebsd.org> Date: Fri, 11 Nov 2011 13:15:57 +0100 X-Google-Sender-Auth: dpL5xuYvt0AsSGAFIklJ_jUT6nU Message-ID: From: Attilio Rao To: Stefan Esser Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current Subject: Re: [amd64] Reproducible cold boot failure (reboot succeeds) in -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2011 12:15:59 -0000 Can you try rebuilding your kernel and modules from scratch and see if it fixes your problem? Attilio 2011/11/11 Stefan Esser : > Am 10.11.2011 11:32, schrieb Attilio Rao: >> >> 2011/11/10 Stefan Esser: >>> >>> 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 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Peace can only be achieved by understanding - A. Einstein