It seems as though I have a dtrace-triggered panic. If anyone is
interested in more info from my crash dump, let me know.
Details...
As I was looking into a zfs problem (feature?) I was running:
dtrace -n 'fbt:zfs:dsl_dataset_promote:return { trace(arg0); stack() }'
The the OS crashed.
# mdb *.0
Loading modules: [ unix genunix specfs dtrace cpu.generic uppc
scsi_vhci zfs random ip hook neti sctp arp usba fctl md lofs sppp
crypto ptm ipc fcp fcip cpc logindmux sv nsctl sdbc ufs rdc ii nsmb ]
> ::status
debugging crash dump vmcore.0 (32-bit) from indy2
operating system: 5.11 snv_86 (i86pc)
panic message:
BAD TRAP: type=e (#pf Page fault) rp=e0620d38 addr=200 occurred in module "<unkn
own>" due to a NULL pointer dereference
dump content: kernel pages only
> ::stack
0x200(eb1ea000)
zfs_ioc_promote+0x3b()
zfsdev_ioctl+0xd8(2d80000, 5a23, 8045e40, 100003, e8b3a020, e0620f78)
cdev_ioctl+0x2e(2d80000, 5a23, 8045e40, 100003, e8b3a020, e0620f78)
spec_ioctl+0x65(ddfb6c00, 5a23, 8045e40, 100003, e8b3a020, e0620f78)
fop_ioctl+0x49(ddfb6c00, 5a23, 8045e40, 100003, e8b3a020, e0620f78)
ioctl+0x155()
sys_call+0x10c()
>
--
Mike Gerdts
http://mgerdts.blogspot.com/
_______________________________________________
dtrace-discuss mailing list
[email protected]
