public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
To: Simon Richard Grint <rgrint@tall.compsoc.man.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: arch/i386/boot/video.S hang
Date: Fri, 17 Jun 2005 17:25:57 -0700	[thread overview]
Message-ID: <20050617172557.A25812@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050616175851.GA22103@mrtall.compsoc.man.ac.uk>; from rgrint@tall.compsoc.man.ac.uk on Thu, Jun 16, 2005 at 06:58:51PM +0100

On Thu, Jun 16, 2005 at 06:58:51PM +0100, Simon Richard Grint wrote:
> On Thu, Jun 16, 2005 at 10:33:41AM -0700, Venkatesh Pallipadi wrote:
> > What boot loader are you using. grub/lilo?
> 
> The same thing happens with either grub or lilo, but I'm using grub at 
> present
>  
> > Does it work with CONFIG_VIDEO_SELECT disabled in your kernel CONFIG?
> 
> It works fine if CONFIG_VIDEO_SELECT is disabled.  Even with 
> CONFIG_VIDEO_SELECT enabled, the problem only arises if I pass a vga= 
> parameter to the kernel
> 
> Thanks for your help
> 

This one continues to be mysterious.

One reason I could think of: VBE call 4f15:0s is storing more than 128 bytes on this platform. With the base address at 0x440, it can write much longer, without affecting anything else in zero page. But, at 0x140 it overwrites some other fields.

But, that doesn't explain why it only fails when vga=<num> is passed. For the above theory it should fail whenever VIDEO_SELECT is enabled.

Can you try some other address higher than 0x440 and less than 0x600 for and see whether it works? Or you can also try and print complete boot_params[] at some place in arch/i386/kernel/setup.c:setup_arch() in the case where it runs fine (with 0x440) and send me the log.

Thanks,
Venki

      reply	other threads:[~2005-06-18  0:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 22:05 arch/i386/boot/video.S hang Simon Richard Grint
2005-06-16 17:33 ` Venkatesh Pallipadi
2005-06-16 17:58   ` Simon Richard Grint
2005-06-18  0:25     ` Venkatesh Pallipadi [this message]

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=20050617172557.A25812@unix-os.sc.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgrint@tall.compsoc.man.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox