Date: Mon, 7 Feb 2005 21:59:57 +0100
From: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
Reply-To: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
Message-ID: <1959057509.20050207215957@dns.toxicfilms.tv>
To: Hans Reiser <reiser@namesys.com>
CC: linux-kernel@vger.kernel.org
Subject: Re[2]: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup
In-Reply-To: <4207CD63.1080802@namesys.com>
References: <1865944987.20050207081532@dns.toxicfilms.tv>
 <4207CD63.1080802@namesys.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1210
Lines: 38

Hello Hans,

Monday, February 7, 2005, 9:19:47 PM, you wrote:

> Maciej Soltysiak wrote:

>>)
>>
>>Feb  6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>>Feb  6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
>>  
>>
> this means bad hard drive, or at least a bad sector on it.
Well, I have reiser4 on this drive with noncritical data which is rather
not used anyway.
But please note that, the process generating the oops (as long as I am
seeing this right) is something called swapper:

scheduling while atomic: swapper/0x00010001/0

My swap partition is not on hdc, it is on hda, which does not report
bad crc and any other dma related errors, or any for that matter.

The same machine runs on 2.6.10-ac10 + reiser-2.6.10 patch well or
at least it does not trigger these oopses.

Only some still not tracked down problems with terrible swap eating :-(
But that's a different story.

Regards,
Maciej


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