![]() | ||||||||||
Messages in this thread |
Well, that's the thing - I _didn't_ switch cpus. Sometimes the error is cpu 0, sometimes it is cpu 1. On Thu, 26 Dec 2002, Joseph D. Wagner wrote: > > usually it says proc #1 in the error, but > > the first time it said proc #0 - is that > > interesting ? > > proc 0 and proc 1 are CPU 0 and CPU 1, respectively. If you switched CPU's > and now the error is on the other proc, then it IS a CPU error. > > Joseph Wagner > > P.S. In hindsight, I probably should have read the entire thread before > responding. 8-) You live you learn. > > Joseph Wagner > > - > 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/ > - 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/ | |||||||||
| Last update: 2005-03-22 11:31 [W:0.171 / U:0.040 seconds] ©2003-2008 Jasper Spaans | ||||||||||