xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Sander Bogaert <sander.bogaert@elis.ugent.be>
Cc: xen-devel@lists.xen.org
Subject: Re: Latest Arndale Xen, dom0 kernel stuck on ASIX mac.
Date: Mon, 03 Jun 2013 13:28:57 +0100	[thread overview]
Message-ID: <51AC8C09.6020203@linaro.org> (raw)
In-Reply-To: <CANO7gZfE1aOGnS3FnZRBNrrqvnMx73hm0NqVXXHYfwtxv31w0w@mail.gmail.com>

On 06/01/2013 03:31 PM, Sander Bogaert wrote:

> Hi,
> 
> I was trying to update my Xen version and noticed I needed to use a
> newer dom0 kernel too ( took the one from Julien's arndale branch ). I
> got both and compiled them but I can't get the new kernel to boot. It
> keeps getting stuck at ( attached the whole boot log too ):
> 
> asix 1-3.2.4:1.0 (unregistered net_device): invalid hw address, using random
> asix 1-3.2.4:1.0 eth0: register 'asix' at usb-12110000.usb-3.2.4, ASIX
> AX88772 USB 2.0 Ethernet, d2:a5:dc:ad:09:b5
> 
> I tried setting another mac address in u-boot as stated on the wiki,
> one starting with '00:16:3e:...' but without result.
> 
> So I was wondering if anyone ran into the same issue yet? The kernel
> getting stuck seemingly because of a mac address?


If you look at few lines before you can see:
Waiting for root device /dev/sda1...

It seems that linux is unable to start the hard drive. Unfortunately, I
never try this configuration with Xen.

Does Xen hang? You can try triple CTRL-a and see if Xen answers.
Is linux/xen receive the SATA interrupt?

> Also I noticed that even using saveenv u-boot isn't keeping my changes
> to ethaddr and usbethaddr after a reboot. I'm using U-Boot
> 2013.01.-rc1-00001-g30dd996 (Apr 29 2013 - 11:09:40) for ARNDALE5250
> which still seems to be the one the Linaro guide says to use. Is this
> a bug in u-boot?


I didn't try recent U-boot. FYI, I'm using U-boot 2012.10-rc1.

Cheers,

Julien

  reply	other threads:[~2013-06-03 12:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01 14:31 Latest Arndale Xen, dom0 kernel stuck on ASIX mac Sander Bogaert
2013-06-03 12:28 ` Julien Grall [this message]
2013-06-04 19:48   ` Sander Bogaert
2013-06-04 21:11     ` Julien Grall
2013-06-05 19:23       ` Sander Bogaert
2013-06-05 20:58         ` Julien Grall
2013-06-06  8:51           ` Sander Bogaert
2013-06-06  8:52             ` Sander Bogaert
2013-06-06 10:37               ` Julien Grall
2013-06-07 14:40                 ` Sander Bogaert
2013-06-07 15:03                   ` Julien Grall
2013-06-07 18:09                     ` Sander Bogaert
2013-06-07 18:25                       ` Julien Grall
2013-06-07 19:58                         ` Sander Bogaert
2013-06-07 20:25                           ` Julien Grall
2013-06-07 20:35                             ` Sander Bogaert
2013-06-07 20:56                               ` Julien Grall
2013-06-07 21:51                                 ` Sander Bogaert
2013-06-07 22:44                                   ` Julien Grall
2013-06-08  7:57                                     ` Sander Bogaert
2013-06-10 10:45                                       ` Julien Grall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51AC8C09.6020203@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=sander.bogaert@elis.ugent.be \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).