I've been writing some software which parses `/proc` to get process info.
The original is in Python, but I got some unexpected results and, as I'm
not the best with Python, assumed it was my bad coding. So, I wrote a bit
of C to cross-reference, and I get the same results. I just can't
understand
> > Since pr_size and pr_rssize are size_t's, I'm guessing that they're zero
> > since the number is too big to represent in 32 bits, so the field is
being
> > made 0 instead
Of course!
> Specifically, if it's a 32-bit process, we won't represent 64-bit fields
> in it's proc structure:
>
So simple! Thanks Jonathan and Jorge.
Rob
On 1 May 2018 at 11:49, Jonathan Perkin <jper...@joyent.com> wrote:
> * On 2018-05-01 at 11:43 BST, Robert Fisher wrote:
>
> > I build pkgin (pkgsrc?) packages of certain tools, customized to my own
> > needs. To get them
I build pkgin (pkgsrc?) packages of certain tools, customized to my own
needs. To get them on my hosts I stick them in Manta, and config-management
downloads them and installs them from the local filesystem. This has always
seemed crude and clumsy, but works.
Now I'm looking at deploying my own
No joy with anything ACPI, XHCI or legacy boot. I've tried absolutely
everything in the BIOS, and I can't even make it fail in a different way.
FreeBSD, OpenBSD, Ubuntu, all work great. SmartOS, OmniOS, Solaris, all
lock at the same point.
Anyone got any more ideas?
Rob
> Do you by chance happen to have a Serial header on that system?
Sadly not. I've had to do everything so far with a screen and a USB
keyboard.
I am, of course, happy to do anything that might help fix this issue for
everyone. If there's kmdb digging, test builds to try, or anything else,
I'm
I've given up on the idea of any Illumos flavour ever running on my little
home server, so I'm planning to swap out the main board.
The backstory of this is that I successfully ran Solaris 11 on it
(encrypted ZFS -- I'm paranoid) and when I upgraded the BIOS (I know, never
upgrade the BIOS, but I
Thanks for the advice everyone, but nothing is helping.
Using `use_mp/W 0` makes no difference. It hangs at exactly the same place.
(However, doing this on Solaris 11 allows it to boot. This is the same as
disabling the cores in the BIOS.)
Booting with `-B disable-xhci=true` also changes
> t seems that there were three BIOS updates since your original February
post regarding the motherboard. Perhaps you can take a chance updating to
the latest BIOS?
I already tried that. No difference.
> Or perhaps you can downgrade to a known working one?
That's the real kicker. I can't. You
> Are there any power management options in the bios?
Very few. "ErP Ready" lets you set a sleep state (S4 or S5), and you can
enable or disable power on by PCI-E, Ring or on a timed schedule.
I've tried them all in all possible states but, as you can imagine, none of
them had any effect.
> I do see some options for managing C states.
Yes. Sorry, I was thinking of power at a broader level. I've tried
disabling Speedstep, Turbo and C-states -- they were my first suspects.
Just been through them all again, to double-check. No difference
Rob
11 matches
Mail list logo
