<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Myles Watson escribió:
<blockquote
cite="mid:2831fecf0912210853l62fe37b5w47a7d7f98e48c4a0@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On Mon, Dec 21, 2009 at 9:15 AM, Knut Kujat <span
dir="ltr"><<a moz-do-not-send="true" href="mailto:knuku@gap.upv.es">knuku@gap.upv.es</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">Myles Watson escribió:
<div>
<div class="h5">
<blockquote type="cite"><br>
<br>
<div class="gmail_quote">On Mon, Dec 21, 2009 at 3:27 AM, Knut
Kujat <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:knuku@gap.upv.es" target="_blank">knuku@gap.upv.es</a>></span>
wrote: <br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"><br>
but I haven't changed anything but inserting some printk_spew into
"void dev_initialize(void)" to see where exactly jumps the exception
out.<br>
</div>
</blockquote>
<div>Did you try increasing the stack size? When you inserted
the
printk statements, were there any warnings about format strings not
matching the number of arguments? Have you tried disabling the
siblings yet?<br>
<br>
Thanks,<br>
Myles <br>
</div>
</div>
<br>
</blockquote>
<br>
</div>
</div>
Hello,<br>
<br>
yes increasing stack size helped with the printks.</div>
</blockquote>
<div>How big did you make it? Try making it bigger until it doesn't
make a difference any more.<br>
</div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">And yes I tried to
disable siblings by adding uses CONFIG_LOGICAL_PROCESSORS and default
CONFIG_LOGICAL_PROCESSORS=0 to the Options.lb file but it complains at
building time that this options is unkown so I uses LOGICAL_CPUS
instead (is it the same?) without results.</div>
</blockquote>
<div>You found the right one. Sorry I steered you wrong. All the
processors get initialized even with CONFIG_LOGICAL_CPUS=0? That's not
good. <br>
</div>
<div> </div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">Now I know that the the
exception comes up in the corresponding
init(dev) for the PCI: 00:02.0 device. So I disabled PCI 2.0 in the
device tree and it just doesn't has any effect even it tells me that
PCI 2.0 enabled 0 at boot times, it stucks at the same place. <br>
</div>
</blockquote>
<div>I don't think the init function is the problem. It's more
likely that something is going wrong much earlier, and just catches up
to you there. I would leave the device enabled.<br>
<br>
Thanks,<br>
Myles <br>
</div>
</div>
<br>
</blockquote>
Morning,<br>
<br>
stack_size = 0x4000 and seems to work fine.<br>
<br>
Sorry, I didn't explain myself, changing CONFIG_LOGICAL_CPUS to 0 made
the compile process fail in northbridge.c so I had to change it back.<br>
Yes disabling devices didn't make any difference so I leave them
enabled.<br>
<br>
hmmmm what else could I do?? <br>
<br>
THX,<br>
<br>
Knut Kujat.<br>
<br>
</body>
</html>