From nobody@FreeBSD.org  Mon Mar 15 07:37:44 2010
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 4B94C106566B
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 15 Mar 2010 07:37:44 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 3A9988FC1B
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 15 Mar 2010 07:37:44 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o2F7biNH033465
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 15 Mar 2010 07:37:44 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id o2F7bhhL033464;
	Mon, 15 Mar 2010 07:37:43 GMT
	(envelope-from nobody)
Message-Id: <201003150737.o2F7bhhL033464@www.freebsd.org>
Date: Mon, 15 Mar 2010 07:37:43 GMT
From: Timothy Yen <yen.timothy@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Transferring files on samba causes the kernel to crash
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         144756
>Category:       amd64
>Synopsis:       [panic] Transferring files on samba causes the kernel to crash
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-amd64
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 15 07:40:04 UTC 2010
>Closed-Date:    Mon Oct 25 18:11:15 UTC 2010
>Last-Modified:  Mon Oct 25 18:11:15 UTC 2010
>Originator:     Timothy Yen
>Release:        8.0
>Organization:
>Environment:
FreeBSD tyen-server. 8.0=RELEASE FreeBSD :0: Sat Nov 21 15:02:08 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
I am transferring a large amount of media files to my RAIDZ of 3x2TB disks through Samba. After about 10-15 minutes I get this error 

msk0 watchdog timeout



Another time I got this error while using grep on the machine

Fatal trap 9: general protection fault while in kernel mode
cpuid = 1; apic id = 01
instruction pointer     = 0x20:0xffffffff80e36d54
stack pointer           = 0x28:0xffffff8079ae6700
frame pointer           = 0x28:0xffffff8079ae6710
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def 32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 1290 (grep)
trap number             = 9
panic: general protection fault
cpuid = 1
Uptime = 28m33s
Cannot dump. Device not defined or unavailable.
Automatic reboot in 15 seconds - press a key on the console to abort



Another time I got this error when I wasn't typing on my server.

panic: kmem_malloc(131072): kmem_map too small: 1346445312 total allocated
cpuid = 0
Uptime: 24m20s
Physical memory: 4066 MB
Dumping 2825 MB: 2810 2794 278 2762
>How-To-Repeat:
My hardware is Asus P5Q-E, 2x2GB PC800, Geforce 8800 GTS 640MB, 2x250 GB in RAID 1 ZFS, 3x2TB in RAIDZ. Transfer a large amount of files (approx 50 MB/s) in Samba to the RAIDZ. I've tried both LAN ports on my motherboard, and they give this error.
>Fix:
No idea.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: jh 
State-Changed-When: Tue Sep 21 18:36:58 UTC 2010 
State-Changed-Why:  
Please provide at least backtrace for the first panic. 

kmem_map too small panic is duplicate of kern/130133. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=144756 
State-Changed-From-To: feedback->closed 
State-Changed-By: jh 
State-Changed-When: Mon Oct 25 18:11:14 UTC 2010 
State-Changed-Why:  
Feedback timeout. 

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