9.0 spontaneously reboots
Volodymyr Kostyrko
c.kworr at gmail.com
Mon Mar 12 14:07:31 UTC 2012
Hi all.
I have one machine behaving unstable. This happened before 9.0. After
upgrading to 9.0 machine was given a light load and now it reboots.
Memory was already tested (without any errors) and changed after another
reboot.
I just have one snippet in the logs:
Mar 12 07:51:56 beeb kernel: interrupt total
Mar 12 07:51:56 beeb kernel: irq18: ehci0 uhci5+ 325
Mar 12 07:51:56 beeb kernel: irq19: uhci2 uhci4 4350
Mar 12 07:51:56 beeb kernel: irq23: ehci1 uhci3 272776
Mar 12 07:51:56 beeb kernel: cpu0:timer 306304013
Mar 12 07:51:56 beeb kernel: irq256: mpt0 106758743
Mar 12 07:51:56 beeb kernel: cpu1:timer 50588836
Mar 12 07:51:56 beeb kernel: cpu14:timer 40862828
Mar 12 07:51:56 beeb kernel: cpu12:timer 66660057
Mar 12 07:51:56 beeb kernel: cpu6:timer 51650325
Mar 12 07:51:56 beeb kernel: cpu13:timer 35826328
Mar 12 07:51:56 beeb kernel: cpu3:timer 47414874
Mar 12 07:51:56 beeb kernel: cpu10:timer 101158759
Mar 12 07:51:56 beeb kernel: cpu2:timer 116817563
Mar 12 07:51:56 beeb kernel: cpu8:timer 137051223
Mar 12 07:51:56 beeb kernel: cpu7:timer 31732225
Mar 12 07:51:56 beeb kernel: cpu11:timer 43244351
Mar 12 07:51:56 beeb kernel: cpu4:timer 83143936
Mar 12 07:51:56 beeb kernel: cpu9:timer 49622770
Mar 12 07:51:56 beeb kernel: cpu5:timer 40662969
Mar 12 07:51:56 beeb kernel: cpu15:timer 27434472
Mar 12 07:51:56 beeb kernel: irq257: igb0:que 0 20058599
Mar 12 07:51:56 beeb kernel: irq258: igb0:que 1 15054525
Mar 12 07:51:56 beeb kernel: irq259: igb0:que 2 14738762
Mar 12 07:51:56 beeb kernel: irq260: igb0:que 3 14702046
Mar 12 07:51:56 beeb kernel: irq261: igb0:que 4 14842310
Mar 12 07:51:56 beeb kernel: irq262: igb0:que 5 15035818
Mar 12 07:51:56 beeb kernel: irq263: igb0:que 6 14826606
Mar 12 07:51:56 beeb kernel: irq264: igb0:que 7 14924631
Mar 12 07:51:56 beeb kernel: irq265: igb0:link 2
Mar 12 07:51:56 beeb kernel: Total 1461395023
Mar 12 07:51:56 beeb kernel: KDB: stack backtrace:
Mar 12 07:51:56 beeb kernel: #0 0xffffffff8038d458 at kdb_backtrace+0x58
Mar 12 07:51:56 beeb kernel: #1 0xffffffff80315b4b at watchdog_fire+0x8b
Mar 12 07:51:56 beeb kernel: #2 0xffffffff80315e10 at hardclock_anycpu+0x2a0
Mar 12 07:51:56 beeb kernel: #3 0xffffffff80583278 at handleevents+0xd8
Mar 12 07:51:56 beeb kernel: #4 0xffffffff80583e36 at timercb+0x2d6
Mar 12 07:51:56 beeb kernel: #5 0xffffffff805aec46 at
lapic_handle_timer+0xb6
Mar 12 07:51:56 beeb kernel: #6 0xffffffff80557f2c at Xtimerint+0x8c
Mar 12 07:51:56 beeb kernel: #7 0xffffffff8055c348 at cpu_idle_acpi+0x38
Mar 12 07:51:56 beeb kernel: #8 0xffffffff8055c402 at cpu_idle+0xa2
Mar 12 07:51:56 beeb kernel: #9 0xffffffff80380b7f at sched_idletd+0x37f
Mar 12 07:51:56 beeb kernel: #10 0xffffffff80331d36 at fork_exit+0x76
Mar 12 07:51:56 beeb kernel: #11 0xffffffff8055790e at fork_trampoline+0xe
What should I blame now? Is it some programming error or should I
continue with testing/changing motherboard and cpu?
--
Sphinx of black quartz judge my vow.
More information about the freebsd-questions
mailing list