From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1RYkOT-0003RZ-F3 for mharc-grub-devel@gnu.org; Thu, 08 Dec 2011 15:16:37 -0500 Received: from eggs.gnu.org ([140.186.70.92]:55488) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RYkOQ-0003Lb-Gk for grub-devel@gnu.org; Thu, 08 Dec 2011 15:16:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RYkOP-0003Z1-6A for grub-devel@gnu.org; Thu, 08 Dec 2011 15:16:34 -0500 Received: from mail-fx0-f41.google.com ([209.85.161.41]:63353) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RYkOO-0003Yx-S0 for grub-devel@gnu.org; Thu, 08 Dec 2011 15:16:33 -0500 Received: by faaq22 with SMTP id q22so746801faa.0 for ; Thu, 08 Dec 2011 12:16:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=HvKSufHzmhGKU2rnEWou7X3nAArvZ1H9Egx5GP7XL6Y=; b=UsEm07nKOdkqCXnpcYsfPAnPwF8RLWEE3naJvGxHlsdTuImgY1l1KnLWc77kQloEj2 TcZ3B3yJ87aSJbPSxd/kcMnVqD7cOhVrd1SfA/ABx+jjiVp62DEe17kGpX5wVZ85IIp3 Ie2AGUsvLhgNlHJI7hGf5JbLxC4rGGEG+ZE0A= Received: by 10.180.84.33 with SMTP id v1mr7711806wiy.4.1323375389290; Thu, 08 Dec 2011 12:16:29 -0800 (PST) Received: from debian.x201.phnet (75-234.197-178.cust.bluewin.ch. [178.197.234.75]) by mx.google.com with ESMTPS id u3sm10179160wiu.10.2011.12.08.12.16.27 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 08 Dec 2011 12:16:28 -0800 (PST) Message-ID: <4EE11B19.6000300@gmail.com> Date: Thu, 08 Dec 2011 21:16:25 +0100 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111114 Icedove/3.1.16 MIME-Version: 1.0 To: The development of GNU GRUB Subject: Re: HP root-caues analysis for GRUB "Red screen of death" on DL120/DL360 G7 servers References: <6F28EE1C9AAED6468989841A3FB66CB44980B21C@Mail2.acmepacket.com> In-Reply-To: <6F28EE1C9AAED6468989841A3FB66CB44980B21C@Mail2.acmepacket.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.161.41 Cc: Iain Barker X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2011 20:16:35 -0000 > 1) Grub installs its own INT13 handler > 2) Near the end of the chain loading process, Grub loads an image of the Linux kernel into memory which wipes out their Int13 handler. > 3) Right before grub transfers control to the kernel to boot, grub makes a call to a function to turn off the floppy drive. > 4) The call to the floppy code then makes an Int13 call to the handler which has been overwritten by the kernel and thereby results in the red screen. > This text seems to be contradictory. INT13 handler is installed if drivemap is useful only with chainload. But then it mentions Linux loading. Also the call to stop floppy doesn't call BIOS: static inline void grub_stop_floppy (void) { grub_outb (0, GRUB_FLOPPY_REG_DIGITAL_OUTPUT); } May I see the configfile in question? Also GRUB does calculate the safe place based on memory layout, looking at code I see the problem that it's calculated before installing drivemap hook. While this should be fixed, I see no reason to use drivemap with Linux. > _end quoted text_ > > Regards, > Iain Barker - Platform Engineering, Acme Packet. > [yoshac@member.fsf.org] > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel > -- Regards Vladimir 'φ-coder/phcoder' Serbinenko