dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41265] KMS does not work on Radeon HD6700M
Date: Sat, 04 Aug 2012 16:14:09 +0000	[thread overview]
Message-ID: <bug-41265-502-Tr5isIhyxY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-41265-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=41265

--- Comment #20 from Alexander E. Patrakov <patrakov@gmail.com> 2012-08-04 16:14:09 UTC ---
I think that the card does have its BIOS, and the problem is really related to
a misconfigured PCI bridge. Please take this with a grain of salt, as I am not
a kernel hacker.

Some snippets from my dmesg that IMHO confirm this:

(just an interesting line, I didn't try this suggestion)
[    0.701044] PCI: Using host bridge windows from ACPI; if necessary, use
"pci=nocrs" and report a bug

(here is the Radeon card)
[    0.722007] pci 0000:16:00.0: [1002:6740] type 00 class 0x030000
[    0.722073] pci 0000:16:00.0: reg 10: [mem 0xb0000000-0xbfffffff 64bit pref]
[    0.722125] pci 0000:16:00.0: reg 18: [mem 0xc0200000-0xc021ffff 64bit]
[    0.722159] pci 0000:16:00.0: reg 20: [io  0x5000-0x50ff]
[    0.722226] pci 0000:16:00.0: reg 30: [mem 0xfffe0000-0xffffffff pref]
[    0.722395] pci 0000:16:00.0: supports D1 D2

(and this is the bridge before it)
[    0.723054] pci 0000:15:03.0: PCI bridge to [bus 16-16]
[    0.723124] pci 0000:15:03.0:   bridge window [io  0x5000-0x5fff]
[    0.723132] pci 0000:15:03.0:   bridge window [mem 0xc0200000-0xc02fffff]
[    0.723149] pci 0000:15:03.0:   bridge window [mem 0xb0000000-0xbfffffff
64bit pref]

(this is vgaarb)
[    0.743085] vgaarb: device added:
PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[    0.743186] vgaarb: device added:
PCI:0000:16:00.0,decodes=io+mem,owns=none,locks=none
[    0.743265] vgaarb: loaded
[    0.743313] vgaarb: bridge control possible 0000:16:00.0
[    0.743367] vgaarb: no bridge control possible 0000:00:02.0

(here the kernel complains about the bug that ultimately leads to unreadability
of the ROM)
[    0.773497] pci 0000:16:00.0: no compatible bridge window for [mem
0xfffe0000-0xffffffff pref]

(and tries to fix it up? still not good enough)
[    0.775668] pci 0000:16:00.0: BAR 6: assigned [mem 0xc0240000-0xc025ffff
pref]
[    0.775745] pci 0000:15:03.0: PCI bridge to [bus 16-16]
[    0.775805] pci 0000:15:03.0:   bridge window [io  0x5000-0x5fff]
[    0.775872] pci 0000:15:03.0:   bridge window [mem 0xc0200000-0xc02fffff]
[    0.775937] pci 0000:15:03.0:   bridge window [mem 0xb0000000-0xbfffffff
64bit pref]

(so we still end up with lost resources)
[    0.778723] pci_bus 0000:15: resource 0 [io  0x3000-0x5fff]
[    0.778725] pci_bus 0000:15: resource 1 [mem 0xb0000000-0xc02fffff]
[    0.778726] pci_bus 0000:15: resource 2 [mem 0xd4400000-0xd44fffff 64bit
pref]
[    0.778728] pci_bus 0000:16: resource 0 [io  0x5000-0x5fff]
[    0.778730] pci_bus 0000:16: resource 1 [mem 0xc0200000-0xc02fffff]
[    0.778731] pci_bus 0000:16: resource 2 [mem 0xb0000000-0xbfffffff 64bit
pref]

So the main question is: why doesn't vgaarb (or who really has this job)
reconfigure the bridge so that radeon can read the ROM?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-08-04 16:14 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 15:48 [Bug 41265] New: KMS does not work on Radeon HD6700M bugzilla-daemon
2011-09-27 15:49 ` [Bug 41265] " bugzilla-daemon
2011-09-29 18:53 ` bugzilla-daemon
2011-09-29 18:54 ` bugzilla-daemon
2011-09-29 19:26 ` bugzilla-daemon
2011-10-13 17:36 ` bugzilla-daemon
2011-11-03  3:40 ` bugzilla-daemon
2011-11-04 15:37 ` bugzilla-daemon
2011-11-14 21:26 ` bugzilla-daemon
2012-01-05  9:58 ` bugzilla-daemon
2012-01-05 10:14 ` bugzilla-daemon
2012-01-10 13:59 ` bugzilla-daemon
2012-01-10 14:55 ` bugzilla-daemon
2012-03-09 13:04 ` bugzilla-daemon
2012-05-10 17:11 ` bugzilla-daemon
2012-05-10 17:14 ` bugzilla-daemon
2012-07-27  3:39 ` bugzilla-daemon
2012-07-27  5:08 ` bugzilla-daemon
2012-07-27  5:16 ` bugzilla-daemon
2012-07-30  8:45 ` bugzilla-daemon
2012-07-30 13:37 ` bugzilla-daemon
2012-08-04 16:14 ` bugzilla-daemon [this message]
2012-08-04 16:32 ` bugzilla-daemon
2012-08-04 16:35 ` bugzilla-daemon
2012-08-04 17:02 ` bugzilla-daemon
2012-08-09 21:12 ` bugzilla-daemon
2012-08-09 21:14 ` [Bug 41265] Radeon KMS does not work on thunderbolt media dock bugzilla-daemon
2012-08-10 12:11 ` bugzilla-daemon
2012-08-10 13:50 ` bugzilla-daemon
2012-08-10 17:44 ` bugzilla-daemon
2012-08-10 17:46 ` bugzilla-daemon
2012-08-12 15:40 ` bugzilla-daemon
2012-08-14 15:30 ` bugzilla-daemon
2012-08-14 17:05 ` bugzilla-daemon
2012-08-14 18:38 ` bugzilla-daemon
2012-08-15  3:20 ` bugzilla-daemon
2012-08-16  5:34 ` bugzilla-daemon
2012-08-16  8:39 ` bugzilla-daemon
2012-08-16  9:26 ` bugzilla-daemon
2012-08-16 10:08 ` bugzilla-daemon
2012-08-16 14:31 ` bugzilla-daemon
2012-08-16 15:16 ` bugzilla-daemon
2012-08-16 17:05 ` bugzilla-daemon
2012-08-16 17:21 ` bugzilla-daemon
2012-08-16 17:22 ` bugzilla-daemon
2012-08-16 17:29 ` bugzilla-daemon
2012-08-16 17:37 ` bugzilla-daemon
2012-08-16 17:39 ` bugzilla-daemon
2012-08-16 17:41 ` bugzilla-daemon
2012-08-16 18:23 ` bugzilla-daemon
2012-08-16 18:59 ` bugzilla-daemon
2012-08-17 10:09 ` bugzilla-daemon
2012-08-17 13:09 ` bugzilla-daemon
2012-08-17 13:09 ` bugzilla-daemon
2012-08-20  7:32 ` bugzilla-daemon
2012-09-05 20:41 ` bugzilla-daemon
2012-12-28  3:34 ` bugzilla-daemon
2013-01-07 17:16 ` bugzilla-daemon

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=bug-41265-502-Tr5isIhyxY@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).