Date: Wed, 27 Jul 2011 06:18:42 -1000 From: Tim Newsham <tim.newsham@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/159222: unusual behavior writing boot0 from single user mode Message-ID: <CAGSRWbiUFrbgEe2KFA94PJce9wNHZJQ1VKK2fzhMY8MXJkBZmw@mail.gmail.com> In-Reply-To: <4E301315.1070501@FreeBSD.org> References: <201107270622.p6R6MCae086774@red.freebsd.org> <4E301315.1070501@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <avg@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGSRWbiUFrbgEe2KFA94PJce9wNHZJQ1VKK2fzhMY8MXJkBZmw>