RE: [Sisuite-users] kernel BUG at include/linux/i2o.h:517!

[Bernard Li]

Title: Re: [Sisuite-users] kernel BUG at include/linux/i2o.h:517!

What OS are you imaging?  Are you sure your hardware works with the OS?

 

SystemImager 3.6.3 provides 2 ways to generate a kernel/initrd.img:

 

1) From the boot-standard package, this is the stock one which SystemImager builds

2) By generating it on the fly using UseYourOwnKernel (triggered by si_prepareclient), this uses the kernel from /boot (on your OS) and generate a initrd.img from the template provided in the initrd_template package

 

So you tried both sets of these and both gave you kernel panic?  Were there any other messages besides that message in the topic?

 

Can you provide us with the exact model of your SATA hardware and what modules it is supposed to use?  You mentioned that it works in "production" so I assume you have a Linux distro which works with that.  Find out the module that it loads when running that distro (well besides i2o, of course)

 

The following is the relevant configuration options on i386 for I2O devices:

 

linux.i386.config:CONFIG_SCSI_DPT_I2O=m
linux.i386.config:# I2O device support
linux.i386.config:CONFIG_I2O=y
linux.i386.config:# CONFIG_I2O_CONFIG is not set
linux.i386.config:CONFIG_I2O_BLOCK=y
linux.i386.config:CONFIG_I2O_SCSI=m
linux.i386.config:# CONFIG_I2O_PROC is not set

 

I'm not sure what CONFIG_I2O_CONFIG or CONFIG_12O_PROC does, perhaps they might help?

 

You are using i386, right?

 

Cheers,

 

Bernard

---

From: [EMAIL PROTECTED] on behalf of Charles Galpin
Sent: Sun 15/01/2006 15:33
To: sisuite-users@lists.sourceforge.net
Subject: Re: [Sisuite-users] kernel BUG at include/linux/i2o.h:517!

Hi Bernard

On Jan 15, 2006, at 4:39 PM, Bernard Li wrote:

> Hi Charles:
>  
> I believe si_prepareclient uses the OS' kernel and generate a
> compatible initrd.img based on your system.
>  
> Have you tried using the stock kernel/initrd.img which came with
> SystemImager's boot-standard package to tftpboot?  That might actually
> work better.

yes, thats what kernel panics :( I did build from source though - i
just tried your prebuilt one and it panics too.

> The modules.dep message can be ignored, it never interferred with
> successful imaging of a system - we'll see about fixing that in the
> future.

Ok, i assumed that was the root cause. The resulting problem as it
didn't see my sata card (adaptec I2O). This does work in production
though...

> If that doesn't work, I recommend you try a newer version of
> SystemImager, eg. 3.6.2 or the code in branches/3.6.x.

Mmh, maybe I lied - i should have said 3.6.3 :0 I have been using
systemimager-3.6.3-1.src.rpm off that site you linked me to. That
change anything you say above?

charles



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=ick
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users