[OmniOS-discuss] OmniOS on Dual CPU Mac Pro

[Eric Bardes]

It appears that it's crashing in the intel_nhm section of the kernel. The
dimm_to_addr function.

I think this is probably the interesting part ...

trap+0xce5(ffffff007acf8790, cc4000000, 3)
intel_nhm`dimm_to_addr+0x43f(0, 2, 0, 82800000, ffffff007acf89f0,
ffffff007acf89e8)

I wonder if it's to something about how Apple distributes the 8 DIMM slots
between the two CPUs.

I want to clarify what I say ZFS file system creation, zpool create tank
<disk>
zpool import -f tank crashes too.

On Mon, Jan 30, 2017 at 5:05 PM, Dan McDonald <danmcd at omniti.com> wrote:

>
> > On Jan 30, 2017, at 4:41 PM, Eric Bardes <ericbardes at gmail.com> wrote:
> >
> > I'm running into an interesting situation.
> >
> > I have an older "Cheese Grater" style Mac Pro (mid-2012 - MacPro5,1)
> with Dual Xeon 6-Core CPUs and 64GB ECC RAM. (24 execution threads) that
> I'm trying to install OmniOS onto. It's been crashing on installation of
> OmniOS (also on OpenIndiana too) and I think I've narrowed it down to the
> ZFS file system creation. Has anyone else run into this? Is there something
> in the kernel debugger I can look at?
>
> So the newer HW panics, but...
>
> > it's sister, a 2010 or 2009 Mac Pro with one Xeon 4 core (8 threads) has
> been running OpenIndiana Hipster flawlessly.
>
> ... the older HW runs without a hitch, huh?
>
> One thing you can do is get to the grub menu, edit the "unix" line to
> include "-k" in its arguments.  You'll drop into kmdb upon panic, and you
> can utter things like:
>
>         $c  (see stack)
>
>         ::msgbuf (scroll through kernel printf backlog, including more
> info on the panic itself).
>
> Hope this helps,
> Dan
>
>


-- 
Eric Bardes

“Love all, trust a few. Do wrong to none” - *All's Well That Ends Well*,
Act 1, Sc 1.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20170130/539865db/attachment.html>