From nobody@FreeBSD.ORG  Fri Oct 13 18:07:25 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id D091337B674; Fri, 13 Oct 2000 18:07:25 -0700 (PDT)
Message-Id: <20001014010725.D091337B674@hub.freebsd.org>
Date: Fri, 13 Oct 2000 18:07:25 -0700 (PDT)
From: ahlberg@fairytale.se
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: Kernel panic when trying to access a UDMA100 harddisk
X-Send-Pr-Version: www-1.0

>Number:         21970
>Category:       kern
>Synopsis:       Kernel panic when trying to access a UDMA100 harddisk
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 13 18:10:02 PDT 2000
>Closed-Date:    Wed Oct 25 11:12:56 PDT 2000
>Last-Modified:  Wed Oct 25 11:15:24 PDT 2000
>Originator:     Daniel Ahlberg
>Release:        4.1.1-CURRENT
>Organization:
Fairytale AB
>Environment:
FreeBSD bleh.intranet.fairytale.se 4.1.1-RELEASE FreeBSD 4.1.1-RELEASE #1: Sat Oct 14 02:47:11 CEST 2000     root@bleh.intranet.fairytale.se:/usr/src/sys/compile/GENERIC  i386
>Description:
When trying to mount or fscsk a 15gb partition from a Maxtor 20gb UDMA100 connected to a Promise Ultra 100 card the kernel panics. I have got some values from nm /kernel | grep : c0237f3c T cpu_switch\n c0237f38 T default_halt. The computer is a Pentium 200MMX.
>How-To-Repeat:
It happens everytime I try to mount the partition or try to fsck the partition.
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: johan 
State-Changed-When: Sat Oct 14 07:14:40 PDT 2000 
State-Changed-Why:  
To be able to help you debug this problem we need some 
more information. 

Please see the FAQ (http://www.FreeBSD.org/FAQ/FAQ.html) 
section 'For serious FreeBSD hackers only' 
question 'Making the most of a kernel panic' 
for info how you can help us getting the info we need. 

I also belive the output from a verbose boot will be good 
to have. 
This can be found in /var/run/dmesg.boot after a  
verbose boot. 

Please send the info as a follow-up to this PR 
by sending a mail to  
'freebsd-gnats-submit@FreeBSD.org' 
with the subject of this mail as subject. 

Thanks 
Johan 


http://www.freebsd.org/cgi/query-pr.cgi?pr=21970 
State-Changed-From-To: feedback->closed 
State-Changed-By: johan 
State-Changed-When: Wed Oct 25 11:12:56 PDT 2000 
State-Changed-Why:  
The submitter says: 

From: "Daniel Ahlberg" <ahlberg@fairytale.se> 
To: <johan@FreeBSD.org> 
Subject: Re: kern/21970: Kernel panic when trying to access a UDMA100 harddisk 
Date: Wed, 25 Oct 2000 10:06:29 +0200 

> I also belive the output from a verbose boot will be good 
> to have. 
> This can be found in /var/run/dmesg.boot after a 
> verbose boot. 

I'd wish to cancel this bug, becuse I can't reproduce it. I had to use 
another computer for our fileserver, and the new one is working with the 
UDMA 100 controller. I'm almost sure that it is something wrong with the 
motherboard, the box began to crash after a couple of days uptime. 

Thanks for the quick answer. 




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