Mike Smith wrote:
On Tue, 13 Jul 1999, Mike Smith wrote:
'siobi' is someone trying to open the serial console, for whatever
reason. Without knowing who it was that was stuck there, it's hard to
guess what is going on.
D'uh, sorry. Long day. It was amd that was hung in the
On Tue, 13 Jul 1999, Mike Smith wrote:
'siobi' is someone trying to open the serial console, for whatever
reason. Without knowing who it was that was stuck there, it's hard to
guess what is going on.
D'uh, sorry. Long day. It was amd that was hung in the siobi
state. No way to
Mike Smith wrote:
On Tue, 13 Jul 1999, Mike Smith wrote:
'siobi' is someone trying to open the serial console, for whatever
reason. Without knowing who it was that was stuck there, it's hard to
guess what is going on.
D'uh, sorry. Long day. It was amd that was hung in the
On Wed, Jul 14, 1999 at 10:56:05PM -0700, Mike Smith wrote:
On Tue, 13 Jul 1999, Mike Smith wrote:
'siobi' is someone trying to open the serial console, for whatever
reason. Without knowing who it was that was stuck there, it's hard to
guess what is going on.
D'uh, sorry.
On Tue, 13 Jul 1999, Mike Smith wrote:
'siobi' is someone trying to open the serial console, for whatever
reason. Without knowing who it was that was stuck there, it's hard to
guess what is going on.
D'uh, sorry. Long day. It was amd that was hung in the siobi
state. No way to
On Tue, 13 Jul 1999, Ladavac Marino wrote:
I don't know if your diagnosis was in jest,
Yes it was, but thank you for asking. :) I should have known
better than to attempt subtle humor at the end of a long, tiring day.
Doug
--
On account of being a democracy and run by the
:
: So I started thinking that maybe the problem was actually in
:syslog (or amd's interface to it). So I disabled the following two options
:in my amd.conf file:
:
:log_file = syslog:local7
:log_options =all
:
: And lo and behold, it worked like a charm. I
After pounding on this some more with today's -current (prior to
the MNT_ASYNC flag change) I got a lot more lockups that looked like
this:
On Mon, 12 Jul 1999, Doug wrote:
Ok, got another hang in "siobi" state (this time after it
successfully completed the script). Here is
On Tue, 13 Jul 1999, Matthew Dillon wrote:
:
: So I started thinking that maybe the problem was actually in
:syslog (or amd's interface to it). So I disabled the following two options
:in my amd.conf file:
:
:log_file = syslog:local7
:log_options =all
:
:
On Tue, 13 Jul 1999, Mike Smith wrote:
After pounding on this some more with today's -current (prior to
the MNT_ASYNC flag change) I got a lot more lockups that looked like
this:
On Mon, 12 Jul 1999, Doug wrote:
Ok, got another hang in "siobi" state (this time after it
On Tue, 13 Jul 1999, Ladavac Marino wrote:
I don't know if your diagnosis was in jest,
Yes it was, but thank you for asking. :) I should have known
better than to attempt subtle humor at the end of a long, tiring day.
Doug
--
On account of being a democracy and run by the
After pounding on this some more with today's -current (prior to
the MNT_ASYNC flag change) I got a lot more lockups that looked like
this:
On Mon, 12 Jul 1999, Doug wrote:
Ok, got another hang in siobi state (this time after it
successfully completed the script). Here is the
On Tue, 13 Jul 1999 13:20:55 MST, Doug wrote:
After confirming that it worked with no logging, I tried enabling
logging to a regular file, and that also worked like a charm. After
turning syslog style logging back on, it locked up cold, with a very
similar traceback.
Sheesh, Mark
:
: So I started thinking that maybe the problem was actually in
:syslog (or amd's interface to it). So I disabled the following two options
:in my amd.conf file:
:
:log_file = syslog:local7
:log_options =all
:
: And lo and behold, it worked like a charm. I was
After pounding on this some more with today's -current (prior to
the MNT_ASYNC flag change) I got a lot more lockups that looked like
this:
On Mon, 12 Jul 1999, Doug wrote:
Ok, got another hang in siobi state (this time after it
successfully completed the script). Here is
On Tue, 13 Jul 1999, Matthew Dillon wrote:
:
: So I started thinking that maybe the problem was actually in
:syslog (or amd's interface to it). So I disabled the following two options
:in my amd.conf file:
:
:log_file = syslog:local7
:log_options =all
:
:
On Tue, 13 Jul 1999, Mike Smith wrote:
After pounding on this some more with today's -current (prior to
the MNT_ASYNC flag change) I got a lot more lockups that looked like
this:
On Mon, 12 Jul 1999, Doug wrote:
Ok, got another hang in siobi state (this time after it
On Tue, 13 Jul 1999, Mike Smith wrote:
After pounding on this some more with today's -current (prior to
the MNT_ASYNC flag change) I got a lot more lockups that looked like
this:
On Mon, 12 Jul 1999, Doug wrote:
Ok, got another hang in siobi state (this time
:*.err;kern.debug;auth.notice;mail.crit /dev/console
:*.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages
:mail.info /var/log/maillog
:lpr.info/var/log/lpd-errs
:cron.*
On Tue, 13 Jul 1999, Mike Smith wrote:
'siobi' is someone trying to open the serial console, for whatever
reason. Without knowing who it was that was stuck there, it's hard to
guess what is going on.
D'uh, sorry. Long day. It was amd that was hung in the siobi
state. No way to clear
On Tue, 13 Jul 1999, Matthew Dillon wrote:
Comment the whole thing out, kill -HUP the syslogd (or kill and restart
it), and see if amd still locks up.
Ok, now I think I get it. You want me to enable syslog'ing in amd,
then do what you're talking about here. I will try this
On Fri, 9 Jul 1999, Doug wrote:
In my continuing efforts to get this freebsd box into shape for
web hosting at my company (where it relies exclusively on NFS for
retrieving customer data) I've been making progress thanks to some recent
commits by Peter. Now I can run the heavy duty NFS
Ok, it's now wedged in a different state (using the same perl
script to wedge it). According to top:
317 root2 0 648K 456K STOP 0 0:00 0.00% 0.00% amd
I also managed to attach to the running process this time:
(gdb) file /usr/sbin/amd
Reading symbols from
On 10 Jul 1999 12:56:41 -0400, R. Matthew Emerson wrote:
I thought that it was almost never proper to soft-mount rw filesytems.
Am I mistaken about this?
I must admit, it sounds like sensible advice. The only NFS exports which
I have to rely on are read-only mounts. The only time I
Ok, got another hang in "siobi" state (this time after it
successfully completed the script). Here is the trace:
(gdb) file /usr/sbin/amd
Reading symbols from /usr/sbin/amd...done.
(gdb) attach 155
Attaching to program: /usr/sbin/amd, process 155
0x8063dc4 in open ()
(gdb) where
#0
On Fri, 9 Jul 1999, Doug wrote:
In my continuing efforts to get this freebsd box into shape for
web hosting at my company (where it relies exclusively on NFS for
retrieving customer data) I've been making progress thanks to some recent
commits by Peter. Now I can run the heavy duty NFS
Ok, it's now wedged in a different state (using the same perl
script to wedge it). According to top:
317 root2 0 648K 456K STOP 0 0:00 0.00% 0.00% amd
I also managed to attach to the running process this time:
(gdb) file /usr/sbin/amd
Reading symbols from
On 10 Jul 1999 12:56:41 -0400, R. Matthew Emerson wrote:
I thought that it was almost never proper to soft-mount rw filesytems.
Am I mistaken about this?
I must admit, it sounds like sensible advice. The only NFS exports which
I have to rely on are read-only mounts. The only time I
Ok, got another hang in siobi state (this time after it
successfully completed the script). Here is the trace:
(gdb) file /usr/sbin/amd
Reading symbols from /usr/sbin/amd...done.
(gdb) attach 155
Attaching to program: /usr/sbin/amd, process 155
0x8063dc4 in open ()
(gdb) where
#0
On Fri, 09 Jul 1999 12:00:52 MST, Doug wrote:
The amd conf files are below, any insights or suggestions welcome.
I can't remember whether it was you or someone else to whom I offered
this advice not so recently, so forgive me if I've suggested this to you
before.
I've found that AMD
Sheldon Hearn [EMAIL PROTECTED] writes:
I've found that AMD exacerbates NFS-related problems. Since I moved away
from AMD toward using proper NFS mounts (soft, interruptible, bg), the
hassles I was having with NFS have gone away completely.
I thought that it was almost never proper to
On Fri, 09 Jul 1999 12:00:52 MST, Doug wrote:
The amd conf files are below, any insights or suggestions welcome.
I can't remember whether it was you or someone else to whom I offered
this advice not so recently, so forgive me if I've suggested this to you
before.
I've found that AMD
Sheldon Hearn sheld...@uunet.co.za writes:
I've found that AMD exacerbates NFS-related problems. Since I moved away
from AMD toward using proper NFS mounts (soft, interruptible, bg), the
hassles I was having with NFS have gone away completely.
I thought that it was almost never proper to
33 matches
Mail list logo
