Date: Thu, 20 Nov 2014 09:03:05 +0100 From: Felix Palmen <felix@palmen-it.de> To: freebsd-x11@freebsd.org Subject: Re: DRI not working, AMD E 300 with Radeon HD 6310 Message-ID: <24424480.8gKnz8UD4t@nexus> In-Reply-To: <2674870.PTfXXQznk8@nexus> References: <546CAD30.3060600@palmen-it.de> <7ceb971998008827645f5ea2b3989bac.squirrel@mx.waitman.net> <2674870.PTfXXQznk8@nexus>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Mittwoch, 19. November 2014, 22:06:52 schrieb Felix Palmen: > Meanwhile, still waiting for buildworld to finish, I found this: > https://bugs.freedesktop.org/show_bug.cgi?id=66963#c175 > > Different chip, different OS, but at least same error. I prepared a similar > patch against freebsd head (completely disabling the DMA ring for my chip) > just for testing purposes. I'll report here whether this does any good, just > in case someone else faces the same problem. Of course, this is an ugly > hack, intentionally disabling a feature in the driver, but if it really > helps, I could polish the patch so it only affects exactly the 0x9802 chip. > But, let's see first... Replying to myself: Patch probably won't be needed. First boot on r274708 looks great: [...] info: [drm] radeon: irq initialized. info: [drm] GART: num cpu pages 131072, num gpu pages 131072 info: [drm] Loading PALM Microcode info: [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). drmn0: info: WB enabled drmn0: info: fence driver on ring 0 use gpu addr 0x0000000018000c00 and cpu addr 0x0xfffff8001532bc00 drmn0: info: fence driver on ring 3 use gpu addr 0x0000000018000c0c and cpu addr 0x0xfffff8001532bc0c info: [drm] ring test on 0 succeeded in 1 usecs info: [drm] ring test on 3 succeeded in 1 usecs info: [drm] ib test on ring 0 succeeded in 0 usecs info: [drm] ib test on ring 3 succeeded in 0 usecs info: [drm] radeon_device_init: Taking over the fictitious range 0xe0000000-0xf0000000 [...] giving this in X: [...] [ 63.593] (II) RADEON(0): [DRI2] Setup complete [ 63.593] (II) RADEON(0): [DRI2] DRI driver: r600 [ 63.593] (II) RADEON(0): [DRI2] VDPAU driver: r600 [...] So it /probably/ was just a kernel bug. Trying now to rebuild r274708 without debugging options, like I had before: --- sys/amd64/conf/GENERIC 2014-11-12 13:30:36.000000000 +0100 +++ sys/amd64/conf/NODEBUG 2014-11-12 15:00:18.000000000 +0100 @@ -77,15 +77,6 @@ # Debugging support. Always need this: options KDB # Enable kernel debugger support. options KDB_TRACE # Print a stack trace for a panic. -# For full debugger support use (turn off in stable branch): -options DDB # Support DDB. -options GDB # Support remote GDB. -options DEADLKRES # Enable the deadlock resolver -options INVARIANTS # Enable calls of extra sanity checking -options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS -options WITNESS # Enable checks to detect deadlocks and cycles -options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed -options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24424480.8gKnz8UD4t>