Re: newnfs pkgng database corruption?

2013-04-10 Thread Eggert, Lars
Hi, On Apr 11, 2013, at 0:16, Baptiste Daroussin wrote: > Will you be able to test it? yes. (But I will be traveling for the next two weeks and so the turnaround may be a bit longer than normal.) Lars ___ freebsd-current@freebsd.org mailing list http

Re: newnfs pkgng database corruption?

2013-04-10 Thread Eggert, Lars
Hi, On Apr 11, 2013, at 1:28, Rick Macklem wrote: > Error code 70 is ESTALE (or NFSERR_STALE, if you prefer). The server > replies with that when the file no longer exists. > > File locking doesn't stop a file from being removed, as far as I know. but the file is still there. Lars

Re: Intel D2500CC motherboard and strange RS232/UART behavior

2013-04-10 Thread matt
On 04/07/13 12:43, Lev Serebryakov wrote: > How could I debug this? Does this board have any fancy BIOS -> RS232 redirection? Could something like that cause these symptoms? Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mail

[head tinderbox] failure on powerpc64/powerpc

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-11 02:53:21 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-11 02:53: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-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-11 02:53:21 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-11 02:53: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 i386/pc98

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-11 01:51:45 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-11 01:51:45 - 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-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-11 03:13:08 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-11 03:13:08 - 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 ia64/ia64

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-11 01:51:45 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-11 01:51:45 - 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 mips64/mips

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-11 01:58:11 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-11 01:58: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 mips/mips

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-11 01:58:05 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-11 01:58:05 - 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 amd64/amd64

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 23:18:09 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 23:18: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

[head tinderbox] failure on i386/i386

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 23:18:09 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 23:18: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

[head tinderbox] failure on armv6/arm

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 23:18:09 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 23:18: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

[head tinderbox] failure on arm/arm

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 23:18:09 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 23:18: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

Re: Problems with axe(4) and checksum offloading

2013-04-10 Thread YongHyeon PYUN
On Wed, Apr 10, 2013 at 07:48:00PM +0200, Spil Oss wrote: > Hi YongHyeon, > > With the original unmodified .ko... > > ifconfig output as requested at bottom > > Static IP-configuration does not make a difference with the ipfw behaviour. > > ipfw ruleset (based on /etc/rc.firewall simple ruleset

Re: Unable to destroy promoted zfs dataset

2013-04-10 Thread Shawn Webb
On Wed, Apr 10, 2013 at 8:34 PM, Shawn Webb wrote: > Hey All, > > Unless I'm misunderstanding how to do what I'm trying to do, I'm unable to > destroy a zfs dataset that was cloned and subsequently promoted from > another dataset. Am I doing something wrong? > > Log of what I'm doing: > > [shawn@

Unable to destroy promoted zfs dataset

2013-04-10 Thread Shawn Webb
Hey All, Unless I'm misunderstanding how to do what I'm trying to do, I'm unable to destroy a zfs dataset that was cloned and subsequently promoted from another dataset. Am I doing something wrong? Log of what I'm doing: [shawn@shawn-vm-host ~]$ sudo zfs send rpool/jails/www_template@2013-04-10|

Re: newnfs pkgng database corruption?

2013-04-10 Thread Rick Macklem
Lars Eggert wrote: > Hi, > > on a diskless server, I keep the ports tree and pkgng databases on a > newnfs NFSv4 mount. After a bunch of "portmaster -a" runs, the pkgng > sqlite database appears to get corrupted. For example, when I try to > update an existing port, this happens: > > root@five:~

Re: newnfs pkgng database corruption?

2013-04-10 Thread Baptiste Daroussin
On Wed, Apr 10, 2013 at 08:09:42AM +, Eggert, Lars wrote: > Hi, > > On Apr 10, 2013, at 10:02, Baptiste Daroussin wrote: > > This can usually happen when a user do not have the nfs lock system started. > > Are you sure that nfs lock is correctly started? > > with NFSv4, the locking system is

Re: Problems with axe(4) and checksum offloading

2013-04-10 Thread Spil Oss
Hi YongHyeon, With the original unmodified .ko... ifconfig output as requested at bottom Static IP-configuration does not make a difference with the ipfw behaviour. ipfw ruleset (based on /etc/rc.firewall simple ruleset) 00010 allow ip from any to me dst-port 22 recv ue0 00010 allow tcp from me

Re: Intel D2500CC motherboard and strange RS232/UART behavior

2013-04-10 Thread Lev Serebryakov
Hello, John. You wrote 10 апреля 2013 г., 18:20:34: JB> Ok, then you need to figure out what is actually failing to install an JB> interrupt handler (e.g. does bus_alloc_resource or bus_setup_intr fail?) uart.ko could not be used, and rebuilding system for this system takes time (a lot of it).

Re: Intel D2500CC motherboard and strange RS232/UART behavior

2013-04-10 Thread John Baldwin
On Wednesday, April 10, 2013 2:28:38 am Lev Serebryakov wrote: > Hello, John. > You wrote 10 апреля 2013 г., 0:58:22: > > >> Problem is, that every uart device now is independent from each > >> other in good "OOP" style, and it looks like interrupt sharing we > >> need one interrupt handler

Re: Intel D2500CC motherboard and strange RS232/UART behavior

2013-04-10 Thread John Baldwin
On Wednesday, April 10, 2013 3:04:15 am Poul-Henning Kamp wrote: > In message <1424327083.20130410103...@serebryakov.spb.ru>, Lev Serebryakov writ > es: > >Hello, Poul-Henning. > >You wrote 10 =E0=EF=F0=E5=EB=FF 2013 =E3., 0:52:04: > > > >>> Problem is, that every uart device now is independent f

[head tinderbox] failure on powerpc64/powerpc

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 09:36:07 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 09:36:07 - 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-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 09:03:33 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 09:03:33 - 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-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 09:45:27 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 09:45:27 - 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 i386/pc98

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 07:47:31 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 07:47:31 - 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 ia64/ia64

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 07:57:06 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 07:57:06 - 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 mips64/mips

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 08:33:09 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 08:33: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

[head tinderbox] failure on mips/mips

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 08:00:01 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 08:00:01 - 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 amd64/amd64

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 04:50:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 04:50:20 - 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: newnfs pkgng database corruption?

2013-04-10 Thread Eggert, Lars
Hi, On Apr 10, 2013, at 10:02, Baptiste Daroussin wrote: > This can usually happen when a user do not have the nfs lock system started. > Are you sure that nfs lock is correctly started? with NFSv4, the locking system is integrated with the main protocol, it's no longer separate. > If that is

Re: newnfs pkgng database corruption?

2013-04-10 Thread Baptiste Daroussin
On Wed, Apr 10, 2013 at 07:42:30AM +, Eggert, Lars wrote: > Hi, > > on a diskless server, I keep the ports tree and pkgng databases on a newnfs > NFSv4 mount. After a bunch of "portmaster -a" runs, the pkgng sqlite database > appears to get corrupted. For example, when I try to update an exi

[head tinderbox] failure on i386/i386

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 04:50:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 04:50:20 - 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 arm/arm

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 04:50:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 04:50:20 - 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 armv6/arm

2013-04-10 Thread FreeBSD Tinderbox
TB --- 2013-04-10 04:50:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-10 04:50:20 - 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

newnfs pkgng database corruption?

2013-04-10 Thread Eggert, Lars
Hi, on a diskless server, I keep the ports tree and pkgng databases on a newnfs NFSv4 mount. After a bunch of "portmaster -a" runs, the pkgng sqlite database appears to get corrupted. For example, when I try to update an existing port, this happens: root@five:~ # portmaster ports-mgmt/pkg ...

Re: Intel D2500CC motherboard and strange RS232/UART behavior

2013-04-10 Thread Adrian Chadd
On 9 April 2013 23:28, Lev Serebryakov wrote: > Hello, John. > You wrote 10 апреля 2013 г., 0:58:22: > >>> Problem is, that every uart device now is independent from each >>> other in good "OOP" style, and it looks like interrupt sharing we >>> need one interrupt handler per irq (not per dev

Re: Intel D2500CC motherboard and strange RS232/UART behavior

2013-04-10 Thread Poul-Henning Kamp
In message <1424327083.20130410103...@serebryakov.spb.ru>, Lev Serebryakov writ es: >Hello, Poul-Henning. >You wrote 10 =E0=EF=F0=E5=EB=FF 2013 =E3., 0:52:04: > >>> Problem is, that every uart device now is independent from each >>> other in good "OOP" style, and it looks like interrupt sharing w