Re: Heads Up: default NFS server changing to the new one

2011-06-06 Thread Rick Macklem
Chris Forgeron wrote: [stuff snipped] I hope to do a speed test comparison between new and old NFS servers this weekend - At this stage, my feeling is that the new NFS server is at least as fast. I suspect tests will show it to be faster (at least the code looks faster. :-) ). Well, I

Re: NEW_PCIB? pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff

2011-06-06 Thread John Baldwin
On Sunday, June 05, 2011 8:23:53 pm John wrote: Hi Folks, I just attempted to update an HP385G0 system from current as of 4-15-2011 to 6-2-2011. The new system will not boot, and shows the following message when it hangs: pcib1:ACPI PCI-PCI bridge at device 3.0 on pci0 pcib1: failed

Re: pcib allocation failure

2011-06-06 Thread John Baldwin
On Saturday, May 28, 2011 9:45:48 pm deeptec...@gmail.com wrote: On Thu, May 26, 2011 at 3:40 PM, John Baldwin j...@freebsd.org wrote: Ohh, you have two devices behind this bridge that have prefetch ranges. As a hack, can you try this: Index: pci_pci.c

[head tinderbox] failure on powerpc64/powerpc

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 14:58:07 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 14:58:07 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2011-06-06 14:58:07 - cleaning the object tree TB --- 2011-06-06 14:58:29 - cvsupping the source tree TB --- 2011-06-06 14:58:29 -

[head tinderbox] failure on sparc64/sparc64

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 15:04:05 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 15:04:05 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2011-06-06 15:04:05 - cleaning the object tree TB --- 2011-06-06 15:04:16 - cvsupping the source tree TB --- 2011-06-06 15:04:16 -

[head tinderbox] failure on powerpc/powerpc

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 14:41:01 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 14:41:01 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2011-06-06 14:41:01 - cleaning the object tree TB --- 2011-06-06 14:41:13 - cvsupping the source tree TB --- 2011-06-06 14:41:13 -

[head tinderbox] failure on arm/arm

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 16:30:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 16:30:00 - starting HEAD tinderbox run for arm/arm TB --- 2011-06-06 16:30:00 - cleaning the object tree TB --- 2011-06-06 16:30:14 - cvsupping the source tree TB --- 2011-06-06 16:30:14 -

[RFC] 'failok' mount(8) flag

2011-06-06 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I think sometimes it's desirable to mark a few file systems as 'failok', which means it's Ok to have these mounts failed on boot and something else (a script, cron job, etc) will handle the case. Here is a proposed patch to implement that,

[head tinderbox] failure on i386/pc98

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 16:30:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 16:30:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2011-06-06 16:30:00 - cleaning the object tree TB --- 2011-06-06 16:30:19 - cvsupping the source tree TB --- 2011-06-06 16:30:19 -

[head tinderbox] failure on amd64/amd64

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 16:30:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 16:30:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2011-06-06 16:30:00 - cleaning the object tree TB --- 2011-06-06 16:30:23 - cvsupping the source tree TB --- 2011-06-06 16:30:23 -

[head tinderbox] failure on i386/i386

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 16:30:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 16:30:00 - starting HEAD tinderbox run for i386/i386 TB --- 2011-06-06 16:30:00 - cleaning the object tree TB --- 2011-06-06 16:30:24 - cvsupping the source tree TB --- 2011-06-06 16:30:24 -

[head tinderbox] failure on ia64/ia64

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 17:21:39 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 17:21:39 - starting HEAD tinderbox run for ia64/ia64 TB --- 2011-06-06 17:21:39 - cleaning the object tree TB --- 2011-06-06 17:21:50 - cvsupping the source tree TB --- 2011-06-06 17:21:50 -

Re: [RFC] 'failok' mount(8) flag

2011-06-06 Thread Poul-Henning Kamp
In message 4ded15b1.8020...@delphij.net, Xin LI writes: I think sometimes it's desirable to mark a few file systems as 'failok', which means it's Ok to have these mounts failed on boot and something else (a script, cron job, etc) will handle the case. Good idea. (This was one of the ideas that

Re: Boot halts on Thinkpad X220 (Sandy Bridge)

2011-06-06 Thread Xin LI
On Tue, May 31, 2011 at 5:03 PM, Jung-uk Kim j...@freebsd.org wrote: [...] I found something strange about this BIOS (well, if we can call it that).  Please try this: Index: sys/dev/atkbdc/atkbd.c === --- sys/dev/atkbdc/atkbd.c  

[head tinderbox] failure on mips/mips

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 18:24:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 18:24:00 - starting HEAD tinderbox run for mips/mips TB --- 2011-06-06 18:24:00 - cleaning the object tree TB --- 2011-06-06 18:24:06 - cvsupping the source tree TB --- 2011-06-06 18:24:06 -

[head tinderbox] failure on powerpc64/powerpc

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 18:30:11 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 18:30:11 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2011-06-06 18:30:11 - cleaning the object tree TB --- 2011-06-06 18:30:16 - cvsupping the source tree TB --- 2011-06-06 18:30:16 -

[head tinderbox] failure on sparc64/sparc64

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 18:44:15 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 18:44:15 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2011-06-06 18:44:15 - cleaning the object tree TB --- 2011-06-06 18:44:22 - cvsupping the source tree TB --- 2011-06-06 18:44:22 -

[head tinderbox] failure on powerpc/powerpc

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 18:24:29 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 18:24:29 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2011-06-06 18:24:29 - cleaning the object tree TB --- 2011-06-06 18:24:36 - cvsupping the source tree TB --- 2011-06-06 18:24:36 -

[head tinderbox] failure on arm/arm

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 20:10:01 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 20:10:01 - starting HEAD tinderbox run for arm/arm TB --- 2011-06-06 20:10:01 - cleaning the object tree TB --- 2011-06-06 20:10:10 - cvsupping the source tree TB --- 2011-06-06 20:10:10 -

Re: [PATCH] Add the infrastructure for supporting an infinite number of CPUs

2011-06-06 Thread Attilio Rao
2011/6/4 Fabian Keil freebsd-lis...@fabiankeil.de: Attilio Rao atti...@freebsd.org wrote: Current maximum number of CPUs supported by the FreeBSD kernel is 32. That number cames from indirectly by the fact that we have a cpumask_t type, representing a mask of CPUs, which is an unsigned int

[head tinderbox] failure on ia64/ia64

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 21:02:12 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 21:02:12 - starting HEAD tinderbox run for ia64/ia64 TB --- 2011-06-06 21:02:12 - cleaning the object tree TB --- 2011-06-06 21:02:17 - cvsupping the source tree TB --- 2011-06-06 21:02:17 -

[head tinderbox] failure on mips/mips

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 22:24:31 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 22:24:31 - starting HEAD tinderbox run for mips/mips TB --- 2011-06-06 22:24:31 - cleaning the object tree TB --- 2011-06-06 22:24:36 - cvsupping the source tree TB --- 2011-06-06 22:24:36 -

[head tinderbox] failure on sparc64/sparc64

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-06 23:27:55 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-06 23:27:55 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2011-06-06 23:27:55 - cleaning the object tree TB --- 2011-06-06 23:28:01 - cvsupping the source tree TB --- 2011-06-06 23:28:01 -

Re: NEW_PCIB? pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff

2011-06-06 Thread John
- John Baldwin's Original Message - On Sunday, June 05, 2011 8:23:53 pm John wrote: Hi Folks, I just attempted to update an HP385G0 system from current as of 4-15-2011 to 6-2-2011. The new system will not boot, and shows the following message when it hangs: pcib1:ACPI

[head tinderbox] failure on arm/arm

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-07 01:30:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-07 01:30:00 - starting HEAD tinderbox run for arm/arm TB --- 2011-06-07 01:30:00 - cleaning the object tree TB --- 2011-06-07 01:30:08 - cvsupping the source tree TB --- 2011-06-07 01:30:08 -

Re: pcib allocation failure

2011-06-06 Thread deeptec...@gmail.com
On Mon, Jun 6, 2011 at 4:52 PM, John Baldwin j...@freebsd.org wrote: Can you try out this change.  It is a possible real solution (or at least a stopgap until we start using multipass to untangle the resource mess a bit further): [snip] that doesn't work. i get an allocation failure.

[head tinderbox] failure on ia64/ia64

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-07 02:21:07 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-07 02:21:07 - starting HEAD tinderbox run for ia64/ia64 TB --- 2011-06-07 02:21:07 - cleaning the object tree TB --- 2011-06-07 02:21:14 - cvsupping the source tree TB --- 2011-06-07 02:21:14 -

[head tinderbox] failure on mips/mips

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-07 03:43:13 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-07 03:43:13 - starting HEAD tinderbox run for mips/mips TB --- 2011-06-07 03:43:13 - cleaning the object tree TB --- 2011-06-07 03:43:21 - cvsupping the source tree TB --- 2011-06-07 03:43:21 -

[head tinderbox] failure on sparc64/sparc64

2011-06-06 Thread FreeBSD Tinderbox
TB --- 2011-06-07 04:41:15 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-07 04:41:15 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2011-06-07 04:41:15 - cleaning the object tree TB --- 2011-06-07 04:41:22 - cvsupping the source tree TB --- 2011-06-07 04:41:22 -

RFC: need one IFCAP bit for NETMAP

2011-06-06 Thread Luigi Rizzo
hi, in order to import netmap support into the tree (see http://info.iet.unipi.it/~luigi/netmap ), i need to use one of the if_cap{abilities|enable} bits to report that the interface supports this mode and record whether the mode is enabled or not. Bit 0x10 is currently the first unused bit