Messages in this thread | | | Date | Mon, 20 Jun 2005 22:07:34 -0700 | From | "Martin J. Bligh" <> | Subject | 2.6.12-mm1 boot failure on NUMA box. |
| |
OK, after fixing the build failure with Andy's patch here:
http://mbligh.org/abat/apw_pci_assign_unassigned_resources
I get a boot failure on the NUMA-Q box. Full log is here:
http://ftp.kernel.org/pub/linux/kernel/people/mbligh/abat/6184/debug/console.log
But at the end it prints out lots of wierd scheduler stuff, then one more message, then dies:
| migration cost matrix (max_cache_size: 2097152, cpu: 700 MHz): --------------------- [00] [01] [02] [03] [04] [05] [06] [07] [08] [09] [10] [11] [12] [13] [14] [15] [00]: - 12.0(0) 12.0(0) 12.0(0) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [01]: 12.0(0) - 12.0(0) 12.0(0) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [02]: 12.0(0) 12.0(0) - 12.0(0) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [03]: 12.0(0) 12.0(0) 12.0(0) - 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [04]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) - 12.0(0) 12.0(0) 12.0(0) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [05]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 12.0(0) - 12.0(0) 12.0(0) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [06]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 12.0(0) 12.0(0) - 12.0(0) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [07]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 12.0(0) 12.0(0) 12.0(0) - 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [08]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) - 12.0(0) 12.0(0) 12.0(0) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [09]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 12.0(0) - 12.0(0) 12.0(0) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [10]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 12.0(0) 12.0(0) - 12.0(0) 466.0(1) 466.0(1) 466.0(1) 466.0(1) [11]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 12.0(0) 12.0(0) 12.0(0) - 466.0(1) 466.0(1) 466.0(1) 466.0(1) [12]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) - 12.0(0) 12.0(0) 12.0(0) [13]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 12.0(0) - 12.0(0) 12.0(0) [14]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 12.0(0) 12.0(0) - 12.0(0) [15]: 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 466.0(1) 12.0(0) 12.0(0) 12.0(0) - -------------------------------- | cacheflush times [2]: 12.0 (12000000) 466.0 (466000000) | calibration delay: 29 seconds -------------------------------- NET: Registered protocol family 16
I guess I'll try backing out the scheduler patches unless someone else has a brighter idea?
M.
- 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/
| |