From root@lumiere.net  Sat Nov 18 15:01:37 2000
Return-Path: <root@lumiere.net>
Received: from leaf.lumiere.net (leaf.lumiere.net [208.44.192.100])
	by hub.freebsd.org (Postfix) with ESMTP id 832B537B479
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 18 Nov 2000 15:01:37 -0800 (PST)
Received: by leaf.lumiere.net (Postfix, from userid 0)
	id 64067CCE4; Sat, 18 Nov 2000 09:07:15 -0800 (PST)
Message-Id: <20001118170715.64067CCE4@leaf.lumiere.net>
Date: Sat, 18 Nov 2000 09:07:15 -0800 (PST)
From: j@lumiere.net
Sender: root@lumiere.net
Reply-To: j@lumiere.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: failed drive causes panic with HPT370 RAID
X-Send-Pr-Version: 3.2

>Number:         22951
>Category:       kern
>Synopsis:       failed drive causes panic with HPT370 RAID
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov 18 15:10:00 PST 2000
>Closed-Date:    Sun Jun 02 03:47:46 PDT 2002
>Last-Modified:  Sun Jun 02 03:47:46 PDT 2002
>Originator:     Jesse Shrieve
>Release:        FreeBSD 4.2-RC1 i386
>Organization:
>Environment:

	
Abit KT7-RAID motherboard with HPT370 RAID chipset. Two identical model
IDE drives, each on a seperate IDE channel. Using a slightly modified
ata-raid.c to compensate for the HPT370's need to store RAID data in block
9(10?). That modification is the adding of "if (buf1->drive)" before
"buf1->bp.b_pblkno += rdp->offset;"


>Description:

	
The system kernel panics approximately 2 minutes after a drive in the
array fails/disappears. Expected behavior would be for it to keep
attempting to access the drive for a while, then give up on it and
continue running off the remaining drives in the array.

Panic messages:
Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x68
fault code              = supervisor read page not present
instruction pointer     = 0x8:0xc0166e2c
stack pointer           = 0x10:0xc02810d4
frame pointer           = 0x10:0xc0281104
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = Idle
interrupt mask          = bio
trap number             = 12
panic: page fault
                        
syncing disks...

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x30
fault code              = supervisor read page not present
instruction pointer     = 0x8:0xc0202b74
stack pointer           = 0x10:0xc0280f04
frame pointer           = 0x10:0xc0280f08
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = Idle
interrupt mask          = bio 
trap number             = 12 
panic: page fault

>How-To-Repeat:
	
Install a 4.2-RC1 system onto an ar* RAID 1 array using the HPT370 chipset
(found on the Abit KT7-RAID motherboard). Disconnect power to one of
drives. System will panic within about 2 minutes.

>Fix:
	


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: iedowse 
State-Changed-When: Sat Nov 17 17:15:40 PST 2001 
State-Changed-Why:  

Does this problem still occur with more recent releases? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22951 
State-Changed-From-To: feedback->closed 
State-Changed-By: iedowse 
State-Changed-When: Sun Jun 2 03:47:25 PDT 2002 
State-Changed-Why:  

Feedback timeout. 

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