From my experience, only x86 32bit kernel has this problem and 64bit kernel do not have it.
However, atom based system do not have it although it's installed with a 32bit kernel. -----Original Message----- From: Johannes Hirte [mailto:johannes.hi...@fem.tu-ilmenau.de] Sent: Tuesday, March 08, 2011 6:12 AM To: Maria Wikström Cc: Mitch Harder; Chris Mason; Xin Zhong; Zhong, Xin; linux-btrfs Subject: Re: [PATCH] btrfs file write debugging patch On Monday 07 March 2011 20:56:50 Maria Wikström wrote: > mån 2011-03-07 klockan 00:07 -0600 skrev Mitch Harder: > > On Sun, Mar 6, 2011 at 6:58 PM, Chris Mason <chris.ma...@oracle.com> wrote: > > > Excerpts from Chris Mason's message of 2011-03-06 13:00:27 -0500: > > >> Excerpts from Mitch Harder's message of 2011-03-05 11:50:14 -0500: > > >> > I've constructed a test patch that is currently addressing all the > > >> > issues on my system. > > >> > > > >> > The portion of Openmotif that was having issues with page faults > > >> > works correctly with this patch, and gcc-4.4.5 builds without > > >> > issue. > > >> > > > >> > I extracted only the portion of the first patch that corrects the > > >> > handling of dirty_pages when copied==0, and incorporated the second > > >> > patch that falls back to one-page-at-a-time if there are troubles > > >> > with page faults. > > >> > > >> Just to make sure I understand, could you please post the full > > >> combined path that was giving you trouble with gcc? We do need to > > >> make sure the pages are properly up to date if we fall back to > > >> partial writes. > > > > > > Ok, I was able to reproduce this easily with fsx. The problem is that > > > I wasn't making sure the last partial page in the write was up to date > > > when it was also the first page in the write. > > > > > Here is the updated patch, it has all the fixes we've found so far: > > This latest patch that Chris has sent out fixes the issues I've been > > encountering. > > > > I can build gcc-4.4.5 without problems. > > > > Also, the portion of Openmotif that was having issues with page faults > > is working correctly. > > > > Let me know if you still would like to see the path names for the > > portions of the gcc-4.4.5 build that were giving me issues. I didn't > > save that information, but I can regenerate it. But it sounds like > > it's irrelevant now. > > With the patch I can compile libgcrypt without any problem, so it solves > my problems to. Can confirm this. And the bug seems to be hardware-related. On my Pentium4 system it was 100% reproducible, on my Atom-based system I couldn't trigger it. N�����r��y����b�X��ǧv�^�){.n�+����{�n�߲)����w* jg��� �����ݢj/���z�ޖ��2�ޙ����&�)ߡ�a���� �G���h��j:+v���w��٥
