From: Nick Piggin <piggin@cyberone.com.au>
To: Linus Torvalds <torvalds@osdl.org>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Gene Heskett <gene.heskett@verizon.net>,
linux-kernel@vger.kernel.org
Subject: Re: amanda vs 2.6
Date: Thu, 27 Nov 2003 19:41:22 +1100 [thread overview]
Message-ID: <3FC5B8B2.7000702@cyberone.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0311261202050.1524@home.osdl.org>
Linus Torvalds wrote:
>
>On Wed, 26 Nov 2003, William Lee Irwin III wrote:
>
>
>>On Wed, Nov 26, 2003 at 02:43:43PM -0500, Gene Heskett wrote:
>>
>>>No, it just hangs forever on the su command, never coming back.
>>>everything else I tried, which wasn't much, seemed to keep on working
>>>as I sent that message with that hung su process in another shell on
>>>another window. I'm an idiot, normally running as root...
>>>I've rebooted, not knowing if an echo 0 to that variable would fix it
>>>or not, I see after the reboot the default value is 0 now.
>>>
>>Okay, then we need to figure out what the hung process was doing.
>>Can you find its pid and check /proc/$PID/wchan?
>>
>
>I've seen this before, and I'll bet you 5c (yeah, I'm cheap) that it's
>trying to log to syslogd.
>
>And syslogd is stopped for some reason - either a bug, a mistaken SIGSTOP,
>or simply because the console has been stopped with a simple ^S.
>
>That won't stop "su" working immediately - programs can still log to
>syslogd until the logging socket buffer fills up. Which can be _damn_
>frsutrating to find (I haven't seen this behaviour lately, but I remember
>being perplexed like hell a long time ago).
>
Same problem here. Been seeing them now and again for quite a while
I have syslogd and klogd sleeping in do_syslog. cron and login are
sleeping in schedule_timeout. A sysrq+T gets things going again but
unfortunately the interesting state probably wasn't captured. I have
the /proc/*/wchan and sysrq+t trace if anyone is interested.
I'll try any suggestions of what I should look at when I hit it again.
Nick
next prev parent reply other threads:[~2003-11-27 8:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 17:12 amanda vs 2.6 Gene Heskett
2003-11-26 17:19 ` William Lee Irwin III
2003-11-26 19:15 ` Gene Heskett
2003-11-26 19:30 ` William Lee Irwin III
2003-11-26 19:43 ` Gene Heskett
2003-11-26 19:50 ` William Lee Irwin III
2003-11-26 20:04 ` Linus Torvalds
2003-11-26 20:07 ` William Lee Irwin III
2003-11-26 20:41 ` Gene Heskett
2003-11-26 20:40 ` Gene Heskett
2003-11-26 20:56 ` Chris Adams
2003-11-26 21:34 ` Diego Calleja García
2003-11-27 8:41 ` Nick Piggin [this message]
2003-11-27 10:05 ` Gene Heskett
2003-11-27 13:39 ` William Lee Irwin III
2003-11-27 17:16 ` Gene Heskett
2003-11-27 17:55 ` Gene Heskett
2003-11-27 18:04 ` Gene Heskett
2003-11-29 17:14 ` Gene Heskett
2003-12-01 18:43 ` Mike Fedyk
2003-12-02 2:41 ` Gene Heskett
2003-12-07 11:56 ` Paul P Komkoff Jr
2003-12-07 13:53 ` Gene Heskett
2003-11-26 20:23 ` Gene Heskett
2003-11-26 20:32 ` William Lee Irwin III
2003-11-26 20:47 ` Gene Heskett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FC5B8B2.7000702@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=wli@holomorphy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).