kern/107436: Core dumps not working via (mpt) driver using LSI contoller

[Johan]

>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: