Re: Common interface for sensors/health monitoring

On Fri, Aug 21, 2009 at 11:17 PM, Oliver Pinter wrote: > Hello! > > When I good know, no common interface exisit in current freebsd > kernel, but some other sysctl interfece exisit: coretemp, aiboost ... > > ~> sysctl dev.coretemp > dev.coretemp.0.%desc: CPU On-Die Thermal Sensors > dev.coretemp.

Re: kernel panics in in_lltable_lookup (with INVARIANTS)

On Fri, 21 Aug 2009 22:41:34 -0700 Brian Somers wrote: > On Fri, 21 Aug 2009 21:55:03 -0700 Brian Somers wrote: > > On Fri, 21 Aug 2009 17:13:45 -0700 Kip Macy wrote: > > > Try this: > > > > > > Index: sys/net/flowtable.c > > > ===

Re: kernel panics in in_lltable_lookup (with INVARIANTS)

On Fri, 21 Aug 2009 17:13:45 -0700 Kip Macy wrote: > Try this: > > Index: sys/net/flowtable.c > === > --- sys/net/flowtable.c (revision 196382) > +++ sys/net/flowtable.c (working copy) > @@ -688,6 +688,12 @@ > struct

Re: Common interface for sensors/health monitoring

Hello! When I good know, no common interface exisit in current freebsd kernel, but some other sysctl interfece exisit: coretemp, aiboost ... ~> sysctl dev.coretemp dev.coretemp.0.%desc: CPU On-Die Thermal Sensors dev.coretemp.0.%driver: coretemp dev.coretemp.0.%parent: cpu0 dev.coretemp.1.%desc:

Common interface for sensors/health monitoring

Hi, I've been using FreeBSD for years in all my servers, but I'm facing a big problem today. All servers are under monitoring using a couple of applications and scripts. Monitored items for each server especially are CPU/mobo/UPS/HDD temperatures, CPU load, memory use, fans speed, PSU/UPS volt

Re: kernel panics in in_lltable_lookup (with INVARIANTS)

Try this: Index: sys/net/flowtable.c === --- sys/net/flowtable.c (revision 196382) +++ sys/net/flowtable.c (working copy) @@ -688,6 +688,12 @@ struct rtentry *rt = ro->ro_rt; struct ifnet *ifp = rt->rt_

kernel panics in in_lltable_lookup (with INVARIANTS)

Hi, I've been working on a fix to address an issue that came up with our update of openssh-5. The issue is that openssh-5 now uses pipe() to create stdin/stdout channels between sshd and the server side program where it used to use socketpair(). Because it uses pipe(), stdin is no longer bi-dire

DTrace lockup on a dual processor VMWare

Hi, I am running a amd64 FreeBSD 7.2 inside a VMWare, and DTrace has been working great. However, I have just changed my VMWare to use two processors instead of one, and things have started to break. I can load the dtraceall module but when I run hotkernel the machine hangs. I have DDB compiled int

Re: DTrace probes & klds

Quoting Daniel O'Connor (from Thu, 20 Aug 2009 17:13:07 +0930): On Thu, 20 Aug 2009, Alexander Leidinger wrote: Quoting Daniel O'Connor (from Wed, 19 Aug 2009 23:31:33 +0930): > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: quoted-printable > Content-Dispositio