mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H.Rosmanith (Kernel Mailing List)" <kernel@wildsau.idv.uni.linz.at>
To: kernel@wildsau.idv.uni.linz.at (H.Rosmanith)
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
Subject: Re: emm386 hangs when booting from linux
Date: Sun, 2 Mar 2003 11:29:54 +0100 (MET)	[thread overview]
Message-ID: <200303021029.h22ATsnP001379@wildsau.idv.uni.linz.at> (raw)
In-Reply-To: <200303021026.h22AQALn001315@wildsau.idv.uni.linz.at> from "H.Rosmanith" at "Mar 2, 3 11:26:10 am"

> 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


  reply	other threads:[~2003-03-02 10:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-28  3:18 H.Rosmanith (Kernel Mailing List)
2003-02-28  3:30 ` H.Rosmanith (Kernel Mailing List)
2003-02-28 22:54 ` Richard B. Johnson
2003-02-28 23:26   ` H.Rosmanith (Kernel Mailing List)
2003-02-28 23:26   ` Kasper Dupont
2003-02-28 23:43     ` H.Rosmanith (Kernel Mailing List)
2003-02-28 23:59       ` Kasper Dupont
2003-03-01  0:05         ` hr
2003-03-02 10:26         ` H.Rosmanith (Kernel Mailing List)
2003-03-02 10:29           ` H.Rosmanith (Kernel Mailing List) [this message]
2003-03-06 10:25           ` Denis Vlasenko

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=200303021029.h22ATsnP001379@wildsau.idv.uni.linz.at \
    --to=kernel@wildsau.idv.uni.linz.at \
    --cc=herp@wildsau.idv.uni.linz.at \
    --cc=kasperd@daimi.au.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    /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

all inboxes | Powered by JetHome®