From owner-freebsd-amd64@FreeBSD.ORG Mon Jul 25 11:07:02 2011 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BCA6106566B for ; Mon, 25 Jul 2011 11:07:02 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 813708FC1D for ; Mon, 25 Jul 2011 11:07:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p6PB72ch046306 for ; Mon, 25 Jul 2011 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p6PB71Cf046304 for freebsd-amd64@FreeBSD.org; Mon, 25 Jul 2011 11:07:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Jul 2011 11:07:01 GMT Message-Id: <201107251107.p6PB71Cf046304@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2011 11:07:02 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/157386 amd64 [powerd] Enabling powerd(8) with default settings on I o amd64/156464 amd64 fpsetprec does not work o amd64/156106 amd64 [boot] boot0 fails to start o amd64/156074 amd64 [hang] Removing CD-Rom from Lenovo T61p hangs system o amd64/155249 amd64 [build] 8.1 buildworld failure o amd64/155135 amd64 [boot] Does Not Boot On a Very Standard Hardware o amd64/154957 amd64 [boot] Install boot CD won't boot up - keeps rebooting o amd64/154629 amd64 [panic] Fatal trap 9: general protection fault while i o amd64/153935 amd64 [hang] system hangs while trying to do 'shutdown -h no o amd64/153831 amd64 [boot] CD bootloader won't on Tyan s2912G2nr o amd64/153496 amd64 [hyper-v] [install] Install on Hyper-V leaves corrupt o amd64/153372 amd64 [panic] kernel panic o amd64/153175 amd64 [amd64] Kernel Panic on only FreeBSD 8 amd64 o amd64/152874 amd64 [install] 8.1 install fails where 7.3 works due to lac o amd64/152430 amd64 [boot] HP ProLiant Microserver n36l cannot boot into i o amd64/151385 amd64 [boot] Installation hangs on MacBook o amd64/150170 amd64 [patch] [amd64] [headers] SIG_ATOMIC_MIN/SIG_ATOMIC_MA o amd64/145991 amd64 [NOTES] [patch] Add a requires line to /sys/amd64/conf o amd64/144405 amd64 [build] [patch] include /usr/obj/lib32 in cleanworld t s amd64/143173 amd64 [ata] Promise FastTrack TX4 + SATA DVD, installer can' f amd64/141413 amd64 [hang] Tyan 2881 m3289 SMDC freeze o amd64/141060 amd64 [install] Can't install 8.0-RELEASE on the server wher o amd64/140715 amd64 [boot] Dell M600 Blade fails to boot 7.2+ 64 bit o amd64/139998 amd64 [panic][net] 7.2 amd64 panic in rtrequest1_fib o amd64/139924 amd64 [boot] cd or dvd not load o amd64/137942 amd64 [pci] 8.0-BETA2 having problems with Asus M2N-SLI-delu o amd64/135265 amd64 [mpt] Boot from install cd hangs on HP DL160 G5 with L o amd64/135040 amd64 [ata] FreeBSD/amd64 does not (always) detect disk on S o amd64/133977 amd64 [panic] [ffs] "panic: ffs_blkfree: freeing free block" o amd64/133701 amd64 Recompiling the kernel with k8temp or smbios break GEO o amd64/132574 amd64 [boot] [hang] Freeze on bootstrap loader (CD) using AT o amd64/131456 amd64 [acpi] [ata] ACPI & ATA problems s amd64/131209 amd64 [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute o amd64/129889 amd64 [boot] [hang] The booting process stops at the line mo o amd64/129426 amd64 [panic] FreeBSD 7.0 crash after subdiskXX: detached o amd64/129315 amd64 [em] amd64 motherboard: Intel DG965WH motherboard comp o amd64/128765 amd64 [install] Install CD loads to Install choices but stop o amd64/127640 amd64 [amd64] gcc(1) will not build shared libraries with -f o amd64/125002 amd64 [install] amd64, SATA hard disks not detected o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 48 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Jul 25 18:55:30 2011 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 5D141106567C; Mon, 25 Jul 2011 18:55:29 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Callum Gibson Date: Mon, 25 Jul 2011 14:55:08 -0400 User-Agent: KMail/1.6.2 References: <20110719112033.GA51765@omma.gibson.athome> <201107221758.01272.jkim@FreeBSD.org> <20110723082108.GB14172@omma.gibson.athome> In-Reply-To: <20110723082108.GB14172@omma.gibson.athome> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201107251455.11482.jkim@FreeBSD.org> Cc: freebsd-stable@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: powernow regression in 8-STABLE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2011 18:55:30 -0000 On Saturday 23 July 2011 04:21 am, Callum Gibson wrote: > On 22Jul11 17:57, Jung-uk Kim wrote: > }Please try the attached patch. If it doesn't work, I need to see > }"acpidump -dt" output. > > Sorry, no difference. Given jhb's response is there any point > pursuing this further? Seems to be a "known issue" with legacy usb > that perhaps can't be fixed. > > In any case, acpidump output here: > http://members.optusnet.com.au/callumgibson/acpidump.out.gz I agree that the legacy USB issue must be fixed but your BIOS is more broken than I originally thought. powernow expects a static table (via acpi_perf) but _PSS is dynamically constructed at runtime. I don't think we can support this case easily, sorry. Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Mon Jul 25 20:30:33 2011 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37C5D106567A for ; Mon, 25 Jul 2011 20:30:33 +0000 (UTC) (envelope-from callumgibson@optusnet.com.au) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by mx1.freebsd.org (Postfix) with ESMTP id AAFAF8FC16 for ; Mon, 25 Jul 2011 20:30:31 +0000 (UTC) Received: from omma.gibson.athome (c122-106-15-156.rivrw1.nsw.optusnet.com.au [122.106.15.156]) by mail05.syd.optusnet.com.au (8.13.1/8.13.1) with SMTP id p6PKUTNA014653 for ; Tue, 26 Jul 2011 06:30:30 +1000 Received: (qmail 24116 invoked by uid 107); 26 Jul 2011 06:30:29 +1000 Date: 26 Jul 2011 06:30:29 +1000 Date: Tue, 26 Jul 2011 06:30:29 +1000 From: Callum Gibson To: Jung-uk Kim Message-ID: <20110725203029.GA23755@omma.gibson.athome> References: <20110719112033.GA51765@omma.gibson.athome> <201107221758.01272.jkim@FreeBSD.org> <20110723082108.GB14172@omma.gibson.athome> <201107251455.11482.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201107251455.11482.jkim@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: powernow regression in 8-STABLE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2011 20:30:33 -0000 On 25Jul11 14:55, Jung-uk Kim wrote: }I agree that the legacy USB issue must be fixed but your BIOS is more }broken than I originally thought. powernow expects a static table }(via acpi_perf) but _PSS is dynamically constructed at runtime. I }don't think we can support this case easily, sorry. Thanks for looking at it. John's hack is working for now. It would be interesting to see a response from either of you to Jeremy's question/comments. C -- Callum Gibson @ home http://members.optusnet.com.au/callumgibson/ From owner-freebsd-amd64@FreeBSD.ORG Mon Jul 25 21:04:33 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id BB13A106566C; Mon, 25 Jul 2011 21:04:33 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Mon, 25 Jul 2011 17:04:18 -0400 User-Agent: KMail/1.6.2 References: <20110719112033.GA51765@omma.gibson.athome> <20110723081304.GA14172@omma.gibson.athome> <20110723084721.GA7931@icarus.home.lan> In-Reply-To: <20110723084721.GA7931@icarus.home.lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201107251704.20389.jkim@FreeBSD.org> Cc: Attilio Rao , Callum Gibson , freebsd-amd64@freebsd.org, Jeremy Chadwick Subject: Re: powernow regression in 8-STABLE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2011 21:04:33 -0000 On Saturday 23 July 2011 04:47 am, Jeremy Chadwick wrote: > On Sat, Jul 23, 2011 at 06:13:04PM +1000, Callum Gibson wrote: > > On 22Jul11 08:16, John Baldwin wrote: > > }The problem is that we calibrate the TSC using this algorithm: > > } > > } - grab the TSC > > } - spin on the ISA timer waiting for it to run for a second > > } - grab the TSC > > } > > }The issue is that the SMI# fires at the same time we want to be > > execuiting }step 3, and step 3 is deferred while the SMI# handler > > runs. As a result, the }TSC delta ends up being "1 second + time > > of an SMI# to poll USB". We have a }hack fix for this at work > > that originally came from Attilio Rao. This is a }patch for it > > relative to 8. It disables interrupt generation for the ISA > > }timer while we calibrate the TSC (which disables the SMI# > > temporarily): > > > > Thanks, John. The hack works as intended, but I guess it's not a > > "real" solution which is why you haven't committed it? > > This sort of thing is going to have to get dealt with officially > sooner or later, hack-fix or elegant solution either way[1]. > > More and more systems are using native USB keyboards, and most > system BIOSes I've seen (from multiple vendors, specifically > Supermicro, Lenovo, Asus, Dell, HP, and Gigabyte[2]) are defaulting > to having these options enabled (and rightfully so). > > If the hack-fix has repercussions, it would be helpful to know what > those are or how those might manifest themselves. Otherwise, has > anyone taken a look at how Linux addresses this problem? To my > knowledge GRUB and similar bootstraps do not have a native USB > stack, so I'm left wondering how they deal with this. > > [1]: I'm in no way saying "Hey! Fix this! {contributes nothing}", > I'm simply pointing out that we're at a point where we really don't > have much of a choice. The more I read technical explanations from > John the more hate x86 architecture. ;-) > > [2]: On a couple Gigabyte boards I have the default values for said > option is enabled (for both keyboard and mouse). It is really annoying problem and it has to be fixed *properly*. Previously, we dealt with similar SMI# problem per platform, e.g., http://svnweb.freebsd.org/base?view=revision&revision=174557 This quirk table matches 6 platforms now: if (strncmp(sysenv, "MacBook1,1", 10) == 0 || strncmp(sysenv, "MacBook3,1", 10) == 0 || strncmp(sysenv, "MacBookPro1,1", 13) == 0 || strncmp(sysenv, "MacBookPro1,2", 13) == 0 || strncmp(sysenv, "MacBookPro3,1", 13) == 0 || strncmp(sysenv, "Macmini1,1", 10) == 0) { if (bootverbose) printf("Disabling LEGACY_USB_EN bit on " "Intel ICH.\n"); outl(ICH_SMI_EN, inl(ICH_SMI_EN) & ~0x8); } ... We definitely need to generalize it as soon as possible. Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Tue Jul 26 11:15:39 2011 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B279106566B for ; Tue, 26 Jul 2011 11:15:39 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B5C828FC08 for ; Tue, 26 Jul 2011 11:15:38 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA08195; Tue, 26 Jul 2011 13:57:42 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E2E9DA5.8020106@FreeBSD.org> Date: Tue, 26 Jul 2011 13:57:41 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: Jung-uk Kim References: <20110719112033.GA51765@omma.gibson.athome> <201107221758.01272.jkim@FreeBSD.org> <20110723082108.GB14172@omma.gibson.athome> <201107251455.11482.jkim@FreeBSD.org> In-Reply-To: <201107251455.11482.jkim@FreeBSD.org> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 26 Jul 2011 23:00:57 +0000 Cc: Callum Gibson , freebsd-stable@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: powernow regression in 8-STABLE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 11:15:39 -0000 on 25/07/2011 21:55 Jung-uk Kim said the following: > powernow expects a static table > (via acpi_perf) but _PSS is dynamically constructed at runtime. I > don't think we can support this case easily, sorry. Just a side note. Actually I do not see anything wrong with that _PSS except that ASL seems to have been passed through a mangler and it makes reading the code hard. _PSS is a method and it is evaluated as a method in acpi_perf, the method returns a package. I am not sure what exactly you meant when you said that powernow expects a static table. I do not see why the return value can not be dynamically constructed while _PSS is evaluated and why that would affect any of our code. -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 07:04:49 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EC99106566C for ; Wed, 27 Jul 2011 07:04:49 +0000 (UTC) (envelope-from tim.newsham@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 60A0C8FC12 for ; Wed, 27 Jul 2011 07:04:49 +0000 (UTC) Received: by qyk30 with SMTP id 30so2276085qyk.13 for ; Wed, 27 Jul 2011 00:04:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=NE7pjLbFZtBfI2w0KvHSBB8XE3o1YYL1vaItaGfR4VI=; b=n/ge1eauE8IhFQn/FBpDHxrSOhetO7z0h7rWy2PXRm2DLk4GqgeLMYhjObMDoUt6CP 1/mfe4a4grQuNQHtiod9YIm46ID5Un1iO4WSs/wMz4e2j8xLCdkL7zuOvprJXzFXqs1b R49mh//mCQ0+1M15q8JQYbniQvyW1+JUJ9GJs= MIME-Version: 1.0 Received: by 10.229.223.130 with SMTP id ik2mr4886930qcb.282.1311748742392; Tue, 26 Jul 2011 23:39:02 -0700 (PDT) Sender: tim.newsham@gmail.com Received: by 10.229.31.134 with HTTP; Tue, 26 Jul 2011 23:39:02 -0700 (PDT) Date: Tue, 26 Jul 2011 20:39:02 -1000 X-Google-Sender-Auth: lpw_ALIJ0_bwukQtSow6i3rVw1c Message-ID: From: Tim Newsham To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: page fault in kernel X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 07:04:49 -0000 I have an amd64 box that is occasionally panic'ing with a kernel page fault while the system is under heavy load. I tried swapping out ram and running ram tests and that hasn't seem to turn up anything. I originally saw this with 8.1 but I recently updated to 8.2 to be sure and I'm still seeing the problem. I'm up to date with "freebsd-update" and I verified that the core files all match the md5 of a clean 8.2 release (after it is also updated). I also tried to disable various frills I had installed (like ip6 tunnel). The normal way I repro this issue is to start a "portupgrade -caP" going and I usually get a crash within a few hours. Sometimes I see some unusual behavior instead of or right before a crash (ie. program segfaults that shouldn't normally). Are there any known kernel issues that sound similar to this problem? I've been working under the assumption that this is probably hardware related, but I haven't yet ruled out software. I'll probably be trying some tests with cpuburn. Any other advice for tracking down this issue would be appreciated. Tim From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 07:23:56 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id E9ADF106566C for ; Wed, 27 Jul 2011 07:23:56 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-4.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id AF1C6151DFA; Wed, 27 Jul 2011 07:23:56 +0000 (UTC) Message-ID: <4E2FBD0C.1040308@FreeBSD.org> Date: Wed, 27 Jul 2011 00:23:56 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:5.0) Gecko/20110723 Thunderbird/5.0 MIME-Version: 1.0 To: Tim Newsham References: In-Reply-To: X-Enigmail-Version: 1.2pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: page fault in kernel X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 07:23:57 -0000 If you're using the default scheduler it would be an interesting datapoint to switch to 4BSD and see if that helps your situation. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 07:44:06 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5CA41065687 for ; Wed, 27 Jul 2011 07:44:06 +0000 (UTC) (envelope-from tim.newsham@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 966528FC0C for ; Wed, 27 Jul 2011 07:44:06 +0000 (UTC) Received: by qwc9 with SMTP id 9so919671qwc.13 for ; Wed, 27 Jul 2011 00:44:05 -0700 (PDT) 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:content-type :content-transfer-encoding; bh=1ZAVSp9FSE4IfLfGsRnobsJeEouk7xMCgp8FwNzOouA=; b=qyku8JZrAGzOtyFQHbhZWj+Mjmbqa6ksf8gR2c3d8opdSgJr2o96M84RpfgrKTB2L5 NW2OzyuX6fh4jxxXH/DR/RAyzNCFroGwP+yLDsmKSOwzwD7V4vTETgcxAYzk7LnYtHdb l1SFgvETEP0hPTvt9XEgzztDA6F4pgZRu6whU= MIME-Version: 1.0 Received: by 10.229.223.130 with SMTP id ik2mr4923096qcb.282.1311752645837; Wed, 27 Jul 2011 00:44:05 -0700 (PDT) Sender: tim.newsham@gmail.com Received: by 10.229.31.134 with HTTP; Wed, 27 Jul 2011 00:44:05 -0700 (PDT) In-Reply-To: References: Date: Tue, 26 Jul 2011 21:44:05 -1000 X-Google-Sender-Auth: 01XNDXax1C1e4H6ZQyLPB9N9Vk4 Message-ID: From: Tim Newsham To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: page fault in kernel X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 07:44:06 -0000 finally got to the cpuburn. Normal cpu burn for K7 didnt turn anything up, but the burnMMX test which does a heavy memory test actually did.. It wouldnt report errors for memory sizes <=3D 256kb, but >=3D 512kb it would return code 254 after a few seconds (when I ran it twice, once for each core). So.. looks like memory after all (fits the pattern). Using the test I took the same ram and seated it in a different slot and it looks like the problem went away. When I tried adding in the second ram stick I have (each 2G, for a total of 4G) the problem came back, but I didnt diagnose it further to see if it was the ram stick or the memory slot that was to blame (save that for another day). So anyway, going to try a big overnight build to see if that has completely resolved the issue or not. Here's my repro for my original crash: - boot single user - mount -o ro -a - (burnMMX P || echo $?) & - (burnMMX P || echo $?) & - ... wait ... (useful program that burncpu package!). will update tomorow if it fixed the original issue or not... Tim On Tue, Jul 26, 2011 at 8:39 PM, Tim Newsham w= rote: > I have an amd64 box that is occasionally panic'ing with a kernel > page fault while the system is under heavy load. =A0I tried swapping > out ram and running ram tests and that hasn't seem to turn up > anything. =A0I originally saw this with 8.1 but I recently updated to > 8.2 to be sure and I'm still seeing the problem. =A0I'm up to date > with "freebsd-update" and I verified that the core files all match > the md5 of a clean 8.2 release (after it is also updated). =A0I also > tried to disable various frills I had installed (like ip6 tunnel). > > The normal way I repro this issue is to start a "portupgrade -caP" > going and I usually get a crash within a few hours. =A0Sometimes > I see some unusual behavior instead of or right before a crash > (ie. program segfaults that shouldn't normally). > > Are there any known kernel issues that sound similar to this > problem? =A0I've been working under the assumption that this is > probably hardware related, but I haven't yet ruled out software. > > I'll probably be trying some tests with cpuburn. =A0Any other advice > for tracking down this issue would be appreciated. > > Tim > From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 06:30:10 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE49E106564A for ; Wed, 27 Jul 2011 06:30:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BFAF98FC13 for ; Wed, 27 Jul 2011 06:30:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p6R6U8HC090205 for ; Wed, 27 Jul 2011 06:30:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p6R6U8Vk090201; Wed, 27 Jul 2011 06:30:08 GMT (envelope-from gnats) Resent-Date: Wed, 27 Jul 2011 06:30:08 GMT Resent-Message-Id: <201107270630.p6R6U8Vk090201@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, tim newsham Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC09C1065676 for ; Wed, 27 Jul 2011 06:22:12 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 9B9448FC13 for ; Wed, 27 Jul 2011 06:22:12 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p6R6MCO8086775 for ; Wed, 27 Jul 2011 06:22:12 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p6R6MCae086774; Wed, 27 Jul 2011 06:22:12 GMT (envelope-from nobody) Message-Id: <201107270622.p6R6MCae086774@red.freebsd.org> Date: Wed, 27 Jul 2011 06:22:12 GMT From: tim newsham To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Wed, 27 Jul 2011 11:59:08 +0000 Cc: Subject: amd64/159222: unusual behavior writing boot0 from single user mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 06:30:11 -0000 >Number: 159222 >Category: amd64 >Synopsis: unusual behavior writing boot0 from single user mode >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jul 27 06:30:08 UTC 2011 >Closed-Date: >Last-Modified: >Originator: tim newsham >Release: 8.2 >Organization: >Environment: FreeBSD hpsux.x0d99.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: I boot single user, then I run "df" to see which disk is root. Then I run: # fdisk -B -b /boot/boot0 /dev/da0 when its done it says "/boot/boot0: Device not configured" (error varies) and then afterwards most commands I type (like "ls") ellicit: "vnode_pager_getpages: I/O read error" from the kernel. I get the same behavior on my real machine as well as in vmware. The vmware has a clean 8.2 release installed off of DVD (8.2 release disk) and then updated with "freebsd-update". >How-To-Repeat: Install 8.2 release for amd64. Update with freebsd-update (I don't know if this matters). Boot single user. Run "fdisk -B -b /boot/boot0 /dev/da0" (or whatever the root disk drive is). Run "ls" after it completes. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 08:05:29 2011 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CB54106566B for ; Wed, 27 Jul 2011 08:05:29 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF6E8FC14 for ; Wed, 27 Jul 2011 08:05:28 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA27458; Wed, 27 Jul 2011 11:05:26 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Qlz7N-000NU1-PT; Wed, 27 Jul 2011 11:05:25 +0300 Message-ID: <4E2FC6B9.7000803@FreeBSD.org> Date: Wed, 27 Jul 2011 11:05:13 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: Tim Newsham References: In-Reply-To: X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 27 Jul 2011 11:59:20 +0000 Cc: freebsd-amd64@FreeBSD.org Subject: Re: page fault in kernel X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 08:05:29 -0000 on 27/07/2011 09:39 Tim Newsham said the following: > I have an amd64 box that is occasionally panic'ing with a kernel > page fault while the system is under heavy load. My personal philosophy is that it is better to gather objective data before making any speculations: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html > I tried swapping > out ram and running ram tests and that hasn't seem to turn up > anything. I originally saw this with 8.1 but I recently updated to > 8.2 to be sure and I'm still seeing the problem. I'm up to date > with "freebsd-update" and I verified that the core files all match > the md5 of a clean 8.2 release (after it is also updated). I also > tried to disable various frills I had installed (like ip6 tunnel). > > The normal way I repro this issue is to start a "portupgrade -caP" > going and I usually get a crash within a few hours. Sometimes > I see some unusual behavior instead of or right before a crash > (ie. program segfaults that shouldn't normally). > > Are there any known kernel issues that sound similar to this > problem? I've been working under the assumption that this is > probably hardware related, but I haven't yet ruled out software. > > I'll probably be trying some tests with cpuburn. Any other advice > for tracking down this issue would be appreciated. -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 13:31:06 2011 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A7B21065675 for ; Wed, 27 Jul 2011 13:31:06 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 998158FC14 for ; Wed, 27 Jul 2011 13:31:05 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA03999; Wed, 27 Jul 2011 16:31:02 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E301315.1070501@FreeBSD.org> Date: Wed, 27 Jul 2011 16:31:01 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: tim newsham References: <201107270622.p6R6MCae086774@red.freebsd.org> In-Reply-To: <201107270622.p6R6MCae086774@red.freebsd.org> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 27 Jul 2011 13:43:41 +0000 Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/159222: unusual behavior writing boot0 from single user mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 13:31:06 -0000 on 27/07/2011 09:22 tim newsham said the following: >> Number: 159222 >> Category: amd64 >> Synopsis: unusual behavior writing boot0 from single user mode >> Confidential: no >> Severity: serious >> Priority: low >> Responsible: freebsd-amd64 >> State: open >> Quarter: >> Keywords: >> Date-Required: >> Class: sw-bug >> Submitter-Id: current-users >> Arrival-Date: Wed Jul 27 06:30:08 UTC 2011 >> Closed-Date: >> Last-Modified: >> Originator: tim newsham >> Release: 8.2 >> Organization: >> Environment: > FreeBSD hpsux.x0d99.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > >> Description: > I boot single user, then I run "df" to see which disk is root. Then I run: > > # fdisk -B -b /boot/boot0 /dev/da0 > > when its done it says "/boot/boot0: Device not configured" (error varies) > and then afterwards most commands I type (like "ls") ellicit: "vnode_pager_getpages: I/O read error" from the kernel. > > I get the same behavior on my real machine as well as in vmware. The vmware has a clean 8.2 release installed off of DVD (8.2 release disk) and then updated with "freebsd-update". > >> How-To-Repeat: > Install 8.2 release for amd64. > Update with freebsd-update (I don't know if this matters). > Boot single user. > Run "fdisk -B -b /boot/boot0 /dev/da0" (or whatever the root disk drive is). > Run "ls" after it completes. >> Fix: Picking on you at random, nothing personal. Have you verified that this problem is amd64 specific? I do not see anything in your report about trying i386. Why then did you pick amd64 as a category? If you don't know for sure that an issue is specific to some architecture, but the issue seems to be in kernel, then you can use just kern category. I wish that more users actually read this article: http://www.freebsd.org/doc/en/articles/problem-reports/article.html Section 4.4 provides quite clear guidelines on filling out the PR template. Among other things it says: If you are convinced that the problem will *only* [*] occur under the processor architecture you are using, select one of the architecture-specific categories: commonly i386 for Intel-compatible machines in 32-bit mode; amd64 for AMD machines running in 64-bit mode (this also includes Intel-compatible machines running in EMT64 mode); and less commonly arm, ia64, powerpc, and sparc64. [*] - emphasis is mine Maybe we should prominently feature a link to this article in send-pr and in the web interface. -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 16:18:44 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46A5C106564A for ; Wed, 27 Jul 2011 16:18:44 +0000 (UTC) (envelope-from tim.newsham@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id DCD208FC0A for ; Wed, 27 Jul 2011 16:18:43 +0000 (UTC) Received: by qyk30 with SMTP id 30so2629450qyk.13 for ; Wed, 27 Jul 2011 09:18:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=VjKKo8ynjWWW3ZzqHe62WuDrDodinWtedZdfo6O/hD4=; b=e440TDKR1eRIudLjI2kwpcLqaUkQN4HK+4ZKA62lq8V3yCoSJbixG0R2ajLeyn7ev8 5SETH8P+zxouFdYLk+7MfzbJyIJlpixcOceEEDC0OV3qKDRvMBK1cF+tMJQ5tvkKBFKb /y1xsAG0X9gyNcXBzo4pKUWQzTWeXcRz21QF0= MIME-Version: 1.0 Received: by 10.229.223.130 with SMTP id ik2mr169384qcb.282.1311783522373; Wed, 27 Jul 2011 09:18:42 -0700 (PDT) Received: by 10.229.31.134 with HTTP; Wed, 27 Jul 2011 09:18:42 -0700 (PDT) In-Reply-To: <4E301315.1070501@FreeBSD.org> References: <201107270622.p6R6MCae086774@red.freebsd.org> <4E301315.1070501@FreeBSD.org> Date: Wed, 27 Jul 2011 06:18:42 -1000 Message-ID: From: Tim Newsham To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 27 Jul 2011 17:58:59 +0000 Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/159222: unusual behavior writing boot0 from single user mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 16:18:44 -0000 sorry, I did not read the article on filing PRs. I will read it now. I reported amd64 because that is what I run and that is the system I verified it on in a vmware (to isolate the issue from my own system which has other issues I'm working on). FWIW, I think a link to the article on the web PR interface would be a good idea. Tim On Wed, Jul 27, 2011 at 3:31 AM, Andriy Gapon wrote: > on 27/07/2011 09:22 tim newsham said the following: >>> Number: =A0 =A0 =A0 =A0 159222 >>> Category: =A0 =A0 =A0 amd64 >>> Synopsis: =A0 =A0 =A0 unusual behavior writing boot0 from single user m= ode >>> Confidential: =A0 no >>> Severity: =A0 =A0 =A0 serious >>> Priority: =A0 =A0 =A0 low >>> Responsible: =A0 =A0freebsd-amd64 >>> State: =A0 =A0 =A0 =A0 =A0open >>> Quarter: >>> Keywords: >>> Date-Required: >>> Class: =A0 =A0 =A0 =A0 =A0sw-bug >>> Submitter-Id: =A0 current-users >>> Arrival-Date: =A0 Wed Jul 27 06:30:08 UTC 2011 >>> Closed-Date: >>> Last-Modified: >>> Originator: =A0 =A0 tim newsham >>> Release: =A0 =A0 =A0 =A08.2 >>> Organization: >>> Environment: >> FreeBSD hpsux.x0d99.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 0= 2:41:51 UTC 2011 =A0 =A0 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GE= NERIC =A0amd64 >> >>> Description: >> I boot single user, then I run "df" to see which disk is root. =A0Then I= run: >> >> =A0 =A0# fdisk -B -b /boot/boot0 /dev/da0 >> >> when its done it says "/boot/boot0: Device not configured" (error varies= ) >> and then afterwards most commands I type (like "ls") ellicit: "vnode_pag= er_getpages: I/O read error" from the kernel. >> >> I get the same behavior on my real machine as well as in vmware. =A0The = vmware has a clean 8.2 release installed off of DVD (8.2 release disk) and = then updated with "freebsd-update". >> >>> How-To-Repeat: >> Install 8.2 release for amd64. >> Update with freebsd-update (I don't know if this matters). >> Boot single user. >> Run "fdisk -B -b /boot/boot0 /dev/da0" (or whatever the root disk drive = is). >> Run "ls" after it completes. >>> Fix: > > Picking on you at random, nothing personal. > Have you verified that this problem is amd64 specific? > I do not see anything in your report about trying i386. > Why then did you pick amd64 as a category? > If you don't know for sure that an issue is specific to some architecture= , but the > issue seems to be in kernel, then you can use just kern category. > I wish that more users actually read this article: > http://www.freebsd.org/doc/en/articles/problem-reports/article.html > Section 4.4 provides quite clear guidelines on filling out the PR templat= e. > > Among other things it says: > If you are convinced that the problem will *only* [*] occur under the pro= cessor > architecture you are using, select one of the architecture-specific categ= ories: > commonly i386 for Intel-compatible machines in 32-bit mode; amd64 for AMD= machines > running in 64-bit mode (this also includes Intel-compatible machines runn= ing in > EMT64 mode); and less commonly arm, ia64, powerpc, and sparc64. > > [*] - emphasis is mine > > Maybe we should prominently feature a link to this article in send-pr and= in the > web interface. > > -- > Andriy Gapon > --=20 Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 22:44:18 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8093B106566B for ; Wed, 27 Jul 2011 22:44:18 +0000 (UTC) (envelope-from tim.newsham@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3A6058FC1E for ; Wed, 27 Jul 2011 22:44:17 +0000 (UTC) Received: by qwc9 with SMTP id 9so1489599qwc.13 for ; Wed, 27 Jul 2011 15:44:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=yNTDdau+eFWrcphpU8e4Z8vlMQQ0DLT/6t7sVzm+oo0=; b=tmpc9Bpd4NfvUxY5VngfhD1JJnZhge22JhtPJ+b2HBfGMIcxHV3F0H5uQzGREUVGqh 7CgfukQMWgMC5aejgXna7Nqg+be28FKx/2CEx0deQtG2vI/HKUX0yZGViJrNCQrdKe7t 2Vjtad2ss+WxuhT+jn9sQXpQ2FFxZ8DMv/hjc= MIME-Version: 1.0 Received: by 10.229.237.129 with SMTP id ko1mr328149qcb.16.1311806656664; Wed, 27 Jul 2011 15:44:16 -0700 (PDT) Received: by 10.229.31.134 with HTTP; Wed, 27 Jul 2011 15:44:16 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 12:44:16 -1000 Message-ID: From: Tim Newsham To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Wed, 27 Jul 2011 23:03:36 +0000 Subject: Re: page fault in kernel X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 22:44:18 -0000 > So anyway, going to try a big overnight build to see if that has > completely resolved the issue or not. things are looking good so far. Looks like rearranging and reseating the ram addressed the problem. *phew* This is getting a little off topic, but any idea what might be wrong given how burnMMX is failing? Sounds like its at least not the primary cache. The fact that reseating or rearranging the RAM made it work makes me think that its not the secondary either. If it turns out that it happens only in specific RAM slots, then what would it most likely be? I ask because I'm wondering if replacing the CPU module would address the issue completely or if it might be something else on the motherboard. -- Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 23:47:03 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FF201065676; Wed, 27 Jul 2011 23:47:03 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 07DCE8FC14; Wed, 27 Jul 2011 23:47:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p6RNl2m0079874; Wed, 27 Jul 2011 23:47:02 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p6RNl2k1079870; Wed, 27 Jul 2011 23:47:02 GMT (envelope-from linimon) Date: Wed, 27 Jul 2011 23:47:02 GMT Message-Id: <201107272347.p6RNl2k1079870@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/159222: [boot0] unusual behavior writing boot0 from single user mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 23:47:03 -0000 Old Synopsis: unusual behavior writing boot0 from single user mode New Synopsis: [boot0] unusual behavior writing boot0 from single user mode Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Jul 27 23:46:14 UTC 2011 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=159222 From owner-freebsd-amd64@FreeBSD.ORG Thu Jul 28 00:04:14 2011 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7871D1065675 for ; Thu, 28 Jul 2011 00:04:14 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 5B8708FC28 for ; Thu, 28 Jul 2011 00:04:14 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 77B205607A; Wed, 27 Jul 2011 18:46:05 -0500 (CDT) Date: Wed, 27 Jul 2011 18:46:05 -0500 From: Mark Linimon To: Andriy Gapon Message-ID: <20110727234605.GB684@lonesome.com> References: <201107270622.p6R6MCae086774@red.freebsd.org> <4E301315.1070501@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E301315.1070501@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Thu, 28 Jul 2011 01:25:39 +0000 Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/159222: unusual behavior writing boot0 from single user mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jul 2011 00:04:14 -0000 On Wed, Jul 27, 2011 at 04:31:01PM +0300, Andriy Gapon wrote: > Why then did you pick amd64 as a category? IMHO it's not Tim's problem; the categories are just misnamed. One of these months I'm going to get out of ports-land and get back onto the topic of "PR system". In whatever the next PR system is, there will be a "hardware-specific" category or something similarly named. There will not be any of the following: i386; amd64; www :-) (The latter will be "website".) It's not fair to blame our users for the drawbacks of the tool we give them. mcl From owner-freebsd-amd64@FreeBSD.ORG Thu Jul 28 12:48:54 2011 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69EDF1065670 for ; Thu, 28 Jul 2011 12:48:54 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B59BF8FC1A for ; Thu, 28 Jul 2011 12:48:53 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA23229; Thu, 28 Jul 2011 15:48:47 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E315AAF.5060801@FreeBSD.org> Date: Thu, 28 Jul 2011 15:48:47 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: Mark Linimon References: <201107270622.p6R6MCae086774@red.freebsd.org> <4E301315.1070501@FreeBSD.org> <20110727234605.GB684@lonesome.com> In-Reply-To: <20110727234605.GB684@lonesome.com> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 28 Jul 2011 12:54:32 +0000 Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/159222: unusual behavior writing boot0 from single user mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jul 2011 12:48:54 -0000 on 28/07/2011 02:46 Mark Linimon said the following: > On Wed, Jul 27, 2011 at 04:31:01PM +0300, Andriy Gapon wrote: >> Why then did you pick amd64 as a category? > > IMHO it's not Tim's problem; the categories are just misnamed. > > One of these months I'm going to get out of ports-land and get back onto > the topic of "PR system". In whatever the next PR system is, there will > be a "hardware-specific" category or something similarly named. There > will not be any of the following: i386; amd64; www :-) > > (The latter will be "website".) > > It's not fair to blame our users for the drawbacks of the tool we give > them. I actually blamed not users but "us", but it was well disguised :-) I agree with you about amd64 and i386. I think I remember times when amd64 was warranted, when the architecture port was fresh and had genuine amd64-specific bugs and missing features. But now these are an extremely rare kind (comparing to total number of base OS bugs). I further agree with you that making users determine which subsystem is responsible for a bug is not a good approach. So until we have better bug reporting and management tools perhaps we could provide more clues to users in the current tools... Squeezing amd64 and i386 into kern could be done already, I guess. -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Thu Jul 28 16:23:24 2011 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D5ED106564A; Thu, 28 Jul 2011 16:23:24 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 0FEC28FC12; Thu, 28 Jul 2011 16:23:23 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 6B9BB5615B; Thu, 28 Jul 2011 11:23:23 -0500 (CDT) Date: Thu, 28 Jul 2011 11:23:23 -0500 From: Mark Linimon To: Andriy Gapon Message-ID: <20110728162323.GA21799@lonesome.com> References: <201107270622.p6R6MCae086774@red.freebsd.org> <4E301315.1070501@FreeBSD.org> <20110727234605.GB684@lonesome.com> <4E315AAF.5060801@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E315AAF.5060801@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Thu, 28 Jul 2011 19:29:34 +0000 Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/159222: unusual behavior writing boot0 from single user mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jul 2011 16:23:24 -0000 On Thu, Jul 28, 2011 at 03:48:47PM +0300, Andriy Gapon wrote: > Squeezing amd64 and i386 into kern could be done already, I guess. Incoming PRs in those often get magically reassigned by the bugbusting sprites :-) The ones that are left are either "won't boot on this hardware" or "here is a patch that only affects i386-specific code". mcl