I'm replying late, but last night I almost had a complete meltdown of the
system.
I did a partial pkg upgrade for the packages that managed to get built by
poudriere, then all hell broke loose. Screen lock-ups, random reboots, and
several hard reboots later I decided to do a fresh
On 29 May 2014, at 23:06, Andreas Nilsson andrn...@gmail.com wrote:
Having a parent set would be nice, yes. I maintain two repos for several
FreeBSD-versions. Being able to pull some of the deps from packages instead
of blindingly building would be nice.
Yes, for a lot of cases you only want
On Thursday, May 29, 2014 5:46:05 pm Adrian Chadd wrote:
On 29 May 2014 14:29, John Baldwin j...@freebsd.org wrote:
On Thursday, May 29, 2014 5:09:05 pm Adrian Chadd wrote:
On 29 May 2014 13:18, John Baldwin j...@freebsd.org wrote:
anyway. Besides all of this - I'm thinking of just
These patches switch hpt27xx(4) from timeout() to callout() and fix it to use
its existing locks in place of Giant for CAM along with some other cleanups.
If anyone has any hardware I suspect the ioctl handling is buggy, but I'm more
hesitant to touch that unless someone has multiple adapters
On 30 May 2014 07:57, John Baldwin j...@freebsd.org wrote:
Ugh. Ok. I was too deep in the trenches of device drivers and other
ancillary things doing bad things to char/short with cpu ids when
walking things. I totally missed kinfo_proc.
I'll go think about it a bit more.
It shouldn't be
John Baldwin j...@freebsd.org wrote:
Yes, I actually started by sorting on the raw delta and ended up going back
and fixing
pctcpu instead. However, there is a problem in this case which is that you
still want to fall back to ki_pctcpu if you don't have a valid previous delta
to compare
On May 28, 2014, at 9:54, John Baldwin j...@freebsd.org wrote:
Yes, I actually started by sorting on the raw delta and ended up going back
and fixing
pctcpu instead. However, there is a problem in this case which is that you
still want to fall back to ki_pctcpu if you don't have a valid
On Thu, Sep 19, 2013 at 03:04:46PM -0400, John Baldwin wrote:
| On Tuesday, September 17, 2013 6:21:10 am Gleb Smirnoff wrote:
|Hi!
|
|When system is writing a kernel core dump, it issues watchdog
| pat wdog_kern_pat(WD_LASTVAL). If ipmi is in action, it registers
| ipmi_wd_event() as
TB --- 2014-05-30 14:40:36 - tinderbox 2.22 running on freebsd-current.sentex.ca
TB --- 2014-05-30 14:40:36 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE
FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
On Fri, May 23, 2014 at 08:35:25PM -0400, Shawn Webb wrote:
On May 23, 2014 07:53 PM +, Wojciech A. Koszek wrote:
On Wed, May 14, 2014 at 09:58:52AM -0400, Shawn Webb wrote:
Hey All,
[NOTE: crossposting between freebsd-current@, freebsd-security@, and
freebsd-stable@. Please
On 5/30/14, 10:44 AM, Doug Ambrisko wrote:
On Thu, Sep 19, 2013 at 03:04:46PM -0400, John Baldwin wrote:
| On Tuesday, September 17, 2013 6:21:10 am Gleb Smirnoff wrote:
|Hi!
|
|When system is writing a kernel core dump, it issues watchdog
| pat wdog_kern_pat(WD_LASTVAL). If ipmi is
Any clue on this ? :(
-Mensagem original-
De: owner-freebsd-curr...@freebsd.org
[mailto:owner-freebsd-curr...@freebsd.org] Em nome de Fred Pedrisa
Enviada em: quinta-feira, 29 de maio de 2014 02:19
Para: 'Adrian Chadd'
Cc: 'freebsd-current'
Assunto: RES: Thread Scheduler Priority
Hello,
On Thu, 2014-05-29 at 02:12 -0300, Fred Pedrisa wrote:
Hi, Guys.
How can I adjust a certain thread to have the maximum system priority in the
scheduler ?
I've tried doing it this way :
/* Set thread priority. */
13 matches
Mail list logo
