Re: sysctl -a is slow

jhell wrote: On 09/19/2010 09:28, David Xu wrote: just typed sysctl -a on keyboard, and found it is slow, sometimes it has been stuck for a few seconds, further studied,I found it is stucked at sysctl kern.geom: %/usr/bin/time sysctl -a kern.geom kern.geom.collectstats: 1 kern.geom.debugflags:

[HEADS UP] recent ld is needed to build kernel

Sorry, I should have sent out this earlier. Please note an entry in UPDATING from 20100915: A workaround for a fixed ld bug has been removed in kernel code, so make sure that your system ld is built from sources after revision 210245 (r211583 if building head kernel on stable/8, r211584 for stab

Re: Crash during boot of current (rev 212885)

on 20/09/2010 08:33 Randall Stewart said the following: > Andrly: > > Ok.. > > I can do that. > > I can positively say that when I have a kernel with 212646.. all is well. > > But a kernel with 212647 crashes as described below... > > I will ship you the read-elf offlist I assume you have che

Re: Crash during boot of current (rev 212885)

Andrly: Ok.. I can do that. I can positively say that when I have a kernel with 212646.. all is well. But a kernel with 212647 crashes as described below... I will ship you the read-elf offlist R On Sep 19, 2010, at 9:40 PM, Andriy Gapon wrote: on 20/09/2010 06:38 Randall Stewart said

Re: sysctl -a is slow

On 09/19/2010 09:28, David Xu wrote: > just typed sysctl -a on keyboard, and found it is slow, sometimes > it has been stuck for a few seconds, further studied,I found it is > stucked at sysctl kern.geom: > > %/usr/bin/time sysctl -a kern.geom > kern.geom.collectstats: 1 > kern.geom.debugflags: 0

[head tinderbox] failure on arm/arm

TB --- 2010-09-20 04:55:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-20 04:55:00 - starting HEAD tinderbox run for arm/arm TB --- 2010-09-20 04:55:00 - cleaning the object tree TB --- 2010-09-20 04:55:38 - cvsupping the source tree TB --- 2010-09-20 04:55:38 - /usr/bin/csu

Re: Crash during boot of current (rev 212885)

on 20/09/2010 06:38 Randall Stewart said the following: > Hi Lawrence: > > I am currently doing a binary search.. > > I know that 212660 shows the break. > > I am just about to try 212560 ;-) > > If that works I will update to 212646 and see if it works.. ;-) Randall, please also make sure th

Re: Crash during boot of current (rev 212885)

Hi Lawrence: I am currently doing a binary search.. I know that 212660 shows the break. I am just about to try 212560 ;-) If that works I will update to 212646 and see if it works.. ;-) R On Sep 19, 2010, at 7:31 PM, Lawrence Stewart wrote: Hiya Randall! On 09/20/10 08:56, Randall Stewart

Re: Crash during boot of current (rev 212885)

Hiya Randall! On 09/20/10 08:56, Randall Stewart wrote: > Hey all: > > I am now seeing a crash when I boot my Intel (in 64 bit more)... > > Its very early in the boot process.. and thus no crash dump ;-0 > > Its in > > netisr_start_swi() > > When it initializes netisr_mtx with a mtx_init() it

Re: gptboot rewrite, bootonce, etc.

Hi PJD! Can you this patcheset release for 7-STABLE? On 9/19/10, Boris Samorodov wrote: > Hi! > > On Sat, 18 Sep 2010 01:45:42 +0200 Pawel Jakub Dawidek wrote: > >> My company was in need for functionality similar to nextboot(8), but on >> boot loader level, so we can have two partitions we boot

Crash during boot of current (rev 212885)

Hey all: I am now seeing a crash when I boot my Intel (in 64 bit more)... Its very early in the boot process.. and thus no crash dump ;-0 Its in netisr_start_swi() When it initializes netisr_mtx with a mtx_init() it crashes saying that netisr_mtx is unaligned... (the address ddb shows for net

Re: Null modem to USB wire not working

2010/9/19 Boris Samorodov : > On Sun, 19 Sep 2010 21:25:36 +0200 David DEMELIER wrote: > >> I just bought a null modem to USB from Profilic and it isn't >> recognized by FreeBSD. > >> It's a chipset Prolific Technology Inc. > >> Sep 19 21:19:15 Melon root: Unknown USB device: vendor 0x067b product

Re: Null modem to USB wire not working

On Sun, 19 Sep 2010 21:25:36 +0200 David DEMELIER wrote: > I just bought a null modem to USB from Profilic and it isn't > recognized by FreeBSD. > It's a chipset Prolific Technology Inc. > Sep 19 21:19:15 Melon root: Unknown USB device: vendor 0x067b product > 0x2303 bus uhub6 > Sep 19 21:19:15

Null modem to USB wire not working

Hi, I just bought a null modem to USB from Profilic and it isn't recognized by FreeBSD. It's a chipset Prolific Technology Inc. Sep 19 21:19:15 Melon root: Unknown USB device: vendor 0x067b product 0x2303 bus uhub6 Sep 19 21:19:15 Melon kernel: ugen6.2: at usbus6 Is there any driver I can use

[head tinderbox] failure on powerpc64/powerpc

TB --- 2010-09-19 15:58:12 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-19 15:58:12 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2010-09-19 15:58:12 - cleaning the object tree TB --- 2010-09-19 15:59:10 - cvsupping the source tree TB --- 2010-09-19 15:59:10 - /u

Re: gptboot rewrite, bootonce, etc.

Hi! On Sat, 18 Sep 2010 01:45:42 +0200 Pawel Jakub Dawidek wrote: > My company was in need for functionality similar to nextboot(8), but on > boot loader level, so we can have two partitions we boot from where one > is known to be good and the other is used for upgrades. We upgrade by > dd(1)ing

[head tinderbox] failure on sparc64/sun4v

TB --- 2010-09-19 16:13:53 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-19 16:13:53 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2010-09-19 16:13:53 - cleaning the object tree TB --- 2010-09-19 16:14:22 - cvsupping the source tree TB --- 2010-09-19 16:14:22 - /usr/b

Re: [head tinderbox] failure on sparc64/sparc64

Sorry for the tinderbox breakagage again. Our main cvsup server seems to be triggering a bug in the em driver :( I will point it to an outside mirror for now... ---Mike At 12:38 PM 9/19/2010, FreeBSD Tinderbox wrote: TB --- 2010-09-19 16:01:48 - tinderbox 2.6 running on freebsd-cur

[head tinderbox] failure on sparc64/sparc64

TB --- 2010-09-19 16:01:48 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-19 16:01:48 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2010-09-19 16:01:48 - cleaning the object tree TB --- 2010-09-19 16:02:24 - cvsupping the source tree TB --- 2010-09-19 16:02:24 - /usr

[head tinderbox] failure on mips/mips

TB --- 2010-09-19 15:03:47 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-19 15:03:47 - starting HEAD tinderbox run for mips/mips TB --- 2010-09-19 15:03:47 - cleaning the object tree TB --- 2010-09-19 15:04:09 - cvsupping the source tree TB --- 2010-09-19 15:04:09 - /usr/bin/c

[head tinderbox] failure on ia64/ia64

TB --- 2010-09-19 13:52:09 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-19 13:52:09 - starting HEAD tinderbox run for ia64/ia64 TB --- 2010-09-19 13:52:09 - cleaning the object tree TB --- 2010-09-19 13:52:57 - cvsupping the source tree TB --- 2010-09-19 13:52:57 - /usr/bin/c

[head tinderbox] failure on arm/arm

TB --- 2010-09-19 13:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-19 13:00:00 - starting HEAD tinderbox run for arm/arm TB --- 2010-09-19 13:00:00 - cleaning the object tree TB --- 2010-09-19 13:00:51 - cvsupping the source tree TB --- 2010-09-19 13:00:51 - /usr/bin/csu

sysctl -a is slow

just typed sysctl -a on keyboard, and found it is slow, sometimes it has been stuck for a few seconds, further studied,I found it is stucked at sysctl kern.geom: %/usr/bin/time sysctl -a kern.geom kern.geom.collectstats: 1 kern.geom.debugflags: 0 kern.geom.label.debug: 0 kern.geom.label.ext2fs.en

Re: RFT: if_ath HAL refactoring

oops, I put it in the wrong place. Try again! adrian On 19 September 2010 18:03, Rui Paulo wrote: > On 19 Sep 2010, at 02:34, Adrian Chadd wrote: > >> On 19 September 2010 06:38, Rui Paulo wrote: >> >>> Can you also provide a diff against HEAD please? >> >> Done. It's in the same place; named

Re: RFT: if_ath HAL refactoring

On 19 Sep 2010, at 02:34, Adrian Chadd wrote: > On 19 September 2010 06:38, Rui Paulo wrote: > >> Can you also provide a diff against HEAD please? > > Done. It's in the same place; named "complete.diff". Hmm, I don't see it :-( Regards, -- Rui Paulo _