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
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 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 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
Hmmm, that comes form the sysmon stuff (sysmon_envsys_events.c).
It would appear that we've queued up some events for the coretemp
sensor, but those events have not been"worked". Events are queued in
sme_events_check() and dequeued by the sme_events_worker() thread.
Have you established alar
On 23 Jun 2015, at 12:01, John D. Baker wrote:
> Last night upon updating my file server from 7.0_BETA to 7.0_RC1 (amd64),
> the message in the Subject: line appeared during the shutdown/reboot
> sequence and the machine was stuck there.
Does it happen on every reboot or did you see it once?
Ba
Last night upon updating my file server from 7.0_BETA to 7.0_RC1 (amd64),
the message in the Subject: line appeared during the shutdown/reboot
sequence and the machine was stuck there. I dropped to DDB and issued
the "reboot" command. While the filesystem on the raidframe RAID (RAID-R)
was unmoun
