Re: [Xen-users] 2.6.29.1 domU: dmi check not initialized yet

[Andrew Lyon <andrew.lyon@xxxxxxxxx>]

On Sun, Apr 5, 2009 at 4:06 PM, jon.hart <jon.hart@xxxxxx> wrote:
> Hello,
>
> booting a 2.6.29.1 kernel on top of a dom0 with the same kernel version
> I get the following console output:
>
> ------------[ cut here ]------------
>
> WARNING: at /usr/src/linux-2.6.29.1/drivers/firmware/dmi_scan.c:425
> dmi_matches+0x7e/0x80()
> dmi check: not initialized yet.
>
> Modules linked in:
>
> Pid: 1, comm: swapper Tainted: G        W  2.6.29.1-wickie-domU #9
>
> Call Trace:
>
>  [<c0126229>] warn_slowpath+0x99/0xc0
>
>  [<c011b49e>] __wake_up+0x3e/0x60
>
>  [<c0136d72>] call_usermodehelper_exec+0x92/0xc0
>
>  [<c021c600>] kobject_uevent_env+0xa0/0x3d0
>
>  [<c012cfb9>] sysctl_set_parent+0x19/0x30
>
>  [<c012cfb9>] sysctl_set_parent+0x19/0x30
>
>  [<c012e05a>] __register_sysctl_paths+0x19a/0x2d0
>
>  [<c0291f2e>] dmi_matches+0x7e/0x80
>
>  [<c0291f87>] dmi_check_system+0x17/0x50
>
>  [<c041f871>] i8042_init+0x41/0xd0
>
>  [<c0102032>] _stext+0x32/0x190
>
>  [<c01cc400>] create_proc_entry+0x0/0xa0
>
>  [<c015a128>] register_irq_proc+0xa8/0xc0
>
>  [<c04075aa>] kernel_init+0x11a/0x180
>
>  [<c0407490>] kernel_init+0x0/0x180
>
>  [<c0104b03>] kernel_thread_helper+0x7/0x10
>
> ---[ end trace 4eaa2a86a8e2da4d ]---
>
> ------------[ cut here ]------------
>
> Only domU shows this WARNING, dom0 is not affected.
>
> I'm not able to figure out what the problem is and how to circumvent
> this warning, seaching the web didn't help so far.
>
> Please can someone on the list point me to the right direction how to
> solve this problem?
>
> Cheers
> jon
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

I get the same message when booting openSUSE 2.6.29 domU kernel, is
your kernel patched for Xen support or are you using pv_ops?

------------[ cut here ]------------
WARNING: at drivers/firmware/dmi_scan.c:425 dmi_matches+0x2a/0x74()
dmi check: not initialized yet.
Modules linked in:
Pid: 1, comm: swapper Tainted: G        W  2.6.29-xen #8
Call Trace:
 [<ffffffff8022b0ba>] warn_slowpath+0xd8/0xf5
 [<ffffffff803abb63>] __xencons_tx_flush+0x57/0xad
 [<ffffffff803abda3>] kcons_write+0x5d/0x9c
 [<ffffffff80240ede>] up+0xe/0x36
 [<ffffffff8022b832>] release_console_sem+0x1ef/0x20a
 [<ffffffff8022bd06>] vprintk+0x2bf/0x319
 [<ffffffff804a4465>] workqueue_cpu_callback+0x9a/0xef
 [<ffffffff80676308>] setup_vcpu_hotplug_event+0x0/0x20
 [<ffffffff8022bdae>] printk+0x4e/0x56
 [<ffffffff80230e22>] __request_region+0x75/0xad
 [<ffffffff80679dce>] pci_arch_init+0x0/0x40
 [<ffffffff804222a8>] dmi_matches+0x2a/0x74
 [<ffffffff80679dce>] pci_arch_init+0x0/0x40
 [<ffffffff8042232e>] dmi_check_system+0x15/0x41
 [<ffffffff80679dce>] pci_arch_init+0x0/0x40
 [<ffffffff80679e05>] pci_arch_init+0x37/0x40
 [<ffffffff80208051>] _stext+0x51/0x15d
 [<ffffffff802c3c97>] create_proc_entry+0x73/0x8a
 [<ffffffff80251534>] register_irq_proc+0x92/0xaa
 [<ffffffff80662640>] kernel_init+0x12c/0x186
 [<ffffffff8020b19a>] child_rip+0xa/0x20
 [<ffffffff80662514>] kernel_init+0x0/0x186
 [<ffffffff8020b190>] child_rip+0x0/0x20
---[ end trace 4eaa2a86a8e2da27 ]---
------------[ cut here ]------------

You can get rid of the message by enabling EMBEDDED (Configure
standard kernel features (for small systems))  in General Setup, then
go to "Processor type and features" and disable "Enable DMI scanning
(NEW)"

I don't think DMI is supported on Xen, I tried dmidecode and it fails:

 dmidecode
# dmidecode 2.9
/dev/mem: mmap: Bad address

Andy

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users