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