Re: panic on vt / kms rv610

2014-05-15 Thread Aleksandr Rybalko
On Wed, 14 May 2014 08:29:32 -0700 Mark Atkinson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I updated -current to r265915 w/ amd64 kernel and I get a panic > when I startx instantly (no video output of panic). There is a LOR > right before the panic. > > This is built using

[RFC] remove dead code from link_elf.c

2014-05-15 Thread Oliver Pinter
Hi all! I found that the SPARSE_MAPPING used only in sys/kern/link_elf.c file, and no other place in kernel, nor in generated codes in /usr/obj/... op@pandora-d opBSD.git> git grep -i SPARSE_MAPPING sys/kern/link_elf.c:#ifdef SPARSE_MAPPING sys/kern/link_elf.c:#ifdef SPARSE_MAPPING sys/kern/link_

Re: [RFC] remove dead code from link_elf.c

2014-05-15 Thread Konstantin Belousov
On Thu, May 15, 2014 at 03:36:51PM +0200, Oliver Pinter wrote: > Hi all! > > I found that the SPARSE_MAPPING used only in sys/kern/link_elf.c file, > and no other place in kernel, nor in generated codes in /usr/obj/... > > op@pandora-d opBSD.git> git grep -i SPARSE_MAPPING > sys/kern/link_elf.c:#

Gallium debugging and crash dumps

2014-05-15 Thread Michael Jung
Hi: If there is a better list to post this to please let me know. I've started playing with VT and gallium. I boot on ZFS but have a UFS drive and swap partition. Anyone with idea's why I'm not getting any crash info? I am guessing it is because the machine is not rebooting but locks up ha

Re: [RFC] remove dead code from link_elf.c

2014-05-15 Thread Oliver Pinter
On 5/15/14, Konstantin Belousov wrote: > On Thu, May 15, 2014 at 03:36:51PM +0200, Oliver Pinter wrote: >> Hi all! >> >> I found that the SPARSE_MAPPING used only in sys/kern/link_elf.c file, >> and no other place in kernel, nor in generated codes in /usr/obj/... >> >> op@pandora-d opBSD.git> git

Re: Gallium debugging and crash dumps

2014-05-15 Thread Michael Jung
On , Michael Jung wrote: Hi: If there is a better list to post this to please let me know. I've started playing with VT and gallium. I boot on ZFS but have a UFS drive and swap partition. Anyone with idea's why I'm not getting any crash info? I am guessing it is because the machine is not

Re: Gallium debugging and crash dumps

2014-05-15 Thread Alan Somers
On Thu, May 15, 2014 at 2:33 PM, Michael Jung wrote: > On , Michael Jung wrote: >> >> Hi: >> >> If there is a better list to post this to please let me know. >> >> I've started playing with VT and gallium. I boot on ZFS but have a UFS >> drive >> and swap partition. Anyone with idea's why I'm not

Re: Gallium debugging and crash dumps

2014-05-15 Thread Michael Jung
On , Michael Jung wrote: On , Michael Jung wrote: Hi: If there is a better list to post this to please let me know. I've started playing with VT and gallium. I boot on ZFS but have a UFS drive and swap partition. Anyone with idea's why I'm not getting any crash info? I am guessing it is b

[head tinderbox] failure on ia64/ia64

2014-05-15 Thread FreeBSD Tinderbox
TB --- 2014-05-15 22:30:39 - tinderbox 2.21 running on freebsd-current.sentex.ca TB --- 2014-05-15 22:30:39 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

[head tinderbox] failure on mips/mips

2014-05-15 Thread FreeBSD Tinderbox
TB --- 2014-05-15 22:57:03 - tinderbox 2.21 running on freebsd-current.sentex.ca TB --- 2014-05-15 22:57:03 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

[head tinderbox] failure on mips64/mips

2014-05-15 Thread FreeBSD Tinderbox
TB --- 2014-05-15 23:17:58 - tinderbox 2.21 running on freebsd-current.sentex.ca TB --- 2014-05-15 23:17:58 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

[head tinderbox] failure on sparc64/sparc64

2014-05-15 Thread FreeBSD Tinderbox
TB --- 2014-05-16 00:15:22 - tinderbox 2.21 running on freebsd-current.sentex.ca TB --- 2014-05-16 00:15:22 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

[head tinderbox] failure on powerpc/powerpc

2014-05-15 Thread FreeBSD Tinderbox
TB --- 2014-05-15 23:38:16 - tinderbox 2.21 running on freebsd-current.sentex.ca TB --- 2014-05-15 23:38:16 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

"operation not permitted" during buildworld/universe

2014-05-15 Thread Bjoern A. Zeeb
Hi, here’s an excerpt from buildworld during make universe; I see this on all architectures. Does anyone else see this or know why this suddenly happens? ... ===> include/protocols (buildincludes) ===> include/rpcsvc (buildincludes) ===> include/rpc (buildincludes) ===> include/xlocale (buildi

[head tinderbox] failure on powerpc64/powerpc

2014-05-15 Thread FreeBSD Tinderbox
TB --- 2014-05-16 00:14:18 - tinderbox 2.21 running on freebsd-current.sentex.ca TB --- 2014-05-16 00:14:18 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014