xfs
[Top] [All Lists]

Re: Bug#557262: 2.6.31+2.6.31.4: XFS - All I/O locks up to D-state after

To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>, 557262@xxxxxxxxxxxxxxx
Subject: Re: Bug#557262: 2.6.31+2.6.31.4: XFS - All I/O locks up to D-state after 24-48 hours (sysrq-t+w available) - root cause found = asterisk
From: Faidon Liambotis <paravoid@xxxxxxxxxx>
Date: Sat, 21 Nov 2009 01:44:24 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, submit@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx, asterisk-users@xxxxxxxxxxxxxxxx, Alan Piszcz <ap@xxxxxxxxxxxxx>
In-reply-to: <alpine.DEB.2.00.0911201530500.10757@xxxxxxxxxxxxxxxx>
Organization: Debian
References: <alpine.DEB.2.00.0910171825270.16781@xxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0910181607040.27363@xxxxxxxxxxxxxxxx> <20091019030456.GS9464@xxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0910190431180.23395@xxxxxxxxxxxxxxxx> <20091020003358.GW9464@xxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0910200431290.21878@xxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0910210618210.10288@xxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0911201530500.10757@xxxxxxxxxxxxxxxx>
User-agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707)
Justin Piszcz wrote:
 > Found root cause-- root cause is asterisk PBX software.  I use an
SPA3102.
> When someone called me, they accidentally dropped the connection, I called
> them back in a short period.  It is during this time (and the last time)
> this happened that the box froze under multiple(!) kernels, always when
> someone was calling.
<snip>
> I don't know what asterisk is doing but top did run before the crash
> and asterisk was using 100% CPU and as I noted before all other processes
> were in D-state.
> 
> When this bug occurs, it freezes I/O to all devices and the only way to
> recover
> is to reboot the system.
That's obviously *not* the root cause.

It's not normal for an application that isn't even privileged to hang
all I/O and, subsequently everything on a system.

This is almost probably a kernel issue and asterisk just does something
that triggers this bug.

Regards,
Faidon

<Prev in Thread] Current Thread [Next in Thread>