Call Trace
 

Hello guru's,

I noticed that one of our server having a call trace message. the hardware name is Proliant BL460c G1, we have two server running on RHEL5.5x84_64, but only one server has this message

------------[ cut here ]------------
WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0xcf/0x111()
Hardware name: ProLiant BL460c G1
mtrr: your BIOS has set up an incorrect mask, fixing it up.
Modules linked in: snd_pcsp(-)(U) i7300_idle(-)(U) radeon(+)(U) ttm(U) snd_seq_dummy(U) drm_kms_helper(U) drm(U) snd_seq_oss(U) snd_seq_midi_event(U) i2c_algo_bit(U) ipmi_si(U) snd_seq(U) ipmi_msghandler(U) i2c_core(U) snd_seq_device(U) hpilo(U) hpwdt(U) snd_pcm_oss(U) serio_raw(U) snd_mixer_oss(U) snd_pcm(U) snd_timer(U) snd(U) soundcore(U) snd_page_alloc(U) floppy(+)(U) i5k_amb(U) iTCO_wdt(U) i5000_edac(U) iTCO_vendor_support(U) edac_core(U) shpchp(U) pcspkr(U) usb_storage(U) lpfc(U) scsi_transport_fc(U) scsi_tgt(U) cciss(U)
Pid: 1124, comm: modprobe Not tainted 2.6.32-300.32.1.el5uek #1
Call Trace:
[<ffffffff810253ff>] ? generic_get_mtrr+0xcf/0x111
[<ffffffff81057850>] warn_slowpath_common+0x7c/0x94
[<ffffffff810578e7>] warn_slowpath_fmt+0x69/0x6b
[<ffffffff81442ca7>] ? klist_put+0x4e/0x70
[<ffffffff8124acbc>] ? match_pci_dev_by_id+0x0/0x61
[<ffffffff8124ae87>] ? pci_get_class+0x6c/0x78
[<ffffffff810253ff>] generic_get_mtrr+0xcf/0x111
[<ffffffff810432d6>] ? should_resched+0xe/0x2f
[<ffffffff81023fae>] mtrr_add_page+0x16e/0x33b
[<ffffffff810241bf>] mtrr_add+0x44/0x51
[<ffffffffa02492e2>] radeon_object_init+0x2e/0x88 [radeon]
[<ffffffffa025bebe>] r100_init+0x195/0x247 [radeon]
[<ffffffffa023d86b>] radeon_device_init+0x217/0x291 [radeon]
[<ffffffffa023e2d5>] radeon_driver_load_kms+0x10b/0x142 [radeon]
[<ffffffffa01d6636>] drm_get_dev+0x32e/0x42f [drm]
[<ffffffffa0270498>] radeon_pci_probe+0x15/0x268 [radeon]
[<ffffffff81249a99>] local_pci_probe+0x17/0x1b
[<ffffffff8124a609>] pci_device_probe+0xc8/0xf4
[<ffffffff812e5565>] ? driver_sysfs_add+0x52/0x78
[<ffffffff812e5740>] driver_probe_device+0xf5/0x215
[<ffffffff812e58b9>] __driver_attach+0x59/0x7c
[<ffffffff812e5860>] ? __driver_attach+0x0/0x7c
[<ffffffff812e5860>] ? __driver_attach+0x0/0x7c
[<ffffffff812e4bbc>] bus_for_each_dev+0x4e/0x7d
[<ffffffff812e5511>] driver_attach+0x21/0x23
[<ffffffff812e4677>] bus_add_driver+0xde/0x266
[<ffffffff812e5c86>] driver_register+0xa3/0x11a
[<ffffffffa02a1000>] ? radeon_init+0x0/0xc5 [radeon]
[<ffffffff8124a887>] __pci_register_driver+0x55/0xb1
[<ffffffffa02a1000>] ? radeon_init+0x0/0xc5 [radeon]
[<ffffffffa01d1cfe>] drm_init+0x6d/0xd0 [drm]
[<ffffffffa02a1000>] ? radeon_init+0x0/0xc5 [radeon]
[<ffffffffa02a10c3>] radeon_init+0xc3/0xc5 [radeon]
[<ffffffff8100a06a>] do_one_initcall+0x5f/0x15a
[<ffffffff810904da>] sys_init_module+0xd0/0x22a
[<ffffffff81011db2>] system_call_fastpath+0x16/0x1b
---[ end trace a948d636029ed196 ]---

does the server kernel panic at this point and die or continue on?
Any hardware changes and/or firmware updates happen recently?

no kernel panic and server is contentiously running.