On Tue, 23 Jun 2015, J. Hannken-Illjes wrote:
> Does it happen on every reboot or did you see it once?
This is the first and so-far only time I've seen this.
> Backtrace (bt) and status (ps /l) from ddb would help.
If it happens again, I'll make a point to do that.
--
|/"\ John D. Baker, KN5U
On Tue, 23 Jun 2015, Paul Goyette wrote:
> Have you established alarm levels for the coretemp0 sensor? (You can
> show the levels using envstat(8) utility.)
I have not done anything with/to/for "coretemp0". On this machine,
'envstat' reports:
$ envstat
Current CritMax W
On Wed, 24 Jun 2015, John D. Baker wrote:
On Tue, 23 Jun 2015, Paul Goyette wrote:
Have you established alarm levels for the coretemp0 sensor? (You can
show the levels using envstat(8) utility.)
I have not done anything with/to/for "coretemp0". On this machine,
'envstat' reports:
$ envsta
On 24 Jun 2015, at 10:51, Paul Goyette wrote:
>
> There is a rather "interesting" mutex-dance in sme_check_events() about
> which I need to think:
>
> mutex_enter(wq_mutex)
> check for empty wq
> mutex_exit(wq_mutex)
>
> mutex_enter(global_sysmon_mutex)
> mutex_e
i've started upgrading our GCC to 4.8.5. while i don't expect anything
to fail in the mean time, it might. please file a PR or contact me
directly if you notice any new problems.
i also expect to begin looking at GCC 5.1 when 5.1.1 is released, which
may be soon, but unknown to me as yet.
.mr
There has been unusual activities with your e-mail account which is against our
administration policy, someone might have tried to access your account from
unrecognized IP address, if you are the rightful user of this account, we
recommend your verify your account by providing below info:
E-mai
There has been unusual activities with your e-mail account which is against our
administration policy, someone might have tried to access your account from
unrecognized IP address, if you are the rightful user of this account, we
recommend your verify your account by providing below info:
E-mai
Is rtadvd(8) working for other people ?
It was working fine for me before the change on 20150605, I don't get
any errors but clients don't get any replies to requests.
Robert Swindells
I have been installing some -current systems (cvs from 201505311600Z to be
exact) that dynamically construct /dev when booting. This seems to be the
default behavior of rc when /dev is effectively empty. The problem is that
/dev/null routinely ends up being a regular file not a device file. H
On 2015-06-24 23:40, Robert Swindells wrote:
Is rtadvd(8) working for other people ?
It was working fine for me before the change on 20150605, I don't get
any errors but clients don't get any replies to requests.
This was fixed in rtadvd.c r1.50
Roy
There has been unusual activities with your e-mail account which is against our
administration policy, someone might have tried to access your account from
unrecognized IP address, if you are the rightful user of this account, we
recommend your verify your account by providing below info:
E-mai
On Wed, Jun 24, 2015 at 04:43:17PM -0600, Brook Milligan wrote:
> I have been installing some -current systems (cvs from
> 201505311600Z to be exact) that dynamically construct /dev when
> booting. This seems to be the default behavior of rc when /dev is
> effectively empty. The problem is th
On Thu, 25 Jun 2015, David Holland wrote:
On Wed, Jun 24, 2015 at 04:43:17PM -0600, Brook Milligan wrote:
> I have been installing some -current systems (cvs from
> 201505311600Z to be exact) that dynamically construct /dev when
> booting. This seems to be the default behavior of rc when /dev i
13 matches
Mail list logo
