Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 2 Mar 2003 05:21:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 2 Mar 2003 05:21:09 -0500 Received: from wildsau.idv.uni.linz.at ([213.157.128.253]:13457 "EHLO wildsau.idv.uni.linz.at") by vger.kernel.org with ESMTP id ; Sun, 2 Mar 2003 05:21:08 -0500 From: "H.Rosmanith (Kernel Mailing List)" Message-Id: <200303021029.h22ATsnP001379@wildsau.idv.uni.linz.at> Subject: Re: emm386 hangs when booting from linux In-Reply-To: <200303021026.h22AQALn001315@wildsau.idv.uni.linz.at> from "H.Rosmanith" at "Mar 2, 3 11:26:10 am" To: kernel@wildsau.idv.uni.linz.at (H.Rosmanith) Date: Sun, 2 Mar 2003 11:29:54 +0100 (MET) Cc: kasperd@daimi.au.dk, kernel@wildsau.idv.uni.linz.at, root@chaos.analogic.com, linux-kernel@vger.kernel.org, herp@wildsau.idv.uni.linz.at X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 797 Lines: 18 > I've still not found a solution, but at least I know what's happening > when emm386 or similar crash the system. e.g., when starting "loadlin" > (with no parameters!) the system will hang too. Reason is that loadlin > will generate an int 0x13, which is the general protection fault. > I wonder *why*. Well, the int 0x13 handler I wrote just writes just to be a bit more specific: yes, it is somehow related to protected mode switching, but the in eflags, the VM86 bit is clear! So I dont understand what's causing the fault. best regards, herbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/