Robert Watson wrote:
> On Sat, 15 Nov 2003, Andy Farkas wrote:
>
> > These messages spew onto my console and into syslogd once every second:
>
> Heh. Sounds like your box is having a really bad day, we'll see if we
> can't get it fixed up over the next couple of weeks as things settle out
> :-).
On Sat, 15 Nov 2003, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Don Lewis <[EMAIL PROTECTED]> writes:
> : I hope the fix isn't too extensive, since I'll probably be typing it in
> : by hand in single user mode ...
>
> You could do what I did: remove the two lines that
In message: <[EMAIL PROTECTED]>
Don Lewis <[EMAIL PROTECTED]> writes:
: I hope the fix isn't too extensive, since I'll probably be typing it in
: by hand in single user mode ...
You could do what I did: remove the two lines that jhb added. You'll
get no more warnings. Sure, the probl
On 15 Nov, Robert Watson wrote:
>
> On Sat, 15 Nov 2003, Andy Farkas wrote:
>
>> These messages spew onto my console and into syslogd once every second:
>
> Heh. Sounds like your box is having a really bad day, we'll see if we
> can't get it fixed up over the next couple of weeks as things sett
On Sat, 15 Nov 2003, Sven Esbjerg wrote:
> On Sat, Nov 15, 2003 at 09:38:37AM -0500, Robert Watson wrote:
> > On Sat, 15 Nov 2003, Andy Farkas wrote:
> > > These messages spew onto my console and into syslogd once every second:
>
> I'm seeing the same on a recently upgraded dual cpu machine.
>
On Sat, Nov 15, 2003 at 09:38:37AM -0500, Robert Watson wrote:
> On Sat, 15 Nov 2003, Andy Farkas wrote:
> > These messages spew onto my console and into syslogd once every second:
I'm seeing the same on a recently upgraded dual cpu machine.
Also when I run the reboot command the errors get mixed
etmsg.cgi?fetch=2157067+0+current/freebsd-current
> >
> > ...
> > Nov 15 16:05:44 hummer kernel: checking stopevent 2 with the following
> > non-sleepable locks held:
> > Nov 15 16:05:44 hummer kernel: exclusive sleep mutex sigacts r = 0
> > (0xc4656aa8) l
f you could drop to DDB and generate a trace for
the event.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
>
> ...
> Nov 15 16:05:44 hummer kernel: checking stopevent 2 with the following
> non-slee
Help!
These messages spew onto my console and into syslogd once every second:
...
Nov 15 16:05:44 hummer kernel: checking stopevent 2 with the following
non-sleepable locks held:
Nov 15 16:05:44 hummer kernel: exclusive sleep mutex sigacts r = 0
(0xc4656aa8) locked @ /hummer/src-current/src
