[OmniOS-discuss] OmniOS crashed (KVM on AMD)
ashley willis
ashleywillis76 at gmail.com
Sun Sep 15 01:08:51 UTC 2013
$ sudo fmdump -Vp -u 088b57af-949f-42db-8310-c72096a1eef2
TIME UUID SUNW-MSG-ID
Sep 14 2013 22:53:42.030600000 088b57af-949f-42db-8310-c72096a1eef2
SUNOS-8000-KL
TIME CLASS ENA
Sep 14 22:53:41.9252 ireport.os.sunos.panic.dump_available 0x0000000000000000
Sep 14 22:52:48.3950 ireport.os.sunos.panic.dump_pending_on_device
0x0000000000000000
nvlist version: 0
version = 0x0
class = list.suspect
uuid = 088b57af-949f-42db-8310-c72096a1eef2
code = SUNOS-8000-KL
diag-time = 1379199221 957508
de = fmd:///module/software-diagnosis
fault-list-sz = 0x1
fault-list = (array of embedded nvlists)
(start fault-list[0])
nvlist version: 0
version = 0x0
class = defect.sunos.kernel.panic
certainty = 0x64
asru =
sw:///:path=/var/crash/unknown/.088b57af-949f-42db-8310-c72096a1eef2
resource =
sw:///:path=/var/crash/unknown/.088b57af-949f-42db-8310-c72096a1eef2
savecore-succcess = 1
dump-dir = /var/crash/unknown
dump-files = vmdump.0
os-instance-uuid = 088b57af-949f-42db-8310-c72096a1eef2
panicstr = BAD TRAP: type=e (#pf Page fault)
rp=ffffff003e3d58d0 addr=0 occurred in module "genunix" due to a NULL
pointer dereference
panicstack = unix:die+df () | unix:trap+db3 () |
unix:cmntrap+e6 () | genunix:list_remove+1b () | zfs:arc_release+208
() | zfs:dbuf_dirty+4e8 () | zfs:dmu_buf_will_fill+2c () |
zfs:dmu_write_uio_dnode+10a () | zfs:dmu_write_uio_dbuf+54 () |
zfs:zvol_write+15a () | genunix:cdev_write+2d () |
specfs:spec_write+4c9 () | genunix:fop_write+8b () |
genunix:pwrite+194 () | unix:brand_sys_syscall+1f5 () |
crashtime = 1379198197
panic-time = Sat Sep 14 22:36:37 2013 UTC
(end fault-list[0])
fault-status = 0x1
severity = Major
__ttl = 0x1
__tod = 0x5234e8f6 0x1d2eb40
On Sat, Sep 14, 2013 at 7:48 PM, ashley willis <ashleywillis76 at gmail.com> wrote:
> OmniOS crashed. Consumer hardware (AMD FX-8150 with 32GB ram) running
> very beta KVM for AMD. At the time I was importing a 14G MongoDB dump
> via OmniOS onto a CentOS 6.4 VM on same box with a ZoL zpool for
> MongoDB data.
>
> This box has been up since this past Sunday with KVM running, several
> different VMs, and I have imported the MongoDB data this way into
> several other VMs without problems (just not using ZoL before).
>
> I have no idea what kind of debugging info would be useful.
> /var/crash/unknown/vmdump.0 is 2.2G.
>
> pictures of monitor messages here:
> https://plus.google.com/110871972189237957931/posts/BwcyxqgC7t9
>
> -ashley
More information about the OmniOS-discuss
mailing list