Message-ID: <48748340.1060603@msgid.tls.msk.ru>
Date: Wed, 09 Jul 2008 13:22:08 +0400
From: Michael Tokarev <mjt@tls.msk.ru>
Organization: Telecom Service, JSC
User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509)
MIME-Version: 1.0
To: Oliver Neukum <oliver@neukum.org>
CC: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25: random stalls on certain hardware - regression?
References: <4873E27C.6050504@msgid.tls.msk.ru> <200807091032.14786.oliver@neukum.org>
In-Reply-To: <200807091032.14786.oliver@neukum.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 950
Lines: 24

Oliver Neukum wrote:
> Am Dienstag 08 Juli 2008 23:56:12 schrieb Michael Tokarev:
> 
>> Any idea how to start welcome.  Meanwhile I'll try current 2.6.26pre,
>> in a hope it will not destroy all our data.. ;)
> 
> Can you test whether select() triggers the lockup?

Hmm.  Sure I can, and it definitely uses select() here and there -
samba & Oracle8 & cronyd & vtund & syslogd - that's services
running on it all using select(2).  Can you elaborate a bit
more on this please?  I mean, should it lock up on first select()
(so that it's not what I see here) or on some random one (still
may be the situation I see), or not so-random which is more-or-less
possible to trigger?

Thank you for the reply!

/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/