Xen users - Aug 2008 - Module crash during xen boot on SuSE Linux 11.0

Hello,

i´m running XEN on a SuSE Linux host/guest system. Starting the guests 
shows this module failing:

OS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
sys_init_module: ''edd''->init suspiciously returned 1, it
should follow
0/-E convention
sys_init_module: loading module anyway...
Pid: 2076, comm: modprobe Tainted: G        N 2.6.25.11-0.1-xen #1
  [<c0104839>] dump_trace+0x63/0x223
  [<c01052e2>] show_trace+0x15/0x29
  [<c02dab9e>] _etext+0x5b/0x65
  [<c013c02c>] sys_init_module+0x1a0c/0x1ab6
  [<c0103f72>] syscall_call+0x7/0xb
  [<f57fe416>] 0xf57fe416
  =====================
can i just ignore this message? Or to avoid this, do i have to but the 
edd module into the modprobe blacklist?

Greeting, Jörg


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

I have 16 blades as Dom0s in an HP blade chassis running OpenSuse 11.0. Each
runs many Suse 11.0 DomUs, and they have all run fine for weeks. Yesterday I
rebooted one of the DomUs and it failed to boot. My error message looks to
be the same as yours:

USB Universal Host Controller Interface driver v3.0
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
sys_init_module: ''edd''->init suspiciously returned 1, it
should follow 0/-E
convention
sys_init_module: loading module anyway...
Pid: 559, comm: modprobe Tainted: G        N 2.6.25.9-0.2-xen #1

Call Trace:
 [<ffffffff8020c4b4>] dump_trace+0xbd/0x36a
 [<ffffffff8020c7a1>] show_trace+0x40/0x57
 [<ffffffff80434ad4>] _etext+0x72/0x7b
 [<ffffffff8024e5d1>] sys_init_module+0x1b8b/0x1c47
 [<ffffffff8020b638>] system_call+0x68/0x6d
 [<00007f3b3e68373a>]


I deleted the DomU and rebuilt it with the same OS and packages/configs. It
has been working fine since. I have no idea what happened, and though
rebuilding worked for me, it is far from an ideal solution. Please keep the
list updated with what you find or end up doing.

-Seraphi




On Tue, Aug 26, 2008 at 6:27 AM, Jörg Spilker <js@jetsys.de> wrote:
> Hello,
>
> i´m running XEN on a SuSE Linux host/guest system. Starting the guests
> shows this module failing:
>
> OS EDD facility v0.16 2004-Jun-25, 0 devices found
> EDD information not available.
> sys_init_module: ''edd''->init suspiciously returned 1,
it should follow 0/-E
> convention
> sys_init_module: loading module anyway...
> Pid: 2076, comm: modprobe Tainted: G        N 2.6.25.11-0.1-xen #1
>  [<c0104839>] dump_trace+0x63/0x223
>  [<c01052e2>] show_trace+0x15/0x29
>  [<c02dab9e>] _etext+0x5b/0x65
>  [<c013c02c>] sys_init_module+0x1a0c/0x1ab6
>  [<c0103f72>] syscall_call+0x7/0xb
>  [<f57fe416>] 0xf57fe416
>  =====================>
> can i just ignore this message? Or to avoid this, do i have to but the edd
> module into the modprobe blacklist?
>
> Greeting, Jörg
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Seraphi schrieb:

Hello,
> I deleted the DomU and rebuilt it with the same OS and packages/configs. 
> It has been working fine since. I have no idea what happened, and though 
> rebuilding worked for me, it is far from an ideal solution. Please keep 
> the list updated with what you find or end up doing.
i´m not really sure but i think the module is crashing since initial 
installation of the domU. What i´ve done for now is to put the module 
edd into /etc/modprobe.d/blacklist of the domU.

Greetings, Jörg

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