From: Oliver Neukum <oliver@neukum.org>
Organization: NOvell
To: Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: 2.6.25: random stalls on certain hardware - regression?
Date: Wed, 9 Jul 2008 13:37:31 +0200
User-Agent: KMail/1.9.9
Cc: "Linux-kernel" <linux-kernel@vger.kernel.org>
References: <4873E27C.6050504@msgid.tls.msk.ru> <200807091032.14786.oliver@neukum.org> <48748340.1060603@msgid.tls.msk.ru>
In-Reply-To: <48748340.1060603@msgid.tls.msk.ru>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200807091337.32118.oliver@neukum.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1173
Lines: 27

Am Mittwoch 09 Juli 2008 11:22:08 schrieb Michael Tokarev:
> 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

select() but not necessary the first call. I've got a report which seems
to indicate a rogue pointer while building the poll table. You might
strace a test programm and see whether it hangs in select() if it manages
to trigger the lockup.

	Regards
		Oliver
--
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/