similar to: [releng_10 tinderbox] failure on sparc64/sparc64

Displaying 20 results from an estimated 1100 matches similar to: "[releng_10 tinderbox] failure on sparc64/sparc64"

2013 Nov 13
2
[releng_10 tinderbox] failure on i386/i386
TB --- 2013-11-13 13:00:41 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-11-13 13:00:41 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-13 13:00:41 - starting RELENG_10 tinderbox run for i386/i386 TB --- 2013-11-13 13:00:41 - cleaning the
2003 Apr 12
1
GENERIC kern compile error 4.8-STABLE
GENERIC Kernel build failure just after stable-cvsup and buildworld. I have ensured that everything in /usr/obj was deleted before i began. Btw. /usr/obj <-- is a symlink to /Disk1/usrobj, because /usr partition was filled up. I have installed these packages from ports. db-2.7.7_1 The Berkeley DB package, revision 2 db3-3.3.11,1 The Berkeley DB package, revision 3
2013 Oct 31
3
[releng_10 tinderbox] failure on i386/pc98
TB --- 2013-10-31 19:50:43 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-10-31 19:50:43 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-10-31 19:50:43 - starting RELENG_10 tinderbox run for i386/pc98 TB --- 2013-10-31 19:50:43 - cleaning the
2003 Apr 14
2
4.8-STABLE GENERIC buildkernel fail
Hello, i've been here with this poblem before, now i installed the berkley db4 in /usr. But now it report another error, still at the same file. Please reply if you think you know the reason... I'm still running 4.6-STABLE, and would soon like the new 4.8-STABLE kernel made. Regards, Johan Christiansen _________ ===> vesa rm -f setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o vesa.ko
2012 Dec 04
2
[releng_8 tinderbox] failure on sparc64/sparc64
TB --- 2012-12-04 23:10:18 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-12-04 23:10:18 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-12-04 23:10:18 - starting RELENG_8 tinderbox run for sparc64/sparc64 TB --- 2012-12-04 23:10:18 - cleaning
2013 Feb 26
1
[releng_9 tinderbox] failure on arm/arm
TB --- 2013-02-26 21:23:55 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-26 21:23:55 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa at freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-26 21:23:55 - starting RELENG_9 tinderbox run for arm/arm TB --- 2013-02-26 21:23:55 - cleaning the
2012 Apr 08
0
[releng_9 tinderbox] failure on sparc64/sparc64
TB --- 2012-04-08 08:26:29 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-04-08 08:26:29 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-04-08 08:26:29 - starting RELENG_9 tinderbox run for sparc64/sparc64 TB --- 2012-04-08 08:26:29 - cleaning the
2013 Nov 25
7
[releng_8 tinderbox] failure on i386/i386
TB --- 2013-11-25 17:30:12 - tinderbox 2.20 running on freebsd-legacy2.sentex.ca TB --- 2013-11-25 17:30:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-25 17:30:12 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2013-11-25 17:30:12 -
2012 Dec 11
0
[releng_9 tinderbox] failure on i386/i386
TB --- 2012-12-11 03:57:29 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-12-11 03:57:29 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa at freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-12-11 03:57:29 - starting RELENG_9 tinderbox run for i386/i386 TB --- 2012-12-11 03:57:29 - cleaning the
2008 Jul 29
1
[releng_7 tinderbox] failure on sparc64/sparc64
TB --- 2008-07-29 09:37:14 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-07-29 09:37:14 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2008-07-29 09:37:14 - cleaning the object tree TB --- 2008-07-29 09:37:32 - cvsupping the source tree TB --- 2008-07-29 09:37:32 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB ---
2005 Nov 10
2
Re: www.centos.org - Contact the CentOS Development Team Form
Ravi Srivastava submitted the following Information: Email ravi_prakash at ngri.res.in URL www.ngri.org.in Company National Geophysical Research Institute Location Hyderabad, India Comments Dear All, I am using CentOs 3.5 on a 64 bit Xeon machine. I wanted to install aic7xxx-6.3.9-rhel3.i686.rpm to use DAT 72 but it is giving following error message. Please help to resolve this problem: I took
2008 Jun 03
0
[releng_6 tinderbox] failure on sparc64/sparc64
TB --- 2008-06-03 09:06:24 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-03 09:06:24 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2008-06-03 09:06:24 - cleaning the object tree TB --- 2008-06-03 09:06:55 - cvsupping the source tree TB --- 2008-06-03 09:06:55 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/sparc64/sparc64/supfile TB ---
2005 Sep 09
3
SCSI controller setup
I have an IDE based PC running Linux/CentOS4 to which I wish to attach a scsi dlt. The host controller is an Adaptec AHA3940 something that lspci reports as: SCSI storage controller: Initio Corporation 360P (rev 02). I would like to have the system load the driver for this adapter at boot but I have two problems: 1. I am not sure which driver to use; and 2. I do not know how to force
2008 Dec 15
2
Zaptel / TDM400P card stopped working
Hi I have a Dell PE2300 with a Digium TDM400P line card in it (with one module to handle an inbound phone line). This is running on a Fedora 8 system with Asterisk 1.4.21.2-1.fc8 This system has been working nicely for about 12 months. After a recent move of office and relocation of the server Asterisk is back on line, but the TDM line card has stopped working. I have spent half a day
2005 Sep 22
1
LPFC support in Xen ?
Hi, Afraid I dont have a very new system to try out Xen.. It''s an ia32 PIII machine with 1GB memory (that''s gud i believe). When I try to build the initrd image for my xen kernel, i get error messages complaining about missing modules, so am trying to compile them on my own. Could find support for the remaining three, but am left with lpfcdd.ko. Couldnt find an appropriate
2007 Jul 20
2
Searching an Scsi Controller for CentOS 5
Hello, does CentOs 5 supports an Adaptec AHA-2940W/2940UW scsi controller (pci)? Is this controller maybe supported by the aic7xxx driver? I want to install CentOS 5 on my desktop pc but the currently installed pci scsi controller for my scanners (drivers: 2x tmscsim, 1x advansys) are not supported by CentOS. So I am searching for something else. Thanks in advanced. regards Olaf
2004 May 27
2
Tape drive problems
Hi, Hi, I have been googling, and can't find anything that will help me: mt -f /dev/st0 status /dev/st0: No such device or address Any suggestion? I am using CentOS 3 [RHEL ES3 without the licenses] The tape drive is recognized at boot [from dmesg] scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 <Adaptec 29160 Ultra160 SCSI adapter> aic7892:
2004 Apr 25
2
PRI Error T100P
I have seen this posted around the list a few times, but have never found my exact error or even a solution to this. I was getting this error every few seconds...... After moving the card to a different PCI slot and turning off some devices that are not needed. I was able to get the messages down to about every 10 minutes and the T1 card now is sitting in it's own intterupt. Apr 25 23:49:15
2003 Jun 25
2
Possible solution to Zaptel panics
Heya Mark (and others), Here's an update on my adventures while trying to debug the Zaptel-related panics, as discussed on this list a while back. While debugging the problem, I completely swapped the machine for an entirely different model (Supermicro dual Xeon 2.4GHz with 2Gb of RAM), put the cards in, recompiled * + Zaptel and administered my stress-test. The machine stayed up in excess
2001 Nov 10
3
root fs mounts as ext2, others ext3
I have ext2 compiled in the kernel (so i can mount the initrd image), all other filesystems are modules. The initrd image contains aic7xxx, jbd, and ext3 modules. /etc/mtab reports the filesystem mounted ext3 /proc/mounts reports it mounted ext2 /proc/filesystems lists ext3 If I umount other partitions that are ext3 the module becomes 'unused'. The filesystem was created