From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Re: [sparc64] Strange interaction between 2.6 kernel and 2.5 (and
Date: Thu, 12 Jul 2007 09:11:32 +0000 [thread overview]
Message-ID: <4695F044.6030107@systella.fr> (raw)
In-Reply-To: <46933AE8.1080509@systella.fr>
[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]
BERTRAND Joël wrote:
> David Miller wrote:
>> From: BERTRAND_Joël <joel.bertrand@systella.fr>
>> Date: Wed, 11 Jul 2007 12:24:07 +0200
>>
>>> Root rayleigh:[/etc/mail] > ps -eLf | grep clamd
>>> clamav 3502 1 3502 1 2 10:53 ? 00:01:23
>>> /usr/sbin/clamd
>>> clamav 3502 1 7226 0 2 12:00 ? 00:00:00
>>> /usr/sbin/clamd
>>> root 8091 5893 8091 0 1 12:18 pts/0 00:00:00 grep clamd
>>>
>>> clamd remains in S mode.
>>>
>>> I have tried to obtain mode information with sysrq+w without any
>>> success, sysrq+w returns no blocked task. In this example, clamd is
>>> blocked, but some other tasks can be blocked.
>>
>> This is not enough information to debug this problem, sorry.
>>
>> You'll need to do some thinking about what kind of other information
>> you can fetch from this stuck process. Perhaps running
>> clamd under strace will provide a good debugging trace so we can
>> see exactly what kind of socket it is stuck on, and in what way.
>
> OK. Now, I run clamd under strace. I hope that it will quickly hang
> ;-) When,clamd hangs, I will post here its strace output. Are there
> significative differences between futex management on sbus and pci
> sparc64 ? I have tried to reproduce this bug on sbus workstation without
> any success, but I can see it on all sparc64/PCI I have (U60, U80, U420)...
I'm lucky ;-) First mail in clamd and clamd sleeps... You can find in
attachement complete strace log (strace -ff ...).
Regards,
JKB
[-- Attachment #2: clamav-strace.bz2 --]
[-- Type: application/octet-stream, Size: 277171 bytes --]
next prev parent reply other threads:[~2007-07-12 9:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 7:53 [sparc64] Strange interaction between 2.6 kernel and 2.5 (and 2.6) BERTRAND Joël
2007-07-10 17:49 ` [sparc64] Strange interaction between 2.6 kernel and 2.5 (and David Miller
2007-07-10 18:03 ` BERTRAND Joël
2007-07-10 18:05 ` BERTRAND Joël
2007-07-11 10:24 ` BERTRAND Joël
2007-07-11 18:56 ` BERTRAND Joël
2007-07-11 20:43 ` David Miller
2007-07-12 7:17 ` BERTRAND Joël
2007-07-12 9:11 ` BERTRAND Joël [this message]
2007-07-12 9:38 ` David Miller
2007-07-12 9:46 ` David Miller
2007-07-12 9:50 ` BERTRAND Joël
2007-07-25 6:19 ` David Miller
2007-07-25 6:58 ` BERTRAND Joël
2007-07-25 8:31 ` BERTRAND Joël
2007-07-25 8:33 ` David Miller
2007-07-28 7:59 ` BERTRAND Joël
2007-07-28 8:07 ` David Miller
2007-07-28 8:25 ` BERTRAND Joël
2007-07-30 5:19 ` David Miller
2007-07-30 7:04 ` BERTRAND Joël
2007-07-30 7:07 ` David Miller
2007-07-30 7:48 ` BERTRAND Joël
2007-07-30 8:17 ` David Miller
2007-07-30 9:16 ` gavin duley
2007-07-30 9:22 ` David Miller
2007-07-30 9:45 ` gavin duley
2007-07-31 9:21 ` David Miller
2007-07-31 9:37 ` BERTRAND Joël
2007-07-31 9:42 ` David Miller
2007-07-31 9:52 ` BERTRAND Joël
2007-07-31 9:54 ` David Miller
2007-07-31 10:28 ` [sparc64] Strange interaction between 2.6 kernel and 2.5 (and 2.6) glibc gavin duley
2007-07-31 11:04 ` [sparc64] Strange interaction between 2.6 kernel and 2.5 (and BERTRAND Joël
2007-07-31 20:12 ` David Miller
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=4695F044.6030107@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.