From: Meelis Roos <mroos@ut.ee>
To: David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Radeon drm: Hang with posting GPU when PCI card is primary
Date: Thu, 9 Jun 2011 15:30:52 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1106091529130.11210@math.ut.ee> (raw)
In-Reply-To: <alpine.SOC.1.00.1106081406460.8911@math.ut.ee>
> [ 10.169900] [drm] radeon kernel modesetting enabled.
> [ 10.170270] radeon 0000:02:00.0: enabling device (0080 -> 0083)
> [ 10.170816] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
> [ 10.171044] radeon 0000:02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
> [ 10.172664] [drm] initializing kernel modesetting (RV100 0x1002:0x5159).
> [ 10.172897] [drm] register mmio base: 0xFEAF0000
> [ 10.173098] [drm] register mmio size: 65536
> [ 10.273609] [drm] GPU not posted. posting now...
Hmm. Added some printk-s (POSTing combios for example) and now it did
not hang any more but failed gracefully which is much better.
[ 5.769826] [drm] radeon kernel modesetting enabled.
[ 5.770181] radeon 0000:02:00.0: enabling device (0080 -> 0083)
[ 5.770677] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
[ 5.770903] radeon 0000:02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
[ 5.772142] [drm] initializing kernel modesetting (RV100 0x1002:0x5159).
[ 5.772363] [drm] register mmio base: 0xFEAF0000
[ 5.772529] [drm] register mmio size: 65536
[ 5.914902] [drm] GPU not posted. posting now...
[ 5.915086] [drm] POSTing combios
[ 5.938458] agpgart-intel 0000:00:00.0: AGP 2.0 bridge
[ 5.938697] agpgart: Couldn't find an AGP VGA controller.
[ 5.938914] radeon 0000:02:00.0: GTT: 64M 0xF8000000 - 0xFBFFFFFF
[ 5.939133] [drm] Generation 1 PCI interface in multifunction mode
[ 5.939352] [drm] Limiting VRAM to one aperture
[ 5.939569] radeon 0000:02:00.0: limiting VRAM to PCI aperture size
[ 5.939792] radeon 0000:02:00.0: VRAM: 128M 0x00000000E8000000 - 0x00000000EFFFFFFF (128M used)
[ 5.940212] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 5.940425] [drm] Driver supports precise vblank timestamp query.
[ 5.940666] [drm] radeon: irq initialized.
[ 5.941035] [drm] Detected VRAM RAM=128M, BAR=128M
[ 5.941263] [drm] RAM width 64bits SDR
[ 5.941607] [TTM] Zone kernel: Available graphics memory: 257508 kiB.
[ 5.941825] [TTM] Initializing pool allocator.
[ 5.942111] radeon 0000:02:00.0: df650c00 pin failed
[ 5.942351] radeon 0000:02:00.0: Fatal error during GPU init
[ 5.942567] [drm] radeon: finishing device.
[ 5.942783] [drm] radeon: cp finalized
[ 5.943014] [TTM] Trying to take down uninitialized memory manager type 1
[ 5.943243] [TTM] Finalizing pool allocator.
[ 5.943523] [TTM] Zone kernel: Used memory at exit: 0 kiB.
[ 5.943693] [drm] radeon: ttm finalized
[ 5.944380] radeon 0000:02:00.0: PCI INT A disabled
[ 5.944564] radeon: probe of 0000:02:00.0 failed with error -22
--
Meelis Roos (mroos@ut.ee) http://www.cs.ut.ee/~mroos/
prev parent reply other threads:[~2011-06-09 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 11:24 Radeon drm: Hang with posting GPU when PCI card is primary Meelis Roos
2011-06-09 12:30 ` Meelis Roos [this message]
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=alpine.SOC.1.00.1106091529130.11210@math.ut.ee \
--to=mroos@ut.ee \
--cc=airlied@linux.ie \
--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