From: "Michel Dänzer" <michel@daenzer•net>
To: Gabriel Paubert <paubert@iram•es>
Cc: "Greg KH" <greg@kroah•com>,
linuxppc-dev@lists•ozlabs.org, dri-devel@lists•freedesktop.org,
LKML <linux-kernel@vger•kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix•de>,
"Dave Airlie" <airlied@gmail•com>
Subject: Re: Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ?
Date: Tue, 12 Apr 2011 13:46:10 +0200 [thread overview]
Message-ID: <1302608770.27054.36.camel@thor.local> (raw)
In-Reply-To: <20110412113033.GA16649@iram.es>
On Die, 2011-04-12 at 13:30 +0200, Gabriel Paubert wrote:=20
>=20
> On Mon, Apr 11, 2011 at 05:32:43PM +0200, Michel D=C3=A4nzer wrote:
> >=20
> > Have you ruled out any MSI related problems? I think the IRQ not workin=
g
> > could explain the symptoms...
>=20
> Booting with MSI disabled does not change anything. Actually on this
> machine the Ethernet (tigon3) uses MSI and everything is fine. OTOH,
> on my home PC (dual code Athlon64 4 1/2 years old), MSI has never worked.
Okay, the fact no_wb helps probably rules out an IRQ problem anyway.
> > Make sure this line changes to 'WB disabled' with no_wb=3D1. There's a
> > writeback endianness bug with modeset=3D1, see
> > http://lists.freedesktop.org/archives/dri-devel/2011-April/009960.html =
.
> >=20
>=20
> With no_wb=3D1 the driver goes a bit further but the X server ends
> up in an infinite ioctl loop and the logs are:=20
Which ioctl does it loop on? Please provide the Xorg.0.log file as well.
> kernel: [drm] radeon kernel modesetting enabled.
> kernel: checking generic (c0000000 140000) vs hw (c0000000 10000000)
> kernel: fb: conflicting fb hw usage radeondrmfb vs OFfb vga,Displa - remo=
ving generic driver
> kernel: [drm] initializing kernel modesetting (RV530 0x1002:0x71C7).
> kernel: radeon 0000:f1:00.0: Using 64-bit DMA iommu bypass
> kernel: [drm] register mmio base: 0xE8000000
> kernel: [drm] register mmio size: 65536
> kernel: radeon 0000:f1:00.0: Invalid ROM contents
> kernel: ATOM BIOS: X1650PRO
> kernel: [drm] Generation 2 PCI interface, using max accessible memory
> kernel: radeon 0000:f1:00.0: VRAM: 512M 0x0000000000000000 - 0x000000001F=
FFFFFF (512M used)
> kernel: radeon 0000:f1:00.0: GTT: 512M 0x0000000020000000 - 0x000000003FF=
FFFFF
> kernel: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> kernel: [drm] Driver supports precise vblank timestamp query.
> kernel: [drm] radeon: irq initialized.
> kernel: [drm] Detected VRAM RAM=3D512M, BAR=3D256M
> kernel: [drm] RAM width 128bits DDR
> kernel: [TTM] Zone kernel: Available graphics memory: 1003018 kiB.
> kernel: [TTM] Initializing pool allocator.
> kernel: [drm] radeon: 512M of VRAM memory ready
> kernel: [drm] radeon: 512M of GTT memory ready.
> kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
> kernel: [drm] radeon: 1 quad pipes, 2 z pipes initialized.
> kernel: [drm] PCIE GART of 512M enabled (table at 0x00040000).
> kernel: radeon 0000:f1:00.0: WB disabled
> kernel: [drm] Loading R500 Microcode
> kernel: [drm] radeon: ring at 0x0000000020001000
> kernel: [drm] ring test succeeded in 6 usecs
> kernel: [drm] radeon: ib pool ready.
> kernel: [drm] ib test succeeded in 0 usecs
> kernel: [drm] Radeon Display Connectors
> kernel: [drm] Connector 0:
> kernel: [drm] DVI-I
> kernel: [drm] HPD1
> kernel: [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7=
e4c
> kernel: [drm] Encoders:
> kernel: [drm] CRT1: INTERNAL_KLDSCP_DAC1
> kernel: [drm] DFP1: INTERNAL_KLDSCP_TMDS1
> kernel: [drm] Connector 1:
> kernel: [drm] S-video
> kernel: [drm] Encoders:
> kernel: [drm] TV1: INTERNAL_KLDSCP_DAC2
> kernel: [drm] Connector 2:
> kernel: [drm] DVI-I
> kernel: [drm] HPD2
> kernel: [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7=
e5c
> kernel: [drm] Encoders:
> kernel: [drm] CRT2: INTERNAL_KLDSCP_DAC2
> kernel: [drm] DFP3: INTERNAL_LVTM1
> kernel: [drm] Possible lm63 thermal controller at 0x4c
> kernel: [drm] fb mappable at 0xC00C0000
> kernel: [drm] vram apper at 0xC0000000
> kernel: [drm] size 9216000
> kernel: [drm] fb depth is 24
> kernel: [drm] pitch is 7680
> kernel: checking generic (c0000000 140000) vs hw (c0000000 10000000)
> kernel: fb: conflicting fb hw usage radeondrmfb vs OFfb vga,Displa - remo=
ving generic driver
> kernel: fb1: radeondrmfb frame buffer device
Hmm, I think this should say fb0, but that should only matter for
console, not X.
> kernel: drm: registered panic notifier
> kernel: [drm] Initialized radeon 2.8.0 20080528 for 0000:f1:00.0 on minor=
0
> kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
BTW, if your kernel contains commit
69a07f0b117a40fcc1a479358d8e1f41793617f2, can you try if reverting that
helps?
--=20
Earthling Michel D=C3=A4nzer | http://www.vmware.c=
om
Libre software enthusiast | Debian, X and DRI developer
next prev parent reply other threads:[~2011-04-12 11:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 23:52 Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ? Gabriel Paubert
2011-04-05 10:39 ` Michel Dänzer
2011-04-06 8:41 ` Uwe Kleine-König
2011-04-06 8:46 ` Dave Airlie
2011-04-06 20:43 ` Gabriel Paubert
2011-04-07 14:04 ` Michel Dänzer
2011-04-11 13:31 ` Gabriel Paubert
2011-04-11 15:32 ` Michel Dänzer
2011-04-12 11:30 ` Gabriel Paubert
2011-04-12 11:46 ` Michel Dänzer [this message]
2011-04-12 12:00 ` Gabriel Paubert
2011-04-12 17:29 ` Michel Dänzer
2011-04-13 7:59 ` Gabriel Paubert
2011-04-13 8:16 ` Benjamin Herrenschmidt
2011-04-13 10:01 ` Gabriel Paubert
2011-04-13 12:12 ` Michel Dänzer
2011-04-13 12:27 ` Gabriel Paubert
2011-04-13 14:15 ` Michel Dänzer
2011-04-13 20:01 ` Andy Furniss
2011-04-13 8:02 ` Gabriel Paubert
2011-04-13 8:12 ` small git lesson [Was: Re: Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ?] Uwe Kleine-König
[not found] ` <20110413081246.GK18850__3180.67204575545$1302682420$gmane$org@pengutronix.de>
2011-04-13 8:59 ` Andreas Schwab
2011-04-13 10:31 ` Gabriel Paubert
2011-04-13 12:17 ` Uwe Kleine-König
2011-04-07 11:25 ` Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ? Gabriel Paubert
2011-04-07 11:33 ` Gabriel Paubert
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=1302608770.27054.36.camel@thor.local \
--to=michel@daenzer$(echo .)net \
--cc=airlied@gmail$(echo .)com \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paubert@iram$(echo .)es \
--cc=u.kleine-koenig@pengutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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