mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@01019freenet.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x oops with X
Date: Sun, 06 Feb 2005 07:35:13 +0100	[thread overview]
Message-ID: <cu4dr1$l4$1@pD9F879A4.dip0.t-ipconnect.de> (raw)
In-Reply-To: <fa.kmfmtrp.1a16aaf@ifi.uio.no>

Andreas Hartmann wrote:
> Andreas Hartmann wrote:
> [...]
>> But now, the question is:
>> Why does X crash running kernel 2.4.x with glibc 2.3.4 and not with kernel
>> 2.6.10? Why does X run fine using kernel 2.4 and 2.6 with glibc 2.3.3?
>> 
>> ----------------------------------------------
>> 	|		glibc
>> 	|	2.3.3		2.3.4
>> ------|-------------------------------------
>> kernel|
>> 2.4	|	X ok		X segfaults
>> 2.6	|	X ok		X ok
> 
> 
> Meanwhile, I could find where X crashes using glibc 2.3.4 with kernel 2.4.
> It's this piece of code in linux_vm86.c:267
> 
> static int
> vm86_rep(struct vm86_struct *ptr)
> {
>     int __res;
> 
> #ifdef __PIC__
>     /* When compiling with -fPIC, we can't use asm constraint "b" because
>        %ebx is already taken by gcc. */
>     __asm__ __volatile__("pushl %%ebx\n\t"
>                          "movl %2,%%ebx\n\t"
>                          "movl %1,%%eax\n\t"
>                          "int $0x80\n\t"
>                          "popl %%ebx"
>                          :"=a" (__res)
>                          :"n" ((int)113), "r" ((struct vm86_struct *)ptr));
> #else
>     __asm__ __volatile__("int $0x80\n\t"
>                          :"=a" (__res):"a" ((int)113),
>                          "b" ((struct vm86_struct *)ptr));
> #endif
> 
>             if (__res < 0) {
>                 errno = -__res;
>                 __res = -1;
>             }
>             else errno = 0;
>             return __res;
> }
> 
> 
> The function ExecX86int10 (vbe.c) calls do_vm86 (linux_vm86.c), which
> calls vm86_rep (linux_vm86.c).
> 
> 
> I don't understand, why this piece of assembler code works fine with glibc
> 2.3.3, but not with glibc 2.3.4, running kernel 2.4.x. It works fine again
> with kernel 2.6.

Solution for this problem can be found meanwhile at
https://bugs.freedesktop.org/show_bug.cgi?id=2431


Kind regards,
Andreas Hartmann

  parent reply	other threads:[~2005-02-06  6:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.gv4g3v7.1ng0thr@ifi.uio.no>
     [not found] ` <fa.kmfmtrp.1a16aaf@ifi.uio.no>
2005-01-08 16:18   ` Andreas Hartmann
2005-01-13 11:30     ` Marcelo Tosatti
2005-02-06  6:35   ` Andreas Hartmann [this message]
     [not found] <fa.kuv2u3i.hhma1k@ifi.uio.no>
     [not found] ` <fa.f87d0no.fk6a9u@ifi.uio.no>
2005-01-07 23:21   ` Andreas Hartmann
     [not found]     ` <20050108014844.GB3210@redhat.com>
     [not found]       ` <41DF98F4.5050805@pD9F8750A.dip0.t-ipconnect.de>
2005-01-10 10:58         ` Marcelo Tosatti
     [not found] <fa.m16skii.8mkd12@ifi.uio.no>
     [not found] ` <fa.f3n91fn.b42ahv@ifi.uio.no>
2005-01-07 18:13   ` Andreas Hartmann
2005-01-07 17:01     ` Marcelo Tosatti
2005-01-07 19:53       ` Dave Jones
2005-01-07  9:03 Andreas Hartmann
2005-01-07 11:30 ` Marcelo Tosatti

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='cu4dr1$l4$1@pD9F879A4.dip0.t-ipconnect.de' \
    --to=andihartmann@01019freenet.de \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome