mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: Helge Hafting <helgehaf@aitel.hist.no>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.10 dies when X uses PCI radeon 9200 SE, binary search result
Date: Sun, 23 Jan 2005 00:01:13 +1100	[thread overview]
Message-ID: <21d7e99705012205012c95665@mail.gmail.com> (raw)
In-Reply-To: <41F21FA4.1040304@pD9F8757A.dip0.t-ipconnect.de>

> >>
> 
> That's certainly correct.
> 
> > Such issues
> > could crash (all) user apps, but shouldn't prevent the machine from
> > responding to sysrq sequences.
> 
> You emphasized the differences of the effects. But there is one reason in
> all cases which I know: int10 crashes X or even the whole kernel.
> 
> I could debug the problem to the following point:
> 
> 
> I could see, that X crashes in glibc 2.3.4 with kernel 2.4.x (not with
> kernel 2.6.x, x <= 10, x > 10 not tested) during the first malloc syscall
> after int10 to execute the function
> xf86MsgVerb(X_INFO,3,"my comment\n");
> 
> The crashes depend on different versions of used software:
> 
> glibc 2.3.3 or 2.3.4 with kernel 2.4.x
> glibc 2.3.2 with kernel > 2.6.9rc2
> 


Well if you can track down which patch in -rc2 causes it then we can
annoy the person who created it, if you build some kernels from the bk
snapshots it might help as -rc2 is quite large vs -rc1..

Dave.

  reply	other threads:[~2005-01-22 13:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.ks44mbo.ljgao4@ifi.uio.no>
     [not found] ` <fa.hinb9iv.s38127@ifi.uio.no>
2005-01-22  9:40   ` Andreas Hartmann
2005-01-22 13:01     ` Dave Airlie [this message]
2005-01-26 10:05       ` 2.6.10 dies when X uses PCI radeon 9200 SE, further " Helge Hafting
2005-01-30 11:16         ` Helge Hafting
2005-01-30 11:22           ` Dave Airlie
2005-01-30 14:43             ` Jon Smirl
2005-01-30 15:05             ` Jon Smirl
2005-01-30 16:32               ` Helge Hafting
2005-01-30 17:05                 ` Jon Smirl
2005-01-30 21:56                   ` Helge Hafting
2005-02-04  3:43                   ` 2.6.10 dies when X uses G550 Helge Hafting
2005-02-04  4:47                     ` Jon Smirl
2005-02-04  5:57                     ` Dave Airlie
2005-02-06 10:10                       ` Dave Airlie
2005-01-30 15:07             ` 2.6.10 dies when X uses PCI radeon 9200 SE, further binary search result Jon Smirl
     [not found] <fa.jfkohta.1il0fq0@ifi.uio.no>
     [not found] ` <fa.hh8592m.qji2ie@ifi.uio.no>
2005-01-21 20:05   ` 2.6.10 dies when X uses PCI radeon 9200 SE, " Andreas Hartmann
2005-01-21 22:09     ` Helge Hafting
2005-01-13 10:30 2.6.10 dies when X tries to initialize PCI radeon 9200 SE Helge Hafting
2005-01-13 11:00 ` John covici
2005-01-13 21:06   ` Dave Airlie
2005-01-15 18:57     ` Helge Hafting
2005-01-16 10:08       ` Dave Airlie
2005-01-16 10:50         ` Helge Hafting
2005-01-16 11:04           ` Jon Smirl
2005-01-16 11:07             ` Dave Airlie
2005-01-16 11:34               ` Jon Smirl
2005-01-16 11:41                 ` Dave Airlie
2005-01-21 18:26                   ` 2.6.10 dies when X uses PCI radeon 9200 SE, binary search result Helge Hafting
2005-01-21 18:49                     ` John covici

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=21d7e99705012205012c95665@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=andihartmann@01019freenet.de \
    --cc=helgehaf@aitel.hist.no \
    --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