From owner-freebsd-current@FreeBSD.ORG  Tue Jun 15 09:22:55 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B7DDC16A4DA; Tue, 15 Jun 2004 09:22:55 +0000 (GMT)
Received: from expert.ukrtel.net (expert.ukrtel.net [195.5.6.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7FC6D43D2F; Tue, 15 Jun 2004 09:22:54 +0000 (GMT)
	(envelope-from astesin@ukrtelecom.net)
Received: from hoexc010.ho.ukrtelecom.net
          (doctor.ukrtel.net [195.5.37.134]) by expert.ukrtel.net
          (Netscape Messaging Server 3.5)  with ESMTP id AAAA2;
          Tue, 15 Jun 2004 12:20:59 +0300
Received: by hoexc010.ukrtelecom.net with Internet Mail Service (5.5.2653.19)
	id <MXA6Z8LL>; Tue, 15 Jun 2004 12:22:34 +0300
Message-ID: <1152675CA9EDD71187130002B3CE5ADA08A6F4F7@hoexc010.ukrtelecom.net>
From: astesin@ukrtelecom.net
To: delphij@frontfree.net, acpi@FreeBSD.org, current@FreeBSD.org
Date: Tue, 15 Jun 2004 12:22:34 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="koi8-r"
Subject: HA: [backtrace] kernel dump when shutting down
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jun 2004 09:22:55 -0000

Hello Xin,

> I got a strange problem when having HTT enabled on a P4 2.8E 
> processor. When rebooting the system, after the disk sync and 
> the system is going to restart, it crashes and generates a 
> crashdump. Strangely, the panic message seems to be corrupted.

That's exactly what I'm seeing on P4 3.0E (yes, also `E') and Intel
S875WP1-E motherboard
ftp://download.intel.com/support/motherboards/server/s875wp1-e/tps.pdf , but
it even doesn't do crashdump, just freeses. And not each time but maybe 3-4
of 5 reboots. BTW running `halt' instead of reboot worked. Sorry I didn't
had time this night to try a kernel with debugging.

> The system used to crash before sync'ing disks. It seems that 
> Nate's recent commit has removed that crash. More information 
> available upon request.

Exactly. 5.2.1-R and -CURRENT of late May were also tested, they were
crashing before syncing discs, 20040614 -CURRENT crashes (freeses) after
syncing.

People say that on older P4 CPUs (Northwood core) that do not have this
problem, only on `E'-s (??? Strange enough).

WBR,
Andrew