From nobody@FreeBSD.org  Tue Nov 29 02:35:09 2011
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 15617106566B
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 29 Nov 2011 02:35:09 +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 DECC68FC0A
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 29 Nov 2011 02:35:08 +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 pAT2Z8KJ079056
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 29 Nov 2011 02:35:08 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.4/8.14.4/Submit) id pAT2Z8Px079055;
	Tue, 29 Nov 2011 02:35:08 GMT
	(envelope-from nobody)
Message-Id: <201111290235.pAT2Z8Px079055@red.freebsd.org>
Date: Tue, 29 Nov 2011 02:35:08 GMT
From: Kevin Ar18 <kevinar18@hotmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: fails boot and destabilizes other OSes on FreeBSD 9 RC2 with MSI P6N SLI Platinum
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         162936
>Category:       amd64
>Synopsis:       fails boot and destabilizes other OSes on FreeBSD 9 RC2 with MSI P6N SLI Platinum
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 29 02:40:07 UTC 2011
>Closed-Date:    
>Last-Modified:  Thu Dec  1 21:40:09 UTC 2011
>Originator:     Kevin Ar18
>Release:        FreeBSD 9 RC2
>Organization:
>Environment:
* MSI P6N SLI Plantium (nForce 650i northbridge)(nForce 430i southbridge)
* Intel Q6600
* USB Memory
* 1x IDE drive
* 1x SATA drive
>Description:
Summary:
--------
Using the "FreeBSD-8.2-RELEASE-amd64-memstick.img"

* System refuses to complete boot
* No hard drives show up in GEOM / rootmount prompt
* Bluescreens Windows after reboot; must cut power
* After powerdown, networking (internet) does not work in Windows right away ... takes some time to start working again.

Details:
1. Tried the "FreeBSD-8.2-RELEASE-amd64-memstick.img" on both a memory stick and an IDE hard drive (the results are the same).
2. On boot, gives several errors:
usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored)
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
ignored)
Root mount waiting for: usbus1
Root mount waiting for: usbus1
Root mount waiting for: usbus1
Root mount waiting for: usbus1
Root mount waiting for: usbus1
Root mount waiting for: usbus1
(Since I don't have log, I copied from this source: http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063196.html)

3. Eventually it ends up at rootmount> prompt
4. If I type "?", no GEOM devices show up.  Guess it can't detect any drives... USB, IDE, or SATA.
5. After reboot, and trying to boot Windows I get a bluescreen stop error.  Must cut power to regain control.
6. After second reboot, in Windows, networking is offline and takes some time to get working (several seconds).  This might not be OS related; it could be my router resetting from the power.


Also tried:
hints.acpi.0.disabled = "1"
Result: the boot process did not get very far.  It said something about not detecting a timer and panicking.  I think I also noticed it couldn't detect some cores/cpus.

hints.apic.0.disabled = "a"
Result: the boot didn't get far. Page fault.


Related items:
This bug report has a lot of similarities: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/118842
Note the problems with not detecting drives, and the same nForce 650i chipset.

This bug report also has similar similarities:
http://www.freebsd.org/cgi/query-pr.cgi?pr=121305&cat=kern
Problems detecting drives and the same motherboard and chipset.

This report also may have some relevance:
http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063196.html
I see some of the same errors (as noted earlier).
>How-To-Repeat:

>Fix:
If you need more exact log info, you may need to tell me how I can save/log it properly.

>Release-Note:
>Audit-Trail:

From: John Baldwin <jhb@freebsd.org>
To: freebsd-amd64@freebsd.org
Cc: Kevin Ar18 <kevinar18@hotmail.com>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: amd64/162936: fails boot and destabilizes other OSes on FreeBSD 9 RC2 with MSI P6N SLI Platinum
Date: Wed, 30 Nov 2011 08:20:14 -0500

 On Monday, November 28, 2011 9:35:08 pm Kevin Ar18 wrote:
 > >Synopsis:       fails boot and destabilizes other OSes on FreeBSD 9 RC2 
 with MSI P6N SLI Platinum
 > ...
 > >Release:        FreeBSD 9 RC2
 > >Organization:
 > >Environment:
 > * MSI P6N SLI Plantium (nForce 650i northbridge)(nForce 430i southbridge)
 > * Intel Q6600
 > * USB Memory
 > * 1x IDE drive
 > * 1x SATA drive
 > >Description:
 > Summary:
 > --------
 > Using the "FreeBSD-8.2-RELEASE-amd64-memstick.img"
 
 Hm, here you say 8.2, bit your title says 9?
 
 On a whim, if this is 9, can you try setting 'debug.acpi.disabled=hostres' 
 from the loader prompt?
 
 -- 
 John Baldwin

From: Kevin Ar18 <kevinar18@hotmail.com>
To: <bug-followup@freebsd.org>
Cc:  
Subject: Re: amd64/162936: fails boot and destabilizes other OSes on FreeBSD
 9 RC2 with MSI P6N SLI Platinum
Date: Thu, 1 Dec 2011 16:21:35 -0500

 --_0600fe61-70c3-404c-ad1f-31ed7b4a30c0_
 Content-Type: text/plain; charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 
 Apologees=2C it is definitely 9 RC2.  I just copied the wrong name.
 
 I was using this one for most tests: ftp://ftp.freebsd.org/pub/FreeBSD/rele=
 ases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC2-amd64-memstick.img
 
 I also tried a nightly build (built with LLVM+Clang) that someone else made=
 :
 http://forums.freebsd.org/showthread.php?p=3D156243
 It was the "freebsd-head-clang.amd64-r228148.img"  It also did not work... =
 although I got the db (debugger?)
 
 
 ...
 Tried debug.acpi.disabled=3D"hostres" by adding that line to /boot/boot.con=
 f and /boot/loader.conf
 Also=2C on boot=2C I escaped to the loader and typed in: set debug.acpi.dis=
 abled=3Dhostres and debug.acpi.disabled=3Dhostres
 (Is one of those right?)
 Anyways=2C same errors.  Including failed boot=2C no devices listed in GEOM=
 =2C and Windows blue screen.
 I looked through the file system to see if it made any logs=3B no logs were=
  made=2C so can't paste any info from that.
 
 
 ------------
 Also=2C I should note=2C that DragonFlyBSD boots and detects just fine.  He=
 re's a piece of the log that might be relevant from DragonFly:
 ohci0.pci0.pcib0.acpi0.nexus0.root0
 ohci0: <OHCI (generic) USB controller> [tentative] mem 0xf9fff000-0xf9fffff=
 f irq 5 at device 11.0 on pci0
 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xf9fff000
 usb0: OHCI version 1.0=2C legacy support
 usb0.ohci0.pci0.pcib0.acpi0.nexus0.root0
 usb0: <OHCI (generic) USB controller> [tentative] on ohci0
 usb0: USB revision 1.0
 uhub0.usb0.ohci0.pci0.pcib0.acpi0.nexus0.root0
 uhub0: <nVidia OHCI root hub=2C class 9/0=2C rev 1.00/1.00=2C addr 1> [tent=
 ative] on usb0
 uhub0: 8 ports with 8 removable=2C self powered
 uhub0: <nVidia OHCI root hub=2C class 9/0=2C rev 1.00/1.00=2C addr 1> [atta=
 ched!] on usb0
 usb0: <OHCI (generic) USB controller> [attached!] on ohci0
 ohci0: <OHCI (generic) USB controller> [attached!] mem 0xf9fff000-0xf9fffff=
 f irq 5 at device 11.0 on pci0
 ehci0.pci0.pcib0.acpi0.nexus0.root0
 ehci0: <EHCI (generic) USB 2.0 controller> [tentative] mem 0xf9ffec00-0xf9f=
 fecff irq 10 at device 11.1 on pci0
 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xf9ffec00
 usb1: waiting for BIOS to give up control
 usb1: EHCI version 1.0
 usb1: companion controller=2C 8 ports each: usb0
 usb1.ehci0.pci0.pcib0.acpi0.nexus0.root0
 usb1: <EHCI (generic) USB 2.0 controller> [tentative] on ehci0
 usb1: USB revision 2.0
 uhub1.usb1.ehci0.pci0.pcib0.acpi0.nexus0.root0
 uhub1: <nVidia EHCI root hub=2C class 9/0=2C rev 2.00/1.00=2C addr 1> [tent=
 ative] on usb1
 uhub1: 8 ports with 8 removable=2C self powered
 uhub1: <nVidia EHCI root hub=2C class 9/0=2C rev 2.00/1.00=2C addr 1> [atta=
 ched!] on usb1
 umass0.uhub1.usb1.ehci0.pci0.pcib0.acpi0.nexus0.root0
 umass0: <PNY Technologies USB 2.0 FD=2C class 0/0=2C rev 2.00/11.00=2C addr=
  2> [tentative] on uhub1
 umass0:2:0:-1: Attached to scbus2
 umass0: <PNY Technologies USB 2.0 FD=2C class 0/0=2C rev 2.00/11.00=2C addr=
  2> [attached!] on uhub1
 usb1: <EHCI (generic) USB 2.0 controller> [attached!] on ehci0
 ehci0: <EHCI (generic) USB 2.0 controller> [attached!] mem 0xf9ffec00-0xf9f=
 fecff irq 10 at device 11.1 on pci0
 atapci0.pci0.pcib0.acpi0.nexus0.root0
 atapci0: <nVidia nForce MCP51 UDMA133 controller> [tentative] port 0xffa0-0=
 xffaf=2C0x376=2C0x170-0x177=2C0x3f6=2C0x1f0-0x1f7 at device 13.0 on pci0
 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0
 
 
 I think it is in this same area that FreeBSD comes up with all kinds of err=
 ors like:
 usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT=2C ignored)
 usbd_req_re_enumerate: addr=3D2=2C set address failed! (USB_ERR_TIMEOUT=2C
 ignored)
 
 I also noticed FreeBSD does not detect the exact controller model in some l=
 ines=2C but just a generic "nvidia"
 
 Other details:
 FreeBSD will bluescreen Windows even if I run another os first.  For exampl=
 e (1) Try to boot FreeBSD=3B it fails (2) Run DragonFlyBSD (3) Run Windows =
 and get a blue screen from the failed FreeBSD boot.
  		 	   		  =
 
 --_0600fe61-70c3-404c-ad1f-31ed7b4a30c0_
 Content-Type: text/html; charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 <html>
 <head>
 <style><!--
 .hmmessage P
 {
 margin:0px=3B
 padding:0px
 }
 body.hmmessage
 {
 font-size: 10pt=3B
 font-family:Tahoma
 }
 --></style>
 </head>
 <body class=3D'hmmessage'><div dir=3D'ltr'>
 Apologees=2C it is definitely 9 RC2.&nbsp=3B I just copied the wrong name.<=
 br><br>I was using this one for most tests: ftp://ftp.freebsd.org/pub/FreeB=
 SD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC2-amd64-memstick.img<b=
 r><br>I also tried a nightly build (built with LLVM+Clang) that someone els=
 e made:<br>http://forums.freebsd.org/showthread.php?p=3D156243<br>It was th=
 e "freebsd-head-clang.amd64-r228148.img"&nbsp=3B It also did not work... al=
 though I got the db (debugger?)<br><br><br>...<br>Tried debug.acpi.disabled=
 =3D"hostres" by adding that line to /boot/boot.conf and /boot/loader.conf<b=
 r>Also=2C on boot=2C I escaped to the loader and typed in: set debug.acpi.d=
 isabled=3Dhostres and debug.acpi.disabled=3Dhostres<br>(Is one of those rig=
 ht?)<br>Anyways=2C same errors.&nbsp=3B Including failed boot=2C no devices=
  listed in GEOM=2C and Windows blue screen.<br>I looked through the file sy=
 stem to see if it made any logs=3B no logs were made=2C so can't paste any =
 info from that.<br><br><br>------------<br>Also=2C I should note=2C that Dr=
 agonFlyBSD boots and detects just fine.&nbsp=3B Here's a piece of the log t=
 hat might be relevant from DragonFly:<br>ohci0.pci0.pcib0.acpi0.nexus0.root=
 0<br>ohci0: &lt=3BOHCI (generic) USB controller&gt=3B [tentative] mem 0xf9f=
 ff000-0xf9ffffff irq 5 at device 11.0 on pci0<br>ohci0: Reserved 0x1000 byt=
 es for rid 0x10 type 3 at 0xf9fff000<br>usb0: OHCI version 1.0=2C legacy su=
 pport<br>usb0.ohci0.pci0.pcib0.acpi0.nexus0.root0<br>usb0: &lt=3BOHCI (gene=
 ric) USB controller&gt=3B [tentative] on ohci0<br>usb0: USB revision 1.0<br=
 >uhub0.usb0.ohci0.pci0.pcib0.acpi0.nexus0.root0<br>uhub0: &lt=3BnVidia OHCI=
  root hub=2C class 9/0=2C rev 1.00/1.00=2C addr 1&gt=3B [tentative] on usb0=
 <br>uhub0: 8 ports with 8 removable=2C self powered<br>uhub0: &lt=3BnVidia =
 OHCI root hub=2C class 9/0=2C rev 1.00/1.00=2C addr 1&gt=3B [attached!] on =
 usb0<br>usb0: &lt=3BOHCI (generic) USB controller&gt=3B [attached!] on ohci=
 0<br>ohci0: &lt=3BOHCI (generic) USB controller&gt=3B [attached!] mem 0xf9f=
 ff000-0xf9ffffff irq 5 at device 11.0 on pci0<br>ehci0.pci0.pcib0.acpi0.nex=
 us0.root0<br>ehci0: &lt=3BEHCI (generic) USB 2.0 controller&gt=3B [tentativ=
 e] mem 0xf9ffec00-0xf9ffecff irq 10 at device 11.1 on pci0<br>ehci0: Reserv=
 ed 0x100 bytes for rid 0x10 type 3 at 0xf9ffec00<br>usb1: waiting for BIOS =
 to give up control<br>usb1: EHCI version 1.0<br>usb1: companion controller=
 =2C 8 ports each: usb0<br>usb1.ehci0.pci0.pcib0.acpi0.nexus0.root0<br>usb1:=
  &lt=3BEHCI (generic) USB 2.0 controller&gt=3B [tentative] on ehci0<br>usb1=
 : USB revision 2.0<br>uhub1.usb1.ehci0.pci0.pcib0.acpi0.nexus0.root0<br>uhu=
 b1: &lt=3BnVidia EHCI root hub=2C class 9/0=2C rev 2.00/1.00=2C addr 1&gt=
 =3B [tentative] on usb1<br>uhub1: 8 ports with 8 removable=2C self powered<=
 br>uhub1: &lt=3BnVidia EHCI root hub=2C class 9/0=2C rev 2.00/1.00=2C addr =
 1&gt=3B [attached!] on usb1<br>umass0.uhub1.usb1.ehci0.pci0.pcib0.acpi0.nex=
 us0.root0<br>umass0: &lt=3BPNY Technologies USB 2.0 FD=2C class 0/0=2C rev =
 2.00/11.00=2C addr 2&gt=3B [tentative] on uhub1<br>umass0:2:0:-1: Attached =
 to scbus2<br>umass0: &lt=3BPNY Technologies USB 2.0 FD=2C class 0/0=2C rev =
 2.00/11.00=2C addr 2&gt=3B [attached!] on uhub1<br>usb1: &lt=3BEHCI (generi=
 c) USB 2.0 controller&gt=3B [attached!] on ehci0<br>ehci0: &lt=3BEHCI (gene=
 ric) USB 2.0 controller&gt=3B [attached!] mem 0xf9ffec00-0xf9ffecff irq 10 =
 at device 11.1 on pci0<br>atapci0.pci0.pcib0.acpi0.nexus0.root0<br>atapci0:=
  &lt=3BnVidia nForce MCP51 UDMA133 controller&gt=3B [tentative] port 0xffa0=
 -0xffaf=2C0x376=2C0x170-0x177=2C0x3f6=2C0x1f0-0x1f7 at device 13.0 on pci0<=
 br>atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0<br><br><br>I =
 think it is in this same area that FreeBSD comes up with all kinds of error=
 s like:<br>usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT=2C ignor=
 ed)<br>usbd_req_re_enumerate: addr=3D2=2C set address failed! (USB_ERR_TIME=
 OUT=2C<br>ignored)<br><br>I also noticed FreeBSD does not detect the exact =
 controller model in some lines=2C but just a generic "nvidia"<br><br>Other =
 details:<br>FreeBSD will bluescreen Windows even if I run another os first.=
 &nbsp=3B For example (1) Try to boot FreeBSD=3B it fails (2) Run DragonFlyB=
 SD (3) Run Windows and get a blue screen from the failed FreeBSD boot.<br> =
 		 	   		  </div></body>
 </html>=
 
 --_0600fe61-70c3-404c-ad1f-31ed7b4a30c0_--
>Unformatted:
