[head tinderbox] failure on sparc64/sparc64

2013-12-30 Thread FreeBSD Tinderbox
TB --- 2013-12-31 06:35:11 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-31 06:35:11 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

Re: new Xorg (KMS, etc.) for Radeon 9600

2013-12-30 Thread Adrian Chadd
On 30 December 2013 16:32, wrote: > > > Oops, I meant panics, not lockups. The kernel panics exactly because -- as I > gather -- the assertions are already there. > > There are lockup issues even with the patch applied (for the most part, only > when using, in Xorg.conf: Option "AccelMethod" "EXA

Re: new Xorg (KMS, etc.) for Radeon 9600

2013-12-30 Thread dt71
Adrian Chadd wrote, On 12/30/2013 22:17: On 17 December 2013 22:41, wrote: It fixes non-deterministic lockups when the (old, drm1) r300 drivers are used. According to John Baldwin [1]: "The drm code is doing a copyin() while holding a mutex (which is not allowed)." The latest version of the p

Re: newcons + device.hints

2013-12-30 Thread Aleksandr Rybalko
On Wed, 11 Dec 2013 14:10:32 +0400 "Vladimir A. Noskov" wrote: > > On 11.12.2013 14:06, Vladimir A. Noskov wrote: > Thanks. > I waiting set :) > > > > > On 11.12.2013 00:54, Ed Schouten wrote: > >> > >> Hey Vladimir, > >> > >> You'd better ask this question on the lists. I've added current@ > >

Re: new Xorg (KMS, etc.) for Radeon 9600

2013-12-30 Thread Adrian Chadd
On 17 December 2013 22:41, wrote: > Jean-Sébastien Pédron wrote, On 12/17/2013 22:20: > >> On 16.12.2013 08:36, d...@gmx.com wrote: >>> >>> Still nobody wants to apply Robert Noland's DRM patch? >> >> >> What problem(s) does this patch fix? > > > It fixes non-deterministic lockups when the (old,

[head tinderbox] failure on powerpc64/powerpc

2013-12-30 Thread FreeBSD Tinderbox
TB --- 2013-12-30 18:59:21 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-30 18:59:21 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

[head tinderbox] failure on powerpc/powerpc

2013-12-30 Thread FreeBSD Tinderbox
TB --- 2013-12-30 18:25:11 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-30 18:25:11 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

[head tinderbox] failure on sparc64/sparc64

2013-12-30 Thread FreeBSD Tinderbox
TB --- 2013-12-30 19:25:17 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-30 19:25:17 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

Re: smp_rendezvous_cpus() deadlock

2013-12-30 Thread Konstantin Belousov
On Sun, Dec 29, 2013 at 04:36:18PM -0500, Mark Johnston wrote: > Hello, > > While experimenting with some userland DTrace scripts, I seem to > be consistently able to trigger a deadlock between smp_rendezvous_cpus() > (called periodically by DTrace) and smp_targeted_tlb_shootdown(): > > spin lock

[head tinderbox] failure on powerpc64/powerpc

2013-12-30 Thread FreeBSD Tinderbox
TB --- 2013-12-30 07:49:29 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-30 07:49:29 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

[head tinderbox] failure on powerpc/powerpc

2013-12-30 Thread FreeBSD Tinderbox
TB --- 2013-12-30 07:12:09 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-30 07:12:09 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013