From owner-freebsd-current@FreeBSD.ORG  Wed Feb 13 22:55:23 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A8EF116A418
	for <freebsd-current@freebsd.org>; Wed, 13 Feb 2008 22:55:23 +0000 (UTC)
	(envelope-from bbiskebo@Princeton.EDU)
Received: from Princeton.EDU (postoffice03.Princeton.EDU [128.112.131.174])
	by mx1.freebsd.org (Postfix) with ESMTP id 4260B13C4D3
	for <freebsd-current@freebsd.org>; Wed, 13 Feb 2008 22:55:23 +0000 (UTC)
	(envelope-from bbiskebo@Princeton.EDU)
Received: from smtpserver2.Princeton.EDU (smtpserver2.Princeton.EDU
	[128.112.129.148])
	by Princeton.EDU (8.13.8/8.13.8) with ESMTP id m1DMhslc017619;
	Wed, 13 Feb 2008 17:44:00 -0500 (EST)
Received: from [140.180.177.201] (formula.Princeton.EDU [140.180.177.201])
	(authenticated bits=0)
	by smtpserver2.Princeton.EDU (8.12.9/8.12.9) with ESMTP id
	m1DMhcbD003421
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 13 Feb 2008 17:43:48 -0500 (EST)
Message-ID: <47B37298.1020004@princeton.edu>
Date: Wed, 13 Feb 2008 17:43:36 -0500
From: Brian Biskeborn <bbiskebo@Princeton.EDU>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Scott Long <scottl@samsco.org>
References: <47B315C8.3060805@bosco.princeton.edu>
	<47B340DF.1010607@samsco.org>
In-Reply-To: <47B340DF.1010607@samsco.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: hptrr driver panics on 7.0-RC2
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Feb 2008 22:55:23 -0000

Scott Long wrote:
> Brian Biskeborn wrote:
>> Hello all,
>>
>> I've reported this problem to HighPoint, but I'm curious to see 
>> whether anyone else has run into it. I'm using a RocketRaid 2314MS 
>> card on an amd64 system. When I boot the install CD for 7.0-RC2, the 
>> driver panics:
>>
>> hptrr: (null): 180*32=5760 bytes
>> hptrr: (null): 180*288=51840 bytes
>>
>> Fatal trap 12: page fault while in kernel mode
>> cpuid = 0; apic id = 00
>> fault virtual address    = 0x3
>> fault code               = supervisor read data, page not present
>> instruction pointer      = 0x8:0xffffffff80502032
>> stack pointer            = 0x10:0xffffffff80fd0950
>> frame pointer            = 0x10:0xffffffff80822ecf
>> code segment             = base 0x0, limit 0xfffff, type 0x1b
>>                          = DPL 0, pres 1, long 1, def32 0, gran 1
>> processor eflags         = interrupt enabled, resume, IOPL = 0
>> current process          = 0 (swapper)
>> trap number              = 12
>> panic: page fault
>> cpuid = 0
>>
>> This is with no drives connected to the controller. My machine specs:
>> Dell Inspiron 531S
>> Processor: Athlon 64 X2 4000+
>> Motherboard: Asus M2N61-AX (seems to be made specifically for Dell) 
>> with the MCP61 chipset
>>
>> So: has anyone else seen a panic with this or other HighPoint cards? I 
>> know HighPoint provides a binary blob for their driver, but could the 
>> problem be in the wrapper code someplace?
>>
>> I wish I could provide more information, but not being able to install 
>> FreeBSD limits my options there. I had to take a picture of the screen 
>> and type in the panic output by hand :)
>>
> 
> I'll take a look at it.  Since you don't have any drives connected, can 
> you remove the card and then do the install?
> 

Heh, not a bad idea... Is there a way to hard-code the dump device into 
the kernel configuration? This crash happens too early for rc.conf to 
have any effect.

I tried building the kernel with online debugging enabled, but my USB 
keyboard doesn't work after the panic (and the box has no PS/2 ports).

Cheers,
Brian