[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Disk Hangs with 2.4.18 and ext3
- From: "Stephen C. Tweedie" <sct redhat com>
- To: Kevin Fenzi <kevin tummy com>
- Cc: "Stephen C. Tweedie" <sct redhat com>, ext3-users redhat com
- Subject: Re: Disk Hangs with 2.4.18 and ext3
- Date: Mon, 5 Aug 2002 16:45:59 +0100
Hi,
On Wed, Jul 31, 2002 at 01:47:17PM -0600, Kevin Fenzi wrote:
> Stephen> When debugging a hang like that, you have the problem that a
> Stephen> hang in one place can cause other parts of the kernel to lock
> Stephen> up too. If the disk locks up, then anything waiting for a
> Stephen> disk IO to complete will wait forever, for example.
>
> yeah... :(
>
> Stephen> ...there are signs of the raid driver being blocked.
>
> Is this indicitive of a hardware problem with the RAID controller? or
> something else? We did do quite a bit of heavy disk activity on this
> machine during burnin.
It's impossible to say at this point.
> Stephen> However, it would be useful to see the whole call trace,
> Stephen> because this particular entry looks as if the
> Stephen> DAC960_ProcessRequest entry is simply the result of a recent
> Stephen> interrupt, and we're not actually in that call path at the
> Stephen> moment (the DAC960 address has simply been left behind on the
> Stephen> stack so is picked up by the trace output.)
>
> ok. Where would I be able to get that?
> I do have the complete sysrq output of process traces...
That would be useful, yes.
Cheers,
Stephen
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]