PDA

View Full Version : kerneloops, abrt and reporting



Underling
23rd November 2009, 09:18 PM
Hi all,

I've done a fresh install of F12 X86_64 on a newish 64 bit machine. Every time following power up I get a kerneloops warning after logging in as follows:


Nov 20 20:23:49 cashew kernel: ------------[ cut here ]------------
Nov 20 20:23:49 cashew kernel: WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:456 generic_get_mtrr+0xcc/0x10a() (Not tainted)
Nov 20 20:23:49 cashew kernel: Hardware name: System Product Name
Nov 20 20:23:49 cashew kernel: mtrr: your BIOS has set up an incorrect mask, fixing it up.
Nov 20 20:23:49 cashew kernel: Modules linked in:
Nov 20 20:23:49 cashew kernel: Pid: 0, comm: swapper Not tainted 2.6.31.5-127.fc12.x86_64 #1
Nov 20 20:23:49 cashew kernel: Call Trace:
Nov 20 20:23:49 cashew kernel: [<ffffffff81051694>] warn_slowpath_common+0x84/0x9c
Nov 20 20:23:49 cashew kernel: [<ffffffff81051703>] warn_slowpath_fmt+0x41/0x43
Nov 20 20:23:49 cashew kernel: [<ffffffff810227a4>] generic_get_mtrr+0xcc/0x10a
Nov 20 20:23:49 cashew kernel: [<ffffffff8171e864>] mtrr_cleanup+0x8f/0x3e1
Nov 20 20:23:49 cashew kernel: [<ffffffff8171d276>] mtrr_bp_init+0x1a9/0x1ce
Nov 20 20:23:49 cashew kernel: [<ffffffff8171970f>] setup_arch+0x465/0xa26
Nov 20 20:23:49 cashew kernel: [<ffffffff8141894f>] ? printk+0x41/0x4a
Nov 20 20:23:49 cashew kernel: [<ffffffff81714aaa>] start_kernel+0xd0/0x3fa
Nov 20 20:23:49 cashew kernel: [<ffffffff817142a1>] x86_64_start_reservations+0xac/0xb0
Nov 20 20:23:49 cashew kernel: [<ffffffff8171439d>] x86_64_start_kernel+0xf8/0x107
Nov 20 20:23:49 cashew kernel: ---[ end trace a7919e7f17c0a725 ]---

I thought I'd use abrt to submit information about this bug. After creating a bugzilla account to let it submit the information, and clicking send, abrt gives me the following error message


CKerneloopsReporter::Report():Report has not been sent...

However, the list of bugs in the main abrt window now says that this bug _has_ been submitted. Any suggestions as to what's going wrong?

Thanks for reading my first post.

RahulSundaram
23rd November 2009, 09:48 PM
Hi,

Abrt itself has some polish issues. Pick up the latest updates and see if it gets better. If not, file a bug report against abrt.

Underling
24th November 2009, 09:38 PM
The latest yum update seems to have cured it. Now to deal with the mtrr fault.

Thanks for your help.

Edit: Spoke too soon! Looks like it worked the first time, and fails every time after that. I'll try to file a bug report (if I can work out how).