From: Matt Domsch <Matt_Domsch@dell.com>
To: Christian Kujau <evil@g-house.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Chuck Ebbert <76306.1226@compuserve.com>
Subject: Re: Oops in 2.6.10-rc1 (almost solved)
Date: Sat, 13 Nov 2004 20:58:14 -0600 [thread overview]
Message-ID: <20041114025814.GA20342@lists.us.dell.com> (raw)
In-Reply-To: <20041113142835.GA9109@lists.us.dell.com>
On Sat, Nov 13, 2004 at 08:28:35AM -0600, Matt Domsch wrote:
> It still doesn't explain why Christian's BIOS reports more devices
> than he has, that's still UI, so don't re-apply the edd.S patch just reverted.
Alexander van Heukelum noted to me that addw here modifies CF, so I
think something like should fix that. Christian, if you're in a
position to test this, I'd really appreciate it. You've been a
fantastic bug reporter / tester!
Not ready for Linus yet, and you'll need to re-apply the previous
edd.S patch which is now reverted in Linus's tree. As your BIOS
reports via CHECK EXTENSIONS PRESENT that you've got more devices than
you actually have, hopefully the int13 EXTENDED READ won't succeed for
non-existant devices anymore, and then neither will the READ SECTORS
call.
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
===== arch/i386/boot/edd.S 1.3 vs edited =====
--- 1.3/arch/i386/boot/edd.S 2004-10-20 03:37:11 -05:00
+++ edited/arch/i386/boot/edd.S 2004-11-13 20:31:58 -06:00
@@ -58,8 +58,12 @@
sti # work around buggy BIOSes
popw %dx
popw %si
- addw $EDD_DEV_ADDR_PACKET_LEN, %sp # remove packet from stack
- jnc edd_mbr_store_sig
+ pushfl # save EFLAGS into ebx
+ popl %ebx # because addw modifies CF
+ addw $EDD_DEV_ADDR_PACKET_LEN, %sp # remove packet from stack
+ pushl %ebx # get back right CF
+ popfl
+ jnc edd_mbr_store_sig
# otherwise, fall through to the legacy read function
edd_mbr_read_sectors:
next prev parent reply other threads:[~2004-11-14 2:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 3:45 Oops in 2.6.10-rc1 (almost solved) Chuck Ebbert
2004-11-13 14:28 ` Matt Domsch
2004-11-13 18:55 ` Matt Domsch
2004-11-14 2:58 ` Matt Domsch [this message]
2004-11-14 4:43 ` Linus Torvalds
2004-11-14 11:45 ` Christian
2004-11-14 20:02 ` Christian Kujau
2004-11-14 21:55 ` Matt Domsch
2004-11-15 12:41 ` Oops in 2.6.10-rc1 (solved) Christian Kujau
[not found] <4180F026.9090302@g-house.de>
2004-11-07 16:57 ` Oops in 2.6.10-rc1 Linus Torvalds
2004-11-07 18:31 ` Christian Kujau
2004-11-07 23:45 ` Christian Kujau
2004-11-08 1:16 ` Linus Torvalds
2004-11-08 13:01 ` Christian Kujau
2004-11-08 18:13 ` Linus Torvalds
2004-11-08 20:59 ` Christian Kujau
2004-11-08 23:49 ` Christian Kujau
2004-11-09 1:31 ` Christian Kujau
2004-11-09 7:40 ` Pekka Enberg
2004-11-09 12:33 ` Christian Kujau
2004-11-09 17:26 ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau
2004-11-09 18:53 ` Linus Torvalds
2004-11-09 23:30 ` Christian Kujau
2004-11-09 23:40 ` Matt Domsch
2004-11-10 0:21 ` Christian Kujau
2004-11-10 1:01 ` Linus Torvalds
2004-11-11 22:43 ` Matt Domsch
2004-11-11 22:53 ` Linus Torvalds
2004-11-11 22:55 ` Matt Domsch
2004-11-12 0:27 ` Christian Kujau
2004-11-12 0:49 ` Linus Torvalds
2004-11-12 1:27 ` Christian Kujau
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=20041114025814.GA20342@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=76306.1226@compuserve.com \
--cc=evil@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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