From nobody@FreeBSD.org  Fri Aug  5 02:20:49 2005
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1FA7B16A41F
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  5 Aug 2005 02:20:49 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DFF0843D46
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  5 Aug 2005 02:20:48 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j752Kmwj004145
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 5 Aug 2005 02:20:48 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id j752Kmtv004142;
	Fri, 5 Aug 2005 02:20:48 GMT
	(envelope-from nobody)
Message-Id: <200508050220.j752Kmtv004142@www.freebsd.org>
Date: Fri, 5 Aug 2005 02:20:48 GMT
From: Ryan Rogers <freebsd@epicoftimewasted.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Sysinstall ata related panic under 6.0-BETAx
X-Send-Pr-Version: www-2.3

>Number:         84568
>Category:       kern
>Synopsis:       [ata] Sysinstall ata related panic under 6.0-BETAx
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    sos
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 05 02:30:15 GMT 2005
>Closed-Date:    Wed Jan 04 22:00:16 GMT 2006
>Last-Modified:  Wed Jan 04 22:00:16 GMT 2006
>Originator:     Ryan Rogers
>Release:        6.0-BETA2
>Organization:
>Environment:
FreeBSD  6.0-BETA2 FreeBSD 6.0-BETA2 #0: Wed Aug  3 08:22:24 UTC 2005     root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
Sysinstall, when executed by the 6.0-BETA2 disc1 .iso, panics during the
commit phase of installation with one of the two following messages (the
former being the most common):

Panic: vm_fault: fault on nofault entry, addr: deadc000
cpuid = 0
KDB: enter: panic
[thread pid 27 tid 100025 ]
Stopped at      kdb_enter+0x2b: nop
db> trace
Tracing pid 27 tid 100025 td 0xc272d480
kdb_enter(c0856274) at kdb_enter+0x2b
panic(c0870f1a,deadc000,1,0,e53e7ae4) at panic+0x127
vm_fault(c1460000,deadc000,1,0,c272d480) at vm_fault+0x1e0
trap_pfault(e53e7bf8,0,deadc0f2) at trap_pfault+0x137
trap(8,28,28,c2cdd640,c29e8080) at trap+0x341
calltrap() at calltrap+0x5
--- trap 0xc, eip = 0xc0645656, esp = 0xe53e7c38, ebp = 0xe53e7c38 ---
devclass_get_name(deadc0de) at devclass_get_name+0x6
device_get_name(c29e8080) at device_get_name+0x18
device_print_prettyname(c29e8080,c2a1a400,e53e7c8c,c04d4c04,c29e8080) at device_print_prettyname+0xe
device_printf(c29e8080,c082b538,c082babf) at device_printf+0xc
ata_completed(c2cdd640,0) at ata_completed+0xec
ata_finish(c2cdd640) at ata_finish+030
ata_timeout(c2cdd640) at ata_timeout+0x8e
softclock(0) at softclock+0x1e7
ithread_loop(c2722980,e53e7d38,c2722980,c061f854,0) at ithread_loop+0x11c
fork_exit(c061f854,c2722980,e53e7d38) at fork_exit+0xa0
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xe53e7d6c, ebp = 0 ---


Panic: vm_fault: fault on nofault entry, addr: dee11000
cpuid = 0
KDB: enter: panic
[thread pid 25 tid 100008 ]
Stopped at      kdb_enter+0x2b: nop
db> trace
Tracing pid 25 tid 100008 td 0xc26d6300
kdb_enter(c0856274) at kdb_enter+0x2b
panic(c0870f1a,dee11000,ee9898c0,257,0) at panic+0x127
vm_fault(c1460000,dee11000,2,0,c26d6300) at vm_fault+0x1e0
trap_pfault(e3970c44,0,dee11800) at trap_pfault+0x137
trap(8,28,28,dee11800,c283d000) at trap+0x341
calltrap() at calltrap+0x5
--- trap 0xc, eip = 0xc04d2cea, esp = 0xe3970c84, ebp = 0xe3970ca4 ---
ata_pio_read(c32fbaf0,800,129,c2898700,c28d9400) at ata_pio_read+0xca
ata_end_transaction(c32fbaf0) at ata_end_transaction+0x8b8
ata_interrupt(c283d000) at ata_interrupt+0xdf
ithread_loop(c2722a80,e3970d38,c2722a80,c061f854,0) at ithread_loop+0x11c
fork_exit(c061f854,c2722a80,e3970d38) at fork_exit+0xa0
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xe3970d6c, ebp = 0 ---


The hardware:
Motherboard: Asus A7N8X Deluxe
CPU: Athlon XP 2500+
Memory: Corsair XMS PC-2700
Storage: 2x Samsung SP0812C SATA drives, connected to the motherboard's onboard 'SiI 3112 SATA150 controller'

The panic only occurs with both drives connected.  Drives have been tested
clean with Samsung's HUTIL program.  Panic existed in 6.0-BETA1, but not
in 5.4-RELEASE.
>How-To-Repeat:
Boot the 6.0-BETA? .iso and try to perform an install with both hard drives
connected.
>Fix:
None that I've found
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->sos 
Responsible-Changed-By: glebius 
Responsible-Changed-When: Wed Aug 24 12:24:23 GMT 2005 
Responsible-Changed-Why:  
It looks like the problem, that Soren has already fixed in HEAD. 
Pass this PR to him. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=84568 
State-Changed-From-To: open->closed 
State-Changed-By: sos 
State-Changed-When: Wed Jan 4 21:56:20 UTC 2006 
State-Changed-Why:  
I belive that sii3112 support is as good as it can get given that the chip 
is haunted with silicon problems. 
However, success depends on motherboard/BIOS/phase of the moon combinations, 
there is no way to garantie that it will or even can work. 
I recommend getting a real SATA controller.. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=84568 
>Unformatted:
