Even if I am having the feeling of talking all by myself, I debugged the kernel
a little and I found why my XEN machine is not starting.
The problem is that, during the boot phase, a conflict in some region of memory
is hit and then the function reserve_region_with_split in kernel/resource.c
tries to fix this conflict.
In particular, the second and last address you see in the boot log, keeps
looping:
> static void __init __reserve_region_with_split(struct resource *root,
> resource_size_t start, resource_size_t end,
> const char *name)
> {
> …
> ...
> if (conflict->start > start)
> __reserve_region_with_split(root, start, conflict->start-1, name);
> if (conflict->end < end)
> __reserve_region_with_split(root, conflict->end+1, end, name);
> }
This function is at line 753 in kernel/resource.c
I think the conflict cannot be "fixed" (somehow, I don't even know what I'm
saying) but my idea is that
there is something bad here, with some resource.
Is there a way to understand what resource is giving problems? Or to get a
better understanding on what's going on?
Thank you again :p
--
Fabiano Francesconi [GPG key: 0x81E53461]
On martedì 8 novembre 2011 at 13:35, Fabiano Francesconi wrote:
> I was able to dump the bootlog of my working kernel, you can find it here:
> http://cl.ly/450I3o2U2q0W3C0I1g06
>
> I think the problem resides in between the following two lines:
>
> > Expanded resource reserved due to conflict with PCI Bus 0000:00
> > Switching to clocksource xen
>
>
>
>
> I saw that on my "hanging" kernel I'm not getting the "Switching to.."
> message while on the working one I do.
> Do you know what may be the culprit? I'm pretty much willing to debug the
> kernel a little bit but I can't find the set of instructions
> of the boot, in particular I don't know where are the calls to those
> functions and there is way too much code for me to read.
>
> Can somebody help me to sort this out? Thanks!
>
> --
> Fabiano Francesconi [GPG key: 0x81E53461]
>
>
> On lunedì 7 novembre 2011 at 15:18, Fabiano Francesconi wrote:
>
> > Thank you Niall but I cannot find that precise symbol in the kernel, but I
> > did play with some of the i2c settings but I did get luck so far.
> >
> > I was able to retrieve a full log of my boot that you can find here:
> > http://cl.ly/3i3U1d0Q2t472Z3C3x1q that refers to a kernel 3.0.7
> >
> > I, then, tried to compile a kernel using a configuration I found on the
> > internet that leads to a similar output (and situation) but raises a panic.
> > You can find the bootlog here: http://cl.ly/150j032l1e3x0Q3S1l3I
> >
> > Anybody has any idea? a clue? a suggestion? a thought to share?
> >
> > Thank you
> >
> > --
> > Fabiano Francesconi [GPG key: 0x81E53461]
> >
> >
> > On lunedì 7 novembre 2011 at 11:27, Niall Fleming wrote:
> >
> > > I had a an issue with i2c_i810 kernel driver, taking this driver out of
> > > the kernel entirely
> > > made the issue go away.
> > >
> > > Niall Fleming BSc. (Hons)
> > > Systems Administrator
> > > Webanywhere Limited
> > >
> > > Phone: 0800 862 0131 Ext: 203
> > > Web: http://www.webanywhere.co.uk
> > >
> > > Aire Valley Business Centre, Lawkholme Lane, Keighley, BD21 3BB
> > > Registered in England with company number 4881346
> > > On 06/11/2011 21:26, Flavio wrote:
> > > > On 6 November 2011 22:02, Fabiano Francesconi
> > > > <fabiano.francesconi@xxxxxxxxx> (mailto:fabiano.francesconi@xxxxxxxxx)
> > > > wrote:
> > > > > Hi Flavio, me and Alessandro are Gentoo users as well (you can find
> > > > > me on #gentoo-it chan @ Freenode). I reply to you since me and
> > > > > Alessandro have the same issue on both of our systems. We own the
> > > > > same machine bought from Abaco Computers. It runs an Atom Intel 330
> > > > > processor so, actually, it runs on paravirtualisation. Your
> > > > > configuration is the same (and mandatory to run a dom0 kernel, to be
> > > > > honest) and it should definitively work. The problem is that there is
> > > > > no error during the boot as you can see from the picture. We are
> > > > > trying to understand where the problem is but no clue, zero ideas.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hi! I actually have seen the screenshot. It is of course nearly
> > > > impossible to understand the reason of this behaviour if no errors
> > > > appear. I have an absurd problem too, as one of my previous email says.
> > > > The only thing that comes on my mind now is that some kernel module
> > > > could be a disturb to the dom0 configuration. The problem is to know
> > > > what this module is. Bye!
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@xxxxxxxxxxxxxxxxxxx (mailto:Xen-users@xxxxxxxxxxxxxxxxxxx)
> > > http://lists.xensource.com/xen-users
> >
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home