mtrr: your BIOS has set up an incorrect mask, fixing it up.

Bug #568441 reported by Alessandro Bono
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi

I have upgraded one of my proliant ml 350 g5 from hardy to karmic and now to lucid, starting from karmic appears this warning on dmesg

WARNING: at /build/buildd/linux-2.6.32/arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140()
[ 7.155329] Hardware name: ProLiant ML350 G5
[ 7.155331] mtrr: your BIOS has set up an incorrect mask, fixing it up.
[ 7.155333] Modules linked in: fbcon tileblit font bitblit softcursor vga16fb vgastate radeon ttm i5000_edac bnx2(+) drm_kms_helper edac_core lp psmouse drm ipmi_si(+) i5k_amb serio_raw i2c_algo_bit kvm_intel floppy(+) ipmi_msghandler hpilo shpchp kvm parport xfs exportfs usbhid hid e1000e cciss
[ 7.155361] Pid: 455, comm: plymouthd Not tainted 2.6.32-21-server #32-Ubuntu
[ 7.155363] Call Trace:
[ 7.155370] [<ffffffff81066d1b>] warn_slowpath_common+0x7b/0xc0
[ 7.155373] [<ffffffff81066dc1>] warn_slowpath_fmt+0x41/0x50
[ 7.155377] [<ffffffff81028d0e>] generic_get_mtrr+0x11e/0x140
[ 7.155381] [<ffffffff8102788b>] mtrr_add_page+0xdb/0x3f0
[ 7.155384] [<ffffffff81027bf6>] mtrr_add+0x56/0x70
[ 7.155400] [<ffffffffa01c91e9>] drm_addmap_core+0x659/0x800 [drm]
[ 7.155408] [<ffffffffa01c942a>] drm_addmap+0x1a/0x30 [drm]
[ 7.155427] [<ffffffffa0261abd>] radeon_driver_firstopen+0x5d/0x70 [radeon]
[ 7.155436] [<ffffffffa01cba43>] drm_setup+0x23/0x1a0 [drm]
[ 7.155444] [<ffffffffa01cc052>] drm_open+0x102/0x120 [drm]
[ 7.155452] [<ffffffffa01cc1a3>] drm_stub_open+0x133/0x260 [drm]
[ 7.155459] [<ffffffff8114702a>] chrdev_open+0x13a/0x240
[ 7.155462] [<ffffffff81146ef0>] ? chrdev_open+0x0/0x240
[ 7.155466] [<ffffffff81141393>] __dentry_open+0x113/0x370
[ 7.155471] [<ffffffff8125192f>] ? security_inode_permission+0x1f/0x30
[ 7.155474] [<ffffffff8114d6ff>] ? inode_permission+0xaf/0xd0
[ 7.155478] [<ffffffff81141707>] nameidata_to_filp+0x57/0x70
[ 7.155481] [<ffffffff8115193a>] do_filp_open+0x2da/0xba0
[ 7.155486] [<ffffffff8115d2da>] ? alloc_fd+0x10a/0x150
[ 7.155489] [<ffffffff81141109>] do_sys_open+0x69/0x170
[ 7.155492] [<ffffffff81141250>] sys_open+0x20/0x30
[ 7.155497] [<ffffffff810131b2>] system_call_fastpath+0x16/0x1b
[ 7.155499] ---[ end trace 36b5203afece7194 ]---

cat /proc/mtrr
reg00: base=0x0e0000000 ( 3584MB), size= 512MB, count=1: uncachable

another identical machine but with ubuntu hardy, kernel 2.6.24-26-xen has this mtrr

cat /proc/mtrr
reg00: base=0xe0000000 (3584MB), size=197120MB: uncachable, count=0

Is it a bios problem? Have I to fill a bug to HP support or newer kernel are incorrect?

thanks
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 10.04
MachineType: HP ProLiant ML350 G5
Package: linux (not installed)
PciMultimedia:

ProcCmdLine: root=/dev/mapper/hostname-root ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-server 2.6.32.11+drm33.2
Regression: Yes
Reproducible: Yes
Tags: lucid regression-release needs-upstream-testing
Uname: Linux 2.6.32-21-server x86_64
UserGroups:

dmi.bios.date: 07/10/2009
dmi.bios.vendor: HP
dmi.bios.version: D21
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrD21:bd07/10/2009:svnHP:pnProLiantML350G5:pvr:cvnHP:ct7:cvr:
dmi.product.name: ProLiant ML350 G5
dmi.sys.vendor: HP

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Alessandro,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 568441

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Alessandro Bono (a.bono) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Alessandro Bono (a.bono) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Alessandro Bono (a.bono) wrote : Lspci.txt

apport information

Revision history for this message
Alessandro Bono (a.bono) wrote : Lsusb.txt

apport information

Revision history for this message
Alessandro Bono (a.bono) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Alessandro Bono (a.bono) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Alessandro Bono (a.bono) wrote : ProcModules.txt

apport information

Revision history for this message
Alessandro Bono (a.bono) wrote : UdevDb.txt

apport information

Revision history for this message
Alessandro Bono (a.bono) wrote : UdevLog.txt

apport information

Revision history for this message
Alessandro Bono (a.bono) wrote :

I tried also kernel 2.6.33.3 from KernelMainlineBuilds with the same result, dmesg attached

tags: removed: needs-upstream-testing
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Alessandro,
     Also, have you checked to see if there are any BIOS updates for your system?

Thanks!

~JFo

Revision history for this message
Alessandro Bono (a.bono) wrote :

HI Jeremy

This machine has all firmware/bios update
This is a semi-production machine so if you need to do test or try patch I can do without big trouble

thanks

Revision history for this message
Adam Collard (adam-collard) wrote :

Also seeing this on an HP ProLiant G3

BIOS Information
        Vendor: HP
        Version: O08
        Release Date: 11/16/2007
        Address: 0xE2340
        Runtime Size: 122048 bytes
        ROM Size: 1024 kB
        Characteristics:
                ISA is supported
                PCI is supported
                PC Card (PCMCIA) is supported
                PNP is supported
                APM is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                ESCD support is available
                USB legacy is supported
                Smart battery is supported
                BIOS boot specification is supported

Handle 0x0001, DMI type 1, 25 bytes
System Information
        Manufacturer: HP
        Product Name: ProLiant DL140 G3
        Version: 436602-001
        Serial Number: GB8813FK6X
        UUID: 7EFFD30F-7EFF-E41F-7EFF-E41F83BF7310
        Wake-up Type: Power Switch

Linux adar 2.6.32-22-server #33-Ubuntu SMP Wed Apr 28 14:34:48 UTC 2010 x86_64 GNU/Linux

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Adam Collard (adam-collard) wrote :

Relevant output from dmesg

[ 0.000000] ------------[ cut here ]------------
[ 0.000000] WARNING: at /build/buildd/linux-2.6.32/arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140()
[ 0.000000] Hardware name: ProLiant DL140 G3
[ 0.000000] mtrr: your BIOS has set up an incorrect mask, fixing it up.
[ 0.000000] Modules linked in:
[ 0.000000] Pid: 0, comm: swapper Not tainted 2.6.32-22-server #33-Ubuntu
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff81066d1b>] warn_slowpath_common+0x7b/0xc0
[ 0.000000] [<ffffffff81066dc1>] warn_slowpath_fmt+0x41/0x50
[ 0.000000] [<ffffffff81028d0e>] generic_get_mtrr+0x11e/0x140
[ 0.000000] [<ffffffff8188410e>] mtrr_trim_uncached_memory+0x91/0x309
[ 0.000000] [<ffffffff818830c5>] ? mtrr_bp_init+0x1ab/0x1d2
[ 0.000000] [<ffffffff8187f848>] setup_arch+0x3d6/0x6eb
[ 0.000000] [<ffffffff81554956>] ? printk+0x41/0x43
[ 0.000000] [<ffffffff8187ab2e>] start_kernel+0xca/0x371
[ 0.000000] [<ffffffff8187a33a>] x86_64_start_reservations+0x125/0x129
[ 0.000000] [<ffffffff8187a438>] x86_64_start_kernel+0xfa/0x109
[ 0.000000] ---[ end trace a7919e7f17c0a725 ]---

Revision history for this message
Stéphane Loeuillet (leroutier) wrote :

Also confirmed with latest 10.04 on HP ProLiant 460c G1 blade servers with latest firmware/BIOS :

Reproductible at every boot

[ 5.601231] ------------[ cut here ]------------
[ 5.601239] WARNING: at /build/buildd/linux-2.6.32/arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140()
[ 5.601242] Hardware name: ProLiant BL460c G1
[ 5.601243] mtrr: your BIOS has set up an incorrect mask, fixing it up.
[ 5.601245] Modules linked in: usbhid(+) i7300_idle(-) fbcon tileblit font bitblit softcursor vga16fb vgastate hid ipmi_si(+) radeon ttm ipmi_msghandler drm_kms_helper psmouse hpilo floppy(+) serio_raw drm i2c_algo_bit bnx2 i5000_edac edac_core i5k_amb shpchp lp parport cciss
[ 5.601266] Pid: 358, comm: plymouthd Not tainted 2.6.32-22-server #33-Ubuntu
[ 5.601268] Call Trace:
[ 5.601274] [<ffffffff81066d1b>] warn_slowpath_common+0x7b/0xc0
[ 5.601277] [<ffffffff81066dc1>] warn_slowpath_fmt+0x41/0x50
[ 5.601280] [<ffffffff81028d0e>] generic_get_mtrr+0x11e/0x140
[ 5.601283] [<ffffffff8102788b>] mtrr_add_page+0xdb/0x3f0
[ 5.601298] [<ffffffffa0097862>] ? drm_ht_just_insert_please+0xa2/0xf0 [drm]
[ 5.601301] [<ffffffff81027bf6>] mtrr_add+0x56/0x70
[ 5.601308] [<ffffffffa008d1e9>] drm_addmap_core+0x659/0x800 [drm]
[ 5.601314] [<ffffffffa008d42a>] drm_addmap+0x1a/0x30 [drm]
[ 5.601328] [<ffffffffa0137abd>] radeon_driver_firstopen+0x5d/0x70 [radeon]
[ 5.601334] [<ffffffffa008fa43>] drm_setup+0x23/0x1a0 [drm]
[ 5.601341] [<ffffffffa0090052>] drm_open+0x102/0x120 [drm]
[ 5.601348] [<ffffffffa00901a3>] drm_stub_open+0x133/0x260 [drm]
[ 5.601353] [<ffffffff8114702a>] chrdev_open+0x13a/0x240
[ 5.601356] [<ffffffff81146ef0>] ? chrdev_open+0x0/0x240
[ 5.601359] [<ffffffff81141393>] __dentry_open+0x113/0x370
[ 5.601363] [<ffffffff8125192f>] ? security_inode_permission+0x1f/0x30
[ 5.601366] [<ffffffff8114d6ff>] ? inode_permission+0xaf/0xd0
[ 5.601368] [<ffffffff81141707>] nameidata_to_filp+0x57/0x70
[ 5.601371] [<ffffffff8115193a>] do_filp_open+0x2da/0xba0
[ 5.601375] [<ffffffff8115d2da>] ? alloc_fd+0x10a/0x150
[ 5.601378] [<ffffffff81141109>] do_sys_open+0x69/0x170
[ 5.601380] [<ffffffff81141250>] sys_open+0x20/0x30
[ 5.601384] [<ffffffff810131b2>] system_call_fastpath+0x16/0x1b
[ 5.601386] ---[ end trace b7aa7c061981b639 ]---

tags: added: kernel-core kernel-needs-review
Revision history for this message
Stéphane Loeuillet (leroutier) wrote :

Bug #548798 and bug #459723 as possible dupes of this one ?

Rank 7: generic_get_mtrr (warning)
Reported 139 times (1009 total reports)
BIOS bug where the MTRRs are not set up correctly
This warning was last seen in version 2.6.30, and first seen in 2.6.25.3.
More info: http://www.kerneloops.org/searchweek.php?search=generic_get_mtrr

tags: added: kernel-reviewed
removed: kernel-needs-review
Revision history for this message
Stéphane Loeuillet (leroutier) wrote :

Still the same with 2.6.32-22-server #35-Ubuntu

Revision history for this message
LAZA (laza74) wrote :

This bug is still existend in Ubuntu 10.04.2 on a Gigabyte GA-MA790GP-UD4H:

[ 302.577002] WARNING: at /build/buildd/linux-2.6.32/arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140()
[ 302.577004] Hardware name: GA-MA790GP-UD4H
[ 302.577005] mtrr: your BIOS has set up an incorrect mask, fixing it up.
[ 302.577007] Modules linked in: radeon(+) r8169 ttm ohci1394(+) usbhid hid drm_kms_helper mii ieee1394 drm i2c_algo_bit pata_atiixp ahci
[ 302.577016] Pid: 423, comm: work_for_cpu Not tainted 2.6.32-30-generic #59-Ubuntu
[ 302.577018] Call Trace:
[ 302.577023] [<ffffffff8106649b>] warn_slowpath_common+0x7b/0xc0
[ 302.577026] [<ffffffff81066541>] warn_slowpath_fmt+0x41/0x50
[ 302.577029] [<ffffffff8102801e>] generic_get_mtrr+0x11e/0x140
[ 302.577032] [<ffffffff81026b4b>] mtrr_add_page+0xdb/0x3f0
[ 302.577034] [<ffffffff81026eb6>] mtrr_add+0x56/0x70
[ 302.577056] [<ffffffffa01175ae>] radeon_bo_init+0x2e/0x90 [radeon]
[ 302.577073] [<ffffffffa015772b>] r600_init+0x11b/0x360 [radeon]
[ 302.577088] [<ffffffffa0104e3f>] radeon_device_init+0x26f/0x360 [radeon]
[ 302.577102] [<ffffffffa0105bef>] radeon_driver_load_kms+0x9f/0x1d0 [radeon]
[ 302.577114] [<ffffffffa002a8af>] drm_get_dev+0x15f/0x270 [drm]
[ 302.577118] [<ffffffff81080520>] ? do_work_for_cpu+0x0/0x30
[ 302.577133] [<ffffffffa016c8f8>] radeon_pci_probe+0x15/0x269 [radeon]
[ 302.577137] [<ffffffff812d0ee7>] local_pci_probe+0x17/0x20
[ 302.577139] [<ffffffff81080538>] do_work_for_cpu+0x18/0x30
[ 302.577142] [<ffffffff810847f6>] kthread+0x96/0xa0
[ 302.577145] [<ffffffff810131ea>] child_rip+0xa/0x20
[ 302.577148] [<ffffffff81084760>] ? kthread+0x0/0xa0
[ 302.577150] [<ffffffff810131e0>] ? child_rip+0x0/0x20
[ 302.577151] ---[ end trace aec9bc9e1fd06243 ]---

Revision history for this message
Joeman1 (jgiles) wrote :

I'm getting this too on my server:
Hardware name: GA-880GMA-UD2H

[ 6.481679] ------------[ cut here ]------------
[ 6.481683] WARNING: at /build/buildd/linux-2.6.32/arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140()
[ 6.481685] Hardware name: GA-880GMA-UD2H
[ 6.481685] mtrr: your BIOS has set up an incorrect mask, fixing it up.
[ 6.481686] Modules linked in: snd_hwdep radeon(+) ttm it87 snd_pcm bridge snd_timer snd soundcore snd_page_alloc drm_kms_helper hwmon_vid stp drm lp i2c_algo_bit parport i2c_piix4 serio_raw xhci edac_core edac_mce_amd shpchp raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 e100 mii multipath pata_jmicron ahci linear
[ 6.481701] Pid: 1080, comm: work_for_cpu Not tainted 2.6.32-31-server #61-Ubuntu
[ 6.481702] Call Trace:
[ 6.481706] [<ffffffff81067bbb>] warn_slowpath_common+0x7b/0xc0
[ 6.481708] [<ffffffff81067c61>] warn_slowpath_fmt+0x41/0x50
[ 6.481710] [<ffffffff81028ebe>] generic_get_mtrr+0x11e/0x140
[ 6.481712] [<ffffffff81027a3b>] mtrr_add_page+0xdb/0x3f0
[ 6.481713] [<ffffffff81027da6>] mtrr_add+0x56/0x70
[ 6.481730] [<ffffffffa01e75ae>] radeon_bo_init+0x2e/0x90 [radeon]
[ 6.481742] [<ffffffffa02277fb>] r600_init+0x11b/0x360 [radeon]
[ 6.481752] [<ffffffffa01d4e2f>] radeon_device_init+0x26f/0x360 [radeon]
[ 6.481762] [<ffffffffa01d5bdf>] radeon_driver_load_kms+0x9f/0x1d0 [radeon]
[ 6.481770] [<ffffffffa00e88af>] drm_get_dev+0x15f/0x270 [drm]
[ 6.481772] [<ffffffff81081a90>] ? do_work_for_cpu+0x0/0x30
[ 6.481783] [<ffffffffa023c9c8>] radeon_pci_probe+0x15/0x276 [radeon]
[ 6.481785] [<ffffffff812d2b67>] local_pci_probe+0x17/0x20
[ 6.481787] [<ffffffff81081aa8>] do_work_for_cpu+0x18/0x30
[ 6.481788] [<ffffffff81085c76>] kthread+0x96/0xa0
[ 6.481790] [<ffffffff810141ea>] child_rip+0xa/0x20
[ 6.481792] [<ffffffff81085be0>] ? kthread+0x0/0xa0
[ 6.481793] [<ffffffff810141e0>] ? child_rip+0x0/0x20
[ 6.481799] ---[ end trace 8ad2a4fdb4253706 ]---

As a side note, I installed 2.6.38-8 to test some other stuff, and noticed I didn't get this BT

Revision history for this message
dikdust (dikdust) wrote :

I'm getting this also in a proliant DL360 GS

[ 9.211377] ------------[ cut here ]------------
[ 9.211388] WARNING: at /build/buildd/linux-2.6.32/arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140()
[ 9.211391] Hardware name: ProLiant DL360 G5
[ 9.211392] mtrr: your BIOS has set up an incorrect mask, fixing it up.
[ 9.211394] Modules linked in: fbcon tileblit font bitblit softcursor vga16fb vgastate radeon ttm drm_kms_helper xfs bnx2(+) exportfs ipmi_si(+) i5000_edac drm psmouse ipmi_msghandler edac_core i2c_algo_bit serio_raw lp hpilo i5k_amb shpchp parport usbhid hid usb_storage cciss
[ 9.211421] Pid: 336, comm: plymouthd Not tainted 2.6.32-32-server #62-Ubuntu
[ 9.211424] Call Trace:
[ 9.211430] [<ffffffff81067beb>] warn_slowpath_common+0x7b/0xc0
[ 9.211434] [<ffffffff81067c91>] warn_slowpath_fmt+0x41/0x50
[ 9.211437] [<ffffffff81028ebe>] generic_get_mtrr+0x11e/0x140
[ 9.211441] [<ffffffff81027a3b>] mtrr_add_page+0xdb/0x3f0
[ 9.211457] [<ffffffffa00d9982>] ? drm_ht_just_insert_please+0xa2/0xf0 [drm]
[ 9.211461] [<ffffffff81027da6>] mtrr_add+0x56/0x70
[ 9.211469] [<ffffffffa00cf209>] drm_addmap_core+0x659/0x800 [drm]
[ 9.211476] [<ffffffffa00cf44a>] drm_addmap+0x1a/0x30 [drm]
[ 9.211492] [<ffffffffa01e3abd>] radeon_driver_firstopen+0x5d/0x70 [radeon]
[ 9.211500] [<ffffffffa00d1ae3>] drm_setup+0x23/0x1a0 [drm]
[ 9.211508] [<ffffffffa00d20fa>] drm_open+0x10a/0x130 [drm]
[ 9.211517] [<ffffffffa00d2253>] drm_stub_open+0x133/0x260 [drm]
[ 9.211521] [<ffffffff8114a68a>] chrdev_open+0x13a/0x240
[ 9.211524] [<ffffffff8114a550>] ? chrdev_open+0x0/0x240
[ 9.211528] [<ffffffff81144a13>] __dentry_open+0x113/0x370
[ 9.211533] [<ffffffff8125629f>] ? security_inode_permission+0x1f/0x30
[ 9.211537] [<ffffffff81150dff>] ? inode_permission+0xaf/0xd0
[ 9.211540] [<ffffffff81144d87>] nameidata_to_filp+0x57/0x70
[ 9.211544] [<ffffffff8115503a>] do_filp_open+0x2da/0xba0
[ 9.211549] [<ffffffff81160aca>] ? alloc_fd+0x10a/0x150
[ 9.211552] [<ffffffff81144789>] do_sys_open+0x69/0x170
[ 9.211555] [<ffffffff811448d0>] sys_open+0x20/0x30
[ 9.211560] [<ffffffff810131b2>] system_call_fastpath+0x16/0x1b
[ 9.211563] ---[ end trace 8d16cf6c6d82976e ]---

Revision history for this message
Mate Gabri (mailinglist-n) wrote :

I'm running 3 identical HP DL380 G5 machines with the exact same setup. OS is Ubuntu 10.04.02 LTS, same stock up-to-date kernel version. Each of the machines are running PostgreSQL.
I experience the above error message only on one of the machines.
[ 4.566420] ------------[ cut here ]------------
[ 4.566431] WARNING: at /build/buildd/linux-2.6.32/arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140()
[ 4.566434] Hardware name: ProLiant DL380 G5
[ 4.566435] mtrr: your BIOS has set up an incorrect mask, fixing it up.
[ 4.566437] Modules linked in: fbcon tileblit font bitblit softcursor vga16fb vgastate radeon ttm drm_kms_helper i5000_edac edac_core bnx2(+) drm i5k_amb ipmi_si(+) ipmi_msghandler lp i2c_algo_bit psmouse shpchp hpilo serio_raw parport usbhid hid cciss
[ 4.566462] Pid: 379, comm: plymouthd Not tainted 2.6.32-32-server #62-Ubuntu
[ 4.566464] Call Trace:
[ 4.566471] [<ffffffff81067beb>] warn_slowpath_common+0x7b/0xc0
[ 4.566474] [<ffffffff81067c91>] warn_slowpath_fmt+0x41/0x50
[ 4.566478] [<ffffffff81028ebe>] generic_get_mtrr+0x11e/0x140
[ 4.566482] [<ffffffff81027a3b>] mtrr_add_page+0xdb/0x3f0
[ 4.566485] [<ffffffff81027da6>] mtrr_add+0x56/0x70
[ 4.566499] [<ffffffffa00b2209>] drm_addmap_core+0x659/0x800 [drm]
[ 4.566507] [<ffffffffa00b244a>] drm_addmap+0x1a/0x30 [drm]
[ 4.566525] [<ffffffffa0151abd>] radeon_driver_firstopen+0x5d/0x70 [radeon]
[ 4.566534] [<ffffffffa00b4ae3>] drm_setup+0x23/0x1a0 [drm]
[ 4.566542] [<ffffffffa00b50fa>] drm_open+0x10a/0x130 [drm]
[ 4.566550] [<ffffffffa00b5253>] drm_stub_open+0x133/0x260 [drm]
[ 4.566554] [<ffffffff8114a68a>] chrdev_open+0x13a/0x240
[ 4.566557] [<ffffffff8114a550>] ? chrdev_open+0x0/0x240
[ 4.566562] [<ffffffff81144a13>] __dentry_open+0x113/0x370
[ 4.566567] [<ffffffff8125629f>] ? security_inode_permission+0x1f/0x30
[ 4.566570] [<ffffffff81150dff>] ? inode_permission+0xaf/0xd0
[ 4.566573] [<ffffffff81144d87>] nameidata_to_filp+0x57/0x70
[ 4.566577] [<ffffffff8115503a>] do_filp_open+0x2da/0xba0
[ 4.566582] [<ffffffff81160aca>] ? alloc_fd+0x10a/0x150
[ 4.566585] [<ffffffff81144789>] do_sys_open+0x69/0x170
[ 4.566588] [<ffffffff811448d0>] sys_open+0x20/0x30
[ 4.566593] [<ffffffff810131b2>] system_call_fastpath+0x16/0x1b
[ 4.566596] ---[ end trace 44b8f52a3e726c0b ]---

This machine is also experiencing a high softirq rate. Every 5 minutes the softirq runs at 20% for maybe 20 seconds. I don't know if they are related but this softirq stuff is also strange.
Please let me know if I should provide more information.

Revision history for this message
penalvch (penalvch) wrote :

Alessandro Bono, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

tags: added: lucid needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: regression-release
Revision history for this message
Alessandro Bono (a.bono) wrote :

Hi

warning disappear after bios upgrade so probably kernel was right
please close this bug

thanks

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.