From: Jeremy Fitzhardinge <jeremy@goop.org>
To: deshantm@gmail.com
Cc: xen-devel mailing list <xen-devel@lists.xensource.com>,
Aviv Grafi <aviv@neocleus.com>
Subject: Re: pv_ops dom0 testing
Date: Mon, 01 Dec 2008 15:19:31 -0800 [thread overview]
Message-ID: <49347103.6010705@goop.org> (raw)
In-Reply-To: <1e16a9ed0811291505s14b84912n7e222a021654d611@mail.gmail.com>
Todd Deshane wrote:
> On Sat, Nov 29, 2008 at 5:32 PM, Aviv Grafi <aviv@neocleus.com> wrote:
>
>> I solved this one by adding "console=hvc0 earlyprintk=xen" to the dom0
>> kernel boot line (thanks to Jeremy Fitzhardinge [jeremy@goop.org]).
>>
>
> Thanks again Aviv. I am really close now. The screen still shows nothing,
> but the debug output has the dom0 kernel boot.
> (Not sure why that would be... any thoughts?)
>
> In the debug output however I successfully get to the the
> (initramfs) prompt.
>
> Full output attached, but some interesting parts inline:
>
> (initramfs)cat /proc/cmdline
> root=/dev/sda1 ro console=tty0 xencons=ttyS0,115200 console=hvc0 earlyprintk=xen
>
> (initramfs) cat /proc/modules
> ata_piix 33586 1 - Loading 0xffffffffa0127000
> libata 196576 1 ata_piix, Live 0xffffffffa00f5000
> scsi_mod 184792 1 libata, Live 0xffffffffa00c5000
> r8169 46084 0 - Live 0xffffffffa00b7000
> mii 14464 1 r8169, Live 0xffffffffa00b1000
> tg3 139396 0 - Live 0xffffffffa008c000
> libphy 32896 1 tg3, Live 0xffffffffa007e000
> ehci_hcd 46726 1 - Loading 0xffffffffa0070000
> uhci_hcd 34037 1 - Loading 0xffffffffa0062000
> usbcore 174512 3 ehci_hcd,uhci_hcd, Live 0xffffffffa0035000
> thermal 27552 0 - Live 0xffffffffa002c000
> processor 55224 1 thermal, Live 0xffffffffa0019000
> fan 13832 0 - Live 0xffffffffa0013000
> fuse 65728 1 - Live 0xffffffffa0000000
>
> a listing of /dev doesn't show any sd* devices.
>
What's your scsi host controller?
USB is known to have problems, so I generally disable it for now, until
I've worked out what's failing. You have an oops in your trace which
could be leaving other things in a bad state.
> So I am guessing I am running into a driver issue at this
> point. I will dig around more and compare my working
> vanilla linux config with the dom0 kernel to see if there
> is something missing in my dom0 kernel.
>
Yes, that would be interesting to compare.
> Thanks for the help so far and if anything comes to mind
> why I don't see console output on the screen (and only in
> the debug output) that would be helpful to me.
>
> I'll report back on progress.
>
> If there are any obvious known workarounds, problems, bugs etc.
> let me know. I know that the pv_ops dom0 kernel is very much in
> development, but I am willing to try to work through that.
>
Thanks for playing with this.
J
next prev parent reply other threads:[~2008-12-01 23:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 21:08 pv_ops dom0 testing Todd Deshane
2008-11-29 21:38 ` Aviv Grafi
2008-11-29 22:16 ` Todd Deshane
2008-11-29 22:32 ` Aviv Grafi
2008-11-29 23:05 ` Todd Deshane
2008-12-01 23:19 ` Jeremy Fitzhardinge [this message]
2008-12-02 2:49 ` Todd Deshane
-- strict thread matches above, loose matches on Subject: below --
2008-12-03 12:16 Andrew Lyon
2008-12-03 12:32 ` Boris Derzhavets
2008-12-03 15:08 ` Andrew Lyon
2008-12-03 15:37 ` Todd Deshane
2008-12-03 16:36 ` Andrew Lyon
2008-12-03 16:43 ` Todd Deshane
2008-12-03 17:10 ` Andrew Lyon
2008-12-03 17:49 ` Boris Derzhavets
2008-12-03 18:03 ` Andrew Lyon
2008-12-03 18:48 ` Boris Derzhavets
2008-12-03 18:55 ` Todd Deshane
2008-12-03 19:34 ` Andrew Lyon
2008-12-03 19:39 ` Andrew Lyon
2008-12-03 20:16 ` Jeremy Fitzhardinge
2008-12-03 17:36 Boris Derzhavets
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=49347103.6010705@goop.org \
--to=jeremy@goop.org \
--cc=aviv@neocleus.com \
--cc=deshantm@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.