All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Reppert <arashi@sacredchao.net>
To: linux-kernel@vger.kernel.org
Subject: PCI ROM resource allocation issue with 2.6.17-rc2
Date: Mon, 24 Apr 2006 00:02:41 -0400	[thread overview]
Message-ID: <1145851361.3375.20.camel@minerva> (raw)

I've been running 2.6.12-rc2-mm3 for a long time.  Recently I upgraded
a bunch of OS packages (Debian unstable), so I thought I may as well
upgrade the kernel, too.  I've got a dual-head setup driven by a Radeon
9200 and a Radeon 7000.  When I booted 2.6.17-rc2, X never came up; I
got "RADEON: Cannot read V_BIOS" and "RADEON: VIdeo BIOS not detected
in PCI space!" for the RADEON 7000, and it eventually gets in a loop of
spitting out "RADEON: Idle timed out, resetting engine ... " messages
in Xorg.log.  Doing a diff of working and broken logs uncovered that the
Radeon 7000's PCI ROM resource area had moved from ff8c000 to c6900000.
Once I removed the Radeon 7000 screen from the Xorg config, X came up fine
on the one head.  Adding stupid amounts of printks to the PCI subsystem in
.17-rc2 uncovered that at some point, the ROM area is discovered to be
at ff8c0000, but is later reallocated to c6900000.

I've also got a Promise PDC20268 whose expansion ROM seems to have made a
similar move (from ff8f8000 to c6920000), but the ATA devices attached to
that controller seem to work fine under 2.6.17-rc2.

I have a copy of relevant dmesg and lspci output, as well as a copy of
Xorg.log files, at http://sacredchao.net/~arashi/pci-problem/ .  I'll
try to binary-search for the last version of the kernel that works later
this week (hopefully by Tuesday afternoon), I just haven't had time to
since I've discovered the problem.

Matt


             reply	other threads:[~2006-04-24  4:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24  4:02 Matthew Reppert [this message]
2006-04-24  5:21 ` PCI ROM resource allocation issue with 2.6.17-rc2 Andrew Morton
2006-04-24  5:54   ` Dave Airlie
2006-04-24 17:07     ` Linus Torvalds
2006-04-24 17:16       ` Arjan van de Ven
2006-04-24 17:28         ` Linus Torvalds
2006-04-26  1:23           ` Dave Airlie
2006-04-26  2:10             ` Jon Smirl
2006-04-24 17:01   ` Linus Torvalds
2006-04-26  3:28     ` Dave Airlie
2006-04-26  3:40       ` Debian Kernel with Squash and UnionFS installed Joshua Perrymon
2006-04-26  5:05       ` PCI ROM resource allocation issue with 2.6.17-rc2 Linus Torvalds
2006-04-26  5:56         ` Dave Airlie
2006-04-24  5:28 ` Matthew Reppert
2006-04-24 19:24   ` Jon Smirl

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=1145851361.3375.20.camel@minerva \
    --to=arashi@sacredchao.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.