Re: test12pre6: BUG in schedule (sched.c, 115)

2000-12-06 Thread Ragnar Hojland Espinosa
On Wed, Dec 06, 2000 at 02:00:12PM -0800, Mike Kravetz wrote: > Ragnar, > > Are you sure that was line 115? Could it have been line 515? Yes, yes, it was 515. 115 is the result of human cache corruption ;) > Also, do you have any Oops data? It just froze there. -- /| Ragnar Højland

Re: test12pre6: BUG in schedule (sched.c, 115)

2000-12-06 Thread Petr Vandrovec
On 6 Dec 00 at 14:00, Mike Kravetz wrote: > > Are you sure that was line 115? Could it have been line 515? > Also, do you have any Oops data? > Yesterday BUG in schedule at 515 happened for me with test12-pre4. As there were no data, and it was followed by NMI detected lockup on CPU24 ... (

Re: test12pre6: BUG in schedule (sched.c, 115)

2000-12-06 Thread Mike Kravetz
Ragnar, Are you sure that was line 115? Could it have been line 515? Also, do you have any Oops data? Thanks, -- Mike Kravetz [EMAIL PROTECTED] IBM Linux Technology Center 15450 SW Koll Parkway Beaverton, OR 97006-6063 (503)578-3494 On Wed,