From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: EDD failures since edd=off patch
Date: Thu, 10 Feb 2005 15:11:52 +0100 [thread overview]
Message-ID: <420B6BA8.1040808@gmx.net> (raw)
Hi Matt,
it seems the edd=off patch has caused some problems with
some machines I have access to. They simply don't boot
anymore unless I specify edd=foo. foo can be {off,skip,bar}
so it seems the hang on boot is related to the parser
not finding the parameter it is looking for.
I looked through the code some days ago and it seemed to
me that the register used to iterate through the command
line buffer only got its lower 16 bit reset before calling
into the BIOS. I don't have the code handy right now,
but I can look later if the hints I gave are insufficient.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next reply other threads:[~2005-02-10 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 14:11 Carl-Daniel Hailfinger [this message]
2005-02-10 17:23 ` EDD failures since edd=off patch Matt Domsch
2005-02-11 2:59 ` Carl-Daniel Hailfinger
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=420B6BA8.1040808@gmx.net \
--to=c-d.hailfinger.devel.2005@gmx.net \
--cc=Matt_Domsch@dell.com \
--cc=linux-kernel@vger.kernel.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