All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
	"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: irq problem with 3.3-rc3 on guest
Date: Mon, 26 Mar 2012 09:53:49 -0400	[thread overview]
Message-ID: <20120326135349.GB18285@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1202160059130.26469@vega-a.dur.ac.uk>

> >>So how does F17 do it now? Is all in the graphical mode (KMS?) and it never
> >>tries to hit text mode (so plymouth is on by default?)
> >
> >I was probably wrong about that. It was a separate non-kernel bug
> >that was stopping me getting a direct graphical boot. As the
> >backtrace happens some time but not others I am not longer
> >convinced about the graphical vs text boot link. The backtrace
> >occurs before the line
> >Feb 14 20:26:31 localhost kernel: [    2.611366] Console:
> >switching to colour frame buffer device 100x37
> >so it seems to be when the frame buffer first launches.
> >
> >>>somthing happening in the wrong order, such as the framebuffer starting
> >>>before the irq is properly set up.
> >>
> >>Hm, could you instrument xen-fbfront.c and see what the flow is during
> >>bootup and compare that when running it under F16? That might shed some
> >>light on this.
> >
> >I will have a look at what useful debugging I can put into
> >xen-fbfront.c - it might be hard for me to compare it with F16 but
> >the comparsion between a backtrace and non-backtrace boot might be
> >useful.
> 
> My first debugging attempt gives the values
> update_wanted=0 in_cons=0 in_prod=1 width=800 height=600

> just before the crash occurs. I am not sure how useful this is.

So how are you actually trying to install F17?
I tried:
 virt-install --name F17 --ram 1024 --disk /dev/vg_guest/f17_32 --paravirt --location http://build/tftpboot/f17-i386/

and it showed the text console, and then rebooted thinking it was complete. 
When using a manual guest config:
kernel="/root/vmlinuz-PAE"
ramdisk="/root/initrd-PAE.img"
append="console=hvc0 loglevel=8 root=http://build/tftpboot/f17-i386"
memory=1024
maxvcpus = 2
vcpus = 2
disk = ['phy:/dev/vg_guest/f17_32,xvda,w']
vif = [ 'type=netfront, bridge=switch' ]
vfb = [ 'vnc=1, vnclisten=0.0.0.0 ,vncunused=1']

I get this:
  5.680395] Broadcom NetXtreme II iSCSI Driver bnx2i v2.7.0.3 (Jun 15, 2011)
[    5.681923] iscsi: registered transport (bnx2i)
[    5.696419] iscsi: registered transport (be2iscsi)
[    5.763271] dracut: FATAL: No or empty root= argument
[    5.764158] dracut: Refusing to continue
[    5.769524] dracut Warning: Signal caught!
[    5.772973] dracut Warning: dracut: FATAL: No or empty root= argument
[    5.776138] dracut Warning: dracut: Refusing to continue
[    5.782548] init used greatest stack depth: 5480 bytes left
[    5.783425] Kernel panic - not syncing: Attempted to kill init!

so is there a new syntax for the root parameter now that is a LiveCD?

  reply	other threads:[~2012-03-26 13:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-12 21:33 irq problem with 3.3-rc3 on guest M A Young
2012-02-13 12:53 ` Ian Campbell
2012-02-13 14:12   ` M A Young
2012-02-14 14:00     ` Konrad Rzeszutek Wilk
2012-02-14 21:48       ` M A Young
2012-02-16  1:01         ` M A Young
2012-03-26 13:53           ` Konrad Rzeszutek Wilk [this message]
2012-03-27 22:14             ` M A Young
2012-03-28 16:20               ` [Fedora-xen] Fedora Core 17 Xorg can't use /dev/fb0 when using Cirrus Logic VGA or Xen PVFB driver, Was:Re: [Xen-devel] " Konrad Rzeszutek Wilk
2012-04-05  0:11                 ` M A Young
2012-04-05 12:48                   ` [Fedora-xen] [Xen-devel] Fedora Core 17 Xorg can't use /dev/fb0 when using Cirrus Logic VGA or Xen PVFB driver, Was:Re: " Konrad Rzeszutek Wilk
2012-04-05 13:01                     ` M A Young

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=20120326135349.GB18285@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=konrad@darnok.org \
    --cc=m.a.young@durham.ac.uk \
    /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.