kernel panic

Tue Jul 29 11:02:19 UTC 2014

Dear Dr  Matthew , 

hope  you are doing fine and  things going well with you ,as we always faced any issue we contact you and get really useful information .

see, in the morning i just find few issues regarding our system CPU manners and seems error should not comes in normal conditions . 

im  using Free BSD version 8  on a server and installing VOIP soft switch over it. could you please check the result that i get today in the morning  

( i have to say that system was not over loaded and working very smooth before and after this message ) 

i can see the following errors in /var/log/messages

Jul 29 08:31:40 smartss kernel: MCA: Bank 0, Status 0xd0000680000f0005
Jul 29 08:31:40 smartss kernel: MCA: Global Cap 0x0000000000000c09, Status
0x0000000000000000
Jul 29 08:31:40 smartss kernel: MCA: Vendor "GenuineIntel", ID
0x306c3, APIC ID 0
Jul 29 08:31:40 smartss kernel: MCA: CPU 0 COR (26) OVER internal parity error
Jul 29 08:31:40 smartss kernel: MCA: Bank 0, Status 0x90000040000f0005
Jul 29 08:31:40 smartss kernel: MCA: Global Cap 0x0000000000000c09, Status
0x0000000000000000
Jul 29 08:31:40 smartss kernel: MCA: Vendor "GenuineIntel", ID
0x306c3, APIC ID 2
Jul 29 08:31:40 smartss kernel: MCA: CPU 2 COR (1) internal parity error
Jul 29 08:31:40 smartss kernel: MCA: Bank 0, Status 0xd0000700000f0005
Jul 29 08:31:40 smartss kernel: MCA: Global Cap 0x0000000000000c09, Status
0x0000000000000000
Jul 29 08:31:40 smartss kernel: MCA: Vendor "GenuineIntel", ID
0x306c3, APIC ID 4
Jul 29 08:31:40 smartss kernel: MCA: CPU 4 COR (28) OVER internal parity error
Jul 29 08:31:40 smartss kernel: MCA: Bank 0, Status 0xd0000740000f0005
Jul 29 08:31:40 smartss kernel: MCA: Global Cap 0x0000000000000c09, Status
0x0000000000000000
Jul 29 08:31:40 smartss kernel: MCA: Vendor "GenuineIntel", ID
0x306c3, APIC ID 6
Jul 29 08:31:40 smartss kernel: MCA: CPU 6 COR (29) OVER internal parity error

Jul 29 09:31:40 smartss kernel: MCA: Bank 0, Status 0xd0000ec0000f0005
Jul 29 09:31:40 smartss kernel: MCA: Global Cap 0x0000000000000c09, Status
0x0000000000000000
Jul 29 09:31:40 smartss kernel: MCA: Vendor "GenuineIntel", ID
0x306c3, APIC ID 0
Jul 29 09:31:40 smartss kernel: MCA: CPU 0 COR (59) OVER internal parity error
Jul 29 09:31:40 smartss kernel: MCA: Bank 0, Status 0xd00000c0000f0005
Jul 29 09:31:40 smartss kernel: MCA: Global Cap 0x0000000000000c09, Status
0x0000000000000000
Jul 29 09:31:40 smartss kernel: MCA: Vendor "GenuineIntel", ID
0x306c3, APIC ID 2
Jul 29 09:31:40 smartss kernel: MCA: CPU 2 COR (3) OVER internal parity error
Jul 29 09:31:40 smartss kernel: MCA: Bank 0, Status 0xd0001700000f0005
Jul 29 09:31:40 smartss kernel: MCA: Global Cap 0x0000000000000c09, Status
0x0000000000000000
Jul 29 09:31:40 smartss kernel: MCA: Vendor "GenuineIntel", ID
0x306c3, APIC ID 4
Jul 29 09:31:40 smartss kernel: MCA: CPU 4 COR (92) OVER internal parity error
Jul 29 09:31:40 smartss kernel: MCA: Bank 0, Status 0xd0000dc0000f0005
Jul 29 09:31:40 smartss kernel: MCA: Global Cap 0x0000000000000c09, Status
0x0000000000000000
Jul 29 09:31:40 smartss kernel: MCA: Vendor "GenuineIntel", ID
0x306c3, APIC ID 6
Jul 29 09:31:40 smartss kernel: MCA: CPU 6 COR (55) OVER internal parity error

please tell me your thought , 

regards 

shahram 

On Thursday, 9 August 2012, 19:00, Matthew Seaman <matthew at FreeBSD.org> wrote:

On 09/08/2012 15:52, dude golden wrote:
> hope my email find you well,first of all thank you very much for your
> grate response always in answering my emails, now i am using freeBSD
> 8.3 in a Intel corI5 server with 12 G of RAM and 500 G HDD sata .we
> have a voip soft switch application installed on it and do
> telecommunication business, yesterday night we experience a strange
> kernel panic and our server hanged, just contact collocation as asked
> for physical reboot,

> in attached, you can find screen shot of rebooting the server . i
> really thank full if you take a look and advise me any update.

The freebsd-questions@ probably won't have seen the screen shot, but it
showed me that the problem was in ffs_blkfree, ie. that the system
panicked because of filesystem corruption.

Unfortunately you haven't enabled a dump device, so no more detailed
debugging info will be available.  There's not a huge amount that can be
determined just from the panic screen unfortunately.

However, in terms of general advice:

  * You need to ensure that there is no lingering filesystem corruption
which could trigger a repeat.  Reboot the system into single user mode,
and then run:

    fsck -fy /dev/ad7s4a

etc. for all the devices listed in /etc/fstab or elsewhere that have
active filesystems on them.  Run fsck like that repeatedly for each
partition until it says 'filesystem clean.'

  * Enable system dumps, so if this happens again, there is more to go
on.  Just add:

dumpdev="AUTO"

to /etc/rc.conf and reboot.

  * The problem could well be due to disk malfunction, or maybe
something as trivial as a loose or kinked data cable leading to the
drive, or overheating.  Powering the machine down, opening the case and
checking for any obvious problems would be a good idea.  Also, check the
system logs to see if there are any kernel messages indicating non-fatal
trouble.  Install the sysutils/smartmontools port and use that to get a
health report on the drive:

   smartctl  -A /dev/ad7

  * It seems you don't have any sort of hard drive resilience set up.
If this server is important for your business, then using mirrored hard
drives is just plain common sense.  If there's room in the chassis,
simply adding another drive identical to the one you have and setting up
gmirror RAID should be fairly simple and will offer adequate levels of
protection against such failures.

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey