Pierre-Luc Drouin
2005-Mar-09 02:05 UTC
kernel trap 12 with interrupts disabled, 5.3-stable
I have updated a system from FreeBSD 4.10 to 5.3 (I did a fresh new installation from scatch). At the same time we put a new CPUs in there. The system is now a dual Xenon 3.2 GHZ with hyperthreading. When there's load on the server, it crashes. Here is what I get on the console: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 07 fault virtual address = 0x8 fault code = supervisor write, page not present instruction pointer = 0x8:0xc064973e stack pointer = 0x10:0xe338fc00 frame pointer = 0x10:0xe338fc0c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 1 (init) trap number = 12 panic: page fault cpuid = 3 spin lock sleepq chain held by 0xc22ad320 for > 5 seconds What could be the cause? The system was very stable with FreeBSD 4.10 and only 2 CPUs (1 real and 1 virtual). When I've seen page faults in the past, it was caused by the RAM or the motherboard. Is it almost always the case? Does the fact to add 2 new CPUs is more likely to reveal a RAM problem that was not known before? Thanks
Am Mittwoch, 9. M?rz 2005 03:04 schrieb Pierre-Luc Drouin:> I have updated a system from FreeBSD 4.10 to 5.3 (I did a fresh new > installation from scatch). At the same time we put a new CPUs in there.[...]> What could be the cause?The non-technical answer: FreeBSD 5.4 is in the release cycle with an upcoming 5.4 iso image. There were enormous efforts in improving FreeBSD 5.x, so if you already broke your system take the chance and get the new 5.4 system which probably fixes your problem. Next thing is that you won't see any benefit when enabling hyperthreading. It's strongly depending on the system's kind of load but almost everytime you'll see performance degradation.> The system was very stable with FreeBSD 4.10 and only 2 CPUs (1 real and > 1 virtual). When I've seen page faults in the past, it was caused by the > RAM or the motherboard. Is it almost always the case? Does the fact toMaybe, but first you have to provide more information and make sure it frequently crashes at different points. Keep patience till anyone of the experts answers, in the meantime you can have a look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html for providing more information. -Mano> add 2 new CPUs is more likely to reveal a RAM problem that was not known > before? > > Thanks > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050309/bf817f76/attachment.bin