Random reboots with 1.2.3-Release

  • hi all

    i've had random reboots on and off for a while. sometimes it stays up for weeks, then may be up and down every day for a little while. i haven't seen any sort of pattern to it and most of the time i don't realize it has done it until some time later.

    today i noticed it go down so when it came back up i grabbed the log, the relevant part is here:

    Jun 29 22:43:04 	kernel: cpu_reset: Stopping other CPUs
    Jun 29 22:43:04 	kernel: Rebooting...
    Jun 29 22:43:04 	kernel: Automatic reboot in 15 seconds - press a key on the console to abort
    Jun 29 22:43:04 	kernel: Cannot dump. No dump device defined.
    Jun 29 22:43:04 	kernel: Uptime: 1d3h51m10s
    Jun 29 22:43:04 	kernel: cpuid = 2
    Jun 29 22:43:04 	kernel: panic: page fault
    Jun 29 22:43:04 	kernel: trap number = 12
    Jun 29 22:43:04 	kernel: current process = 17 (swi1: net)
    Jun 29 22:43:04 	kernel: processor eflags = interrupt enabled, resume, IOPL = 0
    Jun 29 22:43:04 	kernel: = DPL 0, pres 1, def32 1, gran 1
    Jun 29 22:43:04 	kernel: code segment = base 0x0, limit 0xfffff, type 0x1b
    Jun 29 22:43:04 	kernel: frame pointer = 0x28:0xc53e4a58
    Jun 29 22:43:04 	kernel: stack pointer = 0x28:0xc53e4a30
    Jun 29 22:43:04 	kernel: instruction pointer = 0x20:0xc0a6ca2b
    Jun 29 22:43:04 	kernel: fault code = supervisor write, page not present
    Jun 29 22:43:04 	kernel: fault virtual address = 0x1
    Jun 29 22:43:04 	kernel: cpuid = 2; apic id = 02
    Jun 29 22:43:04 	kernel: Fatal trap 12: page fault while in kernel mode
    Jun 29 22:43:04 	kernel:
    Jun 29 22:43:04 	kernel:
    Jun 29 22:43:04 	syslogd: kernel boot file is /boot/kernel/kernel

    sorry just noticed it's in reverse order.

    this is 1.2.3-Release, and the packages squid and countryblock. i have tried to google the messages, but the causes seem to vary so much for everyone with similar errors. if anyone can help i'd appreciate it, i'm not sure where to go next.

    thanks in advance

    edit: hardware is in my sig

  • when this happens to me its normally the cpu, this is the culprit most of the time, disable ht or any other options such as power settings, or motherboard issue (rarely)

  • I had this happen some time ago on a box that was running fine for a year, then random reboots sometimes days later. In my case it was the memory stick. I did a mem test and the ram failed…popped in a new stick and has been running fine for over 2 years now.

  • My vote is for bad RAM.

  • thanks for the suggestions,

    the RAM passes memtest86, but if i exhaust all other options i will replace it anyway and see what happens

    XIII - -i disabled as much as possible on the motherboard when i first set it up, it doesn't appear to have options regarding ACPI other than which S-state to wake from. i disabled hyper threading (that is what you meant by 'ht right?) and the only thing left to disable after that was USB, which i have done.

    thanks again everyone for the help so far. as i said it may be weeks before it randomly goes down again so i'll just have to keep an eye on it.

  • yes ht = hyper threading, I found out that on some builds it works others dont want it (it rebooted one day and started acting up, ht disabled and was perfect)
    might also be a bad install

  • Rebel Alliance Developer Netgate

    Two things the others haven't mentioned, but can easily cause this: Heat, and power issues.

    Check that all fans are spinning at their full (or configured) speed, and that temperatures are within normal limits.

  • Jimp has a good point.
    But dont limit yourself to just look for failing fans but also for buildup of dust.
    (You know the kind of dust that builds up over years, is almost hard like a rock and you have to scratch it off)
    I've seen that happen to a friend. Cleaning the heatsink helped and the random reboots went away.

  • The computer is clean, theres no dust in the computer, I will check the temps and psu as well.

  • my temps look fine too, and inside is pretty clean, i only built the thing less than 6 months ago.

Log in to reply