All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deepak Manohar <mjdeepak@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Mark Hurenkamp <mark.hurenkamp@xs4all.nl>
Subject: Re: Trying fbcon in dom1,but take_over_console fails...
Date: Fri, 20 May 2005 08:13:59 -0700	[thread overview]
Message-ID: <fdef3c2405052008136d72c213@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3AA1@liverpoolst.ad.cl.cam.ac.uk>

Hi Mark,

 Was any progress made on this? Were you able to get X to run in one
of the user domains?

 If not what is the status? Maybe you could give me some pointers on
what needs to be done?

Thanks
Deepak


On 4/8/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> 
> > > I suspect you'd be better off getting the xencons to
> > register as ttyS0
> > > (xencons=ttyS0) so that it doesn't go anywhere near the
> > console, and
> > > compile in VT, VT_CONSOLE and DUMMY_CONSOLE.
> > Tried that, as well as disabling VGA_CONSOLE, but no
> > improvements :-(:-( however, when built as a module, it is
> > somewhat easier to debug this problem in fbcon, since dom1 is
> > still running after it segfaults, and I can still use dmesg
> > to see the printk's (strange that they don't appear on the
> > console...).
> 
> Do you actually need fbcon? You don't need it to run X in most setups.
> 
> [If you want the printk's to come out on the console, use the KERN_ALERT prefix]
> 
> 
> Ian
> 
> > >
> > > Please let us know how you get on.
> >
> > Ok, here's what I found so far:
> >
> > Using printk statements, I was able to find the culprit, it
> > seems to be the vc pointer which is not initialised properly.
> >
> > Here's the piece of code (from fbcon_startup):
> >
> > /* Setup default font */
> > if (!p->fontdata) {
> > if (!fontname[0] || !(font = find_font(fontname)))
> > font = get_default_font(info->var.xres,
> > info->var.yres);
> >
> > DPRINTK("fbcon_startup: ca\n");
> >
> > vc->vc_font.width = font->width;
> > vc->vc_font.height = font->height;
> > vc->vc_font.data = p->fontdata = font->data;
> > vc->vc_font.charcount = 256; /* FIXME Need
> > to support more fonts */
> >
> > DPRINTK("fbcon_startup: cb\n");
> >
> > }
> >
> > And the oops occurs between the two DPRINTK's...
> > So I added a check at startup:
> >
> > static const char *fbcon_startup(void)
> > {
> > const char *display_desc = "frame buffer device";
> > struct display *p = &fb_display[fg_console];
> > struct vc_data *vc = vc_cons[fg_console].d;
> > struct font_desc *font = NULL;
> > struct module *owner;
> > struct fb_info *info = NULL;
> > struct fbcon_ops *ops;
> > int rows, cols;
> > int irqres;
> >
> > DPRINTK("fbcon_startup... fg_console: %d, vc:
> > %d\n",fg_console,vc);
> >
> > This prints 0 for the fg_console (not necessarely a problem)
> > as well as vc...
> > which is defenately a problem since it is dereferenced later!
> >
> > Seems like the vc_cons is not setup right, I'll have to take
> > a look into vt.c I guess.
> > Could this be due to the missing ps/2 port on domU (since
> > they are assigned to dom0)?
> >
> > Will report back when I know more.
> >
> >
> > Regards,
> > Mark.
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  reply	other threads:[~2005-05-20 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08 10:32 Trying fbcon in dom1,but take_over_console fails Ian Pratt
2005-05-20 15:13 ` Deepak Manohar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-05  1:05 Mark Hurenkamp
2005-04-05  0:26 Ian Pratt
2005-04-07 22:38 ` Mark Hurenkamp

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=fdef3c2405052008136d72c213@mail.gmail.com \
    --to=mjdeepak@gmail.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=mark.hurenkamp@xs4all.nl \
    --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.