linux-kernel - Re: edd breaking vesafb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1221757806.26693.14.camel@plop>
Date:	Thu, 18 Sep 2008 19:10:06 +0200
From:	Pascal Terjan <pterjan@...driva.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: edd breaking vesafb

Le jeudi 18 septembre 2008 à 09:26 -0700, H. Peter Anvin a écrit :
> Pascal Terjan wrote:
> > Hello
> > 
> > I got a report of vesafb no longer working since edd is used on a
> > machine (Shuttle FN41SP).
> > It's a BIOS bug that was easily workarounded by calling set_video before
> > query_edd.
> > Does someone see some issue in doing that ?
> > 
> 
> Yes, it means that we won't get the status and error messages from 
> query_edd.  In fact, we changed the ordering specifically for this reason.

Indeed

> The VESA code and EDD code both use the boot code heap.  One could guess 
> that the problem is data left on the heap by the EDD code causing a 
> failure when combined with a bad BIOS.
> 
> Does this patch work for you?
> 

No it does not help

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/