Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[2\.6\.32\]\s+scheduling\s+while\s+atomic\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[2\.6\.32\]\s+scheduling\s+while\s+atomic\s*$/: 3 ]

Total 3 documents matching your query.

1. [2.6.32] scheduling while atomic (score: 1): Author: Martin Hamrle <martin.hamrle@xxxxxxxx>; Date: Mon, 1 Nov 2010 16:11:46 +0100; Hi, I have box with xfs on sw raid5. There is permanent high read / write load. After almost month uptime kernel crashed with this traceback. Note that several minutes before there were problems with; /archives/xfs/2010-11/msg00010.html (16,330 bytes)
2. Re: [2.6.32] scheduling while atomic (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 2 Nov 2010 11:12:44 +1100; trimmed the stack so we can read it: BUG: scheduling while atomic: tscpd/22653/0xffff8802 .... Pid: 22653, comm: tscpd Not tainted 2.6.32-bpo.3-amd64 #1 Call Trace: [<ffffffff812ed71e>] ? schedule+0x; /archives/xfs/2010-11/msg00013.html (12,484 bytes)
3. Re: [2.6.32] scheduling while atomic (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 2 Nov 2010 12:02:01 -0400; Even better move on to a recent kernel - we're now preventing the VM from reentering the filesystem for reclaim, which should take care of all practical stack overlfow issues.; /archives/xfs/2010-11/msg00017.html (7,858 bytes)

Current List: 1 - 3
Page: [1]