[head tinderbox] failure on sparc64/sun4v

TB --- 2010-03-01 05:17:27 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-01 05:17:27 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2010-03-01 05:17:27 - cleaning the object tree TB --- 2010-03-01 05:17:46 - cvsupping the source tree TB --- 2010-03-01 05:17:46 - /usr/b

[head tinderbox] failure on ia64/ia64

TB --- 2010-03-01 04:21:38 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-01 04:21:38 - starting HEAD tinderbox run for ia64/ia64 TB --- 2010-03-01 04:21:38 - cleaning the object tree TB --- 2010-03-01 04:21:58 - cvsupping the source tree TB --- 2010-03-01 04:21:58 - /usr/bin/c

[head tinderbox] failure on powerpc/powerpc

TB --- 2010-03-01 04:31:01 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-01 04:31:01 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2010-03-01 04:31:01 - cleaning the object tree TB --- 2010-03-01 04:31:13 - cvsupping the source tree TB --- 2010-03-01 04:31:13 - /usr

[head tinderbox] failure on sparc64/sparc64

TB --- 2010-03-01 04:32:21 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-01 04:32:21 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2010-03-01 04:32:21 - cleaning the object tree TB --- 2010-03-01 04:32:34 - cvsupping the source tree TB --- 2010-03-01 04:32:34 - /usr

[head tinderbox] failure on mips/mips

TB --- 2010-03-01 04:30:50 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-01 04:30:50 - starting HEAD tinderbox run for mips/mips TB --- 2010-03-01 04:30:50 - cleaning the object tree TB --- 2010-03-01 04:30:59 - cvsupping the source tree TB --- 2010-03-01 04:30:59 - /usr/bin/c

[head tinderbox] failure on amd64/amd64

TB --- 2010-03-01 03:35:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-01 03:35:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2010-03-01 03:35:00 - cleaning the object tree TB --- 2010-03-01 03:35:34 - cvsupping the source tree TB --- 2010-03-01 03:35:34 - /usr/bin

[head tinderbox] failure on i386/pc98

TB --- 2010-03-01 03:35:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-01 03:35:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2010-03-01 03:35:00 - cleaning the object tree TB --- 2010-03-01 03:35:30 - cvsupping the source tree TB --- 2010-03-01 03:35:30 - /usr/bin/c

[head tinderbox] failure on i386/i386

TB --- 2010-03-01 03:35:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-01 03:35:00 - starting HEAD tinderbox run for i386/i386 TB --- 2010-03-01 03:35:00 - cleaning the object tree TB --- 2010-03-01 03:35:31 - cvsupping the source tree TB --- 2010-03-01 03:35:31 - /usr/bin/c

[head tinderbox] failure on arm/arm

TB --- 2010-03-01 03:35:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-01 03:35:00 - starting HEAD tinderbox run for arm/arm TB --- 2010-03-01 03:35:00 - cleaning the object tree TB --- 2010-03-01 03:35:11 - cvsupping the source tree TB --- 2010-03-01 03:35:11 - /usr/bin/csu

Crash with today's HEAD (r204479) appears to be wlan-related

Loaded symbols for /boot/kernel/wpifw.ko #0 doadump () at pcpu.h:246 246 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:246 #1 0xc05f668f in boot (howto=260) at /usr/local/src/sys/kern/kern_shutdown.c:416 #2 0xc05f6972 in panic (fmt=Variable "fmt" is

check for jailed environment for adjkerntz

jail with "complete" type have standard crontab a file of tasks. However not all standard task are adapted for work in jail an environment. For example adjkerntz which generates adjkerntz [46733]: sysctl (set: "machdep.wall_cmos_clock"): Operation not permitted I suggest to give adjkerntz concept

Re: minidump fails on SMP machines

2010/2/28 Andrew Brampton : > Hello, > > When many interrupts are firing on my amd64 SMP machine, and a panic > occurs, dump will fail with the error "Attempt to write outside dump > device boundaries". This problem has been discussed before[1][2], and > I even filled a PR about it last year[3]. >

minidump fails on SMP machines

Hello, When many interrupts are firing on my amd64 SMP machine, and a panic occurs, dump will fail with the error "Attempt to write outside dump device boundaries". This problem has been discussed before[1][2], and I even filled a PR about it last year[3]. >From what I understand the reason this

Problem with new bwn driver on -CURRENT

I was extremely pleased to see this driver, so I could get off of the flaky NDIS version. I have a Dell Vostra 2510 with a LP bwn mini-PCI card. I have set if_bwn_load="YES" in /boot/loader.conf. I also have bwn_v4_lp_ucode_load="YES" set. The firmware and driver loads. However, if_bwn doesn't

Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver

Hi, Thanks for the work ! I have some problems here when I try to create a wlan interface : bwn_v4_ucode5: could not load firmware image, error 2 bwn0: the fw file(bwn_v4_ucode5) not found I have installed bwn-firmware-kmod from ports but the only files I have in /boot/modules are bwn_v4_lp_ucod

Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver

On Wed, Dec 23, 2009 at 11:51:34AM -0800, Weongyo Jeong wrote: > On Wed, Dec 23, 2009 at 08:18:48AM +, Aditya Sarawgi wrote: > > On Tue, Dec 22, 2009 at 07:53:31PM -0800, Weongyo Jeong wrote: > > > Hello, > > > > > > Now bwn(4) is available at the public and waiting test and review. The > > >

Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver

On Sat, Feb 27, 2010 at 01:15:35AM +0200, Alex RAY wrote: > Hi Weongyo, > > Can new siba release operate in systems like in this SVG image? > System example: CPU BCM5836 + Wi-Fi BCM4318 Recent changes of siba(4) by myself doesn't change code flow, layout and doesn't include enhancements if you're