On Tue, May 29, 2007 at 07:18:18PM -0700, Peter Williams wrote: > Siddha, Suresh B wrote: > > I can try 32-bit kernel to check. > > Don't bother. I just checked 2.6.22-rc3 and the problem is not present > which means something between rc2 and rc3 has fixed the problem. I hate > it when problems (appear to) fix themselves as it usually means they're > just hiding. > > I didn't see any patches between rc2 and rc3 that were likely to have > fixed this (but doesn't mean there wasn't one). I'm wondering whether I > should do a git bisect to see if I can find where it got fixed? > > Could you see if you can reproduce it on 2.6.22-rc2?
No. Just tried 2.6.22-rc2 64-bit version at runlevel 3 on my remote system at office. 15 attempts didn't show the issue. Sure that nothing changed in your test setup? More experiments tomorrow morning.. thanks, suresh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/