From owner-freebsd-bugs@FreeBSD.ORG Tue Jan 2 17:50:16 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2831D16A40F for ; Tue, 2 Jan 2007 17:50:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id EB26F13C467 for ; Tue, 2 Jan 2007 17:50:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l02HoFgE043123 for ; Tue, 2 Jan 2007 17:50:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l02HoF33043122; Tue, 2 Jan 2007 17:50:15 GMT (envelope-from gnats) Resent-Date: Tue, 2 Jan 2007 17:50:15 GMT Resent-Message-Id: <200701021750.l02HoF33043122@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Johan Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED77A16A403 for ; Tue, 2 Jan 2007 17:45:15 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id DDBEA13C442 for ; Tue, 2 Jan 2007 17:45:15 +0000 (UTC) (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 l02HjAKJ041821 for ; Tue, 2 Jan 2007 17:45:10 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l02HjA6N041820; Tue, 2 Jan 2007 17:45:10 GMT (envelope-from nobody) Message-Id: <200701021745.l02HjA6N041820@www.freebsd.org> Date: Tue, 2 Jan 2007 17:45:10 GMT From: Johan To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: kern/107436: Core dumps not working via (mpt) driver using LSI contoller X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jan 2007 17:50:16 -0000 >Number: 107436 >Category: kern >Synopsis: Core dumps not working via (mpt) driver using LSI contoller >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 02 17:50:15 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Johan >Release: FreeBSD-7-Current >Organization: Nokia Networks >Environment: # uname -a FreeBSD 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Mon May 14 19:29:31 UTC 2001 root@:/usr/src/sys/i386/compile/GENERIC i386 # >Description: Note: Even though uname -a gives May 14, I also updated the src/sys/cam code and src/dev/mpt code to the latest, and it still does not work. I had to update it to have support for the newer LSI-1064 Anyway, 1 SATA drive connected to PHY 0 of the LSI contoller. Boots fine and works well , but when core dumps of kernel it does not work. jump into debugger by typing: sysctl -w debug.kdb.panic=1 You will now be in the debugger. Go ahead and type "panic" Core dump should now be generated on the swap partition, however, it does not work. This is kind of serious since no debug information will be available when the kernel panic's. >How-To-Repeat: --------------- snip -------------------- # sysctl -w debug.kdb.panic=1 debug.kdb.panic: 0panic: kdb_sysctl_panic cpuid = 0 KDB: enter: panic [thread pid 3438 tid 100053 ] Stopped at kdb_enter+0x2b: nop db> panic cpuid = 0 Uptime: 21h29m12s Physical memory: 501 MB Dumping 75 MB:Aborting dump due to I/O error. status == 0x58, scsi status == 0x0 ** DUMP FAILED (ERROR 5) ** Automatic reboot in 15 seconds - press a key on the console to abort --------------- snip -------------------- >Fix: Unknown. The problem can either be in the CAM layer or the (mpt) driver. If core dumping works with a different card which uses a different driver, then it's a problem with the (mpt) driver, else it's the CAM layer. >Release-Note: >Audit-Trail: >Unformatted: