> - Using a serial console to the box, you can reliably gather information > without the core dump mechanism working. i caught one, but the rest happened and reboot's beastie wiped the console Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x41959c25 fault code = supervisor write, page not present instruction pointer = 0x8:0xc04e813a stack pointer = 0x10:0xe784d978 frame pointer = 0x10:0xe784d994 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 68301 (sshd) trap number = 12 panic: page fault cpuid = 0 boot() called on cpu#0 Uptime: 9h29m10s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#0 cpu_reset: Stopping other CPUs since then, i installed a kernel with debugging symbols (blush), but have yet to get a usable savecore and the beastie got me too. > - "Random panics" could mean "A lot of seemingly different panics > happening with relatively frequency", or it might mean "A few similar > panics, happening at random intervals". as i can't really characterize the causes, let's just say they seem random to me. i have not reported this stuff, as i had no good data. but since hogan whined, i thought i should sing the harmony. randyReceived on Wed Nov 24 2004 - 20:31:02 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:23 UTC