[Bug 568441] Re: mtrr: your BIOS has set up an incorrect mask, fixing it up.

[Alessandro Bono]

apport information

** Tags added: apport-collected

** Description changed:

  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

** Attachment added: "BootDmesg.txt"
   http://launchpadlibrarian.net/46252007/BootDmesg.txt

-- 
mtrr: your BIOS has set up an incorrect mask, fixing it up. 
https://bugs.launchpad.net/bugs/568441
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.