mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Andreas Hartmann <andihartmann@01019freenet.de>,
	linux-kernel@vger.kernel.org, Jon Smirl <jonsmirl@gmail.com>
Subject: Re: 2.6.10 dies when X uses PCI radeon 9200 SE, further binary search result
Date: Sun, 30 Jan 2005 22:22:24 +1100	[thread overview]
Message-ID: <21d7e9970501300322ffdabe0@mail.gmail.com> (raw)
In-Reply-To: <20050130111634.GA9269@hh.idb.hist.no>

> 
> 
> After sorting out a stupid build problem, here is the result for
> the binary search for the crash.
> 2.6.9         crash
> 2.6.9-rc2     pci-oom
> 2.6.9-rc3     crash
> 2.6.9-rc2-bk7 crash
> 2.6.9-rc2-bk4 crash
> 2.6.9-rc2-bk2 pci-oom
> 2.6.9-rc2-bk3 krash in ifconfig
> 
> Up to 2.6.9-rc2-bk2 we don't get a crash, instead the X log shows this:
> 
> (EE) RADEON(0): [pci] Out of memory (-1007)
> 
> and gives up on drm in an orderly fashion.
> 2.6.9-rc2-bk4 crashes though.  As usual, the X log ends with:
> (II) LoadModule: "int10"
> (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
> (II) RADEON(0): initializing int10
> (**) RADEON(0): Option "InitPrimary" "on"
> (II) Truncating PCI BIOS Length to 53248
> 
> 2.6.9-rc2-bk3 wasn't tested further, because the kernel dies upon
> running "ifconfig" which must be some other temporary bug.
> X will probably be difficult without IPv4 anyway.
> 

Just another guess, but Jon could the PCI ROM patch mess up X's access
via the Int10 handler .. maybe if it isn't mapped properly..?

Dave.

  reply	other threads:[~2005-01-30 11:23 UTC|newest]

Thread overview: 16+ 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   ` 2.6.10 dies when X uses PCI radeon 9200 SE, " Andreas Hartmann
2005-01-22 13:01     ` Dave Airlie
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 [this message]
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
2005-01-30 19:00 Zoltan Boszormenyi

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